Database Info

Shield Tablet LTE stuck at Bootmenue/Bootloop

Hey Folks,
got some messy Prob's with my old nVidia Shield LTE Tablet.
The Facts:
-KillSwitch not Triggered and it was succesfully Rooted in November 2015, TEGRA-OTA was also Removed (nomoreota)
-worked for Months (beneath one year), only Super-SU penetrated me periodely that it needs to be Updated, but it couldnt be done, it said "not enough Space" after trying to install a newer Version. :silly:
-past Month (January 2017) i decided to do a Factory-Reset, because Girlfriend should get the Shield, thats where the Problem started:
After clicking Factory-Reset, it began to work. After 4 Hours and nothing happening, i decided to Power it Off and start fresh with Installing a clean Stock-ROM and remove the TEGRA-OTA as i done a year before.
But from now on things get messy and to complicated for me.
In the Past i rooted and flashed it with "Shield-RAM", found here on xda.
But this Time it didnt ended with a working Shielt-Tablet. It stucks alwas in a Bootloop, in Recoverymode also as in normally booting the flashed OS.
Confused an disturbed by this, i tried different Recoverys (TWRP 2.8 and 3.0, also a CWM), all with the same Effect: Bootloop
Now i only can acces the Bootmenue which says Bootloader Unlocked.
I dont now what to do from here on and would be very happy and glad, if someone can help me figuring out whats going wrong.
If further Details are needed i will do my best to provide things i forgot here to mention.
With kind regards - ToxicFighter1
Ps.: excusy my bad spelling, bit rusty in flawless english typing:good:

Hi !
There is this thread where you can try to get it back to stock https://forum.xda-developers.com/shield-tablet/general/unofficial-update-original-shield-t3281541
This nice index may help as well
Good luck !

Thanks, but that's not the problem. If I boot into Fastboot / Bootloader, it's totally fine. In fact, I can plug the tablet up to my PC when it's in any state and doesn't experience the issue. It only occurs when I have it plugged into AC. SO far, I've tried 3-4 different cables and power supplies for 2.4A, 2.1A, and 1.2A - all adapters which worked 100% prior to updating.
Suggestions?

OK - Finally fixed it...
I replaced everything as shown above, but ran into the issue again as soon as FlashFire installed the OTA. So, I tried a different way to upgrade and no longer have the issue. Below is what I did...
- Installed 4.4.0 via ADB/fastboot wirhOEM recovery
- Completed initial setup and upgraded to 5.0 via built in system update
- Rebooted
- Booted to bootloader and flashed TWRP recovery
- Booted to TWRP
- Installed SuperSU via sideload
I would have started out applying 5.0 via adb/fastboot, but have yet to see a full image available yet. Used same TWRP and SuperSU as originally used. Just eliminated GlashFire from process. Once I rebooted and everything loaded, plugged into 2.4a power, and it worked without going into boot loop.
Hope this may help someone else - Thanks

Hey Folks,
thx for the few answers, i'll try these Tips out the upcomig Days.
Lot'a Stuff to do atm, bit Busy.
With kind regards - Toxic

xanthrax said:
Hi !
There is this thread where you can try to get it back to stock https://forum.xda-developers.com/shield-tablet/general/unofficial-update-original-shield-t3281541
This nice index may help as well
Good luck !
Click to expand...
Click to collapse
Hey there, and personally Thx for the provided Link.
As announced i did try it, but with no Success.
I'll or explicit the Tablet gets Stuck at Step 17, the Bootsreen doesn't disapear.
Dont know whats Wrong, cause i did all as menitioned in the Post, every ADB/Fastbootstep with Succes-Message, and because Bootloader was already Unlocked, i took the Rooted Image.
But now, im still on Bootscreen, sick
With kind regards!

Help needed. Bootlooped into recovery

