Database Info

Thought I was doing so well; tablet won't boot to OS

Hey folks; I'm hoping I can get some advice or pointers, or maybe just a slap upside the head with something I've missed.
I have one of the original Shield tablets, and played around with it quite a lot, installing various custom ROMs from the marvelous directions I've found here. When the battery thing happened, I submitted the required info and happily received my new tablet. The original was rooted and customised still, kill-switch averted, and I had two working tablets. I gave the new stock one to my wife.
But then, about three months ago, I was playing with mine again installing a newer ROM than the one I was using (I *think* I was going from an older Bliss rom to one of the Cyanogen), and ... Something Happened (tm). The tablet rebooted in the middle of everything, and now won't boot to an image.
I'm on Windows 10 now, and had some fun getting the drivers working, but they seem to. I can communicate with the tablet through Fastboot, but ADB doesn't see it. I've flashed several versions of TWRP to the tablet, and can boot into that recovery - both through Fastboot and the tablet's power+vol-dn buttons. I've used TWRP to flash several different ROMs, and it *appears* to work (there are no errors), but when I reboot the tablet .... nada. Nothing but the Nvidia boot screen for days.
So now... what have I missed? I'm a little reluctant to flash a stock ROM, but I'm at a loss. I used to have more time to fiddle and figure, and I'm afraid that my impatience is going to kill the thing.

Format system and data see if that works

You need to have the latest bootloader to run the latest roms.
Sent from my ZTE A2017U using Tapatalk

skooter32 said:
Format system and data see if that works
Click to expand...
Click to collapse
Have done, but I'll try it again. Thanks

lafester said:
You need to have the latest bootloader to run the latest roms.
Sent from my ZTE A2017U using Tapatalk
Click to expand...
Click to collapse
I've tried the latest and the not-so-latest, all with similar results.

Hnefatafl said:
I've tried the latest and the not-so-latest, all with similar results.
Click to expand...
Click to collapse
so you wan t your "burning" tablet set again stock?
Did you read about "recovery images" for shield tablet?
If fastboot is working you can flash the recovery image and all will update to the latest(blob,system,boot, etc)
flash latest twrp for shieldtablet.
after that use the nomoreota.zip to prevent the software brick from nvidida

Hnefatafl said:
Have done, but I'll try it again. Thanks
Click to expand...
Click to collapse
Also format data system to something other than ext4 then re format it back

skooter32 said:
Also format data system to something other than ext4 then re format it back
Click to expand...
Click to collapse
can I ask what that should bring?

wiQbold said:
so you wan t your "burning" tablet set again stock?
Did you read about "recovery images" for shield tablet?
If fastboot is working you can flash the recovery image and all will update to the latest(blob,system,boot, etc)
flash latest twrp for shieldtablet.
after that use the nomoreota.zip to prevent the software brick from nvidida
Click to expand...
Click to collapse
No, I don't want it stock at all, I was just worried that was my only option to get this thing to respond again. I was running BlissPop v.somethingorother, but wanted to update. That's when things went awry.

Right, well it looks like I've got this thing going. I could flash TWRP 3.1.0-0, but not any 3.1.1. Cyanogenmod 12 worked. Reading up a little more (it got slow at work for a couple of days...) I flashed the firmware to 5.0, and could now install TWRP 3.1.1-1! Then I could install (in this case) Lineage 14.1, which *almost* worked. It booted, but there's no wifi.
Then I found a suggestion - I think it was on these forums somewhere - and restarted. Wiped all data again, flashed Cyanogenmod 12, no gapps. Restarted, checked everything including wifi, and is good. Rebooted back into recovery, performed a factory reset, then installed Lineage 14.1 and gapps. When it rebooted, everything is working!
So. Firmware. Huh.
Thanks all.

Hnefatafl said:
No, I don't want it stock at all, I was just worried that was my only option to get this thing to respond again. I was running BlissPop v.somethingorother, but wanted to update. That's when things went awry.
Click to expand...
Click to collapse
do not know if you need the bootloader(blob) from nougat to boot up, that lafester told you. but that sounds plausible. skooter says something from re-formating. so if you tried that all and nothing changes? cache and data partition you wiped also, so it has to be work for my understanding.
went always stock, so can t help you..
but you can use recovery images > twrp > bliss/linage. no need to boot up stock?

