Develop Bugs

[Help] No OS, 0mb internal storage.

Not sure what happened. My tablet is showing No OS in TWRP. I haven't installed or done anything to it recently. I just went to turn it on the other day and it wouldn't boot.
For the past hour I've unsuccessfully been trying to flash the factory images in flashboot. I tried using Wugfresh's nexus root toolkit, but I get an error when it tries to flash the images. **FAILED (remote: flash write failure)**
I've attempted to adb side load, but the internal storage fails to mount. the device is unlocked. I've also attempted to fastboot manually but I'm trying to do the system now and it's been "erasing" for about 10 minutes.
I've attempted to us TWRP to repair and it fails, it also fails to format the partition.
My device dead?

It does not look good but luckily your tablet is unlocked and more options are available. Please post your logs.

k23m said:
It does not look good but luckily your tablet is unlocked and more options are available. Please post your logs.
Click to expand...
Click to collapse
Ok. Attached is the dmesg. I was getting access is denied b/c Windows 10. Had to write the file to another folder.
When I try to run the second command I get an I/O Error.

OTA to OOS 4.0 and adb sideload won't work

Hello Guys!
I was kinda hyped when I saw on Dec 31st that there's a new Softwareupdate available. Although I have a rooted device with a custom recovery (latest TWRP), previous OTAs always worked well. So I downloaded the OTA, and tapped "install" when it was finished. But this time it rebooted into recovery mode, and TWRP just did nothing. So, assuming it was because of the rooted device, I completely unrooted it and flashed the stock recovery and tried it again. This time there was actually smth. but an error saying "Update failed" appeared. Kinda pissed I downloaded the OTA update to my PC and tried to do it via adb sideload, same error "Installation failed" on the phone and cmd said
Code:
error: protocol fault (no status)
.
After that I copied the .zip to my phone, flashed TWRP again made a nandroid backup, wiped dalvik, chache & CO (no factory reset) and installed the zip. Again: Error. I don't remember the exact code, but it was smth. with "error reading zip" or so, but the file isn't damaged.
So I have the question: What am I doing wrong? Do I have to lock OEM again?
I am looking forward to your answers.
Sincerely, Firnien
PS: I updated adb to the latest version as well and tried, still not working

You should try this : https://forum.xda-developers.com/oneplus-3/how-to/fix-device-mapper-verity-simple-trick-t3530685
Start with flashin twrp -28 then follow step by step.

Nobody07 said:
You should try this : https://forum.xda-developers.com/oneplus-3/how-to/fix-device-mapper-verity-simple-trick-t3530685
Start with flashin twrp -28 then follow step by step.
Click to expand...
Click to collapse
Thanks, I'll try it

Help - Pixel 3 stuck after failed flash-all...

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

Help with flash stock rom

Hello,
I have a pixel 2 xl, with android 10 february 2020 patch. Device was rooted with magisk than removed it but somehow I lost the option to OTA update from settings and some apps still saying root detected.
Now I tried to add android 11 and all stuck.
I have secure boot yes and device state unlocked.
When I go to recovery on top shows R/RPP4.200409.015/6455311
Wehn I try to apply update from adb with "adb sideload taimen-rpp4.200409.015-factory-dca8dad0.zip" nothing happens, it's stuck to verifying update package...
If I remove cable usb-c to usb-c shows signature verification failed.
tried with:
taimen-rpp4.200409.015-factory-dca8dad0.zip
taimen-ota-qq1a.200205.002-1c132203.zip
Any help please?

z3dulik said:
Hello,
I have a pixel 2 xl, with android 10 february 2020 patch. Device was rooted with magisk than removed it but somehow I lost the option to OTA update from settings and some apps still saying root detected.
Now I tried to add android 11 and all stuck.
I have secure boot yes and device state unlocked.
When I go to recovery on top shows R/RPP4.200409.015/6455311
Wehn I try to apply update from adb with "adb sideload taimen-rpp4.200409.015-factory-dca8dad0.zip" nothing happens, it's stuck to verifying update package...
If I remove cable usb-c to usb-c shows signature verification failed.
tried with:
taimen-rpp4.200409.015-factory-dca8dad0.zip
taimen-ota-qq1a.200205.002-1c132203.zip
Any help please?
Click to expand...
Click to collapse
Just nuke it with flash-all.bat May factory image. You can boot TWRP and flash the R OTA as well.

I did with flash-all.bat too, goes to the end with some missing files in the log, but still not working.
TWRP when I try to flash .img - returns no such partition
When I turn it on i have an alert "your device is corrupt."

z3dulik said:
I did with flash-all.bat too, goes to the end with some missing files in the log, but still not working.
TWRP when I try to flash .img - returns no such partition
Click to expand...
Click to collapse
I would extract the factory image, fastboot erase user data then update bootloader, radio and vendor on both slots(reboot bootloader after each flash) then flash-all or fastboot update with the Taimen file that contains the vendor image
It's a bit longer of a process but it works.

Tried too, same thing. Looks like it's something related to recovery. Can't write to

z3dulik said:
Tried too, same thing. Looks like it's something related to recovery. Can't write to
Click to expand...
Click to collapse
Swap slots and flash to both
Sent from my Pixel 4 XL using Tapatalk

Managed to flash twrp on boot_a

z3dulik said:
Tried too, same thing. Looks like it's something related to recovery. Can't write to
Click to expand...
Click to collapse
I've got out of this before
Boot TWRP
Format data
Pop in an otg with stock OTA hit mount go back and hit mount then it'll appear as auto-1 in TWRP and flash the OTA
It works if you need to go back to previous month or Android version. Just make sure both slots are the same after you boot

OTG not recognised
/vendor error
also the factory images are missing from here? https://developers.google.com/android/images
I can see only OTA

fixed with factory android 10 april. thanks all for help

Xiaomi Mi 10T keeps booting into fastboot

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/