Hi, I'm not sure if I'm the only one experiencing this but when I select the factory reset option in custom ROMs like Cyanogenmod and Paranoid Android on my Moto G it reboots and comes up with a flashing android but does nothing. It just sticks and when force rebooted nothing has changed.
I haven't formatted /system if that could be the issue
Any help would be greatly apprecaited
TechMinerUK said:
Hi, I'm not sure if I'm the only one experiencing this but when I select the factory reset option in custom ROMs like Cyanogenmod and Paranoid Android on my Moto G it reboots and comes up with a flashing android but does nothing. It just sticks and when force rebooted nothing has changed.
I haven't formatted /system if that could be the issue
Any help would be greatly apprecaited
Click to expand...
Click to collapse
Anyone ? Surely I can't be the only one!
I have had the same issue. Here is what I think is happening. Cyanogenmod factory reset is bascially the wipe /data and /cache in recovery. I think the factory reset button in the UI is sending commands to the recovery. When I did this it glitched out and I hard shutdown my phone. Then I manually went into recovery and used the option to format /data and /cache. Then I rebooted and everything was working again.
skyguy126 said:
I have had the same issue. Here is what I think is happening. Cyanogenmod factory reset is bascially the wipe /data and /cache in recovery. I think the factory reset button in the UI is sending commands to the recovery. When I did this it glitched out and I hard shutdown my phone. Then I manually went into recovery and used the option to format /data and /cache. Then I rebooted and everything was working again.
Click to expand...
Click to collapse
Same, I was wondering if there was a way to get the one inside the phones ROM working though, surely there must be a logical solution like /system wipe before install
Doesn't seem like a big problem at this point so....
skyguy126 said:
Doesn't seem like a big problem at this point so....
Click to expand...
Click to collapse
Yes I suppose but it still unnerves me as I don't know what It could do if left like that e.g. Corrupt memory/IMEI
At least for me I wouldn't go about wiping system partition because is might brick your phone. As far as I know you won't need to wipe system to flash a custom ROM.
skyguy126 said:
At least for me I wouldn't go about wiping system partition because is might brick your phone. As far as I know you won't need to wipe system to flash a custom ROM.
Click to expand...
Click to collapse
Hmmm, I wonder what is the cause of the issue, it's really irritating.
You have to ask someone else more experienced I'm afraid.
skyguy126 said:
At least for me I wouldn't go about wiping system partition because is might brick your phone. As far as I know you won't need to wipe system to flash a custom ROM.
Click to expand...
Click to collapse
Hmm, just done some reading. On this ROM it requires you to format /system
http://forum.xda-developers.com/showthread.php?t=2749854
Wouldn't formating the /system screw up the kernel. And wouldn't screwing up the kernel mean a bricked device.
skyguy126 said:
Wouldn't formating the /system screw up the kernel. And wouldn't screwing up the kernel mean a bricked device.
Click to expand...
Click to collapse
No, as long as we can get into bootloader and/or recovery we are set. /System just contains the ROM files as far as I'm aware. The kernel is stored somewhere else
Related
So I'm familiar with flashing, just not with the tablet. What's the accepted method for flashing from 1ROM to the next? With my phone I generally flashed back to stock using ODIN. Is it OK to simply jump from one ROM to the next?
Thanks guys.
gorealmighty said:
So I'm familiar with flashing, just not with the tablet. What's the accepted method for flashing from 1ROM to the next? With my phone I generally flashed back to stock using ODIN. Is it OK to simply jump from one ROM to the next?
Thanks guys.
Click to expand...
Click to collapse
The same method for your phone is generally the best way to do it on a tablet as well. You "can" jump from one to another, but you always run the risk of file pieces getting left behind or random little bugs cropping up and such. For that reason, it's always best to do a full wipe, factory reset, wipe cache, wipe dalvik cache, and then flash the new ROM.
traumbrecher said:
For that reason, it's always best to do a full wipe, factory reset, wipe cache, wipe dalvik cache, and then flash the new ROM.
Click to expand...
Click to collapse
Formating /system, /data and /cache is sufficient. Factory reset could compromise your /sdcard and /sd-ext (if any) data, depending on the custom recovery you're using.
traumbrecher said:
The same method for your phone is generally the best way to do it on a tablet as well. You "can" jump from one to another, but you always run the risk of file pieces getting left behind or random little bugs cropping up and such. For that reason, it's always best to do a full wipe, factory reset, wipe cache, wipe dalvik cache, and then flash the new ROM.
Click to expand...
Click to collapse
I just want to be clear, im to understand that all I really need to do is a fact data reset, and wipe everything from recovery? if thats all there is to it then freaking sweet. flashing to ODIN and going through the motions gets annoying.
AzureusPT said:
Formating /system, /data and /cache is sufficient. Factory reset could compromise your /sdcard and /sd-ext (if any) data, depending on the custom recovery you're using.
Click to expand...
Click to collapse
I have always done this with the express intent to wipe everything clear and reinstall all apps and data fresh once I'm on the new ROM, but this has never messed up my CWM.
gorealmighty said:
I just want to be clear, im to understand that all I really need to do is a fact data reset, and wipe everything from recovery? if thats all there is to it then freaking sweet. flashing to ODIN and going through the motions gets annoying.
Click to expand...
Click to collapse
Yeah, I feel your pain. I love my SGSII and my wife has my old Captivate, but the ODIN stuff all the time did get kind of annoying. Luckily ODIN and a homemade jig are a lifesaver if you ever screw anything up though But yes, flashing to a new ROM on the tablet is pretty simple and doesn't have a few of the extra steps you have to do on certain phones. Just back everything up on your PC first, then I generally like to type out a list of all the apps I have on the tablet to redownload afterward, then wipe it all and flash the new ROM, then start downloading stuff from the market again.
Flashed several ROMS in my life and have not always wiped all data. Mainly i do dalvik and cache. My phones have always work. Now i have a Razr HD with an unlocked BL with TWRP loaded. I cant seem to get past the initial bootup screen no matter what ROM i flash. What am i missing here guys? Do i need to check the "factory reset" in TWRP along with Dalvik, system and cache?
famac! said:
Flashed several ROMS in my life and have not always wiped all data. Mainly i do dalvik and cache. My phones have always work. Now i have a Razr HD with an unlocked BL with TWRP loaded. I cant seem to get past the initial bootup screen no matter what ROM i flash. What am i missing here guys? Do i need to check the "factory reset" in TWRP along with Dalvik, system and cache?
Click to expand...
Click to collapse
answered here http://forum.xda-developers.com/showthread.php?t=2465695
bweN diorD said:
answered here http://forum.xda-developers.com/showthread.php?t=2465695
Click to expand...
Click to collapse
Not really. The majority of ROMS in question have been 4.2.2 based....
famac! said:
Not really. The majority of ROMS in question have been 4.2.2 based....
Click to expand...
Click to collapse
quote from post 11
"By golly that worked! It booted up fast as well. It must lie with the formatting your internal storage before flashing the 4.3 rom. I tried something similiar to this but I was already on a 4.3 rom that wouldn't boot and I formatted the sd card then tried flashing it again and it booted again for the first time but wouldn't the second. So if your having trouble do this:
Restored stock 4.1.2 using Matt's utility
Rooted with Matt's utility
Put 4.3 rom and GAPPS on external SD
Fastboot flash CWM 6.0.3.5 (or install via Matt's utility if you like)
Wipe data/factory reset
Wipe Cache/Dalvik
Go to mounts/storage and format /data and /data/media (/sdcard) **Back up anything in your internal SD you want to keep before doing this!**
Flash 4.3 rom
Wipe Cache/dalvik
Flash GAPPS
Wipe Cache/dalvik
Boot up and setup rom
Reboot"
bweN diorD said:
quote from post 11
"By golly that worked! It booted up fast as well. It must lie with the formatting your internal storage before flashing the 4.3 rom. I tried something similiar to this but I was already on a 4.3 rom that wouldn't boot and I formatted the sd card then tried flashing it again and it booted again for the first time but wouldn't the second. So if your having trouble do this:
Restored stock 4.1.2 using Matt's utility
Rooted with Matt's utility
Put 4.3 rom and GAPPS on external SD
Fastboot flash CWM 6.0.3.5 (or install via Matt's utility if you like)
Wipe data/factory reset
Wipe Cache/Dalvik
Go to mounts/storage and format /data and /data/media (/sdcard) **Back up anything in your internal SD you want to keep before doing this!**
Flash 4.3 rom
Wipe Cache/dalvik
Flash GAPPS
Wipe Cache/dalvik
Boot up and setup rom
Reboot"
Click to expand...
Click to collapse
Please explain this further to me. My problem is with 4.2.2 ROMS. The fix above is for folks having issues with 4.3 ROMS. Are you suggesting that doing this will also fix my 4.2.2 problems? This is also CWM while i run TWRP. I did a quick look and the two are setup a little difference. I played around with those highlighted instructions and almost accidentally wiped my only backup of my previous state. I actually thought i was toast but somehow i reloaded and went back to my old backup state.
famac! said:
Please explain this further to me. My problem is with 4.2.2 ROMS. The fix above is for folks having issues with 4.3 ROMS. Are you suggesting that doing this will also fix my 4.2.2 problems? This is also CWM while i run TWRP. I did a quick look and the two are setup a little difference. I played around with those highlighted instructions and almost accidentally wiped my only backup of my previous state. I actually thought i was toast but somehow i reloaded and went back to my old backup state.
Click to expand...
Click to collapse
i could be wrong, but in my opinion having the exact same issue even though its a different version, one of the 2 fixes in that thread should work.
the first fix likely doesn't directly apply although i suggest you ensure you have the latest version of your recovery of choice found here http://www.mediafire.com/download/tt7cwwua49n24uv/Razr_HD_Recovery_Flasher_V7.rar
second fix (backup ALL data you don't want to loose first as noted above), then do a full wipe as listed above, not just a fdr that doesn't wipe everything on the internal card.
the problem at this point is, you are assuming it wont work because of version differences, i am assuming it will. until you try it, i don't see any point in exploring other options, if there are any.
Dirty flashing when you go to different ROMs is generally not a good idea. Even on 4.2.2, it leaves residual data behind. There's a reason that the devs talk about doing complete wipes in their ROM threads, and there's a reason that they tell you not to talk about bugs unless you use their install directions.
RikRong said:
Dirty flashing when you go to different ROMs is generally not a good idea. Even on 4.2.2, it leaves residual data behind. There's a reason that the devs talk about doing complete wipes in their ROM threads, and there's a reason that they tell you not to talk about bugs unless you use their install directions.
Click to expand...
Click to collapse
Yeah, i am straight now. Did a full wipe and sailed right past the startup animation. Thanks all.
famac! said:
Yeah, i am straight now. Did a full wipe and sailed right past the startup animation. Thanks all.
Click to expand...
Click to collapse
Nice! Glad to see you got it working.
Having not learnt my lesson from previous Android adventures, I decided update CyanogenMod installation from 10.1.3 to 10.2.0 on my Nexus S. I did the sideload from ClockworkMod recovery, rebooted, and got stuck on the loading screen. Having read suggestions to update GApps as well, I went back into ClockworkMod recovery, sideloaded the GApps, and, again, no joy. I understand that the next step to recover the phone is to factory reset it, but I forgot to backup everything beforehand.
I have some important information that I really don't want to lose in a factory reset. Complicating matters is that I've turned on encryption, so I can't simply use the ClockworkMod backup system and/or access the SD card. I'm running Linux with adb, so I can shell in if someone tells me how to dump the saved data off the phone. Even if I just get raw data and I have to enter it back in myself, that's better than losing it.
I know that downgrading back to 10.1 without a wipe is generally frowned upon. Is it worth gambling with the 10.3 nightlies to see if I can get a stable Android (there's an oxymoron!) boot going long enough for me to get everything off my phone before wiping it and reverting back to 10.2? If the issue is a corrupted apk, can I manually remove them to figure out what the problem is?
Borden Rhodes said:
Having not learnt my lesson from previous Android adventures, I decided update CyanogenMod installation from 10.1.3 to 10.2.0 on my Nexus S. I did the sideload from ClockworkMod recovery, rebooted, and got stuck on the loading screen. Having read suggestions to update GApps as well, I went back into ClockworkMod recovery, sideloaded the GApps, and, again, no joy. I understand that the next step to recover the phone is to factory reset it, but I forgot to backup everything beforehand.
I have some important information that I really don't want to lose in a factory reset. Complicating matters is that I've turned on encryption, so I can't simply use the ClockworkMod backup system and/or access the SD card. I'm running Linux with adb, so I can shell in if someone tells me how to dump the saved data off the phone. Even if I just get raw data and I have to enter it back in myself, that's better than losing it.
I know that downgrading back to 10.1 without a wipe is generally frowned upon. Is it worth gambling with the 10.3 nightlies to see if I can get a stable Android (there's an oxymoron!) boot going long enough for me to get everything off my phone before wiping it and reverting back to 10.2? If the issue is a corrupted apk, can I manually remove them to figure out what the problem is?
Click to expand...
Click to collapse
1. why are you side loading instead of flashing normal?
2. have you tried wiping everything minus sd and data and returning to 10.1.3?
3. when jumping versions, you need a full wipe..
Setting.Out said:
1. why are you side loading instead of flashing normal?
Click to expand...
Click to collapse
I sideload the update because you can't access an encrypted SD Card (which mine is) from recovery mode. I'm not aware of any other way to do upgrades.
Setting.Out said:
2. have you tried wiping everything minus sd and data and returning to 10.1.3?
Click to expand...
Click to collapse
Is there a way to do this? My understanding is that a wipe will clear the data and the SD Card unless you're lucky. If I could revert back to 10.1.3 without touching the data, that would be great, but I'd want to be linked to a tutorial so I'm sure not to mess up.
Setting.Out said:
3. when jumping versions, you need a full wipe..
Click to expand...
Click to collapse
Yeah, I'm an idiot. I've gotten away with sideload updates in the past, but Android caught me this time and left me in limbo.
Borden Rhodes said:
I sideload the update because you can't access an encrypted SD Card (which mine is) from recovery mode. I'm not aware of any other way to do upgrades.
Is there a way to do this? My understanding is that a wipe will clear the data and the SD Card unless you're lucky. If I could revert back to 10.1.3 without touching the data, that would be great, but I'd want to be linked to a tutorial so I'm sure not to mess up.
Yeah, I'm an idiot. I've gotten away with sideload updates in the past, but Android caught me this time and left me in limbo.
Click to expand...
Click to collapse
If you boot into CWM and do a format/wipe on everything MINUS the SD and DATA, you won't lose anything, but it may not fix your issue.. If you get your phone back up and running take off the encryption and back up your files, FULL WIPE and try again..
Thank you for the quick reply.
Setting.Out said:
If you boot into CWM and do a format/wipe on everything MINUS the SD and DATA, you won't lose anything, but it may not fix your issue.. If you get your phone back up and running take off the encryption and back up your files, FULL WIPE and try again..
Click to expand...
Click to collapse
When I go into ClockwordMod, version 6.0.4.3, the 'wipe data/factory reset' is the only option that I see, but it then warns me that all data will be wiped, which, I'm guessing, includes the /data partition. Is this correct or should I look some place else?
Borden Rhodes said:
Thank you for the quick reply.
When I go into ClockwordMod, version 6.0.4.3, the 'wipe data/factory reset' is the only option that I see, but it then warns me that all data will be wiped, which, I'm guessing, includes the /data partition. Is this correct or should I look some place else?
Click to expand...
Click to collapse
Mounts and storage / format
Sent from my Nexus S using XDA Premium 4 mobile app
---------- Post added at 11:34 PM ---------- Previous post was at 11:31 PM ----------
Also go to advanced / wipe dalvik... Are you sure you've flashed Roms before?
Sent from my Nexus S using XDA Premium 4 mobile app
Setting.Out said:
Mounts and storage / format
Click to expand...
Click to collapse
OK, found it there, and formatted /storage, /cache, /boot, and /system. Reflashed CM 10.2 and GApps 4.3 with no success. However, I did manage to dd dump the contents of mmcblk0p2 and mmcblk0p3 to my Linux hard drive, so if I ever figure out how to mount those images in Linux, I should be able to recover everything.
Setting.Out said:
Also go to advanced / wipe dalvik
Click to expand...
Click to collapse
Yep, I did that, too.
Setting.Out said:
... Are you sure you've flashed Roms before?
Click to expand...
Click to collapse
I don't understand this question. How else could I have gotten CM onto my phone in the first place if I never flashed a ROM?
With few other options, I did a factory reset which, predictably, wiped everything but the SD card and put me into a fresh phone. It's also not mounting the SD. So, since all of my data on my phone is gone, I'll just have to hang onto the dumps that I have and hope and pray that someone can tell me how to mount them to get all of my files back.
I'm having an issue with an app and I've tried everything I can think of to troubleshoot it, Uninstall/re-install. Turn phone off/on, restart phone.
I was thinking of trying a reset on my phone, but it's currently rooted/unlocked.
Will doing the reset under settings give me any issues?
Any help is greatly appreciated.
Thank you
If you have a custom recovery installed like twrp or cwm you can do a full wipe from there and it will essentially do the same thing.
sent from my VenomOne M8
No it wont.
I also have the same question. Did you do the reset? Lose root? What happened?
Sent from my HTC One
Roque13 said:
If you have a custom recovery installed like twrp or cwm you can do a full wipe from there and it will essentially do the same thing.
Click to expand...
Click to collapse
x_V.I.P.3.l2_x said:
No it wont.
Click to expand...
Click to collapse
Yes it will. And if you think it won't a little more elaborate post would be helpful...... ?????
I would not do a factory restore from Settings with a custom recovery installed. I have never tried this on the M8 but on the Transformer tablets that can get you into a nasty "forced reboot to recovery" loop.
If it's an app causing the problem, just do a Factory Wipe in recovery. In TWRP the Factory Wipe will wipe all your apps and their data (not your personal files in data/media though) and also cache and dalvik. Not sure how CWM handles that option....
Read the recovery log while it's running or save the log from the Advanced option and check afterwards which partitions the recovery wiped.
For good measure re-flash the rom and you should be good to go.
I got a new phone and decided to finally sell the Moto G. It was on some ROM, so I factory reset from options, which forced it into a bootloop. So I then tried to install a stock rom lollipop rom (http://forum.xda-developers.com/showthread.php?t=2542219). But it didn't work. I then realised, that I cannot update the recovery on the phone at all. Its stuck on a custom recovery, that works, but should not be there as I've tried to overwrite it with stock. Ever since then I've been trying to rectify this. I've tried flashing recovery both through the custom recovery itself and through fastboot.
Also, something else I've noticed. If I put some files on the phone and restart it, they seem to disappear. Another thing I've just noticed, I can't seem to wipe the phone. All of my original files are still on it ? That doesn't make sense..
eMMc corruption.
Symptoms:
(i) Cannot change Recovery.
(ii) Cannot wipe /system | /system is read-only
Many Moto G's end up this way. The corruption cannot be repaired, however you may be able to flash a custom ROM (Stock or AOSP) via TWRP.
I've tried flashing a stock rom through TWRP, but it seems to be stuck at boot :/
smilgy said:
I've tried flashing a stock rom through TWRP, but it seems to be stuck at boot :/
Click to expand...
Click to collapse
Try CM12/13.
lost101 said:
Try CM12/13.
Click to expand...
Click to collapse
It gives hangs at patching system image unconditionally.. Looks like its dead.
lost101 said:
Try CM12/13.
Click to expand...
Click to collapse
if is a emmc corruption theres any fix?
alex61194 said:
if is a emmc corruption theres any fix?
Click to expand...
Click to collapse
None that I am aware of.