Database Users

[HELP] Stuck at HTC logo after installing bacon on unofficial CMod

What I did
1. Install unofficial CMod
2. Installed baconbits
Problem after bacon bits install on unofficial CM: i boot up the phone but it gave me an error/popup for every application i was running "google voice has encountered an error" "com.android has encountered an error" etc etc. endless popups to where i couldnt do anything on the phone other than locking and unlocking it.
what i tried to do to fix it:
3. Wipe data/factory reset
4. Tried applying Stock Recovery, thinking it would somehow help
current problem: stuck at HTC logo
please help! i just want to get it back up and running, any rom... rooted or not. i cant even get into the phone

Wow u really messed up.
Idk how to truly guide u out of this because it seems like u really don't know what ur doing. But your going to have to restore the phone. Read the thread about unrooting and returning to stock.
Also if I'm not mistaking you can fastboot flash system.img and data.img from pc10img.zip but as I said idk 100%
And flashing stock recovery is a no no because it can only read htc zips so it will block you out from flashing a new update.zip
Sent from my T-Mobile G2 using XDA App

Can you get into fastboot? Power the phone down and hold VolDown+Power.
Flashing baconbits over a non-official CM 6.1 was a mistake.... Baconbits is just an addon for a stock rom... CM 6.1 will have everything that baconbits has and more...

yes i can get into fastboot. problem is finding a htc signed rom... i think

If you are still S-OFF, you can flash clockwork mod recovery using fastboot and then just boot into recovery and install whatever rom...
http://koush.tandtgaming.com/recoveries/recovery-clockwork-2.5.1.2-vision.img

dantheman_ said:
If you are still S-OFF, you can flash clockwork mod recovery using fastboot and then just boot into recovery and install whatever rom...
http://koush.tandtgaming.com/recoveries/recovery-clockwork-2.5.1.2-vision.img
Click to expand...
Click to collapse
i love you, no homo

just out of curiousity, how did u install that cm rom? if u used clockwork like it required, all u had to do after u messed up flashing bacon, was wipe, and restore, or reflash the rom again. why did u flash a stock recovery?
Sent from my T-Mobile G2 using XDA App

did a wipe, stuck at htc logo. didnt know i could just flash the cm file with clockwork... thought i had to use the clockwork rom manager when the phone is booted up. flash stock recovery, for some reason, i dont know. cried for an hour. called tmobile, had them send me a replacement. now on the phone telling them to cancel first android phone so im a noob, be kind

brick Nexus S

Hello. i am new to the android family
i have a nexus s GT-9020T
i have rooted my phone but without setting the clockworkmod reovery.
today i was playing with the rom manager and downloaded one of the rom from the list. after installation i was unable to start the phone only seeing the google logo with the unlock logo.
i went back into the recovery by typing flash recovery recovery.img etc.
run a restore and restart the phone but still not work
my nexus s is 2.3.4 by the way.
please assist

What "restore" did you run?
Go here: http://forum.xda-developers.com/showthread.php?t=1056062
And download the full rom:
Model: i9020T
Full Rom: GRJ22, KD1
That'll revert your Nexus S to the latest completely stock 2.3.4
Then you can flash recovery again and go back to clockwork mod and go flash another rom or whatever.
Remember when you're flashing a new rom you need to wipe data and cache and dalvik cache.

i run an restore from the backup that i made before installing the new rom using clockwork mod recovery, its part of the option when installing the rom using the rom manager * click box - backup * etc something like that

sheunghko said:
i run an restore from the backup that i made before installing the new rom using clockwork mod recovery, its part of the option when installing the rom using the rom manager * click box - backup * etc something like that
Click to expand...
Click to collapse
Next time don't use Rom Manager to make backups or flash roms. It's stupid and can get you issues like you're having.
Anyways, try wiping data and cache then restoring the backup, do it in Clockwork Recovery.
Let it boot, first boot always takes a while, 5-10 minutes. If you see the boot animation freeze, stop and restart, then yeah it's screwed up, otherwise, just let it is.
If still not working from your backup, do what I said in previous reply, just restore to stock 2.3.4 then re flash clockwork mod and start over with the rom you want to flash.

