I'm from Mexico and like 20 mins ago I got this update. Has anyone got this update? (An OTA update link is in the thread just use the Search bar)
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
alealicks said:
I'm from Mexico and like a 20 min ago got this update. Anyone got the update? (I don't know how to extract the OTA, so don't ask me for that)
Click to expand...
Click to collapse
I'm from Mexico too, I received the OTA today too
---------- Post added at 10:37 PM ---------- Previous post was at 09:52 PM ----------
It seems that this update will also update the bootloader to B1:07(in the September patch Rom, it was B1:06)
Security Patch?
I saw people complaining that the camera does not work well. It is true?
Enviado desde mi Moto G (4) mediante Tapatalk
shadow20012 said:
Security Patch?
Click to expand...
Click to collapse
Yes
RenePaul99 said:
I'm from Mexico too, I received the OTA today too
---------- Post added at 10:37 PM ---------- Previous post was at 09:52 PM ----------
It seems that this update will also update the bootloader to B1:07(in the September patch Rom, it was B1:06)
Click to expand...
Click to collapse
Thanks, that's useful to know, looks like updating to the December 2017 security patch may mean the latest blankflash we have could no longer work for rescuing bricked devices in the future. Until we get a new blankflash possibly.
OTA Captured: https://mega.nz/#!VdcCTZpZ!i4RP94md7le4l5tOlT_88ywmFzxtP9GZISxnLIiyzw4
Sorry for Mega
Thanks! Now some of the wizards might "cook" a full install so we all can update our unlocked/rooted devices.
Blur_Version.25.221.10.athene.retail.en.US.zip
Download
Some observations about this patch:
a)36.2 MB in size, carrying the December 2017 security patch as noted above with a final build of NPJS25.93-14-13/3. md5: 28d24a02c7e7caecf4be102a6059074f Though it's the 1st December 2017 update, I'm not sure if this update has the KRACK patches built in (as they were covered by the 6th November 2017 patch) - depends on when Motorola got the patch. Apologies for misleading anyone.
b)From the updater script, requires NPJS25.93-14-10 already on your device to flash.
Code:
Package expects build thumbprint of 7.0/NPJS25.93-14-13/3:user/release-keys or 7.0/NPJS25.93-14-10/10:user/release-keys
c)Looks to be carrying updates for some apps/services, such as BellTVWidget and OmegaPttMX.
d)As helpfully noted by RenePaul99, updates the bootloader to B1:07 (with a build date of 2017-11-07) from B1:06 in NPJS25.93-14-10. This may result in the blankflash we have at https://forum.xda-developers.com/moto-g4-plus/how-to/moto-g4-plus-hardbrick-solved-guide-t3657761 failing to work if this OTA update is applied - it may check and only work on B1:06 and earlier bootloaders (and no, generally you can't downgrade bootloaders) I'm not certain of this, though I dislike seeing devices bricked and the only resolution being an expensive motherboard replacement. So crucially, if you've updated your device to this OTA update, be very careful if you decide to flash older Motorola stock ROMs (e.g. after flashing a custom ROM), as an OTA update could hard brick your device, and the current blankflash may not work in rescuing your device. The safest way to revert, if you updated to this stock patch level, would be to use your TWRP backup or wait for the NPJS25.93-14-13 fastboot ROM to be 'obtained' (leaked) from Motorola.
EDIT - 17/01/2018 - I've seen one possible rescue with the latest blankflash we have from a user updated to the December 2017 B1:07 bootloader. Though it suggests the blankflash is still working, be very careful regardless.
As generally with OTA updates, they only will flash successfully onto a device with a clean stock system, stock recovery and stock kernel. Unlocked bootloader status doesn't appear to matter.
Of course, if you're rooted, then the above aren't true; I was running a XT1642 with TWRP, ElementalX and magisk 13.3, so the OTA update is a no-go. One straightforward way to restore my device to a OTA friendly state was to re-flash the NPJS25.93-14-10 stock ROM (which we have here: https://forum.xda-developers.com/moto-g4-plus/how-to/stock-rom-npjs25-93-14-4-march-1-t3608138)
The following flashing commands I used should not affect your data and return your device to an OTA friendly state, but as always back up your data just in case. You may be able to use fewer commands but I prefer to flash all these partitions (you probably want to do things properly with the core firmware running your device!) As far as I know, system, OEM, boot, recovery and logo partitions need to be stock at the very least. GPT/bootloader/modem you could omit if you're sure they are the same patch level as NPJS25.93-14-10 (bootloader should be B1:06 and modem should be ending in 62.01R), if you're not sure, I'd flash them too to ensure all your firmware is of the same patch level. Don't mix and match patch levels when it comes to OTA updates... Oh, and check that you have plenty of time, you don't want to rush firmware flashes.
Code:
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash dsp adspso.bin
fastboot flash oem oem.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
fastboot flash system system.img_sparsechunk.6
fastboot flash system system.img_sparsechunk.7
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot reboot
After manually flashing each command (copy and paste is your friend, though nothing to stop you using a script), my device rebooted to system (complaining of bad key or N/A on the bootloader warning screen, that's normal). Rebooted to stock recovery (with the Android on its back and the no command), then held the power button before pressing and releasing the volume up key, then releasing the power button. Took a few tries before getting into the recovery menu. (as explained here: https://forum.xda-developers.com/moto-g4-plus/help/command-stock-recovery-xt1642-t3484616 )
As before, flashed the OTA update without issue from the SD card/internal storage (though had to mount /system as the recovery complained it couldn't mount internal or external storage, after mounting the 'apply update from SD card' worked and loaded up internal storage...), wiped cache after installation and rebooted.
Now I'm running NPJS25.93-14-13 and still have all my data Not rooted or having TWRP on, but I might see how I get on with this new build. Initial impressions are that it's fast and stable, though early days yet. As for the camera, photos and video with the rear camera appear to work okay with version 6.0.86.7 of the Moto camera app, what problems have been mentioned with the camera?
Working fine here XT1621 just used adb to sideload
that oreo update seems to be vaporware as the time goes on
victor.neyoy said:
that oreo update seems to be vaporware as the time goes on
Click to expand...
Click to collapse
Knowing that Motorola is updating the security patches every 3 months, in the best case will get Oreo by the end of March (the date of the new security patch update).
Still Waiting....
Please anyone has the rom flasheable through adb? i tried to downgrade from npjs25.93-14-13 to npjs25.93-14-10 and now my phone is bricked and i need the rom npjs25.93-14-13 to flash. anyone?? links?
leoh.rod said:
Please anyone has the rom flasheable through adb? i tried to downgrade from npjs25.93-14-13 to npjs25.93-14-10 and now my phone is bricked and i need the rom npjs25.93-14-13 to flash. anyone?? links?
Click to expand...
Click to collapse
What firmware did you try to flash that bricked your device? By bricked do you mean LED blinking and failure to boot?
Currently no NPJS25.93-14-13 firmware available, we have to wait for Motorola to deploy it to their firmware server and hopefully someone can grab the link.
echo92 said:
What firmware did you try to flash that bricked your device? By bricked do you mean LED blinking and failure to boot?
Currently no NPJS25.93-14-13 firmware available, we have to wait for Motorola to deploy it to their firmware server and hopefully someone can grab the link.
Click to expand...
Click to collapse
my phone was on npjs25.93-14-13 and i tried to downgrade to npjs25.93-14-10 and it doesnt boot. its stucked on recovery mode. what should i do now to bring it back?
leoh.rod said:
my phone was on npjs25.93-14-13 and i tried to downgrade to npjs25.93-14-10 and it doesnt boot. its stucked on recovery mode. what should i do now to bring it back?
Click to expand...
Click to collapse
Are there any messages in recovery mode or is it just stuck booting? Have you tried a cache wipe in recovery and reboot, or if you've got your data backed up, try a factory reset (which would wipe your data)?
Was the flash complete, did you see [OKAY] on all the NPJS25.93-14-10 firmware flashing commands? You may have an incomplete flash if not, could try another flash of the September 2017 stock firmware (without flashing GPT/bootloader). Can I ask why you were trying to downgrade your firmware from the 7.0 December patch? Is your bootloader unlocked (should be if you're trying to downgrade)?
Are you able to boot to bootloader (power off your device, then hold down power and volume down, then you should boot into bootloader), and select 'Start' - does that boot your device or result in a bootloop again?
leoh.rod said:
my phone was on npjs25.93-14-13 and i tried to downgrade to npjs25.93-14-10 and it doesnt boot. its stucked on recovery mode. what should i do now to bring it back?
Click to expand...
Click to collapse
Never downgrade when you don't have the full flash available. AFAIK the new bootloaders cannot be downgraded, and it was reported that the 14-13 brings in a new bootloader. Older system don't usually work with the new bootloaders.
As it was said, you might need to wait to get the full 14-13 and stay on that.
Anyone from India got this update?
Related
Wrote down guide how to get STOCK version of Android for XT1572 - Moto X STYLE, and also install TWRP recovery and get root with xposed.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Last UPDATE: 25/02/2017
1. GUIDE TO STOCK
@Prazaar 's provided link with STOCK files.
@lAndroXl guide here (Files also for other versions of device).
@dbolivar guide here for RETLA-DS (Brazil).
Stock 6.0.1 EU here, my mirror here (6.0.1 with security patch from September).
Flash scripts - here, or my script here. (for Windows - flashes STOCK files without re-locking bootloader, but also wipes data)
you need adb/fastboot drivers installed (Good ADB installer for PC can be found here);
you need to backup all your data on your phone, guide will erase everything;
reboot your phone into bootloader mode and plug in your usb cable which is connected to your PC. (power off your device then press the POWER and VOLUME DOWN button for 3-4 seconds);
Open a command prompt in the folder where you unpacked the zip file you downloaded before (press SHIFT + RIGHT CLICK on a empty space then "open command prompt here");
Check the functionality of the adb drivers, simply type "fastboot devices" and you will see a list with your connected devices in bootloader mode.
Type every single command in the command prompt window from the list below. (You can ignore OEM LOCK commands if you not wish to lock down bootloader, but just update device to latest version of Android!);
Code:
fastboot oem lock begin
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
fastboot flash system system.img_sparsechunk.6
fastboot flash system system.img_sparsechunk.7
fastboot flash system system.img_sparsechunk.8
[INDENT](for [B]5.1.1 [/B]there are one more file)
fastboot flash system system.img_sparsechunk.9[/INDENT]
[INDENT](for [B]6.0.1[/B] there are more files)
fastboot flash system system.img_sparsechunk.9
fastboot flash system system.img_sparsechunk.10
fastboot flash system system.img_sparsechunk.11[/INDENT]
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot flash bluetooth BTFM.bin
fastboot erase cache
fastboot erase userdata
fastboot erase customize (optional: will erase any customizations if ordered through motomaker)
fastboot erase clogo (optional: will erase the custom boot logo if ordered through motomaker)
fastboot oem lock
fastboot reboot
2. UNLOCK BOORLOADER.
Remember, that after unlocking bootloader, all device will be WIPED.
Code:
fastboot oem unlock UNIQUE_KEY
3. FLASH TWRP RECOVERY.
twrp-3.0.2-0-clark.img from here.
Code:
fastboot flash recovery twrp-3.0.2-0-clark.img
Note: After flashing TWRP, boot into custom recovery and make restart to recovery again!
4. INSTALL SUPERSU.
Flash 2.62-3 from TWRP from here. (Later from Play Store upgrade to latest version);
OR
Flash latest SuperSU root ZIP from here.
(before flashing this, TWRP-Advanced-Terminal and enter "echo SYSTEMLESS=true>>/data/.supersu" and then flash ZIP file.)
5. INSTALL XPOSED.
Latest v86 from here. (xposed-v86-sdk23-arm64.zip)
OR
Latest unofficial SYSTEMLESS Xposed from here. (You need 2.76+ SYSTEMLESS root, latest MAGISK Iterface from here and Material Design Xposed Installer to work)
6. To make OTA update.
Remove XPOSED (can be turned off from XPOSED app) + UNROOT (can be done from SUPERSU app) + remove MAGISK (use latest unintaller from thread);
Flash STOCK recovery file from FASTBOOT (fastboot flash recovery recovery.img);
Now you can perform OTA update;
Follow all steps from guide (I do - > TWRP, SYSTEMLESS ROOT, MAGISK, XPOSED).
I have a Brazilian xt1572 with marshmallow via OTA. Do you think this method will work for me? I mean, without flashing the 6.0 firmware first?
Enviado de meu XT1572 usando Tapatalk
But if you make TWRP read only, how can you flash SuperSu and Xposed Framework?
Inviato dal mio XT1572 utilizzando Tapatalk
bbb77 said:
But if you make TWRP read only, how can you flash SuperSu and Xposed Framework?
Inviato dal mio XT1572 utilizzando Tapatalk
Click to expand...
Click to collapse
yea, you right, I forgot. will edit.
After checking if my device boot up, I restarted to twrp recovery, and unchecked read only. Thanks!
danielgava said:
I have a Brazilian xt1572 with marshmallow via OTA. Do you think this method will work for me? I mean, without flashing the 6.0 firmware first?
Enviado de meu XT1572 usando Tapatalk
Click to expand...
Click to collapse
Its hard to tell that. After upgrading mine stock 5.1.1 to 6.0 via OTA, I unlocked bootloader, but didnt do device restart and did flash TWRP, after that mine device got bootloop. If you are ready to experiment, you can try, but remember that you will wipe all your data on internal storage. Its strange why now I can boot up my device, I think that restart of device after unlocking bootloader and restart after booting into twrp (read only), could change something.
I'll give it a try later, but for insurance, do you have the link for the Brazilian 6.0 firmware?
Never mind, I've found it: https://mega.nz/#!9ItwmIKb!-73GF5Sk00BpkDeFWIJzcUAp2hOFIZS7ksJ5al0CgiA
Enviado de meu XT1572 usando Tapatalk
danielgava said:
I'll give it a try later, but for insurance, do you have the link for the Brazilian 6.0 firmware?
Never mind, I've found it: https://mega.nz/#!9ItwmIKb!-73GF5Sk00BpkDeFWIJzcUAp2hOFIZS7ksJ5al0CgiA
Enviado de meu XT1572 usando Tapatalk
Click to expand...
Click to collapse
Ok, good luck!
What about Indian XT1572?
Can anyone confirm this for India? Or should I risk being the first one to try it on an Indian XT1572 Dual Sim? Although I'll have to wait for a week. My phone is at the service center currently. It apparently had a manufacturing defect in the audio jack.
Any XT1575 owners doing this with success?
radpp16 said:
Any XT1575 owners doing this with success?
Click to expand...
Click to collapse
XT1575 US here. This worked for me on the second try. I followed the procedure in the OP with the following exceptions. Never unchecked system read only in step 3, and never installed xposed. I used the systemless supersu version referenced in the OP and I'm rooted. Confirmed with a few apps that require root like LMT Pie.
The first time I tried this I fastboot flashed, booted straight into recovery, kept system read only, rebooted to recovery, then rebooted into the ROM before I made any changes. I just wanted to be extra sure everything was ok. When I tried to reboot to recovery I got the "no command" error with the android laying on his back. Rooting, even if it is systemless seems to be necessary before you reboot into the system to make TWRP stick.
jason2678 said:
XT1575 US here. This worked for me on the second try. I followed the procedure in the OP with the following exceptions. Never unchecked system read only in step 3, and never installed xposed. I used the systemless supersu version referenced in the OP and I'm rooted. Confirmed with a few apps that require root like LMT Pie.
The first time I tried this I fastboot flashed, booted straight into recovery, kept system read only, rebooted to recovery, then rebooted into the ROM before I made any changes. I just wanted to be extra sure everything was ok. When I tried to reboot to recovery I got the "no command" error with the android laying on his back. Rooting, even if it is systemless seems to be necessary before you reboot into the system to make TWRP stick.
Click to expand...
Click to collapse
You are absolutely right! When I first tried this method I almost lost my device, since when uncheking "system read only" it some how wiped my baseband, and through rsd I was not been able to flash it back... Had to dig a lot in Google to recover it...
So the good way is: unlock bootloader, install systemless SuperSU via fastboot, boot up, go to bootloader, install TWRP by fastboot, boot in it twice, never uncheking read-only, than you can even install Xposed (I'm using it, it's OK)
Enviado de meu XT1572 usando Tapatalk
danielgava said:
You are absolutely right! When I first tried this method I almost lost my device, since when uncheking "system read only" it some how wiped my baseband, and through rsd I was not been able to flash it back... Had to dig a lot in Google to recover it...
So the good way is: unlock bootloader, install systemless SuperSU via fastboot, boot up, go to bootloader, install TWRP by fastboot, boot in it twice, never uncheking read-only, than you can even install Xposed (I'm using it, it's OK)
Enviado de meu XT1572 usando Tapatalk
Click to expand...
Click to collapse
I will appreciate if you could explain how did you install SuperSu via fastboot?
Thanks!
For "TWRP - read only" I can refer to SuperSu thread:
"If TWRP offers you to keep /system read-only, indeed keep it read-only.
If TWRP tells you SuperSU is not installed, and asks you to install it, do not do it, you will break things!"
sayV said:
Can anyone confirm this for India? Or should I risk being the first one to try it on an Indian XT1572 Dual Sim? Although I'll have to wait for a week. My phone is at the service center currently. It apparently had a manufacturing defect in the audio jack.
Click to expand...
Click to collapse
all is good.. @freakzapster has already done this aanndd it works fine
BooBzi said:
I will appreciate if you could explain how did you install SuperSu via fastboot?
Thanks!
For "TWRP - read only" I can refer to SuperSu thread:
"If TWRP offers you to keep /system read-only, indeed keep it read-only.
If TWRP tells you SuperSU is not installed, and asks you to install it, do not do it, you will break things!"
Click to expand...
Click to collapse
Sorry I meant via ADB. Here is the link:
http://forum.xda-developers.com/showthread.php?p=64055153
Enviado de meu XT1572 usando Tapatalk
danielgava said:
Sorry I meant via ADB. Here is the link:
http://forum.xda-developers.com/showthread.php?p=64055153
Enviado de meu XT1572 usando Tapatalk
Click to expand...
Click to collapse
Ok, thanks! That make sense now.
I have an Australian xt1752 Moto X style and i tried the trupure MM rom.
my steps were:
unlock
install TWRP
backup the entire phone , all of it to external card and then save the backup to pc just in case
wipe all partitions except for internal and ext card
flash the trupure mm rom already rooted and ready for exposed.
clear cache
boot
problem is i dont have wifi working and if i flash the modem either from the eu 5.1.1 or the us or the indian version my wifi works but then the sim card stops being detected and no calling or sms working.
what i didnt try is flashing one of these modems and then restoring my efs partition from the backup of twrp.
Other then this the phone is much much faster especially for gaming.
---------- Post added at 12:42 AM ---------- Previous post was at 12:37 AM ----------
jason2678 said:
XT1575 US here. This worked for me on the second try. I followed the procedure in the OP with the following exceptions. Never unchecked system read only in step 3, and never installed xposed. I used the systemless supersu version referenced in the OP and I'm rooted. Confirmed with a few apps that require root like LMT Pie.
The first time I tried this I fastboot flashed, booted straight into recovery, kept system read only, rebooted to recovery, then rebooted into the ROM before I made any changes. I just wanted to be extra sure everything was ok. When I tried to reboot to recovery I got the "no command" error with the android laying on his back. Rooting, even if it is systemless seems to be necessary before you reboot into the system to make TWRP stick.
Click to expand...
Click to collapse
i had the android laying on his back with no command screen in recovery once aswell, what i did was while at that screen i press power + up for 3 second and release up and then its taken to the default recovery menu
Alanbarnes said:
I have an Australian xt1752 Moto X style and i tried the trupure MM rom.
my steps were:
unlock
install TWRP
backup the entire phone , all of it to external card and then save the backup to pc just in case
wipe all partitions except for internal and ext card
flash the trupure mm rom already rooted and ready for exposed.
clear cache
boot
problem is i dont have wifi working and if i flash the modem either from the eu 5.1.1 or the us or the indian version my wifi works but then the sim card stops being detected and no calling or sms working.
what i didnt try is flashing one of these modems and then restoring my efs partition from the backup of twrp.
Other then this the phone is much much faster especially for gaming.
---------- Post added at 12:42 AM ---------- Previous post was at 12:37 AM ----------
i had the android laying on his back with no command screen in recovery once aswell, what i did was while at that screen i press power + up for 3 second and release up and then its taken to the default recovery menu
Click to expand...
Click to collapse
For wifi you can flash TruPureXMM modem!
BooBzi said:
For wifi you can flash TruPureXMM modem!
Click to expand...
Click to collapse
I just tried that and WiFi now works but now I have no network signal. I tried redoing it same thing. I also restored my efs but nope now no phone network
Alanbarnes said:
I just tried that and WiFi now works but now I have no network signal. I tried redoing it same thing. I also restored my efs but nope now no phone network
Click to expand...
Click to collapse
Clean wipe, flash ROM, flash modem?
I did almost the same but I skip " changed to read only, and reboot to recovery again, so it sticks on. Reboot device normally, see that it boots normal. After that, I boot to TWRP again, uncheck read only on mount menu."
After instalation SU and xspoed in twrp reboot system i got loop x2 or x3 but after that system loaded
android starts up
optimalization apps xx/175 :_)
I've just received the April security patch. Just it. No Oreo.
OTA:https://drive.google.com/file/d/1nHOiasjpMbVQVP0gqMC_T_YSjBo-YEC-/view?usp=drivesdk
asks for permission to download the file, you can upload to another server the ota please
tazlooney89 said:
asks for permission to download the file, you can upload to another server the ota please
Click to expand...
Click to collapse
Try again, please. I think I've fixed the permission.
This Zip will work in...RETIN channel ...XT1643??
Thanks, it works correctly on model XT1641
preetvardhan said:
This Zip will work in...RETIN channel ...XT1643??
Click to expand...
Click to collapse
probably yes
Any improvements or fixes?
hello in twrp???
because I did via ota in an xt1626 and it only rebooted in recovery mode. I had to reinstall the rom stock from February 2018 with Original Recovery. deacupe for being lay in the matter I have the device 2 months ago had a reason i. thank you guys:good:
junin_BsB said:
hello in twrp???
because I did via ota in an xt1626 and it only rebooted in recovery mode. I had to reinstall the rom stock from February 2018 with Original Recovery. deacupe for being lay in the matter I have the device 2 months ago had a reason i. thank you guys:good:
Click to expand...
Click to collapse
Stock OTA updates are not usually flashable in TWRP - you must revert back to full stock to use OTA updates anyway (no root, no TWRP, fully unmodified device) as you found out. Unlocked bootloader status does not matter.
you officially received it from Motorola?
The OTA update installed successfully on XT1644 using the manual Recovery Install from SD Card procedure.
Sent from my Moto G (4) using Tapatalk
SnoopDoge said:
you officially received it from Motorola?
Click to expand...
Click to collapse
Yes, sometimes i get checking for updates and then...
alexandreantunez said:
Yes, sometimes i get checking for updates and then...
Click to expand...
Click to collapse
Yeah, Brazil and India appear to be the territories that get the updates first, then are steadily rolled out globally I still don't quite understand why thus far the US seem to get a different patch to everyone else though...
Here's some notes about the update and my experience of updating from a rooted NPJS25.93-14-15 device:
a) File name is Blur_Version.25.231.5.athene.retail.en.US. md5 checksum is: 25eacb6f2ddffe92c438465d068b6bad with a filesize of 40.8 MB.
b)From the OTA updater script, requires NPJS25.93-14-15 (Feb 2018) or NPJS25.93-14-18 (April 2018)
Code:
Package expects build thumbprint of 7.0/NPJS25.93-14-18/3:user/release-keys or 7.0/NPJS25.93-14-15/5:user/release-keys
c)Brings your device up to date with the 1 April 2018 security patch with build NPJS25.93-14-18. Looking at the OTA script, also updates boot/kernel, system, OEM.
d)Bootloader version still maintained at B1:07 (appears to be same version as Dec 2017/Feb 2018), and modem version ends in 62.02R (same as Feb 2018). I do not know if the bootloaders are exactly the same or if they have different signatures (with the same version). So our blankflash may still work or you may have some issues, I have no desire to test the blankflash...
Flashing this onto a rooted NPJS25.93-14-15 XT1642 retgb device was the same as previous OTA updates: unroot by re-flashing stock firmware, copying the OTA update to internal storage, then apply the OTA update.
I re-flashed the NPJS25.93-14-15 firmware from here https://forum.xda-developers.com/showpost.php?p=76337066&postcount=769 with the flashing commands further down. As my device was already on NPJS25.93-14-15, and I had not downgraded my device firmware at any point, I was comfortable skipping GPT/bootloader/modem (since they should not change except from firmware flashes), you could always flash them for peace of mind. If you ever downgraded, I would recommend a full flash. Also, I've backed up in TWRP and omitted the 'fastboot erase userdata' to preserve my data, but you may have to consider a factory reset should your device become unstable. You may also wish to consider flashing each command manually (via copy pasting to your ADB terminal) rather than using a script.
Code:
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash dsp adspso.bin
fastboot flash oem oem.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
fastboot flash system system.img_sparsechunk.6
fastboot flash system system.img_sparsechunk.7
fastboot erase cache
fastboot reboot
This restored my device to a stock NPJS25.93-14-15 firmware without TWRP/root, but preserving my data. As normal with an unlocked bootloader, you will see 'Image signed with bad key' messages during flashing and the 'bad key' on the unlocked bootloader screen. After downloading the Blur_Version OTA update to my device's internal storage, I then booted to bootloader (with 'adb reboot bootloader' in the ADB terminal, without quotes), then selected to boot to recovery with the volume keys and then pressing the power key to select.
As before, in the 'no command' and fallen Android screen of the stock recovery, I pressed the power key first and then pressed the volume up key, holding both keys together for about a second before getting to the recovery menu (might take a few tries).
Once in the recovery menu, as before I tried to select 'Apply update from SD card', but my device complained of 'Internal and external memory cannot be mounted'. Selecting 'Mount /system' then using the 'Apply update via SD card' worked.
Using the volume and power keys to navigate to the OTA update in the Download folder, the installation then took about 5-10 minutes to install. I chose to wipe cache afterwards and then selected 'Reboot system now' to reboot.
One thing I noted, as with the previous NPJS25.93-14-15 OTA update, is that on the first boot after the update, my device showed the unlocked bootloader screen then got stuck on a black screen during the boot. I left it for about 1-2 min, afterwards holding the power button down to force a reboot then caused the device to reboot without issue and has been stable since then. You may encounter this or not, just something to be aware of.
The April 2018 stock update seems to feel quicker, at least compared to the Feb 2018 update, though early days yet. I still have my fingerprint sensor and IMEI are still present. It's also the April 2018 security patch, so whilst no Oreo, at least we're on a recent patch
Nice explanation there @echo92 .
BTW I have the April 2018 firmware ready for testing if anyone is willing to, on the retail variants. However it is better if you take modem/persist/fsg backup in TWRP if possible.
I will be updating my firmware thread once people test this on their models with the backup above mentioned. Please mention the device model and the channel you flashed it onto. Disclaimer as per the standard firmware pages: Take backup and proceed with caution, I don't own this file.
https://sourceforge.net/projects/st...FAULT_regulatory-DEFAULT_CFC.xml.zip/download
thanks @rajatgupta1998.....................bdw is there any possibility for us to an RevivorOS update
punchytoe said:
thanks @rajatgupta1998.....................bdw is there any possibility for us to an RevivorOS update
Click to expand...
Click to collapse
Soon [emoji769]
Sent from my Moto G (4) using Tapatalk
The April patch update has been released in India?
CMKdaGreatest said:
The April patch update has been released in India?
Click to expand...
Click to collapse
no, it seems like VERY few "lucky" (?) users received it like OP here
removed
---edit, flashed no issues
rajatgupta1998 said:
Nice explanation there @echo92 .
BTW I have the April 2018 firmware ready for testing if anyone is willing to, on the retail variants. However it is better if you take modem/persist/fsg backup in TWRP if possible.
I will be updating my firmware thread once people test this on their models with the backup above mentioned. Please mention the device model and the channel you flashed it onto. Disclaimer as per the standard firmware pages: Take backup and proceed with caution, I don't own this file.
https://sourceforge.net/projects/st...FAULT_regulatory-DEFAULT_CFC.xml.zip/download
Click to expand...
Click to collapse
running on xt1640 channel retbr
First of all sorry for my poor English. If you see any language errors, you may always tell them.
After a long road trying to fix my Honor after a bricked it with flashing wrong files with fastboot, I finally fixed it. Because it was so hard to find the right manual, I will write my method down.
This will work for any kind of brick. By example: black screen or reboot cycle. It will also work when you were on EMUI 9 or on a version with a security patch later then June.
Requisites
Access to the inside of your phone
DC-Phoenix + HCU license
ChimeraTool License
TWRP Files for your phone. I used this one.
Huawei Update Extractor
View attachment nvme.zip: got it from [url]https://t.me/huaweihax[/URL]
HUAWEI USB COM 1.0 driver installed
You can only install this driver with driver signature enforcement disabled. For this is Google your best friend.Firmware files
You can find those on androidhost.ru. Be sure you download the right files. You need two files: one with a security patch later then June 2018, but with EMUI 8 and also a firmware that was released just before June. Unzip already the files you downloaded.
I used the versions B378C432 and B366C432 for the Honor 9 (STF-L09).
Fixing your phone
Go into test point mode. See the attached picture. You need to ground this point with some metal plate of the phone. For this you can use a paperclip. You need to press the power button while grounding the test point. You can see in Device Manager if you succeeded when you see HUAWEI USB COM 1.0
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Start DC-Phoenix and go into the 'update OEMINFO' tab. There you need to select the right bootloader. For me it was the selected on in the picture. You can try as much if you want. This won't harm your phone. Unlock FRP and Update OEMINFO don't need to be checked. Press update and when you get the message with completed you can go to the next step.
Close DC-Phoenix and open ChimeraTool. Cholera will see your phone, if everything went right. Now you need to go to the update firmware tab. Select there the update.app and update_xxx_hw_xxxx.app files from the firmware with the security patch later then June. Otherwise there will be errors while flashing the xloader partition. Now flash these.
Normally your phone reboots automatically. Check in the settings/about if you still have your IMEI. If its not 0000000000 your lucky, otherwise go to the next step.
Shutdown your phone and go into fastboot. You have to extract: kernel, system, vendor and ramdisk from update.app from the firmware with a security patch before June. Flash those files with fastboot:
Code:
fastboot flash kernel kernel.img
It's possible that you get an error while flashing vendor. We fix this later.
Try rebooting.
Code:
fastboot reboot
If it doesn’t boot, go back into fastboot. Flash TWRP:
Code:
fastboot flash recovery_ramdisk twrp.img
.
Go into TWRP by holding volume-up and power. Be sure your phone isn't charging, otherwise it will boot into erecovery. In TWRP you need to flash NVME.zip (you need to flash it 4 times, it's a security precaution). After flashing NVME.zip it should be possible to fastboot flash vendor and reboot correctly.
Check your security patch in settings/about. If it's lower then June, then you've done everything right. Before you use HCU, you need to flash the right recovery_ramdisk (recovery_ramdis) again. Extract it from update.app and flash it with fastboot. Reboot again and let now the magic begin with HCU.
Check in settings/about if you can see your IMEI. If so, then you can use Hisuite to go back to an official firmware.
Hi, I followed your instructions, and unfortunately it did not work. I was able to revive the phone but only with the latest (STF-L09 8.0.0.385 (C432) - STF-L09C432E2R1P5B175 (9.0.1.175)) firmware, everything else is XLOADER error ... My problem now is that I use the IMEI can not fix. Do you know what I can do there? Thank you.
tomek5 said:
Hi, I followed your instructions, and unfortunately it did not work. I was able to revive the phone but only with the latest (STF-L09 8.0.0.385 (C432) - STF-L09C432E2R1P5B175 (9.0.1.175)) firmware, everything else is XLOADER error ... My problem now is that I use the IMEI can not fix. Do you know what I can do there? Thank you.
Click to expand...
Click to collapse
Did you tried the last steps with flashing a lower firmware version with fastboot? I think it also could work when you're on B385.
Item 8, which firmware "update.app recovery_ramdisk" B385 or B366?.
There is no recovery_ramdisk there are both recovery_ramdis.
tomek5 said:
Item 8, which firmware "update.app recovery_ramdisk" B385 or B366?.
There is no recovery_ramdisk there are both recovery_ramdis.
Click to expand...
Click to collapse
You have to use B385. Recovery_ramdisk is equal to the partition named recovery_ramdis.
TWRP (stf-twrp-zxz-0.3.img) hangs on startup image.
Item 5. Should I flash everything (kernel, system, vendor and ramdisk) or just kernels?
tomek5 said:
TWRP (stf-twrp-zxz-0.3.img) hangs on startup image.
Item 5. Should I flash everything (kernel, system, vendor and ramdisk) or just kernels?
Click to expand...
Click to collapse
Weird. Yes, you have to flash the four files.
I did everything that flashed the firmware (STF-L09C432B378 (8.0.0.378)). All without success, always the same, as soon as I flashe the kernel, the system, the manufacturer and the Ramdisk starts the phone to Honor picture and boots again into the Fastboot. TWRP will not work anymore.
fastboot flash kernel KERNEL.img
fastboot flash system SYSTEM.img
fastboot flash ramdisk RAMDISK.img
fastboot flash vendor VENDOR.img
tomek5 said:
I did everything that flashed the firmware (STF-L09C432B378 (8.0.0.378)). All without success, always the same, as soon as I flashe the kernel, the system, the manufacturer and the Ramdisk starts the phone to Honor picture and boots again into the Fastboot. TWRP will not work anymore.
fastboot flash kernel KERNEL.img
fastboot flash system SYSTEM.img
fastboot flash ramdisk RAMDISK.img
fastboot flash vendor VENDOR.img
Click to expand...
Click to collapse
Have you tried booting with volume up and power button pressed? If the blue screen comes up, you can stop pressing the power button. Did you already ones succeeded to get into TWRP?
yes, here I come to the erecovery.
tomek5 said:
yes, here I come to the erecovery.
Click to expand...
Click to collapse
You have to unplug your phone. It may not be charging when you try to get into TWRP.
OK, I did it, the IMEI is back. Did it without TWRP. After flashing the kernel, system, vendor and ramdisk I did a Factory Reset. Then HCU.
Thank you for your help!!!
Clarification
waterboy1602 said:
First of all sorry for my poor English. If you see any language errors, you may always tell them.
After a long road trying to fix my Honor after a bricked it with flashing wrong files with fastboot, I finally fixed it. Because it was so hard to find the right manual, I will write my method down.
This will work for any kind of brick. By example: black screen or reboot cycle. It will also work when you were on EMUI 9 or on a version with a security patch later then June.
Requisites
Access to the inside of your phone
DC-Phoenix + HCU license
ChimeraTool License
TWRP Files for your phone. I used this one.
Huawei Update Extractor
View attachment 4766798: got it from https://t.me/huaweihax
HUAWEI USB COM 1.0 driver installed
You can only install this driver with driver signature enforcement disabled. For this is Google your best friend.Firmware files
You can find those on androidhost.ru. Be sure you download the right files. You need two files: one with a security patch later then June 2018, but with EMUI 8 and also a firmware that was released just before June. Unzip already the files you downloaded.
I used the versions B378C432 and B366C432 for the Honor 9 (STF-L09).
Fixing your phone
Go into test point mode. See the attached picture. You need to ground this point with some metal plate of the phone. For this you can use a paperclip. You need to press the power button while grounding the test point. You can see in Device Manager if you succeeded when you see HUAWEI USB COM 1.0
View attachment 4766797
Start DC-Phoenix and go into the 'update OEMINFO' tab. There you need to select the right bootloader. For me it was the selected on in the picture. You can try as much if you want. This won't harm your phone. Unlock FRP and Update OEMINFO don't need to be checked. Press update and when you get the message with completed you can go to the next step.
View attachment 4766799
Close DC-Phoenix and open ChimeraTool. If everything went right, shall Chimera see your phone. Now you need to go to the update firmware tab. Select there the update.app and update_xxx_hw_xxxx.app files from the firmware with the security patch later then June. Otherwise there will be errors while flashing the xloader partition. Now flash these.
Normally your phone reboots automatically. Check in the settings/about if you still have your IMEI. If its not 0000000000 your lucky, otherwise go to the next step.
Shutdown your phone and go into fastboot. You have to extract: kernel, system, vendor and ramdisk from update.app from the firmware with a security patch before June. Flash those files with fastboot:
Code:
fastboot flash kernel kernel.img
It's possible that you get an error while flashing vendor. We fix this later.
Try rebooting.
Code:
fastboot reboot
If it doesn’t boot, go back into fastboot. Flash TWRP:
Code:
fastboot flash recovery_ramdisk twrp.img
.
Go into TWRP by holding volume-up and power. Be sure your phone isn't charging, otherwise it will boot into erecovery. In TWRP you need to flash NVME.zip (you need to flash it 4 times, it's a security precaution). After flashing NVME.zip it should be possible to fastboot flash vendor and reboot correctly.
Check your security patch in settings/about. If it's lower then June, then you've done everything right. Before you use HCU, you need to flash the right recovery_ramdisk (recovery_ramdis) again. Extract it from update.app and flash it with fastboot. Reboot again and let now the magic begin with HCU.
Check in settings/about if you can see your IMEI. If so, then you can use Hisuite to go back to an official firmware.
Click to expand...
Click to collapse
Just for clarification, am sorry if am being a dummy, Step 3: after closing DC phonix, do i use chimera tool for only checking the phone's visibility or I close it again and flash with DC phonix? Please help
Trig18 said:
First of all sorry for my poor English. If you see any language errors, you may always tell them.
After a long road trying to fix my Honor after a bricked it with flashing wrong files with fastboot, I finally fixed it. Because it was so hard to find the right manual, I will write my method down.
This will work for any kind of brick. By example: black screen or reboot cycle. It will also work when you were on EMUI 9 or on a version with a security patch later then June.
Requisites
Access to the inside of your phone
DC-Phoenix + HCU license
ChimeraTool License
TWRP Files for your phone. I used this one.
Huawei Update Extractor
: got it from https://t.me/huaweihax
HUAWEI USB COM 1.0 driver installed
You can only install this driver with driver signature enforcement disabled. For this is Google your best friend.
Firmware files
You can find those on androidhost.ru. Be sure you download the right files. You need two files: one with a security patch later then June 2018, but with EMUI 8 and also a firmware that was released just before June. Unzip already the files you downloaded.
I used the versions B378C432 and B366C432 for the Honor 9 (STF-L09).
Fixing your phone
Go into test point mode. See the attached picture. You need to ground this point with some metal plate of the phone. For this you can use a paperclip. You need to press the power button while grounding the test point. You can see in Device Manager if you succeeded when you see HUAWEI USB COM 1.0
Start DC-Phoenix and go into the 'update OEMINFO' tab. There you need to select the right bootloader. For me it was the selected on in the picture. You can try as much if you want. This won't harm your phone. Unlock FRP and Update OEMINFO don't need to be checked. Press update and when you get the message with completed you can go to the next step.
Close DC-Phoenix and open ChimeraTool. If everything went right, shall Chimera see your phone. Now you need to go to the update firmware tab. Select there the update.app and update_xxx_hw_xxxx.app files from the firmware with the security patch later then June. Otherwise there will be errors while flashing the xloader partition. Now flash these.
Normally your phone reboots automatically. Check in the settings/about if you still have your IMEI. If its not 0000000000 your lucky, otherwise go to the next step.
Shutdown your phone and go into fastboot. You have to extract: kernel, system, vendor and ramdisk from update.app from the firmware with a security patch before June. Flash those files with fastboot: It's possible that you get an error while flashing vendor. We fix this later.
Try rebooting. If it doesn’t boot, go back into fastboot. Flash TWRP:
Just for clarification, am sorry if am being a dummy, Step 3: after closing DC phonix, do i use chimera tool for only checking the phone's visibility or I close it again and flash with DC phonix? Please help
Click to expand...
Click to collapse
You should use Chimera to flash the firmware.
Thanks
waterboy1602 said:
You should use Chimera to flash the firmware.
Click to expand...
Click to collapse
Thank you very much , my device is now fully operational on EMUI9 though I used Dc phonix to flash it in upgrade mode.
Thanks again ??
Hi, waterboy1602!
Are you sure that for HCU works only with security patches LOWER than June 2018 ?
I am trying to find out exactly this dates, and firmware to downgrade.
BTW. On 4pda admins wrotes that it is not possilbe to downgrade to no_gpu_turbo version.
Do you know something about it ?
daemonserj said:
Hi, waterboy1602!
Are you sure that for HCU works only with security patches LOWER than June 2018 ?
I am trying to find out exactly this dates, and firmware to downgrade.
BTW. On 4pda admins wrotes that it is not possilbe to downgrade to no_gpu_turbo version.
Do you know something about it ?
Click to expand...
Click to collapse
Yes, after a lot of trial and error I found out that it only works with a firmware lower then June 2018. I know that most people say it's impossible to downgrade to no_gpu_turbo. I found this way to work with my phone. I've put a lot of time into it to find this way. I hope it will also work for you.
Hi, such a question, what should I do if I short-circuited the wrong contacts and after flashing the phone is forever detected as a comport and will not turn
DydoserLolekDrago said:
Hi, such a question, what should I do if I short-circuited the wrong contacts and after flashing the phone is forever detected as a comport and will not turn
Click to expand...
Click to collapse
Honestly I have no idea. If the testpoints don't work anymore, I dont think you have a lot of options.
how exactly do i ground the testpoint?
i connect it with gnd? or just press it with the
paperclip?
can it break the phone?
Fastboot Stuck as saying booting with logo. Any Solution?
Sent from my GM1911 using Tapatalk
Were you updating to android 10 from 9 or from 10 beta? is it the 2 white dots spinning around the red dot?
I have a problem, I updated from 9 to 10 and lost root and twrp. Is there any possibility for the author: to root and have twrp again? I tried the fastboot version of the twrp installation. img in cmd and kind of says ok, but the phone is on the fastboot logo and nothing happens ?
equlizer said:
Were you updating to android 10 from 9 or from 10 beta? is it the 2 white dots spinning around the red dot?
Click to expand...
Click to collapse
From 9
Sent from my GM1911 using Tapatalk
Jarek84 said:
I have a problem, I updated from 9 to 10 and lost root and twrp. Is there any possibility for the author: to root and have twrp again? I tried the fastboot version of the twrp installation. img in cmd and kind of says ok, but the phone is on the fastboot logo and nothing happens [emoji29]
Click to expand...
Click to collapse
I got a solution
Twrp 3.3.1.65
Sent from my GM1911 using Tapatalk
Jarek84 said:
Is there any possibility for the author: to root and have twrp again? I tried the fastboot version of the twrp installation. img in cmd and kind of says ok, but the phone is on the fastboot logo and nothing happens
Click to expand...
Click to collapse
You can not flash TWRP in fastboot on this device. And that never worked for this device. I know it worked on lots of previous Android devices (standard method to install TWRP). But you should wipe from your mind that notion that it works on the 7 Pro.
The process for Android 9 was to boot TWRP (very different from flash TWRP). But fastboot boot command doesn't work on the Android 10 update. This is similar to the situation when the 7 Pro was first released, and OnePlus fixed the fastboot boot command a bit later.
Current root method, is to flash a patched boot image. But lots of folks seem to be having trouble rooting the new Android 10 stable (even using the proper method). Flashing the stock boot.img is another option (to get the phone working, but no root).
First fastboot stucked
Second no partition found
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Sent from my GM1911 using Tapatalk
You are not supposed to "flash" twrp through windows. Once you "boot" with windows, you install twrp through twrp.
redpoint73 said:
You can not flash TWRP in fastboot on this device. And that never worked for this device. I know it worked on lots of previous Android devices (standard method to install TWRP). But you should wipe from your mind that notion that it works on the 7 Pro.
The process for Android 9 was to boot TWRP (very different from flash TWRP). But fastboot boot command doesn't work on the Android 10 update. This is similar to the situation when the 7 Pro was first released, and OnePlus fixed the fastboot boot command a bit later.
Current root method, is to flash a patched boot image. But lots of folks seem to be having trouble rooting the new Android 10 stable (even using the proper method). Flashing the stock boot.img is another option (to get the phone working, but no root).
Click to expand...
Click to collapse
False, it was possible on android 9 to flash twrp on this device. It worked perfectly. With android 10 that's not possible unfortunately unless you have it already installed on android pie and you are upgrading. Use the unofficial twrp latest build and flash it after you flash the android 10 update in twrp and you are golden.
Hello All,
I decided to hop back in and root my device. I'm running into the same issue as OP. I try to boot into TWRP and i just get a "fastboot mode" screen. Can anyone clarify if this is doable as of now? and how?
Sorry, I havent rooted a phone in 7+ years.
links2586 said:
Hello All,
I decided to hop back in and root my device. I'm running into the same issue as OP. I try to boot into TWRP and i just get a "fastboot mode" screen. Can anyone clarify if this is doable as of now? and how?
Sorry, I havent rooted a phone in 7+ years.
Click to expand...
Click to collapse
Look here. https://forum.xda-developers.com/oneplus-7-pro/how-to/android-q-4th-developer-preview-t3953997
hallo dare said:
Look here. https://forum.xda-developers.com/oneplus-7-pro/how-to/android-q-4th-developer-preview-t3953997
Click to expand...
Click to collapse
That doesn't seem to work for me since I can't see my case, which is the same as @Jarek84
Only the stock boot.img boots for me. magisk_patched.img puts me in a bootloop and I'm stuck at the fastboot logo whenever I try to fastboot boot twrp.img (neither official nor the .65 one here, the modified one).
Any help would be appreciated to get root and twrp back.
Thanks!
hallo dare said:
False, it was possible on android 9 to flash twrp on this device. It worked perfectly. With android 10 that's not possible unfortunately unless you have it already installed on android pie and you are upgrading. Use the unofficial twrp latest build and flash it after you flash the android 10 update in twrp and you are golden.
Click to expand...
Click to collapse
Can you cite anyone who flashed twrp from fastboot in op7p.
---------- Post added at 06:12 PM ---------- Previous post was at 06:09 PM ----------
whisky_ said:
That doesn't seem to work for me since I can't see my case, which is the same as @Jarek84
Only the stock boot.img boots for me. magisk_patched.img puts me in a bootloop and I'm stuck at the fastboot logo whenever I try to fastboot boot twrp.img (neither official nor the .65 one here, the modified one).
Any help would be appreciated to get root and twrp back.
Thanks!
Click to expand...
Click to collapse
. Have you tried patching your own boot.img instead of flashing the one provided on the guide?
Everyone who has ever flashed twrp. But if you want evidence,
https://forum.xda-developers.com/showpost.php?p=79677185&postcount=1
hallo dare said:
Everyone who has ever flashed twrp. But if you want evidence,
https://forum.xda-developers.com/showpost.php?p=79677185&postcount=1
Click to expand...
Click to collapse
If you read a little more carefully you will see that the thread you're linking to says exactly what redpoint73 wrote. I.e. in order to flash TWRP one must first fastboot boot the TWRP-image, and then flash the TWRP-zip from within TWRP.
No one said it's not possible to flash TWRP. What was said was that it's not possible to do it from fastboot.
Cheers.
branko.s67 said:
If you read a little more carefully you will see that the thread you're linking to says exactly what redpoint73 wrote. I.e. in order to flash TWRP one must first fastboot boot the TWRP-image, and then flash the TWRP-zip from within TWRP.
No one said it's not possible to flash TWRP. What was said was that it's not possible to do it from fastboot.
Cheers.
Click to expand...
Click to collapse
Obviously you cannot flash from fastboot, but what I'm referencing to is that it was said "twrp cannot be flashed from fastboot" , but that it can be achieved by the method i pointed out to get to recovery to flash. It's not just a case of saying it cannot be flashed and covered the method in one sweeping statement. There is a method, but as we all know, this is not possible currently with Android 10
hallo dare said:
Obviously you cannot flash from fastboot, but what I'm referencing to is that it was said "twrp cannot be flashed from fastboot" , but that it can be achieved by the method i pointed out to get to recovery to flash.
Click to expand...
Click to collapse
Once you have booted recovery, you are no longer in fastboot.
Just try a fastboot command while in TWRP, and see how that works for you.
redpoint73 said:
Once you have booted recovery, you are no longer in fastboot. Duh!!!!
Click to expand...
Click to collapse
Hold on a sec. If you are going to act in a childish manner how are we to discuss this properly.
To even get to twrp you have to use the .img file in fastboot. So "fastboot flash recovery filename.img"
So you are flashing in fastboot to get to twrp recovery.
Your comment said that you couldn't flash twrp via fastboot and never could with this phone. That's half correct. What I'm saying is you can flash the .img file to access twrp before flashing the zip file on Android pie. Unfortunately that's not the case with Android 10.
hallo dare said:
To even get to twrp you have to use the .img file in fastboot. So "fastboot flash recovery filename.img"
So you are flashing in fastboot to get to twrp recovery.
Click to expand...
Click to collapse
Wrong. Your command is incorrect.
The correct command is: fastboot boot twrp.img
Once you are booted to TWRP, you can than flash TWRP installer zip (not the TWRP img).
Just look at the post you quoted above in response #14.
This phone does not even have a recovery partition. Recovery resides on boot.img for this device due to A/B partition scheme.
My original statements hold as correct.
redpoint73 said:
Wrong. Your command is incorrect.
The correct command is: fastboot boot twrp.img
Just look at the post you quoted above in response #14.
This phone does not have a recovery partition. Recovery resides on boot.img for this device.
My original statements hold as correct.
Click to expand...
Click to collapse
O my God, that recognised contributor tag is going to your head.
The command with "boot" boots into TWRP recovery. The command with "flash", flashes the .img file in fastboot mode on Android pie.
Root OnePlus 9, 9 Pro, 9R Android 12 ColorOS 12 via Magisk
Thi guide will show you how to root the OnePlus 9, OnePlus 9 Pro, and OnePlus 9R running ColorOS 12 Android 12 via Magisk Patched Boot.img
www.droidwin.com
Just sharing what I've learned. Have to patch boot.img and vendor boot.img and flash out of folder in sdk on desktop.Then use vb_meta.img to disable verity flash. Guide above has to be followed to a T. Even though it's for the Chinese version Color os works fine on Oos... Patch boot.img /vendor_boot with magisk 23.0. This way magisk hide and modules work. If you patch with canary version of magisk you loose both. I'm attaching stock boot, vb_meta vendor_boot.img files for the Global unlocked op9. Files are from new A12 os. Btw 23.0 works perfectly on A12. If this helps hit the like button; it's free.
0p9 partitions..A 12 - Google Drive
drive.google.com
This method is overkill for rooting both versions of A12 that were released ,
The best method for a12 with unlocked bootloader is this:
Patch boot.img & copy to adb folder on pc
Reboot to bootloader
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
fastboot flash boot *nameofpatchedbootimagehere.img*
IF YOUR DOING A CLEAN FLASH OF A12 BEFORE SETUP = fastboot-w
fastboot reboot
Worst case scenario you will have to wipe all data for it to register correctly and boot fully.
The vendor_boot does not need to be patched with the A12 update, you have to disable verity and verification instead of just verification for any device running A12.
allenjthomsen said:
This method is overkill for rooting both versions of A12 that were released ,
The best method for a12 with unlocked bootloader is this:
Patch boot.img & copy to adb folder on pc
Reboot to bootloader
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
fastboot flash boot *nameofpatchedbootimagehere.img*
IF YOUR DOING A CLEAN FLASH OF A12 BEFORE SETUP = fastboot-w
fastboot reboot
Worst case scenario you will have to wipe all data for it to register correctly and boot fully.
The vendor_boot does not need to be patched with the A12 update, you have to disable verity and verification instead of just verification for any device running A12.
Click to expand...
Click to collapse
I do know that just patching boot.img and flashing it breaks boot and build. Found that out the hard way. Could only reach fastboot no stock recovery . And couldn't fastboot --set-active=other. Wipe data and boot into old oos on opposite slot. I've had msm tool on my desktop and have heard horror stories of people using and it throwing errors and failing. Plugged mine right in booted edl from adb and 512 sec later had a booting device in oxygen oos
mattie_49 said:
I do know that just patching boot.img and flashing it breaks boot and build. Found that out the hard way. Could only reach fastboot no stock recovery . And couldn't fastboot --set-active=other. Wipe data and boot into old oos on opposite slot. I've had msm tool on my desktop and have heard horror stories of people using and it throwing errors and failing. Plugged mine right in booted edl from adb and 512 sec later had a booting device in oxygen oos
Click to expand...
Click to collapse
I can verify that my method works 100% on build C.36 of A12, because i am currently running it and have redone the steps multiple times to make sure nothing happens that could be bad ,the steps i have listed above in the previous post work perfectly and still let me have root currently, and i have only patched the stock boot.img.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
If your wondering how i have come to this doing it the way i did it.
I downloaded and copied the update to desktop and extracted the stock boot and patched it in magisk from the device.
I then i extracted the stock vbmeta image and after flashing the full update via local install from system settings i booted to bootloader and disabled verity and verification and then flash the patched boot image.
I then rebooted into full stock C.36 with root.
I can tell you i did this 5 times before i made the reply to you earlier and verified that it booted every time no issue without patching vendor_boot.
allenjthomsen said:
If your wondering how i have come to this doing it the way i did it.
I downloaded and copied the update to desktop and extracted the stock boot and patched it in magisk from the device.
I then i extracted the stock vbmeta image and after flashing the full update via local install from system settings i booted to bootloader and disabled verity and verification and then flash the patched boot image.
I then rebooted into full stock C.36 with root.
I can tell you i did this 5 times before i made the reply to you earlier and verified that it booted every time no issue without patching vendor_boot.
Click to expand...
Click to collapse
How does one undo the disable verity with stock vb_meta after flashing back stock boot.img and vendor boot.img ,I still couldn't take internal Google ota today. Failed after I tried restoring both of those.
Anyone knows if the new oos12 is actually "stable"? Haha
infamousvincci said:
Anyone knows if the new oos12 is actually "stable"? Haha
Click to expand...
Click to collapse
Yes all the small issues I had are corrected in today's am build.
mattie_49 said:
Yes all the small issues I had are corrected in today's am build.
Click to expand...
Click to collapse
I talk to you in TG bro. Its me, the one that has a op9 that doesnt read sim on oos12. Hahaha
mattie_49 said:
I do know that just patching boot.img and flashing it breaks boot and build. Found that out the hard way. Could only reach fastboot no stock recovery . And couldn't fastboot --set-active=other. Wipe data and boot into old oos on opposite slot. I've had msm tool on my desktop and have heard horror stories of people using and it throwing errors and failing. Plugged mine right in booted edl from adb and 512 sec later had a booting device in oxygen oos
Click to expand...
Click to collapse
Oh maan, that was my last night. Lost weeks worth of data with no back up
And I've bricked and recovered before but the way this one acted was scary as hell. A few times it said "die" at the crashdump.
mizarddo said:
Oh maan, that was my last night. Lost weeks worth of data with no back up
And I've bricked and recovered before but the way this one acted was scary as hell. A few times it said "die" at the crashdump.
Click to expand...
Click to collapse
Hello, please can you give me more details about what causes you the loss, how you did it because I'm about to do the same process and I'm afraid to get my onePlus 9 bricked
mooadeer said:
Hello, please can you give me more details about what causes you the loss, how you did it because I'm about to do the same process and I'm afraid to get my onePlus 9 bricked
Click to expand...
Click to collapse
Well first of all, at the time my version of magisk did not support android 12 for patching boot.img
But that has been long fixed, just get the latest magisk version.
And for the next part, if you are trying to root first time, do NOT use the command "fastboot flash boot boot.img" instead use "fastboot boot boot.img" to temporarily boot the patched version of boot image. That will temporarily give you root access on next power on until you restart. And while you have that temporary root, you can use magisk app to direct install that patched boot image and gain permanent root access.
Also from there after every OTA update BEFORE RESTARTING THE PHONE you can use magisk and "install to inactive slot" to retain your root with the update.
Hope that helped.
mizarddo said:
Well first of all, at the time my version of magisk did not support android 12 for patching boot.img
But that has been long fixed, just get the latest magisk version.
And for the next part, if you are trying to root first time, do NOT use the command "fastboot flash boot boot.img" instead use "fastboot boot boot.img" to temporarily boot the patched version of boot image. That will temporarily give you root access on next power on until you restart. And while you have that temporary root, you can use magisk app to direct install that patched boot image and gain permanent root access.
Also from there after every OTA update BEFORE RESTARTING THE PHONE you can use magisk and "install to inactive slot" to retain your root with the update.
Hope that helped.
Click to expand...
Click to collapse
It helps a lot thank you I just got my oneplus 9 and it's on the latest update C.47 and I don't have too much experience with onePlus or even the new android devices I'm a little bit outdated didn't use root and stuff sins the android 5 that's why I'm a little bit confused I don't want to break it
mizarddo said:
Well first of all, at the time my version of magisk did not support android 12 for patching boot.img
But that has been long fixed, just get the latest magisk version.
And for the next part, if you are trying to root first time, do NOT use the command "fastboot flash boot boot.img" instead use "fastboot boot boot.img" to temporarily boot the patched version of boot image. That will temporarily give you root access on next power on until you restart. And while you have that temporary root, you can use magisk app to direct install that patched boot image and gain permanent root access.
Also from there after every OTA update BEFORE RESTARTING THE PHONE you can use magisk and "install to inactive slot" to retain your root with the update.
Hope that helped.
Click to expand...
Click to collapse
Update following your instructions everything is Ok done with rooting thank you
LE2113 on C.47
mizarddo said:
Well first of all, at the time my version of magisk did not support android 12 for patching boot.img
But that has been long fixed, just get the latest magisk version.
And for the next part, if you are trying to root first time, do NOT use the command "fastboot flash boot boot.img" instead use "fastboot boot boot.img" to temporarily boot the patched version of boot image. That will temporarily give you root access on next power on until you restart. And while you have that temporary root, you can use magisk app to direct install that patched boot image and gain permanent root access.
Also from there after every OTA update BEFORE RESTARTING THE PHONE you can use magisk and "install to inactive slot" to retain your root with the update.
Hope that helped.
Click to expand...
Click to collapse
from where can I download boot.img for version:
LE2113_11.C.47: LE2113_11.C.47_1470_202203102118
Thanks and best regards
Lol patching the boot image then flashing it with simple "fastboot flash boot patchedboot.img" works for me. It does not require any other images or patches.
_MartyMan_ said:
Lol patching the boot image then flashing it with simple "fastboot flash boot patchedboot.img" works for me. It does not require any other images or patches.
Click to expand...
Click to collapse
you mean boot image from OP? My question is how I get that file
aldoc01 said:
you mean boot image from OP? My question is how I get that file
Click to expand...
Click to collapse
Yep, stock boot images can be extracted from full zips with tools (payload extractor).
Also, i have a collection, check it out.
_MartyMan_ said:
Lol patching the boot image then flashing it with simple "fastboot flash boot patchedboot.img" works for me. It does not require any other images or patches.
Click to expand...
Click to collapse
So you think the same way the 9 Pro does it would work? The guide there says to grab the stock image, install Magisk app on the phone, patch the image with the app, boot (not flash) the image, then have Magisk direct install. I came here and saw all of this other stuff and was like... nahhh...
EtherealRemnant said:
So you think the same way the 9 Pro does it would work? The guide there says to grab the stock image, install Magisk app on the phone, patch the image with the app, boot (not flash) the image, then have Magisk direct install. I came here and saw all of this other stuff and was like... nahhh...
Click to expand...
Click to collapse
If you don't jump magisk across from A11 you have to disable verity with vb_meta partition as well to gain permanent root on A12. This I know it's my post.