Good day,
Help is needed..
I flashed TWRP on the phone since it was not long ago updated to version 10.3 (China).
It flashed well (without errors).
The reboot was successful. No data was lost.
In the morning I decided to check the email, turned on the WIFI, and it went off after 2-3 seconds (everything was OK in the evening, it worked like usually). I thought that restarting the phone would fix the flaw, but alas, I was stuck in BOOTLOOP. Starts with the Mi. LOGO, then goes out, then shows again and goes into Recovery. Recovery runs. All data can be accessed. Restarting is possible only into RECOVERY and FASTBOOT.
What could be the snag here and how to solve it?
P.S. Have tried 'dirty flashing' 10.3 and 10.2 versions from TWRP, changing the kernel (androplus 7-9), reflashing Magisk (recommended by some users on a russian forum), recovering the boot.img (since it it the only recovery I have got).. All that to no avail.
Bootloader was always unlocked since I bought it and rooted. It was MIUI v10.0 then.
MI MIX 3 8/256
Stable 10.3 Chinese ROM with twrp (10.2 before update, with root and twrp)
Had no root but unlocked bootloader

z1ldj1an said:
Good day,
Help is needed..
I flashed TWRP on the phone since it was not long ago updated to version 10.3 (China).
It flashed well (without errors).
The reboot was successful. No data was lost.
In the morning I decided to check the email, turned on the WIFI, and it went off after 2-3 seconds (everything was OK in the evening, it worked like usually). I thought that restarting the phone would fix the flaw, but alas, I was stuck in BOOTLOOP. Starts with the Mi. LOGO, then goes out, then shows again and goes into Recovery. Recovery runs. All data can be accessed. Restarting is possible only into RECOVERY and FASTBOOT.
What could be the snag here and how to solve it?
P.S. Have tried 'dirty flashing' 10.3 and 10.2 versions from TWRP, changing the kernel (androplus 7-9), reflashing Magisk (recommended by some users on a russian forum), recovering the boot.img (since it it the only recovery I have got).. All that to no avail.
Bootloader was always unlocked since I bought it and rooted. It was MIUI v10.0 then.
Click to expand...
Click to collapse
Back up, wipe, flash, restore

Ok. That was the one thing I tried to avoid, since my backup is 27G (nandroid) and internal storage is 133G..
Will try and feedback.

Hi all,
Got it back again, of course with all data and apps gone. I have done nandroid backups (since there is no other way of backing things up from TWRP, except copying everything) from recovery before starting the upper described process. I figure they are of no use to me now or are they?
Please advise

P.S. restoring from nandroids brought me back to square 1..

z1ldj1an said:
P.S. restoring from nandroids brought me back to square 1..
Click to expand...
Click to collapse
Something not right with your data so start over

Restarted, redone. Recovered only Data. Looks ok but works a little laggy..
Upd.: needed to set up the screen lock after had done that and a restart, all works like it was, except with a new OS version

Install TWRP from xiaomi.eu, the official one from here seems to be a lot more buggy.

Isopropil said:
Install TWRP from xiaomi.eu, the official one from here seems to be a lot more buggy.
Click to expand...
Click to collapse
I took it from twrp themselves, not bothering to search any forums. It's not like digging for gold or the like
Upd.:
I read that the official TWRP doesn't support some mounts migrating from EU to global or CN-->EU V Global. It was discovered that it has some bugs with mounting paths. People recommend the LR Team TWRP over the official because of that, besides it has more options under Advanced tab e.g.
Personally I prefer the one that does the job for the moment and is the latest, so it was an easy choice for me ? especially installing a fresh OS update.

How to completely go back to stock, fix everything?

So I did a big mistake. I tried to install OmniROM - the Android Q based one from XDA.
Turns out, it's a big mess. Not trying to attack the developer because whatever - maybe I messed up.
My partitions got messed up as well it seems.
Point is: I ended up with a bricked phone.
I tried everything (and I mean that). In the end, I used the Qualcomm MSM Tool to flash a v9 update.
My phone booted up. All good, right?
Well, I wanted to install Lineage 16 all along, so I started with that at this point.
oem unlock, copy up the .zip, boot twrp, flash image.
Also very good, no errors. Yay!
Here comes the twist.
Upon install LOS, I read you must flash a GApps pack too. No worries, I grabbed one, pushed to the /sdcard/ location and tried to flash it.
Not enough space. On a 256 gb wiped phone. Interesting. But there is a log.
And this shocked me.
Code:
ROM Android version | 9
ROM Build ID | omni_guacamole-eng 16.1.0 PQ3B.190801.002 eng.mauron.20191115.213714 test-keys
ROM Version increment | 1907281556
ROM SDK version | 28
ROM/Recovery modversion | OmniROM-9-20191115-guacamole-HOMEMADE
Device Recovery | TWRP 3.3.1-72-26af64d9
Basically, the Omni junk is still on there somehow - even after the MSM flash, even after I upgraded to the latest Android Pie build before attempting all this. So I am fairly sure my partitions are messed up indeed. But how do I fix this? How can I re-create the factory / normal state?
Ps.: Attached the full log.