thank your nxt. i have found the real problem. it was not my backup problem or the rom that u provided. it was the version of my clockwork mod recovery. i was using an 2.x.x.x to restore the phone which is why it doesn't work. everything work fine now after i flashed with an 3.x.x.x and restore the phone. one question thou, where can i always find the newest clockwork mod recovery release ? thank you very much

sheunghko said:
thank your nxt. i have found the real problem. it was not my backup problem or the rom that u provided. it was the version of my clockwork mod recovery. i was using an 2.x.x.x to restore the phone which is why it doesn't work. everything work fine now after i flashed with an 3.x.x.x and restore the phone. one question thou, where can i always find the newest clockwork mod recovery release ? thank you very much
Click to expand...
Click to collapse
http://mirrorbrain.cyanogenmod.com/cm/recoveries/
Or just use ROM Manager to get the latest.
That's the only thing I use ROM Manager for... getting the latest Recovery.

thanks again nxt. if you don't mind really ...i have one more question. i know the phone intend to uninstall clockwork mod recovery once its restarted. i know there is command type into the cmd to avoid the phone uninstall the clockworkmod reovery and make it permanent in another word. I didn't run those command when i root my phone because i don't know if its good to make it permanent like.... hmmm like if there will be a 2.3.5 coming next month..just saying ok... with a permanent unofficial recovery will cause a problem?

sheunghko said:
thanks again nxt. if you don't mind really ...i have one more question. i know the phone intend to uninstall clockwork mod recovery once its restarted. i know there is command type into the cmd to avoid the phone uninstall the clockworkmod reovery and make it permanent in another word. I didn't run those command when i root my phone because i don't know if its good to make it permanent like.... hmmm like if there will be a 2.3.5 coming next month..just saying ok... with a permanent unofficial recovery will cause a problem?
Click to expand...
Click to collapse
Are you running custom ROM? If you are, it's already made to not revert back to stock recovery. If you leave it stock recovery you'll get notifications for firmware updates by Google, but remember that applying those to a rooted phone might screw things up too.

the blue one is stock recovery right?

sheunghko said:
the blue one is stock recovery right?
Click to expand...
Click to collapse
Don't remember. It should only have like 3-4 options.

thanks again nxt. no i am not running an custom rom. i mean not yet. i planed to try one from the rom manager download section then my phone couldn't start after installation and now i have restored my phone from my backup using the clockwork mod recovery 3.x.x.x.

(What if?)how do you recover from a boot loop on nexus4?

Hello everybody! I have a nexus 4 since a couple of months, and I had a Samsung galaxy s before. With that phone if you got stuck on a boot loop and couldn't access recovery, you used Odin to save you..what if it happens on nexus 4? Flash original image with a tool? Or there is some recovery file I can flash? Or what?
Thanks!
Sent from my Nexus 4 using xda app-developers app

It's highly unlikely that you won't be able to boot into the recovery anymore on a nexus device as the recovery is pretty much "flash once, forget forever".
Meaning, you normally don't mess with the recovery partition.
If you, for whatever reason, really can't access the recovery anymore, you can flash a new one through the bootloader using fastboot.
fastboot flash recovery recovery.img
Should be the command to do so. Just check the tutorials around here.

