Database Info

[Q] ota sideloading aborted

Hey group mates please help me
I'm currently using a nexus 5 and thought of sideloading the ota zip through nexus root toolkit so i first flashed stock recovery and then when i tried to sideload it, it started flashing till it reached 61% and which my phone said installation aborted for no reason.. Tried this more than 3-4 times but the result were all the same
I'm not sure what seems to be the issue here so it would be great if any one could help me solve this issue
Thanks in advance

drunken monkey said:
Hey group mates please help me
I'm currently using a nexus 5 and thought of sideloading the ota zip through nexus root toolkit so i first flashed stock recovery and then when i tried to sideload it, it started flashing till it reached 61% and which my phone said installation aborted for no reason.. Tried this more than 3-4 times but the result were all the same
I'm not sure what seems to be the issue here so it would be great if any one could help me solve this issue
Thanks in advance
Click to expand...
Click to collapse
Are you rooted or having custom kernel?

kaushikd said:
Are you rooted or having custom kernel?
Click to expand...
Click to collapse
I'm currently running stock recovery, stock os rooted and unlocked bootloader

I have the exact same problem. The sideload gets to 61%, then shows the following message:
"/system/bin/install-recovery.sh" has unexpected contents
E:Error in /sideload/package.zip
(Status 7)
I have a stock recovery, was rooted using Chainfire's first method for Lollipop (patched kernel) but flashed the stock kernel (fastboot flash boot boot.img) from the N5 5.0 image before the sideload.

drunken monkey said:
I'm currently running stock recovery, stock os rooted and unlocked bootloader
Click to expand...
Click to collapse
You can't be rooted to use the OTA. Anything that is modified in the system will cause this.

I downloaded the full image and extracted just the radio, system and boot image files. Then just a few fastboot commands with bootloader reboots inbetween and 5.0.1 works.
For reference, I used the following:
fastboot flash radio radio.img
fastboot reboot-bootloader
fastboot flash system system.img
fastboot reboot-bootloader
fastboot flash boot boot.img

So while sideloading it should I unroot as well?

jsgraphicart said:
You can't be rooted to use the OTA. Anything that is modified in the system will cause this.
Click to expand...
Click to collapse
So to sideload I have to be in complete stock without even SuperSU.. Is that correct?

drunken monkey said:
So to sideload I have to be in complete stock without even SuperSU.. Is that correct?
Click to expand...
Click to collapse
That correct
Sent from my Nexus 5 using XDA Free mobile app

pauleyc said:
I downloaded the full image and extracted just the radio, system and boot image files. Then just a few fastboot commands with bootloader reboots inbetween and 5.0.1 works.
For reference, I used the following:
fastboot flash radio radio.img
fastboot reboot-bootloader
fastboot flash system system.img
fastboot reboot-bootloader
fastboot flash boot boot.img
Click to expand...
Click to collapse
I was thinking about doing this, too... but am I correct to assume that this would cause data loss? I have TWRP and SuperSU installed at the moment.
Or, if there's an easy way to ditch these and do the OTA, I'd be okay with that, too.

jrronimo said:
I was thinking about doing this, too... but am I correct to assume that this would cause data loss? I have TWRP and SuperSU installed at the moment.
Or, if there's an easy way to ditch these and do the OTA, I'd be okay with that, too.
Click to expand...
Click to collapse
It won't cause any data loss. It's about the only way to get the ota to work. But in your case, since you have twrp you should also flash the stock recovery.img
Sent from my Nexus 5 using XDA Free mobile app

No data loss (well, apart from root) if you flash just the radio, system and boot images. Worked great for me.

Thanks for the tips, guys. After extracting the full 5.0.1 firmware from the Factory Images page, there are system and boot .img files, but no radio. Is this normal?

jrronimo said:
Thanks for the tips, guys. After extracting the full 5.0.1 firmware from the Factory Images page, there are system and boot .img files, but no radio. Is this normal?
Click to expand...
Click to collapse
There's a radio. It's in the first file you extracted, not the zip you also had to extract
Sent from my Nexus 5 using XDA Free mobile app

