Database Users

[Solved] OnePlus Two stuck on boot after install OxygenOS 3.0

If you have installed OxygenOS 3.0 and when you try to boot recovery mode, or other case, your phone stuck on boot, here's the solution. It's easy, you only have to enter this link: http://forum.xda-developers.com/devdb/project/dl/?id=16684 and download the content. After unzip, connect your phone in fastboot mode (on/off button + volume up button) and execute the script that is in the folder unziped (firstaid.bat in windows or fistaid.sh in linux). Now it's possible that system don't boot, but now you have TWRP recovery and you can install the ROM that you want. If you don't want that your phone becomes to stuck on boot, please, read the instructions in this link: https://forums.oneplus.net/threads/installation-instructions-faqs-oxygenos-3-0-0.439108 before install again OxygenOS 3.0.
Summary:
Before all this you have to install the adb/fastboot and your phone drivers.
1- Download the firstaid tool from http://forum.xda-developers.com/devdb/project/dl/?id=16684
2- Put the phone in fastboot mode (on/off button + volume up button) and connect to pc
3- Execute the script (firstaid.bat in windows or fistaid.sh in linux)
Now you have recovery again.
4- If you want to install OxygenOS 3.0, follow the instructions of https://forums.oneplus.net/threads/installation-instructions-faqs-oxygenos-3-0-0.439108

I've been a lot of hours searching a solution for the problem and it's very annoying. It's a pleasure to help you for don't lose your time like me.

luisito68 said:
If you have installed OxygenOS 3.0 and when you try to boot recovery mode, or other case, your phone stuck on boot, here's the solution. It's easy, you only have to enter this link: http://forum.xda-developers.com/devdb/project/dl/?id=16684 and download the content. After unzip, connect your phone in fastboot mode (on/off button + volume up button) and execute the script that is in the folder unziped (firstaid.bat in windows or fistaid.sh in linux). Now it's possible that system don't boot, but now you have TWRP recovery and you can install the ROM that you want. If you don't want that your phone becomes to stuck on boot, please, read the instructions in this link: https://forums.oneplus.net/threads/installation-instructions-faqs-oxygenos-3-0-0.439108 before install again OxygenOS 3.0.
Summary:
Before all this you have to install the adb/fastboot and your phone drivers.
1- Download the firstaid tool from http://forum.xda-developers.com/devdb/project/dl/?id=16684
2- Put the phone in fastboot mode (on/off button + volume up button) and connect to pc
3- Execute the script (firstaid.bat in windows or fistaid.sh in linux)
Now you have recovery again.
4- If you want to install OxygenOS 3.0, follow the instructions of https://forums.oneplus.net/threads/installation-instructions-faqs-oxygenos-3-0-0.439108
Click to expand...
Click to collapse
thank you for the post but unfortunately it didn't work in my opt

