Database Info

Having trouble rooting, any help?

I am following the guide from the cyanogenmod wiki on how to get CM on my droid 2, however I am getting hung up on one step.. all previous steps have worked fine and I am running android 2.2. I am getting stuck on running the rageagainstthecage script.
I run this command;
/data/local/tmp/rageagainstthecage-arm5.bin
and it appears to run. I then lose my adb connection. Upon restarting adb, I am unable to see the device with 'adb devices'. I am able to browse the phone storage, though. The only way to get it to show up with adb again is to reboot the phone. Upon rebooting and doing an 'adb shell' I still have the $ prompt instead of the # prompt. Any ideas?

Have you tried it my way?
http://forum.xda-developers.com/showthread.php?t=1466786
It's a bit easier than the CMWiki way.

Google 'pete's root tools' and use it. It takes 5 minutes and does everything for you. It's as close to a 'one click' as you can get on gingerbread.

beepea206 said:
Google 'pete's root tools' and use it. It takes 5 minutes and does everything for you. It's as close to a 'one click' as you can get on gingerbread.
Click to expand...
Click to collapse
OK, will this work with the 2.3.3 update?

loudog3114 said:
OK, will this work with the 2.3.3 update?
Click to expand...
Click to collapse
yes, look for link in my sig sbf/root/rom
then look for droid 3 root

[UNLOCK] AT&T Bootloader Unlock Through HTC-Dev

