I used ODIN to root my device... followed instructions from the thread here: http://forum.xda-developers.com/showthread.php?t=2024207
I'm rooted, that's for sure. However, I can't get a custom recovery to stick (using ODIN). Have tried both of the custom recovery versions, CWM/TWRP. The ODIN flash fails right as it starts.
When I boot my device...there isn't a picture of an open lock... So am I rooted but not unlocked?
Any help would be appreciated.
This is a consistent message I get trying to unlock my bootloader. Again, I am rooted, but cannot seem to flash a custom recovery.
Gosh...i can't even post an image yet....basically, my screenshot is at http:slashslashminus.com/lbyMxyQ6o5ZS06
The error in ODIN is NAND Write Start, then Fail!
I did a start for NANDWrite issues, and umm...is this bad?
I believe you need to be unlocked to have custom recovery
you can find out how to unlock bootloader here http://forum.xda-developers.com/showthread.php?t=2043636
MunkinDrunky said:
I believe you need to be unlocked to have custom recovery
you can find out how to unlock bootloader here http://forum.xda-developers.com/showthread.php?t=2043636
Click to expand...
Click to collapse
I followed those steps, and Causal wouldn't continue. Callled me a noob because I have the wrong bootloader! Trying to ODIN an unsecure one, but again, Nand Write, then immediately Fail.
kaminczak said:
I followed those steps, and Causal wouldn't continue. Callled me a noob because I have the wrong bootloader! Trying to ODIN an unsecure one, but again, Nand Write, then immediately Fail.
Click to expand...
Click to collapse
Going to try and flash Revision 3 and start from scratch...
Casual's log says:
COMMAND processed - C:\Users\Steve\AppData\Local\Temp\SteveTEMPCASUAL61FF3C98\adb.exe shell "chmod 777 /data/local/tmp/viewmem; chmod 777 /data/local/tmp/busybox"
SCRIPT COMMAND:shell "su -c /data/local/tmp/viewmem 0x40000200 0x200>/data/local/tmp/BLR"
Unknown id: 0x40000200
COMMAND processed - C:\Users\Steve\AppData\Local\Temp\SteveTEMPCASUAL61FF3C98\adb.exe shell "su -c /data/local/tmp/viewmem 0x40000200 0x200>/data/local/tmp/BLR"
SCRIPT COMMAND:shell "/data/local/tmp/busybox grep I605VRALJB /data/local/tmp/BLR && echo [x]Bootloader Is Proper || echo HellNo"
Removing leading space.
Removing leading space.
SCRIPT COMMAND:$ECHO IMPROPER BOOTLOADER VERSION DETECTED. FOLLOW DIRECTIONS NOOB! GUYS LIKE YOU ARE THE REASON DEVELOPERS HAVE SO MUCH PROBLEMS!!!!!! DO YOU REALIZE WHAT IT TAKES TO MAKE SOMETHING LIKE THIS COME TOGETHER?? AND HERE YOU ARE JUST TRYING TO SCREW THINGS UP.... DAMNIT! GET OFF THE INTERNET!
Received ECHO command$ECHO IMPROPER BOOTLOADER VERSION DETECTED. FOLLOW DIRECTIONS NOOB! GUYS LIKE YOU ARE THE REASON DEVELOPERS HAVE SO MUCH PROBLEMS!!!!!! DO YOU REALIZE WHAT IT TAKES TO MAKE SOMETHING LIKE THIS COME TOGETHER?? AND HERE YOU ARE JUST TRYING TO SCREW THINGS UP.... DAMNIT! GET OFF THE INTERNET!
Removing leading space.
IMPROPER BOOTLOADER VERSION DETECTED. FOLLOW DIRECTIONS NOOB! GUYS LIKE YOU ARE THE REASON DEVELOPERS HAVE SO MUCH PROBLEMS!!!!!! DO YOU REALIZE WHAT IT TAKES TO MAKE SOMETHING LIKE THIS COME TOGETHER?? AND HERE YOU ARE JUST TRYING TO SCREW THINGS UP.... DAMNIT! GET OFF THE INTERNET!
HellNo
COMMAND processed - C:\Users\Steve\AppData\Local\Temp\SteveTEMPCASUAL61FF3C98\adb.exe shell "/data/local/tmp/busybox grep I605VRALJB /data/local/tmp/BLR && echo [x]Bootloader Is Proper || echo HellNo"
If that helps anyone assist.
Update:
Taking a step back and starting with Revision 3, then following all steps worked like a charm. Issue resolved.
Related
Well I rooted my thunderbolt yesterday and today I was going to try to install a ROM but for some reason I can't do it.
I'm using rom manager. I flashed the clockworkmod recovery. Then I went to backup my current rom and the phone restarts then just goes straight to the boot loader where I only have a few options.
Hboot
Power down etc...
What am I doing wrong?
When I tried yesterday I got a little farther and went to install the rom and the same thing happened. No recovery or options to install off SD.
There is no option for recovery?
If not, go back into rom manager, settings, and check erase recovery. Then flash CM Recovery again (the top option on rom manager) and it should fix the problem for you.
Tried that:
I get HBOOT
FASTBOOT
RECOVERY
FACTORY RESET
SIMLOCK
HBOOT USB
IMAGE CRC
I go select recovery and the phone restarts briefly and I get FASTBOOT USB
BOOTLOADER
REBOOT
REBOOT BOOTLOADER
POWER DOWN
No other options.
I would flash back to stock and root again, maybe something didn't take right the first time.
g00s3y said:
I would flash back to stock and root again, maybe something didn't take right the first time.
Click to expand...
Click to collapse
Agh really. It rooted perfectly I thought. I have root access and everything. Any other ideas before I have to go through that process again?
Maybe go to the thunderbolt chatroom on IRC and see if people can help you there. Unless someone else here knows what to do. But i never heard of a problem like that.
I think I might have figured out the problem.
After I go to install the ROM it brings me to the bootloader. Under the pink ***security warning*** I'm showing
MECHA XD SHIP S-ON
I thought S was supposed to be off? Does the root for Mac not do S off?
droidboy850 said:
I think I might have figured out the problem.
After I go to install the ROM it brings me to the bootloader. Under the pink ***security warning*** I'm showing
MECHA XD SHIP S-ON
I thought S was supposed to be off? Does the root for Mac not do S off?
Click to expand...
Click to collapse
That is not good at all I believe. You should go to the chat ASAP, I think you have to restore your system to stock and then root again. You aren't supposed to be showing the pink ***Security Warning*** and you should also be S-OFF.
EDIT: Just saw you were on a mac, I don't have one so any instructions on MAC specifics I wouldn't be able to tell you, sorry.
Any tutorials for going back to stock on a mac? I saw a regular unroot procedure but it said push the image and exploits and I'm not sure what push means. I also don't have ADB or anything on my phone so can I still do it?
droidboy850 said:
Any tutorials for going back to stock on a mac? I saw a regular unroot procedure but it said push the image and exploits and I'm not sure what push means. I also don't have ADB or anything on my phone so can I still do it?
Click to expand...
Click to collapse
ADB would be in your computer. If you used a simple root process, then you will have to learn ADB to fix your issue.
the solution is here: http://forum.xda-developers.com/showthread.php?t=1009423
and if you did the long root way, this will be easy for you.
First, download the following files: To where? The SD?
Stock firmware (MD5 sum: 7141f5620f6128af77d50587e341f4b0)
exploits.zip (MD5 sum: 3b359efd76aac456ba7fb0d6972de3af)
Next, push exploits.zip and misc.img. What is push?
I go into terminal to do adb push misc.img /data/local/ and it says adb: command not found.
Where do the unroot files have to be? I'm still confused how I can be rooted with S on?
droidboy850 said:
I go into terminal to do adb push misc.img /data/local/ and it says adb: command not found.
Where do the unroot files have to be? I'm still confused how I can be rooted with S on?
Click to expand...
Click to collapse
if you type "adb devices" what does it tell you?
I've gotten a little farther but look what it says now:
$ su
/data/local/busybox md5sum /data/local/misc.img
Permission denied
$ c88dd947eb3b36eec90503a3525ae0de /data/local/misc.img
$ dd if=/data/local/misc.img of=/dev/block/mmcblk0p17
/dev/block/mmcblk0p17: cannot open for write: Permission denied
The hope of this thread is to centralize downgrade questions and also make the resources more accessible.
It is important to know your status.
-are you stock ota
-are you htc dev unlock hc
-are you s off hc
If you can not figure this out, god help you. To figure this out get into hboot the top will say
-s on
-unlocked
-s off
Don't know how to get into hboot? Wow! Novice. Hold power and volume down until flyer boots into white screen with androids on skateboards. Ta da!
Now that we know our status how do you downgrade? I take no credit for any of these methods.
Ota stock hboot
http://forum.xda-developers.com/showthread.php?t=1428104
Htc dev unlock
http://forum.xda-developers.com/showthread.php?t=1307759
S off hc
Third post of this thread
http://forum.xda-developers.com/showthread.php?t=1358758
If you have a question ask here or downgrade thread, do not start your own thread. Read the other questions asked first, the hope is that after a little while most scenarios will be covered. If a question is repeated multiple times it will be ignored.
Why bother doing this? I have an odd compulsion to help. I remember when I got my first android device and I rooted it and deleted gtalk. My market stopped working. I went into newbie panic and others helped me even though my issue was pathetic. I remember what that felt like and how cool it was that someone helped me. So, I hope this helps
Need help
Hello,
After a few weeks trying I still have problems downgrading to GB.
My Flyer is Relocked and S-on.
HTC__001
Softwareno. 3.55.1114.31
S-on
HBoot 1.11.0011
Radio-3822.10.08.07_M
I have the following RUU: RUU_Flyer_HTC_WWE_Wifi_2.27.1114.31_Radio_20.3504.30.089BU_3809.07.04.06_M_release_204727_signed
I have used Globatrons guide.
The problem appears when I type the command:
adb shell /data/local/tacoroot.bin --root
I get the following message:
cannot create /data/local.prop: permission denied
And after this i cannot go on.
Can someone tell me what to do, I think I have tried everything now.
thx Driesman
*EDIT: globatron has already mentioned this, but just to confirm, it does not work if you have already unlocked your bootloader through htcdev.com. it does not work if you have obtained CWM recovery through htc unlock. it does not work if you have root through htc unlock. it will only work if you have unmodified stock HC. at least this was my experience.
Have you unlocked before?
I have unlocked and relocked the flyer.
Globatron has to guides; one with unlocked and one with locked flyer.
Is there another way to go back to GB?
I think you should unlock your hboot again. Flash a recovery and super user. Then follow the thread I linked in the op for htc dev unlock
Okay I will try.
Can you tell me step by step how to do: "I think you should unlock your hboot again. Flash a recovery and super user"
Maybe I am doing something wrong.
Follow this site to unlock bootloader
http://htcdev.com/bootloader/
Then get into fastboot mode, I assume you have adb and fastboot commands on your PC. Place this in same folder as command
https://www.box.com/shared/9bb9ba944ea6f301afe8
Open commands on PC then enter command
Fastboot flash recovery "name of file you downloaded"
Place this on your external SD
https://www.box.com/shared/b51a527355d7fba5dca3
Get into recovery and select install zip from Sd. Select this file
Flyer
Everything seems to work ok until I type the following command:
adb shell
$ su
# chmod 777 /data/local/misc_version
# /data/local/misc_version -s 2.27.1114.31
Then I get the error below:
D:\Adb>adb shell
$ su
# chmod 777 /data/local/misc_version
# /data/local/misc_version -s 2.27.1114.31$ $ su
$: permission denied
$ # chmod 777 /data/local/misc_version
$
See also uploaded screenshot
Am I doing something wrong?
What to do now?
You flashed super user in recovery
Flyer
Is that a question?
Yes.
Yes I did.
Can I copy, paste the command below or do I have to run each line seperately?
adb shell
$ su
# chmod 777 /data/local/misc_version
# /data/local/misc_version -s 2.27.1114.31
Each line seperate
Make sure when you enter in su to have your flyers screen on and to allow sufficient access when prompted
Flyer
Yes, I think it is working now??
See attachment
Now I will try to finish it....
The next step is to Reboot to fastboot.
Do I have to enter the command (adb reboot bootloader) into the dos screen or do I choose the option on the Flyer (REBOOT BOOTLOADER)?
However you want
Flyer
YES........It worked!
After all these hours trying.
How can I thank you?
There is a button for that. Glad to hear it worked. Enjoy
Where is the THANKS button?
Have searched for it before but cannot find it.
Depends if you are using app. Or Web page. no worries
Flyer
If there's further discussion of this elsewhere that I've missed, please point me to it.
I'm trying to root my INC4G, but neither the manual nor scripted Fireballas method is successful.
-I have re-flashed the stock RUU, I am using a USB 2.0 port. All the basic ADB commands are fuctional in and out of fastboot, etc.
When I run the manual version, all is well up through restoring the fakebackup.ab file. When I enter the "while" command (without accepting restore yet on phone) I get the endlessly repeating error message mentioned by Aldo101t on the fireballas thread (post #54 and others). Accepting the restore on the phone handset does NOT stop the endless error loop in the Command line, and a prompt never becomes available again. I'm working on a Vista machine and I've tried the process through both the default 64-bit Command.exe and what I believe is the 32-bit version CMD.exe in the C:\Windows\SysWow64\ directory.
When I run the script version, all is well until I get the following:
----------------------------------------------------------------------------------------------------------------------
= Step 2: SuperCID =
========================
Your phone's CID is being modified to SuperCID. Once complete, your
phone will reboot to the bootloader.
/dev/block/mmcblk0p4: cannot open for read: Permission denied
remote object '/sdcard/mmcblk0p4' does not exist
The system cannot find the file specified.
cannot stat 'mmcblk0p4': No such file or directory
/sdcard/mmcblk0p4MOD: cannot open for read: Permission denied
rm failed for /data/local.prop, No such file or directory
< waiting for device >
...
(bootloader) cid: VZW__001
OKAY [ 0.012s]
finished. total time: 0.013s
Just above, you should see (bootloader) cid: 11111111
1) Yes, my cid is 11111111. Keep going.
2) No, my cid is VZW__001. Factory reset and try again.
3) No, my cid is VZW__001. Exit the script.
Select an option:
----------------------------------------------------------------------------------------------------------------------
Hitting option 2 to factory reset and repeat brings the same result each time.
Is there a specific permissions problem that I could resolve manually with a file manager? Or do I need to manually create a dummy file that can then be overwritten?
Any suggestions very welcome. I'd have posted this to the Fireballas forum, but I don't have posting privileges.
Thanks!
D
drenkin said:
If there's further discussion of this elsewhere that I've missed, please point me to it.
I'm trying to root my INC4G, but neither the manual nor scripted Fireballas method is successful.
-I have re-flashed the stock RUU, I am using a USB 2.0 port. All the basic ADB commands are fuctional in and out of fastboot, etc.
When I run the manual version, all is well up through restoring the fakebackup.ab file. When I enter the "while" command (without accepting restore yet on phone) I get the endlessly repeating error message mentioned by Aldo101t on the fireballas thread (post #54 and others). Accepting the restore on the phone handset does NOT stop the endless error loop in the Command line, and a prompt never becomes available again. I'm working on a Vista machine and I've tried the process through both the default 64-bit Command.exe and what I believe is the 32-bit version CMD.exe in the C:\Windows\SysWow64\ directory.
When I run the script version, all is well until I get the following:
----------------------------------------------------------------------------------------------------------------------
= Step 2: SuperCID =
========================
Your phone's CID is being modified to SuperCID. Once complete, your
phone will reboot to the bootloader.
/dev/block/mmcblk0p4: cannot open for read: Permission denied
remote object '/sdcard/mmcblk0p4' does not exist
The system cannot find the file specified.
cannot stat 'mmcblk0p4': No such file or directory
/sdcard/mmcblk0p4MOD: cannot open for read: Permission denied
rm failed for /data/local.prop, No such file or directory
< waiting for device >
...
(bootloader) cid: VZW__001
OKAY [ 0.012s]
finished. total time: 0.013s
Just above, you should see (bootloader) cid: 11111111
1) Yes, my cid is 11111111. Keep going.
2) No, my cid is VZW__001. Factory reset and try again.
3) No, my cid is VZW__001. Exit the script.
Select an option:
----------------------------------------------------------------------------------------------------------------------
Hitting option 2 to factory reset and repeat brings the same result each time.
Is there a specific permissions problem that I could resolve manually with a file manager? Or do I need to manually create a dummy file that can then be overwritten?
Any suggestions very welcome. I'd have posted this to the Fireballas forum, but I don't have posting privileges.
Thanks!
D
Click to expand...
Click to collapse
why not go to unlimited.io and s-off it. DONE
Aldo101t said:
why not go to unlimited.io and s-off it. DONE
Click to expand...
Click to collapse
I'd love to. But their step 12, "get temproot somehow-" appears to be the same part of the Fireballas process that won't work for me. If there's some other way to manage temproot--or if the Fireballas script is actually succeeding at temproot if only I knew to rip the cables out of the phone at the correct instant before the script crashes--please let me know what to try. I've never seen the shell prompt change from $ to #.
Did the unlimited.io process work for you, despite the same endless-error symptom through Fireballas? If so, can I ask how you achieved temproot?
Thanks for responding, above! : )
?
Sent from my ADR6410LVW using xda app-developers app
drenkin said:
I'd love to. But their step 12, "get temproot somehow-" appears to be the same part of the Fireballas process that won't work for me. If there's some other way to manage temproot--or if the Fireballas script is actually succeeding at temproot if only I knew to rip the cables out of the phone at the correct instant before the script crashes--please let me know what to try. I've never seen the shell prompt change from $ to #.
Did the unlimited.io process work for you, despite the same endless-error symptom through Fireballas? If so, can I ask how you achieved temproot?
Thanks for responding, above! : )
Click to expand...
Click to collapse
I USED THE AUTOMATED script in a different cmd window, you need to factory reset first then run it til the scrolling starts then accept restore, if it works properly the scroll stops. then adb reboot. when the phone has a screen with the droid eye on it and no icons(your done with this cmd window). it is in tempt root, then go back to the first cmd window you ruued on and finish the process. make sure usb debugging is on, after the ruu, you have to boot the rom (stock)to turn it on.
are you on a 32bit windows 7 and the enviornmental variables set. and the sdcard will get wiped s-offing so use a spare 8bg to 16gb no larger,and has to have an sdcard installed inthe phone to work. you can also go to unlimited.io for support and help. except the temp root deal they won't support that
Do you have a different machine you could use with a different OS? If so you may want to try that. 64 bit Windows 7 worked for me as far as temp root.
Good Luck
Interesting!
Aldo101t, thanks for mentioning using separate Command prompt windows, it led me to back up even further from a single instruction set and try the original root script by Bin4ry: it got me to a # prompt, and proper temproot...from which I could continue with the manual version of the Fireballas instructions and change out my VZW_001 id...and get the unlock code from HTCDev.
Currently have TWRP recovery installed, and about to flash ViperLTE Rom.
Thanks to Aldo101t and DavDoc for nudges and moral support. : )
drenkin said:
Interesting!
Aldo101t, thanks for mentioning using separate Command prompt windows, it led me to back up even further from a single instruction set and try the original root script by Bin4ry: it got me to a # prompt, and proper temproot...from which I could continue with the manual version of the Fireballas instructions and change out my VZW_001 id...and get the unlock code from HTCDev.
Currently have TWRP recovery installed, and about to flash ViperLTE Rom.
Thanks to Aldo101t and DavDoc for nudges and moral support. : )
Click to expand...
Click to collapse
your welcome, glad you got root.
unfortunately used HTCdev to unlock bootloader.i was following prototype7's guide to getting S-OFF after using HTCdev. i get an error at a certian stage and cannot figure it out. below is the command that errors out.
http://forum.xda-developers.com/showthread.php?t=1751796
"adb shell /data/local/tmp/misc_version -s 2.18.605.3"
what i get in return is:
"c:\android>adb shell /data/local/tmp/misc_version -s 2.18.605.3
--set_version set. VERSION will be changed to: 2.18.605.3
Patching and backing up misc partition...
Error opening input file."
can i get some help please. i am unable to post in dev forums as i am still new. thanks in advance..
Were you able to resolve this issue?
I have the exact same problem and am stuck.
Short story is, I got a DNA off of Craigslist for cheap that was stuck in fastboot mode and would not RUU. Its S-ON/Relocked/Tampered. After trying many things, I flashed a 2.06 update zip, and now it boots into a custom ROM that already has working root access. Looks like someone tried to put it back to a stock state but relocked it preamturely.
Now that I am back into a bootable state, neither Revone or Moonshine will work to get S-OFF so I can clean up the mess. Moonshine fails at 'launching temproot -> waiting 10 seconds -> Error; run distiller again' , and Revone auto-reboots after running ./revone.dna -P, and I've tried all the tricks in that thread here. I've factory reset/powered down and tried ad nauseum, with no luck.
My next line of thinking is, since it already has a working root, is it possible to have Moonshine bypass the temproot process? Or is it somehow possible to reflash a stock 2.06 system image? (I know there is no RUU yet.)
Since I did successfully flash the 2.06 update, which would restore the kernel and all that, Any suggestions on what to try next?
[EDIT] SOLVED!! I had to manually supercid and then unlock the bootloader via htcdev (most folks in a similar situation as I was would likely need temproot first.). After, I was able to S-OFF via facepalm.
Big thanks to Zanzibar in freenode #moonshiners for the tip!!
hurrrtin said:
Short story is, I got a DNA off of Craigslist for cheap that was stuck in fastboot mode and would not RUU. Its S-ON/Relocked/Tampered. After trying many things, I flashed a 2.06 update zip, and now it boots into a custom ROM that already has working root access. Looks like someone tried to put it back to a stock state but relocked it preamturely.
Now that I am back into a bootable state, neither Revone or Moonshine will work to get S-OFF so I can clean up the mess. Moonshine fails at 'launching temproot -> waiting 10 seconds -> Error; run distiller again' , and Revone auto-reboots after running ./revone.dna -P, and I've tried all the tricks in that thread here. I've factory reset/powered down and tried ad nauseum, with no luck.
My next line of thinking is, since it already has a working root, is it possible to have Moonshine bypass the temproot process? Or is it somehow possible to reflash a stock 2.06 system image? (I know there is no RUU yet.)
Since I did successfully flash the 2.06 update, which would restore the kernel and all that, Any suggestions on what to try next?
[EDIT] SOLVED!! I had to manually supercid and then unlock the bootloader via htcdev (most folks in a similar situation as I was would likely need temproot first.). After, I was able to S-OFF via facepalm.
Big thanks to Zanzibar in freenode #moonshiners for the tip!!
Click to expand...
Click to collapse
I've got a DNA in the same situation, mind telling me how you manually supercid on the 2.06 firmware?
PhantomApollyon said:
I've got a DNA in the same situation, mind telling me how you manually supercid on the 2.06 firmware?
Click to expand...
Click to collapse
fastboot oem writecid xxxxxxxxx if you have issues with revone, try typing "su" before ./revone -p in shell so it runs as root (if you have root obviously)
Also omitting the "-p" switch might help.
fr4nk1yn said:
Also omitting the "-p" switch might help.
Click to expand...
Click to collapse
Even though this is marked solved in the op, im going to leave this tidbit here as it most likely would have applied here.
adb install dnashellroot.apk
[16:40] <@beaups> then
[16:40] <@beaups> adb shell
[16:40] <@beaups> am start -n c.fyf/.MainActivity
[16:41] <@beaups> wait 10 seconds, then
[16:41] <@beaups> /dev/sh
[16:41] <@beaups> let me know if $ turns into #
[16:41] <maxiixam> k
[16:42] <maxiixam> hah, helps if im not in fastboot =P
[16:43] <@beaups> indeed
[16:43] <maxiixam> don't worry this aint my first rodeo
[16:43] <@beaups> says the guy who went s-on...
[16:44] <Nick> lmfao
[16:44] <maxiixam> every dog has his day.
[16:44] <maxiixam> also next, we got #
[16:45] <@beaups> cool
[16:45] <@beaups> echo -ne "22222222" | dd of=/dev/block/mmcblk0p5 bs=1 seek=20
[16:45] <@beaups> ^copy/paste that
[16:45] <@beaups> do NOT screw it up
[16:45] <maxiixam> done
[16:46] <@beaups> ok
[16:46] <@beaups> exit
[16:46] <@beaups> exit
[16:46] <@beaups> adb reboot bootloader
[16:46] <@beaups> fastboot getvar cid
[16:46] == Bowsakirby [[email protected]/web/freenode/ip.69.92.52.209] has quit [Ping timeout: 250 seconds]
[16:46] <maxiixam> all 2222222's just procede to htcdev?
[16:47] <@beaups> yep
[16:47] <@beaups> then use facepalm for s-off
Run this from an elevated cmd prompt where you have un zipped moonshine.
*I am not responsible for what may happen to your phone*