ronyjarod said:
thank you for the post but unfortunately it didn't work in my opt
Click to expand...
Click to collapse
Sorry, if you have the problem yet you can try to connect your phone in fastboot mode (having all drivers ok) and write "fastboot devices", if your device appears download the twrp modified of the link of the instructions to install OOS 3 (https://forums.oneplus.net/threads/installation-instructions-faqs-oxygenos-3-0-0.439108), open cmd in the download folder (shift + right mouse -> open cmd here) and write "fastboot flash recoery recovery.img". This did not work for me, but I tried it with an toher recovery. I wish you solve the problem soon!

luisito68 said:
Sorry, if you have the problem yet you can try to connect your phone in fastboot mode (having all drivers ok) and write "fastboot devices", if your device appears download the twrp modified of the link of the instructions to install OOS 3 (https://forums.oneplus.net/threads/installation-instructions-faqs-oxygenos-3-0-0.439108), open cmd in the download folder (shift + right mouse -> open cmd here) and write "fastboot flash recoery recovery.img". This did not work for me, but I tried it with an toher recovery. I wish you solve the problem soon!
Click to expand...
Click to collapse
solved accidentally. what i did was typed fastboot boot OP2_recovery .img (not in the fastboot mode but at the stuck boot logo mode). i don't know how the img went in but that was the way saved my opt from bricked. anyhow, thank you for the reply

i just wanna downgrade pissed off of oos3.0
i wanna flash cm13 or oos 2.2.1 plz help

ronyjarod said:
solved accidentally. what i did was typed fastboot boot OP2_recovery .img (not in the fastboot mode but at the stuck boot logo mode). i don't know how the img went in but that was the way saved my opt from bricked. anyhow, thank you for the reply
Click to expand...
Click to collapse
Oh cool ! It is rare to have recovered at this way , but I'm glad to know it!

Veer1080 said:
i just wanna downgrade pissed off of oos3.0
i wanna flash cm13 or oos 2.2.1 plz help
Click to expand...
Click to collapse
If you follow the three first steps you will have recovery and you will can flash any rom. If this way not work (it worked for me) you can try the way of ronyjarod.

luisito68 said:
If you follow the three first steps you will have recovery and you will can flash any rom. If this way not work (it worked for me) you can try the way of ronyjarod.
Click to expand...
Click to collapse
lol. my way is inappropriate. i was just lucky
---------- Post added at 05:59 AM ---------- Previous post was at 05:53 AM ----------
Veer1080 said:
i just wanna downgrade pissed off of oos3.0
i wanna flash cm13 or oos 2.2.1 plz help
Click to expand...
Click to collapse
my oos 3 seems to be much better than v2.2.1

ronyjarod said:
lol. my way is inappropriate. i was just lucky
---------- Post added at 05:59 AM ---------- Previous post was at 05:53 AM ----------
my oos 3 seems to be much better than v2.2.1
Click to expand...
Click to collapse
3 is laggy after 4 days

Veer1080 said:
3 is laggy after 4 days
Click to expand...
Click to collapse
mine didn't lag after many days

May Factory Image now available MXC89F

For those in custom recovery land just flash the system and vendor img to upgrade
now in May flavor!
https://developers.google.com/android/nexus/images#instructions

Well it should be great IF our TWRP could mount vendor / system correctly
Only boot / recovery partitions are selectable for .img files :/
Edit: I´ve flashed the files via ADB - all went fine

redukt said:
Well it should be great IF our TWRP could mount vendor / system correctly
Only boot / recovery partitions are selectable for .img files :/
Edit: I´ve flashed the files via ADB - all went fine
Click to expand...
Click to collapse
The value of this posting would increase exponentially if you took it upon yourself to share what and how you flashed the files with ADB.

Sorry for my ignorance
Extract the ryu-m5c14j-factory-b714e9bd.tgz with i.e. 7-zip. In image-ryu-m5c14j.zip you find both files system.img and vendor.img.
So... I´ll hope you have some practices using ADB / fastboot. Put both files in your ADB / fastboot folder. Activate USB debugging on your device and restart it in fastboot mode. Connect your device with your USB-C cable.
Go into your ADB / fastboot folder and press shift / rightclick your mouse at twice and open the command prompt.
Bye typing "fastboot devices" or "adb devices" you can check if your device is correctly connect with your PC.
If you´re connected type "fastboot flash system system.img" and wait for end of process. After that type "fastboot flash vendor vendor.img". Now you can reboot your device by typing "fastboot reboot"
Those are my oldschool steps without losing data or settings.

redukt said:
Sorry for my ignorance
Extract the ryu-m5c14j-factory-b714e9bd.tgz with i.e. 7-zip. In image-ryu-m5c14j.zip you find both files system.img and vendor.img.
So... I´ll hope you have some practices using ADB / fastboot. Put both files in your ADB / fastboot folder. Activate USB debugging on your device and restart it in fastboot mode. Connect your device with your USB-C cable.
Go into your ADB / fastboot folder and press shift / rightclick your mouse at twice and open the command prompt.
Bye typing "fastboot devices" or "adb devices" you can check if your device is correctly connect with your PC.
If you´re connected type "fastboot flash system system.img" and wait for end of process. After that type "fastboot flash vendor vendor.img". Now you can reboot your device by typing "fastboot reboot"
Those are my oldschool steps without losing data or settings.
Click to expand...
Click to collapse
No chance of losing root either, is that correct?

Well I assume that you have TWRP? Reboot into recovery and flash supersu again. That´s all If not you can sideload it via ADB.
In my case I have reflash supersu & xposed framework in TWRP

redukt said:
Well I assume that you have TWRP? Reboot into recovery and flash supersu again. That´s all If not you can sideload it via ADB.
In my case I have reflash supersu & xposed framework in TWRP
Click to expand...
Click to collapse
Yes, I will need to reflash both, too (I have TWRP).
Thanks!

Than you´re device is rooted again. With this method you lose no data or wipe anything (ok.... some cache *g)
And... we have a thanks button in XDA So you don´t have to thank mate

Change log ? Or its just a security update

Hello there,
so I am in a little conundrum here.
I flashed the system.img and vendor.img following the instructions, but the pixel was just stuck at the plain Google logo.
After giving it something like 30 minutes, I had to power it off.
I am using TWRP and dragon-boot-encryptable-rooted-MXB48T-02102016-1.img stock kernel.
Another boot went without success.
my next thought was to downgrade to MXC14G but trying to do so resulted in:
Code:
c:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash system system.img
target reported max download size of 268435456 bytes
erasing 'system'...
FAILED (remote: unsupported command)
finished. total time: 0.004s
So far TWRP is working and I can operate within it.
Any ideas what went wrong? Should I format system and vendor in TWRP? I don't think this is a good idea... (Last time I tried to do so in this experimental version of TWRP I had to fight a long fight to revive it, because the formatting tool in TWRP was stuck. But that's another story.) Any way to flash the system.img and vendor.img from within TWRP?
Any help would be much appreciated, m8s.

After playing around in TWRP and using the fix fastboot option I am finally able to flash system and vendor in fastboot.
I don't know if the fix fastboot was really the solution, maybe just some sort of placebo, but nevertheless I am able to flash. Problem with the bootloop remains:
Google logo, reboot recovery.
My data partition is alright. What do I need to flash to get it going?
Going in circles here...

rambobo said:
After playing around in TWRP and using the fix fastboot option I am finally able to flash system and vendor in fastboot.
I don't know if the fix fastboot was really the solution, maybe just some sort of placebo, but nevertheless I am able to flash. Problem with the bootloop remains:
Google logo, reboot recovery.
My data partition is alright. What do I need to flash to get it going?
Going in circles here...
Click to expand...
Click to collapse
Just asking, did you verify your download to make sure not corrupted?
Sent from my Pixel C using Tapatalk

houtx2 said:
Just asking, did you verify your download to make sure not corrupted?
Sent from my Pixel C using Tapatalk
Click to expand...
Click to collapse
Yes, it is verified. I am using all kinds of ways to restore the pixel.
I am positive: fastboot won't write or format partitions unless it is fixed by twrp.
I am trying out to flash the newest factory image with the skipsoft android toolkit. I could have done it manually, but spent already too much of my free Saturday on flashing. I'll report back if and what works out.
---------- Post added at 04:19 PM ---------- Previous post was at 04:16 PM ----------
:/ After 'successful' flashing of the stock firmware, now there is the laying android with the red exclamation sign... help...
---------- Post added at 04:54 PM ---------- Previous post was at 04:19 PM ----------
I redownloaded the official factory image grom google servers.
Then I followed the instruction, means i started the flash-all.bat.
The Tablet boot into the android on the back with the red exclamation mark symbol.
The flashing process went without warnings.
Is it bricked now? Do I have to relock the bootloader to boot it?

rambobo said:
Yes, it is verified. I am using all kinds of ways to restore the pixel.
I am positive: fastboot won't write or format partitions unless it is fixed by twrp.
I am trying out to flash the newest factory image with the skipsoft android toolkit. I could have done it manually, but spent already too much of my free Saturday on flashing. I'll report back if and what works out.
---------- Post added at 04:19 PM ---------- Previous post was at 04:16 PM ----------
:/ After 'successful' flashing of the stock firmware, now there is the laying android with the red exclamation sign... help...
---------- Post added at 04:54 PM ---------- Previous post was at 04:19 PM ----------
I redownloaded the official factory image grom google servers.
Then I followed the instruction, means i started the flash-all.bat.
The Tablet boot into the android on the back with the red exclamation mark symbol.
The flashing process went without warnings.
Is it bricked now? Do I have to relock the bootloader to boot it?
Click to expand...
Click to collapse
Pleas try to reinstall right drivers, change the cable / USB ports. I think your main problem is your system configuration. Good luck

m8... so glad I wasn't too tired to listen to your tip. Awesome! Redid all the steps on my freshly installed laptop, and voila!
Seems either my main PCs USB-connection is flunky or I am damned to reinstall my Windows soon. Scary...
I used the following software to revive the Pixel:
official Google USB Drivers
You have to unzip the file and right-click and install it
then you have to go to your device manager in windows and after connecting the tablet with the PC and getting into fastboot
Find the Android device on the top, select to change driver and go straight to manual selection of the driver, select android and bootloader driver
unpack the official Factory Image with 7Zip until you get to the folder with the flash-all.bat
get the minimal adb fastboot and unpack it in the same folder as the flash-all file
wait until you see the sweet booting animation
I think I didn't forget anything important. My Pixel is alive and ready for prime time.
Big thanks redukt, may the warp speed not pass you!

rambobo said:
Big thanks redukt, may the warp speed not pass you!
Click to expand...
Click to collapse
Enjoy your device
Next time simply hit the thanks button

redukt said:
Sorry for my ignorance
Extract the ryu-m5c14j-factory-b714e9bd.tgz with i.e. 7-zip. In image-ryu-m5c14j.zip you find both files system.img and vendor.img.
So... I´ll hope you have some practices using ADB / fastboot. Put both files in your ADB / fastboot folder. Activate USB debugging on your device and restart it in fastboot mode. Connect your device with your USB-C cable.
Go into your ADB / fastboot folder and press shift / rightclick your mouse at twice and open the command prompt.
Bye typing "fastboot devices" or "adb devices" you can check if your device is correctly connect with your PC.
If you´re connected type "fastboot flash system system.img" and wait for end of process. After that type "fastboot flash vendor vendor.img". Now you can reboot your device by typing "fastboot reboot"
Those are my oldschool steps without losing data or settings.
Click to expand...
Click to collapse
rambobo said:
Hello there,
so I am in a little conundrum here.
I flashed the system.img and vendor.img following the instructions, but the pixel was just stuck at the plain Google logo.
After giving it something like 30 minutes, I had to power it off.
I am using TWRP and dragon-boot-encryptable-rooted-MXB48T-02102016-1.img stock kernel.
Another boot went without success.
my next thought was to downgrade to MXC14G but trying to do so resulted in:
Code:
c:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash system system.img
target reported max download size of 268435456 bytes
erasing 'system'...
FAILED (remote: unsupported command)
finished. total time: 0.004s
So far TWRP is working and I can operate within it.
Any ideas what went wrong? Should I format system and vendor in TWRP? I don't think this is a good idea... (Last time I tried to do so in this experimental version of TWRP I had to fight a long fight to revive it, because the formatting tool in TWRP was stuck. But that's another story.) Any way to flash the system.img and vendor.img from within TWRP?
Any help would be much appreciated, m8s.
Click to expand...
Click to collapse
Following redukt's instructions, I got the same error that rambobo saw. I rebooted into TWRP and executed the "Fix fastboot" option, then rebooted back to the bootloader. System & Vendor image flashing via ADB worked fine
I am now running M5C14J without loss of data, root, or recovery.
The OTA update reminder disappeared on it's own after 5-10 minutes.
Thanks yall!

