Develop Bugs

It’s now easy to bypass MediaTek’s SP Flash Tool authentication

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.

General Warning about the MSM tool

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.

Question Oneplus 9 Pro T-MO (LE-2127) Revert to stock and fix modem. Will donate.

I flashed my device using the Indian MSM Tool and I am unable to revert back the stock T-Mobile flash using the T-Mo MSM Tool. Now my mobile radio will not enable. I tried flashing multiple T-Mobile modems that are posted on here and that did not fix the issue. So let me summerize.
Can someone guide me to 1) Flashing back to the T-Mobile stock firmware from the IN version, and or 2) Help me get my radios working again. I'd be willing to donate to whoever can help me resolve this issue!
Thanks!

Thanks, unfortunately it didn't work for me. My IMEI, MAC Addresses, and fingerprint functionality is still working. Now it's not recognizing my SIM card at all.
@FizzyAps @craznazn Do yall have any suggestions? Seems yall are the all stars here!

ripclap said:
Thanks, unfortunately it didn't work for me. My IMEI, MAC Addresses, and fingerprint functionality is still working. Now it's not recognizing my SIM card at all.
@FizzyAps @craznazn Do yall have any suggestions? Seems yall are the all stars here!
Click to expand...
Click to collapse
India MSM is known to screw things up and make devices think they are LE2120 instead of whatever it originally was, but at the same time, that's what makes it able to also flash ColorOS over to Oxygen easily...
I remember people solving something like issue on this forum, might need to search extensively.... I haven't had my OP9P for over 6 months now probably, so I can't help much... best of luck!

bencozzy said:
Is it possible to pop a different sim in to see if it recognizes it? Could be the sim.
Click to expand...
Click to collapse
I tried 2 others but no luck.

craznazn said:
India MSM is known to screw things up and make devices think they are LE2120 instead of whatever it originally was, but at the same time, that's what makes it able to also flash ColorOS over to Oxygen easily...
I remember people solving something like issue on this forum, might need to search extensively.... I haven't had my OP9P for over 6 months now probably, so I can't help much... best of luck!
Click to expand...
Click to collapse

[]

I really hate to say this. But I don't think there's no coming back from India os. I did the same thing not once but twice. I called T-Mobile and used my insurance. Only way. Read the topic in this forum bout the India msm tool. Idk if u noticed how much different the India os is from the eu and global os. But if there's away I wanna know also. Cause now the only msm tool your going to be able to use is the India one. But you can update to the a12 one of the color or oxygen I can't remember but ur modem will come on everything will be fine for a few days then it will start messing up again.

