hello guys plz help... my phone was rooted and s=off.
I was trying different rom today(CM7,CM6.12, ICE 1.16,and evil's Desire Z) after trying all, i dl the wrong rom for CM6.12(not for mytouch 4g) and flashed, and have error. it said open rom manager to report the issue. after that i flashed back to ice1.16, the phone keep restarting, same as Evil's Desire Z or the CM 7. any idea how to fix it? thanks!!!
kofpk said:
hello guys plz help... my phone was rooted and s=off.
I was trying different rom today(CM7,CM6.12, ICE 1.16,and evil's Desire Z) after trying all, i dl the wrong rom for CM6.12(not for mytouch 4g) and flashed, and have error. it said open rom manager to report the issue. after that i flashed back to ice1.16, the phone keep restarting, same as Evil's Desire Z or the CM 7. any idea how to fix it? thanks!!!
Click to expand...
Click to collapse
It sounds like you might have corrupted your recovery. You'll need to reflash it through rom manager, or through advanced if you can't get the phone to actually boot.
Sent from my HTC Glacier using XDA App
kofpk said:
hello guys plz help... my phone was rooted and s=off.
I was trying different rom today(CM7,CM6.12, ICE 1.16,and evil's Desire Z) after trying all, i dl the wrong rom for CM6.12(not for mytouch 4g) and flashed, and have error. it said open rom manager to report the issue. after that i flashed back to ice1.16, the phone keep restarting, same as Evil's Desire Z or the CM 7. any idea how to fix it? thanks!!!
Click to expand...
Click to collapse
jmwils3 said:
It sounds like you might have corrupted your recovery. You'll need to reflash it through rom manager, or through advanced if you can't get the phone to actually boot.
Sent from my HTC Glacier using XDA App
Click to expand...
Click to collapse
Although jmwils3 may be right to me it sounds like you have not Factory reset your phone through recovery, either that or you need to wipe your Dalvik cache and normal cache... personally I do a factory wipe through recovery twice and wipe norm cache and dalvik cache twice just to be safe. when you flash between roms and dont fully wipe, your phone retains some of the information from the previous rom which creates issues with the one you want to use.
try what I said, IMHO I think that's what is going on and not a corrupted Recovery as you were romming not flashing a new recovery
thanks
thanks for the reply... i reflashed the stock recovery.img and it work now.
kofpk said:
thanks for the reply... i reflashed the stock recovery.img and it work now.
Click to expand...
Click to collapse
Good to hear, bro
Sent from my HTC Glacier using XDA App
[Q] Reset back to stock ROM?
edit:
sorry having 25tabs can be confusing
Posted in wrong thread
Triketra said:
Although jmwils3 may be right to me it sounds like you have not Factory reset your phone through recovery, either that or you need to wipe your Dalvik cache and normal cache... personally I do a factory wipe through recovery twice and wipe norm cache and dalvik cache twice just to be safe. when you flash between roms and dont fully wipe, your phone retains some of the information from the previous rom which creates issues with the one you want to use.
try what I said, IMHO I think that's what is going on and not a corrupted Recovery as you were romming not flashing a new recovery
Click to expand...
Click to collapse
Little known fact learned from option94 wiping cache is wiping dalvik cache also
Sent from my HTC Glaciee using XDA Premium App
one u flash stock go get clockworkmod aka rom manager and install the newest recovery within the app. you should be able to download and restore any rom without bootloop.
Related
if this is the wrong place for this SORRY IN ADVANCE
ok so after rooting my shift i followed all the steps got the recovery on there and downloaded a ROM and wiped everything and when the rom flashed it said error 7 instalation aborted so i hit reboot system now just to see what would happen because i did wipe everything so i was expecting to be stuck at the boot img..no problem was just playing around but the thing actually booted in a rom that looks 100% stock....what happened
even tho the ROM looks 100% stock it is def not i have adfree and esfile explorer added to app drawer now if its gonna flash the rom anyways why does cw 2.5.1 tell me its a no go with a stauts 7 i have even formatted my card to wipe it 100% and the same thing happens>?
when you "wipe" you're not wiping the rom. The data, cache etc yes. Only a rom install overwrites a prior rom. unless you format the phone.
RyteSyde said:
when you "wipe" you're not wiping the rom. The data, cache etc yes. Only a rom install overwrites a prior rom. unless you format the phone.
Click to expand...
Click to collapse
yeah it must have just been an issue with the rom i was flashing because i flashed another one no problem thanks for that bit of info though
I had no problem flash nfinites stock rom...must have been something you did...not so much the rom...
Sent from my PG06100 using XDA App
JKILO said:
I had no problem flash nfinites stock rom...must have been something you did...not so much the rom...
Sent from my PG06100 using XDA App
Click to expand...
Click to collapse
People that flashed the base steel posted had similiar issues. E.G. if you were on cm6 and wiped, then flashed the base, you'd boot into a fresh cm6. The partitions were setup wrong, I believe.
Sent from my Speedy Shift.
smoothtaste said:
People that flashed the base steel posted had similiar issues. E.G. if you were on cm6 and wiped, then flashed the base, you'd boot into a fresh cm6. The partitions were setup wrong, I believe.
Sent from my Speedy Shift.
Click to expand...
Click to collapse
Ok my fault...never took notice..thanks
Sent from my PG06100 using XDA App
I just rooted for the first time yesterday so I'm fairly new to all this... is it common practice to wipe cahce/dalvik prior to flashing any ROM?
I've gone back and forth from the stock ROM to another custom Sense ROM without wiping and no issues. Is it only advised if something goes wrong? Also, is there an issue with just going into recovery and wiping cache when NOT flashing a new ROM (just rebooting to the same one I'm using)? Thanks for the help.
HolyShift said:
I just rooted for the first time yesterday so I'm fairly new to all this... is it common practice to wipe cahce/dalvik prior to flashing any ROM?
I've gone back and forth from the stock ROM to another custom Sense ROM without wiping and no issues. Is it only advised if something goes wrong? Also, is there an issue with just going into recovery and wiping cache when NOT flashing a new ROM (just rebooting to the same one I'm using)? Thanks for the help.
Click to expand...
Click to collapse
Its good practice to always wipe. You may get by without it a few flashes. But eventually you'll be haunted by force closes, boot loops, etc.
Personally when I flash a new rom after the data, cache and dalvik wipes I format my boot, system, data and cache partitions manually via the mounts menu.
From experience, to truly see changes in rom updates or properly enjoy an entirely different one, this eliminates most problems before they ever manifest.
Sent from my Speedy Shift.
I had and htc incredible phone before and I know its because of the locked bootloader for the droid x but it is impossible for me to install roms on this phone. I feel like I am a failure at life lol. I have it rooted with petes root tool, I have bootstrap recovery installed. But when I go into clockwork recovery to install the zip file and that goes OK, the phone reboots and I am stuck in the bootloop. I know I can sbf back to stock and do it all over again because I am smart to always do a backup of the current stock rom I am on.
There has to be something I am missing that I am hoping you guys can help me with. I am dying to put a CyanogenMod or OMFGB rom on here but like I said...I am a failure lol..
Jon2datymuls said:
I had and htc incredible phone before and I know its because of the locked bootloader for the droid x but it is impossible for me to install roms on this phone. I feel like I am a failure at life lol. I have it rooted with petes root tool, I have bootstrap recovery installed. But when I go into clockwork recovery to install the zip file and that goes OK, the phone reboots and I am stuck in the bootloop. I know I can sbf back to stock and do it all over again because I am smart to always do a backup of the current stock rom I am on.
There has to be something I am missing that I am hoping you guys can help me with. I am dying to put a CyanogenMod or OMFGB rom on here but like I said...I am a failure lol..
Click to expand...
Click to collapse
Try booting into recovery and doing a data wipe.
Sent from my DROIDX using XDA App
infazzdar said:
Try booting into recovery and doing a data wipe.
Sent from my DROIDX using XDA App
Click to expand...
Click to collapse
Ya I have done those steps also. wiped data/cache/battery stats. Still was a no go.
Wipe data factory reset, wipe data partition and then go to advance and wipe davlik data. Then flash rom the new rom. Hope this helps.
FrostyIcy said:
Wipe data factory reset, wipe data partition and then go to advance and wipe davlik data. Then flash rom the new rom. Hope this helps.
Click to expand...
Click to collapse
Thanks I will try this out. I finally had enough and called Verizon to send me another phone. Now when I use the bootstrap it reboots goes to the moto icon and then I get a black screen to nothing, I have to do a battery pull and restart the phone. So now I really have no way to get to clockwork recovery. Like I said I called them up and on Tuesday they are sending me a Droid X2, so hopefully I will have better luck with that phone and deal with it for a few more weeks then upgrade to the Nexus Prime because that phone looks sweet.
I was running cm7 since it was first released. I got a new phone so i decided to give my atrix to my younger brother. The problem is after i went through the process of putting the phone back to stock, there now seems to be dead zones on the phone. For example i cannot press the w,e,s, keys. Can anyone help me or tell me if i've done something wrong?
I'm not sure you did anything wrong specifically. Did you make sure the clear all the cache? How did you put stock back on it (IE. flashed stock via CWM, moto fastboot, etc)?.
Boot into recovery, wipe dalvik cache, system cache, reflash your firmware of choice, reboot.
Sent from my MB860 using Tapatalk
Ive had numerous problems with cm7 for atrix but ive found that backup everything you need with titanium backup and then just reflash the rom and wipe the data and davlik cache and it should. But yh there are lots of issues with the cm7 rom for atrix but its still in beta so dont worry too much it will be ok when there are more updates
Sam
samdrake112 said:
But yh there are lots of issues with the cm7 rom for atrix but its still in beta so dont worry too much it will be ok when there are more updates
Click to expand...
Click to collapse
The CM7 beta does not have the issues that the OP described so please don't let him think that's the reason.
OP, re-flash your phone with a different ROM or with CM7 again and see if it still persists.
My wife and I both have MyTouch 4Gs and both of our phones exhibit this problem. Whenever I load a Sense based ROM both phones reboot without warning. The last time I had a Sense based ROM on her phone it would continuously reboot when plugged in to the charger. I loaded a Sense based ROM on my phone last night to try out and it would reboot every few minutes. I've probably tried six or seven different Sense based ROMs and the rebooting issue always happens. Both of our phones are currently running a CM7 based ROM and working fine. Anyone else see the same issue?
greenmaze said:
My wife and I both have MyTouch 4Gs and both of our phones exhibit this problem. Whenever I load a Sense based ROM both phones reboot without warning. The last time I had a Sense based ROM on her phone it would continuously reboot when plugged in to the charger. I loaded a Sense based ROM on my phone last night to try out and it would reboot every few minutes. I've probably tried six or seven different Sense based ROMs and the rebooting issue always happens. Both of our phones are currently running a CM7 based ROM and working fine. Anyone else see the same issue?
Click to expand...
Click to collapse
Did you verify the MD5SUM post pushing the ROM to the SD Card.
neidlinger said:
Did you verify the MD5SUM post pushing the ROM to the SD Card.
Click to expand...
Click to collapse
+1 this
And/or are you flashing anithing else right after flashing the rom? If you are, don't. Just flash the from and reboot. Also, make sure you're found a full complete wipe. Wiping data, cache and dalvik before flashing.
Sent from my HTC Glacier using xda premium
That problem can also be caused by the phone being overclocked a little too much. Try changing speed and voltage to match stock.
Sent from my HTC Glacier using xda premium
neidlinger said:
Did you verify the MD5SUM post pushing the ROM to the SD Card.
Click to expand...
Click to collapse
Yes, I verified this.
coupetastic-droid said:
And/or are you flashing anithing else right after flashing the rom? If you are, don't. Just flash the from and reboot. Also, make sure you're found a full complete wipe. Wiping data, cache and dalvik before flashing.
Click to expand...
Click to collapse
No, not flashing anything else. Yes, I wiped data, cache, and dalvik before flashing.
eqjunkie829 said:
That problem can also be caused by the phone being overclocked a little too much. Try changing speed and voltage to match stock.
Click to expand...
Click to collapse
I'm not sure what those ROMs were overclocked too, but I'm running CM7 at about 1209MHz right now and have no issues.
greenmaze said:
Yes, I verified this.
No, not flashing anything else. Yes, I wiped data, cache, and dalvik before flashing.
I'm not sure what those ROMs were overclocked too, but I'm running CM7 at about 1209MHz right now and have no issues.
Click to expand...
Click to collapse
You need to do a complete factory restore via the recovery image. the /system is the most important part to make sure is wiped. And from that statement you're not doing that.
neidlinger said:
You need to do a complete factory restore via the recovery image. the /system is the most important part to make sure is wiped. And from that statement you're not doing that.
Click to expand...
Click to collapse
Is a complete factory restore simply finding and flashing a stock image?
greenmaze said:
Is a complete factory restore simply finding and flashing a stock image?
Click to expand...
Click to collapse
No. Neidlinger is referring to a full wipe of /system /data and both caches prior to flashing a new rom.
Sent from my HTC Glacier using xda premium
greenmaze said:
Is a complete factory restore simply finding and flashing a stock image?
Click to expand...
Click to collapse
eqjunkie829 said:
No. Neidlinger is referring to a full wipe of /system /data and both caches prior to flashing a new rom.
Sent from my HTC Glacier using xda premium
Click to expand...
Click to collapse
@EQJUNKIE829 hit the nail on the head. Just flashing a new OS isn't wiping the old one. You need to do a nandroid backup of your current OS, then do a complete factory reset. It WILL NOT wipe the recovery image or the hBoot. Then flash the new OS.
No matter how many threads I say to wipe the bloody system partition in, there is always this problem. Its frustrating.
Help my phone acts weird.
Did you do a full wipe?
Yes
Are you sure? You wiped the system partition?
Umm, I dunno. I think so.
:faceplam: Wipe system, data, cache and dalvik cache and reflash.
That fixed it. Thanks!
Sure thing! :hangs self:
estallings15 said:
No matter how many threads I say to wipe the bloody system partition in, there is always this problem. Its frustrating.
Help my phone acts weird.
Did you do a full wipe?
Yes
Are you sure? You wiped the system partition?
Umm, I dunno. I think so.
:faceplam: Wipe system, data, cache and dalvik cache and reflash.
That fixed it. Thanks!
Sure thing! :hangs self:
Click to expand...
Click to collapse
This person only has 5 post on XDA you could go a tad lighter.
neidlinger said:
This person only has 5 post on XDA you could go a tad lighter.
Click to expand...
Click to collapse
Oh no. I wasn't upset with them. Just in general. Its almost ALWAYS a wipe issue, and people just don't get it. I'm just griping period
Sent from my HTC Glacier using XDA App
Clean wipe before install and check md5um
Just recently updated my radio to 26.13.04.19 on Andromadus B3 and applied the Radio lib-ril and .so updater-CM9 & AOKP based ROMs from EdKeys. However, now my phone has random reboots that happen almost every 2 minutes. Flashing an old radio does not fix the issue and wiping the phone does nothing. I tried to flash new roms, but i still get the same issue. Is there a solution to this problem? Happen to anyone else?
nguyenkendy said:
Just recently updated my radio to 26.13.04.19 on Andromadus B3 and applied the Radio lib-ril and .so updater-CM9 & AOKP based ROMs from EdKeys. However, now my phone has random reboots that happen almost every 2 minutes. Flashing an old radio does not fix the issue and wiping the phone does nothing. I tried to flash new roms, but i still get the same issue. Is there a solution to this problem? Happen to anyone else?
Click to expand...
Click to collapse
Did you try a superwipe before flashing another ROM? That could be the issue. Go and superwipe, then flash a ROM again, see if you still get the same boot loops.
Fastboot -w is an even cleaner wipe and you may want to try this
Sent from my HTC Vision using xda premium
demkantor said:
Fastboot -w is an even cleaner wipe and you may want to try this
Sent from my HTC Vision using xda premium
Click to expand...
Click to collapse
Hey thanks for the reply, but ive already done that. Every time i install a new rom i flash the superwipe zip so thats not the problem. However, i have noticed that wiping cache and dalvik keeps it up longer before it reboots. But after that, it begins to reboot as soon as the ohone boots up.
Did you also do the efs wipe? Maybe that could be the problem.
Got this from the other thread:
IMPORTANT: While you are in recovery, wipe your cache and dalvick cache and wipe the efs partitions by flashing the Vision EFS partion wipe tool.
Sent from my HTC Vision using XDA