Stock factory reset? Twrp factory reset? I know you're thinking, if msm didn't work this won't. I am too. But you didn't mention and it sounds like it's worth a shot.

h8Aramex said:
So I did a big mistake. I tried to install OmniROM - the Android Q based one from XDA.
Turns out, it's a big mess. Not trying to attack the developer because whatever - maybe I messed up.
My partitions got messed up as well it seems.
Point is: I ended up with a bricked phone.
I tried everything (and I mean that). In the end, I used the Qualcomm MSM Tool to flash a v9 update.
My phone booted up. All good, right?
Well, I wanted to install Lineage 16 all along, so I started with that at this point.
oem unlock, copy up the .zip, boot twrp, flash image.
Also very good, no errors. Yay!
Here comes the twist.
Upon install LOS, I read you must flash a GApps pack too. No worries, I grabbed one, pushed to the /sdcard/ location and tried to flash it.
Not enough space. On a 256 gb wiped phone. Interesting. But there is a log.
And this shocked me.
Code:
ROM Android version | 9
ROM Build ID | omni_guacamole-eng 16.1.0 PQ3B.190801.002 eng.mauron.20191115.213714 test-keys
ROM Version increment | 1907281556
ROM SDK version | 28
ROM/Recovery modversion | OmniROM-9-20191115-guacamole-HOMEMADE
Device Recovery | TWRP 3.3.1-72-26af64d9
Basically, the Omni junk is still on there somehow - even after the MSM flash, even after I upgraded to the latest Android Pie build before attempting all this. So I am fairly sure my partitions are messed up indeed. But how do I fix this? How can I re-create the factory / normal state?
Ps.: Attached the full log.
Click to expand...
Click to collapse
I use this tool to restore it to the original, you can test https://forum.xda-developers.com/android/software/tool-tool-one-driversunlocktwrpfactory-t3358711 and use https://toolaio.tk/fastboot-roms/ Manage just let it run for about 5-10 minutes, everything is intact.

สุรินทร์ พลโธา said:
So I did a big mistake. I tried to install OmniROM - the Android Q based one from XDA.
Turns out, it's a big mess. Not trying to attack the developer because whatever - maybe I messed up.
My partitions got messed up as well it seems.
Point is: I ended up with a bricked phone.
I tried everything (and I mean that). In the end, I used the Qualcomm MSM Tool to flash a v9 update.
My phone booted up. All good, right?
Well, I wanted to install Lineage 16 all along, so I started with that at this point.
oem unlock, copy up the .zip, boot twrp, flash image.
Also very good, no errors. Yay!
Here comes the twist.
Upon install LOS, I read you must flash a GApps pack too. No worries, I grabbed one, pushed to the /sdcard/ location and tried to flash it.
Not enough space. On a 256 gb wiped phone. Interesting. But there is a log.
And this shocked me.
I use this tool to restore it to the original, you can test https://forum.xda-developers.com/android/software/tool-tool-one-driversunlocktwrpfactory-t3358711 and use https://toolaio.tk/fastboot-roms/ Manage just let it run for about 5-10 minutes, everything is intact.
Click to expand...
Click to collapse
It's all good then? Got everything working?

GeekMcLeod said:
It's all good then? Got everything working?
Click to expand...
Click to collapse
It works quite well as a pleasant machine.

