Root Post July 8 OTA Update Rooting?

[Desiel]

I am new to rooting, I have successfully rooted a Droid X using Z4 root...Duh!

I need help, I have a 2 week old Thunderbolt, a complete virgin (never rooted). I did the OTA update successfully 2 days ago, how stupid of me, now I need to root this thing desperately because I need wifi tethering.

How can I root and get wifi tethering on TB? Please advice in layman's terms.

Thanks

 

[scotty85]

id take a look at this thread:

http://androidforums.com/thunderbolt-all-things-root/372030-possible-root-after-ota-update.html

and at the sticky tunderbolt rooting methods.

the manual root listed on xda is the safest,and best way to root. you can chose to root now,but youll need to install the OTA rooted rom,or a custom rom, right away. or you can wait untill the root guide is updated to incude the "mr2" update.

 

[Desiel]

Does this mean that the manual root method on works on the 1.70.605.0? If so, how do I install the OTA rooted rom?

Please excuse my ignorant question, I am a complete novice on this thing and I am kinda scared of bricking this thing.

 

[scotty85]

Does this mean that the manual root method on works on the 1.70.605.0? If so, how do I install the OTA rooted rom?

Please excuse my ignorant question, I am a complete novice on this thing and I am kinda scared of bricking this thing.

as i explained in post 5 of the the above linked thread, android police said their original guide should still work. the exploits and downgrade RUU files will remain the same in the updated guide,with the only real difference being that the "custom RUU" you flash at the end will be 1.70.605.0 instead of the current 1.13.605.7

you will install the rooted OTA immediately after rooting by using directions in the sticky thread to go to clockwork recovery,and flash the rom you download from xda. there is a link to the xda thread in this one,here: http://androidforums.com/thunderbolt-all-things-root/371976-official-ota-rom.html

there is only 1 step that is a real risk of bricking your phone,and as long as you follow directions,the risk is slim to none. this risk is in step 6 of the xda guide,where you confirm the md5 sum of the s-off bootloader. if an output to a command you enter does not match what its supposed to,STOP. seek help in the chat link at the bottom of the guide thread. again,follow directions and make sure the outputs match when youre asked to verify them,and the risk is very,very small.

my advice is to go to sticky rooting methods thread, watch all the videos,check out some of the links. i personally used the 1st video to set up adb and get it ready. watch the steps 2-9 video,but dont try and use the video as a guide. just watch it and pay attetion so that you get an idea what youll be doing. follow the steps exactly in the xda guide and well be handing you your cigar and blazer in no time

and i cant say this enuff: the biggest prollem in using the guide now is that if you attempt to stay on the stock rooted 1.13.605.7 firmware your phone will prolly pester you to update. it may bug you constantly with a "do you want to update" message,or it may just go ahead and try and do it i have read that some phones have attempted to take the ota without notifying the user.

as long as you realize this,and flash either a custom rom,or the latest rooted stock software,it shouldnt be an issue. or you can wait a couple days. jcase had mentioned on twitter he was out of town,it wouldnt surprise me at all to see an updated guide either tomoro or tuesday.

 

[Desiel]

Ok thanks for the help Scotty, Now I have rooted my phone and successfully installed CM 7. Little problem is that my phone is not connected to any network, no 3g or 4g. I know this has something to do with radio, what do I do now?

 

[Desiel]

Ok, I finally got Radio to work.

How do I set up my google account i.e. gmail, calendar, etc.

Also, I can't find the market app to download anything.

 

[gagglone]

What you will have to do is reload the rom. What happens when you first boot into a rom is it goes out and downloads the right versions, and since you didn't have the radio set up, it couldn't, and didn't. If you reload the rom, you'll be fine.

 

[scotty85]

Ok, I finally got Radio to work.

How do I set up my google account i.e. gmail, calendar, etc.

Also, I can't find the market app to download anything.

sounds like you got the radio working,but for others who may be reading you need to just make sure you used the "mr2 version of rc1.2 so what its compatible with the radios you have,since your phone had allready taken the update(your baseband ends in 627,correct? in settings/about phone)

as got google,if you havent figured it out yet, you didnt flash the "gapps" package that contains googles proprietary apps,market among them

all you need to do is download and transfer gapps to your sd card,and then go back to recovery and flash it. no need to wipe anything. when you reboot,you should be at the "touch the android to begin" screen

last and not least,congratulations! as was told to me... your cigar and blazer are on the table,sir

 

[scotty85]

What you will have to do is reload the rom. What happens when you first boot into a rom is it goes out and downloads the right versions, and since you didn't have the radio set up, it couldn't, and didn't. If you reload the rom, you'll be fine.

mmm im not sure what youre talking about here. all cyanogen mod roms need a seperate flash of google apps addon (gapps) in order for market and sign in to work.

most AOSP roms youll find to be this way.

