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?
Related
Hello Guys!
Recently i received my used Motorola Moto G. Phone was nice, I was using it like every teenager, instagram snapchat etc. But last night i wanted to install rom on phone. Saw thread about installing everything, root rom etc. with 1 program. I tought it will be nice, so i downloaded it, run, and there is a problem. It was command line tool, everything gone right, there was messeage about clicking any button to continue, I did it and then my phone restarted, but there was like normal 5.0.2 android not 5.1 what was saying guy who wrote thread about that program. So i thought that i will do everything step by step, unlocked bootloader, installed recovery and when i first time opened recovery from bootloader menu it had problem with mounting data partition. I was trying to install firmware roms, but it had problems with downgrading bootloader. Downloaded 5.0.2 firmware .xml.zip file, it gone ok, i mean there wasn't a problem with motoboot.img, and at every single command there was only okay, there wasn't failed, just had 2 problems on phone screen, it was saying "hab check failed for boot" and "hab check failed for recovery". After typing every single command to fastboot and restarting phone always phone was stucked on boot screen, i mean on 4.4 it was stuck on messeage about unlocking bootloader, on 5.0.2 it was stucked on that 4 colors orbs flying around the screen. Then i was trying to open my stock recovery, but it was always broken, opened android with warning sign on it. When i was installing custom recovery that had problems with mounting /command /log /last_log /last_install, and when i was trying to mount data it couldn't mount it, I was trying to format /data and /data/media, it was always going ok and then i could mount data partition, but my phone was still stuck on boot screen. I was trying to install custom recovery again but it had same problem, just opened android with warning sign. And there is a question, what can I do to make my telephone working.
I'm sorry for mistakes, but my english is not the best
Try reading this thread here and see if that helps.
I have a TV110 (Amlogic S805, 1gb/8gb) Android TV Box. I was trying to replace the stock ROM with Openelec v5.0.8 from Kerber. The update went fine until it rebooted to launch Openelec then it hung at the Openelec logo for over an hour. I thought the box was hung so I removed power and rebooted. It hung again in the same place so I decided to use the reset button to launch recovery. I must have cycled power too quickly because it would only show the boot logo and would go no further. Something was seriously wrong with the box.
I created a bootup SD card with TWRP recovery on it. I booted up into TWRP 2.8.6 without any issues but could not restore any of the partitions. TWRP was getting errors trying to mount all the partitions. I figured I could go back to stock (I have a NAND backup). When I try to wipe or restore it fails because the partitions are not mounted. I tried to install the old firmware using the install from TWRP and I get "Error executing updater binary in zip".
At this point I am stumped. What do I do next?? How do I get my box bootable again?? Can I somehow re-create the partitions??
Any help would be appreciated.
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...
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.
Hi,
this is my first post on this forum, so please let me know if you are missing any information …
My problem: I'm experiencing a boot loop with my Nexus 5 after having changed its damaged battery. I didn't use it for a long time because of this damage. Now, it does start the boot sequence again, but only to the "circle" animation which it keeps showing indefinitely.
The circumstances:
I never tried to root the phone
USB debugging is not (and cannot be) enabled
I'm completely sure the problem is not caused by the power button (seems to be a common cause)
stock recovery is reachable
an old version of ClockWorkMod Recovery (from this thread) is bootable
three tested versions of TWRP won't boot
What I tried:
I unlocked the bootloader. With both the stock recovery and CWM, I tried to
wipe the device / the cache partition
flash a stock image (directly downloaded from the Google developer page)
flash a ResurrectionRemix image
None of these worked. It seems that the recovery systems are not able to write on or even to mount the necessary partitions. As the stock recovery apparently needs access to /cache for adb sideload, any attempt to flash anything results in an error message. CWM is able to sideload the zip file, but writing the image fails.
I furthermore tried the "factory" (not OTA) image from Google with its flash-all.sh script which tries to also update boot loader and other things via fastboot – every single one of these update attempts failed as well.
So, my question is: Does anyone of you know of a way to get my phone working again?
Many thanks in advance, best regards
Hørk
Hørk said:
Hi,
this is my first post on this forum, so please let me know if you are missing any information …
My problem: I'm experiencing a boot loop with my Nexus 5 after having changed its damaged battery. I didn't use it for a long time because of this damage. Now, it does start the boot sequence again, but only to the "circle" animation which it keeps showing indefinitely.
The circumstances:
I never tried to root the phone
USB debugging is not (and cannot be) enabled
I'm completely sure the problem is not caused by the power button (seems to be a common cause)
stock recovery is reachable
an old version of ClockWorkMod Recovery (from this thread) is bootable
three tested versions of TWRP won't boot
What I tried:
I unlocked the bootloader. With both the stock recovery and CWM, I tried to
wipe the device / the cache partition
flash a stock image (directly downloaded from the Google developer page)
flash a ResurrectionRemix image
None of these worked. It seems that the recovery systems are not able to write on or even to mount the necessary partitions. As the stock recovery apparently needs access to /cache for adb sideload, any attempt to flash anything results in an error message. CWM is able to sideload the zip file, but writing the image fails.
I furthermore tried the "factory" (not OTA) image from Google with its flash-all.sh script which tries to also update boot loader and other things via fastboot – every single one of these update attempts failed as well.
So, my question is: Does anyone of you know of a way to get my phone working again?
Many thanks in advance, best regards
Hørk
Click to expand...
Click to collapse
Ever fix it?