Database Info

Stuck on BlissPop loadscreen. Help.

Hello! I installed BlissPop on my tablet before getting the new one from the callback program. This worked fine for several months, until suddenly the tablet decided not to boot.
The current situation:
The tablet boots onto the Nvidia logo, stays there for about 3 mins, then starts booting BlissPop. The boot is then stuck at the BlissPop animated loading screen. (It does not freeze the tablet or anything like that)
The tablet is not bricked (I think). I do not get the bricked error when checking on serial number. I dont remember which version of BlissPop i flashed over half a year ago.
What I have tried:
1) Flash a new custom ROM through Recovery, installing from zip through adb. I get an error while installing from zip:
- mount: failed to mount /dev/block/platform/sdhci-tegra.3/by-name/UDA at /data: Invalid argument.
- unmount of /data failed; no such volume.
- Patching system image unconditionally
Also, I cannot mount /data or /cache from CWM. Is my partition table messed up?
2) Flash to stock recovery image, through fastboot.
These steps always end up in the same way, nothing has happened during the flashing or installation. The device is still in the same state.
3) I tried installing another recovery type (now using CWM v.6.0.5.0), but I always end up with the old one.
What seems to be the common result on whatever I try, is that nothing happens. I even tried erasing all the data from the tablet, but nothing changes. Still boots into BlissPop and is stuck there. It seems like I cannot write anything to the tablet. Recovery mode (CWM) is also VERY slow, and it takes about 3 mins to get into CWM from fastboot bootloader screen.
Does anyone have any idea what I'm doing wrong, or have any tips for new things to try out?

twrp or CWM saying cant mount any partition TF300T

hELLO,
I tried installing twp and cwm versions from xda/twrp.me/cwm website for T300T and flashed them successfully from FASTBOOT but after I boot into recovery and then, when I try to wipe data/ factory reset, do anything in twrp or CWM, I get error "unable to mount /system /cache/ and every other partition, so I can not flash anything, can not mount any partition or sdcard or emmc or anything and can not copy flash files into tablet from PC while in TWRP CWM or external SDcard. I already enabled USB debugging and everything else in tablet settings but I am unable to mount anything or format anything from TWRP or CWM.
TWRP shows internal memory as 00mb :S
HOw to get pass that error "unable to mount" ??
how to mount so that I can flash custom roms/
REgards
Device info Asus tf300t
Android 4.2.1
Build number JOP4OD.JP_epad-10.6.1.27.5-20130902

Administr4tor said:
hELLO,
I tried installing twp and cwm versions from xda/twrp.me/cwm website for T300T and flashed them successfully from FASTBOOT but after I boot into recovery and then, when I try to wipe data/ factory reset, do anything in twrp or CWM, I get error "unable to mount /system /cache/ and every other partition, so I can not flash anything, can not mount any partition or sdcard or emmc or anything and can not copy flash files into tablet from PC while in TWRP CWM or external SDcard. I already enabled USB debugging and everything else in tablet settings but I am unable to mount anything or format anything from TWRP or CWM.
TWRP shows internal memory as 00mb :S
HOw to get pass that error "unable to mount" ??
how to mount so that I can flash custom roms/
REgards
Device info Asus tf300t
Android 4.2.1
Build number JOP4OD.JP_epad-10.6.1.27.5-20130902
Click to expand...
Click to collapse
If your fastboot still works, please try Kang TWRP 2.8.7.2 from here: http://forum.xda-developers.com/transformer-tf300t/development/recovery-twrp-t3046479.

if the other recovery does not work, you would probably need to reflash stock rom from the asus website, this is due to recovery not being able to identify the partitions without a full boot, if you wiped it from bootloader the whole partition table is messed up and you want to reflash that by using the stock rom. If you need any help on that just pm me.

I have the exact same problem. Not sure about fastboot as so far it has not installed anything. I have twrp 2.5.0.0 .... adb does function and have actually installed KK 6.0 and works fine, but on restart it is back to recovery and no OS.Any help appreciated.
using fastboot all I get is waiting on device and a blinkng cursor.
How can I get Kang twrp on the tf300 with adb commands?

Sorry to sort of hi-jack the OP thread, but my problem is very similar. Here is where I am now tablet sitting at Starting fastboot usb download protocol ... 3 icons with RCK blinking. I ran the following From my sdk platform tools folder.
adb reboot bootloader
it was followed by;
" daemon not running. starting it now on port 5037"
"daemon started successfully"
I then ran the following:
fastboot -i 0x0b05 flash recovery twrp_tf300t_kang_2.8.7.2.img
it was followed by:
sending 'recovery' (7126 kb)...
followed by a white blinking cursor and it just sits there,
Same results if I run it all the same except substituting the blob file instead of the img file.any ideas?

