EDIT - UPDATED INSTRUCTIONS 12th May 2014
Due to the partition sizes being different in the GPE RUU it is not simply a case of flashing a sense rom in recovery. You will experience problems if you do this. This might involve getting the storage encrption message, bootloops, freezing etc etc.
This thread is specifically for users who have problems getting back to sense. Solution is below. If you have alternative solutions that have worked without issues please post.
I have tried to make them as simple as possible. This guide assumes you are S-Off otherwise how did you get here. (
This does not apply if you have installed a GPE ROM. You can flash as normal through recovery. (using instructions of new rom)
Thanks to @exad for his continuing support/assistance throughout the thread, as well as @graffixnyc for the GPE RUU and both he and @navalynt for finding the initial fixes.
It will be much easier if you have your new Rom on your external sdcard prior to starting this. It will also stop a number of problems if you have SuperCID (11111111) If you don't know how to - FASTBOOT Commands
1. Enter the command "fastboot oem readcid". Make and KEEP a note of your original CID.
2. Enter the command "fastboot oem writecid 11111111"
3. Enter the command "fastboot read cid" [it should confirm your CID is 11111111]
4. Press the volume down button twice on your phone and navigate to reboot bootloader, then hit power button to reboot the bootloader.
5. Bootloader will also say "CID-11111111" now to confirm (Thanks to @xl VipeR lx ) Also to @umjammerlammy for the GENTLE reminders to include this
Make sure the firmware file and twrp recovery are in your Android directory on your PC - Mine is
C:\Users\Grentuu\AppData\Local\Android\android-sdk\platform-tools\
During this process you may find that when you reboot the phone starts to boot into android. Mine did but simply had the GPE animated logo but never entered GPE. All you do is press Vol up and power for about 10 seconds to reset. As soon as it resets press vol down and power to get back to bootloader.
Flash 1.54.401.5 firmware from Here
Fastboot Method
Boot device into FASTBOOT mode either by adb reboot bootloader or Vol down & Power (device should show FASTBOOT USB)
Make sure the firmware file to be flashed is in your android folder
Open a command prompt from the folder where fastboot resides. (Hold shift key/right click in the dir to get menu - left click on Open Command Prompt here.)
Run the following commands:
fastboot oem rebootRUU (this will reboot the device into RUU mode in preparation for zip flashing)
fastboot flash zip 1.54.401.5-W_Splash.zip (the name of the zip should EXACTLY match the name of the file you're flashing)
It will fail the first time. Run the same command AGAIN until you see it has flashed successfully.
I repeat - Run the same command TWICE until you see it has flashed successfully.
Once complete, type fastboot reboot-bootloader The hyphen is required.
Some users have stated this firmware (1.54.401.5) did not work for them as they weren't GSM and reboots just threw them back to recovery. If this happens try a stock (your original e.g. T-mobile) firmware then follow the rest of the process.
Boot into stock recovery
Factory reset
Reboot into bootloader
Flash TWRP - command = fastboot flash recovery openrecovery-twrp-2.7.0.2-m8.img (The must match exactly the name of the recovery you are flashing and remember the recovery file must be in your android folder)
Boot into TWRP
Go into Wipe menu
do a full factory reset wipe
Reboot back into recovery
Install rom
Profit
These have worked for me everytime (Change count =19)
Thanks for this. I'm about to give it a shot now.
Sent from my HTC One_M8 using XDA Premium 4 mobile app
---------- Post added at 05:08 PM ---------- Previous post was at 04:40 PM ----------
For some reason the firmware wont flash in twrp. Should I sideload the firmware?
Sent from my GT-P5210 using XDA Premium 4 mobile app
To flash a firmware you must be in bootloader/fastboot mode.
Fastboot oem rebootRUU
Fastboot flash zip firmwarefilename.zip
Then again
Fastboot flash zip firmwarefilename.zip
Fastboot reboot-bootloader
exad said:
To flash a firmware you must be in bootloader/fastboot mode.
Fastboot oem rebootRUU
Fastboot flash zip firnwarefilename.zip
Then again
Fastboot flash zip firnwarefilename.zip
Fastboot reboot-bootloader
Click to expand...
Click to collapse
Thanks. Understood, I was just reviewing my steps for the conversion. I really just want to try out that new Sense rom and then I'll probably revert back. BRB...I'll let you know how it goes.
Bear in mind you must have S-off to flash a firmware that way.
exad said:
To flash a firmware you must be in bootloader/fastboot mode.
Fastboot oem rebootRUU
Fastboot flash zip firmwarefilename.zip
Then again
Fastboot flash zip firmwarefilename.zip
Fastboot reboot-bootloader
Click to expand...
Click to collapse
Those are the instructions in post 1 the original thread.
The issue is with people wanting to go back to sense
This thread is about returning to sense. Flashing a firmware is always the same. It's the firmware itself that's different...
Here is where I am at..
I converted to GP easily and it worked well.. I wanted to convert back so I installed twrp first, then through twrp installed the 1.54.401.5 firmware.
Installing that firmware removed twrp and the rom. So I am without an OS at all, and have stock recovery.
Is there anyway I can flash a custom recovery or a rom via the stock firmware/recovery?
My computer will not recognize adb devices. But it used to obviously.
I have an SD card.
Any help and I will be sooo grateful. (maybe even donate)
Thanks!
You can't flash a firmware through recovery... You can flash a stock recovery after the steps listed above if you like. See the stock backup thread.
You can flash any recovery through fastboot... Adb only works with the rom booted or with custom recovery booted.
Thanks will try it out.
exad said:
You can't flash a firmware through recovery... You can flash a stock recovery after the steps listed above if you like. See the stock backup thread.
You can flash any recovery through fastboot... Adb only works with the rom booted or with custom recovery booted.
Click to expand...
Click to collapse
So what do I do in this situation with no rom installed only 1.54 firmware and stock recovery.
Flash twrp
exad said:
Flash twrp
Click to expand...
Click to collapse
I have no rom installed, so it wont show in adb devices.
PunchLick said:
I have no rom installed, so it wont show in adb devices.
Click to expand...
Click to collapse
You flash recovery via fastboot, no need for a rom.
Just make sure you have the proper fastboot drivers from htc.
Dmaxon said:
You flash recovery via fastboot, no need for a rom.
Just make sure you have the proper fastboot drivers from htc.
Click to expand...
Click to collapse
ADB devices shows no devices. If i had custom recovery this would be so much easier, but im using 1.54.401.5 firmware with stock recovery and no ROM.
Just dont know what to do to get a working device again. All i can do is boot into stock recovery, hboot and fastboot.. but computer shows no device.
PunchLick said:
ADB devices shows no devices. If i had custom recovery this would be so much easier, but im using 1.54.401.5 firmware with stock recovery and no ROM.
Just dont know what to do to get a working device again. All i can do is boot into stock recovery, hboot and fastboot.. but computer shows no device.
Click to expand...
Click to collapse
I would recommend the All-In-One Toolkit. This will allow you to fastboot the recovery, even though the pc doesn't recognize it. This has worked for me in the past.
Meanwhile, I get the following error message when attempting to flash the 1.54...
Any suggestions guys???
Problem solved. I had not supercid. After I did that, I was able to successfully flash 1.54...
Why post steps if your not willing to help?
The steps in the OP can still cause issues for some people.
Sent from my HTC One_M8 using Tapatalk
Ideas4ya said:
I would recommend the All-In-One Toolkit. This will allow you to fastboot the recovery, even though the pc doesn't recognize it. This has worked for me in the past.
Meanwhile, I get the following error message when attempting to flash the 1.54...
Any suggestions guys???
Problem solved. I had not supercid. After I did that, I was able to successfully flash 1.54...
Click to expand...
Click to collapse
Can you elaborate a little on which options etc, because that sounds fantastic and would help me so much!
PunchLick said:
Can you elaborate a little on which options etc, because that sounds fantastic and would help me so much!
Click to expand...
Click to collapse
When you open the all in one...the 3rd option on the top right is what you need. Follow the step, even if fastboot says device is not connected, this will still send the recovery to your device as long as you're in the bootloader.
I will never understand why people play with there phones and have no understanding of adb and fastboot commands with the bootloader. if people would learn that first there wouldn't be so many threads when they get stuck. tool kits are bad it makes people lazy. but I appreciate the devs who make them
Related
Hello,
I updated my UK Xoom 3G (MZ601) via OTA to 3.2 (H.6.5-17-3) last year.
Since I got interested in rooting the device I read I have to install CWM first.
However, when going into recovery mode (for testing) all I get is a green android bot.
Thanks to some googling I found some website that mentions to hold the power button (while the green android bot is shown) and press volume up, then release the power key. Now I see the stock 3e recovery menu.
Is it safe to simply unlock the bootloader and flash CWM via ADB? Or am I required to flash back to the xoom dev stock rom because of the green fella? My question refers to this part:
Or, if you do not already have root on your xoom when you get the green bot of ! then you have to do the following with the stock moto files for your device (from moto dev).
(This Wipes your Xoom )
fastboot oem unlock
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash recovery recovery.img
fastboot -w
fastboot reboot
Click to expand...
Click to collapse
Not sure why I would have to do that? In the end, I'd want to have a rooted stock 3.2.
First unlock it indeed while seeing the green bot in recovery.
(using the commands you posted yourself)
Then, you back into recovery, and push the new cwm recovery using adb
(look on the xda xoom's section: you'll find the right tutorial; should start with downloading adb, downloading cwm into the same directory as where you put the adb drivers for the xoom. Then open command as administrator, etc.)
After that, you should have CWM (or I recommend the touch Rogue recovery! ) on your Xoom, instead of the ugly little green bot, now allowing you to flash many, many ROMs, zips and many other to your device!
Enjoy. Hope this is clear enough and helps you towards the right direction! (if so, please do thank me, since I only just made an XDA account and would like at least one thanked post lol.
If not, please PM me or ask further explanations in this thread! )
adelancker said:
First unlock it indeed while seeing the green bot in recovery.
(using the commands you posted yourself)
Click to expand...
Click to collapse
I suppose you only refer to the adb commands without flashing the img files, right?
I still don't know why that other thread suggested to flash back to an older version first (see quote in my first posting)? Can anyone tell me if I have to downgrade at all?
Landorin said:
I suppose you only refer to the adb commands without flashing the img files, right?
I still don't know why that other thread suggested to flash back to an older version first (see quote in my first posting)? Can anyone tell me if I have to downgrade at all?
Click to expand...
Click to collapse
First unlock it using those fastboot commands you posted. You should in this series of commands not flash anything yet. Just unlock it first. When rebooting and showing the Moto logo:
Get back into recovery and then push the new recovery.img using adb commands
As far as I know, there is not one reason to downgrade. Should work just fine.
---------- Post added at 01:23 PM ---------- Previous post was at 01:05 PM ----------
adelancker said:
First unlock it using those fastboot commands you posted. You should in this series of commands not flash anything yet. Just unlock it first. When rebooting and showing the Moto logo:
Get back into recovery and then push the new recovery.img using adb commands
As far as I know, there is not one reason to downgrade. Should work just fine.
Click to expand...
Click to collapse
Otherwise, use this as your guideline and you should be fine:
http://forum.xda-developers.com/showthread.php?t=1249798
Thank you! All worked out fine. I followed the guide step by step, I did not downgrade the existing ROM.
In case someone else gets into the same situation and wonders how to do it:
once everything is set up for ADB and the device is found (command adb devices) type this in your command prompt window:
Code:
adb reboot bootloader
waited for fastboot protocol text to show up on Xoom device, then:
Code:
fastboot oem unlock
Confirmed the warning. Then had the device booting up normally to re-enable USB debugging. Then continued:
Code:
adb reboot bootloader
again waited for fastboot protocol text to show up on Xoom device, then:
Code:
fastboot flash recovery recovery-Tiamat-R4c-100611-1150-cwm.img
When it said flashing done I restarted the Xoom (holding power button + volume up). About 3-4 sec after seeing the Motorola pic I hit volume down ("android recovery" is displayed), then volume up and CWM showed up.
Since I was already in CWM I also applied the universal root method ("install zip from sdcard" -> "choose zip from sdcard", then selected the actual file on the sd card, installed it, rebooted). Root works.
P.S.: just realized silly me forgot to do a nanddump before rooting.
something like forgetting a nanddump only happens once!
Glad to see it worked for you!
Even happier to see you didn't need to downgrade.
Once you flash a custom ROM, you'll have 3G and ICS!
I did the same a couple of months ago, and my device felt brand new!
Issue solved by using the following commands in fastboot via this link http://forum.xda-developers.com/showpost.php?p=34552123&postcount=1, For anyone who has a similiar problem do the following.
1) Make sure your computer recognizes your device by typing: fastboot devices
2) Unlock your bootloader (if you have not already done so): fastboot oem unlock
3) You will see a prompt on your device. This will wipe your entire device (including the /sdcard folder). Accept. Note: you use the volume keys to change the option and the power button to accept. You cannot use the touch screen.
4) Reboot by typing: fastboot reboot-bootloader
5) Flash the bootloader: fastboot flash bootloader bootloader-mako-makoz10o.img (or whatever the name of the bootloader image that you downloaded).
6) Reboot: fastboot reboot-bootloader
7) Flash the radio: fastboot flash radio radio-mako-m9615a-cefwmazm-2.0.1700.48.img (or whatever the name is of the radio image that you downloaded).
8) Reboot: fastboot reboot-bootloader
9) Flash the system partition: fastboot flash system system.img
Flash the factory images with the toolkit then flash a custom recovery and root
Sent from my Nexus 4 using Tapatalk
Boot your device into fastboot mode and then you can manually flash back to stock.
http://forum.xda-developers.com/nexus-4/general/how-to-how-to-flash-factory-image-t2010312
Zehlek said:
Flash the factory images with the toolkit then flash a custom recovery and root
Sent from my Nexus 4 using Tapatalk
Click to expand...
Click to collapse
audit13 said:
Boot your device into fastboot mode and then you can manually flash back to stock.
http://forum.xda-developers.com/nexus-4/general/how-to-how-to-flash-factory-image-t2010312
Click to expand...
Click to collapse
Thanks, is there a way to backup my sd card before flashing back to stock?
tarroyo said:
Thanks, is there a way to backup my sd card before flashing back to stock?
Click to expand...
Click to collapse
Flash the system.img file only.
Sent with my Nexus® 10 minus 3
Problem solved!
I get remote : partition table doesn't exist.
I have been working on this all night. WIn Drivers for ADB, Fast boot, naked drivers, and on and on. Tried to push a ROM for CWM and round and round I go. Nothing works. The phone for lack of any other words seems to be dead except I can get flashboot to talk to it. ANy idea? Please?
williamsck said:
I get remote : partition table doesn't exist.
I have been working on this all night. WIn Drivers for ADB, Fast boot, naked drivers, and on and on. Tried to push a ROM for CWM and round and round I go. Nothing works. The phone for lack of any other words seems to be dead except I can get flashboot to talk to it. ANy idea? Please?
Click to expand...
Click to collapse
I got it!
I've seen posts requesting "how to" and posts of problems attempting to root after installing the 5.1 OTA update. This post outlines the steps to root with an UNLOCKED BOOTLOADER.
NOTE: This will only work if your bootloader is already unlocked. It is based on -> http://forum.xda-developers.com/moto-x/moto-x-qa/instructions-unlocking-rooting-dev-ed-t2649738 but slightly updated.
Don't know if your bootloader can be unlocked? see -> HERE
Requirements...
the latest TWRP fastboot IMG file (Alternate Link) UPDATE: There is an issue with TWRP 2.8.7.0 (SEE THIS POST Thanks @jodaboda ). Please use TWRP 2.8.6.0 for now!
the latest Installable ZIP of SuperSU (Alternate: http://download.chainfire.eu/supersu )
You must have already installed the Motorola Drivers, ADB, Android Platform Tools, and mFastboot
mFastboot (get from the previous link). NOTE: Stock fastboot that ships with the Android SDK/Platform tools will likely work, but Moto's fastboot is always suggested!
Your battery has an 80% or greater charge!!
MicroUSB Cable.
Know how to start your phone into the Fastboot AP/Bootloader mode...
Unplug phone
Power down phone.
Hold Volume Down and Power
After a few seconds release Power, you should be in Fastboot AP menu on phone.
The steps...
NOTE: replace TWRP.IMG in the below steps, with the name of the file you downloaded!! Example: twrp-2.8.6.0-ghost.img
NOTE: failure to perform these steps EXACTLY as written can result in the apparence of the Android in distress (logo with Exclamation mark) with the caption "No Command" and the inability to enter recovery, OR it will enter STOCK recovery even though you have flashed TWRP!
Start the phone in Fastboot AP mode.
Connect your phone to PC via MicroUSB cable.
open a command prompt and change to the folder you downloaded your TWRP.IMG file.
type the following, pressing enter after each command, and wait for it to finish before going onto the next...
mfastboot flash recovery TWRP.img
mfastboot reboot-bootloader
Use the VOL DOWN Key to SCROLL to Recovery and VOL UP Key to select
The device should enter TWRP.
If your device is not rooted, TWRP may prompt you to root now or install SuperSU. Do it.
Use the menu options to Reboot to system.
You will likely be prompted to UPDATE SuperSU. Please update it, and reboot.
IF TWRP doesn't prompt you to root/install SuperSU.... (more exact instructions coming later...)
With your phone booted normally, connect it via USB cable to your PC.
Drag/Drop the SuperSU.zip you downloaded onto the phone's internal storage
Reboot the phone into TWRP
Use the menu option to install zip, navigate to and select the SuperSU zip.
Boot to System.
EDIT: 9-17-2015 edited first TWRP link.
KidJoe said:
I've seen posts requesting "how to" and posts of problems attempting to root after installing the 5.1 OTA update. This post outlines the steps to root with an UNLOCKED BOOTLOADER.
NOTE: This will only work if your bootloader is already unlocked. It is based on -> http://forum.xda-developers.com/moto-x/moto-x-qa/instructions-unlocking-rooting-dev-ed-t2649738 but slightly updated.
Don't know if your bootloader can be unlocked? see -> HERE
Requirements...
the latest TWRP fastboot IMG file (Alternate Link)
the latest Installable ZIP of SuperSU (Alternate: http://download.chainfire.eu/supersu )
You must have already installed the Motorola Drivers, ADB, Android Platform Tools, and mFastboot
mFastboot (get from the previous link). NOTE: Stock fastboot that ships with the Android SDK/Platform tools will likely work, but Moto's fastboot is always suggested!
Your battery has an 80% or greater charge!!
MicroUSB Cable.
Know how to start your phone into the Fastboot AP/Bootloader mode...
Unplug phone
Power down phone.
Hold Volume Down and Power
After a few seconds release Power, you should be in Fastboot AP menu on phone.
The steps...
NOTE: replace TWRP.IMG in the below steps, with the name of the file you downloaded!! Example: twrp-2.8.6.0-ghost.img
NOTE: failure to perform these steps EXACTLY as written can result in the apparence of the Android in distress (logo with Exclamation mark) with the caption "No Command" and the inability to enter recovery, OR it will enter STOCK recovery even though you have flashed TWRP!
Start the phone in Fastboot AP mode.
Connect your phone to PC via MicroUSB cable.
open a command prompt and change to the folder you downloaded your TWRP.IMG file.
type the following, pressing enter after each command, and wait for it to finish before going onto the next...
mfastboot flash recovery TWRP.img
mfastboot reboot-bootloader
Use the VOL DOWN Key to SCROLL to Recovery and VOL UP Key to select
The device should enter TWRP.
If your device is not rooted, TWRP may prompt you to root now or install SuperSU. Do it.
Use the menu options to Reboot to system.
You will likely be prompted to UPDATE SuperSU. Please update it, and reboot.
IF TWRP doesn't prompt you to root/install SuperSU.... (more exact instructions coming later...)
With your phone booted normally, connect it via USB cable to your PC.
Drag/Drop the SuperSU.zip you downloaded onto the phone's internal storage
Reboot the phone into TWRP
Use the menu option to install zip, navigate to and select the SuperSU zip.
Boot to System.
Click to expand...
Click to collapse
I still haven't unlocked my Bootloader (being on 5.1). In the linked post it's been mentioned that "TWRP custom recovery for KitKat" - my question is, is there a TWRP Custom Recover for OTA 5.1 update? And I'm on XT1052, same procedure follows?
Do you know where I can find mfastboot for Mac OSX?
kidjoe, your a priceless resource!
i installed an older verison of twrp and had all the issues you speak off, installed 2.8.6 with success but would not root upon reboot, installed the super su zip in op via twrp, one last thing i had to enter the super su app and tap enable superuser and now all is good:good::good
Thanks, worked like a charm
Thanks.. It's been ages since I used I last used adb commands and flashed something. I couldn't figure out how to boot into recovery.
Vampirexox said:
I still haven't unlocked my Bootloader (being on 5.1). In the linked post it's been mentioned that "TWRP custom recovery for KitKat" - my question is, is there a TWRP Custom Recover for OTA 5.1 update? And I'm on XT1052, same procedure follows?
Click to expand...
Click to collapse
twrp-2.8.6.0-ghost.img works on Lollipop too. (just used it last night on my sister-in-law's GSM Dev Edition XT1053 that got the lollipop update)
jay_em said:
Do you know where I can find mfastboot for Mac OSX?
Click to expand...
Click to collapse
Here is a copy on my Box 'drive':
https://app.box.com/s/5nlgy2avccupw4box8z2be50ezt4qn7p
EDIT: I just got an e-mail saying it had been downloaded. :good:
---------- Post added at 08:54 AM ---------- Previous post was at 08:45 AM ----------
kyzn said:
Thanks.. It's been ages since I used I last used adb commands and flashed something. I couldn't figure out how to boot into recovery.
Click to expand...
Click to collapse
EDIT: [If you are still running the stock Recovery] You can also use:
Code:
adb reboot recovery
When you see the horizontal robot hold the Volume Up key for 3 seconds and then tap Power and the Recovery Menu will display.
Thanx for this how-to. Everyone has been getting confused in root process for 5.1 although it is nearly same as 4.4.4.
Sent from my XT1052
I had to use twrp-2.8.6.0-ghost.img
twrp 2.8.7 would not "see" the SD card, and I couldn't install the SuperSU.zip
Thanks for the post!
jodaboda said:
I had to use twrp-2.8.6.0-ghost.img
twrp 2.8.7 would not "see" the SD card, and I couldn't install the SuperSU.zip
Thanks for the post!
Click to expand...
Click to collapse
I had the same issue with my XT1053. Following your advice did the trick. Not being able to modify my dpi since upgrading has been killing me. Its the only thing i really want root for. Thanks for everything both you and op!
jodaboda said:
I had to use twrp-2.8.6.0-ghost.img
twrp 2.8.7 would not "see" the SD card, and I couldn't install the SuperSU.zip
Thanks for the post!
Click to expand...
Click to collapse
Ahh... 2.8.7 wasn't out when I tried.. 2.8.6 was the latest at that time. Maybe there is a bug in 2.8.7 that will get fixed in future versions?
Sunshine unlocked bootloader
Does anyone know if there are any issues resulting from a Sunshine unlocked bootloader? I saw one post that had a warning but it was a warning because there was no information at the time. Has this change?
i installed TWRP successful, but after normal reset, TWRP is gone, it's only stock recovery (Android down image). Please help me. My phone is running 5.1 update OTA, unlocked bootloader
md07 said:
i installed TWRP successful, but after normal reset, TWRP is gone, it's only stock recovery (Android down image). Please help me. My phone is running 5.1 update OTA, unlocked bootloader
Click to expand...
Click to collapse
When you say "installed TWRP successful"... do you mean that fastboot didn't error? or that fastboot completed the install, you did a mfastboot reboot-bootloader, and tried entering TWRP but it still gave you the "dead android" image?
Is there any unofficial way to unlock bootloader?
Sent from my Nexus 7 using Tapatalk
I can't get it to work on a friend's Moto X... I flash using mfastboot and upon rebooting, it goes into battery charging mode.
If I fully boot into Android, then reboot to recovery, I still get the "dead Android on his back" recovery. What's going on?!
djibril13 said:
Is there any unofficial way to unlock bootloader?
Click to expand...
Click to collapse
Sunshine... IF you're phone has never been upgraded to 4.4.4.
BUT if you can get unlock code from Moto, while it can void your warranty (depending on your local laws), that is FREE, and the best way.
SX86 said:
I can't get it to work on a friend's Moto X... I flash using mfastboot and upon rebooting, it goes into battery charging mode.
If I fully boot into Android, then reboot to recovery, I still get the "dead Android on his back" recovery. What's going on?!
Click to expand...
Click to collapse
help me understand your situation...
You are doing.. Mfastboot flash recovery -> mfastboot reboot-bootloader -> you get battery charging screen rather than fasboot/bootloader menu/screen?
or ??
SX86 said:
I can't get it to work on a friend's Moto X... I flash using mfastboot and upon rebooting, it goes into battery charging mode.
If I fully boot into Android, then reboot to recovery, I still get the "dead Android on his back" recovery. What's going on?!
Click to expand...
Click to collapse
after flashing did you but to recovery befour booting system? with my experience i had to boot to recovery first befour system
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
I have been on a journey trying to go back to my T-Mobile OnePlus 6T back as my daily driver but the official updates killed the device for me. I have been successful in flashing it to the international version and now the device is on A9. I am trying to get it updated to A10 but in order do that (does not take OTA updates or can not flash within the updates app) I have to flash in recovery. Right now it is on stock recovery so I am trying to flash TWRP.
The problem is now that everytime I run the command " fastboot boot IMAGENAME.img" the phone restarts (as expected) and boots into fastboot but stays stuck in the Fastboot Mode screen.
I tried different TWRP images (older and the most current version per https://dl.twrp.me/fajita/ ) but I keep getting stuck in the Fastboot Mode screen. The last thing I was able to do without issues was unlock bootloader using fastboot.
I just need to be able to flash TWRP on the phone so I can still the final stock image so I can go back to using it as my DD.
EDIT: Disregard everything I fixed it. mods, please delete thread.
EDITR 2: Disregard that last edit lol Yeah I still need help. I am now tryingto flash twrp on a second 6T and the issue described above still applies.
You can try this version. Also try unplugging the USB after it reboots. You aren't getting any crash dump screen? So it should be working.
Brettroth said:
You can try this version. Also try unplugging the USB after it reboots. You aren't getting any crash dump screen? So it should be working.
Click to expand...
Click to collapse
Tried your image and still same result. I am running following command
Code:
fastboot boot TWRP-3.6.1_11-OP6xT.img
The command window outputs the following
Code:
Sending 'boot.img' (34964 KB) OKAY [ 0.747s]
Booting OKAY [ 0.092s]
Finished. Total time: 0.860s
The phone then reboots into Fastboot Mode logo and stays stuck there. I even tried unplugging the USB after it reboots as well.
I even tried using the flash command instead of boot but no success.
How about fastboot boot recovery? Should be able to get into recovery somehow. Doing fastboot flash of twrp will mess up your boot partition but either way you still should be able to get into recovery somehow. There is the msm recovery tool you can use as last resort but it will relock your bootloader
Actually fastboot doesn't let you use boot recovery command I don't think. Only adb. But once you are in fastboot can't you choose to reboot recovery with volume keys?
Brettroth said:
How about fastboot boot recovery? Should be able to get into recovery somehow. Doing fastboot flash of twrp will mess up your boot partition but either way you still should be able to get into recovery somehow. There is the msm recovery tool you can use as last resort but it will relock your bootloader
Click to expand...
Click to collapse
I tried doing fastboot boot recovery but i get following error
Code:
fastboot: error: cannot load 'recovery': No such file or directory
Brettroth said:
Actually fastboot doesn't let you use boot recovery command I don't think. Only adb. But once you are in fastboot can't you choose to reboot recovery with volume keys?
Click to expand...
Click to collapse
When I am in fastboot mode, yes I can choose recovery but it takes me to the stock recovery. I do not have a option to flash any zip files there
Maybe you need a twrp for Android 9 since that's what you are on. But fastboot boot twrp should just take you there. Either have to find one that works or go msm route. Maybe windows not reading it correctly also. You using CMD or PowerShell?
Brettroth said:
Maybe you need a twrp for Android 9 since that's what you are on. But fastboot boot twrp should just take you there. Either have to find one that works or go msm route. Maybe windows not reading it correctly also. You using CMD or PowerShell?
Click to expand...
Click to collapse
I tried both CMD and PowerShell. I am going to try a A9 version of twrp
EDIT: I am using twrp-3.6.1_9-0-fajita.img (which I assume is for A9) and still get the same result. Even tried a different usb port.. not sure what i could be missing. I also did the instructions as advised straight from twrp's website.
smartinez832 said:
I tried both CMD and PowerShell. I am going to try a A9 version of twrp
EDIT: I am using twrp-3.6.1_9-0-fajita.img (which I assume is for A9) and still get the same result. Even tried a different usb port.. not sure what i could be missing. I also did the instructions as advised straight from twrp's website.
Click to expand...
Click to collapse
I don't know bud. I guess msm tool is the way to go then
Curious did you have the twrp file in same folder as adb and fastboot?
smartinez832 said:
I have been on a journey trying to go back to my T-Mobile OnePlus 6T back as my daily driver but the official updates killed the device for me. I have been successful in flashing it to the international version and now the device is on A9. I am trying to get it updated to A10 but in order do that (does not take OTA updates or can not flash within the updates app) I have to flash in recovery. Right now it is on stock recovery so I am trying to flash TWRP.
The problem is now that everytime I run the command " fastboot boot IMAGENAME.img" the phone restarts (as expected) and boots into fastboot but stays stuck in the Fastboot Mode screen.
I tried different TWRP images (older and the most current version per https://dl.twrp.me/fajita/ ) but I keep getting stuck in the Fastboot Mode screen. The last thing I was able to do without issues was unlock bootloader using fastboot.
I just need to be able to flash TWRP on the phone so I can still the final stock image so I can go back to using it as my DD.
EDIT: Disregard everything I fixed it. mods, please delete thread.
EDITR 2: Disregard that last edit lol Yeah I still need help. I am now tryingto flash twrp on a second 6T and the issue described above still applies.
Click to expand...
Click to collapse
I'm having same issue with fajita (OnePlus 6T) you found any solution if yes then please give some reply