Develop Bugs

[Q] Very strange recovery issue

I just received my Nexus 7 2013 16gb WiFi from amazon a few days ago, and it's been great. The recovery has had issues though, it tried to do an OTA update the first day I got it, and when it rebooted, it just stayed on a black screen instead of actually going to recovery, so I had to hard reboot it, to get back to the jellybean it came with. This wasn't a major issue at the time, since then I've just unlocked it and flashed kitkat via fastboot (I'll get lollipop once it has gravitybox or something similar). But since then, I've rooted it and installed TWRP, and TWRP runs fine, but has some weird issues. It seems to not actually see the OS at all, or even the storage filesystem. I have to do a hard reboot to even get out of TWRP, as trying to get out normally gives me the error "Warning blah blah no OS installed, are you sure?", to which I tell it I'm sure and it just reboots recovery. But doing a hard reboot boots into the OS just fine. Am I doing something wrong? TWRP was installed AFTER I installed KitKat and the updated bootloader with the official google factory images, is this a problem?
Some images of what I'm seeing:
1
2

Maybe it's because you're running TWRP 2.8.2.0 which is for Lollipop. If it doesn't work with 2.8.1.0, try with the lastest 2.8.2.2. Running Lollipop at least, everyone had the same problem with both 2.8.2.0 and 2.8.2.1.

where can I place the recovery image where twrp will see it?
Thanks for your suggestion LittleConfucy. I was wondering if you can tell me where to put recovery image that TWRP can see it?
Flashing is a problem without being able to access the image to flash in the stripped down rom file system that twrp boots into. No shared directory in /cache.

Nevermind I got it dialed in.
Sent from my Nexus 7 using xda app-developers app

What did you do to fix this? I just had the exact same thing happen. I had a 5.0 rom and tried to flash a different one but once in twrp no files and the no os line when I tried to reboot. I'm on 2.8.2.0

kingston73 said:
What did you do to fix this? I just had the exact same thing happen. I had a 5.0 rom and tried to flash a different one but once in twrp no files and the no os line when I tried to reboot. I'm on 2.8.2.0
Click to expand...
Click to collapse
I just flashed to 2.8.2.2 and twrp started seeing my internal storage again.

el80ne said:
I just flashed to 2.8.2.2 and twrp started seeing my internal storage again.
Click to expand...
Click to collapse
So if I hold power down and force it to reboot it should boot back into the OS? And once in the OS will I be able to use TWRP manager to flash the latest?

kingston73 said:
So if I hold power down and force it to reboot it should boot back into the OS? And once in the OS will I be able to use TWRP manager to flash the latest?
Click to expand...
Click to collapse
That's what I did.
Sent from my SM-G900V using XDA Free mobile app

My device is pretty much bricked

I took my 5.1.1 VZW Note 4, and rooted it with King Root. I proceeded to follow the instructions to change my CID here. I used adb, performed the commands, and everything seemed golden. I used odin to flash TWRP, but something went wrong. I booted into the recovery, and tried to "update from external storage". I soon recieved a "dm-verity verification failed in recovery" messaged. It did not occur to me that I was still in the stock recovery; I did not bother to check it's initial look and feel, and assumed the TRWP programmers were just lazy. After reading up on this "dm-verity" error, xda posters said I should flash it with Kies. Thinking nothing wrong could happen, I gave it a shot. It updated to 6.0.1. This is where the problems start happening.
Since then, I can't reflash to 5.1.1. I've tried every version I could get my hands on, including the 5.1.1/6.0.1 hybrid posted here. I have 3 total verions of 5.1.1. I then tried to downgrade to 5.0.1. The first version of 5.0.1 started artifacting the screen, but booted and stopped promptly. It only artifacted the "Samsung" loading screen. I couldn't, however, root the device. Feeling desperate, I tried the only other version of 5.0.1. Success! I rooted and reran the adb commands and the script provided to change CID. This time, it skipped the first half of the script. It went directly to "backup up loader to external card". This tells me something about my CID will forever be changed, and is probably the reason my phone is boot looping. This time, I was able to flash TWRP. I installed CM 13 only to find out my sim wasn't recognized (when I used it to download King Root in 5.0.1 before). I figured it was because I was usig a 5.0.1 bootloader/modem. I tried reflashing to 5.1.1, the 5.1.1/6.0.1 hybrid, and 5.0.1 again. 5.11 boot loops and 5.0.1 hangs. Advice please... Thanks
Versions flashed:
"N910VVRU2BPA1_N910VVZW2BPA1_N910VVRU2BPA1_HOME.tar" - 5.1.1, boot loops at Verizon screen
"N910VVRU2BPA1_N910VVRU2CPD1_FullFirmware.tar" - 5.1.1/6.0.1 hybrid, boot loops
"N910VVRU2BOG5_N910VVZW2BOG5_N910VVRU2BOG5_HOME.tar" -5.0.1, boots but artifacts and cannot root
"N910VVRU2BOF1_N910VVZW2BOF1_N910VVRU2BOF1_HOME.tar" - 5.0.1, booted and rooted/flashed to TWRP, caused hiccups in MM custom roms, cannot get to boot again after a reflash
"N910VVRU2BPA1_StockRestore.tar" -5.1.1 unincremented stock restore, fails on ~90% of odin flash
"N910VVRU2BPA1_StockRestore_Incremented.tar" - 5.1.1 incremented stock restore, flashes, boot loops
Edit: Success!! I flashed the Incremented Stock Restore for 5.1.1 to no avail. It keep boot looping. I cleared the cache and data twice in a last ditch effort, and pulled the USB cord. It booted! Can anyone instruct me on how to proceed to flash only the modem/required portion of 6.0.1 after flashing TWRP? Do I just flash the 6.0.1 modem or modem and kernel?
Edit 2: I flashed the 6.0.1 modem over top of my 5.1.1 full firmware. I have TWRP and CM 13 loaded and working perfectly. From previous experiences, I've noticed CM 13 is more forgiving than some other 6.0.1 custom ROMs. Should I attempt to reflash the Lollipop on MM Stock Rom to obtain the MM bootloader, and then unlock it? This is working fine at the moment.
Edit 3: I reflashed to the hybrid rom and everything's okay. I had to wipe the cache..

