I have a T-mobile G2 android phone. I recently rooted the phone. Installed different roms, and attempted to install a different rom. Currently have ClockworkMod Recovery v2.5.1.3 installed. After restarting phone, if I don't load the ClockworkMod, the phone will freeze at the "HTC" screen. I can get into the Bootloader or into the ClockworkMod, but cannot get beyond that. What's the easiest thing to do in this situation?
Wipe data and cache and reflash either your ROM, or a Nand backup. That happened to me trying to ROM my Nook Color's emmc. If wiping data and cache doesn't help, you'll need to format data, cache, boot, and system and reflash. (Hopefully you've backed up)
Note: It's most likely your boot that's a little wonky, not CWM. IMHO CWM is one of the best things to ever happen to us Droid geeks
Ok honestly, Clockwork doesn't work on my Dream 32a. It doesn't boot up into the recovery. It's not compatible with some phones. Hopefully you did a nand backup..
I didn't do NAND backup. Is there an alternative.
Reflash whatever ROM you want, but format the 4 listed above. It's your boot that's messed up, so overwriting it with another one will confuse it... My nook boot-looped for about two weeks straight when I first tried installing to it's internal memory. I just stuck to it and read the forums over and over and never lost hope or gave up.
Sent from my ADR6300 using XDA Premium App
Noob A la VISTA!! Long story SHORT HTC Sensation bought downloaded an application went to erase it thru a File Manager and def deleted a wrong folder cause after that HTC started rebooting non stop. Rooted the phone installed CWR thru revolutionary CM7 thinking it was a software problem booted the phone and when on FASTBOOT the phone starts scanning the sdk and reads:
SD loading
-PG58diag.zip
-PG58diag.nbh
-PG58IMG.zip
-.nbh
-.tar
-.aec
-.enc
and No image for each one of it.... is this the cause of the HTC keeps rebooting btw the screen reads:
Revolution
Pyramid PVT ShipS-off RL
HBoot- 1.17.1111
Radio- 10.14.9035.01_m
eMMC boot
so what should I do to fix therebooting issue and the no image file etc?? thanks for any help in advance!!!!
Just a guess but you could try removing the microsd card from the phone and rebooting.
removed the card... rebooted... htc went into custom ROM... but now freezes up constantly and reboots... any way to fix this or should i start from the beginnign all over again from root??
easiest thing to do would be to reinstall the rom. most roms don't wipe user data, so go into fastboot, choose recovery and re-install the rom from the sd card and wipe cache and dalvik cache.
that's really all you can do at this point. even if it does erase your phone data (not sd card data like photos, videos, etc), its better than not having a working phone.
You could try using one of the Super Wipe ROMs, and then reinstall the custom ROM that you want to use. Also, make sure that you've applied one of the 3.12 firmware images if you're trying to use one of the ICS custom ROMS
super wipe roms? i waas trying the cyanogen mode 7 for htc sensation... have clockwork recovery btw if the phone freezes up on CWR what typ of issue could it be?...
easiest thing to do would be to reinstall the rom. most roms don't wipe user data, so go into fastboot, choose recovery and re-install the rom from the sd card and wipe cache and dalvik cache.
that's really all you can do at this point. even if it does erase your phone data (not sd card data like photos, videos, etc), its better than not having a working phone.
went with your suggestion wiped cache, dalvik, installed CM7 Rom... it still freezes up and reboots... thanks fot he help and suggestions
btw when wiping the cache n formatting it reads E: format_volume make_extf4fs failed on /dev/block/mmcblklp2
where can i find the firmware and rom's?
This just started yesterday and i cant stop it. My phone reboots and says that memory is nearly full, then goes into a bootloop. I cant stop it long enough to back up texts, phone contacts and call log which is REALLY important; is there a way to back that up through recovery?
i'm really desperate here!
Edit: I can get the phone working through a format, but i need to be able to get contacts and sms backed up
Alternitavely, is there a way to run a clockword mod backup on an android emulator on my comp, so i can back up my important stuff?
what you should try doing is putting your sd card directly into your computer and delete stuff you don't need to get back so memory and then once you do that out it back into your phone
i cleared up the memory, internal and external. the stupid ROM is still broken
if its just the rom go to a different one and redownload mikrom later to make sure nothing happened in the initial download
If you haven't already, try removing some apps through adb, then reflash the ROM only wiping dalvik and cache. You shouldn't lose any of your text, call logs or contacts if you don't wipe data.
Sent from my PG06100 using Tapatalk
From The Hacker Manifesto:
I made a discovery today. I found a computer. Wait a second, this is cool. It does what I want it to. If it makes a mistake, it's because I screwed it up. Not because it doesn't like me... Or feels threatened by me.. Or thinks I'm a smart ass.. Or doesn't like teaching and shouldn't be here...
Click to expand...
Click to collapse
I love it sooooo the rom isnt stupid, the team of developers supporting it are amazing and you should setup adb and get a logcat, also you should nandroid before you flash so in case it goes wrong you can flash back, like insurance but you actually get something from this without paying..
if you did nandroid boot into bootloader and select recovery (hold volume down and power on use volume button to highlight recovery and power button to select)
I'm not sure if mikrom wipes or not but there's always that advanced restore option in cwm recovery flash rom, restore data and sd-ext if you have a ext partition with important data on it.
crump84 said:
If you haven't already, try removing some apps through adb, then reflash the ROM only wiping dalvik and cache. You shouldn't lose any of your text, call logs or contacts if you don't wipe data.
Sent from my PG06100 using Tapatalk
Click to expand...
Click to collapse
I managed to get some apps removed, its no longer giving me the memory-full error, but its still bootlooping a minute or so after loading. going to try the cache and davlik wipes, then a another install....
JKILO said:
From The Hacker Manifesto:
Click to expand...
Click to collapse
thanks I always do a nandroid backup before doing a format; doesnt help. I can load the clean rom just fine, but when i restore, it goes into bootloop again....
sparksco said:
I'm not sure if mikrom wipes or not but there's always that advanced restore option in cwm recovery flash rom, restore data and sd-ext if you have a ext partition with important data on it.
Click to expand...
Click to collapse
ok, ill try this.
Also, how do i set up an sd-ext to automatically backup texts and call history etc to it?
crump84 said:
If you haven't already, try removing some apps through adb, then reflash the ROM only wiping dalvik and cache. You shouldn't lose any of your text, call logs or contacts if you don't wipe data.
Sent from my PG06100 using Tapatalk
Click to expand...
Click to collapse
did not work - goes back to bootloop. how do i install ADB?
Jedman67 said:
did not work - goes back to bootloop. how do i install ADB?
Click to expand...
Click to collapse
http://developer.android.com/sdk/index.html
Beginner's Guide to Installing the SDK and Getting Started with ADB
If nothing else, like Jkilo said, provide a logcat and maybe someone could take a look.
Did you ever get this fixed?
The usual way of fixing this is formatting /system, wiping dalvik, wiping cache, and reflashing the rom.
VICODAN said:
Did you ever get this fixed?
The usual way of fixing this is formatting /system, wiping dalvik, wiping cache, and reflashing the rom.
Click to expand...
Click to collapse
no. what i did was a backup, complete factory reset, wipe, dalvik wipe, etc - several times each, including a full on sd-card format, which took me hours to reload everything back on - and then reflashed MikShift. It worked fine for about a day, but then it started to go into bootloops again, so i again did a backup, full reset and all wipes, and restored data only to the new flash of mikshift. Once again its bootlooping.
LOG: ive been off the forums for several months, how do i get this log?
IMAGE: When i go into bootloader and enter recovery, it shows me a message in green text
"PG06diag.zip
No image!
PG06diag.nbh
No image or wrong image!
PG06img.zip
No image!
PG06img.nbh
No image or wrong image!"
At this point, im ready to RUU back to factory unrooted, so i can take it back to sprint and get it replaced.
I should not need to reflash the ROM every single day.
Jedman67 said:
no. what i did was a backup, complete factory reset, wipe, dalvik wipe, etc - several times each, including a full on sd-card format, which took me hours to reload everything back on - and then reflashed MikShift. It worked fine for about a day, but then it started to go into bootloops again, so i again did a backup, full reset and all wipes, and restored data only to the new flash of mikshift. Once again its bootlooping.
LOG: ive been off the forums for several months, how do i get this log?
IMAGE: When i go into bootloader and enter recovery, it shows me a message in green text
"PG06diag.zip
No image!
PG06diag.nbh
No image or wrong image!
PG06img.zip
No image!
PG06img.nbh
No image or wrong image!"
At this point, im ready to RUU back to factory unrooted, so i can take it back to sprint and get it replaced.
I should not need to reflash the ROM every single day.
Click to expand...
Click to collapse
OK
0) Run a backup with titanium backup.
1) First of all go to clockwork -> mounts storage -> FORMAT /SYSTEM.
2) Wipe /cache, wipe dalvik, wipe/data, factory reset, repartition sd card.
3) Redownload the rom or try a proven ROM like UKE or CM7-255. If AOSP MAKE SURE TO FLASH GAPPS.
NO NEED TO RUU.
4) DO NOT RESTORE YOUR BACK UP. See how stable the phone runs.
5) If the phone is still unstable try a different battery.
6) Do not flash a custom kernel.
i formatted my backup SD card, and copied the essential data to it, and i have it running in the phone now. it seems to be running fine so far, i suspect the other SD may have gotten corrupt or physically damaged
Vic: every single time this has happened, i first went to clear the data and dalvik caches and ran a factory reset, all through the CWM recovery interface. Then when i reinstall mikshift, i restore the data using advanced restore, wait 24-48 hours, bootloops start all over again.
after two days of running on the new sd card, i start getting bootloops again. it must be a problem with the phone or the OS, but at this point i dont care anymore.
Is there a guide to RUU back to stock unroot? this phone is going back to sprint by weeks end, period.
thanks for the help folks.
Jedman67 said:
Vic: every single time this has happened, i first went to clear the data and dalvik caches and ran a factory reset, all through the CWM recovery interface. Then when i reinstall mikshift, i restore the data using advanced restore, wait 24-48 hours, bootloops start all over again.
after two days of running on the new sd card, i start getting bootloops again. it must be a problem with the phone or the OS, but at this point i dont care anymore.
Is there a guide to RUU back to stock unroot? this phone is going back to sprint by weeks end, period.
thanks for the help folks.
Click to expand...
Click to collapse
Here's the 2.2 RUU zip http://forum.xda-developers.com/showthread.php?t=971550 Just put it on the root of sd, boot in hboot and let it do its thing.
Or you can run the RUU exe, just download and run from your pc. It's pretty self explanatory http://forum.xda-developers.com/showthread.php?t=1335068
Jedman67 said:
Vic: every single time this has happened, i first went to clear the data and dalvik caches and ran a factory reset, all through the CWM recovery interface. Then when i reinstall mikshift, i restore the data using advanced restore, wait 24-48 hours, bootloops start all over again.
after two days of running on the new sd card, i start getting bootloops again. it must be a problem with the phone or the OS, but at this point i dont care anymore.
Is there a guide to RUU back to stock unroot? this phone is going back to sprint by weeks end, period.
thanks for the help folks.
Click to expand...
Click to collapse
The problem is you didn't format /system.
Redownload the Rom. Then follow THIS GUIDE when you flash.
VICODAN said:
The problem is you didn't format /system.
Click to expand...
Click to collapse
Exactly 10 char
---------- Post added at 12:34 AM ---------- Previous post was at 12:31 AM ----------
prboy1969 said:
Redownload the Rom. Then follow THIS GUIDE when you flash.
Click to expand...
Click to collapse
Yeah that guide is great for flashing sense roms since "most" sense roms don't format/wipe the system partition correctly. Aosp roms you just do a data facotry wipe and everything installs just fine
I am having some serious issues with my phone today. What exactly is the point of formatting system, data, and cache after you wipe? What is the advantage and what happens if you just wipe and not format? I have never had issues making backups and restoring them until I started having to format before flashing these new JB roms. I have noticed that any backup I make (even ones that I have successfully restored without issue numerous times) completely stop working after I format my phone. Phone has bricked three times today.
This morning I had to bust out ODIN again and flash the Root66 (stock root) to fix the phone. Annoying, but no big deal. After I'm done I made a backup of the stock root. No issues. Then I go into recovery and factory wipe, wipe cache, and wipe dalvik. Did that twice. Then formatted system, data, and cache twice too. Flash the TasteOfBeans rom...installs no problem. Working great. Spent about two hours setting my phone up the way I used to have it. Boot into recovery and make a backup of this rom since I have set it up. About an hour goes by and I need to use my GPS so I boot into recovery and attempt to restore the stock root backup I made just this afternoon and it fails. Why the hell is it failing? Then I go to reboot system so I can at least get back into the JB rom and it just get stuck on the samsung boot logo (my boot loader is unlocked).
I had these exact same order of events occur with JellyWiz last night. I'm pretty over the whole format system, data, cache after wiping because this is the only new thing I have been doing and its cause me to bust out ODIN about three times in two days and all my backups are failing.
VERY frustrating...
To make it even worse after my most recent run in of failed restores and stuck on boot, I just ran odin again flashing the same Root 66 that I have been using to solve my issues all day and now its stuck in the Verizon 4G LTE boot.
So, even after using ODIN the phone is stuck in the Verizon 4G LTE bootloop. I flashed the Stock Root 66.
After I gave up on that, I decided to completely unroot the phone and start from scratch so I flashed the stock unrooted zip in ODIN. Same result...cant get past the Verizon boot screen. What is happening? Is my phone completely screwed or is it fixable?
Alright, perhaps you should try odin flashing the phone back to complete stock. No Root66, just factory firmware.
yosterwp said:
Alright, perhaps you should try odin flashing the phone back to complete stock. No Root66, just factory firmware.
Click to expand...
Click to collapse
1+
Odin the stock Verizon ROM.
During first reboot after Odin, sometimes the phone will hang. Pull out the battery. Count to 10. Put the battery back and hopefully the phone should boot.
....just double check all the proper boxes are checked and unchecked in Odin. PDA only.....
Sent from a SYNERGIZED GalaxySIII
Hi All,
I have the Telstra HTC One XL, and have just recently attempted to install CM10 ROM - however have run into some problems that I would appreciate some advice to rectify. I had recently updated to Jelly Bean OTA.
I followed the guide on these forums - http://forum.xda-developers.com/showthread.php?t=1859478
I Successfully unlocked bootloader by following the steps at HTCdev.com
I Successfully installed TWRP Custom Recovery
I Downloaded CM10 as per - http://forum.xda-developers.com/showthread.php?t=1790032. I transferred this as well as Google Apps onto my phones storage.
When attempting to install CM10, I created the Nandroid backup as recommended, and proceeded to wipe the mentioned items using TWRP (a guide I saw said to wipe everything). This is when my Nandroid back-up got wiped. TWRP gives you the option to wipe cache, delvik cache, factory reset, system, external storage, internal storage and format data. I did alll of these, and this was my mistake I believe? I proceeded to try and install CM10 and gapps from internal storage (I had to re load these back on after I wiped everything), and the install of CM10 displayed as successful.
Upon rebooting to system, the HTC screen comes up first and then goes to the CM10 animation. The phone then stays on this animation (rotating circle) for up to 10-15 minutes.
I have read thread after thread with people experiencing similar issues, and have tried rectifying my problem with various versions of roms and different guides out there. I can still boot into recovery (TWRP) mode via bootloader, and this means I can still mount my phone's storage onto my PC and have access to the storage directory. As I have deleted the Nandroid backup though, and because the ROM's won't install, I am stuck in no man's land.
There must surely be a way to have a ROM installed (even if its back to stock Telstra) from the position I am in, it would be greatly appreciated if someone may be able to point me in the right direction.
Thanks,
Robbie
maybe yall need to "fastboot flash boot boot.img" now
robbie.d said:
TWRP gives you the option to wipe cache, delvik cache, factory reset, system, external storage, internal storage and format data. I did alll of these, and this was my mistake I believe?
Click to expand...
Click to collapse
Why do people keep doing this??? Just because TWRP gives you all those options, doesn't mean you should use them.
Sometimes, people will say to do a "full wipe" when flashing a ROM. But that term is a bit misleading. Factory reset (from TWRP, never from hboot), wipe Dalvik and wipe cache is all that is technically required when flashing a new ROM. Some people like to wipe more "just in case". But if you aren't completely confidant in what you are doing, keep in simple and don't make it more complicated than it needs to be.
I don't know if wiping everything is the cause of your woes, but it certainly didn't help, and caused you to do some extra steps.
Flash boot.img via fastboot as previously suggested. Otherwise, just try to re-download and flash the files agin. Its seems that some people are having troubles booting after flashing CM10 (even after doing the correct wipes and flashing boot.img). Doesn't seem to be much rhyme or reason, but just flashing again has fixed the problem for at least one person.
Thanks so much, such a simple fix! That has me booted up into CM10.
I have installed cm-10-20130107-NIGHTLY-evita and cm-10.0.0-evita , however with both of these versions, my touch screen is not working once it boots up. I can function with the volume up/down, and with the power buttons, but cannot get past my SIM card lock screen.
I noticed this thread http://forum.xda-developers.com/showthread.php?t=2083314 (no solution yet)...
Does anyone have a solution to this issue that seems a common one?
Alternatively, more than happy to get an alternative ROM on my phone in the interim...Can someone recommend me a ROM?
Again, I really appreciate the quick response to my problem, very happy my phone is in operation!