Develop Bugs

[Guide] Persist error fix in YUREKA / PLUS [21-Apr-2016]

PERISIST ERROR IN TWRP WHILE FLASHING ANY ZIP.....? THEN HERE IS THE GUIDE
{
"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"
}
I am not responsible for anything that may happen to your phone as a result of installing custom roms and/or kernels. you do so at your own risk and take the responsibility upon yourself.
What is the persist partition?
Persist is partition mounted at /persist. It has ext4 file system. DRM releated files, sensor reg file (sns.reg), wifi and bluetooth mac addresses are stored there.
If you experience the following issues:
1. You get "e: cannot mount /persist" in recovery
2. Can't access to internal storage.
3. Boot loop on Lollipop 5.0 and above
4. IMEI number is lost even after formating cache and fastboot flash cache.img
5. No signal even after formating cache and fastboot flash cache.img
Then your persist partition have to be fixed​
Follow instructions carefully to solve this issue
NOTE : UNLOCK your device bootloader first before doing this
1. Download this " persist file & ADB+&+Fastboot of yureka " provided by @Annabathina
2. extract them in PC
3. open ADB+&+Fastboot of yureka
4. place presist.img file which you have extracted in ADB+&+Fastboot folder
5. Hold shift key and right click on mouse and select Open command window here
6. Connect your device to pc..... and make sure that drivers are installed properly..... ( VERY VERY IMPORTANT )
a. Type : adb devices
If your device is connected you will get it in connected devices list
b. Type : adb reboot-bootloader
Your phone will restart into bootloader.
c. Type : fastboot -i 0x1ebf flash persist persist.img
7. Disconnect your device from PC and REBOOT​
ADB+&+Fastboot : link
persist : link
Useful links
ADB for pc : link
YU usb drivers : link
PdaNet drivers : link
@Annabathina............................for Guide
Ricks ............... for Presist file
YU YUREKA
YU YUREKA PLUS​
XDA:DevDB Information
[Guide] Persist error fix in YUREKA / PLUS [21-Apr-2016], Tool/Utility for the YU Yureka
Contributors
Annabathina
Version Information
Status: Stable
Stable Release Date: 2016-04-21
Created 2016-04-21
Last Updated 2016-04-23

Reserved

Reserved

I dont get a multirom function in the advanced settings menu. Is it because im using twrp 3.0.... Or is it bcoz of persist partition ?
Sent from my AO5510 using XDA-Developers mobile app

After booting into fastboot mode .. i put the commands and then it just says "waiting for device"..

Bazilbycom said:
After booting into fastboot mode .. i put the commands and then it just says "waiting for device"..
Click to expand...
Click to collapse
Have you solved it?

saurav007 said:
Have you solved it?
Click to expand...
Click to collapse
Yes! .. All you have to do is install proper drivers for your device .
Use PDAnet and Google Usb Drivers

Hi,
For me the message is : is not possible to erase this partition
Thanks a lot for your help

still same error.....what to do now..??

Bazilbycom said:
Yes! .. All you have to do is install proper drivers for your device .
Use PDAnet and Google Usb Drivers
Click to expand...
Click to collapse
Earlier i was getting error even after installing all the drivers, all i needed was to update PDAnet on phone as well & it does everything.
Thank you it worked well!

still stucking
i was suffering of problem error persist but using this method it solved the error is gone but not still my device stuck on boot i tried many custom roms stock rom formats and all but still it stuck after 2 of android logo. in twrp recovery in mount option the system, persist, firmware are uncheck .i think it means they are not mount right??? i click many time to check and reboot but still logo stuck problem please give me solution!!!!!!!
Thank You

Can I flash this zip by twrp
Sent from my YU5510 using Tapatalk

vijaysingh1996 said:
Can I flash this zip by twrp
Sent from my YU5510 using Tapatalk
Click to expand...
Click to collapse
This isn't TWRP flashable zip. You have to flash via fastboot (see OP) after extracting the img from downloaded zip file.

Failing on my Pantech Sky Vega Iron 2 IM-A910S (codename: ef63) and bootloader unlocked.
In Fedora Linux the command continues to display "waiting for device" message even though the device is detected by "fastboot devices" command, although its serial number is not displayed and ???????? is display in that place.
While in Windows 7 (64-bit), the following error message is displayed after execution of the command "fastboot -i 0x1ebf flash persist persist.img":
target reported max download size of 1610612736 bytes
sending 'persist' (4324 KB)...
OKAY [ 0.165s]
writing 'persist'...
FAILED (remote: It is not surpport in user build.)
finished. total time: 0.186s
Any one please help...

In my device it showing can't load persist
After typing last line

shekarsahani said:
In my device it showing can't load persist
After typing last line
Click to expand...
Click to collapse
Can you post CMD screenshot?
Make sure the file name is same as in CMD.

Unfortunately I can't is send cmd screenshot it is not uploading..
When I type fastboot -i 0x1ebf flash persist persist.img then it shows error cannot load 'persist.img'

Unable to update AT&T XT1789-04 using Moto Smart Assistant

