Related
Hi
Messed up my desire a while back. It won't boot. When I turn it on I get this screen
When I plug it in to PC then unplug it I get this screen
Can't flash any RUU. Can't access recovery. Just nothing. Anyone any ideas what I can do?
Sent from my GalaxyS2 with CM9
Hm, no fastboot. Does it recognize it if you connect the phone to your pc? Your PC may see a USB serial console that accepts commands.
Google for "HbootAnalysis" to get a list of commands.
The gotofastboot commands looks worth a shot. Once in fastboot you should be able to flash anything you want.
The phone reacts, and the computer knows there is something there. Just not a phone...
Sent from my GalaxyS2 with CM9
So you cannot even access fastboot?
No
Sent from my GalaxyS2 with CM9
This is probably extremely unhelpful so I apologise but what did you do/what happened to the Desire to make it (what seems to be) stuck in a loop?
this is a partition/radio brick
it usually happens when you try and RUU a device when its using the new alpharev hboots that do not have the right sizes (hes using the sense hboot which doesnt use stock sizes)
so basically it kills the partitions. this is because alpharev put that "annoying" hboot protection on to stop RUU's from overwriting it. i love the alpharev team but that really isnt needed
I dont think its possible to fix this without being able to get to fastboot as we need to get the hboot flashed with stock sizes
Stuck on the way RRU
I encountered the same problem today:
My solution:
You need Android-sdk with fastboot command
"fastboot devices" work for me
I got my last backup ClockworkMod on my sdcard
/clockworkdmod/backup/2012-01-16-18.04.51/
width these files:
boot.img
data.yaffs2.img
system.yaffs2.img
recovery.img
...
I flashed these files
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.yaffs2.img
fastboot flash userdata data.yaffs2.img
Then I tried the boot
fastboot oem boot
Iit worked !
After the reboot I stood on this page RUU (hboot)
To erase the RRU Flag on fastboot:
fastboot oem resetRUUflag
And now all is working on my cyanogen 7 NB
Try for Yourself
fxjumper
fxjumper said:
I encountered the same problem today:
My solution:
You need Android-sdk with fastboot command
"fastboot devices" work for me
I got my last backup ClockworkMod on my sdcard
/clockworkdmod/backup/2012-01-16-18.04.51/
width these files:
boot.img
data.yaffs2.img
system.yaffs2.img
recovery.img
...
I flashed these files
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.yaffs2.img
fastboot flash userdata data.yaffs2.img
Then I tried the boot
fastboot oem boot
Iit worked !
After the reboot I stood on this page RUU (hboot)
To erase the RRU Flag on fastboot:
fastboot oem resetRUUflag
And now all is working on my cyanogen 7 NB
Try for Yourself
fxjumper
Click to expand...
Click to collapse
indeed this should work
he said he cant boot to fastboot though, are you saying you can use fastboot in the RUU screen?
yes i can enter fastboot command
but after these stuff, i loosed my name/serial_number in adb but not in fastboot
my new adb username/serial_number is 1234567890ABCDEF
So,recently i switched from cm14.1 back to cm13 and when i did that, i forgot to downgrade the bootloader,so after i flashed the rom I went to the bootloader and made the downgrade,Successfully booted into cm13,but when i tried going to recovery to flash xposed,i found out there's bootloop ( stuck on asus logo ) ! Everytime i try to boot into bootloader or recovery! nothing works!
Saumitraa said:
So,recently i switched from cm14.1 back to cm13 and when i did that, i forgot to downgrade the bootloader,so after i flashed the rom I went to the bootloader and made the downgrade,Successfully booted into cm13,but when i tried going to recovery to flash xposed,i found out there's bootloop ( stuck on asus logo ) ! Everytime i try to boot into bootloader or recovery! nothing works!
Click to expand...
Click to collapse
if no boot loader you have to use unbrick threads.
If you had a flashed back a stock recovery and boot.img if on rooted mm bl with giovix modder tool , you could've downgraded via sd card and stock recovery ..in my link below
There were 2 different cm 13s , one with mm bl and one based on 5.
.
Unbricked
So i unbricked the phone! Everything was success! xfstk worked then i got the 4 color screen and after that the bootloader!
Extracted the .raw file and then flashed using commands, but when the phone tries to reboot, it gets stuck on the ASUS logo! waited half an hour for that! Service center people say that its a motherboard problem! Any advice ?
Saumitraa said:
So i unbricked the phone! Everything was success! xfstk worked then i got the 4 color screen and after that the bootloader!
Extracted the .raw file and then flashed using commands, but when the phone tries to reboot, it gets stuck on the ASUS logo! waited half an hour for that! Service center people say that its a motherboard problem! Any advice ?
Click to expand...
Click to collapse
did you get any error in any command. if you got bootloader it must work
flash xfstk again and and run these commands after extracting raw.. tell me if any of the command fails or give error
1. fastboot devices ( see if it is recognized: else plug out usb and plugin again)
2. fastboot oem erase_osip_header
3. fastboot oem start_partitioning
4. fastboot flash /tmp/partition.tbl partition.tbl
5. fastboot oem partition /tmp/partition.tbl
6. fastboot erase system
7. fastboot erase cache
8. fastboot erase data
9. fastboot erase APD
10. fastboot erase ADF
11. fastboot oem wipe splashscreen
12. fastboot oem stop_partitioning
13. fastboot flash splashscreen splash_sign.bin
14. fastboot flash token MFG_BOM_Full.bin
15. fastboot flash ifwi ifwi-prod.bin
16. fastboot flash boot boot_sign.bin
17. fastboot flash recovery recovery_sign.bin
18. fastboot flash fastboot droidboot_sign.bin
19. fastboot flash APD APD.img
20. fastboot flash system system.img
21. fastboot reboot
No errors
I flashed everything again, no errors whatsoever! The phone just wont boot! Stuck on Asus logo for an hour , then switched off the phone
Saumitraa said:
I flashed everything again, no errors whatsoever! The phone just wont boot! Stuck on Asus logo for an hour , then switched off the phone
Click to expand...
Click to collapse
Which build number raw file you use ?
Saumitraa said:
I flashed everything again, no errors whatsoever! The phone just wont boot! Stuck on Asus logo for an hour , then switched off the phone
Click to expand...
Click to collapse
send me log of cmd when you run commands
timbernot said:
Which build number raw file you use ?
Click to expand...
Click to collapse
This one : WW_ZE551ML_2.20.40.194_20160713
What the title says. I was having an issue installing magisk entirely on the Pixel 3xl root guide, so I followed ubergeek77's advice which was to >fastboot flash boot_a patched_boot.img and fastboot flash boot_b patched_boot.img) manually.
and ever since I've done that, I cant get past the fastboot menu. Please help, I really hope I didnt brick it
When I try using fastboot boot patched_boot.img, after attempted to boot, I get an error saying "FAILED Status read failed (too many links)). After which, I have to manually boot back into recovery mode.
I'm getting the errors on my pixel "no valid slot to boot", "reboot bootloader", and "error booting boot.img"
The problem is probably those patched images. I would reflash your unpatched boot images to both slots a and b. That should get you back to square one.
Then repatch using same technique, but in Magisk Manager you need to set the update channel to custom. Go to settings/update channel and select custom. Paste this address in it: https://bit.ly/2N8UVlq
That's the famous Canary channel.
Then when you go to install/install/patch boot images file, you will be using Magisk 17.4 to do the patching. That's the key.
Sent from my Pixel 3 XL using Tapatalk
how do I reflash the image in the first place? What command should I use?
Get pixel in fastboot mode. Then from command prompt type [fastboot flash boot boot.img], assuming that's the name of your boot images and it's in the same folder you opened your command prompt from.
One nice little trick there is you can just type the [fastboot flash boot ]
Then just drag your boot image file with your mouse onto the command line and it'll type in the whole path even if you stored it in a different folder with a long arcane name!
Sent from my Pixel 3 XL using Tapatalk
after I enter the command flashboot boot patched_boot" the follow outputs
>sending 'boot_b'
>writing 'boot_b'
then it says Finished, and my phone just goes into a black screen, doesnt reboot.
I need to somehow revert the fastboot flash boot_a patched_boot.img and fastboot flash boot_b patched_boot.img commands
You can do the slots independently too, and would not hurt. Just like you did for the patched image, but for the stock image.
Fastboot flash boot_a boot.img and same for b.
Sent from my Pixel 3 XL using Tapatalk
Spoke too soon, I did the boot a and boot b to the crosshatch files, and it keeps going from 95% on the device to 100% on the device and back to 95%
ajtpak said:
after I enter the command flashboot boot patched_boot" the follow outputs
>sending 'boot_b'
>writing 'boot_b'
then it says Finished, and my phone just goes into a black screen, doesnt reboot.
I need to somehow revert the fastboot flash boot_a patched_boot.img and fastboot flash boot_b patched_boot.img commands
Click to expand...
Click to collapse
You need to do the same for slot a, which is probably the slot the phone was trying to boot from.
Sent from my Pixel 3 XL using Tapatalk
Entered the commands .\fastboot flash boot_a crosshatch_boot.img (original file)
Then .\fastboot flash boot_b crosshatch_boot.img
And then tried booting the pixel. It seems to be stuck on the ring reading 100% and 95%, keeps jumping back to 95%
Got back into my device, thank you so much! I'll follow the rest of what you sent earlier with magisk now and report back.
Got it rooted now, thank you so much for your help. I thought I bricked my device. Thank you
Hi everyone,
I bought a Motorola G6 play model XT1922-3 type 374B and wanted root acces on this device.
So I started by succesfully unlocking my bootloader using the following tutorial.
After this a started tried to root the device using this tutorial.
This tutorial doesn't link to boot images anymore so I was able to find the moto-g6-play-jeter-patched-twrp.img somewhere else.
I did the following things:
- reboot to bootloader [Succesfull]
- fastboot boot moto-g6-play-jeter-patched-twrp.img [Unsuccesfull]
The device did boot the twrp image but I was unable to interact with it in any way. I couldn't swipe or press buttons.
I made a short video to show this.
I wanted to retry the whole thing so I did reboot to bootloader but then I accidently entered the following command:
fastboot flash boot moto-g6-play-jeter-patched-twrp.img picture of command prompt
After this I wasn't able to normally boot my device. When I try to do so the screen goes black and says n/a in the left corner.
Please does anyone know how I could either be able to boot my normal stock rom again or to have a rooted rom?
Kind regards Sven Onderbeke
Hi Sven,
This isn't going to be the most advanced reply, as I'm not very experienced with this stuff either, but it seems you have accidentally flashed your twrp image to 'boot', wherever that is, which is why the phone isn't able to boot to system.
Can you still boot into bootloader and recovery (twrp)?
If so, then I'd suggest using fastboot to flash a sock or custom ROM. I'm not sure exactly which one though, you have basically the same model as me and that seems to use the JETER ROMS a list of which are over here (can't post links yet, so you will just have to search on mirrors . lolnet . com /firmware/moto/jeter/official/ or remove the spaces
I seem to have somehow lost the partitions on mine, but will start a new thread question about that.
Sven Onderbeke said:
Hi everyone,
I bought a Motorola G6 play model XT1922-3 type 374B and wanted root acces on this device.
So I started by succesfully unlocking my bootloader using the following tutorial.
After this a started tried to root the device using this tutorial.
This tutorial doesn't link to boot images anymore so I was able to find the moto-g6-play-jeter-patched-twrp.img somewhere else.
I did the following things:
- reboot to bootloader [Succesfull]
- fastboot boot moto-g6-play-jeter-patched-twrp.img [Unsuccesfull]
The device did boot the twrp image but I was unable to interact with it in any way. I couldn't swipe or press buttons.
I made a short video to show this.
I wanted to retry the whole thing so I did reboot to bootloader but then I accidently entered the following command:
fastboot flash boot moto-g6-play-jeter-patched-twrp.imgpicture of command prompt
After this I wasn't able to normally boot my device. When I try to do so the screen goes black and says n/a in the left corner.
Please does anyone know how I could either be able to boot my normal stock rom again or to have a rooted rom?
Kind regards Sven Onderbeke
Click to expand...
Click to collapse
Just flash a stock boot.img to boot. Then just flash TWRP to recovery. In TWRP, format data. Type yes. Then reboot recovery. Then Use TWRP to flash magisk. Done.
Hi again Sven,
I just wanted to let you know that I just downloaded the following RETAIL ROM
ALJETER_RETAIL_9.0_PPPS29.55-35-1_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml
and used the following fastboot commands, one at a time.
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash modem NON-HLOS.bin
fastboot flash fsg fsg.mbn
fastboot flash dsp adspso.bin
fastboot flash boot boot.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash oem oem.img
fastboot flash vendor vendor.img
fastboot erase carrier
fastboot erase userdata
fastboot erase DDR
fastboot flash logo logo.bin
fastboot reboot
Which rebooted into bootloader so pressed "start" and all booted fine now. It looks like we have the same device, so hopefully that will work for you too.
Preparation:
Notes are important, please pay attention
ONLY use stock USB-A to USB-C cable
I have tried the stock cable from Axon 7, fail fail and more fail, don't make this mistake
DON'T store flash files on USB storage.
fastboot will timeout if your flash files are stored at a slow storage device such as a USB drive, or slow computer with eMMC drive
Download and extract the patched MSM download tool and related flash files (credit)
Download and extract TWRP 3.4.0-2 Test by mauronofrio (credit)
Download and extract 10.0.13-GLOBAL-OnePlus7TOxygen_14.O.19_OTA_019_all_2009281709_1026-FASTBOOT.zip (credit)
Optional: Unlock bootloader at this official OnePlus page with those steps
automated process you have to wait 1 whole week for
if you take this route, you will have an easier time get into EDL
Optional for Driver and boot into EDL: Download and extract the TOOL ALL IN ONE (credit) (untested) (can skip this step if you have driver and completed preparation step 7)
Flash Operations:
Run the MSM executable with Administrator Privilege
Boot into bootloader on 7T (if you already have adb connection, adb reboot bootloader would work as well)
Restart device: Vol Up + Power
Boot into recovery: when system reboot from step 4, immediately press and hold Vol Down + Power until recovery screen
Boot into fastboot: English -> Advanced -> fastboot
Boot into EDL on 7T
If you have OnePlus unlock token from Preparation step 7
Connect USB cable to both PC and 7T
on MSMDownloadTool, click Enum to display your device
fastboot flash cust-unlock unlock_token.bin
fastboot oem unlock
fastboot boot twrp.img
when TWRP boot: adb reboot edl
on MSMDownloadTool it will now show connected
If you don't want to wait for token (untested)
Use TOOL ALL IN ONE
Or, hold down the buttons then click start in MSM. If you release the volume buttons early it will kick you out of EDL--well at least for me. you can release the buttons once MSM starts (credit)
When MsmDownloadTool display connected, hit Start until 7T display CORRUPT message (normal behavior) and reboot into fastboot by ITSELF. If your 7T doesn't get into fastboot screen automatically, something is wrong with previous step, redo EDL flashing and do NOT proceed.
Start Power-Shell with Administrator Privilege and go to the extracted path of 10.0.13-global-oneplus7toxygen_14.o.19_ota_019_all_2009281709_1026-fastboot.zip (DO NOT USE DOS, it will fail you miserably)
Unlock bootloader: .\fastboot flashing unlock_critical (suggested, because it works, so I didn't test the oem unlock method)
To avoid potential conflict with installed fastboot binary (possibly lower version), you can either
edit the flash-all.bat, and change fastboot to .\fastboot, such that only the local fastboot binary will be invoked instead of pathed binary
OR run those identical commands with copy and paste
Code:
.\fastboot -w
.\fastboot flash boot boot.img
.\fastboot flash dtbo dtbo.img
.\fastboot flash modem modem.img
.\fastboot flash reserve reserve.img
.\fastboot flash recovery recovery.img
.\fastboot --disable-verity flash vbmeta vbmeta.img
.\fastboot --disable-verity flash vbmeta_system vbmeta_system.img
.\fastboot reboot fastboot
.\fastboot flash abl abl.img
.\fastboot flash aop aop.img
.\fastboot flash bluetooth bluetooth.img
.\fastboot flash cmnlib cmnlib.img
.\fastboot flash cmnlib64 cmnlib64.img
.\fastboot flash devcfg devcfg.img
.\fastboot flash dsp dsp.img
.\fastboot flash hyp hyp.img
.\fastboot flash imagefv imagefv.img
.\fastboot flash keymaster keymaster.img
.\fastboot flash LOGO LOGO.img
.\fastboot flash multiimgoem multiimgoem.img
.\fastboot flash odm odm.img
.\fastboot flash oem_stanvbk oem_stanvbk.img
.\fastboot flash opproduct opproduct.img
.\fastboot flash qupfw qupfw.img
.\fastboot flash storsec storsec.img
.\fastboot flash tz tz.img
.\fastboot flash uefisecapp uefisecapp.img
.\fastboot flash xbl xbl.img
.\fastboot flash xbl_config xbl_config.img
.\fastboot flash system system.img
.\fastboot flash vendor vendor.img
.\fastboot flash product product.img
.\fastboot reboot
Few notes
User data is wiped, again, lol
reserve partition flashing can produce error msg: FAILED (remote: '(reserve_a) No such partition'), it is OK but others should not Fail
Device will reboot once during the flashing process
After reboot, device will NOT go into fastboot screen but instead go into stock recovery screen, however fastboot will pick up and resume flashing the rest, ONLY IF YOU ARE UNDER POWER-SHELL, so DO NOT flash under DOS
if anything else fails besides the reserve partition, repeat step 7
Device will boot into system, you may use the OS updater to upgrade to the lastest firmware then relock bootloader or proceed with root with Magisk
Hope this will save you some precious time. Major kudos for previous contributions from post 1 and post 2.
All steps are recorded from memory, please let me know if any mistakes are in need of correction.
Tested working on Dec 5, 2020
I have followed this method (and literally anything else I can find) to a T and the farthest I get is when flashing the ROM, I get "Flashing is not allowed for critical partitions" - which I can only find people saying that means the bootloader needs to be unlocked, but it is?! It's definitely, fully unlocked. No matter what I try I can't get around that error during the flashing process and it stays stuck on the T-Mobile ROM.
I had the same issue with the critical partition error when I was under DOS and during the reboot process, 7T will only boot into the normal fastboot screen. In here, I always gets that error over and over. I stopped getting it when 7T boot into the recovery screen under power-shell.
Few things to make sure:
Stock cable
Power-shell in admin priv
Use local fastboot binary
If things still not looking up, I would try a different PC.
Good luck.
Yup, those are all correct and I have tried another PC. Now I'm scared I may have bricked it, because other than booting it into FastBoot it just loops on the "Your device is corrupted" screen. Any thoughts? It did this after I re-locked the bootloader to try unlocking Critical again.
Is your device is corrupt screen the one that gets displayed after the MSM EDL flashing?
If so, does your device auto boot into fastboot afterwards?
My thinking is after MSM tool, your device is corrupted, then you unlock critical flashing. Afterwards, the partitions being flashed in by the fastboot should prevent the corrupt msg being displayed. If you are all getting corrupt msg after the fastboot reboot, then something is off with the first part of your fastboot flashing.
It's that same screen, yes, but the phone is just stuck in a boot loop. It says "Your device is corrupt. It can't be trusted and will not boot." and goes black and says it again, over and over. It will not automatically boot to Fastboot, but if I mess with the volume/power keys, I can get it to the fastboot screen. But no matter what else I do it goes back to an endless loop with the corrupt message.
I think some error could have been carried over from the MSMDownloadTool flashing process. My 7T always auto boot into fastboot screen after the corrupt msg display without interaction on my end.
Try your EDL flashing part again, and at the same time, re-download the preparation step 4 file over again and try use that instead afterwards if you are still stuck on the boot loop, just to prevent possible discrepancies might be caused by corrupted file (unlikely, but it doesn't hurt right?)
Gotcha, thanks. Got it into EDL mode and am running MSM right now.
Okay, EDL/MSM was successful, then I tried flashing the ROM per the instructions again but got the same error of being unable to flash to Critical. It no longer does the "device is corrupt" error boot loop, but the phone ONLY boots to Fastboot now, no matter what I do.
Best of luck. Hope the pain stops for you soon, hah.
Can you post your power-shell display message for the last flash-all.bat invocation?
Also, are you using .\fastboot flashing unlock_critical in admin priv power-shell to unlock the bootloader after MSM flashing?
Yes, that's what I was using. Unlocking it wasn't an issue, and when I try any type of unlock command it says it's already unlocked, which I believe to be true. But it still refuses to write to critical.
I can post my powershell message when I get back home. But basically it ran fine at first, it did fail at the "reserve" portion which I read to be normal, but after that it kept saying cannot flash to critical.
I just got the phone today so I hope it's not already bricked. But the fact that I got it out of the "corrupt" loop gives me hope I can fix it. Is there any place to download the stock T-Mobile ROM so I can try and start over? Assuming it will even let me flash it. I couldn't find any by searching.
One observation I found to be very interesting.
The device should have been locked by the MSM tool through EDL flashing; yet, your device shows it's already unlocked.
I think the issue is still with your EDL flashing process as it should lock the bootloader then use flashing unlock critical to prevent critical partition flashing errors.
Also, your device is not bricked as long as you can still perform EDL flash. Just kept going and you can get it working without having to EDL flash anything else.
I see, thanks for the insight. So just so I don't mess anything up further, exactly what steps in what order do you recommend I perform?
My first instinct is to keep trying the EDL flashing until you can perform flashing critical unlock properly.
If things keep on failing, try to change your PC, driver, or other environmental variables.
It's just a painful process of elimination that you have to stick to.
Also, unless there are potential hardware issues, flashing like this shouldn't carry any more risk to brick your device compare to just using your device regularly. You aren't changing the hardware/software that is responsible for facilitating EDL.
EDL is fine, unlock_critical is fine, but flash-all gives me the same 'Flashing is not allowed for Critical Partitions' error on some partitions, and then I get stuck on the T-Mobile boot screen after. I'd think it wouldn't be the TMo screen by that point, right?
I've gone through this twice with the OEM cable and a different cable. The device was up to date with the latest TMo OTA before I started.
I'm about to try the TMo MSM to see if I can get it back to a working state.
Do you want to wipe all the data ( Reccomended )[Y/N]?nSending 'boot_a' (98304 - Pastebin.com
Pastebin.com is the number one paste tool since 2002. Pastebin is a website where you can store text online for a set period of time.
pastebin.com
seryniti said:
EDL is fine, unlock_critical is fine, but flash-all gives me the same 'Flashing is not allowed for Critical Partitions' error on some partitions, and then I get stuck on the T-Mobile boot screen after. I'd think it wouldn't be the TMo screen by that point, right?
I've gone through this twice with the OEM cable and a different cable. The device was up to date with the latest TMo OTA before I started.
I'm about to try the TMo MSM to see if I can get it back to a working state.
Do you want to wipe all the data ( Reccomended )[Y/N]?nSending 'boot_a' (98304 - Pastebin.com
Pastebin.com is the number one paste tool since 2002. Pastebin is a website where you can store text online for a set period of time.
pastebin.com
Click to expand...
Click to collapse
Edit:
[GUIDE][WIP]T-Mobile Brand Conversion to Rooted Global Firmware
First, let me say that this is only an attempt to pull this information out from a lot of different threads that require a bunch of research and a lot of institutional knowledge of Android. The idea of this thread is going from 100% T-Mobile...
forum.xda-developers.com
Apparently I'm not getting into FastbootD, so it's not flashing on the proper place. I'm going to try again. I noticed earlier when it runs "fastboot reboot fastboot" it's not working properly.
seryniti said:
Edit:
[GUIDE][WIP]T-Mobile Brand Conversion to Rooted Global Firmware
First, let me say that this is only an attempt to pull this information out from a lot of different threads that require a bunch of research and a lot of institutional knowledge of Android. The idea of this thread is going from 100% T-Mobile...
forum.xda-developers.com
Apparently I'm not getting into FastbootD, so it's not flashing on the proper place. I'm going to try again. I noticed earlier when it runs "fastboot reboot fastboot" it's not working properly.
Click to expand...
Click to collapse
Let me know what you find. I didn't even know there was other versions of MSM so I'll try that as well. I'd love to just at least get mine out of only being able to boot to Fastboot.
seryniti said:
Edit:
[GUIDE][WIP]T-Mobile Brand Conversion to Rooted Global Firmware
First, let me say that this is only an attempt to pull this information out from a lot of different threads that require a bunch of research and a lot of institutional knowledge of Android. The idea of this thread is going from 100% T-Mobile...
forum.xda-developers.com
Apparently I'm not getting into FastbootD, so it's not flashing on the proper place. I'm going to try again. I noticed earlier when it runs "fastboot reboot fastboot" it's not working properly.
Click to expand...
Click to collapse
Your 7T should be on the stock recovery screen when fastboot reboot fastboot completes. If your device boots into T-Mobile boot screen or bootloader, something is wrong with your env on PC.
You should never see T-Mobile boot screen at any given time during fastboot flashing process.
The final reboot should complete the conversion and boot into the intentional version OS.