[Q] need help, noob flashed a kernel by accident. - AT&T, Rogers HTC One X, Telstra One XL

Ok, this is my first time unlocking a device and it went well. I used Hasoon2000's kit to unlock and got twrp flashed and was going to get the Paranoid Android rom and Rohan's kernel all set to go. while getting it all set up, I was trying to figure out how to launch the command for the kernel but ran it instead. now my device is in a perpetual booting loop. Is there anything I can do or am I out of luck?

ryhnarch said:
Ok, this is my first time unlocking a device and it went well. I used Hasoon2000's kit to unlock and got twrp flashed and was going to get the Paranoid Android rom and Rohan's kernel all set to go. while getting it all set up, I was trying to figure out how to launch the command for the kernel but ran it instead. now my device is in a perpetual booting loop. Is there anything I can do or am I out of luck?
Click to expand...
Click to collapse
Wipe everything except sd card and flash a new ROM..
Typed from my HTC Explorer(Pico)
Powered with NextGen v1.5 and XDA Premium!

reboot into bootloader and "fastboot flash boot boot.img" the stock kernel from PA

How would I go about accessing the bootlaoder if it just keeps loading to the HTC boot screen then resetting itself?

ryhnarch said:
How would I go about accessing the bootlaoder if it just keeps loading to the HTC boot screen then resetting itself?
Click to expand...
Click to collapse
volume down + power

DvineLord said:
volume down + power
Click to expand...
Click to collapse
So I am in the bootloader, now whenever I click recover it goes back into the loop. is it possible for me to flash the stock kernel to stabilize it?

that's what i said. extract the boot.img from the rom. boot.img = kernel and flash it using "fastboot flash boot boot.img"

my problem here is that i don't have PA flashed on it yet. Is there a way to fastboot the rom onto it from my pc? there isn't an option to do that from Hasoon2000's kit.
I got into twrp on my device. Do I need to mount the SD to put PA on my device to flash it?

ryhnarch said:
my problem here is that i don't have PA flashed on it yet. Is there a way to fastboot the rom onto it from my pc? there isn't an option to do that from Hasoon2000's kit.
I got into twrp on my device. Do I need to mount the SD to put PA on my device to flash it?
Click to expand...
Click to collapse
yes, go to install and flash rom.zip then reboot into system

Crappyvate said:
yes, go to install and flash rom.zip then reboot into system
Click to expand...
Click to collapse
Alright, just started the flash. hope everything goes well. thanks for your help so far.

PA is flashed, but now it won't load the rom. It starts the PA loading animation, then nothing it has been sitting there for about 30 mins.

I have the feeling that I may have soft bricked the phone. I have tried re-flashing PA and even tried CM10, both times clearing both caches. Is there anything else I can do to get past the boot animation?

Are you on hboot 1.14 (2.20 firmware)?
Did you flash the kernel before installing the rom?
Just going to start posting this:
http://forum.xda-developers.com/showthread.php?t=1954060

area51avenger said:
Are you on hboot 1.14 (2.20 firmware)?
Did you flash the kernel before installing the rom?
Just going to start posting this:
http://forum.xda-developers.com/showthread.php?t=1954060
Click to expand...
Click to collapse
yes to both, and I had just read about needing to flash the boot.img first. For my own clarification, the boot.img is the kernel correct? If so Hasoon2000's kit has a section to put the img in and just flash it on. When ever I choose factory reset from the bootloader, it takes me into twrp, by doing this has it already done the factory reset, or is there something else I need to do?
this is starting to feel like a trial by fire situation for me

ryhnarch said:
yes to both, and I had just read about needing to flash the boot.img first. For my own clarification, the boot.img is the kernel correct? If so Hasoon2000's kit has a section to put the img in and just flash it on. When ever I choose factory reset from the bootloader, it takes me into twrp, by doing this has it already done the factory reset, or is there something else I need to do?
this is starting to feel like a trial by fire situation for me
Click to expand...
Click to collapse
You factory reset from bootloader? Can you access your SD card in TWRP?

Yes I can access the sdcard from twrp, and I have used the factory reset option a couple of times to access twrp when I was first having issues getting in from the recovery option.
update - I just tried flashing it again and It finally cleared the animation. I am setting it up now and thanks to everyone for their help.

Related

How do I fix this?