ripclap said:
I flashed my device using the Indian MSM Tool and I am unable to revert back the stock T-Mobile flash using the T-Mo MSM Tool. Now my mobile radio will not enable. I tried flashing multiple T-Mobile modems that are posted on here and that did not fix the issue. So let me summerize.
Can someone guide me to 1) Flashing back to the T-Mobile stock firmware from the IN version, and or 2) Help me get my radios working again. I'd be willing to donate to whoever can help me resolve this issue!
Thanks!
Click to expand...
Click to collapse
have you read this thread yet?
[TMO] 9 PRO MODEM RETENTION/DATA FIX
----- With the release of OOS13, the modem issue no longer exist. Thank you all for the support & help with this unfortunate issue, we had to endure.... ----- EXPLICITLY FOR TMOBILE 9 PRO (I'm not responsible for your failure to read or...
forum.xda-developers.com

amaroney55 said:
I really hate to say this. But I don't think there's no coming back from India os. I did the same thing not once but twice. I called T-Mobile and used my insurance. Only way. Read the topic in this forum bout the India msm tool. Idk if u noticed how much different the India os is from the eu and global os. But if there's away I wanna know also. Cause now the only msm tool your going to be able to use is the India one. But you can update to the a12 one of the color or oxygen I can't remember but ur modem will come on everything will be fine for a few days then it will start messing up again.
Click to expand...
Click to collapse
I think you're right. I'm going to RMA it with Oneplus.

I thought with my persist, modest1, and modemst2 I could SMT flash it and restore those files but I get a OnePlus write protection using edl and the OEM Unlocking option will not enable in the OS now. Hopefully they warranty repair it. That's my only concern. It's fairly new lol

Sorry I am just going on what that one thread was saying. And my experience I had to make TMobile believe that it was the phone breaking. Be sure to switch it back to the TMobile os. If the msmtool doesn't work fastboot flash it back before u take it back. The 2nd time they went through my phone saw I had the xda app they really started questioning me. I grabbed my phone back and said umm why u looking in my phone privacy dude. You're concern is only with network and data not my apps files and folders. But just save ya some trouble

amaroney55 said:
Sorry I am just going on what that one thread was saying. And my experience I had to make TMobile believe that it was the phone breaking. Be sure to switch it back to the TMobile os. If the msmtool doesn't work fastboot flash it back before u take it back. The 2nd time they went through my phone saw I had the xda app they really started questioning me. I grabbed my phone back and said umm why u looking in my phone privacy dude. You're concern is only with network and data not my apps files and folders. But just save ya some trouble
Click to expand...
Click to collapse
I'll just flash it clean to where it doesn't even boot lol

Maybe its a bit off topic... but what do we learn about it? NEVER buy a carrier branded device if you want play with root. The lower price is not worth. I learned that over 10yrs ago xD

RheinPirat said:
Maybe its a bit off topic... but what do we learn about it? NEVER buy a carrier branded device if you want play with root. The lower price is not worth. I learned that over 10yrs ago xD
Click to expand...
Click to collapse
Yea I learned my lesson

What sucks is I have the modemst1, modemst2, and persist image backups but I cannot unlock it to upload. I am trying to modify the MSM Tool settings.xml to patch the modemst and persist images and I almost had success using the SMT Downloader but I think I don't have the offset bytes set properly to match the partition table.

Try this, worked for me from In back to TMO....
File on MEGA
mega.nz

TheGhost1951 said:
Try this, worked for me from In back to TMO....
File on MEGA
mega.nz
Click to expand...
Click to collapse
Internet explorer user spotted. xD

ekin_strops said:
Internet explorer user spotted. xD
Click to expand...
Click to collapse
Beg your pardon, I used the Indian MSM to unbrick before I was aware of it changing my TargetID to IN. Now I have to use a modded MSM tool to flash TMO firmware. I use Python3 to extract the .ops file, then open settings.xml, remove the "Target" line at the bottom encrypt back to a .ops file with the name out.ops and then flash that with the MSM tool. Then it will flash the TMO firmware and you are good to go.......

- op6 user - its destroyed now
but as i see that u cant use any other msm but the indian one? right?
i destroyed my op6 system and partations before,
OnePlus Agency, tried to fix it but no luck, i fixed it by msm but not the normal one
if 9pro msm is the same as op6 so you should do this
first, take twrp backup of EFS and MODEM partations and VENDOR ( idk if vendor is important but for precaution )
take another backup of EFC and MODEM by any root apps for precaution too
use the t-mobile msm flashtool and press on verify
the SMT mode should be able to use now
go to options, turn on the COM box or whatever
start flashing with SMT, but i think its high risk bc idk what error you get by normal flashing
keep in mind that SMT Mode will reFlash all known partations and hidden, hidden like MODEM, EFS, etc
my story with this is long, but funny for me, and big lesson..
thx for allah
@ripclap
edit: forget to tell that u have to restore the EFS backup, u should root t-mobile version or idk if u can restore it with some apps without root i dont remember
with op6 old firmware there is something called nvBackupUI it allow us to backup EFS and Restore it by one file
i know this maybe too old now but it may help
edit2:
some links about backup and restore EFS
1- https://community.oneplus.com/thread?id=278167
2- https://www.getdroidtips.com/how-to-backup-or-restore-qcn-efs-on-qualcomm-devices/
3- https://www.droidthunder.com/how-to-backup-efs-imei-on-android-phones/
ALL of this is for SMT Mode, because it may clear the EFS partation and Root is needed to restore it, idk if there is non root method, do ur own search

Question Root Achieved

I achieved root today on REVVL V+ 5G.
This phone is made by wingtech and is a mediatek phone, so why is this in TCL under forums??
I know this sounds crappy but I cannot share all the details. Don't ask why, its complicated. Updates to follow.

xnandman said:
I achieved root today on REVVL V+ 5G.
This phone is made by wingtech and is a mediatek phone, so why is this in TCL under forums??
I know this sounds crappy but I cannot share all the details. Don't ask why, its complicated. Updates to follow.
Click to expand...
Click to collapse
Can u do mine?

Very interested in this
So I guess we should set some sort of appointment ?
Will keep an eye on this thread !

End result is unlocked bootloader and magisk installed.

xnandman said:
I know this sounds crappy but I cannot share all the details. Don't ask why, its complicated. Updates to follow.
Click to expand...
Click to collapse
If you're unable to share the steps for this method, what purpose does this thread have?

Timmmmaaahh! said:
If you're unable to share the steps for this method, what purpose does this thread have?
Click to expand...
Click to collapse
Unlock bootloader with mtkclient since it is a mediatek phone. The exploit works lovely. Then root with magisk. Here is my patched 11 boot flashboot mode - flashboot flash boot magiskpatched.img <--. Example hope this helps people ---- T-Mobile USA Android 11
P.S. - Tidbits for those in need ┤Mod Edit├┤Link not allowed├

LMAO.
You want to keep it as a secret while using someone else's work?
Guys, just follow the guide here:
GitHub - bkerler/mtkclient: MTK reverse engineering and flash tool
MTK reverse engineering and flash tool. Contribute to bkerler/mtkclient development by creating an account on GitHub.
github.com

I paid $8.00 for a carrier unlock via remote TeamViewer on eBay. I asked if he could unlock the bootloader as well. Everything went well. I used the magisk boot.img posted somewhere on here to flash for root. So far everything working well. I pass safetynet but no luck with GPay.

Any possible way for this to work on the REVVL V 4G?

Anyone plan on doing a rom for this phone?

Aluran said:
Any possible way for this to work on the REVVL V 4G?
Click to expand...
Click to collapse
I am also wondering this about my phone, i have REVVL V (TMRVL4G)

xnandman said:
I achieved root today on REVVL V+ 5G.
This phone is made by wingtech and is a mediatek phone, so why is this in TCL under forums??
I know this sounds crappy but I cannot share all the details. Don't ask why, its complicated. Updates to follow.
Click to expand...
Click to collapse
Could you please help me. I have same phone and need to root it. Thanks

Jmasse22 said:
Could you please help me. I have same phone and need to root it. Thanks
Click to expand...
Click to collapse
Same problem bro...

pincali said:
Unlock bootloader with mtkclient since it is a mediatek phone. The exploit works lovely. Then root with magisk. Here is my patched 11 boot flashboot mode - flashboot flash boot magiskpatched.img <--. Example hope this helps people ---- T-Mobile USA Android 11
P.S. - Tidbits for those in need ┤Mod Edit├┤Link not allowed├
Click to expand...
Click to collapse
Can you help me to unlock the bootloader? Any video that explains it?

jwhinery99 said:
Can u do mine
pincali said:
Unlock bootloader with mtkclient since it is a mediatek phone. The exploit works lovely. Then root with magisk. Here is my patched 11 boot flashboot mode - flashboot flash boot magiskpatched.img <--. Example hope this helps people ---- T-Mobile USA Android 11
P.S. - Tidbits for those in need ┤Mod Edit├┤Link not allowed├
Click to expand...
Click to collapse
I'm going to borrow this for my guide. I'll give you credit. Mine works. So weird, two identical phones, one I patched the zipped img, the other I unpacked the img and patched. One will not work for the other and vice versa and I have no idea why. It seems to be the exact same device. But I've had two people brick and need recovery and maybe this could make it easier. Thanks. Hope you don't mind. Check out my guide: do you know an easier way to flash stock ROM? I haven't yet ported twrp. I returned mine to stock and sold them both today and I'm going to take a break
Click to expand...
Click to collapse

Yo, what happened? I seen a link to the patched img and a mod edit nix your video link. I replied taking about my guide, look again and the link is gone. DM that to me please, if you would be so kind. Do you have TWRP, payload.bin mt6833_scatter.txt, OTA? Anything you could give me would be awesome. If you want to edit my guide, feel free to offer any pointers. I'll edit the guide and give you credit. I don't know if that matters to you, or not. I like the attention, but at the same time I'm a perfectionist. I can't stop trying to make something better. Thanks in advance

R41N MuTT said:
Yo, what happened? I seen a link to the patched img and a mod edit nix your video link. I replied taking about my guide, look again and the link is gone. DM that to me please, if you would be so kind. Do you have TWRP, payload.bin mt6833_scatter.txt, OTA? Anything you could give me would be awesome. If you want to edit my guide, feel free to offer any pointers. I'll edit the guide and give you credit. I don't know if that matters to you, or not. I like the attention, but at the same time I'm a perfectionist. I can't stop trying to make something better. Thanks in advance
Click to expand...
Click to collapse
I have the scatter for 6833 if anyone needs it. File enclosed as well as a few other tools and files I needed to root my revvl 6 5g, you should be able to do the rest on your own. Make sure when you are using mtkclient that you back up your preloader above all things in case you mess up. Your scatter will save your hide as well. I've also enclosed mtkclient bypass tool and the 6833 payload you will need as well. Good luck, and credit to Hovatek, and bkerley for their respective tools. If using sp flash tool use the enclosed scatter and the DA_allinone file for the other.

kaliman_chance said:
I have the scatter for 6833 if anyone needs it. File enclosed as well as a few other tools and files I needed to root my revvl 6 5g, you should be able to do the rest on your own. Make sure when you are using mtkclient that you back up your preloader above all things in case you mess up. Your scatter will save your hide as well. I've also enclosed mtkclient bypass tool and the 6833 payload you will need as well. Good luck, and credit to Hovatek, and bkerley for their respective tools. If using sp flash tool use the enclosed scatter and the DA_allinone file for the other.
Click to expand...
Click to collapse
Hey, I'm trying to complete a guide for the revvl v+ 5g. Other people are reporting issues and we're trying to resolve it. We could use your help over here https://forum.xda-developers.com/t/root-flash-stock.4541841/ thanks in advance. Btw, I have that scatter already. It was weird how I got it, though. I found the source code somewhere, I just copied the text and removed the quotation marks and saved it in notepad. Spflash gave me trouble and I had to tinker with some things and bypass DA. But it worked. I thought it'd work for everybody, but now spflash isn't working for some folks, but then we found the newest version. It's not on the official site :/ but now some folks can't get back to stock even with correct files and firmware. I have at least 3 guys dead in the water. Any help would be appreciated. I know you have a life and all, but if you get the time

R41N MuTT said:
Hey, I'm trying to complete a guide for the revvl v+ 5g. Other people are reporting issues and we're trying to resolve it. We could use your help over here https://forum.xda-developers.com/t/root-flash-stock.4541841/ thanks in advance. Btw, I have that scatter already. It was weird how I got it, though. I found the source code somewhere, I just copied the text and removed the quotation marks and saved it in notepad. Spflash gave me trouble and I had to tinker with some things and bypass DA. But it worked. I thought it'd work for everybody, but now spflash isn't working for some folks, but then we found the newest version. It's not on the official site :/ but now some folks can't get back to stock even with correct files and firmware. I have at least 3 guys dead in the water. Any help would be appreciated. I know you have a life and all, but if you get the time
Click to expand...
Click to collapse
I don't know how much I can help; I'm little more than an amateur with an engineer type of learning capability and a tenacious drive. I suck at teaching, but will take a look at the thread anyway, because on the way to rooting a treble based a/b partition with tamper evident ro.props, plus having bricked my device 9 ways to Sunday, there's some possibility of being able to offer some assistance. See you there man.

kaliman_chance said:
I don't know how much I can help; I'm little more than an amateur with an engineer type of learning capability and a tenacious drive. I suck at teaching, but will take a look at the thread anyway, because on the way to rooting a treble based a/b partition with tamper evident ro.props, plus having bricked my device 9 ways to Sunday, there's some possibility of being able to offer some assistance. See you there man.
Click to expand...
Click to collapse
You're definitely more knowledgeable than I am, it seems. Thanks

Question Anyone bricked/EDL/9008 their ROG 6?

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