Nuu~ said:
It's highly unlikely that you won't be able to boot into the recovery anymore on a nexus device as the recovery is pretty much "flash once, forget forever".
Meaning, you normally don't mess with the recovery partition.
If you, for whatever reason, really can't access the recovery anymore, you can flash a new one through the bootloader using fastboot.
fastboot flash recovery recovery.img
Should be the command to do so. Just check the tutorials around here.
Click to expand...
Click to collapse
What he said, and also should be noted that if you do backups of your roms, if you ever upgraded the recovery (say TWRP) you may wish to re-do a backup after you upgrade with the recovery option checked (or don't use it at all) since I've run into a situation once where I backed up my original stock on 2.4.4.0, and when I restored it, it downgraded my 2.5.0.0 to that, didn't cause problems just some options went bye-bye until I reflashed the recovery from fastboot (and just made sure to make a flashable-zip of just that recovery just in case).
As long as you can get to the bootloader on an N4 you can do just about anything to bring your device back to life, even if it's something like erasing the userdata, then formating /data in the new recovery because *cough*me*cough* stupidly flashed a galaxy nexus recovery from goomanager.
PS: Holding down the power for 10 seconds or more is pretty much the universal kill switch, from there should be able to bring up bootloader just fine.

kbeezie said:
What he said, and also should be noted that if you do backups of your roms, if you ever upgraded the recovery (say TWRP) you may wish to re-do a backup after you upgrade with the recovery option checked (or don't use it at all) since I've run into a situation once where I backed up my original stock on 2.4.4.0, and when I restored it, it downgraded my 2.5.0.0 to that, didn't cause problems just some options went bye-bye until I reflashed the recovery from fastboot (and just made sure to make a flashable-zip of just that recovery just in case).
As long as you can get to the bootloader on an N4 you can do just about anything to bring your device back to life, even if it's something like erasing the userdata, then formating /data in the new recovery because *cough*me*cough* stupidly flashed a galaxy nexus recovery from goomanager.
PS: Holding down the power for 10 seconds or more is pretty much the universal kill switch, from there should be able to bring up bootloader just fine.
Click to expand...
Click to collapse
Try booting in safe mode https://support.google.com/nexus/4/answer/2852139?hl=nl. 3rd party apps will not boot in that mode.

gee2012 said:
Try booting in safe mode https://support.google.com/nexus/4/answer/2852139?hl=nl. 3rd party apps will not boot in that mode.
Click to expand...
Click to collapse
Not sure why you linked that or how it even pertained to me (especially since it's been long since resolved and was using as an example). Also those tips do nothing if you couldn't get past the boot splash animation to begin with.

kbeezie said:
Not sure why you linked that or how it even pertained to me (especially since it's been long since resolved and was using as an example). Also those tips do nothing if you couldn't get past the boot splash animation to begin with.
Click to expand...
Click to collapse
It got me out of a bootloop mate, so if you speak for yourself that`s oke but that doesn`t mean it couldn`t work for others

gee2012 said:
It got me out of a bootloop mate, so if you speak for yourself that`s oke but that doesn`t mean it couldn`t work for others
Click to expand...
Click to collapse
How exactly do you get out of a boot-loop, when you can't even get into the rom to bring up the Power dialog in the first place like that instruction says? (The instructions you posted only works if you're already in the rom, holding down the ok button before it reboots, and I suspect all that's doing is clearing the Dalvik-cache which you can do from recovery anyways).
Also my problem wouldn't have anything to do with that, because if you flash a galaxy nexus recovery onto an N4, and reboot, it won't let you in because it'll ask for a password to decrypt storage, an the recovery will do the same thing, and my post which you quoted didn't have anything to do with a bootloop, just simply that you can get out of just bout any situations with a Nexus 4.

These are the most common bootloop solutions http://droidviews.com/2012/how-to-recover-when-your-android-device-is-caught-in-bootloop/.

[Q] Problems with stock rooted rom when flashed from recovery.

Let me give you the timeline. A few days ago I rooted the device using the method outlined in this video. I verified my root status with Root Checker and my device was indeed successfully rooted. I installed BusyBox (basic) and TitaniumBackup Pro. Made a backup of my user apps+data to the external SD. I then downloaded Goomanager and used it to install the latest version of TWRP.
All of this was successful. I went into TWRP and created a NAND backup. I backed up: Boot, System, and Data. I did not back up EFS, Preload, Cache, or Recovery.
I performed a wipe and format of user data. Flashed to SlimBean, had some issues. Wiped. Flashed CM10.1. Again, some issues. I decided I'm going to wait a while for these roms to stabilize a bit before I try using any of them on a regular basis. I wiped and restored my original NAND backup of my stock rooted ROM. The restore appeared to go fine. I don't know if this will have anything to do with anything but I went ahead and ran a PRL and Profile update. The device was functioning okay until...
I noticed that the time was off. The lockscreen time was correct but the time in the upper right status bar was stuck at about an hour before. I decided I'd just try restarting the device to see if that fixed anything. Well when I did it wouldn't boot. I'd get stuck on the first Samsung Galaxy S4 logo screen. Took the battery out, waited, put it back in, restarted. Still... stuck on the logo screen. I tried booting into recovery (Vol. Up + Power). The black SGS4 logo would come up with a tiny blue notification in the upper left corner (Recovery Boot). Then the device would restart and get stuck at the SGS4 logo screen again.
Eventually I was able to get it to boot to TWRP (maybe I was just holding the power button too long?)
I wiped. It failed. I tried again. It worked. I recovered my CM10.1 setup and it's been working "okay" on CM10.1 ever since.
I want to get back to my stock rooted rom but I want to understand what happened first.

Anyone? Please?

Stu_Gots said:
Anyone? Please?
Click to expand...
Click to collapse
What version of TWRP were you on? If it was 2.5.0.3 then there's your culprit. That version of TWRP is known to have issues. You need to flash version 2.5.0.2 found here.......http://forum.xda-developers.com/showthread.php?t=2277480. Scroll down to install Alternate recovery and download the 2.5.0.2 .img file.
Once you've downloaded the file, go to your Goo Manager folder and delete the file there. Then paste the file you downloaded from the above link into that same folder. After that, open Goo Manager and go to Install Recovery Script. It should see the file you have in your folder and then download it from their server. Make SURE it says you are downloading 2.5.0.2. Once Goo does its thing, reboot into Recovery and make sure you're running the 2.5.0.2 version of TWRP. Now you can flash all you want because it will function properly. I would first download a stock rom and clear out any skeletons in the closet. Then go into TWRP and wipe EVERYTHING. This includes data, dalvik cache, cache, system and then factory reset as well 3 times each. MAKE SURE you don't delete the internal or external sd cards. Flash the stock rom, set it up how you wish, make a nand of that file( Include EFS and Preload because it can't hurt to be safe) and then flash whatever you like. You should be good to go.
---------- Post added at 01:20 PM ---------- Previous post was at 01:17 PM ----------
Stu_Gots said:
Anyone? Please?
Click to expand...
Click to collapse
Another question I have is what version of software/firmware are you on? Go to Settings/More/About Phone and check what your software and baseband versions are? If its MDC, then rooting via MotoChopper was a good method to use. If it says MDL, that could also be the reason why the phone was acting so quirky. There is a new method to rooting if you are on MDL and it's also found in Mudavo's thread found here...http://forum.xda-developers.com/showthread.php?t=2277480

For the record. I was using the phone stock rooted for a week or so without any problems. I hadn't had any issues until after restoring the backup I made in TWRP. When I wiped prior to installing SlimBean/CM10.1 I did the standard auto-wipe AND I wiped data
Oh yeah. To answer your questions.
TWRP Version: 2.5.0.2
Software/Baseband versions: L720VPUAMDL
Earlier today I just tried wiping (default TWRP 2.5.0.2). Then restoring the backup again. This was so I could get you the information on what software/baseband version I was on. When the restore completed I went to reboot. The phone stuck on the SGS4 logo screen. I then rebooted in recovery and wiped as before and then I wiped data. The phone was then able to boot into the stock rooted rom. I have so far noticed the times being out of sync from the lock screen and the status bar. I reset the phone again. Stuck at SGS4 logo again.
My trouble getting back into TWRP was my own fault. I was holding the buttons down too long. I can get back into TWRP no problem.
So. What are my options at this point? I would like to be on the latest stock everything... with root and stock wireless tether enabled. The way I was. If I can't restore my backup then I'm going to have to reflash the stock rom. I can't seem to find a comprehensive index of information. Every time I think I've got something figured out I stumble on new bits of information.

Stu_Gots said:
For the record. I was using the phone stock rooted for a week or so without any problems. I hadn't had any issues until after restoring the backup I made in TWRP. When I wiped prior to installing SlimBean/CM10.1 I did the standard auto-wipe AND I wiped data
Oh yeah. To answer your questions.
TWRP Version: 2.5.0.2
Software/Baseband versions: L720VPUAMDL
Earlier today I just tried wiping (default TWRP 2.5.0.2). Then restoring the backup again. This was so I could get you the information on what software/baseband version I was on. When the restore completed I went to reboot. The phone stuck on the SGS4 logo screen. I then rebooted in recovery and wiped as before and then I wiped data. The phone was then able to boot into the stock rooted rom. I have so far noticed the times being out of sync from the lock screen and the status bar. I reset the phone again. Stuck at SGS4 logo again.
My trouble getting back into TWRP was my own fault. I was holding the buttons down too long. I can get back into TWRP no problem.
So. What are my options at this point? I would like to be on the latest stock everything... with root and stock wireless tether enabled. The way I was. If I can't restore my backup then I'm going to have to reflash the stock rom. I can't seem to find a comprehensive index of information. Every time I think I've got something figured out I stumble on new bits of information.
Click to expand...
Click to collapse
Honestly, at this point, you need to unroot and reroot again using the method in Mudavo's post. You used the wrong method to root with motochopper. Motochopper was only for the MDC version. That could be why you are having the issues that you are. That's all I can suggest at this point. Start with a clean slate and try it again. Trust me you aren't the only one to do this. I've done it a few times myself. It sucks but at least you know you did everything right. You're going to have to flash a stock MDC rom that came shipped with the phone via Odin. Then take the OTA to update your phone to MDL and then just follow Mudavo's post to root the proper way when you're on the MDL version.

What about the TWRP recovery I have installed? Am I going to have to deal with that in some way?
What are the advantages of Odin over TWRP? I'm not trying to question your judgment btw. I'm legit curious because I've only ever used TWRP to
Flash roms.
Sorry for all the dumb questions.
Btw . While I was waiting for your reply I tried trouble shooting a bit myself. To see if I could fix my own problem. I found a thread with MDL stock rooted and a bunch of firmware and kernel files. I flashed to it in TWRP and it's working reasonably well so far. I'm still dtf for other methods if mine is somehow flawed.

My method didn't work. When I restarted from TWRP (after no other issues) the phone for stuck.
The phone was restarted several times and booted fine. It wasn't until I restarted into TWRP then and then back into normal boot that I had issues
this time. So I'm going to do what you suggested. I just have a couple questions.
If my rom/recovery is corrupted how do I fix my problem. I would need a working rom AND recovery to flash stock rom. I'm not sure where to start since everything is all messed up.
Thank you so much for your help. You're the best!

You should do a Full Odin restore to Stock and start from scratch if you continue to have issues.
http://forum.xda-developers.com/showthread.php?t=2270065
You can also try this thread to ensure a full wipe before flash
http://forum.xda-developers.com/showthread.php?t=2277261

gharlane00 said:
You should do a Full Odin restore to Stock and start from scratch if you continue to have issues.
http://forum.xda-developers.com/showthread.php?t=2270065
You can also try this thread to ensure a full wipe before flash
http://forum.xda-developers.com/showthread.php?t=2277261
Click to expand...
Click to collapse
Installed Mobile ODIN Pro from the play store for $5... I hope that's the right Odin!

Stu_Gots said:
Installed Mobile ODIN Pro from the play store for $5... I hope that's the right Odin!
Click to expand...
Click to collapse
download Odin 1.85 or 3.07 on your PC don't use mobile version for something like this
Sent from my SPH-L720 using xda premium

Do I need to flash the stock kernal too? Will this eliminate my TWRP recovery installation as well?

If you odin back to stock it also has the kernel and stock recovery this will start you all over. Also of it doesnt boot past galaxy s4 screen then boot into recovery and wipe data after you odin back.
Sent from my SPH-L720 using xda premium

devoureddreams said:
If you odin back to stock it also has the kernel and stock recovery this will start you all over. Also of it doesnt boot past galaxy s4 screen then boot into recovery and wipe data after you odin back.
Sent from my SPH-L720 using xda premium
Click to expand...
Click to collapse
Alright... so another problem. I need the latest Samsung USB driver right? Unfortunately...
1.5.25.0 as linked to in this thread cannot be downloaded because uploaded.com or whatever says I've exceeded my allowance. Trouble is... I haven't downloaded anything from them ever. I have this problem all the time because of my ISP (Satellite Internet).
Is there a rehost? Do these drivers not install themselves automatically when the device is plugged into the PC?

http://downloadcenter.samsung.com/c...ng_USB_Driver_for_Mobile_Phones_v1.5.14.0.exe
Sent from my SPH-L720 using xda premium

I'm so freaking frustrated by this whole process. It looks like by all accounts there are a dozen different ways to do everything and I just know i'm going to mess it up.
I'm following the directions in this video.
http://www.youtube.com/watch?v=ZD5CHlrPQJQ&feature=youtu.be
When I extract the file I downloaded I get an MD5 file not an ODIN file.

Stu_Gots said:
I'm so freaking frustrated by this whole process. It looks like by all accounts there are a dozen different ways to do everything and I just know i'm going to mess it up.
I'm following the directions in this video.
http://www.youtube.com/watch?v=ZD5CHlrPQJQ&feature=youtu.be
When I extract the file I downloaded I get an MD5 file not an ODIN file.
Click to expand...
Click to collapse
Follow this tutorial here
http://www.sxtpdevelopers.com/showthread.php?p=2599
Sent from my SPH-L720 using xda premium

Alright guys. I got it done a while back. Phone is back to normal stock.
Perusing the internet I found this video.
http://www.youtube.com/watch?v=s_hXUJ-u-cw
As it happens I linked to the wrong video in my OP. The method in that video is exactly what I did to root in the first place. The proper way. I installed TWRP from GooManager.
So if I rooted correctly and I installed TWRP correctly what do you suppose caused my problem? I want to root and install custom recovery again!

If I root using the CF-Auto-Root method will I then be able to install custom recovery in goomanager or does custom recovery need to be installed in some other special way?

Stu_Gots said:
If I root using the CF-Auto-Root method will I then be able to install custom recovery in goomanager or does custom recovery need to be installed in some other special way?
Click to expand...
Click to collapse
thats all there is to it.

Can't install stockmod stuck at LG bootscreen HELP!

As the title probably hints i cant seem to install stock mod i mean it says it is successful in TWRP but when i reboot it just stay on LG bootscreen
I have installed this rom before but then went to cyanogen which i didn't like as much as stock but can't seem to go back
currently running stock
Edited:
Managed to get back to stock via this method: http://forum.xda-developers.com/showthread.php?t=2432476
Just can't seem to install StockMOD :/

callum1986 said:
As the title probably hints i cant seem to install stock mod i mean it says it is successful in TWRP but when i reboot it just stay on LG bootscreen
I have installed this rom before but then went to cyanogen which i didn't like as much as stock but can't seem to go back
currently running stock
Edited:
Managed to get back to stock via this method: http://forum.xda-developers.com/showthread.php?t=2432476
Just can't seem to install StockMOD :/
Click to expand...
Click to collapse
Are you formatting? Try to format /system also then flash it. if all else fails go back the the stock rom. good luck

thenewak said:
Are you formatting? Try to format /system also then flash it. if all else fails go back the the stock rom. good luck
Click to expand...
Click to collapse
Thanks for reply yes i formatted and even reverted back to stock following the above link i even wiped phone where it deletes everything included sdcard but no matter what i try StockMOD rom wont boot when flashing
p.s. its the D802 i have
Well i assume i formatted as in wipe menu on TWRP i selected everything other than internal storage

callum1986 said:
Thanks for reply yes i formatted and even reverted back to stock following the above link i even wiped phone where it deletes everything included sdcard but no matter what i try StockMOD rom wont boot when flashing
p.s. its the D802 i have
Click to expand...
Click to collapse
Hmm that's weird, have you tried re flashing your recovery maybe something is broken there? have you tried other roms? If using TWRP try to update it or change to CWM or vice versa

Yea I updated to 2.6.3.4 which as of my knowledge is the latest
Sorry for my noobness :/ it is really bugging me as I think it has something to do with having cyanogen installed before but then again after pursuing the flash tool and restoring back to stock I can't think what is wrong
Sent from my LG-D802 using xda app-developers app

Double Flash seemed to fix it
I flashed the ROM after returning to stock again and before flashing it wiped all partitions and it still stuck on boot so i went straight back into recovery and flash again this time without wiping anything as i was only writing over the StockMOD install and it seems to work
So the solution for me seemed to me to flash it twice wiping before the first and after it fails to boot just flash it again without wiping.
I now have it up and running and I'm very happy with it
Thanks for those who tried to help me much appreciated