Would the 5.0.1 official RUU + factory reset using stock recovery, do the trick for the NV Partition reset?
Or would I have to RUU to 4.4.4 + factory reset using stock recovery, and then update to 5.0.1 later?
All the articles I see refer to 4.4.4, but could that be because the articles were written before 5.0.1 came out?
bigblueshock said:
Would the 5.0.1 official RUU + factory reset using stock recovery, do the trick for the NV Partition reset?
Or would I have to RUU to 4.4.4 + factory reset using stock recovery, and then update to 5.0.1 later?
All the articles I see refer to 4.4.4, but could that be because the articles were written before 5.0.1 came out?
Click to expand...
Click to collapse
The version number you RUU to is irrelevant for this purpose. A factory reset with the stock recovery you got through a 5.0.1 RUU will fix you up.
As I understand, you don't even have to do the RUU. You can install just the stock recovery for your software version and do a factory reset from hboot. Then just flash back your custom recovery and restore a nandroid and you're good to go.
cntryby429 said:
The version number you RUU to is irrelevant for this purpose. A factory reset with the stock recovery you got through a 5.0.1 RUU will fix you up.
As I understand, you don't even have to do the RUU. You can install just the stock recovery for your software version and do a factory reset from hboot. Then just flash back your custom recovery and restore a nandroid and you're good to go.
Click to expand...
Click to collapse
Interesting!!! Thank you.
That would theoretically mean the nv partition info must be stored in the recovery itself.
Thanks for the info
bigblueshock said:
Interesting!!! Thank you.
That would theoretically mean the nv partition info must be stored in the recovery itself.
Thanks for the info
Click to expand...
Click to collapse
I personally don't know but theoretically they could be stored in one of the many other partitions and stock recovery is the only recovery that is scripted to go find those values and apply them. I'm mostly here at this point to repeat the things I've seen smart people say time and time again
Related
Ok, so there is not a question for this in the "G2x" section so this is legal I hope? lol.
How do I reset my phone so it is how it was the day I opened it out of the box? I did the reset on it (under privacy > factory data reset) and I still have the ROM I had loaded on here and CWM...
Paul Nur said:
Ok, so there is not a question for this in the "G2x" section so this is legal I hope? lol.
How do I reset my phone so it is how it was the day I opened it out of the box? I did the reset on it (under privacy > factory data reset) and I still have the ROM I had loaded on here and CWM...
Click to expand...
Click to collapse
You need to download the Nandroid backup image for the Froyo stock ROM. Then boot into Clockworkmod Recovery and restore the image. Then use NVFlash to flash the stock recovery image. The only thing that won't be restored is the baseband if you updated it. The baseband will remain the July 15th version if you did update with the GB OTA or LG Updater flash. You can also download and flash the GB stock image, which is how the phones ship from T-Mobile now.
jboxer said:
You need to download the Nandroid backup image for the Froyo stock ROM. Then boot into Clockworkmod Recovery and restore the image. Then use NVFlash to flash the stock recovery image. The only thing that won't be restored is the baseband if you updated it. The baseband will remain the July 15th version if you did update with the GB OTA or LG Updater flash. You can also download and flash the GB stock image, which is how the phones ship from T-Mobile now.
Click to expand...
Click to collapse
Can you provide me with a few links for this stuff and just a few steps, I am really sorry, I am getting really frustrated right now and idk what to do....
Hey guys, its my first post and I tried searching the forums and google for the answer but didn't seem to find any.
I have the s3 SCHi535-VRLHE firmware and rooted my phone with through Noxious Ninja's walkthrough. During the process (Win7 4bit) after installing the drivers I let windows update update my drivers and cause a conflict with the 1.4.6 drivers. Should of stopped there but went through with rooting anyway (I know I'm a noob).
I have not flashed any custom ROMs after I rooted so my question is what's the difference between a factory reset vs. flashing the stock rom back onto my phone now?
Looking forward to reading and hopefully learning something from your responses!
Malik
A factory reset will just clear out your user data. You should probably put a stock ROM on your exSDcard, boot into recovery, wipe data, then flash the ROM. That will put you back to stock. Though you'll still be rooted and unlocked.
e90driver said:
A factory reset will just clear out your user data. You should probably put a stock ROM on your exSDcard, boot into recovery, wipe data, then flash the ROM. That will put you back to stock. Though you'll still be rooted and unlocked.
Click to expand...
Click to collapse
If I already did a factory wipe/reset is it safe to flash the stock rom onto that or do I have to root again?
I need the MF1 odin flashable package to revert my wifes phone back to stock MF1 and reroot but I can not find where to download the odin package. I have searched through the sticky threads and all I can find is older version prior to MF1. TIA for any help.
deuce237bblock said:
I need the MF1 odin flashable package to revert my wifes phone back to stock MF1 and reroot but I can not find where to download the odin package. I have searched through the sticky threads and all I can find is older version prior to MF1. TIA for any help.
Click to expand...
Click to collapse
Are you looking fir Odin or the MF1 firmware? here is the MF1 firmware for Odin, just unzip then flash with Odin.
http://www.androidfilehost.com/?fid=23134718111254196
Yeah, I am looking for MF1 odin flashable factory image. Will this firmware you have linked revert my wifes phone back to stock MF1?
deuce237bblock said:
Yeah, I am looking for MF1 odin flashable factory image. Will this firmware you have linked revert my wifes phone back to stock MF1?
Click to expand...
Click to collapse
Yes, once it revert back to factory stock, you may received an OTA upgrade to 4.3, make sure don't take the upgrade if not the 4.3 will lock your boot loader and you will NOT able to flash custom rom or custom recovery (you probably knew this right?). Also if you already on the 4.3, you CAN NOT REVERT BACK TO MF1. You will soft brick your device.
buhohitr said:
Yes, once it revert back to factory stock, you may received an OTA upgrade to 4.3, make sure don't take the upgrade if not the 4.3 will lock your boot loader and you will NOT able to flash custom rom or custom recovery (you probably knew this right?)
Click to expand...
Click to collapse
Yes, I plan to update her phone to the new 4.3 ROM in the dev section but right now I can't do anything with the phone because when I am in TWRP recovery it keeps rebooting on me during Restore and when ever I try to wipe as soon as I swipe to wipe it reboots. That's why I am just going to odin back to stock, reroot and flash 4.3 in recovery.
BTW, Thank you for your help!
deuce237bblock said:
BTW, Thank you for your help!
Click to expand...
Click to collapse
Did you try wipe: cache, dalvik cache, system and data? (wipe all 4 at the same time) then reflash the firmware with twrp. BTW what version is your TWRP? It may help to take a look at this http://forum.xda-developers.com/showthread.php?t=2553199
buhohitr said:
Did you try wipe: cache, dalvik cache, system and data? (wipe all 4 at the same time) then reflash the firmware with twrp. BTW what version is your TWRP?
Click to expand...
Click to collapse
Yes, as soon as it says wiping data without wiping data/media it reboots, i'm on latest TWRP version 2.6.3.1.
My phone on that recovery kept on crashing when it had to wipe data. Not sure why, but i had to odin flash cwm recovery. Im afraid to go back to twrp, in fear of the same issue. Any idea what to do?
deuce237bblock said:
Yes, as soon as it says wiping data without wiping data/media it reboots, i'm on latest TWRP version 2.6.3.1.
Click to expand...
Click to collapse
joedajoester said:
My phone on that recovery kept on crashing when it had to wipe data. Not sure why, but i had to odin flash cwm recovery. Im afraid to go back to twrp, in fear of the same issue. Any idea what to do?
Click to expand...
Click to collapse
just go back to twrp and wipe cache see if that works.
joedajoester said:
My phone on that recovery kept on crashing when it had to wipe data. Not sure why, but i had to odin flash cwm recovery. Im afraid to go back to twrp, in fear of the same issue. Any idea what to do?
Click to expand...
Click to collapse
I would just stick to CWM, they have a touch version.
Sent by me.
I'm on cwm now, but when twrp had to touch anything /data related, my phone would reboot to a bootloop, since it corrupt the data when it crashed.
buhohitr said:
just go back to twrp and wipe cache see if that works.
Click to expand...
Click to collapse
Hi guys, can somebody help me? I received the stagefright update this morning and after downloading it and rebooting, the phone stopped working. It shows the logo animation for a few seconds then the screen goes black. It's a rooted and unlocked phone so i don't know if thats the cause. Also, i can access the recovery mode pressing power and down. Other than that nothing.
If you were rooted and updated ya..the rooting may be the reason
So as you can access the bootloader just flash the stock rom back and you will be done with it..
Jaydeep123 said:
So as you can access the bootloader just flash the stock rom back and you will be done with it..
Click to expand...
Click to collapse
I always forget how peacefull people with knowledge can be. Thanks mate, will do that.
But, just for curiosity: rooted phones tends to have problems after updates?
Yes It may get error or Somthing Else Thats Why I prefer if a update is avaiable flash back to stock and then proceed
Just a quick update. Flashed stock, worked fine. Thanks all.
Also, sorry for posting under general, i was so worried that i forgot to put this under HELP TROUBLESHOOTING.
Also, if I went there before i would find this thread here with the same problem and solution
http://forum.xda-developers.com/2015-moto-g/help/ota-caused-boot-loop-t3202322/
Thanks all again.
reinaldojr said:
Just a quick update. Flashed stock, worked fine. Thanks all.
Also, sorry for posting under general, i was so worried that i forgot to put this under HELP TROUBLESHOOTING.
Also, if I went there before i would find this thread here with the same problem and solution
http://forum.xda-developers.com/2015-moto-g/help/ota-caused-boot-loop-t3202322/
Thanks all again.
Click to expand...
Click to collapse
Mod will move or merge.
Sent from my MotoG3 using XDA Free mobile app
Technically, it should not install at all if it's been rooted. It's interesting that Moto has let this slip by.
In the future, if you have made a single change in the system partition...root, build.prop edit....anything...even custom recovery or kernel...you should reflash your current factory image, reboot, then flash your updated factory image. It's VERY IMPORTANT you reboot between flashing one factory image and the next, though. You may have more issues if you don't.
hp420 said:
Technically, it should not install at all if it's been rooted. It's interesting that Moto has let this slip by.
In the future, if you have made a single change in the system partition...root, build.prop edit....anything...even custom recovery or kernel...you should reflash your current factory image, reboot, then flash your updated factory image. It's VERY IMPORTANT you reboot between flashing one factory image and the next, though. You may have more issues if you don't.
Click to expand...
Click to collapse
Hello HP429; reflashin full factory image would effectively wipe phone
sunandoghosh said:
Hello HP429; reflashin full factory image would effectively wipe phone
Click to expand...
Click to collapse
Not if you only flash the system, boot and recovery image files
Recover the factory
I did the update and as mentioned previously on the thread stales after the logo. (bootloader is unlocked)
I can not find my oem backup. I tried twrp on recovery and was able to backup other stuff. Is there a way to generate the OEM so that i can flash or any other roms that are compatible with Moto G 3rd generation?
Try wiping cache, dalvik cache and data with TWRP. Don't use stock recovery for the data wipe or you will lose all the files stored on your internal partition, as well.
Ok guys I'm stumped on this one. I got the OTA notification for 5.1 yesterday on my XT1034 and so I decided to preempt any issues I might have and just flash everything back to stock 5.0.2 in order to install the update.
I was able to flash everything fine then went to reboot, got the unlocked bootloader screen and...... nothing. It just stayed on the unlocked bootloader screen. I figured I did something wrong so I reset back to fastboot mode, tried again and sure enough I missed sparsechunk 3. So I tried again, restarted, and.... same thing.
OK then, reset again and reboot into recovery mode. It booted to the Motorola splash screen, ok this is different..... nope still not loading. Reset again and try flashing a custom recovery.
CWM, flashed ok, reset again, Moto splash
TWRP, flashed ok, reset, Moto splash
Philz, flashed, reset, splash
OK.. so I'm clearly doing something wrong. Did some research and tried:
- formatting the cache and userdata partitions
> cache formatted fine, userdata refused to format, not supported for filesystem type 'raw'
- tried flashing again without erasing the partitions
> flashed fine, no change in booting
- tried flashing back to 4.4.4
> flashed fine, no change in booting
- tried flashing all the custom recoveries with 4.4.4, no change
- I found a thread where someone else had a somewhat similar issue, and apparently resolved by unlocking their bootloader
> mines already unlocked, but sure it can't hurt, tried again, but nothing since it's already unlocked
I looked for anyone that had a stock 5.1 image other than the OTA, but couldn't find anything. I gave up on trying stock and looked at some custom roms, but all of them just start with, unlock your bootloader, load a custom recovery and flash the update zip file.
Soooo I'm stumped. I've tried just about everything I can think of. I made backups of everything so I'm not worried about the data I just want a working phone again. I refuse to accept that it's borked at this point since I can still get to fastboot.
OK so, no clue what changed, but I was finally able to boot into recovery, Philz
I wiped and reformatted everything and tried flashing 5.0.2 again
rebooted and it still hung on the bootloader unlocked screen
I'll try flashing Philz again and updating through there
Captains log, startdate much too late oh clock
I reflashed Philz and wiped everything again, then sidloaded CM 12.
I'm just thankful to have a working phone again so I'll go with this for now.
tapman said:
Captains log, startdate much too late oh clock
I reflashed Philz and wiped everything again, then sidloaded CM 12.
I'm just thankful to have a working phone again so I'll go with this for now.
Click to expand...
Click to collapse
Have you tried installing the stock firmware again?
I'm having exactly the same problem, any recovery says it succeeded flashing but when i try to boot it, it goes to stock motorola recovery.
Sorry for being off-topic but what are requirements of receiving OTA?
Stock ROM, stock recovery and a locked or unlocked bootloader?
Umer520 said:
Sorry for being off-topic but what are requirements of receiving OTA?
Stock ROM, stock recovery and a locked or unlocked bootloader?
Click to expand...
Click to collapse
My experience is that you need to be unrooted, unmodified system partition and stock recovery
It's usually much easier to reflash a stock image and update than trying to unroot, uninstall, xposed tweaks, restore original build.prop settings, restore original hosts file, etc
moralesnery said:
Have you tried installing the stock firmware again?
I'm having exactly the same problem, any recovery says it succeeded flashing but when i try to boot it, it goes to stock motorola recovery.
Click to expand...
Click to collapse
I haven't tried reflashing the stock again over CM12, but I was able to find a link for stock 5.1 image, you can try going straight there skipping this whole pain.
Here's a link, you can also find it on the stock firmware sticky post that I can't seem to find anymore
https://www.androidfilehost.com/?fid=24052804347819474
tapman said:
I haven't tried reflashing the stock again over CM12, but I was able to find a link for stock 5.1 image, you can try going straight there skipping this whole pain.
Here's a link, you can also find it on the stock firmware sticky post that I can't seem to find anymore
https://www.androidfilehost.com/?fid=24052804347819474
Click to expand...
Click to collapse
Already tried to flash the full firmware again without luck, after rebooting the phone gets stuck at the Unlocked bootloader warning.
Thanks for the link.
tapman said:
My experience is that you need to be unrooted, unmodified system partition and stock recovery
It's usually much easier to reflash a stock image and update than trying to unroot, uninstall, xposed tweaks, restore original build.prop settings, restore original hosts file, etc
Click to expand...
Click to collapse
Yeah, I'll reflash stock firmware.
Just wanna confirm about bootloader.
Umer520 said:
Yeah, I'll reflash stock firmware.
Just wanna confirm about bootloader.
Click to expand...
Click to collapse
Yeah unlocking your bl doesn't affect ota's
moralesnery said:
Already tried to flash the full firmware again without luck, after rebooting the phone gets stuck at the Unlocked bootloader warning.
Thanks for the link.
Click to expand...
Click to collapse
I think at least in part what my issue was, was that the partition formatting got borked. If you can boot to a custom recovery you can wipe and reformat them. Then you should be able to reflash it normally.
I was just so tired of dealing with my phone at that point so I only tried once and gave up with stock, but I'm pretty sure that's what I need to do to fix it.