Related
Hey all,
So I received a notification for a system update to 4.4.3, and I had survival mode in SuperSU checked, so I went ahead and followed the procedure. Turns off, then reboots into TWRP. From there I reboot again using the TWRP option, and it boots into android just fine. Notification is gone, still with root. But then I go to settings >> about to find that I'm still running on 4.4.2. Manually check for update, says there isn't one available. Give it a day or so and the notification comes up again. Repeat, and same thing. I'm stuck with the notification again.
So, how do I get rid of the notification, or more preferably, how to I update to 4.4.3 keeping the root? Thanks.
UnfriendlyTurtle said:
Hey all,
So I received a notification for a system update to 4.4.3, and I had survival mode in SuperSU checked, so I went ahead and followed the procedure. Turns off, then reboots into TWRP. From there I reboot again using the TWRP option, and it boots into android just fine. Notification is gone, still with root. But then I go to settings >> about to find that I'm still running on 4.4.2. Manually check for update, says there isn't one available. Give it a day or so and the notification comes up again. Repeat, and same thing. I'm stuck with the notification again.
So, how do I get rid of the notification, or more preferably, how to I update to 4.4.3 keeping the root? Thanks.
Click to expand...
Click to collapse
You can't update the "normal way" like that with a custom recovery. When you try to do that, it tries to boot into the stock recovery to update, but since you have a custom recovery, it will fail everytime if you do it that way. What you have to do is flash the OTA zip using TWRP. You can find the OTA zip in /cache on your device. Or you can just download the update zip from these forums.
UnfriendlyTurtle said:
Hey all,
So I received a notification for a system update to 4.4.3, and I had survival mode in SuperSU checked, so I went ahead and followed the procedure. Turns off, then reboots into TWRP. From there I reboot again using the TWRP option, and it boots into android just fine. Notification is gone, still with root. But then I go to settings >> about to find that I'm still running on 4.4.2. Manually check for update, says there isn't one available. Give it a day or so and the notification comes up again. Repeat, and same thing. I'm stuck with the notification again.
So, how do I get rid of the notification, or more preferably, how to I update to 4.4.3 keeping the root? Thanks.
Click to expand...
Click to collapse
Since 4.4.4 is out, just download the full firmware package from Google and flash system, boot. Only those two.
If you don't know how to do that, the Nexus 5 forums has some great stickies that are mostly relevant to this device.
charesa39 said:
You can't update the "normal way" like that with a custom recovery. When you try to do that, it tries to boot into the stock recovery to update, but since you have a custom recovery, it will fail everytime if you do it that way. What you have to do is flash the OTA zip using TWRP. You can find the OTA zip in /cache on your device. Or you can just download the update zip from these forums.
Click to expand...
Click to collapse
Right, thanks for the information. So I repeated and booted into TWRP again. Tapped 'Install', navigated to /cache, saw a couple of folders named 'back up', 'lost+found', and then a file name of a large string of letters followed by the recognisable "razor KTU70 from KOT49H", so I went ahead and flashed the latter, checking 'verify signature'. Runs through a few commands and in a few seconds comes back as failed, so I reboot into the OS.
Any ideas?
Aerowinder said:
Since 4.4.4 is out, just download the full firmware package from Google and flash system, boot. Only those two.
If you don't know how to do that, the Nexus 5 forums has some great stickies that are mostly relevant to this device.
Click to expand...
Click to collapse
I think I have an idea, but I'll check just to be sure. Thanks for the direction.
Exactly the same for me. Installing the ota sent me to my TWRP recovery. Reboot - > still in 4.4.2.
Reading this thread, I went to TWRP recovery, installed the update from cache and like you, it failed.
Any suggestions? Did your idea work?
Where do I find the 4.4.4 mentioned here and how do I flash it in TWRP? Is install the same as flash in TWRP?
Thanks.
Anderson2 said:
Exactly the same for me. Installing the ota sent me to my TWRP recovery. Reboot - > still in 4.4.2.
Reading this thread, I went to TWRP recovery, installed the update from cache and like you, it failed.
Any suggestions? Did your idea work?
Where do I find the 4.4.4 mentioned here and how do I flash it in TWRP? Is install the same as flash in TWRP?
Thanks.
Click to expand...
Click to collapse
If it fails look to see what the specific error is. It would help to know that. If you pulled it from your cache then I assume it was downloaded by itself and should be the correct OTA. I do NOT have the "Zip file signature verification." box checked or "Enable MD5 verification of backup files." but I am extremely careful to flash/install the correct files. The OTA installed fine for me two days ago using TWRP 2.7.1.0. The 4.4.4 mentioned earlier is the factory image. You will need adb and fastboot installed on your computer to flash the factory image or any image that is pulled from inside the factory image. Wug's toolkit will work also, I think, but I've never used any toolkits. Eventually there will be a stock 4.4.4 rom that you can flash/install in TWRP but I'm not aware of one right now.
You can take the normal updates with root and TWRP (I did), but a custom kernel will prevent them from installing.
I retried to install the downloaded ota file from cache, but this time I checked zip file verification and got the error message that zip verification failed.
File name was
df43279bcf6bb6a0ae403249c3e6f314d0a7eb77.signed-razor-KTU84L-from-KOT49H.df43279b.zip
So it seems the downloaded ota file may be corrupted. How do I get my Nexus 7 2013 to re-download a new one?
(The ota download for my Nexus 5 installed with no problems - but I think it didn't go through TWRP even though TWRP is installed there too).
Thanks
---------- Post added at 04:05 AM ---------- Previous post was at 03:59 AM ----------
Further
I renamed the ota file and in settings checked for system update and got a response that my system is upto date. But it is still 4.4.2.
Need to re-download the ota. How?
Changed the system date to 2 weeks earlier and succeeded in re-downloading the ota file.
So I retried installing it and it again took me to my TWRP recovery screen. I again installed the ota from cache and again the zip verification failed : 1
And the update failed again.
Still on 4.4.2
Did not change any system files as far as I know.
Need help.
Why don't you guys download the stock firmware from Google (link in my signature), and use fastboot to flash system.img, boot.img (DO NOT run the batch file)? If it's a lack of knowledge, all you need do is ask, and I or someone else would be happy to teach you how to use it (fastboot). If you're going to be modifying your Nexus device, you need to learn fastboot. You guys have got to learn the proper way to do things.
You've put forth so much effort to fix a system that is not meant for modified (rooted, customized) phones. You can't fix it, stop trying. Just do it the proper way. And do not use a toolkit. They don't teach you anything, they spoon-feed.
Aerowinder said:
Why don't you guys download the stock firmware from Google (link in my signature), and use fastboot to flash system.img, boot.img (DO NOT run the batch file)? If it's a lack of knowledge, all you need do is ask, and I or someone else would be happy to teach you how to use it (fastboot). If you're going to be modifying your Nexus device, you need to learn fastboot. You guys have got to learn the proper way to do things.
You've put forth so much effort to fix a system that is not meant for modified (rooted, customized) phones. You can't fix it, stop trying. Just do it the proper way. And do not use a toolkit. They don't teach you anything, they spoon-feed.
Click to expand...
Click to collapse
I don't use a toolkit and would be happy to flash the system.Img and boot.img but need instructions on how to do it. You said the stock firmware link is in your signature but it isn't.
I would like to skip 4.4.3 and go directly from 4.4.2 to 4.4.4. I'm talking about a nexus 7 2013 wifi.
So I need the following information to proceed .
1. The Link to download system.img and boot.img for the nexus 7 2013 wifi. Which files exactly?
2. I have fastboot and adb installed on my windows 7 laptop because I used them (once) to root but I don't remember how I used them that one time. How exactly do I use fastboot to flash 4.4.4 ?
3. I presume I will lose root. How do I regain it after the above.
Thank you.
Anderson2 said:
I don't use a toolkit and would be happy to flash the system.Img and boot.img but need instructions on how to do it. You said the stock firmware link is in your signature but it isn't.
I would like to skip 4.4.3 and go directly from 4.4.2 to 4.4.4. I'm talking about a nexus 7 2013 wifi.
So I need the following information to proceed .
1. The Link to download system.img and boot.img for the nexus 7 2013 wifi. Which files exactly?
2. I have fastboot and adb installed on my windows 7 laptop because I used them (once) to root but I don't remember how I used them that one time. How exactly do I use fastboot to flash 4.4.4 ?
3. I presume I will lose root. How do I regain it after the above.
Thank you.
Click to expand...
Click to collapse
1. The Google firmware link in my signature is the one you want. You say you have the 2013 wifi model, aka flo, aka razor. "Factory Images "razor" for Nexus 7 [2013] (Wi-Fi)" is the proper section for you. You want 4.4.4 (KTU84P), and that's at the bottom of the razor section. Click the link to download.
2. Download the most up to date ADB/Fastboot from the link in my signature (19.0.2 (API 19)). Don't extract it yet.
3. You will lose root. Download SuperSU from my signature. 2.00 is the current version. After you download that, you can put it on your device so you can flash it in recovery in a few minutes.
The firmware you downloaded is razor-ktu84p-factory-b1b2c0da.tgz. This is a compressed archive, and you will need to extract it. If you don't know how, 7-Zip should work.
So, you've extracted the files. Delete flash-all.bat, flash-all.sh, flash-base.sh (so you don't accidentally run them).
Now, all you have left is bootloader-flo-flo-04.02.img and image-razor-ktu84p.zip.
Extract image-razor-ktu84p.zip to the current directory, so you will now have bootloader-flo-flo-04.02.img, boot.img, cache.img, recovery.img, system.img, userdata.img, android-info.txt, image-razor-ktu84p.zip in your folder.
Delete userdata.img, flashing this on accident will wipe your data. Delete image-razor-ktu84p.zip, android-info.txt, cache.img, recovery.img (this is stock recovery, you want TWRP).
Now you have boot.img, bootloader-flo-flo-04.02.img, system.img.
Remember the ADB & Fastboot zip you downloaded from my signature? Extract it to the directory with bootloader-flo-flo-04.02.img, boot.img, system.img. All 4 files. This directory now contains 7 files.
Back out of the razor-ktu84p folder. Just one step back. Now, hold shift the right-click the razor-ktu84p folder. Select Open command window here.
Reboot your device to bootloader mode. Do so by shutting it down. Then while the power is off, hold volume down and press the power button. Release these buttons when you see the big green Android.
In your command window, type the command: fastboot devices
Your device with it's serial number should show up on the list. If it does not there is a problem and you need to stop here.
If the device shows up, let's update it.
fastboot flash bootloader bootloader-flo-flo-04.02.img
<wait for it to finish>
fastboot reboot-bootloader
<wait for it to reboot>
fastboot flash system system.img
<wait for it to finish>
fastboot flash boot boot.img
<wait for it to finish>
fasboot reboot-bootloader
Done with fastboot.
At this point, enter recovery (TWRP) and wipe cache and Dalvik under advanced wipe.
Remember the SuperSU you downloaded earlier and put on your device for later? Flash that now.
Reboot, all done. Most of this is just juggling files around. If you have any questions ask.
You are wonderful aerowinder. This is just what I needed to go ahead. Thank you so much.
About your signature, it doesn't show the links when viewed in my Tapatalk version, but I went to the Web view and got it from there. (just FYI if others ask about your links).
is it possible to just flash the system img in fastboot? It's still the same bootloader, not updated? Could I just flash the whole zip by sideloading in adb and TWRP? Just a lottle confused. Thanks!
droider137 said:
is it possible to just flash the system img in fastboot? It's still the same bootloader, not updated? Could I just flash the whole zip by sideloading in adb and TWRP? Just a lottle confused. Thanks!
Click to expand...
Click to collapse
If you were already on 4.4.3, all you need to do is fastboot flash system.img, that is correct.
No, you can't flash that firmware zip in recovery.
thanks
Hi Aerowinder
Thanks again for the excellent instructions. Everything went like clockwork until it didn't ?......
I got to the point where I issued the command fastboot devices which did show the tablet serial number. But my next command to flash the bootloader img gave me the error:
Cannot open 'bootloader-flo-flo-04.02.img
(I had copy pasted the command from your instructions).
The subdirectory below the command window contains that file (one of 7 files)
Sorry. What should I do?
In case you need the info, the device screen showed
Fastboot mode
Product name - flo
Variant - flo 32G
Hw version - rev_e
Bootloader version - flo-04.02
Carrier info = none
Serial number - xxxx
Signing - yes
Secure boot enabled
Lock state - unlocked
Thanks again.
Aerowinder, you are not only an expert but an excellent teacher. Your instructions above should be a sticky.
I'm all done. Everything is fine.
The problem I had above was a file path problem. Not sure why you told me to open the command window in the parent folder. When I opened it in the folder containing the seven files all your commands worked fine. (Except for your last one where you had a spelling mistake: fasboot instead of fastboot).
Thank you very much.
[Solved]Dear friends,
I tried to upgrade my Nexus 5x via factory image files and adb commands. FYI I have done it before on my Nexus 4 so I thought it would be straightforward.
Downloaded the image files and did as the routine procedure is. However when I was flashing individual files, it was system.img turn to be flashed, I got this error "target reported max download size of 536870912 bytes"
and it won't flash system.img file.
The phone can go into bootloader, but fails to start up or whatever.
Any solution is much appreciated. :crying:
[emoji736] Solution:
Use flashall.bat which comes with the stock recovery and give it a good deal of time to parse system.img and transfer it to the phone.
You have to wait longer.
sure thet you have flashed img files one by one? i've had the same problem flashing factory image by flashall.bat...flashing img file one by one, no prob.
but if you have this problem with manual flash, try to flash twrp and install a rom zip by twrp
hamedunix said:
Dear friends,
I tried to upgrade my Nexus 5x via factory image files and adb commands. FYI I have done it before on my Nexus 4 so I thought it would be straightforward.
Downloaded the image files and did as the routine procedure is. However when I was flashing individual files, it was system.img turn to be flashed, I got this error "target reported max download size of 536870912 bytes"
and it won't flash system.img file.
The phone can go into bootloader, but fails to start up or whatever.
Any solution is much appreciated. :crying:
Click to expand...
Click to collapse
It isn't an error I think.
it's because the filesize of system.img is too big for flashed in one go, so system.img need to be parsed (in Nougat, it become 5 parts) and send one by one to phone (the fastboot command will handle this, so no need to manual parsing).
I had this problem, I just canceled the command and tried again, and success.
if it still not working, try clear cache and reset from recovery (twrp is recommended)
as long as your phone can boot to bootloader and detected by fastboot, I think your phone is far from bricked.
ikyeye said:
It isn't an error I think.
it's because the filesize of system.img is too big for flashed in one go, so system.img need to be parsed (in Nougat, it become 5 parts) and send one by one to phone (the fastboot command will handle this, so no need to manual parsing).
I had this problem, I just canceled the command and tried again, and success.
if it still not working, try clear cache and reset from recovery (twrp is recommended)
as long as your phone can boot to bootloader and detected by fastboot, I think your phone is far from bricked.
Click to expand...
Click to collapse
I am on stock recovery.
I managed to solve the problem by using "flash all" command instead of flashing each file separately.
Thanks for the reply though.
There might have been a problem with the version of fastboot I was using since it was unable to parse the package automatically and I had to use flashall.bat and give it a good deal of time to be parsed, transfered and written.
hamedunix said:
There might have been a problem with the version of fastboot I was using since it was unable to parse the package automatically and I had to use flashall.bat and give it a good deal of time to be parsed, transfered and written.
Click to expand...
Click to collapse
Glad that you figured it out. Make sure to update your fastboot of course. For me, flashing system.img took quite awhile longer than I recall it taking on Marshmallow but it did eventually flash for me.
Sent from my Nexus 5X using Tapatalk
It's confirmed, need updating fastboot to latest version to get it work.
Wuzimu said:
You have to wait longer.
Click to expand...
Click to collapse
Thanks. I figured it out accidentally by leaving the phone connected for a while and saw it booted up and all done with flashing.
Sent from my Nexus 5X using Tapatalk
Hi Y'all,
I just dirty flashed the December update, and then attempted to patch boot.img with magisk and flash that with fastboot, same as I've always been doing on Android 10 without fail. However, this time, it starts to boot, I get ADB, it bootloops twice, then goes back to fastboot with an error saying something to the effect of "no available slots"
I re-patched and it came out with the same md5sum of b1d09aa00e3376f3d4ceba4e97b99eae
I was able to get an adb logcat on both attempted boots, they're too large for any paste service so I threw them on a VPC I have
http://irc.killingkittens.net/logcat1.txt
http://irc.killingkittens.net/logcat2.txt
Magisk Canary, manager version 7.4.1-72edbfc4 (260)
Magisk 20.2-72edbfc4 (20108)
Happy to provide any other info that would help.
Worked fine for me.
I update ota by magisk method and work fine.
http://www.mediafire.com/view/k1r6pzneqwcrp4d/Screenshot_20191203-112633.png/file
phoe zay said:
I update ota by magisk method and work fine.
http://www.mediafire.com/view/k1r6pzneqwcrp4d/Screenshot_20191203-112633.png/file
Click to expand...
Click to collapse
I see that you're on older versions of both Magisk and Manager than I am. Which update channel are you on?
OK, root worked on my wife's P3. Canary 7.4.1-72edbfc4 (260) Manager an 20.2.72-edbfcr (20108) Magisk after flashing patched. Both show up to date. Install was a hyrbrid of flash-all and OTA. Still nobody seams to have found a reason why the flash-all (no -w) fails in fastbootd at product, but if you then switch to recovery while still on and then ADB sideload the OTA all is fine. 29.0.5 platform tools of course.
Works as normal for me.
I always sideload ota and then patch the boot.img from the full download
sliding_billy said:
OK, root worked on my wife's P3. Canary 7.4.1-72edbfc4 (260) Manager an 20.2.72-edbfcr (20108) Magisk after flashing patched. Both show up to date. Install was a hyrbrid of flash-all and OTA. Still nobody seams to have found a reason why the flash-all (no -w) fails in fastbootd at product, but if you then switch to recovery while still on and then ADB sideload the OTA all is fine. 29.0.5 platform tools of course.
Click to expand...
Click to collapse
Are you saying that if I update by having the phone in fastboot mode and running flash-all with -w removed than the phone update fails or gets wiped?
I had that experience last month where my phone was wiped even with -w removed! I would like to avoid getting wiped this time!
swieder711 said:
Are you saying that if I update by having the phone in fastboot mode and running flash-all with -w removed than the phone update fails or gets wiped?
I had that experience last month where my phone was wiped even with -w removed! I would like to avoid getting wiped this time!
Click to expand...
Click to collapse
Thankfully, no. I can't speak for any possible error when doing a flash-all (without -w), but the one that fails with the "sending product FAILED (Write to device failed (Invalid argument))" just shows a press any failure in command prompt and press any key to continue. The phone remains in fastbootd where you can use the volume keys and power to select recovery he use the keys again to select "sideload OTA from ADB" and while it is waiting use the "adb sideload [OTA path/filename].zip" command in commander and it acts as if you used the sideload in the first place changing slots, not erasing any data/settings/apps. I am not 100% sure yet, but I tend to think that the script is now acting differently if used without the -w but started without flashing stock .boot to both slots to unroot and remove any non-stock kernel. I have been doing it that way for 3+ years now on a Pixal, Piixel XL, Pixel 3 and Pixel 3 XL without issue until last month. I wanted to try it one more time this month after messing with my path and such, but I guess I will have to wait until January to try again. The 3 XL is on Havoc, so I can't test that one. My proposed instructions before doing it are 1)disable all modules, 2)reboot to system, 3)go to BL, 4)Flash previous stock .boot to both slots, 5)boot to system, 6)go to BL, 7)flash-all (without -w), 8)cross your fingers.
Can someone give me the md5 of the patched boot.img from this release? Or, upload a working patched file?
The specific error I got was "no valid slot to boot"
I tried flashing each slot manually, same error. I see that happened a year ago and it related to magisk versions: https://forum.xda-developers.com/pixel-3-xl/how-to/how-to-root-pixel-3-xl-magisk-t3856712/page2
I always update via flash-all with -w option removed.
Did the same this time and no issues.
Not sure how to attach the patched boot as it is too large.
Here is the patched md5:
02536812e6b2e09e4707f98d65e7918f magisk_patched.img
I have the same problem with the same version of Magisk as you and the -w flag in flash-all didn't make a difference.
nomisunrider said:
I always update via flash-all with -w option removed.
Did the same this time and no issues.
Not sure how to attach the patched boot as it is too large.
Here is the patched md5:
02536812e6b2e09e4707f98d65e7918f magisk_patched.img
Click to expand...
Click to collapse
Completely different md5 as me when I try either magisk canary or stable! Can you please upload it to something like https://mega.co.nz/ and generate a share link?
DOMF said:
Completely different md5 as me when I try either magisk canary or stable! Can you please upload it to something like https://mega.co.nz/ and generate a share link?
Click to expand...
Click to collapse
Well, crap, I was able to get the same md5sum by flashing Canary-non-debug, but I still get the crash back to the bootloader with the error "no valid slot to boot"
Anyone have any suggestions before I try a full wipe?
I'm rooted in December but my network connectivity took a serious downgrade with it.
I'm having the same problem on Pixel 3, it just can't boot after patching the boot.img :\
sliding_billy said:
Still nobody seams to have found a reason why the flash-all (no -w) fails in fastbootd at product,...
Click to expand...
Click to collapse
I found the reason:
Bad cable -> Solution: try another cable,
bad USB port -> Solution: try another port or computer,
or old SDK version -> download and update.
Definitely one of these.
Anyway, I also have the problem with bootloop after patch.
Worked just fine here flashing full image (-w) and then applying the patched boot.img from Magisk (20108). Not sure what is going on, but make sure you are on the latest binaries 29.0.5 (October 2019)
v12xke said:
Worked just fine here flashing full image (-w) and then applying the patched boot.img from Magisk (20108). Not sure what is going on, but make sure you are on the latest binaries 29.0.5 (October 2019)
Click to expand...
Click to collapse
Ugh I don't wanna wipe, especially without having taken a TiBu backup first (I know, bad me, it's just worked every time flawlessly so far!)
I'm on 29.0.5.1
Code:
~ fastboot --version
fastboot version 29.0.5-1
Installed as /usr/bin/fastboot
but now that you mention it, I've run into an issue with Arch's implementation of android-tools in the past. Will try from my mac tomorrow.
DOMF said:
Ugh I don't wanna wipe, especially without having taken a TiBu backup first (I know, bad me, it's just worked every time flawlessly so far!) I'm on 29.0.5.1
Click to expand...
Click to collapse
You wouldn't need to wipe... just fastboot flash the original (stock) boot.img and then get it sorted once back into System. Best of luck :good:
v12xke said:
You wouldn't need to wipe... just fastboot flash the original (stock) boot.img and then get it sorted once back into System. Best of luck :good:
Click to expand...
Click to collapse
When I got into the bootloop after applying the Magisk modified boot.img, flashing stock boot.img didn't fix it for me. I had to flash-all again to get it to boot.
I have the latest Canary Magisk Manager 7.4.1-72edbfc4(260) installed, but I also tried the stable channel and still had the same problem. I noticed that my phone faile SafetyNet over ctsProfile: false. Could my problems be related to not un-hiding Magisk? And thinking back, I may not have rebooted after disabling my modules before I started flashing.
Hey guys, because there is unfortunately no fully working TWRP yet and lack of magisk patched boot.img for each rom, i decided to make a script to make things easier.
This script is based on the post https://forum.xda-developers.com/showpost.php?p=81277507&postcount=613 from @gpz1100, which is based on thread [GUIDE] How to Root OnePlus 7T without TWRP by @mauronofrio
What does it do?
The script pull the boot image from your actual system and copy it to your PC.
Then you have to copy the boot image back to your device and patch it with Magisk Manager.
To prevent problems and bootloops the script will boot the patched image first, if anything went well the script will flash it subsequently.
Requirements:
unlocked bootloader
ADB/Fastboot installed
latest TWRP from here
Make sure the .bat and twrp image are in your adb/fastboot folder!!
How to use?
Download the .bat file, place it into your ADB/Fastboot directory and start it.
If windows shows a warning, then just click on "more informations" and then "run anyway".
If you trust me, dont trust the internet and check hash sum MD5 after downloading the file with:
Code:
CertUtil -hashfile <filename> MD5
MD5 checksum is: 303f338c32841ac752d24647ec6ede14
If you dont trust me there are several options:
Use the guide from https://forum.xda-developers.com/showpost.php?p=81277507&postcount=613 from @gpz1100 and do it yourself
or use any guide from [GUIDE] How to Root OnePlus 7T without TWRP by @mauronofrio
check the code on github here
If you run into problems/errors:
Be sure the .bat file is located where adb.exe and fastboot.exe is
If you need urgent root, than follow the guide mentioned above
Be patient, i try to fix the problem as soon as possible
Only tested on Oneplus 7T with OxygenOS
Download from: google drive or from github
Credits:
topjohnwu - for Magisk
mauronofrio - for TWRP
gpz1100 - for his guide
Will I still be rooted if I take an OTA update?
---------- Post added at 01:16 PM ---------- Previous post was at 12:57 PM ----------
Also at one point your after trying to pull the boot image from the phone the script says:
## checking for adb devices..
## device still not in custom recovery, retrying...
Yet the phone restarts. The script retries about 4 times then fails. I think at whatever set in the script before that occurs, it needs to fastboot into recovery rather than do a normal restart.
slipnslider said:
Will I still be rooted if I take an OTA update?
---------- Post added at 01:16 PM ---------- Previous post was at 12:57 PM ----------
Also at one point your after trying to pull the boot image from the phone the script says:
## checking for adb devices..
## device still not in custom recovery, retrying...
Yet the phone restarts. The script retries about 4 times then fails. I think at whatever set in the script before that occurs, it needs to fastboot into recovery rather than do a normal restart.
Click to expand...
Click to collapse
no, but you can root again with the tool
slipnslider said:
Will I still be rooted if I take an OTA update?
Click to expand...
Click to collapse
No. After ota you won't have root. But after installation of ota don't reboot and do this:
1. Open magisk manager
2. Install --> install after ota
3. Reboot.
Now you have updated system with root.
slipnslider said:
Will I still be rooted if I take an OTA update?
---------- Post added at 01:16 PM ---------- Previous post was at 12:57 PM ----------
Also at one point your after trying to pull the boot image from the phone the script says:
## checking for adb devices..
## device still not in custom recovery, retrying...
Yet the phone restarts. The script retries about 4 times then fails. I think at whatever set in the script before that occurs, it needs to fastboot into recovery rather than do a normal restart.
Click to expand...
Click to collapse
oh sorry i missed the second question,
the script should boot your phone into twrp recovery, where it get's adb access to pull the boot.img. Do you named the twrp img to TWRP.img?
Yeah it was named TWRP.img but I actually had another problem going on with my device that I believe was causing this. Got it all fixed using that back to root/unbrick Msm.exe tool that someone else posted
Worked flawlessly, got a little bit lost when the prompt about magisk came out then realised that I needed to copy files over, patch on the phone with the Magisk Manager app then copy files over again.
But once that's sorted, it worked with no issues
Noob question but the flash of the modified boot.img would be a clean flash or a flash over the existing one,asking cause I haven't rooted a device and was wondering if this would erase all of my apps and existing settings?
Radicalcokemonkey23 said:
Noob question but the flash of the modified boot.img would be a clean flash or a flash over the existing one,asking cause I haven't rooted a device and was wondering if this would erase all of my apps and existing settings?
Click to expand...
Click to collapse
Flashing boot.img won't wipe your data. But unlocking the bootloader will reset your phone.
Kollachi said:
No. After ota you won't have root. But after installation of ota don't reboot and do this:
1. Open magisk manager
2. Install --> install after ota
3. Reboot.
Now you have updated system with root.
Click to expand...
Click to collapse
I didn't want to update because I would loose root but I'll give your advice a go.
At 71% it says something went wrong.
imakul8 said:
At 71% it says something went wrong.
Click to expand...
Click to collapse
i think ur phone disconnect during the process, maybe try another usb cable or usb port for the process
Kollachi said:
No. After ota you won't have root. But after installation of ota don't reboot and do this:
1. Open magisk manager
2. Install --> install after ota
3. Reboot.
Now you have updated system with root.
Click to expand...
Click to collapse
Yes, just make sure you install into INACTIVE slot after OTA, if you havent rebooted yet.
I believe one problem exists with twrp (possibly depending on the version) ... when the script tries to download the stock image, TWRP wants confirmation for write access. Unless I confirm that, the download doesn't succeed. Once confirmed, the same adb line in the script entered manually then works ...
I bought a phone advertised as factory unlocked. It has no carrier branding. It turns out to be a model HD1907, which in Wikipedia shows as T-Mobile.
I installed the OnePlus USB drivers from the phone.
I used the original cable.
In Developer Options I had set Advanced Reboot on and USB Debugging on. I tried OEM Unlocking on and off just to try.
I am getting a failure at the boot to TWRP step. The fastboot error, which I tried manually as well, is:
FAILED (remote: 'boot is not allowed in Lock State')
On the fastboot screen I do see the message:
DEVICE STATE - locked
Am I going to need to go through a bootloader unlocking process like this?
Noob Bootloader Unlock Guide: Answers to several questions and solutions to problems.
***Warning: I am not responsible for bricked or broken devices, warranties, computers, etc. This is your phone and your free will to follow the below steps and you bare the full burden of any consequences.*** A note for the Moderators: I am...
forum.xda-developers.com
It's a nicely done script, by the way.
I'm sorry but I'm really newbie, so please can you tell me how to activate adb access?
imakul8 said:
At 71% it says something went wrong.
Click to expand...
Click to collapse
I'm stuck in the same problem, I changed the slot but nothing changes...
I've spent about 6 hours trying various things and I'm not sure how to continue.
I did a backup then started upgrading to Android 10. Long story short, I want to go back to 9.
Every time I try to flash-all.bat crosshatch-pq1a.181205.006.a1-factory-99bead33 back, it fails on:
Sending sparse 'vendor_b' 1/2 (262140 KB) FAILED (Error reading sparse file)
fastboot: error: Command failed
It always fails on that line, and only after succeeding on 34 other counts of flashing. I've tried multiple cables. After this, there's a constant stream of fastboot and recovery warnings, and nothing works right until I flash crosshatch-qq2a.200405.005-factory-2d1c5652 back on. I've tried a handful of manual flashing of the vendor file without success.
It seems like something changed in the phone that simply disallows flashing back.
Has anyone successfully done this?
bizaff said:
I've spent about 6 hours trying various things and I'm not sure how to continue.
I did a backup then started upgrading to Android 10. Long story short, I want to go back to 9.
Every time I try to flash-all.bat crosshatch-pq1a.181205.006.a1-factory-99bead33 back, it fails on:
Sending sparse 'vendor_b' 1/2 (262140 KB) FAILED (Error reading sparse file)
fastboot: error: Command failed
It always fails on that line, and only after succeeding on 34 other counts of flashing. I've tried multiple cables. After this, there's a constant stream of fastboot and recovery warnings, and nothing works right until I flash crosshatch-qq2a.200405.005-factory-2d1c5652 back on. I've tried a handful of manual flashing of the vendor file without success.
It seems like something changed in the phone that simply disallows flashing back.
Has anyone successfully done this?
Click to expand...
Click to collapse
I am assuming you are on a device which has an unlocked bootloader? If not, you can't go back.
Eudeferrer said:
I am assuming you are on a device which has an unlocked bootloader? If not, you can't go back.
Click to expand...
Click to collapse
Correct - first thing I did when I got it a couple years ago was unlock it. On the fastboot screen it has always said unlocked as well.
Like I said, I can flash Android 10 on it (which it has right now with Magisk installed via copying boot.img and updating it through the app), but I'd like to go back to the image I had (either 9.0.0 (PQ1A.181205.006, Dec 2018) or 9.0.0 (PQ1A.181205.006.A1, Dec 2018, Docomo) - not sure what the Docomo is).
Android 10 (crosshatch-qq2a.200405.005-factory-2d1c5652) installed from flash-all.bat just fine, but neither of the above 9.0.0 images install - they both fail on the vendor_b and only on the vendor_b.
Thoughts?
bizaff said:
Correct - first thing I did when I got it a couple years ago was unlock it. On the fastboot screen it has always said unlocked as well.
Like I said, I can flash Android 10 on it (which it has right now with Magisk installed via copying boot.img and updating it through the app), but I'd like to go back to the image I had (either 9.0.0 (PQ1A.181205.006, Dec 2018) or 9.0.0 (PQ1A.181205.006.A1, Dec 2018, Docomo) - not sure what the Docomo is).
Android 10 (crosshatch-qq2a.200405.005-factory-2d1c5652) installed from flash-all.bat just fine, but neither of the above 9.0.0 images install - they both fail on the vendor_b and only on the vendor_b.
Thoughts?
Click to expand...
Click to collapse
I'm not an expert by any means but my thoughts on this would be: perhaps some file needed is not properly extracted to the right folder. I like to extract everything to the same file and then run the commands I'm using. Don't know how necessary this is but it works for me. Also, perhaps try the commands with a .\ in front of it. For some reason, it doesn't work for me unless I do this.
Have you tried fastboot erase userdata just for giggles? I've gone back to 9 before. I always extract the contents of the factory zip to the fastboot folder directly then just run the flash-all.bat are you using the latest fastboot tools?
Check what slot it is on and switch slots.
Eudeferrer said:
I'm not an expert by any means but my thoughts on this would be: perhaps some file needed is not properly extracted to the right folder.
Click to expand...
Click to collapse
This kinda sorta seems like it might be something wrong? It always fails on the same file. If I recall correctly, I downloaded the archive again and it still failed on the same file..
Eudeferrer said:
I like to extract everything to the same file and then run the commands I'm using. Don't know how necessary this is but it works for me. Also, perhaps try the commands with a .\ in front of it. For some reason, it doesn't work for me unless I do this.
Click to expand...
Click to collapse
I don't think it's that, it's finding and executing everything.
Maybe I could try this on Linux? I don't know, I'm kind of at a loss.
UmbrellaTakedown said:
Have you tried fastboot erase userdata just for giggles? I've gone back to 9 before. I always extract the contents of the factory zip to the fastboot folder directly then just run the flash-all.bat are you using the latest fastboot tools?
Click to expand...
Click to collapse
I haven't tried that, but it's most definitely vendor_b. I wonder if I should erase that partition and see if that works.. but I'm still stumped why updating to 10 works.. just checked the archive and there is a vendor.img in the 10 image.
Yep, that's how I run it too.
I downloaded the "latest", which gave me platform-tools_r30.0.0-windows. I also went back and downloaded 27, 28, and 29, and tried a few of those - no dice.
wangdaning said:
Check what slot it is on and switch slots.
Click to expand...
Click to collapse
I guess that's one thing I didn't try.. is there a decent guide somewhere to select the slot to program, boot, and install Magisk to? I had found something about querying which slot was active, but not about selecting..
Hopefully I can update to the final 9.0 version then not worry about it till I switch to 10..
fastboot -help will tell you the command to select, something like fastboot --set-active=a/b. The bootloader screen should tell you which is active. Once you change active slot use fastboot reboot bootloader and run the flash-all of the factory image you want.