*** Use this at your very own risk.
*** You will lose all data
*** Backup your working modemst1/2 and persist. If you lose these for any reason, it's unique to your device and not recoverable if you didn't back up (via MSM or other people).
*** Read the entire post and follow the steps closely before asking for help. Post all error messages and steps you took. If you just ran a bunch of unknown commands, I would tell you to MSM.
*** Know how to use the MSMTool, Don't start before figuring it out. https://forum.xda-developers.com/t/op9pro-repository-of-msm-unbrick-tools-tmo-glo-in.4272549/
*** DO NOT ATTEMPT THIS IF YOU ARE NOT FAMILIAR WITH ANY STEP DESCRIBED IN THIS GUIDE
General notes:
NR and LTE bands are read only and not modifiable, not in modem.img or any other partition. You cannot get global bands by flashing a global ROM, nor can you lose TMO bands by flashing another ROM.
If you wish to unlock the bootloader without unlock_code.bin, you MUST do it from OOS11. If you upgrade to OOS12/OOS13, you will need the unlock_code.
The T-Mobile NON-HLOS is no longer necessary as of OOS13 release. If you must stay on OOS11 or OOS12, make a backup of the T-Mobile modem partition for the OOS version you want to stay on.
Dual-SIM does not work.
Prerequisites:
This conversion will not SIM unlock you. You can only SIM unlock on a T-Mobile ROM, meaning if you want to do that in the future, you must go back to a TMO ROM (and wipe)
Familiarity with MSMDownload tools. If the regular MSM tool doesn't work for you, turn back now.
Back up all data, it will be wiped.
Download:
Conversion: AndroidFileHost (MD5: 8cc3e5e81d15e28bb10dc5f1e7bd4133)
Steps:
Run the MSM file normally.
Unlock your bootloader if necessary. Now is the time if you don't have unlock.bin
Patch up to Android 13 while on Wifi if your mobile data doesn't work. Use this time to go to another variant (GLO, IN, etc) as needed.
Fastboot method:
* The steps in this guide will convert your TMO LE2127 to EU 11.2.3.3. This is intentionally not the latest version to force you to take a FULL OTA.
* You must already have the bootloader unlocked with an unlock_code.bin
* You can use this guide to convert to your own variant by extracting payload and flashing from a full OTA. No support will be given if you choose to manually do it.
* Use the latest platform tools: https://developer.android.com/studio/releases/platform-tools. DO NOT USE MINIMAL ADB, it has not been updated for years.
* Fastboot can't see your device? https://forum.xda-developers.com/t/...stboot-mode-windows-10.4194491/#post-84943553
* Test that you can boot to fastbootd prior to starting, "fastboot reboot fastboot" and you should see the OnePlus logo with the text "fastbootd" on top. Do not continue if this doesn't work.
* When encountering issues, describe all steps you took, paste any outputs, and take screenshots. Make sure to include the output of fastboot --version in your post.
Steps to convert your device to EU
You need your device bootloader and SIM unlocked. See https://forum.xda-developers.com/t/how-to-unlock-the-t-mobile-bootloader.4256319/
Download and unzip the conversion package:
EU 11.2.3.3
MD5: cb949816fa80d5f0d984359b819426c3
Boot to bootloader.
From adb:
Code:
adb reboot bootloader
From fastboot/bootloader:
Code:
fastboot reboot bootloader
Execute "flash_all.bat" from the unzipped directory from step 2.
Reboot into recovery, and wipe everything.
Once fully booted, connect to WiFi and download Oxygen Updater and take the FULL OTA (11.2.4.4 as of this writing)
Do a regular reboot, don't reboot to fastbootd, bootloader, recovery, etc. Reboot to system.
Reboot into bootloader or fastbootd, and flash the T-Mobile modem.
Code:
fastboot flash modem NON-HLOS.bin
After each Full OTA you take in the future, you will need to repeat step 7 & 8
FAQ
Q: The most recent version is 11.2.4.4, why is this guide converting to 11.2.3.3?
A: You didn't read the full post.
Q: Why is there no conversion to Global?
A: Global variant uses the Google incremental OTA server, and full OTAs are not always provided. There's no functional difference, and EU has better privacy requirements anyways. You can do it manually by extracting payload.bin and running the same flash script. No support will be provided if you choose to flash to Global.
Q: Can I re-lock the bootloader after conversion?
A: While you can go ahead lock your bootloader after conversion, I don't recommend it as you will not be able to take incremental OTA due to modem changes, and lose connectivity if you take a full OTA. To fix it, you need to unlock the bootloader and end up wiping.
Q: Where is the Linux guide?
A: Too lazy, if you're using Linux, you can make your own bash script from the Windows batch script.
Q: Help, I see is 'fastboot' is not recognized as an internal or external command.
A: Your fastboot.exe is not in your $PATH. You can either drop fastboot into the same folder as flash-all.bat, or you can fix your $PATH
Q: Help, I cannot boot to fastbootd because previous flashes messed things up.
A: MSM
Q: Help, "not enough space to resize [system, product, system_ext]"
A: MSM. If the error is on Vendor, it might still work and boot with a generic Android boot logo. If so, take the full OTA as described in the guide.
Q: Help, something went wrong!
A: Post in here the starting state of your device (Device model, ROM version, etc), all steps you've taken since unlocking bootloader, and the output of whatever is causing you trouble. Chances are, the answer is MSM, but read my MSM warning.
Q: Help, I see "Invalid sparse file format at header magic"
A: Ignore this message, not an error
Fixing the About Phone page
These steps are optional, and is only applicable for OOS11. It will fix the "About Phone" page. There are no performance differences. All that's done is change build.prop to reflect the correct model.
You need to rooted with Magisk
Download and install the magisk module: here
Reboot, the About Phone page is filled out.
Instructions to Bootloader Unlock a SIM locked device:
In ADB:
Code:
adb shell pm uninstall -k --user 0 com.qualcomm.qti.uim
Reboot
Go to dev settings and enable OEM Unlock
Reboot to bootloader
Code:
fastboot oem unlock
No unlock.bin needed
Issues so far (please post if you run into more):
If your mobile data doesn't work on OOS13, PM me details including HW Revision in About Phone.
What appears to work:
Everything else.
Much appreciation for everyone that help develop and test
@razercortex
@retryfail
@amaroney55
I went straight to the 11.2.4.4 as well, instead of the 11.2.3.3. Probably why I had such an issue also. Dummy me, wanted the latest and greatest right away and paid the price for it.
Goodness man. Presently I see where I wrecked. I did the EU 11.2.4.4 and not the 11.2.3.3. much obliged for this and clearing that up. Likewise, thank you again for assisting me with saving my mobile. JBBattery
Woohoo! Thank you!!
for some reason my Wildvine downgrades to L3, not sure how to fix it, also as other post indicates, voice mail on dialer doesn't work
avid_droid said:
It says to have magisk hiding from Google play services. Have you done that?
Click to expand...
Click to collapse
Yes, I toggled all options under google play services, no luck
{
"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"
}
ok going to give this a go later fingers crossed and just to clarify i only need to backup ModemST1 and ModemST2 img correct?
avid_droid said:
Nope. TRied again and its a no go since every damn thing is failing. fastboot mode and fastbootd is constantly failing on every file thats being flashed. What you need from me.?
Click to expand...
Click to collapse
you mind pasting some errors here? maybe the 1st error you got from cmd
Ultraman666 said:
ok going to give this a go later fingers crossed and just to clarify i only need to backup ModemST1 and ModemST2 img correct?
Click to expand...
Click to collapse
Persist
avid_droid said:
Nope. TRied again and its a no go since every damn thing is failing. fastboot mode and fastbootd is constantly failing on every file thats being flashed. What you need from me.?
Click to expand...
Click to collapse
* Test that you can boot to fastbootd prior to starting, "fastboot reboot fastboot" and you should see the OnePlus logo with the text "fastbootd" on top. Do not continue if this doesn't work.
* When encountering issues, describe all steps you took, paste any outputs, and take screenshots. Make sure to include the output of fastboot --version in your post.
Sounds like you tested that fastboot can't get you to fastbootd, but you continued anyways.
If you want troubleshooting, post the information I said to post
craznazn said:
Persist
Click to expand...
Click to collapse
Thanks for the hint, I backed up the persist.img but that's after root/unlock bl, so you are saying flash persist.img will get me back to L1?
avid_droid said:
everything fails in flashing. it just says FAILED on every .img that is being pushed. Im so confused. It says be in bootloader,but isnt it supposed to be in fastbootd???
Im still getting no response from fastboot reboot fastboot. Only way i can get into fastbootd is by adb reboot fastboot.
Which is it? in bootloader or fastbootd??
Click to expand...
Click to collapse
avid_droid said:
fastboot --version says unkown option
Click to expand...
Click to collapse
sounds to me like you don't get the proper version of fastboot, one thing to notice, if you install the one plus driver you may get the fastboot from C:\Android, DONT use this one. either put the correct platform-tool path to your $PATH or manually modify every fastboot.exe to be full path in script
sunxutian said:
Thanks for the hint, I backed up the persist.img but that's after root/unlock bl, so you are saying flash persist.img will get me back to L1?
Click to expand...
Click to collapse
No, persist just unique to your device. You just need a backup in case yours get wiped for any reason.
Honestly, you are the 2nd person I've heard from that had the L1 issue and we were never able to figure it out. I did these steps to 2 different devices and both kept L1. Does safetynet pass? Do you have magisk canary?
craznazn said:
No, persist just unique to your device. You just need a backup in case yours get wiped for any reason.
Honestly, you are the 2nd person I've heard from that had the L1 issue and we were never able to figure it out. I did these steps to 2 different devices and both kept L1. Does safetynet pass? Do you have magisk canary?
Click to expand...
Click to collapse
Yes, my safetynet passes and I do have magisk canary
avid_droid said:
I have it in C: and am opening powershell from that folder
Click to expand...
Click to collapse
Download a fresh copy of platform tools and unzip it into the folder that has flash_all.bat and .img files
craznazn said:
No, persist just unique to your device. You just need a backup in case yours get wiped for any reason.
Honestly, you are the 2nd person I've heard from that had the L1 issue and we were never able to figure it out. I did these steps to 2 different devices and both kept L1. Does safetynet pass? Do you have magisk canary?
Click to expand...
Click to collapse
what I suspect might be wrong is when I did the BL unlock I use fastboot oem unlock while some people use fastboot flashing unlock (not sure this makes any difference or not)
I did oem unlock, shouldn't make a difference
From that folder, run fastboot --version and share the screenshot
craznazn said:
I did oem unlock, shouldn't make a difference
Click to expand...
Click to collapse
Then anything I can try?
sunxutian said:
Then anything I can try?
Click to expand...
Click to collapse
Hmm, also try the fix about page magisk module, shouldn't affect anything but you never know.
If that doesn't fix it, take the 11.2.4.4 OTA again via local update, and then lock the bootloader and check. You won't have a working modem but I want to make sure your wildvine keys are still there.
Related
Code:
#include
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired. Please
* do some research if you have any concerns about features included in this Recovery
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*/
{
"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"
}
Team Win Recovery Project 3.x, or twrp3 for short, is a custom recovery built with ease of use and customization in mind. Its a fully touch driven user interface no more volume rocker or power buttons to mash. The GUI is also fully XML driven and completely theme-able. You can change just about every aspect of the look and feel.
[/CENTER]
Credits:
- TWRP Team
Device: Lenovo Tab3 7 Tablet - TB3-730X
Do not flash this on TB3-730F. The F model has different chipset and this recovery will softbrick it.
@sun_dream reported that 730F is working. So you can probably flash it, but be prepared with OFW, in case something goes wrong.
Instructions:
IMPORTANT: read all instructions at least once, before starting.
Note: If you're are a newbie, you can read more detailed instructions by honzazkrumlova here
- Download from link below.
- Enable "USB debugging" from developer options.
- Enable "OEM Unlocking" from developer options.
- Reboot device in Fastboot Mode (Bootloader mode), either with "adb reboot bootloader" or with VolDown+Power, to enter Recovery mode and then select "Reboot into bootloader"
- Unlock the bootloader with "fastboot flashing unlock" or "fastboot oem unlock" and follow the instructions on the tablet. (WARNING: This will erase all your data - Factory Reset)
- Once unlocked, you can use "fastboot boot TWRP_3.0.2_Lenovo_TB3-730X_Android-6.0_recovery.img" to start TWRP.
- When TWRP ask to modify system partition, answer "NO". Otherwise you will soft-brick your device and you will have to flash the original firmware and start from the beginning.
- If you want root - flash SuperSU, or as the user @Kellicros reported, you can flash Magisk 11.1.
- If you want XPosed, get it here.
- If you want to permanently flash the recovery, use "fastboot flash recovery TWRP_3.0.2_Lenovo_TB3-730X_Android-6.0_recovery.img".
- If you use it on any other Lenovo Tab3 7 device, please post the model.
- Thanks is always welcome.
Downloads:
TWRP_3.0.2_Lenovo_TB3-730X_Android-6.0_recovery.zip (well tested, consider it stable)
TWRP_3.1.1_Lenovo_TB3-730X_Android-6.0_recovery.zip
Unbrick your device:
Follow this thread
Hello
I have the same tablet (TB3-730X) and I tried this recovery, but something I did wrong.
Recovery by my works without problems, but now I can no longer boot into the system, I probably deleted it ...
After restarting the tablet always I return to Recovery and you can not flash the firmware because they can not find a version of the 730X (MTK MT8735P)
Can I use the firmware version for TB3-710 or 730F (MTK MT8161P)
Thanks for any advice, and thanks for Recovery.)
beldy said:
Hello
I have the same tablet (TB3-730X) and I tried this recovery, but something I did wrong.
Recovery by my works without problems, but now I can no longer boot into the system, I probably deleted it ...
After restarting the tablet always I return to Recovery and you can not flash the firmware because they can not find a version of the 730X (MTK MT8735P)
Can I use the firmware version for TB3-710 or 730F (MTK MT8161P)
Thanks for any advice, and thanks for Recovery.)
Click to expand...
Click to collapse
Hi.
When TWRP is started for the first time, it asks to modify the system partition.
I answered NO, NEVER. I saw some posts about other MTK devices and other people seems to have problems like yours when TWRP modify the system partition.
Is this your case?
If yes, then you need to download the original firmware and flash it on the device. After that you need to flash the recovery again.
I've downloaded the original firmware from Russian forum (this post: http://4pda.ru/forum/index.php?showtopic=731493&st=20#entry52434543). Here is direct link: https://cloud.mail.ru/public/Fjd9/u7e8mUbhq )
This is the last TB3-730X firmware. Do not try 710 firmwares, they should not work and it is probably dangerous to flash it. I dont know for 730F, this one could work, but anyway, download the the 730X firmware from the link above.
I guess you will need the SPFlash Tool to flash the firmware.
Hope this helps.
Thank you for the link ...
so probably it is my case that TWRP modify the system partition ... try this firmware and send the result ..
Thanks again for your help, I appreciate it.
I can confirm that Tab3 730x is checking if even TWRP is running (fastboot boot twrp.bin) and delete/modify system partition. TWRP not ask for modify system partition after first boot. Tablet stay on Lenovo logo forever. My firmware version is TB3-730X_S030_160509_ROW. Also in my model is not possible to read/write flash by FlashTool. I always get error 0x7D4, no matter what version I use, even after unlock bootloader. I have also try descibed firmware TB3-730X_S033_160707_ROW but this one cannot be flashed in fastboot mode. It says wrong binary (all files have in name _signed so probably different structure). It's seems that Polish Tab3 tb3-730X tablets are better protected than Russian.
0xAF can You post link to FlashTool what you used to flash your tablet?
[EDIT]
This time i get it working 0xAF are you mean first screen when TWRP start and there is swipe button? I Always swipe and this killed system partition I think. Btw do you both can flash this tablet with FlashTool?
DonKapselo said:
I can confirm that Tab3 730x is checking if even TWRP is running (fastboot boot twrp.bin) and delete/modify system partition. TWRP not ask for modify system partition after first boot. Tablet stay on Lenovo logo forever. My firmware version is TB3-730X_S030_160509_ROW. Also in my model is not possible to read/write flash by FlashTool. I always get error 0x7D4, no matter what version I use, even after unlock bootloader. I have also try descibed firmware TB3-730X_S033_160707_ROW but this one cannot be flashed in fastboot mode. It says wrong binary (all files have in name _signed so probably different structure). It's seems that Polish Tab3 tb3-730X tablets are better protected than Russian.
0xAF can You post link to FlashTool what you used to flash your tablet?
[EDIT]
This time i get it working 0xAF are you mean first screen when TWRP start and there is swipe button? I Always swipe and this killed system partition I think. Btw do you both can flash this tablet with FlashTool?
Click to expand...
Click to collapse
When you start the TWRP for the first time, it will ask to do something on system partition. I cannot remember if it was "Yes/No" answer, or a swipe. Just don't let TWRP touch the system partition.
After unlocking the bootloader with fastboot, you can flash the recovery with fastboot if you want, but first try to boot it, as described in the first post.
If you're going to flash the original firmware from the links above, then you will need SPFlash Tool, because the images (dumps) are made with SPFlash Tool and you cannot directly flash them with fastboot.
For bootloader unlocking, you can try this command: "fastboot oem unlock", while you're in the bootloader.
Did you enabled the "OEM Unlocking" from the "Developer Options" menu?
On my device, I was able to unlock it (after enabling "OEM Unlocking" option) with "fastboot flashing unlock".
"I have also try descibed firmware TB3-730X_S033_160707_ROW but this one cannot be flashed in fastboot mode. "
not to flash, always ends with an error 0x7D4 .....
beldy said:
"I have also try descibed firmware TB3-730X_S033_160707_ROW but this one cannot be flashed in fastboot mode. "
not to flash, always ends with an error 0x7D4 .....
Click to expand...
Click to collapse
Is your bootloader unlocked?
see the "fastboot" command manual, to check if it is unlocked.
0xAF said:
When you start the TWRP for the first time, it will ask to do something on system partition. I cannot remember if it was "Yes/No" answer, or a swipe. Just don't let TWRP touch the system partition.
After unlocking the bootloader with fastboot, you can flash the recovery with fastboot if you want, but first try to boot it, as described in the first post.
If you're going to flash the original firmware from the links above, then you will need SPFlash Tool, because the images (dumps) are made with SPFlash Tool and you cannot directly flash them with fastboot.
For bootloader unlocking, you can try this command: "fastboot oem unlock", while you're in the bootloader.
Did you enabled the "OEM Unlocking" from the "Developer Options" menu?
On my device, I was able to unlock it (after enabling "OEM Unlocking" option) with "fastboot flashing unlock".
Click to expand...
Click to collapse
Thanks. Now all working I just swipe button thinking that is locking button.
About flashing problem. I cannot flash with FlashTool because I have 0x7D4 error, same as beldy. I have try different cables, 3 computer, Windows 7, Windows 8 and Windows 10 - same.
I have unlocked bootloader with "fastboot oem unlock". Without it TWRP cannot be installer or booted. Before I enabled "OEM Unlocking" from the "Developer Options" menu. After it, phone format byself but still cannot flash.
I killed pcs one and send to service. Tablet cannot go into recovery. When it back I see some scratches on cover, like was opened. Maybe they used TestPoint to fix it.
DonKapselo said:
Thanks. Now all working I just swipe button thinking that is locking button.
About flashing problem. I cannot flash with FlashTool because I have 0x7D4 error, same as beldy. I have try different cables, 3 computer, Windows 7, Windows 8 and Windows 10 - same.
I have unlocked bootloader with "fastboot oem unlock". Without it TWRP cannot be installer or booted. Before I enabled "OEM Unlocking" from the "Developer Options" menu. After it, phone format byself but still cannot flash.
I killed pcs one and send to service. Tablet cannot go into recovery. When it back I see some scratches on cover, like was opened. Maybe they used TestPoint to fix it.
Click to expand...
Click to collapse
I'm glad you've solved the problem. I dont know what is 0x7D4 error. It could be some sort of extra locking of the device, but I doubt it. It's more likely to be something related to SPFlash Tools. It could be also a broken firmware, I haven't tried to flash the firmware from the links I've provided. I only used the Original Firmware to extract the original recovery from there. I needed the original kernel from the recovery to be able to start the TWRP.
A fast look in google gives this:
Error 0×7D4
Message: BROM ERROR: S_BROM_DOWNLOAD_DA_FAIL
Meaning: SP Flash tool encountered an error writing to the phone
Solution
* Try using a different USB cord, PC port and PC
* Use the latest version of SP flash tool
* Ensure the battery is well charged and the phone's USB port isn't faulty
Click to expand...
Click to collapse
But I guess it's not very helpful.
0xAF said:
I'm glad you've solved the problem. I dont know what is 0x7D4 error. It could be some sort of extra locking of the device, but I doubt it. It's more likely to be something related to SPFlash Tools. It could be also a broken firmware, I haven't tried to flash the firmware from the links I've provided. I only used the Original Firmware to extract the original recovery from there. I needed the original kernel from the recovery to be able to start the TWRP.
A fast look in google gives this:
But I guess it's not very helpful.
Click to expand...
Click to collapse
Just try to read flash, it's safe. I can bet You will get error 0x7D4 or 2004 (depend of version of flashtool). It's extra locked for sure. Btw. why You need original recovery to start TWRP? Maybe You mean that You need it to compile TWRP for this tablet model?
DonKapselo said:
Just try to read flash, it's safe. I can bet You will get error 0x7D4 or 2004 (depend of version of flashtool). It's extra locked for sure. Btw. why You need original recovery to start TWRP? Maybe You mean that You need it to compile TWRP for this tablet model?
Click to expand...
Click to collapse
The easiest way to port TWRP is to get it from another device with the same chipset and cpu. I did not wanted to prepare a toolchain/crosscompiler and start from the beginning to compile TWRP. So I took a TWRP from another tablet (DOOGEE_X6pro_Android6.0_20160707). Since it has a recent version of TWRP and is compiled for android 6.
Then all you need is to replace the kernel in this recovery, so we are booting with the kernel for our device. I needed the kernel from our original recovery for that. Then I've touched some files inside the recovery, fixed the fstab and default.prop and repackaged the recovery image.
This is the easiest way to port the recovery IMO. Took me 15-20 mins with all the testing.
This procedure work for any recovery, not only TWRP.
I guess, I could have dumped the original recovery from the device, but since I was looking for custom recovery for some time, I found the dump in the russian forum and downloaded it. So when I decided to port TWRP, I already had the recovery from the dump.
Thanks for info Any link to step by step how to replace kernet, what data change?
DonKapselo said:
Thanks for info Any link to step by step how to replace kernet, what data change?
Click to expand...
Click to collapse
https://www.youtube.com/watch?v=hwMFBuCY-5k
I saw this video and decided to follow the steps.
You will need some intuition about the files you need to change inside the new recovery, as the video shows that only the fstab is needed, but you need more files, like default.prop and some other device dependent files from the original recovery (mostly in root folder).
In this recovery, I've used the default.prop from the original recovery.
As for the fstab, you will need to convert it by hand to a format understandable by TWRP. I've used the TWRP fstab file from the other device (from which I took the recovery in first place) and adopted it to our device. IIRC, almost nothing had to be changed.
I've copied some other device dependent files from the original recovery too.
Since I'm on linux, I've used these tools:
https://github.com/osm0sis/Android-Image-Kitchen.git
https://github.com/osm0sis/mkbootfs/
https://github.com/osm0sis/mkbootimg/
The tools are also available for windows (as the video shows) and for android itself (I believe the CF-SuperSU uses them on android to repack the boot.img).
These tools can repack recovery.img and boot.img.
Many thanks!
0xAF said:
Is your bootloader unlocked?
see the "fastboot" command manual, to check if it is unlocked.
Click to expand...
Click to collapse
yes bootloader is unlocked by command fastboot oem unlock...
It managed to someone already listed above to flash firmware in fastboot mode?
When you turn on the tablet remains lit Lenovo logo, and that's the end ...
Tablet can not even charged because, in the power cable connection tablet immediately turn on and loading TWRP or Lenovo logo screen
I am not progressed and I would appreciate if someone added original recovery or something what my tablet to function again
thx
beldy said:
yes bootloader is unlocked by command fastboot oem unlock...
It managed to someone already listed above to flash firmware in fastboot mode?
When you turn on the tablet remains lit Lenovo logo, and that's the end ...
Tablet can not even charged because, in the power cable connection tablet immediately turn on and loading TWRP or Lenovo logo screen
I am not progressed and I would appreciate if someone added original recovery or something what my tablet to function again
thx
Click to expand...
Click to collapse
Hi.
I'll make a dump of my system partition and post a link.
Unfortunately my system partition is not like in the original from the OTA ROM.
I've patched it with xposed and removed some ****ty apps from the OTA ROM.
Meanwhile if someone have OTA ROM, I would appreciate a link.
(you could try asking the Lenovo support for the OTA ROM).
0xAF said:
Hi.
I'll make a dump of my system partition and post a link.
Unfortunately my system partition is not like in the original from the OTA ROM.
I've patched it with xposed and removed some ****ty apps from the OTA ROM.
Meanwhile if someone have OTA ROM, I would appreciate a link.
(you could try asking the Lenovo support for the OTA ROM).
Click to expand...
Click to collapse
Thanks for the answer and advice to try anything that can help me
Thx
//EDIT: I add a few screens that I made an attempt to flash ... maybe you help someone ..
beldy said:
Thanks for the answer and advice to try anything that can help me
Thx
//EDIT: I add a few screens that I made an attempt to flash ... maybe you help someone ..
Click to expand...
Click to collapse
You should try to flash the dump with "fastboot flash system <file>"
Hello,
Got the Lenovo TAB3-730M.
What SuperSU.zip do I have to take to get "root"?
The "SR3-SuperSU-v2.78-SR3-20161103171345.zip" does not work.
Hi
After updating to EMUI 8.0 from this tutorial everything went well. Got Oreo working fine, so started to root with magisk = Ok; Xposed=Nok... Bootloop.
First - clean Data and Cache+Dalvik, still Bootloop
Entered to fastboot and tried to flash this file to rollback to 8.0, but...
I nottest that it said on the screen:
Bootloader UNLOCKED (in RED) and FRP Locked (In Green)
Confusing colors, cause it seems that i can't flash anything with unlocking the FRP... but i don´t have access the the system....
Also cant format System partition cause its read only, unable to flash other recovery files thought fastboot....
It s a f*cking MESS....
Can anyone please advice on this?
What can i do to recover this piece of sh*t??
Please........
Thank you, people
==============================
Well, got it figured out... But had to pay for it....
First of all:
{
"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"
}
You SUCK. Thanks for NOTHING
Lastly:
Thank YOU!!!
Long story short, i've solved it but have to pay for it.
Went to HUAWEI Service Center here in Portugal, and they told me that they couldn't do anything since the phone was not marketed for Europe (??????) [ASS Os]
I've discovered this service, and as with any other service online, i get suspicious for a while, asked a lot of questions and decided:
Bought a Month Pass for 50 EUD (45 Euros), and voila, in the first try unbricked the phone
Now i have the rest of the month to play with it...
Thanks for the people of FunkyHuawei for the kind attention (mostly pacience) they had with me.
I recommend it :good::good::good::good::good:
RSGI said:
Hi
After updating to EMUI 8.0 from this tutorial everything went well. Got Oreo working fine, so started to root with magisk = Ok; Xposed=Nok... Bootloop.
First - clean Data and Cache+Dalvik, still Bootloop
Entered to fastboot and tried to flash this file to rollback to 8.0, but...
I nottest that it said on the screen:
Bootloader UNLOCKED (in RED) and FRP Locked (In Green)
Confusing colors, cause it seems that i can't flash anything with unlocking the FRP... but i don´t have access the the system....
Also cant format System partition cause its read only, unable to flash other recovery files thought fastboot....
It s a f*cking MESS....
Can anyone please advice on this?
What can i do to recover this piece of sh*t??
Please........
Thank you, people
Click to expand...
Click to collapse
Do you still have access to twrp?
It could be only hope.
I had frp lock problem after unlocking bootloader. I had hit reset to default setting while inside developer options menu. That flipped the oem unlock switch.
I had to use twrp to flash back the stock boot.img and stock recovery.img then i was able to oem relock (my code).
And boot into room and reflip oem unlock toggle
thanks for replying
Not sure that i can access TWRP cause every time i force the recovery it appears the EMUI recovery (probably the NoCheck version that i used to update to Oreo)
Isn't it possible to reverte back to EMUI 5.1? Maybe with the 'dload' methode??
Is there any way to reset/unlock FRP from fastboot? I tried to relock bootloader with my own key but got an error (can't remember now what...)
I can't access the ROM itself...
This was because i installed Xposed....
If i could access TWRP again, perhaps i could delete the xposed files (in a recovery with the system as read-only)...
But i just dont know what to look for....
In older systems i knew that was the app_process file... Now i just dont know....
Thanks again for your reply!
help
download multi tool in pc and flash oreo beta via bootloader
i phase the same problem and it fixed my problem
RSGI said:
thanks for replying
Not sure that i can access TWRP cause every time i force the recovery it appears the EMUI recovery (probably the NoCheck version that i used to update to Oreo)
Isn't it possible to reverte back to EMUI 5.1? Maybe with the 'dload' methode??
Is there any way to reset/unlock FRP from fastboot? I tried to relock bootloader with my own key but got an error (can't remember now what...)
I can't access the ROM itself...
This was because i installed Xposed....
If i could access TWRP again, perhaps i could delete the xposed files (in a recovery with the system as read-only)...
But i just dont know what to look for....
In older systems i knew that was the app_process file... Now i just dont know....
Thanks again for your reply!
Click to expand...
Click to collapse
If you tried to install exposed from twrp, it should still be there
try dload method with emui 5 rom package, it may downgrade, no harm in trying.
Sudeep Duhoon said:
try dload method with emui 5 rom package, it may downgrade, no harm in trying.
Click to expand...
Click to collapse
Please can you explain that in detail?
Cause that might be the only way to save this (#"))&%&(/)&....
So, here is my situation:
- No TWRP access (recovery_ramdisk might be empty or damage... hopefully just empty)
- Bootloader Unlocked but FRP Locked
- eRecovery only presents 3 choices: Shutdown, Reboot and "Download latest version and recovery"*
- The System it self it's messed up after trying to install xposed.... just when its about to start, it reboots...
So.......
Still 3 ways that i can resolv this:
1 - the dload method (already tried, it updates until 5%, then error:" Install update failed" (Use the update.app file from the OTA, FullOTA, just the app file, all files in the update.zip... ) Not sure if i'm missing the right app file or if the eRecovery (maybe the NoCkeck version used to update initially) is screwed-up...
2 - Unlocking the FRP (Factory Reset Protection) this means that the "Allow OEM unlocking" is Off
Hopping to find a way to unlock it via fastboot
3 - The *Download latest version and recovery method allows to connect to wifi and download the firmware...
Not much sucess, but i know that i'm missing something (just dont know what it is...)
It seems that the router requires a certain configuration which i have no idea....
Suggestions are always welcome!
Thanks
RSGI said:
Please can you explain that in detail?
Cause that might be the only way to save this (#"))&%&(/)&....
So, here is my situation:
- No TWRP access (recovery_ramdisk might be empty or damage... hopefully just empty)
- Bootloader Unlocked but FRP Locked
- eRecovery only presents 3 choices: Shutdown, Reboot and "Download latest version and recovery"*
- The System it self it's messed up after trying to install xposed.... just when its about to start, it reboots...
So.......
Still 3 ways that i can resolv this:
1 - the dload method (already tried, it updates until 5%, then error:" Install update failed" (Use the update.app file from the OTA, FullOTA, just the app file, all files in the update.zip... ) Not sure if i'm missing the right app file or if the eRecovery (maybe the NoCkeck version used to update initially) is screwed-up...
2 - Unlocking the FRP (Factory Reset Protection) this means that the "Allow OEM unlocking" is Off
Hopping to find a way to unlock it via fastboot
3 - The *Download latest version and recovery method allows to connect to wifi and download the firmware...
Not much sucess, but i know that i'm missing something (just dont know what it is...)
It seems that the router requires a certain configuration which i have no idea....
Suggestions are always welcome!
Thanks
Click to expand...
Click to collapse
What I'm trying to understand , is how were you trying to install exposed.
I assume it was with twrp, no.
mrmazak said:
What I'm trying to understand , is how were you trying to install exposed.
I assume it was with twrp, no.
Click to expand...
Click to collapse
theres not much to understand there....
i flashed it with twrp and the phone never booted again...
yes, had access to the twrp for a while, but then, trying to run again the update process to flash the wrong recovery to recovery_ramdisk partition.... (another shot in the foot)
now i dont have twrp anymore and i'm unable to flash it cause th frp lock keeps telling thats not allowed...
the most clean way to solve this is to erase/unlock the FRP without accessing the ROM...
I'm already thinking about buy some credits with one of those online services that might unlock it...
Can you suggest to me some serious and honest services?
I'm desperate....
RSGI said:
theres not much to understand there....
i flashed it with twrp and the phone never booted again...
yes, had access to the twrp for a while, but then, trying to run again the update process to flash the wrong recovery to recovery_ramdisk partition.... (another shot in the foot)
now i dont have twrp anymore and i'm unable to flash it cause th frp lock keeps telling thats not allowed...
the most clean way to solve this is to erase/unlock the FRP without accessing the ROM...
I'm already thinking about buy some credits with one of those online services that might unlock it...
Can you suggest to me some serious and honest services?
I'm desperate....
Click to expand...
Click to collapse
Ok, I see
Didn't know you where 2 or 3 miss- steps past a failed exposed install.
I have no idea which service to recommend.
Hi,
Hope OP got his solution.
@matt4321
Honorable mod, I guess this thread belongs to Honor 7X Q&A forum. Please relocate.
Cheers
you cant downgrade from emui 8 you need to extract update.app of emui 8 an flash the ramdisk boot img so it will boot for that you need to download indian firmware mannual update given in other forum and extract the zip file update22 and data file extract both zip files and download the multi tool version 8 install all drivers boot your phone into bootloader now go to multi tool and click on unbreak and open huawie update extractor and extract update.app of data or update 22 make sure to check the mark on top emui 8 and when you click on update make sure to uncheck the verify the headder for that you go to settings in extracting update and follow the procedure of flashing for that you can google how to use multi tool i cant explain more i am not a developer but i phase the same problem and i got fixed hope i helped you
RSGI said:
Hi
After updating to EMUI 8.0 from this tutorial everything went well. Got Oreo working fine, so started to root with magisk = Ok; Xposed=Nok... Bootloop.
First - clean Data and Cache+Dalvik, still Bootloop
Entered to fastboot and tried to flash this file to rollback to 8.0, but...
I nottest that it said on the screen:
Bootloader UNLOCKED (in RED) and FRP Locked (In Green)
Confusing colors, cause it seems that i can't flash anything with unlocking the FRP... but i don´t have access the the system....
Also cant format System partition cause its read only, unable to flash other recovery files thought fastboot....
It s a f*cking MESS....
Can anyone please advice on this?
What can i do to recover this piece of sh*t??
Please........
Thank you, people
Click to expand...
Click to collapse
can't you install image from fastboot, if so try to flash rr or aosp system.img or extract from update.app
11122314 said:
download multi tool in pc and flash oreo beta via bootloader
i phase the same problem and it fixed my problem
Click to expand...
Click to collapse
Tried that but the only response that fastboot gives me is "Command not allowed" .
I just can´t flash anything in fastboot. I think i can thought adb shell dd (at least that how i manage to screw twrp partition), but i just can´t get ADB connection.
Just got fastboot connection with HiSuite drivers...
How can i get ADB access? It just installs an USB Storage Device...
Also i can try update via fastboot but it saying that it misses android-info.txt file.... whatever that means...
If i could boot once into the ROM, i would enable "Allow OEM Unlocking" and do exactly that.... btut i junt can´t... not yet...
11122314 said:
you cant downgrade from emui 8 you need to extract update.app of emui 8 an flash the ramdisk boot img so it will boot for that you need to download indian firmware mannual update given in other forum and extract the zip file update22 and data file extract both zip files and download the multi tool version 8 install all drivers boot your phone into bootloader now go to multi tool and click on unbreak and open huawie update extractor and extract update.app of data or update 22 make sure to check the mark on top emui 8 and when you click on update make sure to uncheck the verify the headder for that you go to settings in extracting update and follow the procedure of flashing for that you can google how to use multi tool i cant explain more i am not a developer but i phase the same problem and i got fixed hope i helped you
Click to expand...
Click to collapse
That was my plan... but even that is screwed-up.....
Here is my Recovery Status, without the possibility to flash any img via fastboot:
recovery_ramdisk (empty or in-error)
erecovery_ramdisk ( BND-RECOVERY-NoCheck.img flashed to update into EMUI 8.0)
With the software now, whats failling me is the ****ing recovery, that flash only 5% before it shows this error : "Install update failed!"
Dont have ADB support, maybe because i dont have the "USB Debbuging" option enable...
It seems that i will spend 15 euros to unlock this &%/())(/&%$######()/=?(/%&$#
Just thought I'd post here in case you are still in need. I believe that there are two different recovery modes - one that is triggered by holding power, up vol, and down vol, and another that is triggered by holding just power and up vol. Are you sure twrp is gone? I thought I had lost twrp when in fact it was in the other recovery.
RSGI said:
Please can you explain that in detail?
Cause that might be the only way to save this (#"))&%&(/)&....
So, here is my situation:
- No TWRP access (recovery_ramdisk might be empty or damage... hopefully just empty)
- Bootloader Unlocked but FRP Locked
- eRecovery only presents 3 choices: Shutdown, Reboot and "Download latest version and recovery"*
- The System it self it's messed up after trying to install xposed.... just when its about to start, it reboots...
So.......
Still 3 ways that i can resolv this:
1 - the dload method (already tried, it updates until 5%, then error:" Install update failed" (Use the update.app file from the OTA, FullOTA, just the app file, all files in the update.zip... ) Not sure if i'm missing the right app file or if the eRecovery (maybe the NoCkeck version used to update initially) is screwed-up...
2 - Unlocking the FRP (Factory Reset Protection) this means that the "Allow OEM unlocking" is Off
Hopping to find a way to unlock it via fastboot
3 - The *Download latest version and recovery method allows to connect to wifi and download the firmware...
Not much sucess, but i know that i'm missing something (just dont know what it is...)
It seems that the router requires a certain configuration which i have no idea....
Suggestions are always welcome!
Thanks
Click to expand...
Click to collapse
[BND-L22 / BND-AL10C675] Back to Stock / Unbrick your Honor 7X Indian Variants
Sudeep Duhoon said:
[BND-L22 / BND-AL10C675] Back to Stock / Unbrick your Honor 7X Indian Variants
Click to expand...
Click to collapse
Not even that i can do....
Let's update:
State
OS: Bootloop
System: No "recovery_ramdisk" partition (no stock / no twrp)
Bootloader: Unlocked
*FRP: Locked
So can't flash in fastboot, *Already got the unlock code for the FRP but without the "recovery_ramdisk" recovery the system wont reset....
(Weird!) No adb access in recovery mode (which would help A LOT....)
The dload method, whatever the update.app only updates until 5% , then error updating...
The eRecovery Wireless method might work, but i just dont know how to do it.
Tried with a usb pen inserted on the router with all the ROMs all together, in separated folders, whatever, no rom detected... there must be a way to do it right... i just dont know how...
Just need one of two things to happend:
Flash the stock recovery - still dont know how to do it...
Fix the bootloop and access the SO Rom - also, without adb access just dont know how...
Out of the box thinking required...
About UPDATE.APP
Can't we make a update.app much like o do it for zip files?
Would it be possible to make um UPDATE.APP just to flash/restore recovery partition?
The updates with zip files must also be inside a dload folder?
About Bootloop and SD Card
Is there a way, using the sd card, to stop the reboot, maybe enable the Safe Mode...
Something that would allowed me to access the Settings...
Any apk, any script that could be loaded from the SD card....
Not an easy plan... i know...
Maybe something very basic and easy is escaping me....
RSGI said:
Not even that i can do....
Let's update:
State
OS: Bootloop
System: No "recovery_ramdisk" partition (no stock / no twrp)
Bootloader: Unlocked
*FRP: Locked
So can't flash in fastboot, *Already got the unlock code for the FRP but without the "recovery_ramdisk" recovery the system wont reset....
(Weird!) No adb access in recovery mode (which would help A LOT....)
The dload method, whatever the update.app only updates until 5% , then error updating...
The eRecovery Wireless method might work, but i just dont know how to do it.
Tried with a usb pen inserted on the router with all the ROMs all together, in separated folders, whatever, no rom detected... there must be a way to do it right... i just dont know how...
Just need one of two things to happend:
Flash the stock recovery - still dont know how to do it...
Fix the bootloop and access the SO Rom - also, without adb access just dont know how...
Out of the box thinking required...
About UPDATE.APP
Can't we make a update.app much like o do it for zip files?
Would it be possible to make um UPDATE.APP just to flash/restore recovery partition?
The updates with zip files must also be inside a dload folder?
About Bootloop and SD Card
Is there a way, using the sd card, to stop the reboot, maybe enable the Safe Mode...
Something that would allowed me to access the Settings...
Any apk, any script that could be loaded from the SD card....
Not an easy plan... i know...
Maybe something very basic and easy is escaping me....
Click to expand...
Click to collapse
I just read through the fastboot partition from my backup using "strings" to find the available "oem" commands.
I think i found possible solution for you.
careful useing these commands as I do not know for sure if they work and what they do.
Code:
fastboot oem frp-unlock
also not sure about the dashes or underscores.
mrmazak said:
I just read through the fastboot partition from my backup using "strings" to find the available "oem" commands.
I think i found possible solution for you.
careful useing these commands as I do not know for sure if they work and what they do.
Code:
fastboot oem frp-unlock
also not sure about the dashes or underscores.
Click to expand...
Click to collapse
Hi
Thank you for replying.
Already tried that.... Actually the command should be:
Code:
fastboot oem frp-unlock (unlock frp key)
Bought the unlock code from an online unlock store.
Spent 10 euros. The code is correct cause i got the message that the device will reboot and do a factory reset.
Than it reboots into an error screen, cause i screwed up the "recovery_ramdisk" partition earlier and its not working now. So, no factory reset, no changing the Frp status... Still locked.
Still no flashing img files from recovery... Still got the reply oficial Command Not Allowed...
But:
I'm trying to gain adb access while on eRecovery.
Than i could try to flash the stock recovery with the code dd command. From there i would unlock the Frp with the code and the Factory Reset might be enought to fix the bootloop.
Also the bootloop it self...
I wonder if there's a way to force the boot even with FC errors....
Access to the ROM software would allow me to flash the stock recovery and then make a factory reset, by changing the OEM Unlocking status
Thanks for your reply, maybe you can give me some tips on this 2 ways that i'm exploring right now.
Or some other ways that i haven't consider yet... please....
:cyclops::cyclops:
.
Sorry to bother everybody...
I just wanna know that can we flash non carrier firmware into a verizon moto z3 (xt 1929-17) as it can not be getting its boatloader unlocked?? Please help... M new here at xda ....
How is your phone now? Is it still stucked on lockscreen lockout? Is it still containing the exact version of miui? My guess is yes but I need a confirmation.
You can't access adb from lockscreen for an obvious purposes, not even MTP.
And what is the error says?
@Osmanism.91 please ask in that particular forum before you ask it elsewhere
.
You may try from recovery flash via mi flash pro. It will need a miui account and internet connection
Second approach is by erasing every lines up to something that says "fastboot erase boot". Keep those line downwards.
.
rodagola said:
you mean delete everything but "fastboot erase boot"? probably not going to do anything because that line also shown me an error before.
Click to expand...
Click to collapse
Not everything, just every checks. It will goes like this:
{
"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"
}
Figure 1 : Lines to be removed
If you specify every error messages you've encountered, it will help everyone.
rodagola said:
I loaded up mi flash pro before and hit the recovery button to go to that interface but the actual recovery interface within miflashpro didn't popup, do you recommend a specific miflashpro version and specific drivers? or is it because I haven't logged into a mi account yet? can it be a brand new mi account?
Also if I actually have the chance to download a recovery rom then go into this recovery miflashpro menu...I'm scared miflashpro might delete the personal data partition, at least on regular MiFlash there's a checkbox with "save user data"
Click to expand...
Click to collapse
You need to boot to recovery, of course. You're in vanilla, so I bet you still have the miui recovery. No need to be specific about miflash pro version, any version will do. It will work like an upgrade. It will require same level or more recent firmware. You can't revert your firmware this way: the server will refuse. I don't know about the account requirements, but it will be better to log in to your account there.
Figure 2 : MiFlashPro > Recovery Flash interface. My flash is rejected. IDK why. It's been rejected when I tried to upgrade from 12.0.6 to 12.5.1. Used first method to upgrade instead.There is that "Wipe user data" button, pretty self-explanatory.
.
rodagola said:
oh alright, recovery method could work as long as I dont click wipe data, however, how do I get to that screen you screenshoted? Since a Mi Account is a must, if I make an account today, you think will that let me work with that?
Click to expand...
Click to collapse
Boot to recovery, select "Connect to PC Suite", the 3rd option, control selection with volume rocker and select with power button. Depending on how is your device is connected, it will automatically detects the corresponding flash method. In this case, there will be this "Flash in recovery" button in the main interface. Just click that and select your ROM directory.
I don't know about account details, since I always use my account that have permission to get a device unlocked
rodagola said:
Hi all, I've had this issue for a while.
I have a RN8P Chinese running MIUI11.0.3 stable over Android9, however, I wanted to start customizing my experience but didn't mean to go 'too far'.. the issue is:
> I've never unlocked the bootloader on it, therefore no custom recovery available on it. But didn't mean to change this and wanted to keep stock ROM
> However, within my stock ROM, I wanted to have it as clean as possible from bloatware, so I went ahead and plugged the phone to my PC, installed adb, and started running commands with adb shell pm uninstall... I managed to uninstall quite a few useless apps but also thought uninstalling a system app called something like "yman" and another like "xman" was a good idea, oh boy it wasn't a good idea...
> Now the phone has some sort of soft brick. When it reboots and goes to the lock screen (I had it with swipe), I try to swipe up but the phone doesn't respond, and I think the yman and xman apps were responsible for this function, but are now uninstalled)
> I need a way to get my phone working normally. When going back to adb to reinstall these via commands, I get "unauthorized" when checking the phone status with 'adb devices', so no commands are accepted. I also went into the stock recovery mode and tried to run commands but it now shows "sideload" and will give error for every command, so I discarded this option
> Maybe I can run these commands through the fastboot menu somehow? However I don't know how (if even possible)
> If there's absolute no way to get this RN8P to receive the command to reinstall the same package that caused the trouble, then I think I could try flashing...
> I went and downloaded MiFlash, downloaded the corresponding same exact stable ROM on same region for fastboot, plugged my phone and checked SAVE USER DATA on the botton, in order to have the data partition intact, but MiFlash throws some errors. I read somewhere just click on the desired batch file while the phone is still plugged in and it might bypass MiFlash errors, but it didn't, then I tried redownloading drivers and from 3 different PCs, looked up why MiFlash was failing and found out perhaps deleting a few lines from the batch would fix it, but I kept getting further errors related to the next line and the errors were endless.
> Still with the flashing idea on MiFlash, I downloaded the other further Chinese fastboot ROMs, as in upgraded versions to Android10 and MIUI12 (instead of the exact versions the phone still had). But now I get same thing as before, endless errors keep coming up and the flash process won't go through.
> I really want to retain my personal data, so I was suggested to try MiFlashTool v2, however, I've heard that one has no option to save the data partition, so I haven't bothered yet, and before I move on to try, could anybody with experience tell me their experience?
> In general, would there be a way still for me to fix the phone without losing user data? Maybe there's hopes the phone can receive adb commands somehow still? I'm confident I can revive the phone very quick through adb, if only it still wanted to be adb friendly...
Thanks to any pros that might be out there and would save a junior
Click to expand...
Click to collapse
You said you have a RN8Pro Chinese.
Can you give us the full MIUI ROM filename that you're attempting to flash? We have to be sure you're flashing the correct ROM.
Also check if the MIUI ROM you downloaded isn't corrupted.
Compass.
.
rodagola said:
I downloaded "begonia_images_V11.0.3.0.QGGCNXM_20200518.0000.00_10.0_cn" which is supposed to be rn8p chinese fastboot miui11.0.3 a10. And from 2 different sources to try to make sure it wasn't corrupted. I don't know any actual way to check if the ROM is corrupted or not...
Before the soft brick, the phone had this exact same version but for a9 instead of a10. So I guess this is some sort of upgrade.
I'm now going to try downloading same thing but for the recovery version within miflashpro, just like what kekesed97 said
This could have a different output, so I'll update here
If this doesn't go successful, then I guess next step is trying SP flash tool? though I have no clue how to use that one
Click to expand...
Click to collapse
You downloaded a very old MIUI but it should work. Check the link below for a newer release. The latest fastboot for MIUI 12.0.x China is V12.0.5.0.QGGCNXM (if I didn't skip a version; the list is quite big). There's also MIUI 12.5.x China if you want the latest stable (MIUI 12.5.x Global is buggy so I'd skip MIUI 12.5.x for now).
https://xiaomifirmwareupdater.com/archive/miui/begonia/
Here is a YouTube playlist that might help you: https://www.youtube.com/playlist?list=PLLy0_Q3fJ1DLjE5Cx7uCD3yTxeTaUbiIo
Be careful when you flash so that you keep your data. If I remember well that author usually wipes data in his videos.
I don't know which package manager people with Windows are using these days, but I guess WinRar is a popular choice. WinRar should have a "test file" so you could try that to check for a corrupted download.
I can't help you with the flashing process on Windows since I don't use it. kekesed97 instructions or the YouTube playlist should work (I think the YouTube author uses different software for flashing, just so you know).
Compass.
.
rodagola said:
Hi again, I'm in MiFlashPro recovery section, and have downloaded the corresponding recovery ROM, it downloaded as zip. Now should I just browse and select it as is, or do I need to uncompress and select something else? My guess is select as is but would like to confirm. Thanks a lot for your tips so far dude.
Click to expand...
Click to collapse
No unzipping. Use it as is as it will be sent over your phone and flashing is done recovery side (put it simply, it's an ADB sideload, with restrictions)
rodagola said:
Moreover, there's an option to download an incremental zip (just the ota extra files instead of full zip) would you recommend that over full zip? would that fix the brick? My guess is not because it doesn't have all the apks on it, whereas the full one has all the apks so it can reinstall the uninstalled app that caused my brick, and probably the OTA version can't, but I'm NOT sure...
Click to expand...
Click to collapse
It only accepts recovery ROMs (2 gb ones). You are only allowed to flash greater version of your current firmware from the same ROM distribution. It's works like updating your phone when incremental update fails after all.
rodagola said:
Also, to add more detail, I was looking arond and found that MiFlash Tool could not be so friendly with phones running on Mediatek so it's more for Qualcomms... instead, SP flash tool is more meant for MediaTeks (so that makes me believe that's why my RN8P was having all sorts of errors with that "MiFlashTool"). Anyway, I'll stay away from SP flash tool aswell because I read it always wipes everything. So my only real chance now seems to be the Recovery method on MiFlashPro, but I'd love if you confirmed my inquiry mentioned above
Click to expand...
Click to collapse
Not quite correct. There are 3 different flashing methods there. Recovery mode, fastboot mode, and deep flash mode.
In recovery mode, flash is using ADB sideload-like mechanics (or it is? I have no evidence, but it works similiarly that way), while in the Mi Flash program is using fastboot method. Both methods are platform-independent, which means it will work in both MTK or SD chipsets, as long as the phone permits. As for deep flash one, it will require lower level access to hardwares, and only manufacturers are having such access. Thus, flashing method diverges. MTK is using SP Flash tools, in which the mechanics behind that can be red in the CFW Megathread (CFW is quite irrelevant today, but the boot process explanation is something else that will never went irrelevant, unless another boot sequence is introduced), as for SD chipsets will use QPST over Sahara Protocol (more info on this: just dig how to ressurect xiaomi redmi note 5 pro edl 9008 that have their arb lock triggered).
It isn't that it will wipe your phone clean that to be your concern. That can be avoided by selecting "Download Only". But that there is this method requires a special account that only service centres have (but a bypass method is known recently, just dig deeper). Consider this as your last resort. Oh yes, it will need a fastboot rom, and the scatter file is available in the ROM directory.
.
rodagola said:
Hi again, I'm now in recovery mode in MiFlashPro and have attempted browsing the files I downloaded from https://xiaomifirmwareupdater.com
The files I choose were recovery roms with "stable branch" ( I don't know if weekly branch would work better?). Well, I loaded the stable ones into the menu and xiaomi servers authenticated and checked the rom... but then it throws "Sorry, flash to this stable version is not allowed" error.
What is this... I first tried with my downloaded zip package "miui_BEGONIA_V11.0.3.0.QGGCNXM_b656ebe642_10.0"
which is 1 step forward from the version I had (I had v11.0.3 with A9 but this package should update me to A10)
got the error... then tried with a little further update with another zip I downloaded "miui_BEGONIA_V12.0.2.0.QGGCNXM_972f66522c_10.0"
Same error again after xiaomi servers check it out.
There only seems to be a few more stable ROM versions for my chinese variant AFTER these. Those are: "V12.0.3.0.QGGCNXM", "V12.0.4.0.QGGCNXM", "V12.0.5.0.QGGCNXM" and "V12.5.1.0.RGGCNXM".
Before I try with these next 4 versions, from older to newer, I'd like to ask if should I rather try with BETA versions instead of stables... (since the error I was getting says: "Sorry, flash to this stable version is not allowed")
Anyways, I have read somewhere that with an authorized account it would let me install betas and stuff no problem, however those 2 that I tried to install weren't even betas. So I'm confused.
Thanks a lot again for your help dude
Click to expand...
Click to collapse
Don't do that.
Weekly is beta and doesn't mean it's better. It's supposed to be a test version and bug hunting release to device enthusiast so xiaomi can go fix it and accumulate the bug fixes to be included in the next stable version. Weekly is always newer so moving from beta to stable is considered downgrade, which require a data wipe. Btw, is your current firmware is from stable branch?
Or perhaps is it because your account doesn't hold a permission to flash since it's never been granted bootloader unlock permission? Idk about the account part.
Well, now try to use fastboot method if recovery update method fails. Mi Flash Pro have it so you don't have to download another tool. It allows broader range of firmware version, particularly for this phone.
Download a recovery rom and unzip it. Load it to mi flash, boot your phone to fastboot, and flash it there.
Figure 3: Mi Flash main interface. Choose this option to retain dataOr modify a flash batch file as I instructed in previous post and run it through command prompt.
I never flashed anything in a locked bootloader because I always unlock my phone the moment I grab it. But one thing for sure is you are bound to the same ROM region. Never flash any other ROM from another region distribution. You have been warned.
.
.
rodagola said:
Also, reading other threads, I should quote this guy called "zqm" on xda forums. From this post: https://forum.xda-developers.com/t/is-mi-unlock-really-needed-to-unlock-bootloader.4024519/
I quote his input: "This shouldn't be a concern for now. Xiaomi isn't planning to restrict unlocking the bootloader. Another thing you should consider is that Redmi note 8 pro gets easily bricked by flashing custom twrp, magisk, etc. but it's not easily recovered as it requires xiaomi authorised account."
So he's implying you need an auth account for recovery ROMs, (I think)......
I'm reposting this for you because you said you didn't know about the account requirements, maybe this brings forward a theory. However I insist I might need to borrow an authorized account now but don't know where or how
Click to expand...
Click to collapse
No, that one thing is different. What @zaqm talking about is the one to access the low level parts of hardware i.e. deep flash via SPFT, which only the manufacturers have, perhaps xiaomi engineering team and service center team to name a few. Adb sideload and fastboot is user accessible, so it doesn't need such permission, with limited access to emmc partitions (afaik no raw readback is one of its limitation). And fastboot doesn't enforce any account security measure, so does the adb sideload. That thing is implemented via mi recovery and mi flash pro. It will send an sha check to one of xiaomi server, returning if the phone is ok to be flashed. After the check returned true, it will begin to send the zip file to phone. This procedure is non-skippable. Therefore, you can only send firmwares this way. This is not happening in custom recovery, so you can send any command. But unfortunately you have vanilla.
After a quick inspection, that is indeed ADB sideload.
It refuse adb sideload command on redmi note 5 pro with vanilla recovery, unlocked bootloader (see attachment). After the command is issued, the phone immidiately restart and boot to system. It's likely won't hurt, so I think it worth the shot.
Try this :
1. Connect your phone to phone thru pc suite mode in recovery
2. Download minimal adb and fastboot or adb platform tools. Extract it.
3. Check your device by executing this in command prompt:
Code:
adb devices
4. If your device is connected, command prompt will return this:
Code:
D:\begonia\Minimal ADB and Fastboot>adb devices
List of devices attached
3d9ac49b sideload
5. Rename your firmware to something easy (something like update.zip but I don't care) and copy it to the same directory as the adb directory
6. Execute sideload command
Apache config:
adb sideload update.zip
7. See if wonder happens
8. ...
9. Profit?!
Anyway write back if this you succeed or not.
First, as you might now, I am not liable if your phone would be bricked or damaged after this tutorial.
This method has worked perfectly for on my phone, which: OnePlus Nord N10 5G from Metro by T-Mobile. Build Number: 11.0.1.BE88CF. And it should work any rom stock
This tutorial is inspired by andreas__ from this topic. I recommend to take a quick glance before processing here.
General Info:
You need adb and fastboot installed and should know how to use it
You must do this process only once, afterwards you can follow the OTA survival steps
You need to factory hard reset the phone (very important)
Unlock the bootloader
If you are using locked metro by T-Mobile phone, make sure to request the "unlock token" in order to unlock the bootloader.
Google "How to Unlock Bootloader on OnePlus Phones | Unlocked and T-Mobile Variants" for the instructions
After you have unlocked the bootloader using this command:
Code:
fastboot oem unlock
The data will be wiped and it will do the factory reset
Create the boot image:
You need to pull out a clean boot image from your phone. I have used TWRP to do that
flash the latest twrp for this phone:
[TWRP][3.5.2_10][Billie]TWRP for Oneplus Nord N10 5G [BETA]
Use this command to flash it:
Code:
fastboot flash recovery Twrp_3.5.2-10_EduardoA3677-billie_OxygenOs11_Android11.img
boot the phone to twrp recovery, then head to:
Backup > select "Boot (96MB)" > Swipe to Backup
The boot image will be generated in the internal storage under the name "boot.emmc.win"
root and patch the image:
Restart the phone to the system, then download the latest magisk app
Make sure to allow "USB debugging" from the developer Options
Install and open the magisk app then tap on "install" (very top)
tap on "select and patch a file"
select "boot.emmc.win" which is the image that was generated by twrp
Magisk will patch it and place it in the download folder under the name "magisk_patched-23000_Obpf5.img"
Copy the patched image into ADB folder in your PC
flash the patched image:
Reboot the phone into bootloader mode
Then flash the patched image:
Code:
fastboot flash boot magisk_patched-23000_Obpf5.img
Reboot the phone into the system
Hurray! your phone now is officially rooted. You're welcome
I hope you find my instructions useful.
Reserved !!
hamooz92 said:
First, as you might now, I am not liable if your phone would be bricked or damaged after this tutorial.
This method has worked perfectly for on my phone, which: OnePlus Nord N10 5G from Metro by T-Mobile. Build Number: 11.0.1.BE88CF. And it should work any rom stock
This tutorial is inspired by andreas__ from this topic. I recommend to take a quick glance before processing here.
General Info:
You need adb and fastboot installed and should know how to use it
You must do this process only once, afterwards you can follow the OTA survival steps
You need to factory hard reset the phone (very important)
Unlock the bootloader
If you are using locked metro by T-Mobile phone, make sure to request the "unlock token" in order to unlock the bootloader.
Google "How to Unlock Bootloader on OnePlus Phones | Unlocked and T-Mobile Variants" for the instructions
After you have unlocked the bootloader using this command:
Code:
fastboot oem unlock
The data will be wiped and it will do the factory reset
Create the boot image:
You need to pull out a clean boot image from your phone. I have used TWRP to do that
flash the latest twrp for this phone:
[TWRP][3.5.2_10][Billie]TWRP for Oneplus Nord N10 5G [BETA]
Use this command to flash it:
Code:
fastboot flash recovery Twrp_3.5.2-10_EduardoA3677-billie_OxygenOs11_Android11.img
boot the phone to twrp recovery, then head to:
Backup > select "Boot (96MB)" > Swipe to Backup
The boot image will be generated in the internal storage under the name "boot.emmc.win"
root and patch the image:
Restart the phone to the system, then download the latest magisk app
Make sure to allow "USB debugging" from the developer Options
Install and open the magisk app then tap on "install" (very top)
tap on "select and patch a file"
select "boot.emmc.win" which is the image that was generated by twrp
Magisk will patch it and place it in the download folder under the name "magisk_patched-23000_Obpf5.img"
Copy the patched image into ADB folder in your PC
flash the patched image:
Reboot the phone into bootloader mode
Then flash the patched image:
Code:
fastboot flash boot magisk_patched-23000_Obpf5.img
Reboot the phone into the system
Hurray! your phone now is officially rooted. You're welcome
I hope you find my instructions useful.
Click to expand...
Click to collapse
Hate to tell you this but if using twrp just rename magisk apk to magisk zip and install zip it auto patches to the right slot for you and you just confirm the install via magisk in android
scottlam1 said:
Hate to tell you this but if using twrp just rename magisk apk to magisk zip and install zip it auto patches to the right slot for you and you just confirm the install via magisk in android
Click to expand...
Click to collapse
Exactly.
I lost root after the forced OTA on July 31/August 1. Today I followed this guide to install twrp, factory reset, then installed Magisk by renaming the APK and flashing within TWRP. However the SafetyNet check showed "Attestation Failed." I enabled MagiskHide and rebooted, and now pass SafetyNet.
Thank you for this very simple and useful guide. I was able to root with no loss of userdata, saving a lot of time that would otherwise go into creating a backup.
scottlam1 said:
Hate to tell you this but if using twrp just rename magisk apk to magisk zip and install zip it auto patches to the right slot for you and you just confirm the install via magisk in android
Click to expand...
Click to collapse
I don't understand
bgfal3 said:
I don't understand
Click to expand...
Click to collapse
They are saying rename magisk from apk to zip and flash it in TWRP
bgfal3 said:
I don't understand
Click to expand...
Click to collapse
Just rename the APK to .zip extention and install through zip installer in twrp
iam almost ready to root my device i have both zip files from adreas tutorial on how root it.
where those zips files need to be in order to flash it?
cmd can be used, sorry iam new to this.
{
"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"
}
3lgato said:
View attachment 5485447
Click to expand...
Click to collapse
You need to get the unlock token first
Here is the instructions:
https://www.oneplus.com/support/answer/detail/op588
raginhomosapien said:
I lost root after the forced OTA on July 31/August 1. Today I followed this guide to install twrp, factory reset, then installed Magisk by renaming the APK and flashing within TWRP. However the SafetyNet check showed "Attestation Failed." I enabled MagiskHide and rebooted, and now pass SafetyNet.
Thank you for this very simple and useful guide. I was able to root with no loss of userdata, saving a lot of time that would otherwise go into creating a backup.
Click to expand...
Click to collapse
Glad it worked for you. You're welcome
Why it wait forever for attached device, even removing and reconnecting phone?
Rulesless said:
View attachment 5568509
Why it wait forever for attached device, even removing and reconnecting phone?
Click to expand...
Click to collapse
You have to be in fastboot mode before you can flash the recovery. Reboot into fastboot by typing "adb reboot fastboot" (without the quotes). Your phone should then reboot into fastboot mode. NOW, assuming you have already unlocked your bootloader, you can flash the recovery.
If anyone is still having the OEM unlocking greyed out issue, you need to do the device unlock from your phone, select request permanent unlocks then your device will reboot, from there you can then head back into dev options and you will be able to OEM unlock. Hope this helps seems not a lot of people realize this I hunted for the answer all over only to happen upon it when I was about to say forget it.
wcoolj said:
If anyone is still having the OEM unlocking greyed out issue, you need to do the device unlock from your phone, select request permanent unlocks then your device will reboot, from there you can then head back into dev options and you will be able to OEM unlock. Hope this helps seems not a lot of people realize this I hunted for the answer all over only to happen upon it when I was about to say forget it.
Click to expand...
Click to collapse
Just to add to this.....If you are unable to use device unlock because you have not met your carrier's requirements to do so yet you can use the script at this thread and it will open up oem unlock even if your phone is not eligible yet.
I have the N20. No twrp. Flashed a patched boot.img and lost radios. No wifi Bluetooth or sim)mobile data. Hoping that the platform is similar enough that someone could help me recover my device. Phone was sim locked, not sure if that's the issue. I forgot to run the command from the debloat script after flashing the unlock token, shouldn't have rushed this. I don't have a backup of anything though. Was trying to get root to back up everything. Factory resetting did nothing to fix the issue
PsYk0n4uT said:
Factory resetting did nothing to fix the issue
Click to expand...
Click to collapse
LOL never does at this level, just wipes cache and user partition, but nothing of value where we play- the assumption is you (or the bad guys) can't figure out how to write to the system, boot, etc partitions. (snicker).
So the good news is if you can find the EDL image, and follow the procedure to reflash the phone... it should restore everything for you.
(To be clear @PsYk0n4uT I linked you to the N10 EDL thread, not the N20...)
Thanks. So my issue so far. I don't think there is even a stock firmware posted anywhere. Though there is a backup of another device posted. How would I go about finding the EDL files for mine? Can one be created? Or would I need to source that from OnePlus or wait on someone to do that? I actually wasn't aware that I could boot the boot omg without flashing it to test it out first
Caution: I originally wrote this guide when it was necessary to disable verity and verification before flashing patched boot.img. Now Magisk has overcome this requirement and some users have reportedly flashed updates without disabling verification and verity and did not have to wipe their phones, but request everyone, who have verification and verity disabled and using this guide, make sure you backup all the data and post your results here (I suggest backing up data anyway for everyone).
Following is a guide to update Pixel 6 Pro (perhaps all Pixel devices) every month, without wiping and retaining root. I tested it on my Pixel 6 Pro from 12.0.0 (SD1A.210817.015.A4, Oct 2021) to 12.0.0 (SD1A.210817.036, Nov 2021). There is no reason that it should not work on subsequent monthly patches, but just take the backups to be sure.
1) Download the latest factory image for your device and platform-tools from the official Google site and extract them in one folder.
2) Extract the boot.img from image-raven-xxxxxxx.zip which was extracted from the image in the above step and patch it in Magisk Manager (latest canary build from https://github.com/topjohnwu/Magisk) on your phone and copy it back to the folder where you extracted the factory image and platform-tools. Rename the copied file to magisk_patched.img
3) Open flash-all.bat in notepad, add --skip-reboot and remove -w from the fastboot update line. Also add the following lines after the fastboot update line to flash the Magisk patched boot.img automatically:
fastboot reboot-bootloader
ping -n 5 127.0.0.1 >nul
fastboot flash boot magisk_patched.img
fastboot reboot
After editing, the edited part of your flash-all.bat should look something like this:
Code:
fastboot --skip-reboot update [****image_name****]
fastboot reboot-bootloader
ping -n 5 127.0.0.1 >nul
fastboot flash boot magisk_patched.img
fastboot reboot
echo Press any key to exit...
Note: [****image_name****] is just a placeholder and needs to be the name of zip file which was originally there in flash-all.bat, do not change that. Be careful to rename the Magisk patched boot.img to magisk_patched.img or in the alternative make appropriate modifications in the flash-all.bat
4) Open command prompt and go the folder where you extracted factory image and platform-tools. Type the following commands:
adb reboot bootloader
flash-all.bat
Your device should be upgraded to the latest factory image, while retaining root, without wiping data.
Update 1: I updated from 12.0.0 (SD1A.210817.036, Nov 2021) to 12.0.0 (SD1A.210817.037, Nov 2021) successfully using my method, without loosing data and root.
Update 2: I updated from 12.0.0 (SD1A.210817.037, Nov 2021) to 12.0.0 (SQ1D.211205.016.A1, Dec 2021) successfully using my method, without loosing data and root.
Update 3: I updated from 12.0.0 (SQ1D.211205.016.A1, Dec 2021) to 12.0.0 (SQ1D.220105.007, Jan 2022) successfully using my method, without loosing data and root.
Update 4: I updated from 12.0.0 (SQ1D.220105.007, Jan 2022) to 12.0.0 (SQ1D.220205.003, Feb 2022) successfully using my method, without loosing data and root.
Update 5: I updated from 12.0.0 (SQ1D.220205.003, Feb 2022) to Android 12L DP 3 successfully using my method, without loosing data and root.
Update 6: I updated from Android 12L DP 3 to Android 13 DP successfully using my method, without loosing data and root.
gururoop said:
Just a word of caution, I won't be able to support this guide every month because I am returning my Pixel 6 Pro. But it did give me a chance to experiment for the benefit of community, so here it is:
Note: I was already on the November patch, rooted before I tried flashing the November factory image again without wiping data and retaining root. There is no reason that it should not work on subsequent monthly patches, but just take the backups to be sure.
1) Download the latest factory image for your device and platform-tools from the official Google sites and extract them in one folder.
2) Extract the boot.img and patch it in magisk manager on your phone and copy it back to the folder where you extracted the factory image and platform-tools.
3) Open flash-all.bat in notepad and remove -w and add --disable-verity, -- disable verification and --skip-reboot to the fastboot update line. After editing, it should read as:
fastboot --disable-verity --disable-verification update image-raven-xxxxxxxxxxxx.zip --skip-reboot
4) Open command prompt and go the folder where you extracted factory image and platform-tools. Type the following commands:
adb reboot bootloader
flash-all.bat
5) After the factory image is flashed, use the volume down button to select reboot to bootloader option and press power button to execute. Then, open the command prompt again and go the folder where you extracted factory image and platform-tools. Type the following commands:
fastboot flash boot magisk_patched-xxxxx.img
fastboot reboot
Your device should be upgraded to the latest factory image, while retaining root, without wiping data.
Click to expand...
Click to collapse
Why did you return it?
Gytole said:
Why did you return it?
Click to expand...
Click to collapse
I've got Pixel 4 XL, which will get another OS upgrade. I don't want a big screen and I don't use camera. In 6 Pro, I was missing active edge (which I use for flashlight). Plus, I don't use my phone for gaming or any other heavy stuff, so I didn't feel as if it was a huge upgrade for me. Finally, I hate the huge camera module on the back.
gururoop said:
I've got Pixel 4 XL, which will get another OS upgrade. I don't want a big screen and I don't use camera. In 6 Pro, I was missing active edge (which I use for flashlight). Plus, I don't use my phone for gaming or any other heavy stuff, so I didn't feel as if it was a huge upgrade for me. Finally, I hate the huge camera module on the back.
Click to expand...
Click to collapse
Just about to try this method now as I too am on rooted 036 but want to dirty flash the latest factory image to hopefully fix some google play services bugs.
Did you buy the phone or get through a contract? Do Google/mobile network providers allow returns if it's been bootloader unlocked/relocked?
gururoop said:
I've got Pixel 4 XL, which will get another OS upgrade. I don't want a big screen and I don't use camera. In 6 Pro, I was missing active edge (which I use for flashlight). Plus, I don't use my phone for gaming or any other heavy stuff, so I didn't feel as if it was a huge upgrade for me. Finally, I hate the huge camera module on the back.
Click to expand...
Click to collapse
I hear yuh, I get mine today. I am coming from a Oneplus 6T, so it might be an upgrade for me. I understand though. Haha Thanks fam.
cd993 said:
Just about to try this method now as I too am on rooted 036 but want to dirty flash the latest factory image to hopefully fix some google play services bugs.
Did you buy the phone or get through a contract? Do Google/mobile network providers allow returns if it's been bootloader unlocked/relocked?
Click to expand...
Click to collapse
I got mine on a contract, but here in Canada, it is not allowed for the carriers to restrict bootloader unlocking. I will simply relock the bootloader before returning. That's what I did with Pixel 5 too.
Gytole said:
I hear yuh, I get mine today. I am coming from a Oneplus 6T, so it might be an upgrade for me. I understand though. Haha Thanks fam.
Click to expand...
Click to collapse
I am sure you will love it. I swapped my Oneplus 7 Pro for this Pixel 4 XL in 2020 and haven't regretted a single day. The monthly updates and betas are something that I love.
What's wrong with flashing the update, not rebooting, installing Magisk to the inactive slot, and then rebooting?
gururoop said:
Just a word of caution, I won't be able to support this guide every month because I am returning my Pixel 6 Pro. But it did give me a chance to experiment for the benefit of community, so here it is:
Note: I was already on the November patch, rooted before I tried flashing the November factory image again without wiping data and retaining root. There is no reason that it should not work on subsequent monthly patches, but just take the backups to be sure.
1) Download the latest factory image for your device and platform-tools from the official Google sites and extract them in one folder.
2) Extract the boot.img and patch it in magisk manager on your phone and copy it back to the folder where you extracted the factory image and platform-tools.
3) Open flash-all.bat in notepad and remove -w and add --disable-verity, -- disable verification and --skip-reboot to the fastboot update line. After editing, it should read as:
fastboot --disable-verity --disable-verification update image-raven-xxxxxxxxxxxx.zip --skip-reboot
4) Open command prompt and go the folder where you extracted factory image and platform-tools. Type the following commands:
adb reboot bootloader
flash-all.bat
5) After the factory image is flashed, use the volume down button to select reboot to bootloader option and press power button to execute. Then, open the command prompt again and go the folder where you extracted factory image and platform-tools. Type the following commands:
fastboot flash boot magisk_patched-xxxxx.img
fastboot reboot
Your device should be upgraded to the latest factory image, while retaining root, without wiping data.
Click to expand...
Click to collapse
Followed exactly, however it returned an error after running flash-all.bat and attempting to flash the boot.img (which had been patched).......
cd993 said:
Followed exactly, however it returned an error after running flash-all.bat and attempting to flash the boot.img (which had been patched).......
Click to expand...
Click to collapse
Are you sure you rebooted to bootloader after flash-all.bat finished?
gururoop said:
Are you sure you rebooted to bootloader after flash-all.bat finished?
Click to expand...
Click to collapse
flash-all.bat didn't finish as it stumbled when flashing the boot.img. It must not like the fact it's been extracted/patched/replaced?
Hmmmm
cd993 said:
flash-all.bat didn't finish as it stumbled when flashing the boot.img. It must not like the fact it's been extracted/patched/replaced?
Hmmmm
Click to expand...
Click to collapse
Did you replace the patched boot image in the zip file? You don't need to do that, just let flash-all.bat flash the original file and then flash the patched boot image as per the instructions.
spotmark said:
What's wrong with flashing the update, not rebooting, installing Magisk to the inactive slot, and then rebooting?
Click to expand...
Click to collapse
Some people have reported that it doesn't work because you need to disable verity and verification for new devices.
gururoop said:
Did you replace the patched boot image in the zip file? You don't need to do that, just let flash-all.bat flash the original file and then flash the patched boot image as per the instructions.
Click to expand...
Click to collapse
My bad, that's exactly what I did....
But now I'm getting this system 1/4 error?
I started a fresh with the extracted factory image too..... ?
{
"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"
}
Just tried this on my P6Pro. Managed to update from .015 to .036 and retained root.
Also still passing SafetyNet with USNF 2.2 beta
cd993 said:
My bad, that's exactly what I did....
But now I'm getting this system 1/4 error?
I started a fresh with the extracted factory image too..... ?
View attachment 5447353
Click to expand...
Click to collapse
I am not sure, but these kind of errors are usually related to cables. Try switching the cable and see.
In the end, flashing should happen on both boot slots. I have come across various posts (including also my tries) where partition B was active afterwards and root was gone.
Details how it works described in this thread/post
In the other method, when sideloading the OTA, you have to make sure to not reboot so that you can flash vbmeta before restarting in order to avoid Rescue Party and wiping your device. In this method, isn't vbmeta flashed in the batch file with verity and verfication disabled? Why do you have to prevent restart?
Annil said:
In the end, flashing should happen on both boot slots. I have come across various posts (including also my tries) where partition B was active afterwards and root was gone.
Details how it works described in this thread/post
Click to expand...
Click to collapse
Well, I have used this method for several months on my Pixel 4 XL (without disabling verity and verification) and now even on Pixel 6 Pro with same results. I have never tinkered with slots, but still managed to keep data and root.
Cares said:
In the other method, when sideloading the OTA, you have to make sure to not reboot so that you can flash vbmeta before restarting in order to avoid Rescue Party and wiping your device. In this method, isn't vbmeta flashed in the batch file with verity and verfication disabled? Why do you have to prevent restart?
Click to expand...
Click to collapse
Just to avoid the hassle of another reboot to flash the Magisk patched boot image for root.