I read a comment in one of the 2 XL thread where someone always flashed the Google factory image on their device, but fastbooted the Verizon radio and modem images from the VZE factory image.
So I pulled the VZW radio.img and modem.img and when I flashed the radio I got an error saying something like -maximum space req not specified/given-
here are the steps I followed:
d/l Nov VZW factory image
copied the radio.img and modem.img to my fastboot folder
connected device to PC and verified fastboot devices (my device serial number came up)
ran fastboot flash radio radio-vzw radio file name.img
fastboot found the right file, then error stated maximum space required not specified
failed.
attempted again, ensuring proper filename, spacing, all were correct.. same error...
Any ideas what would cause a simple radio.img flash to fail?
Once I get home, I'll try again, and I'll have be sure to capture the exact error message this time
My current device environment:
Google unlocked 2XL
Nov Google factory image
Magisk patched_boot.img flashed via fastboot
Flash Taimen kernel 1.01 flashed via fastboot
busybox installed 1.27.2 installed (latest Stericson via Play)
Adaway installed
TWRP never installed
TIA
Az Biker said:
I read a comment in one of the 2 XL thread where someone always flashed the Google factory image on their device, but fastbooted the Verizon radio and modem images from the VZE factory image.
So I pulled the VZW radio.img and modem.img and when I flashed the radio I got an error saying something like -maximum space req not specified/given-
here are the steps I followed:
d/l Nov VZW factory image
copied the radio.img and modem.img to my fastboot folder
connected device to PC and verified fastboot devices (my device serial number came up)
ran fastboot flash radio radio-vzw radio file name.img
fastboot found the right file, then error stated maximum space required not specified
failed.
attempted again, ensuring proper filename, spacing, all were correct.. same error...
Any ideas what would cause a simple radio.img flash to fail?
Once I get home, I'll try again, and I'll have be sure to capture the exact error message this time
My current device environment:
Google unlocked 2XL
Nov Google factory image
Magisk patched_boot.img flashed via fastboot
Flash Taimen kernel 1.01 flashed via fastboot
busybox installed 1.27.2 installed (latest Stericson via Play)
Adaway installed
TWRP never installed
TIA
Click to expand...
Click to collapse
So you did fastboot flash modem modem.img?
And fastboot flash radio radio.img?
Both gave the same error?
Sent from my Pixel 2 XL using Tapatalk
bryantjopplin said:
So you did fastboot flash modem modem.img?
And fastboot flash radio radio.img?
Both gave the same error?
Sent from my Pixel 2 XL using Tapatalk
Click to expand...
Click to collapse
I did fastboot flash radio radio-filename.img ... two times and received the same error
I did not try the modem.img as I wasn;'t sure if flashing only the VZW modem, and not the VZW radio would cause any issues.
Thanks for the quick reply!
Az Biker said:
I did fastboot flash radio radio-filename.img ... two times and received the same error
I did not try the modem.img as I wasn;'t sure if flashing only the VZW modem, and not the VZW radio would cause any issues.
Thanks for the quick reply!
Click to expand...
Click to collapse
It should not. The modem is most likely the same.
Sent from my Pixel 2 XL using Tapatalk
bryantjopplin said:
It should not. The modem is most likely the same.
Sent from my Pixel 2 XL using Tapatalk
Click to expand...
Click to collapse
I kinda thought that as the radio file had a recent date, and the modem a 2009 date.
I'll try again this afternoon and get the exact error message if it comes up.
Any idea, regardless of the error message, why a simply radio flash wouldn't take?
Patched_boot.img from Magisk?
I've been fastbooting radios, bootloaders regularly on my 6P for nearly 2 years, so I'm not new to fastboot.
Az Biker said:
I kinda thought that as the radio file had a recent date, and the modem a 2009 date.
I'll try again this afternoon and get the exact error message if it comes up.
Any idea, regardless of the error message, why a simply radio flash wouldn't take?
Patched_boot.img from Magisk?
I've been fastbooting radios, bootloaders regularly on my 6P for nearly 2 years, so I'm not new to fastboot.
Click to expand...
Click to collapse
Assuming you have the newest fastboot and drivers correct? Maybe check and see in device manager
Sent from my Pixel 2 XL using Tapatalk
Do you have current fastboot/adb files?
Did you unlock critical when you unlocked?
bryantjopplin said:
Assuming you have the newest fastboot and drivers correct? Maybe check and see in device manager
Sent from my Pixel 2 XL using Tapatalk
Click to expand...
Click to collapse
arcanexvi said:
Do you have current fastboot/adb files?
Did you unlock critical when you unlocked?
Click to expand...
Click to collapse
I uninstalled all my old SDK tools from my pc first,then rebooted the pc
Downloaded/installed latest from SDK tools last week when I updated to Nov factory image and flash kernel.
Originally only ran unlock, then prior to flashing Nov update I did critical_unlock
Az Biker said:
I uninstalled all my old SDK tools from my pc first,then rebooted the pc
Downloaded/installed latest from SDK tools last week when I updated to Nov factory image and flash kernel.
Originally only ran unlock, then prior to flashing Nov update I did critical_unlock
Click to expand...
Click to collapse
Maybe flash a smaller partition and see if it works.
Sent from my Pixel 2 XL using Tapatalk
bryantjopplin said:
Maybe flash a smaller partition and see if it works.
Sent from my Pixel 2 XL using Tapatalk
Click to expand...
Click to collapse
Haven't flashed 'partitions' before other than in TWRP on the 6P selecting boot, vendor, etc...
I know there is a 1 and 2 partition with the 2 XL, but haven't mess with them at all.
Is there a 'how to' or instructions on choosing partitions for this device?
Az Biker said:
Haven't flashed 'partitions' before other than in TWRP on the 6P selecting boot, vendor, etc...
I know there is a 1 and 2 partition with the 2 XL, but haven't mess with them at all.
Is there a 'how to' or instructions on choosing partitions for this device?
Click to expand...
Click to collapse
Not slot. I meant img. Which is basically different partitions. Try flashing dtbo or another smaller one.
Sent from my Pixel 2 XL using Tapatalk
bryantjopplin said:
Not slot. I meant img. Which is basically different partitions. Try flashing dtbo or another smaller one.
Sent from my Pixel 2 XL using Tapatalk
Click to expand...
Click to collapse
Oh okay, got it. I'll try that too tonight.
try a usb 2.0 port and perhaps a different cable, or even plug the usb-c portion of the cable in the "other way" (rotate)
you may also want to try a full flash, i made a tool: https://forum.xda-developers.com/pi...ol-deuces-bootloop-recovery-flashing-t3704761
So I tried a different cable, not sure if it's USB 2 or 3, but radio flashed first try!
I'd totally get it, if "fastboot devices" turned up nothing, yeah, try a new cable. But when fastboot devices sees your device, how can it not flash a file?
Looks like I'll be using this cable from here on out
Thanks for the input and help everyone!
Az Biker said:
So I tried a different cable, not sure if it's USB 2 or 3, but radio flashed first try!
I'd totally get it, if "fastboot devices" turned up nothing, yeah, try a new cable. But when fastboot devices sees your device, how can it not flash a file?
Looks like I'll be using this cable from here on out [emoji14]
Thanks for the input and help everyone!
Click to expand...
Click to collapse
Imo the aylee cables on Amazon are top quality and with great.
Sent from my Pixel 2 XL using Tapatalk
Is there a list if radios for pixel 2xl that can be fast boot flashed? TIA
wooddale said:
Is there a list if radios for pixel 2xl that can be fast boot flashed? TIA
Click to expand...
Click to collapse
Not that I've seen. You'll likely have to extract them from the factory images.
Related
Encountered this error message when trying to manually flash the N Dev 3 image, not via the flash-all bat. I'm very familiar when it comes to flashing images on my devices, fwiw.
I tried rebooting my PC, redownloading the image, and updating SDK Tools. No luck.
I've been able to reflash to mtc19t successfully.
My goal was to upgrade to the N Dev 3, then flash the decrypted modified N boot.img from Tigerstown in order to root.
Your fastboot is out of date or you have a bad download.
Sent from my SM-G930V using Tapatalk
Thanks. I'll give this a shot [TOOL]Minimal ADB and Fastboot [4-27-16]:
http://forum.xda-developers.com/showthread.php?t=2317790
bostonirishguy13 said:
Encountered this error message when trying to manually flash the N Dev 3 image, not via the flash-all bat. I'm very familiar when it comes to flashing images on my devices, fwiw.
I tried rebooting my PC, redownloading the image, and updating SDK Tools. No luck.
I've been able to reflash to mtc19t successfully.
My goal was to upgrade to the N Dev 3, then flash the decrypted modified N boot.img from Tigerstown in order to root.
Click to expand...
Click to collapse
You don't need to decrypt or flash a modified boot.img in order to root.
bobby janow said:
You don't need to decrypt or flash a modified boot.img in order to root.
Click to expand...
Click to collapse
Should have mentioned I'd prefer TWRP, too.
I ended up not using the unencrypted boot.img and rooted with CF Autoroot.
had same issue use fastboot from latest sdk
Has anyone who has unlocked their bootloader successfully flashed a different factory image other than the image on their phone. I've tried numerous ways and have had no success after unlocking my bootloader. Thanks to anyone who may chime in
Sent from my Pixel XL using XDA-Developers mobile app
treIII said:
Has anyone who has unlocked their bootloader successfully flashed a different factory image other than the image on their phone. I've tried numerous ways and have had no success after unlocking my bootloader. Thanks to anyone who may chime in
Sent from my Pixel XL using XDA-Developers mobile app
Click to expand...
Click to collapse
Could you be more specific about how you flashed (flash_all or each individual image file), and what happened? Error or what?
cam30era said:
Could you be more specific about how you flashed (flash_all or each individual image file), and what happened? Error or what?
Click to expand...
Click to collapse
I've tried flashing the entire P factory image and it fails. I've tried with adb and fast boot on my PC. I also tried with skipsoft toolkit to see if that would work. It also fails. I have posted screen shots in that thread if you'd like to see the error. Thanks
treIII said:
I've tried flashing the entire P factory image and it fails. I've tried with adb and fast boot on my PC. I also tried with skipsoft toolkit to see if that would work. It also fails. I have posted screen shots in that thread if you'd like to see the error. Thanks
Click to expand...
Click to collapse
I'd suggest fastboot flash each image file separately (boot, sys, etc)
cam30era said:
I'd suggest fastboot flash each image file separately (boot, sys, etc)
Click to expand...
Click to collapse
I tried that and it seems to work but nothing changes
treIII said:
I tried that and it seems to work but nothing changes
Click to expand...
Click to collapse
What is it that you are expecting to change?
cam30era said:
What is it that you are expecting to change?
Click to expand...
Click to collapse
The build number and for OEM unlocking to be pickable. My bootloader is already unlocked so I thought flashing a different factory image would make it possible in developer options
treIII said:
The build number and for OEM unlocking to be pickable. My bootloader is already unlocked so I thought flashing a different factory image would make it possible in developer options
Click to expand...
Click to collapse
I agree. That's very strange. Does fastboot indicate success after flashing each image?
cam30era said:
I agree. That's very strange. Does fastboot indicate success after flashing each image?
Click to expand...
Click to collapse
Yes for some but the system image fails. Look in skipsoft tool thread and you'll see it. There are pictures
treIII said:
Yes for some but the system image fails. Look in skipsoft tool thread and you'll see it. There are pictures
Click to expand...
Click to collapse
If you don't use skipsoft, and in fastboot do:
fastboot flash system system.img
You still get this partition error?
cam30era said:
If you don't use skipsoft, and in fastboot do:
fastboot flash system system.img
You still get this partition error?
Click to expand...
Click to collapse
Yes
treIII said:
Yes
Click to expand...
Click to collapse
Very strange. I'm at a loss.
cam30era said:
Very strange. I'm at a loss.
Click to expand...
Click to collapse
So u have Verizon version? I'd like to see someone else try to flash a factory image to know where this goes
treIII said:
So u have Verizon version? I'd like to see someone else try to flash a factory image to know where this goes
Click to expand...
Click to collapse
No. Considering buying one. That's why I'm interested in this.
cam30era said:
No. Considering buying one. That's why I'm interested in this.
Click to expand...
Click to collapse
Yeah I wish someone else would chime in and try. I can't figure it out after trying for 4 hours last night and about two today. So I gave up and posted
I flashed the google factory image. . oem unlock will stay greyed out but that is not a big deal. bunch of people did this and discussion in this other thread. http://forum.xda-developers.com/pixel-xl/how-to/verizon-pixel-xl-unlocking-discussions-t3484497
zanoli99 said:
I flashed the google factory image. . oem unlock will stay greyed out but that is not a big deal. bunch of people did this and discussion in this other thread. http://forum.xda-developers.com/pixel-xl/how-to/verizon-pixel-xl-unlocking-discussions-t3484497
Click to expand...
Click to collapse
Not until you want to update to newer firmwares and there is no unlock method on those bootloaders. Converting to a GPS Pixel would be ideal if it is even possible.
joderme said:
Not until you want to update to newer firmwares and there is no unlock method on those bootloaders. Converting to a GPS Pixel would be ideal if it is even possible.
Click to expand...
Click to collapse
If you unlock now and update later your bootloader will remained locked unless Google finds a way to push a bootloader update with the coming OTA's that locks your bootloader after unlocking but that's highly unlikely. Plus, if you jump the gun and install the OTA before knowing the results of the OTA, you're kind of asking for something like this to happen. Hopefully Google doesn't find a deceitful way of pushing bootloader updates to lock us back up as you know they have already learned that a backdoor was found to unlock the Verizon bootloaders. They're not stupid and Jcase already said the sunshine guys were sending the exploit to Google so they would patch it. Vulnerabilities are too common these days on Android and these exploit seekers are quick to submit patches for them.
OK. Finally was able to flash the latest pixel factory image on my PXL. Minimal and fastboot and latest drivers from Google.
i sorta need help in this department as well... do i unzip the zip inside the zip??
im getting missing recovery.img and missing boot.sig i would like to make this a non verizon device. the flash-all.bat didnt work and i tried modifying it by removing -w but still same errors. spoon feed me please or teamview? its been 2 days
Here is what I did when I get my Pixel 2 XL out of the box today.
1. Followed the instructions at androidcentral.com/ how-root-google-pixel-2 and got a corrupt message after rebooting at the end. Only options were to try booting again or factory reset.
2. Figured that since I had 8.0.0 on the device and I used the latest 8.1.0 boot image, that was causing the problem. So I thought if I flashed 8.1.0, all would be good and I could start over.
3. Received several file not found errors when flashing. And my situation did not improve.
4. Can I just flash the original factory image and start over? Or am I totally screwed?
Thanks for any insight.
If you can boot into the bootloader you're most likely ok. Just download https://developers.google.com/android/images the image from google.
mikepopo99 said:
If you can boot into the bootloader you're most likely ok. Just download https://developers.google.com/android/images the image from google.
Click to expand...
Click to collapse
I can boot into the bootloader. My Internet connection has been a bit buggy, maybe the image was corrupted? Will try flashing a different image once it finally downloads.
Droid7of9 said:
I can boot into the bootloader. My Internet connection has been a bit buggy, maybe the image was corrupted? Will try flashing a different image once it finally downloads.
Click to expand...
Click to collapse
Here is the guide that many of us have used. Made by the legend himself :good:
https://forum.xda-developers.com/pixel-2-xl/how-to/guide-unlock-flash-root-pixel-2-xl-t3702418
Make sure your adb and fastboot files on the computer are up to date I had to do this on a Windows machine when I had similar results
Sent from my Pixel 2 XL using Tapatalk
gjkrisa said:
Make sure your adb and fastboot files on the computer are up to date I had to do this on a Windows machine when I had similar results
Sent from my Pixel 2 XL using Tapatalk
Click to expand...
Click to collapse
Thanks to all! Got it up and running again, maybe it was old fastboot/adb version. Might try and root again tomorrow. Will use that guide that was posted.
And now I am rooted, thanks again for the help. It must have been not having the latest adb/fastboot. Lesson learned.
Could somebody provide full untouched fastboot firmware with build number NPPS25.137-93-14 for DualSIM Moto G5 (XT1676) with reteu software channel and 3GB RAM/16GB ROM, please? Thanks in advance.
https://forum.xda-developers.com/g5/development/official-stock-moto-g5-cedric-firmware-t3733897
I have been looking for it during several weeks too, no success until now. I found 137-92-14, which is built for other software channels. It works well in my XT1685 (Dual sim 3GB/32GB reteu).
Still looking for 137-93-14... Regards.
Doesn't XT1685 equal G5 Plus?
Andrej_SK said:
Doesn't XT1685 equal G5 Plus?
Click to expand...
Click to collapse
Yes.
Enviado desde mi Moto G (5) Plus mediante Tapatalk
Andrej_SK said:
Could somebody provide full untouched fastboot firmware with build number NPPS25.137-93-14 for DualSIM Moto G5 (XT1676) with reteu software channel and 3GB RAM/16GB ROM, please? Thanks in advance.
Click to expand...
Click to collapse
How can I provide you with fastboot firmware as I am having same build version with untouched fastboot firmware.but I am having xt1677 with same specs.
I'm also looking for NPPS25.137-93-14 (or NPPS25.137-93-12)... I only need the stock recovery.img file of either of the two...
Ok I will update recovery for you. Which varient it is if amzin one link will be uploaded at evening. Just let me know. Waiting for reply?
Aaric leo's el drigo said:
Ok I will update recovery for you. Which varient it is if amzin one link will be uploaded at evening. Just let me know. Waiting for reply?
Click to expand...
Click to collapse
Mine is retail. Either *-12 or * -14 recovery.img will be ok.
Thanks.
Sent from my Moto G5 using XDA Labs
Ok I will upload it. As fast as possible
---------- Post added at 04:38 AM ---------- Previous post was at 03:42 AM ----------
Because I can't fine firmware online to download, or I don't have retail varient so I can't help you. But if you have laptop, pc. I can help let you know how you can download firmware. Let me know if you need guide as fast as possible.
leohussey said:
I'm also looking for NPPS25.137-93-14 (or NPPS25.137-93-12)... I only need the stock recovery.img file of either of the two...
Click to expand...
Click to collapse
You can flash older recovery without bricking the phone. However, don't do that if you are running CustomROM. In my case, when I wanted to revert to fully updated stock, I flashed NPPS25.137-93-8 firmware without gpt, bootloader (that's what would brick the phone if flashed) and erase modem commands, updated it to NPPS25.137-93-12, then to NPPS25.137-93-14 using stock recovery and these files https://drive.google.com/drive/folders/1BkpfHvgQ477NViLYvzgv88Fgq3SSt5Py. No issues at all and my phone (XT1676, 3/16, DualSIM, reteu) is still working fine.
In the attachment, I'll put recovery.zip (with recovery.img inside of it) of the NPPS25.137-93-8. Use at your own risk, if you are interested.
Andrej_SK said:
You can flash older recovery without bricking the phone. However, don't do that if you are running CustomROM. In my case, when I wanted to revert to fully updated stock, I flashed NPPS25.137-93-8 firmware without gpt, bootloader (that's what would brick the phone if flashed) and erase modem commands, updated it to NPPS25.137-93-12, then to NPPS25.137-93-14 using stock recovery and these files https://drive.google.com/drive/folders/1BkpfHvgQ477NViLYvzgv88Fgq3SSt5Py. No issues at all and my phone (XT1676, 3/16, DualSIM, reteu) is still working fine.
In the attachment, I'll put recovery.zip (with recovery.img inside of it) of the NPPS25.137-93-8. Use at your own risk, if you are interested.
Click to expand...
Click to collapse
Thanks.
But thing is: I'm currently on NPPS25.137-93-12 with TWRP and Magisk. As a proof of concept I want to go to *-14 via OTA to see if it is possible... And if so: to make the oreo jump when available for my channel (XT1671, 2 sim, retla). I want to avoid losing all my data or any long task that would keep me offline for a long time... Daily driver both work and personal...
Uninstalling Magisk reverts boot.img to stock.... but I still need the stock recovery.img to be in 100% stock state (but unlocked). That's the theory.
Tried yesterday using other recovery.img versions, but failed: /cache/recovery/last_log shows the Blur* OTA file updater-script explicitly checks recovery version to be either source or destination versions... So *-12 or *-14.
After that, updater-script checks boot, system and oem. Those are (will be, supposedly) stock since Magisk only patches boot.img and I'll uninstall it .... should work...
The longer path of flashing other version and do the OTAs is also possible... But I'd have to be on vacation or something...
Thanks again.
Sent from my Moto G5 using XDA Labs
leohussey said:
Thanks.
But thing is: I'm currently on NPPS25.137-93-12 with TWRP and Magisk. As a proof of concept I want to go to *-14 via OTA to see if it is possible... And if so: to make the oreo jump when available for my channel (XT1671, 2 sim, retla). I want to avoid losing all my data or any long task that would keep me offline for a long time... Daily driver both work and personal...
Uninstalling Magisk reverts boot.img to stock.... but I still need the stock recovery.img to be in 100% stock state (but unlocked). That's the theory.
Tried yesterday using other recovery.img versions, but failed: /cache/recovery/last_log shows the Blur* OTA file updater-script explicitly checks recovery version to be either source or destination versions... So *-12 or *-14.
After that, updater-script checks boot, system and oem. Those are (will be, supposedly) stock since Magisk only patches boot.img and I'll uninstall it .... should work...
The longer path of flashing other version and do the OTAs is also possible... But I'd have to be on vacation or something...
Thanks again.
Sent from my Moto G5 using XDA Labs
Click to expand...
Click to collapse
Try one more time with file in the attachment of this reply. Although you will get "Image signed with key bad key" (because it's simply extracted from NPPS25.137-93-14), it should flash just fine. In my case, I've tried to flash it with fully updated phone to NPPS25.137-93-14, no issues at all. However, you should be more careful if you are running .12 firmware - this is stock and newer recovery (recovery of .14 firmware). .
Okay, so there are already 2 files in the attachment, first one contains recovery.img of .12 firmware, second one of the .14 firmware. You can recognize them by name of the file. With each of them, you will still get "Image signed with key bad key" message when flashing, but they flash just fine and everything seems to be working flawlessly on my phone with coresponding firmware version (means .12 recovery for .12 firmware, .14 recovery for .14 firmware). Once again, you are doing it at your own risk if you decide to.
Andrej_SK said:
Try one more time with file in the attachment of this reply. Although you will get "Image signed with key bad key" (because it's simply extracted from NPPS25.137-93-14), it should flash just fine. In my case, I've tried to flash it with fully updated phone to NPPS25.137-93-14, no issues at all. However, you should be more careful if you are running .12 firmware - this is stock and newer recovery (recovery of .14 firmware). Once again, you are doing it at your own risk.
Click to expand...
Click to collapse
Thanks. I'll test tonight.
"Bad key" is no problem... Got it twice already by testing with other versions I was able to get.
As for it being from *-14, it should work if I believe the updater script checking for either *-12 recovery (source) or *-14 recovery (target)... We'll see.
Sent from my Moto G5 using XDA Labs
---------- Post added at 06:31 PM ---------- Previous post was at 06:28 PM ----------
Andrej_SK said:
Try one more time with file in the attachment of this reply. Although you will get "Image signed with key bad key" (because it's simply extracted from NPPS25.137-93-14), it should flash just fine. In my case, I've tried to flash it with fully updated phone to NPPS25.137-93-14, no issues at all. However, you should be more careful if you are running .12 firmware - this is stock and newer recovery (recovery of .14 firmware). .
Okay, so there are already 2 files in the attachment, first one contains recovery.img of .12 firmware, second one of the .14 firmware. You can recognize them by name of the file. With each of them, you will still get "Image signed with key bad key" message when flashing, but they flash just fine and everything seems to be working flawlessly on my phone with coresponding firmware version (means .12 recovery for .12 firmware, .14 recovery for .14 firmware). Once again, you are doing it at your own risk if you decide to.
Click to expand...
Click to collapse
Hm... By the time I quoted to answer, you updated. Cool.
Then I'll test directly on 12. Thanks.
Another question: are you extracting them from your own phone? If so, how? Untill now I only found possible by rooting, but rooting means changing recovery in first place... So... Hen and egg...
Sent from my Moto G5 using XDA Labs
leohussey said:
Another question: are you extracting them from your own phone? If so, how? Untill now I only found possible by rooting, but rooting means changing recovery in first place... So... Hen and egg...
Sent from my Moto G5 using XDA Labs
Click to expand...
Click to collapse
Yes, I rooted my phone by Magisk and used app called Flashify to backup recovery. However, to root, I didn't install TWRP permanently by "fastboot flash recovery twrp.img" command, I just booted into it by "fastboot boot twrp.img", so I was able to root my phone and keep stock recovery installed.
Andrej_SK said:
Yes, I rooted my phone by Magisk and used app called Flashify to backup recovery. However, to root, I didn't install TWRP permanently by "fastboot flash recovery twrp.img" command, I just booted into it by "fastboot boot twrp.img", so I was able to root my phone and keep stock recovery installed.
Click to expand...
Click to collapse
Thanks. I had been reading about it and some posts were misleading saying it was no longer possible and others said it was. Had not gotten down to test it yet. So now I know it works, I'll do it. Thanks again.
Sent from my Moto G5 using XDA Labs
Update: tested.
good: Recovery image -12 worked without issue and updater-script check passed.
bad: it failed while validating boot.img.
Apparently, Magisk uninstall did not restore the boot partition to stock. I also had a TWRP backup from when I had just unlocked. Restored boot. No luck. Maybe I took the backup *after* rooting.
well... I guess I will have to wait until I have some free time to do the long way: full flash
EDIT: @Andrej_SK: would you by any chance have the boot.img of *-12 too?
thanks!!
I am reading this tread form more then 2 days. I already told you I can help but it seems no one want know what I am saying. But it's now seem a serious tread so I will tell in anyway if someone is interested or not.
Guide to repair Moto Lenovo models.
Note: pc, laptop required.
1. Download latest driver for moto device.
2. Download Lenovo Moto smart assistant.
3. Enable usb debugging in developer options.
4. Click on Flash button on top of your tab bar.
5. Click on rescue.
6. Get into bootloader , fastboot.
7. Download your current varient latest firmware.
And all done.
Now you have your firmware with latest security patch.
You can relock bootloader and whatever you like.
Have fun enjoy.
Thanks a lot. This tool won't work if you have lost your IMEI, but it allows you to download the latest firmware (in my case 137-93-14). Using this full stock firmware I have been able to recover the IMEI following the steps explained in other topic in this forum.
Regards.
leohussey said:
EDIT: @Andrej_SK: would you by any chance have the boot.img of *-12 too?
Click to expand...
Click to collapse
I might give it a try, if you give me some time.
Coming from Havoc Is, and wanted to try beta 5 so I used fastboot method to flash latest stock image so I would receive beta 5 OTA. In fastboot I did flash-all and it started to do its thing but after a while fastboot said no boot and no recovery image in the file. After a minute or two, it continued to flash the rest. After everything was done, my phone was in bootloop so I formated data with twrp and the phone booted up but it was still on Havoc Os. Can anyone help me with this problem please
Try using this tool.
https://forum.xda-developers.com/pixel-2-xl/development/tool-deuces-bootloop-recovery-flashing-t3704761
Make sure you put the files on your primary hard-drive to avoid errors.
MaleSamus said:
Try using this tool.
https://forum.xda-developers.com/pixel-2-xl/development/tool-deuces-bootloop-recovery-flashing-t3704761
Make sure you put the files on your primary hard-drive to avoid errors.
Click to expand...
Click to collapse
Thanks will give it a try
MaleSamus said:
Try using this tool.
https://forum.xda-developers.com/pixel-2-xl/development/tool-deuces-bootloop-recovery-flashing-t3704761
Make sure you put the files on your primary hard-drive to avoid errors.
Click to expand...
Click to collapse
Works great except that I've relock the bootloader and when the phone starts it says that the phone is not running the stock image andwhen I try to install beta 5, it's giving me an error when installing.
Just to confirm, you are using image from here to go back to stock and not the OTA image?
https://developers.google.com/android/images
Once you've flashed with this image, you should then be able to sideload the beta using the beta OTA image from here:
https://developer.android.com/preview/download-ota.html
coco1476 said:
Works great except that I've relock the bootloader and when the phone starts it says that the phone is not running the stock image andwhen I try to install beta 5, it's giving me an error when installing.
Click to expand...
Click to collapse
I'm not picking on you, but this needs to be said again and again. Everyone Stop Locking Your BootLoaders!! NOW!!
People are destroying their phones at record pace lately and it's all completely unnecessary. There are literally a dozen thread recently that all end the same way. A bricked phone and another warning about the danger of relocking the bootloader.
Sent from my Pixel 2 XL using XDA Labs
CyberpodS2 said:
I'm not picking on you, but this needs to be said again and again. Everyone Stop Locking Your BootLoaders!! NOW!!
People are destroying their phones at record pace lately and it's all completely unnecessary. There are literally a dozen thread recently that all end the same way. A bricked phone and another warning about the danger of relocking the bootloader.
Sent from my Pixel 2 XL using XDA Labs
Click to expand...
Click to collapse
Thanks for the info, I just thought it was best to lock the bootloader to get OTA betas instead of sideloading. I'm up and running beta 5 now
MaleSamus said:
Just to confirm, you are using image from here to go back to stock and not the OTA image?
https://developers.google.com/android/images
Once you've flashed with this image, you should then be able to sideload the beta using the beta OTA image from here:
https://developer.android.com/preview/download-ota.html
Click to expand...
Click to collapse
Thanks it's all running good now with your help