Stock android keeps overwriting TWRP recovery on Nvidia shield tablet every time I boot into android. What do I do?
Related
How do I install a recovery without it being erased the next time I boot up its really getting annoying every boot after installing recovery it says android is updating
Delete /system/etc/install-recovery.sh, flash CWM again and that's it.
This isn't as much as a "help!" question because I got the tablet working again (by flashing a stock blob); it's more of an question to try find out if I can prevent this from happening again...
I was just browsing tapatalk when my tablet froze. I rebooted and saw the tablet kept rebooting to the Asus logo. Recovery didn't work (it kept rebooting after the recovery logo would appear) and the the ROM (KatKiss LP v29) wouldn't boot.
Flashing TWRP again with fastboot didn't work. I couldn't flash the ROM again or use my Nandroid... I ended up formatting recovery with fastboot, flashed a stock blob to get it working again, and then restored from there, but it was a pain.
So I'm curious if anyone can guess what may have happened and if there is any way to prevent it from happening again?
Hi,
I am fixing a friends Shield Tablet (not K1) which I believe in on Android 4.4.
Before the Kill Switch was sent down, he tried to flash a custom ROM to avoid this. He had TWRP 2.8.x.x recovery installed.
He attempted something and the tablet stopped booting.
I tried to install LineageOS but it failed, so I installed the latest TWRP (flashed image in old version of TWRP). This caused it to hang on the black Nvidia logo!
I can still do volume down + power and get into a black screen with a few options (continue, fastboot protocol, recovery, reboot, power off). When I click into Recovery from there, nothing happens. Before flashing TWRP 3.x it worked.
I have now flashed TWRP 2.8.7.0 again and it boots to recovery again.
So have I done something bad by updated TWRP? Do I need to flash firmware first?
Thanks.
Try flashing this blob in your TWRP before you flash newer TWRP
https://androidfilehost.com/?fid=529152257862702195
eoinzy said:
I tried to install LineageOS but it failed, so I installed the latest TWRP (flashed image in old version of TWRP). This caused it to hang on the black Nvidia logo!
Click to expand...
Click to collapse
Have you tried flashing latest TWRP (3.2.1-0) using fastboot, instead of within TWRP?
Yes I installed progressively newer BLOBs to update the fastboot mode and once I installed the latest, then the latest TWRP worked, and I could just flash LineageOS no problems!
Hello, I was wondering could an Android device still boot if I were to lets say try and flash a custom recovery and it not go so well or is something during booting of the device dependent upon the recovery being there and being functional?
Of course you can. The recovery partition can be considered as an alternative boot partition that lets you boot the device into a recovery console for performing advanced recovery and maintenance operations on it.
Tablet's soc is MT8173, and rom is android 7.0. But there is no rec to flashing magisk to root, and tablet automatic restart while lock screen after flashing magisk modified boot.img to root.
So i give up root tablet, and try to modify system.img. but no matter use third part tools under windows or make_ext4fs under linux to repack system.img, the tablet always stuck in first screen after flash.
Plz help me
Re-flash tablet's Stock ROM, because either tablet's bootloader or its Android OS got corrupted.