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
Related
I CAN'T RELOCK THE BOOTLOADER!!!
This only reverts your SPL/HBOOT back to 0.33.0012 after you've installed the Korean FRF91 files and ended up stuck with 0.35.0017 SPL.
Thanks to the guys in the Desire forums and help from the Nexus Q&A, I have reverted my phone to the original HBOOT so I can apply custom roms again.
First you need to root the Korean FRF91 that's on your phone using Paul's instructions for superboot FRF83.
If you are rooted already, skip this step.
http://android.modaco.com/content/g...-erd79-frf83-superboot-rooting-the-nexus-one/
You need to download the EPF30 update, save it to your SD card as PASSIMG.zip.
http://shipped-roms.com/shipped/Passion%20(Nexus%20One)/PASSIMG_Passion_Google_WWE_1.14.1700.1_EPF30_release_signed.zip
Create a new mtd0.img file through this site
http://ks33673.kimsufi.com/misc/
I used the values, CID: 11111111 and Rom version: 0.22.997.0
Save the mtd0.img file to you PC.
Download the flash_image binary (right click, save as)
http://benocharm.lensworks.org/flash_image
Make sure it's saved as flash_image, and not flash_image.txt
If it has a Notepad icon, then it's not saved right.
With mtd0.img and flash_image in the same folder, type these commands from within that directory:
Code:
adb push flash_image /data/flash_image
adb push mtd0.img /data/mtd0.img
adb shell
chmod 755 /data/flash_image
/data/flash_image misc /data/mtd0.img
NOTE: After flashing the MISC partition with the MTD0 from the Desire, you will notice that you have an HTC logo on your phone.
No worries, this goes away after reflashing the EPF30 Nexus One PASSIMG.zip package.
Power off your phone, then turn it on by holding VolDown and pressing Power.
It will start up in HBOOT mode and will prompt you to flash the EPF30 PASSIMG.zip update.
Once this is finished you can root the EPF30 system through Paul's superboot instructions above, then use Rom Manager from the market to apply a custom recovery again.
Now, remember not to flash the new HBOOT again.
I'd recommend flashing the 5.08 radio for the N1 through other means. Search the forum to find the instructions.
Reserved.
Thanks a lot cursordroid.
Finally I managed to downgrade my hboot.
I could save several steps as my phone is unlocked.
So I just needed to:
- make a nandroid backup
- Go through the steps of flashing mtd0.img
- Apply PASSIMG.zip file
- Through fastboot re-install a custome recovery image
- Nandroid restore
Thanks!
rommelin said:
Thanks a lot cursordroid.
Finally I managed to downgrade my hboot.
I could save several steps as my phone is unlocked.
So I just needed to:
- make a nandroid backup
- Go through the steps of flashing mtd0.img
- Apply PASSIMG.zip file
- Through fastboot re-install a custome recovery image
- Nandroid restore
Thanks!
Click to expand...
Click to collapse
That sounds like it should work, except I'm not sure fastboot accepts unsigned recovery images, you might still need to use Rom Manager to flash one.
YMMV
WTF! This can relock the bootloader?
Where is the link to the latest HBOOT?????????????
cursordroid said:
That sounds like it should work, except I'm not sure fastboot accepts unsigned recovery images, you might still need to use Rom Manager to flash one.
YMMV
Click to expand...
Click to collapse
Just did it
You can definitely flash the recovery directly from bootloader when the phone is unlocked.
I forgot to mention one extra step I took.
Delete through adb the PASSIMG.zip file from the sdcard before trying to enter in bootloader and flash the recovery.
For that, I just needed to boot the stock firmware, enable usb debugging mode and:
#adb shell rm /sdcard/PASSIMG.zip
So if I upgrade I loose root? then i root and reflash stock PASSIMG.zip with original HBOOT after flashing Desire hboot I can get stock bootloader meaning? Security gets disabled when using HTC HBoot? so i can relock my bootloader then update using PASSIMG??????????????
I dont think youve realized how happy you made everyone on this forum is you figured out you can relock the bootloader lol!
I CAN'T RELOCK THE BOOTLOADER!!!
This only reverts your SPL/HBOOT back to 0.33.0012 after you've installed the Korean FRF91 files and ended up stuck with 0.35.0017 SPL.
cursordroid said:
This only reverts your SPL/HBOOT back to 0.33.0012
Click to expand...
Click to collapse
And that's already a lot
Not being able to install or upgrade to any signed build (like recent CM 6.0) including official ones... is not funny. It's really annoying.
Going back to normal is lik
e having a new phone again
Then, what does 0.35.0017 do, if not locking the Nexus?
i'm getting an error saying incorrect cid. i actually have korean nexus one. i've been following all the steps but stuck when i try to flash the rom with passimg. big error msg saying incorrect cid. what to do now?
I can also confirm that this method worked with me. Initially screwed by the Korean ROM, but now back to the old bootloader. Thanks!!
i have tried all the method there and followed all the stuff, but it just won't let me flash passimg.zip. i keep getting cid incorrect. any solution people?
evank418 said:
i have tried all the method there and followed all the stuff, but it just won't let me flash passimg.zip. i keep getting cid incorrect. any solution people?
Click to expand...
Click to collapse
Are you using CID value: 11111111?
Yes and it didn't work. Also tried Googl001 but didn't work either. I actually do have Korean nexus one maybe that's why???? Any solution?
Sent from my HTC Legend using XDA App
@cursordroid help me
i'm a newbie, i don't know much about these, but i have installed Korean FRF91
After seeing u'r post i was happy that i could revert back now, but i don't know how to do
i have followed u'r post but i'm stuck in the middle.................
i have created that two files and downloaded EPF30 update.............
where to enter these commands
adb push flash_image /data/flash_image
adb push mtd0.img /data/mtd0.img
adb shell
chmod 755 /data/flash_image
/data/flash_image misc /data/mtd0.img
i have windows 7..............
please help me
my emailid [email protected]
thank you
No need for the help!
I'm back to erd79
evank418 said:
Yes and it didn't work. Also tried Googl001 but didn't work either. I actually do have Korean nexus one maybe that's why???? Any solution?
Sent from my HTC Legend using XDA App
Click to expand...
Click to collapse
Well, if you have a korean one, i'm not sure if there is anything different in that version.
Can you write down all the details from the bootloader screen?
What's the problem with the newer bootloader? Why even downgrade?
rommelin said:
Well, if you have a korean one, i'm not sure if there is anything different in that version.
Can you write down all the details from the bootloader screen?
Click to expand...
Click to collapse
nexusone pvt ship s-on
hboot-0.35.0017
microp-0b15
touch panel-synt0103
radio-5.00.00.04
june 14 2010,12:02:27
Phone: Evo 3D
Android Version: 2.3.4
Software number: 2..08.651.3
Hboot: 1.50
S-On
Done:
1) HTC boot unlock (http://htcdev.com/bootloader)
2) http://forum.xda-developers.com/showthread.php?t=1239821
-was able to push flies over to phone, but command line "fastboot flash recovery recovery.img" resulted in errors
3) tried to downgrade Hboot using RUU and got an error telling me that my current version was most up to date
Common Threads:
1) http://forum.xda-developers.com/showthread.php?t=1388740
-I downloaded Superuser, titanium back up, and a random program that claimed to verify rooting -- all said I was NOT rooted
2) http://forum.xda-developers.com/showthread.php?t=1307982
-My true goal is to install wifi teathering and titanium backup, I don't care much for custom roms
Forum Confusion:
Unlocking the boot loader does not seem to be the same as rooting, but when I've search through the forums people offer one as a solution to the other.
I'd really appreciate any feedback
thanks guys,
-Nave
navenine said:
Phone: Evo 3D
Android Version: 2.3.4
Software number: 2..08.651.3
Hboot: 1.50
S-On
Done:
1) HTC boot unlock (http://htcdev.com/bootloader)
2) http://forum.xda-developers.com/showthread.php?t=1239821
-was able to push flies over to phone, but command line "fastboot flash recovery recovery.img" resulted in errors
3) tried to downgrade Hboot using RUU and got an error telling me that my current version was most up to date
Common Threads:
1) http://forum.xda-developers.com/showthread.php?t=1388740
-I downloaded Superuser, titanium back up, and a random program that claimed to verify rooting -- all said I was NOT rooted
2) http://forum.xda-developers.com/showthread.php?t=1307982
-My true goal is to install wifi teathering and titanium backup, I don't care much for custom roms
Forum Confusion:
Unlocking the boot loader does not seem to be the same as rooting, but when I've search through the forums people offer one as a solution to the other.
I'd really appreciate any feedback
thanks guys,
-Nave
Click to expand...
Click to collapse
Try this, starting over. You shouldnt run into any hiccups.
tailsthecat3 said:
Try this, starting over. You shouldnt run into any hiccups.
Click to expand...
Click to collapse
I received Error [155] Unknown Error
Display From Phone:
***Unlocked***
Shooter XC ship S-ON RL
HBoot-1.50.0000
eMMC-boot
Aug 7 2011, 10:21:40
RUU
Security fail!
Update Fail!
when it rebooted after recovery I still had all of my user data
navenine said:
I received Error [155] Unknown Error
Display From Phone:
***Unlocked***
Shooter XC ship S-ON RL
HBoot-1.50.0000
eMMC-boot
Aug 7 2011, 10:21:40
RUU
Security fail!
Update Fail!
when it rebooted after recovery I still had all of my user data
Click to expand...
Click to collapse
Ive been through this. Relock(lock) it, run the RUU, then proceed with the instructions I linked.
I was never able to run the RUU while the device was 'unlocked'.
tailsthecat3 said:
Ive been through this. Relock(lock) it, run the RUU, then proceed with the instructions I linked.
I was never able to run the RUU while the device was 'unlocked'.
Click to expand...
Click to collapse
I've been trying to lock it back through the CMD, I wrote a little batch file (and I've manually typed it):
cd c:\android
fastboot oem lock
but after it runs a line shows up as follows:
< waiting for device >
I have USB debugging mode on, and I've tried it with the sd card both mounted and unmounted, I have all the drivers, and adb commands are effective...
do you know what I'm missing?
Thanks again for the help,
-Evan
hey im trying to use the ruu to get back to stock , just re locked the phone , and im STILL getting errors with ruu, its saying Update Failed : Hboot version is older , im on hboot 1.5000 .........Im losing my mind trying to get this thing back to stock and out of htc screen logo bootlooping.........any ideas?
navenine said:
I've been trying to lock it back through the CMD, I wrote a little batch file (and I've manually typed it):
cd c:\android
fastboot oem lock
but after it runs a line shows up as follows:
< waiting for device >
I have USB debugging mode on, and I've tried it with the sd card both mounted and unmounted, I have all the drivers, and adb commands are effective...
do you know what I'm missing?
Thanks again for the help,
-Evan
Click to expand...
Click to collapse
That tells me that youre not in fastboot on your device. I can dupe the same message with my phone disconnected from the pc, then I plug it in in fastboot, and all is good.
Please reinstall the drivers needed but it sounds like youre good. On occasion, I wont be able to flash some things or a file cant load. A reboot of the pc fixes those rare cases for me. Also, refreshing the folders where the files are located.
I also had issues using fastboot, flashing things to the evo because I had my nexus connected for a tether.
If I could do it for you, I would. Hopefully I can help.
tailsthecat3 said:
That tells me that youre not in fastboot on your device. I can dupe the same message with my phone disconnected from the pc, then I plug it in in fastboot, and all is good.
Please reinstall the drivers needed but it sounds like youre good. On occasion, I wont be able to flash some things or a file cant load. A reboot of the pc fixes those rare cases for me. Also, refreshing the folders where the files are located.
I also had issues using fastboot, flashing things to the evo because I had my nexus connected for a tether.
If I could do it for you, I would. Hopefully I can help.
Click to expand...
Click to collapse
this just got even worse, I uninstalled the drivers, and now I can't reinstall them. I can't find them. My computer wont recognize my phone at all. I've tried to goto the device manager and find them online automatically, and I've tried the google USB drivers from the extra folder from the SDK Manager...
if you can point me toward the USB drivers that'd be great, but regardless, what your saying is I need to connect my phone while its in the bootloader? not once its booted? or are you saying I need to boot my phone through the bootloader selecting "fastboot" first?
thanks again
-Nave
http://forum.xda-developers.com/showpost.php?p=17083782&postcount=1
Theyre all in there. Youll need those files to root but you should already have the htc sync drivers installed, plus the android usb drivers. You can remove htc sync after installation but keep the drivers.
Boot into hboot and connect it, it may recognize the hardware. Then select fastboot. Fastboot is 'hot swappable' we'll call it, so you can be in fastboot and disconnect and reconnect your usb cable and youll see when its connected-- itll read 'fastboot usb'.
try here
http://developer.android.com/sdk/win-usb.html
tailsthecat3 said:
http://forum.xda-developers.com/showpost.php?p=17083782&postcount=1
Theyre all in there. Youll need those files to root but you should already have the htc sync drivers installed, plus the android usb drivers. You can remove htc sync after installation but keep the drivers.
Boot into hboot and connect it, it may recognize the hardware. Then select fastboot. Fastboot is 'hot swappable' we'll call it, so you can be in fastboot and disconnect and reconnect your usb cable and youll see when its connected-- itll read 'fastboot usb'.
try here
http://developer.android.com/sdk/win-usb.html
Click to expand...
Click to collapse
Great, I have all the drivers, my phone is relocked, and I'm running the RUU prog now, I'll post in a few minutes to say what happens
thanks for all the help so far, I really do appreciate it!
-Nave
navenine said:
Great, I have all the drivers, my phone is relocked, and I'm running the RUU prog now, I'll post in a few minutes to say what happens
thanks for all the help so far, I really do appreciate it!
-Nave
Click to expand...
Click to collapse
Good. Ive done the process on two different 3D's, a few times. If you follow the instructions, its almost as easy to root as my nexus s was.
tailsthecat3 said:
http://forum.xda-developers.com/showpost.php?p=17083782&postcount=1
Theyre all in there. Youll need those files to root but you should already have the htc sync drivers installed, plus the android usb drivers. You can remove htc sync after installation but keep the drivers.
Boot into hboot and connect it, it may recognize the hardware. Then select fastboot. Fastboot is 'hot swappable' we'll call it, so you can be in fastboot and disconnect and reconnect your usb cable and youll see when its connected-- itll read 'fastboot usb'.
try here
http://developer.android.com/sdk/win-usb.html
Click to expand...
Click to collapse
I pushed everything over, got it into the fastboot USB and then typed the "fastboot flash recovery recovery.img" command line
my script was:
sending 'recovery' <5068 KB>...
Okay [ 1.207s]
writing 'recovery'...
<bootloader> signature checking...
FAILED <remote:signature verify fail>
finished. total time: 1.855s
any ideas?
tailsthecat3 said:
Good. Ive done the process on two different 3D's, a few times. If you follow the instructions, its almost as easy to root as my nexus s was.
Click to expand...
Click to collapse
Great! thank you soooo much I finally have everything working the way I want it!
haha it seems so much easier now that I know what I was supposed to do
navenine said:
Great! thank you soooo much I finally have everything working the way I want it!
haha it seems so much easier now that I know what I was supposed to do
Click to expand...
Click to collapse
Where were you going wrong? And what'd you do to correct it? So everyone knows, in case they encounter the same issues.
Sent from my Google Nexus S 4G via XDA Premium
Good Idea:
Problem 1)
The RUU wouldn't run
I had this problem because I had already unlocked the the bootloader
I had to re-lock it in order to fix it
Problem 2)
Then The Recovery.img would push through because I forgot to re-unlock the phone
what I did that made it easier:
I wrote a little batch file to run the scripts - a batch file is a command prompt command list set. you open a notepad, type in the the command lists and save it with a .bat file extension...
so I would install all the files and then make a batch file with the following:
cd C:\android
adb push recovery.img /sdcard/
adb push su-2.3.6.3.zip /sdcard/
adb reboot bootloader
pause
fastboot flash recovery recovery.img
change the C:\andriod to whatever your directory set was
and when the batch program runs
anyway good luck to anyone who ends up here, and thanks again tailsthecat3 for the great help
navenine said:
Good Idea:
Problem 1)
The RUU wouldn't run
I had this problem because I had already unlocked the the bootloader
I had to re-lock it in order to fix it
Problem 2)
Then The Recovery.img would push through because I forgot to re-unlock the phone
what I did that made it easier:
I wrote a little batch file to run the scripts - a batch file is a command prompt command list set. you open a notepad, type in the the command lists and save it with a .bat file extension...
so I would install all the files and then make a batch file with the following:
cd C:\android
adb push recovery.img /sdcard/
adb push su-2.3.6.3.zip /sdcard/
adb reboot bootloader
pause
fastboot flash recovery recovery.img
change the C:\andriod to whatever your directory set was
and when the batch program runs
anyway good luck to anyone who ends up here, and thanks again tailsthecat3 for the great help
Click to expand...
Click to collapse
I appreciate that, thank you.
Want to unlock your bootloader to install a custom recovery and root your One but have no idea how because you have a Mac?
Never fear, Gunnyman is here.
The procedure is actually pretty painless and only takes a few minutes
Some prerequisites:
ADB and Fastboot binaries for OS X, I've attached them to this post.
Your recovery of choice, I'm using Clockwork Mod Recovery, because TWRP seems to have problems with some Aroma installer based ROMS. Get CWM for the One from here
SuperUser.zip
a Unix friendly text editor. I really like Text Wrangler and it's free.
Android File Transfer for Mac macs don't work with MTP mode without this.
In developer Options on the phone, turn on USB Debugging
EDIT:
Thanks to user Shivasmith I now know you can skip textwrangler and
If you hold down the "Alt" (i.e. Option) key on the Mac keyboard in terminal you can do a "column select."
So when you generate the codes for the HTCdev unlock website, you can just do a straight copy-paste without going into TextWrangler. It made it that much quicker
So thanks for the tip!
I've been using macs for 10 years and never knew that.
1. Unzip the adb and fastboot binaries and put them where you can find them. I have a directory on my Mac called /Android and that's where my phone stuff lives, but you can put it anywhere.
2. Put the cwm recovery (or twrp if you prefer) in the same folder as adb and fastboot.
3. Got to htcdev.com and create an account there if you don't already have one.
4. Log in to htcdev.com and choose unlock bootloader.
5. pick the last option for Unlisted device.
6. Open a terminal window and navigate to where you installed fastboot,adb, and your recovery eg: cd /Users/Gunnyman/Android
7. In Terminal execute the following commands ./adb reboot bootloader once in bootloader mode In terminal execute the following command: ./fastboot oem get_identifier_token
8. Open Text Wrangler
9. Copy the output from the terminal window into Text Wrangler make sure you include every line AFTER "please cut the following message"
10. Use Text Wrangler to DELETE (bootloader) from every line and make sure the columns line up exactly.
11. Copy and Paste this output into the box you are provided on HTC Dev. This part is quite annoying, getting the lines to line up.
12. Submit your token. When successful you will be sent a key via email.
13. Put the Unlock.bin file you got via email in the same directory as adb and fastboot on your mac.
14. execute the following command in terminal with the phone in fastboot mode ./fastboot flash unlocktoken Unlock_code.bin
15. Say yes to the prompts on the phone. Bootloader will unlock and the phone will be factory reset (there is NO way to avoid this)
16. OK Now the bootloader is unlocked. Time to install a recovery. In Terminal ./adb reboot bootloader
17. In terminal ./fastboot flash recovery name_of_the_recovery.img
18. After recovery has flashed POWER DOWN PHONE COMPLETELY Then restart it
19. connect phone to the Mac Android File Transfer should fire up
20. Put the Superuser.zip file on your phone
21. in Terminal ./adb reboot recovery
22. Flash the SuperUser.zip in recovery.
23. Pat yourself on the back your phone is now rooted.
great tutorial...thanks. quick question since i have the dev edition (unlock bootlader) can i just follow all these steps but go straight to # 16 to root my One?
thanks again.
Absolutely
WHEN I enter the "fastboot flash unlocktoken Unlock_code.bin i get a "denied " message in the terminal can anyone figure this out for me
What are the cons of rooting the phone and installing a custom recovery?
I know that it voids the warranty. Is there anything else besides that?
Some people reported some functions not working.
Or is that just when you install a custom ROM?
pedromartinez1983 said:
WHEN I enter the "fastboot flash unlocktoken Unlock_code.bin i get a "denied " message in the terminal can anyone figure this out for me
Click to expand...
Click to collapse
I've seen it once before. It was solved by creating a new account on HTC.dev. And getting a new key.
No cons. Rooting doesn't do anything except add access to the super user account built into the device.
gunnyman said:
No cons. Rooting doesn't do anything except add access to the super user account built into the device.
Click to expand...
Click to collapse
Thanks man
Sent from my HTC One using xda app-developers app
gunnyman said:
No cons. Rooting doesn't do anything except add access to the super user account built into the device.
Click to expand...
Click to collapse
Gunny! Good to see you made the right moves for this phone too!
Im reading stuff about att updating that wont allow to unlock bootloader? Is this true?
Sent from my HTC One using Tapatalk 2
MrPlNK said:
Gunny! Good to see you made the right moves for this phone too!
Im reading stuff about att updating that wont allow to unlock bootloader? Is this true?
Sent from my HTC One using Tapatalk 2
Click to expand...
Click to collapse
Not so far.
SU keeps aborting installation when I try to install it, any ideas?
broopa said:
SU keeps aborting installation when I try to install it, any ideas?
Click to expand...
Click to collapse
Youre flashing zip from recovery?
Sent from my HTC One using Tapatalk 2
MrPlNK said:
Youre flashing zip from recovery?
Sent from my HTC One using Tapatalk 2
Click to expand...
Click to collapse
Yeah, from CWM. I tried fixing permissions with no luck.
broopa said:
Yeah, from CWM. I tried fixing permissions with no luck.
Click to expand...
Click to collapse
Did you turn phone on when you flashed recovery and then turn off then boot to recovery?
Sent from my HTC One using Tapatalk 2
I turned off phone, booted phone into BL menu then from there into CWM.
broopa said:
I turned off phone, booted phone into BL menu then from there into CWM.
Click to expand...
Click to collapse
Did you let the phone turn on and boot and then turn it off? Its important because when you unlocked bootloader/flashed recovery it completely reset your system meaning you need to boot it up and let it install the necessary stuff during boot animation (why it always takes so long the first time you boot up)
Sent from my HTC One using Tapatalk 2
I am pretty sure I did, I will reflash the recovery and see if that fixes it.
Edit: I just noticed I am unable to go back and reflash the the recovery. Is there a stock att version without root and CWM already on them so I can start from scratch?
Nice one gunnyman. Never disappoint. Its actually simpler to do on a mac because there isn't any driver installation. I just hope that AT&T allows us to do this for a while so that all of us here can get out key. Thats really all you need. You don't even need to do it, but its always a good idea to just get the key so if AT&T decides to block it again, you're safe.
If you guys are having trouble getting TWRP or CWS to work, make sure you have fastboot turned off in the power settings. It caused mine to not mount data sometimes.
This is a good right up. Finally have a way to do this on my Mac
So I've explored different options on XDA's site for returning to stock and I guess this is why I'm here. I screwed the hell up. I posted this on Phaded's How-To page, but I figured it would also be best to post this in the general Help & Troubleshooting page.
Here's the best way I can explain my issue. Someone please help.
1. My phone is COMPLETELY formatted. No OS now. Zero data.
2. TWRP is installed as my recovery.
3. I can fastboot and adb (only from the recovery obviously)
4. I moonshined the phone in order to S-Off
5. I tried the method to remove S-Off by Phaded
adb devices (verify device ID is listed)
adb shell
su
echo -ne '\x00\x00\x00\x00' | dd of=/dev/block/mmcblk0p3 bs=1 seek=33796
exit
Click to expand...
Click to collapse
When I ran the RUU, I got that error 158 problem. I couldn't flash the HBOOT. downloaded it several times and tried.
6. I flashed it with an AOSP rom and tried the RUU again. No luck.
Now I'm stuck. u_u I tried
adb push "file name" "file directory"
Click to expand...
Click to collapse
so I can drop a zip file in the phone, but it seems to not work. Idk if I did it right. I was hoping to flash a ROM by doing that. smh.
Let me know if there's any other info I can provide. Considering the phone still turns on and I can still get to fastboot and adb, I don't think I'm a lost cause.
Thanks everyone!
UPDATE
I sideloaded a ROM (Carbon) and now I'm up and running. But I still can't RUU it! Figured this detail will help.
I'll keep reading and researching, posting my progress.
Thanks!
Its ok that your'e formatted the main concern would be 1. To be able to turn the phone on and 2. Boot into bootloader and recovery . It sounds like you are able to do both so the term "bricked" doesn't apply here.Okay so first obvious question did you obtain s-off also what bootloader are you on. Also what are you trying to achieve moving forward, going to stock or staying with custom roms, sense or aosp. There is only 1 ruu available for DNA and you need to be relocked to run and have fastboot drivers installed ala HTC sync manager.
Sent from my HTC6435LVW using Tapatalk 4 Beta
xlxcrossing said:
Its ok that your'e formatted the main concern would be 1. To be able to turn the phone on and 2. Boot into bootloader and recovery . It sounds like you are able to do both so the term "bricked" doesn't apply here.Okay so first obvious question did you obtain s-off also what bootloader are you on. Also what are you trying to achieve moving forward, going to stock or staying with custom roms, sense or aosp. There is only 1 ruu available for DNA and you need to be relocked to run and have fastboot drivers installed ala HTC sync manager.
Sent from my HTC6435LVW using Tapatalk 4 Beta
Click to expand...
Click to collapse
1. I obtained s-off with moonshine. I used the above command suggested by Phaded and when I put in
fastboot oem lock
Click to expand...
Click to collapse
(or something like that) it says my phone is locked.
2. What do you mean what bootloader? I guess moonshine, cause that's what comes up when I go to my bootloader screen.
3. I trying flashing the ruu and I get this (see image attached) which the suggested fix for error 158 was to flash the hboot 1.15 (or something). But I can't seem to flash it correctly. I can't even find straight forward instructions on how to do it.
Thanks for responding.
The reason I asked about the bootloader version and I'm not 100% sure about this so someone else may need to chime in is that when you ruu you are flashing firmware which includes hboot so if you upgraded hboot before doing s-off or otherwise went up a version then I'm pretty sure the ruu won't downgrade your hboot airgo the error message. Again this might not be true. At this point all that matters is that your s-off and NOT bricked so instead of toying with an ruu I would choose a stock Rom .zip to flash if its truly stock that you want. Your firmware should be up to date if you took 2.06. There is no ruu for 2.06.
Sent from my HTC6435LVW using Tapatalk 4 Beta
What is s-off?
Sent from my Galaxy Nexus using xda premium
93fuelslut said:
What is s-off?
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
It means you can write to any partition of your nand (internal memory). This means customs roms, kernels, splash screens, firmware, etc. When you are s-on it is more difficult, I can't get into why too many words it just is. If you're not s-off and you like flashing stuff look into it.
---------- Post added at 12:51 AM ---------- Previous post was at 12:41 AM ----------
xlxcrossing said:
It means you can write to any partition of your nand (internal memory). This means customs roms, kernels, splash screens, firmware, etc. When you are s-on it is more difficult, I can't get into why too many words it just is. If you're not s-off and you like flashing stuff look into it.
Click to expand...
Click to collapse
I'm not finding a solid explanation for error 158 which is disheartening - the best offerings are to change USB ports or restart the ruu. Like I said before you are fine on the software end, you can verify you have up to date firmware by comparing the latest below with what you have.
Baseband (radio) 1.01.04.0308
PRI 2.44_002
As for the hboot, how are you trying to flash it? In recovery?
The hboot needs to match the RUU. You need to find the original hboot . It is in a thread with hboot versions and radio versions.
Link to HBOOT please? and answering your questions
Could someone provide a link for the hboot instructions and flashing?
I think my problem is that moonshine screwed up my phone. I relocked my phone, but when trying to run moonshine again, it doesn't unlock the phone. It just says "WTF: What are you dong" and then it just stops and tells me to hit Enter to exit and the phone is still locked, hence why I think I can't flash HBOOT.
I try and flash HBOOT through recovery. I tried doing fastboot to flash it. Recalling from memory, I think the command was:
fastboot flash "file name.zip"
Click to expand...
Click to collapse
and then it says it can't open the file, unknown error. But I can't find any help guides or how-to's that explain the fix for this.
Thanks! Keep asking questions, cause I don't know what info is relevant.
ibthevivin said:
Could someone provide a link for the hboot instructions and flashing?
I think my problem is that moonshine screwed up my phone. I relocked my phone, but when trying to run moonshine again, it doesn't unlock the phone. It just says "WTF: What are you dong" and then it just stops and tells me to hit Enter to exit and the phone is still locked, hence why I think I can't flash HBOOT.
I try and flash HBOOT through recovery. I tried doing fastboot to flash it. Recalling from memory, I think the command was: and then it says it can't open the file, unknown error. But I can't find any help guides or how-to's that explain the fix for this.
Thanks! Keep asking questions, cause I don't know what info is relevant.
Click to expand...
Click to collapse
Moonshine isn't working because you are still s-off.
My thread has the original hboot and instructions to flash it. You do not flash in recovery. You do not put it on your phone at all. Do not push the file in recovery. Read and follow the instructions in the stock thread.
---------- Post added at 02:04 PM ---------- Previous post was at 02:02 PM ----------
You're doing the command wrong or you renamed it PL83IMG.zip.zip
Please, go in my thread, read each step perfectly and follow. It's really quite simple.
Difference
Is s-off/s-on and being locked/unlocked two different things?
Screenshot
Also here Phaded. I tried different variants of flashing the hboot. I renamed it from PL83IMG.zip to HBOOT.zip. It's not HBOOT.zip.zip cause I know Windows 8 automatically appends the end of the file name with the type extension. As you can see, I boot to fastboot, then run rebootRUU, then I'm trying to flash from there. I got frustrated and tried different things, even unpacking the .zip and trying to flash the .img file.
Thanks for your contribution to the community Phaded.
ibthevivin said:
Could someone provide a link for the hboot instructions and flashing?
I think my problem is that moonshine screwed up my phone. I relocked my phone, but when trying to run moonshine again, it doesn't unlock the phone. It just says "WTF: What are you dong" and then it just stops and tells me to hit Enter to exit and the phone is still locked, hence why I think I can't flash HBOOT.
I try and flash HBOOT through recovery. I tried doing fastboot to flash it. Recalling from memory, I think the command was: and then it says it can't open the file, unknown error. But I can't find any help guides or how-to's that explain the fix for this.
Thanks! Keep asking questions, cause I don't know what info is relevant.
Click to expand...
Click to collapse
Strike.
From my S-Off BadSeed DNA
ibthevivin said:
Also here Phaded. I tried different variants of flashing the hboot. I renamed it from PL83IMG.zip to HBOOT.zip. It's not HBOOT.zip.zip cause I know Windows 8 automatically appends the end of the file name with the type extension. As you can see, I boot to fastboot, then run rebootRUU, then I'm trying to flash from there. I got frustrated and tried different things, even unpacking the .zip and trying to flash the .img file.
Thanks for your contribution to the community Phaded.
Click to expand...
Click to collapse
You need to cd to the directory the file is in, which should be where fastboot.exe is
So if it's in say C:\sdk\
Type cd C:\sdk\
Then run command to fastboot
BOOM!
Alright. Worked. I'll keep you all posted. No one really mentioned in any of the tutorials and how-to's that it is VERY important to make sure to CD to the directory. Like there are developers who say just add it to the PATH in Environment Variables. I figured it was enough, but hey, I was wrong.
Live and learn right?
Thank you Phaded.
So basically my problem was, calling the hboot.zip file is not included under Environmental Variables. I have to intentionally CD to that directory.
Hmm, I must have missed putting in the cd step for the hboot. I'll go edit it.
I am currently S-on and I have not been able to successfully flash any new ROM at all. I have tried several times to do a super wipe, flash the new ROM and Gapps but I get stuck in a boot loop and I can't quite figure out the problem. Never had this problem flashing any ROM or even updating my RUU so I am puzzled as to where these issues are coming from. Any insight would be greatly appreciated. I am not complaining about me being there is a very stable rom but I would not mind upgrade to 4.2 or 4.3 and maybe a different ROM. Oh and I'm using TWRP 2.63 I believe is the newest.
Sent from my EVO using Tapatalk 4
hillje1 said:
I am currently S-on and I have not been able to successfully flash any new ROM at all. I have tried several times to do a super wipe, flash the new ROM and Gapps but I get stuck in a boot loop and I can't quite figure out the problem. Never had this problem flashing any ROM or even updating my RUU so I am puzzled as to where these issues are coming from. Any insight would be greatly appreciated. I am not complaining about me being there is a very stable rom but I would not mind upgrade to 4.2 or 4.3 and maybe a different ROM. Oh and I'm using TWRP 2.63 I believe is the newest.
Sent from my EVO using Tapatalk 4
Click to expand...
Click to collapse
Because you are s-on you have to fastboot flash the kernel/boot.img then flash the rom
Look here to fastboot flash kernels/boot.img while s-on
http://forum.xda-developers.com/showthread.php?t=2256478
okay I will definitely try that, was there a point in time when this method change because I have always been S-on
never had to flash and that particular order?
lol in response to the attached photo I am still S-On because my phone would not take the dirty raccoon S off flas.
but lately my phone has been completely spazzing out on me it will do random lock ups and start swyping characters, in opening and closing menus without me pressing any buttons I almost feel like it is on its last leg. Not to mention random shut offs with black screens but still powered on if that makes sense. Normally when that happens it'll get stuck in a boot loop and I'll have to restore a previous backup... #itsucks
hillje1 said:
okay I will definitely try that, was there a point in time when this method change because I have always been S-on
never had to flash and that particular order?
lol in response to the attached photo I am still S-On because my phone would not take the dirty raccoon S off flas.
but lately my phone has been completely spazzing out on me it will do random lock ups and start swyping characters, in opening and closing menus without me pressing any buttons I almost feel like it is on its last leg. Not to mention random shut offs with black screens but still powered on if that makes sense. Normally when that happens it'll get stuck in a boot loop and I'll have to restore a previous backup... #itsucks
Click to expand...
Click to collapse
Some roms have kernel installers for s-on folks MeanBean being one of those roms.
As for s-off DirtyRacun may not be your only option tell me your baseband number.
The spazzing out sounds like a similar problem my buddy was having, he was s-off I ran an RUU and he says it sems to have fixed the problem.
bigdaddy619 said:
Some roms have kernel installers for s-on folks MeanBean being one of those roms.
As for s-off DirtyRacun may not be your only option tell me your baseband number.
The spazzing out sounds like a similar problem my buddy was having, he was s-off I ran an RUU and he says it sems to have fixed the problem.
Click to expand...
Click to collapse
Baseband 1.12.11.1119
hillje1 said:
Baseband 1.12.11.1119
Click to expand...
Click to collapse
Good news you can use FacePalm if you want assistance PM me I'll help you out
bigdaddy619 said:
Good news you can use FacePalm if you want assistance PM me I'll help you out
Click to expand...
Click to collapse
What is facepalm?
It's an s-off exploit
http://forum.xda-developers.com/showthread.php?t=2163013
Facepalm
bigdaddy619 said:
It's an s-off exploit
http://forum.xda-developers.com/showthread.php?t=2163013
Click to expand...
Click to collapse
Are you still able to help me get S-Off with my device. Hopefully that'll fix the issues I mentioned before b/c this is getting ridiculous!
Do you have ADB & Fastboot set up on your computer? If not, look here. This is a small file and the setup is very easy. You may also want to install HTC Sync on your computer so your drivers are up to date. Once you've done this you need to go to the Facepalm thread that Bigdaddy provided a link to previously. In the first post, there are two files to download, the modified boot.img and signed firmware. Download both of these and place them in your ADB-Fastboot folder (if you downloaded and installed the one I linked above, it should be named android-tools). Once you've done this, connect your computer and phone via USB cable. Use your mouse curser and place it on the android-tools folder, then press Shift+right click on the mouse, then select the option to open a command window. Type the following command:
Code:
adb devices
The serial number of your phone should be output on the line below. If not, you might need to change the device type in the notification pull-down on your phone from sync manager to disk drive. Once you're able to successfully run the adb devices command, you are ready to start.
Type:
Code:
adb shell
press enter, then type:
Code:
su
and hit enter. Once you've done this, you can run the command to gain SuperCID on your device. The easiest thing to do is copy the command from the line below and paste it into the command terminal. The command is:
Code:
echo -ne "22222222" | dd of=/dev/block/mmcblk0p5 bs=1 seek=20
Hit enter. Once you've done this, you can begin at step 1, which will reboot your phone to the bootloader. To verify that you've got SuperCID, you should see a line underneath your Hboot version that says something like "CID-22222222". If so, you're ready to move on to step 2, making sure that you're connected via Fastboot USB mode. Just follow the commands in the Facepalm thread and you should be good to go. If after you're done your phone doesn't reboot, simply press the power button to start the phone. You can reboot to the bootloader once the phone powers on to confirm that you're S-off. Also, once you're done gaining S-off, I recommend deleting the two files you downloaded from your android-tools folder to prevent any issues in the future.