Hi, I'm new here... After browsing all over Internet and trying for many hours, hope I can get some help here.
So I was brave yesterday and wanted to root my pixel 3 to install some new themes. Unlocked bootloader, but I screwed up with Magisk / TWRP and the phone could not boot any more. At that point, I was still able to see the phone in adb. Then I tried to flash the stock rom using flash-all, but the process failed at one file (vendor_a?).
Unfortunately, I decided to reboot the phone - and now I'm stuck because the phone will be deadlocked showing the Google screen, and my PC cannot recognize the phone any more. adb shows no device, and device manager doesn't see any Android device. I have the latest developer tools and also installed the latest Google USB driver (at least I think), but now when I plug the phone in, I do hear the new device sound, but it is only recognized as a general USB device.
I can't even turn off the phone. Long pressing power will only go back to restart the phone and the first screen shows "this device is corrupted". Go on to the second screen will only give me an option to pause, with nothing else to choose from. I can't reboot into TWRP or recovery.
Any thoughts? Thanks a lot...
edx2000 said:
Hi, I'm new here... After browsing all over Internet and trying for many hours, hope I can get some help here.
So I was brave yesterday and wanted to root my pixel 3 to install some new themes. Unlocked bootloader, but I screwed up with Magisk / TWRP and the phone could not boot any more. At that point, I was still able to see the phone in adb. Then I tried to flash the stock rom using flash-all, but the process failed at one file (vendor_a?).
Unfortunately, I decided to reboot the phone - and now I'm stuck because the phone will be deadlocked showing the Google screen, and my PC cannot recognize the phone any more. adb shows no device, and device manager doesn't see any Android device. I have the latest developer tools and also installed the latest Google USB driver (at least I think), but now when I plug the phone in, I do hear the new device sound, but it is only recognized as a general USB device.
I can't even turn off the phone. Long pressing power will only go back to restart the phone and the first screen shows "this device is corrupted". Go on to the second screen will only give me an option to pause, with nothing else to choose from. I can't reboot into TWRP or recovery.
Any thoughts? Thanks a lot...
Click to expand...
Click to collapse
First off, if you did successfully unlock your bootloader there is a 99% chance you will be able to recover from this. In fastboot mode is the phone state shown as "unlocked" ? Do you have a second PC or laptop to install the standalone adb/fastboot binaries on? adb does not work in fastboot mode, only in stock recovery mode. First re-try fastboot flashing the full image while in fastboot mode without modifying the flash-all.bat (allow it to wipe). You may also want to check the CRC (checksum) on the image you downloaded to verify it is not corrupt. If unlocked and that install fails capture the error and report back. Then try using adb from the stock recovery. You Tube how to get into recovery and use update via adb with a (different) full OTA image. The full OTA images are also available on the same Google dev site as the factory image, and is sometimes called a rescue OTA. You're in the right place to get help, but you need to provide all relevant information (such as previously installing a custom rom).
try holding power and vol down until the phone reboots and comes back to the menu where you should hopefully get back to Android Recovery mode where you should be able to use adb and the OTA via a sideload......for some strange reason I always get screwed on the vendor partition when using the flash-all script....never have figured it out
GL!!
v12xke said:
First off, if you did successfully unlock your bootloader there is a 99% chance you will be able to recover from this. In fastboot mode is the phone state shown as "unlocked" ? Do you have a second PC or laptop to install the standalone adb/fastboot binaries on? adb does not work in fastboot mode, only in stock recovery mode. First re-try fastboot flashing the full image while in fastboot mode without modifying the flash-all.bat (allow it to wipe). You may also want to check the CRC (checksum) on the image you downloaded to verify it is not corrupt. If unlocked and that install fails capture the error and report back. Then try using adb from the stock recovery. You Tube how to get into recovery and use update via adb with a (different) full OTA image. The full OTA images are also available on the same Google dev site as the factory image, and is sometimes called a rescue OTA. You're in the right place to get help, but you need to provide all relevant information (such as previously installing a custom rom).
Click to expand...
Click to collapse
cmh714 said:
try holding power and vol down until the phone reboots and comes back to the menu where you should hopefully get back to Android Recovery mode where you should be able to use adb and the OTA via a sideload......for some strange reason I always get screwed on the vendor partition when using the flash-all script....never have figured it out
GL!!
Click to expand...
Click to collapse
Thank you guys. I was able to make some progress but now I'm stuck somewhere else.
If I run flash-all, the error message I get is:
"Sending sparse 'vendor_a' 1/2 (262140 KB) FAILED (Error reading sparse file)
Finished. Total time: 108.152s
Press any key to exit..."
Alternatively, I tried sideload in recovery mode, and I get:
"E:footer is wrong
Update package verification took 0.2s
E:Signature verification failed
E:error:21
So it seems the zip I downloaded is corrupted? But I downloaded two different versions from Google Developers and both failed.
Any suggestions? I'm going to try it one more time with another computer.
edx2000 said:
Thank you guys. I was able to make some progress but now I'm stuck somewhere else.
If I run flash-all, the error message I get is:
"Sending sparse 'vendor_a' 1/2 (262140 KB) FAILED (Error reading sparse file)
Finished. Total time: 108.152s
Press any key to exit..."
Alternatively, I tried sideload in recovery mode, and I get:
"E:footer is wrong
Update package verification took 0.2s
E:Signature verification failed
E:error:21
So it seems the zip I downloaded is corrupted? But I downloaded two different versions from Google Developers and both failed.
Any suggestions? I'm going to try it one more time with another computer.
Click to expand...
Click to collapse
Have you also tried a 2.0 USB A to USB C cable, or a different set of cables period?
do what I told you....I always fail at the vendor junk but can easily get the ota sideloaded....give it a try, forget flash-all
EDIT: just read the rest of your post...hmm....
well assuming you get the correct hash after downloading, it should work. after that its computer, port, drivers, sdk, and cable thats a potential issue.
again for me, I always fail on vendor. it happened on my pixel 2xl and still on the 3xl. I have tried multiple pc's, cables, etc and always fail at the vendor partition, but the ota sideload through android recovery always worked. YMMV
cmh714 said:
do what I told you....I always fail at the vendor junk but can easily get the ota sideloaded....give it a try, forget flash-all
EDIT: just read the rest of your post...hmm....
well assuming you get the correct hash after downloading, it should work. after that its computer, port, drivers, sdk, and cable thats a potential issue.
again for me, I always fail on vendor. it happened on my pixel 2xl and still on the 3xl. I have tried multiple pc's, cables, etc and always fail at the vendor partition, but the ota sideload through android recovery always worked. YMMV
Click to expand...
Click to collapse
If vendor "always" fails on your PXL3 you may want to find out why. Could be a symptom of some problem with your phone.
Homeboy76 said:
If vendor "always" fails on your PXL3 you may want to find out why. Could be a symptom of some problem with your phone.
Click to expand...
Click to collapse
I doubt that....happened with my xl2 as well....tried multiple PC's, ports, cables, etc. nothing seems to work so I have been using the OTA as that has been bulletproof thus far
Make your you have latest fastboot and adb, a good non usbc to usb c cable, boot into fastboot, flash all, profit. If your bootloader is unlock your good.
edx2000 said:
Thank you guys. I was able to make some progress but now I'm stuck somewhere else.
If I run flash-all, the error message I get is:
"Sending sparse 'vendor_a' 1/2 (262140 KB) FAILED (Error reading sparse file)
Finished. Total time: 108.152s
Press any key to exit..."
Alternatively, I tried sideload in recovery mode, and I get:
"E:footer is wrong
Update package verification took 0.2s
E:Signature verification failed
E:error:21
So it seems the zip I downloaded is corrupted? But I downloaded two different versions from Google Developers and both failed.
Any suggestions? I'm going to try it one more time with another computer.
Click to expand...
Click to collapse
You should verify the crc checksums of the files you are using. There are many tools to do this and the signature is posted with each image. That, and like Badger says.. try a different cable (A to C). and try another PC. Google provides these image files to enable users who have unlocked their bootloader to completely restore the phone to it's factory state. I'm thinking the problem is with a corrupt image, a marginal cable, or the adb/fastboot setup on your PC/laptop. You don't need the complete Android SDK, only the standalone platform tools. The fact you have a working stock recovery and are bootloader unlocked means your likelihood of success is very high.
Badger50 said:
Have you also tried a 2.0 USB A to USB C cable, or a different set of cables period?
Click to expand...
Click to collapse
Wow, using a USB A to C worked!!
Changing to another computer did nothing.
Thanks everybody!!
edx2000 said:
Wow, using a USB A to C worked!!
Changing to another computer did nothing.
Thanks everybody!![/QUOTGlad you got it working :good:!! Pixel 2 & 3 XL's definitely have something in common. They're both picky sons of guns when it comes to cables! :good:
Click to expand...
Click to collapse
edx2000 said:
Wow, using a USB A to C worked!!
Changing to another computer did nothing.
Thanks everybody!!
Click to expand...
Click to collapse
Pixel 3a here. Found this through a bit of intense google-fu. This did the trick. Hilarious that this was the source of it. Previously was using usbc to usbc on a win10 laptop and it failed at the same part mentioned here.
Sorry for the necro bump but I think it deserves a mention. Thanks everyone here
Related
So I have no OS on my Nexus 7, nor can I flash one. All conventional methods of installing an operating system on to this POS have met with utter failure.
Brief histroy:
-Had CM 11 nightly build until it "imploded" (any shortcut would take me to a PIN screen, users deleted profiles deleted themselves, random reboot every 5 minutes) and stopped functioning.
-Decided to return to an earlier of CM, so I dl'd an earlier version and pushed the .zip to CWM recovery. Big mistake. CWM decided to repartition everything in an erroneous manner rather than just wipe Dalvik cache.
-Now CWM will not open any .zip pushed through ADB. Just a generic "failed to open file" message.
-Sheer desperation and four hours of driver Hell finds me in fastboot and trying to flash a stock image.
-Latest Android system image will not flash. Period. Using the flashall.bat script, the error about a missing system.img pops up. I am staring at system.img right next to the .bat.
-Download Android L preview and run flashall.bat, operating system installs after about 30 minutes and numerous errors that the script "seemed" to fix about missing partitions.
-Reflash TWRP
-Android L gets stuck in non-bootable state (spinning colored ball logo thing) after a random restart.
-Now TWRP cannot find any .zip that I manually push through ADB. I can see it in File Manager, but nowhere else. Flashing custom ROM at this point not possible.
-Return to Android KitKat stock image and manually flash system.img through fastboot. Tablet will not boot, goes directly to black screen after bootloader.
So WTF do I do at this point? I have just about had it with all things Android right now. CWM doesn't work. TWRP doesn't work. Stock images don't work. Fastboot doesn't work. What else is there?
Cortimi said:
So I have no OS on my Nexus 7, nor can I flash one. All conventional methods of installing an operating system on to this POS have met with utter failure.
Brief histroy:
-Had CM 11 nightly build until it "imploded" (any shortcut would take me to a PIN screen, users deleted profiles deleted themselves, random reboot every 5 minutes) and stopped functioning.
-Decided to return to an earlier of CM, so I dl'd an earlier version and pushed the .zip to CWM recovery. Big mistake. CWM decided to repartition everything in an erroneous manner rather than just wipe Dalvik cache.
-Now CWM will not open any .zip pushed through ADB. Just a generic "failed to open file" message.
-Sheer desperation and four hours of driver Hell finds me in fastboot and trying to flash a stock image.
-Latest Android system image will not flash. Period. Using the flashall.bat script, the error about a missing system.img pops up. I am staring at system.img right next to the .bat.
-Download Android L preview and run flashall.bat, operating system installs after about 30 minutes and numerous errors that the script "seemed" to fix about missing partitions.
-Reflash TWRP
-Android L gets stuck in non-bootable state (spinning colored ball logo thing) after a random restart.
-Now TWRP cannot find any .zip that I manually push through ADB. I can see it in File Manager, but nowhere else. Flashing custom ROM at this point not possible.
-Return to Android KitKat stock image and manually flash system.img through fastboot. Tablet will not boot, goes directly to black screen after bootloader.
So WTF do I do at this point? I have just about had it with all things Android right now. CWM doesn't work. TWRP doesn't work. Stock images don't work. Fastboot doesn't work. What else is there?
Click to expand...
Click to collapse
Is this an LTE or WiFi model? Do you have the nexus root tool kit installed on your computer and able to get to fastboot?
someolddude said:
Is this an LTE or WiFi model? Do you have the nexus root tool kit installed on your computer and able to get to fastboot?
Click to expand...
Click to collapse
WiFi model, fastboot and adb are fine, no toolkits.
Cortimi said:
WiFi model, fastboot and adb are fine, no toolkits.
Click to expand...
Click to collapse
Get the toolkit by wugfresh and you should be able to restore it.
someolddude said:
Get the toolkit by wugfresh and you should be able to restore it.
Click to expand...
Click to collapse
Nope. Using the Flash Stock + Unroot option gives the exact same error as doing it manually.
Flash Stock + Unroot...
------------------------------------------------------------------
sending 'bootloader' (3911 KB)...
OKAY [ 0.129s]
writing 'bootloader'...
OKAY [ 1.283s]
finished. total time: 1.412s
rebooting into bootloader...
OKAY [ 0.006s]
finished. total time: 0.006s
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
failed to allocate 754455404 bytes
error: update package missing system.img
Booting up your freshly flashed stock device...
------------------------------------------------------------------
Wait for your device to finish booting up...
- It may appear to be boot looping; just wait...
- It could take 5-10 minutes; please be patient...
When its finally booted back up, please remember
to re-enable USB debugging if you plan on using
the toolkit to perform other operations.
NOTE: If this process was too quick and your device
is still in bootloader mode, then flashing stock may
have failed or been incomplete. Simply check the
log above: if you notice it skipped steps because it
didn't meet certain requirements, like the bootloader
or baseband version, then consider enabling 'Force Flash'
mode in the toolkits options menu and trying the
'Flash Stock + Unroot' processs again. Cheers.
Press any key to exit...
Click to expand...
Click to collapse
Attempting to flash CWM recovery (found here: http://forum.xda-developers.com/showthread.php?t=2583845) results in a stuck bootloader screen. I was able to re-flash TWRP, but it is still useless as it simply does not function in any useful manner whatsoever.
Cortimi said:
Nope. Using the Flash Stock + Unroot option gives the exact same error as doing it manually.
Attempting to flash CWM recovery (found here: http://forum.xda-developers.com/showthread.php?t=2583845) results in a stuck bootloader screen. I was able to re-flash TWRP, but it is still useless as it simply does not function in any useful manner whatsoever.
Click to expand...
Click to collapse
Same problem with mine, cm11 as well.
I like some of the CM features but ever device Ive flashed and had trouble with it has been when Ive went with "Cyanide Mod"
You figure something out, please let me know and I will do the same.
I've got the LTE but my daughter has the WiFi only and is also unlocked. I can make a bone stock backup of here's which is on 4.4.4 if you want to try and restore it to yours.
So I made a post in the general help thread and nobody has replied (although I've only waited a few days so I could probably wait a bit longer) but still I feel like my phone's issues are "unique" compared to other bootloops, I can't find anyone else having the same symptoms on their phone. I'll repost what I said in the general help thread and then give a brief overview of everything because I simply cannot comprehend why I'm unable to get out of bootloop with this damn phone.
So I just recently picked up an old Zenfone 2 (ZE500CL) off of my father who didn't really need it anymore and it was an upgrade from my old ****ty phone, so of course I wanted to root it and after using it for a few hours I wanted to install a custom rom by unlocking the bootloader. Well, I tried that, and something must have gone wrong because I got a bootloop and was only really able to boot into recovery mode.
Now, I didn't backup because I'm dumb for one and two I generally have a good idea of where to start if something does go wrong. The thing is, the methods I've looked up and tried have all failed. First, reflashing the stock rom of my ZE500CL (I've tried four different firmwares from the official website, and I know it's ZE500CL because that's what recovery mode is telling me) does not work. Adb hits 47% in the command prompt, the phone stays at 25% until then, and it goes:
E: failed to verify whole-file signature
E: signature verification failed
Installation aborted
Not sure why it doesn't work, I looked it up and tried various things and it just isn't resolving itself.
So I tried simply running commands like the following:
fastboot flash recovery recovery.img
Using files from the stock firmwares themselves, and that gives me a flash_cmds error. I've tried deleting all of the userdata, the system, the cache, and a factory reset through recovery mode but none of that works. I'd really appreciate any help anyone could offer, this is a pickle and I'd really like to get this phone back up so that I can just run it as a rooted phone.
Click to expand...
Click to collapse
Now, I'll go over the issues quickly:
I'm stuck in bootloop but I can get into recovery mode
Trying to flash any rom, including multiple stock roms from the asus website, results in an installation aborted message at 47% in either ADB or microSD attempt at flashing the rom.
Attempting to run commands like fastboot flash recovery recovery.img ends up giving me a flash_cmds error which I cannot find anywhere else for the Zenfone 2e
Deleting the cache, userdata, system, or factory resetting the phone does not remove the bootloop
Unlocking and relocking the bootloader does nothing
I would really appreciate any help, feels like my phone is a lost cause even when it's not hard bricked.
Try ASUS Flashtool with a .RAW Firmware...
Find on This Thread...
ponnuvelpandian said:
Try ASUS Flashtool with a .RAW Firmware...
Find on This Thread...
Click to expand...
Click to collapse
Thanks, I haven't seen this. I've got the Intel and xFSTK drivers all up and running but my phone isn't being recognized constantly by my computer under Intel Soc in my Driver Manager, and it's not being recognized as MOOREFIELD but rather as CLOVERVIEW PLUS, and only for a second in-between boots on my phone. Can't get the files to be downloaded through xFSTK, so I've hit a snag here unless someone knows the solution to this.
I'll try just running the flash tool and using a raw firmware, then, since I can't do any of the other stuff.
EDIT: Looks like the issue I was having before is stopping me from running the tool, seems that the computer needs to recognize my phone through the Intel drivers at all time (which it doesn't) in order to run the tool. Also I can't get the tool to view the raw file, it only seems to read zip files (so I put the raw into an empty zip, thinking that could maybe work but I don't know for sure). Damnit, I don't know why this is so difficult.
EDIT 2: All right! Looks like I got it working. The process was relatively simple, actually. It involved booting into TWRP but I wasn't able to most of the time for some reason, it would just never do it. But, I was able to using the CWM Zenfone 2 bat file located here: http://forum.xda-developers.com/zenfone2/help/ze500cl-rooting-related-stuff-t3163528/
Then, I needed the stock rom for my ZE550CL placed onto an external sd card which can be found here: http://forum.xda-developers.com/zenfone2/help/ze550cl-factory-reset-return-to-stock-t3141513
So I would download the CWM Zenfone 2, replace the recovery file as the post states, then run the file. After that, I would run T4 since T1 and T2 didn't work (never tried T3), only T4 would seem to boot me into TWRP. From there, I went to Install, left Zip Verification unchecked, and let the damn thing run. It was the only thing that would run for me, even when doing it with ADB it wouldn't work with the stock rom. Then, I just rebooted and now I'm back on my phone. Hopefully this helps anyone else having this troubling issue, it was terrible!
Need some help on how to get the download mode back.
so i have HTC 10, Nougat. S-off and unlocked bootloader,
had some issues with my phone so i formatted the user data from TWRP, the went to flash the original stock ROM, something went wrong obviousely so now i lost the ability to get into download mode.
if i press the power and volume down the phone just gets stuck in boot screen, i can get into the bootloader and recovery (not the TWRP) by pressing power and both volume buttons, bot from recovery I seem to fail flashing the ROM again, it fails on the signature check and even via ADB i cannot boot to download mode.
Any advice on how to get this issue sorted. i want to get the twrp or reinstall the rom again.
PS placing the rom.zip on the SD card is not doing anything as the phone bypasses that step automatically
thanks in advance
Avo_GH said:
Need some help on how to get the download mode back.
so i have HTC 10, Nougat. S-off and unlocked bootloader,
had some issues with my phone so i formatted the user data from TWRP, the went to flash the original stock ROM, something went wrong obviousely so now i lost the ability to get into download mode.
if i press the power and volume down the phone just gets stuck in boot screen, i can get into the bootloader and recovery (not the TWRP) by pressing power and both volume buttons, bot from recovery I seem to fail flashing the ROM again, it fails on the signature check and even via ADB i cannot boot to download mode.
Any advice on how to get this issue sorted. i want to get the twrp or reinstall the rom again.
PS placing the rom.zip on the SD card is not doing anything as the phone bypasses that step automatically
thanks in advance
Click to expand...
Click to collapse
Go into download mode from bootloader.
yldlj said:
Go into download mode from bootloader.
Click to expand...
Click to collapse
I cannot, when i pick download mode it goes straight into a boot loop and gets stuck on the HTC logo screen nothing else happens
push vol down vol up and power
Since the computer can talk to the phone, I would try the RUU executable.
(hard to help troubleshoot not knowing what you did but flashing "original stock ROM" via TWRP is a problem)
If you're getting a signature check fail, investigate that. What file are you flashing? How are you trying to flash it? Does downloading it again and comparing the two show any differences (if there isn't a hash to verify it)?
Rolo42 said:
Since the computer can talk to the phone, I would try the RUU executable.
(hard to help troubleshoot not knowing what you did but flashing "original stock ROM" via TWRP is a problem)
If you're getting a signature check fail, investigate that. What file are you flashing? How are you trying to flash it? Does downloading it again and comparing the two show any differences (if there isn't a hash to verify it)?
Click to expand...
Click to collapse
thanks for your comment,
I will try the RUU method tonight and see if that makes any difference.
I was flashing the Original Stock ROM, but i did that from SD card not TWRP, but during the flashing the phone rebooted multiple times and then i ended up with this issue. i am pretty sure I am trying to flash the same file, but will check the Hash just to be sure.
the issue the annoys me is that i cannot access the download mode, if i could then i will flash TWRP again and restore from backup images i have.
I want to say there's a condition where you have to flash twice but I'm not certain on that but it wouldn't hurt.
The signature fail is a concern; hence getting a new file. Are you exctracting 2PS6IMG.zip from the RUU via the decrypt tool? That's what I've always done to ensure I have the correct file and intact.
Rolo42 said:
I want to say there's a condition where you have to flash twice but I'm not certain on that but it wouldn't hurt.
The signature fail is a concern; hence getting a new file. Are you exctracting 2PS6IMG.zip from the RUU via the decrypt tool? That's what I've always done to ensure I have the correct file and intact.
Click to expand...
Click to collapse
oh thanks for that tip, I used a zip file downloaded from easy-firmware.com
but tonight will try to extract from the RUU. will see how that goes.
really appreciate you taking time to respond
Avo_GH said:
oh thanks for that tip, I used a zip file downloaded from easy-firmware.com
but tonight will try to extract from the RUU. will see how that goes.
really appreciate you taking time to respond
Click to expand...
Click to collapse
Yeah, there's a lot that can go wrong there, like downloading the wrong one, the poster making a mistake, not to mention its an unknown source--especially since you're S-OFF.
Ensure you get the correct version from htc.
Rolo42 said:
Yeah, there's a lot that can go wrong there, like downloading the wrong one, the poster making a mistake, not to mention its an unknown source--especially since you're S-OFF.
Ensure you get the correct version from htc.
Click to expand...
Click to collapse
ok here is the latest development, wondering if anyone has any advise,
firstly extracting the file from the RUU and flashing it did not work. however i managed to find a little app called Windroid that allowed me to flash TWRP from the bootloader (without the need to go to download mode)
but I soon found out that the phone lost all its partitions. so i cannot wipe, format, install anything, but i can see a bunch of folders and filed via the TWRP file manager.
used ADB fdisk -lu I only see one single partition end was only able to remount /dev/block/mmcblk0p1.
any advice will be highly appreciated I am not sure how to proceed here
thanks in advance
Avo_GH said:
ok here is the latest development, wondering if anyone has any advise,
firstly extracting the file from the RUU and flashing it did not work. however i managed to find a little app called Windroid that allowed me to flash TWRP from the bootloader (without the need to go to download mode)
but I soon found out that the phone lost all its partitions. so i cannot wipe, format, install anything, but i can see a bunch of folders and filed via the TWRP file manager.
used ADB fdisk -lu I only see one single partition end was only able to remount /dev/block/mmcblk0p1.
any advice will be highly appreciated I am not sure how to proceed here
thanks in advance
Click to expand...
Click to collapse
If you're still in this trouble: -Search for your actual installed ROM (the firmware zip with a lot of other zips inside), deRUU it (search on google how to decompress a RUU) and flash via BOOTLOADER the hosd_signed.img image (this is "download" and "RUU" modes). You can boot to BOOTLOADER holding both volume buttons and power together (try more times if it wont boot).
vladmitra said:
If you're still in this trouble: -Search for your actual installed ROM (the firmware zip with a lot of other zips inside), deRUU it (search on google how to decompress a RUU) and flash via BOOTLOADER the hosd_signed.img image (this is "download" and "RUU" modes). You can boot to BOOTLOADER holding both volume buttons and power together (try more times if it wont boot).
Click to expand...
Click to collapse
thanks for the response, I want to try this method too, just wondering do you have any idea how to flash the file form bootloader, given i donot have fastboot, or more precisely fastboot would not see my device, but adb does. (but if I try to reboot to download/fastboot from adb the phone just goes to sleep)
thanks in advance
Avo_GH said:
thanks for the response, I want to try this method too, just wondering do you have any idea how to flash the file form bootloader, given i donot have fastboot, or more precisely fastboot would not see my device, but adb does. (but if I try to reboot to download/fastboot from adb the phone just goes to sleep)
thanks in advance
Click to expand...
Click to collapse
Flash in bootloader the hosd image for your actual firmware and you should be able to use fastboot/download
Im stuck!!
I was rooted with Magisk on crosshatch QP1A.190711.020.C3, Sep 2019.
I just tried option #4 keep data and am getting the below (also attached pic) after getting to fastbootd screen during flash:
sending product FAILED (Write to device failed (Invalid argument))
When I try to reboot, it only boots to bootloader. I then tried wiping data same thing. I then tried reverting to the previous .C3 Sep 2019 firmare and again, same thing.
Im currently on slot B and as far as im aware, I havent done anything to slot A. However, in the bootloader screen at the bottom, I see:
Enter reason: no valid slot to boot
Before I try flashing anything else, Id like to try to boot to Slot A and see if I can at least have a usable phone for work tomorrow. Is it possible to boot to slot A from the bootloader screen?
If not, what else can I do?
Thanks in advance!!!!
JJT211 said:
Im stuck!!
I was rooted with Magisk on crosshatch QP1A.190711.020.C3, Sep 2019.
I just tried option #4 keep data and am getting the below (also attached pic) after getting to fastbootd screen during flash:
sending product FAILED (Write to device failed (Invalid argument))
When I try to reboot, it only boots to bootloader. I then tried wiping data same thing. I then tried reverting to the previous .C3 Sep 2019 firmare and again, same thing.
Im currently on slot B and as far as im aware, I havent done anything to slot A. However, in the bootloader screen at the bottom, I see:
Enter reason: no valid slot to boot
Before I try flashing anything else, Id like to try to boot to Slot A and see if I can at least have a usable phone for work tomorrow. Is it possible to boot to slot A from the bootloader screen?
If not, what else can I do?
Thanks in advance!!!!
Click to expand...
Click to collapse
Did you try to use the latest SDK https://developer.android.com/studio/releases/platform-tools.html/
saxmydix said:
Did you try to use the latest SDK https://developer.android.com/studio/releases/platform-tools.html/
Click to expand...
Click to collapse
Yup, im on 29.0.4
So I found the command to switch to slot A
fastboot set_active a
Still stuck in bootloader mode.
Huuu... Had the same problem. You should try again flash.all from pc. You wait until the i/o error apears. Then you are in fastboot.d mode. From here you choose sideload ota from pc (or simular). Now you are able to execute the adb sideload command from your pc. Then wait and reboot. This saved my ass... Make sure you downloaded the full ota image before.
OK I did the regular flash-all as you said and got error. At this point, the CLI says press "any key to exit"
I then exited, selected recovery - apply ADB update - opened CLI - adb devices (saw my serial #) and then entered "adb sideload image-crosshatch-qp1a.191005.007.zip"
And now after im getting:
verifying update package....
E: footer is wrong
Update package verification took .2 s (result 1)
E: signature verifcation failure
E: error: 21
Install from ADB completed with status 2
Installation aborted
EDIT: Im an idiot, I tried to sideload the factory image. Im sideloading the OTA now. Looks like its working. Standby
Donric13 said:
Huuu... Had the same problem. You should try again flash.all from pc. You wait until the i/o error apears. Then you are in fastboot.d mode. From here you choose sideload ota from pc (or simular). Now you are able to execute the adb sideload command from your pc. Then wait and reboot. This saved my ass... Make sure you downloaded the full ota image before.
Click to expand...
Click to collapse
It worked AND I kept all my data! Suweeet! Damn you saved my ass, I wouldve been ****ed tomorrow at work. Thanks again!
How many hours did it take you to figure that out??
JJT211 said:
It worked AND I kept all my data! Suweeet! Damn you saved my ass, I wouldve been ****ed tomorrow at work. Thanks again!
How many hours did it take you to figure that out??
Click to expand...
Click to collapse
Tried several ways to get into recovery (fastboot.d) to sideload the ota after the i/o error... After a hour i got the trick (3. try to begin with flash-all.sh...). Somehow i always got trouble with system space when monthly update is downloaded automatically and can't get applied because i am rooted... Somehow it seems saver to install the full ota with sideload than the flash-all.sh procedure... Glad it also worked on your side.
Donric13 said:
Huuu... Had the same problem. You should try again flash.all from pc. You wait until the i/o error apears. Then you are in fastboot.d mode. From here you choose sideload ota from pc (or simular). Now you are able to execute the adb sideload command from your pc. Then wait and reboot. This saved my ass... Make sure you downloaded the full ota image before.
Click to expand...
Click to collapse
Which file do i sideload? I tried crosshatch-qp1a.191005.007-factory-2989a08d.zip. It failed with same error as guy above. I then tried to adb sideload image-crosshatch-qp1a.191005.007.zip and i got the same error? which file am I supposed to sideload?
EDIT:Never mind. I found the file. downloading and flashing hopefully it works!
Hello guys, I recently formatted data on my phone to fix a bootloop I had. After fixing everything, SIM card and wifi was not working, I downloaded the Official Stock ROM of my phone and flashed bluetooth, modem, dsp and dtbo. The original plan was to run "flash_all_except_storage.bat" but that kept throwing errors. After I flashed those things I booted successfully and unlocked my phone. Problem is Wifi still doesn't work. So once again got into fastboot, tried running "flash_all_except_storage.bat", once again it threw an error, so I restarted my phone and ever since I can't boot into system. Whenever I restart it goes straight into fastboot, Power off and on again goes to fastboot, I can boot into TWRP, rebooting from there still goes into fastboot mode. I fix a problem and 2 more take it's place, I really need your help here.
Thanks a lot !
Edit:
Fix Attempt 1 (FAILED): I tried formating data through TWRP as I read online, it did not work
Attempt 2 (FAILED): Used
Code:
fastboot continue
and got this error:
Code:
Resuming boot FAILED (remote: 'Failed to load image from partition: No Media')
fastboot: error: Command failed
Attempt 3 (HALF FIX): After some digging I realized after a failed attempt to run "flash_all_except_storage.bat", the boot was erased. I tried flashing only the boot.img and the phone booted up with the wifi working as well. Problem is after a reboot I go back into fastboot and I have to flash boot.img again to boot into system.
Here is recovery.log Pastebin
Leonniar said:
Hello guys, I recently formatted data on my phone to fix a bootloop I had. After fixing everything, SIM card and wifi was not working, I downloaded the Official Stock ROM of my phone and flashed bluetooth, modem, dsp and dtbo. The original plan was to run "flash_all_except_storage.bat" but that kept throwing errors. After I flashed those things I booted successfully and unlocked my phone. Problem is Wifi still doesn't work. So once again got into fastboot, tried running "flash_all_except_storage.bat", once again it threw an error, so I restarted my phone and ever since I can't boot into system. Whenever I restart it goes straight into fastboot, Power off and on again goes to fastboot, I can boot into TWRP, rebooting from there still goes into fastboot mode. I fix a problem and 2 more take it's place, I really need your help here.
Thanks a lot !
Edit:
Fix Attempt 1 (FAILED): I tried formating data through TWRP as I read online, it did not work
Attempt 2 (FAILED): Used
Code:
fastboot continue
and got this error:
Code:
Resuming boot FAILED (remote: 'Failed to load image from partition: No Media')
fastboot: error: Command failed
Attempt 3 (HALF FIX): After some digging I realized after a failed attempt to run "flash_all_except_storage.bat", the boot was erased. I tried flashing only the boot.img and the phone booted up with the wifi working as well. Problem is after a reboot I go back into fastboot and I have to flash boot.img again to boot into system.
Here is recovery.log Pastebin
Click to expand...
Click to collapse
Can you flash full rom with mi flash tool
Rares6567 said:
Can you flash full rom with mi flash tool
Click to expand...
Click to collapse
Already did, it didn't work...
Leonniar said:
Already did, it didn't work...
Click to expand...
Click to collapse
Maybe is some motherboard issues?
I don't believe so. The problem I originally had was that after a restart the phone was booting into fastboot. But if I didn't restart the phone was working fine, cellular, wifi google services everything. So in order to fix that I flashed the full stock rom and that's how I ended up in the restart loop in the first place.
https://forum.xda-developers.com/t/decrypting-xiaomi-mi10t-pro-internal-storage.4544271/page-2#posts
Here are all the details, I started from a completely different problem and ended up here. They entire process I took is in that thread
Leonniar said:
I don't believe so. The problem I originally had was that after a restart the phone was booting into fastboot. But if I didn't restart the phone was working fine, cellular, wifi google services everything. So in order to fix that I flashed the full stock rom and that's how I ended up in the restart loop in the first place.
https://forum.xda-developers.com/t/decrypting-xiaomi-mi10t-pro-internal-storage.4544271/page-2#posts
Here are all the details, I started from a completely different problem and ended up here. They entire process I took is in that thread
Click to expand...
Click to collapse
There is no volume buttons problem?
If no maybe you should reflash whole phone, fastboot, recovery, all, using edl ig.... I don't have this phone or any Snapdragon phone, so I don't really know....
Yeah I did, I used the flash_all.bat that comes with the ROM file and pretty much replaced everything. I tried to run it a couple of times and it failed mostly but I was able to run it twice I think (without changing anything, just running it again and again at some point it worked)
Leonniar said:
Yeah I did, I used the flash_all.bat that comes with the ROM file and pretty much replaced everything. I tried to run it a couple of times and it failed mostly but I was able to run it twice I think (without changing anything, just running it again and again at some point it worked)
Click to expand...
Click to collapse
So then why your phone goes to fastboot?
I really don't know, after running flash_all the second time now my phone is stuck in a restart loop. Shows the MI logo and restarts. I can manually boot to recovery or fastboot but if I leave it on it's own it keeps turning on and off
Leonniar said:
I really don't know, after running flash_all the second time now my phone is stuck in a restart loop. Shows the MI logo and restarts. I can manually boot to recovery or fastboot but if I leave it on it's own it keeps turning on and off
Click to expand...
Click to collapse
It seems that this a software bug ig, can you try go to recovery and flash the rom?
I could try but I am not sure how to do that. My rom comes in a .tgz format and not .zip and all guides mention you need a .zip file
Leonniar said:
I could try but I am not sure how to do that. My rom comes in a .tgz format and not .zip and all guides mention you need a .zip file
Click to expand...
Click to collapse
So where u downloaded the fastboot rom, there is a recovery rom too :
Xiaomi Firmware Updater
The ultimate script that provides firmware packages for Xiaomi devices.
xiaomifirmwareupdater.com
Be sure u download the recovery rom not fastboot.
Btw use your miui version u had
Tho I'm not 100% sure if you flashed the fastboot rom correctly, did u :
1. Open MiFlashTool : download the tool from here if you don't have it ---> https://xiaomiflashtool.com/
2. Select your rom ( make sure your path to the rom isn't long and the folder/folders don't have long names )
3. Connect your phone
4. Click Refresh ( to make your device appear)
5. And click flash
I didn't do it with MiFlashTool because it kept throwing errors at me whenever I launched it so I tried the flash_all.bat batch file that runs cmd commands and flashes everything. the ROM I installed was the fastboot version. The official website on the recovery ROM stated that "This page shows a single update only" so I assumed it's just an update and not the full ROM. I was also told I should use the fastboot variant in the above mentioned thread
Leonniar said:
I didn't do it with MiFlashTool because it kept throwing errors at me whenever I launched it so I tried the flash_all.bat batch file that runs cmd commands and flashes everything. the ROM I installed was the fastboot version. The official website on the recovery ROM stated that "This page shows a single update only" so I assumed it's just an update and not the full ROM. I was also told I should use the fastboot variant in the above mentioned thread
Click to expand...
Click to collapse
Ok so to fix the error : go to miflashtool folder and create a new folder called : log
Fixed the start up error, I get the screen that says "Please install driver", I press Install and I get this:
https://prnt.sc/I53g6bs_8i5w
Pressing ok gets me back to the "Please install driver" screen
Well I just closed the Install driver window and flashed as is, I got this:
https://prnt.sc/Bk2eaj9w5Lq7 so presumably it failed but my devices rebooted and is now on system set up
Edit:
3 reboots later and phone still boots fine to system
Rares6567 said:
It seems that this a software bug ig, can you try go to recovery and flash the rom?
Click to expand...
Click to collapse
flashing miui_APOLLOEEAGlobal_V12.5.4.0.RJDEUXM_451a2324af_11.0.zip from stock recovery is good idea, you can do this from MicroSD card to circumvent any usb issues you are obviously facing on fastboot.
Leonniar said:
Well I just closed the Install driver window and flashed as is, I got this:
https://prnt.sc/Bk2eaj9w5Lq7 so presumably it failed but my devices rebooted and is now on system set up
Edit:
3 reboots later and phone still boots fine to system
Click to expand...
Click to collapse
So it worked?
This "error" isn't an "error" so don't worry about it
Leonniar said:
Well I just closed the Install driver window and flashed as is, I got this:
https://prnt.sc/Bk2eaj9w5Lq7 so presumably it failed but my devices rebooted and is now on system set up
Edit:
3 reboots later and phone still boots fine to system
Click to expand...
Click to collapse
This error is normal since you are not re-locking the bootloader.
If some functions are inoperative.
Try to flash the same rom (fastboot) that you had when you bought the phone, probably an A11.
Use clean all(flash_all.bat).
https://forum.xda-developers.com/t/flash-tool-guide-use-xiaomi-flash-tool.4262425/