Hello,
After applying the latest OTA 2.29.405.2 I am unable to boot my phone.
The new firmware was successfully applied, because I could start the phone for the first time.
After I shut it down again it won't got past the HTC logo.
I can get start the hboot but I if i select fastboot or recovery I get stuck again with the HTC logo.
When i select the bootloader "I get no image or wrong image."
I did not root my phone.
Please help.
For a start, unless you have a PB99IMG.zip file on your sd card you will always get that message in the bootloader. It's just telling you it can't find any of the files it looks for on your card so nothing wrong there.
First thing I'd do is try manually reflashing the OTA update. you can get the OTA ZIP file here:
http://fotadl.htc.com/OTA_Bravo_Froyo_HTC_WWE_2.29.405.2-2.10.405.2_R_P_release8gn61bgo3rswcw24.zip
Rename it update.zip and put it on the root of your SD card. Then boot into recovery (if you manage to) and flash it.
If not, go into Fastboot and clear storage (wipe). This should sort you out. If not, download the 2.29.405.2 RUU from my signature and flash that in fastboot and it should see you right if you're still having issues
Did not work unfortunately. I will try to flash it. Any easy to follow tutorial I can use ? I never did this before.
Thank you kindly.
psycho.ro said:
Did not work unfortunately. I will try to flash it. Any easy to follow tutorial I can use ? I never did this before.
Thank you kindly.
Click to expand...
Click to collapse
What didn't work? What I put on my previous post is exactly what you need to do
I downloaded the file and renamed it ot update.zip and copied it to the root of my sdcard. when i select recovery it gets stuck in htc logo.
Then I've cleared storage/user settings and tried again, same thing.
So now do the last thing I suggested
this happened to me also. i downloaded the RUU and just did it via the pc. lost everything i did not backup, but that's my fault. all contacts were on google and and i used appbrain to pull down all my installed apps.
ok, i finally did it and it's fine now. I figured out what i was doing wrong. flashed it and it started now.
thanks for the support, really appreaciate it !
For reference, what were you doing wrong?
i did not go in the fastboot menu when i tried the last thing you suggested and because of this, my phone was not recognized by windows and the flash utility could not do its job.
but now it seems that my phone is restarting from time to time, somewhere between 5-10 minutes.
Might wanna do a hard reset just to make sure things flashed correctly
Related
I can get in to the HBOOT menu, but anything I do after that just contentious reboot loop.
I have tried many different solutions, but no go =(
HBOOT menu .79.
Any advice, thanks.
Since you didn't mention it.
Try pulling the battery? Then try booting into recovery..
kf2mq said:
Since you didn't mention it.
Try pulling the battery? Then try booting into recovery..
Click to expand...
Click to collapse
Thanks for the help, I stated in the title i cant into recovery mode, when i select it from the hboot menu phone resets and goes into boot loop.
I flashed pc36img but no go.
The only way I can seem to connect to pc, is via HBOOT USB.
Don't wanna go back to the TP2 =(
if you can get to hboot, you should be able to run one of the ruu's to bring the phone back, as well as there are several articles on fixing boot loops. Try searching through the forums, almost no loop is permanent, just need to find a fix that works for you
Can you access your sdcard? If so, find a download link to the "Part-two_evo-root_Amon_RA" file (should be in the "root 2.2 instructions thread". Extract the file onto your desktop and drag the files from it onto your sd card (leave all the contents in their zipped format). Select yes to the overwrite. Go into Hboot, and install the pc36img file from your zd card. Select no to reboot, go into recovery (pull the battery if it goes back to hboot, if it still doesnt work download the Evo Recovery files, pm me if you need a link). In Amon's recovery menu select install zip from sd, select the 2.2 root file, and let it install the file, then reboot.
i am having similar issues with my evo. it won't recover just get ! i'm not really sure what i did wront, i know i downloaded the laster update into my rooted evo and it alll went downhill from there. i extacted the update into the phone and now i can't get out of the loop. i can get my computer to regognize the phone, but i can't access the sdcard. truthfullt i had no business doing this, since i don't have much experience rooting or anything. if anyone could help that would be great. thanks
srivera145 said:
i am having similar issues with my evo. it won't recover just get ! i'm not really sure what i did wront, i know i downloaded the laster update into my rooted evo and it alll went downhill from there. i extacted the update into the phone and now i can't get out of the loop. i can get my computer to regognize the phone, but i can't access the sdcard. truthfullt i had no business doing this, since i don't have much experience rooting or anything. if anyone could help that would be great. thanks
Click to expand...
Click to collapse
Can you get into hboot? Recovery?
Sent from my Evo CM6
kf2mq said:
Since you didn't mention it.
Try pulling the battery? Then try booting into recovery..
Click to expand...
Click to collapse
Hello, i have a rooted evo running 2.2 i flashed a new rom called fresh with worked great with not problems at all, then i flashed a new theme called manup456 wich also worked flawlessly, i then tried another theme called riptide which looked like it overlapped the manup456 and looked kind of neat. but i tried to go back to just the manup456 and my phone just keeps trying to reboot (HTC quietly brillian) over and over again. can't get into hboot. Did I brick my phone? Please help!
Thanks in advance
Hello folks,
First of all can I say what a great site this is and how many super and generous people there are who help out twits like me every day!
I have rooted and flashed my phone many, many times, so I am not a Noob as such, though I am stuck on this one....
Here's my issue......
Got phone back from HTC repair - New motherboard - Worked fine.
HBOOT 0.93
I rooted phone using Unrevoked version 3
Then I installed LeeDroid 2.2d - latest version from XDA developers.
Phone worked fine for a few days.
I downloaded a few apps and synced calendars etc.
Then this morning - I unplugged my charger from the phone and Bang.....Phone seems to be not working, my Calendars are blank, so I decided to reboot phone.....................
Now I am unable to get past the HTC White Logo screen. AND I cannot access Recovery mode or Clockworkmod.
Though I can get to the Hboot screen by holding the down key and power.
Cannot boot into recovery though even from this menu.
The initial Recovery bit - the green writing that pops up when the phone looks at the recovery image, seems to be saying something like wrong image - Below.
SD Checking...
Loading...[PB99DIAG.zip]
No Image!
Loading...[PB99DIAG.nhh]
No Image or Wrong Image!
Loading...[PB99IMG.zip]
No Image!
Loading...[PB99IMG.nhh]
No Image or Wrong Image!
I have rebooted several times, but no good.
I have plugged my Desire in to PC and gone into Fastboot mode and then tried to install the Stock HTC RUU by running the exe from my computer.
RUU_Bravo_HTC_WWE_1.21.405.2_Radio_32.36.00.28U_4. 06.00.02_2_release_126984_signed
However I just get either error 131 or Error 140 depending on which SD card I put into the phone..........
This has got me completely stumped? Am I bricked completely or is there a way around this?
Any ideas?
HELP!!!!!!!! - I thought I was good at this!
Download a PB99IMG.zip from www.shipped-roms.com
put it into the root of your sdcard and it should reflash without a problem.
Well i don't know why both your recovery and system has got corrupted without you doing a thing to it. It usually only happens if you messed something up.. Not saying you have, but now would be the time to tell
Otherwise everything you say is exactly what i would expect your phone to do.
First of all the green writing in hboot is not a look at the recovery but a check to see, if you have put a zip file with that name on the sd-card. This is just an alternative to using the ruu.exe
Second of all the stock rom you try to flash may contain an older hboot version og something similar, which is just giving you the error because you are not allowed to downgrade to an earlier software/hboot version. Try the newest one instead with your goldcard in the phone of cause.
And finally no you are not even close to a brick here seriously some people should take a deep breath and read through the forum(not specifically you but people in general. There is just too many topics with people screaming heeelp i have no idea what i did to my phone). Theres plenty of solutions, and it is quite hard to actually brick the phone. Unless you actually tried pulling the battery while flashing a hboot or radio update almost any other software problems are easily solved, because of the way this system is build.
edit: and if you try the above suggested by h3llb3nd4. You should be aware that your phone model on that page is bravo and not desire, which is the cdma desire. So if your phone has a sim card you should pick bravo. You still have to choose one with a similar or newer software and hboot version than your current.
Hi guys,
The latest with the saga is.
I managed to get the latest Froyo RUU to run and install successfully on my phone.
However - Phone still will not get past the HTC white screen, it just sticks there.
I am pretty much out of ideas now?
h3llb3nd4, thank you for your advice, I will give this a go, but as I cannot access any menu's to do a reflash I'm not sure I understand how this can help me? - Not that I'm saying it won't, it's probably my lack of knowledge.
Otherwise, I have to say this phone seems to be a big trouble. I mean even a successful RUU install and still no reboot? Weird
Thanks so much for your help and advice...keep those ideas coming
Rich
h3llb3nd4 said:
Download a PB99IMG.zip from
put it into the root of your sdcard and it should reflash without a problem.
Click to expand...
Click to collapse
Well I tried this, and placed the zip file onto the root of SDCard. However then I restarted phone and it simply stuck at the HTC screen as before?
Do I need to do anything else? - I cannot access recovery to install from zip card.
Do I need to unzip the zip file? or maybe rename it?
Also I am now installed with the latest froyo Bravo RUU Rom 2.10, so the image file that is for 1.21 may not be right for this?
Help........
Put PB99IMG.zip on to the root of your SD card. Then boot into the bootloader (power on with vol down held down).
The bootloader will automatically scan the SD card root for an update file and install it. That should get your back to running stock again.
bigstoo said:
Put PB99IMG.zip on to the root of your SD card. Then boot into the bootloader (power on with vol down held down).
The bootloader will automatically scan the SD card root for an update file and install it. That should get your back to running stock again.
Click to expand...
Click to collapse
Hi Bigstoo,
Sooo close, it actually started reading the PB99IMG.Zip file. However it failed to update sadly.
The error message was "update fail"
Could this be that the ROM image that is on the phone is a higher one than this PB99IMG file? Is there one that is suitable for use with
RUU_Bravo_Froyo_HTC_WWE_2.10.405.2_R_Radio_32.44.00.32U_5.09.05.30_2_release_142828_signed
Thanks though! - Nearly there maybe..............
Ramphis29 said:
Hi Bigstoo,
Sooo close, it actually started reading the PB99IMG.Zip file. However it failed to update sadly.
The error message was "update fail"
Could this be that the ROM image that is on the phone is a higher one than this PB99IMG file? Is there one that is suitable for use with
RUU_Bravo_Froyo_HTC_WWE_2.10.405.2_R_Radio_32.44.00.32U_5.09.05.30_2_release_142828_signed
Thanks though! - Nearly there maybe..............
Click to expand...
Click to collapse
Right I have found the correct PB99IMG file for my current stock Rom.
The phone found it in Bootlaoder and went right through the installation process correctly and successfully......................
Outcome - Phone still not working at stuck at the HTC White screen.
I would say it's now looking like hardware issue to me? I cannot think of anything else that might get this bloody phone to work again...............
Sheeeesh
Hi,
My first phone was rooted and I rooted my second too so I am confident rooting them however my second phone which had been rooted for a while had a space issue on SD card so I cleared out a few things which unfourtunatley included all the backup files ....
It worked fine afterwards but didnt let me change rom (using rom manager) so I just left it in working order for a few months until I wanted to reflash a new rom (as I am sure most people do every few months)
When it didnt let me, I tried to unroot and root options using superoneclick and unrevoked3 however, unrevoked 3 just stayed on "running root" and superoneclick got so far and crashed. When I go into the bootloader, it says something about some filed missing (think might be some nbh files).
At the moment, when normally turning the phone on, it stays on the screen with the pink circle, the first boot screen.
I have tried updating it using the RUU but it takes a long time and then says "use the correct rom for your device" which I am, this method just boots my phone and goes to a htc logo.
I can also get into the bootloader but when I apply update.zip, it says it has failed and something about files not existing/step 7 failure.
The thing is, I can get to fast boot and I am sure there is a way via ADB to force a new image (such as a cyanogen recovery image) on to the device.
Can anyone tell me how to push an image to the phone without using the RUU (as this didnt work for me)??
Maybe my phone is just bricked
Thank you very much!!
It. Is. Not. Bricked.
You can only push files onto the phone through fastboot if you are S-OFF (are you?)
Have you tried to enter recovery? boot into Bootloader (vol down + power) and then select recovery. Does it work?
no?
Then you need a goldcard. Make one with your working Desire, stick it in your misbehaving one, and then run the latest WWE RUU (link on my guide, check #resources)
Thanks but I do not have another Desire...
Any card reader
yeah, I got a card reader laying around somewhere, if not ill go get one in Tesco, what where you thinking?
bortak said:
It. Is. Not. Bricked.
You can only push files onto the phone through fastboot if you are S-OFF (are you?)
Have you tried to enter recovery? boot into Bootloader (vol down + power) and then select recovery. Does it work?
no?
Then you need a goldcard. Make one with your working Desire, stick it in your misbehaving one, and then run the latest WWE RUU (link on my guide, check #resources)
Click to expand...
Click to collapse
Hi Bortak, I am having similair problems with my phone sticking on the pink circle screen. I cant seem to load a recovery file from Bootloader. Will I need to make a Gold Card, my phone is s-off.
thanks mate
if phone is S-OFF go to my guide, look at advanced boot problems S-OFF.
SOLVED WOOHOO!
Thank you to all who helped but I managed to fix it my own way.
For anyone still having trouble...
I still had the cyanogen mod bootloader soo all I did was download the latest cyanogen mod rom and apply it (you can mount sd card from cm bootloader) and after a hairy minute, it finally booted up!
Mugube said:
SOLVED WOOHOO!
Thank you to all who helped but I managed to fix it my own way.
For anyone still having trouble...
I still had the cyanogen mod bootloader soo all I did was download the latest cyanogen mod rom and apply it (you can mount sd card from cm bootloader) and after a hairy minute, it finally booted up!
Click to expand...
Click to collapse
#facepalm#
Translation: I flashed another ROM because my other one didn't boot.
Ok so here's the problem I'm having. I'm trying to take my phone back to stock so I can send it into verizon. The charging port is broken, so there's not RUU option. I've flashed gingerbread, and have gotten back to s-on. Now, I've been following the guide (stickied) and once I get to the PB31IMG.zip flash step it won't do anything. I can't get rid of Clockwork, and the superuser icon is still present on the phone. Whenever I try to flash the zip (I've downloaded from multiple sources) it gets to the "checking" part and then goes back to the hboot main screen. What am I doing wrong, and what can I do to fix it? I'm on a time limit because I need to send it away by tomorrow night. Thanks for all the help.
fiend2386 said:
Ok so here's the problem I'm having. I'm trying to take my phone back to stock so I can send it into verizon. The charging port is broken, so there's not RUU option. I've flashed gingerbread, and have gotten back to s-on. Now, I've been following the guide (stickied) and once I get to the PB31IMG.zip flash step it won't do anything. I can't get rid of Clockwork, and the superuser icon is still present on the phone. Whenever I try to flash the zip (I've downloaded from multiple sources) it gets to the "checking" part and then goes back to the hboot main screen. What am I doing wrong, and what can I do to fix it? I'm on a time limit because I need to send it away by tomorrow night. Thanks for all the help.
Click to expand...
Click to collapse
What hboot and gingerbread version are you on?
I'm on .92 hboot, and i think it's 2.3.4.... it's the 2.15......28 radio.
Ok first backup and format the sdcard fat32 with a pc. Then download this file http://dinc.does-it.net/Stock_Images/4.06.605.3/PB31IMG.zip, and place it on the sdcard in no folders. Then put the sd back in the phone and boot to hboot and see if it will find it. Sometimes if there are errors on the sdcard it wont process the file correctly, reformating it should fix this. If it flashes correctly go back to hboot and do a factory reset, this will ensure all data is gone.
cmlusco said:
Ok first backup and format the sdcard fat32 with a pc. Then download this file ioand place it on the sdcard in no folders. Then put the sd back in the phone and boot to hboot and see if it will find it. Sometimes if there are errors on the sdcard it wont process the file correctly, reformating it should fix this. If it flashes correctly go back to hboot and do a factory reset, this will ensure all data is gone.
Click to expand...
Click to collapse
Thanks a thousand percent! That link is what did it. I've tried numerous sources over the past few days and it never got past the "checking" stage. Everything is all sorted out now. Thanks again.
I accidentally allowed the 2.20.40.183 OTA update, which rendered my phone useless. I tried putting MOFD_UPDATE of 2.20.40.174 on my SD card, but that didn't work.
Here's a few other things I tried:
Recovery menu: Updating phone, then dead droid. No menu appears.
adb sideload: adb didn't recognize my phone.
fastboot flash: Permission denied, or something along those lines. The write fails. Tried to flash system.img but it never did and nothing happened.
adb sideload through temporary CWM: Unauthorized device. Couldn't sideload.
Flashing through temporary CWM and temporary TWRP: Fails early on with Status 7. 2.20.40.174 is older, and this is apparently reason enough to deny me.
Does anyone have an idea about what I can do to fix this? Could I flash Cyanogenmod, then flash stock over that, using temporary CWM/TWRP?
My bootloader is not unlocked.
PasserbyPassingBy said:
I accidentally allowed the 2.20.40.183 OTA update, which rendered my phone useless. I tried putting MOFD_UPDATE of 2.20.40.174 on my SD card, but that didn't work.
Here's a few other things I tried:
Recovery menu: Updating phone, then dead droid. No menu appears.
adb sideload: adb didn't recognize my phone.
fastboot flash: Permission denied, or something along those lines. The write fails. Tried to flash system.img but it never did and nothing happened.
adb sideload through temporary CWM: Unauthorized device. Couldn't sideload.
Flashing through temporary CWM and temporary TWRP: Fails early on with Status 7. 2.20.40.174 is older, and this is apparently reason enough to deny me.
Does anyone have an idea about what I can do to fix this? Could I flash Cyanogenmod, then flash stock over that, using temporary CWM/TWRP?
My bootloader is not unlocked.
Click to expand...
Click to collapse
I do the same! Now my phone stuck on boot screen.
Does anybody can help us?
http://forum.xda-developers.com/zenfone2/general/guide-brick-soft-hard-bricked-zenfone-2-t3284256
mr_gourav2000 said:
http://forum.xda-developers.com/zenfone2/general/guide-brick-soft-hard-bricked-zenfone-2-t3284256
Click to expand...
Click to collapse
I'm not going to lie, that guide's a bit hard to read. I'll try to follow as best as I can and reply if this works for me.
I'd still appreciate any other advice others have.
PasserbyPassingBy said:
I'm not going to lie, that guide's a bit hard to read. I'll try to follow as best as I can and reply if this works for me.
I'd still appreciate any other advice others have.
Click to expand...
Click to collapse
All necessary to read.
Hope you fix the problem.
Fixed
I managed to fix my phone, but not with the method Mr Gourav so kindly posted. I chose not to use mr_gourav2000's IntelSoC fix because the guide was written in a way that made it very hard to follow, and I was unsure if MOOREFIELD was supposed to flash briefly or stay on the Device Manager. Regardless, I wasn't going to risk bricking my phone beyond help by pushing on without knowing what i was doing.
The key was bypassing Status 7 (or 1), which prevents you from downgrading firmware. If your phone says something like "Installation failed with Status 1" or "Status 7," or you get the "Can't install this package over newer build" error when you attempt to flash a previous firmware, this fix can help you. Funny enough, the fix was posted by the very same person earlier this year:
http://forum.xda-developers.com/showpost.php?p=65995574&postcount=116
First, download the latest full firmware from Asus' support site: https://www.asus.com/Phone/ZenFone_2_ZE551ML/HelpDesk_Download/
Then, open or extract the .zip file, and go to into UL-Z00A-WW-(Firmware.Version.Number)-user.zip\META-INF\com\google\android\ . Select updater-script (no file extension), and open it in a plain text editor like Notepad++.
Remove lines 1-6, beginning with "(!less_than_int" and ending with "getprop("ro.product.device") + "\".");". The result should look like this.
Then, insert the edited updater-script into the .zip file, overwriting the old updater-script. At this point, I should mention that one of the removed lines probably checked your phone's model number to see if it was compatible with the firmware. I sure hope you downloaded the right file for your phone. If not, brick city here you come.
Finally, put the edited .zip into a microSD card, and insert that into your phone. If you want to use the stock recovery to install the firmware, rename the .zip to MOFD-UPDATE.zip and put it in the root of the SD, then restart the phone and let it update. Presumably. I didn't use the stock recovery. I used the temporary ClockworkMod recovery to fix my phone, so I'm not sure if it's that simple. If you're using that temporary CWM, just go to the zip installation menu and apply the zip from external_sd.
If you were going through the same problems I was, your phone should boot into stock, unrooted firmware again. Pat yourself on the back and never do whatever dumb thing you did to get to this point in the first place (like absentmindedly apply an OTA update in the middle of a lecture)!
Once again, thanks to mr_gourav2000 for posting this fix earlier. I may not have understood the IntelSoC fix, but I did understand this one!
.183 after update takes an extremelynlong time to boot after asus screen aa well. Made me think mynphone crashed, took a bout 10-15 minutes on first boot for me
Redtexan said:
.183 after update takes an extremelynlong time to boot after asus screen aa well. Made me think mynphone crashed, took a bout 10-15 minutes on first boot for me
Click to expand...
Click to collapse
If it's the 1st boot it generally will as it is recreating cache, dalvik-cache or ART...
It seems to take forever to clear cache too when using recovery but about a heartbeat when using fastboot.... Just another quirk of the phone...
Thank you much
I gotta say, this got me on the right path. Though my issue was exactly the same the fix was a little different.
I had to use the next patch and that worked. Recovery is working now and I have to manually update, but still have root, so no real big deal.
Thanks again.
mastet68 said:
I gotta say, this got me on the right path. Though my issue was exactly the same the fix was a little different.
I had to use the next patch and that worked. Recovery is working now and I have to manually update, but still have root, so no real big deal.
Thanks again.
Click to expand...
Click to collapse
You need to flash boot, droidboot and recovery for the build you are using.
I use fastboot to do this but make sure developer settings are enabled and USB debugging is ticked before trying to flash.
To find the img files for the above mentioned, go to Shakalaka's pre-rooted rom thread in Android Developement, you don't need to download the rom if you don't want to but it sure makes rooting easy.
Find the version of Android you need and download boot,droidboot and recovery img files. Flash with fastboot using these commands -
fastboot flash recovery recovery.img
fastboot flash boot boot.img
fastboot flash fastboot droidboot.img
***Make sure the right commands are used or it may result in a brick...***