you are prolly just used to running stock sense based roms wich are able to include those apps in the rom.

 

[Desiel]

You are right Scotty, I have downloaded gapps for 2.3.4 and flashed it, my phone rebooted and asked me to login to my account. I have tried a couple of times but it wont connect to google server, it says "..... your phone may not be provisioned for data service, if it continues call customer care ". I know I am connected to the internet cos I am sending this from my phone. I have tried it on 3G, 4G and WiFi with no result still. Any ideas?

 

[Desiel]

I just did reboot now everything works! This is the best forum on the planet! Thank you very much Scotty85, You are like the Yoda of this forum. May the force be with you!

 

[gagglone]

mmm im not sure what youre talking about here. all cyanogen mod roms need a seperate flash of google apps addon (gapps) in order for market and sign in to work.

most AOSP roms youll find to be this way.

you are prolly just used to running stock sense based roms wich are able to include those apps in the rom.

oh yeah, you're right on that. I use BAMF 2.1 stripped for my Thunderbolt. Its been so long since I flashed CM on my Eris.

 

[Desiel]

I can't get verizon VM to work, it says it can't connect to server. Any ideas folks?

 

[Desiel]

VM working now! I have no idea how it happened but it is working now....

BTW... I highly recommend CM 7 ROM (the only ROM I have ever used outside stock) if you can live without Sense.

 

[brizey]

Just wanted to confirm that the root method still works post 7/8 update.

Also, the SDK now installs adb in platform-tools, so just unzip the exploits file into that directory and all the adb commands work fine.

I went ahead and got the newest radio and the rooted OTA ROM to use as a "disaster recovery" point.

Now I just need to get everything set back up, make a Titanium back up, and figure out which ROM I want to try first. I want one that works with the latest radio--seems to be too much improved to mess with the old ones.

And also, if this old daddy can root, anyone can. It is NOT totally mindless...you have to figure things out a little bit like cycling USB debugging if adb loses connection to the phone, and things like the directory change (admittedly I read about the directory change here somewhere). I watch a you tube video first mostly so the screens would look familiar.

One more thing I suggest is to keep the command window open the whole time so you can cut and paste out of it in case there are problems, you can show experts exactly what you did. I had no major issues, so it was not needed for me.

Here is my session, hopefully it can be of use for someone (I had already done an adb devices command). The bolded area is where I had to toggle usb debugging a bit to get it to see the phone.

C:\Program Files (x86)\Android\android-sdk\platform-tools>adb push psneuter /dat
a/local/
1722 KB/s (585731 bytes in 0.332s)

C:\Program Files (x86)\Android\android-sdk\platform-tools>adb push busybox /data
/local/
1652 KB/s (1062992 bytes in 0.628s)

C:\Program Files (x86)\Android\android-sdk\platform-tools>adb push misc.img /dat
a/local/
1999 KB/s (262144 bytes in 0.128s)

C:\Program Files (x86)\Android\android-sdk\platform-tools>adb shell chmod 777 /d
ata/local/psneuter

C:\Program Files (x86)\Android\android-sdk\platform-tools>adb shell chmod 777 /d
ata/local/busybox

C:\Program Files (x86)\Android\android-sdk\platform-tools>adb shell
$ /data/local/psneuter

C:\Program Files (x86)\Android\android-sdk\platform-tools>adb shell
adb server is out of date.  killing...
* daemon started successfully *
# /data/local/busybox md5sum /data/local/misc.img
/data/local/busybox md5sum /data/local/misc.img
c88dd947eb3b36eec90503a3525ae0de  /data/local/misc.img
# dd if=/data/local/misc.img of=/dev/block/mmcblk0p17
dd if=/data/local/misc.img of=/dev/block/mmcblk0p17
512+0 records in
512+0 records out
262144 bytes transferred in 0.110 secs (2383127 bytes/sec)
# exit
exit

C:\Program Files (x86)\Android\android-sdk\platform-tools>adb reboot bootloader

[B]C:\Program Files (x86)\Android\android-sdk\platform-tools>adb devices
adb server is out of date.  killing...
* daemon started successfully *
List of devices attached
HT11YS010667    offline


C:\Program Files (x86)\Android\android-sdk\platform-tools>adb devices
List of devices attached
HT11YS010667    offline


C:\Program Files (x86)\Android\android-sdk\platform-tools>adb devices
List of devices attached
HT11YS010667    offline


C:\Program Files (x86)\Android\android-sdk\platform-tools>adb devices
List of devices attached
HT11YS010667    offline


C:\Program Files (x86)\Android\android-sdk\platform-tools>adb devices
List of devices attached
HT11YS010667    offline


C:\Program Files (x86)\Android\android-sdk\platform-tools>adb devices
List of devices attached
HT11YS010667    offline


