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.
Related
I was on 8.1 with Flash Kernel installed using images...I wanted to get back to stock...so unchecked OEM Unlocking in Developer Options, went to bootloader and locked bootloader using fastoboot flashing lock..and now I am getting "Can't find valid operating system. The device will not start". I can't unlock the bootloader now as I unchecked OEM unlocking in Developer Options and can't flash factory images also as it says Flashing is not allowed in Lock State, Did I brick the device?
Update: I have returned my device to Google and they processed a replacement
i am just curious, how were planning on flashing a rom with locked bootloader?
ram4ufriends said:
I was on 8.1 with Flash Kernel installed using images...I wanted to get back to stock...so unchecked OEM Unlocking in Developer Options, went to bootloader and locked bootloader using fastoboot flashing lock..and now I am getting "Can't find valid operating system. The device will not start". I can't unlock the bootloader now as I unchecked OEM unlocking in Developer Options and can't flash factory images also as it says Flashing is not allowed in Lock State, Did I brick the device?
Click to expand...
Click to collapse
Yea, I think you may have turned it into a fancy paperweight. Been there, done that. You should have waited to uncheck OEM unlocking until after you locked the bootloader, which wiped your phone. About the only thing I can suggest is to try and run Deuces script to see if you can rescue your device. Best of luck to you.
https://forum.xda-developers.com/pi...ol-deuces-bootloop-recovery-flashing-t3704761
ram4ufriends said:
I was on 8.1 with Flash Kernel installed using images...I wanted to get back to stock...so unchecked OEM Unlocking in Developer Options, went to bootloader and locked bootloader using fastoboot flashing lock..and now I am getting "Can't find valid operating system. The device will not start". I can't unlock the bootloader now as I unchecked OEM unlocking in Developer Options and can't flash factory images also as it says Flashing is not allowed in Lock State, Did I brick the device?
Click to expand...
Click to collapse
Sorry for your loss, but you indeed have a fancy paperweight.
However I wonder if there isnt the QCom USB mode or something like that that exist on older devices, where you can access the phone partitions at a lower level and then restore whatever partitions is broken.
Paradoxxx said:
Sorry for your loss, but you indeed have a fancy paperweight.
However I wonder if there isnt the QCom USB mode or something like that that exist on older devices, where you can access the phone partitions at a lower level and then restore whatever partitions is broken.
Click to expand...
Click to collapse
With the new partitioning no idea if it still works. But OP has nothing to loose anyway i guess.
gee2012 said:
With the new partitioning no idea if it still works. But OP has nothing to loose anyway i guess.
Click to expand...
Click to collapse
Yeah at that point... Not sure what is Google saying about that. Maybe RMA it ?
Saying something like that should work.
"I was using my device, and suddenly it froze and nothing responded. It suddenly rebooted and shown this error message."
gee2012 said:
With the new partitioning no idea if it still works. But OP has nothing to loose anyway i guess.
Click to expand...
Click to collapse
Sorry didn't get, What do you mean by OP has nothing to loose?
Badger50 said:
Yea, I think you may have turned it into a fancy paperweight. Been there, done that. You should have waited to uncheck OEM unlocking until after you locked the bootloader, which wiped your phone. About the only thing I can suggest is to try and run Deuces script to see if you can rescue your device. Best of luck to you.
https://forum.xda-developers.com/pi...ol-deuces-bootloop-recovery-flashing-t3704761
Click to expand...
Click to collapse
How did you recover your devices from that state earlier when you did the same thing?
ram4ufriends said:
Sorry didn't get, What do you mean by OP has nothing to loose?
Click to expand...
Click to collapse
since your phone is now essentially a brick, you can try just about anything without worry of bricking your phone.
ram4ufriends said:
I was on 8.1 with Flash Kernel installed using images...I wanted to get back to stock...so unchecked OEM Unlocking in Developer Options, went to bootloader and locked bootloader using fastoboot flashing lock..and now I am getting "Can't find valid operating system. The device will not start". I can't unlock the bootloader now as I unchecked OEM unlocking in Developer Options and can't flash factory images also as it says Flashing is not allowed in Lock State, Did I brick the device?
Click to expand...
Click to collapse
You cannot flash full images, but you can still flash OTAs... download the full OTA instead, and install (sideload) it from the stock recovery. Be sure to select the SAME build number you were on to begin with- eg. If you were on 8.1, use the 8.1 OTA. There will be a mode there for "Apply update from ADB". You put the phone into "sideload mode" and then send the OTA to the phone via adb. This will work regardless whether you have usb debugging enabled or not. Follow the directions given on the included link.
ram4ufriends said:
How did you recover your devices from that state earlier when you did the same thing?
Click to expand...
Click to collapse
I didn't. They are still paperweights sitting in a drawer!
I got the same message yesterday after doing... God knows what. I can't even remember what went wrong.
My first thought was to flash a factory image. But it didn't helped at first. Probably, because i was trying to flash another factory image and not the one that came as stock on my phone.
So if you don't remember, which image it was, try all of them Hopefully, you'll get your phone booted again.
My first reaction was, is this april fools day? Is this an xda style joke? unchecked oem unlock?
dontbeweakvato said:
My first reaction was, is this april fools day? Is this an xda style joke? unchecked oem unlock?
Click to expand...
Click to collapse
Meh...you know how it is bro....**it happens!
Call google and just tell them your device wont boot all of a sudden; they will probably ask you to factory restore in the recovery, say the phone wont get past the google image. They will RMA that boy for you. You totally bricked. For future reference if you unlock the bootloader, dont waste your time trying to lock it again. Should have just fastboot flashed a factory image in the bootloader and called it a day. Having a unlocked bootloader doesn't effect you in anyway negatively.
ArminasAnarion said:
Call google and just tell them your device wont boot all of a sudden; they will probably ask you to factory restore in the recovery, say the phone wont get past the google image. They will RMA that boy for you. You totally bricked. For future reference if you unlock the bootloader, dont waste your time trying to lock it again. Should have just fastboot flashed a factory image in the bootloader and called it a day. Having a unlocked bootloader doesn't effect you in anyway negatively.
Click to expand...
Click to collapse
Why is this Google's problem? This guy is at fault. Google shouldn't have to pay for it.
This is part of the reason these phones are so expensive.
Sent from my taimen using XDA Labs
mitchdickson said:
Why is this Google's problem? This guy is at fault. Google shouldn't have to pay for it.
This is part of the reason these phones are so expensive.
Sent from my taimen using XDA Labs
Click to expand...
Click to collapse
Well I never said it was the moral thing to do haha; but this guys best bet is to call Google and see if they will RMA it. They RMA'ed my Nexus 6p after the Android 7 twrp brick; and I told them my pone wouldn't boot anymore; they asked me to go to recovery and factory restore, I told them I couldn't boot into recovery and they RMA'ed it. It was my fault for the brick but they didn't care.
ArminasAnarion said:
Well I never said it was the moral thing to do haha; but this guys best bet is to call Google and see if they will RMA it. They RMA'ed my Nexus 6p after the Android 7 twrp brick; and I told them my pone wouldn't boot anymore; they asked me to go to recovery and factory restore, I told them I couldn't boot into recovery and they RMA'ed it. It was my fault for the brick but they didn't care.
Click to expand...
Click to collapse
Did you tell them it was your fault for the brick?
Sent from my taimen using XDA Labs
mitchdickson said:
Did you tell them it was your fault for the brick?
Sent from my taimen using XDA Labs
Click to expand...
Click to collapse
I told them I had an unlocked boot-loader and installed twrp. I had to send them back my old phone and they put a $500 hold on my account, once they received the device and determined the issue was real, they released the hold on my account. In that period of time they could have determined "Oh he bricked the device with twrp" lets charge him $500 for a new one, but they didn't. I mean whats wrong with calling Google and seeing if they will RMA it; sure the OP made a bad mistake but you have not because you ask not.
ArminasAnarion said:
I told them I had an unlocked boot-loader and installed twrp. I had to send them back my old phone and they put a $500 hold on my account, once they received the device and determined the issue was real, they released the hold on my account. In that period of time they could have determined "Oh he bricked the device with twrp" lets charge him $500 for a new one, but they didn't. I mean whats wrong with calling Google and seeing if they will RMA it; sure the OP made a bad mistake but you have not because you ask not.
Click to expand...
Click to collapse
What's wrong with it? You're telling him to call Google and say that for some reason, all the sudden his device won't boot.
This is why I don't fault Verizon for selling bootloader locked phones.
Sent from my taimen using XDA Labs
Moto G7 Play bootloader unlock issues - "bad key", not OTA, no way to roll back?
My plan was to unlock the bootloader before configuring the new phone - just in case I might need it later, then use the phone as out-of-box. I unlocked the bootloader for the new Moto G7 Play, following the official procedure via the Motorola Accounts page, resulting in:
- Fastboot page shows: "flashing unlocked"
- When booting up, I see a black page with the words "bad key", then the phone boots
- The updater sais that the phone is corrupt and no (OTA) updates can be done
- I could not try TWRP, as there is no TWRP for the G7 Play yet (so not sure if flashing would work)
My concerns now are that I will not be able to update the phone, and that the "bad key" issue might cause other problems.
So my plan would be to roll back and lock the phone again, to use it as out-of-box (not worrying about warranty loss that might already have happened - I did accept these terms). However, that does not work, too:
- Locking bootloader requires factory images, which are not available for the G7 Play
- Locking bootloader with fastboot OEM lock will not work without complete images
Any suggestions how bring the phone back to normal? I am disappointed by Motorola, as they officially offer the unlock procedure - which then does not produce the expected outcome, breaks updating, and provides no way to go back? Mind you, I did not apply any "hacks", nothing but the official Motorola unlocking steps.
Thanks for advice
I have the same problem and i cannot fix it.
I tried to get advice from Motorola support - but replies are very generic, referring to the bootloader unlock page (we obviously found that) or to the Motorola Forum (where the answer isn't). Will now just live with the unlocked phone and hope for the opportunity to OTA / update in a while
CoffeeMachineSwitch said:
- When booting up, I see a black page with the words "bad key", then the phone boots
- The updater sais that the phone is corrupt and no (OTA) updates can be done
Click to expand...
Click to collapse
Unlocking any Motorola bootloader will cause the bootscreen to display "Bad Key". This is normal. It is a warning that the bootloader has been unlocked and the phone may not be "safe". Once you root a Motorola phone, it will display "N/A" instead of "Bad Key". Again, this is normal behavior. There are image makers that can replace the "splash" image and "hide" the "N/A", but since this phone doesn't have TWRP yet, you'll have to live with it for now.
As far as not being able to receive OTA updates, I have no knowledge. In my opinion it shouldn't matter that the bootloader has been unlocked...only if you've modified or deleted system files. I've never worried about system updates as I've always rooted and run custom ROMs, or Xposed (which negates eligibility for OTA).
mn1968 said:
Unlocking any
As far as not being able to receive OTA updates, I have no knowledge. In my opinion it shouldn't matter that the bootloader has been unlocked...only if you've modified or deleted system files. I've never worried about system updates as I've always rooted and run custom ROMs, or Xposed (which negates eligibility for OTA).
Click to expand...
Click to collapse
Thanks for clarifying. And yes, learnt from Moto Support that OTA was disabled for 7 generation
CoffeeMachineSwitch said:
Thanks for clarifying. And yes, learnt from Moto Support that OTA was disabled for 7 generation
Click to expand...
Click to collapse
That would be an unfortunate change if true. Prior devices could be unlocked and still get OTA updates. They won't install if certain changes are made but still get notified of updates.
You still can install full ROM using fastboot commands and regain root by patching boot.img from updated ROM
I did it on both G6 and G7
Where did you get the ROM images from. I understand there are no officials?
CoffeeMachineSwitch said:
Where did you get the ROM images from. I understand there are no officials?
Click to expand...
Click to collapse
Have you tried the LMSA tool? It's a tool you download from Motorola. There is a discussion here about it. It has a rescue button with which, I understand that you can download stock images directly from Motorola, but I haven't used it myself.
umbrisle said:
Have you tried the LMSA tool? ....
Click to expand...
Click to collapse
Yes I have - the last time I tried, however, it said that it would not support the G7 (Play) and did not provide any images/ROMs
CoffeeMachineSwitch said:
Yes I have - the last time I tried, however, it said that it would not support the G7 (Play) and did not provide any images/ROMs
Click to expand...
Click to collapse
I was thinking of buying a G7 Play myself, but I am now leaning more towards a G6 Play, because there are more tools available like a working TWRP.
Should've read the thread here before i go buy g7 play, not my phone get softbricked.
Unblocked bootloader successfully following the official doc but failed to install magisk by copying the wrong build number of boot.img of OTA from here mirrors.lolinet.com/firmware/moto
now my g7 says
Code:
failed to load kernel, no Bootable A/B slot,
Failed to book Linux
falling back to fastboot.
I downloaded `RIVER_RETAIL_9.0_PPO29.80-61_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC` which i think this is the right build number when i see error like
Code:
river/retail corrupted
(can't remember exactly, but it's RETAIL not RETUS)
and make my own version of fastboot command stemming from servicefile.xml, still with unlucky.
there is no recovery.img and google has limited resource to make g7 play back to stock orm, i'd like to see if community has any idea or i have to give it to moto to fix it.
========================update=================================
update: i finally get the correct stock ORM which is exactly matching my build number "XT1952-4_CHANNEL_AMZ_9.0_PPY29.105-36_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC" i was an idiot thinking that mismatch one letter or two will be find, but turns out this is very strict, "second time rooting in my life".
not i has flash all of the original orm into my phone then fastboot reboot works, it give me the original error like
Android Recovery
motorola/channel_retail/channel9/PPY29.105-36/d7abeuser/release-keys
Use volum up/down and power
can't load Android system. Your data may be corrupt.
If you continue to get this message, you may need to perform a factory data
reset and erase all user data stored on this device
=====
Try again
Factory data reset
Click to expand...
Click to collapse
now i need to figure out what to do next
===============update=========
lol, turns out just press Factory data reset will bring the brick back to life!!!!!
just want to post my process for anyone having my issue.
the key point to find the correct build number
umbrisle said:
I was thinking of buying a G7 Play myself, but I am now leaning more towards a G6 Play, because there are more tools available like a working TWRP.
Click to expand...
Click to collapse
.
The G6 Play is really slow, at least the Boost one. I was kind of sorry I bought one to put on Sprint's free unlimited plan. At least Sprint unlocked it for me after 60 days.
Give the G7Play some time, it just came out.
As for you guys complaining of no updates once unlocked, it's not the only phone to require flashing the stock boot.img and relocking to get OTAs.
gedster314 said:
.
As for you guys complaining of no updates once unlocked, it's not the only phone to require flashing the stock boot.img and relocking to get OTAs.
Click to expand...
Click to collapse
Yeah, but there is inconsistency in Motorolas communication, they actively offer the option to unlock the bootloader (with T&C and all) incl. a link to a rollback feature. Which then does not work. So in a scenario where a developer buys the device because it actively offers this features, they dont get what they paid for. Mind you, we are not discussing hacking a device here or jailbraking - we are discussing features that Motorola actively promotes with a dedicated webpage.
wallace_mu said:
was an idiot thinking that mismatch one letter or two will be find, but turns out this is very strict
Click to expand...
Click to collapse
You completely missed the wrong code name "river" in RIVER_RETAIL_9.0_PPO29.80-61_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC it is for another device, while "channel" is the right one
Where did you get the correct Rom from? Thanks
I don't own Moto G7 Play and can not confirm, however this one worked for wallace_mu
wallace_mu said:
XT1952-4_CHANNEL_AMZ_9.0_PPY29.105-36_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC
Click to expand...
Click to collapse
I could successfully lock / unlock / lock the bootloader...
Unlock: fastboot oem unlock [CODE FROM MOTOROLA]
Lock it down:
* first I have to reflash the 'boot.img' from the correct firmware file - fastboot flash boot boot.img
* then I can lock the bootloader clean again with 'fastboot oem lock'. "bad key" is gone, SafetyNet test passed and OTA is working again.
Unlocking / locking again works by the way also. Maybe this will help?
realsine said:
I could successfully lock / unlock / lock the bootloader...
Unlock: fastboot oem unlock [CODE FROM MOTOROLA]
Lock it down:
* first I have to reflash the 'boot.img' from the correct firmware file - fastboot flash boot boot.img
* then I can lock the bootloader clean again with 'fastboot oem lock'. "bad key" is gone, SafetyNet test passed and OTA is working again.
Unlocking / locking again works by the way also. Maybe this will help?
Click to expand...
Click to collapse
yes it does! was waiting for this. 2 quick questions:
- will lock/unlock require factory reset / data loss?
- where to get the (official?) boot.img from (am always careful to flash img from the wild)
thanks!
CoffeeMachineSwitch said:
yes it does! was waiting for this. 2 quick questions:
- will lock/unlock require factory reset / data loss?
- where to get the (official?) boot.img from (am always careful to flash img from the wild)
thanks!
Click to expand...
Click to collapse
Hello,
I'm glad to read that I could help.
I have "my" image of 'https :// mirrors.lolinet.com/firmware/moto/channel/official/RETEU/'. There are also some others - just have a look. And please remove the spaces around '://'. I'm currently not allowed to post (external) links, so this way.
* Every 'LOCK' deletes all data and the system is "clean" again.
* The same applies (unfortunately) to EVERY 'UNLOCK'.
I don't care at the moment because I haven't set up my smartphone yet. But it's not nice.
Best regards
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.
Since the inception of Android getting stuck in a bootloop after updating is a common problem. The Red Magic 6 Pro is no exception. For the purposes of this guide I'm referring to the global, or as known in the USA, the US version of the Red Magic 6 Pro. After receiving my device directly from Red Magic's website, I of course wanted to toy with it and see what I could and couldn't do with it. I downloaded the official global Rom from Red Magic's website for future possible fixes if anything went wrong unlocking the bootloader and rooting. I unlocked my bootloader and rooted via patching stock boot with Magisk as outlined in @chocolote4444 thread. After screwing around with Magisk modules and doing all I wanted to do, I decided to unroot and relock the bootloader. This is where the fun began.
After unrooting and relocking the bootloader, I placed the full update zip in root directory of internal storage and ran the local update. It wasn't necessary, but just to make myself feel better i did it anyway. After the update was complete and I rebooted it was stuck in boot animation bootloop. Factory resetting via recovery did nothing to alleviate the bootloop. Here's what I did to fix the bootloop:
1: Hold down power and volume down to reboot in to fastboot.
2:
Code:
fastboot getvar all
This will tell you what your current active slot is. Just look through the lines returned and you'll see it.
3: Once you see what your active slot is you're going to change the active slot to the opposite slot. If you're slot a you're going to change it to b and vice versa.
4: In order to change active slots you have to be bootloader unlocked if you aren't already. I won't detail here how to unlock because if you don't already know how to do it you shouldn't be doing this anyway.
5:Now to set your active slot,
Code:
fastboot --set-active=a
if you're on slot b or
Code:
fastboot --set-active=b
if you're on a.
6: At this point you can reboot. If all goes well you should reboot and the bootloop is gone. After rebooting and assuming everything has been done correctly, you should boot into system. After rebooting and you boot into system, you can reboot again into fastboot and relock the bootloader if you so wish.
The reason you're getting stuck in bootloop after update is it's not switching slots correctly after update. This is purely speculation on my part but it seems to fit. Thats it! You should now be up and running. I hope this helps someone whos stuck and as aggravated as I was.
Dang thank you for the guide, but rippers to people who still have their bootloader locked
CyberWolf92 said:
Dang thank you for the guide, but rippers to people who still have their bootloader locked
Click to expand...
Click to collapse
it makes me cry that we cant get solution for this locked bootloader
Fastboot flashing unlock worked for me with no adverse consequences. Not sure why it wouldn't work for everyone else. I've unlocked and relocked a couple times with zero ill effects
bob24260 said:
Fastboot flashing unlock worked for me with no adverse consequences. Not sure why it wouldn't work for everyone else. I've unlocked and relocked a couple times with zero ill effects
Click to expand...
Click to collapse
it just that ours oem unlock option didn't checked when the phone still alive, the update brick it then tadaaaa......
I see what you’re saying now. On my version, the US model, OEM unlock is enabled by default. Mine came turned on by default which surprised me.
Nocturne Seigneur said:
it just that ours oem unlock option didn't checked when the phone still alive, the update brick it then tadaaaa......
Click to expand...
Click to collapse
bob24260 said:
I see what you’re saying now. On my version, the US model, OEM unlock is enabled by default. Mine came turned on by default which surprised me.
Click to expand...
Click to collapse
Not my US variant, I told myself I wasn't gonna mess this phone up yet coz I had just gotten it so I didn't even toggled dev settings, guess that's my bad.
My BL is locked tighter than Fort Knox, when using fastboot flashing unlock, it returns:
FAILED (remote: 'Flashing Unlock is not allowed
')
CyberWolf92 said:
Not my US variant, I told myself I wasn't gonna mess this phone up yet coz I had just gotten it so I didn't even toggled dev settings, guess that's my bad.
My BL is locked tighter than Fort Knox, when using fastboot flashing unlock, it returns:
FAILED (remote: 'Flashing Unlock is not allowed
')
Click to expand...
Click to collapse
Do you have the 6 or 6 Pro?
bob24260 said:
Do you have the 6 or 6 Pro?
Click to expand...
Click to collapse
It's the 6 Pro
CyberWolf92 said:
It's the 6 Pro
Click to expand...
Click to collapse
Mines the 6 Pro as well. Screenshot your about section in settings and we can compare. Make sure you block out any personal information. I don’t understand why yours is different.
CyberWolf92 said:
It's the 6 Pro
Click to expand...
Click to collapse
Sorry I feel like an idiot. Yours is soft bricked?
bob24260 said:
Sorry I feel like an idiot. Yours is soft bricked?
Click to expand...
Click to collapse
Yes lmfao I was just gonna reply that its a brick. But yeah if it was unlocked I would be back up n running by now
CyberWolf92 said:
Yes lmfao I was just gonna reply that its a brick. But yeah if it was unlocked I would be back up n running by now
Click to expand...
Click to collapse
Their recovery is totally different. Most stock recoveries have a way to flash stock zips. Just for sh*ts and giggles have you tried adb sideload? Probably won’t work with locked bootloader but you never know. Try it in stock recovery.
The recovery is strange on these models, only gives you a wipe, reboot and power off option but unfortunately there isn't any adb access that I'm aware of, only thing that can be used for sideloading is fastboot or EDL and with a locked bootloader, that just leaves EDL
CyberWolf92 said:
The recovery is strange on these models, only gives you a wipe, reboot and power off option but unfortunately there isn't any adb access that I'm aware of, only thing that can be used for sideloading is fastboot or EDL and with a locked bootloader, that just leaves EDL
Click to expand...
Click to collapse
I know the option isn’t present as far as what’s listed in the recovery options but it never hurts to try anyways. It’s weird because even after wiping data I was still able to unlock bootloader. For some odd reason my oem unlock was enabled without me have ever touching it.
bob24260 said:
I know the option isn’t present as far as what’s listed in the recovery options but it never hurts to try anyways. It’s weird because even after wiping data I was still able to unlock bootloader. For some odd reason my oem unlock was enabled without me have ever touching it.
Click to expand...
Click to collapse
I had already tried it a couple days ago lol, adb doesn't exist in this world of Nubia. The OEM Unlock option in dev settings typically survives simple factory resets which is all this wipe option in recovery does.
CyberWolf92 said:
I had already tried it a couple days ago lol, adb doesn't exist in this world of Nubia. The OEM Unlock option in dev settings typically survives simple factory resets which is all this wipe option in recovery does.
Click to expand...
Click to collapse
That’s strange because every Android device I’ve ever owned would set the oem toggle back to off if you even looked at the reset button lol. As sad as it is to say, I’m already bored with mine and am probably going to either trade it off or sell it. I want to try that Lenovo Legion Duel 2 or whatever it’s called. I also want the Xiaomi Mi 11 Ultra. I’ve had several Xiaomi phones and they’ve all been excellent. Normally I’ll look at what’s currently hot in China and give that a try. If a phone is selling well in the land of electronics aka China then it’s probably a fairly decent device.
bob24260 said:
That’s strange because every Android device I’ve ever owned would set the oem toggle back to off if you even looked at the reset button lol. As sad as it is to say, I’m already bored with mine and am probably going to either trade it off or sell it. I want to try that Lenovo Legion Duel 2 or whatever it’s called. I also want the Xiaomi Mi 11 Ultra. I’ve had several Xiaomi phones and they’ve all been excellent. Normally I’ll look at what’s currently hot in China and give that a try. If a phone is selling well in the land of electronics aka China then it’s probably a fairly decent device.
Click to expand...
Click to collapse
I see lol my experiences are mainly from Samsung/LG lmao so I thought it would be the same case since dev settings are pretty much mirrored across devices with a few regional/hardware exceptions. I haven't had a chance to get bored with mine yet, had to crawl back to one of my back up phones in the meantime xD But the Dual 2 does look really cool but at a $1.2k price tag and then with how picky Verizon is in what they support, it's a tough one. Never had an Xiaomi before but that's a good rule of thumb though that if it sells well over there, it's decent.
Edit: Mod please remove.
CyberWolf92 said:
I see lol my experiences are mainly from Samsung/LG lmao so I thought it would be the same case since dev settings are pretty much mirrored across devices with a few regional/hardware exceptions. I haven't had a chance to get bored with mine yet, had to crawl back to one of my back up phones in the meantime xD But the Dual 2 does look really cool but at a $1.2k price tag and then with how picky Verizon is in what they support, it's a tough one. Never had an Xiaomi before but that's a good rule of thumb though that if it sells well over there, it's decent.
Click to expand...
Click to collapse
Verizon can be a huge pia. I used them for quite a few years but got tired of 400-500$ bills. I highly recommend Xiaomi. I've had several of their devices and for the money you can't beat them. A good entry level device of theirs is the Mi 10T. On paper they look sort of meh but having had one I can attest to their overall decency.
Hey all,
My phone has an issue where it's stuck on target IN, but I discovered with the help of retryfail that the target ID is in the param.bin partition. Does anyone have a param.bin they can dump from their phone using EDL or something? This would help me get back to stock.
Thank you,
razercortex
razercortex said:
Hey all,
My phone has an issue where it's stuck on target IN, but I discovered with the help of retryfail that the target ID is in the param.bin partition. Does anyone have a param.bin they can dump from their phone using EDL or something? This would help me get back to stock.
Thank you,
razercortex
Click to expand...
Click to collapse
I'd like the as well if anyone has it for LE2127 TMO c.22 firmware. But if you use a modded msm tool to accommodate the IN TargetID wouldn't the param img get written over and get you back to stock?
If I borrow my wife's phone long enough, I can get it. She has the same LE2127 9 Pro....
Here you go....
if it works, let me know and include the steps you took....please!
Hi all,
In order to use the file, unlock bootloader, then reboot to fastbootd. From fastbootd, run "fastboot flash param param.bin". You will be able to run stock TMO MSM after this. It doesn't really matter what FW version you are on, you can flash it anyway as long as it's a TMO device.
razercortex said:
Hi all,
In order to use the file, unlock bootloader, then reboot to fastbootd. From fastbootd, run "fastboot flash param param.bin". You will be able to run stock TMO MSM after this. It doesn't really matter what FW version you are on, you can flash it anyway as long as it's a TMO device.
Click to expand...
Click to collapse
You successfully got rid of Target is IN with this? How do you check it?
Yaaaaaaa....!!!!!!
TheGhost1951 said:
if it works, let me know and include the steps you took....please!
Click to expand...
Click to collapse
You'll need to generate new unlock token after you flash this, otherwise you won't be able to unlock bootloader.
TheGhost1951 said:
You successfully got rid of Target is IN with this? How do you check it?
Click to expand...
Click to collapse
Try to flash regular TMO MSM.
TheGhost1951 said:
Yaaaaaaa....!!!!!!
Click to expand...
Click to collapse
I'm so happy for you bro!!
TheGhost1951 said:
Yaaaaaaa....!!!!!!
Click to expand...
Click to collapse
Also, while you're at it, is it possible for you to retrieve persist.img as well? I think mine broke, not allowing for use of FP sensor.
Oh my god. I've been dealing with this stupid indian thing for months, I gave up on trying anymore. No matter what I did , I could never get a normal UNMODDED TMobile msm to run for me.
But I got it now.
Followed the steps above. Unlocked bootloader, went into fastbootd and flashed the param.bin from above, and immediately after that I shut the phone off right from fastbootd mode. Started my TMobile msm tool , plugged it in and we are good!
I'm shocked at how easy of a solution this was, I was trying so many other long drawn out trial and errors and it was truly this easy
razercortex said:
Also, while you're at it, is it possible for you to retrieve persist.img as well? I think mine broke, not allowing for use of FP sensor.
Click to expand...
Click to collapse
hold on...
razercortex said:
Also, while you're at it, is it possible for you to retrieve persist.img as well? I think mine broke, not allowing for use of FP sensor.
Click to expand...
Click to collapse
razercortex said:
Also, while you're at it, is it possible for you to retrieve persist.img as well? I think mine broke, not allowing for use of FP sensor.
Click to expand...
Click to collapse
I encourage you to make a new How-To thread in this forum with instructions on how to fix the target IN problem. There are a quite a few people who are stuck on IN after using the Indian MSM tool. I saw it being asked a bit in the OnePlus telegram group a few months back too. Good work.
It's one more thing off the list for us to have complete control of our device. Since we have the last "real" OnePlus phone with msm tool, the development on this device may go on for a long, long time
Sorry guys, I pulled my param.bin file because deep inside some settings my wife's name was on my phone. I used her param.bin because it was pure TMO... Personal reasons and security reasons as well... hope y'all understand. and as it is I have now gone with flashing my phone to global...... i actually like it better. Got away from a branded phone!
Appreciative said:
I encourage you to make a new How-To thread in this forum with instructions on how to fix the target IN problem. There are a quite a few people who are stuck on IN after using the Indian MSM tool. I saw it being asked a bit in the OnePlus telegram group a few months back too. Good work.
It's one more thing off the list for us to have complete control of our device. Since we have the last "real" OnePlus phone with msm tool, the development on this device may go on for a long, long time
Click to expand...
Click to collapse
I'm going to refrain from doing so because it can potentially cause side effects, but if anyone wants to do so, by all means.
TheGhost1951 said:
Sorry guys, I pulled my param.bin file because deep inside some settings my wife's name was on my phone. I used her param.bin because it was pure TMO... Personal reasons and security reasons as well... hope y'all understand. and as it is I have now gone with flashing my phone to global...... i actually like it better. Got away from a branded phone!
Click to expand...
Click to collapse
At least we know it's possible now. Do you think we need a pure virgin new in box param or do you think there are specifics to the device and that's why he ( @razercortex ) needed persist also? (I was under the impression that persist was device specific)
I also understand your reservations @razercortex, I suppose we can point people here when it comes up, they can read the thread and understand the risks. I'm not stuck on IN but I knew it was possible to undo something the msm package did and I'm glad to see @TheGhost1951 was finally able to undo it. I knew he felt the same way about undoing whatever was done by the IN msm. Maybe someone can piece together a custom repair msm using a virgin param...but maybe I'm getting ahead of myself