Database Info

[Q] Stuck in TWRP (Bricked?)

Hi Guys,
Yesterday I installed the new TWRP 2.7.1.0. and that is when the problems started. Everytime when i loaded TWRP my screen got messed up and i got a split screen (At that time my ROM worked). So I tried to get back to a older TWRP, after a couple of tries i finally installed 2.4.4.0. But then I couldn't acces my internal memory nor my sdcard through TWRP(The ROM still worked fine). So i tried CWM, other TWRP's, still the same issue. To keep the story short, I eventually pressed on the WIPE button in Recovery ... And now I am stuck in TWRP. I can't load any zip files.. Is there any hope?
Tab: TF300T

A small update. After some trial and error i got my rom running again and i can also get in to recovery (Power button + volume down). Now I have erased the old TWRP with "fastboot erase recovery". But now I can't install a new recovery? I tried flashing a recovery and I am getting the messages "sending recovery ok", "writin recovery ok". But i don't see the loading bar on the tab...

I feel lonely here hehe.:laugh:
I resolved the issue and got my tablet running again, with the following steps:
Download your appropriate lates firmware from Asus (WW, US etc.) and extract the zip twice so you have your blob file
http://support.asus.com/download.aspx?SLanguage=en&m=ASUS+Transformer+Pad+TF300T&os=8
Install your device drivers if needed (i used Google SDK ones) (and as a Tip Win8 sucks for Fastboot stuff so try to get Win7 Vista XP for this)
If the PC doesn't recognize your tab, then try installing the universal naked drivers:
http://forum.xda-developers.com/showthread.php?t=2263822
Guide: http://forum.xda-developers.com/showthread.php?t=2139767
Reset your device with a paperclip/needle (about 2 cm down of your sdcard slot) and hold vol-down to enter fastboot
fastboot erase system
fastboot erase recovery
fastboot erase userdata
fastboot erase boot
fastboot erase misc
fastboot erase cache
fastboot -i 0x0B05 flash system c:\adb\TF300t\blob (this is my path - your's may vary depending where you stored your blob) ((also this was the first time i saw the loading bar while flashing)*
fastboot -i 0x0B05 reboot
* it also took a lot longer as it should:
C:\>fastboot -i 0x0B05 flash system c:\adb\TF300t\blob
erasing 'system'...
OKAY [ 1.695s]
sending 'system' (800935 KB)...
OKAY [133.121s]
writing 'system'...
OKAY [153.973s]
finished. total time: 288.789s
All credits to - Buster http://forum.xda-developers.com/showpost.php?p=44244313&postcount=12

Bricked shield Tablet, fastboot only works.

Going through some of the threads here got me as far as being able to use fastboot on my bricked Shield.
I would like to ask if anyone can give me some pointers what to try next.
The previous owner tried to flash Lineage OS onto the Tablet using CWM but this failed and he probably wiped some needed partition.
I tried to flash new partitions and this works but I can not start the Shield and it won't boot into CWM. The strange thing is that I tried flashing TWRP and even though that started it did not boot through. And after a simple Shield reboot the CWM logo popped upmagain.....:confused
I was convinced I could fix this but I am beginning to think that this Tablet is a goner...
Any thoughts would ne appreciated.

What happens if you download an original recovery image from Nvidia for your model, and flashboot flash all 5 (recovery, boot, system, userdata, blob)? Do you get any fastboot errors? If the partition structure is corrupted, you'll see some sort of error message.
If the blob is messed up sometimes TWRP won't start. I suggest getting a factory image and trying again, then giving it a long time to boot. Once mine took 20 minutes at the Nvidia screen.

I did try flashing the original image from Nvidia including the other 4 images. One of the first things I tried. I woyld like to get it back to factory default. This went without issues an no errors. I might not have given it enough tine to but but still CWM seems to be on.
Will give it another try and post a screenshot.
Sent from my SM-G935F using Tapatalk

Here is a dump of the flash log. After flashing I reboot and the CWM logo pops up after a few minutes and gets stuck.
D:\Downloads\Shield Fix\Drivers\ADB FastBoot\Minimal ADB and Fastboot>fastboot flash recovery recovery.img
target reported max download size of 100663296 bytes
sending 'recovery' (9758 KB)...
OKAY [ 0.384s]
writing 'recovery'...
OKAY [ 0.320s]
finished. total time: 0.709s
D:\Downloads\Shield Fix\Drivers\ADB FastBoot\Minimal ADB and Fastboot>fastboot boot recovery.img
downloading 'boot.img'...
OKAY [ 0.394s]
booting...
OKAY [ 0.017s]
finished. total time: 0.417s

Think it is done for, after flashing TWRP numerous times it let me get to the start screen for TWRP it then hangs. When you reboot the Shield and want to go to the recovery again you get the dead android.
PS. I can sometimes get into TWRP but it fails on everything I do. Would there be a terminal solution for this? Like re-creating partitions?

Unlock your bootloader?
Sent from my ZTE A2017U using Tapatalk

It is already unlocked I am afraid.
Sent from my SM-G935F using Tapatalk

sn0r said:
It is already unlocked I am afraid.
Sent from my SM-G935F using Tapatalk
Click to expand...
Click to collapse
Try to flash the attached file. Remember to unzip it first! Flash with:
"fastboot flash dtb tegra124-tn8-p1761-1270-a04-e-battery.dtb"

Flashed the battery file and did another flash of NVIDIA's recovery image and even-tough it says everything is flashed correctly when I reboot I get the CWM logo and nothing more. When I do get into TWRP and try to flash a ROM I get messages errors like attached.

sn0r said:
Flashed the battery file and did another flash of NVIDIA's recovery image and even-tough it says everything is flashed correctly when I reboot I get the CWM logo and nothing more. When I do get into TWRP and try to flash a ROM I get messages errors like attached.
Click to expand...
Click to collapse
Then my guess would be some problems with the internal storage which may not be repairable.

Using fastboot try the following
Fastboot erase cache
Fastboot format cache
Fastboot format userdata
Make sure your tablet is in bootloader mode first though.
Sent from my pa_osprey using Tapatalk

Phone bootlooping on Mi logo after updating firmware, unable to go into recovery

I was using official Lineage 14.1 on Lollipop bootloader with firmware libra_miui_v8120_fw_patch, then today stupidly decided to update firmware with libra-firmware_miui9-7.8.21_7.0.zip which is probably for Nougat bootloader. Now I am unable to go into recovery and also when trying to flash recovery through fastboot I end up with this:
Code:
fastboot flash recovery twrp.img
target reported max download size of 536870912 bytes
sending 'recovery' (40704 KB)...
OKAY [ 1.343s]
writing 'recovery'...
FAILED (remote: Partition flashing is not allowed)
finished. total time: 1.362s
So can't even flash recovery. Fastboot oem unlock ends up with this:
Code:
FAILED (remote: Token verification failed, reboot the device)
finished. total time: 0.031s
tried also flashing logo.bin into bk2 just to verify if partition is logged and end up with same issue as with recovery, apparently bootloader locked:
Code:
fastboot flash bk2 logo.bin
target reported max download size of 536870912 bytes
sending 'bk2' (9591 KB)...
OKAY [ 0.329s]
writing 'bk2'...
FAILED (remote: Partition flashing is not allowed)
finished. total time: 0.341s
Is there any way to flash through fastboot just firmware and get back to where I was before screwed update so I don't need to go through flashing fastboot MIUI ROM, losing all my data in phone and setting up phone from scratch? At least in worst case I hope that's an option and it would work just to flash old libra_images_6.1.7_20151221.0000.11_5.1_cn_b09dac70a0, then do oem unlock flash TWRP and the go to lineage, as i did without official unlocking before, but I would rather avoid this since I have still some data not backed up in the phone (luckily i backed up photos just before flashing).
EDIT: Or is there a way to at least back up my data out of phone through fastboot?
EDIT 2: according google results not possible to do backup through fastboot and according fastboot oem device-info it's locked bootloader, so back to square one, losing files, grr and start from scratch

https://www.google.ro/amp/s/forum.x...-unlocking-mi4c-bl-verification-t3336779/amp/
Steps 2 to 9. It should work.
Might be another way to save your data but I didn't found one. Maybe your pc will se your folders in fastboot so you can save the data.
Sent from my Mi-4c using Tapatalk

You can also try to unlock the bootloader the official way, then install TWRP and flash a lollipop firmware zip with the lollipop bootloader and try to boot your ROM that way. The zip floats around in one of the ROM threads.

cezarmed2 said:
https://www.google.ro/amp/s/forum.x...-unlocking-mi4c-bl-verification-t3336779/amp/
Steps 2 to 9. It should work.
Might be another way to save your data but I didn't found one. Maybe your pc will se your folders in fastboot so you can save the data.
Sent from my Mi-4c using Tapatalk
Click to expand...
Click to collapse
yeah, I did that as usual when unlocking unofficially, but there is no way to see your data, though in miflash it says in bottom "save user data" but nothing was saved, I looked through all phone, can't find it anywhere

OK, I noticed another issue, my available space significantly shrank. I guess it's because during fastboot oem edl flashing fastboot MIUI dev ROM through miflash I left "keep user data" checked instead erase, hoping I can recover them somehow.
Now Settings/Storage shows me that my System takes 21GB out of all 29GB, which is nonsense, since it's pretty much fresh system with few apps and little data used.
So my question is, can I somewhere find my original user data taking all this space and manage them? Or is user data partition (internal storage) somehow corrupted and I should just format it and this should hopefully fix problem with lack of free space (although Settings are showing System is taking all the 21GB)? In Mixplorer Internal storage is showing capacity 7.75GB and Root 1.82GB, so I would think it's corrupted internal storage which should be formatted, although best would be if original data would be somewhere hidden and I could just delete them manually.
EDIT: SOLVED - go to TWRP / Wipe / select Data / Repair button / Resize / and partition was properly resized from 7900MB back to 26136MB without loss of current data, of course original data from before are gone, but I am already over it.

Stuck in fastboot after using fastboot rom

One plus 7 pro, European version
So i was running Lineage OS on my phone for some time now (latest base update i did was to ob1 as far as i am aware), when there was an update lately
I installed it as normal, but the phone would not get past the boot animation and kept restarting, so i went back to the other slot to see if that still worked, but it only had a laggy boot animation, which never booted
I then installed the previous version that i was running before the update back to the other slot, hoping it would solve the problem of not booting (that worked before already) but it still did not boot
I saw someone post they had 10.3 installed as base so i restored the ob1 installation with a fastboot rom i still had on my hard drive, but upon finishing the phone just went into crash dump mode showing
dm-verity device corrupted force dump
kernel_restart
I tried another install just to be sure, but same result
I then tried flashing twrp to the boot partition to at least get there, but the phone just went straight to fastboot upon doing that
Fastboot boot still seems broken and just shows
D:\Minimal ADB and Fastboot>fastboot boot tw.img
downloading 'boot.img'...
OKAY [ 1.228s]
booting...
FAILED (remote: Failed to load/authenticate boot image: Load Error)
finished. total time: 1.346s
I searched around if there were other ways to install twrp from fastboot, and found this tool (https://forum.xda-developers.com/an...g/apk-img-dat-br-one-click-decompile-t3886057) that promises to unpack and repack the boot.img, so i hoped i could use that to manually add twrp to it, but it failed to unpack the file
Next thing i found was this MSM tool post (https://forum.xda-developers.com/oneplus-7-pro/how-to/msm-tool-guac-t3934691) instructed to hold volume up and down for 5 seconds before connecting the phone to a pc, and the program actually picked it up, however the phone started itself after a few seconds and went back to crashdump mode
At this point i'm seriously out of ideas, does anyone else have other ideas that i missed?
Does anyone have a boot img with twrp?

keep trying the MSM tool. it WILL work.
if you can get into fastboot again, type in fastboot reboot edl in ADB

Luke JC said:
Fastboot boot still seems broken and just shows
D:\Minimal ADB and Fastboot>fastboot boot tw.img
downloading 'boot.img'...
OKAY [ 1.228s]
booting...
FAILED (remote: Failed to load/authenticate boot image: Load Error)
finished. total time: 1.346s
Click to expand...
Click to collapse
This is indeed what typically shows for an error when fastboot boot isn't working. Probably due to using an older fastboot ROM. I'd try to use a newer fastboot ROM, or you can flash a patched boot image, which is how the phone was being rooted before fastboot boot was fixed:
https://forum.xda-developers.com/on...isk-patched-boot-image-oneplus-7-pro-t3964345

If I recall correctly, you can't fastboot boot with android 10.

[Q] HELP! -> Boot loop / No USB Debug / Encrypted / No Root / Can't Flash or Reset

Hi all,
I have got a N5 that is not booting (infinite boot animation loop). It's bootloader is unlocked and I can push stuff via ADB so I am assuming eMMC is good.
Also, USB debugging is OFF, phone is ENCRYPTED and NOT rooted.
I can't mount or modify /data and /persist partitions.
I tried reformating with ext2 to destroy encryption but it is not working. I also tried dd method but was unsuccessful.
I am not interested in recovering or rescuing anything from the phone.
Currently trying to figure out how to activate download mode so I can reflash everything using LG Flash tool.
Thanks in advance
EDIT: Bootloader is unlocked but I can't root the phone with wugfresh's nexus root toolkit.

The encyption can disable only with command fastboot flash userdata userdata.img
The userdata.img you can find in the Google OEM ROM Google M4B30Z
It requires the SDK Platform Tools is installed SDK Platform Tools
You may give a chance and with this http://www.wugfresh.com/

Hi Sant514,
'fastboot flash userdata userdata.img' returns this error:
target reported max download size of 1073741824 bytes
erasing 'userdata'...
OKAY [ 0.460s]
sending 'userdata' (137318 KB)...
OKAY [ 4.511s]
writing 'userdata'...
FAILED (remote: flash write failure)
finished. total time: 5.151s
also tried to format userdata:
fastboot format userdata
Couldn't parse erase-block-size '0x'.
Couldn't parse logical-block-size '0x'.
mke2fs 1.45.5 (07-Jan-2020)
/tmp/TemporaryFile-GqLE95: Unimplemented ext2 library function while setting up superblock
/usr/lib/android-sdk/platform-tools/mke2fs failed with status 1
mke2fs failed: 1
error: Cannot generate image for userdata

This reformating with ext2, I don't think this helped the situation,
so can you give a chance with tool http://www.wugfresh.com/?
No you do not need to root your device with wugfresh. It has a choice about unbrick... unroot and resτore
in factory condition...
The menu-choice is "Back to Stock / Flash Stock and Unroot" and you will select "Current Status=Soft Bricked/Bootloop"

Nexus Root Toolkit is giving me multiple flash write failures so I think the eMMC is dead.
Thanks for the help...

I had a similar major crash with my D820 (Nexus 5, US version) last month after trying wireless charging with an aftermarket back cover (overheated followed by kernel panic green screen of death). Infinite reboots. Couldn't get past Google logo. Flashed the factory image without the "-w" option which wipes user data, no joy. I figured I was screwed.
So flashed factory image 4.4.4 totally (-w left in the flash-all.bat script). Then flashed the last 2016 factory image (M4B30Z), and it came back. I hate having to reinstall apps (including discontinued ones via the APK borrowed from my other Nexus device), but it's actually good to clean out old cruft.
https://developers.google.com/android/images#hammerhead
As you probably know, you only need to install the Android SDK, Platform-tools (fastboot, adb, etc), boot into bootloader (run "fastboot devices" to see the phone is connected), and the flash-all.bat file will do the rest. Don't interrupt it, the "warning: ... .sig not found" and "sending System.img" steps will take a while. On my phone, the whole script can take 2 mins.
I've never relocked the bootloader after unlocking, but that could resolve the encryption issue .. but IDK, I've never done it.
Good luck.