Related
I see threads on manually upgrading 8.0->8.1 but none for 8.1->8.0 . Can anyone let me know what needs to be done?
tvdang7 said:
I see threads on manually upgrading 8.0->8.1 but none for 8.1->8.0 . Can anyone let me know what needs to be done?
Click to expand...
Click to collapse
I know Google implemented a new anti-role back feature to it's impossible to roll back if your bootloader is locked and your running stock recovery. If your running twrp you probably could do a system wipe and install 8.0, but I am not sure. I haven't tried haha. Hopefully someone can she'd more light on that.
Stock = No
TWRP = Maybe (Probably?)
Ericarthurc said:
I know Google implemented a new anti-role back feature to it's impossible to roll back if your bootloader is locked and your running stock recovery. If your running twrp you probably could do a system wipe and install 8.0, but I am not sure. I haven't tried haha. Hopefully someone can she'd more light on that.
Stock = No
TWRP = Maybe (Probably?)
Click to expand...
Click to collapse
damn thanks for the reply. I am on stock but bootloader is unlocked.
tvdang7 said:
I see threads on manually upgrading 8.0->8.1 but none for 8.1->8.0 . Can anyone let me know what needs to be done?
Click to expand...
Click to collapse
From what ive read you can. But requires a full wipe of data.
This was possible for me to do before 8.1 was officially rolled out. I was on 8.1 developer preview, I wanted to go back to 8.0 to take advantage of the kernels which at the time we're only for 8.0, so I opted out of the developer preview with Google, they sent an ota to my device, it of course would not take as I was rooted, however the original factory image for 8.0 could be flashed through fastboot.
Yeah I did it to, but it takes a full wipe
jrbxx7 said:
From what ive read you can. But requires a full wipe of data.
Click to expand...
Click to collapse
mac796 said:
Yeah I did it to, but it takes a full wipe
Click to expand...
Click to collapse
Does this mean factory reset first then flash? or do i need to run some adb commands.
tvdang7 said:
Does this mean factory reset first then flash? or do i need to run some adb commands.
Click to expand...
Click to collapse
reboot to bootloader
Code:
fastboot -aa (sets slot a active)
flash-all (using Full Stock 8.0 Factory Image, not an OTA)
If you can catch it before it reboots, hold down the vol-dn to go back into bootloader after it's done flashing - otherwise power off and then power-on holding vol-dn to get back into bootloader.
Code:
fastboot -ab (sets slot b active)
flash-all
done.
Any issues, switch USB ports and/or cables. Do NOT use a USB-C cable.
That's it. Has worked twice for me on my 2XL, bought from Google)
No you cannot. Not even with twrp
You would need to flash the full image via fastboot, and ensure /data was wiped in the process. It would be much trickier due to the dual slots, and odds are you couldn't flash the bootloader with the other images, so it would be a mostly manual flashing process.
Sent from my Pixel 2 XL using Tapatalk
State.of.mind said:
No you cannot. Not even with twrp
Click to expand...
Click to collapse
I don't think this is correct. Apparently the Rollback Index is not updated for devices with unlocked bootloaders. Now I guess I'm not sure if it matters what Android version you were on before unlocking; for example I guess I'm not sure if you get a Pixel 2 XL, immediately update to 8.1, then decide to unlock you bootloader and then try to flash back to 8.0 if it will matter that your Rollback Index probably was updated because you had it locked when updating.
imnuts said:
You would need to flash the full image via fastboot, and ensure /data was wiped in the process. It would be much trickier due to the dual slots, and odds are you couldn't flash the bootloader with the other images, so it would be a mostly manual flashing process.
Sent from my Pixel 2 XL using Tapatalk
Click to expand...
Click to collapse
Isn't that what the instructions provided by @PhoenixPath (below) are meant to do?
PhoenixPath said:
reboot to bootloader
Code:
fastboot -aa (sets slot a active)
flash-all (using Full Stock 8.0 Factory Image, not an OTA)
If you can catch it before it reboots, hold down the vol-dn to go back into bootloader after it's done flashing - otherwise power off and then power-on holding vol-dn to get back into bootloader.
Code:
fastboot -ab (sets slot b active)
flash-all
done.
Any issues, switch USB ports and/or cables. Do NOT use a USB-C cable.
That's it. Has worked twice for me on my 2XL, bought from Google)
Click to expand...
Click to collapse
Out of curiosity, why are you saying not to use a USB C cable? I would've thought that would've sped things up a bit, if available on ones computer...
cognitivedissonance said:
Out of curiosity, why are you saying not to use a USB C cable? I would've thought that would've sped things up a bit, if available on ones computer...
Click to expand...
Click to collapse
re: USB-C: I have yet to see a PC USB-C port used reliably for this or any other flashing process. It either flat-out doesn't work, or it gets partway there and fails. If anyone has had success with it, I have not witnessed it or seen it reported, so I have to suggest sticking with Type-A ports on the PC-side of things for now.
You are, as always, free to give it a shot.
(If you do and it works for ya, let me know; I'd love to hear some success stories there.)
cognitivedissonance said:
I don't think this is correct. Apparently the Rollback Index is not updated for devices with unlocked bootloaders. Now I guess I'm not sure if it matters what Android version you were on before unlocking; for example I guess I'm not sure if you get a Pixel 2 XL, immediately update to 8.1, then decide to unlock you bootloader and then try to flash back to 8.0 if it will matter that your Rollback Index probably was updated because you had it locked when updating.
Click to expand...
Click to collapse
I didn't unlock the bootloader until after updating to 8.1 right after I got the phone. Since that time, I've flashed back to 8.0 no problem.
PhoenixPath said:
re: USB-C: I have yet to see a PC USB-C port used reliably for this or any other flashing process. It either flat-out doesn't work, or it gets partway there and fails. If anyone has had success with it, I have not witnessed it or seen it reported, so I have to suggest sticking with Type-A ports on the PC-side of things for now.
You are, as always, free to give it a shot.
(If you do and it works for ya, let me know; I'd love to hear some success stories there.)
Click to expand...
Click to collapse
Interesting, I would've assumed the new USB C standard would've worked much more reliably than the older methods. I wonder what causes the instability like that. Anyway, thanks for the heads up.
Oh just to clarify, my understanding is correct, right? Those instructions you posted will allow downgrading system versions for unlocked bootloader Pixel 2 XLs?
---------- Post added at 01:14 PM ---------- Previous post was at 01:04 PM ----------
Str0ntium said:
I didn't unlock the bootloader until after updating to 8.1 right after I got the phone. Since that time, I've flashed back to 8.0 no problem.
Click to expand...
Click to collapse
This is very good to hear - thank you for confirming!! I assume you used the method Phoenix detailed?
cognitivedissonance said:
Oh just to clarify, my understanding is correct, right? Those instructions you posted will allow downgrading system versions for unlocked bootloader Pixel 2 XLs?
Click to expand...
Click to collapse
So long as it's not a Verizon device and the device has been given the "fastboot flashing unlock_critical" treatment, you should be good to go. I've done this on my Google-store bought 2 XL several times. Has worked for me going from 8.1 to 8.0 and from P to 8.0 (and 8.1).
The part that seems to trip up most users is the need to flash both slots.
PhoenixPath said:
So long as it's not a Verizon device and the device has been given the "fastboot flashing unlock_critical" treatment, you should be good to go. I've done this on my Google-store bought 2 XL several times. Has worked for me going from 8.1 to 8.0 and from P to 8.0 (and 8.1).
The part that seems to trip up most users is the need to flash both slots.
Click to expand...
Click to collapse
Yeah, the slots thing and the "unlock_critical" are both new to me, coming from a Nexus 6P. I'm going to do a bit of additional reading to just try and wrap my head around exactly what the changes are and what the additional commands do. Thanks again!
cognitivedissonance said:
This is very good to hear - thank you for confirming!! I assume you used the method Phoenix detailed?
Click to expand...
Click to collapse
Basically, yeah. I flashed the image to both slots without booting to OS. Then flashed twrp, magisk, etc...
PhoenixPath said:
Any issues, switch USB ports and/or cables. Do NOT use a USB-C cable.
Click to expand...
Click to collapse
For the record, and I know I am far in the minority on this, but flashing with a USB-C to USB-C cable works perfectly with my PixelBook and Pixel 2 XL.
Again, just to re-iterate, there are probably very few people who do this with USB-C to USB-C, and even fewer with a PixelBook, but it does work.
uicnren said:
For the record, and I know I am far in the minority on this, but flashing with a USB-C to USB-C cable works perfectly with my PixelBook and Pixel 2 XL.
Again, just to re-iterate, there are probably very few people who do this with USB-C to USB-C, and even fewer with a PixelBook, but it does work.
Click to expand...
Click to collapse
So...this is news to me. The PixelBook is a Chromebook, and I have one (A Chromebook, not the PixelBook). I have never even considered using it as my insta-boot phone flashing tool. Definitely going to have to read up on it if you're saying this is actually possible. Nice!
PhoenixPath said:
So...this is news to me. The PixelBook is a Chromebook, and I have one (A Chromebook, not the PixelBook). I have never even considered using it as my insta-boot phone flashing tool. Definitely going to have to read up on it if you're saying this is actually possible. Nice!
Click to expand...
Click to collapse
Well, its not an easy process, for sure, which is why I know I am in the very small minority.
Also, at the very least, your Chromebook will need to support (and you'll have to enable) developer mode.
Most do adb/fastboot through 'Crouton". Check that out.
On the PixelBook it can be done natively, but it is not an easy thing to do, as I said above. PixelBooks come with adb/fastboot already on them (once your in developer mode) however, they are out of date and will not work with newer Pixel phones, so, you need to go through a lot of hoops to update them to the latest.
Weird screen behavior, it seem to me that it isn't a hardware fault, cause when plugging in a charger the phone is able to show the MI logo, but not the charging icon
The phone is able to boot and i can hear the phone locking and unlocking, can see that the screen is on because of the backlight, but there is no image, SO FRUSTRATING!!
If you have any idea of what's going on and can give me a tip, i would thank you so much, the phone has been on this state for a long time
Don't know how to upload videos, if you think that can help diagnose it i can upload it and share a link or something
Hugask said:
Weird screen behavior, it seem to me that it isn't a hardware fault, cause when plugging in a charger the phone is able to show the MI logo, but not the charging icon
The phone is able to boot and i can hear the phone locking and unlocking, can see that the screen is on because of the backlight, but there is no image, SO FRUSTRATING!!
If you have any idea of what's going on and can give me a tip, i would thank you so much, the phone has been on this state for a long time
Don't know how to upload videos, if you think that can help diagnose it i can upload it and share a link or something
Click to expand...
Click to collapse
What did you do before?
Did you flash something?
Is it device unlocked?
This happen also in fastboot/recovery mode?
SubwayChamp said:
What did you do before?
Did you flash something?
Is it device unlocked?
This happen also in fastboot/recovery mode?
Click to expand...
Click to collapse
I hadnt updated my Rom, Pixel experience, in a while, so i took the opportunity and flashed an (at the time) beta Pixel Experience Android 10, i reverted and everything was fine for about one day i think, then some artifacting wich would come and go until the display gived up completly (about an hour between the two)
Yes, it is unlocked, and when in fastboot/recovery the screen is lighted up but not showing anything
My guess is that i have a low level firmware issue, as i had problem with those before (was running a custom ROM from day 1, so i had to manually update firware to use newer versions of PE (still pie version) and almost bricked my device
Hugask said:
I hadnt updated my Rom, Pixel experience, in a while, so i took the opportunity and flashed an (at the time) beta Pixel Experience Android 10, i reverted and everything was fine for about one day i think, then some artifacting wich would come and go until the display gived up completly (about an hour between the two)
Yes, it is unlocked, and when in fastboot/recovery the screen is lighted up but not showing anything
My guess is that i have a low level firmware issue, as i had problem with those before (was running a custom ROM from day 1, so i had to manually update firware to use newer versions of PE (still pie version) and almost bricked my device
Click to expand...
Click to collapse
Then try the next:
- Flash a different vendor.
- Flash a different kernel.
- Revert to stock ROM, no need to lock or nothing, just flash first the recovery ROM but if it doesn't result then flash the fastboot ROM through EDL, so that you know you can boot to EDL mode without need to open the back cover, this will restore all the original images.
SubwayChamp said:
Then try the next:
- Flash a different vendor.
- Flash a different kernel.
- Revert to stock ROM, no need to lock or nothing, just flash first the recovery ROM but if it doesn't result then flash the fastboot ROM through EDL, so that you know you can boot to EDL mode without need to open the back cover, this will restore all the original images.
Click to expand...
Click to collapse
Ok, so... i think i have all the files, but i'm really lost, how am i supposed to flash the vendor, firmware and stock ROM via fastboot?
Also, i put the device in fastboot, so... thats a win i guess (screen working surprisingtly)
I'm just not finding how to do this, it's been a while that i havent messed with this side of android, if you could help me it would mean the world for me
Hugask said:
Ok, so... i think i have all the files, but i'm really lost, how am i supposed to flash the vendor, firmware and stock ROM via fastboot?
Also, i put the device in fastboot, so... thats a win i guess (screen working surprisingtly)
I'm just not finding how to do this, it's been a while that i havent messed with this side of android, if you could help me it would mean the world for me
Click to expand...
Click to collapse
You can flash some images invoking the right partition, I mean, you can flash vendor image onto the vendor partition using
Code:
fastboot flash vendor vendor.img
, and in case you need to flash all the ROM you should use MiFlash tool
SubwayChamp said:
You can flash some images invoking the right partition, I mean, you can flash vendor image onto the vendor partition using
Code:
fastboot flash vendor vendor.img
, and in case you need to flash all the ROM you should use MiFlash tool
Click to expand...
Click to collapse
Ok, so... i am NOT keeping up with what i need to do, i found a vendor update in a site but it is not an image, i am so confused, i don't how was i able to mess around with this i am basically a noob, i feel so dumb, this should have been so easy and here i am having trouble
If you could make a step by step instruction or send a link where i can get a vendor .img it would be perfect thanks in advance
Hugask said:
Ok, so... i am NOT keeping up with what i need to do, i found a vendor update in a site but it is not an image, i am so confused, i don't how was i able to mess around with this i am basically a noob, i feel so dumb, this should have been so easy and here i am having trouble
If you could make a step by step instruction or send a link where i can get a vendor .img it would be perfect thanks in advance
Click to expand...
Click to collapse
Ok, update what is the current status of your device, you said screen now displaying, Did you refer only to fastboot mode? Could you see the bunny in fastboot? But booted up on system screen is displaying nothing?
SubwayChamp said:
Ok, update what is the current status of your device, you said screen now displaying, Did you refer only to fastboot mode? Could you see the bunny in fastboot? But booted up on system screen is displaying nothing?
Click to expand...
Click to collapse
Yes, that is correct, i can see the fastboot screen 100%, no artifacts, just plain working, still no recovery (if i remember right i have orange fox) or ROM screen
Hugask said:
Yes, that is correct, i can see the fastboot screen 100%, no artifacts, just plain working, still no recovery (if i remember right i have orange fox) or ROM screen
Click to expand...
Click to collapse
And what do you want to do now? Did you unlock bootloader?
SubwayChamp said:
And what do you want to do now? Did you unlock bootloader?
Click to expand...
Click to collapse
I actually want to check that, i took the phone to a tecnitician and he may have locked the bootloader
I think the next step would be flashing the vendor, firmwares and stock rom again, right?
Hugask said:
I actually want to check that, i took the phone to a tecnitician and he may have locked the bootloader
I think the next step would be flashing the vendor, firmwares and stock rom again, right?
Click to expand...
Click to collapse
if your bootloader is locked, you can't flash through fastboot mode either vendor or stock ROM, you should need to use EDL method or you can re-unlock bootloader and this way will work. Anyway i don't understand what actually your issue is.
SubwayChamp said:
if your bootloader is locked, you can't flash through fastboot mode either vendor or stock ROM, you should need to use EDL method or you can re-unlock bootloader and this way will work. Anyway i don't understand what actually your issue is.
Click to expand...
Click to collapse
The issue is the display not working, and it's gotta be a firmware issue as it's on my desk right now showing a bunny, also i am not used to fastboot flash anything, i just was used to recoveries and what not
Just runned some code and it's locked, this is getting better and better oh boy
How am i gonna unlock this if i can't even unlock the phone? last time with screen working it was already a nightmare, having to wait for miui account, do i have any method of doing this without using EDL?
Hugask said:
The issue is the display not working, and it's gotta be a firmware issue as it's on my desk right now showing a bunny, also i am not used to fastboot flash anything, i just was used to recoveries and what not
Just runned some code and it's locked, this is getting better and better oh boy
How am i gonna unlock this if i can't even unlock the phone? last time with screen working it was already a nightmare, having to wait for miui account, do i have any method of doing this without using EDL?
Click to expand...
Click to collapse
Well, this make sense although it's not clear if you did unlock it previously and after that at some time you did lock it again.
If you didn't unlock it previously you would need to bind your Mi account to the device and enable USB debugging and OEM unlock options but if you didn't before without a screen working you have a more difficult way, confirm me if that is the case.
Anyway I got happily surprised when I bought this device some months ago at the first attempt I could unlock it without have to wait time, try it and see what happen.
SubwayChamp said:
Well, this make sense although it's not clear if you did unlock it previously and after that at some time you did lock it again.
If you didn't unlock it previously you would need to bind your Mi account to the device and enable USB debugging and OEM unlock options but if you didn't before without a screen working you have a more difficult way, confirm me if that is the case.
Anyway I got happily surprised when I bought this device some months ago at the first attempt I could unlock it without have to wait time, try it and see what happen.
Click to expand...
Click to collapse
It was unloked and i locked again, don't know if this helps my case or if i am royally screwed up
And yeah, Xioami does make difficult to do the process of unlocking but only to recently released devices, aparently to stop re-sellers to buy the cheaper chinese rom and put the global version on them, i think that when a device doenst get made anymore makes sense that they would make it more easy (i bought the device 2 weeks after launch)
Hugask said:
It was unloked and i locked again, don't know if this helps my case or if i am royally screwed up
And yeah, Xioami does make difficult to do the process of unlocking but only to recently released devices, aparently to stop re-sellers to buy the cheaper chinese rom and put the global version on them, i think that when a device doenst get made anymore makes sense that they would make it more easy (i bought the device 2 weeks after launch)
Click to expand...
Click to collapse
Ok, of course this makes a huge difference, if you did unlock it previously then you couldn't receive any wait time, I wonder why you didn't try it if you didn 't. Check if MiUnlock tool unlock your device instantly.
SubwayChamp said:
Ok, of course this makes a huge difference, if you did unlock it previously then you couldn't receive any wait time, I wonder why you didn't try it if you didn 't. Check if MiUnlock tool unlock your device instantly.
Click to expand...
Click to collapse
OMG THIS WORKED
It's been sucessfully unlocked
Hugask said:
OMG THIS WORKED
It's been sucessfully unlocked
Click to expand...
Click to collapse
Hmm, OK, now you have your way sorted out, you can try with a custom ROM (all of them contain a vendor) or in case a custom ROM doesn't solve it you have to try a stock ROM through Mi Flash tool.
SubwayChamp said:
Hmm, OK, now you have your way sorted out, you can try with a custom ROM (all of them contain a vendor) or in case a custom ROM doesn't solve it you have to try a stock ROM through Mi Flash tool.
Click to expand...
Click to collapse
Ok, but how am i gonna flash a rom with fastboot? Is that a thing?
Also, i don't think the vendor is gonna be my only problem, but also the firmware, is there a way to flash firmware without the recovery and trough fastboot?
Hugask said:
Ok, but how am i gonna flash a rom with fastboot? Is that a thing?
Also, i don't think the vendor is gonna be my only problem, but also the firmware, is there a way to flash firmware without the recovery and trough fastboot?
Click to expand...
Click to collapse
You can't be sure of that, sometimes the vendor correct the issue, sometimes the firmware.
Firmware it is in the stock ROM that can be flashed either through fastboot or EDL mode (be careful to not relock bootloader or you couldn't enable this time OEM unlock option). Now that you have the way more clear just do a search "how to flash stock ROM on Xiaomi devices either through fastboot or EDL mode", just keep in mind that you don't need to open the back cover of the device, usually from a device off (only on unlocked ones) you could send it to EDL by pressing both volume buttons at same time that it is connected to PC, I gave you the main tips, for the rest you will find a lot of tutorials.
Just as a reminder: the MSM tool resets your device and locks the bootloader. If for whatever reason, you modified partitions that are not touched by the MSM tool (like param, persist, etc), there is a chance your device will fail the integrity check and will not boot with the red message "Your device is corrupt". If you're at this stage, there is no good way to get you back. Maybe someone knows how to toggle "enable oem unlock" without being able to boot to OS, but without that ability, your device is essentially hard bricked.
Is it what happen to your device ? Hopefully you could recover ?
Steve0007 said:
Is it what happen to your device ? Hopefully you could recover ?
Click to expand...
Click to collapse
No, someone else's, we're trying to see if there's anything we can do via edl currently
craznazn said:
No, someone else's, we're trying to see if there's anything we can do via edl currently
Click to expand...
Click to collapse
Hope it's not a one way street...
craznazn said:
Just as a reminder: the MSM tool resets your device and locks the bootloader. If for whatever reason, you modified partitions that are not touched by the MSM tool (like param, persist, etc), there is a chance your device will fail the integrity check and will not boot with the red message "Your device is corrupt". If you're at this stage, there is no good way to get you back. Maybe someone knows how to toggle "enable oem unlock" without being able to boot to OS, but without that ability, your device is essentially hard bricked.
Click to expand...
Click to collapse
I came across the corrupt message twice during my rooting mission hold down pwr+vol up+vol down until it shut off, then held down all three buttons til it turns on and it went into bootloader mode. It did take several tries but it got there. Then I could oem lock/unlock and reboot to a fresh system. Now I didn't mess with my partitions so maybe that is something deeper but it's worth a try.
hllywd said:
I came across the corrupt message twice during my rooting mission hold down pwr+vol up+vol down until it shut off, then held down all three buttons til it turns on and it went into bootloader mode. It did take several tries but it got there. Then I could oem lock/unlock and reboot to a fresh system. Now I didn't mess with my partitions so maybe that is something deeper but it's worth a try.
Click to expand...
Click to collapse
Yeah, we can get to the bootloader and EDL mode. However, we can't fastboot oem lock/unlock because OEM lock/unlock option is not togged in the System -> Dev options -> OEM Unlocking. This is a T-Mobile device, so not only that, we need to flash cust-unlock first which is not possible with OEM unlocking disabled in dev options.
avid_droid said:
Looks like I won't be doing the Tmo to EU. Looks like root will suffice until MSM for 2127 is released. I'm just wanting my camera updated to the latest and couldn't get it on unrooted. Waiting for my token, will use your magusk patch and update my camera. Thanks for the warning
Click to expand...
Click to collapse
The MSM for the 2127 is actually available now via remote support, just nobody has posted it online yet. That's where this warning comes from. Another user was able to run the 2127 MSM on his phone, and now it's bricked
I thought there was a command for the oem tick switch?
This is essentially what happened to my device! I ended up just returning it as I was in The 15day return window. Waiting on a refund now
ssjucrono said:
This is essentially what happened to my device! I ended up just returning it as I was in The 15day return window. Waiting on a refund now
Click to expand...
Click to collapse
When did this happen? What device did you have?
craznazn said:
When did this happen? What device did you have?
Click to expand...
Click to collapse
Oneplus 9 pro green 256gb. Happened last Wednesday
craznazn said:
Just as a reminder: the MSM tool resets your device and locks the bootloader. If for whatever reason, you modified partitions that are not touched by the MSM tool (like param, persist, etc), there is a chance your device will fail the integrity check and will not boot with the red message "Your device is corrupt". If you're at this stage, there is no good way to get you back. Maybe someone knows how to toggle "enable oem unlock" without being able to boot to OS, but without that ability, your device is essentially hard bricked.
Click to expand...
Click to collapse
Might be a good idea to update the thread title as it's misleading. Makes it look like the normal MSM tool is going F someone's normal variant device. Most people don't have the crappy T-Mobile variant. I understand saving a quick Buck is important though.
avid_droid said:
Looks like I won't be doing the Tmo to EU. Looks like root will suffice until MSM for 2127 is released. I'm just wanting my camera updated to the latest and couldn't get it on unrooted. Waiting for my token, will use your magusk patch and update my camera. Thanks for the warning
Click to expand...
Click to collapse
Is this the Camera app from APKmirror? The one that you'd have to move to... privapp, I think? Because they failed to sign it correctly?
avid_droid said:
Don't understand when people say "save a quick buck on Tmo," when it's exactly the same $1069 right across. It's about getting it in hand instead of waiting for shipping. And the thread is not misleading as it is for the 2127 which is the Tmo variant but it doesn't say that haha
Click to expand...
Click to collapse
Clearly is misleading because he doesn't put T-Mobile in the thread title.
I'd gladly wait up to 2 weeks to get a device that has timely updates and easily has up-to-date development..
avid_droid said:
Yes. Root is needed.
Click to expand...
Click to collapse
How is it so far? Is it worth trying out?
Burt Squirtz said:
Clearly is misleading because he doesn't put T-Mobile in the thread title.
I'd gladly wait up to 2 weeks to get a device that has timely updates and easily has up-to-date development..
Click to expand...
Click to collapse
It's not misleading, because ANY device where you modify a partition that is not usually touched my the MSM tool can result in a hard brick if it's checked by avb
avid_droid said:
@craznazn , it's only if you edit partitions correct? My unlock token should be here in a few days and plan on only rooting for a couple apps. This won't affect my re-locking would it?
Click to expand...
Click to collapse
Rooting only touches the boot partition and that's fine. Even flashing AA/BA/DA is fine because all of those partitions will just get overwritten by the MSM. Things only start to get dicey when you start messing with param, persist, and the likes.
craznazn said:
Rooting only touches the boot partition and that's fine. Even flashing AA/BA/DA is fine because all of those partitions will just get overwritten by the MSM. Things only start to get dicey when you start messing with param, persist, and the likes.
Click to expand...
Click to collapse
Just theoretical question: would flashing the device to something else like LineageOS (if there was working version) help? Or is the partitions check on HW/FW level?
drozd128 said:
Just theoretical question: would flashing the device to something else like LineageOS (if there was working version) help? Or is the partitions check on HW/FW level?
Click to expand...
Click to collapse
Once the bl is locked due to msm, you can't flash anything again.
craznazn said:
Once the bl is locked due to msm, you can't flash anything again.
Click to expand...
Click to collapse
I see. Thank you.
Hi, i am one of the idiots who tried to lock back the bootloader and now i bricked the device, cannot unlock anymore the bootloader, but i saw there is a download mode option, i was wondering anybody have the files to flash a stock rom to that method?
Regards
Your only options are to send the unit to Google and pay the penalty for locking the bootloader, or sell the unit for parts. No file that works in the unit's EDL mode has ever been available.
thanks, i guess for spare parts sad day for this pixel
nongrata23 said:
thanks, i guess for spare parts sad day for this pixel
Click to expand...
Click to collapse
Before you do, are you able to get to the unit's recovery? Or is all the firmware gone?
If the recovery is still present, installing Google's last full OTA should be able to restore the system so you can either unlock the bootloader or sell as a working unit.
Strephon Alkhalikoi said:
Before you do, are you able to get to the unit's recovery? Or is all the firmware gone?
If the recovery is still present, installing Google's last full OTA should be able to restore the system so you can either unlock the bootloader or sell as a working unit.
Click to expand...
Click to collapse
Cannot find operating system, no matter what i do i have fastboot mode but nothing works
.....
Well s***. There isn't anything else that can be done here then.
I tried downgrading my Moto G30 from Android 12 to Android 11 using an available stock ROM I found on the internet. At first, I faced some problems and a soft brick, but finally, I was able to flash and boot it correctly. Then, knowing that the ROM flashed was "stock," I decided to relock the bootloader, which was a mistake. After rebooting, I got the message "No valid operating system could be found. The device will not boot."
I spent the whole day trying to figure out how to get it working again. The main problem here is that I relocked the bootloader and can't get to the OS again to enable the option in developer settings to re-unlock it and flash another ROM. I tried using RSA (LMSA) to restore it, but it refuses, and I think it gets the same error that won't let me flash anything to the phone.
During my research, I found that one possible solution is to boot in EDL mode and flash everything again, but I don't want to open my phone and do weird things to get into that mode. Hopefully, there's another solution or another way to get into EDL.
If you have any information that could help me solve this, please comment.
I had the same problem with mine. The thing is, i tried to flash a blank-flash image but it wont go. I think its to early to downgrade your Moto G30, but you can try to flash the stock image in EDL Mode by opening your Motorola. Also you might need to send it to Motorola. Sorry
In the image you have the EDL Test Point you must brick.
But also you can try
fastboot reboot edl
Click to expand...
Click to collapse
or
reboot edl
Click to expand...
Click to collapse
U_ShowcaseDev said:
But also you can try
or
Click to expand...
Click to collapse
I've already tried several combinations of that command with no success.
aldoo9 said:
I've already tried several combinations of that command with no success.
Click to expand...
Click to collapse
Sorry I think your Motorola is Dead.
U_ShowcaseDev said:
I had the same problem with mine. The thing is, i tried to flash a blank-flash image but it wont go. I think its to early to downgrade your Moto G30, but you can try to flash the stock image in EDL Mode by opening your Motorola. Also you might need to send it to Motorola. Sorry
In the image you have the EDL Test Point you must brick.
Click to expand...
Click to collapse
Hello again! Do you know how to flash the stock rom in EDL mode? I've found some tutorials but the files required are not available in the stock rom files to do so.
aldoo9 said:
Hello again! Do you know how to flash the stock rom in EDL mode? I've found some tutorials but the files required are not available in the stock rom files to do so.
Click to expand...
Click to collapse
Please send me a Link.
aldoo9 said:
Hello again! Do you know how to flash the stock rom in EDL mode? I've found some tutorials but the files required are not available in the stock rom files to do so.
Click to expand...
Click to collapse
Don't you need to just blankflash it in EDL?
And yes you most likely need to open it.
For the Blankflash you need to download Lenovo Rescue and Smart Assistant (since lenovo produces moto phones). What this does it installs the correct drivers for your phone.
And the files can be found here : https://mirrors.lolinet.com/firmware/motorola/caprip/blankflash/
Good luck and as always, do your own research!
Edit: https://forum.xda-developers.com/t/hard-brick-moto-g30.4397117/page-2 this thread has more info.
KAN7A said:
Don't you need to just blankflash it in EDL?
And yes you most likely need to open it.
For the Blankflash you need to download Lenovo Rescue and Smart Assistant (since lenovo produces moto phones). What this does it installs the correct drivers for your phone.
And the files can be found here : https://mirrors.lolinet.com/firmware/motorola/caprip/blankflash/
Good luck and as always, do your own research!
Edit: https://forum.xda-developers.com/t/hard-brick-moto-g30.4397117/page-2 this thread has more info.
Click to expand...
Click to collapse
I tried one, but it doesn't work. The Bootloader keeps locked.
U_ShowcaseDev said:
I tried one, but it doesn't work. The Bootloader keeps locked.
Click to expand...
Click to collapse
Isn't the point to flash the stock ROM, not to unlock the bootloader?
Yes, you right. But how???
KAN7A said:
Isn't the point to flash the stock ROM, not to unlock the bootloader?
Click to expand...
Click to collapse
I saw, that you can flash a .xml Stock Firmware FIle. But i dont find anyone that work...
U_ShowcaseDev said:
I saw, that you can flash a .xml Stock Firmware FIle. But i dont find anyone that work...
Click to expand...
Click to collapse
I think you can flash with Lenovo Rescue and Smart Assistant or manually, the XML is to flash automatically, you can flash manually each image.
If you cant maybe there is an error along the way.
I might look into this later. I would lock my bootloader to test but i dont have a backup.
KAN7A said:
I think you can flash with Lenovo Rescue and Smart Assistant or manually, the XML is to flash automatically, you can flash manually each image.
If you cant maybe there is an error along the way.
I might look into this later. I would lock my bootloader to test but i dont have a backup.
Click to expand...
Click to collapse
That can be the end to your phone. But, if you have a test phone that would be excellent.
KAN7A said:
I think you can flash with Lenovo Rescue and Smart Assistant or manually, the XML is to flash automatically, you can flash manually each image.
If you cant maybe there is an error along the way.
I might look into this later. I would lock my bootloader to test but i dont have a backup.
Click to expand...
Click to collapse
Lenove RSA doesn't work. I tried it. When the Bootloader is unlocked it work. When the Bootloader is locked it wont work.
U_ShowcaseDev said:
Lenove RSA doesn't work. I tried it. When the Bootloader is unlocked it work. When the Bootloader is locked it wont work.
Click to expand...
Click to collapse
I dont have a test device right now so i cant test myself, anything I say might be wrong.
This might be a complete brick because of the downgrade from what I've read.
There is little info on the forum about this issue so I don't want to make wrong suggestions until i can test.
Yes, unfortunately, there is still little information about the Moto G30. But I hope that there will be more information and solutions in the future.
U_ShowcaseDev said:
Yes, unfortunately, there is still little information about the Moto G30. But I hope that there will be more information and solutions in the future.
Click to expand...
Click to collapse
Maybe you can help me with some info i am interested in.
1.You have booted into EDL using Short Pin method
2.You have used blankflash successfully
3.Then you try to flash manually and got Permission Denied?
For both Android 11 Stock ROM and Android 12 Stock Rom?
EDIT: Is the back of the phone glued? Or just clamps so you can put it back with no glue?
Since i want to test this soon hopefully.
KAN7A said:
Maybe you can help me with some info i am interested in.
1.You have booted into EDL using Short Pin method
2.You have used blankflash successfully
3.Then you try to flash manually and got Permission Denied?
For both Android 11 Stock ROM and Android 12 Stock Rom?
EDIT: Is the back of the phone glued? Or just clamps so you can put it back with no glue?
Since i want to test this soon hopefully.
Click to expand...
Click to collapse
1. Yes
2. I used a blankflash successfully.
3. Then in fastboot tried to flash the android 11 stock and after it failed the android 12 stock image. Also i tried the RSA varient. Both will not work.
The back is clicked in place. There are two stickers on the phone. Two white ones, One on the top left corner and one on the bottom of the phone.
But careful when you open the back. The screws are well screwed and the cap over the motherboard is slightly stuck. Maybe this will help you: Dissasembly Moto G30 YouTube
@U_ShowcaseDev Thank you so much! This is exactly what i wanted to know!