Another Firmware update issue. - One (M9) Q&A, Help & Troubleshooting

Hey all,
Noobie question time! Did the firmware update (or so I think) and now I do have adb connection but not fastboot? or mounted sd card. (Did re-format and now it seems to be available). I messed something up along the way obviously, it looked very much finished after both adb and the phone were inactive for a minute or so.
Currently in what seems to be factory recovery?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
^^^ Not working?
Android Recovery
HTC?htc_himauhl/htc_himauhl
6.0/MRA58K/buildteam12161528
(up and down for opions)
rbt sys
rbt boot
apply from adb
apply from sd
wipe/factory reset
wipe cache
Also access to everything else works.
What's next guys? I need twp and Venom update. *** Sideload option available didn't want twrp, because of not having fastboot?
Also showing:FILE/mnt/media_rw/ext_sd/0PJAIMG.zip
File not found.
Thanks for all the help, I'd be useless with out you!

I found out that:
1. Android sdk must be installed.
2. Htc sync must be uninstalled but keep its drivers. (install then uninstall it, keep drivers option!).
3. Use twrp 2.9.0.1 (reboot recovery will not appear until you use this twrp) and supersu 2.65.
4. Do not sideload. Use Fastboot and adb. No matter what!.
Download mode is Fastboot commands. Recovery is adb commands.
When you get to the reboot to recovery bit, boot to bootloader with hold vol+& press power. "reboot recovery" should be halfway down the list in bright lime green font. Read carefully. I missed it first time and panicked.
Sent from my HTC One M9 using Tapatalk

shivadow said:
I found out that:
1. Android sdk must be installed.
2. Htc sync must be uninstalled but keep its drivers. (install then uninstall it, keep drivers option!).
3. Use twrp 2.9.0.1 (reboot recovery will not appear until you use this twrp) and supersu 2.65.
4. Do not sideload. Use Fastboot and adb. No matter what!.
Download mode is Fastboot commands. Recovery is adb commands.
When you get to the reboot to recovery bit, boot to bootloader with hold vol+& press power. "reboot recovery" should be halfway down the list in bright lime green font. Read carefully. I missed it first time and panicked.
Sent from my HTC One M9 using Tapatalk
Click to expand...
Click to collapse
Shivadow, do you have a link for that twrp I can't seem to find it.
Thanks for the info!

Update:
Got twrp 2.8 on. Won't take newer versions of venom, assuming they need 3.0.
I noticed that the error on the bottom of the device - 0PJAIMG.zip file not found on sd path is RUU related? If so should I try the ruu again as I might have a partial install??

0pjaimg is for flashing but in your case it'll do more damage than good.
You can get twrp 2.9.0.1 from the repo or various sites. Google is your friend.
Sent from my HTC One M9 using Tapatalk

Related

[Q] Bricked my Desire Z.... I think (screenshots inside)

I rooted and did s-off and installed a custom ROM about a year and a half ago when I first got my phone.
Last night I obviously missed a step when I tried to update my ROM to Cyanogenmod.
Stuck in Hboot loop. My phone is recognizable in adb when it's stuck at the white HTC screen. I can power into fastboot but the volume buttons don't work so I can't access any of those options.
When I type "adb devices: it says: HT0AMRV07945
When I type "fastboot devices" nothing is found
Here are some screenshots:
No buttons work on this screen so I have to go into Hboot:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I mistakenly hit up instead of down and said yes to updating:
This is the only screen where my volume and power buttons still work.
Looks like the prob is that you have 2 update.zip's find the duplicate and rename reflash rom after wiping to ensure a good flash. That should work I had same prob.
Sent from my HTC Vision using XDA
I can find the duplicate by removing the card from my phone and inserting it into my PC. After that I don't know how to wipe the phone and load a ROM from the hboot screen.
Or are you saying it should boot normally after I rename the duplicate update.zip?
Hmm... is there anything named PC10IMG.zip on your sd card?
Go into recovery
1) Remove all ZIP files from your SD card (only the files that are NOT contained in any folder). So your phone will not try to install anything when in HBOOT.
2) When adb is working you can boot into recovery using the following command:
adb reboot recovery
3) From recovery you can do:
Wipe cache partition
Install a new ROM
Install a new radio
4) While in the white HTC screen you can get some log messages from the phone using adb. Some examples:
adb logcat : Shows logcat information (phone log)
adb logcat *:V : Shows verbose logcat info
adb shell dmesg : Shows kernel messages
adb shell ps : Shows all running processes of your phone
5) When still stuck you can write me a private message at XDA
Best regards,
Catherall

