My phone was acting buggy with the radios and had HUGE performance issues. To be frank, i think a SNAIL was faster than this phone at the time... I am S-OFF, unlocked and i cannot flash recovery.
I get this output and error:
Code:
sending 'recovery' (8516 KB)...
OKAY [ 1.087s]
writing 'recovery'...
FAILED (remote: image error! (BootMagic check fail))
finished. total time: 1.129s
here is the current HBOOT Config and display:
Code:
FIREBALL PVT SHIP S-OFF RL
CID-VZW__001
HBOOT-1.15.0000
OpenDSP-29.1.0.45.622
eMMC-boot
Just for good measure i re-wrote the CID to 11111111 and locked and unlocked the bootloader again to no avail, thinking it was possibly that being unlocked during an RUU. The thing is, while unlocked, the RUU still processed... Oh and the phone boots up fully. i have ZERO issues with actually using the phone, but i cant believe i am stuck on a stock rom and not allowed to flash a custom recovery... >_>
Other thing... just to see if this would help, i used junkmail9's ENG HBOOT with the RegawMOD Customizer to flash the ENG hboot to try my luck. STILL no good. i can flash hboot directly, and whatever else, but is recovery just stuck??
i really want to be free again, so can someone please explain to me why after an RUU even WHILE S-OFF and unlocked, that i cannot flash recovery?
cyberkeeper1 said:
I get this output and error:
Code:
sending 'recovery' (8516 KB)...
OKAY [ 1.087s]
writing 'recovery'...
FAILED (remote: image error! (BootMagic check fail))
finished. total time: 1.129s
Click to expand...
Click to collapse
You did not mention either the recovery image you tried to flash, nor the command you used to try and flash it. There's no point in messing with bootloader lock/unlock if you're s-off. Just leave it alone.
my apologies... well basically, i cannot flash any custom recovery for this phone. CWM 6.0.3.1 which i had before the restore, and i just tried the philZ Touch 5 recovery which is basically the same thing as CWM... for some reason, the recovery partition became locked after the restore despite being s-off. i remember this error before while s-on and locked when I used to have the Wildfire S.
cyberkeeper1 said:
my apologies... well basically, i cannot flash any custom recovery for this phone. CWM 6.0.3.1 which i had before the restore, and i just tried the philZ Touch 5 recovery which is basically the same thing as CWM... for some reason, the recovery partition became locked after the restore despite being s-off. i remember this error before while s-on and locked when I used to have the Wildfire S.
Click to expand...
Click to collapse
alright, i am a dodo-bird... apparently, i really need glasses because i JUST noticed that i was flashing a zip file.... dang it... for whatever reason, it can flash zip files, but i guess i didnt have the right one. anyhow, no help needed now. Mods, you can close the thread... my apologies for the wasted space. If its any consolation, i havent really slept so.... yea. lol. thanks for the help thus far.
i wasnt flashing the IMG file like i should have been.
similiar issue
hello users of the almighty xda!
I have obtained s-off using dirtyracun and flashed between team venoms viper rom and cyanogenmod10.1 multiple times
this last time I tried to flash back to viper2.2.0 from cyanogenmod because of the problems with the m2 snapshot I wiped everything as usual including cache,data, and even a factory reset and installed the viper rom and said everything was good to go and now the phone wont boot past the htc screen
so I figured i'd reflash the viper boot.img to see if that would help and doesn't
not only will it not boot but when I go to the bootloader and try to enter recovery it flashes and I see the clockwork mod symbol and then it boot loops back to the htc logo endlessly
wtf! ugg! any ideas oh great xda users?
p.s im also under the impression that because im s-off I cant RUU back to stock is this the case?
styxking said:
im also under the impression that because im s-off I cant RUU back to stock is this the case?
Click to expand...
Click to collapse
This is not true. You may at any time run the RUU to restore borked programming. Besides, the dirtyracun method of flashing s-off is risky to say the least. I used facepalm s-off and it was stupid easy. Anyhow, run the RUU and then immediately run a factory reset. The RUU formats and repairs all partitions on the device and the factory reset restores the radio and baseband as described by mdmower.
Sent from my ADR6410LVW using xda app-developers app
Do the following to prepare for RUU-
Run these commands in order:
fastboot oem resetRUUflag (wait for reload)
Fastboot oem rebootRUU
Fastboot erase cache
Fastboot flash zip name_of_file.zip
Alternatively, you can run the automated HTC RUU utility, but it often fails vs. A manual reflash.
Sent from my ADR6410LVW using xda app-developers app
ignore please, came late and didnt notice
gonna try it
thanks for the response. I agree the dirtyracun method is pretty risky, but at the time I think it was the only s-off method I could find
well I will ruu then
thanks for the detailed fastboot commands and such
I don't have to relock the bootloader do I?
Related
Hi!
Yesterday i managed my Flyer to S-off via revolutionary tool.
Today i wanted to update to Honeycomb with this tutorial:
+
Google search: android.modaco.com Installing Honeycomb on your Flyer
Guide from Paul.
i got now stuck after the htcdev bootloader unlock.
i should transfer the cwm recovery file via fastboot into the flyer
command: fastboot flash recovery revolutionary-cwm-4.0.1.4-flyer.newhboot.img
Code:
< waiting for device >
sending 'recovery' (4682 KB)...
OKAY [ 0.753s]
writing 'recovery'...
(bootloader) signature checking...
FAILED (remote: signature verify fail)
finished. total time: 1.198s
Why this is failed? i tried to do the next step, getting into clockworkmod recovery but nothing happens.
My Flyer shows now:
Code:
*** RELOCKED ***
*** Security Warning ***
FLYER PUT SHIP S-ON RL
HBOOT-1.11.0006
MICROP-0950
RADIO-3821.08.00.26_M
eMMC-boot
Aug 29 2011, 13:32:02
Fastboot 9v AC (because charging)
VOL UP
VOL DOWN
POWER
Bootloader
reboot
reboot bootloader
power down
What can i do now? any idea?
edit: adb don't work, fastboot works.
I'm going crazy tried to reunlock bootloader via htcdev. When i flash the unlock token i get same error
Code:
C:\Users\h0f1\Desktop\htc\android-sdk_r15-windows\android-sdk-windows\platform-t
ools>fastboot flash untlocktoken Unlock_code.bin
sending 'untlocktoken' (0 KB)...
OKAY [ 0.015s]
writing 'untlocktoken'...
(bootloader) signature checking...
FAILED (remote: signature verify fail)
finished. total time: 0.019s
Why in the world would you use the htcdev unlock? Go to flyer development and follow globatron's honeycomb guide. Much better than voiding your warranty.
Sent from my PG86100 using Tapatalk
i did yesterday exactly those steps from globatron for soff and cw recovery.
For getting Honeycomb i used another guide yesterday.. because i found this site today..
I really dont know what to do now
Worst case run ruu of your stock software
Sent from my HTC Flyer P510e using xda premium
somehow it doesnt work
C:\Users\h0f1\Desktop\htc\android-sdk_r15-windows\android-sdk-windows\platform-t
ools>fastboot flash untlocktoken Unlock_code.bin
sending 'untlocktoken' (0 KB)...
OKAY [ 0.013s]
writing 'untlocktoken'...
(bootloader) signature checking...
FAILED (remote: signature verify fail)
finished. total time: 0.017s
edit:
made it now with other version of fastboot... this is crazy..
so i unlocked again and now i can go on with the other steps?!
I would return to stock then use globatrons update method. Do you know your stock ruu
Sent from my HTC Flyer P510e using xda premium
is going back to stock via ruu possible when i changed hboot, radio and boot file?
the guide from paul says:
Do NOT under any circumstances run the RUU in it’s entirety nor ‘fastboot flash rom.zip’ – this will make irreversible changes that you don’t want!
Be careful if you flash any RUUs or do anything that could revert you to S-ON on a broken system – this could leave you stuck
i think i will recharge and go through the last 4 points..
im afraid
Try to get a new unlock token.
I can not see why running your ruu to stock.would be an issue but I am not 100% certain. I did a revert last week and the only thing I needed to do prior was relock hboot first which you are already locked.
Sent from my HTC Flyer P510e using xda premium
first i wanna say thanks for your help!
i did today the last two steps after recharging the battery.
last 2 steps are putting the new image onto sdcard via adb and second step was factory reset und dalvik wipe. All two steps worked fine for me, but after restart the flyer is going to a bootloop.
what should i do now?
Should i get back with the RUU?
Can i setup honeycomb after getting back with ruu with the tutorial from globatron?
best regards
tom
did you flash the zip through recovery
Sent from my HTC Flyer P510e using xda premium
^the tutorial say get into clockwork recovery mode and type into command "adb shell mount /sdcard && adb push stock-hc-flyer-system.zip /sdcard/"
this command finished after 3 minutes and i was also lookin at the sd card the file is on the sd card.. after this i wiped dalvik and made a factory reset in the clockwork recovery mode. Afterwards Reboot -> then bootloop
lool is it possible that i have to " install zip from sdcard" ? if yes i'm the dumbest flyer user on the world *g*
edit: i tried now to install the update via recovery, it says E: Can't open /sdcard/stock-hc-flyer-system.zip (bad)
h0f1 said:
lool is it possible that i have to " install zip from sdcard" ? if yes i'm the dumbest flyer user on the world *g*
edit: i tried now to install the update via recovery, it says E: Can't open /sdcard/stock-hc-flyer-system.zip (bad)
Click to expand...
Click to collapse
Re-download, it's corrupt.
ikingblack said:
Re-download, it's corrupt.
Click to expand...
Click to collapse
+1
Sent from my HTC Flyer P510e using xda premium
really i promise i will neveer ever never try to flash/hack/root anything. its just horrible thinking all the time you brick it or anything else xD
i tried to reboot bootloader via adb in the recovery mode, flyer turned off and now nothing happens. cant go into bootloader or something else.. trying to recharge again, maybe battery is low again (i hope..)
well i will go on tomorrow evening.
great work guys anyways, thanks
tom
h0f1 said:
really i promise i will neveer ever never try to flash/hack/root anything. its just horrible thinking all the time you brick it or anything else xD
i tried to reboot bootloader via adb in the recovery mode, flyer turned off and now nothing happens. cant go into bootloader or something else.. trying to recharge again, maybe battery is low again (i hope..)
well i will go on tomorrow evening.
great work guys anyways, thanks
tom
Click to expand...
Click to collapse
I don't know if it's possible to really stop it from booting or displaying anything on the screen. Recharge and once it's done hold power button for a long time.
Good Luck
help fully bricked htc flyer p510e
here is what i did step by step:
bought an htc flyer, then upgraded it officially to honeycomb
i did not like honeycomb so i unlocked bootloader with htc dev method
then flashed recovery and rooted....
changed the misc_version and downgrade back to gingerbread with fastboot flash zip rom.zip
it worked........gta 3 and gta vice city worked.......few months later the gta 3 and vice city started crashing( just like honeycomb)
so i got s-off with revolutionary.....and flashed honeycomb PG41IMG.zip
that worked...........few months later i wanted gta back so i could not take i tried flash back down but did not work...it would get stuck in RUU mode ...so i flashed PG41IMG.zip back and that worked ..i was not bricked...so i tried another method
i flashed fastboot express downgrader.nb0 and
flyer downgrader.nb0
then changed gingerbread rom.zip to PG41IMG.zip and placed it on sd card
went into bootloader and let it flash
the bootloader at this moment:
***security warning***
pvt chip s-on
hboot 1.10.000
..................
it does not show whether the bootloader is locked or unlocked......no recovery.......tablet does not boot.....only to bootloader and fastboot.....
i tried to flash the unlock token for bootloader but get
signature failed error....
i tried to flash the honeycomb PG41IMG.zip but get
checking header failed
remote[signature failed]
cant flash anything because of that ...cant flash recover to even turn off the verification signature check.....
plz help ...whether you help me to fix it back to gb or hc to dont care ..just want it to work
plz help me fast
battery charges but phone goes into fastboot .....
plz help
just ask if u need more information on the situation..
plz anyone
Should probably find a good RUU that is compatible, create a gold card and do a clean re-load of compatible ROM.
I had followed this video ht tp://w ww.youtub e.com /watch?v=hQtUxEL8pd8 and did everything correctly. When I go to boot my phone up it shows the blue android boot animation then the green HTC animation then restarts.
Hboot 1.57
Somehow my recovery got deleted.
Clockworkmod recovery is installed.
I just don't know what to do
Is there a way I can just undo everything and go back to the stock rom?
Edit: Tried ViperROM and it's doing the exact same thing.
Make sure you are wiping everything except sdcard and then flash the rom. Maybe even try changing recoveries to 4ext.
Sent from my PG86100 using Tapatalk 2
I assume you are s-off correct? I suggest going with Scotty's idea and switching to 4ext recovery. Cwm has been know to cause issues with the evo 3d. I'm also assuming that you mean hboot 1.58 not 1.57. FYI you can use any hboot with those ROMs. Just can't use the stock 2.89 kernel with any other hboot but 1.58. You also havnt specified whether or not your using the stock kernels that come with the ROM.
The meanrom by default flashes the VM kernel so if your on hboot 1.58. You have to flash the stock 2.89 kernel in the meanrom folder that's generated after you flash meanrom.
As for viperom you shouldnt have any problem flashing it considering that its compatible with any hboot. Which brings me back to my main point. Flash 4ext recovery and make sure you do a full wipe. That includes data factory wipe, cache and dalvik wipe and wipe all partitions except sdcard.
There's no reason give up when you run into a snag. There's usually a solution to every problem and you did the right thing by posting your question here. There's a ton of possibilities on here to do with your phone. Just read, research, ask questions if you are unsure of something.
Jsparta26 said:
I assume you are s-off correct? I suggest going with Scotty's idea and switching to 4ext recovery. Cwm has been know to cause issues with the evo 3d. I'm also assuming that you mean hboot 1.58 not 1.57. FYI you can use any hboot with those ROMs. Just can't use the stock 2.89 kernel with any other hboot but 1.58. You also havnt specified whether or not your using the stock kernels that come with the ROM.
The meanrom by default flashes the VM kernel so if your on hboot 1.58. You have to flash the stock 2.89 kernel in the meanrom folder that's generated after you flash meanrom.
As for viperom you shouldnt have any problem flashing it considering that its compatible with any hboot. Which brings me back to my main point. Flash 4ext recovery and make sure you do a full wipe. That includes data factory wipe, cache and dalvik wipe and wipe all partitions except sdcard.
There's no reason give up when you run into a snag. There's usually a solution to every problem and you did the right thing by posting your question here. There's a ton of possibilities on here to do with your phone. Just read, research, ask questions if you are unsure of something.
Click to expand...
Click to collapse
I'm S-on, will it matter? And also I do mean 1.57. And one more thing. Does it matter if I boot up into a recovery using the command prompt? Also I'm not sure what kernel it is. I guess the one that's in the zip folder? Also sorry for slow responses I've been working days. Any chance you'll be on tomorrow around 7pm central?
Update: I reformatted everything and tried reinstalling Viperrom through CWM but no dice still boots up and resets. Got 4ext installed. Working from there.
Update: 4EXT is the best recovery I've ever seen and I'm never using CWM again.
Update: I installed VIperROM through 4ext and it's still restarting itself.
Do you have smart flash enabled in 4ext recovery? Its under tools settings.
Jsparta26 said:
Do you have smart flash enabled in 4ext recovery? Its under tools settings.
Click to expand...
Click to collapse
No I do not. Just got off work and I'm doing it now. I don't need to have root for a custom rom do I? Also i youtubed bootloop to see if it is really what's wrong and I came up with this video. ht tp ://www .y outube.co m/watch?v=OKXTD1-fqbc and my phones doing more than that. It's booting up all the way then once the screen and dock begins to load it restarts.
IAnb3rlin said:
No I do not. Just got off work and I'm doing it now. I don't need to have root for a custom rom do I?
Click to expand...
Click to collapse
OK go ahead and turn it on. This will enable you to flash kernels inside recovery having s-on. No you don't have to root to flash a custom ROM. However every ROM has superuser baked into them so flashing one will automatically give you root.
I just want to add that s-on users do not have access to the boot partition which is where your kernel sits. Thats the cause of your bootlooping, before your recovery wasn't flashing any kernel with the ROM. Now with 4ext and smart flash its possible.
Jsparta26 said:
OK go ahead and turn it on. This will enable you to flash kernels inside recovery having s-on. No you don't have to root to flash a custom ROM. However every ROM has superuser baked into them so flashing one will automatically give you root.
I just want to add that s-on users do not have access to the boot partition which is where your kernel sits. Thats the cause of your bootlooping, before your recovery wasn't flashing any kernel with the ROM. Now with 4ext and smart flash its possible.
Click to expand...
Click to collapse
How do I flash a kernel? I'm not really sure what one is, I just know it's really important.
Think of a kernel as a airplane tower that guides the direction of how the android system operates. It controls touch screen, it contains the drivers that make your keyboard work, WiFi, 4g, camera etc.. it is also responsible for taking over android run time after hboot finishes initiating everything to get android up and running. Someone correct me if my information is incorrect please lol. For now, stick with 4ext recovery and enable smart flash under tools settings. Everything should be good after that. I would highly recommend gaining s-off to make everything easier.
If your interested just ask and I'm sure one of us will be glad to help you.
Edit: Its real easy to flash a kernel once smartflash is enabled. A kernel always comes with every ROM or else it wouldn't be able to boot up. As I have stated before in my previous post about s-on users and the limitations.
Jsparta26 said:
Think of a kernel as a airplane tower that guides the direction of how the android system operates. It controls touch screen, it contains the drivers that make your keyboard work, WiFi, 4g, camera etc.. it is also responsible for taking over android run time after hboot finishes initiating everything to get android up and running. Someone correct me if my information is incorrect please lol. For now, stick with 4ext recovery and enable smart flash under tools settings. Everything should be good after that. I would highly recommend gaining s-off to make everything easier.
If your interested just ask and I'm sure one of us will be glad to help you.
Edit: Its real easy to flash a kernel once smartflash is enabled. A kernel always comes with every ROM or else it wouldn't be able to boot up. As I have stated before in my previous post about s-on users and the limitations.
Click to expand...
Click to collapse
I formatted everything using 4ext and installed a rom i also flashed the boot img just incase and it still restarted.
Here's the steps I took.
1. Format everything.
2. Download the.zip file and copy to SD card.
3. Load the recovery and enable smartflash.
4. Installed the rom.
5. Flashed the boot.img
6. Also tried without flashing the boot img.
And just to clarify. I'm installing ViperROM. And I only need the .zip file, correct?
I ended up using RUU to fix it and go back to the stock rom/ect, Then locked the bootloader unlocked it and flashed superuser and rooted it then got s-off using the wire trick. But after I rebooted it keeps taking me back to the jbear bootup logo and when I try to flash a recovery it doesn't load I just get the htc logo then jbear logo then it restarts. I followed this guide.htt p://w ww.yo utube.co m/ watch?v =tRj47iFQvbE I found here on the xda forums.
Do you have the ics ruu correct? Boot back into bootloader and reflash the ruu. Do not unlock your bootloader again. Its not necessary anymore now that you have s-off.
Jsparta26 said:
Do you have the ics ruu correct? Boot back into bootloader and reflash the ruu. Do not unlock your bootloader again. Its not necessary anymore now that you have s-off.
Click to expand...
Click to collapse
Booted up perfectly . So now I'm ready to flash any cdma rom with no problems? Do you know if there's a cdma rom that comes with, beats, adobe flash, and extras?
When I tried to flash a recovery this happened.
C:\android-sdk\platform-tools>fastboot flash recovery 4ext.img
sending 'recovery' (3738 KB)...
OKAY [ 1.018s]
writing 'recovery'...
FAILED (remote: not allowed)
finished. total time: 1.031s
Also my bootloader is saying *** locked ***
IAnb3rlin said:
Booted up perfectly . So now I'm ready to flash any cdma rom with no problems? Do you know if there's a cdma rom that comes with, beats, adobe flash, and extras?
When I tried to flash a recovery this happened.
C:\android-sdk\platform-tools>fastboot flash recovery 4ext.img
sending 'recovery' (3738 KB)...
OKAY [ 1.018s]
writing 'recovery'...
FAILED (remote: not allowed)
finished. total time: 1.031s
Also my bootloader is saying *** locked ***
Click to expand...
Click to collapse
Your s-off. If you have root you can flash your recovery from 4ext updater or use flash GUI image from Google play. If no root, you will need to take your recovery and Rename it to PG86IMG, place it on root of sdcard and boot into bootloader. Let the phone pick up the recovery update and flash it. Power up your phone and take the file off the root of your card. Then power back down into bootloader and click on recovery. Let me know if it works.
Jsparta26 said:
Your s-off. If you have root you can flash your recovery from 4ext updater or use flash GUI image from Google play. If no root, you will need to take your recovery and Rename it to PG86IMG, place it on root of sdcard and boot into bootloader. Let the phone pick up the recovery update and flash it. Power up your phone and take the file off the root of your card. Then power back down into bootloader and click on recovery. Let me know if it works.
Edit: just realized your using virgin mobile correct? I believe the reason your phone kept bootlooping with viper ROM was because of hboot. Try flashing a different hboot with the same method as the ruu and recovery.
Click to expand...
Click to collapse
I downloaded root checker and apparently I'm not root anymore. Yes I'm VM. I'm trying to rename the recovery and update it using the SD card now.
I tried changing the name and it won't detect it. Do I rename the img file or use a zip file? For the RUU I used the pc program to update it and the recovery I use fastboot in the cmd prompt. How do I flash a different hboot? Would I be able to use fastboot for the recovery if i reunlocked the boot loader?
IAnb3rlin said:
I tried changing the name and it won't detect it. Do I rename the img file or use a zip file? For the RUU I used the pc program to update it and the recovery I use fastboot in the cmd prompt. How do I flash a different hboot? Would I be able to use fastboot for the recovery if i reunlocked the boot loader?
Click to expand...
Click to collapse
My bad. Yes, get the zip file version. As for hboot, same way your trying to flash the recovery.
Jsparta26 said:
My bad. Yes, get the zip file version. As for hboot, same way your trying to flash the recovery.
Click to expand...
Click to collapse
When I tried to update it said Invalid model ID update failed. For the PG86IMG file.
IAnb3rlin said:
When I tried to update it said Invalid model ID update failed. For the PG86IMG file.
Click to expand...
Click to collapse
OK, get latest twrp recovery zip and do the same thing you tried with 4ext. I know, its a pain in the ass. I had to go through the same thing when I got my phone s-off with wire trick. The reason why I'm having you do this this way is because in case you ever need to have your phone serviced. They will check to see if you unlocked your bootloader or relocked it. Your bootloader is in "locked" state thus, they cannot deny you service regardless of s-on or s-off.
Jsparta26 said:
OK, get latest twrp recovery zip and do the same thing you tried with 4ext. I know, its a pain in the ass. I had to go through the same thing when I got my phone s-off with wire trick. The reason why I'm having you do this this way is because in case you ever need to have your phone serviced. They will check to see if you unlocked your bootloader or relocked it. Your bootloader is in "locked" state thus, they cannot deny you service regardless of s-on or s-off.
Click to expand...
Click to collapse
I just ended up unlocking the boot loader again and installing the recovery that way. Then saw this.. oh well lol. I really do appreciate the help. . I'm going to try to install viperrom again, and double backup this time! I'll let you know how it goes.
The issue
If you flash new 3.15.651.16 JellyBean RUU and it only updates hboot to 2.09, phone might end-up in semi-bricked state.
RUU refuses to flash any other partition (even if bootloader is in locked/relocked state) so its impossible to return phone to stock rom.
Error message from fastboot flash zip is;
Code:
fastboot flash zip RUU.zip
sending 'zip' (659905 KB)... OKAY
writing 'zip'... INFOadopting the signature contained in this image...
INFOsignature checking...
INFOrom parsing start ...
INFOrom parsing finish ...
INFOzip header checking...
INFOzip info parsing...
FAILED (remote: 22 loading zip info fail)
What is causing this
Hboot fails to read ruu-info from new encrypted zip after hboot-preupdate and stops flashing process.
Solution
Solution is to flash firmware.zip from JellyBean OTA. Firmware.zip is "old style" zip file, hboot can open this zip and update radio and sbls.
Fix
- Download JB OTA firmware from http://unlimited.io/jewel.htm
- Download fastboot executable (google)
- Put all files in one directory
- Reboot phone into fastboot mode
- Make sure that bootloader is Locked or Relocked. If bootloader is Unlocked, relock it with command fastboot oem lock
- Enter commands
Code:
fastboot oem rebootRUU
fastboot erase cache
fastboot flash zip jewel_jb_ota_firmware.zip
NOTE:
If you see FAILED (remote: 90 hboot pre-update! please flush image again immediately) text after running fastboot flash zip command you have to run fastboot flash zip command again.
After this flash stock RUU again.
Permanent fix
- S-OFF your phone. With S-OFF phone you can always flash decrypted, unsigned and/or older RUU and get phone working again easily. :good:
Please report any success / failures into this thread. Also tell little bit information about your device, like;
- What hboot you had
- Was radio flashed through recovery
- Was hboot downgraded
- CID
-- Reserved --
Thanks for your work
Sent from my EVO using xda premium
thanks fuses
Wow fuses, this is gonna help A LOT of people. This community is really lucky to have your attention. Thanks. :thumbup::beer:
Sent from my EVO using xda premium
I ran this... Worked to a T. Debating whether or not to s-off...
But, this did in fact update my radios..
Phenomenal. Just to be clear with what I did...
Ran Fuses instructions. Then I did the RUU GUI update in Windows... back to stock, Tampered in bootloader removed. Testing the stock radios and what not, but so far it's perfect.
*** Phone has to be RELOCKED****
I am not sure if I am successful or not right now. Phone is showing HTC black screen with green bar below it. The green bar is not ALL the way across, looks like 95% after running the commands. Not sure what to do so I issued "fastboot reboot"
Phone looks to be in bootloop so I got back into HBOOT.
First I relocked the phone. Rebooted. Then Rebooted into fastboot.
Then ran commands, screen shots are attached.
Seeing this message after running commands:
FAILED (remote: 90 hboot pre-update! please flush image again immediately)
Changes noticed in Bootloader:
My RADIO updated from 1.02.12.0427 to 1.12.11.1119
OpenDSP updated from OpenDSP-v25.1.0.32.0405 to OpenDSPv31.1.0.45.0815
Update:
Put the phone into fastboot and then ran the windows Jellybean RUU. Looked like the RUU got about 98% thru and then gave me a USB error. Then the phone rebooted and it looks like everything updated. Phone is booting into JellyBean. Should I retry installing the RUU?
Cloves
Rerun the ruu. Just hit the up arrow and then enter
Sent from my EVO using Tapatalk 2
I don't personally have a need for this but I know others do so thanks! Nice to know this is there if needed. :thumbup:
Thanks,
Everything looks good. Phone shows RELOCKED and 4.1 is running. Thanks for the fix!
saved my ass. thanks!
My 4G LTE was on HBOOT 2.09
Tried to S-OFF and downgrade HBOOT by DirtyRacun
Was stuck at a point where the screen went blank for a long time
After that the phone does not power on...
Even the PC does not detect it...
Help please...
Seek out soul shadow . He's usually in the stickied threads in original development. He seems to know a hell of a lot about this phone and bricks/semi bricks
Sent from my EVO using xda premium
aankush said:
My 4G LTE was on HBOOT 2.09
Tried to S-OFF and downgrade HBOOT by DirtyRacun
Was stuck at a point where the screen went blank for a long time
After that the phone does not power on...
Even the PC does not detect it...
Help please...
Click to expand...
Click to collapse
Fastest way to get support for DirtyRacun is to join #unlimited channel on freenode.
Lets keep this thread clean, semi-brick on 3.15.651.16 stock RUU stuff only.
Well guys, time to add some info. If you lock and re-flash the RUU file and you get "SBL VERIFY FAILED" errors (but the RUU still completes) and you can't htcdev unlock (signature failed), you should use this fix. Helped me get my friend's phone S-off using Dirty Racun.
Fuses said:
Permanent fix
- S-OFF your phone. With S-OFF phone you can always flash decrypted, unsigned and/or older RUU and get phone working again easily. :good:
Click to expand...
Click to collapse
is this true?
if we're running stock JB (newer hboot), then we can downgrade it to stock ICS (older hboot) via RUU
un1ocked said:
is this true?
if we're running stock JB (newer hboot), then we can downgrade it to stock ICS (older hboot) via RUU
Click to expand...
Click to collapse
Um,...yes. if fuses posted it and it's about S-off,... it's true.
Sent from my EVO using xda premium
un1ocked said:
is this true?
if we're running stock JB (newer hboot), then we can downgrade it to stock ICS (older hboot) via RUU
Click to expand...
Click to collapse
Yes it is true, but always download full stock RUU and use that. There is some problems with repacked firmwares.
After I typed rebootRUU my screen changed to an HTC screen and stayed there for like 30 min, I tried to flash the zip but my phone wasn't recognized. But ever since that exact moment my computer has f***** up. Does anyone know why this happened
Sent from my EVO using xda premium
Jeffrey4Free said:
After I typed rebootRUU my screen changed to an HTC screen and stayed there for like 30 min, I tried to flash the zip but my phone wasn't recognized. But ever since that exact moment my computer has f***** up. Does anyone know why this happened
Sent from my EVO using xda premium
Click to expand...
Click to collapse
Probably windows dropped fastboot-drivers. Try installing drivers again or use Linux, ubuntu live-cd works just fine.
I'm somewhat of a noob at this - this is my first HTC, so I had no idea what S-Off or unlocked bootloader meant. With my Samsung, rooting and installing a custom recovery involved a one-click method, so I never had to learn all the ins and outs of this stuff. With this DNA, I used the revone method (since the phone was purchased with 2.06 firmware already installed), so I still didn't need to learn much.
Anyway, I recently tried to go back to stock. I figured that would involve an RUU, going back to S-On, and locking the bootloader. So I first (yes, before performing the RUU like a dodo) used revone to go back to S-On, then found something saying I needed to execute "fastboot oem writesecureflag 3", so I did that, and now I am stuck at fastboot. I don't have access to CWM recovery, and if I try to boot beyond fastboot it hangs on the initial HTC screen.
Without being able to use ADB since it doesn't boot that far, I can't go back to S-Off via revone. I can't flash anything that I have been able to find so far via fastboot because it fails at signature verification. And I can't use the RUU that I found because it is firmware 1.15 and it won't allow me to install on top of 2.06.
Does anyone have any ideas on how to fix this? Is there a way to get to S-Off through fastboot? Is there an RUU for the 2.06 firmware? I have spent a few days searching and the answer to both seems to be no...
UPDATE: I grabbed the Rom.zip out of the 1.15 RUU and tried flashing that via fastboot (in RUU mode). I got the following message:
sending 'zip' (913111 KB)...
OKAY [ 35.667s]
writing 'zip'...
(bootloader) adopting the signature contained in this image...
(bootloader) signature checking...
(bootloader) rom parsing start ...
(bootloader) rom parsing finish ...
(bootloader) zip header checking...
(bootloader) zip info parsing...
FAILED (remote: 22 loading zip info fail)
finished. total time: 118.073s
Click to expand...
Click to collapse
I assume this has something to do with the firmware version difference (1.15 vs. 2.06). But I was very excited to see a signature check be successful for once.
I should note that the ROM I was running when doing this was Newt's NOS m7 v 3.0.6
When selecting recovery from the fastboot menu, it does nothing?
If that's a yes... You need s-off again.
Phaded said:
When selecting recovery from the fastboot menu, it does nothing?
If that's a yes... You need s-off again.
Click to expand...
Click to collapse
It doesn't do nothing per se, it shows a screen that I'm not used to with a red triangle and exclamation point on top of a picture of a phone with a blue background. I assume this is the recovery screen from the factory, not the CWM recovery I had installed previously.
Is there a way to get s-off without ADB (only using fastboot)?
Flash firmware zip located on the moonshine thread, then use moonshine
Phaded said:
Flash firmware zip located on the moonshine thread, then use moonshine
Click to expand...
Click to collapse
I successfully flashed the firmware zip from the moonshine thread, but the phone still will not boot past fastboot. I assume since the instructions for moonshine require the phone to be booted to android, this option will not work for me.
jdpalmer2k13 said:
I successfully flashed the firmware zip from the moonshine thread, but the phone still will not boot past fastboot. I assume since the instructions for moonshine require the phone to be booted to android, this option will not work for me.
Click to expand...
Click to collapse
I've been thinking about this. Why did the firmware zip from Moonshine pass signature inspection? Was it signed? Could that same signature be placed on a rom or some other zip that installs a recovery or even somehow performs s-off? I know I am not very well experienced with android development, so I'm probably talking out of my ass.
I recently flashed the RUU from fastboot.
http://forum.xda-developers.com/showthread.php?t=2115987 post#4
I believe what you are looking for is in this thread.
To get back to stock on my phone I needed to flash the stock hboot first before I could use the stock RUU
bwhxeon said:
I believe what you are looking for is in this thread.
To get back to stock on my phone I needed to flash the stock hboot first before I could use the stock RUU
Click to expand...
Click to collapse
I can't flash the stock hboot because I'm s-on and the file fails signature verification.
jdpalmer2k13 said:
I can't flash the stock hboot because I'm s-on and the file fails signature verification.
Click to expand...
Click to collapse
Then your pretty much out of luck. Need to exchange it or possibly do a jtag. Does your phone say tampered/relocked? If so then I'd guess Jtag is the only solution.
Unfortunately the guide you used to go back to stock was pretty dumb in telling you make your phone s-on again. It isn't needed especially if it was just so you could do a clean install and flash other roms.
I was in your situation, but I was lucky enough to have unlocked my phone using htcdev when Jcase released his original unlock method. If the super cid method still works. I would unlock my bootloader the super cid method and not even bother with moonshine. That way you end up with a unlock token and wouldn't get stuck in this situation.
bwhxeon said:
Then your pretty much out of luck. Need to exchange it or possibly do a jtag. Does your phone say tampered/relocked? If so then I'd guess Jtag is the only solution.
Unfortunately the guide you used to go back to stock was pretty dumb in telling you make your phone s-on again. It isn't needed especially if it was just so you could do a clean install and flash other roms.
I was in your situation, but I was lucky enough to have unlocked my phone using htcdev when Jcase released his original unlock method. If the super cid method still works. I would unlock my bootloader the super cid method and not even bother with moonshine. That way you end up with a unlock token and wouldn't get stuck in this situation.
Click to expand...
Click to collapse
Nothing was wrong with the guide. He didn't follow it correctly as he did s-on using revone.
Flashing the firmware zip should allow you to boot up and run moonshine. Are you sure it flashed correctly.
Phaded said:
Nothing was wrong with the guide. He didn't follow it correctly as he did s-on using revone.
Flashing the firmware zip should allow you to boot up and run moonshine. Are you sure it flashed correctly.
Click to expand...
Click to collapse
Correct, the guide was not at fault here, I am just an idiot. Here are the results of flashing the dna2.06firmware.zip file from the moonshine thread: http://pastebin.com/GkgdGt19
Following what is shown at this link, I executed "fastboot reboot-bootloader", selected "Power Down", and then tried to turn the phone on again. I got the same result as always (stuck on the initial HTC quietly brilliant screen - not the bootanimation screen).
Spoke with beaups on IRC. I was running a 4.2 rom that will not run on the stock kernel. Since the only thing I can flash is the signed stock kernel because I am s-on, the only remaining option is to run a 2.06 RUU. However, the 2.06 RUU has not been leaked to anyone's knowledge. So I will have to send off for jtag in order to get s-off, then flash whatever - RUU, custom ROM, what-have-you.
Thanks all for trying to help. I will hang on to it for a while if anyone has any other thoughts or suggestions.
jdpalmer2k13 said:
Spoke with beaups on IRC. I was running a 4.2 rom that will not run on the stock kernel. Since the only thing I can flash is the signed stock kernel because I am s-on, the only remaining option is to run a 2.06 RUU. However, the 2.06 RUU has not been leaked to anyone's knowledge. So I will have to send off for jtag in order to get s-off, then flash whatever - RUU, custom ROM, what-have-you.
Thanks all for trying to help. I will hang on to it for a while if anyone has any other thoughts or suggestions.
Click to expand...
Click to collapse
I talked to beaups last night about the same thing... Hes a good guy. I'm in the exact same boat. I hope there is a break through on this but if not I guess JTAG is our only option. Let me know if you figure anything out jdpalmer, i'd really appreciate it.
Try this please
fastboot oem readcid
What's it say?
Phaded said:
Try this please
fastboot oem readcid
What's it say?
Click to expand...
Click to collapse
VZW_001 for me. Not trying to jack your thread jd, it just seems we have screwed up in the exact same manner.
PiperBen85 said:
VZW_001 for me. Not trying to jack your thread jd, it just seems we have screwed up in the exact same manner.
Click to expand...
Click to collapse
Yep same here
jdpalmer2k13 said:
Yep same here
Click to expand...
Click to collapse
You are s-on... Are you also locked?
---------- Post added at 09:41 AM ---------- Previous post was at 09:39 AM ----------
It's possible you might have supercid, although I doubt it
You could try
Fastboot oem writecid 22222222
Reboot
Fastboot oem readcid
Did it change?
Phaded said:
You are s-on... Are you also locked?
---------- Post added at 09:41 AM ---------- Previous post was at 09:39 AM ----------
It's possible you might have supercid, although I doubt it
You could try
Fastboot oem writecid 22222222
Reboot
Fastboot oem readcid
Did it change?
Click to expand...
Click to collapse
Yes, I am locked. Here is the result of trying to writecid:
Code:
C:\Android>fastboot oem writecid 22222222
...
(bootloader) [SD_ERR] The project does not support SD card
(bootloader) E0902910 E0902E20
FAILED (status read failed (Too many links))
finished. total time: 0.005s
I've spent hours for searching and trying different methods to fix my problem, but no success..
I've droid dna, with S-OFF, but NO htcdev ulocked bootloader, nor SuperCid.
I got this phone in this condition, so i have no idea what method previous owner used to gain S-Off
I have some signal issues, and found thread with fix, then i flashed latest rooted stock 3.06 odexed rom(from santod040) and trying to flash stock recovery too,
in order to Factory reset with stock recovery and get stock Radio partition, which should fix my signal drop issue.
TWRP 2.5.0.0 is already installed there, but i can't replace it with stock, nor update to 2.6.x, nor replace with CWM.
Every time i try - " fastboot flash recovery xx.img ", it fails and i'm getting this message:
sending 'recovery' (8380 KB).
OKAY [ 1.005s]
writing 'recovery'...
FAILED (remote: not allowed)
What should i do to flash stock recovery? I was thinking to restore S-ON and go 100% stock, then do factory reset and S-OFF, root, flash recovery again and install custom rom.. But i think it's too long process and there should be other way to fix it.
any help would be greatly appreciated
uNdea said:
I've spent hours for searching and trying different methods to fix my problem, but no success..
I've droid dna, with S-OFF, but NO htcdev ulocked bootloader, nor SuperCid.
I got this phone in this condition, so i have no idea what method previous owner used to gain S-Off
I have some signal issues, and found thread with fix, then i flashed latest rooted stock 3.06 odexed rom(from santod040) and trying to flash stock recovery too,
in order to Factory reset with stock recovery and get stock Radio partition, which should fix my signal drop issue.
TWRP 2.5.0.0 is already installed there, but i can't replace it with stock, nor update to 2.6.x, nor replace with CWM.
Every time i try - " fastboot flash recovery xx.img ", it fails and i'm getting this message:
sending 'recovery' (8380 KB).
OKAY [ 1.005s]
writing 'recovery'...
FAILED (remote: not allowed)
What should i do to flash stock recovery? I was thinking to restore S-ON and go 100% stock, then do factory reset and S-OFF, root, flash recovery again and install custom rom.. But i think it's too long process and there should be other way to fix it.
any help would be greatly appreciated
Click to expand...
Click to collapse
Might try flashify app from play store, or image gui.
Sent from my HTC Droid DNA using XDA Premium 4 mobile app
Unlock Bootloader
uNdea said:
I've spent hours for searching and trying different methods to fix my problem, but no success..
I've droid dna, with S-OFF, but NO htcdev ulocked bootloader, nor SuperCid.
I got this phone in this condition, so i have no idea what method previous owner used to gain S-Off
I have some signal issues, and found thread with fix, then i flashed latest rooted stock 3.06 odexed rom(from santod040) and trying to flash stock recovery too,
in order to Factory reset with stock recovery and get stock Radio partition, which should fix my signal drop issue.
TWRP 2.5.0.0 is already installed there, but i can't replace it with stock, nor update to 2.6.x, nor replace with CWM.
Every time i try - " fastboot flash recovery xx.img ", it fails and i'm getting this message:
sending 'recovery' (8380 KB).
OKAY [ 1.005s]
writing 'recovery'...
FAILED (remote: not allowed)
What should i do to flash stock recovery? I was thinking to restore S-ON and go 100% stock, then do factory reset and S-OFF, root, flash recovery again and install custom rom.. But i think it's too long process and there should be other way to fix it.
any help would be greatly appreciated
Click to expand...
Click to collapse
Thought you need to be unlocked to flash any image, unlocking the bootloader allows you to flash images (write partitions of the phone)
if i were you I will start from the scratch.
Haven't tried any app for flashing yet. Good idea through, ill try as soon as i get home
finanandroid said:
Thought you need to be unlocked to flash any image, unlocking the bootloader allows you to flash images (write partitions of the phone)
if i were you I will start from the scratch.
Click to expand...
Click to collapse
Yea i thought about it too, but as i know there's no way to supercid on 3.06 firmware, am i wrong? Without supercid, i can't unlock bootloader, was getting error 160 when i tried that. Then i read that htcdev could mess up somethung, when phone has s-off so i stopped thinking about bootloader unlock..
uNdea said:
Yea i thought about it too, but as i know there's no way to supercid on 3.06 firmware, am i wrong? Without supercid, i can't unlock bootloader, was getting error 160 when i tried that. Then i read that htcdev could mess up somethung, when phone has s-off so i stopped thinking about bootloader unlock..
Click to expand...
Click to collapse
Yup I read somewhere that unlock the bootloader get u stuck in boot after a while, but yes there is a method
to change cid number and unlock bootloader.
sdamark said:
Might try flashify app from play store, or image gui.
Sent from my HTC Droid DNA using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I've just tried both apps, no success. flasher just says "rebooting in recovery" and nothing happens, waited about 25-30 minutes.
Image gui asks to confirm that i have unlocked bootloader in order to flash kernel/recovery later..
finanandroid said:
Yup I read somewhere that unlock the bootloader get u stuck in boot after a while, but yes there is a method
to change cid number and unlock bootloader.
Click to expand...
Click to collapse
Seems that i can't flash stock recovery until i unlock bootloader and S-ON.
Just wondering, how previous owner flashed TWRP 2.5, without unlocking bt. Any ideas?
Your s-off. Run an RUU. That will give you stock everything. Boot rom. Does signal work? Yes? Flash custom recovery and rom of choice. If not, factory reset from bootloader, then verify signal works. Flash custom recovery, then rom.
Also, being s-off you can write your cid and obtain unlock at htcdev
Phaded said:
Your s-off. Run an RUU. That will give you stock everything. Boot rom. Does signal work? Yes? Flash custom recovery and rom of choice. If not, factory reset from bootloader, then verify signal works. Flash custom recovery, then rom.
Also, being s-off you can write your cid and obtain unlock at htcdev
Click to expand...
Click to collapse
Seems very easy, thank you for help
I'll get 3.06 ruu and run it. Still, I have hboot 1.33, do i need to flash 3.06 hboot manually or it doesn't matter?
uNdea said:
Seems very easy, thank you for help
I'll get 3.06 ruu and run it. Still, I have hboot 1.33, do i need to flash 3.06 hboot manually or it doesn't matter?
Click to expand...
Click to collapse
Flash the 3.06 hboot in bootloader first
Phaded said:
Flash the 3.06 hboot in bootloader first
Click to expand...
Click to collapse
Thank you again guys, my problem is fixed
No problem yo