5,597,313 Members 38,031 Now Online
XDA Developers Android and Mobile Development Forum

Stuck Fastboot-can't flash RUU to return to stock

Tip us?
 
doctajay
Old
#1  
Senior Member - OP
Thanks Meter 4
Posts: 397
Join Date: Jun 2005
Default Stuck Fastboot-can't flash RUU to return to stock

I was in the process of returning my dna to stock so that I could sell it. I performed the OEM lock function which resulted in my bootloader screen looking what what is in the attached picture. After this I attempted multiple, multiple times to install the RUU.exe on my Mac Mini running Windows 7 in bootcamp mode (not virtualization). Each time it popped up an error saying that it couldn't install. At this point, even after flashing the 1.15 hboot I'm still mostly stuck int he bootloader. My operating system no longer boots. I really only have fastboot access and no idea how to get out of this situation.

I've tried to flash a custom recovery so that at least I could flash a rom, but whenever I try to fastboot it over I get an error saying "FAILED <remote: not allowed>". So if I can't flash a recovery ROM, and I can unlock my bootloader again, and I can't boot into a ROM, what can I do. I spent the last 6 hours trying to find an answer and I'm totally out of options now.
Attached Thumbnails
Click image for larger version

Name:	CAM00011.jpg
Views:	460
Size:	250.3 KB
ID:	2469353  
Droid DNA
 
cmay227
Old
#2  
cmay227's Avatar
Senior Member
Thanks Meter 80
Posts: 194
Join Date: Jun 2010
Quote:
Originally Posted by doctajay View Post
I was in the process of returning my dna to stock so that I could sell it. I performed the OEM lock function which resulted in my bootloader screen looking what what is in the attached picture. After this I attempted multiple, multiple times to install the RUU.exe on my Mac Mini running Windows 7 in bootcamp mode (not virtualization). Each time it popped up an error saying that it couldn't install. At this point, even after flashing the 1.15 hboot I'm still mostly stuck int he bootloader. My operating system no longer boots. I really only have fastboot access and no idea how to get out of this situation.

I've tried to flash a custom recovery so that at least I could flash a rom, but whenever I try to fastboot it over I get an error saying "FAILED <remote: not allowed>". So if I can't flash a recovery ROM, and I can unlock my bootloader again, and I can't boot into a ROM, what can I do. I spent the last 6 hours trying to find an answer and I'm totally out of options now.
You need to unlock again in order to flash back a custom recovery. You also need to have the stock splash screen before you ruu. Had the exact same issue you had. Stock h-boot, stock splash screen and relock and all should be good.
 
doctajay
Old
#3  
Senior Member - OP
Thanks Meter 4
Posts: 397
Join Date: Jun 2005
That is my main problem. All of the unlock methods require me to load load an apk to change the CID. I can't do that in fastboot. Is there another unlock method I'm missing that allows you to do it from the fast boot mode?

Sent from my LG-D800 using Tapatalk
Droid DNA
 
mopartonyg
Old
(Last edited by mopartonyg; 23rd December 2013 at 04:13 PM.)
#4  
mopartonyg's Avatar
Senior Member
Thanks Meter 126
Posts: 554
Join Date: Jan 2011
Location: L.A. Area
if u have your original unlock code from htc dev I think u can fastboot flash that code to unlock again. its in the forum somewhere just not sure where it is.
try this thread, good luck

http://forum.xda-developers.com/show....php?t=2160677
 
cmay227
Old
#5  
cmay227's Avatar
Senior Member
Thanks Meter 80
Posts: 194
Join Date: Jun 2010
You don't have to run a apk to change the cid just Google change cid commands, you do it through adb change it to 22222222 then redo the HTC dev to get your unlock.bin again if u don't have it.

Sent from my HTC6435LVW using XDA Premium 4 mobile app
 
thayl0
Old
#6  
thayl0's Avatar
Senior Member
Thanks Meter 69
Posts: 653
Join Date: May 2013
Location: Winston-Salem

 
DONATE TO ME
Quote:
Originally Posted by doctajay View Post
I was in the process of returning my dna to stock so that I could sell it. I performed the OEM lock function which resulted in my bootloader screen looking what what is in the attached picture. After this I attempted multiple, multiple times to install the RUU.exe on my Mac Mini running Windows 7 in bootcamp mode (not virtualization). Each time it popped up an error saying that it couldn't install. At this point, even after flashing the 1.15 hboot I'm still mostly stuck int he bootloader. My operating system no longer boots. I really only have fastboot access and no idea how to get out of this situation.

I've tried to flash a custom recovery so that at least I could flash a rom, but whenever I try to fastboot it over I get an error saying "FAILED <remote: not allowed>". So if I can't flash a recovery ROM, and I can unlock my bootloader again, and I can't boot into a ROM, what can I do. I spent the last 6 hours trying to find an answer and I'm totally out of options now.
You device most likely can't downgrade due to having a locked device. Have you tried flashing the 2.07 ruu
 
doctajay
Old
#7  
Senior Member - OP
Thanks Meter 4
Posts: 397
Join Date: Jun 2005
Thank you for all of the replies. Actually the change of the CID command might have worked but I didn't see that reply before I had tried another method found in this thread: http://forum.xda-developers.com/show....php?t=2570548.

I was truly stuck in fastboot and couldn't flash a custom recovery at all. Well I used the advice from a previous thread and edited the firmware .zip posted in the first post of this thread: http://forum.xda-developers.com/show....php?t=2314771. I had initially tried to flash the .zip posted but when I tried to boot into the recovery it wouldn't work. So I opened the .zip file without extracting it and removed the recovery.img from the .zip, I then took the TWRP custom recovery and inserted it into the .zip (if you extract the zip this will not work; you need to use software that can edit a zip without extracting it. On the Mac, which I was using, I used Spring). I renamed the TWRP recovery to "recovery.img" to match what I had previously deleted.

Then I flashed this edited firmware.zip by using the following command in usb fastboot mode (here's the link for my edited file):

fastboot oem rebootRUU
fastboot flash zip YOUREDITEDFILE.zip
fastboot reboot

This then allowed me to boot into recovery. I thought I had figured it out and could now sideload a ROM using the "adb sideload" command and flash some type of ROM that would boot. This failed miserably; it would allow me to push the file, but the install would always fail before it completed.

So then I found this thread here: http://forum.xda-developers.com/show....php?t=2570548. I first flashed the two .zip files that were posted in post #44. then I flashed the full RUU posted in post #1. This gave me a bootable stock ROM. Praise God!!!

Finally I went back to this thread: http://forum.xda-developers.com/show....php?t=2293919, and flashed the following code.

Code:
adb devices (your device should be listed)

adb reboot bootloader

fastboot devices (your device should be listed)

fastboot oem writesecureflag 3

fastboot reboot-bootloader

*verify you are locked s-on

fastboot reboot
Not sure why I had such a terrible time, but I'm glad its over and the DNA is finally sold. Thank you for all your help!
Droid DNA

Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes


TRENDING IN THEMER...