hugehead83 said:
Following redukt's instructions, I got the same error that rambobo saw. I rebooted into TWRP and executed the "Fix fastboot" option, then rebooted back to the bootloader. System & Vendor image flashing via ADB worked fine
I am now running M5C14J without loss of data, root, or recovery.
The OTA update reminder disappeared on it's own after 5-10 minutes.
Thanks yall!
Click to expand...
Click to collapse
You didn't have to apply root again via ADB or TWRP?

dmnhnterz said:
You didn't have to apply root again via ADB or TWRP?
Click to expand...
Click to collapse
Mates, the may-factory-image is available. Same procedure as ever
https://developers.google.com/android/nexus/images#instructions
Happy flashing

dmnhnterz said:
You didn't have to apply root again via ADB or TWRP?
Click to expand...
Click to collapse
Correct
But judging from others' experiences here, YMMV. I tried the latest FlashFire build too, but that got me nowhere.

----- Root Moto M S356 Android 7 -------

Hi guys,
I have started this thread so that you guys can root your moto M XT_1663_S356 andriod (7.0)
First of all i'm not responsible if your phone bricks burns or dies.
A big thanks to VVizard from lenovo RU forum with out him, it was not possible.
Thanks to Chainfire for the SuperSu.zip
To check Build number go to Settings -> About Phone-> Build number
Note -
1 - This only works for Moto M which is having build number XT1663_S356_170621_ROW. If you are on any other build number then please don't proceed.
2 - All the files are attached
3 - Install all the Motoral drivers and Minimal and adb folder.
4 - Following link contains all files needed to root the phone.
https://drive.google.com/file/d/0B3eDb0dWRU-uUjk4ZS1tdFpRR1U/view?usp=sharing
Rooting Moto M phone is divided into 3 Parts
1) Unlocking BootLoader
2) Flashing TWRP
3) Flashing SuperSu.zip
unlocking the bootloader
Note - This will wipe out all the data hence take a backup before unlocking boot loader
1 - First of all enable the Developer Option, To Enable the Developer Option, Go to your Settings -> About Phone-> Now Tap on the Build Number 7-8 Times until you see a toast message “Developer option enabled"
2 - Go back to settings -> Now you need to enable the OEM Unlock by going to Settings -> Developer Option and Enable OEM Unlock and USB Debugging
3 - Download and Extract the Downloaded ADB fastboot Zip file on your PC
4 - Now connect your phone to Computer using USB Cable.
5 - When you connect your Phone to Computer, please wait until all the drivers get installed.
6 - In your ADB fastboot folder open a command prompt window by pressing Shift Key + Right Mouse Click
7 - Now type the command in your command window
adb devices
If you see a pop up to allow USB Debugging on your phone, Click OK
8 - Now type the command below to reboot your phone to bootloader
adb reboot bootloader
9 - Once your phone reboot into bootloader, then type the command below to make sure fastboot drivers are installed properly.
fastboot devices
10 - This command will list the connected devices. If your phone’s serial number shows up you are good to go and may continue. If the phone is NOT listed this indicates that your drivers are not installed correctly.
11 - If your phone is listed then type in the following command in CMD.
fastboot oem unlock
12 - Check your phone you would have written"do you really want to unloock bootloader ? "(something like this). Just select yes using volume up and down button and press power button to confirm it .
13 - Congrats your bootloader is unlocked
Install TWRP
Note - You should have your bootloader unlocked before proceeding.
Copy the boot_XT1663_356.img and TWRP_Moto_M.img to Minimal adb folder
1 - First of all enable the Developer Option, To Enable the Developer Option, Go to your Settings -> About Phone-> Now Tap on the Build Number 7-8 Times until you see a toast message “Developer option enabled"
2 - Go back to settings -> Now you need to enable the OEM Unlock by going to Settings -> Developer Option and Enable OEM Unlock and USB Debugging
3 - Download and Extract the Downloaded ADB fastboot Zip file on your PC
4 - Now connect your phone to Computer using USB Cable.
5 - When you connect your Phone to Computer, please wait until all the drivers get installed.
6 - In your ADB fastboot folder open a command prompt window by pressing Shift Key + Right Mouse Click
7 - Now type the command in your command window
adb devices
If you see a pop up to allow USB Debugging on your phone, Click OK
8 - Now type the command below to reboot your phone to bootloader
adb reboot bootloader
9 - Once your phone reboot into bootloader, then type the command below to make sure fastboot drivers are installed properly.
fastboot devices
10 - This command will list the connected devices. If your phone’s serial number shows up you are good to go and may continue. If the phone is NOT listed this indicates that your drivers are not installed correctly.
11 - If your phone is listed then type in the following command in CMD.
fastboot flash boot boot_XT1663_356.img
12 - To flash the recovery, Type the command
fastboot flash recovery TWRP_Moto_M.img
13 - Congrats! you have successfully installed TWRP.
Rooting Phone.
Note -
You should have your bootloader unlocked.
You should have TWRP installed.
You should have supersu.zip copied in your phone.
1 - Switch off your phone. Now press volume down + power button till phone vibrates. Once it vibrates release the power button you should see android logo.
2 - Now with the help of volume up and down button select 'Recovery mode' and press power button.
3 - TWRP should start up.
4 - Select 'Allow Modification' and proceed.
5 - Select 'Install' and then select the 'SuperSu.zip' file and flash it.
6 -Restart the Phone.
7 - Congrats! your phone is rooted.
Note -
I have tried all this steps and have successfully rooted my phone i'm not responsible for any damage.
I have not build the boot_M_S365/ img file this is done by VVizard and really very thank full to him.

