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.
Related
Update: The guys at Razer are just about as clueless as a retail phone carrier. They told me to do the exact same thing, the factory reset and all that, but they don't know what they're doing.
So FYI: IF YOU'RE BOOTLOADER IS LOCKED AND YOUR OS WON'T START, YOU'RE SCREWED.
Okay so I rooted the phone on Oreo, the second to last update, and tried to update it to the May update, and the update kept failing inside the system update app. So, I tried installing it by flashing it from a computer. Unsuccessfully. So, I booted into TWRP and installed every image manually through TWRP. Bootlooped it. Soooooo I tried to flash the latest stock image from the computer, and it goes through, but the phone refuses to turn on. And I can't even unlock the bootloader because in the command prompt it says it's not allowed. So I'm stuck with a paperweight that won't unlock any bootloaders and won't even boot into the OS. I think I royally screwed it up and I desperately just wanna use the phone again.
I've tried everything. My drivers are correct, and It just won't cooperate with me no matter what I do to it. It'll either keep booting into download mode or get stuck on the splash screen forever.
I'm literally desperate at this point. I can't do anything with this thing!!! I can't flash anything because it's locked and the phone won't boot into the OS for me to even unlock it.
How did you get twrp with a locked bootloader? :S is that a thing now?
You cant flash the factory images without an unlocked bootloader. So if you didn't check the OEM unlock allowed setting you won't be able to unlock it so won't be able to flash the firmware.
Honestly i think you're out of luck if you can't unlock your bootloader.
Wait how did your bootloader relock itaelf? Because that can happen only with the lock/lock_critical command.
---------- Post added at 02:07 PM ---------- Previous post was at 02:03 PM ----------
Dashaquavius said:
Okay so I rooted the phone on Oreo, the second to last update, sand tried to update it to the May update, and the update kept failing inside the system update app. So, I tried installing it by flashing it from a computer. Unsuccessfully. So, I booted into TWRP and installed every image manually through TWRP. Bootlooped it. Soooooo I tried to flash the latest stock image from the computer, and it goes through, but the phone refuses to turn on. And I can't even unlock the the bootloader because in the command prompt it says it's not allowed. So I'm stuck with a paperweight that won't unlock any bootloaders and won't even boot into the OS. I think I royally screwed it up and I desperately just wanna use the phone again..
I've tried everything. My drivers are correct, and It just won't cooperate with me no matter what I do to it. It'll either keep booting into download mode or get stuck on the splash screen forever.
I'm literally desperate at this point. I can't do anything with this thing!!! I can't flash anything because it's locked and the phone won't boot into the OS for me to even unlock it..
Click to expand...
Click to collapse
Did you say the factory images fully flash with no errors? Both "fastboot flashing unlock/unlock_critical" don't work?
You should try the flash_all.bat or flash_all.sh script from the latest images. If you want to keep your data just comment or erase the line with the "fastboot erase userdata" in the flash_all.
Be sure to have fastboot in your path
Roxas598 said:
How did you get twrp with a locked bootloader? :S is that a thing now?
You cant flash the factory images without an unlocked bootloader. So if you didn't check the OEM unlock allowed setting you won't be able to unlock it so won't be able to flash the firmware.
Honestly i think you're out of luck if you can't unlock your bootloader
Click to expand...
Click to collapse
iliais347 said:
Wait how did your bootloader relock itaelf? Because that can happen only with the lock/lock_critical command.
Did you say the factory images fully flash with no errors? Both "fastboot flashing unlock/unlock_critical" don't work?
Click to expand...
Click to collapse
waiflih said:
You should try the flash_all.bat or flash_all.sh script from the latest images. If you want to keep your data just comment or erase the line with the "fastboot erase userdata" in the flash_all.
Be sure to have fastboot in your path
Click to expand...
Click to collapse
1. I didn't flash TWRP with the bootloader in the locked state, it was while it was unlocked.
2. Out of desperation, after flashing the stock images multiple times (while it says errors and maximum download reached and stuff) I re-locked the bootloader with the command thinking it would finally at least boot into the OS, to no avail.
3. Factory images didn't flash without some kind of error.
4. I'm unable to run any kind of commands, it says it's not allowed.
5. I've flashed multiple times, flashed the previous updates and the latest updates, and there's always some kind of error or it's not allowed.
I'm just gonna contact Razer. Apparently, I can't flash anything if the bootloader is locked? And the phone won't even boot into the OS to let me tick the option? I think I'm screwed.
For what you are telling you may have an outdated fastboot version. Can you try flash_all and post the error messages? kinda difficult to help without that
waiflih said:
For what you are telling you may have an outdated fastboot version. Can you try flash_all and post the error messages? kinda difficult to help without that
Click to expand...
Click to collapse
It says flashing is not allowed for everything.
Ok that is indeed strange. Take a look at this https://insider.razer.com/index.php...afe-method-warning-rebuilds-partitions.23532/
its for the robin but since you already tried everything else you can give it a shot
waiflih said:
Ok that is indeed strange. Take a look at this https://insider.razer.com/index.php...afe-method-warning-rebuilds-partitions.23532/
its for the robin but since you already tried everything else you can give it a shot
Click to expand...
Click to collapse
I just got off with Razer support, they're just gonna send me a new one.
And apparently, absolutely NO OTG support!
Let this thread serve as a warning..
how did you manage to get razer to agree a replacement??.i had a speaker issue and had to send a video of my problem then a week later they finally agreed to replace it.you have done really well for them to accept phone back for replacemnet..as for relocking bootloader as far as i read the other day once you do this phone is bricked
parky169 said:
how did you manage to get razer to agree a replacement??.i had a speaker issue and had to send a video of my problem then a week later they finally agreed to replace it.you have done really well for them to accept phone back for replacemnet..as for relocking bootloader as far as i read the other day once you do this phone is bricked
Click to expand...
Click to collapse
Interesting. I sent 2 phones with speaker issues and they offered a replacement for both and gave me shipping labela.
Hey guys, last week i wanna flash a custom rom on my SM-a520f/DS but my OEM unlock was missing,I thought i just had to wait for 7 days but it won't show even after 7 days
Now i flashed official stock rom and will try to wait again for 7 days, but if this doesn't work then imma bout to lose my mind.
What can i do if it doesnt oem unlock doesnt p
Appear even if you reflashed stock romm
MitchiePitchie said:
Hey guys, last week i wanna flash a custom rom on my SM-a520f/DS but my OEM unlock was missing,I thought i just had to wait for 7 days but it won't show even after 7 days
Now i flashed official stock rom and will try to wait again for 7 days, but if this doesn't work then imma bout to lose my mind.
What can i do if it doesnt oem unlock doesnt p
Appear even if you reflashed stock romm
Click to expand...
Click to collapse
Maybe a factory reset would help, I dunno...
TechGuyOnTechIT said:
Maybe a factory reset would help, I dunno...
Click to expand...
Click to collapse
Just reflashed stock rom and waiting 7 days. I'll update if it works:fingers-crossed:
MitchiePitchie said:
Just reflashed stock rom and waiting 7 days. I'll update if it works:fingers-crossed:
Click to expand...
Click to collapse
Well this SHOULD fix the issue. If not, then I suspect the phone's internal clock is messed and needs complicated repair, but this a very very very VERY rare occasion, and I doubt you don't have this issue.
My phone just flashed a ok TWRP, but after I accidentally restarted, the phone didn't put me in OEM jail. Talk about lucky!
Just wait 7 days, activate developer options, click unlock oem, flash twrp via odin and after that is done IMMEDIATELY hold power and plus so it doesn't get you back to oem jail. After you are in TWRP, try not to turn it off to keep the recovery, and either install a zip that removes the 7 day jail or a cudtom rom. If you don't have a microsd to transfer from your pc to your phone, just use adb sideload. If you have any questions, just reply!
TechGuyOnTechIT said:
Well this SHOULD fix the issue. If not, then I suspect the phone's internal clock is messed and needs complicated repair, but this a very very very VERY rare occasion, and I doubt you don't have this issue.
My phone just flashed a ok TWRP, but after I accidentally restarted, the phone didn't put me in OEM jail. Talk about lucky!
Just wait 7 days, activate developer options, click unlock oem, flash twrp via odin and after that is done IMMEDIATELY hold power and plus so it doesn't get you back to oem jail. After you are in TWRP, try not to turn it off to keep the recovery, and either install a zip that removes the 7 day jail or a cudtom rom. If you don't have a microsd to transfer from your pc to your phone, just use adb sideload. If you have any questions, just reply!
Click to expand...
Click to collapse
WAIT, so you need to wait 7 days before activating developer's option? Does that put you in prenormal rmm state? Because i already activated my developer's option, If thats the case then i already messed up
MitchiePitchie said:
WAIT, so you need to wait 7 days before activating developer's option? Does that put you in prenormal rmm state? Because i already activated my developer's option, If thats the case then i already messed up
Click to expand...
Click to collapse
No, you haven't messed up! The 7 day jail doens't block you access to developer options, but doesn't let you enable OEM unlock. I was suggesting you should do this just to make sure you are not in the 7 day jail. Again, if you can check that option, then there is not a problem. Just try to have your jail patcher zip handy so you won't have to deal with this problem. Again, if you have any questions, just reply!
TechGuyOnTechIT said:
No, you haven't messed up! The 7 day jail doens't block you access to developer options, but doesn't let you enable OEM unlock. I was suggesting you should do this just to make sure you are not in the 7 day jail. Again, if you can check that option, then there is not a problem. Just try to have your jail patcher zip handy so you won't have to deal with this problem. Again, if you have any questions, just reply!
Click to expand...
Click to collapse
Okay, the OEM unlock didn't showed up and my rmm state is still prenormal after 7 days even in flashing stock. I might retry this again in another rom carrier. I'm really at the end of my rope here
MitchiePitchie said:
Okay, the OEM unlock didn't showed up and my rmm state is still prenormal after 7 days even in flashing stock. I might retry this again in another rom carrier. I'm really at the end of my rope here
Click to expand...
Click to collapse
Don't give up! Try to go to download mode, flash a complete Samsung rom (with bootloader, modem, recovery and rom). I guess you can find a stock samsung rom on google or via smart switch. Download mode only blocks installing THIRD PARTY ROMS, not the stock ones. Try that and give a reply.
TechGuyOnTechIT said:
Don't give up! Try to go to download mode, flash a complete Samsung rom (with bootloader, modem, recovery and rom). I guess you can find a stock samsung rom on google or via smart switch. Download mode only blocks installing THIRD PARTY ROMS, not the stock ones. Try that and give a reply.
Click to expand...
Click to collapse
I'll try to flash the rom again and wait 7 days, I'll boot ip without sim and sd card first
TechGuyOnTechIT said:
Don't give up! Try to go to download mode, flash a complete Samsung rom (with bootloader, modem, recovery and rom). I guess you can find a stock samsung rom on google or via smart switch. Download mode only blocks installing THIRD PARTY ROMS, not the stock ones. Try that and give a reply.
Click to expand...
Click to collapse
Man I already flashed stock rom and waited 7 days, I ain't doing that stuff again I'll just sell this phone if I don't find any other way.
MitchiePitchie said:
Man I already flashed stock rom and waited 7 days, I ain't doing that stuff again I'll just sell this phone if I don't find any other way.
Click to expand...
Click to collapse
Seriously? Are you SURE you don't see OEM unlock in developer options, because any Samsung device SHOULD have the 7 day lift period. If you confirm that you don't see it, the only thing left to do is to contact a samsung expert. Don't feel embarrassed that you ask samsung for a third party thing, they must help you even though that may result in voiding your warranty.
Honestly, this is a pretty uncommon issue :/
TechGuyOnTechIT said:
Seriously? Are you SURE you don't see OEM unlock in developer options, because any Samsung device SHOULD have the 7 day lift period. If you confirm that you don't see it, the only thing left to do is to contact a samsung expert. Don't feel embarrassed that you ask samsung for a third party thing, they must help you even though that may result in voiding your warranty.
Honestly, this is a pretty uncommon issue :/
Click to expand...
Click to collapse
I'll try reflashing a carrier rom (Globe) not a XTC (openline) rom and if this doesn't work then i dont know what will:fingers-crossed:
MitchiePitchie said:
I'll try reflashing a carrier rom (Globe) not a XTC (openline) rom and if this doesn't work then i dont know what will:fingers-crossed:
Click to expand...
Click to collapse
Samsung support centre could also help.
TechGuyOnTechIT said:
Seriously? Are you SURE you don't see OEM unlock in developer options...Honestly, this is a pretty uncommon issue :/
Click to expand...
Click to collapse
I have the same issue. Started with Android 7, rooted phone, flashed Hades ROM v6 ( Android 8) which is fine, but I no longer see OEM Unlock in Developer options (presumably I did before installing Hades). Have tried the date fudge:
https://forum.xda-developers.com/samsung-a-series-2017/help/guide-oem-unlock-oreo-t3791774
more than once. No joy. Hades is fine, but I'd like to try the OneUI Android 9 ROM...
Corbynista said:
I have the same issue. Started with Android 7, rooted phone, flashed Hades ROM v6 ( Android 8) which is fine, but I no longer see OEM Unlock in Developer options (presumably I did before installing Hades). Have tried the date fudge:
https://forum.xda-developers.com/samsung-a-series-2017/help/guide-oem-unlock-oreo-t3791774
more than once. No joy. Hades is fine, but I'd like to try the OneUI Android 9 ROM...
Click to expand...
Click to collapse
If you are still on hades, the dev removed the OEM unlock toggle to prevent noobs from disabling it which would bootloop your phone and twrp would also not boot. Most if not all custom roms remove it. So you can flash Oneui
Corbynista said:
I have the same issue. Started with Android 7, rooted phone, flashed Hades ROM v6 ( Android 8) which is fine, but I no longer see OEM Unlock in Developer options (presumably I did before installing Hades). Have tried the date fudge:
https://forum.xda-developers.com/samsung-a-series-2017/help/guide-oem-unlock-oreo-t3791774
more than once. No joy. Hades is fine, but I'd like to try the OneUI Android 9 ROM...
Click to expand...
Click to collapse
When you are on cfw, as the guy said, there is no need. The rom is third party, meaning it's not official, thus it remains unlocked. But if you are on stock rom, then the oem unlock will be shown.
iloveoreos said:
If you are still on hades, the dev removed the OEM unlock toggle to prevent noobs from disabling it which would bootloop your phone and twrp would also not boot. Most if not all custom roms remove it. So you can flash Oneui
Click to expand...
Click to collapse
TechGuyOnTechIT said:
When you are on cfw, as the guy said, there is no need. The rom is third party, meaning it's not official, thus it remains unlocked. But if you are on stock rom, then the oem unlock will be shown.
Click to expand...
Click to collapse
I wondered if this was the case. Thanks to you both.
TechGuyOnTechIT said:
Samsung support centre could also help.
Click to expand...
Click to collapse
that ain't an option for me since they dont really respond. You know any other option if it doesn't even show this week too?
i reflashed stock rom like 5 times now
MitchiePitchie said:
that ain't an option for me since they dont really respond. You know any other option if it doesn't even show this week too?
i reflashed stock rom like 5 times now
Click to expand...
Click to collapse
Punch your phone, return it, and get another one.
SnowFuhrer said:
Punch your phone, return it, and get another one.
Click to expand...
Click to collapse
Nooooo! Don't do that! That would be a waste! Maybe its a bug. Try to flash twrp even though it doesn't show you kem unlock, and if that still doesn't work, give up trying systemless rooting and go full supersu by doing a one-click root (kingroot, etc). Maybe that helps. If it still not working, then I will finally recommend bailing and just getting another one . Sorry...
Wanted to find out if there was a way to revert to the stock rom without hassle.
Yeah, you can use LMSA for that.
arsradu said:
Yeah, you can use LMSA for that.
Click to expand...
Click to collapse
will it lock my bootloader though? Also did you face any issues while using that
rowhen_ said:
will it lock my bootloader though? Also did you face any issues while using that
Click to expand...
Click to collapse
No. And no.
Just make sure your power is stable, so it doesn't interrupt the flashing process.
Also, if you're doing that, I'm curious whether or not your OEM Unlocking option is still ON after flashing stock ROM. It should be ON. If it's not, don't attempt to lock back the bootloader or you may end up in a brick.
arsradu said:
No. And no.
Just make sure your power is stable, so it doesn't interrupt the flashing process.
Also, if you're doing that, I'm curious whether or not your OEM Unlocking option is still ON after flashing stock ROM. It should be ON. If it's not, don't attempt to lock back the bootloader or you may end up in a brick.
Click to expand...
Click to collapse
yeah, it's turned on by default
rowhen_ said:
yeah, it's turned on by default
Click to expand...
Click to collapse
Is it still on after flashing back stock ROM?
Cause, in my case, it's not. It's greyed out, and turned OFF. And it's driving me crazy, cause I don't know why is it still OFF.
arsradu said:
Is it still on after flashing back stock ROM?
Cause, in my case, it's not. It's greyed out, and turned OFF. And it's driving me crazy, cause I don't know why is it still OFF.
Click to expand...
Click to collapse
i havent flashed the stock rom yet so cant say, would it pose an issue if the OEM unlocking button is greyed out?
rowhen_ said:
i havent flashed the stock rom yet so cant say, would it pose an issue if the OEM unlocking button is greyed out?
Click to expand...
Click to collapse
No, but it would pose an issue if it's OFF and you want to relock the bootloader. Don't even attempt relocking your bootloader if that option is OFF.
That option can be:
1. active (not greyed out) with toggle ON or OFF.
2. inactive (greyed out) with toggle ON or OFF.
What's important is the position of that toggle. Because, what that says is that the bootloader is still unlockable.
YES, it is unlocked right now. And you might even get a message telling you that, but if the toggle is OFF, that means the bootloader is no longer unlockable (or get_unlock_ability=0).
Why is this bad? Well, because if you want to relock the bootloader, and something goes wrong, and you end up in an unbootable situation (with an error like "no valid operating system could be found"), you won't be able to unlock the bootloader again to fix your issue, or at least flash another ROM or something so you can boot back into the OS.
Fastboot will complain that the OEM Unlocking option is OFF, and will not allow you to flash anything. And obviously, you won't be able to boot back into the OS to turn it on.
So, be very careful about that option!
If you don't plan on relocking the bootloader, no worries. But if you do, be very, very careful what does that option say.
You can read more about it here.
arsradu said:
No, but it would pose an issue if it's OFF and you want to relock the bootloader. Don't even attempt relocking your bootloader if that option is OFF.
That option can be:
1. active (not greyed out) with toggle ON or OFF.
2. inactive (greyed out) with toggle ON or OFF.
What's important is the position of that toggle. Because, what that says is that the bootloader is still unlockable.
YES, it is unlocked right now. And you might even get a message telling you that, but if the toggle is OFF, that means the bootloader is no longer unlockable (or get_unlock_ability=0).
Why is this bad? Well, because if you want to relock the bootloader, and something goes wrong, and you end up in an unbootable situation (with an error like "no valid operating system could be found"), you won't be able to unlock the bootloader again to fix your issue, or at least flash another ROM or something so you can boot back into the OS.
Fastboot will complain that the OEM Unlocking option is OFF, and will not allow you to flash anything. And obviously, you won't be able to boot back into the OS to turn it on.
So, be very careful about that option!
If you don't plan on relocking the bootloader, no worries. But if you do, be very, very careful what does that option say.
You can read more about it here.
Click to expand...
Click to collapse
That makes sense. Yeah I dont mind the unlocked bootloader, no plans on relocking it.
Also The LMSA doesnt seem to detect my phone, is there like a guide I that I can follow to flash the stock ROM? (I'm currently on PE 12 )
rowhen_ said:
That makes sense. Yeah I dont mind the unlocked bootloader, no plans on relocking it.
Also The LMSA doesnt seem to detect my phone, is there like a guide I that I can follow to flash the stock ROM? (I'm currently on PE 12 )
Click to expand...
Click to collapse
You don't really need a guide. But yeah, LMSA won't detect the phone anymore because of the custom ROM.
You need the Rescue option and you need to enter your IMEI for the device to be detected. Everything else is self explanatory. The device needs to be in fastboot mode for this procedure. And make sure the cable is ok. I would recommend using the original cable.
arsradu said:
You don't really need a guide. But yeah, LMSA won't detect the phone anymore because of the custom ROM.
You need the Rescue option and you need to enter your IMEI for the device to be detected. Everything else is self explanatory. The device needs to be in fastboot mode for this procedure. And make sure the cable is ok. I would recommend using the original cable.
Click to expand...
Click to collapse
I flashed the stock rom and yes, the bootloader option is greyed out but unlocked. But tbh the rom's pretty trash lol. This was the reason I started considering custom rom's in the first place.
rowhen_ said:
I flashed the stock rom and yes, the bootloader option is greyed out but unlocked. But tbh the rom's pretty trash lol. This was the reason I started considering custom rom's in the first place.
Click to expand...
Click to collapse
So the OEM Unlocking option is ON in your case? Could you please help me with a screenshot, for reference? I'm trying to understand why mine is OFF.
Also, which custom ROM did you have before going back to stock ROM?
arsradu said:
So the OEM Unlocking option is ON in your case? Could you please help me with a screenshot, for reference? I'm trying to understand why mine is OFF.
Also, which custom ROM did you have before going back to stock ROM?
Click to expand...
Click to collapse
No Its turned off but greyed out. And the subtext below it says "bootloader already unlocked". Sorry cant share screenshots because I've already switched to lineage os 20. The stock rom was almost unusable
rowhen_ said:
No Its turned off but greyed out. And the subtext below it says "bootloader already unlocked". Sorry cant share screenshots because I've already switched to lineage os 20. The stock rom was almost unusable
Click to expand...
Click to collapse
Ah ok. But why do you say it was almost unusable? I didn’t have any issues with it? Also, in the meantime, I’ve relocked my bootloader, and thank Goodness, everything went fine.
What do you like in LineageOS? Personally I don’t like it.
arsradu said:
Ah ok. But why do you say it was almost unusable? I didn’t have any issues with it? Also, in the meantime, I’ve relocked my bootloader, and thank Goodness, everything went fine.
What do you like in LineageOS? Personally I don’t like it.
Click to expand...
Click to collapse
It was stuttering like crazy, the battery life was surprisingly trash. I prefer Pixel Experience 13 over Lineage OS but I was facing some minor issues with it so stuck with Lineage
rowhen_ said:
It was stuttering like crazy, the battery life was surprisingly trash. I prefer Pixel Experience 13 over Lineage OS but I was facing some minor issues with it so stuck with Lineage
Click to expand...
Click to collapse
That's weird... I've got no stuttering, battery is pretty damn good, so is signal, and I've got IMS services, which are pretty important to me. Also, Tap to Pay now works again, after locking the bootloader.
Well, I'm glad Lineage works for your! I also prefer PE. But...there are some issue right now. And I'm waiting for a new update which could potentially fix them.
Hi
I have Mi 10T 5G
I update it and the system crashed every time I powered on it's show me (the system has been destroyed)
nothing work only fastboot
no I can't flash firmware via Mi flash via fasboot it's show me (erase is not alloed in Lock state)
I tried to use Miflash unlock to unlock bootloader but I can't it's showed me this (please add your account in Mi account)
what could I do now?
Thanks
First of all: stay calm and don't randomly try things in panic mode, that usually makes it worse. Detail your problem a bit further, explaining all steps that lead to the bootloop. You still have fastboot, that's a good start. Breathe
Timmmmaaahh! said:
First of all: stay calm and don't randomly try things in panic mode, that usually makes it worse. Detail your problem a bit further, explaining all steps that lead to the bootloop. You still have fastboot, that's a good start. Breathe
Click to expand...
Click to collapse
No No I'm not panic but I tried everything but the same
this mobile for my friend al last he told me that he root it when I update the system that waht happened to me
and now I think must use test point
IRAQIGHOST said:
No No I'm not panic but I tried everything but the same
this mobile for my friend al last he told me that he root it when I update the system that waht happened to me
and now I think must use test point
Click to expand...
Click to collapse
Have you tried flashing official firmware images? I'm not really familiar with Xiaomi but it shouldn't require a bootloader unlock. In any case it should be covered under warranty if you don't want to go too deep down the rabbit hole...
Timmmmaaahh! said:
Have you tried flashing official firmware images? I'm not really familiar with Xiaomi but it shouldn't require a bootloader unlock. In any case it should be covered under warranty if you don't want to go too deep down the rabbit hole...
Click to expand...
Click to collapse
Yes, I used an official firmware from Xiaomi This baffles me, why does he want to unlock the bootloader if it is official?
Timmmmaaahh! said:
Have you tried flashing official firmware images? I'm not really familiar with Xiaomi but it shouldn't require a bootloader unlock. In any case it should be covered under warranty if you don't want to go too deep down the rabbit hole...
Click to expand...
Click to collapse
Yes, I used an official firmware from Xiaomi This baffles me, why does he want to unlock the bootloader if it is official?
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!