Database Info

Can't load fastboot??

I'm trying to get into fastboot
reboot while holding vol down
select the USB icon and press vol up
but I am stuck at "Starting Fastboot USB download protocol"
am i doing something wrong?

xdeslitx said:
I'm trying to get into fastboot
reboot while holding vol down
select the USB icon and press vol up
but I am stuck at "Starting Fastboot USB download protocol"
am i doing something wrong?
Click to expand...
Click to collapse
No you are doing it right. THAT IS IS FASTBOOT. If you run the fastboot commands from your pc you will see it working on the pc.

xdeslitx said:
I'm trying to get into fastboot
reboot while holding vol down
select the USB icon and press vol up
but I am stuck at "Starting Fastboot USB download protocol"
am i doing something wrong?
Click to expand...
Click to collapse
sbdags said:
No you are doing it right. THAT IS IS FASTBOOT. If you run the fastboot commands from your pc you will see it working on the pc.
Click to expand...
Click to collapse
The above is correct, you are in fastboot if you see this (similar to download mode on samsung devices for use with ODIN).
Be sure to add path to environmental variables so that you can use fastboot commands at prompt (if in NT (windows) environment)

sbdags said:
No you are doing it right. THAT IS IS FASTBOOT. If you run the fastboot commands from your pc you will see it working on the pc.
Click to expand...
Click to collapse
i tried running the command " fastboot devices" and it doesnt see my tf700
i have all drivers loaded

Poser said:
The above is correct, you are in fastboot if you see this (similar to download mode on samsung devices for use with ODIN).
Be sure to add path to environmental variables so that you can use fastboot commands at prompt (if in NT (windows) environment)
Click to expand...
Click to collapse
i added the path to environmental variables.

Fastboot works fine for me.
Suggest you go over to the nvflash thread and download the windows drivers.
---------- Post added at 07:54 PM ---------- Previous post was at 07:52 PM ----------
xdeslitx said:
i tried running the command " fastboot devices" and it doesnt see my tf700
i have all drivers loaded
Click to expand...
Click to collapse
Isn't that adb commands you are trying to run. I.e., adb devices. I think you are confusing fastboot.
What are you trying to do?

sbdags said:
Fastboot works fine for me.
Suggest you go over to the nvflash thread and download the windows drivers.
---------- Post added at 07:54 PM ---------- Previous post was at 07:52 PM ----------
Isn't that adb commands you are trying to run. I.e., adb devices. I think you are confusing fastboot.
What are you trying to do?
Click to expand...
Click to collapse
fastboot devices is also a fastboot command from what i understand...i was trying to run that command to see if the computer can even see my tablet in fastboot...which it doesnt.
and i actually did get the drivers from the nvflash thread because that's what i am trying to accomplish
what does your tablet look like when you are in fastboot mode?
because i am doubting the fact that mine is even in that mode...i get the feeling that it gets stuck when trying to load fastboot

xdeslitx said:
fastboot devices is also a fastboot command from what i understand...i was trying to run that command to see if the computer can even see my tablet in fastboot...which it doesnt.
and i actually did get the drivers from the nvflash thread because that's what i am trying to accomplish
what does your tablet look like when you are in fastboot mode?
because i am doubting the fact that mine is even in that mode...i get the feeling that it gets stuck when trying to load fastboot
Click to expand...
Click to collapse
It just says starting Fastboot mode. It never changes from that.

im going to try and uninstall/reinstall the drivers to see if thatll work

finally got it to work...had to reload my drivers
haha so i did the whole nvflash thing but i dont really know how it works
all i know is that itll keep me from bricking my tf700

xdeslitx said:
finally got it to work...had to reload my drivers
haha so i did the whole nvflash thing but i dont really know how it works
all i know is that itll keep me from bricking my tf700
Click to expand...
Click to collapse
You can still brick your device but it's 100% recoverable, at least if it's not a hardware failure. Just make sure to keep your backup files safe.

Pretoriano80 said:
You can still brick your device but it's 100% recoverable, at least if it's not a hardware failure. Just make sure to keep your backup files safe.
Click to expand...
Click to collapse
are there any instructions on how to recover using these files in case of brick?
i didnt see any on the thread under development

xdeslitx said:
are there any instructions on how to recover using these files in case of brick?
i didnt see any on the thread under development
Click to expand...
Click to collapse
There's no guide so far, but i'm sure you would get some help from xda users when needed.

cool thanks for the replies

I'm stuck at fastboot mode with my TF700. Windows XP recognizes my device but the command "fastboot devices" doesn't show up my TF700. I tried to reinstall drivers from univeral naked drivers package 0.7 with success - tried it three times. Bootet up TF700 in fastboot mode but still fastboot doesn't see my device.
Has anyone an idea what I can do? I tried it also in my virtual linux machine without succes. I want to flash new CWM recovery over old TWRP recovery to update to JB and after this to get proprietary files needed to build CM10 from sources.
As I understand, without fastboot, I can't update my bootloader to JB. Not a nice device...

