Shield tablet bootloops after flashing Custom ROM - Shield Tablet Q&A, Help & Troubleshooting

Shield tablet neverending loop
Hello guys,
Today I've tried flashing my Shield Tablet using Shield Custom ROM guide from by cots from gbatemp.net forums (can't post links).
Despite doing everything carefully, step by step, my Shield is now rebooting forever showing only one screen and rebooting again.
Unfortunately I can't post a picture, because forums rules don't allow me, so I wrote down the text from TWRP:
E:Could not mount /data and unable to find crypto footer.
E:Unable to mount '/data'.
E:Unable to recreate /data/media folder.
Updating partition details...
E:Unable to mount '/data'.
...done
E:Unable to mount storage.
E:Unable to mount /data/media during GUI startup.
Full SELinux support is present.
E:Unable to mount /data/media/TWRP/.twrps when trying to read settings file.
Processing AOSP recovery commands...
E:Unable to mount '/data'
--Wiping Data Partition...
Formatting Cache using make_ext4fs function.
E:Unable to mount '/data'
--Data Partition Wipe Complete!
Done processing script file
aaaaand it reboots.
Pressing "Home" and/or "Back" button at that TWRP screen does nothing, Shield is still rebooting to that screen over and over again.
Help would be greatly appreciated. Any ideas?
Best regards,
Łukasz

I had the same problem; the same thread that you referred to had a post yesterday on resolving this issue. This worked for me.
Re-do all the steps except that before doing the TWRP flash, do a fastboot -w.

Can you boot into twrp? The sequence is: Volume DOWN (keep pressed) + Power (click and release keeping VDOWN pressed)
This should give you access to bootloader mode, where you can eventually reboot into recovery or enable fastboot protocol. So if twrp works you should be able to use the "format" which will fix your corrupted filesystem. Once you've done that you can restore your official OTA, copy your custom rom files again somewhere inside the now-restored filesystem, go back into recovery and flash again (just wipe system, cache and dalvik, nothing else).
If you cannot access twrp, once in bootloader mode you can enable fastboot and flash twrp again via adb from your pc.

Just to clarify, once you're in the bootloader, fastboot is ALREADY enabled and you will need to use fastboot, NOT adb, to flash anything.

Related

[Q] My Internal sdcard is corrupted! Please Help!