mods, you can delete this thread. I solved my issue

av00va said:
mods, you can delete this thread. I solved my issue
Click to expand...
Click to collapse
Hey bud I'm on 6.0.1 can you give me the link to downgrade to 5.1.1 So I can root and unlock
Sent from my VS990 using Tapatalk

mwebb34 said:
Hey bud I'm on 6.0.1 can you give me the link to downgrade to 5.1.1 So I can root and unlock
Sent from my VS990 using Tapatalk
Click to expand...
Click to collapse
http://forum.xda-developers.com/note-4-verizon/general/note-4-verizon-bootloader-unlock-t3358913 and http://forum.xda-developers.com/not...t/howto-bootloader-unlock-upgrade-to-t3398144 Use the 2nd link 1st to downgrade to 5.1
I had to use Kingoroot(Google it) to root. It was a pain but once you root you have to be patient and leave the phone until it stabilizes after rooting. It took me a few attempts but in the end I'm golden. Part of my problem is a bad battery too but that's another story....

flashed custom ROM, can't get past 'let's get started' screen

hey guys,
I loaded the unofficial, then the official versions of LineageOS, as well as SlimRom
after successfully installing both the rom and the gapps 7.1 via recovery, I can't get past the initial android OS screen
my phone simply reboots, and stays in this loop forever
is there something wrong with my phone or did I mess up the install somewhere?

Try an older version of Gapps

maxgohan said:
hey guys,
I loaded the unofficial, then the official versions of LineageOS, as well as SlimRom
after successfully installing both the rom and the gapps 7.1 via recovery, I can't get past the initial android OS screen
my phone simply reboots, and stays in this loop forever
is there something wrong with my phone or did I mess up the install somewhere?
Click to expand...
Click to collapse
Most of the 7.1.1 ROM doesn't work for Canadian network. So far, only one ROM that worked i.e. https://forum.xda-developers.com/htc-one-m8/development/rom-t3430080
Give it a try

ckpv5 said:
Most of the 7.1.1 ROM doesn't work for Canadian network. So far, only one ROM that worked i.e. https://forum.xda-developers.com/htc-one-m8/development/rom-t3430080
Give it a try
Click to expand...
Click to collapse
thanks so much!
I flashed this rom and it works!
I was beginning to think something was wrong with my phone...

Stuck at Twrp loading screen

So whenever I boot into twrp recovery, it gets stuck on the twrp splash screen for a good 5 minutes or so and then it loads into the main screen. It's not a biggie but does anyone else have the same problem? What's the fix?
I'm on twrp version 3.2.3-1 on OP3

Darkweb_182 said:
So whenever I boot into twrp recovery, it gets stuck on the twrp splash screen for a good 5 minutes or so and then it loads into the main screen. It's not a biggie but does anyone else have the same problem? What's the fix?
I'm on twrp version 3.2.3-1 on OP3
Click to expand...
Click to collapse
The official TWRP is known to be slow in loading but 5 minutes seems to be on the higher side. Check whether your ROM dev recommends another version or try reflashing it.

