i have a arc on .62 and have been looking around this site and others for the last couple of days
1) so from what i under stand i have 2 options in rooting this phone downgrade to .48 or flash a pre rooted rom on it like the Pre-rooted_LT15i_4.0.2.A.0.62_Generic Global World (.img file) i found in one of the posts on this site? (i dont see the point of downgrading if i can flash the same rom thats rooted)
2) i have downloaded the flash tool and the above rom but how do i use it?
3) how do i have to boot the phone up to flash the rom?
my last 2 phones (wildfire and San Francisco) seemed easy compared to this one im so confused and dont wanna mess it up please help me
Hey there...
To flash it you're going to need to use fastboot... Have you unlocked the bootloader??? If so, then use fastboot from the android SDK tools to flash it... On the post you downloaded the img file must have the installation guide... If not then you're going to need to do it!!!
But I think your first step should be to read this post very carefully... Then you start playing around with your phone... It's long, but very complete...
Cheers!!!
this should help
http://forum.xda-developers.com/showthread.php?t=1304634
mariolcneto said:
Hey there...
To flash it you're going to need to use fastboot... Have you unlocked the bootloader??? If so, then use fastboot from the android SDK tools to flash it... On the post you downloaded the img file must have the installation guide... If not then you're going to need to do it!!!
But I think your first step should be to read this post very carefully... Then you start playing around with your phone... It's long, but very complete...
Cheers!!!
Click to expand...
Click to collapse
unlocked the bootloader? i found some drivers and the flashtool sees the phone in fastboot dose this mean the bootloader is unlocked? if not how do i know if it is unlocked? i got the phone 2nd hand and have been told it has had a couple of updates
Updates... lol... It probably IS unlocked then... But to make sure, check this post...
Since you're new in the Xperia line, read both the thread I sent on my first message and the one kenooi1984 sent... They are both great to get you introduced to your phone's full capabilities...
Cheers...
So I just got my nexus 5x and it looks like I cant just do the simple fastboot oem unlock and then flash twrp image, which makes me sad (I thought unlocking your phone was pretty much a red flag for "im going to do things to you" so why all the new "security" measures?). Since I'm on the latest update MHC19J, and it seems a modified boot image is not available (unless Im just overlooking it) am I just kinda stuck at the moment until said image is available? (sans the "yeah you could just modify one yourself" comment).
What are you talking about? Before unlocking have you checked OEM unlocking from Developer tools? After this you need to flash Twrp, boot into it directly from bootloader and flash SUPERSU. That should be the minimal steps in order to keep the custom recovery in place.
HaiKaiDo said:
So I just got my nexus 5x and it looks like I cant just do the simple fastboot oem unlock and then flash twrp image, which makes me sad (I thought unlocking your phone was pretty much a red flag for "im going to do things to you" so why all the new "security" measures?). Since I'm on the latest update MHC19J, and it seems a modified boot image is not available (unless Im just overlooking it) am I just kinda stuck at the moment until said image is available? (sans the "yeah you could just modify one yourself" comment).
Click to expand...
Click to collapse
There is a guide and a sticky roll up that have had a lot of time spent writing up with all this info in them.
Supersu modifies the image itself.
You do need some knowledge so take a look at the howto conversation http://forum.xda-developers.com/showthread.php?t=3206930
, this is my go to tool since my Nexus 4 http://forum.xda-developers.com/showthread.php?t=3258492
Darke5tShad0w said:
There is a guide and a sticky roll up that have had a lot of time spent writing up with all this info in them.
Supersu modifies the image itself.
Click to expand...
Click to collapse
I should have included in my post that Im only seeking help after reading everything I could find and still being at a loss. Perhaps i misunderstood the directions, or maybe the fact that Im not looking to root my device, only flash twrp and move to a custom rom right away, that Ive overlooked a step as ive ignored all the rooting steps.
So this guide says to just unlock your device (i have) and then just run fastboot flash recovery twrp.img (also did this) and I should be good (it didnt work, it gave me that warning screen).
http://forum.xda-developers.com/nexus-5x/general/guides-how-to-guides-beginners-t3206930
This guide looks slightly different:
http://forum.xda-developers.com/nexus-5x/general/guide-how-to-install-custom-recovery-t3231143
1]Unlock bootloader- fastboot oem unlock [select yes by pressing volume up and then power button to confirm]
2] Reboot & skip everything in setup as we data will be wiped again!
3] Reboot into bootloader & flash the modified boot image- fastboot flash boot boot.img (This is the part that im asking about as there doesnt appear to be a modified image for me to flash)
4] Reboot into system to make sure it's booting properly! [May not be necessary!]
5] Reboot into bootloader again & flash twrp- fastboot flash recovery "recovery name".img
This is really what I want to achieve. Disabling Encryption and flashing TWRP so I can flash a custom rom. Not interested in the slightest about rooting a stock rom.
So thats where im stuck,no worries, I did attempt to RTFM :]
HaiKaiDo said:
I should have included in my post that Im only seeking help after reading everything I could find and still being at a loss. Perhaps i misunderstood the directions, or maybe the fact that Im not looking to root my device, only flash twrp and move to a custom rom right away, that Ive overlooked a step as ive ignored all the rooting steps.
So this guide says to just unlock your device (i have) and then just run fastboot flash recovery twrp.img (also did this) and I should be good (it didnt work, it gave me that warning screen).
http://forum.xda-developers.com/nexus-5x/general/guides-how-to-guides-beginners-t3206930
This guide looks slightly different:
http://forum.xda-developers.com/nexus-5x/general/guide-how-to-install-custom-recovery-t3231143
1]Unlock bootloader- fastboot oem unlock [select yes by pressing volume up and then power button to confirm]
2] Reboot & skip everything in setup as we data will be wiped again!
3] Reboot into bootloader & flash the modified boot image- fastboot flash boot boot.img (This is the part that im asking about as there doesnt appear to be a modified image for me to flash)
4] Reboot into system to make sure it's booting properly! [May not be necessary!]
5] Reboot into bootloader again & flash twrp- fastboot flash recovery "recovery name".img
This is really what I want to achieve. Disabling Encryption and flashing TWRP so I can flash a custom rom. Not interested in the slightest about rooting a stock rom.
So thats where im stuck,no worries, I did attempt to RTFM :]
Click to expand...
Click to collapse
You're not following the right guide. You don't have to bother with encryption, just use the latest twrp after unlocking the bootloader and flash that IMG file in fastboot. Twrp works with encryption now you don't have to decrypt
Use this guide and follow steps one and two http://forum.xda-developers.com/nexus-5x/general/guides-how-to-guides-beginners-t3206930
wtoj34 said:
You're not following the right guide. You don't have to bother with encryption, just use the latest twrp after unlocking the bootloader and flash that IMG file in fastboot. Twrp works with encryption now you don't have to decrypt
Use this guide and follow steps one and two http://forum.xda-developers.com/nexus-5x/general/guides-how-to-guides-beginners-t3206930
Click to expand...
Click to collapse
Thanks for the reply. I wonder what went wrong the first time though. Cause i did unlock the bootloader, rebooted and let android load, rebooted into bootloader and flashed twrp 3.0.0.0 and it gave me a weird "cannot be verified" message when I tried to boot into recovery.
HaiKaiDo said:
Thanks for the reply. I wonder what went wrong the first time though. Cause i did unlock the bootloader, rebooted and let android load, rebooted into bootloader and flashed twrp 3.0.0.0 and it gave me a weird "cannot be verified" message when I tried to boot into recovery.
Click to expand...
Click to collapse
That happens on Nexus phones. Just give it a second and it'll boot up. It's just a warning telling that you unlocked the bootloader. Make sure you're using the very latest version of twrp available in the site, it ends in a 1 I believe
wtoj34 said:
That happens on Nexus phones. Just give it a second and it'll boot up. It's just a warning telling that you unlocked the bootloader. Make sure you're using the very latest version of twrp available in the site, it ends in a 1 I believe
Click to expand...
Click to collapse
Ahh ok, thanks for info. I think ill run the flash back to stock and give it a fresh try. Is there any plus to being un-encrypted btw?
Thanks again!
Well i went and redid everything the same way I did the first time and it worked! I must done something stupid the first time. Guess this thread was for nothing! xD Thanks for clarifying some things for me though guys.
HaiKaiDo said:
Ahh ok, thanks for info. I think ill run the flash back to stock and give it a fresh try. Is there any plus to being un-encrypted btw?
Thanks again!
Click to expand...
Click to collapse
Disabling encryption does give you a speed increase. It may or may not be noticeable for your use but the majority can see the difference.
So you have to decide between security and a snappier phone.
Just remember to back all your data up as this requires wiping your data and possibly a clean flash and either switching from the stock rom to another rom(Most have the forced encryption disabled) or when on stock rom either flash another kernel or flash supersu in systemless mode.
Hotspot need it Help! Nexus 5x
Ok, so I have a Nexus 5 and a Nexus 5X. I want to keep the Nexus 5x because has more features, but I cannot share the data from my provider cricket wireless (AT&T).
I have the option to return it or find a solution. I am pretty stubborn which means FIX IT. I have the March 1 2016 Update and this MHC19J shows up in the build version... I am under linux, last time I did this was well long time since 2013 for the nexus 5. Can some one help me with a guide for linux.
THANKS A LOT!!!
Varsismaname said:
Ok, so I have a Nexus 5 and a Nexus 5X. I want to keep the Nexus 5x because has more features, but I cannot share the data from my provider cricket wireless (AT&T).
I have the option to return it or find a solution. I am pretty stubborn which means FIX IT. I have the March 1 2016 Update and this MHC19J shows up in the build version... I am under linux, last time I did this was well long time since 2013 for the nexus 5. Can some one help me with a guide for linux.
THANKS A LOT!!!
Click to expand...
Click to collapse
You need to go and start your own thread in the q&a section, its not polite to high jack someone else's.
just got my pixel xl today. unlocked the bootloader fine.
next step flash twrp. i fastboot boot twrp img. temp twrp , installed the zip.. i reboot to recovery. that where everything F up.. now i can not get into fastboot.. is there a way for me to get fastboot mode back ??
never mind just had to reboot the phone 3 times..
Hello. I think I am near you. I was on the latest stock 7.1.2 of may. Unlocked bootloader ok. Then boot the TWRP and flash the TWRP zip. After that I have bootloop all time. I can put the phone in bootloader but now my phone is not recognised by the computer. The first time I connected the phone he asked me what to do and I said transfers data. But now I cannot do anything.
How did you get in fastboot mode???
Any idea how to help me???
I really appreciate help!!
sytayeth said:
Hello. I think I am near you. I was on the latest stock 7.1.2 of may. Unlocked bootloader ok. Then boot the TWRP and flash the TWRP zip. After that I have bootloop all time. I can put the phone in bootloader but now my phone is not recognised by the computer. The first time I connected the phone he asked me what to do and I said transfers data. But now I cannot do anything.
How did you get in fastboot mode???
Any idea how to help me???
I really appreciate help!!
Click to expand...
Click to collapse
Hello,
You need to read this post: https://forum.xda-developers.com/an...signing-boot-images-android-verified-t3600606
The thread contains a zip (verified boot signer v2 zip) that you must install right after you install the TWRP zip on latest May version...
This is weird your phone is not recognized while in bootloader.
Boot the bootloader and issue:
fastboot devices
Does it output your serial number in the command prompt?
Good luck...
5.1 said:
Hello,
You need to read this post: https://forum.xda-developers.com/an...signing-boot-images-android-verified-t3600606
The thread contains a zip (verified boot signer v2 zip) that you must install right after you install the TWRP zip on latest May version...
This is weird your phone is not recognized while in bootloader.
Boot the bootloader and issue:
fastboot devices
Does it output your serial number in the command prompt?
Good luck...
Click to expand...
Click to collapse
Thank for your answer. The real problem was that in fastboot the phone is not recognised. There were no serial number. And I write in past because I could made it work.
I am very happy you worried about me. You have a new friend in Spain.
Thanks.
sytayeth said:
Thank for your answer. The real problem was that in fastboot the phone is not recognised. There were no serial number. And I write in past because I could made it work.
I am very happy you worried about me. You have a new friend in Spain.
Thanks.
Click to expand...
Click to collapse
Hey,
No problem. Glad you solved it by yourself anyway. What was the issue? Maybe others with the same problem could benefit from your experience?
Why your computer didn't recognized your phone while in bootloader?
Cheers...
5.1 said:
Hey,
No problem. Glad you solved it by yourself anyway. What was the issue? Maybe others with the same problem could benefit from your experience?
Why your computer didn't recognized your phone while in bootloader?
Cheers...
Click to expand...
Click to collapse
I really don't know the problem. I was just about to cry when I saw a post about skipsoft toolkit. And I thought why not to try. I installed that software in other pc, follow the instructions and now I am here again.
Yesssss!!!!
sytayeth said:
I really don't know the problem. I was just about to cry when I saw a post about skipsoft toolkit. And I thought why not to try. I installed that software in other pc, follow the instructions and now I am here again.
Yesssss!!!!
Click to expand...
Click to collapse
You shouldn't be modding you're device if you have to rely on a toolkit to save you. What if there wasn't a toolkit. You'd be SOL.
I highly recommend you learn how to use fastboot and adb, and do this stuff the right way. I'm not trying to be mean or anything. I just would hate to see you brick you're device. These pixel phones cost way too much to be screwing around with if you don't know what you're doing.
toknitup420 said:
You shouldn't be modding you're device if you have to rely on a toolkit to save you. What if there wasn't a toolkit. You'd be SOL.
I highly recommend you learn how to use fastboot and adb, and do this stuff the right way. I'm not trying to be mean or anything. I just would hate to see you brick you're device. These pixel phones cost way too much to be screwing around with if you don't know what you're doing.
Click to expand...
Click to collapse
Thanks. I am trying to learn. Not only fastboot or adb. English too. But sometimes I am a bit risky or only stupid.
By the way, recommend me a post or a place to learn.
sytayeth said:
Thanks. I am trying to learn. Not only fastboot or adb. English too. But sometimes I am a bit risky or only stupid.
By the way, recommend me a post or a place to learn.
Click to expand...
Click to collapse
Honestly the best way I found to learn adb and fastboot is YouTube. It's so much easier to watch how to do it. Thats how I learned. There's also @Heisenberg 6p guide. That can get you all setup for adb and fastboot too. It's very comprehensive.
https://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928
toknitup420 said:
Honestly the best way I found to learn adb and fastboot is YouTube. It's so much easier to watch how to do it. Thats how I learned. There's also @Heisenberg 6p guide. That can get you all setup for adb and fastboot too. It's very comprehensive.
https://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928
Click to expand...
Click to collapse
Thanks. I'll try.
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!!
Locked my boatloader by mistake now it won't boots I need help ASAP.... I'm losing my mind over here I need someone to help me please for the love of God somebody... Just bought this phone for like $1,000 and now I'm looking at a ****ing brick......
no worries, you technically cant brick it that easily.
Check the MSM thread for your exact model and follow the steps get it back and running again.
^ Yeah an MSM flash will have you right as rain. Just wondering how the you locked the bootloader "by mistake" that seems like a difficult mistake to make.
was trying to restore and forgot how op works lol...i got it fixed now. while your here, how can i flash twrp and flash a rom? having issues with this now..
Anybody have any ideas of how I can ROM my phone? Been sitting here trying to do it for the last I don't know how long now
So I'm not sure about YOUR phone, if you have a recovery partition you can just flash recovery, if you don't have a recovery partition then you need to fastboot boot twrp first. And there are a few ways to flash a rom, my recommendation would be Fastboot Enhance I personally haven't tried it yet but it seems to work pretty good and even though it's in the 8T category it should work fine. Now one thing that is noteworthy with Fastboot enhance though is that it flashes the current slot instead of the inactive slot.
this.guy.lol said:
Anybody have any ideas of how I can ROM my phone? Been sitting here trying to do it for the last I don't know how long now
Click to expand...
Click to collapse
Didn't reply accidently, not the first time I've done that. Read my previous post.
Brandon.Bissonnette said:
Didn't reply accidently, not the first time I've done that. Read my previous post.
Click to expand...
Click to collapse
thx man