You do this at your own risk!!! This could turn your new phone into a very expensive paperweight!!! If you don't know how to do it or are uncomfortable DON'T DO IT!!!
You need ADB and an understanding of how to use it and have a rooted device (although I didn't test this). You will also need a hex editor like HxD.
BACK UP YOUR DATA BEFORE DOING THIS!!!! WHEN HTCDEV UNLOCKS YOUR DEVICE YOU MUST START FROM SCRATCH!!!
1. Fire up your command prompt and go to the directory that you have ADB installed to. Type "adb shell" and hit enter.
2. Type "su" and hit enter. You now have root privileges.
3. Next type "dd if=/dev/block/mmcblk0p4 of=/sdcard/mmcblk0p4" and hit enter. This will dump the partition to your sdcard.
4. Next type "exit", hit enter, type "exit", and hit enter again. This should take you back to a command prompt for your computer.
5. type "adb pull /sdcard/mmcblk0p4" and hit enter. NOTE THE SIZE OF THE FILE BEFORE THE NEXT STEP!
6. Open the file (mmcblk0p4) with your hex editor.
7. Look for offset 00000210 (if your on RUU version 1.82 the offset may be 00000214) and you should see CWS__001 with your IMEI number attached to it.
8. Change CWS__001 to 11111111 and save the file as mmcblk0p4MOD. This will give you SuperCID as well. MAKE SURE AT THIS POINT THAT THE FILE IS THE EXACT SIZE IT WAS BEFORE YOU HEX EDITED IT!
9. Now go back to your command prompt and type "adb push mmcblk0p4MOD /sdcard/mmcblk0p4MOD" and hit enter.
10. Type "adb shell" and hit enter then type "su" and hit enter again. This will put you back into the android shell and give you root privileges.
11. Type "dd if=/sdcard/mmcblk0p4MOD of=/dev/block/mmcblk0p4" and hit enter. To test if it worked restart the phone into fastboot (type "adb reboot bootloader" and hit enter) and once the bootloader screen comes up type "fastboot oem readcid" and hit enter. It should read "11111111".
12. Next type "fastboot oem get_identifier_token" and hit enter. Leave that up on your screen and go to HTCdev.com. Follow the instructions from there. Choose "All other supported models" from the dropdown menu.
For those having trouble with the hex editor portion of this I have posted a picture from Squeak22 showing exactly what it should look like. Thanks Squeak22!
Enjoy all!
Guy

Worked for me with CID 11111111.
Thanks, my friend, now I can stop that f'ing thread...

I see a whole Case load of "Thanks" coming your way.
Now all we need is SK to finish CWM Recovery!
EDIT:
Confirmed working

LOL no prob. Glad we got it figured ... at least for now.

wooooot

SO this is a NO-Go if we updated to the new 1.85 This morning? Have to wait for the 1.85 Root first correct?
..Gromet

HOLY CRAP! What a great day! Thanks DEVS!

So this appears as an adaptation on how you were able to flip back and forth to older Firmware/RUUs with the changing the software version number? Nice find and congrats!

Holy big picture, batman.
Anyway, a huge thanks to all the devs who worked on this. Hopefully it still works in 4 hours when I get home

high five !!

warri said:
Now all we need is SK to finish CWM Recovery!
Thanks, Will try when I get home
Click to expand...
Click to collapse
Now I can actually test the f-ing thing, should be a gimme...I am so relieved this is done. Now its working recovery and s-off time.... Again, thanks grankin...

Nice job man. The question now is where do I send your 12 pack of beer to? Definitely deserve a nice cold one.
Sent from my HTC One X using Tapatalk 2

Gromet said:
SO this is a NO-Go if we updated to the new 1.85 This morning? Have to wait for the 1.85 Root first correct?
..Gromet
Click to expand...
Click to collapse
Correct. 1.85 has been rooted, just got to wait for them to post the exploit.
Why did I upgrade lol.
Hopefully this will work tonight.

NJGSII said:
Correct. 1.85 has been rooted, just got to wait for them to post the exploit.
Why did I upgrade lol.
Hopefully this will work tonight.
Click to expand...
Click to collapse
Cant you use the downgrade RUU tutorial to get back?

Should the title of this thread reflect specifically for AT&T? Rogers users don't have to follow these steps..just some feedback!

So probably a dumb question, but does unlocking the bootloader through htcdev.com completely wipe the phone, like what happened when I unlocked my Galaxy Nexus?

Ziggurat12 said:
Should the title of this thread reflect specifically for AT&T? Rogers users don't have to follow these steps..just some feedback!
Click to expand...
Click to collapse
Fixed!

ThisWasATriumph said:
Cant you use the downgrade RUU tutorial to get back?
Click to expand...
Click to collapse
You have to be rooted for that as well.
I'm kicking myself for upgrading now, but I didn't think we'd have an unlock solution today.

NJGSII said:
You have to be rooted for that as well.
I'm kicking myself for upgrading now, but I didn't think we'd have an unlock solution today.
Click to expand...
Click to collapse
Woops didnt catch that. Man that sucks.

Red5 said:
Fixed!
Click to expand...
Click to collapse
LOL thanks man! And yes this does wipe your phone ar at least the userdata. It starts as if you just pulled it out of the box.
Clockwork mod flashed with fastboot flash recovery recovery.img command and works perfectly!

[Q] Fastboot issue

Whats up everyone, I have an HTC one S and for the first time I am trying to s-off, root it, and install a new rom. I managed to boot unload it with no issues but I am now at the s-off process and I am running into this problem where moonshine gets hung up on test 3 "waiting for fastboot" and dots just keep appearing ex "........." but nothing happens (see photo)
Any help would be appreciated, thanks.

wow, I guess NOBODY has run into this problem...nice.

camilogod said:
wow, I guess NOBODY has run into this problem...nice.
Click to expand...
Click to collapse
I had the same problem with Windows. Use Linux and you should be OK.

Are you in fastboot mode even?

[Q] Trying follow steps on rooting for 4.4

I am trying to be able to get root on 4.4. I am currently on 4.2.2 (12.15.15) (camera update). I just rooted using RockMyMoto and ran through the MotoWPNoMo and I still get a "1" status when I type "adb shell getprop ro.boot.write_protect". Why is this happening?
Edit: By the way I have a Verizon carrier (if that matters).

Dreadlord12p said:
I am trying to be able to get root on 4.4. I am currently on 4.2.2 (12.15.15) (camera update). I just rooted using RockMyMoto and ran through the MotoWPNoMo and I still get a "1" status when I type "adb shell getprop ro.boot.write_protect". Why is this happening?
Edit: By the way I have a Verizon carrier (if that matters).
Click to expand...
Click to collapse
Carrier doesn't matter. Can you give a couple more details?
Can you paste the output of the motowpnmoto?
When I ran it initially, the output indicated to me it completed without error but I was still getting a 1. After I got it working properly, it fully ran and was clearly successful and i got a zero. I am thinking perhaps it didn't run properly and complete and it did not tell you that.
Check the main motowpnmoto thread and see if you can find my post. I think I posted a complete successful run for reference.
Sent from my XT1080 using Tapatalk

Dreadlord12p said:
I am trying to be able to get root on 4.4. I am currently on 4.2.2 (12.15.15) (camera update). I just rooted using RockMyMoto and ran through the MotoWPNoMo and I still get a "1" status when I type "adb shell getprop ro.boot.write_protect". Why is this happening?
Edit: By the way I have a Verizon carrier (if that matters).
Click to expand...
Click to collapse
How many times have you run it, and did you keep your phone screen on? I think it requests a Give Root pop up for ADB

Another question.
I was on 4.2.2, get root with RMM. Then i suceed with WPNoMo. I get "0" code.
Then I just got messed with SlapMyMoto - cant get it done. I decide to wipe Maxx with House of Moto. Wiped, install 4.4 ota. Now I'm without root, but adb script from WPNoMo still show me "0" code. Can I get root? Any help? :fingers-crossed:

livinitwarrior said:
How many times have you run it, and did you keep your phone screen on? I think it requests a Give Root pop up for ADB
Click to expand...
Click to collapse
I have run it twice with no errors. I had my screen on the whole time. I granted the SU access popup for ADB. I will give you my log report after this post.

Dreadlord12p said:
I have run it twice with no errors. I had my screen on the whole time. I granted the SU access popup for ADB. I will give you my log report after this post.
Click to expand...
Click to collapse
Never mind, I just tried it on my windows 7 laptop and it worked. It said "removed pesky write protection..."

F***!!
I followed all the steps for slapmymoto but when I try to install the 4.4 update, IT FAILS!! PLEASE HELP.

Dreadlord12p said:
I followed all the steps for slapmymoto but when I try to install the 4.4 update, IT FAILS!! PLEASE HELP.
Click to expand...
Click to collapse
did you try the command to see if write protection is still off?

livinitwarrior said:
did you try the command to see if write protection is still off?
Click to expand...
Click to collapse
Yes and it gave me a blank. Not a 1 or a zero. If I did the last step on slapmymoto with the adb commands before I updated to 4.4, would that mess it up?
[email protected]:/ $ su
[email protected]:/ # getprop boot.write_protect
[email protected]:/ #

Dreadlord12p said:
Yes and it gave me a blank. Not a 1 or a zero. If I did the last step on slapmymoto with the adb commands before I updated to 4.4, would that mess it up?
[email protected]:/ $ su
[email protected]:/ # getprop boot.write_protect
[email protected]:/ #
Click to expand...
Click to collapse
What Failure are you getting?
Sent from my KitKat Ultra

Dreadlord12p said:
Yes and it gave me a blank. Not a 1 or a zero. If I did the last step on slapmymoto with the adb commands before I updated to 4.4, would that mess it up?
[email protected]:/ $ su
[email protected]:/ # getprop boot.write_protect
[email protected]:/ #
Click to expand...
Click to collapse
I'm pretty sure, at least for me, that for the command prompt to work with adb the best, have one in the folder you have the adb stuff in and open it from there, because it sounds like your adb shell isn't running. Did you check processes on ctrl+shift+escape?
Edit: try "adb shell getprop ro.boot.write_protect"

Caseyk621 said:
What Failure are you getting?
Sent from my KitKat Ultra
Click to expand...
Click to collapse
When it is installing the update with the little android icon, it gets about halfway and then it says "error". Then it reboots and tells me that the software update failed.

Dreadlord12p said:
When it is installing the update with the little android icon, it gets about halfway and then it says "error". Then it reboots and tells me that the software update failed.
Click to expand...
Click to collapse
So one, did you do all the steps including getting back a 0 after MotoWPNoMo? And then flashed back to stock 4.2.2 on the 12.15.15 update?

livinitwarrior said:
So one, did you do all the steps including getting back a 0 after MotoWPNoMo? And then flashed back to stock 4.2.2 on the 12.15.15 update?
Click to expand...
Click to collapse
Yes. I got a "0" after running MotoWPNoMo and I flashed the 4.2.2 (12.15.15).
Edit: I actually did not get either a 1 nor a 0. It was just blank. But MotoWPNoMo said was, "removed pesky write protection successfully".

Dreadlord12p said:
Yes. I got a "0" after running MotoWPNoMo and I flashed the 4.2.2 (12.15.15).
Edit: I actually did not get either a 1 nor a 0. It was just blank. But MotoWPNoMo said was, "removed pesky write protection successfully".
Click to expand...
Click to collapse
hmm ok. Until you make sure the files have been sent over. It sounds like there might not have been a full overwrite of the FXZ... you might want to try it again with the 12.15.15 on RSDLite version, and then try from there. If you tried to keep data, that might be the issue and it never reloaded the stock recovery back

livinitwarrior said:
hmm ok. Until you make sure the files have been sent over. It sounds like there might not have been a full overwrite of the FXZ... you might want to try it again with the 12.15.15 on RSDLite version, and then try from there. If you tried to keep data, that might be the issue and it never reloaded the stock recovery back
Click to expand...
Click to collapse
I used houseofmoto. I will try with rsd. And I did a full fxz. I kept no data.

Dreadlord12p said:
I used houseofmoto. I will try with rsd. And I did a full fxz. I kept no data.
Click to expand...
Click to collapse
idk why, but RSD has never given me an issue, even though it takes longer. Keep us updated

Dreadlord12p said:
When it is installing the update with the little android icon, it gets about halfway and then it says "error". Then it reboots and tells me that the software update failed.
Click to expand...
Click to collapse
Here is the MotoWPNoMo log:
==================== Moto-WP-NoMo 0.0.4 ==============================
Moto-WP-NoMo comes with NO WARRANTY (express or implied)
and NO GUARANTEE OF FITNESS for any particular task.
We have made every effort we can to make this a safe process for users
however the authors disclaim any liability for damage to your phone
or other materials or devices used during this process.
The entire risk of running Moto-WP-NoMo lies with you, the user.
By using this software you acknowledge and accept that the authors
are not liable for any loss, material or otherwise howsoever caused.
Do you understand the implications of this warning?
(Yes/No)
Yes
Dear User: We will expect that YOU:
(1) Know how to use ADB and FASTBOOT binaries
---- [Yes, use these tools to test USB connection BEFORE running Moto-WP-NoMo] -
---
(1) Know how to enable USB-debugging on YOUR device (Yes, do that now)
(2) Understand that you may NOT repack or redistribute Moto-WP-NoMo
Ok?
(Yes/No)
Yes
!! Do NOT for any reason bite, punch, or molest your device !!
Please wait....
..........
Checking for updates......
Test 1: Rebooting into bootloader
Waiting for fastboot (7/120)
Waiting
Test 2: Booting device
Waiting for ADB (40/120)
must play a little while longer...
it's so cold in here
hmm, hold please
..............................................
[---------------------------------------------]
doing some *stuff*..................
this is getting boring, let's go ahead and get started..
clobbering (1).....
Waiting for ADB (39/120)
must play a little while longer...
lets put some things back in place...
installing root stuff, thanks chainfire
wait for it.........
yep, done. bye bye pesky write protection!
send your money, ALL OF YOUR MONIES to - [email protected]
Press ENTER to exit

write protection log
Here is the log when I check for write protection:
C:\adt-bundle-windows-x86_64-20131030\sdk\platform-tools>adb shell getprop ro.bo
ot.write_protect
0
C:\adt-bundle-windows-x86_64-20131030\sdk\platform-tools>

Alright, I have done all the steps except installing the 4.4 OTA. I will keep you posted on whether or not the update fails. *crossing my fingers*.

[Q] Please help!!!

Ok so my first M8 died so I had to get another one. This one came with 1.55.605.2 out of the box. Baseband 0.89.20.0321. The issue I am having is that every time I try and s-off it just sits there adding dashes at the bottom after I type yes and the message saying if Firewater hangs for more than 2 minutes...I have searched and haven't been able to find a solution. I did see where someone said to export the firewater file from his dropbox into the local folder and in adb start at the adb shell step. Did that or so I thought and that didn't work either. Maybe I'm not extracting the file as all I'm doing is downloading it and then copying and pasting. Any help would be GREATLY appreciated. I apologize if this has been asked before. I searched as much as I could and could not find a definitive answer. Thanks to everyone on XDA.
Roque

Anyone please?

Question Did you look into the post above your in the HOW to links? Your answer should be there.

foamerman said:
Question Did you look into the post above your in the HOW to links? Your answer should be there.
Click to expand...
Click to collapse
Thanks for the response! Yeah those are the steps I've been following but no luck yet..I may reset the phone and start over. I did the steps on my previous m8 and it worked like a champ. This one is being a pain lol.

Roque13 said:
Thanks for the response! Yeah those are the steps I've been following but no luck yet..I may reset the phone and start over. I did the steps on my previous m8 and it worked like a champ. This one is being a pain lol.
Click to expand...
Click to collapse
Ok so I take it you have gained temp root with WeakSauce and have SuperSU installed and verified ADB is working?

fLaWx said:
Ok so I take it you have gained temp root with WeakSauce and have SuperSU installed and verified ADB is working?
Click to expand...
Click to collapse
Yup. I enter adb devices and it recognizes the device. Everything seems to work fine until the last step after I type in Yes. Then it just sits there. It gives me the message "if firewater hangs for more than 2 minutes, press and hold power for 60 seconds" 3 times..Then just dashes and doesn't do anything else. Really confused on this one.

Roque13 said:
Yup. I enter adb devices and it recognizes the device. Everything seems to work fine until the last step after I type in Yes. Then it just sits there. It gives me the message "if firewater hangs for more than 2 minutes, press and hold power for 60 seconds" 3 times..Then just dashes and doesn't do anything else. Really confused on this one.
Click to expand...
Click to collapse
Odd...I had no problems with firewater and my phone is on the same firmware, how many times have you tried it? I read somewhere it make take multiple tries.

fLaWx said:
Odd...I had no problems with firewater and my phone is on the same firmware, how many times have you tried it? I read somewhere it make take multiple tries.
Click to expand...
Click to collapse
SUCCESS!!!! So I deleted all the adb fastboot files and wiped my. Re-rooted with weaksauce and re-did everything and it worked perfectly. Thnaks for trying to help me out. I really appreciate it!!
Roque