moto g8 plus flashing-locked - Moto G8 Plus Questions & Answers

it does not start and I can not put any rom
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

Hi, try booting with a boot.img in the same version of your phone.
First, type in CMD fastboot getvar all
Second, Look for the line which states your installed rom version.
Third, Download the same rom and extract the boot.img from the zip file
Fourth, In CMD type fastboot boot boot.img If nothing goes wrong with the download, your device should boot up. Then check to see if you can activate the OEM lock. If not, try updating phone. Does it let you you update? great do it. If it show device system integrity corrupted, wait seven days without turning phone off and try updating again. If still no dice, then you're out of luck.
I had same problem as you, and what got mine back from the dead was to keep updating till one update fixed my issue.

mrsiri said:
Hi, try booting with a boot.img in the same version of your phone.
First, type in CMD fastboot getvar all
Second, Look for the line which states your installed rom version.
Third, Download the same rom and extract the boot.img from the zip file
Fourth, In CMD type fastboot boot boot.img If nothing goes wrong with the download, your device should boot up. Then check to see if you can activate the OEM lock. If not, try updating phone. Does it let you you update? great do it. If it show device system integrity corrupted, wait seven days without turning phone off and try updating again. If still no dice, then you're out of luck.
I had same problem as you, and what got mine back from the dead was to keep updating till one update fixed my issue.
Click to expand...
Click to collapse
Friend. could you help me?
I tried this method but it did not work, i tried with the version that the getvar gives me :
(bootloader) ro.build.fingerprint[0]: motorola/doha/doha:10/QPI30.28-Q3-
(bootloader) ro.build.fingerprint[1]: 28-26-4-1/2f8cb:user/release-keys
But it still don't work, i tried every other compilation too, excluding the Android 9 ones... I also tried blankflash but did not work.
It gives me error and goes to the "Your device is corrupt. It can't be trusted and will not boot" screen:
fastboot boot boot.img
downloading 'boot.img'...
OKAY [ 1.845s]
booting...
FAILED (status read failed (Too many links))
finished. total time: 32.039s

setryky said:
Friend. could you help me?
I tried this method but it did not work, i tried with the version that the getvar gives me :
(bootloader) ro.build.fingerprint[0]: motorola/doha/doha:10/QPI30.28-Q3-
(bootloader) ro.build.fingerprint[1]: 28-26-4-1/2f8cb:user/release-keys
But it still don't work, i tried every other compilation too, excluding the Android 9 ones... I also tried blankflash but did not work.
It gives me error and goes to the "Your device is corrupt. It can't be trusted and will not boot" screen:
fastboot boot boot.img
downloading 'boot.img'...
OKAY [ 1.845s]
booting...
FAILED (status read failed (Too many links))
finished. total time: 32.039s
Click to expand...
Click to collapse
Fastboot boot won't work because locked bootloader checks for a key which don't match correctly. You should try same version as the one installed on your phone or newer. Can you boot system?
The only way is to get blankflash to work. Try other computer, preferably older ones with intel, not AMD. If system is able to boot try OTA update because it fixed on mine.

mrsiri said:
Fastboot boot won't work because locked bootloader checks for a key which don't match correctly. You should try same version as the one installed on your phone or newer. Can you boot system?
The only way is to get blankflash to work. Try other computer, preferably older ones with intel, not AMD. If system is able to boot try OTA update because it fixed on mine.
Click to expand...
Click to collapse
I know that this version (QPI30.28-Q3-28-26-4-1) is the correct one because i had flashed my phone with it before trying to lock the bootloader, and it worked. I also tried every other compilation. I got the .rar from lolinet.
I tried blankflash, it did not work... It still gives me the same error. My computer on a i7 920, so it's very old. Anyways, thanks for any help you might be able to provide.

Setryky did you find any solution? I have the same problem

Fael.exe said:
Setryky did you find any solution? I have the same problem
Click to expand...
Click to collapse
I did not

setryky said:
I know that this version (QPI30.28-Q3-28-26-4-1) is the correct one because i had flashed my phone with it before trying to lock the bootloader, and it worked. I also tried every other compilation. I got the .rar from lolinet.
I tried blankflash, it did not work... It still gives me the same error. My computer on a i7 920, so it's very old. Anyways, thanks for any help you might be able to provide.
Click to expand...
Click to collapse
You should get boot.img from rom and use command fastboot boot boot.img to boot to rom. Then try oem unlock option activating or OTA updating if first doesn't work

mrsiri said:
You should get boot.img from rom and use command fastboot boot boot.img to boot to rom. Then try oem unlock option activating or OTA updating if first doesn't work
Click to expand...
Click to collapse
i did that with every rom in lolinet... did not work. And now it is saying that my device has "no bootable a/b slot".

Does your device show up as QCOM 9008? It's the EDL state and only way to install via blank flash

mrsiri said:
Does your device show up as QCOM 9008? It's the EDL state and only way to install via blank flash
Click to expand...
Click to collapse
no, it does not. I already tried blankflash... When i do blankflash it goes back to the "your device is corrupted" screen.

setryky said:
no, it does not. I already tried blankflash... When i do blankflash it goes back to the "your device is corrupted" screen.
Click to expand...
Click to collapse
You can't do blank flash if it's not showing QCOM 9008 mode on device manager, that's the device EDL mode. I'm afraid that's you only option, aside from opening back glass plate and shorting 2 points in motherboard or using a stripped USB cable and shorting green cable to black cable

setryky said:
i did that with every rom in lolinet... did not work. And now it is saying that my device has "no bootable a/b slot".
Click to expand...
Click to collapse
No bootable a/b slot... You wiped system?

mrsiri said:
You can't do blank flash if it's not showing QCOM 9008 mode on device manager, that's the device EDL mode. I'm afraid that's you only option, aside from opening back glass plate and shorting 2 points in motherboard or using a stripped USB cable and shorting green cable to black cable
Click to expand...
Click to collapse
Idk the points in motherboard so best way is to use cable method or buy an EDL cable online or use a "box" which flashes directly through JTAG but that is expensive. Just leave the green and black cables connected for 8 seconds if nothing happens try again this time for 20 seconds