Hi Everyone,
I recently purchased an AT&T branded Z2 force. I SIM unlocked the device through the AT&T unlock portal, and subsequently OTA updated the phone to 7.1.1 (Ver. NCXS26.122-59-8-6, security level Sept. 1 2017). The phone thinks it is up to date but we all know Android 8 is available for this device.
I downloaded the latest update zip from android file host (NASH_ATT_OCXS27.109-47-14_subsidy-ATT_regulatory-DEFAULT_CFC.xml.zip).
I tried installing it in recovery mode but both ADB sideload and local installation types fail.
I tried Moto Smart Assistant but it says my device is unsupported. Screenshots:
{
"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"
}
Even the flashall.bat from the Return to stock thread didn't work. The fastboot commands simply hang when trying to transfer files to the phone (which is in bootloader mode).
The phone seems to be recognized correctly in the Windows Device Manager, and I already installed the Motorola Device Manager drivers.
I am stumped. I've rooted/installed custom roms on several android devices in the past, but I've never encountered one as stubborn as this.
Any input would be greatly appreciated. Thank you

Make sure you have the utilities.zip from the 'How to Return to Stock' thread unzipped in your firmware folder, which should be unzipped too. Might seem trivial, but for all intent they're known good and have worked 100s of times. Unplug your phone, close all prompts and the smart tool. Make sure you're using a 2.0 usb port directly from the mobo, not a 3.0 port or a hub port. Typically not an issue, but can be for some. Replug your phone and reboot to bootloader, verify connection with 'fastboot devices', and if all is set then run the flashall.bat
Feel free to post screenshot of your command prompt, and you can also post the output from the command 'fastboot getvar all' if it still doesn't succeed.

The update ZIP file from Android Host is for the Moto Z2 Play (not Force)

HKSpeed said:
The update ZIP file from Android Host is for the Moto Z2 Play (not Force)
Click to expand...
Click to collapse
Incorrect. Nash refers to the Z2 Force. It just happens to share a folder with the Z2 Play. You'd need to contact the folder's owner for a separate one to be made, but that's not necessary.
More importantly, attempts to flash these on the Play will likely result in bricks.