I Think my Internal sdcard is corrupted!
Please Help! Reflashing android won't work. I think the partition is corrupted!
Device: Google Nexus 5
Original OS: Android 5.1.0_r1 (LMY47D)
Recovery: TWRP 2.8.6.0
One day I turned my phone off, and later i decided to go into recovery. I believe I went inside Advanced Options and clicked "Fix Permissions." Then I proceeded to reboot. I was busy at the time, so when I remembered about my phone, I saw that it was still booting. It had been at least 30 minutes so I knew it was in a bootloop. I decided to go back into recovery and reflash the system.img onto it. No luck. I realized I had to try flashing the entire Nexus image (using the flash-all.bat). The phone would still not turn on. I tried flashing different versions of android, and here are my findings:
Android 5.1.0_r3, 5.1.0_r1, 5.0.1: all cause my phone to not be able to boot up (stuck on the 4 color flying animation)
Android 4.4.4, CyanogenMod (cm-11-20141008-SNAPSHOT-M11-hammerhead.zip): Allow my phone to boot up.
However, after I found that I could boot onto Android 4.4.4 and CyanogenMod, I realized that I could not get access to the sdcard!
Here are my findings:
When I go to the phone's root folder, I see a FILE called "sdcard"
When I go to \storage, I see a FILE called sdcard0
When I open camera, the app crashes (possibly because it stores pictures on the sdcard).
I tried to delete these files when I had root access with CyanogenMod but the file manager said "can't delete file." When I am in recovery mode (TWRP) however, I can see the sdcard folder and the contents. Just through every system boot, the sdcard is inaccessible.
After I realized that the problem wasn't due to the data on my phone (after flashing many system images), I realized my data partition might be corrupted. Then I went to this site and followed the directions: http://forum.xda-developers.com/goo...o-repairing-corrupted-data-partition-t2577447
The e2fsck command didn't do anything as cmd said "The superblock could not be read or does not describe a correct ext2 filesystem."
Afterwards, my friend told me to try mke2fs /dev/block/platform/msm_sdcc.1/by-name/userdata
I typed that in adb shell and something happened. I started processing blocks or something. Unfortunately now, I am unable to mount the data partition at all. I am also unable to flash the userdata.img onto my phone through fastboot.
UPDATE: When I open up twrp recovery and look in the log I see the following:
E: Could not mount /data and unable to find crypto footer.
E: Unable to mount '/data'
E: Unable to recreate /data/media folder.
Updating partition details...
E: Unable to mount '/data'
E: Unable to mount '/cache/
E: Unable to mount '/persist'
...done
E: Unalbe to mount storage.
E: Unable to mount /data/media during GUI Startup.
E: Unable to mount '/cache'
Full SELinux support is present.
E: Unable to mount '/cache'
E: Unable to Mount '/cache'
E: Unable to mount /data/media/TWRP .twrps when trying to read settings file.
E: Unable to mount '/data'
MTP Enabled
Anyone know how to fix this? Please help, I owe you so much if you can solve this! Reply to me if you're able to help, I'm also new to xda so I don't really know how messages work. Thanks!
Try taking it out and putting it back in. It happened to me too.
mygoldeneye said:
Try taking it out and putting it back in. It happened to me too.
Click to expand...
Click to collapse
By sdcard I mean the internal sdcard (/storage/emulated/0). Nexus 5 does not have an external sdcard slot anyways.
So you are saying you have no apps, no widgets, nothing... /storage/emulated/0 is your main storage which INCLUDES your system files (unless you have a phone or tablet that has a separate internal SD card - would be /storage/emulated/1 ... I am guessing)

[Q] Partition destroyed after power loss

