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?

Nexus 5 Recovery issues

Hi there, first post on here!
I've bought a nexus 5 off of eBay from some person who tried to root it and failed, thinking it would be an easy matter of restoring it.
However, the standard stock recovery process did not work, and I've encountered a number of issues:
When the device gets to erasing 'cache', it stays there for upwards of half an hour with no results.
With stock recovery flashed, pressing power + volUp immediately makes it erase /data, with no other options given.
It also does not show the stock recovery icon, instead a standing up android figure with a spinning poly in front of it.
Flashing TWRP and booting into recovery, it says 'e' is locked and goes into a boot loop.
Also no options in CWM recovery​
I thought I would ask on here because it's out of my league now, I've tried on both windows and mac with no luck and I'm not sure what to try next, maybe just leave it until cache finally erases?
Thanks in advance!

You need to read read and read some more.
Start here:
http://forum.xda-developers.com/google-nexus-5/general/resource-guides-info-threads-linked-read-t2784527
It sounds like the bootloader is locked.
It's almost impossible to brick a nexus.

I've managed to get a version of CWM loaded.
Performing factory reset gives the error that /data cannot be mounted for wiping.
Bootloader is definitely open.

M1kesky said:
I've managed to get a version of CWM loaded.
Performing factory reset gives the error that /data cannot be mounted for wiping.
Bootloader is definitely open.
Click to expand...
Click to collapse
Ok :good:. That means you can install TWRP 3.0.

Try this: flash back to a completely stock MM or LP ROM by manually flashing each partition, inlcuding the userdata.img file. When you have finished flashing all partitions, boot directly to recovery from fastboot mode, perform a factory wipe, and reboot.

I've tried doing that but it just results in the standing up android icon, with power+up leading to it trying to wipe data again. no option to do a factory wipe.
I put TWRP 3.0.0 on just to test and ended up in a worse bootloop, which failed to load TWRP but occasionally got into it and displayed this:
imgur.com/RKyZIJf
Sorry as I am a new user it doesn't let me use links

audit13 said:
Try this: flash back to a completely stock MM or LP ROM by manually flashing each partition, inlcuding the userdata.img file. When you have finished flashing all partitions, boot directly to recovery from fastboot mode, perform a factory wipe, and reboot.
Click to expand...
Click to collapse
Thanks, I gave it another try and did the recovery partition last, and made sure I manually put it into recovery mode from bootloader.
The red triangle and recovery menu are back, I can't thank you enough!

Glad you got it to work. I suggest using TWRP 2.8.7.1. For some reason version 3.0 does not work properly with all N5 phones.

It's still happening.
I've been away for a few days so only had the chance to respond now.
I got into the ususal recovery screen as mentioned previously and tried to do a factory reset, but it had problems with /data again.
I left it the entire night while I slept and it was still saying formatting /data in the morning, nothing had changed.
Anybody got any more suggestions? It's also back to the android with the rotating poly instead of the android with the exclamation mark.
EDIT: when flashing userdata, no matter what version of android I try, it always hangs.
It started on 6.0.1 if that helps.

The userdata.img file is included with each stock rom. I advise against mixing userdata.img files from different stock ROMs.

Sorry, I mean that I've flashed completely whole different versions of android and the result is the same across all of them, not that I've used different userdata img's on the same version of android.

Could be an emmc problem which would require a motherboard swap.

Is that likely to happen when the previous owner said it was fine before they tried to root?

G930F, LineageOS Install Fail, TWRP Frozen (Help?)

