Related
Hi, just have a quick question that's been bugging me for a while now. If I have made a full backup using TWRP and I want to restore it, should I:
Fully wipe system and caches and then restore; or just restore right over my current ROM?
****, good question
Sent from my HTC One X using xda app-developers app
Restore takes care of wiping for you.
Piggybacking off the OP, sometimes when I try to restore my TWRP backup it fails, and then the only way I've found to get it working again is to do a boot loader factory reset, and then essentially start from scratch or load an older working backup. No problem, just a minor annoyance. Is there something I'm doing wrong or any advice someone can give me?
Sent from my HTC One X using xda app-developers app
Hydromea said:
Hi, just have a quick question that's been bugging me for a while now. If I have made a full backup using TWRP and I want to restore it, should I:
Fully wipe system and caches and then restore; or just restore right over my current ROM?
Click to expand...
Click to collapse
I always wipe everything before a restore, just in case
Better safe than sorry
Restoring a back up !
When restoring a back up from any recovery wipe everything just as if you were installing a new rom. Factory reset, cache, dalvik cache, system just to be safe. Factory reset wipes data and all cache but not system and if you do a factory reset and then try to wipe I think dalvik again you get an error but no harm done it just will not do it again. I usually do them all and then do the superwipe zip and that willl give you a good piece of mind that it is properly wiped. Also, I have noticed that using the external sd card seems to work best for installing roms or backing up and restoring back ups or anything else like mods or themes. Here is the superwipe zip in case anyone needs it.
Hydromea said:
Hi, just have a quick question that's been bugging me for a while now. If I have made a full backup using TWRP and I want to restore it, should I:
Fully wipe system and caches and then restore; or just restore right over my current ROM?
Click to expand...
Click to collapse
I've done both, but I like not having reinstall all my apps, and reset all my ringtone, and that goes with a full wipe. so when ever i can i flash over. Just make sure your slashing the same rom over the old one.
You shouldn't worry about losing ANYTHING on a backup when you do a factory reset, because the backup houses all of the data and settings anyway.
All you do is Factory Reset, Nandroid>Restore, and your old backup will flash everything the way it was when you did a backup in the first place. Factory Reset is always wise, especially when you're fiddling with different ROM's based on different kernels or systems (AOSP/Sense).
XNine said:
You shouldn't worry about losing ANYTHING on a backup when you do a factory reset, because the backup houses all of the data and settings anyway.
All you do is Factory Reset, Nandroid>Restore, and your old backup will flash everything the way it was when you did a backup in the first place. Factory Reset is always wise, especially when you're fiddling with different ROM's based on different kernels or systems (AOSP/Sense).
Click to expand...
Click to collapse
Ahh, this is true I recant my statement. I was mistakenly thinking about flashing a new ROM over an older version, not a buck-up. I feel stupid.
when restoring a nandroid if you've got the new HBoot I think you have to restore boot.img separately via fastboot. Is that right?
gunnyman said:
when restoring a nandroid if you've got the new HBoot I think you have to restore boot.img separately via fastboot. Is that right?
Click to expand...
Click to collapse
Nope. I just flashed a bunch of roms yesterday and did restores with no issue. I think if your using the stock rooted 2.2 you are correct, but any other rom a restore works fine.
Not Restoring = Bad Idea
Hydromea said:
Hi, just have a quick question that's been bugging me for a while now. If I have made a full backup using TWRP and I want to restore it, should I:
Fully wipe system and caches and then restore; or just restore right over my current ROM?
Click to expand...
Click to collapse
I have made the mistake of not wiping everything (excluding sd card) when changing ROMs or when restoring from a backup. This may be a little different because it was when I was switching to a new ROM on my brother's phone, but I tried to take the lazy way out and not restore everything. I really didn't feel like redownloading everything. I soon learned that this was a mistake, and his "phone" app suddenly disappeared. He was also unable to send or receive texts. This soon made the process even longer than I wished it to be because I needed to go back and restore everything again and get it back to normal.
Error While Restoring using twrp
I took a back up of everything using TWRP and then when i tried to restored its giving me error while restoring system E:Unable to extract tar archive . Please help
Are you trying to restore a backup from a different version of TWRP? For example, currently running 2.7.0.8 but backup was originally made using 2.3.3.1?
Sent from my Evita
error on backup restore twrp
hi i have a nexus 4 running 6.0.1 reserection remix, however when i do a backup on twrp then transfer
it to my pc its fine, but when i restore it it not going as a zip and its giving me this error, could not find meta-inf/com/google/android/update-binary' in the zip file. error installing zip file/sdcard/twrp/backups/01c237769c62991c.zip please help, thanks
Become a member of the w
WOW! After a good 3/4 days of frustration, thinking I had ruined my device, I finally got my TWRP backup to restore.
It's my first time using this software and the restoration process is truly amazing. I mean, my test messages were still there, even my browser history and last page loaded up in chrome were still there. I'm blown away.
The strange thing is that It didn't work when all 3 partitions were selected. When I tried it this way (as per the many step by step instructions that I read) my phone would load up a black screen with just the notification bar visible. I'd see my voicemail, sms, wifi and battery icons at the top, but absolutely nothing else except for a myriad of pop ups that read 'Unfortunately [app name] has stopped working'.
So I bit the bullet and did some trial and error with the partitions.
Turns out that when I only selected 2 of the 3 (I believe they were 'Boot', 'Data' and deselected 'System') everything loaded up just as it was before the backup, except there were only the stock apps available and no google services at all. .....Very odd.
So I did the boot to recovery method before turning the phone off (vol. up - Home - Power) which restarted the phone and strangely brought back EVERYTHING as mentioned at the start of this post.
You can probably understand my confusion here and while I'm VERY happy that it all worked out, I don't understand why it worked with only 2 of the partitions but not with the recommended 3 of them?
Can anyone shed any light on this?
---------- Post added at 01:16 PM ---------- Previous post was at 01:02 PM ----------
debmikeshan said:
hi i have a nexus 4 running 6.0.1 reserection remix, however when i do a backup on twrp then transfer
it to my pc its fine, but when i restore it it not going as a zip and its giving me this error, could not find meta-inf/com/google/android/update-binary' in the zip file. error installing zip file/sdcard/twrp/backups/01c237769c62991c.zip please help, thanks
Become a member of the w
Click to expand...
Click to collapse
Hmmm. I'm definitely no pro at this stuff, in fact i'm very new when it comes to using TWRP, but this is what happened with me.
First of all, the backup that I did was simply a folder of files, not zip.
Transferred that do my PC, wiped my phone with TWRP and replaced the backup folder back into the TWRP/Backup folder. However, after reading up on how to restore on about 10 different android sites/forums, only 1 post shared the most vital piece of information.
You folder has to be in the 'serial' number folder that's located in the 'Backup' folder for TWRP.
When I put my backup folder just into the TWRP/Backup folder, the Restore section would only see the folder itself but the partitions were not available/listed for selection.
Once I placed my Backup folder into the TWRP/Backup/e1oog75 (that alphanumeric name is just a random example made for visual clarity) folder, my partitions were visible and available for selection right away.
Hopefully this helps somewhat.
Hi Folks.
Ok here is my situation, I have a rooted and unlocked TF700.
I flashed Zeus 4 and all worked well, then flashed (after full wipe) PARANOIDANDROID 2.15 and again everything was great,
Yesterday I flashed Baked Bean 4 (again after a full wipe) and apart from some SD issues all seemed ok,
I then decided to restore my TWRP backup of Zeus as I needed to use my 64gig msd card.
After a full wipe and restore Zeus started up but the dpi was messed up (160) I think (way small)
I was seeing loads of FC's and file manager showed my internal SD as being empty. Rebooted to recovery and tried the "Format Data" option
It failed right away with this message "E: Unable to format data."
I have tried flashing the stock .26 rom via TWRP and I have the same issue, dpi set to 160 and internal sd not mounted.
It seems my Internal sd is corrupt
What is the procedure to reformat it via ADB or fastboot? (I have searched but the results I found relate to other devices and I dont want to simply follow instructions that might cause further harm to my TF700)
I have followed the NVflash brick proof procedure and have all relevant files backed up (I did this before flashing the last 2 roms)
Please can some one point me in the right direction
Thanks a lot
Jules
I always wipe cache, system, internal, davic and then do a factory reset.
Sent from my SAMSUNG-SGH-I717 using xda app-developers app
When you said that you tried to flash the stock .26 you meant installing not restoring a backup, right? What rom you have on your device right now?
Pretoriano80 said:
When you said that you tried to flash the stock .26 you meant installing not restoring a backup, right. What rom you have on your device right now?
Click to expand...
Click to collapse
Yip extracted the zip from the zip file and copied it to my ext sd and flashed it via TWRP
I have an unusable Zeus4,
Im about to try a full wipe again and then flash .26 again
EDIT
After flashing .26 and selecting reboot I get the "No OS installed! Are you sure you wish to reboot?" message
Looks like the system partition is corrupted, but i'm not sure. I think you should come here on IRC and maybe someone with more experience will help you - - http://webchat.freenode.net/?channels=asus-transformer
Thanks so much Pretoriano80!
With his help on IRC I was able to solve the problem,
In the end I had to return to complete stock, It seems CM10 caused some problems,
You are a a legend dude Thanks!!
:good:
ZaJules said:
Thanks so much Pretoriano80!
With his help on IRC I was able to solve the problem,
In the end I had to return to complete stock, It seems CM10 caused some problems,
You are a a legend dude Thanks!!
:good:
Click to expand...
Click to collapse
This same thing happened to me with my Prime when I was getting ready to send it off for RMA because of a broken HDMI port. Since I was unlocked I was advised to restore to stock before sending it in. However, before I got the chance to do that I started getting the "E: Unable to format data." error that you were. I ended up erasing all partitions from fastboot and putting a note in the box that it wouldn't boot after an OTA. I managed to get away with it and wasn't charged for fixing it
For future reference it would be really helpful to know how you fixed this. Did you do something like what is in this thread: http://forum.xda-developers.com/showthread.php?t=1803343.
Did you ever figure out how CM10 messed up your Infinity? I was running CM9 on my Prime when I got this error. Thanks!
It's hard to say if it was CM10 (or any other custom rom) or TWRP to mess the things up but we managed to get back to stock by replacing the twrp with CWM recovery and installing a modified .30 update package. Was a tricky one but we didn't had to mess with the partitions and that's good.
Pretoriano80 said:
It's hard to say if it was CM10 (or any other custom rom) or TWRP to mess the things up but we managed to get back to stock by replacing the twrp with CWM recovery and installing a modified .30 update package. Was a tricky one but we didn't had to mess with the partitions and that's good.
Click to expand...
Click to collapse
Why did you switch to CWM? Do you have any thoughts on the advantages and disadvantages of TWRP vs CWM?
paddycr said:
Why did you switch to CWM? Do you have any thoughts on the advantages and disadvantages of TWRP vs CWM?
Click to expand...
Click to collapse
Switched to CWM just to make sure it wasn't twrp recovery that somehow was failing to flash the partitions correctly. Tbh so far both do their job and both share the same limitation so far, meaning both fail to restore the boot partition (kernel) so in order to restore successfully (from a nandroid backup) you need to flash the right kernel after restoring is done. Otherwise i like TWRP better and never had issues with it, but i miss the advanced option from CWM, the one that let you format each partition individually.
Pretoriano80 said:
Switched to CWM just to make sure it wasn't twrp recovery that somehow was failing to flash the partitions correctly. Tbh so far both do their job and both share the same limitation so far, meaning both fail to restore the boot partition (kernel) so in order to restore successfully (from a nandroid backup) you need to flash the right kernel after restoring is done. Otherwise i like TWRP better and never had issues with it, but i miss the advanced option from CWM, the one that let you format each partition individually.
Click to expand...
Click to collapse
I'm not certain what you're referring to here. I've restored many times from different TWRP backups (for each custom rom that successfully boots and is half-decent, I make and keep a backup in case I want to jump around and try new things) and I've never had any issues. I am still on the .26 firmware update because I plan to do the nvflash thing. Are you saying that between Zeus v4 (ICS) and various Jelly Bean roms I've been on the same kernel? I gues I just haven't checked.
Anyway, I really love the TWRP recovery and use it with Xoom and Nexus 7 as well. It's so easy to use and always has been reliable.
okantomi said:
I'm not certain what you're referring to here. I've restored many times from different TWRP backups (for each custom rom that successfully boots and is half-decent, I make and keep a backup in case I want to jump around and try new things) and I've never had any issues. I am still on the .26 firmware update because I plan to do the nvflash thing. Are you saying that between Zeus v4 (ICS) and various Jelly Bean roms I've been on the same kernel? I gues I just haven't checked.
Anyway, I really love the TWRP recovery and use it with Xoom and Nexus 7 as well. It's so easy to use and always has been reliable.
Click to expand...
Click to collapse
For me moving between various roms by just restoring a backup never worked like it should. Let's say i'm on CM10 and i want to restore from a stock rom backup, the restore process is done, after reboot the device gets stuck to the first Asus screen and will stay there. Now if i get back to recovery and flash an update. zip containing the stock kernel the device will boot just fine, so definitely the boot image doesn't get restored in my case (with . 26 bootloader ).
Edit: @okantomi: You are using the internal storage or a MicroSD for backup / restoring? I'm really curious how this could work for some and not work for others, i mean same device, same recovery, same bootloader version...
Pretoriano80 said:
For me moving between various roms by just restoring a backup never worked like it should. Let's say i'm on CM10 and i want to restore from a stock rom backup, the restore process is done, after reboot the device gets stuck to the first Asus screen and will stay there. Now if i get back to recovery and flash an update. zip containing the stock kernel the device will boot just fine, so definitely the boot image doesn't get restored in my case (with . 26 bootloader ).
Edit: @okantomi: You are using the internal storage or a MicroSD for backup / restoring? I'm really curious how this could work for some and not work for others, i mean same device, same recovery, same bootloader version...
Click to expand...
Click to collapse
Ok, I only flash a new zip from the internal storage...made myself a "Flashworthy" folder which I keep stocked with newest versions of roms/gapps. I save my TWRP backups to my external microsdcard, as well as my TiBu backups. I have never had a problem restoring from TWRP this way, honestly.
okantomi said:
Ok, I only flash a new zip from the internal storage...made myself a "Flashworthy" folder which I keep stocked with newest versions of roms/gapps. I save my TWRP backups to my external microsdcard, as well as my TiBu backups. I have never had a problem restoring from TWRP this way, honestly.
Click to expand...
Click to collapse
Well, in this case i really have no clue why restoring works for some users but not for all.Dees_Troy, the dev behind Twrp recovery told me that .26 bootloader is to blame for the recovery failing to restore the boot partition, but looks like you have that bootloader version and restoring works good for you... interesting.
Pretoriano80 said:
Well, in this case i really have no clue why restoring works for some users but not for all.Dees_Troy, the dev behind Twrp recovery told me that .26 bootloader is to blame for the recovery failing to restore the boot partition, but looks like you have that bootloader version and restoring works good for you... interesting.
Click to expand...
Click to collapse
It is a mystery. Is there any other info that might be relevant to see why the difference in results? I ask because I would like to understand this device better, as well as potentially help others.
okantomi said:
It is a mystery. Is there any other info that might be relevant to see why the difference in results? I ask because I would like to understand this device better, as well as potentially help others.
Click to expand...
Click to collapse
I don't know, maybe the twrp version and the backup options, like if you are using compression or not, which partitions do you backup (boot, system, data, recovery, cache)...
Pretoriano80 said:
I don't know, maybe the twrp version and the backup options, like if you are using compression or not, which partitions do you backup (boot, system, data, recovery, cache)...
Click to expand...
Click to collapse
I'm using TWRP 2.2.2.1, I back up boot, system and data only, and I don't use compression.
Hey there!
I'm hoping that someone can help me out. My nephew who's a wanna-be geek was going to update my ROM (which didn't to be done really, but he wanted to show me what he was able to do). He went and downloaded the latest CM 11, rebooted and went into TWRP 2.7.0.1, did a factory reset, an advanced wipe, and did the Format Data. When he did that, it got stuck in a loop. Nothing happened. He tried to install the ROM he downloaded, and NOTHING! Long story short, by him doing the Format Data, he wiped out my partitions. TWRP, no matter what I try to do tells me it's unable to mount 'data' or 'media' etc. etc. Which is leading me to believe I have no partitions left. I've tried installing the latest update from Asus, and no dice. I've tried restoring backups that I have on my micro SD, and that's not working.
Can someone please help me and tell me how to fix this? Can I get my partitions back? I'm really hoping that I don't have to send this tablet off to Asus in Dallas, TX to have it repaired.
I'm using a loaner tablet from a rental store, hoping I can get my TF 300 fixed.
Any help is deeply and sincerely appreciated.
Omega
Sent from my SM-P600 using Tapatalk
I was about to suggest you look in the correct forum, but I see you posted there as well. Anyway, your partitions are probably okay, they have just been wiped out, that doesn't mean you lost them. Have you tried reflashing the recovery? Were you able to flash anything with said recovery before that? Wiping the partitions in the recovery shouldn't have any effect on the flashing functionality, no matter which partitions were selected (except for sdcard, since that's where the ZIPs are stored), so there might be a problem with the recovery itself. Are you sure you have the correct one for your device?
Duchman said:
I was about to suggest you look in the correct forum, but I see you posted there as well. Anyway, your partitions are probably okay, they have just been wiped out, that doesn't mean you lost them. Have you tried reflashing the recovery? Were you able to flash anything with said recovery before that? Wiping the partitions in the recovery shouldn't have any effect on the flashing functionality, no matter which partitions were selected (except for sdcard, since that's where the ZIPs are stored), so there might be a problem with the recovery itself. Are you sure you have the correct one for your device?
Click to expand...
Click to collapse
Hey there Duchman ...
Thanks for your reply. I have tried reflashing the recovery like you suggested. And after that tried to reinstall CM11.Afterwards reflashing the recovery it says “Unable to mount data." I don't know if I need to flash a more recent version of TWRP, if that would even help.
Before all of this happened I could flash almost any ROM of my choice as long as it was KitKat supported. All of my backups and restores are kept on my micro SD so they aren't accidentally deleted. As far as I know it's the correct version of TWRP. It's worked for me so far, ever since I updated to KitKat.
Sent from my SM-P600 using Tapatalk
Omega Recon said:
Hey there Duchman ...
Thanks for your reply. I have tried reflashing the recovery like you suggested. And after that tried to reinstall CM11.Afterwards reflashing the recovery it says “Unable to mount data." I don't know if I need to flash a more recent version of TWRP, if that would even help.
Before all of this happened I could flash almost any ROM of my choice as long as it was KitKat supported. All of my backups and restores are kept on my micro SD so they aren't accidentally deleted. As far as I know it's the correct version of TWRP. It's worked for me so far, ever since I updated to KitKat.
Sent from my SM-P600 using Tapatalk
Click to expand...
Click to collapse
You could try flashing a newer recovery first, I think 2.7.1.0 is available for your device. Also try doing a hard reset by cold booting - here's a how-to: https://www.youtube.com/watch?v=oTU38Ewh8qo (wipe the cache afterwards)
If that doesn't help, reverting to stock is probably your best option. Try this: http://forum.xda-developers.com/showthread.php?t=1757077 (be sure to grab the correct firmware and back up your files)
Have you tried installing any other custom ROM? Does it give you the same error when you try to restore your backup?
Here's what I've come across so far. I did the reset, and that did nothing.
Tried to flash the stock version, after a few seconds, TWRP popped up with FAILED.
I've tried flashing Omni ROM. It will flash, load up, and gets stuck at the boot screen or boot animation. This happens with just about every ROM I try to flash.
Been looking for TWRP 2.7.1.0. I'm not seeing it listed on TWRPs site. Where can I get a copy? Thanks!
Sent from my SM-P600 using Tapatalk
Here you go: http://forum.xda-developers.com/showthread.php?t=2772093
Also do try flashing another recovery, PhilZ for instance: http://forum.xda-developers.com/showthread.php?t=2597860
Did you try wiping all of the partitions again?
So I was using Calkulin's stock 33R with AK kernel, which has been running fine. I deciced that I should try PA, so i did my regular thing of making a nandroid backup, wiping /data, /system and /cache. Flashed PA and the relevant Gapps, and got stuck on PA bootscreen. So I tried it again, and upon closer inspection, in, the flashing of Gapps failed because it was unable to find build.prop.
So I tried it all over again just with PA, no Gapps, no anything else. Same result, just the PA boot animation staring at me for over 20 minutes.
I then tried flashing Clakulin's stock again, and no luck, still stuck on OPO logo screen. I thought perhaps my partitions were messed up, so I wiped everything and flashed stock 33R from CM. Well, at least that booted and my EFS data was intact. I then tried reverting to Calkulin's stock by sideloading, and it never went past the boot screen.
Bottomline: I cannot use any ROM apart from stock 33R. Installing a kernel on top bootloops, installing root bootloops, installling a ROM bootloops, almost anything I flash bootloops. This is driving me nuts.
I am using the latest Philz recovery and my BL is unlocked. I am also a very seasoned flasher and I know what I am I am doing. Yet, this issue is boggling the crap outta me.. I know the solution is probably simple, yet I'm overseeing it.
PLS DON'T KILL ME FOR NOT PROVIDING A LOGCAT. I'll provide anything requested by those helping.
EDIT 1: When I say flash stock 33R, I am referring to the factory image provided by CM on their site. Also, remmeber the nandroid backup I made? That failed to restore. Yea, it failed hard on me.
EDIT 2: I remmeber reading in another device forum where his recovery was mounting the wrong partition when flashing, which makes sense since Philz's recovery produces an error where gapps can't find build.prob. I checked the recovery settings and the only mount I can change is SD from /media/0 to /media/
EDIT 3: I want to shoot the phone, and then myself.
Perhaps try using TWRP, just to rule it out?
EddyOS said:
Perhaps try using TWRP, just to rule it out?
Click to expand...
Click to collapse
Tried TWRP, no error on flashing the Gapps, but still stuck on boot animation.
If you flash the stock factory image does that work? I know you say you can 'use stock' but you don't say whether that was your backup or the factory image
EddyOS said:
If you flash the stock factory image does that work? I know you say you can 'use stock' but you don't say whether that was your backup or the factory image
Click to expand...
Click to collapse
I meant the stock factory image. My nan droid failed to restore.
I'm stumped cause if the factory image works so should everything else. Bizarre!
Hope you get it fixed soon, bud!
One last thought - I assume the md5s matched on the files you tried to flash, correct?
EddyOS said:
I'm stumped cause if the factory image works so should everything else. Bizarre!
Hope you get it fixed soon, bud!
One last thought - I assume the md5s matched on the files you tried to flash, correct?
Click to expand...
Click to collapse
All md5s matched with the files. It IS really bizzare indeed. I searched about this problem for several hours, even on other devices. But no luck!
Try an older factory image and let it boot and do all the ota updates and try then that's what i did
gavin-phelan said:
Try an older factory image and let it boot and do all the ota updates and try then that's what i did
Click to expand...
Click to collapse
Tried that too. Started off from 25, moved to 30 and still no luck.
Hi guys!
I got a G3 yesterday and decided to root it. I installed TWRP and decided to install Cloudy G3.
Immediately on boot, all services stop responding. There's a loop of popups saying things like "System UI has stopped responding." The same with download manager and other things. So I figured the rom didn't install properly. I went to my backup to restore it and TWRP doesn't have it listed. I looked in all directories I could (saved it initially to /sdcard/) but it's not there. The weird part is that when you click the restore button going into the list of your backups, my backup pops up for like a quarter of a second and goes away.
I decided to use TWRP's wipe function to do a system restore. It completed and now my android version is "Cloudy g3 2.5." So... System restore installed the rom? I'm just really confused at all of this. Anybody have any insight to the stuff I've mentioned?
it0ken said:
Hi guys!
I got a G3 yesterday and decided to root it. I installed TWRP and decided to install Cloudy G3.
Immediately on boot, all services stop responding. There's a loop of popups saying things like "System UI has stopped responding." The same with download manager and other things. So I figured the rom didn't install properly. I went to my backup to restore it and TWRP doesn't have it listed. I looked in all directories I could (saved it initially to /sdcard/) but it's not there. The weird part is that when you click the restore button going into the list of your backups, my backup pops up for like a quarter of a second and goes away.
I decided to use TWRP's wipe function to do a system restore. It completed and now my android version is "Cloudy g3 2.5." So... System restore installed the rom? I'm just really confused at all of this. Anybody have any insight to the stuff I've mentioned?
Click to expand...
Click to collapse
Did you use wipe before flashing the rom? If not that's Why you had the issue you didn't wipe. You MUST wipe when flashing a rom.
hyelton said:
Did you use wipe before flashing the rom? If not that's Why you had the issue you didn't wipe. You MUST wipe when flashing a rom.
Click to expand...
Click to collapse
Did not know that, and no I didn't. But I appreciate you letting me know that, probably some volatile information I should've been aware of.
May I ask why the device fixed the CloudyG3 rom when I did wipe it? I thought wiping through TWRP sends the phone back to factory settings, but it just fixed the rom and booted fine.
it0ken said:
Did not know that, and no I didn't. But I appreciate you letting me know that, probably some volatile information I should've been aware of.
May I ask why the device fixed the CloudyG3 rom when I did wipe it? I thought wiping through TWRP sends the phone back to factory settings, but it just fixed the rom and booted fine.
Click to expand...
Click to collapse
Your welcome
It wiped your current install, current rom being cloudy it reset it to factory settings. Doing a wipe won't put you back to stock.
hyelton said:
Your welcome
It wiped your current install, current rom being cloudy it reset it to factory settings. Doing a wipe won't put you back to stock.
Click to expand...
Click to collapse
Ah, so flashing the stock lg firmware would be the only way to send a device back to factory settings? I'm enjoying this learning process for sure.
it0ken said:
Ah, so flashing the stock lg firmware would be the only way to send a device back to factory settings? I'm enjoying this learning process for sure.
Click to expand...
Click to collapse
Correct