I could really do with some help on this - Kinda paniking cos i'm afraid!
I posted it in the thread on modaco too, so hopefully I can get some help
I am on a 16gb Wifi Euoropean Flyer that needs the RUU RUU_Flyer_HTC_WWE_Wifi_2.27.1114.31_Radio_20.3504.30.089BU_3809.07.04.06_M_release_204727_signed
I have downloaded all the necessary things, checked all the MD5 sums etc etc.
I have successfully gotten to step 14, where i successfully unlocked the bootloader with the HTC dev tools.
Once the gui option came on screen to say whether i wanted to unlock the bootloader, i selected yes, and instantly the device rebooted, but stayed on the white HTC logo screen.
It stayed like this for about 5 mins, before i held the power button down, restarted and got back to the bootloader. (It says unlocked at the top in pink)
I ran the adb command to flash the updated recovery image, (fastboot flash recovery revolutionary-cwm-4.0.1.4-flyer.hboot0011.img), and it said 'sending' okay and 'writing'okay but once i selected to go to recovery, the decive just stayed on the white splash screen, and i think it is in a bootloop.
I can successfully get back to the bootloader every time, and it is displayed as fastboot USB in red (i can hear the sound as it is connected to my machine), but when i type adb devices, it says device cannot be found.
I can however relock and then subsequently unlock the bootloader using the HTC dev tools, but still get stuck at this point. (when relocked it does say *security warning* as well as locked)
Please please please can somebody help, this would be much appreciated.
(I'm not sure if it is possible to place a recovery image on the SD card and let the bootloader install it as it does the checks at the start?)
Thanks in advance
You can't communicate via adb in fastboot menu
Get back to fastboot
Try to flash recovery again
Fastboot flash recovery "name of recovery file"
Fastboot and adb are two different things
If it fails again, delete the recovery image and redownload and try again
Sent from my HTC Flyer P510e using xda premium
I tired again, i unlocked the bootloader using HTC dev tools, starting through the process instead of using the same email file.
I think the problem is with the HTC dev unlock, cos when i press yes, it gets stuck on the HTC splash screen. (Just out of interest, what should happen when i select yes to unlock on the flyer?)
Flashed the re-downloaded recovery in fastboot (md5 sums match again), this is what was returned:
sending 'recovery' (4746 KB)...
OKAY [ 0.755s]
writing 'recovery'...
OKAY [ 0.612s]
finished. total time: 1.367s
then selected 'bootloader' on the flyer, then 'recovery' and then it still get stucks on the white splash screen.
I double checked all the mb5 sums of all the files i have flashed in this process, and they are all good.
The flyer will not turn off, it just turns itself back on again and again. The only way to make it stay off is to lock the bootloader again
Any reccomendations?
Thanks
I am not sure why the recovery is not flashing
You may want to OEM lock and revert back to gingerbread
Sent from my HTC Flyer P510e using xda premium
thanks, to do that, do i just run fastboot oem lock?
then run the RUU?
That should do it
Sent from my HTC Flyer P510e using xda premium
Phew! That did it, back to GB for now. Thanks ever so much!
Do you recon it is worth my while to try again? I would like to try HC...
I mean you were able to recover so you got that going for you. I am not sure what was causing your problem though.
Yeah, but its a strange one isnt it?
I've just tried to S-OFF with revolutionary, and it reboots to the bootloader, and then stops, with the cmd window just saying, waiting for fastboot..... - it'll stay like this forever untill i turn the device off.
I remember i had this problem the first time i S-OFFed, but cant quite remembver how i fixed it - could this problem be somehow related to the HC install problem?
Maybe try another USB port or uninstall reinstall drivers
how long did you give the htc screen? it may take a lil while for recovery to start. id maybe give it as long as 5 minutes just to make 100% sure its really stuck.
if you wrote the recovery with the unlocked bootloader,im not sure why it wouldnt have worked,other than a bad imagea not compatible image,or possibly a simple fail to start. ive had this happen with TWRP recovery on other devices,and occasionally with clockwork-when booting to recovery it just sticks at the htc screen.
go for it again. assuming youre using all the correct,newest,and matching files,theres no reason it shouldnt work.
if you have the same trouble next time, while the on the white htc screen,when trying to get to recovery,try typing "adb devices" in your command window. if you get your serial number back, try "adb reboot recovery" and see if it starts that time.
the bootloop after unlocking the HC hboot is because that hboot and boot images are not compatible with the GB /system that is still currently on the phone. i was able to "adb reboot bootloader" during the bootloop rather than holding the power button to get back to fastboot so i could flash the recovery.
the *security warning* when you relocked it is becuase the hboot is confused about the firmware that doesnt match it.
hope that helps IMO its worth trying again- honeycomb makes the tablet alot nicer(for me anyway) than gingerbread.
Yeah I left it for at least 10 minutes, and no activity at all, other than the splash screen.
I might give it a go again, I'll report back as to how it goes!
Sent from my HTC Sensation Z710e using XDA App
send me a pm/email if you want me to take a teamviewer look if you get stuck again.
Related
Ok,
So I was following the ez honeycomb guide. (thanks Globatron!) I got all the way to the error 90, and tried again and it failed with error 13 battery low. So I'm like ok and try rebooting it so I can charge it. Well that didn't work and I realized too little too late that that may have been the wrong thing to do. Its screen is black and the notification led is flashing amber. I did get it to fast boot 1 time but it wouldn't reboot into RUU again to finish the flash. I hope that I didn't brick it because its not reacting to anything. I tried holding the power button and also power + volume down.
Any help would be extremely appreciated.
Thanks,
Justin
EDIT::: Still not working, let it sit on the charger for a while, and got it to go back in to hboot. Tried erasing cache and rebooting again from fast boot on laptop and kept getting a ... FAILED (status malformed (1 bytes)) error
Will the device accept any adb or fastboot commands
Sent from my HTC Flyer P510e using xda premium
What version of hboot is on it now? it's not bricked anyway.
I think my battery might be fried.
When I started this procedure it was on hboot 6 something. I don't remember exactly and it won't come on to check.
It won't accept any commands unless I can get it to turn on, which it doesn't seem do except after sitting on the charger for about 3 or 4 hours maybe more. When it does come on it will only come on for a very short while, and I tried to flash it and it gave me a USB write error.
Thanks again
Looks like you have non-functional Bootloader/recovery firmware combination. The Flyer won't charge if the firmware is messed up. Get in touch with Globaltron here and give him all the details of what model you have and what HBoot, recovery , etc. you have loaded. He can fix you up.
I only need to know the current hboot version to tell you how to proceed.
If you can get it on for long enough to get that I can tell you what to do next.
Got It!
ok Im running 6.11.1111 as my hboot
ok, in that case you need to flash the two files in the zip through fastboot as follows:
boot to fastboot mode
Code:
fastboot flash recovery recovery.img
fastboot flash boot boot.img
This will allow you to charge your flyer properly. After that we can proceed with fixing the situation properly.
OOPS
Ok
It wouldn't let me flash either, it said battery too low as an error.
Update
After letting it sit on its mains charger for about 8 hours, it finally let me flash the recovery images you supplied. It did get stuck in a boot loop but I managed to boot back to hboot switch to cwm and power down. Its now charging as normal!
So what would my next steps be?
jcrouzzo said:
After letting it sit on its mains charger for about 8 hours, it finally let me flash the recovery images you supplied. It did get stuck in a boot loop but I managed to boot back to hboot switch to cwm and power down. Its now charging as normal!
So what would my next steps be?
Click to expand...
Click to collapse
The boot loop was expected. There isn't enough of a ROM to boot normally, but you needed cwm both to charge and to be able to continue with the downgrade.
You need to follow this guide. You can skip steps 1-5 from the preparation steps since it appears you have those already done, if you haven't already done steps 6 and 7 from preparation then start there and then complete the procedure steps.
i have the same problem, i have hboot 6.10.102 or something like that, please help . TIA!
I made an observation when I jizzed my flyer up a couple of days ago. If you try to run an RUU from your PC in hboot mode, the RUU will return a low battery error, but if the RUU is run in fastboot mode it will run, at least to the next error if there is one.
Sent from my HTC Flyer P510e using xda premium
Same fix for you akabeware as for jcrouzzo
hey,
Its been a crazy week and I haven't been able to get back to this. I've run into a snag as adb won't recognize the device in fast boot, and it won't boot to be seen by adb.
Thanks again,
Justin
Can not use adb when in fastboot mode, only fastboot commands. Can use adb in recovery or booted device
Sent from my HTC Flyer P510e using xda premium
ok,
tried booting into recovery and its stuck at the htc screen
IM me on skype, contact details in my profile and I'll walk you though this.
Same Problem as jcrouzzo
I have the same problem as jcrouzzo but it gives me sending 'recovery' (4746 KB)... FAILED(status malformed(1 bytes))
what should I do? battery does not recharge
please help Globaltron..
if i can just get it to the OS
i think i messed up boot so badly that it just stuck at HTC logo first then many attempts of flashing other recovery.img boot.img i kinda need just little more than instruction i might need some pros here i guess
Soooo before the flame begins, yes i was stupid to do this so that is covered. Was curious today and never played with the app in question (chainfire 3D) and installed in my LTE. Little did I know this app doesn't work with ICS (so i read?..). Well I installed the driver that came with it and since after initial shutdown from installation, I can only get to my splash screen. I've tried recovery and fastboot combos and neither pass the splash screen >.< Anyone?
U try running the RUU?
Sent from my EVO using XDA
Was thinking about trying that. Worried this may brick my secure element : S
Edit: tried the RUU (RUU_JEWEL_CL_ICS_40_Sprint_WWE_1.12.651.2_Radio_1.02.11.0423_2_NV_SPCS_2.28_003_release_257970_signed), got an unknown error. Attempted the error recovery method from RUU but was unable to get to the bootloader screen...****.
Gotta do it...
sent from my EVO LTE
See post edit.. : S
naterz said:
Was thinking about trying that. Worried this may brick my secure element : S
Edit: tried the RUU (RUU_JEWEL_CL_ICS_40_Sprint_WWE_1.12.651.2_Radio_1.02.11.0423_2_NV_SPCS_2.28_003_release_257970_signed), got an unknown error. Attempted the error recovery method from RUU but was unable to get to the bootloader screen...****.
Click to expand...
Click to collapse
where did you get the 1.12.651.2
all i can find is 1.12.651.1
shipped-roms.com. I guess i could try the .1 version
when i try to run the .1 ruu, it shows im on 1.12.651.1_R2
Just tried the .1 RUU, got error [155]: UKNOWN ERROR again... gonna try the Recover option thru that..
edit* error 155 again after Recovery option success and RUU reflash :'(
edit* I'm not too familiar with ADB, but do you think I could get to my hboot/bootloader screen through it or perhaps Recovery in general?
naterz said:
Just tried the .1 RUU, got error [155]: UKNOWN ERROR again... gonna try the Recover option thru that..
edit* error 155 again after Recovery option success and RUU reflash :'(
edit* I'm not too familiar with ADB, but do you think I could get to my hboot/bootloader screen through it or perhaps Recovery in general?
Click to expand...
Click to collapse
Navigate to your adb tools folder via terminal and type
adb reboot bootloader
tried adb reboot, error device not found : (
ddeecc
naterz said:
Soooo before the flame begins, yes i was stupid to do this so that is covered. Was curious today and never played with the app in question (chainfire 3D) and installed in my LTE. Little did I know this app doesn't work with ICS (so i read?..). Well I installed the driver that came with it and since after initial shutdown from installation, I can only get to my splash screen. I've tried recovery and fastboot combos and neither pass the splash screen >.< Anyone?
Click to expand...
Click to collapse
But you did get to the splash screen and that's a sign of hope..this phone won't even do that. nothing at all screen dead, everything is dead including bootloader. :\
Shutdown the phone and boot into bootloader.
Option 1) do a factory reset and if it doesn't work then,
Option 2) select fastboot then ran Ruu.
Sent from my HTC One X using xda premium
There is no way to boot into bootloader or fastboot, whether through adb or the key combos :S Adb states device not found and the key combos only give me splash then a lightly lit black screen..
Sent from my PC36100 using XDA
Are you positive about not able to boot into bootloader with key combo? Your phone has to pass bootloader before going to the splash screen.
http://htcevohacks.com/htc-evo-4g-l...tc-evo-4g-lte-unlock-bootloadertwrp-recovery/
So you tried booting as instructed as the above link?
Sent from my HTC One X using xda premium
Ive never really pressed the power button a second time after the initial let-off. I'll give it a shot when I get home, but I'm expecting the same results. Just FYI, I DO see the two Orange bars move on the splash screen (upper right) before it goes blank..
Sent from my PC36100 using XDA
Sounds like a case of the looped boot screen
Sent from my HTC One X using xda premium
UPDATE! Phone was completely drained when i got home...plugged into charger, orange light came on! Was able to enter the bootloader through the key combo and successfully entered my TWRP to do a nand restore. Restore went well and am now running again! Brick fixed by draining battery!
Good to hear:good:. brick was fixed by draining battery :what: then why did you need to do a nand restore? Whatever worked for you
why i said it was fixed via drain was that the charge light finally came on after it died and was plugged in, therefore it allowed me to access bootloader which let me into recovery to restore my backed up clean system files. When the nand restore was completed i was actually able to pass my splash screen! : )
so i received two htc eris' from a buddy of mine yesterday so my girlfriend could finally make the move up to a smart phone. neither were ever rooted and were running stock software. one of them works perfect but the other was stuck in an infinite boot cycle so i tried to hard reset it but it gets stuck at the screen with the red triangle and exclamation point.
so i figure maybe ill just try rooting it or at least getting the stock software back on it. im new to rooting but even if i mess up and brick the phone its a brocken spare so who cares. well i got to the point that i try to put it into fastboot usb mode to push a new recovery image to it but it wouldnt load into fastboot usb, the screen just had the red fastboot showing. so i try the working eris and it loads it up no problem. i also tried my htc hero and it didnt have a problem either.
so whats going on with this phone? any ideas why only it cant be loaded into fastboot usb?
goatxxmastr said:
so i figure maybe ill just try rooting it or at least getting the stock software back on it. im new to rooting but even if i mess up and brick the phone its a brocken spare so who cares. well i got to the point that i try to put it into fastboot usb mode to push a new recovery image to it but it wouldnt load into fastboot usb, the screen just had the red fastboot showing. so i try the working eris and it loads it up no problem. i also tried my htc hero and it didnt have a problem either.
so whats going on with this phone? any ideas why only it cant be loaded into fastboot usb?
Click to expand...
Click to collapse
You can only push a new Recovery image using Fastboot if the Eris has the S-OFF bootloader (HBOOT version 1.47.2000 S-OFF). Most Erises are HBOOT 1.46.0000, 1.47.0000, or 1.49.0000 with S-ON.
One method is to install HTC's latest 1.51.0000 bootloader, unlock it, which should allow fastboot to push the recovery image. See http://forum.xda-developers.com/showpost.php?p=23034380&postcount=3 for a more elaborate procedure that you can follow if pushing the recovery image still doesn't work.
I strongly recommend using Scary Alien's version of Amon_RA. Stay away from ClockworkMod Recovery as the default recovery on an Eris - it is problematic if flashes fail. Amon_RA is safer and there are no documented bricked phones from people with Amon_RA. See http://androidforums.com/eris-all-t...2-custom-recovery-trackball-not-required.html
I just unlocked my bootloader (via the toolkit) and then proceeded to install TWRP 2.5 (manually, via fastboot).
The next goal is to root the phone, but I cannot find a way to boot to recovery. I've tried using adb and I've tried it by using the volume keys and power/lock button while in bootloader mode.
The white HTC splash screen comes up with the red warning text at the bottom (the message that comes up when you're booting into a custom recovery -- I forget what it says offhand: something about a build being for development purposes or something). This splash screen is on the screen for maybe half a second before disappearing. After this happens, the normal HTC splash screen (same thing without the red text) pops up and the phone proceeds to boot normally.
This is my second One and the second time I've attempted this. The first time I had no issues, so I'm not sure what I'm doing wrong.
I've tried re-downloading/re-installing TWRP and I've tried fastboot erase cache (which I didn't know about until having searched for a fix). No error messages popped up at any point during the flashing process, so I'm quite confused.
Has anyone else had this happen and if so, how did you fix it?
blackplague1347 said:
I just unlocked my bootloader (via the toolkit) and then proceeded to install TWRP 2.5 (manually, via fastboot).
The next goal is to root the phone, but I cannot find a way to boot to recovery. I've tried using adb and I've tried it by using the volume keys and power/lock button while in bootloader mode.
The white HTC splash screen comes up with the red warning text at the bottom (the message that comes up when you're booting into a custom recovery -- I forget what it says offhand: something about a build being for development purposes or something). This splash screen is on the screen for maybe half a second before disappearing. After this happens, the normal HTC splash screen (same thing without the red text) pops up and the phone proceeds to boot normally.
This is my second One and the second time I've attempted this. The first time I had no issues, so I'm not sure what I'm doing wrong.
I've tried re-downloading/re-installing TWRP and I've tried fastboot erase cache (which I didn't know about until having searched for a fix). No error messages popped up at any point during the flashing process, so I'm quite confused.
Has anyone else had this happen and if so, how did you fix it?
Click to expand...
Click to collapse
I had this issue, if you boot into bootloader does it say tampered? If not turn your phone completely off and then boot it into bootloader. Then you should be able to enter recovery. I ciuldnt enter recovery until my bootloader read tampered.
Sent from my HTC One using Tapatalk 4 Beta
You're right, it won't boot to custom recovery until it says tampered. I'm pretty sure I've rebooted several times since installing TWRP, but either way it's working (for) now. I'm not sure what the hell made it "click," but I'll take it. Thanks.
blackplague1347 said:
You're right, it won't boot to custom recovery until it says tampered. I'm pretty sure I've rebooted several times since installing TWRP, but either way it's working (for) now. I'm not sure what the hell made it "click," but I'll take it. Thanks.
Click to expand...
Click to collapse
Yeah it took me more then 10 tries until I just shut it off and then went into bootloader and there was the tampered. Glad it worked out for you.
Sent from my HTC One using Tapatalk 4 Beta
I had the same problem. I just did "adb reboot recovery" once and it worked, and it boots to recovery from the phone now every time.
blackplague1347 said:
I just unlocked my bootloader (via the toolkit) and then proceeded to install TWRP 2.5 (manually, via fastboot).
The next goal is to root the phone, but I cannot find a way to boot to recovery. I've tried using adb and I've tried it by using the volume keys and power/lock button while in bootloader mode.
The white HTC splash screen comes up with the red warning text at the bottom (the message that comes up when you're booting into a custom recovery -- I forget what it says offhand: something about a build being for development purposes or something). This splash screen is on the screen for maybe half a second before disappearing. After this happens, the normal HTC splash screen (same thing without the red text) pops up and the phone proceeds to boot normally.
This is my second One and the second time I've attempted this. The first time I had no issues, so I'm not sure what I'm doing wrong.
I've tried re-downloading/re-installing TWRP and I've tried fastboot erase cache (which I didn't know about until having searched for a fix). No error messages popped up at any point during the flashing process, so I'm quite confused.
Has anyone else had this happen and if so, how did you fix it?
Click to expand...
Click to collapse
im still having the same problem after allot of tries is there some sort of fix ?
Fastboot Tampered?
im still having the same problem after allot of tries is there some sort of fix ?
Click to expand...
Click to collapse
At the top of your devices when at the fastboot screen does it say Tampered?
Corey.C said:
At the top of your devices when at the fastboot screen does it say Tampered?
Click to expand...
Click to collapse
Yes mine says that. I am a new to this, what do i need to do
Hi all,
This is my sons phone which he doesn't use as phone - just for games.
Last night he dropped it and it froze, after removing battery it started powering and boot-looping on white htc logo screen.
I powered it with vol down and went on boot-loader and I thought I just restore it via recovery to a state I made him few months back, but failed to go to recovery, again on white screen loop.
I tried installing shipped ruu and after few fails I did it, but again restarts on white screen.
I can connect it to pc and all, running fastboot commands usualy comes with "remote not allowed"
I was sure that I did unlock bootloader for this phone but it says locked, so I am not sure ( having 4 htc phones in same house hard to know what I did to which )
This phone prior to drop had:
4EXT_Recovery_Touch_v1.0.0.5_RC7
S-OFF
not sure on unlocked bootloader
and
Cool-ICS-v17-EvoC
any ideas appreciated
Thank you
PS
I tried to go to htc page and unlock boot-loader, but numbers i paste are not recognized ( I did this many times so its not my error in copy paste)
I guess I cant edit my post.
I managed to unlock bootloader
I installed "Cool-ICS-v17-EvoC" rom via sd card as PG86IMG.zip as I can't load into recovery
and it reboots on white htc logo again
help
Wow... If the issue occurred after a drop, I'd worry it's a hardware issue.
As far as not being able to access recovery, either go into the power settings and uncheck fastboot, or do a battery pull and then access the bootloader with volume down +power and then select recovery.
Brian706 said:
Wow... If the issue occurred after a drop, I'd worry it's a hardware issue.
As far as not being able to access recovery, either go into the power settings and uncheck fastboot, or do a battery pull and then access the bootloader with volume down +power and then select recovery.
Click to expand...
Click to collapse
I can get to bootloader and try to switch to recovery, but phone never gets there as it has to reboot into it and once it gets to white screen it loops.
I thought rom got corrupted and tried to restore it, but you are right, it might be a hardware.
I found a motherboard for $18 on ebay but I am not sure will it fix the issue.
cipher101 said:
I can get to bootloader and try to switch to recovery, but phone never gets there as it has to reboot into it and once it gets to white screen it loops.
I thought rom got corrupted and tried to restore it, but you are right, it might be a hardware.
I found a motherboard for $18 on ebay but I am not sure will it fix the issue.
Click to expand...
Click to collapse
Apologies, I went and re-read the op and now I see that.
I think you are having trouble with the fastboot commands because of the locked bootloader like you said. You could also use the juopunutbear patched hboot since you are s-off, it will give you access to the extra fastboot commands regardless of locked/unlocked state. It can be flashed as a PG86IMG.zip via the bootloader.
If you use the patched hboot you could attempt to boot recovery into memory by using fastboot boot recovery.img
Because you are s-off, you can also flash a recovery via the bootloader as a PG86IMG.zip. If you want to try, here is 4ext recovery:
https://www.dropbox.com/s/t6q8wi58xzidgan/4ext_1.0.0.5.rc9_PG86IMG.zip
Obviously just Rename the file and remove everything prior to PG86IMG.zip.
I have a feeling though that since you successfully ran the ruu and it still won't boot, that no amount of software changes will fix the issue. I'm not sure if the motherboard will fix the issue or not buy that's a pretty cheap fix to try
Thanks for help and advice man,
I bought him a working used evo 3d from ebay, it was under $30 so I'll keep this one for parts I guess.
Thanks again