Hey all,
I'm not a total noob, but I do this so infrequently that I can't commit it to memory. Would really appreciate some help here.
I followed the official LineageOS Guide for Herolte, over here.
I had done this previously on my Nexus 7 so I was fairly confident.
Everything worked well, I got TWRP installed using Heimdall from Linux, and successfully pushed the latest LineageOS and open_Gapps images to the phone.
Rebooted into TWRP, and followed the recommendation to wipe System, Cache and data partitions. This failed with red text stating that ti was unable to mount data.
I googled some, and found a suggestion to reformat the partitions, first to a different file system and then back to their original file systems again. I tried formatting /data to exFat, and it took forever, eventually erroring out with an error message. After this I can't get into TWRP anymore. When I try the phone boots to the TWRP startup screen, and just freezes there.
I have tried reflashing TWRP using Heimdall and this does nothing. Flash succeeds, nut still freezes at TWRP splash screen.
I googled some more and found a suggestion to flash stock Samsung firmware, and then try again, this time formatting data system and cache without trying to first wipe them. Problem is I can't successfully flash stock firmware.
I tried using this method in Heimdall, but it complains "Local and device PIT files don't match and repartition wasn't specified!" and fails.
I've also tried booting into Windows and using Odin, but it never works. The screen turns grey, and no progress indicators ever start. I assumed this was because I had the incorrect drivers for the phone, and tried using zadiag.exe to replace them, but the driver install fails.
I'd greatly appreciate any help. I can't seem to force the phone to shut off, it just keeps rebooting and getting stuck on either the TWRP spash screen or on the download mode screen. I know this is solveable, but unless I figure it out fast, I'm worried I am going to burn in the screen.
Any suggestions appreciated!

Never mind. I must just have had a bad stock image.
I downloaded a different one, and retried heimdall and it flashed properly.
I am now able to re-flash and boot into TWRP again.
Hopefully I won't have the same problem again when I try to wipe the partitions...

Alright,
So I solved this issue by (once I reflashed stock, and then reflashed TWRP again) formatting the data partition twice, first to ext3, and then back to ext4. This looks to have cleared the encryption issues that were causing thsi problem ,and allowed everything to continue working as expected.

Android Recovery: Issues flashing via ADB or external SD card

Hey,
following happend: I dirty flashed LOS 17.1 february update over december version following the instructions ivan gave. After flashing gapps and magisk I flashed the newest TWRP image.
Everything went well (at least it seamt so) I booted to LOS and set up new fingerprints (had to deleate them before flashing), started first app (spotify) and screen went black and phone restarted. Than I got the the FRP Lock message and wasn't able to boot agian neither to LOS nor to TWRP.
Everything followed is here. Tldr: I wasn't able to reflash Stock Rom with Odin no matter what I tried and got lost bettween download mode and nothing.
However I somehow got Android Recovery working!! This is what I can and cannot do:
chrisrevoltes said:
Now I'm able to boot to download mode and original recovery but not to system.
This is what Recovery shows:
View attachment 5218201
I can wipe data and cache partition, but not system partition.
I can view the logs, but I'm not sure what they are telling me....
I can view my external SD card, but trying to install ether TWRP, LOS or the stock image aborted with an error Update from external storage is disabled following a reboot to recovery. Any idea how to enable that?
ADB seams to be working. It can find the phone, although there is an message Stopping adbd... on the phone.
View attachment 5218209
adb devices -l shows:
XXXXXXXcf0cd263704 sideload product:heroltexx model:SM_G930F device:herolte transport_id:8
Sideloading the stock image or TWRP results in: Total xfer: 0.00x in console and adb status 1 on phonescreen with phone reboot to recovery.
Any other adb command (except those three getter) has ether no effect or results in an error.
Any further attempt to flash again with Odin results in the same errors like described in my last post.
Any ideas? ADB or external storage seams like a good way. But system partition worries me.
Click to expand...
Click to collapse
Can anyone help me?

Some time ago I had a Samsung S6 Edge G925I with which I had the same problems and errors as you. After an intense week flashing systems and without getting it to work, I took it to a colleague who has box and other tools to unbrick, unfortunately he discovered that the problem was hardware, more specifically emmc memory problem, I had to resort to changing the plate and problem solved. I would advise you to try all the firmwares that you can from your binary and with old versions of Odin, without opening as administrator, I hope you are lucky; I'll keep thinking if I can think of another solution, regards.

Thanks! I have finally made it. It took my the third day (thanks to covid home office) but I'm now up again with new LOS (but old TWRP).
For the record: My last try was using an older and modified version of Odin (3.13 here) and flashing the newest stock image with extracted PIT file. After 3 minutest it finally booted.
Im not sure if it was the older Odin version (some recommending using v3.14 for devices newer 2018) or the modified Odin version.

