this Recovery is now depreciated go https://forum.xda-developers.com/showthread.php?p=71244945 instead
What's new
MTP auto mount on boot fixed!
Data unmount after few seconds fixed.
Bugs
Battery Info doesn't work (due to M based sources)
Data decryption
Mount Loop devices (Kernel issue) can't be fixed atm
Credits: TWRP (Team win Recovery Project)
Huawei
@BadWolfYe for giving info on how he got MTP working.
Me
Current status: Stable
Created: 2016-11-20
Removed
LastStandingDroid said:
This was shared here for reasons that some P9 users came to our H8 thread so i decided to post it here as well.
Click to expand...
Click to collapse
Thank you so much for your hard work. When you say data works but requires reflash could you explain which part requires reflash?
Regards
Lee
Just to clarify, does this allow mounting and editting of /system partition, manually via TWRP terminal?
Atarii said:
Just to clarify, does this allow mounting and editting of /system partition, manually via TWRP terminal?
Click to expand...
Click to collapse
Yes you can mount cust, data, system, product, vendor
thel2dab said:
Thank you so much for your hard work. When you say data works but requires reflash could you explain which part requires reflash?
Regards
Lee
Click to expand...
Click to collapse
The properdata fix will flash a empty image to the phone which you'll have to resize after flash or I'll get 2.Gb of internal storage only.you might need repair data first or reboot recovery for it to be repairable.
Sent from my FRD-L09 using Tapatalk
U are best.
Does flashing ROM's work?
I whant to flash newest N emui 5.0 wihout roolback
I don't know why but my phone fails to boot after flashing the properdatafix.zip and resizing.
It resizes correctly but after it won't boot. I have to flash old firmware and upgrade to to 7.0 again.
Any help would be great.
Regards
Lee
richish said:
U are best.
Does flashing ROM's work?
I whant to flash newest N emui 5.0 wihout roolback
Click to expand...
Click to collapse
It flashes firmwares yes I've reflashed N and the hw_EU full package
thel2dab said:
I don't know why but my phone fails to boot after flashing the properdatafix.zip and resizing.
It resizes correctly but after it won't boot. I have to flash old firmware and upgrade to to 7.0 again.
Any help would be great.
Regards
Lee
Click to expand...
Click to collapse
Exactly what did you flash? AFAIK if it is a zip that mounts a image it will either bill the flash process with a reboot or make your device stuck on splash screen. What zip did u use?
If.u flashed N pack from M twrp u can install it again with this twrp. If it doesn't boot then it's probably due to a Img (ext4) that is being mounted and that's most likely is due to modified boot.img which will kill the boot procedure supersu package can make a modified boot but it won't boot due to su.img being mounted so it'll reboot to recovery
Sent from my FRD-L09 using Tapatalk
LastStandingDroid said:
Exactly what did you flash? AFAIK if it is a zip that mounts a image it will either bill the flash process with a reboot or make your device stuck on splash screen. What zip did u use?
Click to expand...
Click to collapse
I flashed the properdatafix.zip from the 1st post. Then rebooted in to twrp went to wipe - advanced wipe - data - resize partion - reboot - stuck on black screen.
fastboot flash, recovery, boot, system, from stock to get device booting again.
I must be doing something wrong. I know this is really cheeky to ask but could you make a video or something of the correct flashing procedure? The way I have tried is like this:
1 Fastboot flash your recovery.img
2. Boot into TWRP recovery.
3. Install properdatafix.zip
4. Reboot recovery.
5. Resize data partition.
6. Reboot and phone wont boot anymore.
Regards
Lee
thel2dab said:
I flashed the properdatafix.zip from the 1st post. Then rebooted in to twrp went to wipe - advanced wipe - data - resize partion - reboot - stuck on black screen.
fastboot flash, recovery, boot, system, from stock to get device booting again.
I must be doing something wrong. I know this is really cheeky to ask but could you make a video or something of the correct flashing procedure? The way I have tried is like this:
1 Fastboot flash your recovery.img
2. Boot into TWRP recovery.
3. Install properdatafix.zip
4. Reboot recovery.
5. Resize data partition.
6. Reboot and phone wont boot anymore.
Regards
Lee
Click to expand...
Click to collapse
You can install the firmware again after you resized the data partition if something goes wrong and report back if it helps. Maybe it is a block issue in fstab but it shouldn't be
Sent from my FRD-L09 using Tapatalk
@LastStandingDroid
I also will not boot in the system...
What file system (data) should be displayed in TWRP, ext4?
LastStandingDroid said:
You can install the firmware again after you resized the data partition if something goes wrong and report back if it helps. Maybe it is a block issue in fstab but it shouldn't be
Sent from my FRD-L09 using Tapatalk
Click to expand...
Click to collapse
How should I install the firmware again? Through flashable zip or through dload folder and hold vol up and down when restarting phone? Thank you for your patience, I know I am taking a lot of your time with this.
Regards
Lee
kep2008 said:
@LastStandingDroid
I also will not boot in the system...
What file system (data) should be displayed in TWRP, ext4?
Click to expand...
Click to collapse
The data should be ext4 format. Could u mount system and check if there's any file in system folder also u might need to resize system as well since u only have 19mb as well.
thel2dab said:
How should I install the firmware again? Through flashable zip or through dload folder and hold vol up and down when restarting phone? Thank you for your patience, I know I am taking a lot of your time with this.
Regards
Lee
Click to expand...
Click to collapse
Sent from my FRD-L09 using Tapatalk
thel2dab said:
How should I install the firmware again? Through flashable zip or through dload folder and hold vol up and down when restarting phone? Thank you for your patience, I know I am taking a lot of your time with this.
Regards
Lee
Click to expand...
Click to collapse
I'd use twrp to flash it.since u won't have to roll back again
Sent from my FRD-L09 using Tapatalk
LastStandingDroid said:
I'd use twrp to flash it.since u won't have to roll back again
Sent from my FRD-L09 using Tapatalk
Click to expand...
Click to collapse
Thanks. It seems to reflash ok in TWRP but after the flash completes. I need to factory reset but I am back to to stock recovery. It seems that flashing the update.zip overwrites the recovery. (I assume this is expected?)
Thanks again for your help. Is there is anything else I can try to get this to work?
Regards
laststandingdroid said:
the data should be ext4 format. Could u mount system and check if there's any file in system folder also u might need to resize system as well since u only have 19mb as well.
Sent from my frd-l09 using tapatalk
Click to expand...
Click to collapse
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Again install update.zip 7.0, but the system will not boot...
thel2dab said:
Thanks. It seems to reflash ok in TWRP but after the flash completes. I need to factory reset but I am back to to stock recovery. It seems that flashing the update.zip overwrites the recovery. (I assume this is expected?)
Thanks again for your help. Is there is anything else I can try to get this to work?
Regards
Click to expand...
Click to collapse
Yes the recovery is replaced after flash back stock. Did it boot after reflashed?
Strange are you having Vendor And product option available in Mount restore and backup? To see if they are properly flashed?
kep2008 said:
View attachment 3948500View attachment 3948501
Again install update.zip 7.0, but the system will not boot...
Click to expand...
Click to collapse
Did you get the data to work in TWRP? I think the boot.img is the issue here tbh. Since I neither can't boot unless I use a supersu fixed image.
Sent from my FRD-L09 using Tapatalk
Ok w8 I'll fix a twrp that will make the installation of su system less mode possible but u will be forced to remove su.img from /data/ else it won't boot
fastboot flash this: http://www21.zippyshare.com/v/7YNPp3AI/file.html
Before You Flash SuperSU-Systemmode you need to mount system & /vendor first since the Sepolicy is located in the "Vendor" Partition for reasons i won't bother to explain.
Once Flashed Mount Data again (if it gets unmounted, mount system) and navigate to /data and remove su.img
This will make N booting
Sent from my FRD-L09 using Tapatalk
LastStandingDroid said:
Yes the recovery is replaced after flash back stock. Did it boot after reflashed?
Strange are you having Vendor And product option available in Mount restore and backup? To see if they are properly flashed?
Did you get the data to work in TWRP? I think the boot.img is the issue here tbh. Since I neither can't boot unless I use a supersu fixed image.
Sent from my FRD-L09 using Tapatalk
Click to expand...
Click to collapse
/data is mounted only with /system, but the installation files still contain errors /data/media
mount -o bind /data/media /sdcard process ended with ERROR 255
kep2008 said:
/data is mounted only with /system, but the installation files still contain errors /data/media
mount -o bind /data/media /sdcard process ended with ERROR 255
Click to expand...
Click to collapse
Did u use the new recovery? If so that is for now common since it uses a different mount file rather than busbox version) that's why this message comes
In fact I copied over the "original" mount file from stock recovery but it isn't copying the compete file as it's only 6b so it'll stay until I try fix it.
Sent from my FRD-L09 using Tapatalk
Related
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
You are looking for a special modded Clockworkmod recovery?
Clockworkmod Recovery v4.0.0.5
removed downloadlinks cause of issues with the new unity kernel.
please use this very special recovery
Just have a look on this site: 4EXTRecovery v1.1.1 | STAY @EXT4 | Convert EXT4 without losing data | Advanced Backup
Clockworkmod Recovery v3.2.0.0
downloadlink:
PG88IMG-RECOVERYIMG-3.2.0.0.zip
Clockworkmod Recovery v3.1.0.1
downloadlink:
PG88IMG-RECOVERYIMG-3.1.0.1.zip
or visit my blog dev page: lbc mod android development - custom recovery
Install Instructions:
download the zip package
rename it to PG88IMG.zip
put that file on the root of your sd card
start you phone in bootloader (hboot not fastboot)
the bootloader will ask you if you want to install recovery.img
confrim
reboot
rename the file again into something else (cause bootloader will always try to flash if a PG88IMG.zip file is on your sd card
loveboatcaptain said:
Hey Guys,
just have the first booting version of ClockworkMod Recovery v.3.0.2.4 on my phone.
View attachment 575564
a full working beta will come in the next days.
Install instructions will follow, too.
CREDITS: this is basicly the work of HCDR.Jacob how helped my to build this, cause my macbook sucked at building from source. so give him a big tanks too ;-)
see you later with a download for everyone with s-off
regards
Click to expand...
Click to collapse
woohoo
you are great
Ah mr mac user succeeded gratz
Sent from my HTC Incredible S using XDA Premium App
Hawkysoft said:
Ah mr mac user succeeded gratz
Click to expand...
Click to collapse
Yeah, with a little help from my friends ;-)
Jacob is fixing the last bugs and than i think were done and can do some tests before release.
regards
Maybe ours work for you to, koush made ours public today. Ill give u the info tomorrow, should be all the same
Sent from my HTC Incredible S using XDA Premium App
the beta tests have finished...
we talked to koush and he put it into ROM MANAGER just in this minute...
so happy flashing for all with s-off and root.
regards
p.s. don´t forget to thank HCDR.Jacob. He build it together and fixed the bugs and of course koush for pushing it so quick to ROM MANAGER.
thx to this great community
loveboatcaptain said:
Hey Guys,
[ROMmanager]
regards
Click to expand...
Click to collapse
Cool - working, thanks!
running backup now - so let the de-sense begin - I always brake some things when playing around to strip sense, so great to have full backup...
dont know said:
Cool - working, thanks!
running backup now - so let the de-sense begin - I always brake some things when playing around to strip sense, so great to have full backup...
Click to expand...
Click to collapse
feel free to test my first rom ;-)
this would be easier to "de-sense" cause it´s allready deodexed. so you needn´t delete so much stuff ;-)
a light version will follow the nexts days, which will be "de-sensed" and have a custom launcher like ADW or LP
regards
loveboatcaptain said:
feel free to test my first rom ;-)
this would be easier to "de-sense" cause it´s allready deodexed. so you needn´t delete so much stuff ;-)
a light version will follow the nexts days, which will be "de-sensed" and have a custom launcher like ADW or LP
regards
Click to expand...
Click to collapse
It's a very light desense I want (only get rid of the ad-ware inkluded and some others like twitter..)
I'm on ADW because of the cool themes available.
THANKS for the possibility of real rooting (unsecure and clockwork) again..
Hi, how can I root my desire s save
Sent from my Desire S using XDA Premium App
M0ng0 said:
Hi, how can I root my desire s save
Sent from my Desire S using XDA Premium App
Click to expand...
Click to collapse
Hey, today i unlocked mine with an xtc clip.
Then I flashed the unsecured Boot Image. I hope it is called so .
After that worked successful, i rooted it with SuperOneKlick.
Maybe this works for you too.
Any chance you can get in touch with the developer of this as there seems to be a very annoying bug.
Everytime i include:
format CACHE or
format("ext4", "EMMC", "/dev/block/mmcblk0p27", "/cache");
the recovery will not flash the ZIP. It will always give a STATUS 1 error.
So i have to manually format cache and run my ZIPS.
Thanks.
anybody successfully tried to revert on stock recovery?
fastboot says "FAILED (remote: not allowed)", and with cwm recovery it's impossible to try new OTA...
MarylandCookie said:
Any chance you can get in touch with the developer of this as there seems to be a very annoying bug.
Everytime i include:
format CACHE or
format("ext4", "EMMC", "/dev/block/mmcblk0p27", "/cache");
the recovery will not flash the ZIP. It will always give a STATUS 1 error.
So i have to manually format cache and run my ZIPS.
Thanks.
Click to expand...
Click to collapse
hey dude,
i ported the recovery together with a friend. so i´m your man ;-)
i never noticed that there is a problem with formating cache partition, cause i don´t touch it with my updater-script.
so first question:
why you will add that to your updater-script? me for myself prefere the way of wiping my phone manually. and that works very well with CMR. i also tested it in the mount/partition menu.
i would not like it, when a script wipes stuff and i did not know about.
i only use format for system in my full update.zip´s. in updates for my rom i did not wipe anything.
second question: did you know that cache partition is always mounted when recovery starts? perhaps thats the problem.
regards
mih_ said:
anybody successfully tried to revert on stock recovery?
fastboot says "FAILED (remote: not allowed)", and with cwm recovery it's impossible to try new OTA...
Click to expand...
Click to collapse
those fastboot commands only works with an ENG S-Off bootloader. which we dont have. we have SHIP S-Off... there are differences between those both.
our bootloader can everything the ENG can with fastboot commands. we have to use a zip file to flash things like recovery or splash.
you have to add your recovery backup img into my PG88IMG-unsecured_bootimg.zip file from this post [BOOT] Root for S-Off with unsecured Boot Image rename it to PG88IMG.zip and add your recovery.img into that zip file and remove the boot.img file.
than put the file on the root of your sdcard and reboot into bootloader.
the file will be flashed automaticly.
after reboot your phone, rename the file again to something else, cause every time you are in bootloader and this file is named PG88IMG.zip on your sdcard thhe bootloader will try to flash it.
just a little tipp at the end: you can add every img file into this zip. system and data img files from nandroid backups are working too ;-)
regards
Thank you!
I'll try it next time, i'll need it
But i've managed to flash it through flash_image from this link:
http://forum.xda-developers.com/wiki/index.php?title=HTC_Vision#HBOOT_partition_map
with recover.img from OTA downloaded.
After OTA i've lost the root, but gingerbreak still works...
mih_ said:
Thank you!
I'll try it next time, i'll need it
But i've managed to flash it through flash_image from this link:
http://forum.xda-developers.com/wiki/index.php?title=HTC_Vision#HBOOT_partition_map
with recover.img from OTA downloaded.
After OTA i've lost the root, but gingerbreak still works...
Click to expand...
Click to collapse
Could you PLEASE give me a short (or long ) description how to install the ota?
No idea what to do with the linked code...
EDIT Extracted the boot.img from ota and copoed it to PG88IMG.zip - restart - run ota-update -> fail
EDIT2 I'm an idiot: instead of boot.img it is a great idea to try it with recovery.img *LOL*
You just have to replace clockworkmod ecovery with stock one.
I've taken it from OTA downloaded.
It contains file firmware.zip inside, which contains recovery.img as well.
You can flash it with tool flash_image (http://www.thinkthinkdo.com/trac/project1/raw-attachment/wiki/vision_utilities/flash_image.zip)
Just put it somewhere to device, where you can run it (for instance/data/local/bin/, /system/bin/ if remounted to rw, /sdcard if remounted to exec)
and run from device or adb shell like%
su
flash_image recovery /sdcard/recovery.img
after that, you can reboot to hboot, check out that you do not have cwm recovery anymore, boot to android and install OTA as usual from menu...
does the recovery also do a backup of the radio?
(my wifi is broken sinve ota update - and I'm an stock recovery now, so can't test at the moment)
Cache being mounted or unmounted isnt the issue.
I can wipe cache manually but automatting it in the script seems the break the whole process.
Its good for testing and having a fresh install.
Lets android re-build everything.
Take from Clockworks How to:
wipe cache partition
Wipes the cache partition of the device to clear all the data accumulated there over use. This is often used before installing a new ROM, app, kernel or any similar mod via recovery
Click to expand...
Click to collapse
http://www.addictivetips.com/mobile...-and-how-to-use-it-on-android-complete-guide/
This is a flashable ZIP, containing the latest kernel and build of Android 4.3 by Google. It is made for the Google Nexus 7 3G, and is flashable through TWRP. I did not test it since I don't have a 3G model of the Nexus 7.
Download link: https://mega.co.nz/#!xskHxaRb!ZP3kYCk66VinJc70TswVBSAv8yZ3QoKKgUCtzVe66lY
Odexed, and no superuser management tool. Chainfire released an experimental version supporting Android 4.3 on his Google+. so I'll add that to the OP later.
Enjoy!
Anybody tested?
Also, will there be radio and bootlosder in flashable form?
Fatal1ty_18_RUS said:
Anybody tested?
Also, will there be radio and bootlosder in flashable form?
Click to expand...
Click to collapse
From what i can see, there is no bootloader and radio in it, so anyone has to flash it by himself.
EDIT: The ZIP works fine, i just flashed bootloader and radio through fastboot prior to installing it over TWRP. Haven't tested any root zips, yet.
i got 4.3
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Root does work, flashing this zip. Although Titanium Backup didn't work at first, i installed busybox, changed the backups location from /storage/emulated/0 -> /storage/emulated/legacy and i had to uncheck the first backup to make the restore work (no idea which of those three things actually did the work).
biggoldring said:
Click to expand...
Click to collapse
That's great, but can someone explain why baseband is still old (i've flashed 0.18 and on fastboot i see the correct version, but on System->About i get still 0.17)?
stadicon said:
Root does work, flashing this zip. Although Titanium Backup didn't work at first, i installed busybox, changed the backups location from /storage/emulated/0 -> /storage/emulated/legacy and i had to uncheck the first backup to make the restore work (no idea which of those three things actually did the work).
That's great, but can someone explain why baseband is still old (i've flashed 0.18 and on fastboot i see the correct version, but on System->About i get still 0.17)?
Click to expand...
Click to collapse
you mean you flash the zip in stock recovery??
Gabrieltan said:
you mean you flash the zip in stock recovery??
Click to expand...
Click to collapse
I don't have stock recovery, TWRP remained untouched through this process. I just installed this zip to gain root access through TWRP, then changed setting in Titanium Backup to make it work..
stadicon said:
I don't have stock recovery, TWRP remained untouched through this process. I just installed this zip to gain root access through TWRP, then changed setting in Titanium Backup to make it work..
Click to expand...
Click to collapse
so your point is flash the rom then direct flash the zip?? because if boot then flash the zip definitely TWRP will lose. Am i right?
Gabrieltan said:
so your point is flash the rom then direct flash the zip?? because if boot then flash the zip definitely TWRP will lose. Am i right?
Click to expand...
Click to collapse
No, why it should get lost?
The process i did was:
1) Boot at bootloader ([POWER]+[VOL-])
2) fastboot flash bootloader <bootloader.img>
3) fastboot flash radio <radio.img>
4) Start recovery (TWRP)
5) Flash stock-4.3 zip
6) Flash SuperSU zip
That's all. Neither recovery, nor userdata were touched through this process. The only affected partitions are bootloader, radio, system, boot and data.
stadicon said:
No, why it should get lost?
The process i did was:
1) Boot at bootloader ([POWER]+[VOL-])
2) fastboot flash bootloader <bootloader.img>
3) fastboot flash radio <radio.img>
4) Start recovery (TWRP)
5) Flash stock-4.3 zip
6) Flash SuperSU zip
That's all. Neither recovery, nor userdata were touched through this process. The only affected partitions are bootloader, radio, system, boot and data.
Click to expand...
Click to collapse
i just full wipe my tilapia.. lolx.. anyway, i have backup all of my apps in zip file.. hahaha
one thing can confirm is no need flash bootloader.. i didnt flash it still ok.. but radio i not sure yet..because dont have simcard right now..lolx
Gabrieltan said:
i just full wipe my tilapia.. lolx.. anyway, i have backup all of my apps in zip file.. hahaha
one thing can confirm is no need flash bootloader.. i didnt flash it still ok.. but radio i not sure yet..because dont have simcard right now..lolx
Click to expand...
Click to collapse
You mean you download zip file from OP, then flash it in TWRP?
Sent from my GT-N7105 using Tapatalk 4 Beta
zard said:
You mean you download zip file from OP, then flash it in TWRP?
Sent from my GT-N7105 using Tapatalk 4 Beta
Click to expand...
Click to collapse
yup.. without flash bootloader.. now trying for titanium.. where can change the storage thing?
Gabrieltan said:
yup.. without flash bootloader.. now trying for titanium.. where can change the storage thing?
Click to expand...
Click to collapse
This is Chainfire's information: You can fix this by going into preferences and selecting a folder under /storage/emulated/legacy as backup/restore path, not under /storage/emulated/0
I think it means that you copy your files from /storage/emulated/0 to /storage/emulated/legacy, then rescan backup directory and set to /storage/emulated/legacy.
Sent from my GT-N7105 using Tapatalk 4 Beta
zard said:
This is Chainfire's information: You can fix this by going into preferences and selecting a folder under /storage/emulated/legacy as backup/restore path, not under /storage/emulated/0
I think it means that you copy your files from /storage/emulated/0 to /storage/emulated/legacy, then rescan backup directory and set to /storage/emulated/legacy.
Sent from my GT-N7105 using Tapatalk 4 Beta
Click to expand...
Click to collapse
that is what i did just now... and it cause i lost my root for tb.. now trying clear data, forget root and rerun the application
Gabrieltan said:
i just full wipe my tilapia.. lolx.. anyway, i have backup all of my apps in zip file.. hahaha
one thing can confirm is no need flash bootloader.. i didnt flash it still ok.. but radio i not sure yet..because dont have simcard right now..lolx
Click to expand...
Click to collapse
Yeah, i forgot to say that i full wiped first, of course (not sure if it's mandatory, though). Bootloader and radio may not be so important, as after i flashed them 4.2.2 booted successfully (before installing 4.3) which might be a sign that not much of a difference was made.
Gabrieltan said:
yup.. without flash bootloader.. now trying for titanium.. where can change the storage thing?
Click to expand...
Click to collapse
Just go on to Menu->Preferences... . There is an option about the location of the backups (the first option under Backup Settings). If you press on it you get on /storage/emulated/0/TitaniumBackup but you change that to /storage/emulated/legacy/TitaniumBackup. Practically, it's the same folder (nothing needs to be copied or anything) but it's just on a different mount point and for some reason (i am guessing permissions) it does work. If it asks you to copy any other backups just don't do it, everything is already there.
stadicon said:
Just go on to Menu->Preferences... . There is an option about the location of the backups (the first option under Backup Settings). If you press on it you get on /storage/emulated/0/TitaniumBackup but you change that to /storage/emulated/legacy/TitaniumBackup. Practically, it's the same folder (nothing needs to be copied or anything) but it's just on a different mount point and for some reason (i am guessing permissions) it does work. If it asks you to copy any other backups just don't do it, everything is already there.
Click to expand...
Click to collapse
LOLx... i did that and now my backup all lose.. urs still at there?? one more thing, you able use tb to delete apps??
There should be no way to lose your backups unless you have chosen purposely to do so. Check that your Titanium Backups folder is still there in SDCARD.
If I weren't on vacation using only Chromebook I'd have upped this this morning with root; I managed via ARM Chromebook dev mode with adb and fastboot to backup data from my N4 and N7 3G and then install stock, flash recovery and make root, followed by restoring my titanium data. Both devices were as they were in 4.2.2 but in 4.3 within the hour.
Furthermore I had the ability to flash Franco r170 on the N4
Gabrieltan said:
LOLx... i did that and now my backup all lose.. urs still at there?? one more thing, you able use tb to delete apps??
Click to expand...
Click to collapse
Just use a file manager to make sure everything is fine. Technically, /storage/emulated/0/TitaniumBackup and /storage/emulated/legacy/TitaniumBackup is the same folder, i don't know why TB does't list your backups.
BTW, i think the battery drain issue is now fixed.
stadicon said:
Just use a file manager to make sure everything is fine. Technically, /storage/emulated/0/TitaniumBackup and /storage/emulated/legacy/TitaniumBackup is the same folder, i don't know why TB does't list your backups.
Click to expand...
Click to collapse
i also dont know why.. but i can backup... ya, only can use root explorer to delete, i tried few apps, all cant delete..
gapps hosted here works: http://forum.xda-developers.com/showthread.php?t=2248654
I got the notification to install and I tried. Shield restarted and the little green android guy showed up and it started installing the update. Half way through it showed a red explanation mark with the words "error". I had to hold down the shield+home keys to restart. The shield restarted just fine. I deleted the data in google frameworks (read to do that here) and tried the update again, same outcome.
I'm new to android (came from iphone) and now have a galaxy S4. So I apologize about the noobiness.
My shield is rooted and bootloader unlocked. As far as I know I did not install any custom recovery. I thought that users should be able to install OTA if they are running the stock OS and no custom recoveries. Am I wrong about that? Anyways, I have SuperSU installed along with a few rooted apps. My guess is that I will need to install a custom recovery so I can flash this update, is this correct? I would be very grateful if someone would explain whats going on here =P
You should not need a custom recovery for this.
Due to the download size of this update it appears to be an incremental update.
the download size i see is 22.3 MB
You would need to see the exact error to try an figure out more.
UPDATE
Installed fine for me
Custom recovery is definitely not needed. Root by itself also does not interfere. I updated without trouble.
Maybe try reflashing the boot and system partitions to stock and try the update again?
Gnurou said:
Custom recovery is definitely not needed. Root by itself also does not interfere. I updated without trouble.
Maybe try reflashing the boot and system partitions to stock and try the update again?
Click to expand...
Click to collapse
a quick how to on reflashing the boot and system would be awesome!!
--edit:nevermind... im trying out Kwonggers program--
ok somehow i softbricked my shield. I've tried Kwonggers program and I've manually flashed recovery,boot, and system and afterwards all I get is the flashing green controller during boot. I know I did it right because all messages were positive.
I also downloaded the most up to date shield files from nvidia (update64) which is extract-nv-recovery-image-shield-01.00.13216_261.5912.sh however I dont know how to use a *sh file.
Rhokk said:
a quick how to on reflashing the boot and system would be awesome!!
--edit:nevermind... im trying out Kwonggers program--
ok somehow i softbricked my shield. I've tried Kwonggers program and I've manually flashed recovery,boot, and system and afterwards all I get is the flashing green controller during boot. I know I did it right because all messages were positive.
I also downloaded the most up to date shield files from nvidia (update64) which is extract-nv-recovery-image-shield-01.00.13216_261.5912.sh however I dont know how to use a *sh file.
Click to expand...
Click to collapse
it needs a factory rest.
my suggestion is to re-flash system (again) using the command fastboot -w flash system system.img
the .sh file is for use on Linux, cygwin can probably do that if you have the correct things installed with it.
chevyowner said:
it needs a factory rest.
my suggestion is to re-flash system (again) using the command fastboot -w flash system system.img
the .sh file is for use on Linux, cygwin can probably do that if you have the correct things installed with it.
Click to expand...
Click to collapse
Chevyowner you are the best! After reading your suggestion, I tried just the system.img this time and presto! This time it took. Not sure why it didn't take the 2 times I tried it last night.
Thanks for helping newer guys like me. Really appreciate it!
Rhokk said:
Chevyowner you are the best! After reading your suggestion, I tried just the system.img this time and presto! This time it took. Not sure why it didn't take the 2 times I tried it last night.
Thanks for helping newer guys like me. Really appreciate it!
Click to expand...
Click to collapse
glad you got it working
chevyowner said:
glad you got it working
Click to expand...
Click to collapse
hi.
i am a new guy from far far away China, language is the biggist problem.
the same issue, i can't fix it, error in updating ota 65.
re-flash system (again) using the command fastboot -w flash system system.img
Click to expand...
Click to collapse
how to do? where i can get /system.img/? and how to push the img to my Shield?
except a PC and a cable, i don't have any tools, no software. and i can't get that what you guys talking about. but the same issue.
if you guys can help, i will be very appreciated
if u do know Chinese.....=P
Hi, I have the same issue, OTA 64 installed with bootloader unlocked and rooted. Will my data be preserved if I flash only the system image?
Nikojiro said:
Hi, I have the same issue, OTA 64 installed with bootloader unlocked and rooted. Will my data be preserved if I flash only the system image?
Click to expand...
Click to collapse
how can you get the /system image/? thanks
starfriend.y said:
how can you get the /system image/? thanks
Click to expand...
Click to collapse
Here's how I fixed my system:
Downloaded OTA 65 image from https://developer.nvidia.com/develop4shield
As per instructions (see https://developer.nvidia.com/sites/default/files/akamai/mobile/shield/HowTo-Flash-Recovery-Image_1.txt), flashed only boot, recovery and system images (so it wouldn't wipe your user partition, e.g. apps and data)
Rebooted the unit, waited for the upgrade to complete. Root will be lost if you had it.
Rerooted the unit (see https://github.com/linux-shield/shield-root)
It works perfectly now.
Nikojiro said:
Here's how I fixed my system:
Downloaded OTA 65 image from https://developer.nvidia.com/develop4shield
As per instructions (see https://developer.nvidia.com/sites/default/files/akamai/mobile/shield/HowTo-Flash-Recovery-Image_1.txt), flashed only boot, recovery and system images (so it wouldn't wipe your user partition, e.g. apps and data)
Rebooted the unit, waited for the upgrade to complete. Root will be lost if you had it.
Rerooted the unit (see https://github.com/linux-shield/shield-root)
It works perfectly now.
Click to expand...
Click to collapse
thanks for your help.
is that /ota 65 image/ a 1.0GB .sh file? i can't unzip it.
i think that i have to unzip the .sh file with a linux pc.
starfriend.y said:
thanks for your help.
is that /ota 65 image/ a 1.0GB .sh file? i can't unzip it.
i think that i have to unzip the .sh file with a linux pc.
Click to expand...
Click to collapse
Yes the .sh file is a linux shell script. I can repack it in a standard zip and upload it later today on a share if you want.
Sent from my GT-I9100 using Tapatalk
Ok I uploaded a repacked zip of the OTA 65 images for linux-less people
https://mega.co.nz/#!ccRCQTAS!FylQx29ZE7RUvi-kzbwb53woZGRZUu9_RAQNk9_FkMI
Please note that you'll need to have the Android SDK installed, as well as the proper USB driver.
Nikojiro said:
Ok I uploaded a repacked zip of the OTA 65 images for linux-less people
https://mega.co.nz/#!ccRCQTAS!FylQx29ZE7RUvi-kzbwb53woZGRZUu9_RAQNk9_FkMI
Please note that you'll need to have the Android SDK installed, as well as the proper USB driver.
Click to expand...
Click to collapse
thanks a lot! you are so kind!
Nikojiro said:
Ok I uploaded a repacked zip of the OTA 65 images for linux-less people
https://mega.co.nz/#!ccRCQTAS!FylQx29ZE7RUvi-kzbwb53woZGRZUu9_RAQNk9_FkMI
Please note that you'll need to have the Android SDK installed, as well as the proper USB driver.
Click to expand...
Click to collapse
here i come again...
as your guide, i've flash my Shield /recovery.img/ and /boot.img/, they all done. but failed when i flash /system.img/, "FAILED (remote: insufficient memory)"
why?
starfriend.y said:
here i come again...
as your guide, i've flash my Shield /recovery.img/ and /boot.img/, they all done. but failed when i flash /system.img/, "FAILED (remote: insufficient memory)"
why?
Click to expand...
Click to collapse
Hi, sorry with so little background information I'm afraid I can't help. I'd recommend a full reflash of your unit.
Sent from my GT-I9100 using Tapatalk
Nikojiro said:
Hi, sorry with so little background information I'm afraid I can't help. I'd recommend a full reflash of your unit.
Sent from my GT-I9100 using Tapatalk
Click to expand...
Click to collapse
thank you first.
I do as you said, download the file, unzip it, and i got /system.img/, /boot.img/ and /recovery.img/.
i opened cmd and type /fastboot flash system system.img/ and i got failed information: /FAILED (remote: insufficient memory)/
im sure i wipe my shield first, and i flash recovery, boot very well.
can't update
hello,
I would very much appreciate some real help.
I want to be able to update to 65 WITHOUT loosing my userdata. I very much care for all my settings, software and setup.
I am bootloader unlocked from the very beginning and rooted. I was able to update OTA just fine until this update, and the root back very easily each time afterwards.
I knew that this ($#@@ing) delta update will give me trouble so I made some research first. With no use... I still couldn't update..
What I did:
-> downloaded custom CMW for shield and booted. made a nandroid (again: I very much care for my data and I won't update until and can do it without wiping) - all fine
-> downloaded the extracted image of OTA 65 from this thread, booted into boot loader and did:
fastboot flash recovery recovery.img
- OK
fastboot flash boot boot.img
- OK
fastboot flash system system.img
- insufficient memory crap.. (hoped I won't get it but... (( )
-> booted back into JB.. booted fine but my SD card storage partition wasn't where file managers read it anymore (it was mounted and OK on /system/storage but just lost some symlink of some sort... no big deal.. I guess it was the new bootloader at fault but since the 65 system image wasn't flashed I guessed it will work again afterwards..)
-> opened supersu, full unrooted, took a leap of fate and tried the delta update OTA... gave me the killed andoid at about 50% (
-> tried fastboot flash system system.img on another computer.. insufficient memory crap again....
-> so I booted again into CMW and restored my nandroid. Luckily everything worked fine...
So if someone knows how can I go 65 without userdata wipe, please help me!
thank you very much
Same problem here
Surprise, surprise! .... =(
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
//cc @Nikojiro
Basically just as the title says, I can't reboot into TWRP. It shows TWRP, then boots regularly.
Is this a 5.0.1 compatibility issue with TWRP or what?
I can't get root without TWRP and I can't get into TWRP.
Thanks for help.
scottocs said:
Basically just as the title says, I can't reboot into TWRP. It shows TWRP, then boots regularly.
Is this a 5.0.1 compatibility issue with TWRP or what?
I can't get root without TWRP and I can't get into TWRP.
Thanks for help.
Click to expand...
Click to collapse
TWRP 2.8.1.0 boots fine, 2.8.2.0 causes issues atm so flash 2.8.1.0.
gee2012 said:
TWRP 2.8.1.0 boots fine, 2.8.2.0 causes issues atm so flash 2.8.1.0.
Click to expand...
Click to collapse
Ahhhh, great! Thanks
scottocs said:
Ahhhh, great! Thanks
Click to expand...
Click to collapse
You`re welcome
Just as a follow up:
I am on 5.0 and in Android my new TWRP Backups (2.8.1.0) are not shown as a file but rather as a (useless) 0 byte file. Help?
EDIT: Seems like TWRP puts my backups into some other location on my storage so that Lollipop does not see them.
Alright. 2.8.2.0 is broken and 2.8.1.0 puts my backup where I can't reach them conveniently... What now?
Go to the twrp thread and search restorecon. It's a well covered issue
slater_g said:
Just as a follow up:
I am on 5.0 and in Android my new TWRP Backups (2.8.1.0) are not shown as a file but rather as a (useless) 0 byte file. Help?
EDIT: Seems like TWRP puts my backups into some other location on my storage so that Lollipop does not see them.
Alright. 2.8.2.0 is broken and 2.8.1.0 puts my backup where I can't reach them conveniently... What now?
Click to expand...
Click to collapse
I noticed same thing yesterday, and I could not found any solution, so I flashed 5.0.1 again and i´m now comlpetely stock and shearching solution
Wakamatsu said:
Go to the twrp thread and search restorecon. It's a well covered issue
Click to expand...
Click to collapse
Never heard of it, but I shearch now. When I use TWRP filemanager under recovery then this file is correct location (data/media/0/TWRP... ) But under my mixplorer I saw only some TWRP file 0 byt. And after some reboots I even did not saw any filer /root folder. ( it looks like same problem as 5.0 and then permissev boot.img fixed this )
Wakamatsu said:
Go to the twrp thread and search restorecon. It's a well covered issue
Click to expand...
Click to collapse
Thanks. Looked it up but figured that TWRP itself is capable of mounting the device as MTP on my computer and listing the folders correctly. So accessed my backup from there.
slater_g said:
Thanks. Looked it up but figured that TWRP itself is capable of mounting the device as MTP on my computer and listing the folders correctly. So accessed my backup from there.
Click to expand...
Click to collapse
so ..solution was.....?
Mairo said:
so ..solution was.....?
Click to expand...
Click to collapse
Terminal
su
restorecon -FR /data/media/0/*
Aerowinder said:
Terminal
su
restorecon -FR /data/media/0/*
Click to expand...
Click to collapse
thanks this almost helped me.
now when I open Mixplorer then I see SD card/TWRP folder, but still not Backup folder.
But when I go trough /root/data/media/0/TWRP/ then I can see Backups/05c847******/my backup.
can I run some other command in terminal to activate SD card/TWRP location also? ( this location should be /root/storage/emulated/0/TWRP....or.... /root/storage/emulated/legasy/TWRP).
This didnt helped me, I just give up and wait. I dont like if something don't work properly.
Mairo said:
thanks this almost helped me.
now when I open Mixplorer then I see SD card/TWRP folder, but still not Backup folder.
But when I go trough /root/data/media/0/TWRP/ then I can see Backups/05c847******/my backup.
can I run some other command in terminal to activate SD card/TWRP location also? ( this location should be /root/storage/emulated/0/TWRP....or.... /root/storage/emulated/legasy/TWRP).
This didnt helped me, I just give up and wait. I dont like if something don't work properly.
Click to expand...
Click to collapse
It should fix it.
rootSU said:
It should fix it.
Click to expand...
Click to collapse
To I leave this "*", end of this :::restorecon -FR /data/media/0/* :::: or do I add TWRP instead? If so, then I know what I did wrong
You leave the star
ok.. then I did everything correctly. after that I manage to see TWRP folder and inside this same 0 bit BACKUP folder.
Mairo said:
ok.. then I did everything correctly. after that I manage to see TWRP folder and inside this same 0 bit BACKUP folder.
Click to expand...
Click to collapse
Not sure what you're saying. Screenshot?
rootSU said:
Not sure what you're saying. Screenshot?
Click to expand...
Click to collapse
I try tomorrow again, I made a clean install and I have stock right now. ( I flashtomorrow twrp 2.8.1.0 ( 2.8.2.0 seems to be buggy right now), then supersu2.40 and then try " su (enter) restorecon -FR /data/media/0/*" again and let You know.
rootSU said:
Not sure what you're saying. Screenshot?
Click to expand...
Click to collapse
Hi. So I flashed TWRP 2.8.1.0, then flashed superSU 2.40. Then run in Terminal this su restorecon -FR /data/media/0/* command. Then I rebooted in recovery (twrp) and made a nandroid backup.
Then I rebooted and opened my file manager MiXplorer. Under SD I see TWRP foledr but inside this there is unknown BACKUP file (location: /storage/emulated/0/TWRP/BACKUP )
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
But when I go /data/media/0/TWRP/Backup then I see this file
problem is that Windows sees /storage/emulated/0/TWRP location and I can´t get access to this backup file.
You need to delete the unknown backups file then run the command. If that still gives you issues, do a titanium backup, nandroid backup, move the nandroid backup anywhere on your sdcard using a root explorer, copy the data back to your computer and factory reset including wiping sdcard / storage... Maybe even flash factory userdata.img using fastboot.
Then boot into your wiped device, go through initial setup and copy your sdcard contents back and put your nandroid in the correct place. Restore it.
rootSU said:
You need to delete the unknown backups file then run the command. If that still gives you issues, do a titanium backup, nandroid backup, move the nandroid backup anywhere on your sdcard using a root explorer, copy the data back to your computer and factory reset including wiping sdcard / storage... Maybe even flash factory userdata.img using fastboot.
Then boot into your wiped device, go through initial setup and copy your sdcard contents back and put your nandroid in the correct place. Restore it.
Click to expand...
Click to collapse
I ran this command before I made a nandroid backup. And I tried delete this unkonown backup file and now I can't see under /root any files ( No Items ).
I had wiped sd card, userdata. I made flashall.bat with factory image.
I had almost same problem with 5.0 and then this LRX21O-permissive-boot file helped me? are this bootimage same as 5.0.1?
EDIT: Soo strage..
I flashed francos r69 kernel and then I went in to recovery and I restored everything from this backup what I made to testing this problem. And now looks like everything is working. I see now TWRP folder and inside backup file and I also see now files under /root. ( now after restore with stock boot/kernel and no problems ).
looks like somehow flashing francos kernel fixed my problem.
EDIT2: after restoring sms with titanium I can't see again any files under /root folder. But everything is ok with this TWRP folder under sdcard/twrp.
I am not responsible if you brick your device.
UPDATE BETA PIE ROM
Direct link Download- https://drive.google.com/uc?id=1_r6zxR34q5aN72SPhAjMLkV4GxQcD4ff&export=download
Flash procedure for pie- https://www.asuswebstorage.com/navigate/a/#/s/A9A029F390A34806BED2A412E194C44D4
For BL unlocked phones
Recommended PBRP
PBRP has function to fix the encryption after flashing the ROM. You may choose to flash decrypt.zip for your own satisfaction.
PBRP worked like a charm for me.
* Use 7zip/WinRAR- Extract / Open Archive by right clicking the firmware zip and go to > META-INF > com > google > android
*open updater-script with a note editor
* Remove all the lines above the code
ui_print("Target: Android/sdm660_64/sdm660_64:X.X.X/XXXX/XX.20XX.XXXX.XXX-20XXXXXX:user/release-keys");
*Save it/rezip the firmware and copy it to sdcard
*Wipe System, data, cache / format DATA.
*Flash the ROM
Stock FULL ROM OREO 8.1
Stock Recovery & TWRP Flash-able
You have to flash full ROM if magisk is installed. Take backup & be very careful if device get encrypted after installing the ROM. (Flash decryption file- https://forum.xda-developers.com/asus-zenfone-max-pro-m1/how-to/mod-decrypt-data-t3787311 )
* Use 7zip/WinRAR- Extract / Open Archive by right clicking the firmware zip and go to > META-INF > com > google > android
*open updater-script with a note editor
* Remove all the lines above the code
ui_print("Target: Android/sdm660_64/sdm660_64:X.X.X/XXXX/XX.20XX.XXXX.XXX-20XXXXXX:user/release-keys");
*Save it/rezip the firmware and copy it to sdcard
*Wipe System, data, cache / format DATA.
*Flash the ROM
Official ROM link- https://www.asus.com/Phone/ZenFone-Max-Pro-M2/HelpDesk_BIOS/
One click Download - https://dlcdnets.asus.com/pub/ASUS/...995.844210030.1548823414-323285766.1546595187
so after installing latest 186 ROM continue installing decrypt.zip right?
rycroot96 said:
so after installing latest 186 ROM continue installing decrypt.zip right?
Click to expand...
Click to collapse
when i had installed December update (unlocked bootloader & magisk installed) i flashed the new rom, installed decrypt.zip yet the phone got encrypted on boot. Later i formatted data and flashed decrypt.zip and the phone booted normally.
Its kind of two way procedure. Try it. There is nothing wrong in experiment unless you haven't taken backup.
I'll flash as soon as i go home & let you know the status.
Ajeyvm said:
when i had installed December update (unlocked bootloader & magisk installed) i flashed the new rom, installed decrypt.zip yet the phone got encrypted on boot. Later i formatted data and flashed decrypt.zip and the phone booted normally.
Its kind of two way procedure. Try it. There is nothing wrong in experiment unless you haven't taken backup.
I'll flash as soon as i go home & let you know the status.
Click to expand...
Click to collapse
but when encrypted twrp doesn't disappear right? ok I am waiting I haven't updated since ubl + magisk. what is meant by twrp backup right? I have a system backup and booted. thanks a lot for the info bro
rycroot96 said:
but when encrypted twrp doesn't disappear right? ok I am waiting I haven't updated since ubl + magisk. what is meant by twrp backup right? I have a system backup and booted. thanks a lot for the info bro
Click to expand...
Click to collapse
backup means your personal data, apps, contacts, internal storage.
TWRP wont be gone after flashing. The phone works fine even after its encrypted. You need to flash decrypt.zip to get internal storage access in TWRP . And for overall smoothness of the device.
Ajeyvm said:
backup means your personal data, apps, contacts, internal storage.
TWRP wont be gone after flashing. The phone works fine even after its encrypted. You need to flash decrypt.zip to get internal storage access in TWRP . And for overall smoothness of the device.
Click to expand...
Click to collapse
thank you very much for the info
Guys ... Use PBRP Recovery.. It is based on TWRP...
It automatically patches forced encryption, after flashing the firmware file...
But just to make sure flash decrypt.zip too ...
So I did really dumb error... I flashed OTA(edited updater-script), then flashed decrypt.zip and flashed Magisk-v18.0.zip(this is what I shouldn't do)... and now my phone is encrypted
and my nandroid backup that I just make is on internal storage... so now it's already encrypted(or it isn't?) and no longer be able to use...
Is there any way I can decrypt back my phone?
my custom recovery/twrp encrypted as well
I got my nandroid backup few days ago on my computer
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
watatara.102 said:
So I did really dumb error... I flashed OTA(edited updater-script), then flashed decrypt.zip and flashed Magisk-v18.0.zip(this is what I shouldn't do)... and now my phone is encrypted
and my nandroid backup that I just make is on internal storage... so now it's already encrypted(or it isn't?) and no longer be able to use...
Is there any way I can decrypt back my phone?
my custom recovery/twrp encrypted as well
I got my nandroid backup few days ago on my computer
Click to expand...
Click to collapse
I don't think there is a way to decrypt your phone without losing data...
Best way is restore from your nandroid backup...
watatara.102 said:
So I did really dumb error... I flashed OTA(edited updater-script), then flashed decrypt.zip and flashed Magisk-v18.0.zip(this is what I shouldn't do)... and now my phone is encrypted
Click to expand...
Click to collapse
I did exactly the same... But using PBRP recovery... Faced no issue at all...
Tyakrish said:
I don't think there is a way to decrypt your phone without losing data...
Best way is restore from your nandroid backup...
I did exactly the same... But using PBRP recovery... Faced no issue at all...
Click to expand...
Click to collapse
uh, the one that is encrypted is on /data I'm right?
my internal storage/internal SD which is on /data/media is not encrypted right? then I still can copy my NANDroid backup?
error displayed 7 in twrp.
When edit the script and rezip firmware then go to twrp then error 7 displayed that the zip file is crupted.so get me solution
shivrajmalani said:
When edit the script and rezip firmware then go to twrp then error 7 displayed that the zip file is crupted.so get me solution
Click to expand...
Click to collapse
Do not unzip the file.
Right click on the file, open archive. Edit the updater script. Save it. Better to use 7Zip.
watatara.102 said:
uh, the one that is encrypted is on /data I'm right?
my internal storage/internal SD which is on /data/media is not encrypted right? then I still can copy my NANDroid backup?
Click to expand...
Click to collapse
I am not sure exactly, which partitions are encrypted. But yes I think internal storage on /data/media is not encrypted...
But if you open TWRP then you will get a message to decrypt your device... DONT do this ! It will wipe your internal storage too, even if it is not encrypted...
If you want to copy your nandroid backup, then boot up your ROM and then transfer files using MTP to your computer..
---------- Post added at 09:08 AM ---------- Previous post was at 08:51 AM ----------
shivrajmalani said:
When edit the script and rezip firmware then go to twrp then error 7 displayed that the zip file is crupted.so get me solution
Click to expand...
Click to collapse
Did you use WinRAR ? Do one thing...
After extracting zip, and editing the script, go to the root of your firmware folder, select all files then add to archive. Select archive format as zip and keep the lowest compression possible...
While flashing, disable zip verification. This should work... Otherwise try the method by @Ajeyvm
I got this weird bug and it's will keep creating new log everytime reboot
here log file https://pastebin.com/wXHvcbDT
watatara.102 said:
I got this weird bug and it's will keep creating new log everytime reboot
here log file https://pastebin.com/wXHvcbDT
Click to expand...
Click to collapse
i think im the only one getting for this bug......lets rollback old version haha...i see asus official website....that they have rollback the latest version
Zahirpro2 said:
i think im the only one getting for this bug......lets rollback old version haha...i see asus official website....that they have rollback the latest version
Click to expand...
Click to collapse
Whenever i restart my phone i get that bug report. I clear it & use the device as usual. Evrything else is working fine. No need to revert back unless u r facing some major issue.
Zahirpro2 said:
i think im the only one getting for this bug......lets rollback old version haha...i see asus official website....that they have rollback the latest version
Click to expand...
Click to collapse
Oh so its not just me then, good to know
It looks good.
Edit, someone posted a review - https://youtu.be/_wli8M-71yI
Someone should really post a mirror of the official link
Official link is down does anyone has any other mirror link?