I am making a video on this!

Method Issues
Bro, I have faced a few problems since I have started
i) When I type in adb devices it shows my phone but unauthorized
so I have to allow it as you said but only after a reboot and doing the process again will it show authorized
ii) after entering adb reboot bootloader it doesnt show bootloader locked but straight up fastboot mode
iii) then when i enter fastboot oem unlock it shows asks me if I want to unlock, I press on volume up. Then it again asks me some other thing and I hold the volume up down and power together. Next I reboot into my phone. All data erased. I setup it again.
Now, does this mean my bootloader is unlocked? When I reboot it shows something on the middle right- unlocked..
So does this mean I continue and install twrp now? or what?

manandua01 said:
Thanks bro, I will give you credits ^_^
Click to expand...
Click to collapse
Cool!

manandua01 said:
Bro, I have faced a few problems since I have started
i) When I type in adb devices it shows my phone but unauthorized
so I have to allow it as you said but only after a reboot and doing the process again will it show authorized
ii) after entering adb reboot bootloader it doesnt show bootloader locked but straight up fastboot mode
iii) then when i enter fastboot oem unlock it shows asks me if I want to unlock, I press on volume up. Then it again asks me some other thing and I hold the volume up down and power together. Next I reboot into my phone. All data erased. I setup it again.
Now, does this mean my bootloader is unlocked? When I reboot it shows something on the middle right- unlocked..
So does this mean I continue and install twrp now? or what?
Click to expand...
Click to collapse
1 - It doen't matter if its authorized or not..
2 - yes! thats correct it directly takes you to fastboot mode it use to show bootloader locked for old Moto phones).I 'll make changes in the thread.
Yes! your bootloader is unlocked successfully..
if you see something like 'Your devices is unlocked and cant be trusted' on the left hand side during the moto logo.

