I recently unlocked the bootloader and rooted the HTC Jetstream. I wanted to change the apns.xml file in the framework-res.apk. It's been awhile since I've done anything with an android device and I forgot to install CWM. I was in a rush and had done this a few times so I didn't think anything about it.
Now the tablet is stuck in a bootloop. I can get to HBOOT and therefore Fastboot, factory reset, etc. I even ran the factory reset but I'm still stuck in the bootloop. I came across this link so I could download a "stock" ROM, but the instructions call for CWM which I don't have. I was hoping that I could flash this ROM with Fastboot, but since I've never done this I wanted the opinion of an experienced Android user.
Thanks for your help in advance.
kylec8032 said:
I recently unlocked the bootloader and rooted the HTC Jetstream. I wanted to change the apns.xml file in the framework-res.apk. It's been awhile since I've done anything with an android device and I forgot to install CWM. I was in a rush and had done this a few times so I didn't think anything about it.
Now the tablet is stuck in a bootloop. I can get to HBOOT and therefore Fastboot, factory reset, etc. I even ran the factory reset but I'm still stuck in the bootloop. I came across this link so I could download a "stock" ROM, but the instructions call for CWM which I don't have. I was hoping that I could flash this ROM with Fastboot, but since I've never done this I wanted the opinion of an experienced Android user.
Thanks for your help in advance.
Click to expand...
Click to collapse
Can you get ADB to recognize you tablet at all?
ATT Intruder said:
Can you get ADB to recognize you tablet at all?
Click to expand...
Click to collapse
Unfortunately no. I think maybe the factory restore took away the USB debugging.
But since I have access to fastboot, I think I can flash a new system.img correct? And since I downloaded the "stock" ATT ROM it has the system directory. Only it isn't a system.img file.
I found another link that says this to create a system image like this:
sudo mkfs.cramfs temp/ system.1.5.img
sudo umount stock-system
sudo umount temp
So if I was to do this could I then flash via fastboot like this?
fastboot flash system system.img
Thanks for your time
Solved
My Jetstream is now back to normal. I used the information in this post.
Once I downloaded the files from the link I had to plug the tablet into my PC and put the it in fastboot mode and relock the bootloader "fastboot oem lock". The tablet turned off and I had to put it back into HBOOT mode. Run the .exe file that came with the download. Here I ran into a little trouble because the .exe file couldn't find my device. So I had to reinstall the drivers. After that just follow the prompts from the .exe file and I was good to go.
Related
I am having one hell of a time installing the new 4.0.3 Android (Ice Cream Sandwich) update. Everything was going smoothly, downloaded update, atempted to install, but then it got stuck on the HTC logo loading screen when I first boot the phone.
Attempted factory reset, did not work. Attempted recovery, which i was prompted with a phone logo with a red exclimation mark. From there, i help Vol up and power button to get to another screen, wiped cache and attempted another factory reset. Nothing.
I have been looking into re-flashing the phone manually ( i know that this may void the warranty, but due to my location, sending it out is NOT an option). I have downloaded a ripped version of the OEM ROM that the phone came stock with, placed it in a freshly reformatted SD card, then i went back into the boot loader. Immediately, the phone picked it up, and I let the phone do its thing, still nothing.
Am I doing something wrong, or is my phone complete botched past the point of no return?
Any help regarding this issue is GREATLY appreciated. Don't make me go back to using my BB Torch >.>
I talked to a rogers customer support agent, who transfered me to a technician. The reason my phone will load the new ROM, but fail to reboot is because the internal memory is fried. The reason the phone failed during an update and not from regular use is because i NEVER shut off my phone, and the OS was always loaded.
Good thing flashing the phone dosen't void the warranty
Akutalji said:
I talked to a rogers customer support agent, who transfered me to a technician. The reason my phone will load the new ROM, but fail to reboot is because the internal memory is fried. The reason the phone failed during an update and not from regular use is because i NEVER shut off my phone, and the OS was always loaded.
Good thing flashing the phone dosen't void the warranty
Click to expand...
Click to collapse
I had the same issue, but could easily pass through.
The thing is that my original rom was android 2.3, and i wanted to update to ics 4
So i restored the original rom then done, like you the htc update.Wehn the phone has reboot, i faced the same problem as yours.
To make the phone boot correctly, i simply get the boot.img from the latest "TeamGenesis3DRom" then "fastboot flash boot boot.img"
then "fastboot reboot" ans the phone starts correctly.
Hope it will help you.
If you are on s-on you will alwais need to flash new roms using fastboot. You need to upload the boot.img in cmd on your computer. I would open the rom and copy it over to the folder that i used to unlockboot loader then open cmd on your computer then type cd \rootevo3dnew then type fastboot flash boot boot.img. Before you download anny other roms you need to get 4ext recovery from play store. That recovery will work every time you want to flash new roms when your on s-on without having to use your computer.
Install Custom Rom
I didnt read ur second post. I was suggesting u to install custom ROM. I hope ur poblem solved by now.
Arceo85 said:
If you are on s-on you will alwais need to flash new roms using fastboot. You need to upload the boot.img in cmd on your computer. I would open the rom and copy it over to the folder that i used to unlockboot loader then open cmd on your computer then type cd \rootevo3dnew then type fastboot flash boot boot.img. Before you download anny other roms you need to get 4ext recovery from play store. That recovery will work every time you want to flash new roms when your on s-on without having to use your computer.
Click to expand...
Click to collapse
I totally agree with.
But this case is very particular.
I can tell because i'm S-OFF and can flash any rom i wanr whithout fastboot.
But in this particular case, even with taking the boot.img from the rom deployed by HTC and then flash it through fastboot, the phone didn't passed the HTC screen.
As i said, i had to take the boot.img from a custom rom (in his case it was a predator or genesis rom).
Akutalji said:
I am having one hell of a time installing the new 4.0.3 Android (Ice Cream Sandwich) update. Everything was going smoothly, downloaded update, atempted to install, but then it got stuck on the HTC logo loading screen when I first boot the phone.
Attempted factory reset, did not work. Attempted recovery, which i was prompted with a phone logo with a red exclimation mark. From there, i help Vol up and power button to get to another screen, wiped cache and attempted another factory reset. Nothing.
I have been looking into re-flashing the phone manually ( i know that this may void the warranty, but due to my location, sending it out is NOT an option). I have downloaded a ripped version of the OEM ROM that the phone came stock with, placed it in a freshly reformatted SD card, then i went back into the boot loader. Immediately, the phone picked it up, and I let the phone do its thing, still nothing.
Am I doing something wrong, or is my phone complete botched past the point of no return?
Any help regarding this issue is GREATLY appreciated. Don't make me go back to using my BB Torch >.>
Click to expand...
Click to collapse
the easiest way to fix your issue is to download the latest RUU from here then just rename it to PG86IMG, but first you have to relock your bootloader, vol down + power, then go to fast boot and type in command prompt "fastboot oem lock" and once you have the RUU on the root of your SD card boot back into bootloader and it will say **relocked** and then it will recognize the "PG86IMG" and it will check the file and ask you if you want to update, it will then install and everything should be hunky dory, I recommend after that, unlock your bootloader again via the HTCdev method and then make your phone s-off and then start flashing roms as often as you want without any issues
Arceo85 said:
If you are on s-on you will alwais need to flash new roms using fastboot. You need to upload the boot.img in cmd on your computer. I would open the rom and copy it over to the folder that i used to unlockboot loader then open cmd on your computer then type cd \rootevo3dnew then type fastboot flash boot boot.img. Before you download anny other roms you need to get 4ext recovery from play store. That recovery will work every time you want to flash new roms when your on s-on without having to use your computer.
Click to expand...
Click to collapse
Just for the hell of it, I tried it.
I downloaded fastboot, and got my hands on the stock .img for the evo. Still the same issue, the bootloader loads the new image but never asks to reboot.
Memory is fried They are now sending me a new phone
I've been trying everything I could find to root my wife's HTC Rhyme and nothing works. I tried flashing a custom RUU and now it won't boot. It just hangs at the white HTC screen. Now, I can only get to the bootloader.
The only thing that I've been able to do successfully is unlock/relock the bootloader. This is my wife's phone and I really want to root it so that she can have the benefit of being able to completely backup everything. However, at this point, I just want to get the damn phone to work again.
PLEASE... Any help would be greatly appreciated.
Thanks!
I'm still working on this. I'm finding a few hits on Google for this kind of issue but nothing seems to be working.
Please... anyone with any input at all would be helpful.
Thanks.
Boot into fastboot and run your device's RUU from your PC.
Hi... I tried to run the RUU application from my PC several time but it always fails with an error message saying that the "WRONG BOOTLOADER VERSION".
Thanks for your reply anyway.
********** UPDATE **********
I got it to boot-up normally.
I used the method explained here to extract the boot.img file and flashed it in fastboot.
I still have no recovery though. I really want to root this phone or at least get a recovery on it that I can create nandroid back-ups with.
RuLEoF2 said:
Hi... I tried to run the RUU application from my PC several time but it always fails with an error message saying that the "WRONG BOOTLOADER VERSION".
Thanks for your reply anyway.
********** UPDATE **********
I got it to boot-up normally.
I used the method explained here to extract the boot.img file and flashed it in fastboot.
I still have no recovery though. I really want to root this phone or at least get a recovery on it that I can create nandroid back-ups with.
Click to expand...
Click to collapse
If you have S-OFF, you should be able to flash CWM and root your device.
Problem fixed.
I was able to extract the stock recovery and boot image from the RUU application and flash them from fastboot.
Recovery is back and it's booting normally again.
RuLEoF2 said:
Problem fixed.
I was able to extract the stock recovery and boot image from the RUU application and flash them from fastboot.
Recovery is back and it's booting normally again.
Click to expand...
Click to collapse
plx tell me step by step my htc rhyme is bricked and the phone cmpltly dead plx help me
Hello,
I decided tyo go ahead and try to flash CM10 on my phone and when I did it got stuck at the HTC boot screen upon reboot.
I followed all the detailed instructions and this still happened to me. I figured that I could go ahead and apply the stock rom back just like in other cases of a soft-brick. However, this time upon updating it gave me the "Main version is older! error Press Power to reboot" when installing the stock RUU. Seeing as hansoons tool has a fix for that I apply it and it gives me now "Hboot version is older Press Power to reboot." This is now where I am stuck at. My phone is S-ON and I cannot find a way to turn S-OFF without actually booting into the actual OS. Is there a way and a different route I could take to un-brick my phone? Thanks.
glyphs said:
Hello,
I decided tyo go ahead and try to flash CM10 on my phone and when I did it got stuck at the HTC boot screen upon reboot.
I followed all the detailed instructions and this still happened to me. I figured that I could go ahead and apply the stock rom back just like in other cases of a soft-brick. However, this time upon updating it gave me the "Main version is older! error Press Power to reboot" when installing the stock RUU. Seeing as hansoons tool has a fix for that I apply it and it gives me now "Hboot version is older Press Power to reboot." This is now where I am stuck at. My phone is S-ON and I cannot find a way to turn S-OFF without actually booting into the actual OS. Is there a way and a different route I could take to un-brick my phone? Thanks.
Click to expand...
Click to collapse
are you using 43xt recovery? if not you need to use it since your s=on
and to get it to boot, use his tool to put that recovery on. and then reflash the cm10 rom. then it should work.
i believe that when you flashed it the kernel didnt boot.
ziggy46 said:
are you using 43xt recovery? if not you need to use it since your s=on
and to get it to boot, use his tool to put that recovery on. and then reflash the cm10 rom. then it should work.
i believe that when you flashed it the kernel didnt boot.
Click to expand...
Click to collapse
Nice, got it working thanks for your help and speedy reply man I was stuck for a second.
cheers +1
glyphs said:
Nice, got it working thanks for your help and speedy reply man I was stuck for a second.
cheers +1
Click to expand...
Click to collapse
no problem
Use the thanks button
Sent From My Amaze.
glyphs said:
Hello,
I decided tyo go ahead and try to flash CM10 on my phone and when I did it got stuck at the HTC boot screen upon reboot.
I followed all the detailed instructions and this still happened to me. I figured that I could go ahead and apply the stock rom back just like in other cases of a soft-brick. However, this time upon updating it gave me the "Main version is older! error Press Power to reboot" when installing the stock RUU. Seeing as hansoons tool has a fix for that I apply it and it gives me now "Hboot version is older Press Power to reboot." This is now where I am stuck at. My phone is S-ON and I cannot find a way to turn S-OFF without actually booting into the actual OS. Is there a way and a different route I could take to un-brick my phone? Thanks.
Click to expand...
Click to collapse
I had this same problem yesterday and corrected it by doing the following you need to put the phone into fastboot mode hold down power + power down once bootloader comes up click power again plug your USB in go into CMD (If On windows) CD to C drive then cd to the folder you put the files in below and run fastboot flash boot boot.img. The boot.img is going to be the boot.img from the rom you are using. This worked for me yesterday. When installing a rom make sure you clear Dalvik Cache,Cache & Wipe Data Factory Reset as well as formating your SD Card. Then toggle USB and copy the ROM over I would use 4EXT it is the best recovery out there.
Code:
https://dl.dropbox.com/u/102426750/XDA%20Dev/HTC%20Amaze.zip
Put these files in a folder in the root of your C drive. Once you cd into that folder with these files run the commands above
jared407 said:
I had this same problem yesterday and corrected it by doing the following you need to put the phone into fastboot mode hold down power + power down once bootloader comes up click power again plug your USB in go into CMD (If On windows) CD to C drive then cd to the folder you put the files in below and run fastboot flash boot boot.img. The boot.img is going to be the boot.img from the rom you are using. This worked for me yesterday. When installing a rom make sure you clear Dalvik Cache,Cache & Wipe Data Factory Reset as well as formating your SD Card. Then toggle USB and copy the ROM over I would use 4EXT it is the best recovery out there.
Code:
https://dl.dropbox.com/u/102426750/XDA%20Dev/HTC%20Amaze.zip
Put these files in a folder in the root of your C drive. Once you cd into that folder with these files run the commands above
Click to expand...
Click to collapse
Thank you so much, i made an account just to personally thank you for this.
I was stuck on the Bootscreen for cm10 and couldn't figure out what was wrong, but i tried your reply And it worked for me.
Thank you so much sir.
Isn't 4EXT like... the *COUGH*BEST RECOVERY FOR HTC DEVICES*COUGH*
I KNOW I SHOULD POST THIS IN MY NON-EXISTANT DEVICE FORUM,
but there is like no community there and I figured I would get a faster answer here.
I have an LG Mytouch Q C800 and I accidentally applied an OTA update with CWM installed. Since then I have been in a CWM bootloop, unable to boot into normal android. I dont think I can access fastboot or ADB. I have tried reflashing the stock ROM and everything. Can anyone help?
Yoyomah20 said:
I KNOW I SHOULD POST THIS IN MY NON-EXISTANT DEVICE FORUM,
but there is like no community there and I figured I would get a faster answer here.
I have an LG Mytouch Q C800 and I accidentally applied an OTA update with CWM installed. Since then I have been in a CWM bootloop, unable to boot into normal android. I dont think I can access fastboot or ADB. I have tried reflashing the stock ROM and everything. Can anyone help?
Click to expand...
Click to collapse
man the same thing happende to me, the only way i could partially recover my phone was flashing clockwork mod and from there install Cianogenmod 9, then in recovery mode conected to the pc via cable and typed:
"adb reboot bootloader"
once in Fastboot mode typed:
"fastboot boot boot.img"
where boot.img is the file contained in the cyanogenmod .zip file, doing this i managed to boot the rom and use my phone, the problem is that anytime it restarts it gets stuck in the boot loop again, and i have to repeat the process for it to boot again, i think is a bootloader problem since i have virtually done anything else, i think that the OTA update from tmobile changes something on the bootloader and it forces recovery/update boot always, and since the OTA never was completed it never got back to it's original state, its´s just my theory, i´m looking into it, but for now my phone works!.
Solution
I found a solution for the lg c800 bootloop, se my post: http://forum.xda-developers.com/showpost.php?p=39453347&postcount=10
I'm not new to flashing custom roms and rooting Android devices, so I don't think I'm a noob at this. I decided to help my friend unleash the power in his HTC One S by rooting it and giving it a custom recovery, I went through the right processes, Unlocked the phone's bootloader, and flashed the superuser zip and the twrp image, as it didn't seem like a clockworkmod image was compatible with the phone.
I then booted into recovery, wiped/factory reset and then flashed the latest CM11 nightly and got an error in TWRP recovery about the bootloader not been interoperable something like "
Code:
2.15==2.13"
in the error message , fine, I rebooted back into fastboot and checked the HBOOT Version and found out the phone was on HBOOT 1.13 and I think CM11 requires the most recent HBOOT version to work on HTC devices. The phone has got S-Off though.
Now I'm stuck in a bootloop cause I already wiped the OS in TWRP, I have everything in place, the right drivers and all that, I also tried re-installing the stock rom by downloading an HTC One S's RUU file but the device wasn't recognized at all by the RUU installer, I also tried to flash a stock 4.0.x rom as a zip file, no Joy. Now the phone is stuck at the point where it doesn't have an OS to boot into at all.
I'll really appreciate the community's support helping me fix this issue.
geek-x said:
I'm not new to flashing custom roms and rooting Android devices, so I don't think I'm a noob at this. I decided to help my friend unleash the power in his HTC One S by rooting it and giving it a custom recovery, I went through the right processes, Unlocked the phone's bootloader, and flashed the superuser zip and the twrp image, as it didn't seem like a clockworkmod image was compatible with the phone.
I then booted into recovery, wiped/factory reset and then flashed the latest CM11 nightly and got an error in TWRP recovery about the bootloader not been interoperable something like "
Code:
2.15==2.13"
in the error message , fine, I rebooted back into fastboot and checked the HBOOT Version and found out the phone was on HBOOT 1.13 and I think CM11 requires the most recent HBOOT version to work on HTC devices. The phone has got S-Off though.
Now I'm stuck in a bootloop cause I already wiped the OS in TWRP, I have everything in place, the right drivers and all that, I also tried re-installing the stock rom by downloading an HTC One S's RUU file but the device wasn't recognized at all by the RUU installer, I also tried to flash a stock 4.0.x rom as a zip file, no Joy. Now the phone is stuck at the point where it doesn't have an OS to boot into at all.
I'll really appreciate the community's support helping me fix this issue.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2322755
You need that. Luckily you're already S-Off, so shouldn't be terrible to get going again. Just update the firmware, reinstall TWRP and re-flash CM11. Should be good to go afterwards.
es0tericcha0s said:
http://forum.xda-developers.com/showthread.php?t=2322755
You need that. Luckily you're already S-Off, so shouldn't be terrible to get going again. Just update the firmware, reinstall TWRP and re-flash CM11. Should be good to go afterwards.
Click to expand...
Click to collapse
Thank you so much for the reply, does it matter that I don't have an OS to boot into as I already wiped and factory reset the phone for installation of a new rom.?
geek-x said:
Thank you so much for the reply, does it matter that I don't have an OS to boot into as I already wiped and factory reset the phone for installation of a new rom.?
Click to expand...
Click to collapse
Nah, shouldn't. The firmware we're referring to here is independent of the OS.
es0tericcha0s said:
Nah, shouldn't. The firmware we're referring to here is independent of the OS.
Click to expand...
Click to collapse
At the end of the guide, should help fix the issue, there's a part where I'm supposed to install the new CM kernel from the CM .zip package, how do I flash a kernel from Fastboot?
geek-x said:
At the end of the guide, should help fix the issue, there's a part where I'm supposed to install the new CM kernel from the CM .zip package, how do I flash a kernel from Fastboot?
Click to expand...
Click to collapse
Since you are S-Off, needing fastboot to install the boot.img is not necessary. It will install through recovery.
But, for future reference, you would boot to the bootloader screen, select fastboot, then assuming you have fastboot set up on the PC and the boot.img in the directory of said fastboot, you would use this command:
fastboot flash boot boot.img
then
fastboot reboot
es0tericcha0s said:
Since you are S-Off, needing fastboot to install the boot.img is not necessary. It will install through recovery.
But, for future reference, you would boot to the bootloader screen, select fastboot, then assuming you have fastboot set up on the PC and the boot.img in the directory of said fastboot, you would use this command:
fastboot flash boot boot.img
then
fastboot reboot
Click to expand...
Click to collapse
I tried flashing the firmware.zip file from the thread but I got a FAILED: (remote: not allowed) error in command prompt at the end of the process, what did I do wrong?
UPDATE: I was able to update the bootloader version successfully, as I forgot the part where I was to boot into RUU mode with fastboot oem rebootRUU and worked perfectly the second time.
I rebooted and found out the boot loader was updated to HBoot 2.15, and I also updated twrp to the latest S4 version but now in recovery I get errors about twrp been unable to mount the /data partition. Do I flash another recovery image?
UPDATE:
Thank you so much es0tericcha0s, I really appreciate the support, I got the /data mount issue fixed finally. I just had to flash an older twrp recovery image and then reflashed the new one in fastboot and I could then flash CM successfully.
I can't believe I finally unbricked this phone, its been bricked since Sunday. Once again, es0tericcha0s, Thank you!
geek-x said:
UPDATE: I was able to update the bootloader version successfully, as I forgot the part where I was to boot into RUU mode with fastboot oem rebootRUU and worked perfectly the second time.
I rebooted and found out the boot loader was updated to HBoot 2.15, and I also updated twrp to the latest S4 version but now in recovery I get errors about twrp been unable to mount the /data partition. Do I flash another recovery image?
Click to expand...
Click to collapse
You might need to RUU back then. If you have issues with the RUU exe, then you can extract the rom.zip and install it like you did the firmware. There are quite a few tutorials on how to extract it, or there might already be a version floating around for your phone.