tnsmani said:
The official TWRP is known to be slow in loading but 5 minutes seems to be on the higher side. Check whether your ROM dev recommends another version or try reflashing it.
Click to expand...
Click to collapse
I'm using Skydragon OS. The rom dev recommends using latest 3.2.3-0 or higher.

Darkweb_182 said:
I'm using Skydragon OS. The rom dev recommends using latest 3.2.3-0 or higher.
Click to expand...
Click to collapse
Try the 3.2.3-10 version. Search for it on XDA. I think that it is by dianlujitao.

Android 10 stock doesn't boot

So I have this issue with my S7 that it doesn't boot on stock android 10 but on OneUI 2 boots just fine, did anyone have this issue?

Madalin32 said:
So I have this issue with my S7 that it doesn't boot on stock android 10 but on OneUI 2 boots just fine, did anyone have this issue?
Click to expand...
Click to collapse
U format ur datapartion?

joke19 said:
U format ur datapartion?
Click to expand...
Click to collapse
Yes, I do all my wipes and what is necessary to boot but still, stock android 10 doesn't do it. With Treble I can boot but with Pixel Experience and android 10 roms I can't...

Maybe you could have asked this question directly in the thread of the ROM you're trying to boot...

Tanguy_ASM said:
Maybe you could have asked this question directly in the thread of the ROM you're trying to boot...
Click to expand...
Click to collapse
It's not only one specific rom, all Stock android 10 roms don't boot

Madalin32 said:
It's not only one specific rom, all Stock android 10 roms don't boot
Click to expand...
Click to collapse
flash using pit file,and check re-partition

DarkVallen22 said:
flash using pit file,and check re-partition
Click to expand...
Click to collapse
Didn't think of this, might try tommorow.

You using f2fs for /data?
Make sure all the partitions are in ext4, if that didn't help it is probably your TWRP not flashing correctly, try Anajaser1211's TWRP.

Mohamedkam000 said:
You using f2fs for /data?
Make sure all the partitions are in ext4, if that didn't help it is probably your TWRP not flashing correctly, try Anajaser1211's TWRP.
Click to expand...
Click to collapse
I can't acces the link.. it is deleted

I would be interested to hear if you managed to fix this issue as I have exactly the same problem. I have a UK spec Galaxy S7 Exynos and started experimenting with custom ROMs a year ago. Both Lineage 16 and Pixel Experience 9 worked fine with no issues, however whenever I try to flash an Android 10 based ROM (I've tried both Lineage 17 and Pixel Experience 10) they will not boot and get stuck on the startup screen.

Have you updated your boot partition with the latest stock version before trying Android 10 versions?

I have 4 Galaxy Exynos phones (G930W8) and ran 16 (Android 9) on all of them with no problems. But when I started to try 17 (Andoid 10), 3 would boot but one did not and still will not boot any 17.1 ROM. Out of curiosity I tried Ivan's 18 on that one phone and it boots fine. All of the 18 ROMs (Android 11) seem to boot with no problems. I have no idea why and did try every 10 ROM that I could find. Maybe a slight hardware variation?
I did update to the latest stock version and even ran the PIT file to reset partitions with no improvement.

RickBH said:
I have 4 Galaxy Exynos phones (G930W8) and ran 16 (Android 9) on all of them with no problems. But when I started to try 17 (Andoid 10), 3 would boot but one did not and still will not boot any 17.1 ROM. Out of curiosity I tried Ivan's 18 on that one phone and it boots fine. All of the 18 ROMs (Android 11) seem to boot with no problems. I have no idea why and did try every 10 ROM that I could find. Maybe a slight hardware variation?
I did update to the latest stock version and even ran the PIT file to reset partitions with no improvement.
Click to expand...
Click to collapse
My phone was updated to the latest stock version of Samsung's software. I tried the above advice and you are exactly right! Lineage 18 boots with no issues at all as does Lineage 16 - it seems to be certain phones that are not compatible with Android 10 as I am using exactly the same procedure in TWRP when installing the new ROM. Thanks very much for your help, I will see how I get on with Android 11 as this is just a spare phone anyway!

Madalin32 said:
So I have this issue with my S7 that it doesn't boot on stock android 10 but on OneUI 2 boots just fine, did anyone have this issue?
Click to expand...
Click to collapse
I also have same problem ! Did you find any fix ? Pls tell !!! :-(
Exact Same issue

Madalin32 said:
So I have this issue with my S7 that it doesn't boot on stock android 10 but on OneUI 2 boots just fine, did anyone have this issue?
Click to expand...
Click to collapse
Since when was there an official stock Android 10 update for the Galaxy S7?
EDIT: Nvm, misunderstood the post.