GeekMcLeod said:
It's all good then? Got everything working?
Click to expand...
Click to collapse
In my case, no, the MSM Tool, the full OTA image, etc... they all ended up being installed in a broken state.
I'll try the toolkit now. To be fair I tried to use the All In One kit multiple times in the past but I have been warned against it several times on the forums and on the XDA/OnePlus Discord servers. That said, there is not much to lose I suppose.
So.
I did everything but it's still broken. Guess I'll have to send the phone to OP at this rate. Thanks """developer""" guy.
- Flashed with MSM. That put me back to 9.
- Flashed the latest OOS as recommended on top.
- Used official downgrade package to 9 that put my phone to AA from BA.
- Used the latest OOS9 BA package - as recommended by OP, that put my phone on latest OOS9 & correct version.
- Booted TWRP, flashed LOS16 (I am on latest OOS9 at this point), great.
- Tried flashing OpenGapps... same error. Same Omnirom message. (not enough space)
So yea, the partitions are pretty much broken ever since I installed Omni 10.
GG, one more broken phone thanks to the rom. How can this site and moderators tolerate this?

h8Aramex said:
In my case, no, the MSM Tool, the full OTA image, etc... they all ended up being installed in a broken state.
I'll try the toolkit now. To be fair I tried to use the All In One kit multiple times in the past but I have been warned against it several times on the forums and on the XDA/OnePlus Discord servers. That said, there is not much to lose I suppose.
So.
I did everything but it's still broken. Guess I'll have to send the phone to OP at this rate. Thanks """developer""" guy.
- Flashed with MSM. That put me back to 9.
- Flashed the latest OOS as recommended on top.
- Used official downgrade package to 9 that put my phone to AA from BA.
- Used the latest OOS9 BA package - as recommended by OP, that put my phone on latest OOS9 & correct version.
- Booted TWRP, flashed LOS16 (I am on latest OOS9 at this point), great.
- Tried flashing OpenGapps... same error. Same Omnirom message. (not enough space)
So yea, the partitions are pretty much broken ever since I installed Omni 10.
GG, one more broken phone thanks to the rom. How can this site and moderators tolerate this?
Click to expand...
Click to collapse
Why so salty? Also since msm resets your device to the factory stage, I'm pretty sure it's twrp that's messing things up. It's also funny how you said that you're not trying to attack the devs, then you blatantly attack them a few posts later. The devs are pretty much doing everything for free.
Edit: Just checked your logs and surprise surprise! You're using twrp 3.3.1-72, the one that was known to cause issues! Use .70 or .74, and how about you do some research before blatantly attacking the dev, Mr. "Senior Member".

Kaz205 said:
t's also funny how you said that you're not trying to attack the devs
Click to expand...
Click to collapse
I have nothing but respect to the real developers of XDA. Would help them in any way I just can and I am grateful for their work.
However, check the OP in Omni 10's thread. I'd call that person anything, but a "developer". That person does not belong to this crowd in my book.
Anyhow, let's get back to the main topic. I managed to fix everything up and recovered the phone.
Once I upload everything to a mirror I'll update the thread with info.
Thanks for the twrp tip by the way.

The best way I find is use a fastboot rom with flash all. I like to boot to twrp first format data then boot back to bootloader and the use the flash all file inside whatever fastboot rom I decide to use

h8Aramex said:
In my case, no, the MSM Tool, the full OTA image, etc... they all ended up being installed in a broken state.
I'll try the toolkit now. To be fair I tried to use the All In One kit multiple times in the past but I have been warned against it several times on the forums and on the XDA/OnePlus Discord servers. That said, there is not much to lose I suppose.
So.
I did everything but it's still broken. Guess I'll have to send the phone to OP at this rate. Thanks """developer""" guy.
- Flashed with MSM. That put me back to 9.
- Flashed the latest OOS as recommended on top.
- Used official downgrade package to 9 that put my phone to AA from BA.
- Used the latest OOS9 BA package - as recommended by OP, that put my phone on latest OOS9 & correct version.
- Booted TWRP, flashed LOS16 (I am on latest OOS9 at this point), great.
- Tried flashing OpenGapps... same error. Same Omnirom message. (not enough space)
So yea, the partitions are pretty much broken ever since I installed Omni 10.
GG, one more broken phone thanks to the rom. How can this site and moderators tolerate this?
Click to expand...
Click to collapse
Which Gapps package are you trying to flash? Because the Google apps packages are not supported in any way by LineageOS.
https://wiki.lineageos.org/gapps.html
Also if you go into twrp and then in the advanced wipe menu, there is provisions to resize your file system. I have had to use that in the past in order to be able to flash gapps, exactly as you described. Just swipe to resize the partition. Should fix your problem (provided you are installing the correct gapps in the first place).