thunderger said:
I'm stuck at fastboot mode with my TF700. Windows XP recognizes my device but the command "fastboot devices" doesn't show up my TF700. I tried to reinstall drivers from univeral naked drivers package 0.7 with success - tried it three times. Bootet up TF700 in fastboot mode but still fastboot doesn't see my device.
Has anyone an idea what I can do? I tried it also in my virtual linux machine without succes. I want to flash new CWM recovery over old TWRP recovery to update to JB and after this to get proprietary files needed to build CM10 from sources.
As I understand, without fastboot, I can't update my bootloader to JB. Not a nice device...
Click to expand...
Click to collapse
Try to use this command to check if fastboot it's working : " fastboot -i 0x0b05 reboot ". If your device reboot after sending that command it means you can use fastboot just fine.
To be honest i've seen many bricks reports from people that tried to only flash the JB bootloader so imo the best way to get the JB bootloader is to flash the official JB firmware, then install the latest TWRP OR CWM recovery via fastboot, use the custom recovery to make a backup of the stock rom. Once you've did all that you can install CM10 just fine but also you will have the opportunity to go back to stock JB in case you need to.

thunderger said:
I'm stuck at fastboot mode with my TF700. Windows XP recognizes my device but the command "fastboot devices" doesn't show up my TF700. I tried to reinstall drivers from univeral naked drivers package 0.7 with success - tried it three times. Bootet up TF700 in fastboot mode but still fastboot doesn't see my device.
Has anyone an idea what I can do? I tried it also in my virtual linux machine without succes. I want to flash new CWM recovery over old TWRP recovery to update to JB and after this to get proprietary files needed to build CM10 from sources.
As I understand, without fastboot, I can't update my bootloader to JB. Not a nice device...
Click to expand...
Click to collapse
Fastboot devices does not work on this device. I've used fastboot to swap recovery images several times and update to the JB bootloader by itself. It definitely works as a whole.

Pretoriano80 said:
Try to use this command to check if fastboot it's working : " fastboot -i 0x0b05 reboot ". If your device reboot after sending that command it means you can use fastboot just fine.
To be honest i've seen many bricks reports from people that tried to only flash the JB bootloader so imo the best way to get the JB bootloader is to flash the official JB firmware, then install the latest TWRP OR CWM recovery via fastboot, use the custom recovery to make a backup of the stock rom. Once you've did all that you can install CM10 just fine but also you will have the opportunity to go back to stock JB in case you need to.
Click to expand...
Click to collapse
I've tried this command many times, and all I ever get is < waiting for device > and nothing else. This is getting annoying as hell. I've tried so many different things, all with the same result. I guess I'll just have to wait until there is an exploit found to root the JB firmware without having to use fastboot, then use TWRP from Goomanager, and hopefully by then there will be a zip of CWM Recovery.

Help! Might be bricked? Confused.

So i bought a htc one xl on craigslist a few months ago. I downloaded an app to check if its rooted and it said it was. Long story short i think i downloaded the wrong rom and i cleared everything from TWRP. I really have no business doing anything like this.. Now im stuck. I can get to the bootloader mode screen but when i got to recovery it takes me to twrp. I hope i didn't screw it up too bad. TWRP says "no os" also.
Any help would be appreciated! Im done with messing with rooting and such i don't want to mess up my phone anymore.
ps: I didn't do a backup.

Download the right Rom to your computer lets make it viper xl to make things easy once done downloaded mount usb storage in twrp drag the Rom over... Factory reset and flash the Rom and you're good

It installed fine and everything but its been at the viper xl loading screen for 10 minutes. Any reason why its doing this?

Do you have hboot 1.14? And did you factory reset

Yes and Yes

You still have the zip on your computer right? So I guess we're going to have to fastboot the boot.img which is very simple I'll give you a quick tutorial in a sec
---------- Post added at 01:20 AM ---------- Previous post was at 01:19 AM ----------
http://forum.xda-developers.com/attachment.php?attachmentid=1179735&d=1344782533
---------- Post added at 01:22 AM ---------- Previous post was at 01:20 AM ----------
Flashing boot img through fastboot...
download the file in the link which above which will include adb and fastboot....put that on your computer somewhere you can find it.. now take the boot image out of the Rom zip and place it in that folder... Boot your phone into bootloader scroll down and select fastboot and now open a command prompt with in the fastbootbadb folder on your comp and type to command without the quotes "fastboot flash boot boot.img"

I extract the fastboot folder right? I did that and its "saying waiting for device".

Install the drivers

Sorry but where do i find those?

Alright i think i did it right it said finish in the command prop. Now what do i do?

1991birdofprey said:
Alright i think i did it right it said finish in the command prop. Now what do i do?
Click to expand...
Click to collapse
If you have adb/fastboot installed, have a copy if the rom on your phone and also the computer for less confusion. On your computer, extract to rom and copy the boot.img INSIDE your adb/fastboot folder.
Enter boot loader on your phone, (white screen 3 skating droids). Make sure it says fast boot usb. Run a simple command like "fastboot devices" and see if something shows up. If so, proceed. If not, restart computer or make sure drivers are installed.
On your computer, right click on the adb folder and choose "open command prompt here" in the cmd window type->
Fastboot flash boot boot.img
Upon success, immediately boot into recovery (twrp) and flash (install) the entire rom.
Profit
Sent from my HTC One XL using Tapatalk 2