jd1639 said:
There's a radio. It's in the first file you extracted, not the zip you also had to extract
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
Good thing I didn't get past this step -- I had downloaded the wrong factory image. D: That'll explain things a bit...
---------- Post added at 02:13 PM ---------- Previous post was at 01:54 PM ----------
Alrighty! New problem: After the phone boots, I get the battery and signal icons in the top right, but a black screen otherwise. If I hit the power button to put it in sleep mode and then hit the power button again, I get a quick flash of the "Welcome to Android, select your language" screen. Any pro-tips?
If I have to set up from scratch, it's no big deal. Most of the important stuff should be backed up; it'd just be annoying. All that Desert Golfing progress!!!
Finally managed to get around it. Ended up updating TWRP and re-flashing most of the .imgs a bunch, then using TWRP to first let me back up data to my computer and then wipe partitions. I'm on 5.0.1 again.
Welp, that was painful, haha. I'm sure I did something wrong leading into this, but I'm not sure what that was...

If i just flash the whole Firmware that i downloaded from Google, will i be able to flash it and loose root?
I am OK with loosing root and beeing back to stock.
At this moment i have Lolipop 5.0 that is rooted with Chainfire.

I was running rooted stock 5.0 with TWRP and had already flashed the 5.0.1 radio, so I just fastboot flashed the 5.0.1 system.img and rerooted. All is well so far.

jd1639 said:
That correct
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
So if I unroot and then sideload it will I loose all my data ?
P.s I'll be rooting it back immediately after I get 5.1
So is there any way which can avoid a data loss?

I still have a doubt, I saw rootjunky's video in which he sideload 5.1 to his nexus 7 using nrt..
Even I followed the same method but it didn't succeed for me

pauleyc said:
I have the exact same problem. The sideload gets to 61%, then shows the following message:
"/system/bin/install-recovery.sh" has unexpected contents
E:Error in /sideload/package.zip
(Status 7)
I have a stock recovery, was rooted using Chainfire's first method for Lollipop (patched kernel) but flashed the stock kernel (fastboot flash boot boot.img) from the N5 5.0 image before the sideload.
Click to expand...
Click to collapse
So after flashing your stock kernal and stock recovery did the sideload work.. I mean that it didn't get stuck at the 61% mark?

Problems with downgrading to KitKat

Hey guys, I'm trying to downgrade to KitKat after all the issues Lollipop is giving me and the incompatible apps I'm trying to run.
I am following instructions here but I came across a problem when flashing the system.img file.
The error it gives me is:
FAILED (remote: Insufficient memory.)
I can't flash over system and can not boot.
What am I missing? I was rooted and my bootloader unlocked prior to starting and I tried with the factory recovery and the 1.2.1 recovery image.
Edit: My issue has been solved. Flashing the Full OTA.zip file will install KitKat over Lollipop. No need to manually flash each file through fastboot. I wish guides would tell you that instead.

BlackDave said:
Hey guys, I'm trying to downgrade to KitKat after all the issues Lollipop is giving me and the incompatible apps I'm trying to run.
I am following instructions here but I came across a problem when flashing the system.img file.
The error it gives me is:
FAILED (remote: Insufficient memory.)
I can't flash over system and can not boot.
What am I missing? I was rooted and my bootloader unlocked prior to starting and I tried with the factory recovery and the 1.2.1 recovery image.
Click to expand...
Click to collapse
I don't know why that wouldn't work. Have you tried just downloading the image from nvidia HERE?
I'm assuming wifi since your sig says 16GB

Keithn said:
I don't know why that wouldn't work. Have you tried just downloading the image from nvidia HERE?
I'm assuming wifi since your sig says 16GB
Click to expand...
Click to collapse
Those are the same files as the ones I downloaded in the other thread.

I got my tablet working again on Lollipop 5.0.1 but that's not where I want to be. I've searched about my error message but most threads I found went unanswered.

Your best bet might just be to try getting a full OTA and flashing it through cwm or something. I'll try with mine when I have some time to backup and flash, probably later tomorrow. If I find anything out I'll post.
Sent from my SHIELD Tablet

BlackDave said:
I got my tablet working again on Lollipop 5.0.1 but that's not where I want to be. I've searched about my error message but most threads I found went unanswered.
Click to expand...
Click to collapse
I just flashed the images and booted.
Did you accidentally try flashing to the wrong place, such as flashing to boot( which would be too small) instead of system? Did you do all of the commands yourself or use the .bat? My shield disconnected after doing the boot.img and system.img for some reason, so I had to select fastboot protocol to reboot the bootloader and continue to flash the userdata.img, blob, and battery.dtb.

was your tablet internal memory full?, try wipping data and chace and you could use the script that the original Nvidia recovery image has zipped. I went up and down like 3 times, im in kitkat right now and not experiencing any problem.

