Related
Is it safe to update the phone when it is root?sorry for the spelling , but if you write it indifferent whether a software update from the position of the phone or disaster recovery software with ROOT? 2.3 update has come out and my O3D once landed in the service, except that if I had a root and CWM!
I just want to update your phone now and root V10b
No you must go back to your original stock rom and unroot your phone for the update to succeed and work properly.
syberka said:
Is it safe to update the phone when it is root?sorry for the spelling , but if you write it indifferent whether a software update from the position of the phone or disaster recovery software with ROOT? 2.3 update has come out and my O3D once landed in the service, except that if I had a root and CWM!
I just want to update your phone now and root V10b
Click to expand...
Click to collapse
Pretty sure you can update if you have root, but not if you have CWM.
not really too sure about what you're saying, but did you just say 2.3 update has come out?
Has come out in October! I ask what I can only update with ROOT
Jak masz tylko rota to można(ja robiłem tak update), ale dla pewnościbym zrobiłbym unroot
If you have only root without CWm it is safe, but unroot is very fast
How can I remove CWM from my phone?
Questions or Problems Should Not Be Posted in the Development Forum
Please Post in the Correct Forums and Read THIS
Moving to General
Just Try It
I would just give it a shot - there are tutorials on how to unbrick your phone and they are relatively straight forward - lucky there are no locks on this phone so that is a good thing
So how exactly can we put the original recovery back on?
I am not encouraging anyone but in my experience I have flashed many times using LG recovery with both root and CWM without any issues.
kidkoala_uk said:
I am not encouraging anyone but in my experience I have flashed many times using LG recovery with both root and CWM without any issues.
Click to expand...
Click to collapse
But there might be a difference between restore and update. Update should try to keep your settings and restore should intentionally overwrite just everything in /system
edehahn said:
But there might be a difference between restore and update. Update should try to keep your settings and restore should intentionally overwrite just everything in /system
Click to expand...
Click to collapse
Personally I dont mind about settings being kept when I flash a new ROM, I start from scratch intentionally although that would not suit alot of people who would prefer to update is does not bother me. When you flash a new ROM through CWM you wipe the data prior to flash so you are not updating anyway.
Edit: Just to be clear I am not talking about updating but performing a full recovery to the latest ROM relased by your provider, I would not suggest anyone performs an update using LG tool with CWM installed.
Sorry for my slow thinking, if i do root "superoneclick" and few days later i do unroot, is my phone will be in identical state as before root?
Ie. After unroot can i giveaway my O3D to service or with clean conscience can i do update from phone menu?
Yes you can update while rooted, but you cannot update while you are running a custom rom
kidkoala_uk said:
Personally I dont mind about settings being kept when I flash a new ROM, I start from scratch intentionally although that would not suit alot of people who would prefer to update is does not bother me. When you flash a new ROM through CWM you wipe the data prior to flash so you are not updating anyway.
Edit: Just to be clear I am not talking about updating but performing a full recovery to the latest ROM relased by your provider, I would not suggest anyone performs an update using LG tool with CWM installed.
Click to expand...
Click to collapse
Hi Kidkoala_uk,
Will the CWM removed when I reset the phone back to the factory default setting? Thanks.
kidkoala_uk said:
Edit: Just to be clear I am not talking about updating but performing a full recovery to the latest ROM relased by your provider, I would not suggest anyone performs an update using LG tool with CWM installed.
Click to expand...
Click to collapse
sure .. it's just how I explain it might recovery does work with CWM and root installed (I did it twice) and update seems to brick phones (I did not try)
---------- Post added at 08:54 AM ---------- Previous post was at 08:50 AM ----------
RayHK said:
Hi Kidkoala_uk,
Will the CWM removed when I reset the phone back to the factory default setting? Thanks.
Click to expand...
Click to collapse
No .. factory reset will not remove CWM. Factory reset = erase everything in /data (and since cache and dalvik cache are inside /data there is no need to do a wipe cache)
(full recovery using the LG tool will remove CWM)
Thank You for Your answer.
Two more question, if i can ask:
- Can I turn off "debug mode" after root?
- Is "Debug mode" use some resources, so am i speedup my phone turning off "debug mode"?
Yes u can turn off debug mode after root.
Disabling debug mode don't speed up your phone
edehahn said:
sure .. it's just how I explain it might recovery does work with CWM and root installed (I did it twice) and update seems to brick phones (I did not try)
---------- Post added at 08:54 AM ---------- Previous post was at 08:50 AM ----------
No .. factory reset will not remove CWM. Factory reset = erase everything in /data (and since cache and dalvik cache are inside /data there is no need to do a wipe cache)
(full recovery using the LG tool will remove CWM)
Click to expand...
Click to collapse
Thanks edehahn.
edehahn said:
sure .. it's just how I explain it might recovery does work with CWM and root installed (I did it twice) and update seems to brick phones (I did not try)
---------- Post added at 08:54 AM ---------- Previous post was at 08:50 AM ----------
No .. factory reset will not remove CWM. Factory reset = erase everything in /data (and since cache and dalvik cache are inside /data there is no need to do a wipe cache)
(full recovery using the LG tool will remove CWM)
Click to expand...
Click to collapse
Is "full recovery using the LG tool" mean emergency recovery mode which is accessed by doing what is in the attache image below?
Hi everyone,
I have a samsung tab 2 p3100 with me. I used to flash a lot on my tab and try different roms on it. But lately i faced this very uncommon problem when i flashed a purebean hdv2 rom on my tab. After using it for a few days i tried to flash a new one. So I made a titanium backup of my apps at night and in the morning my tab started rebooting as soon as i change any setting. It's like it's stuck on the same data, apps and setting as it was at night. Tab would restart in 10 seconds of usage. And even if i try to change any setting or remove an app in those 10 sec, everything comes back to the same condition after a reboot. I can't format data from the recovery. There's no failure or error. CWM shows the data is erased but the rom has no effect. CWM flashes everything without displaying any error but it does not change anything in the rom. I can't even change the recovery. Even i flashed the original stock rom via odin and the flashing too aroung 2 hrs to finish, but still the custom rom was there with all the apps and everything. Now i have really no clue what to do about it. I cant use it in the present condition and can't even change anything on it..
Please help me Tab 2 community. PLEASE..
kadwal_nitish said:
Hi everyone,
I have a samsung tab 2 p3100 with me. I used to flash a lot on my tab and try different roms on it. But lately i faced this very uncommon problem when i flashed a purebean hdv2 rom on my tab. After using it for a few days i tried to flash a new one. So I made a titanium backup of my apps at night and in the morning my tab started rebooting as soon as i change any setting. It's like it's stuck on the same data, apps and setting as it was at night. Tab would restart in 10 seconds of usage. And even if i try to change any setting or remove an app in those 10 sec, everything comes back to the same condition after a reboot. I can't format data from the recovery. There's no failure or error. CWM shows the data is erased but the rom has no effect. CWM flashes everything without displaying any error but it does not change anything in the rom. I can't even change the recovery. Even i flashed the original stock rom via odin and the flashing too aroung 2 hrs to finish, but still the custom rom was there with all the apps and everything. Now i have really no clue what to do about it. I cant use it in the present condition and can't even change anything on it..
Please help me Tab 2 community. PLEASE..
Click to expand...
Click to collapse
flash again stock rom and before that wipe cache and dalvik cache and factory reset in recovery and then flash the stock rom
did you unchecked the repartition option in odin ??
Place another Rom (e.g. CM or Omni or what-ever-you-like) on the MicroSD-Card (IMPORTANT!!!)
Flash a updated Recovery.
Reboot the recovery after that.
Wipe Data Factory Reset
Wipe Cache
Wipe Dalvic Cache
format /system (under "Mounts and Storage")
format /data
format /data and /data/media (this will format the internal Storage! Be sure you placed the rom.zip on the MicroSD)!
Now flash the new Rom.zip from your MircroSD
Reboot.
Android-Andi said:
Place another Rom (e.g. CM or Omni or what-ever-you-like) on the MicroSD-Card (IMPORTANT!!!)
Flash a updated Recovery.
Reboot the recovery after that.
Wipe Data Factory Reset
Wipe Cache
Wipe Dalvic Cache
format /system (under "Mounts and Storage")
format /data
format /data and /data/media (this will format the internal Storage! Be sure you placed the rom.zip on the MicroSD)!
Now flash the new Rom.zip from your MircroSD
Reboot.
Click to expand...
Click to collapse
Odin shows fail on flashing an updated recovery. What should i do now?
kadwal_nitish said:
Odin shows fail on flashing an updated recovery. What should i do now?
Click to expand...
Click to collapse
You might have an hardware problem... is the device still under warranty?
If I were you, I would try different cable and re-install drivers... also try to flash different recovery image.
kadwal_nitish said:
Hi everyone,
I have a samsung tab 2 p3100 with me. I used to flash a lot on my tab and try different roms on it. But lately i faced this very uncommon problem when i flashed a purebean hdv2 rom on my tab. After using it for a few days i tried to flash a new one. So I made a titanium backup of my apps at night and in the morning my tab started rebooting as soon as i change any setting. It's like it's stuck on the same data, apps and setting as it was at night. Tab would restart in 10 seconds of usage. And even if i try to change any setting or remove an app in those 10 sec, everything comes back to the same condition after a reboot. I can't format data from the recovery. There's no failure or error. CWM shows the data is erased but the rom has no effect. CWM flashes everything without displaying any error but it does not change anything in the rom. I can't even change the recovery. Even i flashed the original stock rom via odin and the flashing too aroung 2 hrs to finish, but still the custom rom was there with all the apps and everything. Now i have really no clue what to do about it. I cant use it in the present condition and can't even change anything on it..
Please help me Tab 2 community. PLEASE..
Click to expand...
Click to collapse
I'm facing the same problem.. Can someone please confirm if this is a hardware problem? And if so, why does it happen??
You need to flash a story Rom + reformat using a pit file for your device. After that i recommend to use my latest TWRP 2.8.1.1
Send from OnePlus One using Tapatalk
Android-Andi said:
You need to flash a story Rom + reformat using a pit file for your device. After that i recommend to use my latest TWRP 2.8.1.1
Send from OnePlus One using Tapatalk
Click to expand...
Click to collapse
Hey Andi! Long time! I tried flashing the latest stock ROM but to no avail.. Whatever I do, whether it's factory reset or odin flash or recovery flash or flashing a new recovery or uninstalling apps or anything, state of the device doesn't change at all.. It still boots up to the same ROM in the same state as it was.. It's like the device has become read-only.. It took 5 hours to flash the stock ROM and nothing changed.. HELP!!! :'(
---------- Post added at 12:39 PM ---------- Previous post was at 12:32 PM ----------
I just tried the pit file too.. Nothing..
---------- Post added at 12:42 PM ---------- Previous post was at 12:39 PM ----------
Do I choose "NAND Erase All" as well??
Please check this for the S3.. They have a solution for this problem.. http://forum.xda-developers.com/showthread.php?t=1840030
Andi, please take a look..
@hottracks4 adb access in recovery?
Send from OnePlus One using Tapatalk
Android-Andi said:
@hottracks4 adb access in recovery?
Send from OnePlus One using Tapatalk
Click to expand...
Click to collapse
Umm I didn't try that.. if it does, Then what?
hottracks4 said:
Umm I didn't try that.. if it does, Then what?
Click to expand...
Click to collapse
Then restart adb as root
Code:
adb root
Now try to mount rw:
Code:
adb remount
Send from OnePlus One using Tapatalk
Android-Andi said:
Then restart adb as root
Code:
adb root
Now try to mount rw:
Code:
adb remount
Send from OnePlus One using Tapatalk
Click to expand...
Click to collapse
Sorry for the late reply Andi.. I tried what you said, just now and this is what it says, "remount failed: Success".. What on earth is this supposed to mean? :/
---------- Post added at 08:36 PM ---------- Previous post was at 08:14 PM ----------
Plus I also tried by booting into the device, going into shell and wiping.. Returns all as I/O errors.. And then the tab goes bonkers.. Even the shut down menu just shows 2 options and both showing as "Error", and not "Shut down" or "Reboot"..
Try remount again.in recovery.
After that try to wipe and flash a Rom. Not sure if it works. Else try reformat in Odin using stock rom and pit file.
Send from OnePlus One using Tapatalk
Tried all of that already.. No change..
hottracks4 said:
Tried all of that already.. No change..
Click to expand...
Click to collapse
Boot the rom please.
Now reboot into recovery.
Give a complete /proc/last_kmsg:
Code:
adb root
adb pull /proc/last_kmsg
Send from OnePlus One using Tapatalk
Same problem with my P3100
Guys,
I have the same issue with my P3100.
I tried to do everything which I could. Flashed recovery with TWRP, Philz, CWM & all but recovery doesn't change.
Tried with stock ROM via Odin, still same issue persists.
Tried to delete all /system & /data through ADB shell. Damn it .. all comes back as soon as I reboot the tab.
Tried to unroot & root the tab but nothing changes. Tab boots to the home screen, stays for 30-40 secs & then reboots.
No matter what I do, nothing happens to the OS. What a solid built! :laugh:
I seriously tried to brick my OS & format with different tools .. :crying::crying::laugh:
Any help is greatly appreciated, I am enjoying this though! :laugh:
Please follow this thread http://forum.xda-developers.com/showthread.php?t=3016879
Send from OnePlus One using Tapatalk
Android-Andi said:
Please follow this thread http://forum.xda-developers.com/showthread.php?t=3016879
Send from OnePlus One using Tapatalk
Click to expand...
Click to collapse
Thanks Andy, see u there.
I am facing the same problem. Plz help me if you are able to get rid of the problem.
According to me the problem with the tablet is that we tried too many custom roms on our device p3100. And actually reached a limit of 20 count of custom binary download. what's your count? For custom binary download? If you get a solution plz do help me out.
Thanks.
Hello guys, I have a XT1033 converted to GPe in stock 5.1. What can I do to get CM12.1?
Flash stockrom 5.0.2 and after that twrp. Flash cm12.0 and dirty flash cm12.1 . hope this is correct.
klaymaniaf said:
Flash stockrom 5.0.2 and after that twrp. Flash cm12.0 and dirty flash cm12.1 . hope this is correct.
Click to expand...
Click to collapse
After I flash the stock rom, it wont go past the boot logo.
In twrp it will say the flash was successful, but if i reboot into stock it wont go past the boot logo which is still the google logo from the 5.1 GPe. If I go to flash CM over that, I get an error.
wipe dalvik cache/cache
Never mind, i got it to work. I had to flash the correct gpt.bin file, because the partitions are different on stock motorola than to the gpe. After that a full wipe and i could go back to stock and onto cm12.1.
http://forum.xda-developers.com/showpost.php?p=57444986&postcount=1
this is the file that worked for me You will have to do a full wipe and reboot to recovery to be able to mount any of the file systems again tho.
r97smith said:
Never mind, i got it to work. I had to flash the correct gpt.bin file, because the partitions are different on stock motorola than to the gpe. After that a full wipe and i could go back to stock and onto cm12.1.
http://forum.xda-developers.com/showpost.php?p=57444986&postcount=1
this is the file that worked for me You will have to do a full wipe and reboot to recovery to be able to mount any of the file systems again tho.
Click to expand...
Click to collapse
Mate can u step by step explain what you did and downloaded? I am on converted GPE and want to install cm12.1 - funny thing is I didnt get anything online for getting gpe to cm12.1 other than your post Your help is appreciated. Also does your sms work on cm12.1?
Vivek
vivekdeshmukh said:
Mate can u step by step explain what you did and downloaded? I am on converted GPE and want to install cm12.1 - funny thing is I didnt get anything online for getting gpe to cm12.1 other than your post Your help is appreciated. Also does your sms work on cm12.1?
Vivek
Click to expand...
Click to collapse
From GPE, I wiped everything in twrp recovery. Flashed the gpt.bin file I had linked to there, and then rebooted to recovery again.
Then I decided to go back to stock 5.0.2, flashed that, then cm12 and then cm12.1. But thats just how I did it anyway.
I had to flash the gpt.bin file to re-partition the system storage, because its different to the stock and cyanogenmod. I flashed stock 5.0.2 just to be sure there wasnt going to be anymore problems when flashing cyanogenmod. Then I flashed cm12 to see everything booted right, and cm12.1 with the 5.1 gapps.
Yes, everything works excellent on cm12.1
r97smith said:
From GPE, I wiped everything in twrp recovery. Flashed the gpt.bin file I had linked to there, and then rebooted to recovery again.
Then I decided to go back to stock 5.0.2, flashed that, then cm12 and then cm12.1. But thats just how I did it anyway.
I had to flash the gpt.bin file to re-partition the system storage, because its different to the stock and cyanogenmod. I flashed stock 5.0.2 just to be sure there wasnt going to be anymore problems when flashing cyanogenmod. Then I flashed cm12 to see everything booted right, and cm12.1 with the 5.1 gapps.
Yes, everything works excellent on cm12.1
Click to expand...
Click to collapse
Thanks mate, it sounds bit of a task for a noob like me, but hell i will give that a try
---------- Post added at 05:16 PM ---------- Previous post was at 05:09 PM ----------
r97smith said:
stock 5.0.2, flashed that, then cm12 and then cm12.1.
Click to expand...
Click to collapse
Our of curiosity, why do we have to go from 5.02 to cm12 to cm12.1? cant we go directly from 5.02 to cm12.1?
vivekdeshmukh said:
Thanks mate, it sounds bit of a task for a noob like me, but hell i will give that a try
---------- Post added at 05:16 PM ---------- Previous post was at 05:09 PM ----------
Our of curiosity, why do we have to go from 5.02 to cm12 to cm12.1? cant we go directly from 5.02 to cm12.1?
Click to expand...
Click to collapse
For flashing cm 12.1 if you are currently using gpe 5.1 converted, you dont need to do all that **** like flashing stock 5.0.2 then cm 12 and then cm12.1
You just need to do this
In twrp recovery go to wipe and change data partition file system to f2fs
Then wipe every thing in recovery and flash cm12.1
sjandroiddeveloper said:
You just need to do this
In twrp recovery go to wipe and change data partition file system to f2fs
Then wipe every thing in recovery and flash cm12.1
Click to expand...
Click to collapse
1st step - wipe and change Data partition to f2fs ONLY or should i change the partition to f2fs for all (data, cache, system, usb)?
2nd step - wipe everything meaning dalvik, data, cache, system BUT NOT internal storage and USB - correct?
vivekdeshmukh said:
1st step - wipe and change Data partition to f2fs ONLY or should i change the partition to f2fs for all (data, cache, system, usb)?
2nd step - wipe everything meaning dalvik, data, cache, system BUT NOT internal storage and USB - correct?
Click to expand...
Click to collapse
You have to change file system to f2fs of data partition only ,don't change other, if you do there is no doubt your device will not boot but it may cause several other problems
And after changing file system of data partition you need to wipe dalvik,cache,system and data
No need to wipe internal storage (data/media)
And where does USB come in this ???
Sent from falcon
PRESS THANKS IF HELPED
sjandroiddeveloper said:
And where does USB come in this ???
Click to expand...
Click to collapse
USB OTG is an option that comes under recovery in twrp - advanced wipe. Thanks trying it right now!
vivekdeshmukh said:
USB OTG is an option that comes under recovery in twrp - advanced wipe. Thanks trying it right now!
Click to expand...
Click to collapse
I know what is USB OTG and where it comes
What I meant was why did you even think of wiping USB
sjandroiddeveloper said:
You have to change file system to f2fs of data partition only ,don't change other, if you do there is no doubt your device will not boot but it may cause several other problems And after changing file system of data partition you need to wipe dalvik,cache,system and data No need to wipe internal storage (data/media)
And where does USB come in this ???
Sent from falcon
PRESS THANKS IF HELPED
Click to expand...
Click to collapse
Tried it yesterday night >> BOOM! OS gone! Dont know what happened, did the f2fs no problem but after dalvik, cache, system and data wipe the OS and all files just disappeared - dont know if it was corrupt data partition or me being too sleepy (5.00am) and could have deleted Internal storage. But the point is I ended up with no OS and then tried ADB pushing my cm files to phone, well only to realize that ADB was not recognizing the device inspite of uninstall/install drivers ... slept at 6.00 in morning. Today, finally, copied the cm files by mounting the phone and copying from PC, just to realize after flashing that the cm12.1 still has the same issues of not able to send sms.
But anyways thanks to you I did learn something new and the opportunity to be in a soft brick situation and come out of it
Btw do u hv a converted gpe and tried the cm12.1 simply by changing the partition? EVerything works very smooth for me but just that the SMS doesnt work - which i cant live without.
vivekdeshmukh said:
Tried it yesterday night >> BOOM! OS gone! Dont know what happened, did the f2fs no problem but after dalvik, cache, system and data wipe the OS and all files just disappeared - dont know if it was corrupt data partition or me being too sleepy (5.00am) and could have deleted Internal storage. But the point is I ended up with no OS and then tried ADB pushing my cm files to phone, well only to realize that ADB was not recognizing the device inspite of uninstall/install drivers ... slept at 6.00 in morning. Today, finally, copied the cm files by mounting the phone and copying from PC, just to realize after flashing that the cm12.1 still has the same issues of not able to send sms.
But anyways thanks to you I did learn something new and the opportunity to be in a soft brick situation and come out of it
Btw do u hv a converted gpe and tried the cm12.1 simply by changing the partition? EVerything works very smooth for me but just that the SMS doesnt work - which i cant live without.
Click to expand...
Click to collapse
No I never converted to gpe
But the method I told you was absolutely correct
And your OS was deletes because you wiped system partition which was necessary to install cm 12.1 so that was obvious and no need to worry.
And for your information you don't need adb if you are using twrp because it supports mtp
And the sms bug was there but it was solved long ago but I don't know why its not working for you
May be try different kernels
And bro PRESS THANKS instead of saying
can you plz help with the sms bug..
sjandroiddeveloper said:
No I never converted to gpe
But the method I told you was absolutely correct
And your OS was deletes because you wiped system partition which was necessary to install cm 12.1 so that was obvious and no need to worry.
And for your information you don't need adb if you are using twrp because it supports mtp
And the sms bug was there but it was solved long ago but I don't know why its not working for you
May be try different kernels
And bro PRESS THANKS instead of saying
Click to expand...
Click to collapse
can you plz help with the sms bug..
Good evening, I saw some questions similar to this one in the forum, but none had my kind of doubt.
When a new ROM comes out for both S7 and S8, I install via ODIN using the CSC HOME option, so as not to lose the data.
The problem is in the installation of TWRP whenever I install the same by ODIN, when entering the app and trying to install example no-verity ja start I get the message that the DATA folder has been corrupted and can not be mounted.
This way it only works once again doing WIPE DATA, but then I lose my data and I have to start from scratch.
Is there a way this does not happen or will it always be like this when updating a ROM?
Thank you.
costafabiof said:
Good evening, I saw some questions similar to this one in the forum, but none had my kind of doubt.
When a new ROM comes out for both S7 and S8, I install via ODIN using the CSC HOME option, so as not to lose the data.
The problem is in the installation of TWRP whenever I install the same by ODIN, when entering the app and trying to install example no-verity ja start I get the message that the DATA folder has been corrupted and can not be mounted.
This way it only works once again doing WIPE DATA, but then I lose my data and I have to start from scratch.
Is there a way this does not happen or will it always be like this when updating a ROM?
Thank you.
Click to expand...
Click to collapse
Have you tried backing up data with twrp before you wipe and copying it to your pc so you can do a full wipe then put the backup onto the phone and flash It? You can back up data folder only
godkingofcanada said:
Have you tried backing up data with twrp before you wipe and copying it to your pc so you can do a full wipe then put the backup onto the phone and flash It? You can back up data folder only
Click to expand...
Click to collapse
Good afternoon,
Thanks for the reply.
So from what I mentioned above, I do a full backup as I normally do, and I also do a separate from the DATA folder.
Then I install the ROM and TWRP, will it corrupt the DATA folder so I restore only it? Would it be this?
If so, will it work out, in relation to being a ROM different from the other?
costafabiof said:
Good afternoon,
Thanks for the reply.
So from what I mentioned above, I do a full backup as I normally do, and I also do a separate from the DATA folder.
Then I install the ROM and TWRP, will it corrupt the DATA folder so I restore only it? Would it be this?
If so, will it work out, in relation to being a ROM different from the other?
Click to expand...
Click to collapse
The main rom info needed is contained in the system folder. The data folder is application data and whatnot. Reboot into twrp and use the backup option, then copy to pc. Do a full wipe of all, pit backup of data folder and new rom on internal or sd. Go into terp and flash the rom and data folder. Do not flaah system or it will overwrite the new rom. u will restore everything even if you don't have the APK installed in your system. It will return the data, you may need to reinstall the APK. Gmail for example will return will email addresses and messages, contacts and texts will come back to what they were at backup. You should back up modem and efs and boot as well and keep them safe. What I do is I get my phone set up fully, all apps I need and any games and data and then back it up again so any issues and I restore it to a fully functional state and don't need to install tons of things
godkingofcanada said:
The main rom info needed is contained in the system folder. The data folder is application data and whatnot. Reboot into twrp and use the backup option, then copy to pc. Do a full wipe of all, pit backup of data folder and new rom on internal or sd. Go into terp and flash the rom and data folder. Do not flaah system or it will overwrite the new rom. u will restore everything even if you don't have the APK installed in your system. It will return the data, you may need to reinstall the APK. Gmail for example will return will email addresses and messages, contacts and texts will come back to what they were at backup. You should back up modem and efs and boot as well and keep them safe. What I do is I get my phone set up fully, all apps I need and any games and data and then back it up again so any issues and I restore it to a fully functional state and don't need to install tons of things
Click to expand...
Click to collapse
Good afternoon,
I'm sorry for the text I'm using Google Translate.
I believe that I did not understand correctly, because the error happens in the following way, I install a ROM, reinstall the TWRP, yes yes it corrupts the folder DATA!
If I understood mistake, I apologize.
costafabiof said:
Good afternoon,
I'm sorry for the text I'm using Google Translate.
I believe that I did not understand correctly, because the error happens in the following way, I install a ROM, reinstall the TWRP, yes yes it corrupts the folder DATA!
If I understood mistake, I apologize.
Click to expand...
Click to collapse
Is it a custom Rom or a stock rom? Also you can backup via ADB
https://forum.xda-developers.com/an...oid-sdk-adb-backup-apps-t3467560#edit68829721
godkingofcanada said:
Is it a custom Rom or a stock rom? Also you can backup via ADB
https://forum.xda-developers.com/an...oid-sdk-adb-backup-apps-t3467560#edit68829721
Click to expand...
Click to collapse
The ROM I use is provided by Samsung, with no modifications, when I install it I use the CSC option the HOME file, in order not to lose the data, and of course, I do not lose anything I only update the ROM.
The problem is that I need to reinstall TWRP after installing ROM, and when I access TWRP it has corrupted the DATA folder.
costafabiof said:
The ROM I use is provided by Samsung, with no modifications, when I install it I use the CSC option the HOME file, in order not to lose the data, and of course, I do not lose anything I only update the ROM.
The problem is that I need to reinstall TWRP after installing ROM, and when I access TWRP it has corrupted the DATA folder.
Click to expand...
Click to collapse
You can extract the samsung md5 and repack it as a zip with superrs kitchen and then flash it from twrp. Just remove the recovery.img from the extracted files before zipping it up. Then you can simply flash twrp. Then the rom and not have to worry about the fact that you are stuck in a loop of being locked out because you don't need odin for the rom and it won't overwrite your recovery. If that's too much work try using a custom Rom from xda
godkingofcanada said:
You can extract the samsung md5 and repack it as a zip with superrs kitchen and then flash it from twrp. Just remove the recovery.img from the extracted files before zipping it up. Then you can simply flash twrp. Then the rom and not have to worry about the fact that you are stuck in a loop of being locked out because you don't need odin for the rom and it won't overwrite your recovery. If that's too much work try using a custom Rom from xda
Click to expand...
Click to collapse
Thank you very much for your patience. But I'm not clear, or you do not understand.
The problem is not in the ROM, but in the TWRP installation. If I install the ROM with the option CSC HOME I do not lose anything, everything is working correctly.
When I install TWRP it corrupts the DATA folder. The problem is there!
costafabiof said:
Thank you very much for your patience. But I'm not clear, or you do not understand.
The problem is not in the ROM, but in the TWRP installation. If I install the ROM with the option CSC HOME I do not lose anything, everything is working correctly.
When I install TWRP it corrupts the DATA folder. The problem is there!
Click to expand...
Click to collapse
I was saying to use a zip rom because then you can reflash the rom without reflashing twrp. So you flash twrp, it says data error and then you flash rom from zip, which reinstall system and data but will not copy stock recovery over twrp. So you will not have to reinstall it and be stuck. Or try a different version of twrp might also help. Stock firmware overwrites recovery and the rom. You need to modify it to remove recovery from the firmware, or use a custom Rom to stop it from erasing twrp
godkingofcanada said:
I was saying to use a zip rom because then you can reflash the rom without reflashing twrp. So you flash twrp, it says data error and then you flash rom from zip, which reinstall system and data but will not copy stock recovery over twrp. So you will not have to reinstall it and be stuck. Or try a different version of twrp might also help. Stock firmware overwrites recovery and the rom. You need to modify it to remove recovery from the firmware, or use a custom Rom to stop it from erasing twrp
Click to expand...
Click to collapse
I think I understood, more or less, since I translate for Google.
But assuming I want to use normal ROM, you have to back up the DATA folder before installing the ROM and after installing the new ROM and TWRP, restore only the DATA?
Thank you again.
Yes a new rom will overwrite data, you need a backup before. You should be able to connect your phone to a linux operating system and use adb to connect and back it up, if twrp will not let you take a back up.
godkingofcanada said:
Yes a new rom will overwrite data, you need a backup before. You should be able to connect your phone to a linux operating system and use adb to connect and back it up, if twrp will not let you take a back up.
Click to expand...
Click to collapse
In my case I can back up the DATA folder by TWRP. Is there doubt, if I back up the DATA folder in one version of Android and then restore in another version, will it be compatible?
costafabiof said:
In my case I can back up the DATA folder by TWRP. Is there doubt, if I back up the DATA folder in one version of Android and then restore in another version, will it be compatible?
Click to expand...
Click to collapse
Yes it will be, marshmallow and nougat are completely compatible from the boot loader up. You can also turn your stock samsung md5 into a zip file so you do not need odin to install it. You will be able to flash it from twrp
godkingofcanada said:
Yes it will be, marshmallow and nougat are completely compatible from the boot loader up. You can also turn your stock samsung md5 into a zip file so you do not need odin to install it. You will be able to flash it from twrp
Click to expand...
Click to collapse
Again thank you very much.
I'll test it and put it here.
Note: The Thank you button is not working.
costafabiof said:
Again thank you very much.
I'll test it and put it here.
Note: The Thank you button is not working.
Click to expand...
Click to collapse
You are welcome. If you want to have a stock zip file instead of the md5 use this link.
https://forum.xda-developers.com/showthread.php?t=2387941
...
costafabiof said:
...
Click to expand...
Click to collapse
Can you not read the website?
I know what you mean. Twrp can't access the data folder because it's encrypted. But you do have to format it to gain proper access. You have to copy the files out or back them up
godkingofcanada said:
Can you not read the website?
Click to expand...
Click to collapse
I believe that because I am a new user I can not exclude publications, I already tested in CHROME and IE. In the same way I can not give THANK YOU.
Ok... As you can see from this thread,
https://forum.xda-developers.com/on...en-restore-t3804734/post76832485#post76832485
I soft bricked my phone after trying to restore a backup in official TWRP.
I followed this tutorial https://forum.xda-developers.com/oneplus-6/how-to/oneplus-6-unlock-bootloader-flash-twrp-t3792643
And jumped over to this tutorial https://forum.xda-developers.com/oneplus-6/how-to/guide-how-to-install-official-twrp-t3801558 per this post in the tutorial https://forum.xda-developers.com/showpost.php?p=76564290&postcount=5 note that this post points to another way of getting TWRP. The link I went to is how to install OFFICIAL TWRP.
And jumped back to the original tutorial for the rest. I'm scared to death now to try and test the restore functionality in TWRP. Has anyone successfully restored a backup? If so, what steps did they take to get the backup and what steps did they take restoring backup? What partitions did the check.mark during backup and what partitions did they check mark during restore? And do you need to do anything with changing the a/b slots????
Edited to add correct link to install official TWRP.
vinnievegas said:
Ok... As you can see from this thread,
https://forum.xda-developers.com/on...en-restore-t3804734/post76832485#post76832485
I soft bricked my phone after trying to restore a backup in official TWRP.
I followed this tutorial https://forum.xda-developers.com/oneplus-6/how-to/oneplus-6-unlock-bootloader-flash-twrp-t3792643
And jumped over to this tutorial per this post in the tutorial https://forum.xda-developers.com/showpost.php?p=76564290&postcount=5
And jumped back to the original tutorial for the rest. I'm scared to death now to try and test the restore functionality in TWRP. Has anyone successfully restored a backup? If so, what steps did they take to get the backup and what steps did they take restoring backup? What partitions did the check.mark during backup and what partitions did they check mark during restore? And do you need to do anything with changing the a/b slots????
Click to expand...
Click to collapse
Flash stock ROM in TWRP, flash TWRP again. It won't touch data partition but you can restore just your data partition from your TWRP backup. Boot into system once, then reboot recovery and flash magisk if you want root. All modules you have will be back and active after that.
---------- Post added at 01:34 AM ---------- Previous post was at 01:33 AM ----------
On the off chance TWRP says there is no OS after flashing stock ROM and TWRP, ignore messages and boot anyway. It will restore your phone without losing all data.
mikex8593 said:
Flash stock ROM in TWRP, flash TWRP again. It won't touch data partition but you can restore just your data partition from your TWRP backup. Boot into system once, then reboot recovery and flash magisk if you want root. All modules you have will be back and active after that.
---------- Post added at 01:34 AM ---------- Previous post was at 01:33 AM ----------
On the off chance TWRP says there is no OS after flashing stock ROM and TWRP, ignore messages and boot anyway. It will restore your phone without losing all data.
Click to expand...
Click to collapse
I'll try this and if this works and is in deed the process we need to follow until TWRP can just do what it's supposed to, then shouldn't this stuff be in the tutorials or have the OPs actually pulled this off like it's supposed to be?
vinnievegas said:
I'll try this and if this works and is in deed the process we need to follow until TWRP can just do what it's supposed to, then shouldn't this stuff be in the tutorials or have the OPs actually pulled this off like it's supposed to be?
Click to expand...
Click to collapse
Just too lazy to make an official thread, I guess. It will work.
mikex8593 said:
Flash stock ROM in TWRP, flash TWRP again. It won't touch data partition but you can restore just your data partition from your TWRP backup. Boot into system once, then reboot recovery and flash magisk if you want root. All modules you have will be back and active after that.
---------- Post added at 01:34 AM ---------- Previous post was at 01:33 AM ----------
On the off chance TWRP says there is no OS after flashing stock ROM and TWRP, ignore messages and boot anyway. It will restore your phone without losing all data.
Click to expand...
Click to collapse
mikex8593 said:
Just too lazy to make an official thread, I guess. It will work.
Click to expand...
Click to collapse
So to be clear, I get the roms from here under signed flashable zips?
https://forum.xda-developers.com/oneplus-6/how-to/oneplus-6-mirrors-official-oxygen-os-t3792244
vinnievegas said:
So to be clear, I get the roms from here under signed flashable zips?
https://forum.xda-developers.com/oneplus-6/how-to/oneplus-6-mirrors-official-oxygen-os-t3792244
Click to expand...
Click to collapse
Yep. You can use the method with any of those zips.
I restored boot, system and data and ended in twrp loop. Flashing magisk revived it.
Sent from my ONEPLUS A6003 using Tapatalk
tdamocles said:
I restored boot, system and data and ended in twrp loop. Flashing magisk revived it.
Sent from my ONEPLUS A6003 using Tapatalk
Click to expand...
Click to collapse
Did you do it like he instructed above?
Flash rom
Flash TWRP
Restore boot, system, and data
Reboot?
vinnievegas said:
Did you do it like he instructed above?
Flash rom
Flash TWRP
Restore boot, system, and data
Reboot?
Click to expand...
Click to collapse
To tell you the truth I didn't even see the other post and was trying to get the renovate magisk module working in the process. It was the first time for me trying to restore a twrp backup because I borked something in the renovate magisk install. Like I said, I tried restoring boot, system and data and ended in a bootloop twrp situation. I figured what the heck, let's try flashing magisk root again and see what happens, and voila it work.
Yes me too twrp on oneplus 6 are buggy when I had restore all system part my Phone enter in bootloop [emoji58]
Actual Device : OnePlus 6 Past Devices : Galaxy S6, Xperia Z2, Huawei P7, Nokia 620
mikex8593 said:
Flash stock ROM in TWRP, flash TWRP again. It won't touch data partition but you can restore just your data partition from your TWRP backup. Boot into system once, then reboot recovery and flash magisk if you want root. All modules you have will be back and active after that.
---------- Post added at 01:34 AM ---------- Previous post was at 01:33 AM ----------
On the off chance TWRP says there is no OS after flashing stock ROM and TWRP, ignore messages and boot anyway. It will restore your phone without losing all data.
Click to expand...
Click to collapse
Ok. Worked like a charm. Thank you so much. I tested all this without any lock screen security. Now I'm wondering if this procedure works with backups with lock screen security.
mikex8593 said:
Flash stock ROM in TWRP, flash TWRP again. It won't touch data partition but you can restore just your data partition from your TWRP backup. Boot into system once, then reboot recovery and flash magisk if you want root. All modules you have will be back and active after that.
---------- Post added at 01:34 AM ---------- Previous post was at 01:33 AM ----------
On the off chance TWRP says there is no OS after flashing stock ROM and TWRP, ignore messages and boot anyway. It will restore your phone without losing all data.
Click to expand...
Click to collapse
black_file said:
Yes me too twrp on oneplus 6 are buggy when I had restore all system part my Phone enter in bootloop [emoji58]
Actual Device : OnePlus 6 Past Devices : Galaxy S6, Xperia Z2, Huawei P7, Nokia 620
Click to expand...
Click to collapse
tdamocles said:
To tell you the truth I didn't even see the other post and was trying to get the renovate magisk module working in the process. It was the first time for me trying to restore a twrp backup because I borked something in the renovate magisk install. Like I said, I tried restoring boot, system and data and ended in a bootloop twrp situation. I figured what the heck, let's try flashing magisk root again and see what happens, and voila it work.
Click to expand...
Click to collapse
Ok. Just tried what tdamocles did. But I've been wiping before restore. I then just restore and select system, boot, and data. I did not reflash TWRP. Rebooted and everything was good. Still had root and didn't need to reflash magisk. Was also able to reboot back into TWRP, so there was no need to reflash TWRP. But.... I think that is due to not flashing the stock room first. I'm assuming that if you reflash stock that you will indeed have to reflash TWRP. So, conclusion... If you restore system, boot, and data then no need to reflash TWRP and in my case no need to reflash magisk. Again, this is without lock screen security. My next test will be with lock screen security unless someone posts a negative result before I do.
vinnievegas said:
Ok. Just tried what tdamocles did. But I've been wiping before restore. I then just restore and select system, boot, and data. I did not reflash TWRP. Rebooted and everything was good. Still had root and didn't need to reflash magisk. Was also able to reboot back into TWRP, so there was no need to reflash TWRP. But.... I think that is due to not flashing the stock room first. I'm assuming that if you reflash stock that you will indeed have to reflash TWRP. So, conclusion... If you restore system, boot, and data then no need to reflash TWRP and in my case no need to reflash magisk. Again, this is without lock screen security. My next test will be with lock screen security unless someone posts a negative result before I do.
Click to expand...
Click to collapse
You will not be able to get past encrption if you decrypt in TWRP and restore. It essentially forgets encryption key.
mikex8593 said:
You will not be able to get past encrption if you decrypt in TWRP and restore. It essentially forgets encryption key.
Click to expand...
Click to collapse
Update...
Just performed a backup with lock screen security and was able to restore the backup choosing system, boot, and data. No reflashing of TWRP or magisk. Not sure if needed but I've been performing basic wipe before all my restores. Still able to boot back into TWRP and still had root.
mikex8593 said:
You will not be able to get past encrption if you decrypt in TWRP and restore. It essentially forgets encryption key.
Click to expand...
Click to collapse
Check my post above. I edited it to quote you.
I must also note that I'm using official TWRP. I edited my first post to reflect the link I used when jumping out if the tutorial and back.
vinnievegas said:
Update...
Just performed a backup with lock screen security and was able to restore the backup choosing system, boot, and data. No reflashing of TWRP or magisk. Not sure if needed but I've been performing basic wipe before all my restores. Still able to boot back into TWRP and still had root.
Click to expand...
Click to collapse
Nice.
I have restored from twrp a couple times now with no problem.. I did get the message saying can't mount system or something like that, ok I went into the mount options and mounted system after that the restore worked perfectly and I could boot back into the rom and back into twrp after.
Restored mine yesterday too, all files checked when backup, deleted lockscreen settings before, few bootloops at the beginning, until phone changed slot, then booted into system. Cheers!
primus19 said:
Restored mine yesterday too, all files checked when backup, deleted lockscreen settings before, few bootloops at the beginning, until phone changed slot, then booted into system. Cheers!
Click to expand...
Click to collapse
Not necessary to check all partitions. This only results in a huge nandroid file.