Desire Z/G2: Boot into Fastboot with adb/debug deactivated | Dead Screen | Clockwork

Hello devs,
my HTC Desire Z broke over night.
The phone still works, boots and runs as expected, but the Screen is dead, although the Touchscreen is still working (PatternUnlock working and so on).
I want to send it in for warranty repair, but I still have flashed Clockwork Recovery with S-OFFand Cyanogen 9 RC1 and root.
That's the reason why I want to flash the original image PC10IMG via fastboot.
How can I access the bootloader and boot into fastboot?
I tried:
Volume Down and waiting long enough (~45s) and then pressed Power to access Fastboot, but it doesn't work.
(I think the clockwork menu is presented instead of the android bootloader menu, which I don't know by minds).
Debug mode is off on the phone, so "adb reboot fastboot" does not work
Can someone with a Desire Z and Clockwork Recovery flashed give an step-by-step instruction how to boot into fastboot if your screen is dead?
Thank you in advance.
me|kor
Here you go, perfect guide for you: [GUIDE] Returning to stock, unroot. Also with broken screen/digitizer
-Nipqer
Nipqer said:
Here you go, perfect guide for you: [GUIDE] Returning to stock, unroot. Also with broken screen/digitizer
-Nipqer
Click to expand...
Click to collapse
That's what I tried already, but sadly it doesn't work due to Clockwork Recovery I think.
My device reboots when I press power after one minute, which makes sense if this screenshot represents my menu.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
In the ClockworkMod in this screenshot is fastboot not listed and I couldn't find a screenshot of the advanced menu nor the complete menu structure where fastboot was listed.
I'm using the most recent version of Clockwork Rom Manager and Recovery Image
Should be 5.0.2.7 I think.
You don't need to use recovery at all with my guide.
You can go straight to fastboot mode, from powered down, by holding the Trackpad while powering on, then you can use your computer to talk to it and send a rom to flash.
-Nipqer
Nipqer said:
You don't need to use recovery at all with my guide.
You can go straight to fastboot mode, from powered down, by holding the Trackpad while powering on, then you can use your computer to talk to it and send a rom to flash.
-Nipqer
Click to expand...
Click to collapse
Thank you very much I didn't knew the Trackpad shortcut and didn't find / oversee it in your guide.
That was the one I needed.
You made my day!
:fingers-crossed:
Yeah I don't think I mentioned it in my guide, as the guide is also written for Ace/Glacier, which don't have trackpads.
I'm glad you managed to get it sorted
-Nipqer

[FIXED] adb sideload "timed out waiting for package"

Hi guys, i'm new in this forum, so please pardon me if i did something wrong.
i really need a help now, my asus zenfone 2 (ZE551ML) got bricked Yesterday.
this is the timeline why my zenfone 2 got bircked:
1. I rooted my phone without cwm or anything else on around 2 weeks ago
2. Yesterday, i recieved the firmware update message (auto download) and i accidentaly clicked on update now without unrooting first.
3. My phone stuck on the logo screen, loading forever (softbrick?)
4. i've tried to factory reset and wipe all the system cache via recovery mode, but it didn't wok.
5. i looked at some forum and youtube said that i can flash rom my device to unbrick my device with 2 ways : via adb and microsd.
6. using adb sound promising, so i learnt how to flash rom via adb and i downloaded the latest firmware on the official website.
7. i tried to flash rom via adb: i've put the firmware zip on adb folder and open windows command in that folder, i connected my zenfone 2 with usb and start to "apply update from adb" and type "adb sideload xxxx.zip".
8. several times later i got message: "timed out waiting for package, installation aborted".
9. i repeated step 7 and 8 for almost 5 times and the results are same
Can someone help me? I'm really frustated now cause i can't using my phone or maybe share the reference about flash rom with microsd, because i've tried it but i don't really understand how to do it
Thx. in advance for all of you
nb: i've tried to search in this forum, but i didn't find correct answer for me
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
FIXED!!!
FINALLY I FOUND HOW TO FIX IT IN THIS SITE http://www.asus.com/zentalk/forum.php?mod=viewthread&tid=39487 THE PROBLEM IS PERSIST WITH MINE AND FINALLY I DIDN'T NEED TO STPCK RECOVERY! THX FOR THE REPLIES GUYS
since you know how to go into recovery mode so i'll skip that part,
use this adb tool instead https://www.androidfilehost.com/?fid=95784891001607611
If you have an external sdcard take it out and copy the firmware you want to side load and copy it to the external sdcard. Now name it "MOFD_SDUPDATE.zip" and reboot to fastboot and choose recovery. It should automatically flash the firmware. Move it to a folder when you are done or it will install automatically every time you reboot to recovery.
bar4 said:
since you know how to go into recovery mode so i'll skip that part,
use this adb tool instead https://www.androidfilehost.com/?fid=95784891001607611
Click to expand...
Click to collapse
Thx for your reply! My device has been fixed already
mremghz said:
If you have an external sdcard take it out and copy the firmware you want to side load and copy it to the external sdcard. Now name it "MOFD_SDUPDATE.zip" and reboot to fastboot and choose recovery. It should automatically flash the firmware. Move it to a folder when you are done or it will install automatically every time you reboot to recovery.
Click to expand...
Click to collapse
Thx for your reply! My device has been fixed already
great thanks

Black screen - Bricked

Ok, so this is how it went.
I uninstalled Magisk 18.1 via TWRP using the latest uninstaller zip. Unfortunately, my phone would not boot any more. Not in to the the system, not into recovery.
So I went to fastboot and tried to boot the TWRP image (fastboot boot twrp-3.2.3-0-daisy_zero.img). It loaded TWRP and then in the TWRP recovery, because it was set to boot at slot B, I changed it in TWRP to boot into slot A. After I restarted the phone, there is only the black screen. I can't reset the phone, I can't get in to fastboot, nothing. Basically it is bricked. It won't even show that it is charging.
Can anything be done? I have broken my system before, but always had no problems with restoring it with flashing threw fastboot. But now I can't get to fastboot.
I was using stock rom with Pie v 1.0.4.0.
Really appreciate the help.
zk_eu said:
Ok, so this is how it went.
I uninstalled Magisk 18.1 via TWRP using the latest uninstaller zip. Unfortunately, my phone would not boot any more. Not in to the the system, not into recovery.
So I went to fastboot and tried to boot the TWRP image (fastboot boot twrp-3.2.3-0-daisy_zero.img). It loaded TWRP and then in the TWRP recovery, because it was set to boot at slot B, I changed it in TWRP to boot into slot A. After I restarted the phone, there is only the black screen. I can't reset the phone, I can't get in to fastboot, nothing. Basically it is bricked. It won't even show that it is charging.
Can anything be done? I have broken my system before, but always had no problems with restoring it with flashing threw fastboot. But now I can't get to fastboot.
I was using stock rom with Pie v 1.0.4.0.
Really appreciate the help.
Click to expand...
Click to collapse
That´s really strange... Will windows detect the phone when you connect it?
Maybe you´re in edl-mode. If yes, you could get out of it by pressing pwr for more then 10 seconds.
If that doesn´t help and you will not be alble to do anything (incl. going to fastboot) you can restore you phone by going to edl by usng the test point method. But thant will break your warranty - you have to open the phone...
If you want to do it you need to do the following.
1. Download latest fastboot rom and MiFlash
2. Install MiFlash, unpack fastboot rom and selct extracted folder in MIFlash.
3. Open your phone: https://www.youtube.com/watch?v=PmpHdqRUlDA
4. Remove the metal cover over the mainboard
5. Remove battery
6. short these both pins: https://www.youtube.com/watch?v=mhsRv42rsqI
7. connect your phone to pc (in device manager you should see "qualcomm qdloader 9008"
8. In MiFlash click on refresh (now you should see something with com-port)
9. On the lower right corner you can selct "clean all", "save user data" and "clean all and lock" - if you were on 10.0.3.0 before, you can select "save user data" if not, you have to wipe by selecting "clean all". Now click "flash"
I did this once and needed a few tries... It´s a bit tricky to connect both pins and then the phone to pc - after the 4th try I got it running.
I had the problem of locked bootloader and a not booting phone...
Hi!
Yes, Windows detects the device. I can see the phone in the device manager by the name Qualcomm HS-USB diagnostics 900E (COM10).
If I hold power on and volume up or down, I can hear via Windows sound that it gets reconnected. So there is some life still in it.
The device is also detectable by MiFlash tool. But unfortunately since I can't get into Fastboot, I can't flash it. I've been trying to flash it, but this is where I get (it just stays here no matter how long I leave the device):
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I know about the method you posted. I still have a year and a half warranty on the phone. So I will sent it on repair and see what they will say. Maybe the won't notice and I will be able to keep my warranty.
i am in the same situation right now, after try to update the twrp, what tool you use to open the phone?.
I think you can also use the deepflashcable for the same effect.

Flashed corrupted boot image and now can't can't boot into bootloader or recovery

Hi all.
Did a stupid thing.
I downloaded firmware file for my Galaxy S20 Ultra 5G (SM-G988B) Exynos as an MD5 file and extracted the file which came out as a .img file instead of .lz4 (which I overlooked until the damage was done!).
So not noticing the file was the wrong type, I used 7-Zip to tar it, copied it to my phone's SD card, then patched it with latest Magisk manager app. After this, I copied it back to my laptop and flashed this file using Odin.
Result: Phone goes to insecure boot warning screen but of course here it goes wrong:
It won't proceed to booting up
Power+volume up key combination or power alone do nothing no matter how long you hold them in
It boots to to same insecure boot warning screen if you use either power+volume down, or power+volume down+volume up key combination with cable unplugged. With cable plugged in it restarts to a charging icon, which promptly freezes, and stays on the screen even if you unplug the cable.
I have managed to get it into stock recovery by holding power+volume up+volume down randomly once in a while (usually it goes to insecure boot warning screen as usual), but if I select Reboot to bootloader, it does not manage to open download mode, and hangs on red text that says "entering fastboot mode"
QUESTION: If I can get it back into recovery, is there a way to re-flash stock firmware without download mode on this device using ADB (or any other method)?
Or is my phone a brick for good?
FIXED!
I managed to flash an Android 11 One UI 3.0 Beta via ADB sideload. While it didn't finish properly due to corrupted boot image and possibly not the prerequisite firmware, all was not lost. It ran okay right to the end, when it said "installation aborted".
Once I had got this far Download mode was working again, THANK HEAVENS!
Opened Odin, and flashed away. I'm now back on Stock firmware and didn't even lose my data thanks to the vbmeta_disabled file I flashed in USERDATA section.
Talk about getting out of Jail!
jesterpaul said:
FIXED!
I managed to flash an Android 11 One UI 3.0 Beta via ADB sideload. While it didn't finish properly due to corrupted boot image and possibly not the prerequisite firmware, all was not lost. It ran okay right to the end, when it said "installation aborted".
Once I had got this far Download mode was working again, THANK HEAVENS!
Opened Odin, and flashed away. I'm now back on Stock firmware and didn't even lose my data thanks to the vbmeta_disabled file I flashed in USERDATA section.
Talk about getting out of Jail!
Click to expand...
Click to collapse
will that method work on my note10+?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

Categories

Resources