Iams1002 said:
was your tablet internal memory full?, try wipping data and chace and you could use the script that the original Nvidia recovery image has zipped. I went up and down like 3 times, im in kitkat right now and not experiencing any problem.
Click to expand...
Click to collapse
No I wipped internal data since I keep everything on external and it still didn't work.
Keithn said:
I just flashed the images and booted.
Did you accidentally try flashing to the wrong place, such as flashing to boot( which would be too small) instead of system? Did you do all of the commands yourself or use the .bat? My shield disconnected after doing the boot.img and system.img for some reason, so I had to select fastboot protocol to reboot the bootloader and continue to flash the userdata.img, blob, and battery.dtb.
Click to expand...
Click to collapse
So I should just flash the ota.zip?
Also i did everything like the guide. I flashed boot to boot, recovery to recovery. The only thing that gave me an error was system. Userdata, blob, and battery also flashed successfully. After that didn't work, I also tried the .bat and that didn't work either. Flashing the 5.0.1 update got my tablet running again.

BlackDave said:
No I wipped internal data since I keep everything on external and it still didn't work.
So I should just flash the ota.zip?
Also i did everything like the guide. I flashed boot to boot, recovery to recovery. The only thing that gave me an error was system. Userdata, blob, and battery also flashed successfully. After that didn't work, I also tried the .bat and that didn't work either. Flashing the 5.0.1 update got my tablet running again.
Click to expand...
Click to collapse
If you can find a full ota.zip for update 1.2.1 I'd try that. I'm not sure why you would be having this issue. The only other things I can say to try is redownloading and rebooting the boot loader (select fastboot protocol) between images in case something funny is happening there. Let us know how you end up doing.
Sent from my HTC M8

Keithn said:
If you can find a full ota.zip for update 1.2.1 I'd try that. I'm not sure why you would be having this issue. The only other things I can say to try is redownloading and rebooting the boot loader (select fastboot protocol) between images in case something funny is happening there. Let us know how you end up doing.
Sent from my HTC M8
Click to expand...
Click to collapse
I flashed the 1.2.1 OTA update and it worked. The first time I tried, I did using the TWRP recovery but for some reason, that recovery fails to flash OTAs, so I went with CWM and flashed the 2.1 update and all worked again. After a while, I got tired of all the issues lollipop gave me so that's why I tried following that guide to downgrade.
In the end, using CWM and flashing the OTA is the best way to go. Thank you all for you help.

Moto G XT1033 (India) problems updating to Lollipop

Hello everyone, I have a Moto G (2013) aka first generation Moto G & I live in India. I had unlocked my bootloader. I even flashed cwm touch via fastboot but it doesn't go to recovery mode at all. I get a black screen. I tried flashing the official TWRP 2.8.4.0 today, but I get a message that reads, "Partition size mismatch" & I'm stuck. The phone is usable & it boots up normally & I use it daily. But it is the recovery that is messed up. I tried updating to lollipop by ota but the device got stuck on a black screen once the ota was downloaded. I tried downloading the KitKat factory image, but the link is dead. Please, somebody help!! Thanks in advance!
Sent from my XT1033 using xda premium