wiQbold said:
can I ask what that should bring?
Click to expand...
Click to collapse
I have had similar issues and I tried everything even this plus what harm is it going to be and as the fellow below said if ur in fastboot and recovery with no issues then surely u should be flashing stick to fix Ur problem ?

Phone bricked with the latest Oreo security patch

Mine is the AL-10. I flashed the Oreo update a while back and it was working just fine. Yesterday I received a 1MB security patch through OTA which simply bricked my phone. I was on my way home from college, the update popped up and as it said only 1MB, I proceeded with it and my phone didn't boot up after that. Tried every basic fix including factory reset but it's still not booting up!
Note: The changelog in the patch said it fixed in-game sound issue.

I was finally able to fix it by flashing system,cust,recovery manually. Dunno why Huawei pulled this stunt on me! Lost all my data

I identified the issue: It's Magisk.
The patched boot image causes the device to get stuck at boot.

Yup. You're suppose to flash the stock boot and recovery for an OTA (unless you have the erecovery flashed as TWRP like I do). I too did the same thing once, learned my lesson lol.

agraceful said:
Yup. You're suppose to flash the stock boot and recovery for an OTA (unless you have the erecovery flashed as TWRP like I do). I too did the same thing once, learned my lesson lol.
Click to expand...
Click to collapse
Tnx, I learned it the hard way too. But the thing is, Magisk isn't working anymore after the update.

I received it too .and my phone is working well
---------- Post added at 06:50 AM ---------- Previous post was at 06:46 AM ----------
SirDarknight said:
Tnx, I learned it the hard way too. But the thing is, Magisk isn't working anymore after the update.
Click to expand...
Click to collapse
flash it By Adb

How did you flash Magisk? Which TWRP did you use? Could you tell me? I'm lost without V4A on my phone LOL

OTA update with unlocked bootloader

I'll be switching to Project Fi soon from ATT. With the switch I'll lose my only reason for being rooted (wifi hotspot) since Fi offers hotspot for no extra charge. Am I able to install OTA updates with an unlocked bootloader if everything else is stock (ie. not rooted)?

geicogecko said:
I'll be switching to Project Fi soon from ATT. With the switch I'll lose my only reason for being rooted (wifi hotspot) since Fi offers hotspot for no extra charge. Am I able to install OTA updates with an unlocked bootloader if everything else is stock (ie. not rooted)?
Click to expand...
Click to collapse
I think you should be able to
Sent from my Pixel 2 XL using Tapatalk

You cannot take OTA updates normally with an unlocked bootloader. The phone will download the update, but the update will fail.
You CAN update manually using either OTA or factory images from here and following my guide here.
To sideload OTA images using either stock recovery or TWRP, follow the instructions here.

Excellent, thank you. I'd rather not wipe the phone so I guess I'll settle for sideloading OTAs. And it would be nice to be able to root later on if I decide I need to.

geicogecko said:
Excellent, thank you. I'd rather not wipe the phone so I guess I'll settle for sideloading OTAs. And it would be nice to be able to root later on if I decide I need to.
Click to expand...
Click to collapse
The nice thing about getting an OTA is that it installs in the background and a quick reboot to finish the update. Why not start fresh with a full wipe since you're changing carriers. It's not super difficult to get it set up again and now you have a clean install. I say that because I'm about to suggest you relock the bootloader and see how it runs. You obviously have the oem switch enabled so its really easy to go back and unlock if you so desire. Just a thought. I liked Project Fi when I had it but it didn't make financial sense in my case with a family plan. Good luck.

geicogecko said:
Excellent, thank you. I'd rather not wipe the phone so I guess I'll settle for sideloading OTAs. And it would be nice to be able to root later on if I decide I need to.
Click to expand...
Click to collapse
Just for ****s and giggles, I tried installing the OTA zip through TWRP. Worked like a charm.
Please note that if you do this, the kernel and recovery will revert to stock, so you'll have to boot TWRP via fastboot and reflash.