Thanks a bunch guys! I thought i lost my phone! Everything worked!

[Q&A] **TWRP** custom recovery for IDOL3 6045

Q&A for **TWRP** custom recovery for IDOL3 6045
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.
Before posting, please use the forum search and read through the discussion thread for **TWRP** custom recovery for IDOL3 6045. If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.
Thanks for understanding and for helping to keep XDA neat and tidy!

stuck on twrp bootloop
stuck on twrp boot loop. any suggestions? i followed instructions as posted, but when rebooted into twrp and tried to reboot system, i keep going back to twrp. thanks

Heyy
I have the same problem,, although i did a backup and then a deleted everything cause it was looping,,, how do i fix everything to the original condition,, i won't be doing this again,, my model is an i version.. Although mine is not booting into twrp ,, just the original..

Restoring my backup does not work

I tryed everything,, i know not to do this anymore I think it's broke forever.

If you can get into twrp it can most likely be fixed.
Download the system image and try to install it. May need to put it on sdcard or USB otg.
This is all Alcatel's fault for not releasing anything when we kindly asked...

Where is the system image?
neilownz said:
If you can get into twrp it can most likely be fixed.
Download the system image and try to install it. May need to put it on sdcard or USB otg.
This is all Alcatel's fault for not releasing anything when we kindly asked...
Click to expand...
Click to collapse
---------- Post added at 12:30 AM ---------- Previous post was at 12:20 AM ----------
im in tears (

I believe there's a link in the thread about ota updates after rooting.
http://forum.xda-developers.com/idol-3/general/want-to-able-to-install-ota-updates-t3163745

Yeah that what i was following and made a backup.. and now my crap is all screwed
I updated another backup from someone but it doesn't notice it,, same model and everything... sighhh
---------- Post added at 02:43 AM ---------- Previous post was at 01:43 AM ----------
TrevBlu19 said:
Yeah that what i was following and made a backup.. and now my crap is all screwed
I updated another backup from someone but it doesn't notice it,, same model and everything... sighhh
Click to expand...
Click to collapse
Trying to make the other guys restore show up.... with my other phone and swapping.. trying to change timestamps...

TrevBlu19 said:
Yeah that what i was following and made a backup.. and now my crap is all screwed
I updated another backup from someone but it doesn't notice it,, same model and everything... sighhh
---------- Post added at 02:43 AM ---------- Previous post was at 01:43 AM ----------
Trying to make the other guys restore show up.... with my other phone and swapping.. trying to change timestamps...
Click to expand...
Click to collapse
Tell us which backup you used and exactly what the path is to where you put it on the phone. Is it in TWRP/BACKUPS? If so, give us the rest of the path. If TWRP's Restore menu is not showing the backup you put on the phone, it's probably (assuming it's there and in the right place) because the folder name that starts with "4" isn't the right one or because it's in the wrong place. If you haven't already done this, from TWRP, make a system image backup. You probably won't use it, but it'll create the directory in which you can put the backup from XDA. It'll have a name that your installation of TWRP can recognize. Then, you can put that unrecognized backup there and it should be seen.

I can't even get into TWRP mode now it reboots too fast now..
maigre said:
Tell us which backup you used and exactly what the path is to where you put it on the phone. Is it in TWRP/BACKUPS? If so, give us the rest of the path. If TWRP's Restore menu is not showing the backup you put on the phone, it's probably (assuming it's there and in the right place) because the folder name that starts with "4" isn't the right one or because it's in the wrong place. If you haven't already done this, from TWRP, make a system image backup. You probably won't use it, but it'll create the directory in which you can put the backup from XDA. It'll have a name that your installation of TWRP can recognize. Then, you can put that unrecognized backup there and it should be seen.
Click to expand...
Click to collapse

You mean it's looping every few seconds? What happens, exactly? Do you get the black logo screen briefly, then it all goes black and comes back again?
Maybe it's worth copying a command like
Code:
adb reboot-bootloader
or, maybe better,
Code:
fastboot reboot bootloader
so that you have it in your clipboard. Then, keep entering them into the command line. You're bound to time it right at some point, at least if it can possibly be done in the state your device is in. You might have to do:
Code:
fastboot -i 0x1bbb reboot-bootloader
If you can get into the bootloader, you should be able to get booted into TWRP from there. Keep in mind that when you do get booted into the bootloader, it won't look like anything distinct. It's just that same black logo screen you see every time you boot up (or loop, probably).

I soft-bricked my 6045i after editing the build.prop and didn't have a backup like a fool. I cannot get the phone to boot at all, stuck on the Alcatel Onetouch boot logo and can't go any further. I have tried to create an update.zip to be able to flash the build.prop thru stock recovery but so far no luck. Each time it would give me an error saying invalid footer, I tried editing the updater-script to match the device but still the error remains and I cannot sideload the update.zip.
Would it be possible for someone to upload a signed update.zip for the 6045i model with only the build.prop for use with adb sideload in stock recovery?

datkevjames said:
I soft-bricked my 6045i after editing the build.prop and didn't have a backup like a fool. I cannot get the phone to boot at all, stuck on the Alcatel Onetouch boot logo and can't go any further. I have tried to create an update.zip to be able to flash the build.prop thru stock recovery but so far no luck. Each time it would give me an error saying invalid footer, I tried editing the updater-script to match the device but still the error remains and I cannot sideload the update.zip.
Would it be possible for someone to upload a signed update.zip for the 6045i model with only the build.prop for use with adb sideload in stock recovery?
Click to expand...
Click to collapse
Flash a stock system rom image from here: http://forum.xda-developers.com/idol-3/general/want-to-able-to-install-ota-updates-t3163745/
Important points: A corrupted build.prop should still mean you have adb access to your phone even though it won't finish booting...you can do an "adb reboot bootloader" then fastboot boot twrp and flash one of the stock recoveries.
How do I know this so well? I soft bricked mine for a day by editing the build.prop before TWRP was available.
---------- Post added at 07:42 PM ---------- Previous post was at 07:41 PM ----------
maigre said:
You mean it's looping every few seconds? What happens, exactly? Do you get the black logo screen briefly, then it all goes black and comes back again?
Maybe it's worth copying a command like
Code:
adb reboot-bootloader
or, maybe better,
Code:
fastboot reboot bootloader
so that you have it in your clipboard. Then, keep entering them into the command line. You're bound to time it right at some point, at least if it can possibly be done in the state your device is in. You might have to do:
Code:
fastboot -i 0x1bbb reboot-bootloader
If you can get into the bootloader, you should be able to get booted into TWRP from there. Keep in mind that when you do get booted into the bootloader, it won't look like anything distinct. It's just that same black logo screen you see every time you boot up (or loop, probably).
Click to expand...
Click to collapse
If you can execute fastboot commands, your already in bootloader.

famewolf said:
Flash a stock system rom image from here: http://forum.xda-developers.com/idol-3/general/want-to-able-to-install-ota-updates-t3163745/
Important points: A corrupted build.prop should still mean you have adb access to your phone even though it won't finish booting...you can do an "adb reboot bootloader" then fastboot boot twrp and flash one of the stock recoveries.
How do I know this so well? I soft bricked mine for a day by editing the build.prop before TWRP was available.
---------- Post added at 07:42 PM ---------- Previous post was at 07:41 PM ----------
If you can execute fastboot commands, your already in bootloader.
Click to expand...
Click to collapse
Believe me I've already tried. For whatever reason I cannot boot to fastboot, no matter what I try. I go into stock recovery and choose update from adb, when this happens adb gets enabled supposedly. Well when I try doing 'adb reboot-bootloader' it gives me: error: closed, no matter what I do. I've even added the 0x1bbb and same thing. When I try doing fastboot commands it just gives me <waiting for device> and nothing happens.
I either need to flash an update.zip with build.prop or somehow flash an entire image uploaded to the other thread which I'm well aware of.
PS: I've tried all different sorts of adb/fastboot executables as well as multiple adb drivers (Samsung, Motorola, Google etc) even the Alcatel ones provided with their Mobile Upgrade Q app which install more of the phone than any other drivers, I've noticed.
PPS: A handful of times I was able to get a tiny bit further in stock recovery adb sideload mode, of course it was an error: 'you must use adb 1.0.32 to be able to sideload' blah blah and I made sure I was using that version.
PPPS: Is there a 3rd party app I can use to flash the image like odin or rsd lite? I cannot for the life of me get to fastboot to flash the image. Adb devices detects the phone but beyond this I can't do squat.
PPPPS: Phone is rooted and bootloader unlocked. USB debugging enabled iirc although this may be the reason for all the 'error: closed' issues.
Please someone upload a signed flashable zip with build.prop in it for 6045i (USA) model. I love this phone more than my Moto X 2014 (XT1097), that's saying something considering the Moto has more power and smoothness to it.

twrp bootloop
im able to boot into bootloader and also able to get into twrp, but cant fully reboot. i have 6045i and if anybody has any solution to this, i would greatly appreciate it.

datkevjames said:
Believe me I've already tried. For whatever reason I cannot boot to fastboot, no matter what I try. I go into stock recovery and choose update from adb, when this happens adb gets enabled supposedly. Well when I try doing 'adb reboot-bootloader' it gives me: error: closed, no matter what I do. I've even added the 0x1bbb and same thing. When I try doing fastboot commands it just gives me <waiting for device> and nothing happens.
I either need to flash an update.zip with build.prop or somehow flash an entire image uploaded to the other thread which I'm well aware of.
PS: I've tried all different sorts of adb/fastboot executables as well as multiple adb drivers (Samsung, Motorola, Google etc) even the Alcatel ones provided with their Mobile Upgrade Q app which install more of the phone than any other drivers, I've noticed.
PPS: A handful of times I was able to get a tiny bit further in stock recovery adb sideload mode, of course it was an error: 'you must use adb 1.0.32 to be able to sideload' blah blah and I made sure I was using that version.
PPPS: Is there a 3rd party app I can use to flash the image like odin or rsd lite? I cannot for the life of me get to fastboot to flash the image. Adb devices detects the phone but beyond this I can't do squat.
PPPPS: Phone is rooted and bootloader unlocked. USB debugging enabled iirc although this may be the reason for all the 'error: closed' issues.
Please someone upload a signed flashable zip with build.prop in it for 6045i (USA) model. I love this phone more than my Moto X 2014 (XT1097), that's saying something considering the Moto has more power and smoothness to it.
Click to expand...
Click to collapse
There are no install-script and install-binary example files to use to build a signed update.zip because there are no rom's available....maybe someone could build something using the spanish rom just posted but I don't read spanish and they seem to have built it for a 6045Y which isn't gonna help 6045i or 6045K users. If you were running twrp it wouldn't be an issue as twrp allows adb access....stock recovery doesn't..it also doesn't support rebooting to bootloader....if your bootup was "freezing" as a normal build.prop issue would then you should STILL be able to do an "adb reboot bootloader" or an "adb shell" and look around.

datkevjames said:
Believe me I've already tried. For whatever reason I cannot boot to fastboot, no matter what I try. I go into stock recovery and choose update from adb, when this happens adb gets enabled supposedly. Well when I try doing 'adb reboot-bootloader' it gives me: error: closed, no matter what I do. I've even added the 0x1bbb and same thing. When I try doing fastboot commands it just gives me <waiting for device> and nothing happens.
.
Click to expand...
Click to collapse
Try this:
-turn off your phone
-run command line in direcotry where is fastboot and adb.exe
-connect phone to the pc and turn the phone on
-when the phone is booting you will hear a sound that new device is detected from your pc
-in this point type "adb reboo bootloader"
-the phone should reboot to initial screen and stays there
-now you are in bootloader mode and you can flash twrp recovery
-in twrp recovery you can run file manager and copy and delete files, so you can replace the bad build.prop with your backup (you surely have)
---------- Post added at 10:58 AM ---------- Previous post was at 10:50 AM ----------
faresbreech said:
im able to boot into bootloader and also able to get into twrp, but cant fully reboot. i have 6045i and if anybody has any solution to this, i would greatly appreciate it.
Click to expand...
Click to collapse
if you have a problem then:
1- you have to tell what did you do before it happen.
anyway if you can go to TWRP, you can download system Image backup from @famewolf thread HERE, copy it to your sd card and then proceed with restore menu from TWRP. And just check the "system" .

First I rooted phone, then verified through root checker that I was truly rooted. After that I proceeded to flash twrp. Once twrp was flashed, I went to recovery to make a full backup. There I first chose read only and then backed up, but realized that I was limited on performing different actions so I reflashed twrp and this time I chose for twrp to fully work and again preformed another backup. It was when I rebooted system after the second backup when I started looping back to twrp.
I was wondering if maybe there is a terminal command I can execute through twrp to fix this like the LG G2 has. I had a problem like this before on my G2 but after executing the terminal command it would get fixed. Thanks
Sent from my Z987 using XDA Free mobile app

DallasCZ said:
Try this:
-turn off your phone
-run command line in direcotry where is fastboot and adb.exe
-connect phone to the pc and turn the phone on
-when the phone is booting you will hear a sound that new device is detected from your pc
-in this point type "adb reboo bootloader"
-the phone should reboot to initial screen and stays there
-now you are in bootloader mode and you can flash twrp recovery
-in twrp recovery you can run file manager and copy and delete files, so you can replace the bad build.prop with your backup (you surely have)
Click to expand...
Click to collapse
I tried spamming 'adb reboot-bootloader' as fast as possible, but apparently I didn't authorize my computer. ADB gives me this: error: device unauthorized. Please check the confirmation dialog on your device. ffs. Now what? I do appreciate all help. I am savvy enough to try to solve this on my own but any helpful advice would be awesome.

[Resolved] One Plus 3 OxygenOs 3.2.2 Installation failed

Hi, I have been using One plus 3 for a week now. Today I received new update 3.2.2 After downloading it, started the update. However after some time, the installation window is saying "Installation failed" with only reboot option given. I am really confused right now. Note : This phone is Chinese variant and was given OxygenOS while purchasing. Any help regarding this would be much appreciated.

farhan37 said:
Hi, I have been using One plus 3 for a week now. Today I received new update 3.2.2 After downloading it, started the update. However after some time, the installation window is saying "Installation failed" with only reboot option given. I am really confused right now. Note : This phone is Chinese variant and was given OxygenOS while purchasing. Any help regarding this would be much appreciated.
Click to expand...
Click to collapse
Same issue. i thought it may be a security with my unlocked bootloader so i reflashed stock recovery and relocked the bootloader. Still failed.
Trying adb sideload now. Will let you know if it works
---------- Post added at 07:04 AM ---------- Previous post was at 07:01 AM ----------
mayerlench said:
Same issue. i thought it may be a security with my unlocked bootloader so i reflashed stock recovery and relocked the bootloader. Still failed.
Trying adb sideload now. Will let you know if it works
Click to expand...
Click to collapse
Success!! Adb sideload the full oxygenos 3.2.2 full rom(1.3gb) and youll be up and running.
Let me know if you need help.

mayerlench said:
Same issue. i thought it may be a security with my unlocked bootloader so i reflashed stock recovery and relocked the bootloader. Still failed.
Trying adb sideload now. Will let you know if it works
---------- Post added at 07:04 AM ---------- Previous post was at 07:01 AM ----------
Success!! Adb sideload the full oxygenos 3.2.2 full rom(1.3gb) and youll be up and running.
Let me know if you need help.
Click to expand...
Click to collapse
Thats great ! However, I am newbie to these things ! Could you please suggest a step by step guide for the procedure ? Thanks a lot in advance.

farhan37 said:
Thats great ! However, I am newbie to these things ! Could you please suggest a step by step guide for the procedure ? Thanks a lot in advance.
Click to expand...
Click to collapse
First you need adb on your computer.
1. Download the ADB For Windows from here :- https://drive.google.com/open?id=0B0...VB1elljU2NPR0k
2. Run the .exe file downloaded from above as Administrator.
3. Press 'Y' every time the installer asks.
4. Continue Driver Installation.
Now,ADB and Fastboot have been installed on your PC. Great
1. Now, go to settings>aboutphone>click buildnumber 10 times to activate developer options.
2. Settings>developer options>enable usb debugging
3. Dowbload the update to your pc fron here: https://mega.nz/#!o4EhnCDZ!lG3IrVdAc6ceIbSLQRRvOzZrzGhL-DObCg0oBtncgDc
4. Connect phone to pc. and boot phone into recovery by powering down phone and booting back up while holding volume down and power button. Using volume buttons navigate to recovery. Use power button as select.
Now go to advanced and click the adb option while in recovery mode.
5. Open command prompt on your pc. Type "adb sideload (Update file zip)".
Type without the quotes and the update zip file is the big file you downloaded, just drag and drop it onto the command prompt window without the parentheses obviously.
Hopefully this helps
let me know if you need more help

Easy Flash to Nougat Tutorial (Unlocked Retail Devices)

Easy Flash to Nougat Tutorial (Unlocked Retail Devices)
Prerequisites:
Download RSD lite XML to Batch Script from https://www.androidfilehost.com/?fid=24651430732235266
Download ROGERS_MPL24.246-45 from https://mega.nz/#!nssGEDiT!hhLkcTM106hmqbH_fiWfAytEV-fgdlYOhUwpcd_sGJY
Download Nougat firmware from https://mega.nz/#!608HGYqB!kKTc1196PhimDtVte6OdCWF6aXSWGSNLToEkvUePymE
Steps:
Unpack RSDLite XML to Batch Script to a folder on your computer
Unpack Rogers 24.246-45 firmware to the SAME folder
Run 2-rsd-flash-flashfile-windows.bat
Batch File #2 will convert the flashfile.xml file (included in Rogers zip) to a Batch file
Run flashfile.bat which will flash the Rogers firmware to your device (WILL WIPE EVERYTHING EXCEPT MICRO SD CARD)
Wait till its done!
Your device should now have Rogers 24.246-45 Firmware.
From the Bootloader, select Recovery Mode.
If you see No Command don't panic! That's normal. Press the power button for a couple seconds and press volume up or down (not sure if you need volume buttons but I always do anyway)
Once it displays on screen, Select ADB Sideload
From an adb capable command prompt, enter ADB Sideload <name and location of Nougat.zip> (minus the <> obviously)
This will take time. Leave it alone!
Once complete, simply reboot from recovery and let the device start like normal.
TROUBLESHOOTING:
If ADB Sideload gives you a Can't Read error, try these steps:
1. Download Large Address Awareness from here https://www.techpowerup.com/forums/threads/large-address-aware.112556/
2. Download ADB from here http://forum.xda-developers.com/showthread.php?t=2588979
3. Start Task Manager and kill adb.exe if its running
4. Load the adb.exe file from Large Address Awareness and check the flag button
5. Continue on with adb sideload
I've tested this process multiple times today and it should work well. Let me know if you have any trouble!
I want to mention I have had NO success backing up with TWRP and restoring after this. Something changed with Nougat and any modification to System causes a soft brick (it did for me anyway). Do not attempt to flash system mode TWRP or flash the TurboZ kernel. They don't work and they will cause a boot loop.
UPDATE:
This method might not be for everyone, and if you're not interested in sticking with stock 7.0 and potentially want to roll around to other ROMs you should follow this guide instead; http://forum.xda-developers.com/moto-z/development/android-nougat-moto-z-versions-t3506342

Great thank you! Question:
Will all the radio bands (T-MOBILE) still work as normal?
Have you try this out with Google Day Dream VR yet?
I had the note 7 and the Galaxy VR., Kinda of miss that.

dallas90733 said:
Great thank you! Question:
Will all the radio bands (T-MOBILE) still work as normal?
Have you try this out with Google Day Dream VR yet?
I had the note 7 and the Galaxy VR., Kinda of miss that.
Click to expand...
Click to collapse
Daydream works from what I can tell. Also I'm on att so I haven't checked T-Mobile bands but im assuming they work fine. I know there's an app to check which bands your device supports. I'll try downloading it and let you know

So I get to the point to sideload the nougat update and it always says "can't read..." I've done factory resets and everything else I could think of, still no go for me.

Prfndhatrdofman said:
...
I want to mention I have had NO success backing up with TWRP and restoring after this. Something changed with Nougat and any modification to System causes a soft brick (it did for me anyway). Do not attempt to flash system mode TWRP or flash the TurboZ kernel. They don't work and they will cause a boot loop.
Click to expand...
Click to collapse
So... are you of the opinion that recovering a Nougat boot+system TWRP backup on a MM phone would cause a soft brick too?
What type of soft brick do you faced exactly?

Prfndhatrdofman said:
Easy Flash to Nougat Tutorial (Unlocked Retail Devices)
Prerequisites:
Download RSD lite XML to Batch Script from https://www.androidfilehost.com/?fid=24651430732235266
Download ROGERS_MPL24.246-45 from https://mega.nz/#!nssGEDiT!hhLkcTM106hmqbH_fiWfAytEV-fgdlYOhUwpcd_sGJY
Download Nougat firmware from https://mega.nz/#!608HGYqB!kKTc1196PhimDtVte6OdCWF6aXSWGSNLToEkvUePymE
Steps:
Unpack RSDLite XML to Batch Script to a folder on your computer
Unpack Rogers 24.246-45 firmware to the SAME folder
Run 2-rsd-flash-flashfile-windows.bat
Batch File #2 will convert the flashfile.xml file (included in Rogers zip) to a Batch file
Run flashfile.bat which will flash the Rogers firmware to your device (WILL WIPE EVERYTHING EXCEPT MICRO SD CARD)
Wait till its done!
Your device should now have Rogers 24.246-45 Firmware.
From the Bootloader, select Recovery Mode.
If you see No Command don't panic! That's normal. Press the power button for a couple seconds and press volume up or down (not sure if you need volume buttons but I always do anyway)
Once it displays on screen, Select ADB Sideload
From an adb capable command prompt, enter ADB Sideload <name and location of Nougat.zip> (minus the <> obviously)
This will take time. Leave it alone!
Once complete, simply reboot from recovery and let the device start like normal.
I've tested this process multiple times today and it should work well. Let me know if you have any trouble!
I want to mention I have had NO success backing up with TWRP and restoring after this. Something changed with Nougat and any modification to System causes a soft brick (it did for me anyway). Do not attempt to flash system mode TWRP or flash the TurboZ kernel. They don't work and they will cause a boot loop.
Click to expand...
Click to collapse
I did up until this
From the Bootloader, select Recovery Mode.
If you see No Command don't panic! That's normal. Press the power button for a couple seconds and press volume up or down (not sure if you need volume buttons but I always do anyway)
Once it displays on screen, Select ADB Sideload
From an adb capable command prompt, enter ADB Sideload <name and location of Nougat.zip> (minus the <> obviously)
But when I boot up i have no wifi and I am unable to get the no command to go away to select sideload any ideas?

pieman13 said:
So I get to the point to sideload the nougat update and it always says "can't read..." I've done factory resets and everything else I could think of, still no go for me.
Click to expand...
Click to collapse
Same here, did you find a fix? Tried re-downloading Blur_Version.24.21.46.griffin.retail.en.US.zip and got the same error...

pixelens said:
Same here, did you find a fix? Tried re-downloading Blur_Version.24.21.46.griffin.retail.en.US.zip and got the same error...
Click to expand...
Click to collapse
This happened to me as well. I think it came down to being an ADB Driver issue for me. I reinstalled a different set of ADB drivers and it had no issue after that.

enetec said:
So... are you of the opinion that recovering a Nougat boot+system TWRP backup on a MM phone would cause a soft brick too?
What type of soft brick do you faced exactly?
Click to expand...
Click to collapse
Didn't work for me. As soon as the system partition was mounted R/W My device would boot loop. Could be a symptom of something else but im not sure.

Prfndhatrdofman said:
This happened to me as well. I think it came down to being an ADB Driver issue for me. I reinstalled a different set of ADB drivers and it had no issue after that.
Click to expand...
Click to collapse
Interesting... I'm using the adb drivers from Android Studio.
---------- Post added at 02:27 PM ---------- Previous post was at 02:16 PM ----------
Tried using the ADB drivers from Minimal ADB and Fastboot, same result. Oh well.

pixelens said:
Interesting... I'm using the adb drivers from Android Studio.
---------- Post added at 02:27 PM ---------- Previous post was at 02:16 PM ----------
Tried using the ADB drivers from Minimal ADB and Fastboot, same result. Oh well.
Click to expand...
Click to collapse
Yeah i struggled for about 3 hours trying to get sideload to work. I dunno why but after i completely deleted the driver, rebooted, reinstalled from ADB it finally worked. Its definitely not your device or the image its just ADB being a pain in the ass. I even tried multiple versions of ADB. One guy just tried on a different computer and it worked. I dunno why

Prfndhatrdofman said:
Yeah i struggled for about 3 hours trying to get sideload to work. I dunno why but after i completely deleted the driver, rebooted, reinstalled from ADB it finally worked. Its definitely not your device or the image its just ADB being a pain in the ass. I even tried multiple versions of ADB. One guy just tried on a different computer and it worked. I dunno why
Click to expand...
Click to collapse
Yah, I've had similar experiences in the past - been ages since I've done this though (Samsung Galaxy SII Skyrocket days) so just wanted to make sure I wasn't missing something.
Quick question though, title says "unlocked retail devices" - does that mean the bootloader has to be unlocked? Or will this work with a locked bootloader? Cheers.

pixelens said:
Yah, I've had similar experiences in the past - been ages since I've done this though (Samsung Galaxy SII Skyrocket days) so just wanted to make sure I wasn't missing something.
Quick question though, title says "unlocked retail devices" - does that mean the bootloader has to be unlocked? Or will this work with a locked bootloader? Cheers.
Click to expand...
Click to collapse
I specifically meant network unlocked. Really just any device purchased directly from Motorola.
But yeah i think you might need to have an unlocked bootloader as well.

pixelens said:
Same here, did you find a fix? Tried re-downloading Blur_Version.24.21.46.griffin.retail.en.US.zip and got the same error...
Click to expand...
Click to collapse
Fix was I went back to my pixel and sold the Z.

Mine has unlocked bootloader. Unlocked thru Motorola's website since the first hour I got it

Got the Nougat update to sideload (yay!) - tried a different computer that had no adb drivers installed, used the ones from Minimal ADB and Fastboot and they worked no problem.
Is it possible to lock the bootloader after the Nougat update? I tried and received "(bootloader) still require signed boot.img" message.

pixelens said:
Got the Nougat update to sideload (yay!) - tried a different computer that had no adb drivers installed, used the ones from Minimal ADB and Fastboot and they worked no problem.
Is it possible to lock the bootloader after the Nougat update? I tried and received "(bootloader) still require signed boot.img" message.
Click to expand...
Click to collapse
Dunno. I get the same error.

Thank you for this guide!

Prfndhatrdofman said:
Easy Flash to Nougat Tutorial (Unlocked Retail Devices)
Prerequisites:
Download RSD lite XML to Batch Script from https://www.androidfilehost.com/?fid=24651430732235266
Download ROGERS_MPL24.246-45 from https://mega.nz/#!nssGEDiT!hhLkcTM106hmqbH_fiWfAytEV-fgdlYOhUwpcd_sGJY
Download Nougat firmware from https://mega.nz/#!608HGYqB!kKTc1196PhimDtVte6OdCWF6aXSWGSNLToEkvUePymE
Steps:
Unpack RSDLite XML to Batch Script to a folder on your computer
Unpack Rogers 24.246-45 firmware to the SAME folder
Run 2-rsd-flash-flashfile-windows.bat
Batch File #2 will convert the flashfile.xml file (included in Rogers zip) to a Batch file
Run flashfile.bat which will flash the Rogers firmware to your device (WILL WIPE EVERYTHING EXCEPT MICRO SD CARD)
Wait till its done!
Your device should now have Rogers 24.246-45 Firmware.
From the Bootloader, select Recovery Mode.
If you see No Command don't panic! That's normal. Press the power button for a couple seconds and press volume up or down (not sure if you need volume buttons but I always do anyway)
Once it displays on screen, Select ADB Sideload
From an adb capable command prompt, enter ADB Sideload <name and location of Nougat.zip> (minus the <> obviously)
This will take time. Leave it alone!
Once complete, simply reboot from recovery and let the device start like normal.
I've tested this process multiple times today and it should work well. Let me know if you have any trouble!
I want to mention I have had NO success backing up with TWRP and restoring after this. Something changed with Nougat and any modification to System causes a soft brick (it did for me anyway). Do not attempt to flash system mode TWRP or flash the TurboZ kernel. They don't work and they will cause a boot loop.
Click to expand...
Click to collapse
Hello
I flashed the rogers 45 firmware, but when I go to recovery mode I can't get the ADB menu to appear. I've held power and down, power and up, nothing, etc. Am I missing something? I did the rogers install, then went to homescreen, then powered off.
EDIT
after restarting my phone like 10 times in 5 minutes (rest in peace...) I finally figured it out. Now my issue is that I can't seem to get the sideload to work. I am going to try uninstalling android studio and start again. Did you guys figure out why it says * cannot read ' blur.....' * ?

I found how to fix the adb problem about being unable to read from another thread on XDA
1. Download Large Address Awareness from here https://www.techpowerup.com/forums/threads/large-address-aware.112556/
2. Download ADB from here http://forum.xda-developers.com/showthread.php?t=2588979
3. Start Task Manager and kill adb.exe if its running
4. Load the adb.exe file from Large Address Awareess and check the flag button
5. Continue on with adb sideload
---------- Post added at 09:42 AM ---------- Previous post was at 09:40 AM ----------
Porcelainfog said:
Hello
I flashed the rogers 45 firmware, but when I go to recovery mode I can't get the ADB menu to appear. I've held power and down, power and up, nothing, etc. Am I missing something? I did the rogers install, then went to homescreen, then powered off.
Click to expand...
Click to collapse
Do you see the "No command" picture after choosing Recover Mode? Once you get to that, I hold down power and tap volume up and down again and again