TWRP Recovery
akash.mahadeshwar said:
1 - It doen't matter if its authorized or not..
2 - yes! thats correct it directly takes you to fastboot mode it use to show bootloader locked for old Moto phones).I 'll make changes in the thread.
Yes! your bootloader is unlocked successfully..
if you see something like 'Your devices is unlocked and cant be trusted' on the left hand side during the moto logo.
Click to expand...
Click to collapse
Thanks for your help Y_Y
Hey bro, I am not about to install the recovery.
Before this may I ask why we need to flash boot_XT1663_356.img ?
Also, isn't this command wrong? fastboot flash boot boot_XT1663_356.img
It should be fastboot flash boot boot_XT1663_356.img
Without the boot twice ryt?
Also, will the data be erased after installing TWRP recovery or not? If not, will it be erased after installing the SuperSU?

manandua01 said:
Thanks for your help Y_Y
Hey bro, I am not about to install the recovery.
Before this may I ask why we need to flash boot_XT1663_356.img ?
Also, isn't this command wrong? fastboot flash boot boot_XT1663_356.img
It should be fastboot flash boot boot_XT1663_356.img
Without the boot twice ryt?
Also, will the data be erased after installing TWRP recovery or not? If not, will it be erased after installing the SuperSU?
Click to expand...
Click to collapse
1 - It is the Image file which is specifically build for S356 (build number) hence it is necessary to flash it before flashing TWRP. If you don't flash boot image then you might face boot loop issues and hard brick your phone.
2 - The correct command is 'fastboot flash boot boot_XT1663_356.img' . the first boot is to recognize cmd that we are flashing a boot image and the second boot is the name of image file.
3 - Flashing TWRP and Super SU won't erase your data.