socal87 said:
Just for ****s and giggles, I tried installing the OTA zip through TWRP. Worked like a charm.
Please note that if you do this, the kernel and recovery will revert to stock, so you'll have to boot TWRP via fastboot and reflash.
Click to expand...
Click to collapse
Did you let it reboot on its own, or did you manually boot into TWRP, find the file and flash it that way?

k.s.deviate said:
Did you let it reboot on its own, or did you manually boot into TWRP, find the file and flash it that way?
Click to expand...
Click to collapse
I'm not sure I understand your question. I flashed the OTA file in recovery using TWRP. There is no way to flash things in recovery without rebooting...

socal87 said:
I'm not sure I understand your question. I flashed the OTA file in recovery using TWRP. There is no way to flash things in recovery without rebooting...
Click to expand...
Click to collapse
After the OTA downloaded, did you just reboot when it asked you to, or, did you manually boot into TWRP and find the OTA file to flash. OR, did you download the OTA from an third party and flash that way.

k.s.deviate said:
After the OTA downloaded, did you just reboot when it asked you to, or, did you manually boot into TWRP and find the OTA file to flash. OR, did you download the OTA from an third party and flash that way.
Click to expand...
Click to collapse
I downloaded the OTA directly from https://developers.google.com/android/ota, then rebooted into TWRP and flashed the zip.
I'm on stock software with the exception of Magisk and Flash kernel, so OTAs always fail. Thus, I have Automatic System Updates turned off in Developer Options.
Regardless of how you do it, the OTA will always overwrite /boot, so you'll lose custom kernel and recovery.

bobby janow said:
The nice thing about getting an OTA is that it installs in the background and a quick reboot to finish the update. Why not start fresh with a full wipe since you're changing carriers. It's not super difficult to get it set up again and now you have a clean install. I say that because I'm about to suggest you relock the bootloader and see how it runs. You obviously have the oem switch enabled so its really easy to go back and unlock if you so desire. Just a thought. I liked Project Fi when I had it but it didn't make financial sense in my case with a family plan. Good luck.
Click to expand...
Click to collapse
I may do this eventually. I want to see what having a non-rooted phone is like first. I haven't had a non-rooted phone in probably eight years. If I find out I really don't need root for anything, I may relock the bootloader.

socal87 said:
Just for ****s and giggles, I tried installing the OTA zip through TWRP. Worked like a charm.
Please note that if you do this, the kernel and recovery will revert to stock, so you'll have to boot TWRP via fastboot and reflash.
Click to expand...
Click to collapse
Wait... do you mean you actually flashed the downloaded, official OTA zip using TWRP over a rooted OS with no issues at all?... Interesting. Was that flashed OTA, a security patch only?
Sent from my Moto Z2 Play using XDA Labs

The Analog Kid said:
Wait... do you mean you actually flashed the downloaded, official OTA zip using TWRP over a rooted OS with no issues at all?... Interesting. Was that flashed OTA, a security patch only?
Sent from my Moto Z2 Play using XDA Labs
Click to expand...
Click to collapse
When the 9.0 update came out, I installed that via TWRP. Again, as noted, this will install it to both slots, and when it boots, it will boot via the other slot.
So, for instance, if you happen to be on slot A, and you install the OTA, it installs the stock kernel to slot B, and boots via that slot - stock kernel, no Magisk or TWRP. After it boots , when it is "Finishing update", it installs the stock kernel to slot A.
So, every time you flash an OTA, you need to let it boot, then reboot into bootloader, boot TWRP via fastboot, install TWRP, install kernel, and Magisk.

