Develop Bugs

Nexus 5x stuck at google screen [Potentially Hard-bricked]

*** The issue is resolved!!! Thanks to xda, the solution is provided in the link in the comments.***
Couple of days ago I got this OTA notification that Android 7.1 preview is available for update. As my phone is rooted I started the manual update procedure. After the flashing was finished, I restarted the phone and then I saw it was stuck at the Google screen. Just stuck, no response. Seemed unusual to me.
Let me tell you that I have been modding my Nexus 5 for about two years. I am familiar with most of the tweaks that can be done to a Nexus device. Nexus 5 served me amazingly. I bought Nexus 5x 3 months ago.
So, after it was stuck I restarted. Still stuck. I will tell you step by step what I did then:
1. Flashed the OS 7.1 again (I dunno why, the flash.all script doesn't work for me, so I always do that manually) - result is the same.
2. Last October update (NBD90W) was available in the folder so I flashed that - same result.
3. I downloaded the previous one (NRD90S) and flashed that - same result.
4. I locked the phone and unlocked again to erase everything (not sure if that's a good idea), then flashed the OS again - same result.
5. Then I tried LGUP and the tot files to give it the factory version. LGUP detects the phone, started installing. When the installation is finished and the phone restarted - same result.
6. Now that I gave it the factory version the phone got locked!
7. I searched google for hours but couldn't find a way to unlock it as the OS is not booting and I cannot turn USB debugging on!
8. Then I tried the default recovery mode (Android recovery, from the recovery screen Power + volume up) as it doesn't require unlocking the device. Wiped the cache and restarted - same result.
9. My phone is detected by the pc and ADB. So, I wiped everything and tried ADB sideload and get this error E: footer is wrong
10. I tried Nexus root toolkit. It detects the phone in fastboot mode, then restarts it and then it again is stuck on the Google screen.
I am extremely depressed!
I am from Bangladesh and there is no authorized LG servicing center here. So, I can't ask for their help.
All that I did over the past two years was the awesome threads of xdadevelopers. So, a big thumbs up for you guys . :good:
I learnt from the web that phone can be hard bricked if a wrong bootloader is flashed. That's impossible for me as I always remove the factory image extracted files after flashing is done from the ADB>platform-tools folder.
Now, is the phone hard-bricked? If it is, what to do with it? Will replacing the motherboard get my phone back? Any kind of suggestion will be very much appreciated.

Bummer. This sounds a lot like what I just posted here: http://forum.xda-developers.com/nexus-5x/help/req-help-bootloop-7-1-1-beta-ota-enter-t3486957
I really hope someone has an idea how to fix this...

Like DC_Knight said, please try the TOT method given here. Hope it works.
http://forum.xda-developers.com/nexus-5x/help/tutorial-how-unbricked-nexus-5x-16gb-t3481766

what is your model H790 or H791
16 or 32 GB?

DC_Knight said:
Bummer. This sounds a lot like what I just posted here: http://forum.xda-developers.com/nexus-5x/help/req-help-bootloop-7-1-1-beta-ota-enter-t3486957
I really hope someone has an idea how to fix this...
Click to expand...
Click to collapse
Well, I don't get bootloops, my phone is just stuck at the Google screen and I can enter recovery mode (lying Android with red exclamation mark), from there I can enter Android recovery mode, where ADB sideload is available.
harihacker said:
Like DC_Knight said, please try the TOT method given here. Hope it works.
http://forum.xda-developers.com/nexus-5x/help/tutorial-how-unbricked-nexus-5x-16gb-t3481766
Click to expand...
Click to collapse
Like I mentioned in point 5, I did exactly that as mentioned in this link.
Duckscreen said:
what is your model H790 or H791
16 or 32 GB?
Click to expand...
Click to collapse
It's H791, 32 GB.

There is no more reply
I need to know one thing. Will replacing the motherboard fix the phone? Anyone??

jadu45 said:
There is no more reply
I need to know one thing. Will replacing the motherboard fix the phone? Anyone??
Click to expand...
Click to collapse
How about trying to get a replacement if you're still within the 1 year warranty?
Sent from my Nexus 5X using Tapatalk

EeZeEpEe said:
How about trying to get a replacement if you're still within the 1 year warranty?
Sent from my Nexus 5X using Tapatalk
Click to expand...
Click to collapse
"I am from Bangladesh and there is no authorized LG dealer/servicing center here. So, I can't ask for their help."
I'm on my own...

jadu45 said:
"I am from Bangladesh and there is no authorized LG dealer/servicing center here. So, I can't ask for their help."
I'm on my own...
Click to expand...
Click to collapse
Ah my bad. TL;DR on my end.
Sent from my Nexus 5X using Tapatalk

Please say something about replacing the motherboard. It's very very pricey, so I want to be sure -_-

sounds like its hardware problem, contact seller to replace it. if not going to happen, then buy a new phone from a company that does have a dealer in your country to warrant. aside of camera, the specs of other phones at this price range are better

That thought is also roaming around my head, still Nexus is Nexus!

What's the price going for the 5X over there? It's as low as $280 here in the US which is easy better then it's original.
Sent from my Nexus 5X using Tapatalk

Try the tutorial here. It's little bit different from the original thread ,
as @bardhi92 said, THE MAIN DIFFERENCE HERE IS THAT AFTER I FLASHED THE .TOT FILE, I BOOTED MY PHONE INTO BOOTLOADER AND DID AN ADB SIDELOAD OF THIS OTA.ZIP
Well, for my case, eventually I successfully bring my N5X alive. The tricky part is to enter Android System Recovery (hold Power + Volume Up) after flashing TOT.

questionquince said:
Try the tutorial here. It's little bit different from the original thread ,
as @bardhi92 said, THE MAIN DIFFERENCE HERE IS THAT AFTER I FLASHED THE .TOT FILE, I BOOTED MY PHONE INTO BOOTLOADER AND DID AN ADB SIDELOAD OF THIS OTA.ZIP
Well, for my case, eventually I successfully bring my N5X alive. The tricky part is to enter Android System Recovery (hold Power + Volume Up) after flashing TOT.
Click to expand...
Click to collapse
Thanks for this, it looks interesting and I definitely didn't try that. I'm at office right now, I'll let you know after trying this.

harihacker said:
Like DC_Knight said, please try the TOT method given here. Hope it works.
http://forum.xda-developers.com/nexus-5x/help/tutorial-how-unbricked-nexus-5x-16gb-t3481766
Click to expand...
Click to collapse
There was a difference in the method here and I didn't realize that before; as it was written at the bottom. Sorry about that. I'll try this method and let you know. Thanks!

jadu45 said:
There was a difference in the method here and I didn't realize that before; as it was written at the bottom. Sorry about that. I'll try this method and let you know. Thanks!
Click to expand...
Click to collapse
Goodluck, and let us know the result.. :fingers-crossed:

A warranty is a warranty, it doesn't matter what country you're in or where the repair place is. People in Canada send stuff to the USA for warranty issues all the time. I'd get on the phone with LG until I heard what I wanted, but I'm a stubborn old goat lol.

ShishkaBerry said:
A warranty is a warranty, it doesn't matter what country you're in or where the repair place is. People in Canada send stuff to the USA for warranty issues all the time. I'd get on the phone with LG until I heard what I wanted, but I'm a stubborn old goat lol.
Click to expand...
Click to collapse
Well, there is no authorized dealer here; I had to buy it from a local shop. So, there is no warranty!

harihacker said:
Like DC_Knight said, please try the TOT method given here. Hope it works.
http://forum.xda-developers.com/nexus-5x/help/tutorial-how-unbricked-nexus-5x-16gb-t3481766
Click to expand...
Click to collapse
questionquince said:
Try the tutorial here. It's little bit different from the original thread ,
as @bardhi92 said, THE MAIN DIFFERENCE HERE IS THAT AFTER I FLASHED THE .TOT FILE, I BOOTED MY PHONE INTO BOOTLOADER AND DID AN ADB SIDELOAD OF THIS OTA.ZIP
Well, for my case, eventually I successfully bring my N5X alive. The tricky part is to enter Android System Recovery (hold Power + Volume Up) after flashing TOT.
Click to expand...
Click to collapse
Both of you provided me the link. I don't know who you are, but I if I find you you guys are going to have a treat for sure. I literally cried when I got my phone back. Thank you guys. Thanks xda!

[SOLVED] PLEASE HELP - HardBricked my OnePlus 5T

Dear Community,
I just searched the past 2 days for a solution but I've not been lucky
Therefore I'd like to ask for help in this forum and hope there is some additional hint or hack I could try...:
So here's the situation:
OnePlus 5T (8/128) with a non booting or not "useful" OS (see last point what I've tried)
No TWRP or CWM
Stock Recovery present
Bootloader Locked
Allow Bootloader to be unlocked = FALSE
What I've already tried yet:
Flashing TWRP --> Not possible Bootloader Locked
Flashing regarding any other kinds like "update" or "flash all" as provided with TOOL_ALL_IN_ONE
ADB Sideload any available ROMS (Original "full" OP5T / FreedomOS / Omni8) --> ADB stops at 47% in Stock Recovery regardless of size of the ZIP file
Tried different versions of ADB (32 & 64 Bit / older & new / also with the LargeAddressAware approach / and on multiple PC's) --> Always same error (47%)
Stumbled upon the possibility to EmergencyDownload a factory flash due to Qualcomm chipset using the MSM-Download-Tool --> Only OnePlus 5 ROM available (no "T")
Mentioned EDL procedure works and OS is booting BUT neither Touchscreen nor USB OTG (for external mouse support) is working --> So I can't navigate and allow Bootloader to be unlocked again
Unfortunately I'm now stuck and have no more idea how to unbrick my phone again
What would help:
Any source to MSM-Download-Tool packed with a correct ROM for the OnePlus 5T
A Workaround to just flash TWRP via MSM-Download-Tool or Qualcomm's QFIL application in EDL mode
Some "hack" to bypass the locked Bootloader situation
Every appreciated Input you might have that I'm currently not aware of...
So PLEASE let me know of any approach that I could try or if you might have found a link or something else to a solution that might help me out of this disaster...
Many thanks in advance!
Tryouts due to your feedback:
@dreinulldrei - "fastboot boot recovery.img" tried with the original 5T Recovery.img also with blu_spark TWRP --> no luck...
SOLVED SOLUTION:
As the EDL factory flash ROM is currently not (or will never officially be) available public getting in contact with the OnePlus support team is required.
They have such a recovery tool (MSM-Download-Tool) with an appropriate ROM and are able to flash the device during a remote support session conducted via chat.
So by starting a chat on the OnePlus Support page and describing your situation will lead to scheduled time slot where a Level-2 technician will do all required steps remotely.
(All files are password protected and the technician ensures they are deleted at the end of the session so I'm unfortunately not able to provide the sources for DIY purposes...)

Following. I would think there would be some way to flash some sort of signed image via fastboot...

U flashed a 5 os to it, using the msmtool try to extract those files from 5t os, I will do it when I get home and so u can try it, i can't guarantee anything though, would u like me to do that for u

Bradl79 said:
U flashed a 5 os to it, using the msmtool try to extract those files from 5t os, I will do it when I get home and so u can try it, i can't guarantee anything though, would u like me to do that for u
Click to expand...
Click to collapse
Thanks for your input - I'm really not aware of how to generate such *.ops ROM files as this is what the MSM Tool expects...
But if there is a way and you are able to extract and produce a MSM flashable file I would be very happy to try!

I would recommend trying to boot a OP5T recovery, you might have flashed some OP5 rom including OP5 recovery. Just go into fastboot (power on with volume up pressed down), then via cmd:
fastboot boot recovery.img
Since OP does not offer the recovery to be downloaded, it will need to be downloaded from a working device. Lacking the cable right where I am, but I am sure someone else can help out.

crakerjac said:
Following. I would think there would be some way to flash some sort of signed image via fastboot...
Click to expand...
Click to collapse
Thanks for the input - I forgot to mention I also tried the 2 original available OP5T "full" ZIP ROM's (think they should be signed...)
Will add this to the initial Post but I assume also no chance here...

dreinulldrei said:
I would recommend trying to boot a OP5T recovery, you might have flashed some OP5 rom including OP5 recovery. Just go into fastboot (power on with volume up pressed down), then via cmd:
fastboot boot recovery.img
Since OP does not offer the recovery to be downloaded, it will need to be downloaded from a working device. Lacking the cable right where I am, but I am sure someone else can help out.
Click to expand...
Click to collapse
Ohhh good point - I also think there is the "wrong" recovery (from 5) currently on my phone (because also there the touchscreen behaves unexpectedly...)
But unfortunately with your command I get the "Your device is corrupted. It can't be trusted and will not boot" message.
Tried this with the original 5T Recovery.img I managed to obtain and also with the blu_spark TWRP - no luck...

Edit: Ignore, misread previous post.

U may have to make a call to oneplus so they can restore for u

Submit a ticket to One Plus
You are going to have to submit a ticket, they will arrange a time to help you by unbricking the phone remotely.
I just had to do this myself this week, and it got done today.
I do have the 5t unbricking files but I cannot access the archive because it's password protected.

One important this you didn't mention is how this happened.

OnePlus may be able to help with this one, but all root guides explicitly include the phrase "at your own risk."

blackknightavalon said:
OnePlus may be able to help with this one, but all root guides explicitly include the phrase "at your own risk."
Click to expand...
Click to collapse
Bradl79 said:
U may have to make a call to oneplus so they can restore for u
Click to expand...
Click to collapse
WMerkens said:
You are going to have to submit a ticket, they will arrange a time to help you by unbricking the phone remotely.
I just had to do this myself this week, and it got done today.
I do have the 5t unbricking files but I cannot access the archive because it's password protected.
Click to expand...
Click to collapse
Thanks for all your advice - so I will arrange a support chat/ticket as soon as possible and inform about the result in this thread.
Didn't thought that OnePlus Support Team would even care about such bricks (no warranty / own risk / "playing" with root / etc...)
But as indeed they seem to help like @WMerkens experienced I would be very happy to have a working device again

CodeXter said:
Thanks for all your advice - so I will arrange a support chat/ticket as soon as possible and inform about the result in this thread.
Didn't thought that OnePlus Support Team would even care about such bricks (no warranty / own risk / "playing" with root / etc...)
But as indeed they seem to help like @WMerkens experienced I would be very happy to have a working device again
Click to expand...
Click to collapse
don't know why you would think that OP wouldn't help...they have said from day one that unlocking/rooting does not void your warranty. Heck they encourage it. I assume you are the same person on the OP forum w/ this problem. Hopefully after you get this resolved you will have learned to NEVER EVER RELOCK your phone unless you do the whole factory image qualcomm recovery tool bit. and experienced OP folks on this forum know any claims of a "hardbricked" OP phone is ALWAYS not true.

Yeah oneplus used to be good about and does a remote session to restore, this was back in the one plus one days though, but I think they still do it
---------- Post added at 03:25 AM ---------- Previous post was at 02:54 AM ----------
WMerkens said:
You are going to have to submit a ticket, they will arrange a time to help you by unbricking the phone remotely.
I just had to do this myself this week, and it got done today.
I do have the 5t unbricking files but I cannot access the archive because it's password protected.
Click to expand...
Click to collapse
Awwww I wish we could get them, do they use the msmtool too?

How I bricked a 5t
I got the phone and I had installed twrp, that went fine. I was looking at magick systemless rooter when the phone then kicked in with a OTA update, I chose to ignore it the first time. It occurred again a few minutes and in my haste I let it do it's job but it did not complete correctly. I rebooted and the phone complained about corruption to the OS, I got in again but made the dumb mistake of re enabling the OEM lock and because I thought that might be causing the problem. I rebooted again but now I could not boot any more into the OS, it complained I was corrupted and go to google to see what to do.
So I was left with a bricked phone.
I could do bootloader but not recovery and I could not unlock the bootloader.
I could not get in via adb usb debug, So after much research I download the OnePlus 5 unbricking pack and learned a whole lot about qualicom and EDL mode, plus I learned a lot about the QFIL tools and restoring a phone. I did the 5 unbrick but my screen ended up upside down but the touch was right side up, which resulted in a very hard to use phone.
I tried the QFIL method but I was missing a mdb file to be able to talk to the phone.
So I gave up submitted a ticket and after much bad co-ordination on their part got a level 2 tech to debrick the phone remotely.
They do a reverse VPN and connect to your computer, they tell you to have 2 files archive ready in a folder on your desktop (they supply the links). They install the EDL driver and unpack the debrick archive. The archives are password protected, they run the tool and restore the phone
back to factory.
They erase the unpacked archives after they are done.

jerrywmilton said:
don't know why you would think that OP wouldn't help...they have said from day one that unlocking/rooting does not void your warranty. Heck they encourage it. I assume you are the same person on the OP forum w/ this problem. Hopefully after you get this resolved you will have learned to NEVER EVER RELOCK your phone unless you do the whole factory image qualcomm recovery tool bit. and experienced OP folks on this forum know any claims of a "hardbricked" OP phone is ALWAYS not true.
Click to expand...
Click to collapse
Oh yes I've learned my lesson on this :angel: --> Never ever set OEM to be unlocked to NO again
Obviously I do not exactly know what wrong procedure made me stuck in this situation but I just wanted to revert every single step back one by one to see which element brings me back to a valid SafetyNet situation...
I've been with the OnePlus "family" since the OP1 but never needed any direct support from the vendor - so every time there's a first time and so for me now...
Thus I really didn't know OP staff is actively doing remote support for their devices - but thumbs up for that! :good:
(BTW: I'm not the guy from the OP forum)

Bradl79 said:
Yeah oneplus used to be good about and does a remote session to restore, this was back in the one plus one days though, but I think they still do it
---------- Post added at 03:25 AM ---------- Previous post was at 02:54 AM ----------
Awwww I wish we could get them, do they use the msmtool too?
Click to expand...
Click to collapse
Yes basically it's the same archive as the 5 unbrick pack but it's for 5t, OnePlus 5T OxygenOS 4.7.2-171116.zip is the archive and you can look in it and you see the ops file is for dumpling not cheesburger, which is the code name for 5t. I saw the MsmDownloadTool is 4.0.8

Bradl79 said:
Yeah oneplus used to be good about and does a remote session to restore, this was back in the one plus one days though, but I think they still do it
---------- Post added at 03:25 AM ---------- Previous post was at 02:54 AM ----------
Awwww I wish we could get them, do they use the msmtool too?
Click to expand...
Click to collapse
I just had a chat with them before and got mailed a link to the MSMTool incl. ROM for the OP5T (dumpling)
But unfortunatley support files from OnePlus are password protected Nevertheless here the original vendor link:
https://onepluscn-my.sharepoint.com/personal/sheva_liu_oneplus_net/_layouts/15/guestaccess.aspx?docid=0fde9596c72744b4fb9c073ca5d87edbe&authkey=AQPXKRi7pdIzZX-5WH_pwWg&e=1030aa0046da4d1aa9189020027d9c93
So I have to wait for my remote support schedule on Saturday to have the L2 technician entering the password and do the rest.
Would be able to do this myself but OnePlus obviously wants to protect their sources what I have to accept, respect and be patient for...

So, never turn off the OEM Unlocking?

Questions about developpement

Hello there !
I got the RN8Pro, last week and i unlocked it today. I naturally started to look how to root/install TWRP. I found numerous threads with instructions on how to do it but i also found a lot of warnings that it may brick the device, and that if that happens i need a special account to be able to unbrick it. It seems that some methods will work for the Chinese version while bricking others and vice versa. I have the Global ROM version 11.0.3.0(PGGEUXM) and the model of my phone is M1906G7G. Do you think it's safe for me to try flashing TWRP or at least root through ADB ?
I have also searched for custom ROMs and did not find any. The phone is relatively new so i wouldn't mind if i had to wait a bit, but i have also read that people just don't want to develop for it because of the Mediatek chip. Everyone says that development is not possible because there is no source code the the Mediatek chip. But here it says that the sources have been released partially here and the rest here. Is there something that's missing from these repos that makes development impossible ?
I also would like to become more than just a user and learn how to make custom roms. I found this thread that compiles some guides but a lot of them seem a bit outdated and I'm lost. Is that a good starting point or i should i go elsewhere ?
Thanks ^^

TheBolshe said:
Hello there !
I got the RN8Pro, last week and i unlocked it today. I naturally started to look how to root/install TWRP. I found numerous threads with instructions on how to do it but i also found a lot of warnings that it may brick the device, and that if that happens i need a special account to be able to unbrick it. It seems that some methods will work for the Chinese version while bricking others and vice versa. I have the Global ROM version 11.0.3.0(PGGEUXM) and the model of my phone is M1906G7G. Do you think it's safe for me to try flashing TWRP or at least root through ADB ?
I have also searched for custom ROMs and did not find any. The phone is relatively new so i wouldn't mind if i had to wait a bit, but i have also read that people just don't want to develop for it because of the Mediatek chip. Everyone says that development is not possible because there is no source code the the Mediatek chip. But here it says that the sources have been released partially here and the rest here. Is there something that's missing from these repos that makes development impossible ?
I also would like to become more than just a user and learn how to make custom roms. I found this thread that compiles some guides but a lot of them seem a bit outdated and I'm lost. Is that a good starting point or i should i go elsewhere ?
Thanks ^^
Click to expand...
Click to collapse
Can't you look at guides section we need Testers for POSP :crying:

girishjangir7 said:
Can't you look at guides section we need Testers for POSP :crying:
Click to expand...
Click to collapse
I did, but what is said there doesn't apply to me. I don't live near a center and I bought it on AliExpress, so I don't tink that I have a guarantee that I could use.

TheBolshe said:
I did, but what is said there doesn't apply to me. I don't live near a center and I bought it on AliExpress, so I don't tink that I have a guarantee that I could use.
Click to expand...
Click to collapse
No problem then wait for someone to test:laugh:

TheBolshe said:
I did, but what is said there doesn't apply to me. I don't live near a center and I bought it on AliExpress, so I don't tink that I have a guarantee that I could use.
Click to expand...
Click to collapse
I would love to help though. But your post is quite cryptic. More details could be nice like what are the risks, what is need to be done, what to do in case of a problem. Plus, it's my only phone ATM and I am poor ^^

It Is Safe As Well As Not Safe.
I Had Bricked My Redmi Note 8 Pro(8GB) And I Had To Visit Mi Service Centre As I Required Xiaomi Authorised Account Which I Don't Have.
Some Peoples Bricked Their Phone After Flashing TWRP And Some After Flashing Wrong Boot.img
I Flashed TWRP Successfully But When I Rooted My Phone, I Faced Bootloop Problem Then To Solve That Problem I Accidently Flashed Wrong Boot.img File( 10.0.4 Boot File Into 11.0.3) Which Resulted Into Bootloop
But If You Follow All The Steps Carefully Then It Is Absolutely Safe.

Hemant Singh Rajput said:
I Had Bricked My Redmi Note 8 Pro(8GB) And I Had To Visit Mi Service Centre As I Required Xiaomi Authorised Account Which I Don't Have.
Some Peoples Bricked Their Phone After Flashing TWRP And Some After Flashing Wrong Boot.img
I Flashed TWRP Successfully But When I Rooted My Phone, I Faced Bootloop Problem Then To Solve That Problem I Accidently Flashed Wrong Boot.img File( 10.0.4 Boot File Into 11.0.3) Which Resulted Into Bootloop
But If You Follow All The Steps Carefully Then It Is Absolutely Safe.
Click to expand...
Click to collapse
Mine has 6gb ram. Which TWRP img did you use?
When it's in bootloop, all I need to do is hold power up to get to fastboot so I can flash boot.img right?

TheBolshe said:
Mine has 6gb ram. Which TWRP img did you use?
When it's in bootloop, all I need to do is hold power up to get to fastboot so I can flash boot.img right?
Click to expand...
Click to collapse
I Flashed This TWRP Through CMD
https://forum.xda-developers.com/re...overy-unofficial-twrp-recovery-redmi-t4002397
You Need To Press&Hold Power+Vol Down Button To Enter Into Fastboot Mode.
When TWRP Flashed Successfully Through CMD You Have To Immediately Disconnect Your Phone From PC Otherwise Your Phone Will Load Stock Recovery.
---------- Post added at 12:45 PM ---------- Previous post was at 12:42 PM ----------
TheBolshe said:
Mine has 6gb ram. Which TWRP img did you use?
When it's in bootloop, all I need to do is hold power up to get to fastboot so I can flash boot.img right?
Click to expand...
Click to collapse
I Think You Shouldn't Take Risk As Your Phone Has No Warranty

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 Requesting param.bin from someone with working T-Mobile OnePlus 9 Pro stock

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