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.
Related
Ok, here's the procedure for returning to stock S-ON after running revolutionary if required for warranty reasons.
Preparation
(Windows): Uninstall HTC Sync and any other sync software ( eg Androsync ) that you have been using.
(Windows) : Install these fastboot drivers
Get fastboot and adb tool for windows here
Get Fastboot and adb for linux here
Download the RUU for your device
Download the downgrade hboot for your device:
Flyer downgrade hboot MD5SUM=6f82c00e2029c4bf3cb00e861789e2f8
View downgrade hboot MD5SUM=d3462b3587564db133c2215127485fe4
Check the mdsum of your download
Check the mdsum of your download
Reboot to to fastboot mode
Flash the downgrade hboot
Flyer:
Code:
fastboot flash hboot flyer_downgrader.nb0
View:
Code:
fastboot flash hboot express_downgrader.nb0
Run the RUU for your device
I can't use adb on recovery mode. Can you upload your fastboot driver?
buidung said:
I can't use adb on recovery mode. Can you upload your fastboot driver?
Click to expand...
Click to collapse
1. Yes, you can use adb in recovery mode if you followed the instructions correctly.
2. Done
an system's update
...can be installed if i use this procedure?
I get an error
C:\Users\Namit>fastboot flash zip RUU_Flyer_BrightstarUS_WWE_2.27.1540.31_R_Radio_20.3504.30.089BU_3809.07.04.06_M_release_204116_signed.zip
sending 'zip' (500195 KB)...
OKAY [ 77.287s]
writing 'zip'...
(bootloader) adopting the signature contained in this image...
(bootloader) signature checking...
FAILED (remote: not allowed)
finished. total time: 157.279s
Click to expand...
Click to collapse
EDIT1: Just moved the zip to sdcard as PG41IMG and went into bootloader. It is working right now; will report on results.
EDIT2: Worked! Flashed Radio and rebooted to finish the rest of the installation.
what is the name of hbbot image file in the "rom.zip"? is that "boot_signed.img"?
chong5379 said:
what is the name of hbbot image file in the "rom.zip"? is that "boot_signed.img"?
Click to expand...
Click to collapse
It is something like hboot_xxxxx.nb0
I try to flash the stock recovery by fastboot on my Htc View but not success. It shows "failed, signature .... Bla bla". My device is still s-on and hangs at htc screen. Hmm, I think its recovery partition was damaged and RUU can't overwrite another recovery.img on it. Can someone help me out ? Thanks
Namit1994 said:
It is something like hboot_xxxxx.nb0
Click to expand...
Click to collapse
*.nb0? isnt that should be *.img? im still confusing about this, i tried to use the "boot_signed.img", bootloader dead now, cannot turn on at all, the power light is blinking
Hello there,
I'm really desperate as I have this problem and I hope someone could help me, I'd be really grateful.
My following problem is :
I have an HTC FLYER and I tried to flash a new hboot FROM HERE ( http://forum.xda-developers.com/showpost.php?p=17481836&postcount=2 ) but mistakenly it was from another device, now my FLYER wont turn on at all.
Can someone help me how to flash a new hboot so my device can finally power up ? Please I really need my HTC FLYER to start working.
I tried running ADB and "adb devices" but my device serial doesn't how in the list of attached devices and i don't know neither how to flash the new hboot through adb.
Please I'm really desperate, I hope someone can help me . I'm really afraid my Htc Flyer is dead.
I'm afraid you worry is valid, if you flash an incorrect hboot and it won't boot then the only recovery is to send it for repair. The best option you have is to say that this happened as a result of the HC upgrade OTA.
hm
globatron said:
I'm afraid you worry is valid, if you flash an incorrect hboot and it won't boot then the only recovery is to send it for repair. The best option you have is to say that this happened as a result of the HC upgrade OTA.
Click to expand...
Click to collapse
yes but its bought in sweden and now i live in balkans so no warranty for me and i was thinking if i can fix it with some box method like jtag jig?
I motion that this thread either be stickied or combined with the S-OFF sticky thread.
hboot_1.11.0003.nb0
chong5379 said:
*.nb0? isnt that should be *.img? im still confusing about this, i tried to use the "boot_signed.img", bootloader dead now, cannot turn on at all, the power light is blinking
Click to expand...
Click to collapse
It was hboot_1.11.0003.nb0 in my case.
It can be either, mostly it will be .nb0 but it can be a .img. The important thing is that it is hboot not boot.
Where i can find RUU for my 3g flyer.
Now I use Leedroid rom i want to go back to official 2.3 to wail for official 3.2.
When or where?
Sent from my HTC Flyer P510e using xda premium
Where is can download RUU for my 3g flyer
^_^
I will correct my post
Thz
hi,
I updated to honeycomb using your method, but my tablet is now slower so I wanted to revert back to gingerbread.
The problem is I can't use ADB commands with it. It responds to fastboot commands but doesn't respond to adb commands. It shows: Error: device not found.
I have tried to put the rom.zip in the sd card, which seems to install gingerbread back, but it won't boot.
What can I do? I am desperate now.
Reflash honeycomb before you run out of battery
Past situation:
S OFF with HC HBoot and fully running Dexter's JB.
Wanted:
Downgrade to GB.
What i did:
Run RUU: RUU_Flyer_HTC_WWE_1.36.405.5_R_Radio_20.35.30.089BU_3809.05.0401.04_M_release_189803_signed.exe
The same one i used when i was downgrading to SOFF from HC first time
Present situation:
HTC white screen - does not boot.
I can get into HBOOT where it says:
- REVOLUTIONARY-
FLYER PVT SHIP S-OFF RL
HBOOT - 6.11.1111
MICON - 0850
Radio - 3809.05.0401.04
EMNC-boot
oct 25 2011, 10:55:07
I tried acces recovery but got stuck on HTC white logo screen...
so i tried reflash recovery:
C:\android-win-tools>fastboot flash recovery cwm-4.0.1.4-flyer.img
sending 'recovery' (4644 KB)... OKAY [ 0.750s]
writing 'recovery'... OKAY [ 1.646s]
finished. total time: 2.396s
but stil cant acces it...
What to do from here on.
I also notice that if i POWER OFF it in HBOOT its not complet power down. Its siting on powercharger now. Was at 85% when i started procedure. ADB no responce FASTBOOT worked.
Went this way:
http://forum.xda-developers.com/showthread.php?t=1358758
fastboot erase cache
fastboot oem rebootRUU
fastboot flash zip <name of zipfile>
Flashing will fail with Error 90 first time due to hboot change
fastboot flash zip <name of zipfile>
The on screen indicator on the phone will not reach fully to the right end of the progress bar, this is ok
fastboot reboot
I am in Android. Hope didint loose S OFF.
OK - still S OFF and RECOVERY accesable. Puff
Thanks, so I just run the RUU, wait for it to finish and input the strings you wrote in 2nd post? No need to run RUU/flash rom.zip in the end once again?
teorouge said:
Thanks, so I just run the RUU, wait for it to finish and input the strings you wrote in 2nd post? No need to run RUU/flash rom.zip in the end once again?
Click to expand...
Click to collapse
no need to. Basically i was tould to downgrade from HC i onlly would need to run RUU. I hang up so those r steps that got me working after runing RUU. To migrate up to HC i onlly run RUU and its fine no aditional steps needed. worked 4 times for me like this. I am not exactlly sure what i am doing but worked for me As u can see i was asking for help but couldnt wait more so started to experiment
And yes those strings r onlly thing after runing RUU; u need to download PG41IMG-3G.zip from post i linked.
What is funny is that post i linked is to get HC tbh; i was thinking at the time to restore HC but ended up on GB. Maybe someone alse could explain it but hey as long as it works
See u on GB!
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.
Hello Amaze thread. I flashed jose's Dark Glass ROM based off of CM10.1 and one day my phone turned off and wouldn't boot. I went into recovery and it goes into safe mode because the internal memory card is unreadable, tells me to wipe, etc. but it gives me junk errors. My issue is similar to the issue of someone else in another thread http://forum.xda-developers.com/showthread.php?t=1773723(which was resolved)], but I'm not having such an easy time fixing my problem. When I go into the bootloader and try to flash my RUU from mobilicity by changing it's name to PH85IMG, the blue bar fills up, it says "parsing..." but then it goes back to the bootloader. Does anyone know what is going wrong? Thanks in advance to all you helpful people. Sorry if I violated any rules in this post.
Details: S-OFF + bootloader is unlocked
Edit1: I read that my bootloader had to be locked in order to reflash RUU. I relocked it using Hasoon's all-in-one-tool but the zip file would still go back into bootloader after the blue bar fills up. The zip isn't parsing. I also tried using Hasoon's tool to reflash the RUU. Bootloader says re-locked (still s-off) but it still doesn't work. The CMD spits out this:
Code:
sending 'zip' (331249 KB)...
OKAY [ 32.595s]
writing 'zip'...
(bootloader) zip header checking...
(bootloader) zip info parsing...
FAILED (remote: 24 parsing android-info fail)
finished. total time: 40.896s
andres8900 said:
Hello Amaze thread. I flashed jose's Dark Glass ROM based off of CM10.1 and one day my phone turned off and wouldn't boot. I went into recovery and it goes into safe mode because the internal memory card is unreadable, tells me to wipe, etc. but it gives me junk errors. My issue is similar to the issue of someone else in another thread http://forum.xda-developers.com/showthread.php?t=1773723(which was resolved)], but I'm not having such an easy time fixing my problem. When I go into the bootloader and try to flash my RUU from mobilicity by changing it's name to PH85IMG, the blue bar fills up, it says "parsing..." but then it goes back to the bootloader. Does anyone know what is going wrong? Thanks in advance to all you helpful people. Sorry if I violated any rules in this post.
Details: S-OFF + bootloader is unlocked
Edit1: I read that my bootloader had to be locked in order to reflash RUU. I relocked it using Hasoon's all-in-one-tool but the zip file would still go back into bootloader after the blue bar fills up. The zip isn't parsing. I also tried using Hasoon's tool to reflash the RUU. Bootloader says re-locked (still s-off) but it still doesn't work. The CMD spits out this:
Code:
sending 'zip' (331249 KB)...
OKAY [ 32.595s]
writing 'zip'...
(bootloader) zip header checking...
(bootloader) zip info parsing...
FAILED (remote: 24 parsing android-info fail)
finished. total time: 40.896s
Click to expand...
Click to collapse
In order to flash RUU you will need to be unlocked bootloader because it rejects all time when you try to flash RUU.
So first unlock it and after that try to put ruu on SDcard and then go into recovery .
It will work for sure.
Hit thanks if I helped you !!!
shubham211995 said:
In order to flash RUU you will need to be unlocked bootloader because it rejects all time when you try to flash RUU.
So first unlock it and after that try to put ruu on SDcard and then go into recovery .
It will work for sure.
Hit thanks if I helped you !!!
Click to expand...
Click to collapse
Hi, it still didn't work. Tried it while the bootloader was unlocked and again while it was relocked. It doesn't get past the "parsing" stage. I tried it with two different SD cards already btw and I also checked the MD5 checksum. They match. No luck for me.
andres8900 said:
Hi, it still didn't work. Tried it while the bootloader was unlocked and again while it was relocked. It doesn't get past the "parsing" stage. I tried it with two different SD cards already btw and I also checked the MD5 checksum. They match. No luck for me.
Click to expand...
Click to collapse
Are you sure that your sdcard slot is working ??
Sent from my HTC_Amaze_4G using xda app-developers app
Mobilicity ruu isn't working it's a firmware zip with a update it's not a ruu... And it's not a brick.. Also a ruu can't be flashed from recovery... Flash the t mobile R2 RUU from bootloader and it'll work.
Sent from my HTC_Amaze_4G using XDA Premium 4 mobile app
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?