akash.mahadeshwar said:
1 - It is the Image file which is specifically build for S356 (build number) hence it is necessary to flash it before flashing TWRP. If you don't flash boot image then you might face boot loop issues and hard brick your phone.
2 - The correct command is 'fastboot flash boot boot_XT1663_356.img' . the first boot is to recognize cmd that we are flashing a boot image and the second boot is the name of image file.
3 - Flashing TWRP and Super SU won't erase your data.
Click to expand...
Click to collapse
I installed TWRP unlocked bootloader copied SuperSU- and was abt to root. With volume up and down I came to Factory Mode
It said Factory Mode
I pressed on power button- now it shows something in Japenese or Chinese what should I DO? I am scared as hell bro
ITS DOING SOME WEIRD STUFF NOW- GPS, SIM etc I have no clue .-.
UPDATE: Rebooting phone- Back to my home screen now. Heres what happened
(uploading video will post link here soon)

manandua01 said:
I installed TWRP unlocked bootloader copied SuperSU- and was abt to root. With volume up and down I came to Factory Mode
It said Factory Mode
I pressed on power button- now it shows something in Japenese or Chinese what should I DO? I am scared as hell bro
ITS DOING SOME WEIRD STUFF NOW- GPS, SIM etc I have no clue .-.
UPDATE: Rebooting phone- Back to my home screen now. Heres what happened
(uploading video will post link here soon)
Click to expand...
Click to collapse
As i have mentioned in my thread that you need to select recovery mode and not factory mode
Please select recovery mode and you should b able to see twrp
Note - to select recovery mode press volum up n down button till it shows 'recovery mode ' in the andrioid logo screen

akash.mahadeshwar said:
1 - It is the Image file which is specifically build for S356 (build number) hence it is necessary to flash it before flashing TWRP. If you don't flash boot image then you might face boot loop issues and hard brick your phone.
2 - The correct command is 'fastboot flash boot boot_XT1663_356.img' . the first boot is to recognize cmd that we are flashing a boot image and the second boot is the name of image file.
3 - Flashing TWRP and Super SU won't erase your data.
Click to expand...
Click to collapse
akash.mahadeshwar said:
As i have mentioned in my thread that you need to select recovery mode and not factory mode
Please select recovery mode and you should b able to see twrp
Note - to select recovery mode press volum up n down button till it shows 'recovery mode ' in the andrioid logo screen
Click to expand...
Click to collapse
Bro, I opened Recovery Mode, but now its asking for a password. It shows temp on the top. You from India, ryt? Could you give me your number? or maybe a skype id?
EDIT: Here's what was on my cmd after flashing the recovery http://prntscr.com/ft3t1l

manandua01 said:
Bro, I opened Recovery Mode, but now its asking for a password. It shows temp on the top. You from India, ryt? Could you give me your number? or maybe a skype id?
Click to expand...
Click to collapse
Go ahead ignore the password part.. it will only appear first time.. you should have a option to go ahead..

akash.mahadeshwar said:
As i have mentioned in my thread that you need to select recovery mode and not factory mode
Please select recovery mode and you should b able to see twrp
Note - to select recovery mode press volum up n down button till it shows 'recovery mode ' in the andrioid logo screen
Click to expand...
Click to collapse
Please reply asap
---------- Post added at 08:57 AM ---------- Previous post was at 08:56 AM ----------
akash.mahadeshwar said:
Go ahead ignore the password part.. it will only appear first time.. you should have a option to go ahead..
Click to expand...
Click to collapse
Ok trying now
---------- Post added at 09:21 AM ---------- Previous post was at 08:57 AM ----------
akash.mahadeshwar said:
Go ahead ignore the password part.. it will only appear first time.. you should have a option to go ahead..
Click to expand...
Click to collapse
Yo bro, I can only view External (sd card) storage. Not internal storage! What to do now? As I have SuperSU in Internal Storage
---------- Post added at 09:29 AM ---------- Previous post was at 09:21 AM ----------
Ok, I have rooted the phone successfully. Had to copy the SuperSU file to SD Card though 6-6

