Related
Hi there,
I've been searching around to find a specific firmware zip for my new tablet, the SKU: WW, Version: 10.26.1.7.
It appears that asus has pulled this file and was wondering if anyone still has this file available somehow.
I soft-bricked my tablet and am not capable of flashing any other (earlier) firmware zip.
Any help would be greatly appreciated.
Yours sincerely,
Rens "Ikkerens" Rikkerink
Ikkerens said:
Hi there,
I've been searching around to find a specific firmware zip for my new tablet, the SKU: WW, Version: 10.26.1.7.
It appears that asus has pulled this file and was wondering if anyone still has this file available somehow.
I soft-bricked my tablet and am not capable of flashing any other (earlier) firmware zip.
Any help would be greatly appreciated.
Yours sincerely,
Rens "Ikkerens" Rikkerink
Click to expand...
Click to collapse
Why can't you download an earlier firmware?
schmeggy929 said:
Why can't you download an earlier firmware?
Click to expand...
Click to collapse
I can, but it always ends up with some kind of error.
I basically tried following the steps you did:
schmeggy929 said:
i downloaded the asus firmware for 10.14.1.47. extract zip and you get a user.zip. extracted the boot.img. I fastboot erase boot, system, format system, data and cache(as you did)
fastboot -i 0x0B05 flash boot boot.img then
fastboot -i 0x0B05 flash system blob then
fastboot -i 0x0B05 flash system UL-K00C-US-10.14.1.47-user.zip
rebooted back into fastboot and bootloader showed 10.14.1.47 version.
Click to expand...
Click to collapse
But on when trying to flash the ***-user.zip, I get this error message:
Code:
$ fastboot -i 0x0B05 flash system UL-K00C-WW-10.14.1.47-user.zip
target reported max download size of 643825664 bytes
Invalid sparse file format at header magi
Edit: My bootloader version shows: WW_epad-10.26.1.7-20131108
Ikkerens said:
I can, but it always ends up with some kind of error.
I basically tried following the steps you did:
But on when trying to flash the ***-user.zip, I get this error message:
Code:
$ fastboot -i 0x0B05 flash system UL-K00C-WW-10.14.1.47-user.zip
target reported max download size of 643825664 bytes
Invalid sparse file format at header magi
Edit: My bootloader version shows: WW_epad-10.26.1.7-20131108
Click to expand...
Click to collapse
you are going to get that along with a few more errors. Wait until it is done. It will take like 10 mins and finish.
when it is done reboot in bootloader and you should see the version change.
schmeggy929 said:
you are going to get that along with a few more errors. Wait until it is done. I will take like 10 mins and finish.
Click to expand...
Click to collapse
You're getting this wrong, it does not do anything. The process immediately quits.
Ikkerens said:
You're getting this wrong, it does not do anything. The process immediately quits.
Click to expand...
Click to collapse
Ok when you get that message do you get a blinking curser?
Ikkerens said:
Hi there,
I've been searching around to find a specific firmware zip for my new tablet, the SKU: WW, Version: 10.26.1.7.
It appears that asus has pulled this file and was wondering if anyone still has this file available somehow.
I soft-bricked my tablet and am not capable of flashing any other (earlier) firmware zip.
Any help would be greatly appreciated.
Yours sincerely,
Rens "Ikkerens" Rikkerink
Click to expand...
Click to collapse
did you make any backup with cwm recovery?
try this:
unpack blob from 47 update
Code:
fastboot flash staging blob
fastboot flash recovery recovery.img
fastboot reboot-bootloader
load recovery, restore your backup
if you have not made any backup with cwm recovery, tell me.
btw fastboot flash system... is not needed here
lpdunwell said:
did you make any backup with cwm recovery?
try this:
unpack blob from 47 update
Code:
fastboot flash staging blob
fastboot flash recovery recovery.img
fastboot reboot-bootloader
load recovery, restore your backup
if you have not made any backup with cwm recovery, tell me.
btw fastboot flash system... is not needed here
Click to expand...
Click to collapse
I have not made a backup using cwm because there was no CWM available for my version.
My tablet was already updated to 4.3 and I (apparently) could not boot the cwm in the development section.
If I would be able to flash a usable recovery, I wouldn't be in this situation anyway as the asus update (.47) is flashable (found an updater-script in the zip).
Ikkerens said:
I have not made a backup using cwm because there was no CWM available for my version.
My tablet was already updated to 4.3 and I (apparently) could not boot the cwm in the development section.
If I would be able to flash a usable recovery, I wouldn't be in this situation anyway as the asus update (.47) is flashable (found an updater-script in the zip).
Click to expand...
Click to collapse
forget what I wrote here. I opened a thread with unbricking instructions. Good luck
lpdunwell said:
forget what I wrote here. I opened a thread with unbricking instructions. Good luck
Click to expand...
Click to collapse
Won't do me any good at the moment, I already managed to brick it even further (couldn't even get into fastboot mode anymore), so I RMA'd it.
Ikkerens said:
Won't do me any good at the moment, I already managed to brick it even further (couldn't even get into fastboot mode anymore), so I RMA'd it.
Click to expand...
Click to collapse
oh crap. sorry about that. I know there's the nvflash, too, but I have no idea how to use that so far...
would you mind telling what exactly happened?
lpdunwell said:
oh crap. sorry about that. I know there's the nvflash, too, but I have no idea how to use that so far...
would you mind telling what exactly happened?
Click to expand...
Click to collapse
Nvflash is inaccessible at the moment, it requires some preparation (you have to prepare it BEFORE you brick it)
Anyway, basically, I bought the tablet a few hours earlier.
Wanted to root it to remove some bloatware and restore some titanium backup thingies.
So I unlocked, rooted, basic stuff.
Went into TB, removed bloatware such as Amazon Kindle and some other irrelevant titles.
That action however, somehow caused it to be unbootable.
So I went into some basic repair stuff, as usual.
Tried to flash a recovery, only to find out, there is no working recovery. Only CWM, which required an earlier version of my bootloader.
So, what next. Restore stock? Downloaded the firmware, found out it was the earlier version of my device, because Asus removed the 4.3-EU version from their website.
So, I downloaded the .47-EU version, opened it. Saw there were no images, merely plain files meant for /system and an updater-script.
I ended up attempting to package my own system.img after that. Created an ext4 image on my computer, moved the files there. Followed the instructions in updater-script, which were mostly symlinks and stuff.
In the end of the updater-script they flashed blob to /staging and boot.img to /boot.
So, I flashed my custom system.img to /system.
Flashed boot
Flashed the blob
And beyond that point, I ended up in a bootloop of my bootloader. I could not hold down volume to enter fastboot or anything. All I could do was watch the asus logo as it constantly rebooted. (And ofcourse, no way to turn it off other than waiting for the battery to die)
Ikkerens said:
Nvflash is inaccessible at the moment, it requires some preparation (you have to prepare it BEFORE you brick it)
Anyway, basically, I bought the tablet a few hours earlier.
Wanted to root it to remove some bloatware and restore some titanium backup thingies.
So I unlocked, rooted, basic stuff.
Went into TB, removed bloatware such as Amazon Kindle and some other irrelevant titles.
That action however, somehow caused it to be unbootable.
So I went into some basic repair stuff, as usual.
Tried to flash a recovery, only to find out, there is no working recovery. Only CWM, which required an earlier version of my bootloader.
So, what next. Restore stock? Downloaded the firmware, found out it was the earlier version of my device, because Asus removed the 4.3-EU version from their website.
So, I downloaded the .47-EU version, opened it. Saw there were no images, merely plain files meant for /system and an updater-script.
I ended up attempting to package my own system.img after that. Created an ext4 image on my computer, moved the files there. Followed the instructions in updater-script, which were mostly symlinks and stuff.
In the end of the updater-script they flashed blob to /staging and boot.img to /boot.
So, I flashed my custom system.img to /system.
Flashed boot
Flashed the blob
And beyond that point, I ended up in a bootloop of my bootloader. I could not hold down volume to enter fastboot or anything. All I could do was watch the asus logo as it constantly rebooted. (And ofcourse, no way to turn it off other than waiting for the battery to die)
Click to expand...
Click to collapse
Since you are unlocked, you can try to flash the recovery (extract it first) of the US version 1.7, should be the same as wwe. Or just even try to flash the whole us update manually. And later change back to the wwe version when it comes available. The 47 update was only a minor ota for 4.2 so no image of recovery or bootloader there.
Sad story. What would have been the safe thing to do, if others wish to root their devices?
Snah001 said:
Since you are unlocked, you can try to flash the recovery (extract it first) of the US version 1.7, should be the same as wwe. Or just even try to flash the whole us update manually. And later change back to the wwe version when it comes available. The 47 update was only a minor ota for 4.2 so no image of recovery or bootloader there.
Click to expand...
Click to collapse
I still had the original recovery flashed, I never overwrote it actually. I needed a custom recovery (such as CWM, TWRP).
Flashing an US update is not possible alltogether, there are some minor differences with hardware compitability and such.
Problem is, I could've downloaded the .47 update, but I had already updated to 4.3 (BL 10.26.1.7)
Ikkerens said:
I still had the original recovery flashed, I never overwrote it actually. I needed a custom recovery (such as CWM, TWRP).
Flashing an US update is not possible alltogether, there are some minor differences with hardware compitability and such.
Problem is, I could've downloaded the .47 update, but I had already updated to 4.3 (BL 10.26.1.7)
Click to expand...
Click to collapse
I don't know if it isn't possible. On the TF700 it was only a line in the build.prop file that made the difference.
I would try it because now you have nothing and when it works you have the us version yes, but at least it works.
pelago said:
Sad story. What would have been the safe thing to do, if others wish to root their devices?
Click to expand...
Click to collapse
This guide worked fine for me; http://forum.xda-developers.com/showthread.php?t=2516215
It's only about what you do with the root ^^
Snah001 said:
I don't know if it isn't possible. On the TF700 it was only a line in the build.prop file that made the difference.
I would try it because now you have nothing and when it works you have the us version yes, but at least it works.
Click to expand...
Click to collapse
Already too late, it has been RMA'd, and then, I had nothing to flash it with.
Ikkerens said:
This guide worked fine for me; http://forum.xda-developers.com/showthread.php?t=2516215
It's only about what you do with the root ^^
Click to expand...
Click to collapse
Well I meant, what should a root user do to try and protect themselves against bricking their device like you did? Is it a matter of making sure that CWM or TWRP is on the device as a recovery partition? And are those available on TF701T yet?
Oh dear. That's a lot gone wrong.
Cwm is available and that works.
It's made by drgravy. I use it in my unbrick tut.
All i can say is, root --> cwm --> backup.
Sent from my GT-I9505 using xda app-developers app
That CWM wouldn't boot for me :/
Similar to the previous threads for OnePlus 5, OnePlus 5T or OnePlus 6, here are the necessary packages to unbrick/revive a hard bricked OnePlus 7 Pro.
The following hardware revisions are supported:
GM1910: China
GM1911: India
GM1913: Europe
GM1917: Global/US Unlocked
Download: https://www.androidfilehost.com/?w=files&flid=294744
guacamole_21_H.04_190416_unlocked.zip
After using it, the phone will be restored to HydrogenOS aka Chinese firmware.
Click to expand...
Click to collapse
guacamole_21_E.08_190515_unlocked.rar
After using it, the phone will be restored to OxygenOS 9.5.4.GM21BA aka European firmware.
Click to expand...
Click to collapse
guacamole_21_O.07_190512_unlocked.zip
After using it, the phone will be restored to OxygenOS 9.5.3.GM21AA aka global firmware.
Click to expand...
Click to collapse
In every case, it is possible to upgrade to latest OxygenOS by using full signed zip from this thread via Local Upgrade.
With the device powered off, hold Volume Up & Volume Down buttons to force it to boot to Qualcomm download mode.
Use the most updated signed driver (2.1.2.2 at this moment) to avoid potential issues..
For detailed procedures, please consult the linked threads above. There is no reason to repeat the same thing again.
Make sure the path of the extracted files doesn't contain any non-English character. The tool isn't unicode aware.
Source:
HydrogenOS package: 人艱不拆 (OnePlus China forum thread), @trollavin & @Some_Random_Username for the help in mirroring
OxygenOS (EU) package: @MrVoshel
OxygenOS (global) package: @Lucifer6
Reserved for future.
Thank you for this!!
Doesn't this leave you with a Chinese modem (limited LTE bands and roaming configs?) and critical partitions? Wouldn't an international or European tool be more suitable considering that Oxygen zips may not overwrite everything? Or is this just a temporary guide with what we have?
LLStarks said:
Doesn't this leave you with a Chinese modem (limited LTE bands and roaming configs?) and critical partitions? Wouldn't an international or European tool be more suitable considering that Oxygen zips may not overwrite everything? Or is this just a temporary guide with what we have?
Click to expand...
Click to collapse
Temp? yes and no, I would say. Better than warranty R&D in days no phone for use.
As far as you can revive the phone from QDL9008 back to HOS/OOS, you now have a chance Again to switch over whatever ROM or OS you want later on.
jkyoho said:
Temp? yes and no, I would say. Better than warranty R&D in days no phone for use.
As far as you can revive the phone from QDL9008 back to HOS/OOS, you now have a chance Again to switch over whatever ROM or OS you want later on.
Click to expand...
Click to collapse
Well, that's the perfect explanation.
:highfive:
Can you turn TMobile to int'l with this ?
HtcOnekid said:
Can you turn TMobile to int'l with this ?
Click to expand...
Click to collapse
What he said
When i start MsmdownloadtoolV4.0.exe it says :
Packet image not exist!
Take out the Chinese characters in the file name and then try
joemossjr said:
Take out the Chinese characters in the file name and then try
Click to expand...
Click to collapse
Yep that's i though, but i finaly looking for EU version. Because i think with OTA upgrade to GMBA EU modem will not contain the good modem right ?
---------- Post added at 12:59 AM ---------- Previous post was at 12:27 AM ----------
failed to install on EU model : param preprocessing and stop at 5 ou 7 sec before flashing. I tryed using anothere patched tool and not working :s
Please help me, I failed pretty hard and bricked my phone.
I rooted my phone with stock recovery using a patched magisk boot image and all went fine.
Today, I deviced to temporarily boot into twrp to check it out, so I booted into fastboot and used "fastboot boot twrp.img"
and booted into system. I was confused and rebooted but now I was stuck in stock recovery. So I completely flashed TWRP
on boot_a and boot_b and into TWRP I rooted my device. But even now I am always bootlooping into TWRP and can't
get my phone to boot into system.
I tried using the unbrick tool but my device won't show up on my computer, even with the driver installed.
I'm screwed, can someone help?
Can I somehow reflash the stock recovery and revert back to my patched boot image?
uniQ191 said:
Please help me, I failed pretty hard and bricked my phone.
I rooted my phone with stock recovery using a patched magisk boot image and all went fine.
Today, I deviced to temporarily boot into twrp to check it out, so I booted into fastboot and used "fastboot boot twrp.img"
and booted into system. I was confused and rebooted but now I was stuck in stock recovery. So I completely flashed TWRP
on boot_a and boot_b and into TWRP I rooted my device. But even now I am always bootlooping into TWRP and can't
get my phone to boot into system.
I tried using the unbrick tool but my device won't show up on my computer, even with the driver installed.
I'm screwed, can someone help?
Can I somehow reflash the stock recovery and revert back to my patched boot image?
Click to expand...
Click to collapse
what is your device OOS 9.5.3/4/5/6 ?
flash the co-responding stock boot.img from twrp with magisk zip together, and see if you can boot
uniQ191 said:
Please help me, I failed pretty hard and bricked my phone.
I rooted my phone with stock recovery using a patched magisk boot image and all went fine.
Today, I deviced to temporarily boot into twrp to check it out, so I booted into fastboot and used "fastboot boot twrp.img"
and booted into system. I was confused and rebooted but now I was stuck in stock recovery. So I completely flashed TWRP
on boot_a and boot_b and into TWRP I rooted my device. But even now I am always bootlooping into TWRP and can't
get my phone to boot into system.
I tried using the unbrick tool but my device won't show up on my computer, even with the driver installed.
I'm screwed, can someone help?
Can I somehow reflash the stock recovery and revert back to my patched boot image?
Click to expand...
Click to collapse
You havn't bricked your phone, just put it in fastboot mode and reupload boot image to the correct slot !
Regards,
thebigtross said:
You havn't bricked your phone, just put it in fastboot mode and reupload boot image to the correct slot !
Regards,
Click to expand...
Click to collapse
Thanks for your replies! I was on OOS 9.5.5 and I tried flashing the twrp/magisk zips but that didn't work either. I also tried applying the stock boot.img to the active slot, but still got the recovery bootloop.
So as my last hope, I wiped all data in recovery mode, rebooted to fastboot and sideloaded the complete stock image from here https://forum.xda-developers.com/oneplus-7-pro/how-to/rom-stock-fastboot-roms-oneplus-7-pro-t3931424
I reconfigured my phone from scratch, rooted with the patched boot image like before and everythings works now. Guess I will not bother with TWRP any time soon.
Added global and EU packages.
Titokhan said:
Added global and EU packages.
Click to expand...
Click to collapse
Will global work for 1911 (India)
Mr.Crucial said:
Will global work for 1911 (India)
Click to expand...
Click to collapse
Yes, the packages are interchangable.
[/COLOR]
Titokhan said:
Yes, the packages are interchangable.
Click to expand...
Click to collapse
But I think that these packages will not work on T-mobile 1915!
When I reboot into edl mode, it recognizes the "Qualcomm HS-USB QDLoader 9008", but then 10 seconds later, the phone automatically boots the the battery display, which disables edl. The same this happens whether I use the vol up+down and plug in, or `adb reboot edl`.
Edit: "How I learned to stop worrying and risk a brick"
Selecting the right COM and hitting start in MSMtool in that 10 second window kept it in edl mode for the duration of the flash.
I rooted my phone but didn't really like it while having my banking apps on it. So I tried to get back to normal but ended up wiping everything, even the OS, off of my phone. I am trying to get it back to normal. I followed one guide on here which gave me an android 10 ROM but I was unable to update it to the latest version. The link for that guide is: https://forum.xda-developers.com/mi-a2/how-to/guide-official-stock-android-10-t4033835. I didn't install the force encrypt or the magisk because I don't wanna root it. I just want it back to how it was before the root. So I am wondering if there is a way that I can get back to normal now. Thanks in advance for any advice.
Tyche303 said:
I rooted my phone but didn't really like it while having my banking apps on it. So I tried to get back to normal but ended up wiping everything, even the OS, off of my phone. I am trying to get it back to normal. I followed one guide on here which gave me an android 10 ROM but I was unable to update it to the latest version. The link for that guide is: https://forum.xda-developers.com/mi-a2/how-to/guide-official-stock-android-10-t4033835. I didn't install the force encrypt or the magisk because I don't wanna root it. I just want it back to how it was before the root. So I am wondering if there is a way that I can get back to normal now. Thanks in advance for any advice.
Click to expand...
Click to collapse
well what is the problem ? if it booted and you didn't flash magisk you are on stock. ...what exactly do you want ? to lock the bootloader or remove twrp custom recovery too ?
KevMetal said:
well what is the problem ? if it booted and you didn't flash magisk you are on stock. ...what exactly do you want ? to lock the bootloader or remove twrp custom recovery too ?
Click to expand...
Click to collapse
The ROM was an earlier version of android 10. But I am unable to install the latest updates for android 10 OTA. It's working but I would like to be able to receive updates again. If there is another ROM that would give me those results I would be fine with flashing that too.
Tyche303 said:
The ROM was an earlier version of android 10. But I am unable to install the latest updates for android 10 OTA. It's working but I would like to be able to receive updates again. If there is another ROM that would give me those results I would be fine with flashing that too.
Click to expand...
Click to collapse
the most likely issue is your recovery ... take the stock recovery from a fastboot stock rom and flash that with fastboot
also make sure to flash stock rom in both slot A & B then updates will work
go to this website
https://www.getdroidtips.com/xiaomi-mi-a2-stock-firmware/
download a PIE stock rom that is a FASTBOOT version ... download miflash ...follow instructions to flash it using miflash in fastboot mode
then boot & set it up ...it will start offering updates by itself
your problem right now is that you flashed stock rom in only one slot and you have a custom recovery so that is why it can't update
KevMetal said:
the most likely issue is your recovery ... take the stock recovery from a fastboot stock rom and flash that with fastboot
also make sure to flash stock rom in both slot A & B then updates will work
go to this website
https://www.getdroidtips.com/xiaomi-mi-a2-stock-firmware/
download a PIE stock rom that is a FASTBOOT version ... download miflash ...follow instructions to flash it using miflash in fastboot mode
then boot & set it up ...it will start offering updates by itself
your problem right now is that you flashed stock rom in only one slot and you have a custom recovery so that is why it can't update
Click to expand...
Click to collapse
Awesome, thanks! I will try that later tonight or tomorrow.
KevMetal said:
the most likely issue is your recovery ... take the stock recovery from a fastboot stock rom and flash that with fastboot
also make sure to flash stock rom in both slot A & B then updates will work
go to this website
https://www.getdroidtips.com/xiaomi-mi-a2-stock-firmware/
download a PIE stock rom that is a FASTBOOT version ... download miflash ...follow instructions to flash it using miflash in fastboot mode
then boot & set it up ...it will start offering updates by itself
your problem right now is that you flashed stock rom in only one slot and you have a custom recovery so that is why it can't update
Click to expand...
Click to collapse
So I downloaded a fastboot file from here :https://forum.xda-developers.com/mi-a2/how-to/fastboot-xiaomi-mi-a2-fastboot-images-t3824849
The miui flash program wouldn't work for me. On the website you linked me there was a method that used twrp to flash it. But when use twrp I can't see any of the zip files in twrp. I've tried three different ones from the link I just shared here. Not sure what the problem is.
KevMetal said:
the most likely issue is your recovery ... take the stock recovery from a fastboot stock rom and flash that with fastboot
also make sure to flash stock rom in both slot A & B then updates will work
go to this website
https://www.getdroidtips.com/xiaomi-mi-a2-stock-firmware/
download a PIE stock rom that is a FASTBOOT version ... download miflash ...follow instructions to flash it using miflash in fastboot mode
then boot & set it up ...it will start offering updates by itself
your problem right now is that you flashed stock rom in only one slot and you have a custom recovery so that is why it can't update
Click to expand...
Click to collapse
nevermind, I have gotten it to work. Thank you for your help
Tyche303 said:
nevermind, I have gotten it to work. Thank you for your help
Click to expand...
Click to collapse
okay glad you came right
half the fun is figuring this stuff out
Is there a way to restore my stock rooted phone to allow updated the latest stock OTA updates without having to reflash the whole previous stock ROM? With my previous MOT phones (Moto 2, Moto 3, Moto 4) all I had to do was restore stock recovery and logo and then reboot to allow OTA updates. But since there is no recovery.img in this phone's ROM xml then that option is out. It would be nice not have to restore everything from scratch in order to get the updates.
pastorbob62 said:
Is there a way to restore my stock rooted phone to allow updated the latest stock OTA updates without having to reflash the whole previous stock ROM? With my previous MOT phones (Moto 2, Moto 3, Moto 4) all I had to do was restore stock recovery and logo and then reboot to allow OTA updates. But since there is no recovery.img in this phone's ROM xml then that option is out. It would be nice not have to restore everything from scratch in order to get the updates.
Click to expand...
Click to collapse
Yup, If you are just rooted stock and have NOT installed the copy partions.ZIP... Boot to TWRP From FASTBOOT BACKUP your DATA to flash back after Install...Just the Data and install Magisk Uninstaller... After MAGISK unistall... Format DATA PARTITION ONLY...MAKE SURE YOU ARE ON BOOT SLOT A... Reboot to the SETUP WIZARD... STOP and reboot to bootloader.......HAVE STOCK BOOT IMG READY TO BOOT FROM CURRENT FIRMWARE... The STOCK installed boot img has the bootloader and modified devices flagged so that kills the OTA INSTALLATION.... If you have installed any modded logo.bin you have to replace it with STOCK on both logo_a and logo_b
fastboot --set-active=a
fastboot flash logo_a logo.bin
fastboot flash logo_b logo.bin
fastboot boot boot.img
DONT FLASH BOOT
it will trick the flags from trippin that stop the OTA
Setup the phone from setup wizard and it should automatically update the OTA so really its two updates....
Once its done reinstall TWRP and TWRP restore data then install Magisk reboot to your data rooted stock updated OTA
KtownJeff said:
Yup, If you are just rooted stock and have NOT installed the copy partions.ZIP... Boot to TWRP From FASTBOOT BACKUP your DATA to flash back after Install...Just the Data and install Magisk Uninstaller... After MAGISK unistall... Format DATA PARTITION ONLY...MAKE SURE YOU ARE ON BOOT SLOT A... Reboot to the SETUP WIZARD... STOP and reboot to bootloader.......HAVE STOCK BOOT IMG READY TO BOOT FROM CURRENT FIRMWARE... The STOCK installed boot img has the bootloader and modified devices flagged so that kills the OTA INSTALLATION.... If you have installed any modded logo.bin you have to replace it with STOCK on both logo_a and logo_b
fastboot --set-active=a
fastboot flash logo_a logo.bin
fastboot flash logo_b logo.bin
fastboot boot boot.img
DONT FLASH BOOT
it will trick the flags from trippin that stop the OTA
Setup the phone from setup wizard and it should automatically update the OTA so really its two updates....
Once its done reinstall TWRP and TWRP restore data then install Magisk reboot to your data rooted stock updated OTA
Click to expand...
Click to collapse
Thanks KtownJeff, that does sound much easier. Why aren't others posting this much simpler solution? Has anyone else tried this?
I haven't tried it yet as it looks like they may be about to figure out the low call volume issue in custom ROMs and then these OTA updates won't be necessary anyway? I'll wait and see what happens over the next week or so.
I'm wondering why it's necessary to wipe the data though. Why isn't uninstalling Magisk and booting with the original kernel enough?
JerseyChewi said:
Yeah the calling issue is just a lineage thing...and lineage is so generically lame. mokee or corvusos are my favs. Most of the custom Roms work well.... and there is a lot more ROMS for our device that is not on XDA.... The Data may be fine Just back it up first....and I put this on telegram and if you haven't checked it out there is five channels for our phone with tons of stuff.....more ROM builds We also have Pitch Black Recovery now available which is twrp with a cleaner UI and lots more options
Click to expand...
Click to collapse
KtownJeff said:
Yup, If you are just rooted stock and have NOT installed the copy partions.ZIP... Boot to TWRP From FASTBOOT BACKUP your DATA to flash back after Install...Just the Data and install Magisk Uninstaller... After MAGISK unistall... Format DATA PARTITION ONLY...MAKE SURE YOU ARE ON BOOT SLOT A... Reboot to the SETUP WIZARD... STOP and reboot to bootloader.......HAVE STOCK BOOT IMG READY TO BOOT FROM CURRENT FIRMWARE... The STOCK installed boot img has the bootloader and modified devices flagged so that kills the OTA INSTALLATION.... If you have installed any modded logo.bin you have to replace it with STOCK on both logo_a and logo_b
fastboot --set-active=a
fastboot flash logo_a logo.bin
fastboot flash logo_b logo.bin
fastboot boot boot.img
DONT FLASH BOOT
it will trick the flags from trippin that stop the OTA
Setup the phone from setup wizard and it should automatically update the OTA so really its two updates....
Once its done reinstall TWRP and TWRP restore data then install Magisk reboot to your data rooted stock updated OTA
Click to expand...
Click to collapse
WHHAAAT?? I got a few questions...
Why is it important not to have the copy-partitions.zip installed?
Why you should be on slot _a?
There is no need to boot the boot.img instead of flashing it. The Magisk uninstaller restores exactly the same boot.img as you can find in the firmware zip. Your device isn't able to store any data on that image.
Sorry, but this is the most complicate way for an OTA I have ever red. You could sum up these steps to "flash the stock firmware". In the end the result is the same. But it's much easier.
WoKoschekk said:
There is no need to boot the boot.img instead of flashing it. The Magisk uninstaller restores exactly the same boot.img as you can find in the firmware zip. Your device isn't able to store any data on that image.
Click to expand...
Click to collapse
Sooo... assuming you haven't changed the logo then all you need to do is uninstall Magisk? Why do you need to flash the stock firmware then?
WoKoschekk said:
Sorry, but this is the most complicate way for an OTA I have ever red. You could sum up these steps to "flash the stock firmware". In the end the result is the same. But it's much easier.
Click to expand...
Click to collapse
It seems a lot less risky to me. Flashing all those different partitions makes me nervous.
JerseyChewi said:
Sooo... assuming you haven't changed the logo then all you need to do is uninstall Magisk? Why do you need to flash the stock firmware then?
Click to expand...
Click to collapse
Assuming this is not your first time flashing the firmware and you already have a flash script/.bat file:
1. run the script
Done! One command and 5 min later you are on the latest firmware.
JerseyChewi said:
It seems a lot less risky to me. Flashing all those different partitions makes me nervous.
Click to expand...
Click to collapse
Motorola provides you OEM signed images and a .xml sheet with proper commands to flash them as a .zip file. I've never heard that someone bricked his device by using the manufacturer's recommended way. I think it's risky to use your own workaround just because you're nervous about it.
Even if you unplug the device in the middle of the flashing process you won't face any trouble. Every single flashing command loads the image into your device's RAM before it gets written to the device.
fastboot oem fb_mode_set = no matter what reboot command you run your device boots into bootloader
Why are you nervous about it?
Why is it important not to have the copy-partitions.zip installed?
Ok so the copy partitons zip is only supposed to be installed when you install the first custom rom coming from original stock..... because it breaks the chain for OTA from motorola.... If you root stock and flash recovery only Its not necessary.... so that way when OTA comes it will move to the B partition the way that it was intended to.....but the boot-loader is unlocked now both slots start with a boot-loader, bootloader_a and bootloader_b.. .and the on board preboot chip will trip the first flag that communicates with stock flashed boot image which also holds the recovery and the kernel... even if its backed up stock.img with magisk, it will break the next flag on the device along with the custom logo.bin.... now the custom logo if it is cloned with a moto signature official it wont matter and the only one Im aware is logo.bin for the TMOBILE REVVLY variant.... when you boot not flash the stock boot.img it bypasses the security chain until reboot.... I've flashed b slot on accident and then booted several GSI and other lake Roms and at some point ill notice on the bootloader screen that maybe i have April 2020 when Im running July 2020 version....which is headache to fix and i booted to b slot flash stock as normal let boot to the setup wizard then reverse to a and do it again because it brings it back together... now the mapping for the AB partition with duel slots t is standard for all ARM64 AB devices Bootloader a and b Boot a and b Radio a and b which is (firmeware) slot Vendor a and b System a and b....
https://www.xda-developers.com/how-...ess-updates-affect-custom-development-on-xda/
the reason why I wrote it the way that I did was because I tried everything to OTA back and this was the only way it worked for me.... and trust me I stayed up for weeks trying to break it or fix it....I finally I came across a moto g6 thread where some one relocked there bootloader and didnt have the oem unlock set and they couldnt do anything to unlock it again using fastboot because the switch was grey out on developer options which means they couldnt root to fix..., I believe it was Sd_shadow that recommended trying to boot the boot.img like how we boot the twrp.img because it bypasses the security flag... well my first attempt it didn't work which led me to the mismatched boot-loaders and I kept at it and by process of elimination and fully learning the way these partitions communicate..... which is totally backwards from the way it used to be... If u leave data then flash back stock, the boot-loader thinks its fresh but finds its not......so boot-loop... tried it cussed and tried again and screamed but now its automatic. for me because of trial and error... I've been at this a few years now and I'm learning something new all the time and most of time when people don't post is because they either don't know or don't wanna give wrong info or maybe nobody showed them. There kinda is an unwritten bylaw at XDA (tough love)... you gotta learn by experience that way when get an opportunity to help or find a new way it makes it worth the stress
That is why I wrote it the way I did step by step in the easiest way possible because of my experiences and headaches...If it don't work you didn't follow directions.... Now I'm gonna tell you I re-locked my bootloader too and was not able to flash back ota don't even try its a waste of time because the only way to get that flag back is to re ball a chipset, or replace the motherboard, or buy a new phone....
Quoteriginally Posted by WoKoschekk
Sorry, but this is the most complicate way for an OTA I have ever red. You could sum up these steps to "flash the stock firmware". In the end the result is the same. But it's much easier.
I
Our device is unbreakable... trust me I've tried to and still haven't managed to Qualcomm brick it.... test point is the only way to get it to EDL mode and i plan on taking my screen off tonight just to see if I can..... and write another essay because some ass hole from Germany thinks he know everthing
KtownJeff said:
Why is it important not to have the copy-partitions.zip installed?
Ok so the copy partitons zip is only supposed to be installed when you install the first custom rom coming from original stock..... because it breaks the chain for OTA from motorola.... If you root stock and flash recovery only Its not necessary....
Click to expand...
Click to collapse
First of all the copy-partions.zip is a simple dd command script packed with flashize to flash it through TWRP. It determines the active slot and copies your essential partitions to the inactive one in case they were left blank by your manufacturer. You should have a look inside it.
Also there is no complicated chain of safety for OTAs. When a device powers on, the bootloader first checks if a device is locked or unlocked. If a device is unlocked, the bootloader shows the user a warning and then proceeds to boot even if the loaded OS isn't signed by the root of trust.
If the device is locked, the bootloader goes through the steps in Verifying Boot to verify the device's software.
Magisk hides the unlock state to pretend a trustworthy environment. That's the reason why OEM unlocking option is active and OTA updates start to install. But OTA update files verify your system's integrity by calculating checksums for each partition. This check fails with a active Magisk installation and update process ends with an error.
A preboot chip or sth like this is not in use on Moto devices. Partitions 1-14 (+/-) are defined as your bootloader. A prebootloader does only exist for MediaTek devices but not for SnapDragon.
There's a lot of official documentation about all the stuff...
In my opinion the easiest way to update your device is to flash the stock ROM. One script and it's done. No need to flash this and boot that only to be able to download the OTA which hasn't been installed until then. Your system takes more time to flash the OTA update then fastboot takes to flash the firmware.
BTW: You can call me what you want but that doesn't make your statements right either.
WoKoschekk said:
First of all the copy-partions.zip is a simple dd command script packed with flashize to flash it through TWRP. It determines the active slot and copies your essential partitions to the inactive one in case they were left blank by your manufacturer. You should have a look inside it.
Also there is no complicated chain of safety for OTAs. When a device powers on, the bootloader first checks if a device is locked or unlocked. If a device is unlocked, the bootloader shows the user a warning and then proceeds to boot even if the loaded OS isn't signed by the root of trust.
If the device is locked, the bootloader goes through the steps in Verifying Boot to verify the device's software.
Magisk hides the unlock state to pretend a trustworthy environment. That's the reason why OEM unlocking option is active and OTA updates start to install. But OTA update files verify your system's integrity by calculating checksums for each partition. This check fails with a active Magisk installation and update process ends with an error.
A preboot chip or sth like this is not in use on Moto devices. Partitions 1-14 (+/-) are defined as your bootloader. A prebootloader does only exist for MediaTek devices but not for SnapDragon.
There's a lot of official documentation about all the stuff...
In my opinion the easiest way to update your device is to flash the stock ROM. One script and it's done. No need to flash this and boot that only to be able to download the OTA which hasn't been installed until then. Your system takes more time to flash the OTA update then fastboot takes to flash the firmware.
Click to expand...
Click to collapse
KtownJeff said:
Yes correct it easier to flash rom after it is available for download with a month behind....
Click to expand...
Click to collapse
You should check your sources.
KtownJeff said:
Quoteriginally Posted by WoKoschekk
Sorry, but this is the most complicate way for an OTA I have ever red. You could sum up these steps to "flash the stock firmware". In the end the result is the same. But it's much easier.
I
Our device is unbreakable... trust me I've tried to and still haven't managed to Qualcomm brick it.... test point is the only way to get it to EDL mode and i plan on taking my screen off tonight just to see if I can..... and write another essay because some ass hole from Germany thinks he know everthing
Click to expand...
Click to collapse
I also want to leave my device in oem_locked state and not in flashing_locked
Holy Moly! Come on guys! I only wanted a way to fix OTA on my rooted stock installation without having to do a complete stock reinstall. At the time I asked the question, the newest full stock ROM update was not yet available. It is now. My point was I didn't like going through a complete reinstall of my apps and settings, Backing up my Data partition then trying to restore it has never seemed to work for me. Anyway you all need to just chill and put your egos away.
pastorbob62 said:
Holy Moly! Come on guys! I only wanted a way to fix OTA on my rooted stock installation without having to do a complete stock reinstall. At the time I asked the question, the newest full stock ROM update was not yet available. It is now. My point was I didn't like going through a complete reinstall of my apps and settings, Backing up my Data partition then trying to restore it has never seemed to work for me. Anyway you all need to just chill and put your egos away.
Click to expand...
Click to collapse
The fact is you need to restore everything back to stock for an OTA. This includes a deinstallation of Magisk (also modules are gone) and restore your stock boot.img with the stock recovery. Then you download and install the OTA, go back to fastboot mode and start installing TWRP and everything else.
This was option 1.
Option 2: Download the latest firmware on Telegram (only possible with your device!) or install LMSA tool, which also downloads the latest build. Boot into fastboot, flash the firmware (without erase userdata) and boot TWRP. Flash TWRP installer and Magisk. Done!
WoKoschekk said:
The fact is you need to restore everything back to stock for an OTA. This includes a deinstallation of Magisk (also modules are gone) and restore your stock boot.img with the stock recovery. Then you download and install the OTA, go back to fastboot mode and start installing TWRP and everything else.
This was option 1.
Click to expand...
Click to collapse
I'm thinking not, since this was the first thing I tried when I got the notification for the update. And the update still failed.
WoKoschekk said:
Option 2: Download the latest firmware on Telegram (only possible with your device!) or install LMSA tool, which also downloads the latest build. Boot into fastboot, flash the firmware (without erase userdata) and boot TWRP. Flash TWRP installer and Magisk. Done!
Click to expand...
Click to collapse
Telegram didn't have it when I installed the update. LMSA kept giving me a "Decompression failed" error message. So I just reinstalled the stock version I was already on and allowed the update to complete. Then reinstalled TWRP and Magisk without any issues once I had all of my apps and data restored.
Not taking any offense here, but I am not a noob and while I didn't give all of the details to what I had tried I also didn't want to reinvent the wheel. I didn't think about eliminating the line "erase userdata". Since it was very simple with previous devices to do it I knew there had to be an easier way. By the way, the XT1965-2_LAKE_RETLA_10_QPWS30.61-21-14_subsidy-DEFAULT_regulatory-XT1965-2-SUTEL-DS_CFC.xml.zip verson of the ROM is now available here: https://mirrors.lolinet.com/firmware/moto/lake/official/
pastorbob62 said:
Telegram didn't have it when I installed the update.
...
By the way, the XT1965-2_LAKE_RETLA_10_QPWS30.61-21-14_subsidy-DEFAULT_regulatory-XT1965-2-SUTEL-DS_CFC.xml.zip verson of the ROM is now available here: https://mirrors.lolinet.com/firmware/moto/lake/official/
Click to expand...
Click to collapse
The mentioned firmware is available on Telegram since Sep 03. Screenshot
Telegram group: https://t.me/s/motoupdatestracker
WoKoschekk said:
The mentioned firmware is available on Telegram since Sep 03. Screenshot
Telegram group: https://t.me/s/motoupdatestracker
Click to expand...
Click to collapse
That's nice. But the one for my phone was not available on tracker until the day after I updated via OTA.
KtownJeff said:
Yup, If you are just rooted stock and have NOT installed the copy partions.ZIP... Boot to TWRP From FASTBOOT BACKUP your DATA to flash back after Install...Just the Data and install Magisk Uninstaller... After MAGISK unistall... Format DATA PARTITION ONLY...MAKE SURE YOU ARE ON BOOT SLOT A... Reboot to the SETUP WIZARD... STOP and reboot to bootloader.......HAVE STOCK BOOT IMG READY TO BOOT FROM CURRENT FIRMWARE... The STOCK installed boot img has the bootloader and modified devices flagged so that kills the OTA INSTALLATION.... If you have installed any modded logo.bin you have to replace it with STOCK on both logo_a and logo_b
fastboot --set-active=a
fastboot flash logo_a logo.bin
fastboot flash logo_b logo.bin
fastboot boot boot.img
DONT FLASH BOOT
Click to expand...
Click to collapse
I tried this to go back to stock rom from LOS17.
With : fastboot --set-active=a
I have this error :
(bootloader) slot-suffixes: not found
error: could not get suffixes
Any idea of what it means ?
Many thanks
[email protected] said:
I tried this to go back to stock rom from LOS17.
I've never seen that error before have you tried google search for the error?
Click to expand...
Click to collapse
[email protected] said:
I tried this to go back to stock rom from LOS17.
With : fastboot --set-active=a
I have this error :
(bootloader) slot-suffixes: not found
error: could not get suffixes
Any idea of what it means ?
Many thanks
Click to expand...
Click to collapse
Don't know what your error means, but flash the stock ROM and it should be fine.
Hey everyone
I recently got this phone and went through the bootloader unlock process.
I then tried to follow the instructions on this page https://wiki.pixelexperience.org/devices/rosemary/install/ to get this rom installed but somehow ****ed it up.
Everything went well until I tried to flash the recovery img from this page: https://get.pixelexperience.org/rosemary (i downloaded the 13 plus recovery img).
I flashed the img via fastboot but after that I got stuck in fastboot. The phone is stuck in a bootloop when I try to reboot into recovery or normal boot. The only thing I can get back into is fastboot.
Would really appreciate any help to get the phone working again. Im not new to android custom roms but Im new to xiaomi phones and Im a little lost
Thanks.
OK nevermind I successfully got the phone booting again with miflash tool by reflashing an official firmware...
Greetings!
You can install the rom via adb sideload too. Put on some random recovery (see my tutorial here: https://forum.xda-developers.com/t/twrp-on-android-12.4522273/), and start adb sideload.
Then,
adb sideload insert_package_name.zip
Click to expand...
Click to collapse
Hope it helps! ; D
dona3000 said:
Hey everyone
I recently got this phone and went through the bootloader unlock process.
I then tried to follow the instructions on this page https://wiki.pixelexperience.org/devices/ros mary/install/ to get this rom installed but somehow ****ed it up.
Everything went well until I tried to flash the recovery img from this page: https://get.pixelexperience.org/rosemary (i downloaded the 13 plus recovery img).
I flashed the img via fastboot but after that I got stuck in fastboot. The phone is stuck in a bootloop when I try to reboot into recovery or normal boot. The only thing I can get back into is fastboot.
Would really appreciate any help to get the phone working again. Im not new to android custom roms but Im new to xiaomi phones and Im a little lost
Thanks.
Click to expand...
Click to collapse
Did u make sure ur on Miui 12.5.16.0.RKLMIXM?
I'm also having similar problem and circumstance, may I ask where did you find the official firmware and/or recovery img for the Redmi note 10s
fol!s said:
I'm also having similar problem and circumstance, may I ask where did you find the official firmware and/or recovery img for the Redmi note 10s
Click to expand...
Click to collapse
Greetings!
As this phone has an MTK processor, we don't really have a recovery image, it's stored in the boot img I suppose. That link, you can download the official rom to this. DISCLAIMER: There are two types of ROMs listed here, one type is fastboot, that you need now in order to flash it through a computer for example. The another type is the recovery rom, that you can flash from recovery like a magisk package, or anything flashable zip, or with adb sideload.
https://mifirm.net
You should choose global if you are in Europe, but it's suitable for devices in the US or USA probably, ony feature differences are here between an EEA and Global rom.
Also, if you install pixel experience recovery, you can install the firmware by going into recovery, and do it via sideload. Or, you can try flashing the rom with TWRP (tutorial linked below), but then you won't able to install updates automatically.
One question: Did you checked in OEM unlocking in developer options before flashed PE?
Hope it helps!
Yeah, I did checked the oem unlocking. I think the reason why i failed because my bootloader probably updated and I forgot to check. You need bootloader version 12.5.16.0.RKLMIXM to install the pixel experience. Also thank for help
Greetings!
You can install the rom via adb sideload too. Put on some random recovery (see my tutorial here: https://forum.xda-developers.com/members/gurtnyi.11842195), and start adb sideload.
Then,
adb sideload insert_package_name.zip
Hope it helps! ; D
Click to expand...
Click to collapse
Can I do that on newer firmware or should I roll back to version 12.5.16.0.RKLMIXM? And if I roll back then I need to unlock device again?
I think you can. I've flashed it successfully on the latest version too. Currently I don't use PE but it was good for me.
Well, regarding to the unlock, it's not a big deal, you don't have to wait 168h again, once you've firstly unlocked your device, you can re-unlock it again, and again, no matter how many times, you don't have to wait a lot again.
But depending on how you rollback it,
I mean, with xiaomi flasher (i think that's its name) you can choose between clean all and lock, save userdata, and clean all, but in the first case, it'll lock back the bootloader. With SP flash tool (if you need, I can provide a link for the modified version of it, that doesn't require an auth file, but if fails, you need a python script, I can link that too), as I remember it won't lock back the device, but I'm not a 100% sure
Hope it helps!
Can you repair link to totorial https://forum.xda-developers.com/members/gurtnyi.11842195 doesn't seem to work.
raven17a said:
Can you repair link to totorial https://forum.xda-developers.com/members/gurtnyi.11842195 doesn't seem to work.
Click to expand...
Click to collapse
Corrected, thank you!
Thank you! I managed to install PE by rolling back to MIUI 12.5. Sideload unfortunatly not working on stock recovery.
raven17a said:
Thank you! I managed to install PE by rolling back to MIUI 12.5. Sideload unfortunatly not working on stock recovery.
Click to expand...
Click to collapse
Happy to hear that!
By the way, yes, pe recovery is better for sideloading, or eventually any not stock recovery. Also, if you install PE recovery, you can apply updates automatically, and in the future you won't need to flash it manually.