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
I'm not sure if i bricked my tablet or not...i've spent the last 4hrs googling and surfing looking for answers but i can't seem to find anything definitive. Here's what i did
1) Was on CM10.1 nightlies and wanted to update to the newest ones on the JB Bootloader
2) downloaded all the necessary files (stock Asus, twrp2.5-42 and newest CM nightly)
3) went to go into recovery but accidentally hit Wipe Data (no idea how i managed that one)
4) tablet was wiped and rebooted into a fresh from the box Android install
5) went back into recovery and wiped data/cache and flashed stock Asus
6) rebooted and it hung at the Asus "loading screen"
I still have fastboot and recovery access...i fastbooted twrp 2.5-42 recovery on to the device and can flash roms they just don't boot
Is there a fix for the this or am i screwed...i should also point out when i go into the bootloader menu at the top it says "key driver not found.. Booting OS" before it tells me the bootloader and starting fastboot
Any help is appreciated
moosehead11 said:
Hello
I'm not sure if i bricked my tablet or not...i've spent the last 4hrs googling and surfing looking for answers but i can't seem to find anything definitive. Here's what i did
1) Was on CM10.1 nightlies and wanted to update to the newest ones on the JB Bootloader
2) downloaded all the necessary files (stock Asus, twrp2.5-42 and newest CM nightly)
3) went to go into recovery but accidentally hit Wipe Data (no idea how i managed that one)
4) tablet was wiped and rebooted into a fresh from the box Android install
5) went back into recovery and wiped data/cache and flashed stock Asus
6) rebooted and it hung at the Asus "loading screen"
I still have fastboot and recovery access...i fastbooted twrp 2.5-42 recovery on to the device and can flash roms they just don't boot
Is there a fix for the this or am i screwed...i should also point out when i go into the bootloader menu at the top it says "key driver not found.. Booting OS" before it tells me the bootloader and starting fastboot
Any help is appreciated
Click to expand...
Click to collapse
This is a link if you want more explenation! : http://forum.xda-developers.com/showthread.php?p=39272826
go to the stock asus site and download firmware for your sku
extract the zip in the zip flash the "blob" file to your tablet
reboot your bootloader
flash twrp 2.5.0.0 -4.2
that zip you extracted from that download? put it on your device and flash it
this should work!
about the "key driver not found.. Booting OS" it's normal everyone has it!
Sent from my Transformer Pad TF300T using xda app-developers app
noahvt said:
This is a link if you want more explenation! : http://forum.xda-developers.com/showthread.php?p=39272826
go to the stock asus site and download firmware for your sku
extract the zip in the zip flash the "blob" file to your tablet
reboot your bootloader
flash twrp 2.5.0.0 -4.2
that zip you extracted from that download? put it on your device and flash it
this should work!
about the "key driver not found.. Booting OS" it's normal everyone has it!
Sent from my Transformer Pad TF300T using xda app-developers app
Click to expand...
Click to collapse
I've tried flashing stock Asus a few different times either form fastboot, twrp or sideload none seem to work...given i can't boot should i be worried if i decided to wipe data, format system or just doing a factory reset before trying again
What error does it give when you try to flash?
Sent from my sensational HTC Desire C
noahvt said:
What error does it give when you try to flash?
Sent from my sensational HTC Desire C
Click to expand...
Click to collapse
no errors...i flash the ROM (in either TWRP or fastboot) and reboot...after the reboot i get to the ASUS "boot screen" (the one with the spinning circle under the Asus Logo) and it hangs there...have left it there "loading" for 30 minutes and nothing
scared of bootloader/fasboot access...can i wipe data/cache, format system and try again...would factory resetting in TWRP help maybe?
moosehead11 said:
no errors...i flash the ROM (in either TWRP or fastboot) and reboot...after the reboot i get to the ASUS "boot screen" (the one with the spinning circle under the Asus Logo) and it hangs there...have left it there "loading" for 30 minutes and nothing
scared of bootloader/fasboot access...can i wipe data/cache, format system and try again...would factory resetting in TWRP help maybe?
Click to expand...
Click to collapse
you forgot somethink (i think) after you have flashed it via fastboot you have to flash twrp 2.5.0.0 -4.2 then reboot bootloader then go to twrp and wipe everything! then flash via twrp!
Sent from my Transformer Pad TF300T using xda app-developers app
noahvt said:
you forgot somethink (i think) after you have flashed it via fastboot you have to flash twrp 2.5.0.0 -4.2 then reboot bootloader then go to twrp and wipe everything! then flash via twrp!
Sent from my Transformer Pad TF300T using xda app-developers app
Click to expand...
Click to collapse
So flash the rom and twrp via fastboot and then reboot bootloader...then in twrp install cm?
I thought you needed to let the rom fully boot before adding the recovery so the new bootloader gets installed properly
Sent from my GT-I9000 using xda app-developers app
moosehead11 said:
So flash the rom and twrp via fastboot and then reboot bootloader...then in twrp install cm?
I thought you needed to let the rom fully boot before adding the recovery so the new bootloader gets installed properly
Sent from my GT-I9000 using xda app-developers app
Click to expand...
Click to collapse
Flash blob file from fastboot
Type fastboot reboot bootloader
Flash twrp
Type fastboot reboot bootloader again
Launch twrp and wipe /system /data etc
In twrp flash the zip where the blob was in
Reboot
That's how I did it! I downgraded and upgraded
Sent from my sensational HTC Desire C
noahvt said:
Flash blob file from fastboot
Type fastboot reboot bootloader
Flash twrp
Type fastboot reboot bootloader again
Launch twrp and wipe /system /data etc
In twrp flash the zip where the blob was in
Reboot
That's how I did it! I downgraded and upgraded
Sent from my sensational HTC Desire C
Click to expand...
Click to collapse
So you are flashing the stock asus rom twice?
Sent from my GT-I9000 using xda app-developers app
Let's just get the Asus stock ROM on there first. Do you get the blue bar after flashing it from twrp (make sure you flash the zip inside the Asus zip)?
sbdags said:
Let's just get the Asus stock ROM on there first. Do you get the blue bar after flashing it from twrp (make sure you flash the zip inside the Asus zip)?
Click to expand...
Click to collapse
Yes...after flashing the ROM in twrp and rebooting i get the blue bar
moosehead11 said:
Yes...after flashing the ROM in twrp and rebooting i get the blue bar
Click to expand...
Click to collapse
And what happens if you leave it for 20 mins to boot?
sbdags said:
And what happens if you leave it for 20 mins to boot?
Click to expand...
Click to collapse
reflashing as we speak...i've left it going for about 30min on one attempt and it just kept "loading"
i did notice that if i check the file verification before flashing it fails to verify the zip...is that normal?
UPDATE: Left it for 2hrs while i sent out to do something when i got back still "loading"
Try my method! First flash blob via fastboot then wait till blue bar is full then flash twrp then open twrp wipe /system /data /cache then install that zip in twrp
Sent from my sensational HTC Desire C
noahvt said:
Try my method! First flash blob via fastboot then wait till blue bar is full then flash twrp then open twrp wipe /system /data /cache then install that zip in twrp
Sent from my sensational HTC Desire C
Click to expand...
Click to collapse
is it normal for the zip to fail verification in twrp?
Yes it's normal disable that verification!
Sent from my sensational HTC Desire C
noahvt said:
Yes it's normal disable that verification!
Sent from my sensational HTC Desire C
Click to expand...
Click to collapse
Well i tried your method and still no go
What would happen if i tried an older Asus rom from the 4.1 bootloader...would that maybe fix things
Sent from my GT-I9000 using xda app-developers app
you could try BUT REMEMBER AFTER FLASHING IN FASTBOOT: FLASH THE 4.1 TWRP!!!!!!
Sent from my Transformer Pad TF300T using xda app-developers app
hi, ive just flashed TWRP onto my lollipop. seemed to be succesful, however when i boot into recovery all i get is the wee android dude lying on his back looking a bit dead! any ideas how to get this working. i just installed lollipop today
If you did 'fastboot flash recovery twrp.img' and not 'fastboot boot twrp.img':
Browse around, I'm pretty sure this has been answered before.
Search topics: install-recovery.sh, recovery-from-boot.p
Boot to Android, then flash again.
Aerowinder said:
Boot to Android, then flash again.
Click to expand...
Click to collapse
Ugh... What are you talking about?
What's happening is that every boot, his install is checking for stock recovery, and every time it doesn't find it, it will reflash it.
well I was using the flash method and it didnt work so i tried yor boot method and i could see teh twrp logo for about 5 seconds then the rebooted. i still get the android dude on his back with red triangle
5.0 will check recovery and overwrite twrp if your not rooted. Download latest SuperSU and place on sd. Boot to boot loader/fastboot. Fastboot flash recovery recovery.IMG. then fastboot boot recovery.IMG. then when twrp boots, flash SuperSU. Reboot
Sent from my Nexus 5 using Tapatalk
MG386 said:
5.0 will check recovery and overwrite twrp if your not rooted. Download latest SuperSU and place on sd. Boot to boot loader/fastboot. Fastboot flash recovery recovery.IMG. then fastboot boot recovery.IMG. then when twrp boots, flash SuperSU. Reboot
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
that worked a treat. is it necessary to flash the MODIFIED BOOT IMAGE?
Recently I decided to try flashing a custom rom onto my old phone, a Gionee F103 Pro. Since it is quite obscure it isn't officially supported by twrp, but I managed to find an unofficial build. I unlocked the bootloader and flashed twrp using fastboot, and according to the console it was successful. When I booted my phone twrp began to load, but then there were multiple 'unable to mount' and 'failed to mount' errors and it rebooted. This has been repeating for almost an hour now. It's unresponsive to any button presses, and it won't show up on the device manager either. The only way I've got it to stop was by removing the battery. I've tried fastboot mode, recovery mode and regular boot but they all end up the same. I'd be grateful if anyone could could help me fix this.
Thanks!
fibonazi said:
Recently I decided to try flashing a custom rom onto my old phone, a Gionee F103 Pro. Since it is quite obscure it isn't officially supported by twrp, but I managed to find an unofficial build. I unlocked the bootloader and flashed twrp using fastboot, and according to the console it was successful. When I booted my phone twrp began to load, but then there were multiple 'unable to mount' and 'failed to mount' errors and it rebooted. This has been repeating for almost an hour now. It's unresponsive to any button presses, and it won't show up on the device manager either. The only way I've got it to stop was by removing the battery. I've tried fastboot mode, recovery mode and regular boot but they all end up the same. I'd be grateful if anyone could could help me fix this.
Thanks!
Click to expand...
Click to collapse
Can you flash a copy of stock recovery.img via fastboot?
Sent from my SM-S767VL using Tapatalk
Droidriven said:
Can you flash a copy of stock recovery.img via fastboot?
Click to expand...
Click to collapse
I tried to boot my phone into fastboot but it goes straight to twrp instead. My PC doesn't seem to detect it either.
fibonazi said:
I tried to boot my phone into fastboot but it goes straight to twrp instead. My PC doesn't seem to detect it either.
Click to expand...
Click to collapse
If there is a LineageOS ROM or some other custom ROM available for your device, try flashing a ROM.
If that doesn't work...
Flash a copy of stock recovery.img via TWRP. TWRP has the ability to flash .img files.
Or, if you can find a copy of your stock recovery that has been converted into a TWRP flashable .zip, you can flash that .zip via TWRP then reboot the device into recovery mode to see if it boots stock recovery.
If you can't get that to work, TWRP has a terminal emulator built in, you can try flashing stock recovery.img using dd commands in the TWRP terminal. You'll have to research your devices partition structure to get the correct dd command to make sure that the recovery gets flashed to the correct partition.
I'm only saying to do all of this because it seems that screwing with the recovery partition caused the issue, maybe, restoring/repairing the recovery partition might fix the issue.
If not, you'll have to find a fix that involves flashing your stock firmware or stock system.img.
Sent from my SM-S767VL using Tapatalk
Droidriven said:
If there is a LineageOS ROM or some other custom ROM available for your device, try flashing a ROM.
If that doesn't work...
Flash a copy of stock recovery.img via TWRP. TWRP has the ability to flash .img files.
Or, if you can find a copy of your stock recovery that has been converted into a TWRP flashable .zip, you can flash that .zip via TWRP then reboot the device into recovery mode to see if it boots stock recovery.
If you can't get that to work, TWRP has a terminal emulator built in, you can try flashing stock recovery.img using dd commands in the TWRP terminal. You'll have to research your devices partition structure to get the correct dd command to make sure that the recovery gets flashed to the correct partition.
I'm only saying to do all of this because it seems that screwing with the recovery partition caused the issue, maybe, restoring/repairing the recovery partition might fix the issue.
If not, you'll have to find a fix that involves flashing your stock firmware or stock system.img.
Click to expand...
Click to collapse
Actually, the problem I'm having is that twrp runs into an error and shuts down before I can do anything on it. It is stuck in an endless boot loop and is unresponsive to any button or screen presses. I have a lineage os rom, but I don't have any way to flash it right now. Is there any way to make it responsive again? Or any way to connect it to a pc?