manandua01 said:
Please reply asap
---------- Post added at 08:57 AM ---------- Previous post was at 08:56 AM ----------
Ok trying now
---------- Post added at 09:21 AM ---------- Previous post was at 08:57 AM ----------
Yo bro, I can only view External (sd card) storage. Not internal storage! What to do now? As I have SuperSU in Internal Storage
---------- Post added at 09:29 AM ---------- Previous post was at 09:21 AM ----------
Ok, I have rooted the phone successfully. Had to copy the SuperSU file to SD Card though 6-6
Click to expand...
Click to collapse
Ext_sdcard folder is ur memory card folder and sdcard folder is the internal memory folder in twrp

BAM!
---------- Post added at 01:14 PM ---------- Previous post was at 01:12 PM ----------

I really thank you for this great effort
all things went good but I had a problem that I didn't find the SuperSU-v2.82-201705271822.zip although I am sure that I put it in the internal memory
please help

Hi there,
After I unlocked the bootloader, pushed the twrp recovery successfully, got stuck in the recovery mod each time I reboot the phone so can't boot the stock rom. Done wipe factory reset and format data and still nothing changed. Any ideas?
Thanks in advance OP
Edit: Just solved issue by flashing stock firmware

pdf5 said:
Hi there,
After I unlocked the bootloader, pushed the twrp recovery successfully, got stuck in the recovery mod each time I reboot the phone so can't boot the stock rom. Done wipe factory reset and format data and still nothing changed. Any ideas?
Thanks in advance OP
Edit: Just solved issue by flashing stock firmware
Click to expand...
Click to collapse
May I have the firmware file, just in case? Is it ok if firmware country code doesn't match? Do you get imei?

any idea? when image for new build will be released?

rajesh280392 said:
any idea? when image for new build will be released?
Click to expand...
Click to collapse
Well, yes ... The new boot.img for removing encryption. Especially for post-OTA updating to XT1663_S364_170803_ROW.
boot_XT1663_364.img

Does anyone know how to keep your Moto M rooted even after updating to the new security update of 7.0? Do we just flash the new .img file or what? Kinda newb here

New way to flash stock rom without miflash!! (easy way) will work on any mi device

I have developed this process by mistake
TRIED AND TESTED
Requirements -1)Download the miui 9 beta rom or stable rom (ie miui 8) from officical miui page.
It has to be fastboot rom
2)Download adb tools from androiddatahost
Procedure
*extract the rom file and then move the files from the image folder to Minimal ADB and Fastboot(which is located in c/program files)
*reboot ur phone into fasboot mode.
*open the command window in Minimal ADB and Fastboot folder and type the following commands
1) fastboot -w
2) fastboot flash system system.img
3) fastboot flash boot boot.img
4) fastboot flash recovery recovery.img
*after completing the above process type the command
5) fastboot oem lock ( it's optional this will lock ur bootloader)
6) fastboot reboot
THATS ALL ITS VERY EASY PROCESS:laugh:
AND WILL WORK ON ANY MI DEVICE WHEN EVER U WANT TO ROLL BACK TO STOCK ROM:good:
?If u want proof let me know in the comments

That re-locking bootloader step is 'optional', right?

lscambo13 said:
That re-locking bootloader step is 'optional', right?
Click to expand...
Click to collapse
Yes it depends upon u
Whether u want to remain in unlocked bootloader or u want to lock it?

Adi.s said:
Yes it depends upon u
Whether u want to remain in unlocked bootloader or u want to lock it
Click to expand...
Click to collapse
i guess you better add some explanation for that step just in case someone really did all the step without knowing it was optional
thank you for this thread, useful
---------- Post added at 02:17 PM ---------- Previous post was at 02:12 PM ----------
i think you have some typos on your last words too
cheers

Z17S (NX595J) Unlock Bootloader & TWRP

Hi, I'm new to this phone. Just got it 1 week ago. I tried to find any related information on the bootloader unlock and custom recovery, but it is very limited. I think maybe this phone is not well known. I would appreciate if someone can provide me the way to unlock bootloader, flash TWRP and roots. I can't live without magisk and viper4android. Thanks.

Here ya go,
1. Download and install minimal fastboot adb
2.Download TWRP rename it Recovery and move it to minimal fastboot adb folder
3. Unlock bootloader, in fastboot enter the following code : fastboot oem nubia_unlock NUBIA_NX595J
4. then also in fastboot: fastboot flash recovery recovery.img
5. you may need to format data in TWRP to get it to boot up !
Enjoy your new life !

thanks

