Was using BobZhome ROM CM9 Android 4.0 ICS for VM670. Had some bugs and flashed to CM7 (BZROM). Backed up Rom, Cleared cache, wiped DAV, etc. Then flashed new BZCM7ROM.
Now, gets stuck in boot loop, when rebooted in recovery I get (CMR v5.0.2.7 at top; then) the standard options list... have to use camera button to nav down list, vol up also nav's down the list, vol down nav's up list, seems damned backward?? No buttons seem to be able to activate (select) from the list. WTF
Even tried emergency mode and several attempts on the LGSWupdate, just kept saying my softwaer is current, no Update available but phone would not get off boot screen DANGIT!
ANYWHO,,,, just need some pointers, obviously a noob, HAPPY THANKSGIVING
As you should already be aware, cross/double posting is not allowed. Please familiarize yourself with forum rules and do not post the same thing across multiple threads or sections. Thread closed.
Related
I have an Epic 4g Touch that is flashed to Boost Mobile. I think I bricked it by flashing the newest ICS update by Shabbypenguin, then trying to switch back to the other ROM I was on. I noticed that I didn't have cwm recovery anymore, so I flashed a cwm touch recovery to get back on the previous ROM I was on. After wiping data/factory reset, wiping delvik cache, and wiping cache, I restored the recovery that I had saved in cwm previously, then I tapped on the "fix permissions" button that was available because I didn't know how to get back to the main screen on the recovery mode where it says reboot system now. After that I tapped on reboot system now, and it hasn't shown anything on the screen since. It may have been because I accidentally fixed permissions after wiping and flashing the previous ROM that I bricked it. However, it does have the blue notification light on, and if I hold the power button, it will flash once, then stay on. I'm not sure if this means anything as far as it being bricked or not bricked. My question is that if I restore it to factory settings using the unbrick method, will it erase my flash to Boost Mobile?
There is a ton of threads on this very topic! I hate to say it but you are bricked. Always read first before messing around with your phone.
Here is a thread that will give you some suggestions.
http://forum.xda-developers.com/showthread.php?t=1524442
nickman102 said:
I have an Epic 4g Touch that is flashed to Boost Mobile. I think I bricked it by flashing the newest ICS update by Shabbypenguin, then trying to switch back to the other ROM I was on. I noticed that I didn't have cwm recovery anymore, so I flashed a cwm touch recovery to get back on the previous ROM I was on. After wiping data/factory reset, wiping delvik cache, and wiping cache, I restored the recovery that I had saved in cwm previously, then I tapped on the "fix permissions" button that was available because I didn't know how to get back to the main screen on the recovery mode where it says reboot system now. After that I tapped on reboot system now, and it hasn't shown anything on the screen since. It may have been because I accidentally fixed permissions after wiping and flashing the previous ROM that I bricked it. However, it does have the blue notification light on, and if I hold the power button, it will flash once, then stay on. I'm not sure if this means anything as far as it being bricked or not bricked. My question is that if I restore it to factory settings using the unbrick method, will it erase my flash to Boost Mobile?
Click to expand...
Click to collapse
You my friend just received the blue light of death.. aka hardbricked. I had the same thing trying to flash cm9. You can do one of three things: use a jigg to try and force it into download mode (although a lot of people have been saying it doesn't work in this case). Ship it to mobiletechvideos and pay 60 bucks to have them unbrick it, or take it to sprint and hopefully get a new phone.. I took mine to sprint and they thought my screen went out, so I got new one..(best bet)
SMH!!
So apparently noobs are too lazy to read before they destroy anything. I made a full thread on "HOW NOT TO BRICK YOUR DEVICE" should have read it, too late now. In the future, if you purchase another e4gt, stay away from cwm touch, and rom manager
Heres my thread
http://forum.xda-developers.com/showthread.php?t=1525495
nickman102 said:
I have an Epic 4g Touch that is flashed to Boost Mobile. I think I bricked it by flashing the newest ICS update by Shabbypenguin, then trying to switch back to the other ROM I was on. I noticed that I didn't have cwm recovery anymore, so I flashed a cwm touch recovery to get back on the previous ROM I was on. After wiping data/factory reset, wiping delvik cache, and wiping cache, I restored the recovery that I had saved in cwm previously, then I tapped on the "fix permissions" button that was available because I didn't know how to get back to the main screen on the recovery mode where it says reboot system now. After that I tapped on reboot system now, and it hasn't shown anything on the screen since. It may have been because I accidentally fixed permissions after wiping and flashing the previous ROM that I bricked it. However, it does have the blue notification light on, and if I hold the power button, it will flash once, then stay on. I'm not sure if this means anything as far as it being bricked or not bricked. My question is that if I restore it to factory settings using the unbrick method, will it erase my flash to Boost Mobile?
Click to expand...
Click to collapse
Not to harp on you like everyone else, but dude, general and q/a section had a dozen threads with people that bricked their phones using touch recovery. Others have posted in bold letters- DO NOT USE TOUCH RECOVERY. lol. [email protected]!
EDIT- This could be a troll. LOL. I find it hard to believe that someone would use the touch recovery to brick their phone after so many others did it.
stargaterules said:
Not to harp on you like everyone else, but dude, general and q/a section had a dozen threads with people that bricked their phones using touch recovery. Others have posted in bold letters- DO NOT USE TOUCH RECOVERY. lol. [email protected]!
EDIT- This could be a troll. LOL. I find it hard to believe that someone would use the touch recovery to brick their phone after so many others did it.
Click to expand...
Click to collapse
No I truly believe he did this there are so many idiots who can't be bothered to take 5 minutes to read ....they know what they are doing .....300 may get you another off Craigslist have fun with your new brick
Sent from my SPH-D710 using XDA
I'm sorry I accidently had posted this question in the development forum. Mods please delete that thread.
Guys I need your help. I had 4.0.4 and then I unlocked and rooted my phone to get Jelly Bean (installed V1) following the walkthrough (the day it was released). Tonight I wanted to get to V3 so I made my backups (note not nandroid, just on Titanium & Go Backup) and tried to boot into Recovery Mode. Did the whole vol & power thing and got to the Fastboot mode. Selected Recovery Mode from the menu and was hoping to get to the screen where I can wipe and do the nandroid backup and all. But it shows the Google lock screen (unlocked icon) and then shows the android guy on its back, chest open and a red triangle. I remember having this a while ago when I was unlocking the phone and flashing JB on it but it was no problem. This time it just stays on this red triangle for a while and then the phone reboots (no menu for wipe, backup etc) but the kicker is that it stays stuck on the nexus jelly bean (the "x") animation forever and does not move from there. I've tried to wait it out for over 15 minutes and nothing. I can't even go back to stock on this as I'm using Wugs toolkit and the phone is not recognized in the list devices (I have Win8). I need to get this working as soon as possible. Any help is greatly appreciated.
Did you try ODIN back? I had this problem, but instead of the red triangle, I had the EXCLAMATION mark between a PC and phone icon. Somewhere along the line I messed up with the files and soft-bricked my phone. ODIN would be your last bet, but for me, nothing worked.
Got a replacement next day (covered by warranty)... Good luck, dude...
I met the same problem when I flash JB (JRN84D ROM) from 4.0.4. When I saw "red triangle", I just kept pressing power and press volume up and then it brought me to recovery page. However, be careful, after I did data wipe, I lost all of kernels, rom, cwm recovery...in my phone. it was my first time to flash a phone so I must have done something wrong so now I have 4.1 but re-locked and don't know how to root it again and get CWM back. But at least, you can try power and volume up when you see "red triangle" to enter recovery mode.
sueshake,
thanks for that handy tip with the power and vol up combo. At least now I have some access to phone...thanks
will keep u updated on the progress
You are welcome. Be careful if you want to do superwipe. I guess I almost bricked my phone by doing that. Fortunately, I did flash 4.1 stock rom successfully before wiping data, though I am not sure how I made it from 4.0.4.
I'm thinking to use this thread for n00b questions and bug reports on A77R's CM10.1 builds as I am not allowed to post in the dev forums (under 10 comments), probably for good reason.
My observations or maybe silly n00b problems, having come off CAMP ROM and having done 4 wipes (data/factory reset, cache, dalvik, and battery stats)
1. Having installed cm-10.1-20130119-UNOFFICIAL-i927 then gapps-jb-20121212-signed, phone started vibrating all through boot but stopped by pressing the power key after booting. Alt key didn't work and on screen keyboard wouldn't come up to enter my wifi password, turned it off
2. Rebooted, performed 4 wipes, installed cm-10.1-20130119-UNOFFICIAL-i927 then gapps-jb-20121212-signed then Android-4.2.1-Keyboard-Lights-Fix. Phone started vibrating about halfway through boot, would not stop even pressing the power key, turned it off
Thanks
So I just done a clean install of the lastest CM10.1. I was restoring my apps/data with Titanium (I made sure to unclick all the red ones) but now it gets stuck in the CM bootscreen then goes into a loop. Fine I thought, I'll just restore and then start all over. However I can't get into the bootloader at all. It let's me do Power+Volume Down to hard reset the phone (all the capacitive lights flash) but when I continue holding it the bootloader won't open, it just goes back into the loop. What the hell have I managed to do here?!
Edit: Completely disregard, apparently you user Power+VolDown to reset and then release power to get into bootloader. Also shoutout to XDA's terrible thread recommendation service, didn't find a helpful thread when posting this, but a google search (that admittedly I didn't think of till I posted) found a thread straight away.
You must not release any button of those 2 before you are in the bootloader ! Hold them both forever until you see the bootloader
Q&A for [ROM][4.4.4][Official] CyanogenMod 11.0
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.
Before posting, please use the forum search and read through the discussion thread for [ROM][4.4.4][Official] CyanogenMod 11.0. If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.
Thanks for understanding and for helping to keep XDA neat and tidy!
Please help!
Please Help-
I have a HTC ONE M7 from Verizon that is rooted and running CM11 snapshot M10. I recently started using the phone after a couple of months. When I started using the phone it was still on CM10.2, working fine. I upgraded to CM11 and had an issue with google play services failing, so I wiped the device and did a fresh install of CM11. The install worked fine and but I had none of my previous apps so I began the process of setting my phone back up and downloading all of my apps. Certain apps would not install and come up with an error message. ( Unknown error code during application install "-24". So I did some research and found out how to get rid of the error code but it only worked for certain apps, others still came up with the same message. I had wanted to clean out my phones memory anyways because it was getting full so I decided to do a full factory data wipe/reset from the phones settings menu, not from recovery. So I proceeded to wipe the phone and it rebooted and showed the android logo with the crazy blue lines in his stomach and the blue loading bar below. I let the phone sit for a while and nothing was happening. It stayed on that screen for a couple of hours without rebooting or showing any signs that it was wiping the device. So I decided to to hard reboot the device with the power and volume down button ( probably a bad idea I know) and reboot the device. Now when I power on the device the CM logo shows up but it just keeps spinning, never boots into the device. If I try to boot into recovery, the bootloader shows up fine, and then I select recovery and it goes back to the same screen with the android logo and cray blue lines in his stomach and loading bar below. I have let the device sit for hours both trying to boot up or boot into recovery and it just either stays on the CM loading screen or the android logo with blue loading bar. I now do not know what to do and am a little worried. I am not new to rooting and roming android devices but I am also not a pro. Please help me recover my device to any rom.
Thank you for your help and sorry for the long post.
manklee said:
Please Help-
I have a HTC ONE M7 from Verizon that is rooted and running CM11 snapshot M10. I recently started using the phone after a couple of months. When I started using the phone it was still on CM10.2, working fine. I upgraded to CM11 and had an issue with google play services failing, so I wiped the device and did a fresh install of CM11. The install worked fine and but I had none of my previous apps so I began the process of setting my phone back up and downloading all of my apps. Certain apps would not install and come up with an error message. ( Unknown error code during application install "-24". So I did some research and found out how to get rid of the error code but it only worked for certain apps, others still came up with the same message. I had wanted to clean out my phones memory anyways because it was getting full so I decided to do a full factory data wipe/reset from the phones settings menu, not from recovery. So I proceeded to wipe the phone and it rebooted and showed the android logo with the crazy blue lines in his stomach and the blue loading bar below. I let the phone sit for a while and nothing was happening. It stayed on that screen for a couple of hours without rebooting or showing any signs that it was wiping the device. So I decided to to hard reboot the device with the power and volume down button ( probably a bad idea I know) and reboot the device. Now when I power on the device the CM logo shows up but it just keeps spinning, never boots into the device. If I try to boot into recovery, the bootloader shows up fine, and then I select recovery and it goes back to the same screen with the android logo and cray blue lines in his stomach and loading bar below. I have let the device sit for hours both trying to boot up or boot into recovery and it just either stays on the CM loading screen or the android logo with blue loading bar. I now do not know what to do and am a little worried. I am not new to rooting and roming android devices but I am also not a pro. Please help me recover my device to any rom.
Thank you for your help and sorry for the long post.
Click to expand...
Click to collapse
Are you s-off? You'll find it in your HBOOT
Help
I've upgraded my phone yesterday by CM 11.0 but i cant make a phone call or even draft a massage. It said Molbie network not available
hectorvo said:
I've upgraded my phone yesterday by CM 11.0 but i cant make a phone call or even draft a massage. It said Molbie network not available
Click to expand...
Click to collapse
You probably need to update your firmware to use the newer cm. Make sure you flash the latest with no boot.img.