Related
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
Hello everyone!
First of all, I would like to apologize, as these kind of issues have probably been talked about and solved a gazillion of times before, but the thing is, I'm having a hard time grasping the start and the end of this issue myself, as the phone that is stuck in a boot-loop isn't mine - it belongs to a friend of mine who somehow managed to get the whole thing bricked.
Anyhow, I'll start off with what I know;
His goal was to flash a new ROM (http://forum.xda-developers.com/showthread.php?t=1601543). He unlocked the bootloader and rooted the phone using these instructions; http://onexroot.com/one-x-root/how-to-root-one-x/). He succeeded in doing so and decided to move onto flashing the rom.
But the problems started when he read that he's first supposed to flash "Android Fastboot kit 2.1" onto the device, prior to flashing the device. And so he did. Or well, tried - what he told me was that he booted the phone into fastboot mode, then ran the "Install Boot.img" bat file inside the Fastboot Kit folder he downloaded and after that, the phone got bricked.
Now, my knowledge in this area isn't too great either, but I've flashed a few ROMs in my life before, so, I decided I'd do my best to help. But I have no clue on what steps he should take from here on.
To my understanding, he was running the official 1.29 version and he is still able to access the boot-loader as well as Clockwork Recovery mod. To my understanding, he didn't create a back-up of his previously working ROM and the phone won't show up in Windows Explorer while connected via USB either.
To my limited understanding, I should now try and install the rom onto his phone and once done, the whole thing should work - the only problem with that is the fact I can't get the ROM zip onto the SD Card right now, as explorer won't recognize it. So far, I tried using ADB to push the ROM file onto the phone, but every time I use the command "adb shell mount /sdcard" I get a "Device not foound" error. So, I'm kinda stuck here right now. If this even is the right way to solve the issue, that is.
So, like I said, I'm having a hard time grasping the start and the end of this issue myself, and if there is any additional information needed, I'll do my best to find out more about it - I do have the phone in my possession at the moment as well.
Thanks a lot to anyone who'll offer any kind of help!
Atraeh said:
Hello everyone!
First of all, I would like to apologize, as these kind of issues have probably been talked about and solved a gazillion of times before, but the thing is, I'm having a hard time grasping the start and the end of this issue myself, as the phone that is stuck in a boot-loop isn't mine - it belongs to a friend of mine who somehow managed to get the whole thing bricked.
Anyhow, I'll start off with what I know;
His goal was to flash a new ROM (http://forum.xda-developers.com/showthread.php?t=1601543). He unlocked the bootloader and rooted the phone using these instructions; http://onexroot.com/one-x-root/how-to-root-one-x/). He succeeded in doing so and decided to move onto flashing the rom.
But the problems started when he read that he's first supposed to flash "Android Fastboot kit 2.1" onto the device, prior to flashing the device. And so he did. Or well, tried - what he told me was that he booted the phone into fastboot mode, then ran the "Install Boot.img" bat file inside the Fastboot Kit folder he downloaded and after that, the phone got bricked.
Now, my knowledge in this area isn't too great either, but I've flashed a few ROMs in my life before, so, I decided I'd do my best to help. But I have no clue on what steps he should take from here on.
To my understanding, he was running the official 1.29 version and he is still able to access the boot-loader as well as Clockwork Recovery mod. To my understanding, he didn't create a back-up of his previously working ROM and the phone won't show up in Windows Explorer while connected via USB either.
To my limited understanding, I should now try and install the rom onto his phone and once done, the whole thing should work - the only problem with that is the fact I can't get the ROM zip onto the SD Card right now, as explorer won't recognize it. So far, I tried using ADB to push the ROM file onto the phone, but every time I use the command "adb shell mount /sdcard" I get a "Device not foound" error. So, I'm kinda stuck here right now. If this even is the right way to solve the issue, that is.
So, like I said, I'm having a hard time grasping the start and the end of this issue myself, and if there is any additional information needed, I'll do my best to find out more about it - I do have the phone in my possession at the moment as well.
Thanks a lot to anyone who'll offer any kind of help!
Click to expand...
Click to collapse
The latest Clockwork jobby will allow you to mount the sdcard as USB drive.
Other than that, you seem to be on the right track.
^ he's right
What you want to do is first download the 5.8.4.0 version of the endeavoru CWM recovery.
reboot to your bootloader, make sure you're in fastboot and flash the new recovery img.
After you have successfully flashed the new recovery, well... go to the recovery
On the recovery, tap mounts and storage, then tap Mount USB. VOILA!!!!!
Yeah, I forgot to mention that I've already tried mounting the SD Card via Clockwork Recovery - I get an error saying "Unable to open ums lunfile (No such file or directory exists). So that doesn't seem to be an option either, unless you have an idea on how to counter this?
EDIT: Ah, I see - he's using an older version. I'll get the latest one on board and give it a go. Will have to wait a bit for the phone to charge up first it seems though. Not enough battery to do it right now .
Thanks!
And voila! The phone is operational.
Thanks a lot for the help and, I just hope I never manage to half-brick my own HOX .
Ok, this is my first post so forgive if this is in the wrong section...
I have a friend's Galaxy Note 2 ATT that was stuck on the Galaxy Note 2 Boot screen, and it wouldn't go any further.
Because I work for Samsung at the Samsung Experience Shop, I tried running it through our smart reflash tool
-----> This didn't work because it would fully download it onto the phone, but when it got to the Android with the thing spinning in its chest, it would stop and ALWAYS freeze halfway.
Next step I tried doing was going through Samsung Kies and downloading the stock OS and load that, but the same Android with the spinning thing in its chest would show up and it would freeze.
Due to this guy being my friend I told him I would try anything to get his phone to work again (root, to custom recovery, to custom rom)
My steps so far:
1. I have successfully rooted my device via ODIN 1.85 by using CF-Auto-Root
2. Afterwards, I loaded on a custom recovery via ODIN 1.85 which now is philz_touch_6.07.9
Here is my problem now, I've tried searching everywhere and I can't really find the answer...
Whenever I try to side load a rom through ADB through Android tools (its in the right directory and everything because it transfers over), I keep getting an error message "E: Error in /tmp/update.zip (status 7) Installation Aborted."
Now before I get that error I get stuff like getprop("ro.product.device")==t0lte" ||getprop("ro.build.product").... etc. and it goes on and on.
So far the ROMs that I have tried were Cyanogenmod 10.1 and the Pacman Rom, and yes, both are for the correct device like the model name/number match up. And now how I said I thought I rooted the device, whenever I try to reboot into recovery via Philztouch, it says at the top Root Access is missing. Root device, and I click yes. When it reboots into recovery and I want to turn the phone off again, it still says Root Access is missing.
I am open for anything really. My friend just wants his phone to work again. and I've literally exhausted all of my ideas as I keep running into the same issue.
What am I doing wrong? and is something like this possible to fix? Or is my friend SOL?
Thanks for all the help. It's much appreciated.
Your recovery is outdated. Status 7 error.
I use TWRP from the original development section.
rangercaptain said:
Your recovery is outdated. Status 7 error.
I use TWRP from the original development section.
Click to expand...
Click to collapse
+1 to this^^^^^
Look here»»» http://forum.xda-developers.com/showthread.php?t=1981198
And why not give him something stock instead of a CM Rom??[emoji37]
Plenty of stock 4.3 Rom's in the development section...
Sent from my SAMSUNG-SGH-I317 using Tapatalk
Good advice ^^^^ for your friend.
Ok, thanks for the direct response. I've downloaded the latest TWRP recovery and when I try to push it through ODIN, I still have PhilZ Touch 6..? Sorry, I feel like I'm skipping something simple...
according to a guide, I have to make sure when I'm pushing a custom recovery through ODIN I have to leave Auto Reboot and F. Reset Time UNCHECKED. I made sure they were, and for some reason after it says PASS and thread successful 1 failed 0. When I disconnect the phone and turn it back on into recovery mode, I still has PhilZ Touch...
Use your recovery to flash TWRP. There's a zip version and an odin version.
Ok, I got stock recovery on there just by redoing the CF-Auto Root package through ODIN.
I figured well I can apply the ROM the adb through the stock recovery...
It was going well until I got this error. The last line before the error stated:
"Veryfying update package..."
Error:
E: failed to verify whole-file signature
E: signature verification failed
is that due to the fact that i'm using stock recovery?
In the mean time since that didn't work I'm going to flash TWRP and hopefully that fixes the issue.
I'm kinda just documenting my steps here in case anyone wants to follow and chime in if i'm doing something wrong.
Thanks for the help guys!
************3AM EDIT*****************
Ok so I managed to get TWRP 2.7 on the device as I needed the ability to adb sideload the update.zip to the phone since I can't boot into the phone's OS whatsoever.
This is the error I'm receiving now:
Checking for MD5 file...
Skipping Md5 check: no MD5 file found.
then it restarts and I'm stuck at the Samsung GALAXY Note II screen... what's my next step..? Find a different ROM?
**********Another Edit**************
It has just come to me, I shouldn't have to adb sideload the update.zip or the custom rom... even though I can't get into the phones OS and can't copy and paste to the root of the device. Can't I just copy and paste it to a micro SD card and mount that, and then apply the update from there? And as far as those errors I had earlier, I'm still not sure why I received them...
Again, thanks for all the help
Adb won't work if USB debugging wasn't enabled.
In TWRP you can disable md5 checking.
And you don't unzip the zip file.
Thanks for the reply. ADB didn't work because, in fact, since I haven't been able to turn the phone on, I know USB debugging isn't turned on.
And as far as having the MD5 check, it is unchecked.
I received a success message. However, when I try to boot the phone it still gets stuck at the Samsung Galaxy Note II screen.
******Edit******
Ok ended up using a different ROM, I think PacMan rom? It seemed to work until it got to extracting system files and then the phone sits for a couple minutes, screen turns black. And when I try to wake the screen, only the back and menu buttons come up...
Another thing, even though I've already rooted my device using CF-Auto-Root, When I reboot my device with TWRP I go to reboot and then recovery. Then it warns me saying no OS bla bla bla, and then it says it notices that my phone isn't rooted? And that SuperSU isn't on the device. It asks to install it by swiping. I swipe it starts to install, phone reboots. When I reboot it again, it still tells me that the phone isn't rooted. And with the phone not being rooted, I'm coming to the conclusion why I'm having trouble trying to flash Roms.. Is this a possibility?
Why are you using ADB? just drop the .zip for the ROM you wish to flash onto a micro SD card, and flash from within the TWRP. Don't try to extract the .zip whatsoever.
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...***
i tried installing the lastest ota update while i had twrp installed, i have tried everything to get out of this loop.
tried flashing the updated rom off the oneplus website and if gave me errors
just looked at my phone and now it wont turn on what so every getting really stressed please help
[SOLVED]
went back to stock recovery and side loaded the full 1.4 gb rom i will leave a link for tutorial that i used, i wanted to get back to complete stock and this was the one use
"https://forums.oneplus.net/threads/guide-how-to-unroot-your-oneplus-3-and-go-back-completely-to-stock.456232/"
When you have TWRP you have to install full zip, not simply the eval OTA zip
bob_cheeseman5 said:
i tried installing the lastest ota update while i had twrp installed, i have tried everything to get out of this loop.
tried flashing the updated rom off the oneplus website and if gave me errors
just looked at my phone and now it wont turn on what so every getting really stressed please help
Click to expand...
Click to collapse
Flash the stock recovery.
Get stock recovery from downloads.oneplus.net
I cant seem to flash the stock recovery. The device is not visible in adb devices or fastboot devices. im facing the same issue.
If you are using TWRP 3.0.4-0 - try a hard boot...hold down the power button for 20s...wait 20s, power it back on.
bob_cheeseman5 said:
i tried installing the lastest ota update while i had twrp installed, i have tried everything to get out of this loop.
tried flashing the updated rom off the oneplus website and if gave me errors
just looked at my phone and now it wont turn on what so every getting really stressed please help
Click to expand...
Click to collapse
easy solution. Boot into fastboot
download this tool.
https://forum.xda-developers.com/oneplus-3/development/toolkit-oneplus-3-toolkit-unlock-t3398799
if newest version isnt working, download an older version with older twrp
than unzip the tool and run the .bat file and install twrp.
Thats it
There are many posts on Nougat not working with official TWRP (based on 6.0 build). Try booting into stock recovery. performing a system settings reset, then booting into fastboot and run the adb command, <fastboot boot TWRP-3.0.2-1.28.img>. From there you can do virtually anything you need to do. I recommend at least using a modified version of TWRP (such as 1.28). This has been posted many times before, please try and do a search for the answers first, it will help tremendously. Thanks
recovery
i had the same problem on my rooted OP3 when i used TWRP 3.0.2-1 , it worked to flash the full 4.0.1 rom but failed for everything else, flashing latest verion of twrp fixed it for me
Got the same problem (unrooted phone + device state locked, cannot access recover, but can access fastboot) with an added "benefit", USB debugging mode was off before it all went crashing and burning.
How to access my phone via PC? (all the guides I've found assume I had USB debugging mode on before the phone got soft-bricked, but as a normal phone user who never installed anything custom, I've never figured it is A MUST BE ON function).
Or simpler question - what tool to use to turn on the USB debugging mode? (if that is at all possible?)
Aislandas said:
Got the same problem (unrooted phone + device state locked, cannot access recover, but can access fastboot) with an added "benefit", USB debugging mode was off before it all went crashing and burning.
How to access my phone via PC? (all the guides I've found assume I had USB debugging mode on before the phone got soft-bricked, but as a normal phone user who never installed anything custom, I've never figured it is A MUST BE ON function).
Or simpler question - what tool to use to turn on the USB debugging mode? (if that is at all possible?)
Click to expand...
Click to collapse
I have tried doing the installing of the newer twrp but cant find a newer version of it, i am on 3.0.2-1. i have the same problem as you that my USB debugging isnt on i dont think so when trying to use the op3 tool kit i can get it to pick up fast boot but nothing else.
have you found a solution to your problem yet?
bob_cheeseman5 said:
I have tried doing the installing of the newer twrp but cant find a newer version of it, i am on 3.0.2-1. i have the same problem as you that my USB debugging isnt on i dont think so when trying to use the op3 tool kit i can get it to pick up fast boot but nothing else.
have you found a solution to your problem yet?
Click to expand...
Click to collapse
Noted that you solved your issue, but this post is about the new version of TWRP. Version 3.0.3 is available on twrp.me and it works with Nougat.
bob_cheeseman5 said:
I have tried doing the installing of the newer twrp but cant find a newer version of it, i am on 3.0.2-1. i have the same problem as you that my USB debugging isnt on i dont think so when trying to use the op3 tool kit i can get it to pick up fast boot but nothing else.
have you found a solution to your problem yet?
Click to expand...
Click to collapse
Gave up trying and booked a session with OP technicians Will see how it goes in a week.