dantonuci said:
Here ya go,
1. Download and install minimal fastboot adb
2.Download TWRP rename it Recovery and move it to minimal fastboot adb folder
3. Unlock bootloader, in fastboot enter the following code : fastboot oem nubia_unlock NUBIA_NX595J
4. then also in fastboot: fastboot flash recovery recovery.img
5. you may need to format data in TWRP to get it to boot up !
Enjoy your new life !
Click to expand...
Click to collapse
Hi, I've tried numerous timed and it always won't pick up the command of unlocking bootloader. It always stay in the fastboot menu. I've toggled the 'OEM Unlock' function in the developer setting, as well as the USB debugging. Any idea why the device won't pick up that command?

Is it changing to unlock after you enter the command?
If so flash twrp then boot into recovery ...

dantonuci said:
Is it changing to unlock after you enter the command?
If so flash twrp then boot into recovery ...
Click to expand...
Click to collapse
Nope. It doesn't respond to the command in the fastboot. It just shows the fastboot menu. My adb is written 'waiting for device.... '.

Drivers , uninstall all other drivers and try please

dantonuci said:
Drivers , uninstall all other drivers and try please
Click to expand...
Click to collapse
Okay will try again

storytellerz said:
Okay will try again
Click to expand...
Click to collapse
I am also finding this message, what is its solution ???

the same recovery
dantonuci said:
Here ya go,
1. Download and install minimal fastboot adb
2.Download TWRP rename it Recovery and move it to minimal fastboot adb folder
3. Unlock bootloader, in fastboot enter the following code : fastboot oem nubia_unlock NUBIA_NX595J
4. then also in fastboot: fastboot flash recovery recovery.img
5. you may need to format data in TWRP to get it to boot up !
Enjoy your new life !
Click to expand...
Click to collapse
Hi there, when I flashed the recovery that is always the stock recovery, why?

vins84 said:
Hi there, when I flashed the recovery that is always the stock recovery, why?
Click to expand...
Click to collapse
Not sure what you're asking, did you want to flash TWRP or stock? I was just giving tutorial for how to install TWRP

dantonuci said:
Here ya go,
1. Download and install minimal fastboot adb
2.Download TWRP rename it Recovery and move it to minimal fastboot adb folder
3. Unlock bootloader, in fastboot enter the following code : fastboot oem nubia_unlock NUBIA_NX595J
4. then also in fastboot: fastboot flash recovery recovery.img
5. you may need to format data in TWRP to get it to boot up !
Enjoy your new life !
Click to expand...
Click to collapse
I'm having the problem. Unlock is not sticking to unlock. The unlock works and the flash works but as soon as you try and reboot into recovery it hangs at a blank screen no twrp. Console says waiting for device and stuck. next time I go into bootloader it says locked. The count is 3 for unlock count is there a limit? 7-6-18 Nubia Z17 NX591J WIn 10.

bmaz121 said:
I'm having the problem. Unlock is not sticking to unlock. The unlock works and the flash works but as soon as you try and reboot into recovery it hangs at a blank screen no twrp. Console says waiting for device and stuck. next time I go into bootloader it says locked. The count is 3 for unlock count is there a limit? 7-6-18 Nubia Z17 NX591J WIn 10.
Click to expand...
Click to collapse
Trouble shoot and experiment with the process it will work, even if it appears not locked after reboot

dantonuci said:
Trouble shoot and experiment with the process it will work, even if it appears not locked after reboot
Click to expand...
Click to collapse
I don't understand? Appears not locked? It is locked. Now I remember when I flashed my Star N997 the developer said that there is a unlock bit that has to be turned on in the process of unlocking. I think this may be the case here since it unlocks until a reboot. I am deep concerned that after a unlock count of 3 the phone will not boot anymore. Do you know anything about these things? Another thought is does the USB C need different drivers and should it be plugged into a USB 3.0 outlet?

TWRP will flash only when it's unlocked so even if it's saying it's locked go by what you can do with TWRP
---------- Post added at 12:25 AM ---------- Previous post was at 12:24 AM ----------
I did it several times and never had a problem

i was looking for camera.apk file from Nubia Z17S phone from Stock ROM, can anyone upload it here..it should be located in system / app or app-pvt folder, you can copy using Root Explorer tool.
pls. let me know...

I'm having problems unlocking the bootloader. Has anyone got the proper TWRP for this phone? I can't find it. The one I have says FAILED (remote: Requested download size is more than max allowed). Thanks

hello links no longer works. Someone could give me back the TWRP and minimalb fastboot adb

For anyone's information, TWRP will not boot in recovery while the phone is being charged. Unplug first. You will just get a black screen.

i am also experiencing the same issue.. where can i find the drivers for this phone nx595j? or how do i uninstall the drivers for it?
---------- Post added at 01:21 AM ---------- Previous post was at 01:17 AM ----------
yo can somebody help me install a custom rom on my z17s via team viewer?? im willing to pay for your time