Related
Unlocked and rooted ATT HTC One X and flashed pa_evita-2.54-09NOV2012-210217 ROM.
Boot up as far as an Android character with the lettering Paranoid Android 2.+ and then freezes there.
Any suggestions?? If nothing else, how do I get back to stock ROM?
Noob rldieb
rldieb said:
Unlocked and rooted ATT HTC One X and flashed pa_evita-2.54-09NOV2012-210217 ROM.
Boot up as far as an Android character with the lettering Paranoid Android 2.+ and then freezes there.
Any suggestions?? If nothing else, how do I get back to stock ROM?
Noob rldieb
Click to expand...
Click to collapse
1. What recovery are you using?
2. Did you wipe cache/dalvik-cache, factory reset?
In order to get back to a stock ROM, you will need to boot into recovery, then mount your usb storage. Put the rom on your sd card and then unmount. To be safe, wipe the cache and dalvic cache, then flash the stock rom.
What hboot are you on?
You may have flash boot.img first if you are on hboot 1.14
I think he just didn't full wipe
That's just wrong!
Sent from my Nexus 7 using Tapatalk 2
I'm having the same issue. I'm trying to flash this same rom on a device rooted on 2.20. I think my issue has something to do with flashing the boot.img. I have tried to flash using hasoon's toolkit, which doesnt seem to work, i have extracted the zip and placed the boot.img in the kernel folder, and when the command prompt tries to flash it, it says error. I have also tried flashing the kernel from the phone directly using the flash flash image gui app, and it says flash is successful, but when it prompts to boot into recovery, the command doesnt work from my phone so i have to boot into recovery manually.
can anyone give a solid link or tutorial on how to successfully flash the boot img onto my device, every link I have read uses windows cmd prompt, which when i try to replicate, it never works.. So, for now I flashed back to viper rom, since it has its own installer. It would be so nice if all these other roms were able to install like that.
thanks in advance for the help
threetwentyfizzle said:
I'm having the same issue. I'm trying to flash this same rom on a device rooted on 2.20. I think my issue has something to do with flashing the boot.img. I have tried to flash using hasoon's toolkit, which doesnt seem to work, i have extracted the zip and placed the boot.img in the kernel folder, and when the command prompt tries to flash it, it says error. I have also tried flashing the kernel from the phone directly using the flash flash image gui app, and it says flash is successful, but when it prompts to boot into recovery, the command doesnt work from my phone so i have to boot into recovery manually.
can anyone give a solid link or tutorial on how to successfully flash the boot img onto my device, every link I have read uses windows cmd prompt, which when i try to replicate, it never works.. So, for now I flashed back to viper rom, since it has its own installer. It would be so nice if all these other roms were able to install like that.
thanks in advance for the help
Click to expand...
Click to collapse
I do have a solution! Download Flash Image GUI from the market (it's $1.99) and it will do the process for you, no commands needed! The app is also available via XDA for free, do a search and download it.
After months of flashing everything in sight on my NS4g, the device appears to have rolled over and died! It started a few days ago, when it rebooted and asked me for a password to decrypt from storage (no password has ever been set). I couldn't get past that screen, so I decided to boot into recovery (TWRP), reinstall ROM (CM10) and gapps and restore data from backup.
No go. It just kept rebooting into recovery. But I was able to connect the phone to the PC and copy files from the phone but could not copy or delete files on the phone from the PC.
I used fastboot, Odin, and one-click-stock to wipe the device and install factory images, but the phone would boot no further than the red triangle-dead android.
Is my phone dead? I searched the forums and couldn't find any solutions other than to do what I have already done.
ttakacs said:
After months of flashing everything in sight on my NS4g, the device appears to have rolled over and died! It started a few days ago, when it rebooted and asked me for a password to decrypt from storage (no password has ever been set). I couldn't get past that screen, so I decided to boot into recovery (TWRP), reinstall ROM (CM10) and gapps and restore data from backup.
No go. It just kept rebooting into recovery. But I was able to connect the phone to the PC and copy files from the phone but could not copy or delete files on the phone from the PC.
I used fastboot, Odin, and one-click-stock to wipe the device and install factory images, but the phone would boot no further than the red triangle-dead android.
Is my phone dead? I searched the forums and couldn't find any solutions other than to do what I have already done.
Click to expand...
Click to collapse
When you flashed to stock you erased your recovery.. Reconnect to your computer and push a recovery onto your phone and you're good to go..
Unfortunately, when I flashed TWRP and boot.img to the phone using fastboot and attempted to boot into recovery, bootloader reports "No Boot or Recovery Img."
ttakacs said:
Unfortunately, when I flashed TWRP and boot.img to the phone using fastboot and attempted to boot into recovery, bootloader reports "No Boot or Recovery Img."
Click to expand...
Click to collapse
Try the Nexus tool kit and from the bootloader (power and vol. up) select flash to stock (bricked) then in advanced boot temporary recovery to flash the recovery of your choice.. or push a boot image.
Setting.Out said:
Try the Nexus tool kit and from the bootloader (power and vol. up) select flash to stock (bricked) then in advanced boot temporary recovery to flash the recovery of your choice.. or push a boot image.
Click to expand...
Click to collapse
Wish I had better news but ... using the Nexus tool kit I was able to boot into TWRP but when trying to flash CM10 and gapps for this phone the flash failed; likewise, I could not flash CM10 and gapps by pushing the files from the PC to the phone. I first did flash to stock (bricked) but that brought me back to the red triangle, dead android.
I am beginning to suspect that the phone internal sdcard is corrupted ... is there a way to test for that?
ttakacs said:
Wish I had better news but ... using the Nexus tool kit I was able to boot into TWRP but when trying to flash CM10 and gapps for this phone the flash failed; likewise, I could not flash CM10 and gapps by pushing the files from the PC to the phone. I first did flash to stock (bricked) but that brought me back to the red triangle, dead android.
I am beginning to suspect that the phone internal sdcard is corrupted ... is there a way to test for that?
Click to expand...
Click to collapse
When you got it to flash to stock did it boot up fully?
Remember that flashing to stock removes custom recoveries and you will need to flash one
Sent from my Nexus S using xda premium
Setting.Out said:
When you got it to flash to stock did it boot up fully?
Remember that flashing to stock removes custom recoveries and you will need to flash one
Sent from my Nexus S using xda premium
Click to expand...
Click to collapse
No, the phone never did boot up fully. It got to the Google screen with the unlock icon and then to the red triangle, dead Android.
ttakacs said:
No, the phone never did boot up fully. It got to the Google screen with the unlock icon and then to the red triangle, dead Android.
Click to expand...
Click to collapse
This happened when you tried stock or custom?..
Did it fully boot on stock image?..
The dead android usually shows up when you attempt to boot into recovery and you don't have one... If you try to boot and you loop back to the dead android it usually means you don't have a rom...
Try again to flash to stock, use the toolkit to boot a temporary recovery and flash a custom recovery.. Then make sure you are flashing the correct rom and correct gapps for that rom and for your phone.
Setting.Out said:
This happened when you tried stock or custom?..
Did it fully boot on stock image?..
The dead android usually shows up when you attempt to boot into recovery and you don't have one... If you try to boot and you loop back to the dead android it usually means you don't have a rom...
Try again to flash to stock, use the toolkit to boot a temporary recovery and flash a custom recovery.. Then make sure you are flashing the correct rom and correct gapps for that rom and for your phone.
Click to expand...
Click to collapse
I know have a recovery because the tool kit booted into TWRP; furthermore, the tool kit installed a TWRP 2.3 image (prior to installing the tool kit I was on 2.5 so the tool kit did something). From there, I tried to flash CM10 and gapps in the sdcard/download folder, but that failed, with TWRP returning message similar to "error opening ZIP".
I have used Odin to flash the stock image and it did not fully boot, ending at the dead android. Same results for flashing the stock image using fastboot with the phone connected to the PC. Same results with using the Nexus tool kit to flash a stock image (first JB and then, when that didn't boot, ICS). And, after the toolkit booted into temporary recovery (TWRP), I tried to flash (in this order) CM10 plus gapps, JB stock, and ICS, each time with the same results (no full boot, dead android).
I am with you when you say that the dead android means there is no rom, because my efforts to flash any rom, whether stock or custom, don't do anything. To all appearance, the phone contains a bootloader and a recovery and nothing else.
Thanks for your persistence ... any ideas for something else to try?
ttakacs said:
I know have a recovery because the tool kit booted into TWRP; furthermore, the tool kit installed a TWRP 2.3 image (prior to installing the tool kit I was on 2.5 so the tool kit did something). From there, I tried to flash CM10 and gapps in the sdcard/download folder, but that failed, with TWRP returning message similar to "error opening ZIP".
I have used Odin to flash the stock image and it did not fully boot, ending at the dead android. Same results for flashing the stock image using fastboot with the phone connected to the PC. Same results with using the Nexus tool kit to flash a stock image (first JB and then, when that didn't boot, ICS). And, after the toolkit booted into temporary recovery (TWRP), I tried to flash (in this order) CM10 plus gapps, JB stock, and ICS, each time with the same results (no full boot, dead android).
I am with you when you say that the dead android means there is no rom, because my efforts to flash any rom, whether stock or custom, don't do anything. To all appearance, the phone contains a bootloader and a recovery and nothing else.
Thanks for your persistence ... any ideas for something else to try?
Click to expand...
Click to collapse
I'm at a loss.. Try again, maybe there's something missing.. And flash only one at a time and see if it worked (just ROM then reboot) then wipe d+c and flash gapps reboot then wipe flash... Ect... Ect...
Sent from my Nexus S using xda premium
Setting.Out said:
I'm at a loss.. Try again, maybe there's something missing.. And flash only one at a time and see if it worked (just ROM then reboot) then wipe d+c and flash gapps reboot then wipe flash... Ect... Ect...
Click to expand...
Click to collapse
I am too. Every method known to me (Odin, fastboot, adb) to flash a ROM, whether custom or stock, has failed to boot. Thanks for hanging with me on this; if you can think of solution I'll be glad to have it. Or if I solve it, I'll post here.
Hello, my tablet seems to be stuck in a boot loop and i've tried flashing the recovery and supersu again to no avail. I've also tried that exitrecovery zip floating around. I think I might have flashed a kernel by accident want trying to root.
Background
Tried using WinDroid Universal Android ToolKit. <- was successful in unlocking bootloader only. tried various times to install twrp but nothing would happen. The "recovery mode" in BL would just show android with caution triangle. I then used WinDroid's "commands" section to try and flash recovery. I may have flashed kernel instead? I have CWM 6.0.5.0. Help would be appreciated. This is what i get for trying to take the easy way out -_-.
Update: I tried "SHIELD TABLET RECOVERY IMAGE FLASHING INSTRUCTIONS" from nvidia itself and now it just hangs in the nvidia logo screen forever. I tried both the "flash-all.bat" and the manual line by line one. any clues?
If someone could tell me how to just make the wipe the whole thing i wouldn't mind restarting to root properly.
Any one got any info? =D
Cveezy said:
Any one got any info? =D
Click to expand...
Click to collapse
Its not hard, just restore it back to factory, a couple of quick google searches:
https://developer.nvidia.com/sites/...s/HowTo-Flash-SHIELDTablet-Recovery-Image.txt
http://forum.xda-developers.com/shi...k-recovery-images-ota-library-guides-t2988881
When you download the images make sure you do a MD5 on them.
The good news its very hard to kill this tablet, and very easy to unlock/flash/root.
jpierson said:
Its not hard, just restore it back to factory, a couple of quick google searches:
https://developer.nvidia.com/sites/...s/HowTo-Flash-SHIELDTablet-Recovery-Image.txt
http://forum.xda-developers.com/shi...k-recovery-images-ota-library-guides-t2988881
When you download the images make sure you do a MD5 on them.
The good news its very hard to kill this tablet, and very easy to unlock/flash/root.
Click to expand...
Click to collapse
I tried flashing and doing a full OTA rom install to no avail. I however unsure what MD5 is and would that have a effect on my outcome.
Cveezy said:
I tried flashing and doing a full OTA rom install to no avail. I however unsure what MD5 is and would that have a effect on my outcome.
Click to expand...
Click to collapse
You restored the recovery, boot, system, and userdata per the instructions and it still boot loops?
Check out this post:
http://forum.xda-developers.com/shield-tablet/help/help-stuck-nvidia-boot-screen-t3076462
jpierson said:
You restored the recovery, boot, system, and userdata per the instructions and it still boot loops?
Check out this post:
http://forum.xda-developers.com/shield-tablet/help/help-stuck-nvidia-boot-screen-t3076462
Click to expand...
Click to collapse
Yeah, its werid that its still stuck. I have tried doing it both way manual tell adb each file to flash and through the flash-all.bat way as well. Im going to try the link you sent in a bit.
How long did you let it sit at the boot logo? If you are booting on a clean install it may take a bit longer.
Just download and use fastboot (fastboot flash recovery image.img) to flash twrp. I'd suggest using adb/fastboot anyway since it's simple enough and a good thing to learn if you plan on doing this sort of thing. After that you can just flash from there. The ota zips, super su, etc. and wipe.
So I got a oneplus 6 bootloader unlocked, rooted, with twrp 3.2.3
Yesterday I accidently upgraded phone to android p (official update). And I was like no I want to go back to my previous android (official oxygen) so I tried to flash my old back up with twrp, but it was gone. So I tried to flash again twrp. again with the command flashboot boot twrp.img, but it didn’t work. My phone goes straight into QUALCOMM Crash Dump. when i only try to flash the twrp image. I googled for a few hours, tried an other image named boot_op6_ob3_twrp.img but also didn’t work. Can someone give me some tips to get twrp back again so I can flash my back up >.<! sorry for my bad English and thank you in advance!
justsaying said:
So I got a oneplus 6 bootloader unlocked, rooted, with twrp 3.2.3
Yesterday I accidently upgraded phone to android p (official update). And I was like no I want to go back to my previous android (official oxygen) so I tried to flash my old back up with twrp, but it was gone. So I tried to flash again twrp. again with the command flashboot boot twrp.img, but it didn’t work. My phone goes straight into QUALCOMM Crash Dump. when i only try to flash the twrp image. I googled for a few hours, tried an other image named boot_op6_ob3_twrp.img but also didn’t work. Can someone give me some tips to get twrp back again so I can flash my back up >.<! sorry for my bad English and thank you in advance!
Click to expand...
Click to collapse
To go back you will have to format. Search this part of the forum for Qualcomm crash dump and would will find a few threads with instructions,that is how a forum works. Imjustsaying
P.s also by reading slot you will also find out that restoring backups really doesn't work that great for this device yet....
https://forum.xda-developers.com/oneplus-6/how-to/tool-msmdownloadtool-v4-0-international-t3798892 you can make the phone work again with this tool. It will reset EVERYTHING, even lock your bootloader, just in case something else got bad I would use it .
justsaying said:
So I got a oneplus 6 bootloader unlocked, rooted, with twrp 3.2.3
Yesterday I accidently upgraded phone to android p (official update). And I was like no I want to go back to my previous android (official oxygen) so I tried to flash my old back up with twrp, but it was gone. So I tried to flash again twrp. again with the command flashboot boot twrp.img, but it didn’t work. My phone goes straight into QUALCOMM Crash Dump. when i only try to flash the twrp image. I googled for a few hours, tried an other image named boot_op6_ob3_twrp.img but also didn’t work. Can someone give me some tips to get twrp back again so I can flash my back up >.<! sorry for my bad English and thank you in advance!
Click to expand...
Click to collapse
wrong twrp img used. https://forum.xda-developers.com/devdb/project/?id=27466#downloads blue spark is your friend.
Hi.
So this was pretty stupid of me. I was trying to flash LiquidRemix onto my OP6, but I forgot to wipe the system partition. Flashed the rom, then blu_spark twrp, and rebooted into recovery to flash gapps and all. Got a black screen with a static LED. Didn't think that was a big issue cause this has happened before with normal TWRP on OB6 or OB7. Tried hard resetting to see if I could get into system, same result. Tried fastboot flashing 9.0.2, no help. And finally tried flashing OB9 via fastboot, and also no help.
I've reverted back to my tiny S6 and have sent repair request to OP. I haven't gotten anything back yet, so I thought in the mean time, I'd look for help on XDA and try to fix it before having the chance to send it in.
Any help/advice would be greatly appreciated.
Cheers
// EDIT
Figured out how to fix it. Used the MSMDownloadTool to unbrick my device. Worked wonders. Thanks to r/oneplus Discord
I did something like that I had to format data after I flashed the stock rom
mightyblazer said:
I did something like that I had to format data after I flashed the stock rom
Click to expand...
Click to collapse
How did you get to format? I really can't get into the OS or recovery at all
I was actually able to boot into TWRP maybe you can get into fastboot? And try flashing TWRP again
mightyblazer said:
I was actually able to boot into TWRP maybe you can get into fastboot? And try flashing TWRP again
Click to expand...
Click to collapse
I'm able to get into fastboot, but even if I fastboot boot [insert twrp file name here], it'd still result in the blank screen and static LED
Hmm I don't know then sorry
Try
fastboot flash boot twrp.zip
Then
fastboot reboot
You will need to use full stock rom first before doing anything else though.
I was in the same boat as you the other day. I flashed different versions of twrp until i managed to boot one because some twrp isn't compatible with pie.
Lol I never wipe system...
Might sound like a "hard-bricking" issue since you cant boot into the OS nor recovery. There 's a hard brick recovery guide, but it'll put you down to oreo OOS: https://forum.xda-developers.com/oneplus-6/how-to/tool-msmdownloadtool-v4-0-international-t3798892
As long as you can boot into fastboot, you can follow the guide's process with no problem.