Hi everyone,
today i tried to update my CM11 to the newest CM12 Version. I booted into TWRP recovery and made a full Wipe. While doing this, my device had something like power loss, so the wipe could not finish.
Now the device doesn't boot anyway, after Power on it's booting into fastboot mode. The recovery isn't able to start. It is possible to use ADB and Fastboot. Using "fastboot boot /....../recovery.img it is possible to boot an recovery. The TWRP Recovery displays:
E:Unable to find partition size for '/recovery'
E:Unable to find partition size for '/boot'
E:Unable to find partition size for '/misc'
E:Updating partition details
E:Unable to mount '/cache'
E:Unable to mount '/data'
E:Unable to mount '/sytem'
...done
E:Unable to mount storage
E:Unable to mount /sdcard during GUI startup
E:Unable to mount '/cache'
Full SELinux support is present
E:Unable to mount '/cache'
E:Unable to set emmc bootloader message.
E:Unable to mount /'cache'
E:Unable to mount /sdcard/TWRP/.twrps when trying to read settings file.
MTP Enabled​
The "repair file system" option in TRWP Recovery doesnt work.
After several hours reading threads about similar problems i don't know what to do.
How can i repair the file system tables to reinstall the CM12 or any other ROM?
Hopefully
DragonGuard
I think, i have an idea.
What about to rewrite the complete partitions on my Sensation using adb shell and then rewrite with the partitions? Could that work?
I read an article with an similar problem here: cyanogenmod.org
The problem was that I managed to screw up the partitions on my internal storage card, so basically nothing would work properly. I could still get into recovery, though. That's key.
Here's what you'll need:
Working recovery, basic knowledge of adb & the shell
Parted (download here)
stock PB31IMG.zip
Note also that I had run unrevoked forever (so my phone was S-OFF) ... I'm not sure if that's required or not.
So, grab parted from the link above. Now you need to extract the individual binaries from the .zip (the 6 files in the sdparted folder within the zip), ideally to your android-sdk\tools directory. Now push all 6 files (adb push [file] /sbin/). Next, we need to make them useable, so go into the shell (adb shell). Change to your /sbin/ directory, and run: chmod 0755 <file> on each of the 6 files.
Now, we need to fix the partitions. This is assuming that the partitions are there, just the wrong format (which is what happened to me .. I accidentally made them FAT32 instead of ext). So, run the following: parted /dev/block/mmcblk0 mkfs ext2. It will ask if you want to continue, hit yes. When it asks for the partition number, enter 1. Next, when it asks for the format, enter ext2. Let it do its thing. Now, once it's done, run parted again. This time, enter partition 2 (everything else is the same).
Once all that's done, your recovery program should be able to mount both the /data and /cache partitions. If that's true, you're pretty much done! One thing I found was that I couldn't directly install a new OS (I tried both Cyanogen and Ultimate). In both cases, it would look for stuff in the davik-cache that it couldn't find, so something wasn't installing correctly I think. So, if that happens, flash back to the stock PB31IMG.zip (put it in the root of your /sdcard/ and let hboot install it), and then root your phone anew. That's what I ended up doing.
Again, huge credit for this goes to -Steveo- and ciwrl for helping me figure out which partitions were the right ones (and for supplying parted, which I hadn't been able to find anywhere). If something doesn't end up working, just drop me a pm and we'll see what we can do.
Click to expand...
Click to collapse
Today i would need parted for ext4 partitions and i need to know where on the internal storage i have to write which partition. Is this a possible way to repair the partitions?
Hopefully
Bump
I'm having the same problem, my recovery log shows exactly the same. Have you found a solution yet?
Hi,
i am sorry, but i haven't found any solution yet. I am looking for an HTC Sensation to pull the emmc Data system Files and rewrite it on my broken HTC Sensation. I need the /dev/block/mmcblk0 etc. files to try. In my /dev/block/ folder are only "loop" files located, i think they are part of my problem.
Greetz

Facing issues in rooting Nexus 5 for Marshmallow

Hi Guys,
I was trying to root my Nexus 5 on marshmallow. I was able to run all the TWRP commands by connecting the device. I was able to run all the commands but during bootup I am getting below errors.
Error:
E: Unable to recreate /data/media folder.
E. Unable to mount '/data'
....done
E. Unable to mount storage.
E. Unable to mount /data/media/TWRP/.twrps when trying to read settings file.
Processing AOSP recovery commands.
E. Unable to mount '/data'
--- Wiping Data Partition .....
E. Unable to mount '/data'
Formatting Cache using make_ext4fs function.
-- Data Partition Wipe Complete!
Done processing script file
Renamed stock recovery file in /system to prevent
the stock ROM from replacing TWRP.
Please help guys phone isn't starting up, everytime it boots up and shows this errors and then boots again. :crying::crying:
parasmani said:
Hi Guys,
I was trying to root my Nexus 5 on marshmallow. I was able to run all the TWRP commands by connecting the device. I was able to run all the commands but during bootup I am getting below errors.
Error:
E: Unable to recreate /data/media folder.
E. Unable to mount '/data'
....done
E. Unable to mount storage.
E. Unable to mount /data/media/TWRP/.twrps when trying to read settings file.
Processing AOSP recovery commands.
E. Unable to mount '/data'
--- Wiping Data Partition .....
E. Unable to mount '/data'
Formatting Cache using make_ext4fs function.
-- Data Partition Wipe Complete!
Done processing script file
Renamed stock recovery file in /system to prevent
the stock ROM from replacing TWRP.
Please help guys phone isn't starting up, everytime it boots up and shows this errors and then boots again. :crying::crying:
Click to expand...
Click to collapse
It's not nexus 5 forum and reflash stock rom again..
Sent from my GT-I9500 using XDA Free mobile app

Nexus 5 turns on but cannot access anything

I have a Nexus 5 rooted and running Catacalysm 5.1.1 Lollipop (Sep 27, 2015 Stable final release)
Yesterday while I was on my phone all of a sudden it froze for a couple of seconds and then restarted.
When it booted it says "To start Android, Enter your Password"
I can type in literally any password and it will go to the next screen and say
"Decryption Unsuccessful"
The password you entered is correct, but unfortunately your data is corrupt.
To resume using your phone, you need to perform a factory reset. When you set up your phone after the reset, you'll have an opportunity to restore any data that was backed up to your google account.
Click to expand...
Click to collapse
Then the only thing I can select is "reset phone."
The thing is I never encrypted my phone. I don’t want to do a factory reset as I have some things in my phone that I need
When I go into recovery this is what I get:
E:Could not mount /data and unable to find crypto footer.
E:Unable to mount ‘/data’
E:Unable to recreate /data/media folder
Updating partition details…
E:Unable to mount ‘/data’
…done
E:Unable to mount storage.
E:Unable to mount /data/media during GUI startup.
Full SELinux support is present
E:Unable to mount /data/media/TWRP/.twrps when trying to read settings file.
E:Unable to mount ‘/data’
MTP enabled
E:Unable to mount ‘/data’
Click to expand...
Click to collapse
Also the internal storage shows 0 MB.
When I go into backup these are the sizes that are shown:
System (882MB)
Data (0MB)
Cache (12MB)
Boot (22MB)
EFS (6MB)
Click to expand...
Click to collapse
I’m using TWRP
I was wondering if anyone ran into this issue or knew anything about what is going on in my phone.
Is my phone dead? Can I get it to work again? Is there any way I can access the internal storage and retrieve my files?
Any help would be appreciated. Thank you

Boot Loop after Installing TWRP

Hello, I am trying to root my phone for the first time and am running in to an issue where after I flash to TWRP, as soon as it boots in to TWRP is throws an error which quickly flashed on the screen before it restarts and does this in a loop. Here is information on my phone and the steps I have taken:
FASTBOOT MODE
PRODUCE_NAME - hammerhead
VARIANT - hammerhead D820 16GB (LG Nexus 5)
HW VERSION - rev_11
BOOTLOADER VERSION - HHZ11d
BASEBAND VERSION - M8974a-2.0.50.2.30
SECURE BOOT - enabled
LOCK STATE - unlocked
Android version: M (6.0.1)
Steps:
Turned on developer options
Enabled USB debugging (via LG driver found on https://forum.xda-developers.com/go...ide-nexus-5-how-to-unlock-bootloader-t2507905)
"fastboot oem unlock"
fastboot flash recovery twrp-3.1.0-0-hammerhead.img
Now, if I'm in the bootloader and select "START" it goes in to the TWRP splash screen, then throws an exception:
E:Could not mount /data and unable to find crypto footer.
E:Unable to mount '/data'
E:Unable to recreate /data/media folder.
Updating partition details...
E:Unable to mount '/data'
...done
E:Unable to mount storage
E:Unable to mount /data/media during GUI startup.
Full SELinux support is present.
E:Unable to mount /data/media/TWRP/.twrps when trying to read settings file.
Process AOSP recovery commands...
E:Unable to mount '/data'
-- Wiping Data Partition...
E:Unable to mount '/data'
Formatting Cache using make_ext4fs function.
-- Data Partition Wipe Complete!
Done process script file
Click to expand...
Click to collapse
My end goal is to root... but if I can't root and can get the phone back to how it was before... that wouldn't be bad Thanks for reading.
I say restart from scratch. Update to the latest bootloader by flashing the latest factory image(M4B30Z) with instructions found here: https://developers.google.com/android/images#hammerhead
Keep the bootloader unlocked then flash twrp and see the result.

Categories

Resources