geicogecko said:
I may do this eventually. I want to see what having a non-rooted phone is like first. I haven't had a non-rooted phone in probably eight years. If I find out I really don't need root for anything, I may relock the bootloader.
Click to expand...
Click to collapse
So... How's the non-rooted phone experience going so far? Because I can't get fully used to the experience yet (I have this phone for a month now) and coming from... well, ALL of my previous devices rooted too (about an eight year span as well). Even though the phone in question (Z2 Play) runs very smooth and plain "force-close-less" (yeah, you know root) I still don't find myself quite at home without Xposed and it's useful modules, for example... Oreo is nice indeed but, on the other hand, I also have this little tiny bit temptation for Android 9... Sure, if it ever lands on my phone in less than a year! Quite a bet.
Sent from my Moto Z2 Play using XDA Labs
---------- Post added at 10:31 PM ---------- Previous post was at 10:28 PM ----------
socal87 said:
When the 9.0 update came out, I installed that via TWRP. Again, as noted, this will install it to both slots, and when it boots, it will boot via the other slot.
So, for instance, if you happen to be on slot A, and you install the OTA, it installs the stock kernel to slot B, and boots via that slot - stock kernel, no Magisk or TWRP. After it boots , when it is "Finishing update", it installs the stock kernel to slot A.
So, every time you flash an OTA, you need to let it boot, then reboot into bootloader, boot TWRP via fastboot, install TWRP, install kernel, and Magisk.
Click to expand...
Click to collapse
... That's only if you want to preserve root, I guess? AND for Pixel devices, right?
Sent from my Moto Z2 Play using XDA Labs

The Analog Kid said:
So... How's the non-rooted phone experience going so far? Because I can't get fully used to the experience yet (I have this phone for a month now) and coming from... well, ALL of my previous devices rooted too (about an eight year span as well). Even though the phone in question (Z2 Play) runs very smooth and plain "force-close-less" (yeah, you know root) I still don't find myself quite at home without Xposed and it's useful modules, for example... Oreo is nice indeed but, on the other hand, I also have this little tiny bit temptation for Android 9... Sure, if it ever lands on my phone in less than a year! Quite a bet.
Sent from my Moto Z2 Play using XDA Labs
---------- Post added at 10:31 PM ---------- Previous post was at 10:28 PM ----------
... That's only if you want to preserve root, I guess? AND for Pixel devices, right?
Sent from my Moto Z2 Play using XDA Labs
Click to expand...
Click to collapse
Yes. If you're otherwise stock aside from an unlocked bootloader, you can sideload the OTA zip...or, copy it to internal storage, reboot to recovery, and install it that way.
If you want to keep TWRP, you'll have to boot the TWRP image after installing and rebooting, then flash TWRP. The OTA does not wipe data (obviously); it just returns everything in /boot and /system to stock.

The Analog Kid said:
So... How's the non-rooted phone experience going so far? Because I can't get fully used to the experience yet (I have this phone for a month now) and coming from... well, ALL of my previous devices rooted too (about an eight year span as well). Even though the phone in question (Z2 Play) runs very smooth and plain "force-close-less" (yeah, you know root) I still don't find myself quite at home without Xposed and it's useful modules, for example... Oreo is nice indeed but, on the other hand, I also have this little tiny bit temptation for Android 9... Sure, if it ever lands on my phone in less than a year! Quite a bet.
Click to expand...
Click to collapse
So I actually took the advice and relocked the bootloader. No issues. I think there was one app that I would've needed root for, but I can't remember what it was. I didn't use Xposed. I don't even know if it works on the Pixel. Like I said in the opening post, I only needed it to enable wifi hotspot, so others may notice it more.

Were you able to update with ota after relocking your boot loader? I tried it after and the update would install but stay at 0% then eventually fail. Any suggestions? Thanks.

ychongy13 said:
Were you able to update with ota after relocking your boot loader? I tried it after and the update would install but stay at 0% then eventually fail. Any suggestions? Thanks.
Click to expand...
Click to collapse
You should be able to install the latest OTA image using stock recovery:
https://developers.google.com/android/ota

Downgrade from 9.0.2 to 9.0.1?

Hi, just tried to do this by flashing the old zip trough TWRP, but i always end to boot in recovery, maybe i'm doing something wrong...?