The partition size mismatch error can be ignored, You get that error because the TWRP 2.8.4.0 is for the XT1032 and not the XT1033. To flash the OTA, you have to use the stock recovery only. Your system should not be modified (eg. It shouldn't be rooted, and if it had been rooted previously, you will have to unroot it.) To flash the stock recovery again, download the Asian XT1033 4.4.4 firmware and just flash the "recovery.img" from it. The flash the OTA. The numerous guides regarding this in the general section should help you.

I have a similar question.
I have unlocked bootloader & rooted moto g.
I received official OTA update today but its not installing. Do I need to lock bootloader or do something else to install the official OTA update?

Facing a similar issue. Updated the moto g and was successful. It was used for a couple of days before the error cropped up.
Now, it boots up but goes to a black screen after the boot animation. However, it still connects to the computer and I'm able to see the phone and its files in explorer. Beyond that, I can't interact with the phone because the screen is totally black.
Additionally, I can access the bootloader, but selecting 'factory' or 'recovery' isn't doing anything - just black screens everywhere.
The phone was perfectly fine for a few days after the update. (The phone is unrooted and unmodded and was running stock at lolipop update.)
Another thread suggests that I should
Code:
fastboot erase cache
fastboot erase userdata
Is that a viable course of action? Has anybody been able to recover from this issue?

pr.itdude said:
I have a similar question.
I have unlocked bootloader & rooted moto g.
I received official OTA update today but its not installing. Do I need to lock bootloader or do something else to install the official OTA update?
Click to expand...
Click to collapse
No need to lock. Unroot, reflash stock signed recovery and you should be good to go. Also undo any modifications you made to the filesystem and wiping /cache should help prevent errors.
---------- Post added at 02:42 AM ---------- Previous post was at 02:40 AM ----------
SoberDogs said:
Facing a similar issue. Updated the moto g and was successful. It was used for a couple of days before the error cropped up.
Now, it boots up but goes to a black screen after the boot animation. However, it still connects to the computer and I'm able to see the phone and its files in explorer. Beyond that, I can't interact with the phone because the screen is totally black.
Additionally, I can access the bootloader, but selecting 'factory' or 'recovery' isn't doing anything - just black screens everywhere.
The phone was perfectly fine for a few days after the update. (The phone is unrooted and unmodded and was running stock at lolipop update.)
Another thread suggests that I should
Code:
fastboot erase cache
fastboot erase userdata
Is that a viable course of action? Has anybody been able to recover from this issue?
Click to expand...
Click to collapse
Try fastboot erase cache, it shouldn't delete any of your data and it might be enough to get the device working again. You might want to wipe the dalvik-cache as well. If all else fails, since you can access you filesystem, backup all important files and do a factory reset.

skyguy126 said:
No need to lock. Unroot, reflash stock signed recovery and you should be good to go. Also undo any modifications you made to the filesystem and wiping /cache should help prevent errors.
Click to expand...
Click to collapse
Ok. Few more Q pls:
1. Reflashing stock recovery wipes system data & apps? After this my phone will be rooted or not? Any links where i can read more about it?
2. I have stock ROM but yes I installed xposed framework & few modules. Is it a filesystem modification?
3. Any other alternative to this?

pr.itdude said:
Ok. Few more Q pls:
1. Reflashing stock recovery wipes system data & apps? After this my phone will be rooted or not? Any links where i can read more about it?
2. I have stock ROM but yes I installed xposed framework & few modules. Is it a filesystem modification?
3. Any other alternative to this?
Click to expand...
Click to collapse
1. No it should not. If you had root before you will still have it. Search in the forum for more info.
2. Yes but you can easily uninstall xposed with the click of a button.
3. This is by far the easiest and safest method. I know of one alternative is to flash the ota update zip through custom recovery but you are on your own there.

skyguy126 said:
1. No it should not. If you had root before you will still have it. Search in the forum for more info.
2. Yes but you can easily uninstall xposed with the click of a button.
3. This is by far the easiest and safest method. I know of one alternative is to flash the ota update zip through custom recovery but you are on your own there.
Click to expand...
Click to collapse
ok so Here what i am planning:
1. Uninstall all modules & xposed framework
2. Unroot using supersu
3. Restore/reflash stock recovery (just recovery not whole firmware as I already have stock rom)
4. Install the update either manually via recovery or using auto install.
Am i on right path? Pls help me on step 3, any link or step-t-step guide? I couldn't find one, every post is abt restoring whole firmware.
TIA. Cheers !!

pr.itdude said:
ok so Here what i am planning:
1. Uninstall all modules & xposed framework
2. Unroot using supersu
3. Restore/reflash stock recovery (just recovery not whole firmware as I already have stock rom)
4. Install the update either manually via recovery or using auto install.
Am i on right path? Pls help me on step 3, any link or step-t-step guide? I couldn't find one, every post is abt restoring whole firmware.
TIA. Cheers !!
Click to expand...
Click to collapse
Yep you should be good good luck!!!

Unable to boot up after flashing Supersu on stock firmware image

PROBLEM SOLVED, THREAD CLOSED, THANKS FOR YOUR HELP
Hi guyz i'm stuck in a problem and may you can help me to get over it. I have Moto G 2015 (XT1550), before i was on stock and everything was working perfectly (including xposed and supersu). Then i moved to CyanogenMod 13.0 for my device. Now i want to flash stock again and i did it perfectly as well and it does boot up perfectly, but when i flash Supersu to root this time (I tried every supersu for marshmallow whether it is "2.67 or 2.71(latest)" it is not booting up, it freezes on logo.
1. I tried every version of TWRP for moto G
2. Tried every version of supersu
3. Without flashing supersu i boots up perfectly.
4. I can't provide log as phone is not booting up.
I'm attaching 3 screenshots, one of them is after flashing Stock firmware (of course through cmd method) and the another two after flashing cyanogenmod 13. There is difference between both images, please check them and try to provide me solution for it.
First two are after flashing cyanogenmod and last one is after flashing supersu on stock

Try BETA-SuperSU-v2.65.

lost101 said:
Try BETA-SuperSU-v2.65.
Click to expand...
Click to collapse
Tried didn't worked same problem stuck on logo, as you can see difference between both screenshots is, one is flashing "system mode" and the another one "system less mode" and in system less mode it is also flashing boot image.. Before it was fine, i don't know wtf is this.
Sent from my MotoG3 using XDA-Developers mobile app

@Chainfire please do have a look, it's a supersu problem.
Sent from my MotoG3 using XDA-Developers mobile app

@Aman Dewett - Are you doing a 'Factory data reset' in Android before flashing the firmware image? Just because Android loads does not mean everything is fine.

Aman Dewett said:
Tried didn't worked same problem stuck on logo, as you can see difference between both screenshots is, one is flashing "system mode" and the another one "system less mode" and in system less mode it is also flashing boot image.. Before it was fine, i don't know wtf is this.
Sent from my MotoG3 using XDA-Developers mobile app
Click to expand...
Click to collapse
Did you try 2.62-3?

lost101 said:
@Aman Dewett - Are you doing a 'Factory data reset' in Android before flashing the firmware image? Just because Android loads does not mean everything is fine.
Click to expand...
Click to collapse
No, through twrp -> wipe-> advance, I remove OS totally. I mean wipe everything except otg and external sd card.
Sent from my MotoG3 using XDA-Developers mobile app

Aman Dewett said:
No, through twrp -> wipe-> advance, I remove OS totally. I mean wipe everything except otg and external sd card.
Click to expand...
Click to collapse
Don't ignore the instructions in the Factory Firmware flashing tutorial. This is the source of your problem.
You must do a 'Factory data reset' in Android or Stock Recovery prior to flashing.

lost101 said:
Don't ignore the instructions in the Factory Firmware flashing tutorial. This is the source of your problem.
You must do a 'Factory data reset' in Android or Stock Recovery prior to flashing.
Click to expand...
Click to collapse
I did factory reset as well bro and of course i flashed properly as instructed in "how to flash" thread by you.
That is the reason everything was working perfectly before and still i'm following the same process but this time after flashing supersu on stock it stuck on logo.
Sent from my MotoG3 using XDA-Developers mobile app

MrTooPhone said:
Did you try 2.62-3?
Click to expand...
Click to collapse
Yes
Sent from my MotoG3 using XDA-Developers mobile app

Aman Dewett said:
I did factory reset as well bro and of course i flashed properly as instructed in "how to flash" thread by you.
Click to expand...
Click to collapse
Please state clearly that you did a Factory data reset via Settings > Backup & reset.

lost101 said:
Please state clearly that you did a Factory data reset via Settings > Backup & reset.
Click to expand...
Click to collapse
No i did not performed "factory data reset" through backup & reset settings.
I format phone through twrp only..
At first i wiped it normally, then format it through advance wipe option and removed whole os from phone then flashed stock through CMD.
Sent from my MotoG3 using XDA-Developers mobile app

I cannot help you as you refuse to follow the instructions I have provided.

lost101 said:
I cannot help you as you refuse to follow the instructions I have provided.
Click to expand...
Click to collapse
Ok this time i will follow proper instruction likewise format phone through backup & reset option and then will open boot loader mode and flash the rom according to instruction (commands) provided. Let's see what will happen.

As of now SuperSU 2.62-3 is the only version that is not creating a problem. I too tried the latest versions from 2.67 to 2.71 but landed with my phone stuck at unlocked bootloader screen. Erasing cache and userdate is recommended as suggested by twrp.

lost101 said:
I cannot help you as you refuse to follow the instructions I have provided.
Click to expand...
Click to collapse
I did properly what you said, at first i "factory reset" through backup & reset option, then i open bootloader mode and flashed it according to given instructions. At the end after flashing supersu 2.65 stuck n logo. Same issue.

arunhebbare said:
As of now SuperSU 2.62-3 is the only version that is not creating a problem. I too tried the latest versions from 2.67 to 2.71 but landed with my phone stuck at unlocked bootloader screen. Erasing cache and userdate is recommended as suggested by twrp.
Click to expand...
Click to collapse
removed cache and user data as well bro didn't worked.

I faced the same problem on 6.0.1 only, and I tried every su version "UPDATE" "BETA", rooted with kingroot and unfortunately I lost my SIM card recognition!
Sent from my MotoG3 using Tapatalk

Aman Dewett said:
Hi guyz i'm stuck in a problem and may you can help me to get over it. I have Moto G 2015 (XT1550), before i was on stock and everything was working perfectly (including xposed and supersu). Then i moved to CyanogenMod 13.0 for my device. Now i want to flash stock again and i did it perfectly as well and it does boot up perfectly, but when i flash Supersu to root this time (I tried every supersu for marshmallow whether it is "2.67 or 2.71(latest)" it is not booting up, it freezes on logo.
1. I tried every version of TWRP for moto G
2. Tried every version of supersu
3. Without flashing supersu i boots up perfectly.
4. I can't provide log as phone is not booting up.
I'm attaching 3 screenshots, one of them is after flashing Stock firmware (of course through cmd method) and the another two after flashing cyanogenmod 13. There is difference between both images, please check them and try to provide me solution for it.
First two are after flashing cyanogenmod and last one is after flashing supersu on stock
Click to expand...
Click to collapse
If you and I are having the same device, and have followed the steps as given elsewhere, and I could root my phone without any problem I don't see any reason why you should not unless you are deviating or any other reason which you know or do not.... BTW it takes a long time to reboot the phone after flashing the 2.62-3. Are you falling short on patience?

arunhebbare said:
If you and I are having the same device, and have followed the steps as given elsewhere, and I could root my phone without any problem I don't see any reason why you should not unless you are deviating or any other reason which you know or do not.... BTW it takes a long time to reboot the phone after flashing the 2.62-3. Are you falling short on patience?
Click to expand...
Click to collapse
If you can read i mentioned in OP that phone gets freeze on logo, It is not going on booting stage.

XT1254 Won't boot to system after factory reset

Hi,
I have a VZW Quark that's been unlocked with Sunshine and rooted and running fine on custom ROM's for a year. Today I did a factory reset and complete wipe and reinstalled RR Rom and GApps etc. However, on reboot, it only goes back to recovery (TWRP 3.1.1-0). I faced this the last time as well and managed to find the fix by googling it but can't seem to get to it now. It was a quick fix and then it booted to system fine and I cannot remember it. Can anyone help! Thanks.

Rikhit said:
Hi,
I have a VZW Quark that's been unlocked with Sunshine and rooted and running fine on custom ROM's for a year. Today I did a factory reset and complete wipe and reinstalled RR Rom and GApps etc. However, on reboot, it only goes back to recovery (TWRP 3.1.1-0). I faced this the last time as well and managed to find the fix by googling it but can't seem to get to it now. It was a quick fix and then it booted to system fine and I cannot remember it. Can anyone help! Thanks.
Click to expand...
Click to collapse
Someone else had this issue and they solved it by flashing the latest @bhb27 modded TWRP. You say you have TWRP 3.1.1, but is it from the TWRP website or from @bhb27? Flash this one below to make sure.
twrp-3.1.1-mod_2-quark.img
https://androidfilehost.com/?w=files&flid=39562
Once they flashed it, they were able to boot to system, then they booted back to TWRP (on purpose) -- and then upon subsequent reboots everything was fine.
See here:
mpro420 said:
@bhb27 Im face a problem, since I do a clean install build 08/23, when my phone restart, it always boot into TWRP, and I need to boot to bootloader and press START to start system normally.
Maybe Im doing something worng due the install process, (full wipe include internal storage, flash Crdroid, flash Gapps, reboot), I try to flash boot.img and new TWRP 3.1.1 recovery.img, but got a same results.
Please help, thanks a lot.
我從使用 Tapatalk 的 DROID Turbo 發送
Click to expand...
Click to collapse
bhb27 said:
You may not be using the TWRP made by me, check TWRP thread and use the twrp-3.1.1-mod_2-quark.img version that is in the afh mirror folder if you are not using that... also try to update the ROM as 8/23 is one month old on updates...
Click to expand...
Click to collapse
mpro420 said:
Thank you!!
After flash the TWRP 3.1.1-mod 2, my phone booting is back to normal. :good
ps: I want to donate to your hard work, but I dont had a Paypal account, its there other way I can buy you a beer?
我從使用 Tapatalk 的 DROID Turbo 發送
Click to expand...
Click to collapse
bhb27 said:
Mod TWRP can cleanup the "android to recovery commands" the process was changed in nougat and official or old version don't have the new support...
From outside of Brazil that is the only option that I can received and use what I have received...
:good:
Click to expand...
Click to collapse