Smart Assistant didn't recognize that file I downloaded form Android Host. Instead Smart Assistant downloaded a different file and flashed it.
Android Host file: OCXS27.109-47-14
Smart Assistant (build # on my Z2 Force): OCXS27.109-47-17 (Nov 1, 2018 patch level date)

I have one as well and I just used the flshall but that did not work, it soft bricked. So then I used LSMA restore and now I have oreo.

41rw4lk said:
Make sure you have the utilities.zip from the 'How to Return to Stock' thread unzipped in your firmware folder, which should be unzipped too. Might seem trivial, but for all intent they're known good and have worked 100s of times. Unplug your phone, close all prompts and the smart tool. Make sure you're using a 2.0 usb port directly from the mobo, not a 3.0 port or a hub port. Typically not an issue, but can be for some. Replug your phone and reboot to bootloader, verify connection with 'fastboot devices', and if all is set then run the flashall.bat
Feel free to post screenshot of your command prompt, and you can also post the output from the command 'fastboot getvar all' if it still doesn't succeed.
Click to expand...
Click to collapse
Thanks for your help. I am not allowed to post screenshots as a new user. Here's a copy-paste of my command prompt (serial redacted):
Code:
Microsoft Windows [Version 10.0.17134.523]
(c) 2018 Microsoft Corporation. All rights reserved.
C:\Temp\FlashAllUtils>fastboot devices
ZY224BCXXX fastboot
C:\Temp\FlashAllUtils>flashall.bat
C:\Temp\FlashAllUtils>fastboot oem fb_mode_set
...
FAILED (remote: unknown command)
finished. total time: 0.002s
C:\Temp\FlashAllUtils>fastboot getvar max-sparse-size
getvar:max-sparse-size FAILED (remote: unknown command)
finished. total time: 0.004s
C:\Temp\FlashAllUtils>fastboot flash partition gpt.bin
(bootloader) slot-cou: not found
(bootloader) slot-suffi: not found
(bootloader) max-downlo: not found
target didn't report max-download-size
sending 'partition' (206 KB)...
FAILED (remote: unknown command)
finished. total time: 0.003s
C:\Temp\FlashAllUtils>fastboot flash bootloader bootloader.img
(bootloader) current-slott: not found
error: Failed to identify current slot
C:\Temp\FlashAllUtils>fastboot flash modem NON-HLOS.bin
(bootloader) slot-countott: not found
(bootloader) partition-: not found
target didn't report max-download-size
sending 'modem' (97411 KB)...
"Sending Modem" hangs indefinitely. Doesn't seem like anything is actually being sent to the device.

Your firmware.zip and utilities.zip should both be unzipped into one folder, see attached. The only thing that might be causing a problem, maybe not though, is the fact that everything is coming out of a Temp folder in your root directory. Whether that is an actual temp folder or just a folder you made called temp it's not a good choice to work out of. Certain namespaces and paths are subject to environmental variables and permissions; a folder named Temp in your root directory would definitely qualify. Try renaming the folder and make sure everything is unzipped in there.

Just a quick update: it looks like there was a hardware issue with the device; no laptop I tried (of 3) could properly communicate with the phone in both adb and fastboot modes.
I received my replacement from Motorola, and it was immediately identified by Lenovo Moto Smart Assistant

can't unlock bootloader by miflash

i was android 10 custom rom .
i used twrp to wip data .
i used mi flash to flash official android 9 rom to downgrade android 10.
but bymistake i checked flash_all_lock.bat
now the problem is
bootloader is locked + phone start when i choose language and select connection wifi or sim it reboot again
so i'm stuck now ,, no twrp or recovery work ,,
when try flash twrp from fastboot it say FAILED (remote: 'oem unlock is not allowed')
i don't have mi account and i never made one ............
there are the log from mi flash
[5:29:40 AM 2349f23c0005]:info:$fastboot -s 2349f23c0005 flash userdata C:\Users\gowan\OneDrive\Desktop\daisy_global_images_V9.6.11.0.ODLMIFF_8.1\\images\userdata.img ||
[5:29:45 AM 2349f23c0005]:err:Sending 'userdata' (181024 KB) OKAY [ 4.049s]
[5:29:45 AM 2349f23c0005]:err:Writing 'userdata' OKAY [ 1.264s]
[5:29:45 AM 2349f23c0005]:err:Finished. Total time: 5.813s
[5:29:45 AM 2349f23c0005]:info:$fastboot -s 2349f23c0005 set_active a
[5:29:45 AM 2349f23c0005]:err:Setting current slot to 'a' OKAY [ 0.020s]
[5:29:45 AM 2349f23c0005]:err:Finished. Total time: 0.023s
[5:29:45 AM 2349f23c0005]:info:$fastboot -s 2349f23c0005 oem lock 2>&1 | findstr /r "locked!" 2>&1 && fastboot -s 2349f23c0005 reboot
[5:29:46 AM 2349f23c0005]:flash done
[5:29:46 AM 2349f23c0005]rocess exit.
[5:29:46 AM 2349f23c0005]:flashSuccess True
[5:29:46 AM 2349f23c0005]:isFactory False CheckCPUID False
[5:29:46 AM 2349f23c0005]:before:flashSuccess is True set IsUpdate:True set IsDone True
[5:29:46 AM 2349f23c0005]:after:flashSuccess is True set IsUpdate:false set IsDone true
Click to expand...
Click to collapse
{
"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"
}
after this by 3 sec it reboot again

any way or go to shops ?

Are you able to enter in fastboot with keys combo?
If so you might try the following tool
Read carefully the file readme.md before starting
https://github.com/Szaki/XiaomiADBFastbootTools

You can boot twrp in fastboot mode and make a format data ( fastboot boot twrpname.img), use official twrp, try to Finish setup, enable developers options, enable usb debugging oem unlocking options, then go back to fastboot mode and type fastboot oem unlock

Os_Herdz said:
You can boot twrp in fastboot mode and make a format data ( fastboot boot twrpname.img), use official twrp, try to Finish setup, enable developers options, enable usb debugging oem unlocking options, then go back to fastboot mode and type fastboot oem unlock
Click to expand...
Click to collapse
I CAN go to fastboot but same error when flash any thing twrp
twrp is broken no recovery

srepole said:
Are you able to enter in fastboot with keys combo?
If so you might try the following tool
Read carefully the file readme.md before starting
https://github.com/Szaki/XiaomiADBFastbootTools
Click to expand...
Click to collapse
FAILED (remote: 'oem unlock is not allowed')
fastboot: error: Command failed

Maybe this helps
https://androidfilehost.com/?a=show&w=files&flid=38683
Download this Tool and Install, connect your Phone, then use on the right Side Flash factory, choose your original image and install.
Then finish the Phone Setup, activate Developer Options, activate OEM unlock and USB Debugging and retry to unlock and install twrp.

Big-Schrotty said:
Maybe this helps
https://androidfilehost.com/?a=show&w=files&flid=38683
Download this Tool and Install, connect your Phone, then use on the right Side Flash factory, choose your original image and install.
Then finish the Phone Setup, activate Developer Options, activate OEM unlock and USB Debugging and retry to unlock and install twrp.
Click to expand...
Click to collapse
it say can't modify system ..... - now way to install factory rom from fastboot
alltoolbox use fastboot

Well i think the last resource is trying to unbrick your device with EDL mode
But you'll have to physically open your phone
Once connected test-point and phone with usb cable you'll be able to see in device manager a new device
Use some metal tool like tweezers to connect the test points together
While holding test-points together connect your device to pc
After new device appeared in device manager you can release the test-points and continue
Press “refresh” in MiFlash tool
A new device should also appear
This means that everything is good and you've entered EDL mode
Then you'll have to flash phone
Here an example/tutorial
https://www.youtube.com/watch?v=BrEyAEXid_o

srepole said:
Well i think the last resource is trying to unbrick your device with EDL mode
But you'll have to physically open your phone
Once connected test-point and phone with usb cable you'll be able to see in device manager a new device
Use some metal tool like tweezers to connect the test points together
While holding test-points together connect your device to pc
After new device appeared in device manager you can release the test-points and continue
Press “refresh” in MiFlash tool
A new device should also appear
This means that everything is good and you've entered EDL mode
Then you'll have to flash phone
Here an example/tutorial
https://www.youtube.com/watch?v=BrEyAEXid_o
Click to expand...
Click to collapse
thx it worked <3

Howto - Root your bramble with Magisk

Hi everyone,
I just got my bramble today. And yes, the first thing I did, was unlocking the bootloader and rooting it.
Here I tell you how I did it.
You need a ADB/Fastboot suite installed and this rooted kernel.
Section 1: Unlocking your Bootloader Unlocking your Bootloader will erase all your data - so best case is a brandnew and clean bramble...:
1. Go to settings - "About phone" and tip 6 times on "Build number" until you see "congratulations, you are a developer"
2. Go to settings - "System", tip on "Advanced" and then on "Developer options". Now you can see "OEM unlocking". Enable it (yes it warns you about security and stuff... It´s your choice - I did it ).
3. Install Adb and Fastboot suite and scroll to the adb-folder inside your windows explorer and when you are there, copy the rooted boot.img to your adb-folder (you need that for section 2).
4. Right click + shift on the white background of your adb-folder "open power shell window here"
5. Reboot your bramble holding vol- and you will enter the fastboot screen. Connect your bramble to your pc and type in your power shell window the following code:
Code:
./fastboot flashing unlock
and hit enter
6. Your bramble will warn you that unlocking your bootloader is insecure! And one really important thing again: This will format all your data
7. Use the vol-/vol+ keys to accept and violla, you unlocked your Bootloader!
Section 2: flashing the patched boot.img
1. Luckily you already copied the rooted boot.img to your adb folder and you are still in your power shell window. That gives you everything for 2.
2. type the following in your power shell window:
Code:
./fastboot flash boot boot.img
3. hit enter and
4. reboot to system (yes it has to be setup again since your data got wipede) and install Magisk manager after setting up your system
Congrats, your system is now rooted with Magisk!

@TNSMANI, sorry, unfortunately I put this into the wrong forum. It hast to be unter "Guides news and discussion". Would you be so kind to put it from here to there? Thx.

Hey now ..thanks for posting .
I'm bootloader unlocked but when I run command to root ./fastboot flash boot boot.img.img
I get no such file or directory although I have it in my adb folder
If I take the last .img out I get okay
{
"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"
}

bkdodger said:
Hey now ..thanks for posting .
I'm bootloader unlocked but when I run command to root ./fastboot flash boot boot.img.img
I get no such file or directory although I have it in my adb folder
If I take the last .img out I get okay View attachment 5138473
Click to expand...
Click to collapse
He's got a case of the "didn't enable show file extensions" in windows. I downloaded my own system image and then patched the boot.img with magisk manager. I hate for you to have to piece it together, but I got my phone yesterday and worked through these things. Check it out here:
https://forum.xda-developers.com/pixel-4a-5g/help/magisk-boot-img-patching-flashing-t4191955

bkdodger said:
Hey now ..thanks for posting .
I'm bootloader unlocked but when I run command to root ./fastboot flash boot boot.img.img
I get no such file or directory although I have it in my adb folder
If I take the last .img out I get okay View attachment 5138473
Click to expand...
Click to collapse
Funny, maybe Gdrive removes double endings... I'll edit my post, thx!

Hey there,
after following your instructions Magisk Manager does not seem to detect Magisk (see Attachment). Can anyone help me figure out what am i missing?
Here's my consoleoutput:
Code:
$fastboot flashing unlock
OKAY [ 0.290s]
Finished. Total time: 0.291s
-------------------------------
$fastboot flash boot ./boot.img
Sending 'boot_b' (98304 KB) OKAY [ 2.850s]
Writing 'boot_b' OKAY [ 0.310s]
Finished. Total time: 3.520s
-------------------------------
Also: will there be a way to hide the 'device-is-unlocked-warning' on boot?
Thank you!

[Jan] said:
Hey there,
after following your instructions Magisk Manager does not seem to detect Magisk (see Attachment). Can anyone help me figure out what am i missing?
Here's my consoleoutput:
Code:
$fastboot flashing unlock
OKAY [ 0.290s]
Finished. Total time: 0.291s
-------------------------------
$fastboot flash boot ./boot.img
Sending 'boot_b' (98304 KB) OKAY [ 2.850s]
Writing 'boot_b' OKAY [ 0.310s]
Finished. Total time: 3.520s
-------------------------------
Also: will there be a way to hide the 'device-is-unlocked-warning' on boot?
Thank you!
Click to expand...
Click to collapse
That´s really strange! I have exactly the same console output... And it works for me.
Might it be possilbe that you use another rom build? I used the November -b build.
Maybe you can first update to the last os and then retry flashing my boot.img.
About BL-Warning. I have the same... And I dont´t know how to remove it. We would need to manipulate the bl, what I would not do...! Just ignore it!

Voodoojonny said:
;83961089']
That´s really strange! I have exactly the same console output... And it works for me.
Might it be possilbe that you use another rom build? I used the November -b build.
Maybe you can first update to the last os and then retry flashing my boot.img.
Click to expand...
Click to collapse
For me, it also didn't work with your pre-patched boot.img (also on latest November update). Had to download the factory image and patch it myself to make it work.

Voodoojonny said:
That´s really strange! I have exactly the same console output... And it works for me.
Might it be possilbe that you use another rom build? I used the November -b build.
Maybe you can first update to the last os and then retry flashing my boot.img.
About BL-Warning. I have the same... And I dont´t know how to remove it. We would need to manipulate the bl, what I would not do...! Just ignore it!
Click to expand...
Click to collapse
Hm.. actually been on the latest available build. Can you confirm this boot.img is working for build-id *.003.B1? (Also appended file-checksum, even though I doubt the file is damaged).
Code:
$shasum -a 256 ./boot.img
50fc81f5f59def3f366fcddd7976cbcbdc406172685c3e8a6cc24968d55c5964 ./boot.img
-------------------------------
$adb shell getprop | grep "ro.build.date\|ro.build.date\|ro.build.id\|ro.build.tags\|ro.build.product\|ro.build.version"
[ro.build.date]: [Tue Oct 6 11:12:31 UTC 2020]
[ro.build.date.utc]: [1601982751]
[ro.build.id]: [RD1A.201105.003.B1]
[ro.build.product]: [bramble]
[ro.build.tags]: [release-keys]
[ro.build.version.all_codenames]: [REL]
[ro.build.version.base_os]: []
[ro.build.version.codename]: [REL]
[ro.build.version.incremental]: [6886588]
[ro.build.version.min_supported_target_sdk]: [23]
[ro.build.version.preview_sdk]: [0]
[ro.build.version.preview_sdk_fingerprint]: [REL]
[ro.build.version.release]: [11]
[ro.build.version.release_or_codename]: [11]
[ro.build.version.sdk]: [30]
[ro.build.version.security_patch]: [2020-11-05]
-------------------------------
Simma said:
For me, it also didn't work with your pre-patched boot.img (also on latest November update). Had to download the factory image and patch it myself to make it work.
Click to expand...
Click to collapse
Thanks, will try this as well!
UPDATE: Got it successfully rooted by patching the factory image.

[Jan] said:
Hm.. actually been on the latest available build. Can you confirm this boot.img is working for build-id *.003.B1? (Also appended file-checksum, even though I doubt the file is damaged).
Code:
$shasum -a 256 ./boot.img
50fc81f5f59def3f366fcddd7976cbcbdc406172685c3e8a6cc24968d55c5964 ./boot.img
-------------------------------
$adb shell getprop | grep "ro.build.date\|ro.build.date\|ro.build.id\|ro.build.tags\|ro.build.product\|ro.build.version"
[ro.build.date]: [Tue Oct 6 11:12:31 UTC 2020]
[ro.build.date.utc]: [1601982751]
[ro.build.id]: [RD1A.201105.003.B1]
[ro.build.product]: [bramble]
[ro.build.tags]: [release-keys]
[ro.build.version.all_codenames]: [REL]
[ro.build.version.base_os]: []
[ro.build.version.codename]: [REL]
[ro.build.version.incremental]: [6886588]
[ro.build.version.min_supported_target_sdk]: [23]
[ro.build.version.preview_sdk]: [0]
[ro.build.version.preview_sdk_fingerprint]: [REL]
[ro.build.version.release]: [11]
[ro.build.version.release_or_codename]: [11]
[ro.build.version.sdk]: [30]
[ro.build.version.security_patch]: [2020-11-05]
-------------------------------
Thanks, will try this as well!
UPDATE: Got it successfully rooted by patching the factory image.
Click to expand...
Click to collapse
I don't know what I'm doing wrong I can't patch it .. unsuccessful..ughhh

bkdodger said:
I don't know what I'm doing wrong I can't patch it .. unsuccessful..ughhh
Click to expand...
Click to collapse
My advice would be:
- ensure you got the factory image from developer.google.com corresponding to your buildnumber
- ensure you are using canary magisk manager (which is the only version as of today supporting redfin and bramble)

[Jan] said:
My advice would be:
- ensure you got the factory image from developer.google.com corresponding to your buildnumber
- ensure you are using canary magisk manager (which is the only version as of today supporting redfin and bramble)
Click to expand...
Click to collapse
I check the build is latest ...my Magisk is below

bkdodger said:
I check the build is latest ...my Magisk is below View attachment 5138961
Click to expand...
Click to collapse
Magisk version fits.
What about the boot.img file? It should be originated from path '*/bramble-{buildnumber}-factory-{sha}.zip/bramble-{buildnumber}/image-bramble-{buildnumber}.zip/boot.img'.

[Jan] said:
Magisk version fits.
What about the boot.img file? It should be originated from path '*/bramble-{buildnumber}-factory-{sha}.zip/bramble-{buildnumber}/image-bramble-{buildnumber}.zip/boot.img'.
Click to expand...
Click to collapse
Oh maybe I'm doing this part wrong ? I moved over the top file

bkdodger said:
Oh maybe I'm doing this part wrong ? I moved over the top file
Click to expand...
Click to collapse
It's the boot.img inside the next zip (image-bramble...)

Simma said:
It's the boot.img inside the next zip (image-bramble...)
Click to expand...
Click to collapse
Thanks for reply ..it was in there and I finally got it rooted ...I really don't know why it was not working but the third time was the charm ...[emoji16]

I'm trying to install Magisk, but I need a custom recovery. I can't figure out how to install one. TWRP app keeps force-closing when I try to install it, and there's no Pixel 4a 5G listed in devices in the TWRP website. I also can't find anything from ClockworkMod.

Hey, there ist no custom recovery available yet, becouse this phone is brandnew! There will be TWRP and other recoveries in the future, until then, we need to be creative. One way is extracting and patching the boot.img and reflash it via fastboot. How to do that is described in OP!

I got Magisk working. However, I cannot pass safetynet. I tried the props workaround mentioned in the 4a guide, but it still does not work.

WhiteAsIce said:
I got Magisk working. However, I cannot pass safetynet. I tried the props workaround mentioned in the 4a guide, but it still does not work.
Click to expand...
Click to collapse
Have you tried hiding the apps in Magisk? Do you want safetynet for a specific app that won't launch/complains about being rooted? Try MagiskHide in Magisk Manager if you haven't. Exclude those apps to hide root from them.

Question Can't load ROM - OnePlus 9 Pro bricked

Hi,
I want ask for help with recovery of my One Plus 9 Pro. The smartphone was oryginally in LE2120 (China) version but with India ROM (LE2121). I Wanted change it for EU ROM (LE2123) but that crashesh my phone...
After hours of failed attempts I don;t know what else I can do...
First ROM install attemt ended with errors on first pics. Next I've installed TWRP and now after each start of OnePlus it launches TWRP ant nothing else. I can ewentually go to the fastboot menu.
From TWRP I can't do repair, upload files from my PC, repair filesystem - amost nothing... Errors in another attached pics..
I've try to use MSM Tools and push files using EDL but it also finished with error (another attached pics).
In current state I can't go to the fastbootD menu (only TWRP available and launching automatically). When trying go to fastbootD - getting error (attachement).
I have downloaded many versions of OnePlus ROM's and recovery files with MSM Tolls but with any results - all of them eded with the same eerors like in attachements.
Please help what I should do now to get my Oneplus working again.

Let me think....

Try using the Eu MSM. I've read on oneplus community someone had a similar problem. Google "msmtool for le2120" and it should be one of the first results.

Marffi said:
Hi,
I want ask for help with recovery of my One Plus 9 Pro. The smartphone was oryginally in LE2120 (China) version but with India ROM (LE2121). I Wanted change it for EU ROM (LE2123) but that crashesh my phone...
After hours of failed attempts I don;t know what else I can do...
First ROM install attemt ended with errors on first pics. Next I've installed TWRP and now after each start of OnePlus it launches TWRP ant nothing else. I can ewentually go to the fastboot menu.
From TWRP I can't do repair, upload files from my PC, repair filesystem - amost nothing... Errors in another attached pics..
I've try to use MSM Tools and push files using EDL but it also finished with error (another attached pics).
In current state I can't go to the fastbootD menu (only TWRP available and launching automatically). When trying go to fastbootD - getting error (attachement).
I have downloaded many versions of OnePlus ROM's and recovery files with MSM Tolls but with any results - all of them eded with the same eerors like in attachements.
Please help what I should do now to get my Oneplus working again.
Click to expand...
Click to collapse
In twrp you can goto advanced->adb sideload, to flash roms.
You can also go into twrp fastbootd, if you follow these steps:
normally boot into twrp with "fastboot boot"
in twrp goto reboot->fastboot
while shutting down hold power+vol down (brings you to bootloader)
run fastboot boot twrp.img
For flashing partitions in fastboot you can always use _slot instead of --slot. For example "fastboot flash boot --slot=a boot.img" ->"fastboot flash boot_a boot.img". Same has to be done with slot b.
It could also be a good idea to use LE2120 MSM to go back to a usable state.

Since your original firmware was from India, I can mod you an MSM tool to flash the EU firmware. Give me a couple hours. Have to run an errand in town first...

In the meantime use the IN MSM Tool to revive your phone then wait for my mod MSM Tool to flash EU to phone.

der_akinator said:
In twrp you can goto advanced->adb sideload, to flash roms.
You can also go into twrp fastbootd, if you follow these steps:
normally boot into twrp with "fastboot boot"
in twrp goto reboot->fastboot
while shutting down hold power+vol down (brings you to bootloader)
run fastboot boot twrp.img
For flashing partitions in fastboot you can always use _slot instead of --slot. For example "fastboot flash boot --slot=a boot.img" ->"fastboot flash boot_a boot.img". Same has to be done with slot b.
It could also be a good idea to use LE2120 MSM to go back to a usable state.
Click to expand...
Click to collapse
Unfortunatley not I can't go to fastbootd. When trying do that I'm getting another error:

Marffi said:
Unfortunatley not I can't go to fastbootd. When trying do that I'm getting another error:
Click to expand...
Click to collapse
Use the IN MSM Tool to revive phone... In edl mode.
OP9Pro - Repository of MSM Unbrick Tools (TMO, EU, GLO, IN)
By using these tools, you accept full responsibility for your actions. Your warranty is void should you run any of these utilities without OnePlus support present. I am not responsible for bricks, fires, nuclear war, etc. If you modified any...
forum.xda-developers.com

here you go.......
File on MEGA
mega.nz

In EDL mode using new downlod the same error as previous

TheGhost1951 said:
here you go.......
File on MEGA
mega.nz
Click to expand...
Click to collapse
Using moded MSM Tools I've get messages:
1. Try Firehose Communication Handshake
2. Setting Firehose Communication Data trasmi...
3. Get TID Failed
and nothing more.
Log File:
[2472][05-17 16:38:43.843]<4> Set Proc Mode 0
[2472][05-17 16:38:43.996]<2> =========================================================
[2472][05-17 16:38:43.996]<2> | OnePlus DL PID:14264
[2472][05-17 16:38:43.996]<2> | Execute: 2023/05/17 14:38 GMT
[2472][05-17 16:38:43.996]<2> =========================================================
[2472][05-17 16:38:50.359]<4>
========================================================
[2472][05-17 16:39:06.535]<4> MetadataVersion=2,CryptVersion=1,[2472][05-17 16:39:06.535]<4> m_bIsPackImage=1
[2472][05-17 16:39:06.566]<4> Set Proc Mode 1
[2472][05-17 16:39:06.766]<4> ATO element doesn't exist. Skip.
[2472][05-17 16:39:06.782]<4> Project Name: 20857
[2472][05-17 16:39:06.782]<4> Factory ID: 20857IN
[2472][05-17 16:39:06.782]<4> Image Version: lemonadep_22_I.07_210412
[2472][05-17 16:39:06.782]<4> Skip SHA256 Check: No
[2472][05-17 16:39:06.782]<4> HW CHK: No
[2472][05-17 16:39:06.782]<4> RF CHK: No
[2472][05-17 16:39:06.782]<4> PRJ CHK: No
[2472][05-17 16:39:06.798]<4> MDL CHK: Yes
[2472][05-17 16:39:06.798]<4> ATO build: No
[2472][05-17 16:39:06.798]<4> Load upd cfg failed. continue.
[2472][05-17 16:39:06.798]<4> frp: 1
[2472][05-17 16:39:06.798]<4> Tool version verified! (V5.1.77)
[2472][05-17 16:39:06.798]<4> project 20857 not support boot mode feature
[2472][05-17 16:39:06.798]<4> project 20857 enable fuse
[2472][05-17 16:39:06.835]<4> [1] dwMajorVersion=6,dwMinorVersion=2,is_win7_system=0
[2472][05-17 16:39:06.873]<4> Skip multi-image identify: 0
[13140][05-17 16:39:15.492]<4> Device Arrival: \\?\USB#VID_05C6&PID_9008#5&318e2ee3&0&1#{86e0d1e0-8089-11d0-9ce4-08003e301f73}
[6740][05-17 16:39:19.069]<4> [0] SetComStep: 1
[6740][05-17 16:39:19.069]<4> [0] GetComStep: 1
[6740][05-17 16:39:19.071]<4> CID = -1
[6740][05-17 16:39:19.071]<4> Non TMO group
[6740][05-17 16:39:19.085]<4> [1] Set device as UFS
[6740][05-17 16:39:19.311]<4> [1] [CSerialCommHelper] Buf: 0 (16/10)
[6740][05-17 16:39:19.327]<4> [1] [CSerialCommHelper] No data in buffer to be sent 0
[6740][05-17 16:39:21.514]<4> [1] [SP][195] Check cmd done status failed. 1
[6740][05-17 16:39:21.637]<4> [1] [SP][208] Reset Sahara
[6740][05-17 16:39:21.852]<4> [1] [COM1] AddCpuIDtoIndex cupid(8aeb0289)
[6740][05-17 16:39:25.061]<4> [1] UFS Inquiry Command Output: SAMSUNG KLUEG8UHDB-C2D1 1903
[6740][05-17 16:39:25.061]<4> [1] UFS info Vendor = samsung, TotalLogicalBlocks = 499892224
[6740][05-17 16:39:25.061]<4> [1] [FFU]FWversion 903
[6740][05-17 16:39:25.061]<4> [1] [FFU] UFS Total Active LU 6
[6740][05-17 16:39:25.061]<4> [1] EmmcSizeInGB = 238.367188, TotalLogicalBlocks = 499892224
[6740][05-17 16:39:25.061]<4> [1] Memory size:
[6740][05-17 16:39:25.061]<4> [1] Not in intranet, pass.[6740][05-17 16:39:25.077]<4> [1] [Firehose] HwVersion = 22
[6740][05-17 16:39:25.093]<4> [1] [Firehose] RfVersion = 11
[6740][05-17 16:39:25.124]<4> [1] [Firehose] PrjVersion = 11
[6740][05-17 16:39:25.146]<4> [1] Get SW ID failed.
[13140][05-17 16:40:15.427]<4> Device Remove: \\?\USB#VID_05C6&PID_9008#5&318e2ee3&0&1#{86e0d1e0-8089-11d0-9ce4-08003e301f73}
[13140][05-17 16:42:34.518]<4> Device Arrival: \\?\USB#VID_05C6&PID_9008#5&318e2ee3&0&1#{86e0d1e0-8089-11d0-9ce4-08003e301f73}
[18596][05-17 16:42:36.464]<4> [0] SetComStep: 1
[18596][05-17 16:42:36.464]<4> [0] GetComStep: 1
[18596][05-17 16:42:36.466]<4> CID = -1
[18596][05-17 16:42:36.466]<4> Non TMO group
[18596][05-17 16:42:36.470]<4> [1] Set device as UFS
[18596][05-17 16:42:36.704]<4> [1] [CSerialCommHelper] Buf: 0 (16/10)
[18596][05-17 16:42:36.720]<4> [1] [CSerialCommHelper] No data in buffer to be sent 0
[18596][05-17 16:42:38.924]<4> [1] [SP][195] Check cmd done status failed. 1
[18596][05-17 16:42:39.025]<4> [1] [SP][208] Reset Sahara
[18596][05-17 16:42:39.256]<4> [1] [COM1] AddCpuIDtoIndex cupid(8aeb0289)
[18596][05-17 16:42:42.432]<4> [1] UFS Inquiry Command Output: SAMSUNG KLUEG8UHDB-C2D1 1903
[18596][05-17 16:42:42.432]<4> [1] UFS info Vendor = samsung, TotalLogicalBlocks = 499892224
[18596][05-17 16:42:42.432]<4> [1] [FFU]FWversion 903
[18596][05-17 16:42:42.432]<4> [1] [FFU] UFS Total Active LU 6
[18596][05-17 16:42:42.432]<4> [1] EmmcSizeInGB = 238.367188, TotalLogicalBlocks = 499892224
[18596][05-17 16:42:42.432]<4> [1] Memory size:
[18596][05-17 16:42:42.432]<4> [1] Not in intranet, pass.[18596][05-17 16:42:42.447]<4> [1] [Firehose] HwVersion = 22
[18596][05-17 16:42:42.463]<4> [1] [Firehose] RfVersion = 11
[18596][05-17 16:42:42.501]<4> [1] [Firehose] PrjVersion = 11
[18596][05-17 16:42:42.516]<4> [1] Get SW ID failed.
[13140][05-17 16:42:48.489]<4> Device Remove: \\?\USB#VID_05C6&PID_9008#5&318e2ee3&0&1#{86e0d1e0-8089-11d0-9ce4-08003e301f73}
and second one:
IA V1.0
FCL V1.2
PL V1.9
MVL V1.3
SID 300 is non enc
Encrytped block of item 20 is incorrect
SID 300 is non enc
Encrytped block of item 20 is incorrect

Marffi said:
Unfortunatley not I can't go to fastbootd. When trying do that I'm getting another error:
Click to expand...
Click to collapse
This error shouldn't be a problem, but you probably have to wait 5-10 seconds to use fastboot. You can also flash boot, vendor_boot and dtbo of any rom and use their fastbootd.

der_akinator said:
This error shouldn't be a problem, but you probably have to wait 5-10 seconds to use fastboot. You can also flash boot, vendor_boot and dtbo of any rom and use their fastbootd.
Click to expand...
Click to collapse
Do you think he could get to recovery from fastboot and factory reset?

Or from fastboot flash update payload.bin?

TheGhost1951 said:
Do you think he could get to recovery from fastboot and factory reset?
Click to expand...
Click to collapse
Yes, should work with all recoveries with "fastboot reboot recovery"
Payload has to be extracted, but after that you can flash all partitions from fastbootd.
One caveat is that MSM payload contains some partitions that are not included in OTA payload.bin
Edit:
MSM payload can be extracted with this: https://github.com/bkerler/oppo_decrypt
But I don't know if the extra MSM partitions are flashable with fastboot.

der_akinator said:
Yes, should work with all recoveries with "fastboot reboot recovery"
Payload has to be extracted, but after that you can flash all partitions from fastbootd.
One caveat is that MSM payload contains some partitions that are not included in OTA payload.bin
Click to expand...
Click to collapse
"
C:\ADB>fastboot reboot recovery
Rebooting into recovery OKAY [ 0.016s]
Finished. Total time: 0.016s
"
Phone just restart and automatically load TWRP. Nothing more.

Marffi said:
"
C:\ADB>fastboot reboot recovery
Rebooting into recovery OKAY [ 0.016s]
Finished. Total time: 0.016s
"
Phone just restart and automatically load TWRP. Nothing more.
Click to expand...
Click to collapse
Yes that's was the answer to @TheGhost1951 question.

TheGhost1951 said:
Or from fastboot flash update payload.bin?
Click to expand...
Click to collapse
"
C:\ADB>fastboot devices
8aeb0289 fastboot
C:\ADB>fastboot flash update payload.bin
error: write_sparse_skip_chunk: don't care size 4211328355 is not a multiple of the block size 4096
Sending sparse 'update' 1/7 (786428 KB) error: write_sparse_skip_chunk: don't care size 4211328355 is not a multiple of the block size 4096
error: write_sparse_skip_chunk: don't care size 4211328355 is not a multiple of the block size 4096
OKAY [ 19.952s]
Writing 'update' FAILED (remote: 'Partition not found')
fastboot: error: Command failed
"
So failed as well

What was the last MSM tool tried? Did you try the Indian MSM tool?

TMO 9PRO LAST OPTION HARDBRICKED FIX & BACK TO TMO STOCK FIX
Frist off I'm not Responsible for anything that happens to your phone!!! DO NOT FLASH UNLESS YOU TRIED EVERYTHING ELSE FIRST INDIA MSM TOOL TO FIX YOUR HARD BRICKED T-MOBILE 9PR0!!!! DO THIS AT YOUR OWEN RISK!!! DISCLAIMER: THIS WILL...
forum.xda-developers.com