I tried this today and happened the same, i guess you have to clean flash to downgrade.
Also a tip, if you got stuck in recovery and yet cannot decrypt (doesn't ask for password/pin in TWRP), boot to fastboot mode, use the command "fastboot boot <the img file name for twrp>" so that you can boot directly to the img file from your PC. This way it will ask for your password.

Killua96 said:
Hi, just tried to do this by flashing the old zip trough TWRP, but i always end to boot in recovery, maybe i'm doing something wrong...?
Click to expand...
Click to collapse
You might try flashing again when you get booted back to TWRP. That way, you can get 9.01 flashed to both slots if it's not already. No guarantees, but it's worth a try.

maigre said:
You might try flashing again when you get booted back to TWRP. That way, you can get 9.01 flashed to both slots if it's not already. No guarantees, but it's worth a try.
Click to expand...
Click to collapse
I tried this way too but keep getting booted back to TWRP. Even did a wipe of the caches, system and data (not internal storage).
Is there anything I can still try?

jiatern said:
I tried this way too but keep getting booted back to TWRP. Even did a wipe of the caches, system and data (not internal storage).
Is there anything I can still try?
Click to expand...
Click to collapse
Flash Magisk again.

maigre said:
Flash Magisk again.
Click to expand...
Click to collapse
I did as well but it didn't help. Still the same.

jiatern said:
I did as well but it didn't help. Still the same.
Click to expand...
Click to collapse
Backup all your data outside the phone and flash a fastboot rom, it worked with me stuck in fastboot and I got back from that horrible 9.0.2

Killua96 said:
Backup all your data outside the phone and flash a fastboot rom, it worked with me stuck in fastboot and I got back from that horrible 9.0.2
Click to expand...
Click to collapse
Why horrible?

PuCiNhOOO said:
Why horrible?
Click to expand...
Click to collapse
Keyboard continuously crash 'cause the new gesture system, that have longer animations and the recent app one loses the vibration feedback and it' s also a lot confusing.
Anyway you can read the same things in the ota's thread, unfortunately are widespread problems

​
Killua96 said:
Keyboard continuously crash 'cause the new gesture system, that have longer animations and the recent app one loses the vibration feedback and it' s also a lot confusing.
Anyway you can read the same things in the ota's thread, unfortunately are widespread problems
Click to expand...
Click to collapse
I think they pushed the update too fast from beta to stable... But yes, agree with the gestures bug... Its a fact, but the other stuff is good

Killua96 said:
Backup all your data outside the phone and flash a fastboot rom, it worked with me stuck in fastboot and I got back from that horrible 9.0.2
Click to expand...
Click to collapse
Can you link me to the exact fastboot rom you flashed? Some said I have to use the downgrade zip from OnePlus to Oreo 5.1.1 then only upgrade to 9.0.1. The OP of the fastboot rom said the rom is not for downgrading.
Did you downgrade to Oreo first or directly flash the 9.0.1 fastboot rom?

jiatern said:
Can you link me to the exact fastboot rom you flashed? Some said I have to use the downgrade zip from OnePlus to Oreo 5.1.1 then only upgrade to 9.0.1. The OP of the fastboot rom said the rom is not for downgrading.
Did you downgrade to Oreo first or directly flash the 9.0.1 fastboot rom?
Click to expand...
Click to collapse
I've wiped everything, then downgraded to Pie directly, but I was in a slightly different situation (only fastboot available).
Just to be sure flash the Oreo one and then upgrade to Pie.

With the whole A/B partition layout it should be easier to downgrade too right?

Update issue

Hi, i updated my xz premium to pie and installed most recent pie for my phone, (47.2.A.10.107) but I installed TWRP and tried to flash magisk but i couldnt do it gives error, (encryption related error) , twrp cant flash encrypted rom magisk, i wiped all data in order to avoid encryption but i every time when i flash new rom it is encrypted , how can i flash pie latest version and root my phone?

Never had the decryption issue stop Magisk but try this first and then Magisk.
https://forum.xda-developers.com/android/software/universal-dm-verity-forceencrypt-t3817389

bobsright said:
Never had the decryption issue stop Magisk but try this first and then Magisk.
https://forum.xda-developers.com/android/software/universal-dm-verity-forceencrypt-t3817389
Click to expand...
Click to collapse
finally i could root my device but with different method , now problem is i cant flash anything with using twrp, it gives mounting error, i dont want to delete my data again because i installed a lot of programs, Can you help me?
i think it is ENCRYPTION problem

murad1990 said:
finally i could root my device but with different method , now problem is i cant flash anything with using twrp, it gives mounting error, i dont want to delete my data again because i installed a lot of programs, Can you help me?
i think it is ENCRYPTION problem
Click to expand...
Click to collapse
If the issue is with mounting the storage where your, whatever it is you're trying to flash, then put that file on an external drive and connect it to your phone via an OTG cable. Once you flash that zip in my last response, you won't have this issue. How did you root your phone?

Ok i unlocked bootloader, flashed stock pie rom, then flashed twrp but not latest one, because latest gave me mount error, i flashed 3.2.1 it solved my mounting problem, then i flashed janjan kernek then magisk. But problem is i lost most of functionalities of my phone(drm key lost) is there any way to restore it? Or is there any kernel?

murad19900 said:
Ok i unlocked bootloader, flashed stock pie rom, then flashed twrp but not latest one, because latest gave me mount error, i flashed 3.2.1 it solved my mounting problem, then i flashed janjan kernek then magisk. But problem is i lost most of functionalities of my phone(drm key lost) is there any way to restore it? Or is there any kernel?
Click to expand...
Click to collapse
Afraid not. There are steps to take to get temp root to back up those keys before unlocking the bootloader, and then restoring the keys after unlock. There's a whole thread on that here: https://forum.xda-developers.com/xp...devonly-exploits-temp-root-to-backup-t3795510. I never bothered with all that and have not had any issues that concern me. What issues are you having?

Image enhancement doesnt work i think, and other camera function as well, any other function?

murad19900 said:
Image enhancement doesnt work i think, and other camera function as well, any other function?
Click to expand...
Click to collapse
Yeah, I couldn't tell you. As for me the phone still does what I need it to do. As far as the camera it still takes the pics I need it to take. I don't social media so I don't need the special effects/enhancements people use for that. When it comes to taking pictures, that's what I have a camera for. My phone is for calls, text, and email and web search when I'm not near my computer. You could try other phone apps to see if they replace what's lost. I believe photo quality is as stock.

Sorry I mean video image enhancement, and i want to ask question, do you think i should stay stock rom or use one of these carbon, existenz...

murad19900 said:
Sorry I mean video image enhancement, and i want to ask question, do you think i should stay stock rom or use one of these carbon, existenz...
Click to expand...
Click to collapse
Well same answer as far as video too.
I'm using eXtstenZ Pie. It's the stock rom with enhancements. It's stable and customizable. I would install the Aroma Add-on at the same time. I've tried Carbon but I had sim card issues, that may be resolved by now. There is also a Lineage 17.1 available but I don't believe it's reliable enough for a main phone. If you don't mind experimenting you could try that as it's Android 10. There's Tomahawk Project if you want barebones and get away from Google. CrDroid also out there. These last three I have not tried.

I am sorry but, i dont know so much about the android phones, I am using stock, exitstenz looks like custom rom, or is this modified stock? Because i lot changes and it doesnt have stock rom interface

murad19900 said:
I am sorry but, i dont know so much about the android phones, I am using stock, exitstenz looks like custom rom, or is this modified stock? Because i lot changes and it doesnt have stock rom interface
Click to expand...
Click to collapse
Yes, it's a modified stock rom.

To flash it, i just need to fladh latest firmware then twrp, then magisk?

If you're already on .107, you're good there. Then from twrp flash eXistenZ then flash Magisk. If you're going to use Aroma Add-on flash it next and you should be good to go. Also, with this phone you can install twrp in recovery partition so you don't have to use a computer every time you want to use twrp. You have to unzip it and save the .img file to where you put all the other files you flash, then from twrp install the image to recovery partition. Then next time you need to flash something, hold power and volume down at the same time (after turning phone off) when the screen just starts to light up release the buttons and it'll boot into twrp.

Thanks, but i have a another question, i flashed 47.2.a.6.30 version pie with using emma, and used janjan kernel of the same version, everyting works without any problem, should i stay this version or i must update to the 107 then root my phone? What is the advantages of the janjan's kernel? and without any custom kernel can i root my phone after flashing 107 firmware?

Don't know anything about the janjan kernel and it's compatibility with eXistenZ. As far as firmware version just flash the eXistenZ version that matches your rom version, I believe there is a list on the first page of the thread that tells which file to use.
---------- Post added at 08:27 PM ---------- Previous post was at 08:19 PM ----------
I don't know anything about the janjan kernel or it's compatibility with eXistenZ.
You can stay on that firmware if you wish. Just use the correct version of eXistenZ for it.
You can root any kernel once bootloader is unlocked. You loose root when you change firmware versions though.