Related
How close are we to having a no-wipe root?
its not like u have to root and wipe everyday
EXACTLY
johnxjets said:
its not like u have to root and wipe everyday
Click to expand...
Click to collapse
lol the phone had root within hours of launch so chances are your phone will be BRAND NEW when you root it. I don't see how much stuff you could possibly put on your phone in a couple hours before you have the chance to do it. all you should have to do is sign into gmail. Apps, WIFI settings, passwords, all of it now restore when you log in automatically. i love it!
I rooted the phone last night while it was on and it didn't wipe anything. To have root, you just need to have the right files in the right places. It wipes absolutely nothing
jroid said:
I rooted the phone last night while it was on and it didn't wipe anything. To have root, you just need to have the right files in the right places. It wipes absolutely nothing
Click to expand...
Click to collapse
Every other post on the forum disagrees with you.
seriouslyjeff said:
lol the phone had root within hours of launch so chances are your phone will be BRAND NEW when you root it. I don't see how much stuff you could possibly put on your phone in a couple hours before you have the chance to do it. all you should have to do is sign into gmail. Apps, WIFI settings, passwords, all of it now restore when you log in automatically. i love it!
Click to expand...
Click to collapse
Well how about that since this stupid thing doesn't have a memory card, all of my pix, vids, etc are now in internal memory....
hah2110 said:
Every other post on the forum disagrees with you.
Click to expand...
Click to collapse
The "rooting" does not wipe - unlocking the boot loader wipes. The actually placement of the SU binary through custom recovery doesn't wipe. Unfortunately if you don't have a custom recovery loaded you need to unlock in order to proceed (thus wiping).
hah2110 said:
Well how about that since this stupid thing doesn't have a memory card, all of my pix, vids, etc are now in internal memory....
Click to expand...
Click to collapse
Does it wipe the entire internal storage or only the ~ 1G allocated for apps and such? Has anyone tried this to verify?
krohnjw said:
Does it wipe the entire internal storage or only the ~ 1G allocated for apps and such? Has anyone tried this to verify?
Click to expand...
Click to collapse
The fastboot oem unlock wipes EVERYTHING. The app storage and internal sd storage. So make sure to back up everything. When roms start coming out, if it's like the Galaxy S phone, it will only do factory reset wipe and not the internal sd partition.
krohnjw said:
The "rooting" does not wipe - unlocking the boot loader wipes. The actually placement of the SU binary through custom recovery doesn't wipe. Unfortunately if you don't have a custom recovery loaded you need to unlock in order to proceed (thus wiping).
Click to expand...
Click to collapse
Exactly
hah2110 said:
Every other post on the forum disagrees with you.
Well how about that since this stupid thing doesn't have a memory card, all of my pix, vids, etc are now in internal memory....
Click to expand...
Click to collapse
What I meant by this was the phone has only been on the market for a day so It couldn't be too hard to redo or reput back on what you already have. But once boot is unlocked it shouldn't ever be an issue again. Wasn't the n1 the same when you unlocked boot?
N1 didn't wipe SD though. Since this has no SD card wiping will wipe far more content.
Non-unlocking root possible?
Ok. Ive been playing around with the nexus s for sometime now. Im starting to think on rooting the phone. The problem is that unlocking the boot wipes the phone, something i do not want to happen.
If i understood these posts right i can get root if i boot with a custom recovery. So connecting to adb in fastboot mode and executing:
fastboot boot recovery-clockwork-crespo.img
Should do that.
If i then flash the superuser zip, will i get the phone rooted and still locked (not wiped).
Am i missing something? Almost certain i am.
Could any of you provide a guide on how to do it, please?
Thanxs,
Iñaki
Your method is worth a try. I thought you couldn't flash the custom recovery without unlocking the bootloader, but I've seen posts saying you could (but none saying they did, if you see the difference).
Sounds like you know what to do. I'd use the 3.0.0.5 recovery image, it's linked a couple of places here.
As soon as i have some free time to do it, i will test it. Though i still think i am missing something. Just wanted to confirm i was not overlooking something obvious.
fastboot won't work unless you have unlocked it.
distortedloop said:
Your method is worth a try. I thought you couldn't flash the custom recovery without unlocking the bootloader, but I've seen posts saying you could.
Click to expand...
Click to collapse
Don't flash the recovery, just boot directly from the file.
mazodude said:
fastboot won't work unless you have unlocked it.
Click to expand...
Click to collapse
Yes it does.
Edit:
I just tried this:
First I copied the su-2.3.6.1-ef-signed.zip to /sdcard, then I booted into fastboot mode with (power + volume up). The phone said
LOCK STATE - LOCKED
Click to expand...
Click to collapse
I then booted into Clockwork recovery with
Code:
fastboot boot recovery-clockwork-3.0.0.5-crespo.img
I mounted /system and installed su-2.3.6.1-ef-signed.zip. No errors.
Of course, I noticed no differences at all, because I was already rooted. But nandroid backup obviously worked.
Edit 2:
/system/bin/su didn't have the exact permissions as defined in the install script, but I definitely had root. Was it a new version of su, or the old one? The /system/xbin/su -> /system/bin/su symlink was new, though.
I'm new to the whole thing and in fact still haven't got my phone. I'm just excited and would like to prepare myself.
As I understand it, it is the unlocking / locking of the bootloader that does the wipe. Therefore:
a) As soon as I get my phone, can I unlock the bootloader and then can I go about as if nothing has happened keeping the stock as is for a while to enjoy it that way? When I feel comfortable enough, go about rooting ... later.
b) Would leaving it unlocked cause any problem?
c) will I get updates if I leave the bootloader unlocked and so long as I don't flash custom roms?
Thanks
Paparasee said:
I'm new to the whole thing and in fact still haven't got my phone. I'm just excited and would like to prepare myself.
As I understand it, it is the unlocking / locking of the bootloader that does the wipe. Therefore:
a) As soon as I get my phone, can I unlock the bootloader and then can I go about as if nothing has happened keeping the stock as is for a while to enjoy it that way? When I feel comfortable enough, go about rooting ... later.
b) Would leaving it unlocked cause any problem?
c) will I get updates if I leave the bootloader unlocked and so long as I don't flash custom roms?
Thanks
Click to expand...
Click to collapse
a- yes
b- none that I am aware of. I've left mine unlocked. On other devices, like the Nexus One, you can't re-lock it.
c- yes
Also, there are some posts here lately saying they've been able to root without unlocking by using "fastboot boot recovery.img" (replace recovery.img" with whichever version of clockwork you've downloaded. Then use clockwork to flash the su zip that you'd put on your sdcard before fastboot.
The only post I've only seen where someone says that particular process actually worked is the one right above yours. Note that he was already rooted, but apparently had re-locked his bootloader. I've got no reason to doubt the process if he says it worked...it would be interesting to see someone with a fresh new phone report it works.
On the other hand, since I don't know of any reason to leave your bootloader locked, the only real advantage to that method is not wiping the phone with the oem unlock. If you're on a new phone, there's nothing lost with the wipe.
shrivelfig said:
Don't flash the recovery, just boot directly from the file.
Edit:
I just tried this:
First I copied the su-2.3.6.1-ef-signed.zip to /sdcard, then I booted into fastboot mode with (power + volume up). The phone said
I then booted into Clockwork recovery with
Code:
fastboot boot recovery-clockwork-3.0.0.5-crespo.img
I mounted /system and installed su-2.3.6.1-ef-signed.zip. No errors.
Of course, I noticed no differences at all, because I was already rooted. But nandroid backup obviously worked.
Click to expand...
Click to collapse
That's a good find. First I've ever read of just booting from the recovery image. Does the recovery image file need to be on the phone to do this?
shrivelfig said:
Edit 2:
/system/bin/su didn't have the exact permissions as defined in the install script, but I definitely had root. Was it a new version of su, or the old one? The /system/xbin/su -> /system/bin/su symlink was new, though.
Click to expand...
Click to collapse
The 2.3.2 update changes the permissions of the /system/bin files. Maybe you'd applied that and didn't notice it had changed them?
Fastboot oem unlock, does this do anything else except for rooting your phone, unlocking the bootloader and wiping all your data?
If it doesn't do anything else, there is no harm of rooting your device when you get it, right? You won't notice it?
distortedloop said:
That's a good find. First I've ever read of just booting from the recovery image. Does the recovery image file need to be on the phone to do this?
Click to expand...
Click to collapse
Nope. I think the fastboot command copies the image to the phone first, and then boots it, apparently without any flashing.
The 2.3.2 update changes the permissions of the /system/bin files.
Click to expand...
Click to collapse
Yes, I discovered that when I lost root
When I applied 2.3.2 I did the whole shebang with backup, unlock, flash, su, busybox, relock and restore. After all that I discovered that I could boot the phone directly into Clockwork from a Windows command prompt. I did a nandroid backup and fix permissions just to test. Hard to tell who fingered the su permission last
I'd test more, but right now I'm loath to unroot.
Androyed said:
Fastboot oem unlock, does this do anything else except for rooting your phone, unlocking the bootloader and wiping all your data?
Click to expand...
Click to collapse
It doesn't actually root. It just unlocks (so that you can flash non-standard stuff, like root) and wipes.
I accidentally wiped my TF300 and now i cant even get it to go into bootloader, it just goes straight to TWRP. I'm know what i did wrong - causing the wipe- but now i cant get any img to apply to the tab. it will mount system but not cache or anything else. i cant change my recovery because i cant get to bootloader. Any ideas??
LancasterCI said:
I accidentally wiped my TF300 and now i cant even get it to go into bootloader, it just goes straight to TWRP. I'm know what i did wrong - causing the wipe- but now i cant get any img to apply to the tab. it will mount system but not cache or anything else. i cant change my recovery because i cant get to bootloader. Any ideas??
Click to expand...
Click to collapse
Dude... I could be wrong, but enjoy your paperweight.
You might have luck doing this. Go to Asus site and download the full image for your tablet based on SKU region. Extract it to get the blob file. Do you have fastboot setup? Turn off your tablet completely and turn it on my holding the vol down and power it should allow you to boot into fast boot. You can flash the image that way. By
> fastboot -i 0x0B05 flash system C:...\Path-to-blob\blob
> fastboot -i 0x0B05 reboot
LancasterCI said:
I accidentally wiped my TF300 and now i cant even get it to go into bootloader, it just goes straight to TWRP. I'm know what i did wrong - causing the wipe- but now i cant get any img to apply to the tab. it will mount system but not cache or anything else. i cant change my recovery because i cant get to bootloader. Any ideas??
Click to expand...
Click to collapse
If you were on JB download 10.4.2.20, unzip once and place the new zip on your external sdcard. If you were on ICS choose 9.4.3.30 unzip once and place the new zip on your external sdcard.
install zip with twrp.
Good Luck!
hmm
ok just to make sure i am looking for my correct SKU would it be JP or US i beleive the latter since i am in ths US, but i do want to make sure as to to make the problem worse
LancasterCI said:
ok just to make sure i am looking for my correct SKU would it be JP or US i beleive the latter since i am in ths US, but i do want to make sure as to to make the problem worse
Click to expand...
Click to collapse
If you have a US tablet then US.
more issues
So i have the correct Firmware matching SKU, but whe i go to flash i get the following error
E: unable to mount ' /data ' (tw_mount)
E: unable to mount ' /cache ' (tw_mount)
then is repeats but it dose verify the filesystems and partition sizes
Any other ideas. just but this but not sure if bricked is and excuse for a return
LancasterCI said:
So i have the correct Firmware matching SKU, but whe i go to flash i get the following error
E: unable to mount ' /data ' (tw_mount)
E: unable to mount ' /cache ' (tw_mount)
then is repeats but it dose verify the filesystems and partition sizes
Any other ideas. just but this but not sure if bricked is and excuse for a return
Click to expand...
Click to collapse
Were you on 4.2.1 prior to this or encrypted?
LancasterCI said:
So i have the correct Firmware matching SKU, but whe i go to flash i get the following error
E: unable to mount ' /data ' (tw_mount)
E: unable to mount ' /cache ' (tw_mount)
then is repeats but it dose verify the filesystems and partition sizes
Any other ideas. just but this but not sure if bricked is and excuse for a return
Click to expand...
Click to collapse
Don't use clockwork. Extract the zip until you see the blob file. Use fastboot to flash it. It is very easy to do. see my post above. Good luck
defiantj3 said:
Don't use clockwork. Extract the zip until you see the blob file. Use fastboot to flash it. It is very easy to do. see my post above. Good luck
Click to expand...
Click to collapse
OP can't access the bootloader menu so he can't access fastboot.
Thanks for trying.
tobdaryl said:
Were you on 4.2.1 prior to this or encrypted?
Click to expand...
Click to collapse
i did have the latest ota update i believe 4.2.1
LancasterCI said:
i did have the latest ota update i believe 4.2.1
Click to expand...
Click to collapse
I was afraid that was where we were going.
The good, bad, and the ugly.
I'm sorry to tell you that you will probably stuck here until we get the full firmware update from Asus. We are hoping it will drop this week.
I don't know how to help yet on 4.2.1.
Here is a thread you might want to subscribe to where people with your issue are gathering till a resolution is found.
I wish I had better news but the one good thing I can say is there are some devs watching the thread and preparing for the release.
Good Luck!
tobdaryl said:
I was afraid that was where we were going.
The good, bad, and the ugly.
I'm sorry to tell you that you will probably stuck here until we get the full firmware update from Asus. We are hoping it will drop this week.
I don't know how to help yet on 4.2.1.
Here is a thread you might want to subscribe to where people with your issue are gathering till a resolution is found.
I wish I had better news but the one good thing I can say is there are some devs watching the thread and preparing for the release.
Good Luck!
Click to expand...
Click to collapse
Well any idea exactly what happened or if it is even fixable??
LancasterCI said:
Well any idea exactly what happened or if it is even fixable??
Click to expand...
Click to collapse
We think it has to do with encryption of your tablet when updating to 4.2.1 and the effects are not removed by downgrading.
update-binary also changed with 4.2.1 and we are looking into the changes as they need to be known to create zips for flashing. Other changes as well.
4.2.1 appears to encrypt by default; I think it is done to enable multi-user to restrict access to any other account.
Sorry I forgot fixable. Yes I believe once the update drops it will be resolved. That is why I provided the link.
tobdaryl said:
We think it has to do with encryption of your tablet when updating to 4.2.1 and the effects are not removed by downgrading.
update-binary also changed with 4.2.1 and we are looking into the changes as they need to be known to create zips for flashing. Other changes as well.
4.2.1 appears to encrypt by default; I think it is done to enable multi-user to restrict access to any other account.
Sorry I forgot fixable. Yes I believe once the update drops it will be resolved. That is why I provided the link.
Click to expand...
Click to collapse
Thanks to all for the help will continue to chck back.. Thank god for my nexus 7
LancasterCI said:
Thanks to all for the help will continue to chck back.. Thank god for my nexus 7
Click to expand...
Click to collapse
I'm sorry.
Good Luck!
Hi LancasterCI,
After several test with the new ota update I have also had similar issue with recovery no being able to mount anything but system.
However my fastboot was still working so we need to get that up and running first.
What I believe is happening is that the new bootloader is not actually encrypting anything but rather reformatting the cache, data partitions to a format that twrp & cwm are not looking for.
pjc21; said:
After reading through some of the posts in the twrp thread with similar issues. I seems that twrp looks for these partitions (data, system, cache, etc) to be in a certain format, ie ext4. However is the ext twrp is looking for does not exist (say the ext4 is now ext3) twrp will assume that it is encrypted and will bring up a password prompt and be unable to mount.
So with the test I have done to confirm that flashing just the new 4.2.1 bootloader and nothing else wiil encrypt the custom recoveries, could it be that the new 4.2.1 bootloader is reformatting these partitions to some other format making twrp & cwm assume that these partitions are now encrypted??
Click to expand...
Click to collapse
What we need to do 1st is get fastboot working for you, now I think we can get adb working by following this how-to just follow on from the device manager part to get adb working in recovery provided you have adb setup on your pc already.
Once you have adb working try the following command to reboot into bootloader, sometimes the tab just needs a hard reboot.
Code:
adb reboot bootloader
If this works, boot into fastboot and follow my post here, once done you'll be back on stock 4.1.1 but will then be able to boot back into fastboot and flash custom recovery and custom rom again.
Hope this helps.
pjc21 said:
Hi LancasterCI,
After several test with the new ota update I have also had similar issue with recovery no being able to mount anything but system.
However my fastboot was still working so we need to get that up and running first.
What I believe is happening is that the new bootloader is not actually encrypting anything but rather reformatting the cache, data partitions to a format that twrp & cwm are not looking for.
What we need to do 1st is get fastboot working for you, now I think we can get adb working by following this how-to just follow on from the device manager part to get adb working in recovery provided you have adb setup on your pc already.
Once you have adb working try the following command to reboot into bootloader, sometimes the tab just needs a hard reboot.
Code:
adb reboot bootloader
If this works, boot into fastboot and follow my post here, once done you'll be back on stock 4.1.1 but will then be able to boot back into fastboot and flash custom recovery and custom rom again.
Hope this helps.
Click to expand...
Click to collapse
ok I got back into the boot loader but i cant flash anyhting it wont even let me change my recovery
I get this message
"erroe: cannot load 'stock.blob' : No error"
The 4.2.1 update is on Asus so with luck we will start to see resolutions for these problems
Found the ultimate recovery, the receipt!!! The retailer exchanged it no questions asked. I know it the noon way out but now I have a fresh slate to start with and won't be flashing 4.2 anytime soon. I do however want to thank you all for your support and help. I'm definitely gonna be modding my tab as soon as the devs get a good fix going. BTW would love to for and a toolkit for this eventually, please devs??
Sent from my Nexus 7 using xda app-developers app
Increase 1GB in /data partition for more userdata and apps.
!!!ADVISE!!! -> ----THIS DO A RESET TO THE PHONE !!! DO BACKUP FROM YOUR DATA (USE DEFAULT APP FROM THE PHONE FOR THAT)----
-------------------------------------------------------------------------------------------------------/data partition
Also called userdata, the data partition contains the user’s data – this is where your contacts, messages, settings and apps that you have installed go. Wiping this partition essentially performs a factory reset on your device, restoring it to the way it was when you first booted it, or the way it was after the last official or custom ROM installation. When you perform a wipe data/factory reset from recovery, it is this partition that you are wiping.
--------------------------------------------------------------------------------------------------------
First check your partitions like they are with any app for that from Google Play, for example https://play.google.com/store/apps/details?id=me.kuder.diskinfo&hl=pt_PT , than check after the change.
It need TWRP recovery to flash the zips.
1º extract the zips from the main zip to external sd card
2º flash the zip Update-resize to increase 1GB to /data partition.
3º boot the phone and ingnore the settings
4º turn off and flash the zip with default recovery (L-default_recovery.zip)
5º boot in to recovery (the default recovery) and do a factory reset
6º done!
This increase 1024MB = 1GB in user data for apps, etc and decrease it in sdcard0.
I say L model because i think all L model have the same size for storage, i only test in L11, but i think it works in L22 and L33, if any one whant ot test please let a post.
you can check with any partition app from google play.
-Resize partitions L model
https://mega.nz/#!7xgTmb6J!sRG5_fIguL8I9jrM921EjpyeATRhXmkhOMhYTtx-zII
to go back to default, follow the the steps above but with Update_orig-G6-L11.zip, i dont test with L22, L33 models but the have the same partitions if any one try it let a post.
This is how it is in my phone after the change
is this for B370 users? i'm on b117 and planning to update to B370, want to know what should i do first? Doing THIS or updating first?
First update than change partitions sizes, is better.
Hello persona78
I try with my phone, but the flash with update-resize doesn't work (abort).
My phone is g6-l11 b 370 and it is rooted
Could you help me please?
Thank you
Christian
sleo38 said:
Hello persona78
I try with my phone, but the flash with update-resize doesn't work (abort).
My phone is g6-l11 b 370 and it is rooted
Could you help me please?
Thank you
Christian
Click to expand...
Click to collapse
What say in error???
Hello
The exact texte is:
--- OTA update
Finding update package. ..
Openning update package...
Verifying update package...
Formating /cache...
Installation aborded .
Are you using TWRP or the default recovery?????
First i have used ROM Manager. Then TWRP with the same bad result.
TWRP doesn't propose g6-l11
Both with ROM Manager and TWRP lounch the same recovery
You bootloader is unlocked?
No, it is the original bootloader
Something is not correct, check if bootloader is really unlocked.
Twrp have a blue screen, use Google to find twrp screen, see is the same you have.
The bootloader is not unlocked.
When i try to instal twrp, g6-l11 model is not in th list of devices
sleo38 said:
No, it is the original bootloader
Click to expand...
Click to collapse
Ok...
with the phone OFF
press vol - and power, release power when turn ON, vol - when you see a screen.
It says, Locked or Unlocked????
It is write PHONE Locked on the bottow
sleo38 said:
It is write PHONE Locked on the bottow
Click to expand...
Click to collapse
Tha is your bootloader and is locked, you can't do nothing if is locked.
There are a post in this group that help you to unlock.
persona78 said:
Tha is your bootloader and is locked, you can't do nothing if is locked.
There are a post in this group that help you to unlock.
Click to expand...
Click to collapse
Hi personna78
You are right. I have unlocked the bootloader and now every thing works
Thank you
This is awesome, makes the phone a lot more useful.
Is it safe to put TWRP back on after using this mod? Also is there a way to switch to SuperSU?
Lum_UK said:
This is awesome, makes the phone a lot more useful.
Is it safe to put TWRP back on after using this mod? Also is there a way to switch to SuperSU?
Click to expand...
Click to collapse
You can return to twrp.
SuperSU doesn't work on G6, sorry
Factory reset necessary?
Thanks a lot for this script.
Question: is it necessary to do the factory reset when resizing /data (including the flashing of the default recovery image)? Or, is this done implicitly by the script which removes and re-creates the partition?
Also, I may have had an issue with the update to /data not being effective because it was still mounted (by default on TWRP, it seems). Perhaps a "umount" could be added to the script?
---------- Post added at 07:42 PM ---------- Previous post was at 07:37 PM ----------
Hmm... as for the umount, it seems to be there, maybe it was another issue...
Thanks a lot!
It worked fine to me.
Regards.
Hi,
I have a friend that has a Moto G 2nd gen and she forgot her pin number.
She want to retrieve some data that are stored in the phone. I told her to install TWRP so then she could use TWRP file manager to erase the protection files and then access the phone to retrieve the info.
Her phone has no root or anything.
Is it possible to install TWRP to do that or is there another way ?
Thanks in adv
Anyone can help me ? Plz
Elsin10 said:
Anyone can help me ? Plz
Click to expand...
Click to collapse
She needs to unlock the bootloader before flashing the TWRP. But after she unlocks the bootloader, the /data partition will be automatically wiped. So i guess, that it will be better if she tries to think about the pin for some time (maybe she will remember) before unlocking BL and flashing TWRP
dc239 said:
She needs to unlock the bootloader before flashing the TWRP. But after she unlocks the bootloader, the /data partition will be automatically wiped. So i guess, that it will be better if she tries to think about the pin for some time (maybe she will remember) before unlocking BL and flashing TWRP
Click to expand...
Click to collapse
Ohhh damn. Too bad that there isn't any other way.
I will tell her that.
Thanks for the reply
After i wanted to install Android P, i got a bootloop. so i wanted to go to twrp but now my files are encrypted and twrp is not asking for a pin or pattern so i can't decrypt my internal storage files.
Now the biggest problem is that i just came back from a family weekend and i made a lot of pictures, witch i can't acces now, and i really want them back.
Now i can't install a new os or anything ...
Can someone please help me! i'm really despirate
(sorry for my bad english)
Try downgrading twrp , night get it to ask for pin
downgrading is never the answer. In fact, that will cause this problem to happen. Now i must ask, are you temp booting twrp or is twrp installed to phone.
I got this when I temp booted the mtp enabled twrp the other day, although it still asked for my passcode and said description was successful. When I rebooted the installed (official) twrp it all came back....
MrSteelX said:
downgrading is never the answer. In fact, that will cause this problem to happen. Now i must ask, are you temp booting twrp or is twrp installed to phone.
Click to expand...
Click to collapse
Now i am booting from temp twrp, before that i got the latest twrp installed
Bringing this back up... Did booting from temp twrp work? Ran into the same issue.
Temp boot and use the usb c to pull ur data from the device to a computer. After that you can wipe and start over. Unbricking guide available in the help section
Having the same issue. If I boot using fastboot TWRP I'm able to decrypt data. I did that and flashed stock OOS and the same TWRP version (BluSpark) that was used in the fastboot. But the folders are still encrypted. It's weird how a fastboot can decrypt it but a regular recovery boot can't. Is there any alternatives available?
I'm in the process of backing up my data before I officially bite the bullet.
spartan268 said:
Having the same issue. If I boot using fastboot TWRP I'm able to decrypt data. I did that and flashed stock OOS and the same TWRP version (BluSpark) that was used in the fastboot. But the folders are still encrypted. It's weird how a fastboot can decrypt it but a regular recovery boot can't. Is there any alternatives available?
I'm in the process of backing up my data before I officially bite the bullet.
Click to expand...
Click to collapse
Only way i know to get rid of this by removing the encryption on the data is to Format the Internal Storage !
Totone56 said:
Only way i know to get rid of this by removing the encryption on the data is to Format the Internal Storage !
Click to expand...
Click to collapse
That's what I did in the end. I just backed up my media through fastboot TWRP beforehand. Beats having to use the download tool at least
spartan268 said:
That's what I did in the end. I just backed up my media through fastboot TWRP beforehand. Beats having to use the download tool at least
Click to expand...
Click to collapse
Probably the best way indeed. I think i'm gonna start disabling forced encryption to stop these kind of problems.
Totone56 said:
Probably the best way indeed. I think i'm gonna start disabling forced encryption to stop these kind of problems.
Click to expand...
Click to collapse
How to do it? I tried with zero luck
starche_old said:
How to do it? I tried with zero luck
Click to expand...
Click to collapse
I haven't tried yet, don't know for now !