Related
So, yesterday, I decided to finally jump into the abyss and try to root my Evo. Luckily, everything went completely smooth the first time (never had that happen with any other device). I was actually surprised how easy this root was.
Anyway...my question is, if I decide to flash another ROM on my phone, or rather, in 10 minutes WHEN I flash another ROM onto my phone, if I decide I don't like it, how do I reflash my original NANDROID backup back onto the phone?
I was able to navigate on my SD to where the backup was saved, but shouldn't it be a ZIP file or something? I only have individual backup files.
Also, sorry for the noob question.
Thanks in advance for your help
You go into recovery to do a nandroid restore. Its not something you flash. There is an option for backups and restore. You just run those. I like to do a full wipe before a restore though, just in case. Oh, and keep your backups in the original folder, thats where recovery will get them from
I appreciate the quick response! Thanks
No prob, hope it helped
It definitely helped to get back to the stock ROM, but now it appears as though no other ROMs are working for me. I've tried MIUI and MikFroyo, and they both get stuck in boot loops. There's something I'm apparently not doing right. Hmmm.
Did you wipe data/cache/dalvik before flashing the roms?
mosesport said:
It definitely helped to get back to the stock ROM, but now it appears as though no other ROMs are working for me. I've tried MIUI and MikFroyo, and they both get stuck in boot loops. There's something I'm apparently not doing right. Hmmm.
Click to expand...
Click to collapse
Are you updated to the latest Radio and pri? You have to check what version you have and what version you need to flash the rom you want to use. That is most likely the problem. I know older kernels do not like the new radio or pri. You probably have to update them and you should be fine.
Alright so I'm new at this and haven't managed to brick my phone yet so that's a good sign.
As far as I've learned the process is Root>Recovery>Rom Flash, at least generally.
I rooted it successfully, but when I try to install recovery with ROM Manager it lists only one S3 with a bracketed cell phone provider I don't think I have. So I ditched CWM and went to Goo Manager but when I try to install that, it just hangs on some download page telling me its about to start.
So I'm going to assume the recovery thing is pretty easy to sort out and move on to my next question.
My S3 is unlocked, but I am under Koodo, which is an extension of Telus. My phone model is a I747M, not an I747. As far as I can see they are identical in hardware and software, but I'm really wondering what ROMs I can install. I've researched but didn't find much, and I don't want to blindly flash a i747 rom onto a potentially different phone, and risk anything.
Oh and PS any ROM with the vanilla android (like on the google phones) will do.
Thanks.
Czaran said:
Alright so I'm new at this and haven't managed to brick my phone yet so that's a good sign.
As far as I've learned the process is Root>Recovery>Rom Flash, at least generally.
I rooted it successfully, but when I try to install recovery with ROM Manager it lists only one S3 with a bracketed cell phone provider I don't think I have. So I ditched CWM and went to Goo Manager but when I try to install that, it just hangs on some download page telling me its about to start.
So I'm going to assume the recovery thing is pretty easy to sort out and move on to my next question.
My S3 is unlocked, but I am under Koodo, which is an extension of Telus. My phone model is a I747M, not an I747. As far as I can see they are identical in hardware and software, but I'm really wondering what ROMs I can install. I've researched but didn't find much, and I don't want to blindly flash a i747 rom onto a potentially different phone, and risk anything.
Oh and PS any ROM with the vanilla android (like on the google phones) will do.
Thanks.
Click to expand...
Click to collapse
Hello Noob (I mean that kindly, I used to be one)
I'll help you with what ever you need. I'm Canadian and on Bell i747M. Feel free to ask me any questions and I'll reply as soon as I can. Hopefully I wont be too confusing. I'll just try to break down all your questions in a point form.
First, i747 and i747M are almost identical. With the latest 4.3 ROMS there are differences in the bootloader that will make data not work on your phone. For now, stay away from any stock 4.3 ROM. AOSP ROMs (CM10, Task650) are fine.
Recovery: Through Rom Manager you will want to download the recovery titled "Samsung Galaxy S3 (ATT) " The AT&T version of the S3 is commonly shown as D2ATT(i747). This recovery will work for you. I have had a problem with TWRP myself recently being stuck on the download page. There is another way to install TWRP, but it is a bit more difficult. Try CWM first and if you like I will give you instructions for TWRP.
ROMs: If you want the most common and most stable Vanilla ROMs for your phone you are gonna want Cyanogenmod or Task's ROM. They are very similar with a few different features. Beware, if you ask questions in Task's thread you will be told it is an ATT ROM only. It does work on the i747M though.
Latest Cyanogen: http://download.cyanogenmod.org/?device=d2att
Latest Task : http://forum.xda-developers.com/showthread.php?t=1766684
You will of course lose Touchwiz on these ROMs.
Touchwiz Roms:
STAY AWAY FROM 4.3 ROMS!!!!!!
These ones will do as is. Watch that they are still 4.1.2
http://forum.xda-developers.com/showthread.php?t=1766684 This one has a white theme and is my favorite.
http://forum.xda-developers.com/showthread.php?t=2176793 This one has tons of options.
As always be sure to read the OP in every thread. You will learn lots there. If you want any more info reply and I will try and help.
BCSC said:
Hello Noob (I mean that kindly, I used to be one)
I'll help you with what ever you need. I'm Canadian and on Bell i747M. Feel free to ask me any questions and I'll reply as soon as I can. Hopefully I wont be too confusing. I'll just try to break down all your questions in a point form.
First, i747 and i747M are almost identical. With the latest 4.3 ROMS there are differences in the bootloader that will make data not work on your phone. For now, stay away from any stock 4.3 ROM. AOSP ROMs (CM10, Task650) are fine.
Recovery: Through Rom Manager you will want to download the recovery titled "Samsung Galaxy S3 (ATT) " The AT&T version of the S3 is commonly shown as D2ATT(i747). This recovery will work for you. I have had a problem with TWRP myself recently being stuck on the download page. There is another way to install TWRP, but it is a bit more difficult. Try CWM first and if you like I will give you instructions for TWRP.
ROMs: If you want the most common and most stable Vanilla ROMs for your phone you are gonna want Cyanogenmod or Task's ROM. They are very similar with a few different features. Beware, if you ask questions in Task's thread you will be told it is an ATT ROM only. It does work on the i747M though.
Latest Cyanogen: http://download.cyanogenmod.org/?device=d2att
Latest Task : http://forum.xda-developers.com/showthread.php?t=1766684
You will of course lose Touchwiz on these ROMs.
Touchwiz Roms:
STAY AWAY FROM 4.3 ROMS!!!!!!
These ones will do as is. Watch that they are still 4.1.2
http://forum.xda-developers.com/showthread.php?t=1766684 This one has a white theme and is my favorite.
http://forum.xda-developers.com/showthread.php?t=2176793 This one has tons of options.
As always be sure to read the OP in every thread. You will learn lots there. If you want any more info reply and I will try and help.
Click to expand...
Click to collapse
Awesome, I appreciate the writeup. So I flashed recovery successfully (ROM Manager doesn't seem to have d2att anymore so I used ODIN).
I'll probably go for Cyanogen mod tommorow, I'll post again if I have any questions.
Thanks.
Czaran said:
Awesome, I appreciate the writeup. So I flashed recovery successfully (ROM Manager doesn't seem to have d2att anymore so I used ODIN).
I'll probably go for Cyanogen mod tommorow, I'll post again if I have any questions.
Thanks.
Click to expand...
Click to collapse
CM is a good ROM. There should soon be Kitkat versions available. You will be seeing nightly updates when it does come around. Before you start flashing, you should learn what a 'Nandroid' is. You can take a Nandroid backup in CWM or TWRP. Always save these to an External SD card. If anything ever goes wrong with your ROM, you can just re flash the Nandroid backup and be back to where you were the day you did the backup. The farther you get into flashing the more likely you will need these. Before doing your first Flash, do an Nandroid and copy your photops and stuff off of the phone. When jumping between Stock and AOSP roms, you will need to do a full wipe and will lose what you have not backed up. Be sure to sync contacts to Google....this is the one that has screwed me the most.
BCSC said:
CM is a good ROM. There should soon be Kitkat versions available. You will be seeing nightly updates when it does come around. Before you start flashing, you should learn what a 'Nandroid' is. You can take a Nandroid backup in CWM or TWRP. Always save these to an External SD card. If anything ever goes wrong with your ROM, you can just re flash the Nandroid backup and be back to where you were the day you did the backup. The farther you get into flashing the more likely you will need these. Before doing your first Flash, do an Nandroid and copy your photops and stuff off of the phone. When jumping between Stock and AOSP roms, you will need to do a full wipe and will lose what you have not backed up. Be sure to sync contacts to Google....this is the one that has screwed me the most.
Click to expand...
Click to collapse
Alright, so I have CWM v5.5.0.4, which from what I understand is pretty outdated. It was probably just me following an outdated guide and forgot to look up an updated version. Will I need to update of will it cause any problems? I already backed up my phone on 5.5.0.4 with Nandroid.
Also I feel like I'm misunderstanding the procedure of flashing a new rom. So I downloaded a cm-10.1.3 zip which is is the latest stable build on android 4.2.2. This has an .img inside so this is the rom. I use CWM to flash this onto my phone correct? (Once I figure out if I need to update CWM)
Lastly whats the deal with Gapps? I downloaded the CM Gapps for 10.1 from their wiki. Is this the only way to get Gmail, Maps, and the Google Play Store onto the phone?
From what I understand I think I can just use odin to flash, correct? If so I'd probably prefer that because its the most familiar and noob friendly.
Czaran said:
Alright, so I have CWM v5.5.0.4, which from what I understand is pretty outdated. It was probably just me following an outdated guide and forgot to look up an updated version. Will I need to update of will it cause any problems? I already backed up my phone on 5.5.0.4 with Nandroid.
Also I feel like I'm misunderstanding the procedure of flashing a new rom. So I downloaded a cm-10.1.3 zip which is is the latest stable build on android 4.2.2. This has an .img inside so this is the rom. I use CWM to flash this onto my phone correct? (Once I figure out if I need to update CWM)
Lastly whats the deal with Gapps? I downloaded the CM Gapps for 10.1 from their wiki. Is this the only way to get Gmail, Maps, and the Google Play Store onto the phone?
From what I understand I think I can just use odin to flash, correct? If so I'd probably prefer that because its the most familiar and noob friendly.
Click to expand...
Click to collapse
I wouldn't use Odin. It really will only become necessary if you want to flash back to complete stock.
You do want the latest version of CWM installed or you will run into problems flashing. You can get this 2 ways.
1: through Rom Manager. You will find your specific CWM with these steps. a-Recovery Setup b-ClockworkMod Recovery c-Hit menu button to left of home and pick 'Show All Devices' d- Here scroll until you get 'Samsung Galaxy S3 (AT&T)' D2ATT. e- Click Flash ClockworkMod Recovery. Allow permissions for root. Ignore the touch option unless you want to pay for it. I can teach you the free way.
You will now have the latest CWM
You can download the latest CM-10.2, it is in release candidate stage and is extremely stable. They have been working on it for months. It will give you 4.3 (The good kind, not the one I warned against). After downloading a ROM, you leave it zipped exactly like it is. Do not extract it, just move it to your SD card. You will also want Gapps. Gapps is necessary because it is Google's own software that is legally not allowed to be built into ROMs. It must be installed separately. You can find those here. They help you know which to use with chart depending on which Cyanogen you use http://wiki.cyanogenmod.org/w/Gapps. Again just move the zip over to your internal.
With these 2 zips transferred to your phone you are ready to start. Before you do, make sure you have transferred all your pics and stuff off of the phone. Also be sure to save your contacts. You can now boot into recovery. You should notice recovery version 6.0.4.3. Volume button scrolls menu, Power button selects. You will want to do a Nandroid backup in case anything goes wrong. I know you did one with CWM 5.5 but should do another just to be sure it is with current CWM. You can delete the other one later.
Goto - backup and restore
Goto - backup to external or /storage/sdcard1 (i put both because im already on 4.4 and may have different menu than you.
Let this work and when done continue to flashing ROM
Go to 'choose zip from /sdcard'
Select CM-10-xxxxxxx.zip
After this completes you will do the same with Gapps.zip
After completion of both files you will need to factory reset your phone. Flashing AOSP over Stock will cause boot loops if you do not.
Go back to CWM main menu and select wipe data/factore reset
After completing this go to wipe cache partition and select this.
Finally you want to wipe Dalvik cache. you will find this in CWM under main menu /advanced/wipe dalvik cache.
Upon completion of this you should have CM10 4.3 running. Just exit CWM reboot phone and when booted follow setup instructions.
Let me know if you get stuck somewhere.
BCSC said:
Upon completion of this you should have CM10 4.3 running. Just exit CWM reboot phone and when booted follow setup instructions.
Let me know if you get stuck somewhere.
Click to expand...
Click to collapse
Alright cool. So through Mod Manager, there was not d2att, there was only S3(Metro PCS) which I thought was a bit odd. I found a way to flash an updated recovery via terminal emulator so that went well.
And your steps were very well written and concise. I'm now running CM without a problem.
Thanks for your help!
Czaran said:
Alright cool. So through Mod Manager, there was not d2att, there was only S3(Metro PCS) which I thought was a bit odd. I found a way to flash an updated recovery via terminal emulator so that went well.
And your steps were very well written and concise. I'm now running CM without a problem.
Thanks for your help!
Click to expand...
Click to collapse
Cool terminal emulator was that other way to do it. Hope all is well for you with this. Welcome to flashing. As another tip, if you are going to flash a lot, there is an app called Titanium backup that is well worth the $5 it costs. It saves all your apps and data and after a clean wipe you can just reinstall all your apps in one step. For example after a wipe you will not lose your Angry Birds levels if you restore your titanium data. It's worth a look.
Hello,
My LG G Pad 8.3 currently has the recent OTA Android 4.4.2 upgrade, nothing rooted/modded etc... Can someone let me know please:
1. When is CM11 Milestone 5 being released for the LG G Pad 8.3? I notice M5 was out a whie ago for other devices.
2. What are the known bugs/problems with CM11 M4?
3. Is it better to use CM11 M4 or the latest CM11 Nightly? I'm after a stable release, less so new features.
4. Are these good upgrade instructions? - http://true-android.blogspot.co.uk/2013/12/update-lg-g-pad-83-v500-to-android-442.html
Thank you
Is anyone able to help answer my questions please? Thanks
1) While the official CM11 did not do a M5 release, infected_ did an unofficial one.
http://forum.xda-developers.com/showthread.php?t=2660676
2/3) Not sure about M4 but infected_ M5 and near latest nightly (4/18) broke wifi on my device. Maybe that's why the official maintainers skipped the M5 release. I'm currently running the latest Mahdi-Rom.
http://forum.xda-developers.com/showthread.php?t=2581988
4) Use this instructions for 4.4.2 stock
http://forum.xda-developers.com/showpost.php?p=52092510&postcount=110
ruibing said:
1) While the official CM11 did not do a M5 release, infected_ did an unofficial one.
http://forum.xda-developers.com/showthread.php?t=2660676
Click to expand...
Click to collapse
Are you sure? - http://www.cyanogenmod.org/blog/cyanogenmod-11-0-m5-release. Thanks btw.
ruibing said:
2/3) Not sure about M4 but infected_ M5 and near latest nightly (4/18) broke wifi on my device. Maybe that's why the official maintainers skipped the M5 release. I'm currently running the latest Mahdi-Rom.
http://forum.xda-developers.com/showthread.php?t=2581988
Click to expand...
Click to collapse
That's my worry. Even Cyanogenmod, which as I understand it has the highest quality control, it still breaks things.
LG's "attempt" at Android maybe pretty poor but at least everything works. Still CM11 isn't "Stable" yet.
* Is it worth waiting for a Release Candidate or Stable build or would you say M4 is stable? I appreciate probably tricky to answer. My concern is I go to all the effort and something crucial (like Wifi) no longer works. Currently my G Pad works perfectly (just using the poor LG software).
* I understand M4 is considered more stable than the latest Nightly right?
Thanks
ruibing said:
4) Use this instructions for 4.4.2 stock
http://forum.xda-developers.com/showpost.php?p=52092510&postcount=110
Click to expand...
Click to collapse
Great, thanks, will do.
The CM team did a blog post on their release process. Google "cm-11-m4-post-release-items"
The reason why device maintainers don't do a M release for a device is often a judgement call since M releases are not just tagged/renamed nightlies as of CM11. A M4 was released so I would give that a shot.
LG software was just too different for me. I'd prefer for the OS (and hardware) to disappear so that I can focus on using the apps, and LG does its best to remind me I'm using its product.
I would just backup stock kernel and recovery with flashify before flashing TWRP and then backing up your stock rom in TWRP before flashing to anything else.
ruibing said:
The CM team did a blog post on their release process. Google "cm-11-m4-post-release-items". A M4 was released so I would give that a shot.
Click to expand...
Click to collapse
Thanks. That's a really useful blog in explaining what a Milestone release is. I'll give M4 a go. My only concern is I just know M5 will come out shortly after. I'm only intending to do this 1-2 times if I can help it, second time preferably being Stable.
ruibing said:
LG software was just too different for me. I'd prefer for the OS (and hardware) to disappear so that I can focus on using the apps, and LG does its best to remind me I'm using its product.
Click to expand...
Click to collapse
True.
The only thing LG have added that's really much use is QPair and MySMS (free on Google Play) is better than that anyway. LG's G Pad interface needs refinement, the e-mail app is poor too. I don't mind OEM Android modifications as a general rule though. I'm perfectly happy with TouchWiz on my Galaxy S4.
ruibing said:
I would just backup stock kernel and recovery with flashify before flashing TWRP and then backing up your stock rom in TWRP before flashing to anything else.
Click to expand...
Click to collapse
Is it easy enough to backup the LG G Pad stock ROM so if need be I can revert back?
Finally when your best guess on CM11 Release Candidate or Stable? Obviously best guess only. Thanks again.
bradavon said:
Thanks. That's a really useful blog in explaining what a Milestone release is. I'll give M4 a go. My only concern is I just know M5 will come out shortly after. I'm only intending to do this 1-2 times if I can help it, second time preferably being Stable.
Click to expand...
Click to collapse
You mean M6? I don't they ever retroactively release builds.
bradavon said:
True.
The only thing LG have added that's really much use is QPair and MySMS (free on Google Play) is better than that anyway. LG's G Pad interface needs refinement, the e-mail app is poor too. I don't mind OEM Android modifications as a general rule though. I'm perfectly happy with TouchWiz on my Galaxy S4.
Click to expand...
Click to collapse
I do miss QRemote (IR blaster). It's the only thing you can't replace (at least not yet) on custom ROMs.
bradavon said:
Is it easy enough to back the LG G Pad stock ROM so if need be I can revert back?
Finally when your best guess on CM11 Release Candidate or Stable? Obviously best guess only. Thanks again.
Click to expand...
Click to collapse
You can go back by going to recovery and restoring your backup. If you backup your stock recovery in flashify, you can restore that too afterwards.
You may want to ask someone on the official or infected_ CM threads about the next RC/stable. However, the snapshots are pretty much monthly (within first two weeks of every month). So hopefully the maintainers decide to do the M6 release.
ruibing said:
You mean M6? I don't they ever retroactively release builds.
Click to expand...
Click to collapse
I probably do. I was thinking M5 for G Pad may still come but it's probably to late now. I'll wait to see if M6 appears before trying M4 now. M4 will be 2 months old by that point :-|
ruibing said:
I do miss QRemote (IR blaster). It's the only thing you can't replace (at least not yet) on custom ROMs.
Click to expand...
Click to collapse
I heard that. Thankfully I prefer using the original remote than a phone or tablet.
ruibing said:
You can go back by going to recovery and restoring your backup. If you backup your stock recovery in flashify, you can restore that too afterwards.
Click to expand...
Click to collapse
Ah so backing up your stock recovery and stock image are two different things?
ruibing said:
You may want to ask someone on the official or infected_ CM threads about the next RC/stable. However, the snapshots are pretty much monthly (within first two weeks of every month). So hopefully the maintainers decide to do the M6 release.
Click to expand...
Click to collapse
Thanks. Will do.
Hey, been runnig the M4 release for the last month, got an auto update to the m5, which ive been running for the last few weeks, been stable, no problems so far, no idea why the release isnt listed on the cyanogen site.
bradavon said:
Ah so backing up your stock recovery and stock image are two different things?
Click to expand...
Click to collapse
You usually override the stock recovery with TWRP (or CWM) before you reboot to recovery to backup then flash over your stock rom. In other words, you are backing up your stock rom through TWRP as your recovery, you've already lost your stock recovery. When you restore your stock rom, you will still have TWRP as your recovery. It may cause an issue if you try to install a future LG OTA update.
On the other hand, correct me if I'm wrong, but I believe you can use stock recovery backups from other users.
nibzzz said:
Hey, been runnig the M4 release for the last month, got an auto update to the m5, which ive been running for the last few weeks, been stable, no problems so far, no idea why the release isnt listed on the cyanogen site.
Click to expand...
Click to collapse
Thanks. That's great news. I may still wait for M6 now, not being long away now though. Definitely good to read though.
ruibing said:
You usually override the stock recovery with TWRP (or CWM) before you reboot to recovery to backup then flash over your stock rom. In other words, you are backing up your stock rom through TWRP as your recovery, you've already lost your stock recovery. When you restore your stock rom, you will still have TWRP as your recovery. It may cause an issue if you try to install a future LG OTA update.
Click to expand...
Click to collapse
And I can use Flashify instead of TWRP or CWM? Is Flashify stable/easy to use? Thanks again.
nibzzz said:
Hey, been runnig the M4 release for the last month, got an auto update to the m5, which ive been running for the last few weeks, been stable, no problems so far, no idea why the release isnt listed on the cyanogen site.
Click to expand...
Click to collapse
Could you let me know if you've had any problems with either M4 or M5 in these areas? -
1. Wireless
2. Bluetooth
3. GPS
4. Crashing
5. Slowness
5. Random Reboots
Thanks
p.s - Thanks for the screenshots. It's great to see the Multi-task button present and correct. I'm always using it and holding down Home is such a pain.
bradavon said:
Could you let me know if you've had any problems with either M4 or M5 in these areas? -
1. Wireless
2. Bluetooth
3. GPS
4. Crashing
5. Slowness
5. Random Reboots
Thanks
p.s - Thanks for the screenshots. It's great to see the Multi-task button present and correct. I'm always using it and holding down Home is such a pain.
Click to expand...
Click to collapse
Hey, no problems with wifi, I run Spotify with a set of bluetooth speakers off into problems, also no crashes or random reboots. I think it's def faster than stock rom and yes the standard buttons are sooo much better, but I think it's perceptibly slower compared to the nex 5, doesn't bother me though, il try post a benchmark later. Also flashify works great, it's not a substitute for Cwm or twrp, just let's you send and queue commands to recovery from an app, so u still need a custom recovery with it.
Antutu on cm11 m5, no other mods. looks pretty good! Interested to see the difference with stock rom? Could anyone post stock? Cheers!
nibzzz said:
Hey, no problems with wifi, I run Spotify with a set of bluetooth speakers off into problems, also no crashes or random reboots. I think it's def faster than stock rom and yes the standard buttons are sooo much better
Click to expand...
Click to collapse
Great stuff. Thank you again. I can wait a wee while longer for M6 now but will definitely be "upgrading".
nibzzz said:
Antutu on cm11 m5, no other mods. looks pretty good! Interested to see the difference with stock rom? Could anyone post stock? Cheers!
Click to expand...
Click to collapse
Are you running AnTuTu 4.4? Did you restart the G Pad before you ran the test? (I did). As oddly my LG G Pad 8.3 (UK Wifi Only model) running Android 4.4.2 OTA from LG (no mod/root or anything) is higher -
p.s - I'd expect the Nexus 5 to be faster, it's got a newer generation Snapdragon CPU.
Second run: 26917
Third run: 26172
bradavon said:
Great stuff. Thank you again. I can wait a wee while longer for M6 now but will definitely be "upgrading".
Are you running AnTuTu 4.4? Did you restart the G Pad before you ran the test? (I did). As oddly my LG G Pad 8.3 (UK Wifi Only model) running Android 4.4.2 OTA from LG (no mod/root or anything) is higher -
p.s - I'd expect the Nexus 5 to be faster, it's got a newer generation Snapdragon CPU.
Click to expand...
Click to collapse
Yep antutu 4.4, consistently get 25200's, not much higher, even after a reboot run, interesting that stock scores higher!
Now CM11 M6 is out, I have a few questions please:
1. Should I first install Flashify to backup my Stock Recovery?
2. If so, where do I find Flashify?
3. Then ClockworkMod Recovery?
4. Then perform a Nandroid backup using ClockworkMod Recovery?
5. If I did want to Restore my Original Stock ROM, is it simply a case of going into Recovery and restoring it?
I want to be sure I can revert back to exactly how my LG G Pad is now before installing CM11 M6. If I end up doing this, I'm overly bothered if I need to Factory Reset after/before restoring the stock image though.
Thanks
bradavon said:
Now CM11 M6 is out, I have a few questions please:
1. Should I first install Flashify to backup my Stock Recovery?
2. If so, where do I find Flashify?
3. Then ClockworkMod Recovery?
4. Then perform a Nandroid backup using ClockworkMod Recovery?
5. If I did want to Restore my Original Stock ROM, is it simply a case of going into Recovery and restoring it?
I want to be sure I can revert back to exactly how my LG G Pad is now before installing CM11 M6. If I end up doing this, I'm overly bothered if I need to Factory Reset after/before restoring the stock image though.
Thanks
Click to expand...
Click to collapse
1) Always good idea to backup everything. If you backup your stock recovery before installing a new recovery image, it makes going back to full stock easier.
2) It's on the app store.
3) I don't think CWM supports this tablet anymore. Use TWRP 2.7.0.1
4) Yes, backup your system, data, and boot, then do a factory reset (in TWRP), and then flash the new rom.
5) Yes. Then if you want to restore the stock recovery (if you backed it up), do it through flashify.
---------- Post added at 11:23 AM ---------- Previous post was at 11:18 AM ----------
Here's the exact process I went through (I posted it somewhere awhile ago). Keep in mind I came from stock 4.2.2. If you come from stock 4.4.2, you need to use the ioroot method to root.
0) Download custom rom, twrp, and gapps to SD card
1) Rooted it using Kingo Android Root
2) Installed flashify
3) Backed up stock recovery using flashify
4) Flashed TWRP recovery using flashify
5) Rebooted to recovery
6) Backed up boot, system, and data
8) Wipe data, cache, etc (factory reset)
7) Flashed custom rom then gapps
9) Wipe cache
10) Reboot
Restore
0) Reboot to recovery
1) If you want to backup your custom rom, back up boot, system, and data
2) Restore boot, system, and data from your stock backup
3) Wipe cache
4) Reboot
5) If you want to restore stock recovery, restore using flashify
6) If you want to unroot, either use the root tool or flash back to stock 4.2.2 (http://forum.xda-developers.com/showthread.php?p=51466025)
ruibing said:
2) It's on the app store.
Click to expand...
Click to collapse
Firstly thanks for such a detailed and helpful post.
This is Flashify right? - https://play.google.com/store/apps/details?id=com.cgollner.flashify
ruibing said:
Keep in mind I came from stock 4.2.2. If you come from stock 4.4.2, you need to use the ioroot method to root.
Click to expand...
Click to collapse
Yes I've upgraded my G Pad OTA from 4.2.2 to 4.4.2, so noted thanks. Do you have to root the G Pad? This guide doesn't mention it:
http://true-android.blogspot.co.uk/2013/12/update-lg-g-pad-83-v500-to-android-442.html
It even says: "NOTE: Root is turned off by default in CM ROMs". Although I see I'd need to root for Flashify anyway.
ruibing said:
6) If you want to unroot, do a factory reset (in the settings menu)
Click to expand...
Click to collapse
It's really that simple?
Thanks again.
Just a word to say that my E980 got softbricked just after flashing the new [20140920]VUPMP.GPRO.sG3.Stable from datphu2811 ROM .
I did not restore stock rom before flashing. I came from CM 10.2, did wipe every cache and flashed from CWM recovery.
I am trying to recover using these steps now.
Thank you
pzkfwg said:
Just a word to say that my E980 got softbricked just after flashing the new [20140920]VUPMP.GPRO.sG3.Stable from datphu2811 ROM .
I did not restore stock rom before flashing. I came from CM 10.2, did wipe every cache and flashed from CWM recovery.
I am trying to recover using these steps now.
Thank you
Click to expand...
Click to collapse
Follow each step by it's directions and it will get you back for sure. I've softbricked a few times myself and that method got me up and back on my feet again.
If you need any help you are welcome to ask.
Snepsts said:
Follow each step by it's directions and it will get you back for sure. I've softbricked a few times myself and that method got me up and back on my feet again.
If you need any help you are welcome to ask.
Click to expand...
Click to collapse
Thank you for your support. I managed to restore stock ROM. Back to the basics of rooting again
pzkfwg said:
Thank you for your support. I managed to restore stock ROM. Back to the basics of rooting again
Click to expand...
Click to collapse
Good stuff! If you're in the business of stock ROMs I suggest Bountyman's G3 port, it's really nice if you can get the darn thing to deep sleep. Otherwise if you're looking at CM11 ROMs, Beanstalk, PAC, and Gummy are great choices. Along with the E980 Kernel+
Snepsts said:
Good stuff! If you're in the business of stock ROMs I suggest Bountyman's G3 port, it's really nice if you can get the darn thing to deep sleep. Otherwise if you're looking at CM11 ROMs, Beanstalk, PAC, and Gummy are great choices. Along with the E980 Kernel+
Click to expand...
Click to collapse
Thanks for the tips. I am looking for the most stable ROM, but yet recent enough. I have been happy with CM 10.2 for 6 months or so, but now I am starting to get problems (battery "leaks", power button not always responding) so I figured that I would check on the latest. I will try the G3 ports as they may be better adapted to the hardware capabilities of the G Pro (e.g.: Quick memo button).
I have seen my error by reading the later posts with the ROM that soft bricked my phone. I needed to select Phil's recovery instead of keeping mine during installation. I'll give another try.
I flashed a couple of ROMs in the past and have become too comfortable. I had no idea that I could brick a phone and yet recover it! Thanks engineers of the world for that last line of defense!
EDIT: Even with Philz recovery and going from the stock ROM, I always soft-brick my phone with datphu2811's ROM. I'll try Bountyman now.
pzkfwg said:
Thanks for the tips. I am looking for the most stable ROM, but yet recent enough. I have been happy with CM 10.2 for 6 months or so, but now I am starting to get problems (battery "leaks", power button not always responding) so I figured that I would check on the latest. I will try the G3 ports as they may be better adapted to the hardware capabilities of the G Pro (e.g.: Quick memo button).
I have seen my error by reading the later posts with the ROM that soft bricked my phone. I needed to select Phil's recovery instead of keeping mine during installation. I'll give another try.
I flashed a couple of ROMs in the past and have become too comfortable. I had no idea that I could brick a phone and yet recover it! Thanks engineers of the world for that last line of defense!
EDIT: Even with Philz recovery and going from the stock ROM, I always soft-brick my phone with datphu2811's ROM. I'll try Bountyman now.
Click to expand...
Click to collapse
Philz has constant softbrick issues with me. I use mack's hacked TWRP with Loki support. Have you tried that yet?
Snepsts said:
Philz has constant softbrick issues with me. I use mack's hacked TWRP with Loki support. Have you tried that yet?
Click to expand...
Click to collapse
I managed to install TWRP instead and install the ROM (Bounty's) but got other problems with LG's logo screen stuck. Finally, I also got it solved by flashing this modem instead of this one. Both were put in the instructions.
This is by far the most difficult rom installation I have ever made, and I installed quite a few in the past!
pzkfwg said:
I managed to install TWRP instead and install the ROM (Bounty's) but got other problems with LG's logo screen stuck. Finally, I also got it solved by flashing this modem instead of this one. Both were put in the instructions.
This is by far the most difficult rom installation I have ever made, and I installed quite a few in the past!
Click to expand...
Click to collapse
Yeah the G3 ROM doesn't like to boot without Mack's kernel, and the modem is nice with deep sleep.
Just a question, what ROMs have you flashed in the past?
Hello, i tried to OTA update my op3 from oficial CM13 nighly to oficial CM14 nighly and it did update.
but when i tried to enter TWRP recovery mode (i want to restore the backup because the new cm version has too many bugs) it wont open twrp, it stays in the op logo for some seconds and then a black screen appears and i have to restart my phone
i tried to reinstall twrp, intall stock recovery but nothing works, please help
If you had searched for your problem, you would have come across this: http://forum.xda-developers.com/oneplus-3/how-to/oos-3-5-2-comunity-build-t3461648/post68691560#post68691560. Reflash it in fastboot and it will work.
luigymarani said:
Hello, i tried to OTA update my op3 from oficial CM13 nighly to oficial CM14 nighly and it did update.
but when i tried to enter TWRP recovery mode (i want to restore the backup because the new cm version has too many bugs) it wont open twrp, it stays in the op logo for some seconds and then a black screen appears and i have to restart my phone
i tried to reinstall twrp, intall stock recovery but nothing works, please help
Click to expand...
Click to collapse
Are you running official TWRP? CM14.1 requires modified TWRP and I believe most people are using version 23 (Credits to @eng.stk) for CM14.1.
nitros12 said:
If you had searched for your problem, you would have come across this: http://forum.xda-developers.com/oneplus-3/how-to/oos-3-5-2-comunity-build-t3461648/post68691560#post68691560. Reflash it in fastboot and it will work.
Click to expand...
Click to collapse
Thanks a lot! it worked
Hw4ng3r said:
Are you running official TWRP? CM14.1 requires modified TWRP and I believe most people are using version 23 (Credits to @eng.stk) for CM14.1.
Click to expand...
Click to collapse
Oh I didnt know that, thank you
Thank you for both asking the question and answering the question. If I had seen this topic earlier I wouldn't have wasted 5 f*cking hours. Thank you!
CM13 nightly to CM14 nightly ruined everything for me. Never doing dirty flash again.
DamianSewo said:
Thank you for both asking the question and answering the question. If I had seen this topic earlier I wouldn't have wasted 5 f*cking hours. Thank you!
CM13 nightly to CM14 nightly ruined everything for me. Never doing dirty flash again.
Click to expand...
Click to collapse
This is quite funny (obviously not to you and no offense) and sad, but people that have been used CM14.1 for a while have said the same thing for about 2 months now: "people coming to CM14.1 from 13 are in for a mess"
This is quite funny (obviously not to you and no offense) and sad, but people that have been used CM14.1 for a while have said the same thing for about 2 months now: "people coming to CM14.1 from 13 are in for a mess"
Click to expand...
Click to collapse
No offense taken. This is just what happens if you venture using MODs with limited knowledge
But the misery of updating hasn't ended yet. So now I have access to TWRP, and I had done a TWRP nand backup before going to CM14, but I found out this was from the Boot, System, EFS and System Image, but NOT from the 'data'. When I restore everything I have I do get back into CM13, but nothing is working and it's rebooting all the time. Completely useless. I just checked and both my data and sd-card are intact. So I don't understand why I am not just getting back to the state I was before starting the CM14 misery. Is this because files on the 'data' got changed when doing the OTA CM14 nightly?
I also tried first restoring the image and then putting the CM13 nightly that I came from on top of it. Same ****. Also tried other way around, first CM13 nightly from TWRP, and then the image restore ('data' excluded since I didn't have that) on top of it. Also no luck.
Anyone an idea how to get back to my CM13?
By now I have wasted a full working day. I regret ever installing CM14, I just want to get back to the situation yesterday with a working CM13... :crying:
DamianSewo said:
No offense taken. This is just what happens if you venture using MODs with limited knowledge
But the misery of updating hasn't ended yet. So now I have access to TWRP, and I had done a TWRP nand backup before going to CM14, but I found out this was from the Boot, System, EFS and System Image, but NOT from the 'data'. When I restore everything I have I do get back into CM13, but nothing is working and it's rebooting all the time. Completely useless. I just checked and both my data and sd-card are intact. So I don't understand why I am not just getting back to the state I was before starting the CM14 misery. Is this because files on the 'data' got changed when doing the OTA CM14 nightly?
I also tried first restoring the image and then putting the CM13 nightly that I came from on top of it. Same ****. Also tried other way around, first CM13 nightly from TWRP, and then the image restore ('data' excluded since I didn't have that) on top of it. Also no luck.
Anyone an idea how to get back to my CM13?
By now I have wasted a full working day. I regret ever installing CM14, I just want to get back to the situation yesterday with a working CM13... :crying:
Click to expand...
Click to collapse
Exactly, when I got my TWRP working again I tried to restore my backup (cm13) but it happened like you said, wouldn't work.
I had to clean flash a new cm13 rom :/
luigymarani said:
Exactly, when I got my TWRP working again I tried to restore my backup (cm13) but it happened like you said, wouldn't work.
I had to clean flash a new cm13 rom :/
Click to expand...
Click to collapse
Why were you unable to use your backup to restore CM13? In my case I didn't have a backup of the data-partition, which I think is the problem. But if you have a complete backup you should be able to get it back right? Isn't that the whole purpose of doing a backup before you update the ROM?
DamianSewo said:
Why were you unable to use your backup to restore CM13? In my case I didn't have a backup of the data-partition, which I think is the problem. But if you have a complete backup you should be able to get it back right? Isn't that the whole purpose of doing a backup before you update the ROM?
Click to expand...
Click to collapse
It should have worked, but it didn't. I have no idea why, it was a complete backup and everything in it was working perfectly so idk
luigymarani said:
It should have worked, but it didn't. I have no idea why, it was a complete backup and everything in it was working perfectly so idk
Click to expand...
Click to collapse
Okay so if you restored a complete backup and still wasn't able to get back to a working CM13 then we probably have exactly the same issue.
It could also be related to the TWRP version we have installed now, maybe the new TWRP is not able to handle CM13. Anyone here to comment on this?
DamianSewo said:
Okay so if you restored a complete backup and still wasn't able to get back to a working CM13 then we probably have exactly the same issue.
It could also be related to the TWRP version we have installed now, maybe the new TWRP is not able to handle CM13. Anyone here to comment on this?
Click to expand...
Click to collapse
Which TWRP version are you using? I flashed the 3.0.2.1-v23 and it supports cm13, because o already flashed a new cm13 rom and I'm using TWRP normally.
luigymarani said:
Which TWRP version are you using? I flashed the 3.0.2.1-v23 and it supports cm13, because o already flashed a new cm13 rom and I'm using TWRP normally.
Click to expand...
Click to collapse
I'm also using 3.0.2.1-v23. Trying to find any information that could help me have my CM13 TWRP image working again, but no luck so far