Related
NO ONE?????
ODIN --> Flash Stock Recovery (AP) with NAND Erase All Option Checked (because it seemed to make sense) + Auto Reboot + F. Time Reset --> Reboots to Stock Recovery (did not work before) --> Reboot into Recovery --> Wipe Data/Cache and Dalvik just to be safe (this crashed it before) --> Reboot. THE END
TL/DR: I am currently stuck on recovery/update mode. Any attempt to wipe data or clear dalvik crashes it. any attempt to access data through TWRP crashes it. Flashing stock rom or custom rom does not help. Somethings wrong with /data? It thinks it has root from the CF Auto Root, but does not really? Something wrong with partitions? Should I wipe the nand with ODIN 3.10? Repartition? ugh ... Please help ...
I have searched the forums and found nothing that describes this issue precisely. I have also tried to apply various suggestions to repair, which, for the most part seems to have made it worse. I am hoping that people still look at this forum.
PC - Windows 7
Initially @4.2.2 ---> Touchwiz debloated stock ROM which I rooted. It worked for a couple years, but the device crashed frequently. I do not recall much about the installation, but believe that I used CWM/TWRP at the time. After installing the ROM, I ran triangle away (out of the box, it had 4.1.2, i recall)
I decided to upgrade to the most recent stock ROM (4.4.2). In order to do so, I used an easy installer I found else where on XDA. (http://forum.xda-developers.com/showthread.php?t=2773712 ---ODIN One Click exe). The device was not initially recognized, so I reinstalled the official driver package (said that they already existed, but I installed again anyway). Ran 1-click and it appeared to work.
Initially, the device booted (long startup) and seemed to function. It also preserved all data and programs (presumably did not touch the internal memory - 16 GB) and possibly root /data.
I then tried to root through most recent ODIN with CF auto root. This appeared to work and rebooted (again, showing the updating android apps screen before fully booting).
The only thing that i could find that had changed was the wallpaper (showed on lock screen but not on home screen). I could no longer find the image, so tried to go to /data/data to find it with root explorer equivalent. This is where it started to act weird.
NOTE: I did not clear anything (system cache, etc. at any point)<--a lie (see below)
It showed the root folder fine, but when I clicked on /data it took a while and could not access it. It either rebooted itself or I rebooted, but this time it was stuck in a boot logo loop. I entered download mode and flashed TWRP through ODIN. I set it to not reboot automatically so that the bootloader was not overwritten automatically (thus losing recovery). TWRP came up. The computer recognized it as a Media Device after I mounted USB storage. Just in case, I copied all of the important files from the internal SD Card to my computer. I then tried to go to the file explorer to copy the wall paper and it forced a reboot. At this point it was stuck on a logo screen boot loop again. I was able to enter Download mode and reflash TWRP. This allowed me to enter recovery again, however, now it would only boot directly into recovery (or Download mode if I did the button combo). The interesting thing was that it would reboot two or three times before successfully entering TWRP.
I believe I tried to reflash the stock ROM at this point, which might have worked but made no difference.
I was also having a lot of problems getting Windows to properly recognize the device. I had to reinstall the drivers a couple times. I tried Kies after the problems started and it tried to connect by failed. The diagnose connection did not work either. I was not able to get Kies to connect though I tried several times throughout the attempted repair
I downloaded a stock-rooted 4.4.2 ROM from here and tried to flash it. It failed.
I also tried to flash via Heimdall, but initially could not find any stock ROMs for Heimdall for the Galaxy 8. (The driver utility that is included helped to get the phone recognized by Windows sporadically).
I decided to switch over to CWM touch recovery, which I flashed via ODIN (I was having issues with TWRP again and also could not get windows to recognize the device as a media device when I mounted USB storage). This worked after a couple tries and I was able to enter CWM. I attempted to flash the stock ROM but it failed. Either at that point or when I tried to mount data it returned an error that device did not have root. Again, it would only boot into CWM (on its own) or Download mode (with key combo). At some point around here I cleared the cache and dalvik (error) after it returned an error saying insufficient space when trying to flash ROM.
I dissected the .exe from the autoflash used in the beginning (stock unrooted 4.4.2) and used the contents (system.img, cache.img, hidden.img, tz.img, recovery.img and one other I do not remember) in Heimdall to create a Heimdall package. At this point I figured out I did not need to create the package, but just specify the individual files. I flashed. It appeared to complete System.img successfully and then failed. Tried again with the same result.
Now when I rebooted, it would enter download mode with the Key combo, but otherwise it booted instantly to an error screen to the effect that a firmware installation had failed and to use the repair function in Kies to fix. Kies still did not recognize it.
At this point, I figured I should stop. Currently I can get to the download screen or the error screen. The computer recognizes it but intermittently fails to install driver. Zadig.exe sees it as Gadget Serial. Sometimes Windows just sees it as SAMSUNG_Android, in which case drivers fail. Once or twice I got it to recognize it as Samsung USB Composite Device, but Kies would still not work.
That's all i have for now. If more information is needed, let me know and I will update the post when I get home from work tonight (this is from memory).
Thank you
UPDATE: last night I went home and was able to get it back to the point where I could flash TWRP or CWM recovery. If I try to flash Stock Recovery, it fails. A minor problem is that I cannot turn it off - it just turns it self on again, so the battery keeps running down.
Hi,
I wanted to update my Pixel C to the most current factory image with flashfire as i did it before a few times without problems.
So I DL'd current factory image from https://developers.google.com/android/images#ryu, opened it in flashfire and said it should flash the normal partitions except recovery as i don't want that it overwrites my TWRP.
Flashfire analyzed the zip file and after i said "flash" it restarted my Pixel into a black screen. At this point i was wondering that nothing more happened.
I waited for 10 minutes so that maybe something in the background could happen, but there was no further action. The screen kept black.
After these 10 minutes i restarted the device but now it always runs into TWRP directly instead of starting the system
I also tried to install the zip manually in TWRP but it tells me
"Could not find 'META-INF/com/google/android/update-binary' in the zip file.
Error installing the zip file '/usb-otg/ryu-n2g48c-factory-0bc0ee15.zip'"
As you can see from the error message i also tried to dl the file again and install it via OTG but the same thing.
If I go into the file manager in TWRP i can still access the folders from the sdcard.
The bootloader is unlocked of course.
Anyone an idea what i can do without loosing all the data?
Thanks in advance
Download the full system image and extract it. There should be a flash_all-file (bat for windows of sh for linux). Open it with an editor and remove the "-w" option in fastboot. "-w" is the switch for wipe. After you removed it, you can flash the complete image and your system should boot again into android. After that you can install a custom recovery, etc. again.
Thank you peter, worked like a charm for the system flash. Now follows the TWRP etc again
EDIT: ok, the system flash was the only thing that worked like a charm. I tried flashing TWRP with NRT but didn't work. I am stuck now at a "no command" screen when i start the device.
To install the custom recovery NRT tells me that i will loose all my data, so i wanted to backup everything.
Unfortunately i can't backup everything now as the temp booted TWRP demands a password to decrypt the sdcard, but i only have a pattern and no password set.
So now i try to flash everything again and to install twrp without loosing all the data.
Hey everyone I have flashed android 7.1.2 August again and android started afterwards without any problems. I was able to restore the backup of all the apps from Google.
Than I wanted to get back root and flashed TWRP with Nexus Root Toolset, but now only TWRP starts every time I switch on the tablet. Any ideas what I can do?
EDIT: I fixed it somehow with flashing the whole firmware package again and than the TWRP wich broke the startup again so i ended up in a TWRP bootloop. Therefore i flashed android again and TWRP 3.0.0.0 than TWRP 3.0.2.4 (something like that) and after like 3 to 4 different flashing steps it worked again. I have no idea what happened during the first flash of Andoir 7.1.2 but i think that something broke there.
I'm about 4 hours of reading in on this matter, and I still don't have a proper answer. I've run through countless threads with similar titles, and found some helpful tidbits, but nothing the resolves or fully explains what is going on here.
I just made the jump from Android 9.0.0 (latest) rooted to Android 10.0.0 (latest.) Here were my steps:
Download the latest Platform Tools & unzip
Download the latest Android 10.0.0 Factory image for Pixel 2 XL & unzip into the platform tools folder
Download the latest USB drivers & install
Hook up my phone to the computer (Windows 10) and verify that ADB & Fastboot are working properly via command prompt
Execute the flash-all.bat (left the -w flag in so that it wiped my data) -- it appeared to be only flashing the one slot except for a couple mentions of the other slot's system towards the end of the commands
The phone booted just fine and I went through and installed TWRP and Magisk 23 and so on
Here's where I encountered the error:
As I was rebooting out of TWRP, I realized I'd never used the "Slot A" or "Slot B" buttons, so I picked one, and it started rebooting the phone. The normal screen with the yellow text about phone being unlocked came up, then switched to the white background with the 'G' as expected. The expected next step would've been the 'G' spinning into a circle for a second, and then going to the homescreen, but instead what happened was the screen went black, and then a screen that said "Your device is corrupt. It can't be trusted and may not work properly." showed. It looked similar to the one when the phone first boots with the yellow text about the bootloader, but this text was red. I attempted to use the power button to bypass it, and when I did, it switched the the normal yellow-text-about-bootloader screen, and then switched to the 'G' with the white background again, but there it stayed, just frozen.
I was still able to boot to bootloader by using the power + down button, and could then boot to the stock recovery, but that was it. After a bit of reading, I discovered the following command:
fastboot set_active a
or
fastboot set_active b
and also fastboot getvar all
The set_active command chooses which Slot is being used, and the getvar command shows all the fastboot variables, one of which shows the "current_slot." Once I set the other Slot to be the active one and rebooted, the phone booted normally. Buuut, now I'm concerned that someone is screwed up with my phone, and it's going to fail at some point when I don't have my computer handy, so I went back to work trying to resolve the error when I booted out of the one slot.
Here's what I've tried:
Run the flash-all.bat file in one slot, let the phone reboot, boot to bootloader, switch slots, reboot to bootloader, flash-all.bat in the other slot.
Same as above, but without the -w flag.
Manually flash the bootloader, radio and image zip on both slots
Install the TWRP while booted into the adb-loaded TWRP img (this seems to write to both slots based on the output)
Install and uninstall Magisk both via recovery and via the patched stock boot image.
After every single attempt, the one slot would work just fine, and the other slot would exhibit the behavior I mentioned. Depending on which Slot is flashed first, the Slot that fails to boot properly does change (ie. it's not always Slot A or Slot B that fails.)
Untested methods:
Screwing with dm-verity -- I saw one thread that gave a few fastboot commands to disable dm-verity, and a couple people reporting success with it. After searching around and doing a bit of reading on dm-verity, I still don't understand what it does, whether disabling it would have any negative repercussions, and whether disabling it would fix the issue legitimately, or just kinda mute it.
Using Deuce's bootloop recovery tool -- again, I don't really know what that thing is running, it hasn't been maintained in quite some time as far as I can tell, and there are several threads indicating that it runs a bunch of haphazard stuff that could cause more problems. Some reports indicated it worked for them, but I'm concerned about what else it might be doing that may negatively affect things down the road.
Re-locking the bootloader -- I saw this one mentioned several times, but I also saw several people warning that you could brick your phone if you do it wrong. I also saw one or two folks who seemed like they couldn't get back to being unlocked after re-locking. I don't want to screw with this option given those risks.
Can anyone give me any more tips on how to resolve this? I'm pretty sure that the Pixels are supposed to run equally well from both slots, so I'd really like to get the matter resolved so I don't have to worry about what would happen if my phone moved me over to the other Slot for some reason. Any insight and explanations are appreciated!
People say that you cannot install both TWRP and magisk (I haven't tried it myself). So start again with a flash-all, and then, instead of installing TWRP, run it using fastboot boot whenever you need it.
The OP needs to flash a factory image first or the corruption message will never disappear. While he's at it he should make the jump to Android 11...latest radios and all that. If he doesn't want to lose data he can edit flash-all.bat in the factory image and remove the -w flag in that batch file.
From there he can flash anything he wants. If he plans on rooting however he cannot install TWRP, only boot it using ADB. The combination of Magisk and TWRP causes a bootloop.
runekock said:
People say that you cannot install both TWRP and magisk (I haven't tried it myself). So start again with a flash-all, and then, instead of installing TWRP, run it using fastboot boot whenever you need it.
Click to expand...
Click to collapse
The problem presents with even the stock boot image though.
Strephon Alkhalikoi said:
The OP needs to flash a factory image first or the corruption message will never disappear. While he's at it he should make the jump to Android 11...latest radios and all that. If he doesn't want to lose data he can edit flash-all.bat in the factory image and remove the -w flag in that batch file.
From there he can flash anything he wants. If he plans on rooting however he cannot install TWRP, only boot it using ADB. The combination of Magisk and TWRP causes a bootloop.
Click to expand...
Click to collapse
Understood on the magisk / twrp thing, but regarding the factory image, that is exactly what I was going. The problem presents even after doing that. That's why it's so puzzling.
Edit: it's admittedly a very long post, but if you look at the section that's numbered, you'll see I'm grabbing the latest factory image for Android 10 and flashing it. Then in the section labeled "Here's What I've Tried" (aka my attempts to troubleshoot) the very first thing I did was flash the factory image (including the wipe) to both Slots and then trying to boot from one slot and then from the other.
Grab an Android 11 package and don't remove the -w flag when installing. The corruption may be persisting because user storage isn't being wiped.
The factory image - NOT OTA - is the only way to fix this short of sending the device to Google for service.
Strephon Alkhalikoi said:
Grab an Android 11 package and don't remove the -w flag when installing. The corruption may be persisting because user storage isn't being wiped.
The factory image - NOT OTA - is the only way to fix this short of sending the device to Google for service.
Click to expand...
Click to collapse
Why would it be any different when I wipe with Android 10 or Android 11? I flashed the latest Android 10 factory image to the phone *with* the -w flag as mentioned in my "here's what I tried" section. I even went so far as to force the phone to Slot A with the "set_active" command, and then set_active Slot B and flashed the factory image (not the OTA) again. After doing that, the one slot will boot just fine while the other gives the error. If I change it up and flash Slot B first and then Slot A the same thing occurs, just in reverse (the slot that booted before throws the error while the slot that threw the error before now boots.)
My initial post explains why I recommended an Android 11 ROM (updated radio). Any of them will of course work, but that's beside the point. Try using ADB to format the partitions and see if that resolves the issue. Otherwise contact Google, as I can't think of anything else that would be blocking you.
I had this same issue and Flashing Android 11 on both partitions (without removing the -w command) resolved it.
I first booted into Recovery Menu and wiped both slots. Then downloaded the factory image (not ota) and flashed each slot separately wiping the device after each flash in recovery menu. it's the only way to fix this just like user @Strephon Alkhalikoi
If that doesn't resolve it then you have an issue that's more serious and will require a repair of some sort (not necessarily hardware).
Good Day All, I've seen a few thread regarding this but nothing stating what causes it to happen. Can anyone provide any insight?
I was about to perform a reflash of my rom but didn't even reach that far.
I restarted phone to recovery
Was going flash a firmware before the rom flash but decided to switch from slot a to b cuz i wasn't sure if the firmware is a global thing or per slot
Changed slots and restarted to recovery
Noticed no prompt for decryption key and my data/media was gone.
Changed slots again without doing anything and restarted (TWRP prompted no OS found)
After the recovery started again no prompt for decryption key again and no data
Figured twrp loaded badly or something. Restarted to recovery one more time
Phone did not boot to recovery. Keep bootlooping to fastboot
Attempted to reflash TWRP when I encounted the error "Failed to load/authenticate boot image"
After a quick google the solution seemed to be the flash over the stock rom via miflash and start over which I unfortunately did
While the solution worked. Does anyone have any clue why this might've happened so I can avoid it in the future? I don't think the Rom matters but I was running Arrow-v12.1-alioth-OFFICIAL-20220819-VANILLA.zip and the recommended firmware V13.0.4.0.SKHMIXM
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/