"Hi! I'm messaging you in regards to my issue while flashing Cyanogenmod 10. I will try to explain exact details of what happened. First I successfully rooted flash clockwork recovery mod superuser etc. using your amazing step by step videos. I decided to flash CM10. I did the beginning part by opening cmd prompt and doing the boot.img etc. While I was on fastboot mode I noticed you had an option for hboot. I did not have that option so instead I clicked Bootloader, opened into to recovery, and tried vigorously installing cm10 from sd card but it always said it could not open it and aborted it. I panicked and wipe data/cache/dalvik cache. I tried multiple times and I still could not install it. On the bootloader I decided to click Factory Reset. It took me too recovery but now I cannot open my sdcard and this error keeps popping up: "E: Can't mount". Now I am panicking big time because I know this could by a soft brick but I have no idea how to undo everything. Please help! It would be greatly appreciated! ".
This is the message i sent to the person who made the video but I am also posting it here because I was wondering how to undo all of this and fix it. This is his video he does a good job of explaning but I just want to fix this and get it back to normal: http://www.youtube.com/watch?v=elDvcVot7qo
Thanks everyone!
First things first... Don't use clock work use twrp second r u sure that cm10 is for our phone not the int one...third don't factory reset from bootloader you corrupted your sd reformat your sd flash twrp from fastboot go into recovery and drag over a Ron from your comp and flash
omario8484 said:
First things first... Don't use clock work use twrp second r u sure that cm10 is for our phone not the int one...third don't factory reset from bootloader you corrupted your sd reformat your sd flash twrp from fastboot go into recovery and drag over a Ron from your comp and flash
Click to expand...
Click to collapse
This, also note what version your hboot is, 1.14 means you have to flash the boot.img first from fastboot before you can install that .zip fromTWRP
omario8484 said:
First things first... Don't use clock work use twrp second r u sure that cm10 is for our phone not the int one...third don't factory reset from bootloader you corrupted your sd reformat your sd flash twrp from fastboot go into recovery and drag over a Ron from your comp and flash
Click to expand...
Click to collapse
I just found out that there is a version specifically for the AT&T builds. Yeah I did that and corrupted my sdcard and now I'm stuck on how to reformat it. I have to admit I am quite a noob at this but I've been flashing since my old Samsung Captiviate.
Myrder said:
This, also note what version your hboot is, 1.14 means you have to flash the boot.img first from fastboot before you can install that .zip fromTWRP
Click to expand...
Click to collapse
Yes you're right I have to fastboot the boot.img first. I'm just stuck on how to get back because the CM10 I put on my phone was for a different version of the One X and I've corrupted my sd card.
omario8484 said:
First things first... Don't use clock work use twrp second r u sure that cm10 is for our phone not the int one...third don't factory reset from bootloader you corrupted your sd reformat your sd flash twrp from fastboot go into recovery and drag over a Ron from your comp and flash
Click to expand...
Click to collapse
I did exactly as you said and I did reformat SD from windows using TWRP and successfully flashed CM10/GAAPS etc. But my phone is just on a bootloop with the HTC screen popping up and a message saying "This build is for development purposes only. Do not distribute outside of HTC without HTC's written permission. Failure to comply may lead to legal action". Now what lol?
sam10037 said:
I did exactly as you said and I did reformat SD from windows using TWRP and successfully flashed CM10/GAAPS etc. But my phone is just on a bootloop with the HTC screen popping up and a message saying "This build is for development purposes only. Do not distribute outside of HTC without HTC's written permission. Failure to comply may lead to legal action". Now what lol?
Click to expand...
Click to collapse
You'll always see that screen that's our splashy screen after we unlock our bl...but it seems as your forgetting to flash the boot IMG manually through fastboot AFTER you flash the rom
omario8484 said:
You'll always see that screen that's our splashy screen after we unlock our bl...but it seems as your forgetting to flash the boot IMG manually through fastboot AFTER you flash the rom
Click to expand...
Click to collapse
+1. You need to manually flash boot.img via fastboot first, and then flash the CM10 rom w/ GApps. fastboot flash boot boot.img
once you've flashed the boot.img via fastboot (hopefully that'll clear up your bootloop issue). There is an app around called FlashImageGUI for flashing img files (straight from the zip too) so you don't need a computer to flash the boot.img. This is a great timesaver.
stopped at clockwork recovery .....
CheesyNutz said:
stopped at clockwork recovery .....
Click to expand...
Click to collapse
exactly, dude screwed up. time to start from scratch.

[Q] Flashed new kernel, won't boot

