I was running the latest CleanRom on my nexus 7 tablet and it randomly rebooted and stopped working. The tablet now doesn't want to boot into the OS. When i boot into TWRP recovery mode i need to wait at least 20 minutes before the TEAMWIN splash screen goes away and finally boots into the TWRP recovery interface. I'm trying to reflash a rom but it fails everytime, in doing so i'm prompted with a log message that says "/system, /cache" was unable to mount.
My biggest concern right now is getting all my user data such as music, document, books, movies off of my tablet so i can restore the tablet to factory defualt. Is there a way to recover such files? (~26GB of Data)
This is what i have tried with no luck:
TWRP backup of user data to OTG USB
adb install of factory image. (-w removed from bat file)
Nexus root toolkit 1.7.9 backup of virtual SD. (says successful but backup size is 0MB)
Related
Hey so here goes. Stupid me went to perform a factory restore from within in android (stock 4.2.2 rooted) and I forgot that I had installed TWRP (currently 2.7.0.2) and when the tablet rebooted to wipe everything it booted to TWRP and tried to wipe where it promptly failed with "Unable to mount /data, /internal storage, /system, etc.
So here's where i'm at. The tablet will boot to recovery but will not let me wipe anything and will not boot to android.
When i attempt to restore a nand backup it will restore then error at the end with "Unable to mount /data" and again, the tablet will not boot.
I downloaded the TWRP 2.7.0.2 update zip and flashed over my existing recovery to see if that helped, no dice.
Now i'm trying to use the method found here on XDA to restore to factory using Download Mode and everything goes well until I get to the step where i actually flash the KDZ file I get this message:
Please install CSMG B2C Client TOOL.
Select Tool > B2C Client Setup Menu.
I have followed the instructions to the letter minus putting my tablet in USB debugging mode (can't boot the tablet, no Debugging Mode)
I have no idea where to go from here.
I should mention I also tried this on Windows 7 64 bit and Windows 8.1 Pro 64 bit.
Edit: I'm not sure what wizardry has happened but it finally worked! That was terrifying for a while there.
deletedhttp://www.droidviews.com/how-to-restore-lg-g2-to-stock-firmware/2/
First some details: M9, 5.0.2 w/ Sense 7, TWRP 2.8.6.1, S-Off. I have two nandroid backups on my micro SD card
I tried flashing the experimental xposed for 64 bit lollipop found [here](http://forum.xda-developers.com/xposed/xposed-android-5-1-successfully-t3074586). I waited 10 minutes but it never booted past the "HTC One Powered by Android" screen.
I booted into recovery and connected my phone to the computer. I was going to use adb but it couldn't detect the device in either bootloader, download, or recovery mode (yet it showed in Device Manager as HTC One), so I used windows file manager to place [this](http://forum.xda-developers.com/xposed/xposed-framework-disabler-incase-t3100669) on my sd card, which is supposed to disable xposed for lollipop, which I flashed in recovery. I tried booting again but no luck.
I went back to recovery, and decided to restore one of my backups. It always error-ed because it was mounted as read only, and I can't figure out how to change that in the Mount section of TWRP.
I found [this](http://www.theandroidsoul.com/htc-o...m-as-read-write-in-2-8-6-0beta-version-76248/) terminal command online "mount -t ext4 /dev/block/bootdevice/by-name/system /system", and after using it was able to restore one of my nandroid backups (I restored System, Boot, Data, and System Image). However, this did not let me escape the bootloop.
So I went back to recovery and intended to try again. I factory reset in recovery, and attempted to restore using that nandroid backup using just System, Data, and Boot. However, it wouldn't (mount problem). I executed the aforementioned terminal command again, and it still wouldn't let me restore (mount problem). So I entered the same terminal command again and it failed because "the device is busy."
I'm really at a loss for what to do right now.
How old are those nandroids? Did you do them with the 2.8.6.x betas? Some people have had trouble restoring nandroids from the betas in 2.8.6.1.
You might try reflashing your rom, or flashing a full stock firmware package.
leadCactus said:
First some details: M9, 5.0.2 w/ Sense 7, TWRP 2.8.6.1, S-Off. I have two nandroid backups on my micro SD card
I tried flashing the experimental xposed for 64 bit lollipop found [here](http://forum.xda-developers.com/xposed/xposed-android-5-1-successfully-t3074586). I waited 10 minutes but it never booted past the "HTC One Powered by Android" screen.
I booted into recovery and connected my phone to the computer. I was going to use adb but it couldn't detect the device in either bootloader, download, or recovery mode (yet it showed in Device Manager as HTC One), so I used windows file manager to place [this](http://forum.xda-developers.com/xposed/xposed-framework-disabler-incase-t3100669) on my sd card, which is supposed to disable xposed for lollipop, which I flashed in recovery. I tried booting again but no luck.
I went back to recovery, and decided to restore one of my backups. It always error-ed because it was mounted as read only, and I can't figure out how to change that in the Mount section of TWRP.
I found [this](http://www.theandroidsoul.com/htc-o...m-as-read-write-in-2-8-6-0beta-version-76248/) terminal command online "mount -t ext4 /dev/block/bootdevice/by-name/system /system", and after using it was able to restore one of my nandroid backups (I restored System, Boot, Data, and System Image). However, this did not let me escape the bootloop.
So I went back to recovery and intended to try again. I factory reset in recovery, and attempted to restore using that nandroid backup using just System, Data, and Boot. However, it wouldn't (mount problem). I executed the aforementioned terminal command again, and it still wouldn't let me restore (mount problem). So I entered the same terminal command again and it failed because "the device is busy."
I'm really at a loss for what to do right now.
Click to expand...
Click to collapse
I have created a guide to install xposed, its in the themes and apps section, called screen off animation.
---------- Post added at 01:54 PM ---------- Previous post was at 01:49 PM ----------
To get back to a functional ROM I would try to install a ROM which matches the firmware that you're on, perform a full wipe of data, android secure, cache and dalvic. You can use the file manager within twrp, also make sure your running the latest beta version of twrp.
You haven't bricked your device it will be recoverable..
Backup your nandroid, wipe everything (full internal storage data, cache, EVERYTHING). If that doesnt work, go to advanced wipe-> check everything and then click on repair as ext4
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've just updated CM13 to the latest nightly using TWRP, but now the system just boots into TWRP - that's whether I select boot system, recovery, or bootloader. I tried restoring from a TWRP backup or another copy of the nightlies zip - it all seems to work fine but doesn't solve the problem. I can connect to the 'recovery' device using adb but adb restart bootloader just loads TWRP again. I've tried wiping first the dalvik/cache, then everything but the internal card, then finally everything but nothing seems to work.
I did get something a little bit like this a few days ago because SuperSU was complaining that I needed to update the binary. I let it do it the way that it suggested one does when TWRP is installed and afterwards couldn't reboot into system, but after a few minutes of frustration sorted things by wiping various partitions.
I attempted to load the full system restore files (cm-13.1-ZNH2KAS29G-crackling-signed-fastboot-74bb753396.zip) using TWRP but that didn't work (I imagine because they're designed to be run via fastboot). I tried loading them via the ADB sideloader option included in TWRP but it failed after a few seconds (I think the message was 'transmitting 0.0x'
I opened that zip and copied the various files to the external card, but I then baulked at installing the image files manually because the only partition option I'm given is boot and my understanding is that each image file should go into its own partition.
The only other potentially pertinent information I can think of:
TWRP keeps reporting "E: Unable to find partition size for '/recovery'"
Has anyone got any ideas please? I had been musing that my next phone would have OTG and NFC, but I wasn't planning to upgrade just yet if I don't absolutely have to.
Have you got it fixed? And if yes - how? I am stuck in a similar situation and can't find a solution for it. Tnx in advance.
So I was updating six rom and phone went into continuous boot. So went into recovery and wiped all but internal memory and reinstalled. Same boot problem. Went into fast boot and pushed another over as well as a vendor image. Tried installing the new rom, beans gaps, super su and same result. I've left the phone for over 20 mins with no result but the boot screen.
I'm having a similar problem.
My status- Unlocked bootloader, twrp accessible, devices not getting detected in fastboot mode by the pc, rooted, restoring using the backup results in a bootloop, correct drivers installed on the pc, superSU and full backup in the mobile.
i cant transfer files since device not getting detected.
my timeline- i followed every instruction on https://forum.xda-developers.com/nexus-5x/general/guides-how-to-guides-beginners-t3206930 and everything went successful, but when it rebooted to the 'Welcome' page (the page which comes when u open mobile for the first time) i restarted my nexus 5x 32gb to recovery mode and then the every boot procedure doesn't complete for several minutes(doesn't go ahead the ball animation)