So I have a quick question.
I have unlocked my bootloader and rooted my v60. The updates to Android 12 are erroring out. I get nag screens once every three days or so to update.
If I want to update my v60 to Android 12, and allow the OTA update to work, what must I walk back?
Relock the bootloader, and unroot?
Just relock the bootloader?
Just unroot?
Anyone know?
[NG]Owner
Replacing only the patched boot_a and boot_b with stock boot_a and boot_b did not allow for an OTA update. It continued to error out.
Is there a method of updating from A11 to A12 if you are rooted and bootloader unlocked that doesn't require rebuilding the phone?
Locking and unlocking the bootloader will force a wipe. Don't want to have to rebuild my phone.
What will happen if I replace abl_a and abl_b with the stock versions (the engineering bootloader is currently in both slots)? Will I lose the unlocked status of the phone, and then regain it automatically when I revert back to the engineering bootloader? Will swapping out these two partitions with their stock versions brick the phone if I don't first go in and relock the bootloader? If I have to relock when loading stock abl_a and abl_b, I've forced myself down the path of rebuilding the phone, which I want to avoid.
Using LGUP Refurbish is also a non-starter as data gets wiped.
Any guidance?
[NG]Owner
The short answer is: NO. Once you are rooted, there is no OTA/LGUP update possible.
Reflashing the stock boot_a and boot_b worked for me.. i have the tmobile variant, not sure if that makes things any different or not though.. Be careful to not flash the android 11 boot_a and boot_b otherwise you won't have working wifi/data/bluetooth, etc. ensure its the original non modified boot_a and boot_b from android 12.
texas7412 said:
Reflashing the stock boot_a and boot_b worked for me.. i have the tmobile variant, not sure if that makes things any different or not though.. Be careful to not flash the android 11 boot_a and boot_b otherwise you won't have working wifi/data/bluetooth, etc. ensure its the original non modified boot_a and boot_b from android 12.
Click to expand...
Click to collapse
Yes,the engineering bootloader works for a12.I'm currently using it on a12 30a AT&T firmware and wifi/bluetooth/mobile data all work.This is currently what I'm using for a12 for boot_a and boot_b.
texas7412 said:
Reflashing the stock boot_a and boot_b worked for me.. i have the tmobile variant, not sure if that makes things any different or not though.. Be careful to not flash the android 11 boot_a and boot_b otherwise you won't have working wifi/data/bluetooth, etc. ensure its the original non modified boot_a and boot_b from android 12.
Click to expand...
Click to collapse
That does not address the question of OP relating to OTA update. Additionally, if you reflash "boot_a" and "boot_b" then you lose the rooted status.
Royaltiger said:
The short answer is: NO. Once you are rooted, there is no OTA/LGUP update possible.
Click to expand...
Click to collapse
Flash new kdz, done. If files are needed try replacing boot
Once you flash a new KDZ file, you will lose the root privilege.
Royaltiger said:
That does not address the question of OP relating to OTA update. Additionally, if you reflash "boot_a" and "boot_b" then you lose the rooted status.
Click to expand...
Click to collapse
Yes, you reflash the modified boot_a and boot_b files after you do the ota update and you have root and an updated device
texas7412 said:
Reflashing the stock boot_a and boot_b worked for me.. i have the tmobile variant, not sure if that makes things any different or not though.. Be careful to not flash the android 11 boot_a and boot_b otherwise you won't have working wifi/data/bluetooth, etc. ensure its the original non modified boot_a and boot_b from android 12.
Click to expand...
Click to collapse
So I'm supposed to source the original non modified boot_a and boot_b from android 12, and then flash them to my existing A11 device? Then the device will OTA update to a12? Sounds fishy.
Leronex_1 said:
Flash new kdz, done. If files are needed try replacing boot
Click to expand...
Click to collapse
Unless I'm mistaken, there is no TMo kdz for a12 yet.
[NG]Owner
Related
I tried to flash a downgrade image to my moto e 2nd gen. Now Im stuck in bootloader and a warning message for unlocked bootloder. Ive tried to flash logo.bin, and other images aswell with no luck. It keeps asking me to install a valid signed images, I don't know where to find these images. Please help!
You need to do exactly what it's asking you to do - flash valid signed images. Which model do you have (XT152x)? Which region are you in? Which version were you downgrading from?
Just so you know, downgrading the stock ROM is very highly discouraged as it can cause bricking in certain circumstances. In particular, never try to downgrade the stock ROM when the bootloader is locked. You can try flashing back the upgraded images and seeing if your phone accepts them. Be aware that the signed images must match your model number and region.
squid2 said:
You need to do exactly what it's asking you to do - flash valid signed images. Which model do you have (XT152x)? Which region are you in? Which version were you downgrading from?
Just so you know, downgrading the stock ROM is very highly discouraged as it can cause bricking in certain circumstances. In particular, never try to downgrade the stock ROM when the bootloader is locked. You can try flashing back the upgraded images and seeing if your phone accepts them. Be aware that the signed images must match your model number and region.
Click to expand...
Click to collapse
Thanks for reply.
I don't have these images, where to get them? My model is xt1524reteuall, I'm in europe/sweden and I downgraded from stock Lollipop 5.0.2
I did unlock the bootloader via motorolas site.
pemhak said:
Thanks for reply.
I don't have these images, where to get them? My model is xt1524reteuall, I'm in europe/sweden and I downgraded from stock Lollipop 5.0.2
I did unlock the bootloader via motorolas site.
Click to expand...
Click to collapse
Hmm, so you went from a newer 5.0.2 build to an old 5.0.2 build? What were you downgrading to?
Go to this folder: https://mega.nz/#F!rMIhDLgR!oq5Cz_XbgZLEEysmqoYtcA
Navigate to Surnia ->5.0.2
Look for the file XT1524_RETEUALL_MOTOE2... (it's near the middle of the list)
Download and try flashing everything it in using fastboot.
squid2 said:
You need to do exactly what it's asking you to do - flash valid signed images. Which model do you have (XT152x)? Which region are you in? Which version were you downgrading from?
Just so you know, downgrading the stock ROM is very highly discouraged as it can cause bricking in certain circumstances. In particular, never try to downgrade the stock ROM when the bootloader is locked. You can try flashing back the upgraded images and seeing if your phone accepts them. Be aware that the signed images must match your model number and region.
Click to expand...
Click to collapse
Thanks for reply.
I don't have these images, where to get them? My model is xt1524reteuall, I'm in europe/sweden and I downgraded from stock Lollipop 5.0.2
I did unlock the bootloader via motorolas site.
I got my device back!! I did succeed to flash it with this rom "surnia_stock_5.0.2.zip" with TWRP. I did not have the patience to wait at the Motorola logo when booting, I have to wait 2-3 min and 2-3 min for services to start. for the device to boot. But now it doesn't register any sim card when at desktop?!?
squid2 said:
Hmm, so you went from a newer 5.0.2 build to an old 5.0.2 build? What were you downgrading to?
Go to this folder:
Navigate to Surnia ->5.0.2
Look for the file XT1524_RETEUALL_MOTOE2... (it's near the middle of the list)
Download and try flashing everything it in using fastboot.
Click to expand...
Click to collapse
I was downgrading to kitkat 4.4.4 due to poor battery in lollipop 5.0.2. I'm downloading a xt1524reteuall rom right now but ir is going slowly.
pemhak said:
I was downgrading to kitkat 4.4.4 due to poor battery in lollipop 5.0.2. I'm downloading a xt1524reteuall rom right now but ir is going slowly.
Click to expand...
Click to collapse
Oh, you must have flashed something really wrong then. There are no 4.4.4 ROMs for this device. You would have flashed something totally incompatible and highly risky if you flashed 4.4.4 from somewhere. That may have wrecked your modem software too. Download and flash the proper XT1524-specific software with the correct modem. If you are unhappy with the performance of the stock ROM, you can flash scritch007's CM12.1.
squid2 said:
Oh, you must have flashed something really wrong then. There are no 4.4.4 ROMs for this device. You would have flashed something totally incompatible and highly risky if you flashed 4.4.4 from somewhere. That may have wrecked your modem software too. Download and flash the proper XT1524-specific software with the correct modem. If you are unhappy with the performance of the stock ROM, you can flash scritch007's CM12.1.
Click to expand...
Click to collapse
Ok, thanks. I will wait for download to complete and flash that image.
pemhak said:
Ok, thanks. I will wait for download to complete and flash that image.
Click to expand...
Click to collapse
Hi! Did you solve your problem? I'm kind of stuck on same problem and with no working solution yet.
EDIT: I tried the @squid2 with no success. Maybe I will send the phone to waranty....
Noeljunior said:
Hi! Did you solve your problem? I'm kind of stuck on same problem and with no working solution yet.
EDIT: I tried the @squid2 with no success. Maybe I will send the phone to waranty....
Click to expand...
Click to collapse
I did solve the problem with these steps.
1. Find and download the files for your region.
2. Unzip files to a folder with fastboot and adb.
3. Create stock.bat with these commands and run stock.bat within the same folder as above files.
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase userdata
fastboot erase customize
fastboot oem config carrier vzw
fastboot oem fb_mode_clear
fastboot reboot
(4. I needed to reunlock my Moto E 2nd Gen at Motorolas site, because i did relock it.)
5. Get into bootloader menu and flash this TWRP image (i can email it to you) within the same folder and flash it with fastboot.
6. Restart phone. Wait 2-3 minutes so it boots into android.
7. Hope I made it clear enough to follow the instructions, if you got questions please reply and I try to answer them. Sorry for my poor english.
pemhak said:
I did solve the problem with these steps.
1. Find and download the files for your region.
2. Unzip files to a folder with fastboot and adb.
3. Create stock.bat with these commands and run stock.bat within the same folder as above files.
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase userdata
fastboot erase customize
fastboot oem config carrier vzw
fastboot oem fb_mode_clear
fastboot reboot
(4. I needed to reunlock my Moto E 2nd Gen at Motorolas site, because i did relock it.)
5. Get into bootloader menu and flash this TWRP image (i can email it to you) within the same folder and flash it with fastboot.
6. Restart phone. Wait 2-3 minutes so it boots into android.
7. Hope I made it clear enough to follow the instructions, if you got questions please reply and I try to answer them. Sorry for my poor english.
Click to expand...
Click to collapse
And I'm back with my Moto E! Thank you! I wasn't doing some of those commands and with all those commands it works! Thank you!
Disregard
I used a payload extraction tool to open up the OTA file and then flashed each partition via fastboot manually (saw it in a oneplus thread) phone is currently at the boot screen which is much further than it was any time before this, going to give it a little more time before trying anything further as I did a factory reset before upgrading so it could just be first booting.
thoughtlesskyle said:
I messed up while trying to install the android 10 update, I have backups of my stock boot images but not my system paritionwas on MP2) my system partition is now wiped
I can only get to the bootloader but accessing anything else just results in a bootloop so I can't install the OTA updates, I do however still have a working fastboot.
does anyone have a backup of their paritions that I can flash via fastboot?
I also can't seem to boot twrp from fastboot anymore either
any help is appreciated
Click to expand...
Click to collapse
First you didn't state your device model or version.
Android 10 update will lock your bootloader, and till now the unlocking code is no where to be found, and so it can't be rooted unless it is unlocked.
So what you could do is swapping your current partition slot to the one with Android 9 if you want to have root, flash your phone, or booting TWRP.
Code:
fastboot set_active other
Then reboot your phone to bootloader, and you will see that it is unlocked, and do 'Factory Reset' if needed.
Warning do not try to flash anything while the bootloader is locked.
If you have BS 2 Pro global and want to flash MP2 back, check my thread.
Goodluck
KM7 said:
First you didn't state your device model or version.
Android 10 update will lock your bootloader, and till now the unlocking code is no where to be found, and so it can't be rooted unless it is unlocked.
So what you could do is swapping your current partition slot to the one with Android 9 if you want to have root, flash your phone, or booting TWRP.
Code:
fastboot set_active other
Then reboot your phone to bootloader, and you will see that it is unlocked, and do 'Factory Reset' if needed.
Warning do not try to flash anything while the bootloader is locked.
If you have BS 2 Pro global and want to flash MP2 back, check my thread.
Goodluck
Click to expand...
Click to collapse
Okay further update, I am using a SKW-H01, I flashed all the partitions from the 10 update manually and hung at a bootloop rebooted to recovery after waiting a little while and factory reset now I am fully booted. I didn't read enough or else I would have been smarter about trying an android 10 build to recover the phone because of it locking the bootloader. Either way we are all good to go. Thanks for your help. I was just stupid and went into it unprepared. I have messed around with a lot of devices over the years but never one that had a payload.bin instead of a factory image.
WE'RE ALL GOOD NOW THOUGH!
thoughtlesskyle said:
Okay further update, I am using a SKW-H01, I flashed all the partitions from the 10 update manually and hung at a bootloop rebooted to recovery after waiting a little while and factory reset now I am fully booted. I didn't read enough or else I would have been smarter about trying an android 10 build to recover the phone because of it locking the bootloader. Either way we are all good to go. Thanks for your help. I was just stupid and went into it unprepared. I have messed around with a lot of devices over the years but never one that had a payload.bin instead of a factory image.
WE'RE ALL GOOD NOW THOUGH!
Click to expand...
Click to collapse
Good to know that you managed to boot it. Hope things are working well for you.
thoughtlesskyle said:
Okay further update, I am using a SKW-H01, I flashed all the partitions from the 10 update manually and hung at a bootloop rebooted to recovery after waiting a little while and factory reset now I am fully booted. I didn't read enough or else I would have been smarter about trying an android 10 build to recover the phone because of it locking the bootloader. Either way we are all good to go. Thanks for your help. I was just stupid and went into it unprepared. I have messed around with a lot of devices over the years but never one that had a payload.bin instead of a factory image.
WE'RE ALL GOOD NOW THOUGH!
Click to expand...
Click to collapse
22 sections.
Yes, all the partitions had to be flashed to run it.
Code:
fastboot flash xbl_config_a rom/xbl_config.img
fastboot flash xbl_a rom/xbl.img
fastboot flash vendor_a rom/vendor.img
fastboot flash vbmeta_a rom/vbmeta.img
fastboot flash uefisecapp_a rom/uefisecapp.img
fastboot flash tz_a rom/tz.img
fastboot flash system_a rom/system.img
fastboot flash qupfw_a rom/qupfw.img
fastboot flash modem_a rom/modem.img
fastboot flash keymaster_a rom/keymaster.img
fastboot flash imagefv_a rom/imagefv.img
fastboot flash hyp_a rom/hyp.img
fastboot flash dtbo_a rom/dtbo.img
fastboot flash dsp_a rom/dsp.img
fastboot flash devcfg_a rom/devcfg.img
fastboot flash custom_a rom/custom.img
fastboot flash cmnlib64_a rom/cmnlib64.img
fastboot flash cmnlib_a rom/cmnlib.img
fastboot flash boot_a rom/boot.img
fastboot flash bluetooth_a rom/bluetooth.img
fastboot flash aop_a rom/aop.img
fastboot flash abl_a rom/abl.img
All writing* [OK].
But having root on board this operation passes with the format userdata error.
In the flash writing* [FAILED].
Only by deleting hidden folders and files via the /data/directory... in internal storage, writing* [OK].
Hello,
I've been looking through this forum for quite a while, but I have yet to stumble upon a guide that can fix me up for taking the next step after the bootloader unlocking process. Yet, there's been lots of custom roms made for rmx2001. So here I'm with my unlocked rmx2001 or realme 6, wondering if I am missing out on something crucial for the next step because this is my first time doing something like this on a mediatek based phone. Kindly help me out pweese.. thank you;
Update:
I've dwelled deep into the forest, fought clones of sundar pichai, then finally.. successfully flashed my phone with custom recovery.
From what I've had read around this forum and other places, before flashing any custom recovery, the vbmeta.img must be flashed with a patched one, which as usual, there are rules one must follow to modify this certain android component.
This is the first for me, as per Android 8 (or Android 7 with its super confusing arb system took in place), any changes inside the recovery, system, etc are being handled by this vbmeta module.
It seems that vbmeta.img changes for every android or system update and to patch this vbmeta.img, the android version must be the same as what the patch corresponds to... (correct me if I'm wrong; this is my understanding based solely from what I have read, please take this with a big chunk of salt).
I currently have the b.57 update installed on my device, and I only found b.55 here on the next forum's page... the point is I have to wait for the latest patch of vbmeta b.57. Am I understanding this correctly, or am I just talking in elven language to myself? Anyway thank you for reading.
zero help, good for nothing advices. Search on other forums ,you Will get at least real help
cristianwcw said:
zero help, good for nothing advices. Search on other forums ,you Will get at least real help
Click to expand...
Click to collapse
lmao
ignoll said:
From what I've had read around this forum and other places, before flashing any custom recovery, the vbmeta.img must be flashed with a patched one, which as usual, there are rules one must follow to modify this certain android component.
This is the first for me, as per Android 8 (or Android 7 with its super confusing arb system took in place), any changes inside the recovery, system, etc are being handled by this vbmeta module.
It seems that vbmeta.img changes for every android or system update and to patch this vbmeta.img, the android version must be the same as what the patch corresponds to... (correct me if I'm wrong; this is my understanding based solely from what I have read, please take this with a big chunk of salt).
I currently have the b.57 update installed on my device, and I only found b.55 here on the next forum's page... the point is I have to wait for the latest patch of vbmeta b.57. Am I understanding this correctly, or am I just talking in elven language to myself? Anyway thank you for reading.
Click to expand...
Click to collapse
Hi fellow weeb I'm curious of how did you manage to flash custom recovery?
Lyco. said:
Hi fellow weeb I'm curious of how did you manage to flash custom recovery?
Click to expand...
Click to collapse
g'day to you sire *tip*, sorry for the late response. Before flashing any custom recovery;
make sure your phone is unlocked,
- boot to bootloader,
- flash vbmeta.img (this assuming you will not be using realme UI or stock ROM in that case, because chances are you can't go back once you've flashed this image [although not entirely sure])
code here:
Code:
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
- finally, flash your custom recovery
code here:
Code:
fastboot flash recovery <name of the file>.img
Now, I tried flashing twrp, but for some reason, it didn't work. I personally got recommended to use Pitch Black Recovery Project, basically a fork from twrp. It couldn't read my sdcard, but it has better ui compared to twrp. That said, you still can flash custom rom by adb shell through pbrp.
ignoll said:
g'day to you sire *tip*, sorry for the late response. Before flashing any custom recovery;
make sure your phone is unlocked,
- boot to bootloader,
- flash vbmeta.img (this assuming you will not be using realme UI or stock ROM in that case, because chances are you can't go back once you've flashed this image [although not entirely sure])
code here:
Code:
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
- finally, flash your custom recovery
code here:
Code:
fastboot flash recovery <name of the file>.img
Now, I tried flashing twrp, but for some reason, it didn't work. I personally got recommended to use Pitch Black Recovery Project, basically a fork from twrp. It couldn't read my sdcard, but it has better ui compared to twrp. That said, you still can flash custom rom by adb shell through pbrp.
Click to expand...
Click to collapse
Do you a vbmeta.img for the latest patches b.59 or any guide to extract vbmeta, Just like you said the vbmeta corresponds with the patch.
Lyco. said:
Do you a vbmeta.img for the latest patches b.59 or any guide to extract vbmeta, Just like you said the vbmeta corresponds with the patch.
Click to expand...
Click to collapse
We can just use the vbmeta.img from stock ROM .ozip
Thanks
HemanthJabalpuri said:
We can just use the vbmeta.img from stock ROM .ozip
Thanks
Click to expand...
Click to collapse
I thought it depends on the patch. i just want to be careful i don't want to brick my device again btw the stock ozip is b.23 am i right? Or do you have a stock vbmeta?
Lyco. said:
I thought it depends on the patch. i just want to be careful i don't want to brick my device again btw the stock ozip is b.23 am i right?
ignoll said:
g'day to you sire *tip*, sorry for the late response. Before flashing any custom recovery;
make sure your phone is unlocked,
- boot to bootloader,
- flash vbmeta.img (this assuming you will not be using realme UI or stock ROM in that case, because chances are you can't go back once you've flashed this image [although not entirely sure])
code here:
Code:
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
- finally, flash your custom recovery
code here:
Code:
fastboot flash recovery <name of the file>.img
Now, I tried flashing twrp, but for some reason, it didn't work. I personally got recommended to use Pitch Black Recovery Project, basically a fork from twrp. It couldn't read my sdcard, but it has better ui compared to twrp. That said, you still can flash custom rom by adb shell through pbrp.
Click to expand...
Click to collapse
ignoll said:
g'day to you sire *tip*, sorry for the late response. Before flashing any custom recovery;
make sure your phone is unlocked,
- boot to bootloader,
- flash vbmeta.img (this assuming you will not be using realme UI or stock ROM in that case, because chances are you can't go back once you've flashed this image [although not entirely sure])
code here:
Code:
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
- finally, flash your custom recovery
code here:
Code:
fastboot flash recovery <name of the file>.img
Now, I tried flashing twrp, but for some reason, it didn't work. I personally got recommended to use Pitch Black Recovery Project, basically a fork from twrp. It couldn't read my sdcard, but it has better ui compared to twrp. That said, you still can flash custom rom by adb shell through pbrp.
Click to expand...
Click to collapse
Click to expand...
Click to collapse
Is this the stock vbmeta? Or do anyone have any?
Lyco. said:
I thought it depends on the patch. i just want to be careful i don't want to brick my device again btw the stock ozip is b.23 am i right? Or do you have a stock vbmeta?
Click to expand...
Click to collapse
No, we don't need to modify anything to it.
--disable-verity and --disable-verification options to fastboot will patch it and flash automatically for you.
Also you can use vbmeta.img from any version of stock .ozip.
I am a Realme C12 user.
Thanks
HemanthJabalpuri said:
No, we don't need to modify anything to it.
--disable-verity and --disable-verification options to fastboot will patch it and flash automatically for you.
Also you can use vbmeta.img from any version of stock .ozip.
I am a Realme C12 user.
Thanks
Click to expand...
Click to collapse
Ok so what would I do if pbrp didn't showed up? And goes to bootloop, Do i just need to flash ofp and use realme flash tool?
I'm a new at flashing firmware so sorry about that
Lyco. said:
Ok so what would I do if pbrp didn't showed up? And goes to bootloop, Do i just need to flash ofp and use realme flash tool?
I'm a new at flashing firmware so sorry about that
Click to expand...
Click to collapse
Then flash stock recovery.
HemanthJabalpuri said:
Then flash stock recovery.
Click to expand...
Click to collapse
So after i flash the stock recovery should I flash the ozip there? And thanks for all the information.
So i rooted my Oneplus Nord 2 and got into a bootloop wiped the device using TWRP booted into rooted OS and wifi and bluetooth are not working. I dont have a backup of EFS partition.
Flash Boot image
Flash vbmeta.img
.\fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
or from twrp.
pankspoo said:
Flash Boot image
Click to expand...
Click to collapse
Didnt work
krugm0f0 said:
Flash vbmeta.img
.\fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
or from twrp.
Click to expand...
Click to collapse
Didnt work
Try flashing stock boot, then vbmeta. Restart phone, let it boot and see if it works.
If yes, reboot to bootloader again, and fastboot flash rooted boot image. My latest image attached. And then vbmeta. Reboot phone.
fellu4485 said:
Didnt work
Click to expand...
Click to collapse
You need to flash stock Boot image not rooted
pankspoo said:
You need to flash stock Boot image not rooted
Click to expand...
Click to collapse
I did
krugm0f0 said:
Try flashing stock boot, then vbmeta. Restart phone, let it boot and see if it works.
If yes, reboot to bootloader again, and fastboot flash rooted boot image. My latest image attached. And then vbmeta. Reboot phone.
Click to expand...
Click to collapse
I can't get WiFi and Bluetooth to work
This error is almost exclusively caused by having the wrong boot.img.
I know you already said you're certain you flashed the correct boot.img, but the fact your phone is showing these symptoms means you likely have the wrong boot.img, as is true in 99.999% of these cases.
The only other possible cause of these symptoms would be because you wiped or corrupted your persist partition.
The persist.img partition contains unique data calibrated to your own device which contains calibration specific to your phone's wifi and bluetooth module/antennas, if you wiped this partition by accident, you will need to find a backup of the persist.img taken from YOUR OWN DEVICE and reflash it, no one else on these forums will be able to provide these for you.
Again, I'll restate that the chances of the persist.img case being the cause here is almost unheard of unless you distinctly remember tampering with the persist image, which you would have had absolute ZERO reason to have done so.
I would highly recommend that you double, triple, and quadruple check you flashed the CORRECT boot.img before resorting to messing with your persist.img, it's likely your download source provided the wrong one, or you mixed up the files in your downloads folder which happens frequently.
Just got the edge+ (2023) from Boost Mobile, but they don't enable the esim usage. Currently running build T1TR33.43-48-21, model #XT2301-1
Does anyone know a way to enable this? Is the Edge+ 2023 rootable yet?
fatmanSings said:
Just got the edge+ (2023) from Boost Mobile, but they don't enable the esim usage. Currently running build T1TR33.43-48-21, model #XT2301-1
Does anyone know a way to enable this? Is the Edge+ 2023 rootable yet?
Click to expand...
Click to collapse
Is the device carrier locked? Haven't heard of anyone else not having esim, my converted Edge 40 Pro has it. If you can unlock the bootloader you can root the device; since you just got it you may have to wait around a week or so in order to actually be able to enable it in developer options but idk what the situation is for the US variant.
gibberishman said:
Is the device carrier locked? Haven't heard of anyone else not having esim, my converted Edge 40 Pro has it. If you can unlock the bootloader you can root the device; since you just got it you may have to wait around a week or so in order to actually be able to enable it in developer options but idk what the situation is for the US variant.
Click to expand...
Click to collapse
Great thanks! I'll wait a week and see. Do you know the firmware version I should be using for the US variant?
fatmanSings said:
Great thanks! I'll wait a week and see. Do you know the firmware version I should be using for the US variant?
Click to expand...
Click to collapse
I don't think the firmware has been uploaded yet. You can use ADB commands to extract the boot.img file and use magisk to patch it then flash patch boot, or wait to see if the full firmware gets uploaded. Unless the Edge+ has a different codename from the other Edge variants ( I don't think that's the case ) I couldn't find the full firmware.
gibberishman said:
I don't think the firmware has been uploaded yet. You can use ADB commands to extract the boot.img file and use magisk to patch it then flash patch boot, or wait to see if the full firmware gets uploaded. Unless the Edge+ has a different codename from the other Edge variants ( I don't think that's the case ) I couldn't find the full firmware.
Click to expand...
Click to collapse
Thanks for your help!
The codename should be rtwo, correct? You think I could flash to the RETAIL version? or should I just wait for the RETUS?
fatmanSings said:
Thanks for your help!
The codename should be rtwo, correct? You think I could flash to the RETAIL version? or should I just wait for the RETUS?
Click to expand...
Click to collapse
The model number in those firmware files don't match the model number for the US variant. I'm assuming the firmware hasn't been dumped yet since the phone has only been out a few weeks in the states.
gibberishman said:
The model number in those firmware files don't match the model number for the US variant. I'm assuming the firmware hasn't been dumped yet since the phone has only been out a few weeks in the states.
Click to expand...
Click to collapse
How long does it usually take for the firmware files to get dumped? A month or so?
fatmanSings said:
How long does it usually take for the firmware files to get dumped? A month or so?
Click to expand...
Click to collapse
Maybe a couple weeks if that. It just depends. Not really sure how they dump the firmware and if they need the physical device or not.
gibberishman said:
Maybe a couple weeks if that. It just depends. Not really sure how they dump the firmware and if they need the physical device or not.
Click to expand...
Click to collapse
I unlocked the bootloader and flashed stock firmware, but the software channel is still 'dish wireless' and esim settings are still hidden. Do you know of any other possible solutions to enable e-sim capabilities?
I tried to change the oem config carrier to retus and that didn't work either
fatmanSings said:
I unlocked the bootloader and flashed stock firmware, but the software channel is still 'dish wireless' and esim settings are still hidden. Do you know of any other possible solutions to enable e-sim capabilities?
I tried to change the oem config carrier to retus and that didn't work either
Click to expand...
Click to collapse
You did "fastboot oem config carrier retus" ?
gibberishman said:
You did "fastboot oem config carrier retus" ?
Click to expand...
Click to collapse
yes, it changed the value, but there are no changes to the software channel. Is there a way to change the ro.carrier value?
Do you think I can flash to the RETEU Edge 40 Pro firmware?
fatmanSings said:
yes, it changed the value, but there are no changes to the software channel. Is there a way to change the ro.carrier value?
Do you think I can flash to the RETEU Edge 40 Pro firmware?
Click to expand...
Click to collapse
You may be able to root the device and change the value. Don't thing there's a file you can flash to override the carrier. I wouldn't recommend flashing the EU firmware. The hardware is slightly different, don't know if it would affect anything.
Any updates? In the same situation. Tried flashing retail US firmware and FASTBOOT oem config carrier but it didn’t seem to work.
DeSlaye said:
Any updates? In the same situation. Tried flashing retail US firmware and FASTBOOT oem config carrier but it didn’t seem to work.
Click to expand...
Click to collapse
I tried flashing with the RSA Motorola tool and the MotoFlashPro, but neither worked with the US firmware. I haven't tried anything else yet, since I'm scared I'm going to mess something up. But if you would like to try, you could try rooting and patching some of the files, or try flashing the RETAIL firmware, although it's designed for xt2301-4 and not xt2301-1.
Flashing the RETAIL firmware may work since others have been able to convert from other regions as well. But as @gibberishman mentioned the hardware is slightly different and there have been reports of nfc not working, etc.
fatmanSings said:
I tried flashing with the RSA Motorola tool and the MotoFlashPro, but neither worked with the US firmware. I haven't tried anything else yet, since I'm scared I'm going to mess something up. But if you would like to try, you could try rooting and patching some of the files, or try flashing the RETAIL firmware, although it's designed for xt2301-4 and not xt2301-1.
Flashing the RETAIL firmware may work since others have been able to convert from other regions as well. But as @gibberishman mentioned the hardware is slightly different and there have been reports of nfc not working, etc.
Click to expand...
Click to collapse
I downloaded the RETAIL firmware and attempted to 'spoof' the Boost software by removing the MD5 checks in the flash script but no luck. Half the items didn't flash due to protected partitions so unless I have an unlocked bootloader, it doesn't flash. What's odd is these are legitimate firmware files straight from Motorola. I'm guessing there is a different signature for these from the standard unlocked variant vs Boost/Dish.
echo off
fastboot getvar max-sparse-size
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash vbmeta vbmeta.img
fastboot flash vbmeta_system vbmeta_system.img
fastboot flash radio radio.img
fastboot flash bluetooth BTFM.bin
fastboot flash dsp dspso.bin
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash init_boot init_boot.img
fastboot flash vendor_boot vendor_boot.img
fastboot flash dtbo dtbo.img
fastboot flash recovery recovery.img
fastboot flash super super.img_sparsechunk.0
fastboot flash super super.img_sparsechunk.1
fastboot flash super super.img_sparsechunk.2
fastboot flash super super.img_sparsechunk.3
fastboot flash super super.img_sparsechunk.4
fastboot flash super super.img_sparsechunk.5
fastboot flash super super.img_sparsechunk.6
fastboot flash super super.img_sparsechunk.7
fastboot flash super super.img_sparsechunk.8
fastboot flash super super.img_sparsechunk.9
fastboot flash super super.img_sparsechunk.10
fastboot flash super super.img_sparsechunk.11
fastboot erase apdp
fastboot erase apdpb
fastboot erase carrier
fastboot erase ddr
fastboot oem fb_mode_clear
pause
fastboot reboot
exit
EDIT: Flashing the RETAIL on locked BL caused my device to soft-brick, I had to restore via Motorola Rescue and Smart assistance software which worked like a charm. If open BL, you may be able to change the software/carrier channel then attempt to restore through Motorola tool although YMMV.
Ascertion said:
I downloaded the RETAIL firmware and attempted to 'spoof' the Boost software by removing the MD5 checks in the flash script but no luck. Half the items didn't flash due to protected partitions so unless I have an unlocked bootloader, it doesn't flash. What's odd is these are legitimate firmware files straight from Motorola. I'm guessing there is a different signature for these from the standard unlocked variant vs Boost/Dish.
echo off
fastboot getvar max-sparse-size
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash vbmeta vbmeta.img
fastboot flash vbmeta_system vbmeta_system.img
fastboot flash radio radio.img
fastboot flash bluetooth BTFM.bin
fastboot flash dsp dspso.bin
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash init_boot init_boot.img
fastboot flash vendor_boot vendor_boot.img
fastboot flash dtbo dtbo.img
fastboot flash recovery recovery.img
fastboot flash super super.img_sparsechunk.0
fastboot flash super super.img_sparsechunk.1
fastboot flash super super.img_sparsechunk.2
fastboot flash super super.img_sparsechunk.3
fastboot flash super super.img_sparsechunk.4
fastboot flash super super.img_sparsechunk.5
fastboot flash super super.img_sparsechunk.6
fastboot flash super super.img_sparsechunk.7
fastboot flash super super.img_sparsechunk.8
fastboot flash super super.img_sparsechunk.9
fastboot flash super super.img_sparsechunk.10
fastboot flash super super.img_sparsechunk.11
fastboot erase apdp
fastboot erase apdpb
fastboot erase carrier
fastboot erase ddr
fastboot oem fb_mode_clear
pause
fastboot reboot
exit
EDIT: Flashing the RETAIL on locked BL caused my device to soft-brick, I had to restore via Motorola Rescue and Smart assistance software which worked like a charm. If open BL, you may be able to change the software/carrier channel then attempt to restore through Motorola tool although YMMV.
Click to expand...
Click to collapse
Were you able to unlock the bootloader? Usually you have to unlock the bootloader before flashing.
fatmanSings said:
Were you able to unlock the bootloader? Usually you have to unlock the bootloader before flashing.
Click to expand...
Click to collapse
No, when I go to the unlock site it just gives me a 404 error page after submitting my unlock token. I gave up and decided to just use the Boost firmware. The device is sim-unlocked and supports AT&T/T-Mobile.