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.
Okay, so I rooted my wife's LG C800 (T-Mobile MyTouch Q), with the hopes of finding a decent custom ROM. No luck, went back to stock. Didn't unroot. OTA comes out today. Wife doesn't know any better, and tries the OTA update. Now can't get out of recovery. I've cleared Dalvic (although get an error message "E:unknown volume for path [/sd-ext]", it still says wipe successful), format system, format cache, factory resent and re=flash the stock ROM several times. Still will only boot to ClockworkMOD. I have tried manually flashing the boot.img. Same thing. I tried manually flashing system.img, but it says it's too big. Any ideas would be GREATLY appreciated.
Thanks,
Wulf
Stock Recovery
greowulf said:
Okay, so I rooted my wife's LG C800 (T-Mobile MyTouch Q), with the hopes of finding a decent custom ROM. No luck, went back to stock. Didn't unroot. OTA comes out today. Wife doesn't know any better, and tries the OTA update. Now can't get out of recovery. I've cleared Dalvic (although get an error message "E:unknown volume for path [/sd-ext]", it still says wipe successful), format system, format cache, factory resent and re=flash the stock ROM several times. Still will only boot to ClockworkMOD. I have tried manually flashing the boot.img. Same thing. I tried manually flashing system.img, but it says it's too big. Any ideas would be GREATLY appreciated.
Thanks,
Wulf
Click to expand...
Click to collapse
On a side note, any ideas how to go back to stock recovery on the LG C800?
Thanks in advance!
I have the exact same problem
Any help would be appreciated.
Thanks
Any luck yet Greowulf?
ng1and said:
Any luck yet Greowulf?
Click to expand...
Click to collapse
Nope, ended up having to replace it. Unlike my HTC Doubleshot, this LG C800 just doesn't have a robust dev community. I think I'll keep her on the stock recovery and ROM until we can afford a better phone. . .
Bummer
Guess I'll have to do the same thing. I'm going to try taking it to a store but I doubt they'll help since it's jailbroken. I'll update when I do.
Thanks for letting me know.
I have the same problem
Hi, i have the same problem, but when i flashed the original recovery that i downloaded from de clockwork mod recovery post my phone died, now when i turn it on it does the same thing (it always boot to recovery) as before but with the original recovery, when it tries to boot the original recovery it doessen´t do anything and restarts which starts the same process again (boot in recovey for 1 second and restarts), any idea to get my phone back???
Update on my problem
Hello i´ve manage to put my phone in S/W Upgrade mode but i try to use the LGMobile Support Tool to restore my phone to its original state, in this process it stops about twelve seconds in and tells me that an error ocurred and it cant continue with the process, i´ve tried fastboot keys to but in that mode but it boots directly into recovery mode and stays in a loop of reseting and going in to recovery mode (in this mode i can't do anything on my pc because it appears and disapears to fast), the only way i´ve managed to use pc tools is by putting it in S/W Upgrade, in my pc i can see a serial port, a modem and a Lg android phone, but in cmd using "adb device" nothing appears, any idea on what to do next?
mr arrieta said:
Hi, i have the same problem, but when i flashed the original recovery that i downloaded from de clockwork mod recovery post my phone died, now when i turn it on it does the same thing (it always boot to recovery) as before but with the original recovery, when it tries to boot the original recovery it doessen´t do anything and restarts which starts the same process again (boot in recovey for 1 second and restarts), any idea to get my phone back???
Click to expand...
Click to collapse
Ok, if you have this problem plss never restore to the original recovery before solving it, if you flash your original recovery you might end up worst, all you have to do in this case is restoring the backup you made when installing clockwork mod, if you are like me and never did one or erased it later on, i´ve been trying to see how to fix my phone, and the closest i am of making it work is flashing CyanogenMod through CWM then i enter fastboot mode and make it boot from the extracted boot image from the CyanogenMod .zip file, i dont have a permanent fix, but ill keep you posted.
Partial solution
Hello, i foud i very nasty solution but it works for now is the only way i know to fix Lg c800 bootloop, this was only tested with Cyanogen mod 9 latest nightly, to force always your phone to boot os and not the recovery i repaced the phone's recovery.img with the boot.img contained in the cyanogen mod .zip file, here's a step by step guide.
1. Download latest nightly Cyanogen mod 9 for lg c800 release .zip
2. Flash this image with the clockworkmod recovery
3. In recovery mode connect your phone to the pc and with adb and fastboot installed
4. Reboot your phone to fastboot mode typing: "adb reboot bootloader"
5. Once in fastboot (lg logo with black screen) type: "fastboot flash recovery boot.img", for this to work you must have your boot.img extracted from the cyanogen mod9 zip file in the same directory as your adb and fastboot .exe
6. Reboot your phone typing: "fastboot continue"
And when this is finished your phone boots drectly to your installed Cyanogen mod 9 firmware, there are some side effects to this fix, because it is no final, the side effects are:
1. Your phone does not have recovery now, if you boot it in recovery mode or normal mode it always boots to your Cyanogenmod 9 ROM, you can always boot your recovery manually from the pc in fastboot by typing "fastboot boot recovery.img", for this to work you must have your recovery.img extracted from the Clockwork recovery zip file in the same directory as your adb and fastboot .exe
2. This fix only works for custom roms, if you try this with a stock 2.3.6 o 2.3.4 Rom your phone wont boot and you will have to start over, it only worked for me with Cyanogen mod 9.
I hope you can take back to live your phones as i did, if you're stuck in bootloop and dont have clackwork mod installed into your device, you have to flash a custom kdz rom that contains clockwork recovery an then do what´s on the guide, i have a custom kdz to do this but have no place or time to upload it, as soon as i con i will post it.
---------- Post added at 04:59 PM ---------- Previous post was at 04:24 PM ----------
PLSSSS be aware that if you do this wrong (by using a stock rom instead of cyanogen mod 9) and dont have the .kdz that flashes clockwork recovery to your phone, you might end up worst than before, but in my experience i always had adb acces to the phone when using cyanogen mod 9, to restore your phone if something goes wrong and you have adb acces type:
"adb reboot bootloader"
"fastboot erase recovery"
"fastboot flash recovery recovery.img", for this to work you must have your recovery.img extracted from the Clockwork recovery zip file in the same directory as your adb and fastboot .exe
"fastboot continue"
and your are done, now you have cwm recovery installed in your phone and stuck in bootloop again.
Plss if you don't have adb acces flash this kdz image (this is pending, i'm uploading it but i think it will be available on tuesday), is a custom rom that mounts clockwork recovery and other usefull stuff to recover your phone in this method (this kdz wot fix your bootloop problems, only mounts clockworkmod recovery to your phone so you can follow the guide, flash roms and have a adb acces)
ng1and said:
Bummer
Guess I'll have to do the same thing. I'm going to try taking it to a store but I doubt they'll help since it's jailbroken. I'll update when I do.
Thanks for letting me know.
Click to expand...
Click to collapse
Don't take it in, call in. They'll walk you through trouble shooting and mail you a new one if it's still in warranty. LG will do the same if you're not with T-mobile, but you'll have to pay for shipping
Link
this is the link for the kdz image i made: https://www.dropbox.com/s/p4ozl5wwdtwsub0/V10V_00 mia CWM y Cianog.kdz, this one installs clockworkmod to your phone's recovery, flash it to follow the guide i posted before.
Has anyone found a full solution? I am stuck just like the first post, i can get to cwm recovery but it is stuck in a continuos loop back to recovery. I haven't tried mr arrieta still as i need a full solution to this. I have backup in my sdcard of the original recovery i took from flash boot, a copy of the stock rom that is rooted and the lastest Cyanogenmod 9.
I tried using a zip I found called exitrecovery.zip but it didn't work. Should i try to install the original recovery with the stock rom and try to do a factory reset with LG PC Suite software??
I would really appreciate some help here.
I have my father's MyTouch Q that was rooted and is now in a boot loop. It only stays active (as far as being connected by usb) for about 2-3 seconds so I don't have enough time to put it into fast boot or really do anything with it unless I can figure out how to keep it active longer. I have tried many of the possible fixes and yet I am still banging my head against this desk. I would appreciate any help on this matter.
BigDv said:
I would really appreciate some help here.
I have my father's MyTouch Q that was rooted and is now in a boot loop. It only stays active (as far as being connected by usb) for about 2-3 seconds so I don't have enough time to put it into fast boot or really do anything with it unless I can figure out how to keep it active longer. I have tried many of the possible fixes and yet I am still banging my head against this desk. I would appreciate any help on this matter.
Click to expand...
Click to collapse
To keep active longer you need to put you'r phone into S/W update mode by pressing E+volup+pwr, in this mode you can flash via KDZ updater the .kdz file i compiled and published, if you complete correctly this steps your phone should be booting into cwm recovery from there you have to flash the latest cm9 nightly and via fastboot replace your recovery with the boot.img contained in the cm9.img.
when you finish this process you should have a phone that has no recovery mode but always boot into the rom directly, that is how i've been using my phone till i have time to find a solution with recovery mode.
---------- Post added at 12:46 AM ---------- Previous post was at 12:37 AM ----------
Altaflux said:
Has anyone found a full solution? I am stuck just like the first post, i can get to cwm recovery but it is stuck in a continuos loop back to recovery. I haven't tried mr arrieta still as i need a full solution to this. I have backup in my sdcard of the original recovery i took from flash boot, a copy of the stock rom that is rooted and the lastest Cyanogenmod 9.
I tried using a zip I found called exitrecovery.zip but it didn't work. Should i try to install the original recovery with the stock rom and try to do a factory reset with LG PC Suite software??
Click to expand...
Click to collapse
Hello i've tried all solutions you can find on the internet and none seem to work, i restored original backups, tried zip files, etc... the probles is that if you flash the stock recovery you will end up worst because you will have to us the kdz programer to recover the CWM and your phone will be in a bootloop of 3 seconds in which you can do less.
for now there is no full solution, since i think i am the only one working on this and i don't have the time for this project, when i bricked my phone i needed a fast solution and that is what i have and posted.
my solution makes your phone to boot always into the OS partition so your phone will always work, but you will not have a recovery.
Update
Hello, i've learned a lot of stuff since last time, but i have no solution yet, i'm hoping some one will read this and help me get to a solution since i've read a lot and there are still lots of stuff i cant seem to make out (@chui101).
First i tried a couple of solutions i found online for fixing CWM recovery loop after ota, but one of them bricked my phone even worst, i ended up in a qualcom high speed conection with black screen and no GUI, i thought my phone was dead forever (i've felt that way a lot lately but it always seems to find the way to come back to life ), i managed to get my phone back to life with QPST and some files i got out a KDZ file, but i was still in the CWM recovery loop.
I continued my research and found out that it is mostlikely fault of the misc partition that stores data between phone modules, so i got my phone partition table and began looking in the original boot.img and recovery.img files to find any piece of information i could get my hands on, since this phone has very little info out there and tried to find any comand that would reset the ota update flag that began all this, in this process i bricked my phone fastboot mode and had to do a full brick and fix with QPST since KDZ didn't seemed to do the trick, here is what i got so far as partition table goes:
mmcblk0p1 ----->
mmcblk0p2 ----->
mmcblk0p3 ----->
mmcblk0p4 ----->
mmcblk0p5 ----->
mmcblk0p6 ----->
*mmcblk0p7 -----> boot
mmcblk0p8 ----->
mmcblk0p9 ----->
mmcblk0p10 ----->
mmcblk0p11 ----->
mmcblk0p12 ----->
mmcblk0p13 -----> rmt storage
mmcblk0p14 -----> rmt storage
*mmcblk0p15 -----> system
*mmcblk0p16 -----> data
*mmcblk0p17 -----> recovery
*mmcblk0p18 -----> cache
mmcblk0p19 -----> rmt storage
mmcblk0p20 -----> wifi pemission root
mmcblk0p21 -----> DivX cache
mmcblk0p22 ----->
mmcblk0p23 ----->
mmcblk0p24 ----->
*mmcblk1p1 -----> sd card
I cant seem to locate which one is the misc partition yet, my theory is that if i can identify this partition some one that has a working lg c800 Mytouch Q cand back up this partition for me as a misc.img and with it i could restore my phone to a correct working state, since i foud online a nandroid backup but it didn't fixed my loop.
Other Approach
Another option i thought is to mod an original boot.img to boot directly to the kernel img and trigger a new OTA from there with the unrooted phone and original recovery, but i cant seem to make this right, since i unpack the original boot.img and then without changing anything i repack it and only by doing that the newboot.img doesn't do anything it freezes on the LG logo of the fastboot mode.
I'm using boot kitchen.rar i found online which uses split_bootimg.pl to get out kernel and ramdisk from image, then 7Zip to extract ramdisk.gz and its content, then repacks it with mkbootfs.exe and with mkbootimg.exe, the command i'm using for making the boot image is:
"mkbootimg --kernel boot.img-kernel --ramdisk ramdisk-new.gz -o newboot.img --base 0x00200000"
but ive tried with --cmdline option (using the comand line message it gives me when extracting, and my mkbootimg.exe does not recieve the --base comand), and tried in different order but newboot.img doese't work.
Any ideas, any developers, any mod? any something????
LG myTouch Q (C800) Stuck on LG Logo Fix Solution !
:good: :good::laugh:
mobiletek909 said:
:good: :good::laugh:
Click to expand...
Click to collapse
Will this make me lose root or relock the phone?
Hi guys, I have stumbled upon a problem and any help found here is not helping. I have decided to finaly root moto E (I thought I am too old for rooting now, but I am not) and the problem I got is pretty simple.
Bootlocked unlock is ok.
But then I decided not to reflash stock recovery and just to boot into recovery for once to flash superSU to avoid martyrium caused by getting original recovery (since HTC different retarded versions for every country and every retailer, I am very cautious). I have tried 2 versions of TWRP, one CWM, after "fastboot boot recovery.img" phone boots forever, never finishes, but phonw is fully operational still, so no damage done. I have even tried to reflash recovery in the end, none of them worked. Well, command prompt told me OKAY OKAY, but nothing really happened, like while just booting into recovery. I have even tried several USB cables (happened once with desire X that everything was due to broken USB cable).
I am out of ideas, could please someone point me to some direction of what is wrong?
It runs 4.4.4
mindlesSheep said:
Hi guys, I have stumbled upon a problem and any help found here is not helping. I have decided to finaly root moto E (I thought I am too old for rooting now, but I am not) and the problem I got is pretty simple.
Bootlocked unlock is ok.
But then I decided not to reflash stock recovery and just to boot into recovery for once to flash superSU to avoid martyrium caused by getting original recovery (since HTC different retarded versions for every country and every retailer, I am very cautious). I have tried 2 versions of TWRP, one CWM, after "fastboot boot recovery.img" phone boots forever, never finishes, but phonw is fully operational still, so no damage done. I have even tried to reflash recovery in the end, none of them worked. Well, command prompt told me OKAY OKAY, but nothing really happened, like while just booting into recovery. I have even tried several USB cables (happened once with desire X that everything was due to broken USB cable).
I am out of ideas, could please someone point me to some direction of what is wrong?
It runs 4.4.4
Click to expand...
Click to collapse
Please post screenshot of terminal.
Try these steps
1: adb reboot bootloader
2: fastboot devices
3: fastboot flash recovery name-of-the-recovery.img
not at pc atm,but as I said,devices list my device, fastboot flash gives okay twice,same as fastboot boot, and reboot bootloader... I think it would not help me at all, bootloader is accesible
edit: adb reboot recovery does notghing else than manualy booting into recovery (=nothing)
I didn't pay attention to HTC part, recently I faced same problem after flashing recovery and worst part was when I did Factory Reset. It got stuck on forever Boot Loop. Try this Go through Recovery 1. Wipe Dalvik Cache 2. Factory Reset. This worked for me hope same for you. And correct me if I couldn't get your problem.