TWRP shows internal storage folders named as random letters.

I have a Redmi note 8 with MIUI 12 installed. Bootloader is unlocked and the phone is rooted.
When I try to flash TWRP recovery in fastboot mode using my PC, it successfully flashes and boots into the TWRP recovery. TWRP does not ask for any password for decrypting the files, and when I go to install>sdcard then the storage is all in random letters, completely unrecognizable.
I have tried a lot of tutorials on youtube but none of them worked. I tried flashing the latest version of TWRP, didn't work. I tried formatting all data and rebooting back into recovery mode, didn't work. (if you reboot to system after installing TWRP, the phone automatically deletes TWRP and the next time you open recovery mode you just get the default MI recovery, and you have to flash TWRP again to open TWRP recovery.) I tried almost everything on the internet but none of it worked. Is there any way I can make it ask for the decryption password? or have my files decrypted? I just need the TWRP for a one-time-use to install a custom ROM. I don't need it to be installed permanently, but no problem even if it does get installed permanently. I just want my custom ROM.
Please help

does that work?:
Boot into twrp, then
Code:
adb shell
twrp decrypt myPassword
(myPassword is your user password)

User699 said:
does that work?:
Boot into twrp, then
Code:
adb shell
twrp decrypt myPassword
(myPassword is your user password)
Click to expand...
Click to collapse
It didnt work, "failed to decrypt data" i typed the right password

#JKTheBaskieBoy said:
It didnt work, "failed to decrypt data" i typed the right password
Click to expand...
Click to collapse
Okay, interessting. What's the exact error?
However, since you only want to use twrp to flash a custom OS, you could try to boot twrp (without flashing)
Code:
fastboot boot twrp.img
and then wipe data via twrp and then install your custom OS. You can use sideload which should be located under "advanced" I guess.
Code:
adb sideload myCustomOS.zip
EDIT: Don't boot out of twrp before sideloading, since your os should encrypt everything again after wiping which makes it unpossible for twrp to decrypt again (at least in your case, since it failed for some reason).
If you booted out of twrp, just wipe again and then sideload.

the correct and recommend way to install TWRP is
Flash TWRP
Erase userdata partition <~ it's important to do this as soon as possible since booting your device would just encrypt everything again
Format userdata partition
by doing this you would be able to access data partition files and folder would not be random letters.

User699 said:
Okay, interessting. What's the exact error?
However, since you only want to use twrp to flash a custom OS, you could try to boot twrp (without flashing)
Code:
fastboot boot twrp.img
and then wipe data via twrp and then install your custom OS. You can use sideload which should be located under "advanced" I guess.
Code:
adb sideload myCustomOS.zip
EDIT: Don't boot out of twrp before sideloading, since your os should encrypt everything again after wiping which makes it unpossible for twrp to decrypt again (at least in your case, since it failed for some reason).
If you booted out of twrp, just wipe again and then sideload.
Click to expand...
Click to collapse
Sorry for the late reply. Earlier i just gave up on installing the custom ROM and continued with my stock from. Today a tried again, installed TWRP and turns out it is not showing random letters now. its all regular storage. i didn't even do anything to decrypt it lol it just fixed itself. Now I will install the room myself. Thank you for your help though

Ah sh** here we go again. So i installed the custom rom successfully and everything worked fine, the TWRP too. but when I tried to flash a magisk patched image (the image that I used to root my phone in MIUI) then it got stuck in the boot screen. I had to flash the stock fastboot rom again.. And as expected from my piece of **** that xiaomi calls a phone, TWRP will show encrypted folders, and does not ask for a password. Same problem. Rooted my phone again, using the magisk root image, and it worked like usual, the phone rooted. Now i am stuck again in this bs. I guess I will wait for about 4-5 days and continue using the phone like normal. Maybe it will work again this time. I will try your method here first
User699 said:
Okay, interessting. What's the exact error?
However, since you only want to use twrp to flash a custom OS, you could try to boot twrp (without flashing)
Code:
fastboot boot twrp.img
and then wipe data via twrp and then install your custom OS. You can use sideload which should be located under "advanced" I guess.
Code:
adb sideload myCustomOS.zip
EDIT: Don't boot out of twrp before sideloading, since your os should encrypt everything again after wiping which makes it unpossible for twrp to decrypt again (at least in your case, since it failed for some reason).
If you booted out of twrp, just wipe again and then sideload.
Click to expand...
Click to collapse