I used Hasoon2000's HTC All-In-One Kit to root my phone. That all worked.
The issue came when i flashed a new kernel. I placed the boot.img from King Kang's new ROM (http://forum.xda-developers.com/showthread.php?t=1959099)
Anyway, When i boot I get the HTC, quietly brilliant logo, and this in red letters "This build is for development purposes only. Do not distrubute... "
i can boot into recovery (pwr+ vol down)
And i get the ***TAMPERED*** AND ***unlocked*** tags at the top
I don't know where to go from here...
Thanks for the help.
Also, whenever i boot into recovery or factory reset, neither succeed.
This was probably known info, just wanted to add it.
ccamwilkins said:
Also, whenever i boot into recovery or factory reset, neither succeed.
This was probably known info, just wanted to add it.
Click to expand...
Click to collapse
You mentioned in your original post that you could boot into recovery, so is that not working now? Factory reset might've fubared the recovery piece, so you could do one of two things:
1) download the original RUU version for your phone, relock your phone, and flash the RUU and start over.
2) try reinstalling TWRP.
This whole thing sounds like trying to install a kernel or fastboot flash a boot.img without SuperSU correctly installed. This is what happened to me when I first unlocked my phone and tried to fastboot flash the CM10 boot.img after failing the flash from recovery twice. Without that super-user permission, bad things tend to happen. If you decide to continue on with reinstalling TWRP, make sure SuperSU.zip is flashed successfully from
TWRP, then try your rom/kernel combination again (or even a different combination if you're apprehensive).
BEWARE: sometimes partially flashing these things can corrupt your sd card. I had to reflash the original RUU to fix my phone BEFORE I rerooted and flashed a rom/kernel.
Have you fastbooted a SU to your phone after you rooted and unlocked? I'd imagine you did if you followed the toolkit.. So your on 2.20... Just download cleanrom 5.1 on your computer. Mount sdcard via recovery and drag cleanrom onto phone. Flash entire rom in recovery. I bet it works
Once your on a stable rom, download king kang from your phone. Download flashgui. Open flashgui app, navigate to king kang and let it find the boot img and flash it for you.. Once successful, immediately boot into recovery and flash entire rom through twrp.
Success
Sent from my One X using Tapatalk 2

[Q] Soft-Bricked - usual solutions don't work

Sorry, for bothering you with this but unfortunately, I have soft-bricked my phone. It's a WIND Canada HTC One S with S4 cpu, CID is GLOBA001 with HBOOT 1.14.0004.
I had Cyanogenmod 10 installed, ran in some problems, tried to find a solution (among others this: http://forum.xda-developers.com/showthread.php?t=1630459 didn't work) and bricked it: boot loop, unmountable /sdcard, no working recovery. I have tried for hours all the tips I found in the forums but none helped. I even downloaded a RUU but I couldn't install it (probably the wrong version).
Current state is: I can only get into the bootloader which is re-locked (by courtesy of one of my repair attempts). Connecting via USB to fastboot works. Nothing else, for all purposes the phone is clean, empty and oh so very much dead.
How do I proceed from here? In the end I want to have working version of Cyanogenmod back.
Thank you in advance, guys!
el_Harmakhis said:
Sorry, for bothering you with this but unfortunately, I have soft-bricked my phone. It's a WIND Canada HTC One S with S4 cpu, CID is GLOBA001 with HBOOT 1.14.0004.
I had Cyanogenmod 10 installed, ran in some problems, tried to find a solution (among others this: http://forum.xda-developers.com/showthread.php?t=1630459 didn't work) and bricked it: boot loop, unmountable /sdcard, no working recovery. I have tried for hours all the tips I found in the forums but none helped. I even downloaded a RUU but I couldn't install it (probably the wrong version).
Current state is: I can only get into the bootloader which is re-locked (by courtesy of one of my repair attempts). Connecting via USB to fastboot works. Nothing else, for all purposes the phone is clean, empty and oh so very much dead.
How do I proceed from here? In the end I want to have working version of Cyanogenmod back.
Thank you in advance, guys!
Click to expand...
Click to collapse
Unlock it first, you can't do anything with it locked.
Darknites said:
Unlock it first, you can't do anything with it locked.
Click to expand...
Click to collapse
Okay, the device is unlocked again. How do I continue?
Thanks a lot, by the way!
el_Harmakhis said:
Okay, the device is unlocked again. How do I continue?
Thanks a lot, by the way!
Click to expand...
Click to collapse
Flash TWRP recovery and try to mount the sd and connect it to the pc.
Darknites said:
Flash TWRP recovery and try to mount the sd and connect it to the pc.
Click to expand...
Click to collapse
Okay, flashing TWRP worked. I then booted into recovery, clicked on "mount" and then "mount usb device". After some driver installs I can no see the internal storage. Apart from a folder for TWRP and .android_secure it's empty. Is this where I now put the Cyanogenmod file and install it via the recovery?
el_Harmakhis said:
Okay, flashing TWRP worked. I then booted into recovery, clicked on "mount" and then "mount usb device". After some driver installs I can no see the internal storage. Apart from a folder for TWRP and .android_secure it's empty. Is this where I now put the Cyanogenmod file and install it via the recovery?
Click to expand...
Click to collapse
Ya place it where you want and then flash it but you will need to fastboot the boot.img file thats in the rom zip, you can use the All-In-One Toolkit to do that.
Darknites said:
Ya place it where you want and then flash it but you will need to fastboot the boot.img file thats in the rom zip, you can use the All-In-One Toolkit to do that.
Click to expand...
Click to collapse
Copying the ROM and then installing via TWRP worked though I saw that TWRP displayed an error, saying it was unable to mount /cache. When I tried to wipe the Cache & Dalvik Cache I got the same error.
Nevertheless I then went ahead and copyed the boot.img (extracted that one from the Cyanogenmod zip) via fastboot and rebooted the device. Now the phone is stuck in the Cyanogenmod boot loop.
el_Harmakhis said:
Copying the ROM and then installing via TWRP worked though I saw that TWRP displayed an error, saying it was unable to mount /cache. When I tried to wipe the Cache & Dalvik Cache I got the same error.
Nevertheless I then went ahead and copyed the boot.img (extracted that one from the Cyanogenmod zip) via fastboot and rebooted the device. Now the phone is stuck in the Cyanogenmod boot loop.
Click to expand...
Click to collapse
Hmm think you going to have flash the stock recovery then do a factory reset in the bootloader then go back to TWRP and copy over the rom again then factory reset in TWRP and then wipe system and then flash the rom. Do not lock the bootloader.
Darknites said:
Hmm think you going to have flash the stock recovery then do a factory reset in the bootloader then go back to TWRP and copy over the rom again then factory reset in TWRP and then wipe system and then flash the rom. Do not lock the bootloader.
Click to expand...
Click to collapse
Okay, I will try that! Where might I get the stock recovery? I don't want to pick the wrong!
el_Harmakhis said:
Okay, I will try that! Where might I get the stock recovery? I don't want to pick the wrong!
Click to expand...
Click to collapse
Go here for it.
Darknites said:
Go here for it.
Click to expand...
Click to collapse
Ha! It finally worked! Thank you very much! Have a nice weekend!
el_Harmakhis said:
Ha! It finally worked! Thank you very much! Have a nice weekend!
Click to expand...
Click to collapse
Np dude, you too.

[Q] Red Triangle, Dead Android

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.

[Q] Stuck at HTC splash screen after ROM flash

Happens ever time when I try to flash a new ROM. The phone will get stuck at the splash screen and nothing else happens. The default backup I made works fine, but if I try any other ROM, it freezes.
Currently using TWRP 2.6.3.0, rooted, and bootloader is unlocked.
Any suggestions?
YourYellowFriend said:
Happens ever time when I try to flash a new ROM. The phone will get stuck at the splash screen and nothing else happens. The default backup I made works fine, but if I try any other ROM, it freezes.
Currently using TWRP 2.6.3.0, rooted, and bootloader is unlocked.
Any suggestions?
Click to expand...
Click to collapse
Without s off you will need to manually fastboot flash the boot.img of every Rom you flash. Recovery has no access to boot partition without s off.
Gizmoe said:
Without s off you will need to manually fastboot flash the boot.img of every Rom you flash. Recovery has no access to boot partition without s off.
Click to expand...
Click to collapse
Ah, okay. Thanks.
Gizmoe said:
Without s off you will need to manually fastboot flash the boot.img of every Rom you flash. Recovery has no access to boot partition without s off.
Click to expand...
Click to collapse
Not my thread, but it still kinda applies:
What about if I'm flashing a stock RUU and it gets stuck on the splash screen (or boot loop)?
Currently the phone has a relocked bootloader and S-ON.
Can't really access much else.
Ideas?
Pigbenis12 said:
Not my thread, but it still kinda applies:
What about if I'm flashing a stock RUU and it gets stuck on the splash screen (or boot loop)?
Currently the phone has a relocked bootloader and S-ON.
Can't really access much else.
Ideas?
Click to expand...
Click to collapse
I would run RUU with a freshly formatted sd card. Make sure RUU flash is completed as well and you aren't trying to downgrade or anything. Other than that your emmc may be toast.

Categories

Resources