mrsiri said:
Idk the points in motherboard so best way is to use cable method or buy an EDL cable online or use a "box" which flashes directly through JTAG but that is expensive. Just leave the green and black cables connected for 8 seconds if nothing happens try again this time for 20 seconds
Click to expand...
Click to collapse
i entered in the edl mode via the pins... the blankflash did work, but not to fix my system.

mrsiri said:
No bootable a/b slot... You wiped system?
Click to expand...
Click to collapse
no, its like when i do "fastboot boot boot.img" too many times, and when i do a blankflash it goes to that your device is corrupted screen.

The EDL should have worked... Well your last bet is on the box JTAG flasher. You'll either buy it and learn how to flash or ask some professional to do it

boa tarde eu to com esse problema no meu moto g8 plus flashing- locked ...alguem pode me ajudar por favor
Mod translation via GT: good afternoon I have this problem on my moto g8 plus flashing-locked ... can someone help me please

Related

OnePlus 7 Pro 5G [UK Model] Bricked Please Help!

I was attempting to root my OnePlus 7 so that I could increase the volume limits (I'm hearing impaired) via TWRP and then eventually Magisk, however it seems many things went wrong along the way. I managed to get TWRP working on my phone but then it wasn't finding any of my stored memory and therefore the TWRP Zip file I needed to finally root the phone. In my efforts to correct that I have bricked my phone (not sure if it's hard bricked or soft bricked) but currently it will only boot into the fastboot menu and selecting any option brings me right back to the fastboot menu again.
I tried getting back to the TWRP but no luck when I try to boot it I get the error message FAILED (remote: Failed to load/authenticate boot image: Load Error)
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
After reading online for a bit of help I thought it might be hard bricked so I tried to use the MSM tool but again I had no luck due to Param Preload - Device not match image
I have attached screenshots for both issues, I've also tried guides for soft bricked OP7P and despite showing as successful they reboot right back into the fastboot menu as if nothing has happened.
Please I'd really appreciate some help I've been trying for days to fix this mess!
Darhk Citadel said:
I was attempting to root my OnePlus 7 so that I could increase the volume limits (I'm hearing impaired) via TWRP and then eventually Magisk, however it seems many things went wrong along the way. I managed to get TWRP working on my phone but then it wasn't finding any of my stored memory and therefore the TWRP Zip file I needed to finally root the phone. In my efforts to correct that I have bricked my phone (not sure if it's hard bricked or soft bricked) but currently it will only boot into the fastboot menu and selecting any option brings me right back to the fastboot menu again.
I tried getting back to the TWRP but no luck when I try to boot it I get the error message FAILED (remote: Failed to load/authenticate boot image: Load Error)
After reading online for a bit of help I thought it might be hard bricked so I tried to use the MSM tool but again I had no luck due to Param Preload - Device not match image
I have attached screenshots for both issues, I've also tried guides for soft bricked OP7P and despite showing as successful they reboot right back into the fastboot menu as if nothing has happened.
Please I'd really appreciate some help I've been trying for days to fix this mess!
Click to expand...
Click to collapse
How did you unlock the boot loader?
tech_head said:
How did you unlock the boot loader?
Click to expand...
Click to collapse
I enabled USB Debugging on my phone and then used "Shift + Right Click" from within the folder with twrp file and used the command "fastboot oem unlock"
Was in this situation. If you have an unlocked bootloader, try to search for the fastboot ROMs on xda. Not sure if there is a 5g version though. With a try. Best of luck.
Darhk Citadel said:
I enabled USB Debugging on my phone and then used "Shift + Right Click" from within the folder with twrp file and used the command "fastboot oem unlock"
Click to expand...
Click to collapse
Look here https://forum.xda-developers.com/oneplus-7-pro/how-to/rom-stock-fastboot-roms-oneplus-7-pro-t3931424
toonstra said:
Look here https://forum.xda-developers.com/oneplus-7-pro/how-to/rom-stock-fastboot-roms-oneplus-7-pro-t3931424
Click to expand...
Click to collapse
Thanks, I tried that this morning perhaps I did it wrong, but when I used the same cmd window as I did to "unlock" the bootloader nothing happened. It went through the process and finally finished with no errors and said "press any key to exit" -But as for my phone it did not reboot in fact there was no change at all, it remained on the bootloader screen as normal. When I tried to reboot for a normal load it looped back to the bootloader, when I tried to reboot to recovery it booted back to recovery. It was as if the fastboot ROM was completely ineffective.
Darhk Citadel said:
Thanks, I tried that this morning perhaps I did it wrong, but when I used the same cmd window as I did to "unlock" the bootloader nothing happened. It went through the process and finally finished with no errors and said "press any key to exit" -But as for my phone it did not reboot in fact there was no change at all, it remained on the bootloader screen as normal. When I tried to reboot for a normal load it looped back to the bootloader, when I tried to reboot to recovery it booted back to recovery. It was as if the fastboot ROM was completely ineffective.
Click to expand...
Click to collapse
So I just tried to flash a recovery.img and I got this error "failed (remote (recovery_a) no such partition)" which leads me to believe that my phone is a lot worse than I originally thought...
Any help would be greatly appreciated I fully accept that I messed this up BIG TIME!
Darhk Citadel said:
So I just tried to flash a recovery.img and I got this error "failed (remote (recovery_a) no such partition)" which leads me to believe that my phone is a lot worse than I originally thought...
Any help would be greatly appreciated I fully accept that I messed this up BIG TIME!
Click to expand...
Click to collapse
Ok so I finally managed to get to the root of the problem and my phone is now back up and running without any issues, I completely missed the correct MSM too package that I needed for my phone and region as I have a UK OnePlus Pro 7 5G I needed to use this specific package to reset my phone back to stock: [OP7PRO 5G EU][OOS 9.5.11 GM27BA]
Appreciate all the help everyone hopefully someone else can use this to avoid making the same mistake I did!

Realme x50 Pro Fastboot Mode Lock Help ?

can someone help me phone is stuck in fastboot mode i can't enter recovery mode i can't flash file
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
can someone help me phone is stuck in fastboot mode i can't enter recovery mode i can't flash file
smhzhl said:
can someone help me phone is stuck in fastboot mode i can't enter recovery mode i can't flash file
Click to expand...
Click to collapse
Me too, i have updated to Android 11_ UI 2.0 via VPN fake IP Guangdong, after that I install TWRP and my phone is stuck in fastboot mode i can't enter recovery mode i can't flash file, plz help me! Thanks all so much!
Once you update to android 11 you cant flash recovery through fast boot with that old twrp.img file. Only way is to stay in android 10. Dont try to flash android 10 ozip file through color os recovery if you are in android 11. I got bootloop and couldn't recover.
Or you can flash an old .ofp file from realme flash tool to android 10 (which wipes everything) and use fastboot to flash twrp recovery.
With Android 11 A/B partitioning became mandatory (Google). Installing TWRP became risky for that reason. This "issue" exists for more than 1 year on OnePlus phones for example.
Extract this https://mirrors.lolinet.com/firmware/gsi/Pixel/Pixel-AB-11-20200909-ErfanGSI.img-0125.7z and fastboot flash the extracted .img into system.
Do you know if it's possible to install Magisk on a A/B Android 11 Realme device ? Personally the modified boot way doesn't work, it doesn't boot on my x50 pro :/
Check with treble checker app from playstore. If seamless updates are available then you have A/B partitions. And basically if you have that there wont be actual "recovery" partition. So you cannot use the flash recovery command in fastboot. For that you have to flash that recovery in boot partition like "fastboot flash boot "recovery".img"
I dont know much about it and i am still on android 10. I am not a developer so correct me if i am wrong.
Tried what jjgvv said but I got this:
fastboot flash system Pixel-AB-11-20200909-ErfanGSI.img
Sending sparse 'system' 1/4 (786428 KB) OKAY [ 18.067s]
Writing 'system' FAILED (remote: 'Partition not found')
fastboot: error: Command failed
What shoud I do?
My phone is RMX2071 Chinese model
Where can I find the OFP for the RMX071 Chinese phone?
Thanks guys
Touche said:
Tried what jjgvv said but I got this:
fastboot flash system Pixel-AB-11-20200909-ErfanGSI.img
Sending sparse 'system' 1/4 (786428 KB) OKAY [ 18.067s]
Writing 'system' FAILED (remote: 'Partition not found')
fastboot: error: Command failed
What shoud I do?
Click to expand...
Click to collapse
Is your phone booting after that?
You can try flashing the old twrp in place of boot as recovery partition is not there. This will eventually flash onto A/B partition for temporary twrp.
Lamhehe said:
Me too, i have updated to Android 11_ UI 2.0 via VPN fake IP Guangdong, after that I install TWRP and my phone is stuck in fastboot mode i can't enter recovery mode i can't flash file, plz help me! Thanks all so much!
Click to expand...
Click to collapse
same happend to me
jhosharath said:
Is your phone booting after that?
You can try flashing the old twrp in place of boot as recovery partition is not there. This will eventually flash onto A/B partition for temporary twrp.
Click to expand...
Click to collapse
Hi mate,
My phone is not booting it is stuck in the bootloader like the photo in the post.
I tried to flask the old TWRP in boot partition too but it is still not booting or entering the recovery..
I think my only option is flash an OFP file, but I can't find it for RMX2071 Chinese phone.
Help! Hahaha
Touche said:
Hi mate,
My phone is not booting it is stuck in the bootloader like the photo in the post.
I tried to flask the old TWRP in boot partition too but it is still not booting or entering the recovery..
I think my only option is flash an OFP file, but I can't find it for RMX2071 Chinese phone.
Help! Hahaha
Click to expand...
Click to collapse
Bad luck bro. RMX 2071 doesnt have an official ofp file i think. You can try entering edl mode and flash the firmware from that.
You can get the firmware from officialrom.com site. Instructions are given there.
Try to enter edl from fastboot by typing fasboot reboot edl or fastboot oem edl command. If not try the button combination given there.
Or you can go to realme service center and they will do it for free if under warranty.
jhosharath said:
Bad luck bro. RMX 2071 doesnt have an official ofp file i think. You can try entering edl mode and flash the firmware from that.
You can get the firmware from officialrom.com site. Instructions are given there.
Try to enter edl from fastboot by typing fasboot reboot edl or fastboot oem edl command. If not try the button combination given there.
Or you can go to realme service center and they will do it for free if under warranty.
Click to expand...
Click to collapse
Bro! I spent all day yesterday trying to understand why it is not flashing. I still don't know.
I do not think RMX2071 has A/B partition. Tried to use fastboot "fastboot --set-active=a" returns no partition found.
I found an OFP file from "https://www.officialroms.com/realme-x50-pro-flash-file/" .
I tried to use the Realme flasher with this OFP but I'm getting " Invalid sparse file format at header magi" when it starts to flash the super.img. It finishes flash everything but It still doesn't boot. It goes back to the Bootloader/fastboot.
I tried using the MSM Download Tool but all the files I found are compacted and has password.
I found another OFP file but it is inside a compacted file from GSMMafia and I do not want to pay to get a password. It's not about the money but principles. hehehe.
No way to get to EDL mode. it says no partition found too.
Any Ideas?
Thanks for the help!
Bro i think its better to take to service center and get it flashed for free if under warranty or they may charge a little if out of warranty period. I dont have much idea about these realme stuffs. Even i had a similar problem but my fastboot/bootloader wont stay and keeps restarting for every 30 secs for which i couldnt do anything. So i took to service center and they did it in 4 hours. They flashed firmware using edl mode. Thereafter i never upgraded to android 11. Sorry couldnt help you much. Good luck
Touche said:
Bro! I spent all day yesterday trying to understand why it is not flashing. I still don't know.
I do not think RMX2071 has A/B partition. Tried to use fastboot "fastboot --set-active=a" returns no partition found.
I found an OFP file from "https://www.officialroms.com/realme-x50-pro-flash-file/" .
I tried to use the Realme flasher with this OFP but I'm getting " Invalid sparse file format at header magi" when it starts to flash the super.img. It finishes flash everything but It still doesn't boot. It goes back to the Bootloader/fastboot.
I tried using the MSM Download Tool but all the files I found are compacted and has password.
I found another OFP file but it is inside a compacted file from GSMMafia and I do not want to pay to get a password. It's not about the money but principles. hehehe.
No way to get to EDL mode. it says no partition found too.
Any Ideas?
Thanks for the help!
Click to expand...
Click to collapse
did you find any solution? im in the same boat like you
afgboy said:
did you find any solution? im in the same boat like you
Click to expand...
Click to collapse
Not yet bro. I still have some thing to try.
I'll let you know if I find a solution.
Please let me know if you find before me
Touche said:
Not yet bro. I still have some thing to try.
I'll let you know if I find a solution.
Please let me know if you find before me
Click to expand...
Click to collapse
sure the same goes for you bro
Touche said:
Not yet bro. I still have some thing to try.
I'll let you know if I find a solution.
Please let me know if you find before me
Click to expand...
Click to collapse
And me too cuz I have an Oppo 10x zoom having same problem unlocked bootloader, stuck in Fastboot mode

How to flash custom kernel/ROM in EMUI 10 via Software Testpoint mode

HOW TO FLASH IN EMUI10 VIA SOFTWARE TESTPOINT
1. Enter USB Update Mode
On older EMUI versions you would use vol up + vol down + power. This has changed now.
On EMUI 10, enter eRecovery by holding volume up and power until you see the Huawei logo appear. Then let go and press volume up again and wait for eRecovery screen. Then press USB Update and it should show an update screen at 5% complete.
2. Enable Software Testpoint
Using the update.app of the same firmware that you are currently on, turn factory mode on via whichever app you happen to be using. Personally I am using Octoplus Huawei Tool (paid), but you could also use Chimera (paid), Sigmakey (paid) and many others. There are free methods too by manual flashing in Linux but it is too involved to discuss here.
Output from Octoplus looks like:
Code:
Starting ON/OFF Factory Mode
Selected phone model: CLT-L29
To Enable Factory mode put the phone in Upgrade mode and connect USB cable!
To Disable Factory mode connect the phone in Factory mode or Factory Fastboot mode!
Checking the existence of the auto firmware file...
Selected firmware file file: C:/Users/srefs/Documents/HiSuite/ROM/Charlotte-L29C10.0.0.171_Firmware_EMUI10.0.0_05015AMH/Software/dload/UPDATE_BASE.APP
Performing ON Factory Mode operation...
Checking firmware package type
Searching device in Upgrade mode...
Connecting to phone..
Phone connect successfully!
Writing firmware partitions...
Writing ‪SHA256RSA‬ partition...
Writing ‪CRC‬ partition...
Writing ‪BASE_VERLIST‬ partition...
Writing ‪BASE_VER‬ partition...
Writing ‪PACKAGE_TYPE‬ partition...
Writing ‪HISIUFS_GPT‬ partition...
Writing ‪XLOADER‬ partition...
ON/OFF Factory Mode done.
Performed by ‪1.2.3‬ Software version.
You should now see this in Device Manager on Windows, which means you successfully entered testpoint mode without disassembling your hardware. You can now literally do anything to your hardware.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
3. Write factory fastboot.
If you are using Octoplus, you just go to the Update backup tab, make sure 'Update OEMInfo' is NOT ticked and click Update. As soon as you see fastboot is flashed, you can cancel. For free method, see: Downgrade/Unbrick Huawei device (if other methods doesn't work) | XDA Developers Forums (xda-developers.com)
4. Flash whatever you want
Now you can flash whatever the heck you want over EMUI 10, such as a kernel. You will also need to disable verified boot so you can load unsigned images without getting the dreaded "your device has failed verification". Have fun!
Code:
PS C:\adb> .\fastboot flash kernel .\KERNEL.img
target reported max download size of 471859200 bytes
sending 'kernel' (24576 KB)...
OKAY [ 0.183s]
writing 'kernel'...
OKAY [ 0.275s]
finished. total time: 0.462s
PS C:\adb> .\fastboot flash kernel .\image-new.img
target reported max download size of 471859200 bytes
sending 'kernel' (20664 KB)...
OKAY [ 0.155s]
writing 'kernel'...
OKAY [ 0.081s]
finished. total time: 0.241s
PS C:\adb> .\fastboot oem get-build-number
...
(bootloader) :CLT-L29 10.0.0.171(C432E3R1P3)
OKAY [ 0.008s]
finished. total time: 0.011s
PS C:\adb> .\fastboot oem get-lockstate
...
(bootloader) locked
OKAY [ 0.004s]
finished. total time: 0.005s
5. Turn off Software Testpoint
Turn factory mode off in same software you used in step 2.
Code:
Performing OFF Factory Mode operation...
Searching Fastboot devices...
Found a fastboot device:
Device Model: ‪CLT-L29‬
System: ‪CLT-L29 10.0.0.171(C432E3R1P3)‬
...
Writing secure data...
Rebooting device...
ON/OFF Factory Mode done.
Performed by ‪1.2.3‬ Software version.
Now either you did the right thing by this stage and it boots up nicely... or you screwed up something and it doesn't boot up. As long as you can get to eRecovery again, you can let Huawei automatically recover. Note: If recovery fails the first time complaining about 'authorization', just run recover again and it will work.
Could that mean Possible Custom Roms in the Future?
I don't see why not. I'm just confused why the Huawei forums are totally devoid of custom kernels and ROMs.
I understand the lack of unlock bootloader, but with software testpoint this is really a moot point.
Me i
xsacha said:
I don't see why not. I'm just confused why the Huawei forums are totally devoid of custom kernels and ROMs.
I understand the lack of unlock bootloader, but with software testpoint this is really a moot point.
Click to expand...
Click to collapse
I Wonder myself aswell. The P20 Pro would be even better with Custom Firmware.
The Development should be there in my Opinion.
Good Phone, lag of Development.
By the way, you should be able to flash an older bootloader (but keep EMUI 10) using this method and then your bootloader will be unlocked again. Or, if not already unlocked, you can unlock with a key as per old way.
Advantages of bootloader unlock:
Flash kernels/roms without third-party software.
Disadvantages:
Have to root and use magisk hide for Google Pay to work again.
So, with this method, you can literally flash treble roms? Also, can we just the usb cable provided instead of a dongle for the paid programs?
xsacha said:
I don't see why not. I'm just confused why the Huawei forums are totally devoid of custom kernels and ROMs.
I understand the lack of unlock bootloader, but with software testpoint this is really a moot point.
Click to expand...
Click to collapse
Because without a bootloader unlock method, nobody bothered to keep maintaning the phone
AnotyClaws said:
So, with this method, you can literally flash treble roms? Also, can we just the usb cable provided instead of a dongle for the paid programs?
Click to expand...
Click to collapse
Dongle? I'm using the digital licence and it's just a key you paste in. No dongles required.
Is the same possible for honor 9 lite, lld-l31, EMUI 9.1 too? And how to make this free in linux?
sergeyzap said:
Is the same possible for honor 9 lite, lld-l31, EMUI 9.1 too? And how to make this free in linux?
Click to expand...
Click to collapse
Linux method requires you to open up your device, from what i see above. Shame that i don't have cash to buy the software required to root my phone.
Awesome there's some roms we can flash already?
Hi, does anyone know how to retrieve saved notes from the Huawei phone’s in-built note after a factory reset, without having it backed up in huawei’s cloud? Please help! Much appreciated
Nwl295 said:
Hi, does anyone know how to retrieve saved notes from the Huawei phone’s in-built note after a factory reset, without having it backed up in huawei’s cloud? Please help! Much appreciated
Click to expand...
Click to collapse
You can't. I'm sorry
I actually wonder, by "Flash anything" you mean i can just flash TWRP and, from there, do everything i want?
AnotyClaws said:
I actually wonder, by "Flash anything" you mean i can just flash TWRP and, from there, do everything i want?
Click to expand...
Click to collapse
@xsacha tell us more
Sorry to budge in, but Octoplus does not detect my phone at all, regardless of HiSuite version installed, reboots.
One weird thing I noticed is that even though I have USB debugging turned on and accept/approve the connection, HiSuite prompts me to approve the connection to my PC again while in USB update mode.
Any help is highly appreciated.
Edit: This is what it sees attached.
Found COM ports:
1: COM12 HUAWEI Mobile Connect - Fake Acm Interface
2: COM13 DBAdapter Reserved Interface
3: COM14 Android Adapter PCUI
this is great !
please can you share a simple how-to document when you have a valid ROM [e.g. TWRP]
i would like to flash my own p20 pro and dont have the skilset yet :-/
my p20pro is now wide open after battery change, and I wonder if it is possible to unlock bootloader by grounding test pin? Are there any good instructions?
xsacha said:
HOW TO FLASH IN EMUI10 VIA SOFTWARE TESTPOINT
[...]
4. Flash whatever you want
Now you can flash whatever the heck you want over EMUI 10, such as a kernel. You will also need to disable verified boot so you can load unsigned images without getting the dreaded "your device has failed verification". Have fun!
[...]
Click to expand...
Click to collapse
Hello dear xsache. I'm playing around with my P20 Pro since yesterday morning and I fked up.
I used DC Phoenix which can also set phone into Software TestPoint mode which is a great thing.
But... I'm now stuck exactly on that Device Verification, and I cant flash new Firmware because CURVER can't be flashed. I'm now wondering how I can deactivate Device Verification.
I can get into TestPoint Mode + Fastboot (with temp. unlocked bootloader), and I can get into Regular Fastboot (with locked bootloader).
I would like to run TWRP and install LineAgeOS, but I cant start TWRP out of TestPoint Mode.
I already ordered OctoPlus licence, but maybe you can give me a hint on how to deactivate verification.
Thx.
Update: With OctoPlus I managed to fully flash EMUI 8. Verification Message is gone.
But still no TWRP
I can get into Testpoint mode and Flash to recovery_ramdisk. Then get out of Testpoint Mode and phone reboots normally. Then shutdown. If I try Vol Down + Power I get into Fastboot, if I try Vol UP + Power I get into Huawei eRecovery...
If I go to fastboot mode and type "fastboot reboot recovery" it gets me into Huawei eRecovery too.
Do I need to flash another Partition? Or are changes reverted after I get out of Testpoint Mode?
UPDATE2:
FKIN HELL! FK HUAWEI!
I managed to boot into TWRP.
In DC Phoenix I went into Testpoint mode, temporarily unlocked bootloader, then:
fastboot flash erecovery_ramdisk twrp-3.5.0_9-0-charlotte.img (make sure its *e*recovery)
Then.... started holding Vol UP + Power, in DC Phoenix Disables TestPointed and holded the buttons all the time.
It then went into fastboot and then into ... TWRP!
Unfortunately, TWRP was not able to provide mounted partitions to windows and fastboot commands didnt work. But I was able to adb push the zip to /storage.
When I tried to install, I got following error:
huawei.verify_vendor_build_id() failed to read
current vendor build id: -2
updater process ended with ERROR: 7
Fking Huawei all over the place....
Update3:
Changed updater-script in LineAge Zip. remove first 3 assert lines... hehe xd
Successfully flashed.
It could have been so nice.... tried to reboot but it always went to TWRP. Not able to boot System.... :/
Gonna Flash EMUI 9 and Try again.
And then EMUI10 and Try again.
And then Give up and burn that fking phone.
Final(?) Update:
Phone Dead. Looks like I flashed a Bad FW.
(1) Verification failed msg back.
(2) eRecovery destroyed (recovery image load failed)
(3) Bootloader Locked
(4) FRP Locked, so no bootloader unlock
I then have thrown the phone out of the window.
OK, unfortunately that was just in my imagination.
I opened up the phone and used hardwaretestpoint, got into fastboot with DC Phoenix and was able to flash another firmware...
I think LineAge OS like it is (Install Script) wont work with termporary unlocked bootloader.
It looks like TWRP does some stuff it needs an unlocked bootloader for.
So we will have to wait until there is a working method.
BTW, Ministry of Solutions really offers CLT-L29 Bootloader unlock codes now. But it seems to doesnt work with every model. He was on my PC yesterday for hours trying to do so but the found Code didnt work. It was the second phone (P20 Pro) that didnt work for him. With some others he was successful. So there might be some hope for some people out there. He refunded my $15 same day even after I told him he could keep it.
To be continued...
Is it possible on Emui10 to just flash Magisk to get root and not go through all the hell posted above?

ONEPLUS 8T - only fastboot - no edl, msm sees nothing!? [SOLVED]

[SOLVED] Please read through, hopefully this helps someone!​
Ive tried numerous threads and followed the steps always end up with some sort of error.
Device manager shows:
Kedacom USB Device>Android Bootloader Interface
errors:
fastboot: error: Failed to boot into userspace fastboot; one or more components might be unbootable.
fastboot: error: Could not check if partition xbl has slot all
fastboot: error: Could not check if partition xbl_config has slot all
and continues with this error for what ever its trying to flash "has slot all"
flashing logical patitions error:
no such partition or partition not found
I keep researching and every video that shows what to do or posts, i can only get so far before my results dont match and there is no option or description for what to do if getting an error.
edit: adb devices shows nothing, but fastboot devices shows serial.
TIA
I think you have the wrong drivers, try these and check in windows update if your Qualcomm drivers are up to date in the optional updates. Also if fastboot is working and the bootloader is unlocked, you can download the latest full oos 12 and flash it all.
LaviLev said:
Ive tried numerous threads and followed the steps always end up with some sort of error.
Device manager shows:
Kedacom USB Device>Android Bootloader Interface
errors:
fastboot: error: Failed to boot into userspace fastboot; one or more components might be unbootable.
fastboot: error: Could not check if partition xbl has slot all
fastboot: error: Could not check if partition xbl_config has slot all
and continues with this error for what ever its trying to flash "has slot all"
flashing logical patitions error:
no such partition or partition not found
I keep researching and every video that shows what to do or posts, i can only get so far before my results dont match and there is no option or description for what to do if getting an error.
edit: adb devices shows nothing, but fastboot devices shows serial.
TIA
Click to expand...
Click to collapse
If you need the latest oos I can link it here.
Nimiskiv said:
If you need the latest oos I can link it here.
Click to expand...
Click to collapse
Please do! currently DLing the drivers posted Thank you!
https://android.googleapis.com/packages/ota-api/package/435fc808f603bbc8a63ce30fd944676a65a61d6f.zip
LaviLev said:
Please do! currently DLing the drivers posted Thank you!
Click to expand...
Click to collapse
Oh but be careful that's for kebab 2005
Here's the repo
[OnePlus 8T][ROM][OTA][Oxygen OS] Repo of Oxygen OS Builds
Added 11.0.5.6 KB05AA full zip from support website to OP
forum.xda-developers.com
Nimiskiv said:
Oh but be careful that's for kebab 2005
Here's the repo
[OnePlus 8T][ROM][OTA][Oxygen OS] Repo of Oxygen OS Builds
Added 11.0.5.6 KB05AA full zip from support website to OP
forum.xda-developers.com
Click to expand...
Click to collapse
Anything with "kebab" in the beginning is OOS 12
Nimiskiv said:
https://android.googleapis.com/packages/ota-api/package/435fc808f603bbc8a63ce30fd944676a65a61d6f.zip
Click to expand...
Click to collapse
ok ty, looks like is c11 the first android 12 update for the OP8T, downloading now. Hopefully i can get it to flash.
LaviLev said:
ok ty, looks like is c11 the first android 12 update for the OP8T, downloading now. Hopefully i can get it to flash.
Click to expand...
Click to collapse
Use the MSM tool first
Nimiskiv said:
Use the MSM tool first
Click to expand...
Click to collapse
can not get phone to edl stuck in fastboot only. tried all the commands and physical button configs and still only get fastboot. Any workarounds?
I downloaded Fastboot Enhance, which allowed me to flash a bin file, but the phone still wont boot. I had to check ignore unknown partitions for it to flash. Now i can access fastbootd and when choose boot to recovery it loads what looks to a limited recovery similiar to fastbootd.
Any advice?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
LaviLev said:
I downloaded Fastboot Enhance, which allowed me to flash a bin file, but the phone still wont boot. I had to check ignore unknown partitions for it to flash. Now i can access fastbootd and when choose boot to recovery it loads what looks to a limited recovery similiar to fastbootd.
Any advice?
View attachment 5683905
Click to expand...
Click to collapse
That's a stock OOS recovery you're seeing.
BillGoss said:
That's a stock OOS recovery you're seeing.
Click to expand...
Click to collapse
Any advice or known methods to get me running from here?
LaviLev said:
Any advice or known methods to get me running from here?
Click to expand...
Click to collapse
Run the MSM tool in edl, since now it should work fine. Also did the drivers work? If not you need to uninstall them in windows device manager, then reinstall them
LaviLev said:
Any advice or known methods to get me running from here?
Click to expand...
Click to collapse
Well, you've never said in your initial post what it was that you were trying to do.
Now that you are in the stock recovery you can select Advanced> reboot fastboot.
This will put you into fastbootd mode where you can do things like flash partitions and, more importantly, flash the logical partitions.
But, if you don't know how to do this and get out of whatever mess you're in , then use MSM Tool to reset your phone.
BillGoss said:
Well, you've never said in your initial post what it was that you were trying to do.
Now that you are in the stock recovery you can select Advanced> reboot fastboot.
This will put you into fastbootd mode where you can do things like flash partitions and, more importantly, flash the logical partitions.
But, if you don't know how to do this and get out of whatever mess you're in , then use MSM Tool to reset your phone.
Click to expand...
Click to collapse
I just reread my initial post, damn I started typing mid thought.. my bad!
I tried msmtool, but it doesn't load up a com port. All the listed methods with holding both vol buttons after already hitting start then plugging in did not work as I don't think it sees it at all.
Haven't found a thread with fastboot instructions that didn't require something I couldn't get to, to restore the phone. other methods fail writing to numerous areas when flashing.
trying this...
[GUIDE] Unbrick or restore to OOS using only fastboot
This guide will only work up to OOS 11. This guide is for users that can't or just don't want to download MsmDownloadTool. Linux users especially, since the tool is not available for linux. All you need is a recent version of android tools with...
forum.xda-developers.com
LaviLev said:
trying this...
[GUIDE] Unbrick or restore to OOS using only fastboot
This guide will only work up to OOS 11. This guide is for users that can't or just don't want to download MsmDownloadTool. Linux users especially, since the tool is not available for linux. All you need is a recent version of android tools with...
forum.xda-developers.com
Click to expand...
Click to collapse
OK was able to execute the first 4 fastboot commands, the it hung on the first flash --slot=all
In the end i just boot the phone in fasbootd using fastboot enhance and then using the flash bin file option in FE to flash the OOS 12 FILE @Nimiskiv shared.
Final boots into OOS, hope all works I will be testing to see for a day or two before i switch back from the 6, also before all this the 8T went a12_c11 to a12_c33
right now update for c20 came up!?
Any additional insight or final thoughts appreciated. Thanks again all!
LaviLev said:
OK was able to execute the first 4 fastboot commands, the it hung on the first flash --slot=all
In the end i just boot the phone in fasbootd using fastboot enhance and then using the flash bin file option in FE to flash the OOS 12 FILE @Nimiskiv shared.
Final boots into OOS, hope all works I will be testing to see for a day or two before i switch back from the 6, also before all this the 8T went a12_c11 to a12_c33
right now update for c20 came up!?
Any additional insight or final thoughts appreciated. Thanks again all!
Click to expand...
Click to collapse
check if EDL is working now, its very important for edl to work, because if something happens in the future, you need edl to reset.

Trying to fix corrupted boot file on oneplus 8 5g in2017 tmobile model (FIXED)

sorry if this is not the right place to ask this
After unlocking my bootloader i tried to flash twrp on my phone by using the command "fastboot flash recovery twrp-3.7.0_11-0-instantnoodle.img"
When i restarted the phone it got stuck in a bootloop
I've been searching for a way to fix it for hours now, but everytime i do something it feels like i make it worst, now my phone is showing me an error that reads "the current image(boot/recovery) have been destroyed"
I dont know what to do, please if you have an idea of how to go forward reply
Provenscroll said:
sorry if this is not the right place to ask this
After unlocking my bootloader i tried to flash twrp on my phone by using the command "fastboot flash recovery twrp-3.7.0_11-0-instantnoodle.img"
When i restarted the phone it got stuck in a bootloop
I've been searching for a way to fix it for hours now, but everytime i do something it feels like i make it worst, now my phone is showing me an error that reads "the current image(boot/recovery) have been destroyed"
I dont know what to do, please if you have an idea of how to go forward reply
Click to expand...
Click to collapse
Hi, try to download the firmware for your device and flash it to your phone.
Jan Skokan said:
Hi, try to download the firmware for your device and flash it to your phone.
Click to expand...
Click to collapse
Do you know where I could find the stock firmware?
Provenscroll said:
Do you know where I could find the stock firmware?
Click to expand...
Click to collapse
Try this
Jan Skokan said:
Try this
Click to expand...
Click to collapse
It's telling me to get a "download package". Do I have to pay for this?
First, are you sure your device bootloader is unlocked?
Two, are you able to enter fastboot menu?
Three, if you can enter fastboot, try to BOOT into twrp instead of FLASH
Example: fastboot boot twrp.img
Booting into TWRP is the instructions for the OnePlus Pro 9, maybe it may work on the 8?
MAKE SURE OEM lock is removed first!!!
immortalwon said:
First, are you sure your device bootloader is unlocked?
Two, are you able to enter fastboot menu?
Three, if you can enter fastboot, try to BOOT into twrp instead of FLASH
Example: fastboot boot twrp.img
Booting into TWRP is the instructions for the OnePlus Pro 9, maybe it may work on the 8?
MAKE SURE OEM lock is removed first!!!
Click to expand...
Click to collapse
I'm talking about the website with the package thing, when i tried to boot into twrp i got this error
./fastboot boot twrp-3.7.0_11-0-instantnoodle.img
Sending 'boot.img' (67276 KB) OKAY [ 1.949s]
Booting FAILED (remote: 'Failed to load/authenticate boot image: Load Error')
fastboot: error: Command failed
[OnePlus 8][ROM][OTA][Oxygen OS] Repo of Oxygen OS Builds
As OnePlus doesn't always provide download links for all of their OxygenOS ROMs & OTA update zips, we've created an index to put the links in one post so that they're easy to find. Note: This is not a support thread for issues you may have with...
forum.xda-developers.com
Has old firmware you can download / flash. You can use a tool called Payload dumper on the firmware to extract all the sections and re-flash the sections you messed up. Can you get into the bootloader / fastboot screen and show me what it shows?
Re-download the twrp file for your device, rename it to twrp.img and try to do this command
Make sure you also have the correct drivers installed on your pc and disable driver signature enforcement:
fastboot boot twrp.img
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
FastBoot Mode
PRODUCT_NAME - Kona
VARIANT - SM8 UFS
BOOTLOADER VERSION -
BASEBAND VERSION -
SERIAL NUMBER - (Censored)
SECURE BOOT - yes
DEVICE STATE - unlocked
Provenscroll said:
View attachment 5863469
FastBoot Mode
PRODUCT_NAME - Kona
VARIANT - SM8 UFS
BOOTLOADER VERSION -
BASEBAND VERSION -
SERIAL NUMBER - (Censored)
SECURE BOOT - yes
DEVICE STATE - unlocked
Click to expand...
Click to collapse
Ok the fact you can enter into this mode and it says device unlocked is good. I am not sure why it doesn't allow you to boot with the above mentioned command into recovery.
Please make sure like I previously mentioned you have latest platform tools, latest oneplus usb drivers and try to switch to a usb 2.0 port on your pc or laptop. Disable driver signature enforcement in windows before you try to install oneplus drivers.
I've should have mentioned this earlier but i'm doing most of this on a linux machine, but i have repeated the commands on a windows laptop doing everything that has been mentioned previously to similar results
Now when i try to boot Twrp it just hangs and no changes happen on my phone
.\fastboot boot twrp.img
Sending 'boot.img' (67276 KB)
and then nothing happens
When i try to flash recovery it also hangs
.\fastboot flash recovery twrp.img
and no response
I'll try this with a different cable and update this post
Provenscroll said:
I've should have mentioned this earlier but i'm doing most of this on a linux machine, but i have repeated the commands on a windows laptop doing everything that has been mentioned previously to similar results
Now when i try to boot Twrp it just hangs and no changes happen on my phone
.\fastboot boot twrp.img
Sending 'boot.img' (67276 KB)
and then nothing happens
When i try to flash recovery it also hangs
.\fastboot flash recovery twrp.img
and no response
I'll try this with a different cable and update this post
Click to expand...
Click to collapse
I think you corrupted a bunch of stuff when you used a linux machine to flash a recovery. The drivers are vastly different on a linux machine. You might have to use a MSM tool at this point, but I am not sure if the T-mobile version has one. Keep us updated on the new cable. Also try different usb ports as well.
Which android version did your phone have? I checked the official twrp website and it only supports A11 devices for oneplus 8.
@Provenscroll EDIT: I was just testing different slots a/b on fastboot and realized that when I changed to slot a, my inactive slot, I get the same error as you did with fastboot. Try to use the other slot if possible.
immortalwon said:
I was just testing different slots a/b on fastboot and realized that when I changed to slot a, my inactive slot, I get the same error as you did with fastboot. Try to use the other slot if possible.
Click to expand...
Click to collapse
So i tried this and it successfully flashed:
.\fastboot flash recovery_b twrp.img
Sending 'recovery_b' (67276 KB) OKAY [ 1.638s]
Writing 'recovery_b' OKAY [ 0.212s]
Finished. Total time: 2.093s
When I reboot into recovery though it just ends up at the boot/recovery error
immortalwon said:
Which android version did your phone have? I checked the official twrp website and it only supports A11 devices for oneplus 8.
Click to expand...
Click to collapse
My android was at 12 so that might explain why flashing twrp isn't working
immortalwon said:
I checked the official twrp website and it only supports A11 devices for oneplus 8.
Click to expand...
Click to collapse
Does the firmware i flash onto the phone also have to match the original android version?
Provenscroll said:
Does the firmware i flash onto the phone also have to match the original android version?
Click to expand...
Click to collapse
Yes I would try it on A11 first. But don't quote me on that because there is a reason I don't like using carrier based phones instead of fully unlocked phones. They come with unpredictable problems. Try at own risk. I would first try to boot into TWRP first on a11 firmware and then flash TWRP recovery with the option: "Install Recovery ramdisk" then select the .img file you downloaded from website. You can also use: Go to Advanced > Flash Current TWRP.
But the problem is: you need to be able to BOOT first into the recovery.
Heck I would try to boot with the a11 twrp right now just to see if it loads instead of using the flash command, if it boots up its a good sign but it probably won't have decryption support, all your files will look like random numbers. Your bootloader is unlocked so common sense dictates it should be able to boot the twrp.
Fastboot boot twrp.img
EDIT: Well I tried to boot unofficial a12 twrp onto my device and it didn't boot into it. So it might not work for you either. I am on stock oos 11 and the a11 version is the only one that boots.
This link might be able to help:
https://forum.xda-developers.com/t/...p-for-oneplus-8-8pro-official-beta-3.4341707/
I noticed at this link, they have different .img files then the official website. Give it a try. They mentioned flashing instead of booting, so it's slightly confusing.
Ok so I tried flashing a boot.img file I extracted from a payload I got from here
OnePlus Android 12 Tracker: Here are all the official OxygenOS 12 builds to download and install
OxygenOS 12 Open Beta builds based on Android 12 have begun rolling out to multiple OnePlus smartphones. Head on over for the download links!
www.xda-developers.com
and now theres a recovery screen:
I tried using format data to see what happens since my important data is already backed up, when i did this my phone rebooted into a setup screen but when i get to the point where i have to setup my network the screen hangs and the phone restarts. Maybe this is because the roms model number doesn't exactly align with my phone?
I got it in twrp!!
Provenscroll said:
I got it in twrp!!
View attachment 5866011
Click to expand...
Click to collapse
Nice work man, what did you do exactly?
immortalwon said:
Nice work man, what did you do exactly?
Click to expand...
Click to collapse
After flashing the boot.img that i mentioned before i was simply able to run the command fastboot boot recovery.img to get it into twrp
Provenscroll said:
After flashing the boot.img that i mentioned before i was simply able to run the command fastboot boot recovery.img to get it into twrp
Click to expand...
Click to collapse
Ok I am not sure what you should do at this point: flashing the recovery while in TWRP or simply booting into it future wise. I read on t-mobile devices, if you try to flash it might brick it but I am not sure.

Categories

Resources