Many Thanks
Many Thanks, go out to gs-crash-24-7 as well to the forums here at XDA, I now have my tf 300 back up and running on the stock JB 4.2.1 rom. Still isn't recognizing my Micro SD card, but that is a problem I think should be easier to solve.
Again, many thanks all.
Took forever to get it to be recognized as a fastboot device with windows 10, but once that happened ( I won't lie, I erased everything many times) well that and me switching to a little 3 ft cord (after so many attemps at adb>fastboot flash staging blob) it is going for now.
Good advice below if your TF300T seems bricked.
gs-crash-24-7 said:
if the other recovery does not work, you would probably need to reflash stock rom from the asus website, this is due to recovery not being able to identify the partitions without a full boot, if you wiped it from bootloader the whole partition table is messed up and you want to reflash that by using the stock rom. If you need any help on that just pm me.
Click to expand...
Click to collapse

Still isn't recognizing my Micro SD card, but that is a problem I think should be easier to solve.
Click to expand...
Click to collapse
Man was I ever wrong about that statement .... still no success getting the tablet to once again recognize external storage at all.
If anyone can help me with the MicroSD/External Storage not being recognized problem, please take a look here.

Thank you all, its all good and working now with recovery file you posted above.
Cheers!

Administr4tor said:
Thank you all, its all good and working now with recovery file you posted above.
Cheers!
Click to expand...
Click to collapse
You are welcome! Good to hear that the issues are solved with the recommended Kang TWRP.
BTW, using the thanks button is greatly appreciated.

Nexus 5 bootloop bricked - CAN'T FASTBOOT/SIDELOAD FLASH - Need QCom TESTPOINT

I had a Nexus5 that was stock, and working.
I unlocked the bootloader and flashed to 31E, using the factory image.
It was OK afterwards. I used
After a week it one day randomly rebooted, and hasn't booted since.
After power on, there is Google screen for ~50sec, and then colour animation for 30+min.
THE PROBLEM - FASTBOOT FAST WRITE FAILURE
I can boot into fastboot. It says its unlocked. I can erase and flash laf, boot .. but Most of them, like recovery, cache, it says
FAILED (remote: flash write failure)
Obviously, if you run the flash-all or anything similar you will get the same thing.
RECOVERY IMAGES - FAIL
It says it can't mount /cache. Mounting system, and then wiping cache spits out 20 mount errors. Factory reset/wiping - same.
fastboot boot with 4 different TWRP boots after 5min to TWRP logo screen, and shows up in adb. I found a CWM recovery that booted,
but had lots of mount errors.
I played around with parted, and make4fs, trying to recreate partitions - no dice.
they are there under block./mmcblk0 - 29 of them. I get errors that journal is outstanding when trying to e2fsck. And trying different superblock didn't work either.
SIDELOADING - FAIL
I tried sideloading from ADB. Doesn't work. Complains about mount points. 0%.
LG DOWNLOAD MODE - NOT EXIST??
I cannot boot into "LG" Download mode. 2 other LG phones boot immediately into download , so I'm 99% sure the cable or PC, or "static" is not the issue.
QDLOADER - NO EFFECT
Finally, Qualcomm USB QDLoader - I got it working in Win10 x64.
To boot device into QDLoader, it has to be booting up normally to Google screen, and you are holding all buttons for 8+ sec, until you see it in Device Manager.
I tried both the 16GB and extracted TOT flash, and they completed, but phone is the same. Still cannot flash factory image.
I tried running RAM test. Success. EMCC read and erase test are OK, but "rwrite" test fails immediately (write protected???)
So, I tried flashing the system, cache, misc, persist, modem and recovery from BoardDiag. They completed, taking 30min for system and 20min for cache.
Still fails.
QFIL - WHERE FILES?
Where do I get the files for QFIL? Is it worth even trying?

FYI, for reference, I basically gave up and bought a new phone.
This error message basically means your eMMC is "fried":
FAILED (remote: flash write failure)
The failing eMMC BoardDiag test confirms it.
I dont believe so many people would have Sandisk eMMC (the one in Nexus5) which would suddenly become completely broken.
I'm quite sure some internal project engineer out there knows of some "fuse" or "write-block" that's causing this...
But, in meantime, I've decided its better to be enjoying the phones I express ordered from Hong Kong...

Bootloader error: FAILED (remote: Failed to load/authenticate boot image: Load Error)

Hey,
so, I'm really sorry if this has been asked before, but I've searched far and wide for something I can do and I have run out of ideas.
I tried a custom rom on my Oneplus 6 today and wanted to revert back to my old rom, which led to everything spiraling downwards. First I tried restoring my TWRP backup but that oddly sent me into a bootloop. Afterwards I tried installing the zip for the stock rom of OB5, which I was on before and just recovering the data partition, which worked and I could boot, but oddly enough the stock Oneplus launcher was gone. Since I couldn't open any apps without the launcher, I couldn't just install it via an apk or something, so I tried installing the stock rom and afterwards just recovering the data, boot and system partitions, which sent me into a bootloop which keeps booting into fastboot. But now, I am not able to boot the twrp.img anymore with the error shown in the title:
Code:
FAILED (remote: Failed to load/authenticate boot image: Load Error)
So then I downloaded the stock kernel boot img in the hopes that booting it would work, which it didn't. I tried flashing it to the boot_a and boot_b partitions: same result. So now I'm out of ideas. Can anyone help me with figuring out what I can do to recover my oneplus 6 from the bootloop without erasing the internal storage (data partition is not that important, but it would really suck to lose my internal storage). Thanks
EDIT: After finding this fastboot flashable rom and using the flash-all-partitions-fastboot.bat, I could at least boot into recovery without it bootlooping again. I then used this opportunity to back up all my important files to a USB stick and clean flashed OOS, so now I finally resolved it

ddominikt said:
Hey,
so, I'm really sorry if this has been asked before, but I've searched far and wide for something I can do and I have run out of ideas.
I tried a custom rom on my Oneplus 6 today and wanted to revert back to my old rom, which led to everything spiraling downwards. First I tried restoring my TWRP backup but that oddly sent me into a bootloop. Afterwards I tried installing the zip for the stock rom of OB5, which I was on before and just recovering the data partition, which worked and I could boot, but oddly enough the stock Oneplus launcher was gone. Since I couldn't open any apps without the launcher, I couldn't just install it via an apk or something, so I tried installing the stock rom and afterwards just recovering the data, boot and system partitions, which sent me into a bootloop which keeps booting into fastboot. But now, I am not able to boot the twrp.img anymore with the error shown in the title:
Code:
FAILED (remote: Failed to load/authenticate boot image: Load Error)
So then I downloaded the stock kernel boot img in the hopes that booting it would work, which it didn't. I tried flashing it to the boot_a and boot_b partitions: same result. So now I'm out of ideas. Can anyone help me with figuring out what I can do to recover my oneplus 6 from the bootloop without erasing the internal storage (data partition is not that important, but it would really suck to lose my internal storage). Thanks
Click to expand...
Click to collapse
at this point, https://forum.xda-developers.com/oneplus-6/how-to/tool-msmdownloadtool-v4-0-international-t3798892 is your only option that will get you up and running again. this WILL wipe the whole device including internal storage. Or you could try the fastboot rom thread, https://forum.xda-developers.com/oneplus-6/how-to/rom-stock-fastboot-roms-oneplus-6-t3796665.

MrSteelX said:
at this point, https://forum.xda-developers.com/oneplus-6/how-to/tool-msmdownloadtool-v4-0-international-t3798892 is your only option that will get you up and running again. this WILL wipe the whole device including internal storage. Or you could try the fastboot rom thread, https://forum.xda-developers.com/oneplus-6/how-to/rom-stock-fastboot-roms-oneplus-6-t3796665.
Click to expand...
Click to collapse
Yeah I guess I'll try the fastboot rom now without wiping the internal storage. If that at least helps me to boot into recovery, I can at least back up my most important files. If not, there is no other option I guess. Unless anybody has any ideas left for me

ddominikt said:
Yeah I guess I'll try the fastboot rom now without wiping the internal storage. If that at least helps me to boot into recovery, I can at least back up my most important files. If not, there is no other option I guess. Unless anybody has any ideas left for me
Click to expand...
Click to collapse
Asaik fastboot flash all will erase your internal drive but just don't take my work read on the thread, I have been through this and have lost data so now I try my best to keep my data stored elsewhere like online storage etc, cheers

Unable to keep flashed recovery or rom. Device restores everything after reboot

I've got an old Samsung Galaxy Note 10.1 (N8010) which was flashed to a custom ROM (Cyanogenmod) in 2016. I'm not sure what version because I'm unable to boot it. A few weeks ago, the tablet rebooted without reason and got stuck on the Cyanogenmod bootscreen forever. I've let it run for 24 hours without result.
So this is what I tried:
Reboot into recovery mode (TWRP 2.8.6.0) and wipe everything. Then I tried to flash a different ROM, but when the device reboots, everything seems to be reset and it tries to boot the old corrupted ROM again. I also tried a newer version of LineageOS. But for that, I need a newer TWRP version. So I download and put the newest TWRP version on it using ODIN mode. Flash Passes says ODIN, but after reboot, TWRP 2.8.6.0 is still being loaded. I tried it again without 'reboot' checked so I can reboot directly back into recovery manually, but this also, didn't worked. (by the way, ADB works when loading TWRP, FASTBOOT doesn't work when loading ODIN mode, fastboot doesn't recognize the device)
I tried to flash stockrom back onto the device, also using ODIN mode. Flash passes, no errors. Device reboots and.. nope! It still tries to load the old Cyanogenmod forever.
I'm basically stuck here. I can't update to a newer Recovery and I cant flash the rom because everytime I reboot the device, everything change i made is gone.
I noticed that when I list files in /data the folder seems to be empty.
I also tried to reformat /data to fat and back to ext4 but formatting to fat fails and formatting to ext4 succeeds, however, after a reboot, everything i did seems to be undone by the device. Even the time and date is reset.
Is there a way I can bring back my tablet back to life? Thank you!
I have pulled the recovery.log file and uploaded it to pastebin.
I can't post a link to it because I do not have made 10 posts yet.. (very anoying). So i put the adress here:
https://pastebin.com/3muqPMzz

FSCK check on /data returned this:
Code:
~ # e2fsck /dev/block/platform/dw_mmc/by-name/USERDATA
e2fsck 1.41.14 (22-Dec-2010)
/dev/block/platform/dw_mmc/by-name/USERDATA: recovering journal
Superblock needs_recovery flag is clear, but journal has data.
Run journal anyway<y>? y
yes
e2fsck: unable to set superblock flags on /dev/block/platform/dw_mmc/by-name/USERDATA
And Odin mode: NAND ERASE ALL returns
Code:
<ID:0/006> Complete(Write) operation failed.
It seems like my Note 10.1 tablet is suffering from the emmc brick bug.

niquedegraaff said:
I've got an old Samsung Galaxy Note 10.1 (N8010) which was flashed to a custom ROM (Cyanogenmod) in 2016. I'm not sure what version because I'm unable to boot it. A few weeks ago, the tablet rebooted without reason and got stuck on the Cyanogenmod bootscreen forever. I've let it run for 24 hours without result.
So this is what I tried:
Reboot into recovery mode (TWRP 2.8.6.0) and wipe everything. Then I tried to flash a different ROM, but when the device reboots, everything seems to be reset and it tries to boot the old corrupted ROM again. I also tried a newer version of LineageOS. But for that, I need a newer TWRP version. So I download and put the newest TWRP version on it using ODIN mode. Flash Passes says ODIN, but after reboot, TWRP 2.8.6.0 is still being loaded. I tried it again without 'reboot' checked so I can reboot directly back into recovery manually, but this also, didn't worked. (by the way, ADB works when loading TWRP, FASTBOOT doesn't work when loading ODIN mode, fastboot doesn't recognize the device)
I tried to flash stockrom back onto the device, also using ODIN mode. Flash passes, no errors. Device reboots and.. nope! It still tries to load the old Cyanogenmod forever.
I'm basically stuck here. I can't update to a newer Recovery and I cant flash the rom because everytime I reboot the device, everything change i made is gone.
I noticed that when I list files in /data the folder seems to be empty.
I also tried to reformat /data to fat and back to ext4 but formatting to fat fails and formatting to ext4 succeeds, however, after a reboot, everything i did seems to be undone by the device. Even the time and date is reset.
Is there a way I can bring back my tablet back to life? Thank you!
I have pulled the recovery.log file and uploaded it to pastebin.
I can't post a link to it because I do not have made 10 posts yet.. (very anoying). So i put the adress here:
https://pastebin.com/3muqPMzz
Click to expand...
Click to collapse
Some of what you describe seems to suggest that your internal sdcard is corrupted, but, you still have TWRP booting. I would think that TWRP wouldn't boot if the internal was damaged.
Sent from my LGL84VL using Tapatalk

I can boot twrp but anything I do in there is temporary. I can't write to the internal SD. Only read. Seems like the emmc brick bug to me. I wish there was a way to check if this is absolutely true.