So just as the title says i decided to root my n7. Everything seemed to go smooth until my nexus 7 was stuck on the boot animation screen for about 20 minutes. I tried doing a factory reset in TWRP and it said wipe failed. I decided to flash CWM instead and do a factory reset but i couldn't. It said error mounting /data. I'm not sure what to do googling around didn't seem to work.
TWRP gave me a message saying SU is not installed after i installed the recovery so i clicked instal SU. I'm not sure if that contributed to my problem or not. Any help would be greatly appreciated.
Ok so i figured this out.
So for anyone who ever gets into an endless bootloop with the inability to wipe data you need to do the following.
1. Download the latest Factory image from google.
2. Exctract the files into your platform-tools folder an run the "flash-all" command this video illustrates it perfectly http://www.youtube.com/watch?v=bsss9e71bKo
3. And you're done! hopefully this helps someone out
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.
I made a very noob mistake today. I was going to factory reset my Oneplus 3 in TWRP (recovery) and flash back to the stock rom but I accidentally checked off everything to be erased... which erased my current operating system, along with the stock rom I was going to install :crying:
Now im stuck with no OS, phone won't boot, can only get into recovery etc etc
I tried connecting it to the computer and clicking MOUNT in recovery, my PC detects it, but when I try to drag and drop the stock rom it just hangs there and the file transfer progress bar doesnt move.
What are my options ?
The phone is rooted
You can use sideload from twrp. Or you can put the zip you want to flash in a usb and flash it via otg.
613BulletProof said:
I made a very noob mistake today. I was going to factory reset my Oneplus 3 in TWRP (recovery) and flash back to the stock rom but I accidentally checked off everything to be erased... which erased my current operating system, along with the stock rom I was going to install :crying:
Now im stuck with no OS, phone won't boot, can only get into recovery etc etc
I tried connecting it to the computer and clicking MOUNT in recovery, my PC detects it, but when I try to drag and drop the stock rom it just hangs there and the file transfer progress bar doesnt move.
What are my options ?
The phone is rooted
Click to expand...
Click to collapse
Put the OOS you want to install on a flash memory and use it as OTG from TWRP
As mentioned above, sideload is the easiest way.
Simply follow the steps here:
https://twrp.me/faq/ADBSideload.html
You can transfer data from a pc in twrp so you have loads of options
Push it with ADB
Ex- "adb push (input_file_name) /sdcard/(output_file_name)"
I will try adb sideloading, i had tried that method a while back for installing a rom and had issues, i have windows 10.
Skinpipe said:
You can transfer data from a pc in twrp so you have loads of options
Click to expand...
Click to collapse
already tried that it wont let me. it detects the phone on my pc, but when dragging and dropping it wont transfer and throws an error saying device could not be found.
613BulletProof said:
already tried that it wont let me. it detects the phone on my pc, but when dragging and dropping it wont transfer and throws an error saying device could not be found.
Click to expand...
Click to collapse
Try reflashing twrp from fastboot
I had the same problem when I was trying to upgrade to OOS 4.0. The phone was stuck at bootscreen. I powered it off by holding power button for 10 seconds. I turned it on again and booted in recovery mode. Then I connected my OP3 to PC and I was able to copy the .zip file into the TWRP folder. In recovery mode I installed the latest firmware from the .zip file.
Maybe I should mention that the OS I'm using is Arch Linux. My PC instantly recognized my phone.
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/