Related
Hi all,
I started out on TWRP version 2.7.1.0, and I wanted to flash the latest TWRP recovery (2.8.7.0), so I used the app that was linked by the TWRP site (TWRP Manager). So I tried to flash the latest update, and then a message pops up telling me to check if this was the right partition. I was careless and I didn't check it, and went ahead and installed it. It said it failed, but next thing I know, every time I tried to reboot(into the system/OS) I just boot right into TWRP (version 2.8.7.0). Then from TWRP (2.8.7.0) I tried to reboot into recovery, and it rebooted into TWRP, except that it was version 2.7.1.0, where I started.
So, when I hit boot into system, I got TWRP (2.8.7.0), and when I hit boot into recovery, I got TWRP 2.7.1.0. I was completely confused, so I wiped the OS, and then booted into fastboot to fastboot flash TWRP(2.8.7.0) in my recovery (It worked). Right now, I'm soft-bricked so I don't have an OS, but I have TWRP(2.8.7.0) as my recovery. Except now, I still get TWRP when I try to boot into system, and fastboot flashing, adb sideloading, and regular TWRP flashing is not working...
Any help is very appreciated, I need my phone to just be working!!! Except, if anyone can help me update it to 5.1 while they're at it, that would be awesome!
akn4497 said:
Hi all,
I started out on TWRP version 2.7.1.0, and I wanted to flash the latest TWRP recovery (2.8.7.0), so I used the app that was linked by the TWRP site (TWRP Manager). So I tried to flash the latest update, and then a message pops up telling me to check if this was the right partition. I was careless and I didn't check it, and went ahead and installed it. It said it failed, but next thing I know, every time I tried to reboot(into the system/OS) I just boot right into TWRP (version 2.8.7.0). Then from TWRP (2.8.7.0) I tried to reboot into recovery, and it rebooted into TWRP, except that it was version 2.7.1.0, where I started.
So, when I hit boot into system, I got TWRP (2.8.7.0), and when I hit boot into recovery, I got TWRP 2.7.1.0. I was completely confused, so I wiped the OS, and then booted into fastboot to fastboot flash TWRP(2.8.7.0) in my recovery (It worked). Right now, I'm soft-bricked so I don't have an OS, but I have TWRP(2.8.7.0) as my recovery. Except now, I still get TWRP when I try to boot into system, and fastboot flashing, adb sideloading, and regular TWRP flashing is not working...
Any help is very appreciated, I need my phone to just be working!!! Except, if anyone can help me update it to 5.1 while they're at it, that would be awesome!
Click to expand...
Click to collapse
I would flash the new RUU.
andybones said:
I would flash the new RUU.
Click to expand...
Click to collapse
Thanks for the reply!
I have already tried to flash the RUU for 4.4.4 but the recovery flash method gave me an error, and the fastboot flash method gave me
FAILED...(remote: not allowed)
I will try again in the morning and let you know how it goes, but I have a feeling it will end the same way.
akn4497 said:
Thanks for the reply!
I have already tried to flash the RUU for 4.4.4 but the recovery flash method gave me an error, and the fastboot flash method gave me
FAILED...(remote: not allowed)
I will try again in the morning and let you know how it goes, but I have a feeling it will end the same way.
Click to expand...
Click to collapse
Why not use the new 5.0.1 RUU?
andybones said:
I would flash the new RUU.
Click to expand...
Click to collapse
andybones said:
Why not use the new 5.0.1 RUU?
Click to expand...
Click to collapse
Yup that's what I meant I'll try 5.0.1 in the morning. Just wondering, will I need the firmware for it? Because I am coming from 4.4.4
akn4497 said:
Yup that's what I meant I'll try 5.0.1 in the morning. Just wondering, will I need the firmware for it? Because I am coming from 4.4.4
Click to expand...
Click to collapse
The firmware is apart of the RUU, did you use cmd
fastboot oem rebootRUU
Then flash RUU? Fastboot flash zip nameofRUU.zip
andybones said:
The firmware is apart of the RUU, did you use cmd
fastboot oem rebootRUU
Then flash RUU?
Click to expand...
Click to collapse
Oh shoot, I feel dumb. I'll let you know, thanks!
The RUU worked! I used the exe and I'm up and running. Thanks!!
akn4497 said:
The RUU worked! I used the exe and I'm up and running. Thanks!!
Click to expand...
Click to collapse
When you go to flash your custom recovery, use fastboot rather than twrp manager. If you MUST use such a shortcut, I might recommend flashify.
cntryby429 said:
When you go to flash your custom recovery, use fastboot rather than twrp manager. If you MUST use such a shortcut, I might recommend flashify.
Click to expand...
Click to collapse
Yeah I think I'll just stick with fastboot flashing recoveries from now on! Thanks
akn4497 said:
Yeah I think I'll just stick with fastboot flashing recoveries from now on! Thanks
Click to expand...
Click to collapse
Glad to hear you're up and running my friend.
Hi guys, i need help.
My tablet has only temporary recovery installed after flashing 3.1.1. I can boot to OS just fine, but there's no permanent recovery even the stock one. I can install twrp but only temporarily. everytime i reboot to recovery, it only shows a dead android with exclamation point above it.
I have to flash again every time i want to use recovery.
I came from stock rooted 1.2.1 image with twrp 2.8.7.1 without any problem.
I hope anyone is kind enough to point out where am i doing it wrong.
I just flashed 3.1.1 stock image using this thru fastboot:
fastboot flash recovery recovery.img
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash userdata userdata.img
fastboot flash staging blob
fastboot flash dtb tegra124-tn8-p1761-1270-a04-e-battery.dtb
and then twrp using:
fastboot flash twrp-2.8.7.1.img
Try copying SuperSU zip to your tablet. Then flash TWRP again, but do not reboot. Go immediately into recovery (which should be TWRP) and flash the zip, then reboot.
koop1955 said:
Try copying SuperSU zip to your tablet. Then flash TWRP again, but do not reboot. Go immediately into recovery (which should be TWRP) and flash the zip, then reboot.
Click to expand...
Click to collapse
Wow thanks a lot. That actually did the trick
bonkeng said:
Wow thanks a lot. That actually did the trick
Click to expand...
Click to collapse
I say this with a smile on my face, but why does everyone seem so surprised whenever I a right about something?
In the folder where I keep my ROM/OTA updates, I always have:
1) SuperSU.zip - to give me and maintain root. And also...
2) Nomoreota.zip (from here: http://forum.xda-developers.com/shield-tablet/general/kill-kill-switch-shield-tablet-xx-t3179489) which will eliminate the kill-switch file.
When I flash an update, I then flash the other two zips. Not necessary if you are flashing a ROM, of course, but important if you are flashing an OTA. It only adds seconds to the process and prevents a brick.
koop1955 said:
I say this with a smile on my face, but why does everyone seem so surprised whenever I a right about something?
In the folder where I keep my ROM/OTA updates, I always have:
1) SuperSU.zip - to give me and maintain root. And also...
2) Nomoreota.zip (from here: http://forum.xda-developers.com/shield-tablet/general/kill-kill-switch-shield-tablet-xx-t3179489) which will eliminate the kill-switch file.
When I flash an update, I then flash the other two zips. Not necessary if you are flashing a ROM, of course, but important if you are flashing an OTA. It only adds seconds to the process and prevents a brick.
Click to expand...
Click to collapse
I'm sorry if i may have offended you. This was my first time trying this method.
Thanks to you, now I know exactly what to do
bonkeng said:
I'm sorry if i may have offended you. This was my first time trying this method.
Thanks to you, now I know exactly what to do
Click to expand...
Click to collapse
No offense at all, I was saying that in jest. Really. (I have an odd sense of humor.)
Just to complete your understanding (and I am glad that I could help) installing SuperSu roots the tablet. Without root, it was not accepting the custom recovery.
hey guys! I've been lurking for a while now, but I think I may have broken something, but was wondering what to do now.
I unlocked the bootloader in fastboot, installed TWRP, factory reset, and then flashed cyanogenmod nightly via twrp.
.... and it just stayed on the NVidia logo for over an hour when I tried to boot.
so at this point I wanted to make sure I didn't break something, so I wiped every partition via twrp (except recovery) and then used fastboot to reinstall the stock image..... and nothing. I can't get the tablet to boot anything.
... what do I do next? I can reliably get into TWRP and fastboot.
Did you wipe system before flashing?
Natebluehooves said:
... what do I do next? I can reliably get into TWRP and fastboot.
Click to expand...
Click to collapse
If you still have twrp - you didn't flash stock.
Downloads and instructions:
https://developer.nvidia.com/shield-open-source
Download, unpack, install adb & drivers, copy imgs and blob to /program files/minmalAdb...
Open flash all.bat(as txt) and retype commands from keyboard.
"fastboot devices
fastboot flash recovery recovery.img"...etc.
dzidexx said:
If you still have twrp - you didn't flash stock.
Downloads and instructions:
https://developer.nvidia.com/shield-open-source
Download, unpack, install adb & drivers, copy imgs and blob to /program files/minmalAdb...
Open flash all.bat(as txt) and retype commands from keyboard.
"fastboot devices
fastboot flash recovery recovery.img"...etc.
Click to expand...
Click to collapse
I re flashed twrp after it failed to boot. think of it like a safety blanket. I did actually flash over recovery/system/staging/etc, but it wouldn't boot. it just sits there.
it's worth mentioning this is the k1 tablet. not sure what that changes.
With twrp you can restore only backup.
Stock - fastboot & pc.
dzidexx said:
With twrp you can restore only backup.
Stock - fastboot & pc.
Click to expand...
Click to collapse
okay perhaps I was not clear....
IN THIS ORDER:
I was on stock update 4.4 on the K1 shield tablet
I decided I wanted to run cyanogenmod, so I unlocked the bootloader (fastboot oem unlock), and then flashed CWM (fastboot flash recovery "insert file name for cwm here".img
I couldn't boot into recovery for some reason. it just hangs on the nvidia screen forever when I choose recovery from fastboot
I now install TWRP (fastboot flash recovery etc etc), this works, and I use twrp to install cyanogenmod. won't boot.
I try a few other roms like AICP, still won't boot. just gets stuck forever.
At this point, I figure i'm doing something wrong and i need my tablet to work for this coming week (i use it at work), so I "fastboot flash system/staging/recovery/etc" from the nvidia package. THIS DOES NOT WORK. AT THIS POINT I NO LONGER HAVE TWRP, AND CAN NOT BOOT.
I can install TWRP to get that functionality back, but at this point I can't get the tablet to boot into anything but bootloader or TWRP if i install it. anything else leaves me stuck on the nvidia logo forever.
this is a brand new nvidia tablet K1 as of about a week ago. no issues until i unlocked the bootloader.
Also, I really need to know, and nobody anywhere is answering this for some reason: are roms for the original shield compatible with the K1? As i understand it, the k1 is nearly identical in hardware (missing the stylus sensor, but not much else), but I seem to be the only person having these problems.
edisso10018 said:
Did you wipe system before flashing?
Click to expand...
Click to collapse
yes. am i not supposed to do this? is a dirty flash recommended for some reason?
Natebluehooves said:
yes. am i not supposed to do this? is a dirty flash recommended for some reason?
Click to expand...
Click to collapse
Nvidia shield k1 tablet had 1.4 & 1.5 updates(november).
You flashed wrong firmware.
You have to download and flash 1.4 firmware(recovery image) from:
https://developer.nvidia.com/gameworksdownload#?search=SHIELD%20Tablet%20K1&tx=$additional,shield
dzidexx said:
Nvidia shield k1 tablet had 1.4 & 1.5 updates(november).
You flashed wrong firmware.
You have to download and flash 1.4 firmware(recovery image) from:
https://developer.nvidia.com/gameworksdownload#?search=SHIELD%20Tablet%20K1&tx=$additional,shield
Click to expand...
Click to collapse
ok. grabbed it, flashed everything including recovery, aaand.... it's just frozen on the bootloader screen saying cold booting Linux. it's been here for a while. same issue as previously.
edit: looked at the old file I was flashing, it was 1.3.
my previous tablet I worked with was an original shield, so that's why I had the 4.4 update in my head.
I think that you flashed(yesterday) twrp with multiboot option.
Reflah it, uncheck multiboot and try "optimized stock".
dzidexx said:
I think that you flashed(yesterday) twrp with multiboot option.
Reflah it, uncheck multiboot and try "optimized stock".
Click to expand...
Click to collapse
I can't find any multi boot option in twrp...
I have the same problem with the cold booting linux, did you solved it?
Natebluehooves said:
I can't find any multi boot option in twrp...
Click to expand...
Click to collapse
I have this same issue lol can't boot into anything!
Any recommendations on removing TWRP and restoring stock recovery so I can move up to 7.1.1?
I don't have a backup of the old recovery.
Moogagot said:
Any recommendations on removing TWRP and restoring stock recovery so I can move up to 7.1.1?
I don't have a backup of the old recovery.
Click to expand...
Click to collapse
Flash the boot.img from the stock system image. This has been mentioned many times around this forum. Search is your friend.
cntryby429 said:
This has been mentioned many times around this forum. Search is your friend.
Click to expand...
Click to collapse
I've spent hours searching everything from "Stock Bootloader" to "Remove TWRP" with no luck. Any advice?
Moogagot said:
I've spent hours searching everything from "Stock Bootloader" to "Remove TWRP" with no luck. Any advice?
Click to expand...
Click to collapse
Well, it's actually everywhere. However, you have to discern what apply to you and what do not. That's the danger of a public forum such a this. Everyone has an opinion. Sometimes, an inaccurate answer is provided. Most other times, the incorrect question was originally posed.
In your case, you don't need to go back to the original stock image. Assuming your bootloader is still unlocked, just flash 7.1.1 and get on with your life. Download 7.1.1 stock image from the Google developers' web site. Extract it. Edit the flash-all.bat file to remove the -w switch if you don't want to lose userdata. Boot the phone into bootloader. Execute flash-all.bat. Then you have 7.1.1.
If you don't have a recovery backup, then you're taking a risk. I have not only a recovery backup, but more importantly, a complete set of Titanium backup on my laptop.
Moogagot said:
I've spent hours searching everything from "Stock Bootloader" to "Remove TWRP" with no luck. Any advice?
Click to expand...
Click to collapse
Download the factory image for the version of Android that you're currently running. Look inside the zip and you'll find another zipped file. Open that and you'll see a file in there that's named boot.img. Extract the boot.img file the same folder as your fastboot is in, open a command prompt in that folder flash it with fastboot.
fastboot flash boot_a boot.img
fastboot flash boot_b boot.img
That will get you back to the stock bootloader and stock recovery.
robocuff said:
Download the factory image for the version of Android that you're currently running. Look inside the zip and you'll find another zipped file. Open that and you'll see a file in there that's named boot.img. Extract the boot.img file the same folder as your fastboot is in, open a command prompt in that folder flash it with fastboot.
fastboot flash boot_a boot.img
fastboot flash boot_b boot.img
That will get you back to the stock bootloader and stock recovery.
Click to expand...
Click to collapse
I tried flashing some other stuff and it bricked Google is sending out a replacement.
Moogagot said:
I tried flashing some other stuff and it bricked Google is sending out a replacement.
Click to expand...
Click to collapse
Well, hope there's not a next time, but power + volume up should take you to the recovery menu. It's next to impossible to brick phones any more. Lord knows I try daily to see how I can brick my phones, just so I can assist others.
quangtran1 said:
Well, hope there's not a next time, but power + volume up should take you to the recovery menu. It's next to impossible to brick phones any more. Lord knows I try daily to see how I can brick my phones, just so I can assist others.
Click to expand...
Click to collapse
I broke recovery. I just says "No Command"
Moogagot said:
I broke recovery. I just says "No Command"
Click to expand...
Click to collapse
No you didn't, at that screen with "No Command":
Hold the Power button and press Volume Up once, and a menu will appear.
Moogagot said:
I broke recovery. I just says "No Command"
Click to expand...
Click to collapse
Come on man, you can do it next time. Please?
http://lmgtfy.com/?q=no+command+stock+recovery+pixel
krelvinaz said:
No you didn't, at that screen with "No Command":
Hold the Power button and press Volume Up once, and a menu will appear.
Click to expand...
Click to collapse
No menu appears. I just get a flash and back to no command.
I can get into the bootloader, but again, any option leads to the No Command screen.
Ok, from the bootloader I was able to manually flash a different image and things are looking a little better.
I now have the dancing dots and ADB see's a device attached. PROGRESS!
The devices throws errors on bootup, but it runs for now.
Please ignore. Posted to wrong thread. Sorry!
Here's the easiest way I've found to update. You'll need TWRP, so go ahead and download it - https://twrp.me/devices/googlepixel.html. Put the img file on your computer and the zip file on your phone. You'll boot into TWRP by using the "Fastboot boot" command. DO NOT "fastboot flash" it or you'll have to re-flash the boot image to get your phone out of a bootloop.
Now that you're in TWRP, you'll need the OTA file. I've only tested going up one increment so I suggest doing it that way. If you're brave, go ahead and download the latest OTA - https://developers.google.com/android/ota. Worst case TWRP won't flash it and you'll have to go back and do them incrementally.
Now that you're in TWRP and have the OTA and TWRP-RC1.zip on your phone, flash the update just like you would a rom. As soon as it successfully flashes (and before you reboot), flash the TWRP zip.
I did this incrementally from NMF260 > NMF26U > NMF26V without any issues. I believe it'll work as long as you're moving up an OTA just as the phone would have normally received them. Just remember to flash TWRP every time after you install the OTA as it gets overwritten with each OTA.
Sent from my Pixel using Tapatalk
Google needs to start voiding warranty for people who want to unlock bootloader
Moogagot said:
I broke recovery. I just says "No Command"
Click to expand...
Click to collapse
I Know this post is old, I am just researching but, sounds to me like you really need to search, read, and actually learn before you attempt anything on your phone. I am not being hateful or rude, just pointing out the obvious....
I was following the directions here on how to unlock and root my new pixel, and after the fastboot boot-to-image step, it restarted a few times (as it was supposed to) and then it got stuck on the bouncing dots stage. When I attempted to restart into recovery, I instead got a "[Ramdump] writing to EXT4 file" message, and I was not able to get into recovery after several attempts. Are there any options for recovering this or did I manage to brick it beyond repair?
Thanks
Are you able to flash the factory image?
roirraW "edor" ehT said:
Are you able to flash the factory image?
Click to expand...
Click to collapse
or flash the recovery TWRP
roirraW "edor" ehT said:
Are you able to flash the factory image?
Click to expand...
Click to collapse
After the battery drained overnight, I manged to boot into recovery. Is it worth it to try and see if it starts normally or should I leave it in recovery and try the factory reflash? If the reflash, should I pick the most recent image, or do I need to pick the correct one that it came with?
henk-jan said:
or flash the recovery TWRP
Click to expand...
Click to collapse
Even though ADB recognizes my device now (I was able to boot into recovery after the battery drained overnight), I can't see it on my computer to manually transfer files, can I push the TWRP .zip file onto the device using ADB, and does it matter where on the device it gets put (the instructions just say to copy it to the device)?
cdenney said:
After the battery drained overnight, I manged to boot into recovery. Is it worth it to try and see if it starts normally or should I leave it in recovery and try the factory reflash? If the reflash, should I pick the most recent image, or do I need to pick the correct one that it came with?
Click to expand...
Click to collapse
It won't hurt anything to see if it'll boot. Most recent image.
roirraW "edor" ehT said:
It won't hurt anything to see if it'll boot. Most recent image.
Click to expand...
Click to collapse
Flashing the factory image worked. Now I just have to decide if I try it again or just relock the bootloader and leave well enough alone. Thanks!
cdenney said:
Flashing the factory image worked. Now I just have to decide if I try it again or just relock the bootloader and leave well enough alone. Thanks!
Click to expand...
Click to collapse
If you're in any way hesitant, don't touch it. I wouldn't relock the bootloader personally.
cdenney said:
Flashing the factory image worked. Now I just have to decide if I try it again or just relock the bootloader and leave well enough alone. Thanks!
Click to expand...
Click to collapse
You don't need anything but SuperSU zip to root. Enable developers option in settings, enable usb debugging, in fastboot mode fastboot boot TWRP IMG, if you want custom recovery, flash pixel TWRP zip, reboot recovery, flash SuperSU, reboot, otherwise skip TWRP zip and reboot recovery part. No boot to root is necessary. Just flash SuperSU. Simple.
Here is link to TWRP IMG to boot into
https://dl.twrp.me/sailfish/twrp-3.0.2-0-RC1-fastboot-sailfish.img.html
...
cdenney said:
Flashing the factory image worked. Now I just have to decide if I try it again or just relock the bootloader and leave well enough alone. Thanks!
Click to expand...
Click to collapse
I will say, I had this exact issue before. The issue was that I had inadvertently used an older version of fastboot. Worth double checking.
Tulsadiver said:
You don't need anything but SuperSU zip to root. Enable developers option in settings, enable usb debugging, in fastboot mode fastboot boot TWRP IMG, if you want custom recovery, flash pixel TWRP zip, reboot recovery, flash SuperSU, reboot, otherwise skip TWRP zip and reboot recovery part. No boot to root is necessary. Just flash SuperSU. Simple.
Here is link to TWRP IMG to boot into
https://dl.twrp.me/sailfish/twrp-3.0.2-0-RC1-fastboot-sailfish.img.html
Click to expand...
Click to collapse
Hey you mind giving me guild on how it is done, i am lost here. I read number of them but do not wish to brick my phone.
Thank you