I had a M build from the original D which I flashed and I saw the LTE was no different from the L so I tried to go back to MDA..D and I made an error or the file was corrupted as all I have is a large white Google. I can get to the bootloader and lock/unlock it but when it is unlocked there is an error message about unable to check corrupted files and press Pause and when I did that it still had message and to press Continue and still it only will go back to the large Google ?
Is my phone beyond repair now as I tried your toolkit and must not have chosen the right options as there is no escaping the White google screen?
I have used and supported your toolkit since the Nexus 5 days but now I am really stumped..
just fastboot flash the factory images. you should be good to go since you can get into the bootloader.
painfree said:
I had a M build from the original D which I flashed and I saw the LTE was no different from the L so I tried to go back to MDA..D and I made an error or the file was corrupted as all I have is a large white Google. I can get to the bootloader and lock/unlock it but when it is unlocked there is an error message about unable to check corrupted files and press Pause and when I did that it still had message and to press Continue and still it only will go back to the large Google ?
Is my phone beyond repair now as I tried your toolkit and must not have chosen the right options as there is no escaping the White google screen?
I have used and supported your toolkit since the Nexus 5 days but now I am really stumped..
Click to expand...
Click to collapse
Like the guy above said to fastboot the factory image.
See the link below, follow step 9
fastboot flash bootloader C:\angler\images\bootloader-angler-angler-xx.xx.img
fastboot reboot-bootloader
fastboot flash radio C:\angler\images\radio-angler-angler-xx.xx.img
Also note in these commands that the xx.xx.img, the xx's are numbers. Just make sure you change the xx to whatever the number is. It will vary depending on version you flash.
http://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928
So you are saying that the Skipsoft Toolkit is NOT able to resolve this situation by using any of its options?
painfree said:
So you are saying that the Skipsoft Toolkit is NOT able to resolve this situation by using any of its options?
Click to expand...
Click to collapse
Why use a toolkit in the first place? As you've found out they're more trouble than they're worth. Plus, with a Nexus you really shouldn't need one anyway, these phones are simple to work with. Check out my guide, it has everything you need to know:
http://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928
Heisenberg said:
Why use a toolkit in the first place? As you've found out they're more trouble than they're worth. Plus, with a Nexus you really shouldn't need one anyway, these phones are simple to work with. Check out my guide, it has everything you need to know:
http://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928
Click to expand...
Click to collapse
I am using windows 10 and I cannot for the life of me figure out the file locations .. How do I do a simple thing as find a file called fastboot.exe on my PC using windows 10 ? this is what I have so far :
http://screencast.com/t/qhapdJk8
I have no idea where bootloader.exe is located and I cannot figure out how to do a simple file search on Windows 10. As a result I cannot open up a command prompt there if I cannot find it..
painfree said:
I am using windows 10 and I cannot for the life of me figure out the file locations .. How do I do a simple thing as find a file called fastboot.exe on my PC using windows 10 ? this is what I have so far :
http://screencast.com/t/qhapdJk8
I have no idea where bootloader.exe is located and I cannot figure out how to do a simple file search on Windows 10. As a result I cannot open up a command prompt there if I cannot find it..
Click to expand...
Click to collapse
Did you follow the instructions in the beginning of the thread to install the SDK and in turn install adb/fastboot? I make no mention of bootloader.exe so I'm not sure where you're getting that from, there's no such thing, you don't know what the bootloader is? It might be a good idea for you to read the prerequisites section and the quick tips section at the beginning of the first post, and the FAQ section in the second post.
Heisenberg said:
Did you follow the instructions in the beginning of the thread to install the SDK and in turn install adb/fastboot? I make no mention of bootloader.exe so I'm not sure where you're getting that from, there's no such thing, you don't know what the bootloader is? It might be a good idea for you to read the prerequisites section and the quick tips section at the beginning of the first post, and the FAQ section in the second post.
Click to expand...
Click to collapse
yes I completed part 1 with all the command prompt tests and someone said to skip to step 9... I read this regarding bootloader and I assumed it was an exe file.. sorry..
"Like the guy above said to fastboot the factory image.
See the link below, follow step 9
fastboot flash bootloader C:\angler\images\bootloader-angler-angler-xx.xx.img
fastboot reboot-bootloader
fastboot flash radio C:\angler\images\radio-angler-angler-xx.xx.img
Also note in these commands that the xx.xx.img, the xx's are numbers. Just make sure you change the xx to whatever the number is. It will vary depending on version you flash.
http://forum.xda-developers.com/nexu...nners-t3206928 "
painfree said:
yes I completed part 1 with all the command prompt tests and someone said to skip to step 9... I read this regarding bootloader and I assumed it was an exe file.. sorry..
"Like the guy above said to fastboot the factory image.
See the link below, follow step 9
fastboot flash bootloader C:\angler\images\bootloader-angler-angler-xx.xx.img
fastboot reboot-bootloader
fastboot flash radio C:\angler\images\radio-angler-angler-xx.xx.img
Also note in these commands that the xx.xx.img, the xx's are numbers. Just make sure you change the xx to whatever the number is. It will vary depending on version you flash.
http://forum.xda-developers.com/nexu...nners-t3206928 "
Click to expand...
Click to collapse
Are you following my instructions as they're written? They're very thorough so should be easy to follow.
Heisenberg said:
Are you following my instructions as they're written? They're very thorough so should be easy to follow.
Click to expand...
Click to collapse
OK I am back to system but there is a message about internal system problem yet it is factory now. .." Android System There's an internal problem with your device. Contact your manufacturer for details"
painfree said:
OK I am back to system but there is a message about internal system problem yet it is factory now. .." Android System There's an internal problem with your device. Contact your manufacturer for details"
Click to expand...
Click to collapse
Which images did you flash? And which build?
Heisenberg said:
Which images did you flash? And which build?
Click to expand...
Click to collapse
fastboot flash bootloader C:\angler\images\bootloader-angler-angler-
01.31.img
fastboot reboot-bootloader
fastboot flash radio C:\angler\images\radio-angler-angler-01.29.img
fastboot reboot-bootloader
fastboot flash boot C:\angler\images\boot.img
fastboot erase cache
fastboot flash cache C:\angler\images\cache.img
fastboot flash recovery C:\angler\images\recovery.img
fastboot flash system C:\angler\images\system.img
fastboot flash vendor C:\angler\images\vendor.img
MDA089D I have t mobile and all the other builds K L M crippled my in home reception..
painfree said:
fastboot flash bootloader C:\angler\images\bootloader-angler-angler-
01.31.img
fastboot reboot-bootloader
fastboot flash radio C:\angler\images\radio-angler-angler-01.29.img
fastboot reboot-bootloader
fastboot flash boot C:\angler\images\boot.img
fastboot erase cache
fastboot flash cache C:\angler\images\cache.img
fastboot flash recovery C:\angler\images\recovery.img
fastboot flash system C:\angler\images\system.img
fastboot flash vendor C:\angler\images\vendor.img
MDA089D I have t mobile and all the other builds K L M crippled my in home reception..
Click to expand...
Click to collapse
Ok, but you're able to actually boot into Android, right? Or are you not able to? If you're able to it's probably worth trying a factory reset (Settings>Backup & Reset>Factory Data Reset).
Heisenberg said:
Ok, but you're able to actually boot into Android, right? Or are you not able to? If you're able to it's probably worth trying a factory reset (Settings>Backup & Reset>Factory Data Reset).
Click to expand...
Click to collapse
I am able to set up the phone as I normally would but my replacement via RMA just arrived so I will be sending this one back but now I know to avoid the toolkits.
Related
Hi all,
my nexus wont start after (failed?!) flashing with factory image. bootloader and recovery mode are accessable. i have no backup so i need to flash a new img, but my tablet wont be recognized by my computer anymore(adb drivers not working?!). i tried to deinstall and reinstall the adb drivers alrdy. Device manager shows nexus 7 as Android Phone with "Android Bootloader interface" i cant install adb drivers while in bootloader. in recovery mode i succeeded installing the adb drivers and the tablet is shown correctly in device manager... i need help dont know what to do :crying: .. any suggestions ?
ADB and fastboot drivers are different.
Pirateghost said:
ADB and fastboot drivers are different.
Click to expand...
Click to collapse
yes .. what are u trying to tell me? dont get it.. i used nexus root toolkit to help me apply those drivers.. but it wont work for bootloader/fastboot mode.. i cant flash my tablet because my device wont be recognized by my pc.. im stuck at the bootloaderscreen/fastbootmode....
http://bit.ly/Zqk7pm
and what do u want me to type in there ? i alrdy used google for the last 7 hours ?
oads said:
and what do u want me to type in there ? i alrdy used google for the last 7 hours ?
Click to expand...
Click to collapse
SMH
i filled it in for you.....
Pirateghost said:
SMH
i filled it in for you.....
Click to expand...
Click to collapse
ok sry wasnt patient enough to see... ya well this all makes sense to someone who knows what hes doing but to a noob like me? i thought i alrdy installed fastboot drivers since i unrooted the device a month ago? do i need to deinstall the driver "Android Phone with "Android Bootloader interface"" in device manager first, before applying the new fastboot drivers? pls help me through this i think i damaged enough alrdy ..
no. ADB and fastboot require separate drivers. just install the drivers required for n7 fastboot. there was a link in that list.
there are tutorials here on xda, as well as youtube videos and tutorials on other sites. take a little initiative and learn the ropes. it will help you out later on.
oads said:
ok sry wasnt patient enough to see... ya well this all makes sense to someone who knows what hes doing but to a noob like me? i thought i alrdy installed fastboot drivers since i unrooted the device a month ago? do i need to deinstall the driver "Android Phone with "Android Bootloader interface"" in device manager first, before applying the new fastboot drivers? pls help me through this i think i damaged enough alrdy ..
Click to expand...
Click to collapse
Just relax and take your time.
If your tablet can go into fastboot mode, it is fine and will get better; the only thing standing between it's current state and being brought back to life is a little learning on your part.
Now you see what the problems are with using a toolkit - because they hide all the gory details from you, when the smallest thing goes wrong you are totally helpless due to a lack of understanding about what things are going on underneath the hood. And as it turns out, what "goes on under the hood" isn't really all that complicated either if you do things the full manual way.
Which is not to say that you can not simply just use the toolkit again; if you previously successfully installed drivers that allowed you to talk to the tablet in all of these modes:
- fastboot
- adb w/ custom recovery booted
- adb with Android booted
then it is not evident that you need to be fooling with drivers.
I suggest you read this thread, from start to finish
[GUIDE] Flashing a Factory Image with fastboot / return to stock
Then, go over to your toolkit thread and read it from start to finish. You will see that there are & have been plenty of people in circumstances nearly identical to yours.
good luck
hey thx for ur replies! im a lil more calm now than i was 30 min !
the big problem i still have is that my tablet will show up as Androidphone/Android Bootloader Interface not as an unknown device or as the Nexus 7 it is when i plug it in.. so i cant install the drivers am i correct? well i tried it a few times .. deinstalled and reinstalled .. the problem persists? anyone familiar with that? when i change into Recovery Modus it will show up as Androidphone/Google Nexus ADB Interface.. so my first steps to get rid of this mess would be ...?
oads said:
hey thx for ur replies! im a lil more calm now than i was 30 min !
the big problem i still have is that my tablet will show up as Androidphone/Android Bootloader Interface not as an unknown device or as the Nexus 7 it is when i plug it in.. so i cant install the drivers am i correct? well i tried it a few times .. deinstalled and reinstalled .. the problem persists? anyone familiar with that? when i change into Recovery Modus it will show up as Androidphone/Google Nexus ADB Interface.. so my first steps to get rid of this mess would be ...?
Click to expand...
Click to collapse
that does not sound like a problem to me at all.
You communicate with the device using the "fastboot" program when it is in bootloader/fastboot mode, and with the "adb" program when it is in custom recovery boot.
What you see in the device manager appears to be completely normal - In different modes it shows up in different places. It's not supposed to show up with the same driver in different modes.
Code:
fastboot devices
will show you whether you are communicating successfully with the device when it is in bootloader/fastboot mode, and
Code:
adb devices
will show you whether you are communicating successfully with the device in recovery mode.
I suppose your toolkit has some stoopid menu or buttons someplace that will allow you to test for exactly the same thing. Now all you need to do is stop posting here and read a little bit.
good luck
bftb0 said:
Now all you need to do is stop posting here and read a little bit.
good luck
Click to expand...
Click to collapse
well i did read quite a lot today :crying: i cant find my device when i type in adb devices, im pretty sure i have the right drivers installed since i followed the instructions step by step.
this guy seems to have the same problem: http://forum.xda-developers.com/showthread.php?t=1808076
could someone tell me if this could be a possible solution :http://stackoverflow.com/questions/...e-over-usb-via-adb-devices-from-windows-7-x64
also would it be possible to just get into the bootloader (since thats the purpose of adb drivers and i can do this) and just proceed with fastboot commands ? if i type in fastboot devices the tablet will show up...
In your first post, you indicated that you couldn't connect to the tablet that was in bootloader mode with adb.
And then you were told - once vaguely and once quite specifically - that *nobody* can communicate with the tablet using adb when the tablet is in bootloader/fastboot mode.
As stated previously, use the "fastboot" program when the tablet is in bootloader mode, and use the "adb" program when the tablet is booted to the custom recovery (or the regular android boot if USB debugging has been enabled).
You can use either one of these modes to effect a rescue so long as they are working correctly - they don't need to both be working. Eventually you would want that to be the case, but for the moment why don't you just stick with what is working for you.
If you get a device ID printed when you execute "fastboot devices" when the tablet is in boot loader/fastboot mode, that is all you need to reinstall a factory ROM, using nothing but fastboot.
thx for pointing me in the right direction! so i started flashing with the fastboot commands... as soon i get to: fastboot flash radio radio-tilapia-1231_0.17.0_1025.img
i receive:
error: cannot load 'radio-tilapia-1231_0.17.0_1025.img': No error
any clues? thx in advance
edit:using 4.2.2 factory rom for nexus 7 3g
oads said:
thx for pointing me in the right direction! so i started flashing with the fastboot commands... as soon i get to: fastboot flash radio radio-tilapia-1231_0.17.0_1025.img
i receive:
error: cannot load 'radio-tilapia-1231_0.17.0_1025.img': No error
any clues? thx in advance
edit:using 4.2.2 factory rom for nexus 7 3g
Click to expand...
Click to collapse
Well, I can't see what instructions you are following, and there is a possibility of sensitivity to an exact sequence. In particular, is a
fastboot reboot-bootloader
performed after the bootloader is flashed, but before the radio is flashed? It might be important that you are performing the radio flash from one bootloader vs. the other. Just a guess. (Along the same lines, do you see something unexpected happening, such as a boot to the recovery after the radio flash command?)
There are some other threads on this I think. (I have a grouper device not tilapia) But I thought that those threads were about problems with radio flashing when a custom recovery (rather than a stock recovery) was on the phone, but that was for applying the OTA package for tilapia rather than flashing directly from fastboot.
-------------------------------------------------------
[Edit] whoops, wait a minute.... "cannot load"
When you run fastboot from the command line, the file names you give are relative to the current directory. Did you move those image files into the same directory that you are executing the "fastboot" command from?
Alternately you can specify the full pathname to wherever you unpacked the files, for instance
fastboot flash radio C:\myfolder\unpacked\googlen7\4.2.2\radio-tilapia-1231_0.17.0_1025.img
hi! basically im following this guide http://forum.xda-developers.com/showthread.php?t=1907796!
GSM/HSPA+ devices (nakasig)
Code:
> fastboot erase boot
> fastboot erase cache
> fastboot erase recovery
> fastboot erase system
> fastboot erase userdata
> fastboot flash bootloader bootloader-tilapia-4.18.img
> fastboot reboot-bootloader
> fastboot flash radio radio-tilapia-1231_0.17.0_1025.img
> fastboot reboot-bootloader
> fastboot -w update image-nakasig-jdq39.zip
its all good till i want to flash the radio. The .img is in the correct folder, just tried it again... could it be broken? should i try a other factory update like 4.2.1?
oads said:
hi! basically im following this guide http://forum.xda-developers.com/showthread.php?t=1907796!
GSM/HSPA+ devices (nakasig)
Code:
> fastboot erase boot
> fastboot erase cache
> fastboot erase recovery
> fastboot erase system
> fastboot erase userdata
> fastboot flash bootloader bootloader-tilapia-4.18.img
> fastboot reboot-bootloader
> fastboot flash radio radio-tilapia-1231_0.17.0_1025.img
> fastboot reboot-bootloader
> fastboot -w update image-nakasig-jdq39.zip
its all good till i want to flash the radio. The .img is in the correct folder, just tried it again... could it be broken? should i try a other factory update like 4.2.1?
Click to expand...
Click to collapse
I would complete the rest of the steps first and see if everything is still working. Your device *should* still work just fine with an old radio firmware. (Boot it up and see what radio firmware the OS reports on the Settings... about device... status page).
I'll pull down the tilapia image and tell you what MD5 I observe for the radio image.
just to verify, you actually have the 3g/4g model? or just the wifi only model. if wifi only, there is no radio
Pirateghost said:
just to verify, you actually have the 3g/4g model? or just the wifi only model. if wifi only, there is no radio
Click to expand...
Click to collapse
yes
SHA1
0798439d363beb145d9223a42ed9edf3de1a30f4 nakasig-jdq39-factory-0798439d.tgz
bb824d449f44d2ad43c5d2a463fe1244d2faf525 nakasig-jdq39/radio-tilapia-1231_0.17.0_1205.img
f406ae9133c56200306d5c7d64d151f21e0be3c4 nakasig-jdq39/image-nakasig-jdq39.zip
MD5
ee8db1ed6ff1c007fe12136d4bc65cd8 nakasig-jdq39-factory-0798439d.tgz
276cb738e5b9e18a088b6a3eef8155ad nakasig-jdq39/radio-tilapia-1231_0.17.0_1205.img
4cfa996b6513a7fa53db7cbfd1134396 nakasig-jdq39/image-nakasig-jdq39.zip
radio image is 16,777,216 bytes long
---------- Post added at 05:43 PM ---------- Previous post was at 05:40 PM ----------
the google - provided instructions (flash-all.sh) have 10 second sleeps after the bootloader resets - are you waiting long enough?
fastboot oem unlock
fastboot erase boot
fastboot erase cache
fastboot erase recovery
fastboot erase system
fastboot erase userdata
fastboot flash bootloader bootloader-tilapia-4.18.img
fastboot reboot-bootloader
sleep 10
fastboot flash radio radio-tilapia-1231_0.17.0_1205.img
fastboot reboot-bootloader
sleep 10
Also - something to check since you are rebooting the bootloader - does the device show up correctly in the Windows device manager? (Sometimes with soft reboots I have found the need to pull the USB cable and plug it back in to the PC).
Hello gents,
After messing around with the fastboot yesterday i got back to stock Android and realised i have only a 5GB partition....
I formatted the phone and installed again the stock Rom but that didn't work.
Anybody as any idea on how to solve this problem? thanks:good:
Anyone?
Fix for 16GB N4 showing as 8GB
I just experienced the same exact problem, and wasn't able to find a solution until I followed this guide: http://forum.xda-developers.com/showthread.php?t=2033692
Make sure you have the latest occam image https://developers.google.com/android/nexus/images#occam
Use 7-Zip to extract the files from within the .tgz file, and then the .tar file.
Shift + Right Click in the folder to Open a Command Prompt, and run the following commands:
Code:
fastboot erase boot
fastboot erase cache
fastboot erase recovery
fastboot erase system
fastboot erase userdata
fastboot flash bootloader bootloader-mako-makoz20i.img
fastboot reboot-bootloader
fastboot -w update image-occam-jwr66y.zip
jsteg94 said:
I just experienced the same exact problem, and wasn't able to find a solution until I followed this guide: http://forum.xda-developers.com/showthread.php?t=2033692
Make sure you have the latest occam image https://developers.google.com/android/nexus/images#occam
Use 7-Zip to extract the files from within the .tgz file, and then the .tar file.
Shift + Right Click in the folder to Open a Command Prompt, and run the following commands:
Code:
fastboot erase boot
fastboot erase cache
fastboot erase recovery
fastboot erase system
fastboot erase userdata
fastboot flash bootloader bootloader-mako-makoz20i.img
fastboot reboot-bootloader
fastboot -w update image-occam-jwr66y.zip
Click to expand...
Click to collapse
Its a common error after flashing the factory images and all you usually have to do is this:
-Boot into STOCK RECOVERY (If you are running a custom recovery you must flash to stock)
-Clear cache
-Factory reset
which is right at the top of el daddy's thread
kzoodroid said:
Its a common error after flashing the factory images and all you usually have to do is this:
-Boot into STOCK RECOVERY (If you are running a custom recovery you must flash to stock)
-Clear cache
-Factory reset
which is right at the top of el daddy's thread
Click to expand...
Click to collapse
Thanks, kzoodroid. I didn't realize that you had to be in Stock Recovery. Every time I followed the above steps on el daddy's thread, I was using TWRP, which never solved the problem.
Well i´ve been trying and trying... its simple to follow the guide but wen i get to this step fastboot -w update image-occam-jdq39.zip the CMD crashes all the time...
I´ve restarted the computer and everything but it crashes always...
And also i can´t get into stock recovery... The droid with the triangle come up the i press power and then vol up but nothing happends...
Yeah, i think i just found a easy way to go around this problem!
Very simple:
1. After flashing the stock rom use Nexus Root Toolkit to do a OEM Lock
2. Run CMD fastboot and use this command: fastboot oem unlock. You will see a prompt on your device. This will wipe your entire device (including the /sdcard folder). Accept.
3 Restart and that's it! Your back to 13GB again
Thanks to all for your help. I will share this info on El Daddy thread.
SWEagle said:
Yeah, i think i just found a easy way to go around this problem!
Very simple:
1. After flashing the stock rom use Nexus Root Toolkit to do a OEM Lock
2. Run CMD fastboot and use this command: fastboot oem unlock. You will see a prompt on your device. This will wipe your entire device (including the /sdcard folder). Accept.
3 Restart and that's it! Your back to 13GB again
Thanks to all for your help. I will share this info on El Daddy thread.
Click to expand...
Click to collapse
I've had this issue come up more times than I can count, and just the other day I wasn't able to get back to the full storage allotment after several attempts following the steps to erase all the partitions and reflash. I did exactly what you did by flashing the factory images, re-locking the bootloader, then unlocking it again, and my storage was back to normal. I'm not exactly sure what happened, but I discovered this works, just as you did
hp420 said:
I've had this issue come up more times than I can count, and just the other day I wasn't able to get back to the full storage allotment after several attempts following the steps to erase all the partitions and reflash. I did exactly what you did by flashing the factory images, re-locking the bootloader, then unlocking it again, and my storage was back to normal. I'm not exactly sure what happened, but I discovered this works, just as you did
Click to expand...
Click to collapse
Cool! :laugh:
SWEagle said:
Well i´ve been trying and trying... its simple to follow the guide but wen i get to this step fastboot -w update image-occam-jdq39.zip the CMD crashes all the time...
I´ve restarted the computer and everything but it crashes always...
And also i can´t get into stock recovery... The droid with the triangle come up the i press power and then vol up but nothing happends...
Click to expand...
Click to collapse
With my phone I have to press power and volume+ a bunch of times to get it to finally go into stock recovery it never does it on the first few tries and can take a few minutes of playing to hit them perfectly to get it to open.
SWEagle said:
Yeah, i think i just found a easy way to go around this problem!
Very simple:
1. After flashing the stock rom use Nexus Root Toolkit to do a OEM Lock
2. Run CMD fastboot and use this command: fastboot oem unlock. You will see a prompt on your device. This will wipe your entire device (including the /sdcard folder). Accept.
3 Restart and that's it! Your back to 13GB again
Thanks to all for your help. I will share this info on El Daddy thread.
Click to expand...
Click to collapse
Wow, that's actually a lot easier. Thanks for finding a simpler way, SWEagle! I'll try that next time.
jsteg94 said:
Wow, that's actually a lot easier. Thanks for finding a simpler way, SWEagle! I'll try that next time.
Click to expand...
Click to collapse
Instead of using the toolkit you probably could just use fastboot to lock the device too.
fastboot oem lock
kzoodroid said:
Instead of using the toolkit you probably could just use fastboot to lock the device too.
fastboot oem lock
Click to expand...
Click to collapse
I thought about that too. It might work. If it does it's even easier
The aim of this thread is to make an easy guide to flashing stock firmware. Owners of previous nexus devices already know all this stuff, this thread is aimed at making the process as simple as possible for new users. This will work regardless of what modifications you've done to your device. Remember to backup all your important data and do this with the knowledge that all flashing activity carries some risk.
Download
Factory image here
(for windows users) Minimal adb & fastboot
(for mac users) adb & fastboot for mac
Follow the instructions to install adb on your computer.
Prepare your tablet
Enable developer options in settings > about tablet and tapping build number 7 times
Open developer options and enable usb debugging. (If you haven't unlocked your bootloader yet, tick enable oem unlock)
Extract images
Place the downloaded factory image inside your adb folder and extract with 7zip.
A new folder will be there called something like volantis-lrx21. Open and extract "image-xxxxx-zip" to your adb folder. We are interested in these files:
bootloader-flounder-xxxxxx.img
boot.img
recovery.img
cache.img
system.img
vendor.img
Place these files directly into your adb folder.
# I recommend renaming the 'bootloader-flounder-xxxxxx.img' to just 'bootloader.img' to make it easier to type.
Now that everythings set up, we can start flashing
Plug in your device. Open the adb folder, hold shift and right click and select open command window here
(if your having driver issues try using Pdanet)
Run these commands one at a time
Code:
adb devices
adb reboot bootloader
if you haven't unlocked the bootloader yet run
Code:
fastboot oem unlock
and follow the instructions using the volume keys to scroll through the menu. This procedure will wipe all data.
Run the following commands one at a time
Code:
fastboot flash bootloader bootloader-flounder-xxxxxxx.img
[B] [I](replace 'bootloader-flounder-xxxxx.img' with full name of bootloader image[/I])[/B]
fastboot reboot-bootloader
fastboot -w
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash cache cache.img
fastboot flash system system.img
fastboot flash vendor vendor.img
(OPTIONAL) At this stage you can relock the bootloader if you want by running the command
Code:
fastboot oem lock
finally reboot the device by running
Code:
fastboot reboot
Thats it. Enjoy your tablet in factory condition
Great. Is it possible to make a batch file to run all the commands at once?
albsat said:
Great. Is it possible to make a batch file to run all the commands at once?
Click to expand...
Click to collapse
There is already a flash all batch script that comes with the firmware files but I've noticed that some people have problems with it so I decided not to include it. It should work fine most of the time.
i am long-time familiar with htc,but new to nexus. i was looking thru a couple downloaded factory image files and having noticed that "rebootRUU" is an oem command,and that "image-xxxxx-zip" contains an android info document,i am curious if anyone has tried flashing image-xxxxx-zip as a zip file,in ruu mode?
Cool, thanks for the information.
Thanks for creating this! Will come in handy. Saving this for later
This has been useful as the update from 5.0.1 to 5.0.2 kept failing on my rooted device. It was successful and educational.
scotty1223 said:
i am long-time familiar with htc,but new to nexus. i was looking thru a couple downloaded factory image files and having noticed that "rebootRUU" is an oem command,and that "image-xxxxx-zip" contains an android info document,i am curious if anyone has tried flashing image-xxxxx-zip as a zip file,in ruu mode?
Click to expand...
Click to collapse
I indeed tried this as a last chance hoping it would bypass bootloader lock protection. It didn't work since I think the factory image is not signed by HTC as RUU are . It also lead to a fastboot crash. Now sending my nexus 9 for RMA
Sent from my HTC One using XDA Free mobile app
remedya said:
This has been useful as the update from 5.0.1 to 5.0.2 kept failing on my rooted device. It was successful and educational.
Click to expand...
Click to collapse
Same here. The manual flash method worked very well. Here's hoping that Google doesn't muck 5.1
cant flash stock rom
I'm trying to downgrade my nexus 9 from DU rom 5.1.1 to stock for everything. I'm running the flash-all.sh on linux while my tablet is in bootloader mode. Tab makes and few checks and reboots automatically in bootloader mode. I reboot tablet and still has the DU rom. Any tips
nyasha1935 said:
I'm trying to downgrade my nexus 9 from DU rom 5.1.1 to stock for everything. I'm running the flash-all.sh on linux while my tablet is in bootloader mode. Tab makes and few checks and reboots automatically in bootloader mode. I reboot tablet and still has the DU rom. Any tips
Click to expand...
Click to collapse
The flash all script doesn't seem to work on linux. You shouldn't have a problem if you write the commands out manually.
nyasha1935 said:
I'm trying to downgrade my nexus 9 from DU rom 5.1.1 to stock for everything. I'm running the flash-all.sh on linux while my tablet is in bootloader mode. Tab makes and few checks and reboots automatically in bootloader mode. I reboot tablet and still has the DU rom. Any tips
Click to expand...
Click to collapse
Art Vanderlay said:
The flash all script doesn't seem to work on linux. You shouldn't have a problem if you write the commands out manually.
Click to expand...
Click to collapse
As indicated, the flash all script doesn't work very well on any system. Flash each .img separately via fastboot.
cam30era said:
As indicated, the flash all script doesn't work very well on any system. Flash each .img separately via fastboot.
Click to expand...
Click to collapse
Problem is that the tgz is too big for the device's buffer, so it craps out before it actually writes the images. Its been this way for a while over several different nexus devices. Kind of like nobody at google ever even bothered to test the process.
doitright said:
Problem is that the tgz is too big for the device's buffer, so it craps out before it actually writes the images. Its been this way for a while over several different nexus devices. Kind of like nobody at google ever even bothered to test the process.
Click to expand...
Click to collapse
I agree.
I also used Linux but I executed the commands individually rather than using the script. It worked.
remedya said:
I also used Linux but I executed the commands individually rather than using the script. It worked.
Click to expand...
Click to collapse
I cant flash system.img I get error
sending 'system' (1108544 KB)...
FAILED (remote: data length is too large)
finished. total time: 0.105s
nyasha1935 said:
I cant flash system.img I get error
sending 'system' (1108544 KB)...
FAILED (remote: data length is too large)
finished. total time: 0.105s
Click to expand...
Click to collapse
Update your Android SDK.
These instructions also worked with 5.1.1
im trying to install back to facctory i erased my system and recovery and data and now when i try to flash bootloader i get error cannot open bootloader someone please im stuck in bootloader mode
maxtcee said:
im trying to install back to facctory i erased my system and recovery and data and now when i try to flash bootloader i get error cannot open bootloader someone please im stuck in bootloader mode
Click to expand...
Click to collapse
Are you writing the full name and file path for the bootloader img?
This guide will help you unlock your bootloader, flash a factory image, and return you to a stock device. It is wriiten assuming you have a windows PC (MAC users, see post 2). This can be helpful if you need to RMA your device or if you are getting erratic behavior or messed something up.
Tools and Files You’ll Need
If you don’t have adb and fastboot installed on your PC go here for a quick install of the necessary files, thanks to @Snoop05, http://forum.xda-developers.com/showthread.php?t=2588979
For MAC users go here. http://forum.xda-developers.com/showthread.php?p=32305619
For Linux users, http://forum.xda-developers.com/showthread.php?p=10746225
For the factory image go here, https://developers.google.com/android/nexus/images You’ll download a .tgz file. Use winrar or 7-zip to extract the file to its own directory and remember where that directory is. Inside is another zip file, extract that too. You’ll need those image files if you use the long method to install the factory image. It’s also good to know where they are as they come in handy as you get more familiar with fastboot and what you can do with it.
How To Unlock the Bootloader
If you don’t have developer options enabled on your device go to settings, about device and tap on the build number 7 times.
In settings, developer options enable oem unlock
Now you get to use fastboot! Boot you device into the bootloader, vol up + power with your device shut off. Once booted into the bootloader connect it to your PC with the usb cable and open a command window on your PC. Once connected type the following command in the cmd window:
fastboot devices (Your device serial number should show up and this will ensure fastboot is working properly)
Then type:
fastboot oem unlock (This will unlock the bootloader and you’re now good to go)
NOTE, UNLOCKING THE BOOTLOADER DOES WIPE YOUR DEVICE SO BACKUP OFF YOUR DEVICE FIRST
How To Flash the Factory Image, SHORT METHOD
Open a command window on your PC in the same directory as you extracted the factory image. In that directory shift, right click in an open area and use “Open a command window here”
Boot your device into the bootloader and connect it to your PC. Then simply double click on the flash-all batch file. Note that there are batch files in there that will work for Windows as well as Linux machines
Let the batch file run and when it’s done you’ll be back to stock.
NOTE THAT FLASHING BY THIS METHOD DOES WIPE YOUR DEVICE SO MAKE SURE YOU BACKUP OFF YOUR DEVICE FIRST.
How To Flash the Factory Image, LONG METHOD
In this method each factory image is flashed separately. This should be used if you have problems with the short method and as you get more familiar with fastboot you’ll be able to flash only the images that you need for your specific requirement. For instance, you might want to only flash the stock recovery if you’re trying to take an ota and you’ve installed a custom recovery. The order that you flash the images is not important.
In the folder you extracted the factory image it’s easiest if you re-name the bootloader image file to simply bootloader and radio. Then open a Windows command window in that folder and use the fastboot commands:
fastboot flash bootloader bootloader.img
fastboot reboot-bootloader
fastboot –w (NOTE, this command does wipe your device. It’s possible to flash the factory image without this command but if you’re going from different revision numbers of android it’s highly recommend to wipe the device)
Now open a Windows command window in the same folder that you extracted the zip file in, the one where you find recovery, system, etc. Then run the fastboot commands:
fastboot flash boot boot.img
fastboot flash cache cache.img
fastboot flash recovery recovery.img
fastboot flash system system.img [Note, flashing system takes a long time, so let it do it's thing]
fastboot flash vendor vendor.img
Congratulations, you’ve now flashed a factory image and learned how to use fastboot!
For MAC users, proceed each fastboot command with a ./ e.g. ./fastboot flash boot boot.img
This should be made a 'sticky'...
An excellent well written tutorial... succinct, clear and to the point.
Far better to use fastboot instead of a toolkit... Everything is more transparent, and you actually gain a better understanding of your device as a result.
Rgrds,
Ged.
GedBlake said:
This should be made a 'sticky'...
An excellent well written tutorial... succinct, clear and to the point.
Far better to use fastboot instead of a toolkit... Everything is more transparent, and you actually gain a better understanding of your device as a result.
Rgrds,
Ged.
Click to expand...
Click to collapse
Thanks @GedBlake. I would have responded sooner but I had to get home and check my tablet. Actually both work, vol up + power and vol down + power.
Sent from my Nexus 9 using XDA Free mobile app
But.... Toolkit so easy?
(agreed... Toolkits not the best choice)
Thread stuck. Great guide @jd1639!
If we get enough guides, tutorials, how to's and other great info threads.... I would suggest a "sticky roll up" thread, so too many stickies aren't created.
Food for thought.
Edit : That ^^^^ was a hint to other members to get your guides, tutorials, info threads, FAQ... Etc... Going..... This is a Nexus section after all. :silly:
Darth said:
But.... Toolkit so easy? ?
(agreed... Toolkits not the best choice)
Thread stuck. Great guide @jd1639! ?
If we get enough guides, tutorials, how to's and other great info threads.... I would suggest a "sticky roll up" thread, so too many stickies aren't created.
Food for thought. ?
Click to expand...
Click to collapse
I'll keep an eye it and do a roll up when the need arises
Sent from my Nexus 9 using XDA Free mobile app
cant flash system.img
I Xubuntu 14.04 I can't seem to flash the system.img I get the following error
sending 'system' (1108544 KB)...
FAILED (remote: data length is too large)
finished. total time: 0.032s
nyasha1935 said:
I Xubuntu 14.04 I can't seem to flash the system.img I get the following error
sending 'system' (1108544 KB)...
FAILED (remote: data length is too large)
finished. total time: 0.032s
Click to expand...
Click to collapse
It's possible that you need to update your Android SDK to the latest. There was a recent change (within last 6 months) to fastboot to allow flashing these large .img files.
cam30era said:
It's possible that you need to update your Android SDK to the latest. There was a recent change (within last 6 months) to fastboot to allow flashing these large .img files.
Click to expand...
Click to collapse
Ok thanks gonna try on windows, im a noob on linux
nyasha1935 said:
Ok thanks gonna try on windows, im a noob on linux
Click to expand...
Click to collapse
You'll be sorry.....
cam30era said:
You'll be sorry.....
Click to expand...
Click to collapse
Ok back to linux, how do I update android SDK
nyasha1935 said:
Ok back to linux, how do I update android SDK
Click to expand...
Click to collapse
http://rootzwiki.com/topic/20770-gu...-adb-and-fastboot-in-linux-ubuntu-and-mint12/
Is it possible to flash a factory image using a custom recovery like TWRP?
Sent from my Nexus 9 using Tapatalk
iamroddo said:
Is it possible to flash a factory image using a custom recovery like TWRP?
Click to expand...
Click to collapse
Is it possible to extract the .img from the volantis-lmy47x-factory-3efdc8d4.tgz from https://developers.google.com/android/nexus/images and flash them individually with TWRP (with the exception of recovery.img, which I guess would over-write TWRP)? Can it this be done directly from 5.0.1 or would I need to first upgrade to 5.02?
Hi, I'm Italian so i'm sorry if my english is bad xD what happens if i flash a different kernel? Will i lose my warranty?
If yes, if i flash the factory image, will i have my warranty again?
And, again, sorry for my bad english
Leoncino said:
Hi, I'm Italian so i'm sorry if my english is bad xD what happens if i flash a different kernel? Will i lose my warranty?
If yes, if i flash the factory image, will i have my warranty again?
And, again, sorry for my bad english
Click to expand...
Click to collapse
No need top apologize. You're English if fine.
There's a lot of discussion and lack of agreement about what affects the warranty on the Nexus 9. HTC says that even unlocking the bootloader "may void the warranty".
My advice would be to do what you want to it, but make sure you understand what you are doing. Ask a lot of questions before you do something you're unsure of.
Unlock your bootloader (if you haven't already). Do not relock bootloader if something goes wrong (this does not solve anything). With an unlocked bootloader, you can recover from almost any problem.
And you can flash the Google factory images anytime you want to return to stock.
I'm sorry there's not a clear answer to your question.
cam30era said:
No need top apologize. You're English if fine.
Click to expand...
Click to collapse
Thanks
So it's like Samsung knox, we don't know what happens to our device.
An other little question? Is the same if i root my device? Need to unlock bootloader?
Leoncino said:
Thanks
So it's like Samsung knox, we don't know what happens to our device.
An other little question? Is the same if i root my device? Need to unlock bootloader?
Click to expand...
Click to collapse
Bootloader has to be unlocked to root, install custom recovery (TWRP). And note that when you unlock bootloader, it will wipe the contents of your SDcard. If you have anything important there, back it up on your PC.
cam30era said:
Bootloader has to be unlocked to root, install custom recovery (TWRP). And note that when you unlock bootloader, it will wipe the contents of your SDcard. If you have anything important there, back it up on your PC.
Click to expand...
Click to collapse
And what happens if i lock again my bootloader, will i restore the warranty?
Leoncino said:
And what happens if i lock again my bootloader, will i restore the warranty?
Click to expand...
Click to collapse
That's a good question, without a clear answer (unfortunately).
For those who only want custom roms - an easier way to convert from T-Mobile USA. You don't need to flash system/product/vendor partitions. No restoring modem to get signal, data will work on first boot after you install a custom rom.
This could be easily done on Linux and Windows too. I don't recommend flashall. Just do it manually. For this discussion, I am converting T-Mobile to Euro:
1. Get T-Mobile MSM package from HERE. Get Euro package (for converting) from HERE
2. Flash T-Mobile MSM (you can't transfer the MSM package via flash drive, as some files will be corrupted and you won't be able to start the package. Just download straight, unzip and execute the exe. file)
3. Boot, enable OEM unlock (you'll have to connect to the internet for a few minutes) and unlock bootloader (get unlock bin from Oneplus)
4. Once unlocked, boot again, connect to PC, enable Developer options, enable ADB. Open terminal and execute adb command:
Code:
adb reboot fastboot
You will get into 'fastbootd' recovery, but that's how it should be. Your fastboot commands will be accepted.
5. Now, unzip the downloaded Euro version, go to that directory, open terminal and execute manually the following commands separately (just copy and paste a single command from the code below) followed by pressing 'enter', i.e. paste the command, press enter, paste the next command, press enter. Watch the terminal to make sure that each command went through:
Code:
fastboot flash aop aop.img
fastboot flash bluetooth bluetooth.img
fastboot flash boot boot.img
fastboot flash dsp dsp.img
fastboot flash dtbo dtbo.img
fastboot flash logo logo.img
fastboot flash modem modem.img
fastboot flash mdm_oem_stanvbk mdm_oem_stanvbk.img
fastboot flash qupfw qupfw.img
fastboot flash storsec storsec.img
fastboot flash multiimgoem multiimgoem.img
fastboot flash uefisecapp uefisecapp.img
fastboot flash recovery recovery.img
fastboot flash vbmeta vbmeta.img
fastboot flash vbmeta_system vbmeta_system.img
fastboot flash opproduct opproduct.img
6. Once done, don't reboot in system. Instead, reboot into bootloader. From that, follow directions to install a custom rom. If Lineage, for example, flash their recovery first (fastboot flash recovery...), then boot into that recovery. Don't flash their 'copy partitions' files. Instead, just install the latest release via 'adb-sideload' (factory reset before or after flashing is required). Then boot into System normally. Your phone will have normal IMEI/Baseband and it will be listed as IN2013.
This is only for those who want custom roms. No stock OOS updates, which vendor is not needed any way, as all custom roms for Oneplus 8 provide their own vendor.
How to Unlock Oneplus 8 tmobile Bootloader without unlock token
farhansaeeddnp3021 said:
How to Unlock Oneplus 8 tmobile Bootloader without unlock token
Click to expand...
Click to collapse
Short answer - Forget it, for good. Here is the long one:
Tmobile branded Oneplus 8's bootloader is tied to a key generated based on the unique numbers, which in turn, are tied to your device's unique IMEI. This is why it is a 2 step process: first, you generate a sequence of 2 long numbers on the phone. Second, you send those numbers together with your IMEI to Oneplus. Only after that, you get the token, which could only work on your phone.
This is why, at Oneplus online store, unbranded Oneplus 8 is $100 more expensive than the branded one. The latter is software crippled, and on other sites, the difference is up to $200. You get what you paid for.
optimumpro said:
Short answer - Forget it, for good. Here is the long one:
Tmobile branded Oneplus 8's bootloader is tied to a key generated based on the unique numbers, which in turn, are tied to your device's unique IMEI. This is why it is a 2 step process: first, you generate a sequence of 2 long numbers on the phone. Second, you send those numbers together with your IMEI to Oneplus. Only after that, you get the token, which could only work on your phone.
This is why, at Oneplus online store, unbranded Oneplus 8 is $100 more expensive than the branded one. The latter is software crippled, and on other sites, the difference is up to $200. You get what you paid for.
Click to expand...
Click to collapse
thanks for replay. recently i unlock oneplus 7t pro Mclarn without unlock token. so that why i was thinking about it.
farhansaeeddnp3021 said:
thanks for replay. recently i unlock oneplus 7t pro Mclarn without unlock token. so that why i was thinking about it.
Click to expand...
Click to collapse
That's because there is a modified MSM tool for Oneplus 7 with a removed device name check. That enables you to flash global firmware on any Oneplus 7 variant. This is not possible on Oneplus 8.
Hi. Im on oxygen os 11.0.4.6IN55CB. do i need to downgrade to TMO android 10 before proceed with this? My device is TMO unlocked and bootloader locked (I don't mind about the bootloader, i can unlock it anytime)
aikattx said:
Hi. Im on oxygen os 11.0.4.6IN55CB. do i need to downgrade to TMO android 10 before proceed with this? My device is TMO unlocked and bootloader locked (I don't mind about the bootloader, i can unlock it anytime)
Click to expand...
Click to collapse
No. You don't. The tool already includes the downgrade software.
Why did you link to and suggest the Euro version of this ROM? The global version is recommended if converting from T-Mobile and should be used instead. Also creates a discrepency from the title of this thread, you did not make a guide on how to convert to global, you made a guide on how to convert to the European version.
to be fair tho shouldn't really cause issues
FoxyDrew said:
Why did you link to and suggest the Euro version of this ROM? The global version is recommended if converting from T-Mobile and should be used instead. Also creates a discrepency from the title of this thread, you did not make a guide on how to convert to global, you made a guide on how to convert to the European version.
to be fair tho shouldn't really cause issues
Click to expand...
Click to collapse
You are right, but as you said, there would be no difference in the outcome, except that your phone will show IN2013 instead of IN2015.
optimumpro said:
You are right, but as you said, there would be no difference in the outcome, except that your phone will show IN2013 instead of IN2015.
Click to expand...
Click to collapse
That's not the ONLY difference, the differences there are will probably be imperceivable in daily use however. Honestly only brought it up because I saw the title of the thread and the a link to the euro ROM and was a tad confused for a sec
Edit: "or Euro" I actually audibly laughed when I saw that, that's great. Great tutorial man haha
FoxyDrew said:
That's not the ONLY difference, the differences there are will probably be imperceivable in daily use however. Honestly only brought it up because I saw the title of the thread and the a link to the euro ROM and was a tad confused for a sec
Edit: "or Euro" I actually audibly laughed when I saw that, that's great. Great tutorial man haha
Click to expand...
Click to collapse
All right. Thanks for a very useful comment. Ha-Ha!
optimumpro said:
All right. Thanks for a very useful comment. Ha-Ha!
Click to expand...
Click to collapse
Ouch you seem salty lol, I could say the same
FoxyDrew said:
Ouch you seem salty lol, I could say the same
Click to expand...
Click to collapse
That's because you seamed to sound sarcastic. "Great guide, ha-ha"
optimumpro said:
That's because you seamed to sound sarcastic. "Great guide, ha-ha"
Click to expand...
Click to collapse
oh no that was genuine lol
FoxyDrew said:
oh no that was genuine lol
Click to expand...
Click to collapse
All right. My apologies. Sometimes it's difficult to figure out intentions on the internet.
Hi and thank you so much for this guide! I'm having a problem with flashing the global rom, it tells me flashing isnt allowed for critical partitions, despite having done both the unlock (fastboot menu confirms it) and fastboot oem unlock_critical.
Has anyone seen this before?
ManlyP0tato said:
Hi and thank you so much for this guide! I'm having a problem with flashing the global rom, it tells me flashing isnt allowed for critical partitions, despite having done both the unlock (fastboot menu confirms it) and fastboot oem unlock_critical.View attachment 5426977 Has anyone seen this before?
Click to expand...
Click to collapse
Step 4: adb reboot fastboot
This has to be done on a live device with adb enabled, connected to PC and typed on PC terminal. As a result, you are not rebooting into fastboot, but in recovery with fastboot commands enabled.
optimumpro said:
Step 4: adb reboot fastboot
This has to be done on a live device with adb enabled, connected to PC and typed on PC terminal. As a result, you are not rebooting into fastboot, but in recovery with fastboot commands enabled.
Click to expand...
Click to collapse
Thanks for your reply!
Is this the difference between fastboot and fastbootd?
Despite using the command and going into fastboot I still can't seem to make it work, even selecting recovery mode in fastboot only brings me back here. I of course installed a fresh MSM version beforehand and unlocked the bootloader.
this is the screen I'm getting, is this fastboot with recovery or only fastboot?
Before reaching fastboot though it takes me to the oneplus language select screen, then gives me the option to wipe, fastboot or recovery, maybe it has something to do with this?
Thanks again for your time.
ManlyP0tato said:
Thanks for your reply!
Is this the difference between fastboot and fastbootd?
Despite using the command and going into fastboot I still can't seem to make it work, even selecting recovery mode in fastboot only brings me back here. I of course installed a fresh MSM version beforehand and unlocked the bootloader. View attachment 5426993 this is the screen I'm getting, is this fastboot with recovery or only fastboot?
View attachment 5426995
Before reaching fastboot though it takes me to the oneplus language select screen, then gives me the option to wipe, fastboot or recovery, maybe it has something to do with this?
Thanks again for your time.
Click to expand...
Click to collapse
Wrong action. You'll never be able to flash critical partitions from fastboot, i.e., the screen in your picture. After executing the adb command in step 4, your phone will enter recovery (not fastboot) and you must stay there. Nowhere my instructions say reboot to fastboot. So, stay in recovery and execute all further commands from your PC.
Edit: Yes, that's the difference between fastboot (your screen shot) and fastbootd, which is Recovery with fastboot commands support.
optimumpro said:
Wrong action. You'll never be able to flash critical partitions from fastboot, i.e., the screen in your picture. After executing the adb command in step 4, your phone will enter recovery (not fastboot) and you must stay there. Nowhere my instructions say reboot to fastboot. So, stay in recovery and execute all further commands from your PC.
Edit: Yes, that's the difference between fastboot (your screen shot) and fastbootd, which is Recovery with fastboot commands support.
Click to expand...
Click to collapse
Ooh! I see I misunderstood that, it works just fine from the recovery screen!
I tried flashing the entire global rom because I don't want a custom rom but I just got a qualcomm crashdump mode . Currently using MSM to fix that. Is it even possible to use the global rom with the Tmobile model? Otherwise I'll just use Lineage.