stable android 11 released for op7p

why is no one discussing stable android 11 for op7p ? got my update round 3 a.m. this morning. been searching all day for a working twrp since the stable android 11 been released. no luck though......

Hi,
Today I installed the update manually and my phone keeps flashing the TWRP load-screen at boot. It's stuck now. Is that because there is no compatible TWRP version yet? How do I fix this?? Any idea?

There is no working TWRP yet for Android 11. You'll need to flash the stock boot.img or rooted boot.img from one of the threads in the news, guides section.
Edit: TWRP screen flashing is because it's incompatible. I had the same issue on the open betas.

Have the exact same issue as above, Twrp screen flashing, cannot boot back to normal even with adb... anybody has a rooted boot.img link that knows works with Android 11?
Should have checked on xda first *slaps his face*
Always check xda first *slaps his face again*
EDIT: For other poor saps with this issue use this -> https://www.androidfilehost.com/?fid=2188818919693770594 I didnt managed to get booted with rooted img but the original boot img file worked well ... at least I got a phone now...

im on 10.3.8 and rooted..
can i just do the same old process.. twrp isnt an issue as long as may apps are safe and root..

santiagoruel13 said:
im on 10.3.8 and rooted..
can i just do the same old process.. twrp isnt an issue as long as may apps are safe and root..
Click to expand...
Click to collapse
No, its not the same process.... For me for example I couldnt get wifi to actually work on rooted image AND you lose the ability to do backups via TWRP..... Refer here for the latest on this: https://forum.xda-developers.com/t/...p-recovery-for-oneplus-7-pro.3931322/page-153

dejjem said:
No, its not the same process.... For me for example I couldnt get wifi to actually work on rooted image AND you lose the ability to do backups via TWRP..... Refer here for the latest on this: https://forum.xda-developers.com/t/...p-recovery-for-oneplus-7-pro.3931322/page-153
Click to expand...
Click to collapse
I mean.. same steps.. that ive used so far amd retain its root.
1. Download rom via o2 updater
2. Flash it via local update
3. Install magisk to inactive slot
4. Reboot.
So if i do this.. wifi wont work??? Is that it???
Finished updating my phone..after downloading it for about 2 hours.
And im quite satisfied with the results. No problems whatsoever..

Glad for you... You probably had already removed the encryption on your mobile... from what I'm reading that is the main incompatibility issue with TWRP...
FWIW after playing around for a day, I had to revert everything Phone wifi was weird (weirder with root and all mods disabled) and system was a little unstable in some 3p apps and there seems to be some bugs with the phone screen 60/90 refresh... Gonna wait a bit to update again.

dejjem said:
Glad for you... You probably had already removed the encryption on your mobile... from what I'm reading that is the main incompatibility issue with TWRP...
FWIW after playing around for a day, I had to revert everything Phone wifi was weird (weirder with root and all mods disabled) and system was a little unstable in some 3p apps and there seems to be some bugs with the phone screen 60/90 refresh... Gonna wait a bit to update again.
Click to expand...
Click to collapse
i dont mind not having TWRP for the meantime,, i just used TWRP previously for flashing CUSTOM kernels.. hehehehe.
anyways, what problem have you encountered regarding wifi?? i dont seem to experience those,, maybe because i came from stable oos 10.3.8..
what app crashed and problems have you encountered???

I super messed up, need suggestions. [I fixed it like the chad I am :) ]

