Related
Currently on VZN, XT1060, MotoX, DEV unlocked bootloader, TWRP, SuperSU:
version: 4.4
kernel: [email protected]#1
system: 140.45.5.ghost_verizon.Verizon.en.US
build: 13.11.1Q2.X-69-3
NO ROM And I only changed two items:
1. VzwEntitlementService.apk via [http://forum.xda-developers.com/showthread.php?t=2536166] by changing the originalVzwEntitlementService.apk to VzwEntitlementService.apk.bak
2. Remove bootloader warning image
Question: for the 4.4.2 update (hopefully coming soon)
1. Can I just get the 4.4.2 update via OTA with my current setup
2. Or do I have a to flash back to stock
Thank you much.
and I'm new to xda.
you need to flash the stock recovery and then run the OTA. after it installs flash your custom recovery back.
dray_jr said:
you need to flash the stock recovery and then run the OTA. after it installs flash your custom recovery back.
Click to expand...
Click to collapse
Thanks, if someone has an unlocked bootloader but is not rooted and they removed the bootloader unlocked message using the command:
fastboot flash logo logo.bin
and used a logo.bin file that has the original kitkat 4.4 logo in it, can they take the OTA without doing anything else?
Also, when you flash the stock recovery, you become unrooted and so then if you flash your custom recovery after the OTA, you reroot, right?
Are you supposed to wipe the davlik/cache or anything else like that before you take the OTA?
Cozume said:
Thanks, if someone has an unlocked bootloader but is not rooted and they removed the bootloader unlocked message using the command:
fastboot flash logo logo.bin
and used a logo.bin file that has the original kitkat 4.4 logo in it, can they take the OTA without doing anything else?
Also, when you flash the stock recovery, you become unrooted and so then if you flash your custom recovery after the OTA, you reroot, right?
Are you supposed to wipe the davlik/cache or anything else like that before you take the OTA?
Click to expand...
Click to collapse
as for the logo i am not sure i think you should be ok .
as for when you flash the stock recovery yes you loose root but when you reflash the custom recovery if you still dont have root just reinstall SuperSU and you will be good to go,
and anytime i flash something i always wipe the cache/davlik
dray_jr said:
and anytime i flash something i always wipe the cache/davlik
Click to expand...
Click to collapse
really so when I flashed my custom recovery to root for the first time, I should have wiped that?
Cozume said:
really so when I flashed my custom recovery to root for the first time, I should have wiped that?
Click to expand...
Click to collapse
you dont have too but it is recommended
dray_jr said:
as for when you flash the stock recovery yes you loose root but when you reflash the custom recovery if you still dont have root just reinstall SuperSU and you will be good to go
Click to expand...
Click to collapse
Hmm, I have a VZW DE, unlocked bootloader, flashed TWRP then SuperSU to get root, then flashed the stock recovery and still have root. I honestly can't remember if I re-rooted after flashing back to stock recovery, but I don't think that I did. Are you saying that flashing to stock recovery should have unrooted the phone? What does it mean if it didn't? I hope I'm remembering correctly.
I'd like to be able to get the OTA 4.4.2 update from VZW when available but I keep reading it's not possible with root. How do I remove root if reflashing the stock recovery didn't do it? I'm coming from a GNex which was much simpler so I want to make sure I'm prepared for the OTA when it arrives. Thanks!
Melarsa said:
Hmm, I have a VZW DE, unlocked bootloader, flashed TWRP then SuperSU to get root, then flashed the stock recovery and still have root. I honestly can't remember if I re-rooted after flashing back to stock recovery, but I don't think that I did. Are you saying that flashing to stock recovery should have unrooted the phone? What does it mean if it didn't? I hope I'm remembering correctly.
I'd like to be able to get the OTA 4.4.2 update from VZW when available but I keep reading it's not possible with root. How do I remove root if reflashing the stock recovery didn't do it? I'm coming from a GNex which was much simpler so I want to make sure I'm prepared for the OTA when it arrives. Thanks!
Click to expand...
Click to collapse
OK,listen and listen closely, by far the best way to accept the ota is flash stock recovery and also flash your system.img, I don't care what other folks say, I've been here for 3 ota's , this will prevent any chances of having issues when accepting the ota. You may also flash Verizon's sbf firmware when available, the later is what I prefer
Sent on my Gummy running Lenoto X
flashallthetime said:
OK,listen and listen closely, by far the best way to accept the ota is flash stock recovery and also flash your system.img, I don't care what other folks say, I've been here for 3 ota's , this will prevent any chances of having issues when accepting the ota. You may also flash Verizon's sbf firmware when available, the later is what I prefer
Sent on my Gummy running Lenoto X
Click to expand...
Click to collapse
Got it, that's what I'll do when the time comes. Thanks!
flashallthetime said:
OK,listen and listen closely, by far the best way to accept the ota is flash stock recovery and also flash your system.img, I don't care what other folks say, I've been here for 3 ota's , this will prevent any chances of having issues when accepting the ota. You may also flash Verizon's sbf firmware when available, the later is what I prefer
Sent on my Gummy running Lenoto X
Click to expand...
Click to collapse
Could I do a TWRP backup of /data and just flash the entire system back to new, take the OTA and TWRP restore /data?
Or does /data contain some stuff that is linked to the version of Android I did the backup with?
fbiryujin said:
Could I do a TWRP backup of /data and just flash the entire system back to new, take the OTA and TWRP restore /data?
Or does /data contain some stuff that is linked to the version of Android I did the backup with?
Click to expand...
Click to collapse
Why would you need to do that? /data isn't going anywhere in the process of flashing system and recovery and then taking an OTA
piccit said:
Why would you need to do that? /data isn't going anywhere in the process of flashing system and recovery and then taking an OTA
Click to expand...
Click to collapse
I thought it might be different because I'm rooted, and encrypted.
fbiryujin said:
Could I do a TWRP backup of /data and just flash the entire system back to new, take the OTA and TWRP restore /data?
Or does /data contain some stuff that is linked to the version of Android I did the backup with?
Click to expand...
Click to collapse
You can try to restore your data after you upgrade, there is no guarantee you won't have any issues but it won't be a huge problem, you'll just have to factory reset. It no different when you flash a custom ROM , if the developer uses a new base then often they request you to do a clean fresh install, otherwise you'll have issues
Sent on my Gummy running Lenoto X
flashallthetime said:
You can try to restore your data after you upgrade, there is no guarantee you won't have any issues but it won't be a huge problem, you'll just have to factory reset. It no different when you flash a custom ROM , if the developer uses a new base then often they request you to do a clean fresh install, otherwise you'll have issues
Sent on my Gummy running Lenoto X
Click to expand...
Click to collapse
I'm not using a custom ROM though.
fbiryujin said:
I'm not using a custom ROM though.
Click to expand...
Click to collapse
I understand that, try it and see what happens, you might be OK restoring your data , no harm in trying
Sent on my Gummy running Lenoto X
flashallthetime said:
I understand that, try it and see what happens, you might be OK restoring your data , no harm in trying
Sent on my Gummy running Lenoto X
Click to expand...
Click to collapse
So far no official update available to me even after flashing the stock image from Moto. My biggest goal here is to find a way to backup and restore nandroids from the encrypted phone.
Flash and relock Moto X manually
No lie my a$$hole did pucker up though the whole process but... success woohoo!
I followed the instruction on Motorola website [https://motorola-global-portal.custhelp.com/app/standalone/bootloader/recovery-images] one thing I did not have is 'Motorola fastboot utility to flash (included in the Darwin/, Linux/ or Windows/ directory)' had to do some searching; came across [http://forum.xda-developers.com/showthread.php?t=1138092] Thanks for that.
DETAILS (So this is what I was working with):
VZN, XT1060, MotoX, DEV unlocked bootloader, TWRP, SuperSU:
version: 4.4 | system: 140.45.5.ghost_verizon.Verizon.en.US | build: 13.11.1Q2.X-69-3
Did this on my Mac, NOT on PC
Steps:
1. got recovery image
2. got Motorola fastboot utility from | http://forum.xda-developers.com/showthread.php?t=1138092 moto-fastboot-osx.zip
3. used the fastboot from Darwin folder
4. follow steps from motorola website, but did not oem lock [$ fastboot oem lock]
5. last step reboot [$ fastboot reboot] a$$hole pucker up
But success, everything booted up properly even had the warning bootloader unlocked image
There was one point when it got to the Verizon boot image; it took abit longer a$$hole pucker up but finished booting.
Then phone went through the setup process (like new).... It's Miller time!
Come on 4.4.2 update via OTA
_slam said:
No lie my a$$hole did pucker up though the whole process but... success woohoo!
I followed the instruction on Motorola website [https://motorola-global-portal.custhelp.com/app/standalone/bootloader/recovery-images] one thing I did not have is 'Motorola fastboot utility to flash (included in the Darwin/, Linux/ or Windows/ directory)' had to do some searching; came across [http://forum.xda-developers.com/showthread.php?t=1138092] Thanks for that.
DETAILS (So this is what I was working with):
VZN, XT1060, MotoX, DEV unlocked bootloader, TWRP, SuperSU:
version: 4.4 | system: 140.45.5.ghost_verizon.Verizon.en.US | build: 13.11.1Q2.X-69-3
Did this on my Mac, NOT on PC
Steps:
1. got recovery image
2. got Motorola fastboot utility from | http://forum.xda-developers.com/showthread.php?t=1138092 moto-fastboot-osx.zip
3. used the fastboot from Darwin folder
4. follow steps from motorola website, but did not oem lock [$ fastboot oem lock]
5. last step reboot [$ fastboot reboot] a$$hole pucker up
But success, everything booted up properly even had the warning bootloader unlocked image
There was one point when it got to the Verizon boot image; it took abit longer a$$hole pucker up but finished booting.
Then phone went through the setup process (like new).... It's Miller time!
Come on 4.4.2 update via OTA
Click to expand...
Click to collapse
I just want to make sure that when you did this all it did was remove root and replace the bootloader, not any data or settings you had on your phone. That is the only thing that worries me before I decide to do the 4.4.2 update.
_slam said:
Currently on VZN, XT1060, MotoX, DEV unlocked bootloader, TWRP, SuperSU:
version: 4.4
kernel: [email protected]#1
system: 140.45.5.ghost_verizon.Verizon.en.US
build: 13.11.1Q2.X-69-3
NO ROM And I only changed two items:
1. VzwEntitlementService.apk via [http://forum.xda-developers.com/showthread.php?t=2536166] by changing the originalVzwEntitlementService.apk to VzwEntitlementService.apk.bak
2. Remove bootloader warning image
Question: for the 4.4.2 update (hopefully coming soon)
1. Can I just get the 4.4.2 update via OTA with my current setup
2. Or do I have a to flash back to stock
Thank you much.
and I'm new to xda.
Click to expand...
Click to collapse
1) You don't need to do much. Revert the Entitlement hack you did, you need the one that came on the device, not a hacked one.
2) Flash the stock recovery back to your phone. You'll need the stock recovery to install the OTA. Just do it the same way you flashed TWRP to your phone but use the stock recovery.img file from the 4.4 .sbf ( http://sbf.droid-developers.org/download.php?device=0&file=5 )
You will NOT lose root flashing the stock recovery, you will NOT lose root taking the OTA.
After updating, use Xposed and the Moto Tether module for tethering instead of using a hacked version of the app.
shadowmonk36 said:
I just want to make sure that when you did this all it did was remove root and replace the bootloader, not any data or settings you had on your phone. That is the only thing that worries me before I decide to do the 4.4.2 update.
Click to expand...
Click to collapse
If you have the Dev edition from VZW, it's simple to install the OTA.
This is what I did as I had root and xposed installed.
1. Download 4.4.2 file from XDA and cut and paste it from download folder to root of sdcard
2. Flash stock 4.4 recovery image via fastboot.
3. Flash 4.4 system image using mfastboot (must use mfastboot)
4. Boot into recovery
5. Apply update and selected the OTA zip.
6. Reboot
7. Power down and boot back into fastboot.
8. Flash TWRP, allow it to root, reboot.
9. Reinstall Xposed framework.
All my data and settings were still there. Even my xposed modules reactivated. No additional setup and my phone was exactly the same but had 4.4.2.
Only caveat is only do this if you've never installed other OS's and have only taken official OTAs from VZW. You need to be on the right bootloader. Don't brick your phone.
Sent from my Dev Edition Moto X
First of all I just bought Global Moto G 2014 (XT1063) from US Amazon and that was KXH21.85-23 (not updatable to Lollipop via shared OTA.)
So I did manage to unlocked the bootloader and flashed KXH21.85-17 and tried to flash the "Blur_Version.21.11.17.titan_retuglb.retuglb.en.US" which supposed to flash the Lollipop.
Unfortunately at first it failed to update me because "Printspooler.apk" mismatch the hash check. After attempt to flash (yes, I ignore the abort message and redo the process, It passed.... I don't know why) and stuck at some "xxx.apk" mismatch the hash again. After redo the process and bypass (for unknown reason that redo bypass the mismatch) I stuck at "velvet.apk" mismatch and this time It won't let me bypass and keep going on update to lollipop.
In my theory, Is it possible that I flash KXH21.85-17 from other country? Yes, any XT1063 (latin american, whereever on earth) supposed to flashable, but maybe the different country has slightly different apk. So that's why I failed the hash check.
Can anyone give me a URL or mirror to USA XT1063 for KXH21.85-17 that confirmed updatable to Lollipop? Since SBF-Dev and MotoFirmware is now down I couldn't find any.
I know what I'm saying is sound ridiculous, but I have no other theory that support my conspiracy anymore.
Hi @bankkung, I was facing similar problems. First you'd want to get back to stock kitkat which is up-gradable to Lollipop, so I would suggest downloading this file, http://180upload.com/bzl3ah1wov5g, which is 21.85-17, you can flash this file with fastboot by following this guide http://forum.xda-developers.com/moto-g-2014/general/index-guide-update-to-lollipop-android-t2941340. Next you'd want to download both Lollipop files, the first and second one. (The second one is the newest update that fixes memory management). First file: https://mega.co.nz/#!UoQ02KLQ!22OUNBctGLoAUOMd_frTRT9jgbB3tRPUa4pPqfesGho.. Second file: https://mega.co.nz/#!s8ZSVJDA!SqUWPZODvM4-GYuXo6MC2JWTmpE9_jdyqlH-ycWi78I. Download both of those files and put them somewhere accessible (like your SD card) so you can flash these in stock recovery, so after you downgrade to kitkat you can flash the first one, then boot up and then go back into stock recovery and flash the second file. I'd recommend factory resetting your phone after this to smoothen everything out.
If all else fails you can flash TWRP recovery using this guide http://forum.xda-developers.com/moto-g-2014/development/recovery-twrp-2-8-0-1-moto-g-2014-t2896165, and then download this TWRP backup of the latest Lollipop, and place it in /data/media/0/TWRP/backups/(your device name here). All of that can be done right in TWRP recovery using the file manager (no need to root your phone). https://mega.co.nz/#!59AAiQaR!cPUsNpI5j-ZaIMX10uiS93EJqpLxua-iwKHj30InX1U
I would really recommend the first option tho, just in case any other updates come you can easily upgrade your phone.
Hope I helped!
Lamech242 said:
Hi @bankkungFirst you'd want to get back to stock kitkat which is up-gradable to Lollipop, so I would suggest downloading this file, http://180upload.com/bzl3ah1wov5g, which is 21.85-17, you can flash this file with fastboot by following this guide http://forum.xda-developers.com/moto-g-2014/general/index-guide-update-to-lollipop-android-t2941340. Next you'd want to download both Lollipop files, the first and second one. (The second one is the newest update that fixes memory management). First file: https://mega.co.nz/#!UoQ02KLQ!22OUNBctGLoAUOMd_frTRT9jgbB3tRPUa4pPqfesGho.. Second file: https://mega.co.nz/#!s8ZSVJDA!SqUWPZODvM4-GYuXo6MC2JWTmpE9_jdyqlH-ycWi78I. Download both of those files and put them somewhere accessible (like your SD card) so you can flash these in stock recovery, so after you downgrade to kitkat you can flash the first one, then boot up and then go back into stock recovery and flash the second file. I'd recommend factory resetting your phone after this to smoothen everything out.
Click to expand...
Click to collapse
Hi Thanks for your help
I've done that several time and still having the same problem (yes, mine is unlocked bootloader and flashed-reflashed that 21.85-17 over twenty time right now)
Lamech242 said:
If all else fails you can flash TWRP recovery using this guide http://forum.xda-developers.com/moto-g-2014/development/recovery-twrp-2-8-0-1-moto-g-2014-t2896165, and then download this TWRP backup of the latest Lollipop, and place it in /data/media/0/TWRP/backups/(your device name here). All of that can be done right in TWRP recovery using the file manager (no need to root your phone). https://mega.co.nz/#!59AAiQaR!cPUsNpI5j-ZaIMX10uiS93EJqpLxua-iwKHj30InX1U
I would really recommend the first option tho, just in case any other updates come you can easily upgrade your phone.
Hope I helped!
Click to expand...
Click to collapse
I'm thinking about getting some Nandroid backup (never used TWRP before but I think this methond you gave is the same thing as I think) to get straight from Custom Recovery to Lollipop.
So what I need to do in the 2nd method is
a
flash TWRP
Place TWRP Backup of XT1063 Lollipop
restore
reflash Stock Recovery + Locked recovery
Is this sound corrected?
bankkung said:
Hi Thanks for your help
I've done that several time and still having the same problem (yes, mine is unlocked bootloader and flashed-reflashed that 21.85-17 over twenty time right now)
I'm thinking about getting some Nandroid backup (never used TWRP before but I think this methond you gave is the same thing as I think) to get straight from Custom Recovery to Lollipop.
So what I need to do in the 2nd method is
a
flash TWRP
Place TWRP Backup of XT1063 Lollipop
restore
reflash Stock Recovery + Locked recovery
Is this sound corrected?
Click to expand...
Click to collapse
Yes once you place the backup on your SD card, flash TWRP, reboot into recovery and go to advanced then go to file manager, then finish following the instructions above. Once you place it in the right place then you restore it. As of the stock recovery issue, it wouldn't make much sense to do that unless you followed the first option, where the stock recovery would actually be needed. But if you find a recovery image then yeah. If you do the second method you won't be able to receive updates nor update it manually unless doing the first method.. But the TWRP backup is the latest lollipop so enjoy!
If you still need help you can just flash TWRP recovery, and download this and flash it. http://forum.xda-developers.com/mot...-stock-rom-t2970427/post57438355#post57438355
I am looking for an easy way to be able to receive OTA updates after rooting with the 'systemless' root method, the steps I mention below assume that the system partition remains untouched after rooting. I have searched and not found a clear answer on this.
Would I be correct in assuming that this procedure should work to receive an OTA update and keep stock recovery after rooting?
Start with completely stock Android 6.0
fastboot boot twrp-recovery.img (boot TWRP, NOT flash, to maintain stock recovery after rooting)
Flash systemless root with TWRP
OTA arrives (Android 6.0.1 for example)
fastboot flash boot boot.img (with stock 6.0 kernel, root lost)
Accept & install OTA update
Success?
So unless I am missing something, this method would leave the system in a stock, unrooted state after the OTA is installed, and could be repeated for future updates. Anybody have any experience with this yet?
Sounds like it will work, but why mess with the ota? More work and risk honestly.
Since you're already using fastboot just flash the newest boot and system.img. Then flash/boot twrp and flash su like you'd need to do anyway. Done. You don't lose anything flashing system.
yosmokinman said:
Sounds like it will work, but why mess with the ota? More work and risk honestly.
Since you're already using fastboot just flash the newest boot and system.img. Then flash/boot twrp and flash su like you'd need to do anyway. Done. You don't lose anything flashing system.
Click to expand...
Click to collapse
That is true, kind of just wondering/gathering information. It just seemed like with the new root method, OTA would be possible and less risky than before.
Sent from my MotoG3 using Tapatalk
@quakeaz there is one step missing on your guide. After boot.img you also have to flash stock recovery.img. From Lollipop, Google is also checking installed recovery, and for successful OTA, it has to be stock as well.
Otherwise, your guide should work, I've done same thing with my Nexus 5 and 7 for like last 3 months.
Srandista said:
@quakeaz there is one step missing on your guide. After boot.img you also have to flash stock recovery.img. From Lollipop, Google is also checking installed recovery, and for successful OTA, it has to be stock as well.
Otherwise, your guide should work, I've done same thing with my Nexus 5 and 7 for like last 3 months.
Click to expand...
Click to collapse
Thanks for your reply, but I intentionally left that step out, due to step 2 in my list. By only booting TWRP, instead of flashing, I assume stock recovery will remain after rooting.
Sent from my MotoG3 using Tapatalk
quakeaz said:
Thanks for your reply, but I intentionally left that step out, due to step 2 in my list. By only booting TWRP, instead of flashing, I assume stock recovery will remain after rooting.
Sent from my MotoG3 using Tapatalk
Click to expand...
Click to collapse
Ah, sorry, I overlooked that.
Since I have flashed TWRP instead of stock recovery, I'm going by same process as you write, just reflash stock recovery. And can confirm, that the process is indeed working (no need to install system.img, as with previous system-based SuperSU).
Sounds good!
Sent from my MotoG3 using Tapatalk
quakeaz said:
I am looking for an easy way to be able to receive OTA updates after rooting with the 'systemless' root method, the steps I mention below assume that the system partition remains untouched after rooting. I have searched and not found a clear answer on this.
Would I be correct in assuming that this procedure should work to receive an OTA update and keep stock recovery after rooting?
Start with completely stock Android 6.0
fastboot boot twrp-recovery.img (boot TWRP, NOT flash, to maintain stock recovery after rooting)
Flash systemless root with TWRP
OTA arrives (Android 6.0.1 for example)
fastboot flash boot boot.img (with stock 6.0 kernel, root lost)
Accept & install OTA update
Success?
So unless I am missing something, this method would leave the system in a stock, unrooted state after the OTA is installed, and could be repeated for future updates. Anybody have any experience with this yet?
Click to expand...
Click to collapse
Instead of fastboot flashing boot.img, you can use "Settings --> Full Unroot" in SuperSU. During SuperSU systemless flash, your old boot image is backed up. Among other things, the full unroot option will restore the backup, assuming it hasn't been lost due to a factory reset and whatnot.
On many firmwares, this procedure also restores stock recovery. This requires that both the firmware supports recreating the recovery from the boot image plus a patch file (most do), and that TWRP did not remove said patch file (which some versions do).
That being said, if you're using fastboot anyway, flashing boot, recovery, system and vendor manually is always the safest thing before an OTA.
Thanks for the info. So I take it while using systemless root, installing ota without unrooting is a big nono? The January ota just downloaded and is asking me to install, should I do it manually?
Chainfire said:
Instead of fastboot flashing boot.img, you can use "Settings --> Full Unroot" in SuperSU. During SuperSU systemless flash, your old boot image is backed up. Among other things, the full unroot option will restore the backup, assuming it hasn't been lost due to a factory reset and whatnot.
On many firmwares, this procedure also restores stock recovery. This requires that both the firmware supports recreating the recovery from the boot image plus a patch file (most do), and that TWRP did not remove said patch file (which some versions do).
That being said, if you're using fastboot anyway, flashing boot, recovery, system and vendor manually is always the safest thing before an OTA.
Click to expand...
Click to collapse
Thank you for this thread and the procedure. I tried myself to avoid as much as possible to use a computer for super easy OTA update. But there is always one obligatory step: to root the phone.
Phone systemless rooted (2.66) - TWRP installed - OTA arrives.
In SuperSu app : Fully unroot
Install OTA - success
Fastboot boot (or install) TWRP
Flash superSu 2.66.zip
And that's it!
My question is the following: Does it exist a possibility to load on step 3. something that could flash superSu.zip from within the phone, no computer required?
Maybe FlashFire? I guess not, for it needs root and the point is to flash a rooting zip... You see the loop there...
Would it be theoreticaly possible at all?
Judim said:
Maybe FlashFire? I guess not, for it needs root and the point is to flash a rooting zip... You see the loop there...
Would it be theoreticaly possible at all?
Click to expand...
Click to collapse
Yes, this is one of the use-cases of FlashFire. I just haven't finished updating it to 6.0 yet.
Oh nice!
I didn't know it cause I never had the chance to try out FlashFire.
Thanks so much for everything you do for the Android community!
Cheers!
Srandista said:
Ah, sorry, I overlooked that.
Since I have flashed TWRP instead of stock recovery, I'm going by same process as you write, just reflash stock recovery. And can confirm, that the process is indeed working (no need to install system.img, as with previous system-based SuperSU).
Click to expand...
Click to collapse
mine fail here. i previously got systemless root 2.62, blu spark kernel and twrp. fastboot flash stock boot and recovery. reboot to update and it fail. any idea why?
ShanxRoux said:
mine fail here. i previously got systemless root 2.62, blu spark kernel and twrp. fastboot flash stock boot and recovery. reboot to update and it fail. any idea why?
Click to expand...
Click to collapse
Did you modify system?
Try flashing system, boot, and recovery.
Then try again.
Hi, I have a Oneplus One and today has been released an OTA, so I tried the method. I have COS13 JK (latest full rom) firmware, with systemless 2.84beta supersu and twrp.
The only apps that have root access are AdAway and Greenify (without mods to system apps). No Busybox installed.
I reverted via fastboot to original JK boot.img and recovery.img, and restored, via Adaway, the original hosts file, then I applied the OTA via stock Cyano Recovery, but update failed ("system partition has unexpected contents" error).
Why?
Thanks.
you have to unroot first from the app.Revert to original boot. and then flash
Sent from my ASUS_Z00LD using Tapatalk
caldent said:
you have to unroot first from the app.Revert to original boot. and then flash
Sent from my ASUS_Z00LD using Tapatalk
Click to expand...
Click to collapse
I tried: no way to install OTA, I had to wait for the full rom, and dirty flashed it via TWRP without a problem.
Then I rerooted.
Bye!
ok i seem to be getting the run around on where i need to be to ask my question(s)
i am very interested in systemless root....
that being said i am clueless and all info i am findingis just super confusing me.
if someone could humor a noob to systemless rooting that would be greatly appreciated!!
i recently bought 2 new phone for my household, both are the lg tribute hd (also called lg x style)
one click root and pc method of kingoroot etc dont work... i cant locate a twrp or a cwm for this model easily by searching so i am assuming there isnt one (maybe someone could located or help to build one?)- or maybe im not tech smart enough and i can use any?(i dont think so)
model is lg ls675,android 6.0.1, kernel version 3.10.49, build # MXB48T, software is ls676zv3
main reason at the moment for trying to get root is to remove bloatware and to be able to wifi tether without limitations buy the provider, on ther phone that i have obtained root on i used an app called WIFI Tether Router which works beautifully but requires root...
please help as this is how we use our computer with internet and its beneficial all the way around especially to get rid of bloatware and keep device running smoothly...
thanks again for any help. greatly appreciated.
if im not in the right thread please kindly direct me to the correct one. thanks
Some People are frustrated and ask many questions about how to root ze550kl when they cant unlock bootloader
Here is the Guide
You need to backup your data !!! This is the fresh Rom it will delete all of your apps and data
Before You Start
1/ make sure that you install all the ASUS driver needed in your PC
2/Enable Usb Debugging From Developer Option
3/Download ADB Fastboot here: https://drive.google.com/open?id=0Bz0dm2NbHldNS1ZhQUdZYkdqbDQ
4/Go to download page and click package downlaod Pre-Rooted Firmware Here
(noted that you need to use 7zip to unzip the file)
https://drive.google.com/file/d/0Bz0dm2NbHldNZHl0NW91WUFyVlE/view?usp=sharing
Now Root Your Phone
1/Unzip The ADB Fastboot Tool
2/Unzip the Pre-Rooted Firmware
3/Transfer boot.img, recovery.img system.img md5sum Files To Fastboot Adb Tool Folder
4/ Turn Off Your Phone
Hold Volume Up And Insert Usb Cable ( connected with Your PC)
Shift + Mouse Right click To Open Command Prompt In Fastboot Adb Tool Folder
Now write the following command one by one
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img
fastboot -w
fastboot reboot
Done!!
dollasoy said:
Some People are frustrated and ask many questions about how to root ze550kl when they cant unlock bootloader
Here is the Guide
Before You Start
1/ make sure that you install all the ASUS driver needed in your PC
2/Enable Usb Debugging From Developer Option
3/Download ADB Fastboot here: https://drive.google.com/open?id=0Bz0dm2NbHldNS1ZhQUdZYkdqbDQ
4/Download Pre-Rooted Firmware Here
https://www.asuswebstorage.com/navigate/s/732DBEFD76FD487D89C531B63CF6D9E0Y
Now Root Your Phone
1/Unzip The ADB Fastboot Tool
2/Unzip the Pre-Rooted Firmware
3/Transfer boot.img, recovery.img system.img md5sum Files To Fastboot Adb Tool Folder
4/ Turn Off Your Phone
Hold Volume Up And Insert Usb Cable ( connected with Your PC)
Shift + Mouse Right click To Open Command Prompt In Fastboot Adb Tool Folder
Now write the following command one by one
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img
fastboot -w
fastboot reboot
Done!!
Click to expand...
Click to collapse
I would try it but i dont understand in which way dowload from here https://www.asuswebstorage.com/navigate/s/732DBEFD76FD487D89C531B63CF6D9E0Y
I have naturally Auss ID
Hispa
hispanico957 said:
I would try it but i dont understand in which way dowload from here https://www.asuswebstorage.com/navigate/s/732DBEFD76FD487D89C531B63CF6D9E0Y
I have naturally Auss ID
Hispa
Click to expand...
Click to collapse
Click Zek550kl rom and choose package download (I recommend ZE550KL_WW_1.16.40.763)
http://forum.xda-developers.com/attachment.php?attachmentid=3758676&stc=1&thumb=1&d=1463919906
dollasoy said:
Click Zek550kl rom and choose package download (I recommend ZE550KL_WW_1.16.40.763)
http://forum.xda-developers.com/attachment.php?attachmentid=3758676&stc=1&thumb=1&d=1463919906
Click to expand...
Click to collapse
I follow you but download ASUS WebStorage.7z of only 1k ?!?
I try but no proper download...
Just a requst ..but this way is also for ZE550KL with firmware ZE550KL_WW_1.17.40.1234
Hispa
hispanico957 said:
I follow you but download ASUS WebStorage.7z of only 1k ?!?
I try but no proper download...
Just a requst ..but this way is also for ZE550KL with firmware ZE550KL_WW_1.17.40.1234
Hispa
Click to expand...
Click to collapse
Try this link, this is the latest Version I have just uploaded https://drive.google.com/file/d/0Bz0dm2NbHldNZHl0NW91WUFyVlE/view?usp=sharing
dollasoy said:
Try this link, this is the latest Version I have just uploaded https://drive.google.com/file/d/0Bz0dm2NbHldNZHl0NW91WUFyVlE/view?usp=sharing
Click to expand...
Click to collapse
Thank download now... apply your procedure my app and data remain or are deleted ?
Hispa
hispanico957 said:
Thank download now... apply your procedure my app and data remain or are deleted ?
Hispa
Click to expand...
Click to collapse
You need to backup your data !!! This is the fresh rom it will delete all of your app and data
dollasoy said:
You need to backup your data !!! This is the fresh rom it will delete all of your app and data
Click to expand...
Click to collapse
Ok thnak...uhmm backup data without titanium backup or twrp is difficult
Hispa
hispanico957 said:
Ok thnak...uhmm backup data without titanium backup or twrp is difficult
Hispa
Click to expand...
Click to collapse
You can backup apps+appdata using ASUS Backup app.
You don't need to do wipe userdata. Internal memory will be unaffected. I have flashed all pre rooted ROMs from 1.13 to 1.17 without deleting userdata or factory reset. The only annoying thing is that your first boot will show up "Android is upgrading " which will take around 40mins to reach homescreen. Just wipe cache.
sziraqui said:
You can backup apps+appdata using ASUS Backup app.
Click to expand...
Click to collapse
...apps+appdata you mean user apps or also system apps ?
Thank
Hispa
P.S.
To avoid "..up "Android is upgrading " which will take around 40mins to reach homescreen."...you wipe dat from twrp before or pheraps i dont understand
hispanico957 said:
...apps+appdata you mean user apps or also system apps ?
Thank
Hispa
P.S.
To avoid "..up "Android is upgrading " which will take around 40mins to reach homescreen."...you wipe dat from twrp before or pheraps i dont understand
Click to expand...
Click to collapse
System + user apps with data
I am assuming you have stock Rom installed.
If yes, you don't even need to backup anything, if no you will have to backup atleast app data (you will understand when you use the backup app) and restore using the same app after flashing pre rooted firmware.
If I had wiped from recovery, I would lose data, which I don't want as I am too lazy to set up my phone again and again. Also restoring from Backup app takes time. I know I can avoid the "android is upgrading" but I don't want to spend time on frequent restoring, though I always keep a backup of mini militia to save game data since it bothers me:silly:
can I still update to marshmallow if I root my device now?
It's almost useless to root without unlocking bootloader. If you can't flash custom ROMs then it's of no use. I would be happy if you can find a way to unlock bootloader unofficially coz official unlock app does not work
chromsome said:
can I still update to marshmallow if I root my device now?
Click to expand...
Click to collapse
No!
ZenFreak said:
It's almost useless to root without unlocking bootloader. If you can't flash custom ROMs then it's of no use. I would be happy if you can find a way to unlock bootloader unofficially coz official unlock app does not work
Click to expand...
Click to collapse
this thread is not for you !! go and find another thread
ZenFreak said:
It's almost useless to root without unlocking bootloader. If you can't flash custom ROMs then it's of no use. I would be happy if you can find a way to unlock bootloader unofficially coz official unlock app does not work
Click to expand...
Click to collapse
Not really. Root is still very useful for some of us. Some people tend to prefer stock roms and will even upload heavily customized versions of stock firmware. Hell, I've even seen devices with the most hacked together root solution that was hard earned development-wise because it evolved painfully slow as it all revolved around a partial root solution that prevented full on custom or bone stock roms like CM or AOSP.
My point is, if you can't find root useful without a custom rom, then you're doing it wrong.
What do you even do with root?
HampTheToker said:
Not really. Root is still very useful for some of us. Some people tend to prefer stock roms and will even upload heavily customized versions of stock firmware. Hell, I've even seen devices with the most hacked together root solution that was hard earned development-wise because it evolved painfully slow as it all revolved around a partial root solution that prevented full on custom or bone stock roms like CM or AOSP.
My point is, if you can't find root useful without a custom rom, then you're doing it wrong.
What do you even do with root?
Click to expand...
Click to collapse
You can root if you have unlocked bootloader but converse is not always true. We are going to get updates for MM. Its impractical to spend time on patching every official firmware to gain root access. Instead, everyone should focus on unlocking bootloader. The best use of rooting this device would be if we can unlock bootloader with root access. I have been trying to achieve it since the day I bought this phone. Most users gave up but I won't! I quote @LuK1337, "ROOT means nothing unless we can unlock bootloader"
Do you have a pre-rooted fille for the latest Android 6.0.1 firmware???
Thanks!
In the flash of system.img i receive the error: ERROR <File too large>
My phone is hardbricked HELP-ME
Pic: https://uploaddeimagens.com.br/imagens/sem_titulo-jpg--6559
i have done that ..but my phone model was z00ed .but now after doing this phone is not opening !! it stucks in the asus logo !! no recovery mood too!!! i have booted twrp through adb !! then tried to install my last firmware which was lollipop and it says..this package is for "ww-phone" devices ..this is a omni_ze500kl " ...please help me !! what to do now
[Stock Rom] Huawei (Prague) PRA-xxxC432B182
For restoring/ rescue your device.P8 Lite 2017 - PRA-LX1, LX2, LX3, LA-1
P9 Lite 2017
Nova Lite
Honor 8 Youth
Created and tested on this device:
Huawei P8 lite 2017 [PRAGUE]
Model number: PRA-LX1
Build number: PRA-LX1C432B182
free device
The PRA is extrem sensitiv.
Any unconsidered, unofficial intervention, don't forgive it.
Hundreds of users have already "bricked" their device.
The response to the dealers is enormous.
To restore your devices,
I'll provide a complete rom.
It is 100% functional and rooted with SuperSu.
It is to be applied to the device via TWRP restoring.
But it is also suitable for this purpose without an OTA update,
to get the current firmware.
Be sure to read the following instructions carefully.
You're doing it at your own risk!
Rom installation:
In the download folder:
2017-12-30-PRAstockB182root (zip)
there are 26 backup files compressed as Zip files.
After downloading, unpack all files individually into this directory. Then delete all zip's. Now copy the whole directory to your TWRP backup folder. Where your other backups are.
Now flash the stock recovery and perform a factoryreset.
Now flash TWRP and make a wipe of the data and system partitions in TWRP.
Then restore my backup and reboot.
The firmware and the kernel are already rooted.
If necessary, you can install Busybox.
If the device does not boot, the bootloader must be unlocked again with the Huawei unlockcode.
It is a little bit more work for you to unpack everything individually, but this way a faultless installation is possible.
I have tested the up- and download, unpacking and restoring several times. It works perfectly. The rom is bug free.
Now create a new TWRP backup
and remove all older backups from the TWRP backup folder, otherwise they could cause problems later.
Save it to another folder or to
USB-/Stick, or HD.
I would now like to make a few comments on the end of the year:
I've had the P8 lite 2017 for a year.
The first rooting was developed by me.
The SuperSu and the first rooted kernel,
enabled the developers
@Tecalote and KangVip.
TWRP was provided by the LineageOS team. Again and again I have added fresh rootings and roms.
Nevertheless, increased Bricks are not missing.
It took an enormous amount of time to find
help the users. Unfortunately, this didn't work out for everyone.
My recommendation:
Now set up your device completely. Then create a complete backup with the ingenious Huawei Backup App. Now you take the recovery back.
"fastboot flash recovery recovery. img"
Removes TWRP from your brain for the time being.
Your device is now perfect and the firmware is original. You also have root and the OTA update authorization. When OREO comes, you just wait until I announce the new rooting."
I wish you all the best for 2018.
WARNING !
If all this has worked on my device, it does not mean that it goes with everyone else. Follow exactly the instructions to prevent damage. The execution is your risk.
Never make a factory reset in TWRP. Brick !!! Wipes only in stock recovery.
NOTE: Despite careful preparation I can not guarantee that through the implementation of this Guidance does not create damage to the device or operating system, and therefore assume no liability for ensuing damage and malfunction of hardware and software! If you are still unsure, follow these steps: Only perform the procedure if any mentioned conditions (model number, Android version, etc.) apply to you or your device. Read the instructions carefully and completely, check unfamiliar terminology by google or xda. Downloaded files check for viruses. A backup of important settings and data make. The instructions do not perform, if you do not know what you're doing.
Thank you very much: @Tecalote, KangVip,Chainfire, Stephen (Stericson), Jmz Software, LinageOs team, JRummy, as well as.
Huawei Technologies Co., Ltd.
Update 2017-12-31:
I removed the part "dual recovery".
The support on xda is finished.
Only here:
https://www.android-hilfe.de/forum/huawei-p8-lite-2017.2980/
I couldn't restore my phone. I followed all of your instructions and after restoring, when I reboot, the phone goes only in TWRP (no volume keys pressed). Any ideas on what I can do?
In any case thank you for the thread, it's good to have a well described procedure for these things
Restore your last backup and repeat the procedure.
Try this one first:
Root again with the SU (B182) from the download.
Tip for life: try not to trust random nerds on forums, offering "ROMs" and what they call "tutorials". Stick to the outlet which sold you the phone, and deal with them and/or the manufacturer, and you can't go far wrong.
afit5 said:
I couldn't restore my phone. I followed all of your instructions and after restoring, when I reboot, the phone goes only in TWRP (no volume keys pressed). Any ideas on what I can do?
In any case thank you for the thread, it's good to have a well described procedure for these things
Click to expand...
Click to collapse
I had the same situation. It's a bit tricky and you must really know, what you are doing
I rebooted to bootloader an repeated the oem unlock -> this caused a factory reset!!
I am on dual recovery and so I rebooted to twrp, repeated the restore with the b182 stock rom and could reboot to the system
mbwf said:
Tip for life: try not to trust random nerds on forums, offering "ROMs" and what they call "tutorials". Stick to the outlet which sold you the phone, and deal with them and/or the manufacturer, and you can't go far wrong.
Click to expand...
Click to collapse
100% useless post. This does not help anyone.
ChinHon tries to help others and i would trust him more than you...
KuGeSch said:
I had the same situation. It's a bit tricky and you must really know, what you are doing
I rebooted to bootloader an repeated the oem unlock -> this caused a factory reset!!
I am on dual recovery and so I rebooted to twrp, repeated the restore with the b182 stock rom and could reboot to the system
Click to expand...
Click to collapse
UPDATE: I solved in another way, which is: booted to fastboot mode, restored the stock recoveries (recovery1 to recovery1, erecovery to recovery2), then the phone booted normally as it should have had. At that point I could reflash twrp to recovery1, but that is optional.
I think the phone tried to boot but having the wrong recovery in recovery2 slot caused problems (just a random hypothesis). Hope this helps
afit5 said:
UPDATE: I solved in another way, which is: booted to fastboot mode, restored the stock recoveries (recovery1 to recovery1, erecovery to recovery2), then the phone booted normally as it should have had. At that point I could reflash twrp to recovery1, but that is optional.
I think the phone tried to boot but having the wrong recovery in recovery2 slot caused problems (just a random hypothesis). Hope this helps
Click to expand...
Click to collapse
What you call erecocery is this the stock erecovery or is it prague311.img from ChinHon? If it is the stock erecovery, where can I find it for download?
Thanks a lot!
KuGeSch said:
What you call erecocery is this the stock erecovery or is it prague311.img from ChinHon? If it is the stock erecovery, where can I find it for download?
Thanks a lot!
Click to expand...
Click to collapse
-prague311.img is TWRP
-recovery.img is the stock recovery on recovery partition 1
-recovery2.img is the stock eRecovery on recovery partition 2
https://www.mediafire.com/file/r33el93w5wyqwde/recovery2.img
ChinHon said:
-prague311.img is TWRP
-recovery.img is the stock recovery on recovery partition 1
-recovery2.img is the stock eRecovery on recovery partition 2
https://www.mediafire.com/file/r33el93w5wyqwde/recovery2.img
Click to expand...
Click to collapse
Thanks a lot! You are doing a great job!
Hello!
I want to follow this guide, it should be fine for my Dual SIM Variant, right?
I have a problem with one file, that is 'version.emmc.win.md5.zip' that can't be downloaded from MEGA. Can someone please provide a working link for that file?
Also a doubt: when all the files will be ready my idea is to restore your TWRP backup, flash stock recovery then lock bootloader, to make it as near to stock as possible: will this work? I have another TWRP backup that is running on my phone, but if I lock the bootloader it won't start, if I unlock the bootloader there no problems at all.
Thanks for your interesting topic!
SnoopyDog said:
100% useless post. This does not help anyone.
ChinHon tries to help others and i would trust him more than you...
Click to expand...
Click to collapse
Very good. Keep smiling.
baffo92 said:
Hello!
I want to follow this guide, it should be fine for my Dual SIM Variant, right?
I have a problem with one file, that is 'version.emmc.win.md5.zip' that can't be downloaded from MEGA. Can someone please provide a working link for that file?
Also a doubt: when all the files will be ready my idea is to restore your TWRP backup, flash stock recovery then lock bootloader, to make it as near to stock as possible: will this work? I have another TWRP backup that is running on my phone, but if I lock the bootloader it won't start, if I unlock the bootloader there no problems at all.
Thanks for your interesting topic!
Click to expand...
Click to collapse
Here's the link.
https://mega.nz/#!4sd3DI6Z!BOfI0teLD_m3aLUROhiMVZuePySmp329RXZpjsH3AM0
Please tell me why you want to take the rom. What's happening?
ChinHon said:
Here's the link.
https://mega.nz/#!4sd3DI6Z!BOfI0teLD_m3aLUROhiMVZuePySmp329RXZpjsH3AM0
Please tell me why you want to take the rom. What's happening?
Click to expand...
Click to collapse
The link works perfectly. Thanks!
I can now give this stock ROM a try!
EDIT 1: I'm trying to install the ROM but I have a problem with TWRP: I launch the command 'fastboot flash recovery prague311.img' then boot to TWRP, but the touchsceen of the phone is unresponsive and I can't do anything to make it work. Have you got any suggestion?
EDIT 2: I made some mistakes here and there, but the TWRP booted and now I have the phone on your ROM Version! I'm trying to clean everything and do a clean install if I can...
EDIT 3: I've done a full phone clean by using the 'Factory Reset' option in 'Settings'... now the phone boots, but:
1. NFC/GPS are not working, they are blinking
2. FM Radio is not working (it says com.huawei.... and has an Android icon instead of the original icon)
baffo92 said:
The link works perfectly. Thanks!
I can now give this stock ROM a try!
EDIT 1: I'm trying to install the ROM but I have a problem with TWRP: I launch the command 'fastboot flash recovery prague311.img' then boot to TWRP, but the touchsceen of the phone is unresponsive and I can't do anything to make it work. Have you got any suggestion?
EDIT 2: I made some mistakes here and there, but the TWRP booted and now I have the phone on your ROM Version! I'm trying to clean everything and do a clean install if I can...
Click to expand...
Click to collapse
To get the rom completely clean you do the following:
Go to my root thread section: Threadupdate: 2018-01-02 and work through the instructions. Then you have a perfect clean stock rom.
ChinHon said:
To get the rom completely clean you do the following:
Go to my root thread section: Threadupdate: 2018-01-02 and work through the instructions. Then you have a perfect clean stock rom.
Click to expand...
Click to collapse
Your support is very helpful, thanks!
I have problems on the steps to reproduce, even after reading your guide :')
This is what I do:
1. Wipe Data/Factory Reset + Wipe cache with stock recovery
2. Flash TWRP
3. Open TWRP, clean data, system and also cache + dalvik
4. Reboot the phone to a fully working with B182, in English with Dual SIM fully recognised
5. What I have to do from now on to have a fully stock experience (remove custom Kernel, reflash stock recovery and erecover, re-lock bootloader and fully ready to Oreo)?
Can you please guide me?
Thanks and sorry for my problems, but I work with Nexus devices thare a bit more 'elastic' in flashing
The kernel is stock. You just have to flash the eRecovery and recovery. That's all.
ChinHon said:
The kernel is stock. You just have to flash the eRecovery and recovery. That's all.
Click to expand...
Click to collapse
Ok, thanks!
This is what I did before, but I can't do a factory reset due to the problems described (Radio FM not working, NFC not working).
I can't also relock the bootloader, because the phone will boot to erecovery (recovery2) and won't let me reach the boot of the ROM. Have you got any suggestion?
If leave it as it is now (unlocked bootloader with stock recovery1 and recovery2) will Oreo arrive without any problems?
Your support is awesome, thanks
If you now take my UPDATE.APP via dload the problems should be gone.
ChinHon said:
If you now take my UPDATE.APP via dload the problems should be gone.
Click to expand...
Click to collapse
Sounds good!
If I flash the stock recovery, then update officially with an UPDATE.APP from SD Card everything should be ok.
Where can I find your UPDATE.APP? I didn't find it in your MEGA Folder
Thanks, again, for your incredible support!