hello guys, my T-mobile z2force was bricked now, and when I connect to my pc , it only show it is qcom 9008, seems that I need blankflash to save my phone , so does anyone who can find it, please help me , thx .
18712886438 said:
hello guys, my T-mobile z2force was bricked now, and when I connect to my pc , it only show it is qcom 9008, seems that I need blankflash to save my phone , so does anyone who can find it, please help me , thx .
Click to expand...
Click to collapse
Can I ask how this happened?
On Moto Z we opened a very useful thread listing all dangerous operations to avoid others doing same errors/operations... :fingers-crossed:
enetec said:
Can I ask how this happened?
On Moto Z we opened a very useful thread listing all dangerous operations to avoid others doing same errors/operations... :fingers-crossed:
Click to expand...
Click to collapse
I did something wrong with some partitions like tz, and then it goes to 9008 now, can u give me the link for the thread?
18712886438 said:
I did something wrong with some partitions like tz, and then it goes to 9008 now, can u give me the link for the thread?
Click to expand...
Click to collapse
This is the thread about "brick experiences": https://forum.xda-developers.com/moto-z/how-to/how-bricked-share-experiences-t3515167
and this are about blankflash: https://forum.xda-developers.com/moto-z/how-to/guide-how-to-unbrick-moto-z-hardbricked-t3590133 and https://forum.xda-developers.com/moto-z/help/moto-z-bricked-qdloader9008-t3524448
PLEASE NOTE they are for Moto Z & not for Z2 Force, but maybe you could still find something useful...
enetec said:
This is the thread about "brick experiences": https://forum.xda-developers.com/moto-z/how-to/how-bricked-share-experiences-t3515167
and this are about blankflash: https://forum.xda-developers.com/moto-z/how-to/guide-how-to-unbrick-moto-z-hardbricked-t3590133 and https://forum.xda-developers.com/moto-z/help/moto-z-bricked-qdloader9008-t3524448
PLEASE NOTE they are for Moto Z & not for Z2 Force, but maybe you could fstill fnd something useful...
Click to expand...
Click to collapse
yes, thx
guys i tried blank flash oreo on mine bricked tmobile moto z2 force and it isnt working, any help would be great on this , thanks.. and also i have tried many blank flashes some for even other moto phone models none worked so far.. one or two of them got really close the oreo one did but failed at last part... tried about hundred times and yes i even tried holding down power and volume button with no success it didnt work it did though recognize the phone but still failed trying to boot or flash it though... seems to me it needs either up to date or just different blank flash it seems, but i dont know that for sure...
SmartPhoneDeveloper said:
guys i tried blank flash oreo on mine bricked tmobile moto z2 force and it isnt working, any help would be great on this , thanks.. and also i have tried many blank flashes some for even other moto phone models none worked so far.. one or two of them got really close the oreo one did but failed at last part... tried about hundred times and yes i even tried holding down power and volume button with no success it didnt work it did though recognize the phone but still failed trying to boot or flash it though... seems to me it needs either up to date or just different blank flash it seems, but i dont know that for sure...
Click to expand...
Click to collapse
I started a thread literally 2 threads down from yours on how to fix this lol.https://forum.xda-developers.com/z2-force/help/gotta-super-slim-brick-t3798403
bricked moto z2 force tmobile
mookiexl said:
I started a thread literally 2 threads down from yours on how to fix this lol.https://forum.xda-developers.com/z2-force/help/gotta-super-slim-brick-t3798403
Click to expand...
Click to collapse
tried both them files, the first one seems to almost work but says failed to read file after it says waiting to read firehose or something like that during the process, i can post the pics of what it says but need to know how to post them?...
---------- Post added at 04:17 PM ---------- Previous post was at 03:51 PM ----------
mookiexl said:
I started a thread literally 2 threads down from yours on how to fix this lol.https://forum.xda-developers.com/z2-force/help/gotta-super-slim-brick-t3798403
Click to expand...
Click to collapse
these are what it says on pics hope pics can be viewed??.. let me know thanks..
{
"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"
}
SmartPhoneDeveloper said:
tried both them files, the first one seems to almost work but says failed to read file after it says waiting to read firehose or something like that during the process, i can post the pics of what it says but need to know how to post them?...
---------- Post added at 04:17 PM ---------- Previous post was at 03:51 PM ----------
these are what it says on pics hope pics can be viewed??.. let me know thanks..
Click to expand...
Click to collapse
Steps I also did uninstalled Motorola drivers and Disable Driver Signature Enforcement(google it). From reading different unbrick scenarios it seems that the desktop may need the perfect operating environment to run the commands of the blank flash.
FINALLY UNBRICKED moto z2 force tmobile !!
:highfive:
mookiexl said:
Steps I also did uninstalled Motorola drivers and Disable Driver Signature Enforcement(google it). From reading different unbrick scenarios it seems that the desktop may need the perfect operating environment to run the commands of the blank flash.
Click to expand...
Click to collapse
gonna try your steps just sec...
---------- Post added at 06:46 AM ---------- Previous post was at 05:58 AM ----------
mookiexl said:
Steps I also did uninstalled Motorola drivers and Disable Driver Signature Enforcement(google it). From reading different unbrick scenarios it seems that the desktop may need the perfect operating environment to run the commands of the blank flash.
Click to expand...
Click to collapse
your awesome mookiexl a genius mate!!, you saved my new z2 force thank gosh
thought it would be never working again , your steps worked exactly as you said..
guys if anyone gets in a tight position like i was and has a moto z2 force tmobile -(xt1789-04 model)- and flashed TWRP then tried to open slot b and then bricked your moto z2 force and now it wont boot just black screen , follow mookiexl steps it works great..
1: uninstall all moto drivers -(dont restart pc yet)
2: Disable Driver Enforcement in pc settings-(google it)
3: then after pc restart now in desktop screen connect phone to pc with usb
then click blank-flash.. there could be something i left out but i dont think i did
let me know if i missed something guys, and as always thank you so much!!..
btw mookixl, here are my results to show it finally flashed properly after you told me to proceed to next step(s) uninstall moto drivers and then disable driver enforcement then try again..
SmartPhoneDeveloper said:
:highfive:
gonna try your steps just sec...
---------- Post added at 06:46 AM ---------- Previous post was at 05:58 AM ----------
your awesome mookiexl a genius mate!!, you saved my new z2 force thank gosh
thought it would be never working again , your steps worked exactly as you said..
guys if anyone gets in a tight position like i was and has a moto z2 force tmobile -(xt1789-04 model)- and flashed TWRP then tried to open slot b and then bricked your moto z2 force and now it wont boot just black screen , follow mookiexl steps it works great..
1: uninstall all moto drivers -(dont restart pc yet)
2: Disable Driver Enforcement in pc settings-(google it)
3: then after pc restart now in desktop screen connect phone to pc with usb
then click blank-flash.. there could be something i left out but i dont think i did
let me know if i missed something guys, and as always thank you so much!!..
btw mookixl, here are my results to show it finally flashed properly after you told me to proceed to next step(s) uninstall moto drivers and then disable driver enforcement then try again..
Click to expand...
Click to collapse
Hell yeahz brother. Glad to be of assistance because I couldn't get any lol.
mookiexl said:
Hell yeahz brother. Glad to be of assistance because I couldn't get any lol.
Click to expand...
Click to collapse
sorry to hear that brother and i really appreciate your help of this matter so far,
but there are other issues now:
okay, guys there's alot of issue(s) going on with our device
and yes i know as we all do these are the risks we undertake
by unlocking our bootloader blah blah blah.. lol
anyways heres whats going on with mine okay
so much confusion and not really where to start, okay first off- what i did
is this:
i unlocked my bootloader on my moto z2 force tmobile-(xt1789-04), ]
did a flash boot twrp img it worked and all
and then read somewhere by a xda member on
one of the forums on said to try to go into or open
slot b on our moto z2 force and okay i did that and BAM! guess what!!..
it of course bricked my phone , this is where the fun began-(not really),
1: finally was able to unbrick it using a blank flash method one
believe it was an nougat blank flash one, and then when it got to the bootloader
i noticed it was a verizon bootloader smack dead on top.. i WAS SHOCKED!!
because we all know how verizon does our phones -locks the bootloader and stuff
verizon anything is the last thing i want to see on my device!!, one
i want to know how to get this off if possible and second
also been noticing that every time i try to
flash roms when phone boots up it just keeps going into bootloops
and also every since my device bricked and
i unbricked it it hasnt been same since because
it has verizon bootloader on it and two when i start
it up phone boots really fast now too fast and also
it doesnt vibrate no more like it used to before intially bricking it..
also anyone remembers or knows of motrola rom flashing and stuff
knows that there are some you can flash a global or usa unlocked version
of that rom and then it makes it fully global unlocked without
asking for a sim unlock code.. well i was in for a shocker , i thought
i was going to be do this with our motoz2 force turns out i not only
cant do this far as i know yet.. and two it seems alot more complicated
of the flashing methods to get stuff working properly must be
due to the dual partitions or something unless im just doing the flashall thing
wrong?.. and the flashall methods i read somewhere on one of the forums
where they was talking about the flashall* method and i tried
one of the oreoflashall methods but i noticed that
the *.bat* file it doesnt include the sparschunk files??.. are they needed!?..,
and if not needed then what exactly are they for because i have the tmobile
version and the sparschunk files are in there along with all other flash
files thats noted inside of the orginal flashfile.xml... any help guys would
be appreciated!!.. because as of the moment for over 5 days now im still stuck on
bootloader because i tried everything i can think of and its a no go
but i believe my flashing methods must be wrong or something...
In the moto unbricking forum it is mentioned that sometimes trying to go back to stock after a brick is troublesome. They suggest flashing a custom rom after unbricking then flashing an official stock. The reason it bootloops after flashing is probably because you didn't fastboot -w
I would flash AOSiP, and make sure you use the prep zip for TMO and follow the guide to the 'T' The prep zip will make sure you have an oreo base on both slots so it doesn't fall over on itself. If all is well and you get AOSiP up and going and you feel like returning to stock. Just go here and follow this guide.
UNBRICKED , but stuck in bootloader and now showing verizon bootloader!!
41rw4lk said:
In the moto unbricking forum it is mentioned that sometimes trying to go back to stock after a brick is troublesome. They suggest flashing a custom rom after unbricking then flashing an official stock. The reason it bootloops after flashing is probably because you didn't fastboot -w
I would flash AOSiP, and make sure you use the prep zip for TMO and follow the guide to the 'T' The prep zip will make sure you have an oreo base on both slots so it doesn't fall over on itself. If all is well and you get AOSiP up and going and you feel like returning to stock. Just go here and follow this guide.
Click to expand...
Click to collapse
okay will try, but note: i have tried this prior to bricking before,but that was before my bricking, it was throwing me a error 255 whatever that is, matter of fact never could get any custom rom working but also i do have an additional working perfect order untouched motoz2 force as well if that makes a difference couldnt i just use the twrp backup of the original to flash back the original rom?.. my original bootloader was oreo firmware also if that helps with these problems im having?... and also whats prep-zip?.
never heard that method?.. is that mean flashing via twrp custom recovery?..
and thanks for the help i really appreciate this bro... and also if you read the part where i said these problems trying to flash anything was having same ones even before bricking
my device,.. it just giving me more issues in a sense now...
SmartPhoneDeveloper said:
okay will try, but note: i have tried this prior to bricking before,but that was before my bricking, it was throwing me a error 255 whatever that is, matter of fact never could get any custom rom working but also i do have an additional working perfect order untouched motoz2 force as well if that makes a difference couldnt i just use the twrp backup of the original to flash back the original rom?.. my original bootloader was oreo firmware also if that helps with these problems im having?... and also whats prep-zip?.
never heard that method?.. is that mean flashing via twrp custom recovery?..
and thanks for the help i really appreciate this bro... and also if you read the part where i said these problems trying to flash anything was having same ones even before bricking
my device,.. it just giving me more issues in a sense now...
Click to expand...
Click to collapse
Twrp and backups for our phone at least isn't solid, maybe to restore some data, but other than that there have been issues. The prep zip, that's what I call it at least is in the 2nd comment in the AOSiP thread. It's a base package that flashes to both slots, its intent was to prevent trouble should Nougat be on the other slot. Either way, I would flash it. It is flashed via a flashall.bat inside the zip, no need for twrp yet. Just follow the guide in the OP of the AOSiP thread. That should at least get AOSiP up and running. If you don't like it, or if things are off and you want to return to stock, just follow the guide in the return to stock guide. Don't worry about anything else right at the moment, just AOSiP. If you have trouble, post it.
trying aosip custom rom now on bootloader stuck motoz2 force
41rw4lk said:
Twrp and backups for our phone at least isn't solid, maybe to restore some data, but other than that there have been issues. The prep zip, that's what I call it at least is in the 2nd comment in the AOSiP thread. It's a base package that flashes to both slots, its intent was to prevent trouble should Nougat be on the other slot. Either way, I would flash it. It is flashed via a flashall.bat inside the zip, no need for twrp yet. Just follow the guide in the OP of the AOSiP thread. That should at least get AOSiP up and running. If you don't like it, or if things are off and you want to return to stock, just follow the guide in the return to stock guide. Don't worry about anything else right at the moment, just AOSiP. If you have trouble, post it.
Click to expand...
Click to collapse
okay will do, and thanks for help on this matter mate, im trying it now but
also i forgot to mention on how to flash properly twrp on our device?..
as i couldnt even get twrp to boot up now but it will flash on fastboot at least it shows it flashing and stuff, but when it goes to restart on boot up
it just keeps restarting bootloop, also i think i may be flashing it wrong or something and is moto drivers needed or not?..
SmartPhoneDeveloper said:
okay will do, and thanks for help on this matter mate, im trying it now but
also i forgot to mention on how to flash properly twrp on our device?..
as i couldnt even get twrp to boot up now but it will flash on fastboot at least it shows it flashing and stuff, but when it goes to restart on boot up
it just keeps restarting bootloop, also i think i may be flashing it wrong or something and is moto drivers needed or not?..
Click to expand...
Click to collapse
Make sure you're using the 3.2.1-1.img and 3.2.1-1.zip from here
Follow the AOSiP guide and when it's time to BOOT twrp just
Code:
fastboot boot (drag n drop twrp.IMG here)
Once booted into twrp, flash the twrp.ZIP after the install do a reboot to recovery inside twrp to reboot back into it and follow along in the guide.
You can't flash twrp through fastboot with our phone because technically it doesn't have a recovery partition, it's built into boot. So just follow what I posted which is what the AOSiP guide says as well.
SmartPhoneDeveloper said:
sorry to hear that brother and i really appreciate your help of this matter so far,
but there are other issues now:
okay, guys there's alot of issue(s) going on with our device
and yes i know as we all do these are the risks we undertake
by unlocking our bootloader blah blah blah.. lol
anyways heres whats going on with mine okay
so much confusion and not really where to start, okay first off- what i did
is this:
i unlocked my bootloader on my moto z2 force tmobile-(xt1789-04), ]
did a flash boot twrp img it worked and all
and then read somewhere by a xda member on
one of the forums on said to try to go into or open
slot b on our moto z2 force and okay i did that and BAM! guess what!!..
it of course bricked my phone , this is where the fun began-(not really),
1: finally was able to unbrick it using a blank flash method one
believe it was an nougat blank flash one, and then when it got to the bootloader
i noticed it was a verizon bootloader smack dead on top.. i WAS SHOCKED!!
because we all know how verizon does our phones -locks the bootloader and stuff
verizon anything is the last thing i want to see on my device!!, one
i want to know how to get this off if possible and second
also been noticing that every time i try to
flash roms when phone boots up it just keeps going into bootloops
and also every since my device bricked and
i unbricked it it hasnt been same since because
it has verizon bootloader on it and two when i start
it up phone boots really fast now too fast and also
it doesnt vibrate no more like it used to before intially bricking it..
also anyone remembers or knows of motrola rom flashing and stuff
knows that there are some you can flash a global or usa unlocked version
of that rom and then it makes it fully global unlocked without
asking for a sim unlock code.. well i was in for a shocker , i thought
i was going to be do this with our motoz2 force turns out i not only
cant do this far as i know yet.. and two it seems alot more complicated
of the flashing methods to get stuff working properly must be
due to the dual partitions or something unless im just doing the flashall thing
wrong?.. and the flashall methods i read somewhere on one of the forums
where they was talking about the flashall* method and i tried
one of the oreoflashall methods but i noticed that
the *.bat* file it doesnt include the sparschunk files??.. are they needed!?..,
and if not needed then what exactly are they for because i have the tmobile
version and the sparschunk files are in there along with all other flash
files thats noted inside of the orginal flashfile.xml... any help guys would
be appreciated!!.. because as of the moment for over 5 days now im still stuck on
bootloader because i tried everything i can think of and its a no go
but i believe my flashing methods must be wrong or something...
Click to expand...
Click to collapse
https://forum.xda-developers.com/z2-force/how-to/how-to-return-to-stock-sprint-t3694783 Follow guide. New T-Mobile firmware is linked and official from the Motorola firmware Team. The new update was released two days ago in flash all format. There is a utilities zip you can use to flash with. Just follow OP and download from second post. You'll be golden and back to stock.
UNBRICKED , but stuck in bootloader, trying other methods thanks to members!
41rw4lk said:
Make sure you're using the 3.2.1-1.img and 3.2.1-1.zip from here
Follow the AOSiP guide and when it's time to BOOT twrp just
Code:
fastboot boot (drag n drop twrp.IMG here)
Once booted into twrp, flash the twrp.ZIP after the install do a reboot to recovery inside twrp to reboot back into it and follow along in the guide.
You can't flash twrp through fastboot with our phone because technically it doesn't have a recovery partition, it's built into boot. So just follow what I posted which is what the AOSiP guide says as well.
Click to expand...
Click to collapse
going to try these methods so far i believe i was using older methods that was non-relevant or was maybe outdated for this, i was originally on oreo firmware before i flashed anything, it was oreo stock on mine as i heard some have 7.1.1 stock or so.. so maybe i just need to try flash oreo firmware since that was originally the firmware on mine?.. and also i really appreciate the help on this guys.. trying it now just sec.. i tried also to flash stock nougat firmware but no success?.., can we not downgrade as i was reading on some post about z2 force our phones and they said you could downgrade, but like i said maybe just my flash methods or .bat files are wrong or so?.. also btw i read somewhere that people that was on oreo firmware couldnt do a flashall method or something like that anyone can either confirm this or wrong it?....
---------- Post added at 11:05 AM ---------- Previous post was at 10:44 AM ----------
Uzephi said:
https://forum.xda-developers.com/z2-force/how-to/how-to-return-to-stock-sprint-t3694783 Follow guide. New T-Mobile firmware is linked and official from the Motorola firmware Team. The new update was released two days ago in flash all format. There is a utilities zip you can use to flash with. Just follow OP and download from second post. You'll be golden and back to stock.
Click to expand...
Click to collapse
going to try this now mate, and thanks for all the help guys mookiexl, airwalk, and Uzephi on this matter for our great device, oh by the way guys i have been working on some things for our device for while now, while trying to get out of bootloader , while i was waiting to do a stock recover and such , but no worries i need some testers on this matter i tried two of them to see and they did seem to show on screen and no crashes or nothing so far, so it seems it's okay so far ..-(i have three variants of this splash screen to remove unlocked screen for replacing it because it can be kinda of pesky to some) - the commands are fastboot flash logo_a (the logo.bin here)..
EDIT!:
DISCLAIMER!!:
They do indeed work, But as i said-- I MANUALLY FLASHED THEM!-- THEY WORKED FOR ME NO PROBLEMS, BUT IF ON DIFFERENT FIRMWARE
PLEASE TEST AND LET ME KNOW I WASNT ON CUSTOM FIRMWARE SO ANY OTHERS ON THEM LET ME or other experienced members on this matter KNOW AND TRY TO SEE IF WORKS I WAS JUST ON BOOTLOADER AND IT WORKED SO FAR I TRIED ALL THREE VARIANTS...
links are below at the --BOTTOM OF THE POST-- also i almost forgot i ALSO INCLUDED TWRP RECOVERY FLASHABLE ZIP(s) file(s) for the logo boot splash screens for anyone only wanting to flash or has issues with fastboot for whatever reason to flash them in twrp instead they should work but if any issue(s) let us know thanks!!..
the way i did this was below, it worked for me both ways as well as in just:
**fastboot flash logo logo.bin** -(without quotes) also i did try it worked but as i say it may be different depending on if your either nougat or oreo users..
(guys side note!!: not 100% sure if logo_a and logo_b may be needed -(this is why i said i need some testers, so please be easy on me, im still learning myself, i did make these from scratch)
commands are:
fastboot flash logo_a (logo.bin here)
fastboot flash logo_b (logo.bin here)
note#2!: i heard somewhere on a xda post that oreo users may or may not be able to do a flashall method, this is why i say do it manually, correct me as needed please!, because as i said im learning myself in the process , but i learn really fast so no worries!
oreo users: to be safe side of things, do command below manually:
fastboot flash logo_a (logo.bin here)
fastboot flash logo_b (logo.bin here)
check out and see if you guys like the logo boot screen pics of ones i made
if no one likes these then i will happily remove them, and as always thanks guys for all the help with me on these matter(s)...
and also i have another question too about something -(this is seperate upon these things )-one more thing its about Sparsechunk files** as i noticed in our flashall.bat files thats provided from others, its not in there i have tmobile version of our variant and it does have sparsechunk files in there 0-3 of them check out my file flashall_main.bat file please someone and just right click this one i made by scratch and been using maybe reason why it hasnt been working for me and go to option 8 is what i been using for flashall.bat method- for the flashall method to flash on our motoz2 force, and let me know if its correct or no, also btw you know how its have dual partition on our device now, well i need to know of my flashll-main.bat file i will provide below in link if its right on the flashall methods on how to flash it on our device, notice thats theres system_a system_b but in sparsechunk files its like this below:
this is my part of it in my file(s) of my flashall-main.bat file:
option 8 only!!! as i noted others dont pay no attention to them was done for other model(s)
nash i made for option 8 on menu of this flashall
but i need help to see if it was done right
need to know if sparsechunk file(s) since its orginally system_b.img
would it need to be like system_a system_b then or like this:
_a _a
_a _b
_b _a
_b _b
????? see what i mean since we have dual partitions but since it is originally system_b
as i was saying i may not need to change it thats why im asking and as always thanks guys for this help
________________________________________________________
:flashStockR-ORIG-Custom#1-2-FLASHFILE.XML
cls
echo.
echo You will flash a Stock or Custom Stock Rom
echo The Stock or Custom Stock Rom Folder needs Used or Could Be Set within your ADB-Folder or Outside of ADB-Folder As Well Either Should Be Fine
echo.
pause
echo.
fastboot getvar max-sparse-size
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash bootloader_a bootloader.img
fastboot flash bootloader_b bootloader.img
fastboot flash modem_a NON-HLOS.bin
fastboot flash fsg_a fsg.mbn
fastboot flash modem_b NON-HLOS.bin
fastboot flash fsg_b fsg.mbn
fastboot erase modemst1
fastboot erase modemst2
fastboot flash bluetooth_a BTFM.bin
fastboot flash dsp_a adspso.bin
fastboot flash logo_a logo.bin
fastboot flash boot_a boot.img
fastboot flash system_a system.img_sparsechunk.0
fastboot flash system_a system.img_sparsechunk.1
fastboot flash system_a system.img_sparsechunk.2
fastboot flash system_a system.img_sparsechunk.3
fastboot flash system_a system.img_sparsechunk.4
fastboot flash system_a system.img_sparsechunk.5
fastboot flash system_a system_b.img_sparsechunk.0
fastboot flash system_a system_b.img_sparsechunk.1
fastboot flash system_a system_b.img_sparsechunk.2
fastboot flash system_a system_b.img_sparsechunk.3
fastboot flash oem_a oem.img
fastboot flash bluetooth_b BTFM.bin
fastboot flash dsp_b adspso.bin
fastboot flash logo_b logo.bin
fastboot flash boot_b boot.img
fastboot flash system_b system.img_sparsechunk.0
fastboot flash system_b system.img_sparsechunk.1
fastboot flash system_b system.img_sparsechunk.2
fastboot flash system_b system.img_sparsechunk.3
fastboot flash system_b system.img_sparsechunk.4
fastboot flash system_b system.img_sparsechunk.5
fastboot flash system_b system_b.img_sparsechunk.0
fastboot flash system_b system_b.img_sparsechunk.1
fastboot flash system_b system_b.img_sparsechunk.2
fastboot flash system_b system_b.img_sparsechunk.3
fastboot flash oem_b oem.img
fastboot erase carrier
fastboot erase ddr
fastboot oem fb_mode_clear
fastboot -w
fastboot --set-active=other
fastboot reboot-bootloader
echo.
echo Done!
pause>nul
cls
goto menu
________________________________________________________
This worked, Disabling driver enforcement and uninstall Motorola drivers via programs and features! THANKS!!
Related
Please don't ask why (the answer will be: "because I'm stupid"), but I relocked my bootloader and now my Swift 2 Plus won't boot anymore. When turning it on, it vibrates and the Wileyfox logo flashes for less than a second. After that the screen stays black and nothing happens. Same thing when I try to boot into recovery. I can only boot into the bootloader but I can't flash any images or unlock it again ("FAILED (remote: oem unlock is not allowed)").
Is there any way I can revive my phone or is it lost?
I think your only way is to flash twrp again with fastboot install method :
//twrp.me/devices/wileyfoxswift2.html
And then flash the stock rom :
//cyngn.com/support
hope it will helps you!
---------- Post added at 02:07 PM ---------- Previous post was at 02:05 PM ----------
Sorry, I'm a new user so I can't post link, you've just have to ad "https" at the beginning of the line.
Thanks for answering, but I can't do that, because the bootloader is locked and protected from unlocking. I guess the only thing I can do is ask the support if they can provide the mbn and xml files that are needed for unbricking with QFIL (I can boot into edl mode as I recently found out). They probably won't but it's worth a shot.
If you use the signed zip ( not the fastboot image) the default recovery should be able to install it.
It doesn't boot to recovery. Only fastboot and edl mode work.
You could try flashing fastboot image from http://cyngn.com/support
Sent from my Swift 2 using XDA-Developers mobile app
Thanks, but that doesn't work with a locked bootloader (already tried).
It seems like the only way to revive it is with QFIL, but for doing that it needs the matching mbn and xml files that aren't included in the factory images. Wileyfox support wasn't helpful, either.
xrmnx said:
Thanks, but that doesn't work with a locked bootloader (already tried).
Click to expand...
Click to collapse
Can't we put the dirty cow bug to a use now? It should work on the phone unless it has the latest security patches, right? And with root privileges you should be able to flash a new recovery or reset the phone.:fingers-crossed:
I'm actually not sure, if I still have root privileges. It could be that I turned it off inside the SuperSU app.
I tried to flash the stock rom and that didn't work, though. Do I have to do something different than usually to flash with root privileges?
boa05 said:
Can't we put the dirty cow bug to a use now? It should work on the phone unless it has the latest security patches, right? And with root privileges you should be able to flash a new recovery or reset the phone.:fingers-crossed:
Click to expand...
Click to collapse
I read a little about dirty cow, now (didn't know much about it before), but if I understand it right, I need adb to upload files onto the phone, right? Sadly, adb doesn't work. Only fastboot :/
Hmmm, there is a similar thread for the Nexus 5X. You might want to check it out if you haven't already ( http://forum.xda-developers.com/nexus-5x/help/nexus-5x-permanently-bricked-locked-t3232105/page2 ).
A few of the suggestions were to try with:
Code:
fastboot flashing unlock
or
Code:
fastboot format userdata
fastboot format cache
I don't know if it will be of any help but it is worth a shot.
You could try to flash individual portions of the stock image like the recovery or the userdata but I doubt that it will be successful.
PS: From the thread above, for some reason removing the SIM card allowed them to enter recovery.
Thanks, but none of these solutions works. Already tried all of them a couple of times....
Hmmm, how about you try to trick it then?
Grab the official signed firmware, place it on SD Card and try with:
Code:
fastboot update <path/to/zip>
or this one to try to wipe the device? (dunno if the command is still in use, though)
Code:
fastboot -w
If this doesn't work as well, I guess it will be a waiting game for QFIL files.
Pak0St said:
Hmmm, how about you try to trick it then?
Grab the official signed firmware, place it on SD Card and try with:
or this one to try to wipe the device? (dunno if the command is still in use, though)
If this doesn't work as well, I guess it will be a waiting game for QFIL files.
Click to expand...
Click to collapse
I tried to flash/update every official rom (with and without -w) there is, but I never put it on an SD-card. Does that make a difference? If so, this might be one ofhe stupidest mistakes I ever made :/
I'll try in a few days. Not much time, at the moment...
Yes... Waiting for QFIL files is what I'm prepared for...
The idea with the SDCard is just a random thought. There is a slight chance to trigger the allowed update policies.
Usually you place the update.zip through adb (not possible in this situation) but placing it on the sdcard is possible.
Still, QFIL is the safest bet once someone uploads the files.
Pak0St said:
Still, QFIL is the safest bet once someone uploads the files.
Click to expand...
Click to collapse
That's what I thought. Since I couldn't find any (yet), is there a way to extract the QFIL files from a working phone (I bought another one since I needed a phone)? I don't think so, but I hope I'm wrong...
xrmnx said:
That's what I thought. Since I couldn't find any (yet), is there a way to extract the QFIL files from a working phone (I bought another one since I needed a phone)? I don't think so, but I hope I'm wrong...
Click to expand...
Click to collapse
I'm in the same boat here, same phone and same issue. Did you find a way to fix it? already searched all internet for a fix. Thanks a lot
Sorry, but for some reason I never saw your answer... I never found a solution either, though
how to unlock bootloader
Use fast boot to unlock the bootloader again.
connect your Swift 2 to your PC and in a command prompt type the following "fastboot oem unlock"
When you press enter, check the phone and using the volume keys you need to select yes and then press power to execute.
Your bootloader should then be unlocked again. Good Luck.
Hey all,
Since I first unlocked my 10, I've been trying to get a Lineage/CM based rom on the thing with no success. I typically get either a boot loop, or a hard reset to the HTC logo.
Unless people are just lying, CM/Lineage on the Sprint 10 should be possible as I've read many posts claiming so.
I've tried a variety of things including different versions of TWRP from 3.0.3-0 to 3.0.3-6, and multiple Lineage/CM based roms.
One supposition is that my current MM firmware is to blame. I think this may well be the issue; however, I don't know how (if it's even possible) to get my 10 to 2.** firmware, as Sprint has not released this yet.
I just S-Offed my phone, and I'm currently S-Off, Boot Unlocked.
I don't have a Windows computer, but I'm capable of using adb and fastboot. I'm also comfortable using command line tools.
Help!!! Haha, I'm so frustrated with this device!
Thanks in advance!
jayreed1 said:
Hey all,
Since I first unlocked my 10, I've been trying to get a Lineage/CM based rom on the thing with no success. I typically get either a boot loop, or a hard reset to the HTC logo.
Unless people are just lying, CM/Lineage on the Sprint 10 should be possible as I've read many posts claiming so.
I've tried a variety of things including different versions of TWRP from 3.0.3-0 to 3.0.3-6, and multiple Lineage/CM based roms.
One supposition is that my current MM firmware is to blame. I think this may well be the issue; however, I don't know how (if it's even possible) to get my 10 to 2.** firmware, as Sprint has not released this yet.
I just S-Offed my phone, and I'm currently S-Off, Boot Unlocked.
I don't have a Windows computer, but I'm capable of using adb and fastboot. I'm also comfortable using command line tools.
Help!!! Haha, I'm so frustrated with this device!
Thanks in advance!
Click to expand...
Click to collapse
You need to first flash the firmware for an unlocked device. Then you can RUU back to Sprint and install LOS. @andybones made a custom firmware zip specifically for Sprint to do this.
tabp0le said:
You need to first flash the firmware for an unlocked device. Then you can RUU back to Sprint and install LOS. @andybones made a custom firmware zip specifically for Sprint to do this.
Click to expand...
Click to collapse
Hey,
Thanks for your response.... I can't seem to find his Sprint specific zip. He's quite prolific!
I've found what I believe is the us Unlocked:
2PS6IMG_1.80.617.1_R_firmware.zip
Here
Could you either point me to his zip, or could you verify that if I remove all but firmware from this zip, I should be able to accomplish the same task?
Thanks again!
jayreed1 said:
Hey,
Thanks for your response.... I can't seem to find his Sprint specific zip. He's quite prolific!
I've found what I believe is the us Unlocked:
2PS6IMG_1.80.617.1_R_firmware.zip
Here
Could you either point me to his zip, or could you verify that if I remove all but firmware from this zip, I should be able to accomplish the same task?
Thanks again!
Click to expand...
Click to collapse
Please read this entire thread. You'll find my detailed guide in Post #3. There are also posts in Page #2 with Sprint user (@mcwups1) that will help you out, and possibly reach out to him about his experience, and if he has any tips for you. He is a good man.
andybones said:
Please read this entire thread. You'll find my detailed guide in Post #3. There are also posts in Page #2 with Sprint user (@mcwups1) that will help you out, and possibly reach out to him about his experience, and if he has any tips for you. He is a good man.
Click to expand...
Click to collapse
I read the entire post as you recommended, and I believe I now know how to proceed.
Unfortunately, I've ran myself clear out of free time.
I'll give this a go and report back as soon as I get a few free hours again--probably Friday or so.
Thanks a million!
You guys are very welcome.
Please proceed at your own risk (as with any flashing).
I've tried to make the guide I used as clear as possible and will certainly help if anything is unclear, but keep in mind nougat wasn't out at the time it was created. I don't foresee any issues as really the main thing that is making it boot was anyone that had flashed the us unlocked firmware at any point in time, and I believe people are still converting, The guide is really flashing the us unlocked firmware then back to your (Sprint) RUU.
Woot!
This worked. I'm now running los with pico gapps and su.
Thanks all.
For anybody that follows in my path, I'm running arch linux, and the android tools package in extras was all I needed (this was a concern of mine).
I grabbed @andybones' modified vzw zip and simply changed the mid and cid to match my phone in the android text file within.
I then flashed the double modded zip.
Next, I flashed the sprint modified (recovery removed) firmware only ruu.
Los booted fine after this; however, I had no lte. So, I rebooted to boatloader, and erased modems 1 & 2.
Finally!!#?! This has been the most frustrating device I've owned to date, but I'm sitting pretty now.
Thanks again everyone!
jayreed1 said:
Woot!
This worked. I'm now running los with pico gapps and su.
Thanks all.
For anybody that follows in my path, I'm running arch linux, and the android tools package in extras was all I needed (this was a concern of mine).
I grabbed @andybones' modified vzw zip and simply changed the mid and cid to match my phone in the android text file within.
I then flashed the double modded zip.
Next, I flashed the sprint modified (recovery removed) firmware only ruu.
Los booted fine after this; however, I had no lte. So, I rebooted to boatloader, and erased modems 1 & 2.
Finally!!#?! This has been the most frustrating device I've owned to date, but I'm sitting pretty now.
Thanks again everyone!
Click to expand...
Click to collapse
Nice! Great to finally see some feedback from a sprint user. Wanted to try this myself before I upgrade to nougat firmware. Only thing I'm confused about is you having to erase modem 1&2. What does that mean?
For clarification I didn't end up on nougat firmware either. Sprint hasn't released that. Just nougat rom with MM firmware.
After flashing only 3G and cell signal work.
I found in another post (can't find to credit) that a possible fix was to erase modemst1 and modemst2.
To do this, reboot to bootloader.
-> adb reboot bootloader
Then use fastboot to erase modemst 1&2
-> fastboot erase modemst1
-> fastboot erase modemst2
-> fastboot reboot
Also, the lines in the android text file that need to be changed should become.
modelidnum: 2PS640000
cidnum: SPCS_001
Fin
jayreed1 said:
For clarification I didn't end up on nougat firmware either. Sprint hasn't released that. Just nougat rom with MM firmware.
After flashing only 3G and cell signal work.
I found in another post (can't find to credit) that a possible fix was to erase modemst1 and modemst2.
To do this, reboot to bootloader.
-> adb reboot bootloader
Then use fastboot to erase modemst 1&2
-> fastboot erase modemst1
-> fastboot erase modemst2
-> fastboot reboot
Also, the lines in the android text file that need to be changed should become.
modelidnum: 2PS640000
cidnum: SPCS_001
Fin
Click to expand...
Click to collapse
Awesome thanks! Sprint released Nougat OTA yesterday and OMJ extracted firmware that we can flash. Sprint Nougat RUU isn't out yet though waiting for it on HTC's site. Check it out on Sprint HTC 10 XDA dev page. If you flash the firmware and everything still works fine please let me know. Should be trying this if I have time tonight. Have a lot of homework :silly:
I believe there has been a new method found that only involved flashing 1 .img from the US Unlocked firmware that will save a lot of trouble.
If I can find the post I will link it here.
EDIT:
https://forum.xda-developers.com/showpost.php?p=71137922&postcount=866
andybones said:
I believe there has been a new method found that only involved flashing 1 .img from the US Unlocked firmware that will save a lot of trouble.
If I can find the post I will link it here.
EDIT:
https://forum.xda-developers.com/showpost.php?p=71137922&postcount=866
Click to expand...
Click to collapse
Thanks, for spreading the word. If it works for others....on Sprint/Verizon...I could make a guide
Sent from my Sprint HTC 10 using Tapatalk
The Fer-Shiz-Nizzle said:
Thanks, for spreading the word. If it works for others....on Sprint/Verizon...I could make a guide
Sent from my Sprint HTC 10 using Tapatalk
Click to expand...
Click to collapse
Very welcome, least I can do.
Nice work on finding the difference. Will certainly save alot of trouble for many!
guys right now what i have to do?
* i updated my htc 10 sprint till the last MM ota, i didn´t make nougat update
* i unlocked my bootloader and install unoficial twrp that i found here
* i have last viper rom
what should i do so i can install other custom roms because right now i can´t pass the boot logo
i´m s off
---------- Post added at 05:27 AM ---------- Previous post was at 05:19 AM ----------
i just need to flash this?
Attached Files
File Type: zip rfg_3.imgs.zip - [Click for QR Code] (1.91 MB, 12 views)
The Fer-Shiz-Nizzle said:
Thanks, for spreading the word. If it works for others....on Sprint/Verizon...I could make a guide
Click to expand...
Click to collapse
I tried flashing the rfg_3 image on Sprint but got failed (remote: 35 ru_partition_not_support rfg_3). I'm S-OFF and unlocked bootloader. Do you know what may be going on? I'm currently running stock ROM after running nougat RUU with magisk. Thank you.
beastlymonkey said:
I tried flashing the rfg_3 image on Sprint but got failed (remote: 35 ru_partition_not_support rfg_3). I'm S-OFF and unlocked bootloader. Do you know what may be going on? I'm currently running stock ROM after running nougat RUU with magisk. Thank you.
Click to expand...
Click to collapse
Are you flashing it while in Download mode or bootloader?
Sent from my Sprint HTC 10 using Tapatalk
The Fer-Shiz-Nizzle said:
Are you flashing it while in Download mode or bootloader?
Click to expand...
Click to collapse
Download. I ran the command "fastboot flash rfg_3 US_UL...img" sorry on mobile forgot exact name
beastlymonkey said:
Download. I ran the command "fastboot flash rfg_3 US_UL...img" sorry on mobile forgot exact name
Click to expand...
Click to collapse
I thought I flashed it from Download mode, but I just tried it, and got the same error. Then I reboot to bootloader, and tried again and it flashed successfully. So you need to do it from bootloader
Sent from my Sprint HTC 10 using Tapatalk
The Fer-Shiz-Nizzle said:
I thought I flashed it from Download mode, but I just tried it, and got the same error. Then I reboot to bootloader, and tried again and it flashed successfully. So you need to do it from bootloader
Click to expand...
Click to collapse
Cool thanks! I thought you can only do fastboot in download mode? I'll try again later and will let you know. Thanks again
beastlymonkey said:
Cool thanks! I thought you can only do fastboot in download mode? I'll try again later and will let you know. Thanks again
Click to expand...
Click to collapse
Yeah I know TWRP is flashed from Download mode, but some stuff apparently still use the bootloader.
Sent from my Sprint HTC 10 using Tapatalk
Hi,
Everybody is looking for official stock roms for Moto G4/G4 Plus *AWAY* from Motorola support, which looked to me like kind of weird but I now know why: people are looking for stock roms that will allow them over the air upgrades. If you have a developer edition or a moto with unlocked bootloader, Moto's own roms are flashable and *COMPLETELY WORKING*
motorola-global-portal.custhelp.com/app/standalone/bootloader/recovery-images
Go to above URL, quick login using G+, follow instructions to get to the download list. The listed download for XT1625 will also work just fine for XT1642.
Or, you can just use this direct link: motorola-global-portal.custhelp.com/cc/ajaxCustom/getBootFile/fileName/ib65qpz53y
may also require login.
******** VERY IMPORTANT ************
Everybody lists fastboot utility commands with which you restore a Moto stock rom. They do not tell these severe warnings:
- Never flash a gpt.bin file unless you really absolutely ultimately intentionally and knowingly NEED TO. Why? in 99.9% of the cases it is useless to your phone and your needs and all it will do is deprive you the ability to downgrade to an earlier version or flash an older boot file, system file, ...etc. You get the picture. BTW, gpt.bin is only a partition image containing Moto's partition table scheme, with versioning for downgrade prevention. Keep away from it. It is pure EVIL.
IF YOU SEE gpt.bin FILE, DELETE IT WITHOUT HESITATION.
- Our second vanity: bootloader.img or bootloader.bin or anything that spells BOOTLOADER. EVIL. DELETE IT. It will 99.9% only mess up your cellular capability and render your phone without voice calls, with out SMS and without 2G/3G/4G; no data whatsoever. It will convert your phone into a 5.5 inch SIM-less tablet. It will KILL YOUR SIM SLOTS.
Instruction are on the first link, but anyway, here we go:
To flash, put the phone in fastboot mode:
1. Power OFF your device
2. Then Power ON + Volume Down Alternatively, you can reboot into fastboot mode if you have adb...
adb reboot bootloader.
Next flash the images using fastboot:
Code:
"DELETED COMMAND HERE WAS SUPPOSED TO FLASH THE GPT.BIN. NEVER DO IT"
"DELETED COMMAND HERE WAS SUPPOSED TO FLASH THE BOOTLOADER. NEVER DO IT"
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase userdata
fastboot erase cache
fastboot reboot
enjoy
****removed****
MK+2017 said:
****removed****
Click to expand...
Click to collapse
I would like back to MM from Nougat on XT1642. This firmware comes from a trusted source, but have you tried this firmware, no problems after flashing? Do I have to have an unlocked bootloader ?
kkamelot said:
I would like back to MM from Nougat on XT1642. This firmware comes from a trusted source, but have you tried this firmware, no problems after flashing? Do I have to have an unlocked bootloader ?
Click to expand...
Click to collapse
if you have not unlocked boot-loader you are covered by warranty and I advise you keep it that way. Motorola is a BI***.
if you really can't live without older stock, go to moto service and ask them to do it for you. should not cost you much, if any.
if what you hate is stock firmware, you can unlock bootloader, get warranty off, and flash LinageOS. Stable enough although still in nightly builds (successor of CyanogenMod)
hope that helps.
PS1: what you would fear the most is lose your SIM slot, happens a lot. Be safe!
PS2: asking if I tried it yes, I did. it worked. but I was on 6.0.1 at the time. do not take risk.
PS3: Motorola is a *****. DON'T MESS WITH IT.
MK+2017 said:
if you have not unlocked boot-loader you are covered by warranty and I advise you keep it that way. Motorola is a BI***.
if you really can't live without older stock, go to moto service and ask them to do it for you. should not cost you much, if any.
if what you hate is stock firmware, you can unlock bootloader, get warranty off, and flash LinageOS. Stable enough although still in nightly builds (successor of CyanogenMod)
hope that helps.
PS1: what you would fear the most is lose your SIM slot, happens a lot. Be safe!
PS2: asking if I tried it yes, I did. it worked. but I was on 6.0.1 at the time. do not take risk.
PS3: Motorola is a *****. DON'T MESS WITH IT.
Click to expand...
Click to collapse
Thank you for your answer !
I have one more question, is there way (like in nexus) to back to original software (Nougat can be) after changing OS or make a modifications?
kkamelot said:
Thank you for your answer !
I have one more question, is there way (like in nexus) to back to original software (Nougat can be) after changing OS or make a modifications?
Click to expand...
Click to collapse
There is, but if you are not good with command line, think twice. Check here: https://forum.xda-developers.com/moto-g4-plus/help/complete-partition-backup-script-xt1644-t3608408
you would typically use that alongside full TWRP backup.
I can assure you nothing will go wrong if you jump straight to LineageOS, it might only go wrong if you take the bad decision of going back to stock. The dd images would give you solid backup, though.
In case you lose your sim slot, you can use help from here: https://forum.xda-developers.com/showpost.php?p=72343095&postcount=101
I intuitively contributed to that solution Giving is taking!
Thank you @m.sawastik and @givitago
MK+2017 said:
There is, but if you are not good with command line, think twice. Check here: https://forum.xda-developers.com/moto-g4-plus/help/complete-partition-backup-script-xt1644-t3608408
you would typically use that alongside full TWRP backup.
I can assure you nothing will go wrong if you jump straight to LineageOS, it might only go wrong if you take the bad decision of going back to stock. The dd images would give you solid backup, though.
In case you lose your sim slot, you can use help from here: https://forum.xda-developers.com/showpost.php?p=72343095&postcount=101
I intuitively contributed to that solution 😊Giving is taking!
Thank you @m.sawastik and @givitago
Click to expand...
Click to collapse
I would also be happy to assist you if you want to jump to LineageOS. I won't assist you with dd backup, just because you need to take that responsibility on your own
My XT1625 is already on Lineage OS Andriod N. However, I feel like the cellular reception and thus battery life has been worse versus stock.
I wanted to flash only the latest baseband from the latest stock Andriod N but your Moto link only has 6.0.1 for XT1625.
What gives- I thought Motorola already updated the G4 to 7.0?
Will OTAs work with this?
Will OTAs work with these?
If I just want to upgrade my modem/baseband and then go back to LOS, do I just need to type "fastboot flash modem NON-HLOS.bin" or do I need to make a full install?
it works for moto g4 t1625 amazon version?? compilation number npj25.93-14.5 ?????? i answer this because in the web site motorola its appear the moto g4 rom xt1625 build MPJ24.139-64
Works!
I just want to say that I had a Moto G4 Plus (XT1642) that had no SIM recognition, no IMEI, no Wifi, and thanks to the instructions at the top of this thread, I now have it all.
I spent the whole day trying all sorts of things. Now it finally works!
Thanks!
How do I flash?
Hi friend, sorry but my English is not good.
My phone will receive nougat via OTA?
Something has broken my sound notifications
When I try this procedure I get a lot of these errors against some of the commands
(bootloader) Image aboot failed validation
(bootloader) Preflash validation failed
(bootloader) will fail: flash:aboot
FAILED (remote failure)
And now sounds that accompany any notifications from any applications fail to make any sound. Vibrate does initiate.
I am trying to find a way to enable hotspot on my ATT Moto G4 plus, if I flash this rom can anyone confirm it will unlock this feature? Torn between flashing or just going in to kernel and make change for this feature, any advice appreciated..
how to restore the sim slot after flash( i have no service)
i had frp, and after remove it with 3rd party tool i flash new rom.
now i have no service(but it detect the sim), there is any way to restore the sim slot?
i flashed the original rom from motorola site and it didnt help.
i flash the lineage OS and it didnt helped.
thanks
ggc201 said:
there is any way to restore the sim slot?
Click to expand...
Click to collapse
I've been searching for a fix for a few months now, whenever I get free time. Most threads about the subject die and aren't revisited. Someone will inevitably come to this page on a Google search wondering like us. I haven't found anything that will help and so I'm calling it quits. This phone is so outdated it would be better suited to find a deal somewhere else.
Thanks... can't find the button.
I have the xt1625 amz channel version and the: XT1625-XT1644_ATHENE-RETUS_6.0.1_MPJ24.139-48_cid50_subsidy-DEFAULT_CFC.xml.zip > provided enhanced LTE whereas the official OS did not support. I can actually do sh** on my phone without hanging up.
I want you and yours to be blessed forever and great post.
Bootloader is unlocked but somehow it is stuck between root and no root. Will figure it out....
Again... thanks... this is a big deal for me. :good:
non-developer edition?
If you have a developer edition or a moto with unlocked bootloader, Moto's own roms are flashable and *COMPLETELY WORKING*
Click to expand...
Click to collapse
Can anyone attest to having successfully flashed an unlocked non-developer edition G4 with this ROM? Motorola clearly warns against doing this:
IMPORTANT! Do not use these images/packages on non-developer edition devices or on devices with a locked bootloader.
Click to expand...
Click to collapse
(sorry, I'm a new member so I'm not allowed to include a link)
Hey guys
It all started with an OEM unlock and wanting to have Nougat update after flashing TWRP. Mobile network stopped working after flashing Nougat update ROM. Trying to fix that ended up with a hard brick (That's right. Only response I get from the phone is notification LED and Vibration)
Have been trying to fix it for past two weeks and all were dead ends. QFIL, QcomDloader and MI flash tool are some of the tools I have tried and given up. What left is MB swap. Need to be back to India in order to do it economically. Here in UK, I can get a new phone for the money to fix this one.
Do you guys know any ways I can try? Is there a firehose programmer available for P2a42's chipset? I have factory image for P2 with me (P2a42_S232_170320_ROW_fastboot).
ADB and fastboot are not recognising the phone. Device manager recognises it as Qualcomm HS-USB QLoader 9008 (COMX), value for X changes.
Below is the log for MI Flash tool.
[0.15 COM4]:[COM4]:start flash.
[2.18 COM4]:cannot receive hello packet,MiFlash is trying to reset status!
[4.77 COM4]:cannot receive hello packet,MiFlash is trying to reset status!
[7.27 COM4]:try to reset status.
[8.46 COM4]:write time out try agian 96
[9.97 COM4]:write time out try agian 97
[11.47 COM4]:write time out try agian 98
[13.00 COM4]:write time out try agian 99
[14.51 COM4]:write time out try agian 100
[15.13 COM4]:error:The write timed out.
[15.14 COM4]:error:The write timed out.
Any help is much appreciated. If you can't help, better not answer, as the admin says.
Did you get the firehouse file for flashing?
I have the same issue.
sisqin1 said:
Did you get the firehouse file for flashing?
I have the same issue.
Click to expand...
Click to collapse
Nope. I tried the firehose for P1. But not working. Can someone with a working P2 take a download and share? I know at least 3 people having the same issue.
Ronin1986 said:
Nope. I tried the firehose for P1. But not working. Can someone with a working P2 take a download and share? I know at least 3 people having the same issue.
Click to expand...
Click to collapse
It depends as how far you are bricked guys.
Are you able to enter fastboot?
Does the Lenovo P2 enter fastboot by itself?
You can use the factory images using fastboot to restore functionality.
I haven't come across a firehose for the Lenovo P2.
Usually those firehose flashers are signed to match the device's signature.
Unless someone leaks it somehow. I don't see how Mi-Flasher or QPST can work.
Both require the proper signed firehose.
celoxocis said:
It depends as how far you are bricked guys.
Are you able to enter fastboot?
Does the Lenovo P2 enter fastboot by itself?
You can use the factory images using fastboot to restore functionality.
I haven't come across a firehose for the Lenovo P2.
Usually those firehose flashers are signed to match the device's signature.
Unless someone leaks it somehow. I don't see how Mi-Flasher or QPST can work.
Both require the proper signed firehose.
Click to expand...
Click to collapse
From what I read, I think he is unable to access fastboot. So fastboot restore won't work
Siva Mk said:
From what I read, I think he is unable to access fastboot. So fastboot restore won't work
Click to expand...
Click to collapse
to my knowledge. previous firehose's weren't signed. you could use them from other devices with the same chipset.
i know that the SD820's uses a signed firehose. my main phone is as SD820. as the SD625 is from the same chipset-series (QC 2016).
they have added that "security feature" to prevent what was possible in the past.
in the old chipsets i would have recommend by try looking for a firehose that was successfully used on a device with the same chipset.
google search term would be "prog_emmc_firehose_8953" but as they are all signed now. the best hope would be:
A: wait for a leak for an EDL factory flasher. the chinese will probably leak one for the P2c72, it's just a matter of time.
B: try third party solutions such as this
remember we already have factory images. that can be flashed. currently only by fastboot.
those packages already contain the critical parts like: rawprogram0.xml and the images itself
all that is required is the proper signed firehose.
I am able to enter fastboot mode and also able to downgrade / upgrade from MM to N.
But the issue is with the modem, i am unable to make or receive any calls.
The carrier name shows up but there is no connectivity.
celoxocis said:
to my knowledge. previous firehose's weren't signed. you could use them from other devices with the same chipset.
i know that the SD820's uses a signed firehose. my main phone is as SD820. as the SD625 is from the same chipset-series (QC 2016).
they have added that "security feature" to prevent what was possible in the past.
in the old chipsets i would have recommend by try looking for a firehose that was successfully used on a device with the same chipset.
google search term would be "prog_emmc_firehose_8953" but as they are all signed now. the best hope would be:
A: wait for a leak for an EDL factory flasher. the chinese will probably leak one for the P2c72, it's just a matter of time.
B: try third party solutions such as this
remember we already have factory images. that can be flashed. currently only by fastboot.
those packages already contain the critical parts like: rawprogram0.xml and the images itself
all that is required is the proper signed firehose.
Click to expand...
Click to collapse
So if i have a P2c72 and yet the model say P2a42 in About Phone.. should i wait a certain time before unlocking my Leno device? I have exp. unlocking and using fastboot to do the neccesary for applying TWRP, and rooting.
Wmateria said:
So if i have a P2c72 and yet the model say P2a42 in About Phone.. should i wait a certain time before unlocking my Leno device? I have exp. unlocking and using fastboot to do the neccesary for applying TWRP, and rooting.
Click to expand...
Click to collapse
If you're asking about the 14 days wait then yes
---------- Post added at 03:53 AM ---------- Previous post was at 03:50 AM ----------
celoxocis said:
to my knowledge. previous firehose's weren't signed. you could use them from other devices with the same chipset.
i know that the SD820's uses a signed firehose. my main phone is as SD820. as the SD625 is from the same chipset-series (QC 2016).
they have added that "security feature" to prevent what was possible in the past.
in the old chipsets i would have recommend by try looking for a firehose that was successfully used on a device with the same chipset.
google search term would be "prog_emmc_firehose_8953" but as they are all signed now. the best hope would be:
A: wait for a leak for an EDL factory flasher. the chinese will probably leak one for the P2c72, it's just a matter of time.
B: try third party solutions such as this
remember we already have factory images. that can be flashed. currently only by fastboot.
those packages already contain the critical parts like: rawprogram0.xml and the images itself
all that is required is the proper signed firehose.
Click to expand...
Click to collapse
The firehose you mentioned is similar to that if Redmi note 3(I think). In that case miflash should work. Further more the XML file name maybe same but the file content maybe different. Don't have much knowledge on this. But have used all these.
No i'm asking is it safe to go through all that process.. cause it seems multiple people had had problems unlocking and flashing and end up bricking their phones. Oh and which TWRP to flash via ADB the 3.0.3-0 or the 3.1.0-3? I see that the 3.0.3.0 does not conform with the P2c72.. am trying to flash Lineage 13 that's why i ask about the 3.0.3-0.
Wmateria said:
No i'm asking is it safe to go through all that process.. cause it seems multiple people had had problems unlocking and flashing and end up bricking their phones. Oh and which TWRP to flash via ADB the 3.0.3-0 or the 3.1.0-3? I see that the 3.0.3.0 does not conform with the P2c72.. am trying to flash Lineage 13 that's why i ask about the 3.0.3-0.
Click to expand...
Click to collapse
I personally found TWRP bit too powerful. Be sure to read how to's and do's and don'ts before doing anything. One misstep, your device is bricked.
sisqin1 said:
I am able to enter fastboot mode and also able to downgrade / upgrade from MM to N.
But the issue is with the modem, i am unable to make or receive any calls.
The carrier name shows up but there is no connectivity.
Click to expand...
Click to collapse
I can't remember out of my head but I think the NON-HLOS.bin is included in the factory image package. It would be the one responsible for the modem.
Before you replace the partition make sure your device is the P2a42 or P2C72 and use appropriate modem image. You can't simply exchange them.
If exchanged wrongly. It could end up in:
A: bootloop
B: what you are describing. Unable to connect to a network.
My official TWRP can be used to flash that partition without entering fastboot.
Simply rename that .bin into *.img and select "install" browse the folder located and select "flash image". Select the image and select the modem partition, boot into system.
---------- Post added at 08:42 AM ---------- Previous post was at 08:32 AM ----------
Wmateria said:
So if i have a P2c72 and yet the model say P2a42 in About Phone.. should i wait a certain time before unlocking my Leno device? I have exp. unlocking and using fastboot to do the neccesary for applying TWRP, and rooting.
Click to expand...
Click to collapse
Sounds to me like you have one of those P2C72 which were flashed using the fastboot factory flasher with the P2a42 images. Leaving out the modem partition to make it multilingual. That Chinese shops, like to do to sell the Chinese version on the international market.
To answer your question, it depends all what your target is.
If you simply want to upgrade to stock Nougat.
You don't need to unlock the Bootloader.
As the fastboot factory flasher images are signed.
If you want root. That's another story.
Dump me your partition table details and I will see to build an TWRP that works for the P2C72.
I haven't read yet through all the threads and I'm not sure if the P2a42 TWRP works the P2c72.
It was probably already tested by users and
It should work but I think I saw at least one discrepancy in partition sizes when comparing the rawprogram0.xml file of both devices.
---------- Post added at 08:47 AM ---------- Previous post was at 08:42 AM ----------
Siva Mk said:
If you're asking about the 14 days wait then yes
---------- Post added at 03:53 AM ---------- Previous post was at 03:50 AM ----------
The firehose you mentioned is similar to that if Redmi note 3(I think). In that case miflash should work. Further more the XML file name maybe same but the file content maybe different. Don't have much knowledge on this. But have used all these.
Click to expand...
Click to collapse
I think you meant Redmi Note 4(x) codename mido. But like said above. To my knowledge the big change in the firehose's is they are all signed now.
I'm thinking it's due to the Chinese shops doing what I explained above and the company asking Snapdragon a way to prevent it. And we have what we have to today, signed firehose's that can only be used with the appropriate devices.
---------- Post added at 08:50 AM ---------- Previous post was at 08:47 AM ----------
Wmateria said:
No i'm asking is it safe to go through all that process.. cause it seems multiple people had had problems unlocking and flashing and end up bricking their phones. Oh and which TWRP to flash via ADB the 3.0.3-0 or the 3.1.0-3? I see that the 3.0.3.0 does not conform with the P2c72.. am trying to flash Lineage 13 that's why i ask about the 3.0.3-0.
Click to expand...
Click to collapse
Every TWRP outside my official TWRP thread is not based and compiled on sources but was "ported". Which introduces unknown issues. Stick with the TWRP's I made available. But like said. Dump me your partition table and in spare time I will build an P2C72 TWRP.
Hi celoxocis
Thank you for helping out!
My device is P2a42.
I have the NON-HLOS.bin which is included in the firmware file.
Just so i understand it correctly.
1) Update the TWRP recovery from https://forum.xda-developers.com/le...covery-unofficial-twrp-lenovo-p2-3-0-t3533659.
2) Rename the NON-HLOS.bin to NON-HLOS.img.
3) Flash it by using the "flash image" section.
4) Select the modem partation and boot into system.
I have an an Unlocked bootloader, when i tried previously to flash from fastboot using " fastboot flash modem NON-HLOS.bin " i used to get an error
writing 'modem'...
FAILED (remote: Do not allow to flash Bootloader image on Unlock device)
Would TWRP work flashing to modem partation?
celoxocis said:
I can't remember out of my head but I think the NON-HLOS.bin is included in the factory image package. It would be the one responsible for the modem.
Before you replace the partition make sure your device is the P2a42 or P2C72 and use appropriate modem image. You can't simply exchange them.
If exchanged wrongly. It could end up in:
A: bootloop
B: what you are describing. Unable to connect to a network.
My official TWRP can be used to flash that partition without entering fastboot.
Simply rename that .bin into *.img and select "install" browse the folder located and select "flash image". Select the image and select the modem partition, boot into system.
Click to expand...
Click to collapse
sisqin1 said:
Hi celoxocis
Thank you for helping out!
My device is P2a42.
I have the NON-HLOS.bin which is included in the firmware file.
Click to expand...
Click to collapse
That is correct.
However make sure your device is an P2c72 and use the proper NON-HLOS.bin file.
Best way would be to find the stock rom for the P2c72 and extract the zip file containing the right NON-HLOS.bin file.
As i stated I'm not sure the fastboot factory flasher package containts the NON-HLOS.bin file for the P2c72 its probably the one for the P2a42.
Thank you celoxocis,
My device is P2a42 which i have not changed or altered, do i still need to find the NON-HLOS.bin for P2c72 and flash it.
Or do i flash the NON-HLOS.bin for P2a42.
celoxocis said:
That is correct.
However make sure your device is an P2c72 and use the proper NON-HLOS.bin file.
Best way would be to find the stock rom for the P2c72 and extract the zip file containing the right NON-HLOS.bin file.
As i stated I'm not sure the fastboot factory flasher package containts the NON-HLOS.bin file for the P2c72 its probably the one for the P2a42.
Click to expand...
Click to collapse
sisqin1 said:
Thank you celoxocis,
My device is P2a42 which i have not changed or altered, do i still need to find the NON-HLOS.bin for P2c72 and flash it.
Or do i flash the NON-HLOS.bin for P2a42.
Click to expand...
Click to collapse
If you haven't changed and altered anything. Then there is no need to flash the modem partition.
The whole topic is about reviving a device?
I had used these commands and i was not able to make or receive calls.
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
I will try flashing the image and report back.
celoxocis said:
If you haven't changed and altered anything. Then there is no need to flash the modem partition.
The whole topic is about reviving a device?
Click to expand...
Click to collapse
sisqin1 said:
I had used these commands and i was not able to make or receive calls.
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
I will try flashing the image and report back.
Click to expand...
Click to collapse
I thought you said you didn't alter the device?
What's the sources of that NON-HLOS you flashed?
Make sure it is the right one.
It's simple.
P2A42 device must match NON-HLOS for P2a42
P2C72 device must match NON-HLOS for P2C72
You can NOT exchange them.
By alter I meant changing / flashing different firmware.
I have only unlocked the bootloader and downgraded to MM.
That's when I lost the network connectivity.
I ran the commands above to see if it resolves the issue and it did not.
I have the NON-HLOS for P2a42 which I downloaded. Bi when I try to flash using fast boot I get error.
Well, the only person i asked at the time that succesfully flashed roms was @Billytromp.. when he first attempted to flash DU Rom.. it didn't work and the LED flashed blue.. and then when flashed LOS 13.. it took 2 attempts for it to finally work. Um.. i dont think i can give you what you are asking since i have not dared to unlock and root my phone. Perhaps ask him since he is the only person i knew that has a P2c72.
----- With the release of OOS13, the modem issue no longer exist. Thank you all for the support & help with this unfortunate issue, we had to endure.... -----
EXPLICITLY FOR TMOBILE 9 PRO(I'm not responsible for your failure to read or bricked issues, but will help assist.)
NO MORE MODEM FLASHING!!!
Now the Fun Part (SIMPLE)
Backup your damn data!!!
1. Run TmoEU MSM
2. local update 11.2.10.10AA zip
(Global very important)
3A. OTA update OOS12, OTA to OOS13
3B. Regardless at this point. Re-run TmoEu Msm to Lock-in Modem !!!
Now follow again...
Reboot... Unlock, Local update to 10.10AA, and take the updates to OOS13....
AS LONG AS YOU ONLY USE TmoEU MSM as your unbrick tool
OOS/COS DATA FIX FOR A12 (ROOT) {DEPRECIATED}
MAGISK Module zip provided below...
((((Going to OOS12 & OOS13, Global build will need to be updated prior to taking A12 update. Only way data retain module will work.....))))
(link)
[TMO] OOS/COS DATA FIX
TO CLARIFY THIS IS A ROOT ONLY FIX After gaining root install given module. Data is now retained. Even after reboot(s). No empty slot or waiting. Issue is TMO variant is showing multi sim. So props were added to make it like a conversion to...
forum.xda-developers.com
---------------------------------------------------------------------
---ONLY USE TO GO BACK FOR WARRANTY & TRADE PURPOSES
Use Tmobile MSM (Stock) to go back to complete stock. For warrenty, trade in purposes. No!, modem will not stick after ota, duh
[WARNING!!!]--Do not use IN or EU MSM or you will not be able to go back to Tmobile stock(which voids everything with warrty, etc)
INCASE YOU MESSED UP OR HAD NO CHOICE BUT TO SAVE DEVICE BY USING IN OR EU MSM'S. THERE IS A FIX!!.
-Modded MSM to take you back to TMobile Stock.....
TMO_MSM(IN-EU_Return-to-Stock)
TMO_MSM(IN-EU_Return-to-Stock).zip
drive.google.com
----------------------------------------------------------------
Now everything you need is available here on XDA, but for convenience it's right here.
DOWNLOADSAll Files Located Here!!!
---------------------------------------------------------------------
FASTBOOT IMGS(A11 only)
(DO NOT FLASH MODEM IMG VIA OOS A12 & A13)
(CRASH DUMP & DEATH WILL OCCUR)
- This will be left here for users with Non-Tmo variant, but have T-mobile service and need access to bands.
- Just use modem flasher, unzip and run .bat file (A11 only)
visit TG for T-mobile 9 pro for community growth and helpful conversations
Join «T-Mobile Oneplus 9 Pro Support» on TELEGRAM
Donations welcomed:
CASHAPP
PAYPAL
First off I can't stress enough how much time and effort was put into this process, no amount of modem flashing, no signal, and device sacrifice would stop us. Not to mention this variant is treated with extreme prejudice from OnePlus ......
Special Thanks to:
@Jhoopes517
for stumbling upon signal still being there. The amount of replicating is to die for
@FizzyAps
for not sleeping, not even taking a damn break until it was explained & able to process
Without him T-mobile variant would be left in the dark.. So please appreciate his hard work and much more simplicity to come and for providing fastboot script
@twinnfamous
For providing data retain module.
In my experience, using my own modem seemed to work better, not exactly sure why. I got slower speeds flashing someone else's modem.
Not sure how that truly would effect.
Since TWRP is now functional
I've added a twrp file to restore Tmobile modem (11.2.5.5)
follow twrp guide above {post #1}
My apologies everyone. I provided an update to the twrp backup (above). Fixed issue where backup file wasn't showing in twrp... Again extract file from zip, move to twrp file on device...
Do you think this modem could benefit me any on AA version using TMobile as my provider or any ups or downs? I guess I could always try after making a backup to my modern, do y'all think so? Edit- I just flashed it and everything seems to be ok so far. How I did it was I made a backup of my modem, & then replaced the files with the ones you posted. Thanks
Samuel Holland said:
Do you think this modem could benefit me any on AA version using TMobile as my provider or any ups or downs?
Click to expand...
Click to collapse
Of course. As a temporary fix. Definitely best to MSM tool back to Tmobile and backup your modem images.
**Always backup
Libra420T said:
This thread is created to provide all who need T-Mobile Modem.img, from loss of service due to an OTA, Flashing, or EU Conversion..
Also to prevent cluttering up other threads with same question.
--- FASTBOOT IMG (11.2.3.3)
Unzip image, move to PC
Reboot to Bootloader
fastboot command
"fastboot flash modem *modem.img"
*Replace modem with tmobile modem.
Flash A/B
---TWRP BACKUPS (11.2.5.5)
Unzip file, move to twrp folder
reboot recovery, Restore, Select file,
Flash on Modem partition, reboot
Good luck & Happy Flashing
**Edit:
If from Tmobile, flashing to custom rom service will be fine. since dual sim isn't a thing for NA..
-If using EU conversion to avoid unlock.bin, then you absolutely need to flash modem after every update...
***Reason to use:
OTA update causes Tmo modem to be replaced..
-EU does the same...
-Or just want Tmo modem instead of stock because you have tmobile service.
img=11.2.3.3 twrp zip=11.2.5.
Click to expand...
Click to collapse
anyone experience on qulacome dump crush page ??after flashing tmobile modem
?
car king said:
anyone experience on qulacome dump crush page ??after flashing tmobile modem
?
Click to expand...
Click to collapse
which process u using, fastboot or twrp?
Otherwise imgs are clean and work perfectly. Provide process if u don't mind..
Libra420T said:
which process u using, fastboot or twrp?
Otherwise imgs are clean and work perfectly. Provide process if u don't mind..
Click to expand...
Click to collapse
fastboot using on color os
load android 12 then downgrade to color os which i want to test out, need to flash modem to get data . the android 12 modem works fine ...only 4G so try to use Tmobile modem but no luck
Although I have managed to root, use Magisk, flash Omega multiple times, take OnePlus updates, I am unsure about the instructions in the first post. It seems like a mixture of steps and comments. Sorry for my noob-ness. Can I flash this modem (I am a TMobile user) using Franco Kernal Manager? If not can someone list the exact steps for fastboot?
Thanks, I appreciate it!
car king said:
fastboot using on color os
load android 12 then downgrade to color os which i want to test out, need to flash modem to get data . the android 12 modem works fine ...only 4G so try to use Tmobile modem but no luck
Click to expand...
Click to collapse
pretty sure android is issue. tmo modem came from A11 so not sure
I pulled the modem files to the 11.2.5.5 T-Mobile firmware for the OnePlus 9 Pro if you want them. If it helps anyone. I do seem to get much better service on the 5.5 modem than I did with the 2.2 modem.
In my room, I always got 1 to 2 bars. I now get 3 to 4. Granted, I use Wi-Fi most of the time, but my 5G is faster than the Wi-Fi here due to not being able to get good internet out here.
TheKnux said:
I pulled the modem files to the 11.2.5.5 T-Mobile firmware for the OnePlus 9 Pro if you want them. If it helps anyone. I do seem to get much better service on the 5.5 modem than I did with the 2.2 modem.
In my room, I always got 1 to 2 bars. I now get 3 to 4. Granted, I use Wi-Fi most of the time, but my 5G is faster than the Wi-Fi here due to not being able to get good internet out here.
Click to expand...
Click to collapse
yes of course if you have 5.5 img please upload , I only have 5.5 for twrp and 3.3 as img.
Okay, gimme a few. Gotta start up my ancient laptop and throw it on the otg drive, upload it to gdrive, and I'll post the link here.
Edit: Link Posted. https://drive.google.com/drive/folders/1LFEy0q58Dke1t_Uh7bdTxdp-wY0YFs_Z?usp=sharing
Modem_a/_b are fastboot flashable. Modemst1/st2 have to be flashed via fastbootd.
Fastboot flash modem_a modem_a.img
Fastboot flash mkdem_b modem_b.img
Fastboot reboot fastboot
Fastboot flash modemst1 modemst1.img
Fastboot flash modemst2 modemst2.img
Fastboot reboot
These can also be replaced in payload.bin firmware fastboot roms. Just extract via payload dumper, place these modem files into the rom, then fastboot flashall in fastbootd.
.
TheKnux said:
Okay, gimme a few. Gotta start up my ancient laptop and throw it on the otg drive, upload it to gdrive, and I'll post the link here.
Edit: Link Posted. https://drive.google.com/drive/folders/1LFEy0q58Dke1t_Uh7bdTxdp-wY0YFs_Z?usp=sharing
Modem_a/_b are fastboot flashable. Modemst1/st2 have to be flashed via fastbootd.
Fastboot flash modem_a modem_a.img
Fastboot flash mkdem_b mkdem_b.img
Fastboot reboot fastboot
Fastboot flash modemst1 modemst1.img
Fastboot flash modemst2 modemst2.img
Fastboot reboot
These can also be replaced in payload.bin firmware fastboot roms. Just extract via payload dumper, place these modem files into the rom, then fastboot flashall in fastbootd.
Click to expand...
Click to collapse
There is typo in the 2nd fastboot cmd.
I got the following error when fastboot flash modemst1/2...
fastboot flash modemst1 modemst1.img
target reported max download size of 805306368 bytes
sending 'modemst1' (3072 KB)...
OKAY [ 0.077s]
writing 'modemst1'...
FAILED (remote: Flashing is not allowed for Critical Partitions
)
Holy crap guys,
don't mess with or share modemst1/2
don't mess with or share modemst1/2
don't mess with or share modemst1/2
don't mess with or share modemst1/2
don't mess with or share modemst1/2
don't mess with or share modemst1/2
don't mess with or share modemst1/2
don't mess with or share modemst1/2
DON'T MESS WITH OR SHARE MODEMST1/2
It contains your device specific info, device specific NV data, IMEI, etc. Flashing someone else's modemst will screw up your device and lose all cellular capability (and you are completely SOL if you don't have a backup), and someone with your modemst might be able to clone your IMEI.
This is why my guides all tell you to back them up, so you can restore it in case something goes wrong. You should not be messing with it unless you know what you're doing.
The only modem file you need to flash on to a OP9P conversion is modem.bin, AKA NON-HLOS.
craznazn said:
Holy crap guys,
don't mess with or share modemst1/2
don't mess with or share modemst1/2
don't mess with or share modemst1/2
don't mess with or share modemst1/2
don't mess with or share modemst1/2
don't mess with or share modemst1/2
don't mess with or share modemst1/2
don't mess with or share modemst1/2
DON'T MESS WITH OR SHARE MODEMST1/2
It contains your device specific info and IMEI. Flashing someone else's modemst will screw up your device and lose your IMEI / all cellular capability (if you don't have a backup), and someone with your modemst might be able to clone your IMEI.
The only modem file you need to flash on to a OP9P is modem.bin, AKA NON-HLOS.
Click to expand...
Click to collapse
So flashing the 2 cmds below should still be good for modem, right?
fastboot flash modem_a modem_a.img
fastboot flash modem_b modem_b.img
avid_droid said:
Question: op9, I have converted from tmobile to Global(AA) and have experienced no calls inbound/outbound. Flashed non-hlos from Tmo and things got worse. Wondering if the 11.2.5.5 on AA will persist with issue or resolve. The one I flashed was from 11.2.3.3 I believe
Click to expand...
Click to collapse
Don't use a OP9P NON-HLOS on a OP9, there are obvious differences.
xpdragon said:
So flashing the 2 cmds below should still be good for modem, right?
fastboot flash modem_a modem_a.img
fastboot flash modem_b modem_b.img
Click to expand...
Click to collapse
Yes, that should be the only thing you touch