Article here
What do you think? Will this finally let us unbrick redmi note 8 pro without mi authorized account?
Did some dev look into this yet?
yes i've tested it it works. i couldnt do anything with it though but it shouldnt be that hard to let us flash cfw and twrp or unlock the bootloader using spflashtool right. this thing is huge i mean granted its not the easiest to do but honestly its not even that hard if you know what you're doing which you should if you're on xda, it took about 10 mins on me
it is possible, we're just waiting for a dev to implement it, right now there isnt much you can do w sp flash tools
wentaas said:
it is possible, we're just waiting for a dev to implement it, right now there isnt much you can do w sp flash tools
Click to expand...
Click to collapse
Why not? The scatter file is sitting there on /images folder in every fastboot rom distribution. Look for MT6785_Android_scatter.txt.
After that, your device should be a blank slate. The rest, is up to you.
Well, I think flashing vanilla rom should be your priority, since everything can be done when your device is up-and-running. And extra cautious of course.
kekesed97 said:
Why not? The scatter file is sitting there on /images folder in every fastboot rom distribution. Look for MT6785_Android_scatter.txt.
After that, your device should be a blank slate. The rest, is up to you.
Click to expand...
Click to collapse
wdym by blank state? and is that safe to do?
wentaas said:
wdym by blank state? and is that safe to do?
Click to expand...
Click to collapse
Not a blank state, a blank slate. You know, a blank board which you can write or draw anything you like? But that's not important right now.
Theoritically it should safe. It's like removing a boulder that blocking your way.
If you have access to SPFT, theoritically you should be able to flash your vanilla ROM, given the security measures are null (or rather, bypassed). If your device is chinese based you should flash chinese ROM there. Do a wipe and lock procedure. Let the bootloader locked for now, since you can unlock it later. Do not do crossflash there, without bootloader unlock (this should be a common sense).
But theory is a theory. I can't test it since my device is up-and-running.
My knowledge may be obsolete, since the last device I flashed was MT6572 back on its glory days, no security measures and bootloader was unlocked back then. You can't flash only and only if your eMMC is damaged, which is the worst case (oppo phones was prone to eMMC failure back then, and that happened to me). But afaik the flash process isn't changed that much, just an additional security measure was added, so I think my knowledge still apply.
Additional note: try to flash without nvram and nvdata to avoid losing IMEI (someone from Redmi Note 9 forum lose his IMEI).
kekesed97 said:
Not a blank state, a blank slate. You know, a blank board which you can write or draw anything you like? But that's not important right now.
Theoritically it should safe. It's like removing a boulder that blocking your way.
If you have access to SPFT, theoritically you should be able to flash your vanilla ROM, given the security measures are null (or rather, bypassed). If your device is chinese based you should flash chinese ROM there. Do a wipe and lock procedure. Let the bootloader locked for now, since you can unlock it later. Do not do crossflash there, without bootloader unlock (this should be a common sense).
But theory is a theory. I can't test it since my device is up-and-running.
My knowledge may be obsolete, since the last device I flashed was MT6572 back on its glory days, no security measures and bootloader was unlocked back then. You can't flash only and only if your eMMC is damaged, which is the worst case (oppo phones was prone to eMMC failure back then, and that happened to me). But afaik the flash process isn't changed that much, just an additional security measure was added, so I think my knowledge still apply.
Additional note: try to flash without nvram and nvdata to avoid losing IMEI (someone from Redmi Note 9 forum lose his IMEI).
Click to expand...
Click to collapse
ooh thanks for the explanation, to be clear, my phone is working fine right now but i hate miui. so my intention was to unlock the bootloader if possible, or install cfw and twrp if its not, or if thats not possible either, just installing a custom rom (probably aosp a11)
wentaas said:
ooh thanks for the explanation, to be clear, my phone is working fine right now but i hate miui. so my intention was to unlock the bootloader if possible, or install cfw and twrp if its not, or if thats not possible either, just installing a custom rom (probably aosp a11)
Click to expand...
Click to collapse
Well, for unlocking bootloader there's no other method than the official one. But in some cases the waiting time could be forever (well, many failed attempts would lead to loong waiting time, practically doesn't worth the wait).
My device was resurrected (around May 20, when everyone make a fuss about the lockout). And it can do UBL and root just fine, and tripped AVB many times. It's pretty safe to say tripping AVB on device with unlocked bootloader is recoverable. Just do fastboot flash via MiFlash Pro, and you are set! But never do "Flash and Lock" operation. It would lead to the lockout. You would regret it.
kekesed97 said:
You can't flash only and only if your eMMC is damaged, which is the worst case (oppo phones was prone to eMMC failure back then, and that happened to me)
Click to expand...
Click to collapse
Thanks for sharing your experience. This eMMC failure is because of Oppo or Mediatek? I have a Realme C12.
3 guys 'hard bricked' their devices. No sign of life. Flashing in SP Flash Tools results 'RAM_EXCEPTION (0xC0050005)'. Not able to readback too. It seems like eMMC replacement is only solution.
What are your ideas in this?
Thanks
HemanthJabalpuri said:
Thanks for sharing your experience. This eMMC failure is because of Oppo or Mediatek? I have a Realme C12.
3 guys 'hard bricked' their devices. No sign of life. Flashing in SP Flash Tools results 'RAM_EXCEPTION (0xC0050005)'. Not able to readback too. It seems like eMMC replacement is only solution.
What are your ideas in this?
Thanks
Click to expand...
Click to collapse
Maybe because oppo tried to cut corners since they're using mediatek? I don't see any reason for them to not cut the corner any further. It was 2015, it have a mediocre specs with mediocre quality for their price.
It's been a long ago, I forgotten the error messages. I'm afraid you are facing a worst case scenario.
If you can pull out your eMMC and put that on a jtag reader, there's might be a slight chance of revival.
Related
I bought a phone that was FRP locked (I know, stupid me) and cannot access the serial number in order to emergency flash it with Smart Switch. Can someone please share their serial number with me so I can reflash it? If not, does anyone have any help? I am on G920PVPU3CPF4
Even doing a SmartSwitch (or Odin) flash won't remove the lock. No amount of flashing or resetting will remove it. The lock is stored in a hidden partition that is never touched by flashes and resets.
There are ways to remove the lock, but they're paid services offered by professionals
iBowToAndroid said:
Even doing a SmartSwitch (or Odin) flash won't remove the lock. No amount of flashing or resetting will remove it. The lock is stored in a hidden partition that is never touched by flashes and resets.
There are ways to remove the lock, but they're paid services offered by professionals
Click to expand...
Click to collapse
I have a similar issue, could this be fixed with a Z3X Box?
you could try this method . . .
https://www.youtube.com/watch?v=ggRhkme9FC0
if for any reason didn't work try this one
https://www.youtube.com/watch?v=KRUp09bXnDA
JeffB81 said:
I have a similar issue, could this be fixed with a Z3X Box?
Click to expand...
Click to collapse
Yes it can be, do you have one?
discomaniac said:
Yes it can be, do you have one?
Click to expand...
Click to collapse
No, but I was able to repair my phone with Odin and the CPI3 firmware. Thank you
JeffB81 said:
No, but I was able to repair my phone with Odin and the CPI3 firmware. Thank you
Click to expand...
Click to collapse
You took off FRP lock with software?
JeffB81 said:
No, but I was able to repair my phone with Odin and the CPI3 firmware. Thank you
Click to expand...
Click to collapse
Confirm?
vazersecurity said:
Confirm?
Click to expand...
Click to collapse
I have read elsewhere that flashing the original firmware the phone was factory installed with can fix the frp lock
crazynapkinman said:
I have read elsewhere that flashing the original firmware the phone was factory installed with can fix the frp lock
Click to expand...
Click to collapse
Incorrect. FRP is held in a partition that is not touched during a firmware flash
vazersecurity said:
Confirm?
Click to expand...
Click to collapse
iBowToAndroid said:
Incorrect. FRP is held in a partition that is not touched during a firmware flash
Click to expand...
Click to collapse
Then what about this Cl3? Are there steps after flashing the firmware?
crazynapkinman said:
Then what about this Cl3? Are there steps after flashing the firmware?
Click to expand...
Click to collapse
Flashing firmware can't fix an FRP lock - period.
If you want to know what that poster meant by his message, I suggest you ask him directly
Samsung phones can be frp unlocked by flashing firmware
I have personally FRP unlocked 2 Samsung phones by flashing the stock firmware usin Odin. A samsung j7 and a Samsung s5. I am getting so sick of people saying you can't do something when they have no clue. I have also flashed older versions into phones. That's how I rooted the s5 infact. When everyone was saying it was impossible to root at the time. As soon a I figure out how to use sp flash or something to flash different phones other than Samsung I will post saying how it worked not get on someone else's post and say it will never work it's impossible. The world of computers, phones and software is suppose to be open source not locked, hidden and full of viruses.
Bullshipcaptcha said:
I have personally FRP unlocked 2 Samsung phones by flashing the stock firmware usin Odin. A samsung j7 and a Samsung s5. I am getting so sick of people saying you can't do something when they have no clue. I have also flashed older versions into phones. That's how I rooted the s5 infact. When everyone was saying it was impossible to root at the time. As soon a I figure out how to use sp flash or something to flash different phones other than Samsung I will post saying how it worked not get on someone else's post and say it will never work it's impossible. The world of computers, phones and software is suppose to be open source not locked, hidden and full of viruses.
Click to expand...
Click to collapse
LOL.
The FRP data is stored in the "persistent" partition, which is never touched by a firmware flash, just like EFS and a bunch of other partitions.
So no.
That doesn't matter when the phone no longer has a persistent partition.
iBowToAndroid said:
LOL.
The FRP data is stored in the "persistent" partition, which is never touched by a firmware flash, just like EFS and a bunch of other partitions.
So no.
Click to expand...
Click to collapse
You obviously think you know something and I wont argue or dispute whether you do or dont but I know what I did for sure and what I did was flash stock firmware into those phones and they where no longer FRP locked afterwards. Also When the phone is bricked the phone is flashed blank. There are no patitions if flashed blank. Even when there is persistent data it's still data that is able to be edited with a custom rom which can be flashed after you flash stock rom. I dont know much but I know what I have done personally. My wife is still using her rooted j7 with note 8 D.N.A undetected that we bought f.r.p. locked.
So ya. Just because the internet says it's not possible doesn't mean it's not possible It just means you haven't tried hard enough to prove it yourself. Brick that phone if you have to. Build with that brick.
Bullshipcaptcha said:
You obviously think you know something and I wont argue or dispute whether you do or dont but I know what I did for sure and what I did was flash stock firmware into those phones and they where no longer FRP locked afterwards. Also When the phone is bricked the phone is flashed blank. There are no patitions if flashed blank. Even when there is persistent data it's still data that is able to be edited with a custom rom which can be flashed after you flash stock rom. I dont know much but I know what I have done personally. My wife is still using her rooted j7 with note 8 D.N.A undetected that we bought f.r.p. locked.
So ya. Just because the internet says it's not possible doesn't mean it's not possible It just means you haven't tried hard enough to prove it yourself. Brick that phone if you have to. Build with that brick.
Click to expand...
Click to collapse
I own a business that does FRP removals and many other software-related services for mobile devices . I've done this for years - knowing this type of thing is literally my job.
The "persistent" partition is ALWAYS there - just like system, boot, recovery, and all the others. And I promise you, you can't remove an FRP lock by throwing it in Download mode and flashing some firmware with Odin, just like you can't remove it by booting to recovery mode and doing a factory reset. It's just not that easy.
Your going to need to go against the grain her a moment . Business or no business
iBowToAndroid said:
I own a business that does FRP removals and many other software-related services for mobile devices . I've done this for years - knowing this type of thing is literally my job.
The "persistent" partition is ALWAYS there - just like tem, boot, recovery, and all the others. And I promise you, you can't remove an FRP lock by throwing it in Download mode and flashing some firmware with Odin, just like you can't remove it by booting to recovery mode and doing a factory reset. It's just not that easy.
Click to expand...
Click to collapse
I'm telling you. I'm not debating the facts. Im telling you what I did. Kinda like I did today with a Moto e4 play. I bypassed frp with flashing stock rom through Odin and then custom rom on the Samsung J7. Today I bypassed frp lock with twrp on the Moto e4 with the bootloader still saying OEM locked . I don't have a business in the phones field but I am a business man and sittin on 12 frp locked phones gets tire some. Thant goodness for broken digitizers and displays or I'd still have a bunch more of them. I wont dipute that you know what your doing because likely you do more so than I; we can can probably be certain. I'm just going to tell you the 100 percent fact. Upset wife as my motivating factor I successfully unlocked and rooted a j7 by flashing stock rom into it with Odin then custom reccovery then root then custom rom. The custom recovery I used by accident was for a different brand Jay 7 so mysecond time around I tried the "right" recovery and bricked it. Then again and again and again until Knox was tripped and that's when finally I took bl,ap cp, csc and flashed them in dl mode successfully from there I had Rob from simple cell unlock ( Thanks Rob your the best) remotely unlock the jay7 from T-Mobile after which I flashed the "wrong" proper twrp file giving me the ability to install custom note 8 dna rom into the system. Took two tries, first try I flashed no encrypt no verity but it custom rom frp locked. So second time I made sure I install the developer tools package with OEM unlock switch not able to be turned off then no encrypt no verity. It was a very long process since especially since it was only my second successful full root. Then vallet. Man becomes praised by wife. Man feels empowered man tears apart more phones makes mess, MAN HAPPY! WIFE HAPPY! LOL okay sorry about that part.
---------- Post added at 04:18 PM ---------- Previous post was at 04:06 PM ----------
iBowToAndroid said:
LOL.
The FRP data is stored in the "persistent" partition, which is never touched by a firmware flash, just like EFS and a bunch of other partitions.
So no.
Click to expand...
Click to collapse
None the less each developer has a different approach that being said you frp unlocking phones? I have a Samsung s8 Moto e5 five LGs one zte n835 a couple of alcatels and a few more I couple reassemble real quick If I knew some one who had the abilitby to unlock especially if said amazing developer was teaching El padawan young Como. Yo tango mucho programs, apps and software. Just need the knowledge.
Bullshipcaptcha said:
Today I bypassed frp lock with twrp on the Moto e4 with the bootloader still saying OEM locked
Click to expand...
Click to collapse
Thinking you can flash TWRP on a locked bootloader device shows me exactly what your knowledge level is when it comes to all of this. Future discussion would be futile, and no more responses from me will be had. I do wish you luck with your devices though
How frustrating you are.
Your business need some schooling it sounds like. Your business can't be doing good. Go ahead and Google the Moto e4 unlock method. You will see. You have to try before you say it won't work.
discomaniac said:
I bought a phone that was FRP locked (I know, stupid me) and cannot access the serial number in order to emergency flash it with Smart Switch. Can someone please share their serial number with me so I can reflash it? If not, does anyone have any help? I am on G920PVPU3CPF4
Click to expand...
Click to collapse
I just removed the frp lock on my s6 using a combination firmware (found here-https://firmware.gem-flash.com/index.php?a=downloads&b=folder&id=7410) which completely erased all partions and allowed me to access the settings menu to enable the OEM unlock setting. They are two different firmware there. I used the second one and it worked like a charm. Hope this helps
V 12.0.2.0 QGGMIXM --just got a notification.
Anybody try it out yet?
I'm interested in knowing if the upgrade slows down the phone. Since it is difficult to downgrade, I'm waiting to here from others
No upgrade in the UK yet.
DON'T DO IT
It will slow down your phone and you're stuck with it
jshames said:
DON'T DO IT
It will slow down your phone and you're stuck with it
Click to expand...
Click to collapse
Sometimes a factory reset after a big update is a good idea
blaccqnes said:
Sometimes a factory reset after a big update is a good idea
Click to expand...
Click to collapse
According to at least one post, that didn't help
blaccqnes said:
Sometimes a factory reset after a big update is a good idea
Click to expand...
Click to collapse
I did it cause I always do it after a big one is out, but it doesn't help at all. This firmware looks good, it has several very nice features...but it needs more polishing if you ask me. My phone was the best with Android 9 firmware, after Android 10 update it was also OK but not that nice as before...now it is even worse...
Years ago I had a Sony Experia phone. At some point an major update became available. However, along with the release notes was a explicit warning that the resource use of the update is greater, and that the performance of the phone may degrade. Further it warned that this would be irreversible as reverting was not possible.
I don't know if Sony still does this, but I think all manufacturers should. Even Apple IOS degrades performance after a few upgrade cycles on old devices, which is also irreversible unless an unlock hack is released.
Each person should be informed and be able to decide. Do I want the latest features and security, and willing to sacrifice speed?
pujolsk said:
I did it cause I always do it after a big one is out, but it doesn't help at all. This firmware looks good, it has several very nice features...but it needs more polishing if you ask me. My phone was the best with Android 9 firmware, after Android 10 update it was also OK but not that nice as before...now it is even worse...
Click to expand...
Click to collapse
jshames said:
Years ago I had a Sony Experia phone. At some point an major update became available. However, along with the release notes was a explicit warning that the resource use of the update is greater, and that the performance of the phone may degrade. Further it warned that this would be irreversible as reverting was not possible.
I don't know if Sony still does this, but I think all manufacturers should. Even Apple IOS degrades performance after a few upgrade cycles on old devices, which is also irreversible unless an unlock hack is released.
Each person should be informed and be able to decide. Do I want the latest features and security, and willing to sacrifice speed?
Click to expand...
Click to collapse
Yes, that is the point. In this case speed is not that much compromissed, but it feels ugly..
So you're taking about mainly and aesthetic issue? No lag?
pujolsk said:
Yes, that is the point. In this case speed is not that much compromissed, but it feels ugly..
Click to expand...
Click to collapse
jshames said:
So you're taking about mainly and aesthetic issue? No lag?
Click to expand...
Click to collapse
I dont know how to describe, it is more like stuttering animation. It just doesn't look nice. Icons also make some strange thing if you make them bigger.
This firmware looks like the first major iOS beta, if you ever had iPhone....
Just installed it. It feels okay, as advertized. But I don't have it's main attraction on my device. WHERE IS MY SUPER WALLPAPER????
And about downgrading, you can dirty flash your phone to any version (but don't downgrade your Android version, as some apps may render useless) via MiFlashtool. Use "save user data" option. Anti Rollback is not exist on Begonia. God thanks they didn't **** this phone further.
Edit: I've been using super wallpaper long before tho and applied via quick shortcut maker, but it didn't appear in wallpaper picker as it should be.
kekesed97 said:
Just installed it. It feels okay, as advertized. But I don't have it's main attraction on my device. WHERE IS MY SUPER WALLPAPER????
And about downgrading, you can dirty flash your phone to any version (but don't downgrade your Android version, as some apps may render useless) via MiFlashtool. Use "save user data" option. Anti Rollback is not exist on Begonia. God thanks they didn't **** this phone further.
Edit: I've been using super wallpaper long before tho and applied via quick shortcut maker, but it didn't appear in wallpaper picker as it should be.
Click to expand...
Click to collapse
So you say I can flash back to Android 10 and MIUI 11?
If yes, can you point me to some tutorial?
Thanks
pujolsk said:
So you say I can flash back to Android 10 and MIUI 11?
If yes, can you point me to some tutorial?
Thanks
Click to expand...
Click to collapse
My device have Magisk, EdXposed, and OrangeFox installed.
As flashing by custom recovery may render bootloop, and flashing by fastboot mode via MiFlash Pro reject downgrade, the only solution left is either XiaomiFlash or SP Flashtool. But SP Flashtool is locked to service account, so your only choice is XiaomiFlash.
I've red every flash command on XiaomiFlash, and the "Save user data" option format every partition EXCEPT user data (/data and emulated storage), basically the same operation to be performed when you install any rom via any custom recovery.
Fastboot flash leave the data intact for upgrading, but rejects downgrade. But in XiaomiFlash, as I wrote above, it should work bidirectional.
And don't worry about Anti Rollback. Since I've bootlooped over and over, I've performed countless Downgrade and Upgrade. But do at your own risk tho.
Hope that help.
kekesed97 said:
My device have Magisk, EdXposed, and OrangeFox installed.
As flashing by custom recovery may render bootloop, and flashing by fastboot mode via MiFlash Pro reject downgrade, the only solution left is either XiaomiFlash or SP Flashtool. But SP Flashtool is locked to service account, so your only choice is XiaomiFlash.
I've red every flash command on XiaomiFlash, and the "Save user data" option format every partition EXCEPT user data (/data and emulated storage), basically the same operation to be performed when you install any rom via any custom recovery.
Fastboot flash leave the data intact for upgrading, but rejects downgrade. But in XiaomiFlash, as I wrote above, it should work bidirectional.
And don't worry about Anti Rollback. Since I've bootlooped over and over, I've performed countless Downgrade and Upgrade. But do at your own risk tho.
Hope that help.
Click to expand...
Click to collapse
Thanks, now I know what my only option is.
Just to be clear, before I use XiaomiFlash, I have to unlock my bootloader, right?
pujolsk said:
Thanks, now I know what my only option is.
Just to be clear, before I use XiaomiFlash, I have to unlock my bootloader, right?
Click to expand...
Click to collapse
Of course
kekesed97 said:
Of course
Click to expand...
Click to collapse
Thanks, I will go and check it out...
So it turns out, according to the company website, that this is a "beta global stable release" sent to limited users:
https://c.mi.com/thread-3218614-1-0.html
Which explains why most people haven't gotten it.
The company doesn't give a link to download but if you google it you can find it.
Does anyone know when EU QGGEUXM version comes out?
jshames said:
So it turns out, according to the company website, that this is a "beta global stable release" sent to limited users:
https://c.mi.com/thread-3218614-1-0.html
Which explains why most people haven't gotten it.
The company doesn't give a link to download but if you google it you can find it.
Click to expand...
Click to collapse
That makes sense, as it feels like it is a beta, an early one. I just hope they will fix it and make it feels nicer for everyday use, but knowing Xiaomi and how many devices they make on a daily basis, I am not that sure...
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.
Follow and complain here.
Let ASUS know their bootloader implementation is VERY NOT FRIENDLY to us. I've been modding my Android devices since the Android 2 era and this is the first time I encountered an UNOFFICIALLY UNRECOVERABLE state which is a HORRIBLE experience.
Me? Have played with
Samsung(S5 to S9 and Tab/Odin is a good thing)
XiaomiRedmiPoco(Main device for me today, very modder friendly and robust)
Huawei(Remember when they allow applying for BL unlock?)
Apple(LOL jailbreak from A4 SoC until iPhone X(meantime Samsung S8 looks gorgeous) lost my interest)
And various small brands or exited market big brands(honorable mention Lenovo LePhone C101. My first smart device/Android and received big community support at the good old time)
ASUS. Fix your buggy BL. Fix your policy. Release everything we need to fix OUR DEVICES of OURSELVES. Just ONE step closer to perfect.
Just imagine how stupid is this:
Everytime you want to update you operating system, your UEFI/BIOS firmware might break.
And worse, that you don't have free official resources to fix it?
And can it be worse? Yes! Your Warranty is maybe void because you may unlocked bootloader, now supposedly only ASUS service center have the file to fix it.
Ha now it's interesting. That's the era of ANTITRUST. Even Apple won't do it(Worst case DFU, easily fixable using OFFICIAL iTunes).
WT*?
yeah dude i'm bricked up rn
Paid here, paid there.
Yeah sure.
Exploit people.
Perhaps instead of ranting about asus, you could tell us what you have done exactly to brick your device, and someone might be able to help you ? can you get into fastboot at all?
EDIT: quoted content removed.
Never use this firmware, because it has not been modified, 100% of fingerprints and IMEI will be lost after use. You need to modify the firmware before you can flash it.
mahdibassam said:
Perhaps instead of ranting about asus, you could tell us what you have done exactly to brick your device, and someone might be able to help you ? can you get into fastboot at all?
Click to expand...
Click to collapse
Trying to flash img unpacked from update zip. Which you should NOT do. Because Android 12 dynamic partition.
iMoc said:
Trying to flash img unpacked from update zip. Which you should NOT do. Because Android 12 dynamic partition.
Click to expand...
Click to collapse
Ok, yes you definitely should not do that
So just wondering, you went and grabbed some img files and made the decision to flash them, why is this any fault of asus?
mahdibassam said:
Ok, yes you definitely should not do that
So just wondering, you went and grabbed some img files and made the decision to flash them, why is this any fault of asus?
Click to expand...
Click to collapse
1\ The fastboot code in their bootloader have bugs, any CORRECT command you type can easily break bootloader then stuck you in 9008.
2\ The normal update method failed because THEIR UPDATER did do things wrong.
3\ They refuse to provide official ROM to let yourself fix it. SEND IT TO ME TO FIX IT, AND I MIGHT CHARGE YOU SOME.
....\
N\ You go talk to Apple about it because they are experts about saying YOU USED IT WRONG.
Anyone asked for help gets it for free so far.
All devs on my chat group agree at least fastboot flashable should be available on the official download page.
MOD EDIT: off topic content removed
Did you manage to unbrick your phone?
I managed to semi hard brick my phone. Can get into fastboot but unable to start recovery mode from fast boot and phone doesn't show up from adb devices.
I guess I'll start a new thread but any tips?
insideoft said:
Did you manage to unbrick your phone?
I managed to semi hard brick my phone. Can get into fastboot but unable to start recovery mode from fast boot and phone doesn't show up from adb devices.
I guess I'll start a new thread but any tips?
Click to expand...
Click to collapse
If you can boot into fastboot you can just flash the RAW ROM file available a few days ago. It's not bricked in this case.
Moderator Information
Hello everyone,
I have cleaned the thread from off topic contents and posts. Please focus on problem solving related discussion, not finger pointing or flaming each other. We all come here to solve the issues and learn some new stuffs.
Thanks.
iMoc said:
If you can boot into fastboot you can just flash the RAW ROM file available a few days ago. It's not bricked in this case.
Click to expand...
Click to collapse
Sorry long time ago since I was into this stuff previosly.
That fixed it, thanks for the help!
same here
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?