Cant flash twrp nor the patched magisk boot img to both slot a and b.
Bootloader is unlocked.
Flashing scripts via .bat files for stock zips of both android 10 and 12 results in "FAILED (remote: Partition product not found)" or "FAILED (remote: variable not found)" respectively.
I have no recovery.
When I had twrp, I've made the mistake of wiping my whole android 12 data, storage, and system and flashing an android 10 rom without reading up of the separate a and b boot slots nor the effects of my actions leading to bootlooping. (I've done with this other devices before with no problems). This in turn wiped the twrp recovery I had flashed and left me only fastboot commands and a twrp version up to 3.3 and 3.2 with no hope of getting usb otg to work as it was only available with the later versions of twrp and since I and now technically on an android 10 bootloader, any attempt at that time to flash twrp 3.6 was met with a (remote: Error calling AvbLoadAndVerifyBootImages Load Error) or some kind of other error I have no logs for. Now I cant even tetherboot to twrp 3.2 nor 3.3 and I get that error regardless.
[Boots to bootloader no matter what. Shows as UFS:Micron, Error reason - reboot bootloader - bootloader version is b1c1-0-4-7617406]
I believe I can get access to internal storage to flash these updates once I get a recovery tethered from the bootloader. I do not know if its possible to boot to fastbootd or whatever its called (used for write permissions/sideload update zips) even if I hadn't gotten into this predicament. I will be buying another Pixel 3 in the meantime as I have money to burn and like to hurt myself financially, and emotionally to get to my goal with this device. ( Didn't buy another one, I was committed to the cause!)
I am not a noob nor a pro, but somewhere in between. My biggest point of failure is not reading up on how the partitions are set up and the various issues others had when flashing android 10 and 11 roms. Any suggestions other than "uPdAtE tHe fAsTbOoT aNd AdB dRiVeRs" are not welcomed. Thank you. I will update once I find a soluton to my problem Which I Will.
Again, my main concern right now is getting tethered twrp to work again and need suggestions. I have older versions of platform tools and the latest so please non of those comments I see on literally every other thread.
Edit: I didn't mention this before, but I did have the ability yo sideload when I had twrp at the time before crapping everything out the window, but nothing would work and gave up. Just wanted to add if anyone was wondering.

First update, I used the propriatary "Tool All In One Tool" and I was able to boot to fastbootd, and wipe my data and storage, while updating my stock zip to android 12. Now I can tetherboot twrp 3.6.1_11-0 with the option for usb otg, wish me luck boys. I'm in.

Second update. Still stuck on first update, but weighing my options in the meantime. I flashed twrp via the flash current twrp option, but when I boot to it, touch is disabled so thats great... I can fast boot to only the twrp versions after 3.6+, so not so bad. I have no os installed, but I will try my hand again at that tool all in one tool again. I'll update tomorrow if anything comes of it.

3rd update. FROM THE BRINK OF DEATH!!! WHOOOOOOOOOO!!!!! I got the pixeldust rom flashed and working like a BOSS!!!!! You won't believe the 2 days I've had trying to get this thing to work. All in all 1 out of my 3 flashdrives finally worked with otg. I had a windows recovery drive premade on it so I just copied and pasted the files there without a hitch! Thank you Google for having to make me miss work and actually do research to get this thing working again! Thank you for the guys at Tool All In One Tool for making this recovery possible, I will shout out your thread. If anyone who's in a similar situation needs any help from me or any info, I'll be glad to help. This will be the second to last update. I can also make phone calls and use data so Pixel Dust rom is good to go if that was one of your concerns. See ya!

Final update, I got crdroid flashed with root and safetynet passed, I just found out that google Pay was imbedded in gapps so now I don't need the pay app anymore to do transactions! My banking app also works, got vanced finally installed (couldn't do it on regular stock ROM) some glitches with the ROM here and there but no worries. For who ever reads this. There's hope. I fd up as bad as you can get shy of a hard brick. I still don't know too much but learned near twice as much as I knew just a few days ago. If you need help just DM me and I'll work my hardest to bring the light. This phone is absolutely amazing and on god wished google was a better company to praise. I have more plans for these phones and hope more Roms come out to support it.
I have one question however, how do I make a backup of my system/system_ext partitions? I can make a back up of everything else but that with these two Roms... I have a backup of it with my stock ROM, but it resumed to mount when I used otg... Didn't try internal yet but I'll assume the same, is it a glitch with current twrp?