Related
I bought the original Pixel from Verizon and that was a complete waste. Then the Pixel2 was released, and I bought it online (directly from Google). I've had it for a long while.
The first thing I did was oem unlock and flash twrp, Magisk, and Elemental X. I was running the stock rom and just let all of the updates slip past (updating the kernel of course) and had a few issues so I thought I'd factory reset and update the phone.
But I didn't take the sim card out...
When the phone rebooted it behaved *exactly* like the original Pixel if you had the sim card in. It specifically sets up according to what Verizon wants on the phone.
Now, when I go into the developer settings, the oem unlock is greyed out!!!
Does Verizon lock Pixel phones regardless of its origin?
I'm not completely stupid, this just doesn't make sense... Anyone else have this issue?
Honestly, I didn't think something like that was possible. Can anyone here confirm the hardware is the exact same? Is it possible Verizon signing keys can overwrite default/official Google keys?
Or will the phone behave as normal if I reset without the sim in?
Gonna try it and report back after work (gotta wait another 8 hours or so as of writing this).
Exactly how did you update it, and I mean every step you took?
The steps, specifically as possible:
downloaded the original image from Google (https://developers.google.com/android/images)
I grabbed [8.1.0 (OPM1.171019.013, Jan 2018] as that was the version I was running
Extracted zip, extracted the zip inside the zip (to get boot.img)
flashed stock recovery to boot_a and boot_b (using instructions found at https://www.androidexplained.com/pixel-2-restore-stock-recovery/
Reboot
Checked phone to see if it worked fine
Rebooted to [stock] recovery to see if it would load
This is where things get a little sketchy, as I could only confirm the stock recovery was in place. I only saw dead Andy with "No Command"
Reboot to system- everything looks okay so far...
Let phone automagically download and install any/all updates through the System Settings.
Make sure I want to- and then actually, factory reset phone (I did *not* remove the sim card)
Went through the initial setup
wait for it...
At this point, all Verizon default apps were installed on phone during the initial setup (not at user request/Google Play Store):
MyVerizon, Messages+, etc.
Raised an eyebrow, went to settings, enabled Developer Options, checked OEM unlock...
As of this point I have not been able to check if I can [fastboot oem unlock]
Another thing is that the flash-all.sh script refused to work properly, even with a root shell. I made sure to double check usb debug was enabled, udev rules in place, and checked, double checked cables and ports.
I can, however, confirm that I am on OPM2.171026.006.C1
I haven't memorized the list at the Google Images (*.img type) link above, but I'm pretty sure this one is listed as the generic Pixel 2 and not the Verizon variant. I will still attempt to unlock using the fastboot method... let's hope it still works...
Anywho, I work nights so, I won't be able to test anything out until after work, waffle house, and a nap. But I will indeed be back to keep this updated.
allcaps33 said:
The steps, specifically as possible:
downloaded the original image from Google (https://developers.google.com/android/images)
I grabbed [8.1.0 (OPM1.171019.013, Jan 2018] as that was the version I was running
Extracted zip, extracted the zip inside the zip (to get boot.img)
flashed stock recovery to boot_a and boot_b (using instructions found at https://www.androidexplained.com/pixel-2-restore-stock-recovery/
Reboot
Checked phone to see if it worked fine
Rebooted to [stock] recovery to see if it would load
This is where things get a little sketchy, as I could only confirm the stock recovery was in place. I only saw dead Andy with "No Command"
Reboot to system- everything looks okay so far...
Let phone automagically download and install any/all updates through the System Settings.
Make sure I want to- and then actually, factory reset phone (I did *not* remove the sim card)
Went through the initial setup
wait for it...
At this point, all Verizon default apps were installed on phone during the initial setup (not at user request/Google Play Store):
MyVerizon, Messages+, etc.
Raised an eyebrow, went to settings, enabled Developer Options, checked OEM unlock...
As of this point I have not been able to check if I can [fastboot oem unlock]
Another thing is that the flash-all.sh script refused to work properly, even with a root shell. I made sure to double check usb debug was enabled, udev rules in place, and checked, double checked cables and ports.
I can, however, confirm that I am on OPM2.171026.006.C1
I haven't memorized the list at the Google Images (*.img type) link above, but I'm pretty sure this one is listed as the generic Pixel 2 and not the Verizon variant. I will still attempt to unlock using the fastboot method... let's hope it still works...
Anywho, I work nights so, I won't be able to test anything out until after work, waffle house, and a nap. But I will indeed be back to keep this updated.
Click to expand...
Click to collapse
USB debugging is only for ADB, and has nothing to do with fastboot commands. When you attempted to run the flash-all script, were you in ADB or bootloader? In ADB it will fail, because it doesn't recognize fastboot commands. However, in the bootloader, if it's not recognizing fastboot commands, that's a whole different animal. OTAs, when it comes to VZW are dangerous, so it's always best to just sideload them via stock recovery. They should come straight from Google, but I'm afraid that something that you did in the entire process broke that.
In all honesty, all you really needed to do was unzip the latest factory image, run the flash-all script while you were still unlocked, and be done with it. The -w in the script would have taken care of the factory reset for you, as it's a full wipe.
Let us know if what you tried worked, and best of luck ?
I was in the bootloader, I realize adb and fastboot are 2 different entities.... thus far, I'm still locked out... working it now...
An update to this mess:
Still working with known exploits to try and get back to where I was. Looks like I'm gonna have to pull from CVE or ExDB.
Any suggestions from the pros?
allcaps33 said:
I was in the bootloader, I realize adb and fastboot are 2 different entities.... thus far, I'm still locked out... working it now...
Click to expand...
Click to collapse
I do apologize for underestimating your knowledge. That being said, an OTA can't re-lock the bootloader without permission, as that would completely wipe userdata. And, neither can the presence of a SIM card. I fear that, with everything that you did, as far as getting your phone as clean as possible, you may have put the device in limbo, so to speak, and the OTAs, combined with vzw's penchant for locking bootloaders, may have made it susceptible to becoming a Verizon device. Just a thought.
I totally agree with you.
I'm just completely confused how this happened...
As you said, with an unlocked bootloader, it *might* have been possible that through some kind of bug it may have taken something VZW specific... But... The OTA packages don't actually contain the entire ROM do they?
From what I noticed, they're almost all under 80 MB, while the actual ROM packages are (on average) 1.5 GB.
At what point could this crossover happen?
(The reason I bring up package sizes is that would be the most likely reason for an overwrite... I think...)
Can I probe you for more theories? Out of the box solutions never work, perhaps you might trigger ideas within the community.
Thank you very much @DuckRuckus for your help!
Still to this point attempting anything within fastboot seems to just not work...
I can get "fastboot devices" and "fastboot reboot bootloader" to work. But that's about it. No other commands issued get so as a response.
I've made a .bat file for flashing and some other stuff. Basic stuff that I use the most.
I made it for One Vision but since Action use exactly the same flash commands, it works for Action as well.
{
"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"
}
Unzip .bat to same dir as your fastboot.exe and double click it or drag it to your cmd window and press enter.
Options:
[f] - FLASH FULL FIRMWARE.
[w] - FACTORY RESET. (erase userdata)
[g] - DEVICE INFO. (getvar all)
[p] - OEM PARTITION INFO. (oem partition)
- GET BOOTLOADER UNLOCK CODE FROM DEVICE. (oem get_unlock_data)
[r] - REBOOT TO SYSTEM, EXIT.
- REBOOT TO BOOTLOADER.
[e] - EXIT, leave the phone in fastboot mode.
Nice work! Really useful for flashing Android 9. However, couple of changes might be necessary for Android 10, in case anyone wants to use it for that. Minor changes.
Such as:
renaming bootloader.bin to bootloader.img
renaming fwbl1.nbl1.bin to fwbl1.img
renaming keystorage.bin to keystorage.img
renaming ldfw.bin to ldfw.img
Other than that, very good idea, and very useful tool!
Thank you!
Updated Fastboot command batch file for Android 10
This is the updated fastboot command batch file for Android 10. Just move to the platform-tools folder and execute it (obviously the stock firmware should be there as well )
Haven't added the fastboot reboot command at the end. You will have to execute that command manually after the flashing is done (in case the device doesn't automatically boots up).
PS: Can't upload the .bat file directly so had to compress it.
Attached the updated version for Android 10, including the rest of the tool, for anyone interested.
arsradu said:
Attached the updated version for Android 10, including the rest of the tool, for anyone interested.
Click to expand...
Click to collapse
Thanks for your contribution. I actually updated the .bat it a few weeks ago to include both pie and A10 flash commands, since not everyone is updated yet.
Then I realized it would be stupid to share it cause someone would probably try to downgrade, which may result in i brick, and then blame me for it although it's common knowledge not to downgrade android version on new devices.
I'll probably have to add a warning about it in the .bat at least.
tys0n said:
Thanks for your contribution. I actually updated the .bat it a few weeks ago to include both pie and A10 flash commands, since not everyone is updated yet.
Then I realized it would be stupid to share it cause someone would probably try to downgrade, which may result in i brick, and then blame me for it although it's common knowledge not to downgrade android version on new devices.
I'll probably have to add a warning about it in the .bat at least.
Click to expand...
Click to collapse
Heey! Welcome back!
It is common knowledge indeed. And I always wondered why is that. Why does it result in a brick? I'm guessing there are some conflicts or something, right? If you have more info (which it sounds like you do) could you share it? I would love to know more about it.
I mean, you could do that pretty easily with older (Android 6 for example) devices. I mean, it's not advisable. But...if the update sucks or it brings some really nasty bugs and you cannot use your phone cause the modem part of it is broken, for example, there should be a way to safely go back to the previous version, right...? At least until the bug is fixed. Shouldn't it be possible to simply flash Android 9 the same way you do Android 10 (I'm guessing the answer is no, but just wondering why...)? You can even do that on iOS, for God's sake! Which is like the definition of no downgrades! But Apple still allows it. Not permanently, but for a while, yeah, if you have an issue with the new version, you can go back to the old one.
But, yeah, you're definitely not the first one advising against going back to, in this case, Android 9.
By the way, nice job with this script. I was working on a version for Mac, since I'm a Mac guy. And...I got pretty far. But one thing I can't figure out how to do: goto (especially for the "Back to Menu" option which is used pretty often). There is no such thing in Bash. So...you have to improvise. And so far, everything I tried failed, for one reason or the other. So..for now, I just boot into Windows if I need to flash anything. Then return to Mac. )
It's' good to see you around. And once again, thank you!
Update:
So...downgrading to Android 9 is definitely possible. You just need to make sure OEM Unlock is checked in Developer Options (allowing bootloader to be unlocked) and that you actually are bootloader unlocked. Everything else is the same.
Update 2:
There seems to be a typo in your script when flashing vbmeta.
It should be "fastboot flash vbmeta_a vbmeta.img" according to the flashfile.xml for Android 9.
arsradu said:
Heey! Welcome back!
It is common knowledge indeed. And I always wondered why is that. Why does it result in a brick? I'm guessing there are some conflicts or something, right? If you have more info (which it sounds like you do) could you share it? I would love to know more about it.
I mean, you could do that pretty easily with older (Android 6 for example) devices. I mean, it's not advisable. But...if the update sucks or it brings some really nasty bugs and you cannot use your phone cause the modem part of it is broken, for example, there should be a way to safely go back to the previous version, right...? At least until the bug is fixed. Shouldn't it be possible to simply flash Android 9 the same way you do Android 10 (I'm guessing the answer is no, but just wondering why...)? You can even do that on iOS, for God's sake! Which is like the definition of no downgrades! But Apple still allows it. Not permanently, but for a while, yeah, if you have an issue with the new version, you can go back to the old one.
But, yeah, you're definitely not the first one advising against going back to, in this case, Android 9.
By the way, nice job with this script. I was working on a version for Mac, since I'm a Mac guy. And...I got pretty far. But one thing I can't figure out how to do: goto (especially for the "Back to Menu" option which is used pretty often). There is no such thing in Bash. So...you have to improvise. And so far, everything I tried failed, for one reason or the other. So..for now, I just boot into Windows if I need to flash anything. Then return to Mac. )
It's' good to see you around. And once again, thank you!
Update:
So...downgrading to Android 9 is definitely possible. You just need to make sure OEM Unlock is checked in Developer Options (allowing bootloader to be unlocked) and that you actually are bootloader unlocked. Everything else is the same.
Update 2:
There seems to be a typo in your script when flashing vbmeta.
It should be "fastboot flash vbmeta_a vbmeta.img" according to the flashfile.xml for Android 9.
Click to expand...
Click to collapse
Sorry, I don't know what it is that can cause bricks when downloading android version, but you're right, everything was easier with older android versions
Did you try to downgrade from 10 to 9, and it worked? It would be great if that was the case.
Thank you..again! Didn't notice that typo and I've had no problems or errors while testing/flashing with it.
I guess that's why I missed it. You don't look for errors if it's working
I'm attaching an updated tool with pie and android 10 flashing, and typo corrected. Also added you to "credits".
For now I've added a warning about downgrade since I don't have any confirmation on if it's possible or not.
tys0n said:
Sorry, I don't know what it is that can cause bricks when downloading android version, but you're right, everything was easier with older android versions
Did you try to downgrade from 10 to 9, and it worked? It would be great if that was the case.
Thank you..again! Didn't notice that typo and I've had no problems or errors while testing/flashing with it.
I guess that's why I missed it. You don't look for errors if it's working
I'm attaching an updated tool with pie and android 10 flashing, and typo corrected. Also added you to "credits".
For now I've added a warning about downgrade since I don't have any confirmation on if it's possible or not.
Click to expand...
Click to collapse
It is possible. I'm back on Android 9 right now.
BUT, a few notes:
1. the problem causing boot failure (and flash failure, with error "(bootloader) validation image failed") is not so much the ROM itself, as it is the Security Patch. It seems that it HAS TO be at least the same version. Which makes me think that it should be possible (at least in theory) to downgrade to Android 9, even without unlocking the bootloader, IF the Security Patch you're coming from is the same as the one of the ROM you're trying to flash. In other words, if your Security Patch is not being downgraded. It has to be at least the same version, or newer, in order to work without any issues.
2. IF you already upgraded to something, anything, with a newer Security Patch, downgrading is no longer possible with a locked bootloader. It IS, however, possible after unlocking the bootloader (which will void the warranty).
3. once in this state (unlocked and downgraded to Android 9), you cannot relock the bootloader anymore (again, IF you're coming from a newer Security Patch). No errors when locking, but upon boot, you'll get the "your device has failed verification and may not work properly" warning, and, despite the message underneath that says "your device will boot in 5 seconds", it won't boot.
I'm guessing...it should be possible to relock the bootloader IF:
1. you're upgrading again to the ROM with the Security Patch you had before (January 2020 for example), but then you won't be able to downgrade again (unless you unlock the bootloader).
2. you're waiting for a security patch for the current Android version to match the one you had before (again, January 2020 for example).
So, in other words, you can either flash a January 2020 Security Patch included with a ROM, or wait to receive it via OTA.
Also, thank you very much for the update. Indeed, it doesn't show any errors. When upgrading to Android 10, I already corrected that line. But I forgot to do the same in the original script. No errors indeed (not sure if it makes any difference....) but it's probably better to be corrected nonetheless.
Soo...thank you!
Hey, first off thanks to both of you arsradu and tys0n for sharing some wonderful insights. What I failed to understand is the fact that how the initial tool was still able to flash the vbmeta file if you failed to mention which slot should it be flashed to? Is explicitly mentioning slot isn't compulsory for all the files?
Another thing which seems to intrigue me is the fact that how come we have fixed the slots in these fastboot commands. Because in dual slots, the active/inactive slots keep on changing every time we flash an OTA and REBOOT the device. So in those cases, why don't we have to modify these fastboot commands according to the changing slots?
For example, if we use fastboot flash vbmeta_a vbmeta.img, then we always use this command only and not vbmeta_b vbmeta.img. It seems we are explicitly assuming that every device should be having 'A' partition as the inactive slot (before REBOOT), but that can't be universally applicable, right? But we all know it works like a charm! So what is it that is actually happening ??
Any update on this by you guys will be highly appreciated
binary**# said:
Hey, first off thanks to both of you arsradu and tys0n for sharing some wonderful insights. What I failed to understand is the fact that how the initial tool was still able to flash the vbmeta file if you failed to mention which slot should it be flashed to? Is explicitly mentioning slot isn't compulsory for all the files?
Another thing which seems to intrigue me is the fact that how come we have fixed the slots in these fastboot commands. Because in dual slots, the active/inactive slots keep on changing every time we flash an OTA and REBOOT the device. So in those cases, why don't we have to modify these fastboot commands according to the changing slots?
For example, if we use fastboot flash vbmeta_a vbmeta.img, then we always use this command only and not vbmeta_b vbmeta.img. It seems we are explicitly assuming that every device should be having 'A' partition as the inactive slot (before REBOOT), but that can't be universally applicable, right? But we all know it works like a charm! So what is it that is actually happening ??
Any update on this by you guys will be highly appreciated
Click to expand...
Click to collapse
Your guess is a s good as mine. ) Maybe tys0n has some better knowledge about it. I was also wondering why only vbmeta_a.... And how does it work though, without specifying which slot to write to? There is no vbmeta_b in the xml. Why? I have no idea.
I mean, it's clear that, for other components, you need to specify it. At least, the flashfile.xml is specifying it. So you would assume it is important. Aaand I don't think anyone is assuming this is a universal tool for every device. Though it can definitely be adapted for other phones.... ) So I'm not assuming every phone is gonna write to the same partition. But these two (the Vision and the Action) seem to have this thing in common.
I'm not sure what you mean by switching slots. I honestly don't have enough experience with that. Also, I don't think the tool is for flashing the OTA updates... I think it's only for flashing the full images. Again, I could be wrong here. This is a new phone for me, and I haven't checked any OTAs for it yet. If you have one, we can analyse that. But...again, I'm not sure if this tool was meant for flashing OTAs.
arsradu said:
Your guess is a s good as mine. ) Maybe tys0n has some better knowledge about it. I was also wondering why only vbmeta_a.... And how does it work though, without specifying which slot to write to? There is no vbmeta_b in the xml. Why? I have no idea.
I mean, it's clear that, for other components, you need to specify it. At least, the flashfile.xml is specifying it. So you would assume it is important. Aaand I don't think anyone is assuming this is a universal tool for every device. Though it can definitely be adapted for other phones.... ) So I'm not assuming every phone is gonna write to the same partition. But these two (the Vision and the Action) seem to have this thing in common.
I'm not sure what you mean by switching slots. I honestly don't have enough experience with that. Also, I don't think the tool is for flashing the OTA updates... I think it's only for flashing the full images. Again, I could be wrong here. This is a new phone for me, and I haven't checked any OTAs for it yet. If you have one, we can analyse that. But...again, I'm not sure if this tool was meant for flashing OTAs.
Click to expand...
Click to collapse
First off I should have been more specific regarding the term "every device", what I actually meant was "every Moto one action device".... An error on my part [emoji2960]....
Regarding the OTA I didn't meant to say that this tool could be/couldn't be used to flash OTAs[emoji85]
Coming back to the point, while executing the fastboot command to flash vbmeta, we always keep the slot A attached to it, rather than checking for the inactive slot beforehand and then flashing. I guess the reason could be the fact that since we are using these fastboot commands to install the stock firmware from scratch...so whatever slot we install the system to, vbmeta needs to be flashed to that slot...
As we are installing system to slot A (fastboot flash system_a system.img), so it's 'vbmeta_a' vbmeta.img.
Now I'll try flashing all these sparsechunk files to slot b and then check whether vbmeta gets flashed to that slot without actually mentioning that slot (B) in its fastboot command [emoji14]
And yes, thanks for your prompt response
Sent from my motorola one action using Tapatalk
binary**# said:
First off I should have been more specific regarding the term "every device", what I actually meant was "every Moto one action device".... An error on my part [emoji2960]....
Regarding the OTA I didn't meant to say that this tool could be/couldn't be used to flash OTAs[emoji85]
Coming back to the point, while executing the fastboot command to flash vbmeta, we always keep the slot A attached to it, rather than checking for the inactive slot beforehand and then flashing. I guess the reason could be the fact that since we are using these fastboot commands to install the stock firmware from scratch...so whatever slot we install the system to, vbmeta needs to be flashed to that slot...
As we are installing system to slot A (fastboot flash system_a system.img), so it's 'vbmeta_a' vbmeta.img.
Now I'll try flashing all these sparsechunk files to slot b and then check whether vbmeta gets flashed to that slot without actually mentioning that slot (B) in its fastboot command [emoji14]
And yes, thanks for your prompt response
Sent from my motorola one action using Tapatalk
Click to expand...
Click to collapse
You know why I love this community? Cause we can share interesting ideas and experiences like this. We can learn from each other. And at least for what I'm concerned, I do have a LOT to learn. And I'm glad I have nice people I can learn from.
As for your experiment, I'm also curious to know the outcome. I never wondered what would happen in that particular case. But then again, I'm very much a noob when it comes to this phone. It's a new phone, never done this on another Moto phone, and I know each manufacturer (and sometimes each phone) has its own particularities. So I'm happy to learn from you guys.
arsradu said:
You know why I love this community? Cause we can share interesting ideas and experiences like this. We can learn from each other. And at least for what I'm concerned, I do have a LOT to learn. And I'm glad I have nice people I can learn from.
As for your experiment, I'm also curious to know the outcome. I never wondered what would happen in that particular case. But then again, I'm very much a noob when it comes to this phone. It's a new phone, never done this on another Moto phone, and I know each manufacturer (and sometimes each phone) has its own particularities. So I'm happy to learn from you guys.
Click to expand...
Click to collapse
Exactly! There are tons of new things to learn from everyone out there. And this being my first Exynos device, I'm just loving the challenges here. Till now I only had Snapdragon devices in which everything was a cakewalk. Furthermore, my recent devices were all Redmi/Xiaomi and it had a pretty neat escape even from hard-brick situations via EDL Mode. But with One Action, everything is so different, thanks to its processor
binary**# said:
Exactly! There are tons of new things to learn from everyone out there. And this being my first Exynos device, I'm just loving the challenges here. Till now I only had Snapdragon devices in which everything was a cakewalk. Furthermore, my recent devices were all Redmi/Xiaomi and it had a pretty neat escape even from hard-brick situations via EDL Mode. But with One Action, everything is so different, thanks to its processor
Click to expand...
Click to collapse
Yeah, I was actually surprised (pleasantly surprised, I might say) it had a Samsung SOC. My previous Moto had a Mediatek and I did not enjoy that one bit. New versions are better though. But that one...not really. And before that I had a SONY Z3 Compact. Cool phone, plenty powerful for its time, but apparently SONY had some troubles with their glue...cause the display kept getting unstuck. )) Looks like this was its "thing".
Anyway, back to Moto Action, I'm liking it so far. The only thing I don't particularly like about it is the update. Kinda slow for an Android One device. But hey, it could be worse. ) I'm not expecting too much from a mid-range device. It's perfect for the price. And for my use case, it gets the job done.
arsradu said:
Yeah, I was actually surprised (pleasantly surprised, I might say) it had a Samsung SOC. My previous Moto had a Mediatek and I did not enjoy that one bit. New versions are better though. But that one...not really. And before that I had a SONY Z3 Compact. Cool phone, plenty powerful for its time, but apparently SONY had some troubles with their glue...cause the display kept getting unstuck. )) Looks like this was its "thing".
Anyway, back to Moto Action, I'm liking it so far. The only thing I don't particularly like about it is the update. Kinda slow for an Android One device. But hey, it could be worse. ) I'm not expecting too much from a mid-range device. It's perfect for the price. And for my use case, it gets the job done.
Click to expand...
Click to collapse
You pretty much summed it up: "kinda slow, but could have been worse". I was confused between Mi A3 and One Action, but I ultimately decided to go with the latter (because of 720p display of Mi A3, there was really no point in going after that). And now I'm quite satisfied with my choice, even more so considering Mi A3 is yet to receive the Android 10 update.
binary**# said:
You pretty much summed it up: "kinda slow, but could have been worse". I was confused between Mi A3 and One Action, but I ultimately decided to go with the latter (because of 720p display of Mi A3, there was really no point in going after that). And now I'm quite satisfied with my choice, even more so considering Mi A3 is yet to receive the Android 10 update.
Click to expand...
Click to collapse
Lucky dawg, you already got it. You got it first, didn’t you? ))
Well, you know, I’m happy for you, man. This way you have more time to experiment with it so you can help others when they get theirs. So, if you think about it, it’s really a win-win. ))
i ****ed up
guys i ****ed up and bricked my moto one action xt2013-4 and now it wont boot and i cant flash stock firmware back to it
achmed420 said:
guys i ****ed up and bricked my moto one action xt2013-4 and now it wont boot and i cant flash stock firmware back to it
Click to expand...
Click to collapse
What did you do? What error do you get on boot? What error do you get when flashing?
i ****ed up
i unlocked boot loader and attempted to flash TROIKA_QSB30.62-17_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml some items failed other flashed some had verification image errors and now it won let me boot anything except recovery and fastboot ... i was on psbs29. 105-27-2 before this with january 2020 security patch
achmed420 said:
i unlocked boot loader and attempted to flash TROIKA_QSB30.62-17_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml some items failed other flashed some had verification image errors and now it won let me boot anything except recovery and fastboot ... i was on psbs29. 105-27-2 before this with january 2020 security patch
Click to expand...
Click to collapse
Where did you get the ROM from? Can you post a link? I'm trying to understand which exact variant (for which region) did you flash.
You still didn't tell me which error do you get upon boot.
Also, did you use the correct commands for Android 10? Which script did you use?
By the looks of it, you tried to flash a ROM with December security patch over one with January security patch. Which, with a locked bootloader is not gonna be possible, but...should be possible with an unlocked bootloader. But since you didn't tell me which error do you get upon boot, I'm not sure how to help you.
So... I unlocked the bootloader, but I haven't found a way to get root yet. There's no TWRP available, and I can't find a useable boot image. I tried to copy boot_a and boot_b using dd in an ADB shell, but all I got was "permission denied". There don't seem to be any stock images available, so I'm not sure where to get a boot image until there's an OTA update, but even then I might not be able to pull it from the data partition without root. Argh.
Also, Motorola has kernel source at https://github.com/MotorolaMobilityLLC/kernel-msm, but the last commit was over 2 months ago, and I can't find a default config for racer.
https://mirrors.lolinet.com/firmware/moto/racer/official/
Firmware for device
Thanks for that. I also found Lenovo's support app at https://support.lenovo.com/us/en/downloads/ds101291 (Lenovo owns Motorola.) Too tired to mess with this now. I'll try it later.
You can retrieve full ROM and boot.img from LMSA using rescue mode.
You can run rescue to update the ROM, observe the download process, copy the .zip once it reached 100% as well as retrieve boot
Copy boot.img to phone and patch with Magisk Manager, and copy back to host computer
Flash the patched boot
Make sure ADB is up to date
adb reboot fastboot
fastboot flash boot patched_boot.img
Yup, it's working now. Thanks all.
I have successfully rooted mine and having adaway installed
Can you install stock android 10 or even android 11 now?
ROM updated
Since Motorola/Lenovo updated the Edge since this was first posted, I would like to add that coming across the boot image file is a bit more scarce than the original release version for the Edge. However, using Rescue and Smart Assistant, you can downoad the latest ROM version. You may now use the boot image file in the downloaded folder [ProgramData\Lenovo\Downloads\Roms] and use that for Magisk patching to attain root. However, since I am not sure how that EXACTLY works, I am worried about the resulting file size. Original file size is 101MB. Patched file size is 36MB. I am afraid to flash due to this. Another however, I use fastboot to boot the patched file directly and it DOES work, just unsure if there would be any problems with it if I FLASH it, instead. I believe I read in a related thread to Magisk and rooting, that it reduces the file size to remove unnecessary space now that it is patched? Can someone confirm how that works and if it is safe to flash? I really don't want to flash it, then come across a problem and have to flash stock boot image and end up running into some other problems all because I wanted to flash the patched file instead of using fastboot to boot every time I reboot. Thanks for any and all help, guys.
mingkee said:
I have successfully rooted mine and having adaway installed
Click to expand...
Click to collapse
How did you get root?
zrex said:
How did you get root?
Click to expand...
Click to collapse
Magisk patched boot flashing method
TOOLBOYNIN39 said:
Since Motorola/Lenovo updated the Edge since this was first posted, I would like to add that coming across the boot image file is a bit more scarce than the original release version for the Edge. However, using Rescue and Smart Assistant, you can downoad the latest ROM version. You may now use the boot image file in the downloaded folder [ProgramData\Lenovo\Downloads\Roms] and use that for Magisk patching to attain root. However, since I am not sure how that EXACTLY works, I am worried about the resulting file size. Original file size is 101MB. Patched file size is 36MB. I am afraid to flash due to this. Another however, I use fastboot to boot the patched file directly and it DOES work, just unsure if there would be any problems with it if I FLASH it, instead. I believe I read in a related thread to Magisk and rooting, that it reduces the file size to remove unnecessary space now that it is patched? Can someone confirm how that works and if it is safe to flash? I really don't want to flash it, then come across a problem and have to flash stock boot image and end up running into some other problems all because I wanted to flash the patched file instead of using fastboot to boot every time I reboot. Thanks for any and all help, guys.
Click to expand...
Click to collapse
Yes, my patched boot image is smaller too, but it works. I'm guessing the patched image is either sparse or truncated.
Mogster2K said:
Yes, my patched boot image is smaller too, but it works. I'm guessing the patched image is either sparse or truncated.
Click to expand...
Click to collapse
That makes all the sense in the world to me. I flashed it and have been running it for a few days now without issue. Have my usual setup with Magisk, Riru-core, Riru EdXposed, and then GravityBox in EdXposed for the free customization. Only thing I couldn't get was Xblast module. Not compatible at all with Android Q. Only thing I need now is make the nav bar black all the time. Can't do it with GB since it doesn't have an option for that. Xblast had one but... oh well. Phone works nice aside from the occasional app that isn't compatible with edge enable/disable.
minidude2012 said:
https://mirrors.lolinet.com/firmware/moto/racer/official/
Firmware for device
Click to expand...
Click to collapse
WOW! You're a life savor, thank you!
I unlocked my bootloader through moto and downloaded the rom through lmsa and patched the boot img with magisk, then tried to flash it using adb but it put my phone into a boot loop.. can anyone help me out? this phone seems like a pain the ass to root* compared to the last one ive done (about 2 years ago)
edit: i think i found out what i did wrong, not renaming the patch file back to how it should be. and i patch the boot.img correct? or patch the recovery.img? getting conflicting guides
Make sure you flash boot.img in fastbootd
I'm curious of people's opinions of rooting this phone?
I just got mine yesterday, and I don't think I've ever not used rooted android all the way back to my first Android Eclair device over a decade ago now.
But here I find myself worried I'll have some of the display issues so I'm hesitant to root my device or request an unlock code while I'm in the 2 week return window because of the wording of the agreement once the code is used. It very explicitly absolves Moto of every possible responsibility for hardware faults under a blanket accusation that by unlocking the phone I must have broken it. And while I have no doubt the wording would crumple in court or whatever, I don't really want to go to court over a cell phone.
I rooted both my "send-ins". I am on my third and just going to accept the light green haze at low light. I rooted my first two and sent them in within a total of a month. First phone was on day 17. 2nd was about 6 or 7 days. That one was a turn around since it displayed the haze during setup. This third one shows it as well but I don't feel like doing the return and setup all over again. You shouldn't have to worry about the agreement since Lenovo/Motorola is not looking into that as this is a known hardware/software issue from factory.
Does this forum include the edge 5G? I have the US model(6/ram, 256GB). Does twrp still have that builder? There used to be something, to that, don't know if that's continued.
reggjoo said:
Does this forum include the edge 5G? I have the US model(6/ram, 256GB). Does twrp still have that builder? There used to be something, to that, don't know if that's continued.
Click to expand...
Click to collapse
Sorry to be a little late, but I am unsure of your question. This forum IS "Motorola Edge 5G". There is a separate forum under the name of "Motorola Edge+ 5G" for the more expensive version. If you are looking for TWRP for this phone, there never was a release. At least none that I had ever seen around here. I was always on the lookout for one and never came across one. The "plus" version of the phone does have a TWRP, however. Maybe that is the phone you have or at least the one you are confusing the TWRP with?
stock rooted pixel4a (from google directly) running root.boot.sunfish-qd4a.200805.003.img iirc.
just hit the upgrade magisk button as i always do (yes, i unhid the app back to normal) but it failed. directly following this, it rebooted and i am now stuck inside fastboot mode without access to ADB. fastboot commands work but ADB do not. is there a way to upload a boot image to get me back to where i was? OR at the least, backup my phone before a full wipe. thanks in advance!
xxTECRAxx said:
stock rooted pixel4a (from google directly) running root.boot.sunfish-qd4a.200805.003.img iirc.
just hit the upgrade magisk button as i always do (yes, i unhid the app back to normal) but it failed. directly following this, it rebooted and i am now stuck inside fastboot mode without access to ADB. fastboot commands work but ADB do not. is there a way to upload a boot image to get me back to where i was? OR at the least, backup my phone before a full wipe. thanks in advance!
Click to expand...
Click to collapse
adb commands don't run on fastboot.
You must flash stock boot.img or magisk patched boot.img using fastboot flash boot "the_boot.img_file_you_want_to_flash"
should i flash this image "root.boot.sunfish-qd4a.200805.003.img"? or do you know where i get a patched magisk boot image? i've looked through magisk github as well as here but i may not be looking for the right stuff. i get the idea of what needs to be done. how i do it exactly is a little stretch, outside the obvious command "fastboot flash boot.img"
little more push in the right direction, please?
EDIT:
reviewing this https://forum.xda-developers.com/t/guide-unlock-root-safetynet-for-pixel-4a.4153773/
and this https://forum.xda-developers.com/t/help-access-internal-storage-from-fastboot.4221223/#post-84332187
the fastboot mode screen displays the following for the bootloader version: s5-0.2-6281315 and i do have a bootloader that matches that. going to give that a whirl
making headway but not booting still
xxTECRAxx said:
making headway but not booting still
Click to expand...
Click to collapse
Judging by the screens you've shared, you've just tried to flash bootloader into boot partition. DON'T DO THAT.
If I were you I would just download the complete fastboot ROM and would run flash-all.bat.
In order to retain your data, before running the bat, open it and remove the "-w" you'll see on the update command line.
This will flash the hole ROM and firmware, thus making your device to achieve boot.
Afterwards you may try to root it again.
THANK YOU!
hey @Typhus_ wanted to say thank you again! i was not only able to get back to norm, i was also able to root back to where i was, with the exception of not passing SafetyNet. been reading about it and what all is available to use with HidePropCconfig module. the pixel4a was passing prior to this riggamaroll but not really concerned about that issue at this time.
i just noticed i am not seeing the full 128gb disk. about 6 months ago i had an issue with root and went full retard, re-formatting the phone and throwing commands at it with ADB. i really couldn't tell you exactly what i did as i don't remember but i can confirm i messed with the partitions and this has obviously effected me adversely.
being that you had efficiently helped me with my bootloader and your experience here at XDA, i thought maybe you had some thoughts on the disk not being 128gb and how i might repair that. i have since backed up and in a position to go full retard
please see attached screenshots of disk analyzer, sdmaid, and a windows shared drive mount
xxTECRAxx said:
hey @Typhus_ wanted to say thank you again! i was not only able to get back to norm, i was also able to root back to where i was, with the exception of not passing SafetyNet. been reading about it and what all is available to use with HidePropCconfig module. the pixel4a was passing prior to this riggamaroll but not really concerned about that issue at this time.
i just noticed i am not seeing the full 128gb disk. about 6 months ago i had an issue with root and went full retard, re-formatting the phone and throwing commands at it with ADB. i really couldn't tell you exactly what i did as i don't remember but i can confirm i messed with the partitions and this has obviously effected me adversely.
being that you had efficiently helped me with my bootloader and your experience here at XDA, i thought maybe you had some thoughts on the disk not being 128gb and how i might repair that. i have since backed up and in a position to go full retard
please see attached screenshots of disk analyzer, sdmaid, and a windows shared drive mount
Click to expand...
Click to collapse
That storage space values are just... weird. Can't quite find another word for it.
If I ran into that kind of problem I would completely clean flash the stock ROM again, this time keeping the "-w" flag. You see, that flag completely cleans the user data partition and creates it again as soon as the flashing procedure ends. Most likely, and by doing so, your storage space values will be correct again. Obviously this will wipe everything so, if you decide to do so, please backup manually all your important stuff.
As for SafetyNet fix, you may use kdrag0n module (he made and shared one universal mod that fixes it) or you may flash my addon features module (link on my signature) that, not only, fixes SafetyNet, but also, adds several cool mods.
Cheers!
It seems lots of us have had to use the India 9 Pro MSM to recover our devices and in the process, we lose the ability to go back to OOS12 or ROMs based on that firmware because the touchscreen stops working and also trying to convert T-Mobile variants, the fastboot scripts are just bricking them. Well I found a fix for these issues. Those who just want to convert can skip the MSM Tool process and get right to the conversion process as long as they're already running OOS11.
First thing is first, you need to be on OOS11. If you have a T-Mobile variant and you have flashed it with India firmware, you have to use a modded T-Mobile MSM: https://forum.xda-developers.com/t/...ariant-flashing-as-well.4454357/post-87050821
If you have a T-Mobile variant that hasn't used the Indian 9 Pro MSM Tool, is on OOS12, and you're just wanting to convert, you need this tool: https://forum.xda-developers.com/t/oneplus-9-11-2-22-2-t-mobile-msm-download-tool.4276119/
If you have a global variant or a global variant that has been flashed with Indian firmware, you can use this MSM (choose O2 for global or India for India in the Target dropdown, check Sha256, uncheck use lite firehose, it's a multi-target MSM Tool): https://mega.nz/file/ZWtGxTSb#UZ6aSOR2UTYrCao2fQNJ1IN5LSxPNBOxzel1kihnnJs
If you don't know how to use the MSM Tool, there are other guides around here, that's outside of the scope of this post.
Once you are back on OOS11, unlock the bootloader. We also need USB debugging enabled.
Now we need a tool called Fastboot Enhance. This wonderful tool allows you to directly flash OTAs from fastbootd and it doesn't have the same brick risk that flashing with fastboot scripts does.
Download it and unzip it somewhere.
Next we need the OOS11 global downgrade package (or whatever region you are wanting to switch to, global is recommended for T-Mobile variants) from here: https://forum.xda-developers.com/t/oneplus-9-rom-ota-oxygen-os-repo-of-oxygen-os-builds.4254579/
Fire up command prompt in the folder you have your platform tools and run:
adb reboot fastboot (if you do adb reboot bootloader you will then need to type fastboot reboot fastboot to get to fastbootd)
This will take you into fastbootd. It will have a screen that has three different languages to choose from on it. Go ahead and fire up Fastboot Enhance now.
It may take a few seconds for the app to recognize the device but when you see it in the list, double-click it to get to the main screen.
{
"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"
}
Check that it says that the device is in fastbootd. Now we just need to click Flash Payload.bin and choose the OTA we downloaded earlier (we don't even need to extract the zip, the app does that for us). If it pops up with an unrecognized partitions error, you're either not in fastbootd, you didn't MSM back to stock (you cannot do this with a custom recovery), or you grabbed an OOS12 OTA. Do not continue and check that everything is correct otherwise you will brick and have to start all over with the MSM Tool. Likewise, if it pops up an alert about cow partitions, don't continue. Go to the partitions screen and search for cow and delete them all.
Once it's done, boot the device, factory reset it in the settings (this is mandatory as Fastboot Enhance does not erase the device like a normal downgrade would do and this can cause problems), set it back up, and then do the OTA process to get back to where you want to go.
Hey bud. So I ended up having too india again. After flashing nameless, it locked up completely. I followed along, but maybe I made a mistake around this point?
Once I was able to boot into India, i just used another msmtoolkit, this successfully converted my Pro to the proper OP 9 5g (the cutout for the cam was aligned so it worked) and i was now on 11.2.10.10
i then let the phone just OTA itself to Android 12.1 c.48
this is when i attempted to get into the latest nameless ROM that requires us to go from OOS 11 based system for the tom to A12.
did i mess up? Should i have flashed 12.1 again?
because the additional flash requirements were fairly straight forward. .
i unlocked the bootloader and then re-enabled /adb debugging the 12.1 and rebooted to bootloader
i flashed the 3 images i extracted from the payload of the latest 12.1 nameless zip and flashed them
fastboot flash boot boot.img
fastboot flash vendor_boot vendor_boot.img
fastboot flash dtbo dtbo.img
Click to expand...
Click to collapse
while in the same fastboot, i selected recovery boot. i was in the lineage recovery system, this is where i formatted and sideloaded in the same session
when i rebooted i was qualcom killed. could sitll fastboot but nothing would take so i just started over. i am now on my 2nd toolkit flash (india-pro to non-pro global.
i may just stick with the latest release that doesnt require 12. it doesnt help that im 2 days no sleep (unrelated but not helping) but even saying that, i feel i had most of what was required done, but im a big dummy so who knows
youre knowledge is sexy
THANK YOU SIR, true gentleman. Your post I guess was the only one convincing enough that it was finally brushed through the beta testing phase enough that it would be worth trying. No real risk here considering its just using that awesome tool you mentioned in the post, which i've never heard of. will be using for now on. Dunno about any testing with this method so i thought i would owe the community my post. i saw the sahara error post not too long ago talking about a fix with no testing yet xD that made me laugh honestly. But yeah my phone is now converted global through payload.bin flash in fastbootd. Tmo Variant had me & my girls phone networked unlocked through the one guy that was doing it for free on here a while back.. then applied for unlock code and did it officially, never tried to convert due to brick concerns, so i had the easy route through the methods involved in this post, considering i was still on oos 11 with bootloader unlocked when reading this. anyways, i think its safe to say its fixed pretty hyped to flash roms now and not get bootlooped and excited to see where this variant is gonna go! thanks again mate.
applyscience said:
Hey bud. So I ended up having too india again. After flashing nameless, it locked up completely. I followed along, but maybe I made a mistake around this point?
Once I was able to boot into India, i just used another msmtoolkit, this successfully converted my Pro to the proper OP 9 5g (the cutout for the cam was aligned so it worked) and i was now on 11.2.10.10
i then let the phone just OTA itself to Android 12.1 c.48
this is when i attempted to get into the latest nameless ROM that requires us to go from OOS 11 based system for the tom to A12.
did i mess up? Should i have flashed 12.1 again?
because the additional flash requirements were fairly straight forward. .
i unlocked the bootloader and then re-enabled /adb debugging the 12.1 and rebooted to bootloader
i flashed the 3 images i extracted from the payload of the latest 12.1 nameless zip and flashed them
while in the same fastboot, i selected recovery boot. i was in the lineage recovery system, this is where i formatted and sideloaded in the same session
when i rebooted i was qualcom killed. could sitll fastboot but nothing would take so i just started over. i am now on my 2nd toolkit flash (india-pro to non-pro global.
i may just stick with the latest release that doesnt require 12. it doesnt help that im 2 days no sleep (unrelated but not helping) but even saying that, i feel i had most of what was required done, but im a big dummy so who knows
youre knowledge is sexy
Click to expand...
Click to collapse
Did you use the copy partitions zip? You will brick if you don't do that after a MSM.
Process is:
MSM
Upgrade to C.48
Extract boot, dtbo, and vendor_boot from ROM
Fastboot flash dtbo, vendor_boot, and boot in that order
Reboot to recovery
Factory reset
Run copy partitions script
Reboot recovery
Flash ROM
Reboot
It shouldn't brick if you follow that process exactly.
zacattackkc said:
THANK YOU SIR, true gentleman. Your post I guess was the only one convincing enough that it was finally brushed through the beta testing phase enough that it would be worth trying. No real risk here considering its just using that awesome tool you mentioned in the post, which i've never heard of. will be using for now on. Dunno about any testing with this method so i thought i would owe the community my post. i saw the sahara error post not too long ago talking about a fix with no testing yet xD that made me laugh honestly. But yeah my phone is now converted global through payload.bin flash in fastbootd. Tmo Variant had me & my girls phone networked unlocked through the one guy that was doing it for free on here a while back.. then applied for unlock code and did it officially, never tried to convert due to brick concerns, so i had the easy route through the methods involved in this post, considering i was still on oos 11 with bootloader unlocked when reading this. anyways, i think its safe to say its fixed pretty hyped to flash roms now and not get bootlooped and excited to see where this variant is gonna go! thanks again mate.
Click to expand...
Click to collapse
Awesome, glad that it worked for you! There were two other testers before you as well as myself that have confirmed this method works, I guess I should have put that in the post. Thanks for being a guinea pig
question; so now that i did it through advanced boot app, does that mean my phone is officially seen as a global one? can i use global regular msm? can i use fastboot payload files for global, ect?
zacattackkc said:
question; so now that i did it through advanced boot app, does that mean my phone is officially seen as a global one? can i use global regular msm? can i use fastboot payload files for global, ect?
Click to expand...
Click to collapse
So your phone will be seen as global by OTAs but not the MSM. You would have to use a modded MSM Tool that flashes global firmware while targeting your device model.
EtherealRemnant said:
So your phone will be seen as global by OTAs but not the MSM. You would have to use a modded MSM Tool that flashes global firmware while targeting your device model.
Click to expand...
Click to collapse
damn.. that seems to be the culprit of everyone's hard brick.. so what about fastboot flashing oem software for global? I'm guessing that's not a problem because otas are of similar format, but just in a smaller package because it's adding only the updated parts instead of the full ROM.. and is this enhanced fastboot app an alternative to using msmtool and then unlocking bootloader and then flashing custom roms? kinda seems like it would be. and as a matter of fact after using the enhanced fastboot tool I went ahead and put it into fastbootd and flashed payload and it wouldn't boot at first. The app itself gave me an error regarding some cow partitions (really strange and very new concept for me) and told me that I could possibly fix everything if I deleted the cow partitions so I did and then formatted data and it booted into nameless AOSP. This might be the new way to flash custom roms due to the simple fact that it's way quicker than having to use NSM tool and then unlock bootloader and then do all the intricate flashing custom ROM parts. Just put in a fast boot d and flash just always have to make sure you format data afterwards to decrypt. This hasn't been fully tested at least not that I'm aware of
zacattackkc said:
damn.. that seems to be the culprit of everyone's hard brick.. so what about fastboot flashing oem software for global? I'm guessing that's not a problem because otas are of similar format, but just in a smaller package because it's adding only the updated parts instead of the full ROM.. and is this enhanced fastboot app an alternative to using msmtool and then unlocking bootloader and then flashing custom roms? kinda seems like it would be. and as a matter of fact after using the enhanced fastboot tool I went ahead and put it into fastbootd and flashed payload and it wouldn't boot at first. The app itself gave me an error regarding some cow partitions (really strange and very new concept for me) and told me that I could possibly fix everything if I deleted the cow partitions so I did and then formatted data and it booted into nameless AOSP. This might be the new way to flash custom roms due to the simple fact that it's way quicker than having to use NSM tool and then unlock bootloader and then do all the intricate flashing custom ROM parts. Just put in a fast boot d and flash just always have to make sure you format data afterwards to decrypt. This hasn't been fully tested at least not that I'm aware of
Click to expand...
Click to collapse
So honestly I haven't wanted to mess with it too much because it's such a chore to MSM and set everything back up. I can confirm the conversion works as long as you don't ignore any errors and continue (as you found out yourself with the cow files) but as for switching between custom ROMs, fastbootd is part of the custom recovery that we use to flash these ROMs and I don't know if it's possible to get a full flash using that custom recovery. When I tried to use an OOS12 OTA to skip having to use the MSM Tool to go back to stock, I got a partitions error and it rebooted to fastboot. Upon trying to flash the stock boot, dtbo, and vendor_boot, it bricked. I decided it was more important to figure out how to help people with their initial conversion process and I was frustrated because this particular brick was refusing to go into edl until I putzed around with the phone for a few minutes and managed to get it. It just isn't worth me possibly having an unrecoverable brick so I didn't mess with it any further.
In theory though, moving between custom ROMs using the same base firmware should be fine. People will have to test and find out.
EtherealRemnant said:
So honestly I haven't wanted to mess with it too much because it's such a chore to MSM and set everything back up. I can confirm the conversion works as long as you don't ignore any errors and continue (as you found out yourself with the cow files) but as for switching between custom ROMs, fastbootd is part of the custom recovery that we use to flash these ROMs and I don't know if it's possible to get a full flash using that custom recovery. When I tried to use an OOS12 OTA to skip having to use the MSM Tool to go back to stock, I got a partitions error and it rebooted to fastboot. Upon trying to flash the stock boot, dtbo, and vendor_boot, it bricked. I decided it was more important to figure out how to help people with their initial conversion process and I was frustrated because this particular brick was refusing to go into edl until I putzed around with the phone for a few minutes and managed to get it. It just isn't worth me possibly having an unrecoverable brick so I didn't mess with it any further.
In theory though, moving between custom ROMs using the same base firmware should be fine. People will have to test and find out.
Click to expand...
Click to collapse
ive been playing with them for the last 20 hours almost nonstop. im back to being tmobile but no msm tool (yet) will work with it. I tried almost every tmobile msm and a plethora of others have yet to work with it since. i also cant get my unlock_code.bin to work since i think somehow the code dont match with the region that it was applied with was. so i cant unlock my bootloader to get any conversion scripts or flashing commands to work. fastbootenhanced doesn't work either. i dont know what to do, please help me cuz i goofed hard as hell somewhere.
YourLocalDund33 said:
ive been playing with them for the last 20 hours almost nonstop. im back to being tmobile but no msm tool (yet) will work with it. I tried almost every tmobile msm and a plethora of others have yet to work with it since. i also cant get my unlock_code.bin to work since i think somehow the code dont match with the region that it was applied with was. so i cant unlock my bootloader to get any conversion scripts or flashing commands to work. fastbootenhanced doesn't work either. i dont know what to do, please help me cuz i goofed hard as hell somewhere.
Click to expand...
Click to collapse
Is the MSM saying device not match image, is it an unsupported target TMO error, what's the error?
EtherealRemnant said:
Is the MSM saying device not match image, is it an unsupported target TMO error, what's the error?
Click to expand...
Click to collapse
the msm is saying its a device mismatch and it thinks its the Indian variant but everything else is T-Mobile (stock), sorry about the late reply, its a holiday for me here.
Edit: I am Android version 12 now on T-Mobile, but I trying to get back to global rooted if that helps any with where I'm wanting to go with it
Edit 2: when I tried to use the multi msm tool provides I couldn't get O2 to show as an option anywhere, only Indian again.
YourLocalDund33 said:
the msm is saying its a device mismatch and it thinks its the Indian variant but everything else is T-Mobile (stock), sorry about the late reply, its a holiday for me here.
Edit: I am Android version 12 now on T-Mobile, but I trying to get back to global rooted if that helps any with where I'm wanting to go with it
Edit 2: when I tried to use the multi msm tool provides I couldn't get O2 to show as an option anywhere, only Indian again.
Click to expand...
Click to collapse
If it thinks it's an Indian variant, you use my modded MSM and select India for the target.
I recovered my bricked LE2110 from Oneplus 9 pro Indian msm tools and I wish to restore it to Oneplus 9 global rom. I try to use the "Fastboot enhance (version 1.3)" to flash the payload.bin into my LE2110, but I cannot find any "lfash" button ! The only button I can see is "Extract Image", am I missing something ? I try local upgrade but it cannot find the firmware file ! Please help !
EtherealRemnant said:
If it thinks it's an Indian variant, you use my modded MSM and select India for the target.
Click to expand...
Click to collapse
Thats why i edited my post, I tried to use the modded tool but it only gives the option for the indian variant. the 02 option is not there boss.
YourLocalDund33 said:
Thats why i edited my post, I tried to use the modded tool but it only gives the option for the indian variant. the 02 option is not there boss.
Click to expand...
Click to collapse
Which mod are you using? There have been a bunch posted in this forum.
EtherealRemnant said:
Which mod are you using? There have been a bunch posted in this forum.
Click to expand...
Click to collapse
the one from the op. its the one thats said its multi support for indian and global
YourLocalDund33 said:
the one from the op. its the one thats said its multi support for indian and global
Click to expand...
Click to collapse
Try this one.
3.56 GB file on MEGA
mega.nz
That one is also multi target. Both of these have been tested, I don't know why it's not working for you. You can also try not selecting a target and see what happens, I have found I don't always need to select the target if my device firmware hasn't been too corrupted.
Beware that with this one, you can't unlock the bootloader until after you go to OOS12 because OnePlus bugged the erase script on 11.2.10.10.
EtherealRemnant said:
Try this one.
3.56 GB file on MEGA
mega.nz
That one is also multi target. Both of these have been tested, I don't know why it's not working for you. You can also try not selecting a target and see what happens, I have found I don't always need to select the target if my device firmware hasn't been too corrupted.
Beware that with this one, you can't unlock the bootloader until after you go to OOS12 because OnePlus bugged the erase script on 11.2.10.10.
Click to expand...
Click to collapse
I'm already OOS12. still couldn't unlock bootloader. I was on chat with Oneplus support for an hour or so just a few minutes ago. They were a little slow with understanding the situation (didn't mention to them using a lot of modded msm tools) but I did tell them I used the tool to reset it to stock. that and my unlock_code.bin was no longer working. They put me on chat with the higher team and then the supervisor herself overtook chat and had a look at when my original application for my phone was. She decided she will reissue me a new code and said after 24-48hrs ill get the new code via email. How familiar are you with the erase script with the msm tool?
YourLocalDund33 said:
I'm already OOS12. still couldn't unlock bootloader. I was on chat with Oneplus support for an hour or so just a few minutes ago. They were a little slow with understanding the situation (didn't mention to them using a lot of modded msm tools) but I did tell them I used the tool to reset it to stock. that and my unlock_code.bin was no longer working. They put me on chat with the higher team and then the supervisor herself overtook chat and had a look at when my original application for my phone was. She decided she will reissue me a new code and said after 24-48hrs ill get the new code via email. How familiar are you with the erase script with the msm tool?
Click to expand...
Click to collapse
It's not the MSM Tool that's borked, it's the ROM itself.
Looking for a stock c61 LE2115 Global boot.img (oneplus 9)
I overwrote mine trying to root and now I can't get the phone to boot back into c61. I have access to fastboot though