Okay i tried wiping the data, cache and dalvik but it shows a huge essay of "error opening xxx/xxxx" in red text. Data wipe failed.
See you after like 4-5 days... hopefully

Update. I finally found a solution. It took literal hours of experimenting to find this.
-Flashed the fastboot ROM of the phone
-Rooted the phone by flashing magisk patched image
-Flashed Inception kernel via FK kernel manager
-Rebooting after flashing the kernel, It will get stuck in a black screen with no text whatsoever (probably a bootloop)
-Installed TWRP (This time TWRP does not show encrypted letters), Wiped all data, Transferred the custom ROM zip to the phone (while in TWRP) and flashing the rom
-The rom is flashed successfully. On the first reboot you get greeted with another bootloop. Fortunately the phone booted into TWRP. This time the folders are encrypted again.
-Successfully wiped the data (advanced>wipe data). No errors in data wiping this time.
-A fully working Corvus OS setup appears on rebooting.
I think the whole TWRP problem was fixed by the custom kernel. Anyways I am finally done with this now. You probably enjoyed seeing all this xD

#JKTheBaskieBoy said:
Update. I finally found a solution. It took literal hours of experimenting to find this.
-Flashed the fastboot ROM of the phone
-Rooted the phone by flashing magisk patched image
-Flashed Inception kernel via FK kernel manager
-Rebooting after flashing the kernel, It will get stuck in a black screen with no text whatsoever (probably a bootloop)
-Installed TWRP (This time TWRP does not show encrypted letters), Wiped all data, Transferred the custom ROM zip to the phone (while in TWRP) and flashing the rom
-The rom is flashed successfully. On the first reboot you get greeted with another bootloop. Fortunately the phone booted into TWRP. This time the folders are encrypted again.
-Successfully wiped the data (advanced>wipe data). No errors in data wiping this time.
-A fully working Corvus OS setup appears on rebooting.
I think the whole TWRP problem was fixed by the custom kernel. Anyways I am finally done with this now. You probably enjoyed seeing all this xD
Click to expand...
Click to collapse
I like that you keep trying and finding a solution, even though you had to invest hours to make it work!
Let's hope it will work if you update the OS though – I'd actually suggest a backup of all of your data before you do an update in the future, just to be safe!

#JKTheBaskieBoy said:
I have a Redmi note 8 with MIUI 12 installed. Bootloader is unlocked and the phone is rooted.
When I try to flash TWRP recovery in fastboot mode using my PC, it successfully flashes and boots into the TWRP recovery. TWRP does not ask for any password for decrypting the files, and when I go to install>sdcard then the storage is all in random letters, completely unrecognizable.
I have tried a lot of tutorials on youtube but none of them worked. I tried flashing the latest version of TWRP, didn't work. I tried formatting all data and rebooting back into recovery mode, didn't work. (if you reboot to system after installing TWRP, the phone automatically deletes TWRP and the next time you open recovery mode you just get the default MI recovery, and you have to flash TWRP again to open TWRP recovery.) I tried almost everything on the internet but none of it worked. Is there any way I can make it ask for the decryption password? or have my files decrypted? I just need the TWRP for a one-time-use to install a custom ROM. I don't need it to be installed permanently, but no problem even if it does get installed permanently. I just want my custom ROM.
Please help
Click to expand...
Click to collapse
tell me how to turn off a smartphone with a non-working sensor?

you can still use adb push command from pc to transfer files to your phone :
adb push "nameoffile" /sdcard
(place the file in your adb folder) I was able to root a phone that had this issue using this technique.

I think u should flash dm verity becoz when i flashed the rom and flashed dm verity it worked fine