This week only. Pastebin PRO Accounts Christmas Special! Don't miss out!Want more features on Pastebin? Sign Up, it's FREE!
Guest

Untitled

By: a guest on Oct 9th, 2010  |  syntax: None  |  size: 0.95 KB  |  views: 2,458  |  expires: Never
download  |  raw  |  embed  |  report abuse  |  print
This paste has a previous version, view the difference. Text below is selected. Please press Ctrl+C to copy to your clipboard. (⌘+C on Mac)
  1. Proof for anyone who still thinks the G2 has a "restore" mechanism, and a middle finger to T-Mobile for lying and actually going along with this story. It's really the same thing as the "NAND lock" on other recent phones, with a bug. It sucks, but it's nothing crazy like many websites would have you believe.
  2.  
  3. Right now, I'm (temp) rooted.
  4.  
  5. # cd /system
  6. # ls
  7. fonts
  8. usr
  9. lib
  10. framework
  11. media
  12. tts
  13. build.prop
  14. bin
  15. etc
  16. xbin
  17. app
  18. # mkdir lol
  19. # cd lol
  20. # echo "HI!" > sup.txt
  21. # cat sup.txt
  22. HI!
  23.  
  24. OK, we have a file on /system/lol/sup.txt. Now lets flush Linux's caches.
  25.  
  26. # echo 3 > /proc/sys/vm/drop_caches
  27. # ls
  28. ash: ls: not found
  29.  
  30. OH NOES, Busybox is gone! There's no built in ls command, but we can do this:
  31.  
  32. # echo *
  33. *
  34.  
  35. Nada. It's all gone. The controller is buggy, and is lying to Linux about actually writing the data (it's actually write protected the same way every other one of HTC's recent phones have been, which have all been cracked).
clone this paste RAW Paste Data