Hi folks,
My NEW (RMA) Shield is rooted / TWRPed / 3.1 / and I applied the noOTA process to it so that they couldn't force-push some future undesirable OTA (or accidental bricking) at me.
Of course, as soon as I get settled in to the new unit with all apps and data where I want them, they do this new OTA.
What's the process for applying the latest OTA, given a rooted, TWRP recovery system? Do I just boot to TWRP, flash the full OTA, reflash noOTA, and be done? But wouldn't the full OTA kill TWRP, so I should reflash it?
Before I mess up this thing I want to make sure I get it right. I've got a PC so I can ADB/Fastboot sideload stuff if need. My main interest is in not messing up my data and apps.
Thanks
:highfive:
Frankenscript said:
Do I just boot to TWRP, flash the full OTA, reflash noOTA, and be done? But wouldn't the full OTA kill TWRP, so I should reflash it?
Click to expand...
Click to collapse
that's correct. this update in particular doesn't upgrade the recovery too, so TWRP won't be affected, but if you have an unlocked bootloader, you can just reflash TWRP at any time. for root, you might also want to flash SuperSU from TWRP (it will ask before rebooting if you don't install it yourself)
Thanks Bogdacutu.
I copied the full US LTE OTA 3.1.1 over to the internal memory (I used the downloads folder), rebooted to TWRP, and flashed it from TWRP. Before rebooting, to be safe I also flashed nomoreota.zip and then supersu.zip. On first boot I got the typical post-OTA "android is updating" thing where it optimizes the apps. Any idea what this app optimization is? I've always wondered... This app optimization process actually took longer than flashing the OTA and stuff.
After finishing the first boot, SuperSU told me it needed to update the binary, which failed. It suggested a reboot.
I rebooted normally (not going into recovery or anything first). This boot stayed on the NVIDIA boot up screen a lot longer than usual. after about 10 minutes like this I turned it off. After it was all the way off I turned it back on again. This time I let it go about 20 minutes. Still nothing past the NVIDIA boot screen. Crap.
I turned it all the way off. Rebooted with volume down button and was relieved to see it give the usual options (continue, recovery, fastboot, etc.). I let it go into recovery and got to TWRP in short order.
At this point I turned it off, as the battery was getting a bit low and I have to take my kid to a soccer game. I'm charging it in powered off mode until I get home.
Any ideas what to do next to get this thing booting into Android again?
Thanks
Marc
After it charged all the way up, when I got back from my kid's game, I booted back to TWRP and reflashed the OTA update.
I then told TWRP to reboot... it said something about should it reflash SuperSU script to preserve root. I agreed and let it reboot. It came back up in Android. I'll explore the situation and report back.
All seems well at this time.
According to rootcheck my root is preserved. SuperSU successfully updated binaries in normal (non-twrp) mode. Checked for system update. It said I was up to date. I booted back to TWRP, flashed nomoreOTA.zip again. Rebooted again, no problems. Back to normal, fully updated. Phew.
I'm not sure what went wrong the first time, but it seems OK now.
Related
Hi folks,
I'm a little kerfluffled if you will by the sheer number of threads - search isn't pointing me to a thread that deals with this - so apologies if this has been answered before.
I originally rooted my phone with towelroot. I kept stock but installed a few things like Xposed, greenify, gravity box, etc... (also i switched to ART some time back).
Once i received the OTA notification, I deactivated greenify and gravity box, then uninstalled them, then "unrooted" the phone using SuperSU. I did forget to reset my "startup animation" but otherwise everything seems fine. The root checker confirms that the phone is no longer rooted. Since i forgot to backup the stock animation i just renamed the .zip and now when i boot the animation just says Android (with a little animation regarding the color of the letters).
I then DLed the update, restarted and approximately 30 ~ 40% of the way through the update screen it freezes up and then i get the little android dude with his belly open and the red error triangle. The text below says "error" but provides no further information. The only way to resolve the issue is to power off the phone and then turn it back on. It goes back into 4.4.4 and works fine but i can't get past that error and have no idea how to tell what the error actually is.
Any suggestions will be appreciated! I would prefer to not have to wipe my phone if at all possible.
You'll must wipe your phone as I am. Then you'll be able to OTA update your phone.
I do exactly like you, but error appears every time in the middle of update process. After wipe everything was fine
Fastboot flash the new factory images one by one. Reboot the bootloader in between each image, just to be safe. Then use chain fire auto root. It'll take you about 20 min. You will lose all info on your device though.
To save your information, you need to get back to totally stock, unmodified 4.4.4. So flash that in fastboot, just don't flash the user data. Then you can accept the ota.
Even modifying the boot image will cause an ota to throw out an error.
Lokke9191 said:
Fastboot flash the new factory images one by one. Reboot the bootloader in between each image, just to be safe. Then use chain fire auto root. It'll take you about 20 min. You will lose all info on your device though.
To save your information, you need to get back to totally stock, unmodified 4.4.4. So flash that in fastboot, just don't flash the user data. Then you can accept the ota.
Even modifying the boot image will cause an ota to throw out an error.
Click to expand...
Click to collapse
Since I'm not concerned about root in Lollipop for now - if i can find the original boot animation and "reinstall it" so to speak - will that allow me to use the ota without having to wipe my phone?
Not for sure. To guarantee it will work. Fastboot flash 4.4.4 system.img, boot.img, and recovery.img.
Lokke9191 said:
Not for sure. To guarantee it will work. Fastboot flash 4.4.4 system.img, boot.img, and recovery.img.
Click to expand...
Click to collapse
okay thanks! i'm going to try and find the original boot animation somehow and if that doesn't solve the problem, i'm going to fastboot everything.
Just dont flash userdata, or you'll lose your setup.
Lokke9191 said:
Just dont flash userdata, or you'll lose your setup.
Click to expand...
Click to collapse
thanks mate!
Hi all,
So I'm far from a noob at at all of this (doing the custom android thing for years). But I'm not exactly constantly fiddling with my phone all the time anymore either. Basically I get a set-up that works for me, and I stick with it.
I've patiently been waiting to update to Lollipop. And today I did it. I did it by flashing the required factory images with fastboot.
AND IT WORKS. No problem. It boots. I go through the initial set-up. I can let it restore all my apps and passwords from the google servers, etc. So far so good.
My problem is that I cannot root. After I try, it bootloops (stuck at the Google splash, with my unlocked icon).
I tried to root before my first boot. I tried after the initial boot (before set-up and signing in). I tried rooting after setting it all up, and singing in, and letting google restore all of my apps. No matter which sequence I try, it will reboot a couple times at the first Google splash, and then fall back to Recovery.
(So, I'm on back on my rooted 4.4.4 nandroid, I think it's Mahdi Rom-- I forget)
Vital Stats:
Trying to install factory images of 5.0.1, all stock (system, boot (kernel), radio, bootloader)
Factory reset
(the above works fine)
TWRP 2.8.1.0
SuperSU-v2.40 (flashed via recovery)
Any ideas? Thanks for any help.
No, but could you try the previous version of SuperSU? Just to rule out the new version that I haven't tested please?
I updated to 5.0.1 earlier
Flashed all the img files exact userdata and then booted in to Android.
I then flashed TWRP 2.8.1.0 and used that to flash SuperSU 2.37
All that worked fine.. I then did a play update and SuperSU updated to 2.40
All working fine as far as I can tell. Apps needing root are working!
iowabeakster said:
Hi all,
So I'm far from a noob at at all of this (doing the custom android thing for years). But I'm not exactly constantly fiddling with my phone all the time anymore either. Basically I get a set-up that works for me, and I stick with it.
I've patiently been waiting to update to Lollipop. And today I did it. I did it by flashing the required factory images with fastboot.
AND IT WORKS. No problem. It boots. I go through the initial set-up. I can let it restore all my apps and passwords from the google servers, etc. So far so good.
My problem is that I cannot root. After I try, it bootloops (stuck at the Google splash, with my unlocked icon).
I tried to root before my first boot. I tried after the initial boot (before set-up and signing in). I tried rooting after setting it all up, and singing in, and letting google restore all of my apps. No matter which sequence I try, it will reboot a couple times at the first Google splash, and then fall back to Recovery.
(So, I'm on back on my rooted 4.4.4 nandroid, I think it's Mahdi Rom-- I forget)
Vital Stats:
Trying to install factory images of 5.0.1, all stock (system, boot (kernel), radio, bootloader)
Factory reset
(the above works fine)
TWRP 2.8.1.0
SuperSU-v2.40 (flashed via recovery)
Any ideas? Thanks for any help.
Click to expand...
Click to collapse
Try not doing that? When you go through the initial configuration, choose "Set up as a new device". Maybe the restore is somehow corrupting SuperSU?
BirchBarlow said:
Try not doing that? When you go through the initial configuration, choose "Set up as a new device". Maybe the restore is somehow corrupting SuperSU?
Click to expand...
Click to collapse
It happens even if I try to root before setting anything up at all.
albert_htc,
Are you saying: I should also flash the stock recovery first. Then boot for the first time. Then re-flash TWRP. Then flash SuperSU.
I never flashed the stock recovery. TWRP was on already on it.
Thanks guys. I'll give it another rip (doing stock recovery, then flashing back to TWRP) sometime soon.
iowabeakster said:
It happens even if I try to root before setting anything up at all.
albert_htc,
Are you saying: I should also flash the stock recovery first. Then boot for the first time. Then re-flash TWRP. Then flash SuperSU.
I never flashed the stock recovery. TWRP was on already on it.
Thanks guys. I'll give it another rip (doing stock recovery, then flashing back to TWRP) sometime soon.
Click to expand...
Click to collapse
Yes, flash the factory image using the batch file so every partition gets re-flashed. Now I'm thinking maybe your recovery is corrupt.
Run flash-all.bat and when your device reboots, go through all of the initial configuration and download all of the Gapps updates. Once that's all completed, go ahead and route using TWRP. If you find yourself still having the same problem, try live booting TWRP to flash SuperSU.
BirchBarlow said:
Yes, flash the factory image using the batch file so every partition gets re-flashed. Now I'm thinking maybe your recovery is corrupt.
Run flash-all.bat and when your device reboots, go through all of the initial configuration and download all of the Gapps updates. Once that's all completed, go ahead and route using TWRP. If you find yourself still having the same problem, try live booting TWRP to flash SuperSU.
Click to expand...
Click to collapse
I'm not going to flash over my user data, nandroids, app back-ups, etc. I'll stay with kit kat forever on my nexus 5 before I do that. Version numbers aren't that important. Hours wasted getting things set-up again are.
My recovery works fine. Both on kit kat and lollipop. My only problem is a boot loop when I flash SuperSU (via TWRP), on lollipop. I will try flashing stock recovery, though and then reflashing TWRP.
iowabeakster said:
I'm not going to flash over my user data, nandroids, app back-ups, etc. I'll stay with kit kat forever on my nexus 5 before I do that. Version numbers aren't that important. Hours wasted getting things set-up again are.
My recovery works fine. Both on kit kat and lollipop. My only problem is a boot loop when I flash SuperSU (via TWRP), on lollipop. I will try flashing stock recovery, though and then reflashing TWRP.
Click to expand...
Click to collapse
It's a tedious process, but it really isn't all that hard to back everything up to a computer, and you can do it easily with fastboot and a single command line.
Or what I'd recommend doing is just booting up, backing up all folders to a PC and then resetting and restoring later, backup apps with Titanium Backup (what I always do). A lot of us flashed factory images when Lollipop came out, so it isn't that bad once you start on the road.
Have you tried rooting from the bootloader via Chainfire's cf-auto root? I know I've read that sometimes rooting from recovery doesn't work properly, and that only certain zips will work. I've used the auto root each time (from stock fastboot flashing 5.0 & 5.0.1) with lollipop and it works fine. Link
Unzip and run batch file in bootloader. It will wipe everything if you haven't already unlocked bootloader (fastboot oem unlock). If you are already unlocked it won't wipe anything.
snappycg1996 said:
It's a tedious process, but it really isn't all that hard to back everything up to a computer, and you can do it easily with fastboot and a single command line.
Or what I'd recommend doing is just booting up, backing up all folders to a PC and then resetting and restoring later, backup apps with Titanium Backup (what I always do). A lot of us flashed factory images when Lollipop came out, so it isn't that bad once you start on the road.
Click to expand...
Click to collapse
I just backed the /sdcard, to my PC. I just re-ran titanium.
I can deal with "/sdcard issues" from updating to lollipop easy enough. That's a 30 second fix. I can deal with setting up my email accounts to my email client app. I can deal with launcher settings, and all the other apps, widgets, etc. Those are things that I can slowly get back to where I want. They aren't critical. But yeah, very tedious.
I think "starting over" may be much more tedious for me than most people though. I run ssh servers and clients on all PCs, servers, and phones (disabling passwords and using rsa encryption keys for security). It's very nice, once I get it all set up in that I can access everything (from anything) very easily. I do need root for that though also.
But if I can't just hit a "restore" to get it all my ssh addresses, keys, fingerprits, etc back to where it was and then I have to: reverify new fingerprints, generate new keys, re-enable passwords to transmit new keys for everything, then disable passwords (for all machines) ... well... I just get very very grumpy.
anactoraaron said:
Have you tried rooting from the bootloader via Chainfire's cf-auto root? I know I've read that sometimes rooting from recovery doesn't work properly, and that only certain zips will work. I've used the auto root each time (from stock fastboot flashing 5.0 & 5.0.1) with lollipop and it works fine. Link
Unzip and run batch file in bootloader. It will wipe everything if you haven't already unlocked bootloader (fastboot oem unlock). If you are already unlocked it won't wipe anything.
Click to expand...
Click to collapse
I'll check that out. Thanks.
Last night, I downloaded the 6.0 update, copied the .zip to external storage, rebooted to CWM, and flashed it (successfully), then flashed SuperSU over it, cleared dalvik, and rebooted.
Since then, I'm stuck with the Nvidia boot screen. I can use Power/Vol Up to get in to fastboot, but when I try to boot back into recovery, the screen goes black, but goes back to the Nvidia boot screen instead of booting to recovery, even after flashing a recovery image to it via fastboot.
I can probably fix this with enough time and tinkering, but I just came back from a two week from vacation at work and don't have the time to futz around with this. Posting here in case someone already has an idea on what the problem is/how to fix this.
Update: I was able to get back into recovery using TWRP referenced in http://forum.xda-developers.com/shield-tablet/general/unofficial-update-original-shield-t3281541. Direct link is https://www.androidfilehost.com/?fid=24345424848487676.
I'm thinking this is a kernel issue.
This was a kernel issue. Flashing a older OTA (http://ota.nvidia.com/ota/data/post...wf-full_ota-36442_589.1541.20150826095201.zip) and booting normally, then rebooting to bootloader and fastbooting the CWM image worked. I'm restoring from a backup I took before flashing the update last night, then flashing TWRP, backing up, and trying this all over again.
Thank you, I was having the same issue :good:
Have the exact same issue, except that now, for some reason, I can't even get the device to turn on!
Google Play Store Pixel, stock feb update (nof26v), unrooted, unlocked bootloader. There's a longer back story to this issue I've encountered, but to cut to the chase:
I can successfully flash TWRP 3.0.2 RC1 and 2.79 SR3. I can boot into system and enjoy benefits of root. However, I've noticed that whenever I try to reboot SYSTEM, it only boots into recovery. Even when I boot into bootloader and flash stock boot.img, it'll just reboot into stock recovery, but never into system. My way out of this quasi soft-brick state is to flash stock boot.img and sideload ota and I'm good to go with all my settings/data intact, I'll just be unrooted (as expected). I can verify it survives reboot in this state.
Has anyone else encountered this before? Is there something in the latest SU that won't let it reboot properly? Is there a way I can force it to reboot a certain slot to somehow avoid this issue?
The way Android handles memory now, I don't ever feel the need to reboot. But one of the things that's essential for me is to edit build.prop to enable wifi tether and miracast. Thing is, it requires a reboot for those changes to apply, but as soon as I reboot...
I've had this all working before on the dec update and SuperSU-v2.79-201612051815.zip but then something really strange happened (long backstory referenced above) and it required me to have to re-root, only now it won't survive reboot.
Any insight is greatly appreciated!
I have never encountered this issue as a result of flashing Super SU. I have come across this when I updated to the latest image by just flashing a few components.. IE: i didnt flash the whole factory image.
Flashing the latest factory image to both slots and starting over fixed the issue for me.
Flash the image (flash_all.bat) then fastboot boot twrp and switch slots, flash factory image again.
Just my two cents.
k.s.deviate said:
Flashing the latest factory image to both slots and starting over fixed the issue for me.
Flash the image (flash_all.bat) then fastboot boot twrp and switch slots, flash factory image again.
Just my two cents.
Click to expand...
Click to collapse
Thanks for your input! Should I remove -w while flashing, or when you said starting over do you mean full wipe?
Was hoping to avoid going that route... Is there any way to salvage without wipe?
Let me also share the strange event I encountered which led me to this point:
As stated, I had December update with stable 2.79 and TWRP 3.0.2. I skipped Jan update and was planning to do the same for the Feb update, but for whatever reason, I went to check updates (knowing full well it wouldn't take since I'm not on stock recovery). It gave me the standard "downloading, installing..Oops, there's a problem" prompt and I went on my merry way.
A week or so later, I decided to manually reboot and upon boot, I noticed it said "Android is starting/configuring" something along those lines. Then I tried double tap to lock (Nova gesture) and it says phone wasn't rooted. I check and sure enough, no SU icon. Checked Android version and now it says I'm on Feb update.
Attempt to install latest from chainfire on play store and no dice. Decide to flash it instead. Downloaded 2.79 SR3. Booted temporary TWRP and flashed the install and SU and then I found that phone won't boot to anything but recovery. Now anytime, I modify the boot image in any way, I'm bricked on subsequent reboots until I flash stock boot image and sideload OTA.
How do you think the Feb update installed when it shouldn't have? Did it install to one slot while my other slot was TWRP+root?
I would guess that it may have installed onto the inactive slot, but it doesn't sound like it should have if you had TWRP and Su installed. However we are all still learning new things about the pixel every day.
I would recommend clean flashing the factory image to both slots and starting over. Sounds like something became corrupt.
What version of ADB and Fastboot are you running? This reboot to bootloader happened to me when I unknowing using an older version.
Try wiping the device completely push your factory image via ADB and fastboot and installed of TWRP RC1 use alpha 2 never had a issue with alpha 2 after flashing TWRP boot into stock then go back into TWRP then flash SuperSU
jamespark said:
How do you think the Feb update installed when it shouldn't have?
Click to expand...
Click to collapse
People have reported automatic OTA updates on rooted Pixel phones. You can shut off automatic OTA updates by following the following link. People report still getting a notification for updates after the setting change, but updates no longer happen automatically. The site below also lists a way to entirely shut off OTA notifications, yet that change causes my phone to stay awake constantly and never go into deep sleep, so I only recommend the link. There's a thread or two about FlashFire, which I may eventually get around to trying.
https://www.androidexplained.com/pixel-disable-ota-updates/
Are you okay with losing data? I can post the links I used to download SuperSU and a little guide to flash to stock and reroot. Maybe you'll be able to figure what you're doing wrong or just doing what I do step by step might fix it.
mngdew said:
What version of ADB and Fastboot are you running? This reboot to bootloader happened to me when I unknowing using an older version.
Click to expand...
Click to collapse
Definitely using an older version of adb and fastboot. I'll update and retry with the latest, thanks for the suggestion!
alluringreality said:
People have reported automatic OTA updates on rooted Pixel phones. You can shut off automatic OTA updates by following the following link. People report still getting a notification for updates after the setting change, but updates no longer happen automatically. The site below also lists a way to entirely shut off OTA notifications, yet that change causes my phone to stay awake constantly and never go into deep sleep, so I only recommend the link. There's a thread or two about FlashFire, which I may eventually get around to trying.
https://www.androidexplained.com/pixel-disable-ota-updates/
Click to expand...
Click to collapse
Thanks for the heads up! I had this setting enabled and I have since disabled it.
I really appreciate the community and all your help!
SOLVED
I'm pleased to report that I now have root that survives reboot!
- From stock: flashed TWRP and SU. verified root, edited build.prop and reboot system..... boots into recovery (the usual problem)
- switched active slots and flashed SU, reboot
- SU icon in app drawer but when launched: "supersu binaries not installed"
- reboot into recovery and flashed su, reboot
- su is installed, but build.prop changes didn't stick. edited build.prop, reboot system
- boots into recovery.
- flashed su, did NOT reboot, backed out, switched slots, flash SU to the other slot, reboot
- huzzah!
is it verified that android will alternate active slots upon each subsequent reboot (i.e. A/B/A/B/...)?
it would seem I was making changes and rebooting to the other slot which was jacked up, so I had to finally apply the same changes to both slots and now everything is working!
I honestly don't know what I just did, and I guess sometimes it's better to be lucky than smart lol but, boy, this two-system partition is a piece of work...
Thanks again to everyone for all your help!!
Well, not fully bricked, but it's completely non-working just the same.
I've had the K1 for a few years now and have been fine with the standard, stock OTA updates. Recently though I've been seeing constant notifications that I'm short on ram and after uninstalling apps, deleting old files, it would work ok for a few days and then start complaining about low memory again. So I figured that something must be corrupt and now is a good a time as any to root and see about flashing a new rom.
I've owned many android devices over the years and have rooted and patched most of them. so I'm familiar with the tools.
This time however, I think I must have crossed something up somewhere.
What I did was this:
Grabbed the minimal ADB package and fastboot drivers.
Booted into the bootloader and ran the fastboot oem unlock. No problem.
From the nVidia site, I then grabbed and flashed the latest stock image and recovery, just to ensure I was on a clean slate. No problem.
Flashed the latest TWRP for the device. No problem.
Flashed SuperSU. No problem.
Booted into the stock system to make sure everything was still working and it was. But, this is the start of where I maybe hosed things up(?).
While running stock, I converted the SD card to internal memory, just so I wasn't having to mess with it later, not thinking that I'd have to do it again anyway after flashing a new rom.
Rebooted back to TWRP and proceeded to flash the new rom (AOSP Extended (AEX) 5.8).
I flashed it by way of the sideload method rather than from a zip file sitting on the SD card. This all seemed to work just fine.
Next I went ahead and flashed OpenGapps Mini. This resulted in an error 70 and after reading about it, it was a simple matter of going into the advanced settings in TWRP and extending the system partition. Did that and OpenGapps then flashed with no problem.
Finally I wrapped it up by flashing tegra124-tn8-p1761-1270-a04-e-battery.dtb and rebooted.
... Nothing. Now I know that when flashing a new rom, the first boot can take some time, but I let it sit for about 2 hours with no result. It didn't appear to be boot looping, but instead just stuck on the nVidia boot screen. Forced it to boot back to the bootloader and brought up TWRP. I obviously did something wrong, so I prepared to reflash the stock image.
Did the wipe, flashed the files and rebooted. Again, nothing.
This time however, not only can I not boot to the system, I now also can't get back into recovery.
No matter how many times I reboot, or attempt to reflash anything, it hangs on the boot screen when attempting to get back into recovery.
So I'm stuck. I've tried reflashing TWRP, stock recovery and stock system, with the SD card in and out, a number of times, all with no joy.
I can access the bootloader, so I can at least run fastboot commands, but that's all I can do. Without being in recovery, I can't access an ADB shell if I need to repair anything.
If you're still with me after this rambling mess, do I have any hope at all in recovering this thing?
Hi,
I think the problem is in the modified .dtb try flash the original file.
Or : https://forum.xda-developers.com/showpost.php?p=82359331&postcount=39
greetings
kozaqu said:
Hi,
I think the problem is in the modified .dtb try flash the original file.
Or : https://forum.xda-developers.com/showpost.php?p=82359331&postcount=39
greetings
Click to expand...
Click to collapse
That got me in the right direction and I can at least get back into recovery now. Thanks! :good:
Also in the same boat
mkhopper said:
Well, not fully bricked, but it's completely non-working just the same.
I've had the K1 for a few years now and have been fine with the standard, stock OTA updates. Recently though I've been seeing constant notifications that I'm short on ram and after uninstalling apps, deleting old files, it would work ok for a few days and then start complaining about low memory again. So I figured that something must be corrupt and now is a good a time as any to root and see about flashing a new rom.
I've owned many android devices over the years and have rooted and patched most of them. so I'm familiar with the tools.
This time however, I think I must have crossed something up somewhere.
What I did was this:
Grabbed the minimal ADB package and fastboot drivers.
Booted into the bootloader and ran the fastboot oem unlock. No problem.
From the nVidia site, I then grabbed and flashed the latest stock image and recovery, just to ensure I was on a clean slate. No problem.
Flashed the latest TWRP for the device. No problem.
Flashed SuperSU. No problem.
Booted into the stock system to make sure everything was still working and it was. But, this is the start of where I maybe hosed things up(?).
While running stock, I converted the SD card to internal memory, just so I wasn't having to mess with it later, not thinking that I'd have to do it again anyway after flashing a new rom.
Rebooted back to TWRP and proceeded to flash the new rom (AOSP Extended (AEX) 5.8).
I flashed it by way of the sideload method rather than from a zip file sitting on the SD card. This all seemed to work just fine.
Next I went ahead and flashed OpenGapps Mini. This resulted in an error 70 and after reading about it, it was a simple matter of going into the advanced settings in TWRP and extending the system partition. Did that and OpenGapps then flashed with no problem.
Finally I wrapped it up by flashing tegra124-tn8-p1761-1270-a04-e-battery.dtb and rebooted.
... Nothing. Now I know that when flashing a new rom, the first boot can take some time, but I let it sit for about 2 hours with no result. It didn't appear to be boot looping, but instead just stuck on the nVidia boot screen. Forced it to boot back to the bootloader and brought up TWRP. I obviously did something wrong, so I prepared to reflash the stock image.
Did the wipe, flashed the files and rebooted. Again, nothing.
This time however, not only can I not boot to the system, I now also can't get back into recovery.
No matter how many times I reboot, or attempt to reflash anything, it hangs on the boot screen when attempting to get back into recovery.
So I'm stuck. I've tried reflashing TWRP, stock recovery and stock system, with the SD card in and out, a number of times, all with no joy.
I can access the bootloader, so I can at least run fastboot commands, but that's all I can do. Without being in recovery, I can't access an ADB shell if I need to repair anything.
If you're still with me after this rambling mess, do I have any hope at all in recovering this thing?
Click to expand...
Click to collapse
I'm also sort of in the same boat i had a custom rom installed and decided to go back to stock os and now i'm stuck at either the Nvidia Logo or the Fastboot menu there's nothing else it let's me do i'd take any advice at this point. I can use Fastboot commands and I've tried Flashing Twrp.img and also flashing all the stock os which goes through with no problems i reboot the device and it's just stuck at the Nvidia logo
Ps: how did you manage to get back into recovery
Hello.
I think i had the same Problem.
I Flashed a Custom Rom, MiniGapps and the tegra...Battery file and since then i had boot loop an the NVidia Logo.
The Problem was: i flashed the tegra-Battery.ZIP file!!!
I noticed that i have to unzip it and flash teh tegra-..battery.DTP file.
since then it booted up again.
the OpenGappMini was buggy. it worked with the Nano!
Hope this helps for you as well!
OMG you guys. I did the exact same damn thing. Flashed the ZIP instead of the DTP file. 100 million thanks to you. I'm going to give it a shot now.
It worked! I wonder how many other folks didn't realize it wasn't a zip to flash to dtb and bricked their devices.