C:\Program Files (x86)\Android\android-sdk\platform-tools>adb devices
adb server is out of date.  killing...
ADB server didn't ACK
* failed to start daemon *
error:

C:\Program Files (x86)\Android\android-sdk\platform-tools>adb devices
adb server is out of date.  killing...
* daemon started successfully *
List of devices attached
HT11YS010667    device[/B]


C:\Program Files (x86)\Android\android-sdk\platform-tools>adb push psneuter /dat
a/local/
2315 KB/s (585731 bytes in 0.247s)

C:\Program Files (x86)\Android\android-sdk\platform-tools>adb push busybox /data
/local/
1973 KB/s (1062992 bytes in 0.526s)

C:\Program Files (x86)\Android\android-sdk\platform-tools>adb push wpthis /data/
local/
2439 KB/s (679475 bytes in 0.272s)

C:\Program Files (x86)\Android\android-sdk\platform-tools>adb shell chmod 777 /d
ata/local/psneuter

C:\Program Files (x86)\Android\android-sdk\platform-tools>adb shell chmod 777 /d
ata/local/busybox

C:\Program Files (x86)\Android\android-sdk\platform-tools>adb shell chmod 777 /d
ata/local/wpthis

C:\Program Files (x86)\Android\android-sdk\platform-tools>adb shell
$ /data/local/psneuter
/data/local/psneuter
property service neutered.
killing adbd. (should restart in a second or two)

C:\Program Files (x86)\Android\android-sdk\platform-tools>adb shell
adb server is out of date.  killing...
* daemon started successfully *
# /data/local/wpthis
/data/local/wpthis
Build: 25
Section header entry size: 40
Number of section headers: 45
Total section header table size: 1800
Section header file offset: 0x00014e90 (85648)
Section index for section name string table: 42
String table offset: 0x00014cc7 (85191)
Searching for .modinfo section...
 - Section[16]: .modinfo
 -- offset: 0x00000f80 (3968)
 -- size: 0x000000c4 (196)
Kernel release: 2.6.32.21-g2447a8d
New .modinfo section size: 204
Loading module... OK.
Write protect disabled.
Searching for mmc_blk_issue_rq symbol...
 - Address: c02d3114, type: t, name: mmc_blk_issue_rq, module: N/A
Kernel map base: 0xc02d3000
Kernel memory mapped to 0x40001000
Searching for brq filter...
 - Address: 0xc02d3114 + 0x34c
 - 0x2a000012 -> 0xea000012
Done.
# exit
exit

C:\Program Files (x86)\Android\android-sdk\platform-tools>adb push hbooteng.nb0
/data/local/
1786 KB/s (1048576 bytes in 0.573s)

C:\Program Files (x86)\Android\android-sdk\platform-tools>adb shell
# /data/local/busybox md5sum /data/local/hbooteng.nb
/data/local/busybox md5sum /data/local/hbooteng.nb
md5sum: can't open '/data/local/hbooteng.nb': No such file or directory
# /data/local/busybox md5sum /data/local/hbooteng.nb0
/data/local/busybox md5sum /data/local/hbooteng.nb0
6991368ee2deaf182048a3ed9d3c0fcb  /data/local/hbooteng.nb0
# dd if=/data/local/hbooteng.nb0 of=/dev/block/mmcblk0p18
dd if=/data/local/hbooteng.nb0 of=/dev/block/mmcblk0p18
2048+0 records in
2048+0 records out
1048576 bytes transferred in 0.466 secs (2250163 bytes/sec)
# /data/local/busybox md5sum /dev/block/mmcblk0p18
/data/local/busybox md5sum /dev/block/mmcblk0p18
6991368ee2deaf182048a3ed9d3c0fcb  /dev/block/mmcblk0p18
#
C:\Program Files (x86)\Android\android-sdk\platform-tools>adb devices
adb server is out of date.  killing...
* daemon started successfully *
List of devices attached
HT11YS010667    device


C:\Program Files (x86)\Android\android-sdk\platform-tools>adb devices
adb server is out of date.  killing...
* daemon started successfully *
List of devices attached
HT11YS010667    device


C:\Program Files (x86)\Android\android-sdk\platform-tools>adb reboot bootloader

C:\Program Files (x86)\Android\android-sdk\platform-tools>

 

[brizey]

Just noticed something I was not expecting: my phone remembered my wifi setting once I flashed the rooted stock ROM.

 

[odnerd]

Just noticed something I was not expecting: my phone remembered my wifi setting once I flashed the rooted stock ROM.

Assuming you had logged into your google account during setup that's one of the things it backs up so when you logged in it added that info back to your phone along with contacts and bookmarks and stuff...

 

[brizey]

Assuming you had logged into your google account during setup that's one of the things it backs up so when you logged in it added that info back to your phone along with contacts and bookmarks and stuff...

Yeah, I read that somewhere along the way after I posted the above.