I'm trying to root my Moto G 3rd generation. I looked around a bit and started using a guide from a website called "the unlockr" (which I can't link to) and it all seemed to be going well until the very end. I got to Part 5 "Rooting the Motorola Moto G (3rd Gen) Using SuperSU" and everything seemed to be going well, however on reboot it seems to be stuck on the bootloader warning screen. Maybe I'm being impatient but its been sitting there for a while and I fear that I've broken something.
I've read around a bit and a few threads/people in similar situations recommend flashing to a stock rom and starting again but I'm afraid I'll find a way to make things worse.
Did you make a backup before you flashed SuperSU?
Lollipop or marshmallow?
I believe stock marshmallow needs systemless root, google it there is a SuperSU systemless version out there.
If you took a backup first, just restore and try again
hossman said:
Did you make a backup before you flashed SuperSU?
Lollipop or marshmallow?
I believe stock marshmallow needs systemless root, google it there is a SuperSU systemless version out there.
If you took a backup first, just restore and try again
Click to expand...
Click to collapse
No, in my infinite wisdom I didn't take a backup. It seemed so simple before I started I didn't think I'd need it.
I'll look into SuperSU systemless but if I can't get my phone to turn on, how do I load the files to flash it? Can I transfer it using USB debugging or something?
You will most likely need to flash factory image
Check here
http://forum.xda-developers.com/showthread.php?t=3169639
[INDEX][Osprey][Merlin] Moto G Factory Firmware Images
After that you can reflash recovery and make a backup before you start tinkering again.
Follow the directions linked in that thread to the T
---------- Post added at 11:38 AM ---------- Previous post was at 11:20 AM ----------
Before you flash factory image, maybe you could try flashing just stock boot.IMG through fastboot. Or maybe even squid kernel
hossman said:
You will most likely need to flash factory image
Check here
http://forum.xda-developers.com/showthread.php?t=3169639
[INDEX][Osprey][Merlin] Moto G Factory Firmware Images
After that you can reflash recovery and make a backup before you start tinkering again.
Follow the directions linked in that thread to the T
---------- Post added at 11:38 AM ---------- Previous post was at 11:20 AM ----------
Before you flash factory image, maybe you could try flashing just stock boot.IMG through fastboot. Or maybe even squid kernel
Click to expand...
Click to collapse
Finally got around to trying your advice, but I can't get ADB to recognize the phone at all. When I try to get a list of devices this is what I'm greeted with.
Code:
C:\Program Files (x86)\Minimal ADB and Fastboot>adb devices
List of devices attached
This is what my fastboot screen looks like.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Phone also shows up in Windows device manager. I dont remember the first line saying "Secure" before. Could that be part of the problem?
RTWinter said:
Finally got around to trying your advice, but I can't get ADB to recognize the phone at all. When I try to get a list of devices this is what I'm greeted with.
This is what my fastboot screen looks like.
Phone also shows up in Windows device manager. I dont remember the first line saying "Secure" before. Could that be part of the problem?
Click to expand...
Click to collapse
Which command did you use? adb devices or fastboot devices?
Henriquefeira said:
Which command did you use? adb devices or fastboot devices?
Click to expand...
Click to collapse
Hah, oh wow. I was using adb devices. Fastboot returns the phone.
One thing I'm not sure of, though, is how to push the recovery image to the phone. Someone online said you can use adb push to do so but will that work with fastboot?
RTWinter said:
Hah, oh wow. I was using adb devices. Fastboot returns the phone.
One thing I'm not sure of, though, is how to push the recovery image to the phone. Someone online said you can use adb push to do so but will that work with fastboot?
Click to expand...
Click to collapse
All info here http://forum.xda-developers.com/2015-moto-g/orig-development/twrp-twrp-moto-g-2015-t3170537
Henriquefeira said:
All info here http://forum.xda-developers.com/2015-moto-g/orig-development/twrp-twrp-moto-g-2015-t3170537
Click to expand...
Click to collapse
I tried the command fastboot flash recovery.img and I have the .img in the correct directory on my computer. However, I get the following output.
Code:
unknown partition 'recovery.img'
error: cannot determine image filename for 'recovery.img'
I tried using fastboot boot to temporarily load the .img but all that does is get me to a screen that says "No Command."
EDIT
Whoops, sorry. Realized I should have been using "fastboot flash recovery recovery.img" instead. Trying that now.
So I've tried this tutorial that hossman linked to but I still get the "No command" error when I try to go into the recovery menu.
Stuck here again, sorry to be a bother but I'm in over my head.
RTWinter said:
I tried the command fastboot flash recovery.img and I have the .img in the correct directory on my computer. However, I get the following output.
I tried using fastboot boot to temporarily load the .img but all that does is get me to a screen that says "No Command."
EDIT
Whoops, sorry. Realized I should have been using "fastboot flash recovery recovery.img" instead. Trying that now.
Click to expand...
Click to collapse
RTWinter said:
So I've tried this tutorial that hossman linked to but I still get the "No command" error when I try to go into the recovery menu.
Stuck here again, sorry to be a bother but I'm in over my head.
Click to expand...
Click to collapse
Download the "twrp-osprey-3.0.2-r1.img" image from the thread link that I gave you and move the image to your ADB and FB folder, after that booted on the bootloader of your phone use this command fastboot flash recovery twrp-osprey-3.0.2-r1.img
Related
Can anyone help me with this Ive got a Nexus S, with the latest stable vers. of Cyanogen (update-cm-7.1.0-NS-signed) and ClockworkMod as the recovery image. Was working great then all of a sudden the phone will not load past the "Google" unlocked padlock image OR go into recovery mode. I can get into the bootloader alright (vol+ key & power button) and it confirms that the phone's still "UNLOCKED". All I get, on the screen, when I try to get into ClockworkMod is "Google" and the unlocked padlock image.
Can't even get into the SD card when I hook the phone up to my PC. Tried flashing CWM says that its sent and written but still wont load.
Any ideas how I can at least get into recovery mode? Once i'm in, in theory (if there's nothing terminal, hardware-wise) I can wipe the phone, mount the sd card, put a fresh vers. of CyanogenMod on it and start again.
Wrong section.
Soooooo moved.
Obligatory YOU MORON BLAH BLAH RABBLE RABBLE!!!!
....
Seriously though, what version of the Nexus S do you have? Just want to rule out any ID10T erros first. Second what CMW did you flash via fastboot? Thridly what was your fastboot command?
ackte11 said:
Can anyone help me with this Ive got a Nexus S, with the latest stable vers. of Cyanogen (update-cm-7.1.0-NS-signed) and ClockworkMod as the recovery image. Was working great then all of a sudden the phone will not load past the "Google" unlocked padlock image OR go into recovery mode. I can get into the bootloader alright (vol+ key & power button) and it confirms that the phone's still "UNLOCKED". All I get, on the screen, when I try to get into ClockworkMod is "Google" and the unlocked padlock image.
Can't even get into the SD card when I hook the phone up to my PC. Tried flashing CWM says that its sent and written but still wont load.
Any ideas how I can at least get into recovery mode? Once i'm in, in theory (if there's nothing terminal, hardware-wise) I can wipe the phone, mount the sd card, put a fresh vers. of CyanogenMod on it and start again.
Click to expand...
Click to collapse
How did you root it?
You just need to use fastboot to flash CWM & a new rom
Example for the rom:
fastboot update ROMFILENAME.ZIP -w
For more info on fastboot
http://wiki.cyanogenmod.com/wiki/Fastboot
Edit: There, got you the Cyanogenmod page. It's a step by step guide. Skip the bootloader unlocking section. Do all the rest.
http://wiki.cyanogenmod.com/wiki/Nexus_S:_Full_Update_Guide
slimdizzy said:
Soooooo moved.
Obligatory YOU MORON BLAH BLAH RABBLE RABBLE!!!!
....
Seriously though, what version of the Nexus S do you have? Just want to rule out any ID10T erros first. Second what CMW did you flash via fastboot? Thridly what was your fastboot command?
Click to expand...
Click to collapse
sorry bout posting in the wrong section. But Ive got the GT-I9020 version, Second I tried to flash versions 3.0.2.4-crespo, 4.0.0.2-crespo, and 5.0.2.0. Nothing responded.
$ fastboot flash recovery recovery-clockwork-4.0.0.2-crespo.img
ackte11 said:
sorry bout posting in the wrong section. But Ive got the GT-I9020 version, Second I tried to flash versions 3.0.2.4-crespo, 4.0.0.2-crespo, and 5.0.2.0. Nothing responded.
$ fastboot flash recovery recovery-clockwork-4.0.0.2-crespo.img
Click to expand...
Click to collapse
Do you have a working adb setup on your computer?
Put your device in fastboot mode ( VOL up + power button)
Make sure it's properly connected and interfacing with adb (you can type "adb devices" and you should see your device in the list)
If you don't see any string of characters after typing adb devices, then you don't have a working adb setup. You need either a standalone adb or the android SDK.
polobunny said:
How did you root it?
You just need to use fastboot to flash CWM & a new rom
Example for the rom:
fastboot update ROMFILENAME.ZIP -w
For more info on fastboot
---wiki.cyanogenmod.com/wiki/Fastboot
Edit: There, got you the Cyanogenmod page. It's a step by step guide. Skip the bootloader unlocking section. Do all the rest ---.cyanogenmod.com/wiki/Nexus_S:_Full_Update_Guide
Click to expand...
Click to collapse
tried that and got these results
$ fastboot update update-cm-7.1.0-NS-signed.zip -w
archive does not contain 'android-info.txt'
archive does not contain 'android-product.txt'
error: update package has no android-info.txt or android-product.txt
I have the android sdk but after "adb devices" its saying command not found
ackte11 said:
I have the android sdk but after "adb devices" its saying command not found
Click to expand...
Click to collapse
on a mac? also what about "fastboot devices"?
Linux Ubuntu 11.04 and Windows 7 "fastboot devices" recognizes it and shows the serial number. adb on windows runs the command but just comes up blank
ackte11 said:
Linux Ubuntu 11.04 and Windows 7 "fastboot devices" recognizes it and shows the serial number. adb on windows runs the command but just comes up blank
Click to expand...
Click to collapse
Alright. Try to flash CWM recovery first, as stated in the Cyanogenmod guide. Then once that's done, boot back into CWM and flash CM7.
Did that and it says that everything goes through, move down to recovery and it just loops the "google" padlock screen
ackte11 said:
Did that and it says that everything goes through, move down to recovery and it just loops the "google" padlock screen
Click to expand...
Click to collapse
Ah okay, maybe a corrupted boot.img
Download the full 2.3.6 rom for your model
i9020a
i9020t/i9023
You can get the model in fastboot mode at the top if you're unsure of which you own.
Extract the ZIP contents and grab hold of boot.img. Flash this boot.img using fastboot
Example: fastboot flash boot boot.img
Once that is done, reboot to fastboot and flash CWM. Then from CWM flash superuser and whichever ROM you want.
polobunny said:
Ah okay, maybe a corrupted boot.img
Download the full 2.3.6 rom for your model
i9020a
i9020t/i9023
You can get the model in fastboot mode at the top if you're unsure of which you own.
Extract the ZIP contents and grab hold of boot.img. Flash this boot.img using fastboot
Example: fastboot flash boot boot.img
Once that is done, reboot to fastboot and flash CWM. Then from CWM flash superuser and whichever ROM you want.
Click to expand...
Click to collapse
Nothings working. flashed the boot then CWM still cant get into recovery. Just right back to the "google" page
I am not sure if this works on the nexus s but give it a try.
Instead of flashing the recovery try and boot it. Change the command to fastboot boot recovery .....instead of flash.
albundy2010 said:
I am not sure if this works on the nexus s but give it a try.
Instead of flashing the recovery try and boot it. Change the command to fastboot boot recovery .....instead of flash.
Click to expand...
Click to collapse
still no go.
i am having the exact same problem, my computer can see my phone, but nothing is working. anyone have any input??? it seems like i can not write to certain parts of the sd card, it says, FAILED (remote: Write Fail)
trying to run an update. see how the image says it was copied over correctly? ive also tried ereasing it as well..
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
No boot or recovery img
This post specifically helped me.
http://forum.xda-developers.com/showpost.php?p=19531979&postcount=30
just rename the file "install-recovery.sh" which is in the /etc folder. You can only access it with a root file manager (rootexplorer $4 on the market)
make sure your new file is not ending with .sh
It appears that this file keeps writing stock recovery to your phone. Once you erase it, flash CWM recovery and then flash your rom. Hope it helps.
Nice catch. Didn't even think about it getting rewritten every boot.
Sent from my Nexus S using xda premium
ISSUE
I can not get into recovery mode.
What is happening is a loop. I get booted into the fastboot mode and when i click on recovery, the screen goes black and then right back to fastboot mode.
I read all the related posts, and nothing helped. I downloaded Nexus Root Toolkit v1.6.2 and tried to use it as well but it didn't fix my issue. i took a screen shot of the message from NRT. When i get that message, the phone is just sitting at the fastboot menu.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I also tried one click stock, same issue.
Nexus S
Att
Andriod 2.3.4
baseband version: I9020AUCKE1
KernalVersion: 2.6.35.7-ge382d80 [email protected] #1
build number: gtj61
I kind of think i may have done something when i was trying to unlock this phone a few months ago. Any help is much appreciated. I just want to reset my phone to factory settings.
zach18 said:
ISSUE
I can not get into recovery mode.
What is happening is a loop. I get booted into the fastboot mode and when i click on recovery, the screen goes black and then right back to fastboot mode.
I read all the related posts, and nothing helped. I downloaded Nexus Root Toolkit v1.6.2 and tried to use it as well but it didn't fix my issue. i took a screen shot of the message from NRT. When i get that message, the phone is just sitting at the fastboot menu.
View attachment 1637759
I also tried one click stock, same issue.
Nexus S
Att
Andriod 2.3.4
baseband version: I9020AUCKE1
KernalVersion: 2.6.35.7-ge382d80 [email protected] #1
build number: gtj61
I kind of think i may have done something when i was trying to unlock this phone a few months ago. Any help is much appreciated. I just want to reset my phone to factory settings.
Click to expand...
Click to collapse
First off, download the attached zip.Extract the zip to your desktop. Open up command prompt and navigate to the folder where you extracted the files. Now connect your phone to your computer and boot into fastboot. In command prompt, type in
fastboot devices
Click to expand...
Click to collapse
It should list your phone.
Then type in
fastboot flash recovery recovery.img
Click to expand...
Click to collapse
Now you can boot to recovery on your phone. Download a ROM you like and flash it from the recovery. Make sure to wipe data/cache before flashing the ROM though.
Lemme know if it works.
try another computer to install recovery back or just rom manager by wi-fi.
Talal916 said:
First off, download the attached zip.Extract the zip to your desktop. Open up command prompt and navigate to the folder where you extracted the files. Now connect your phone to your computer and boot into fastboot. In command prompt, type in
It should list your phone.
Then type in
Now you can boot to recovery on your phone. Download a ROM you like and flash it from the recovery. Make sure to wipe data/cache before flashing the ROM though.
Lemme know if it works.
Click to expand...
Click to collapse
Quick question, do i need to do anything special to get into fastboot? other than power button + volume up? The first line on the screen says FASTBOOT MODE. Nothing happens when i type in that command. it goes to the next line but nothing shows up.
any idea why my computer can't see the phone in that line? i probably missing a step.
zach18 said:
Quick question, do i need to do anything special to get into fastboot? other than power button + volume up? The first line on the screen says FASTBOOT MODE. Nothing happens when i type in that command. it goes to the next line but nothing shows up.
any idea why my computer can't see the phone in that line? i probably missing a step.
Click to expand...
Click to collapse
So being curious and trying to further troubleshoot, I followed this wiki to make sure everything was setup correctly.
Howto: Install the Android SDK (Google that, i can't post links yet)
When I typed
adb devices
Click to expand...
Click to collapse
and my device showed up.
But I am still not seeing it when I boot into FASTBOOT MODE, and type
fastboot devices
Click to expand...
Click to collapse
mypat said:
try another computer to install recovery back or just rom manager by wi-fi.
Click to expand...
Click to collapse
How do i install recovery back? where would i find that img?
zach18 said:
How do i install recovery back? where would i find that img?
Click to expand...
Click to collapse
Instal twrp.apk on your rooted phone. Connect to internet and twrp will download the IMG recovery for your phone. Reboot to boatloader and select recovery.
Sent from my HTC Sensation XL with Beats Audio X315e using Tapatalk 2
Is your phone unlocked?
ej8989 said:
Is your phone unlocked?
Click to expand...
Click to collapse
So I finally figured it out. I do apologize for how vague and un informative the question was. It was a case of me needing to dig a little more.
Here is what i did.
I had installed a Rom Manager, CyonGenMod when i rooted the phone. They had a recovery img in the app which i used. I think googled around for cyogenmod 10 and ICS 4.0.4. Then i realized i had to find google apps, so i could add my contacts from gmail. Then it was just messing around with bootloader to get the right setup.
I do appreciate the help, y'all put me on the right path. Made me find answers to the right questions. Again I apologize for not doing more due diligence.
Thanks for the help
Hi,
I have unlocked the bootloader and rooted my moto g and installed a custom ROM. As the custom ROM had few bugs, i did a restore of my Stock ROM in TWRP.
Now when i see the TWRP to install another custom ROM, it shows the internal Storage is 0 mb . However when the phone is connected to the computer , i can view all the files there, just in recovery it shows 0 mb.
Any Idea guys?
i am using TWRP v2.6.3.3
Try the latest build '2.8.0.1':
http://techerrata.com/browse/twrp2/xt1032
flashed still no luck... and i am not able to wipe the data as well, it says unable to mount
Odd case. It could be partition corruption. Maybe try Phil's Touch.
Alternatively, you could backup contents of 'internet storage' and fastboot fastboot the latest firmware image for your phone. That would fix any partition issues. Tutorial: http://forum.xda-developers.com/showthread.php?t=2542219
What model do you have?
i have XT1033 dual SIM version.. when i searched the firmware for umtsds i have only 4.3 available for Asia.. (Android 4.3
Blur_Version.14.85.4.falcon_umtsds.AsiaRetail.en.03) however i am right now running 4.4.4... i have one for 4.4.2 which is of Brazil.. any suggestion which one to flash.
I bought this phone in India so i am looking for Asian firmware...
http://forum.xda-developers.com/showpost.php?p=54487261&postcount=332
flashed.. i ll try flashing TWRP again..
thank you guys..it worked..
ghost9685 said:
thank you guys..it worked..
Click to expand...
Click to collapse
I have the same problem. please tell me which solution worked @ghost9685
ghost9685 said:
flashed still no luck... and i am not able to wipe the data as well, it says unable to mount
Click to expand...
Click to collapse
hey @lost101 I am having the same problem. I tried doing the guide which you have linked but the first two commands come back as failed and then after all other commands have been executed the phone reboots to the android dummy screen which keeps blinking. Please help me out
Saadjamil36 said:
hey @lost101 I am having the same problem. I tried doing the guide which you have linked but the first two commands come back as failed and then after all other commands have been executed the phone reboots to the android dummy screen which keeps blinking. Please help me out
Click to expand...
Click to collapse
Fastboot flash the latest factory firmware image for your phone. Do all fastboot commands mentioned in tutorial
Factory Firmware Images: http://forum.xda-developers.com/moto-g/general/index-moto-g-falcon-factory-firmware-t3110795
Fastboot Tutorial: http://forum.xda-developers.com/showthread.php?t=2542219
lost101 said:
Fastboot flash the latest factory firmware image for your phone. Do all fastboot commands mentioned in tutorial
Factory Firmware Images: http://forum.xda-developers.com/moto-g/general/index-moto-g-falcon-factory-firmware-t3110795
Fastboot Tutorial: http://forum.xda-developers.com/showthread.php?t=2542219
Click to expand...
Click to collapse
Didn't work. All commands were OKAY but phone rebooted to android dummy lying on its back and screen keeps turnin pn and off on itself
Saadjamil36 said:
Didn't work. All commands were OKAY but phone rebooted to android dummy lying on its back and screen keeps turnin pn and off on itself
Click to expand...
Click to collapse
Then everything did not obviously go 'OKAY.' It would help to see a log of the flashing process. Copy and paste command prompt screen. Take screenshots if necessary.
lost101 said:
Then everything did not obviously go 'OKAY.' It would help to see a log of the flashing process. Copy and paste command prompt screen. Take screenshots if necessary.
Click to expand...
Click to collapse
Maybe there is something I am doing incorrectly. These are the screenshots of the command prompt
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Saadjamil36 said:
Maybe there is something I am doing incorrectly. These are the screenshots of the command prompt
Click to expand...
Click to collapse
Unlock Bootloader (if not already done) and flash twrp - mfastboot flash recovery twrp.img
Alternatively you can boot into twrp without flashing: mfastboot boot twrp.img
Download twrp: http://forum.xda-developers.com/moto-g/development/recovery-twrp-2-8-2-0-touch-recovery-t2980621
Then via PC, do the following wipe: (requires working ADB setup - google it)
http://forum.xda-developers.com/showpost.php?p=65431978&postcount=22
lost101 said:
Unlock Bootloader (if not already done) and flash twrp - mfastboot flash recovery twrp.img
Alternatively you can boot into twrp without flashing: mfastboot boot twrp.img
Download twrp: http://forum.xda-developers.com/moto-g/development/recovery-twrp-2-8-2-0-touch-recovery-t2980621
Then via PC, do the following wipe: (requires working ADB setup - google it)
http://forum.xda-developers.com/showpost.php?p=65431978&postcount=22
Click to expand...
Click to collapse
How do i type this command in Twrp? adb shell dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/misc
thanks a lot for the help
Saadjamil36 said:
How do i type this command in Twrp? adb shell dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/misc
thanks a lot for the help
Click to expand...
Click to collapse
http://lifehacker.com/the-easiest-way-to-install-androids-adb-and-fastboot-to-1586992378
Thank You. It worked
Saadjamil36 said:
I have the same problem. please tell me which solution worked @ghost9685
Click to expand...
Click to collapse
you will have to restore the stock firmware where it re writes the recovery partition and then flash any custom recovery.. thats wat worked
Is anyone having an issue where the sd card is unmountable, shows 0mb and no gapps zip while in recovery... and then also has an eternal black screen when trying to run without recovery?
Note: Your warranty is now void. I am no way liable for any issues with this. I have ran it on my phone with no issues. YOU HAVE BEEN WARNED. The .bat file is included for convince and I have not tested it and I am on Linux. Please respond if you test this and it works or does not work.
Usage: To remove the bootloader unlock warning on the Droid Turbo XT1254. You must have the USB drivers and the android sdk installed properly.
-Moto drivers: https://motorola-global-portal.custhelp.com/app/answers/detail/a_id/88481
-How to install Android SDK: http://www.androidcentral.com/installing-android-sdk-windows-mac-and-linux-tutorial
Command:
adb reboot bootloader
fastboot flash logo logofixed.bin
fastboot reboot
Or..
Windows: Run the .bat file
Linux: run the .sh file as SU
Let me know if you find any issues. I am not a developer...more of a script kiddie as jcase would say.
Change 1.1
added linux .sh script.
Thanks bro
Sent from my Nexus 5X using Tapatalk
Is this the same as this?
http://forum.xda-developers.com/moto-maxx/themes-apps/moto-maxx-remove-unlocked-bootloader-t2981608
McDastardly said:
Is this the same as this?
http://forum.xda-developers.com/moto-maxx/themes-apps/moto-maxx-remove-unlocked-bootloader-t2981608
Click to expand...
Click to collapse
Same principle but I tried to flash that and it didn't work (everything was distorted and jacked up). So I made this.... This does the same thing but for the turbo.
phatwcinfrcr said:
Note: Your warranty is now void. I am no way liable for any issues with this. I have ran it on my phone with no issues. YOU HAVE BEEN WARNED. The .bat file is included for convince and I have not tested it and I am on Linux. Please respond if you test this and it works or does not work.
Usage: To remove the bootloader unlock warning on the Droid Turbo XT1254.
Command:
adb reboot bootloader
fastboot flash logo logofixed.bin
fastboot reboot
or just run the .bat file
Let me know if you find any issues. I am not a developer...more of a script kiddie as jcase would say.
Click to expand...
Click to collapse
after i reboot into bootloader and type the fastboot cammand, ADB hangs on waiting for device...same with the batch file, device reboots but hangs in bootloader??? any ideas???
patdroid1 said:
after i reboot into bootloader and type the fastboot cammand, ADB hangs on waiting for device...same with the batch file, device reboots but hangs in bootloader??? any ideas???
Click to expand...
Click to collapse
type adb devices
You should get a list with your device. If not you probably don't have the motorola drivers installed. If you are on linux you must run it as SU. Example: sudo fastboot flash logo logo.bin
********EDIT*******
ok fixed it, disabled USB debugging and got the Verizon installer to pop up and installed the drivers that came with phone....FIXED working perfect now THX
phatwcinfrcr said:
type adb devices
You should get a list with your device. If not you probably don't have the motorola drivers installed. If you are on linux you must run it as SU. Example: sudo fastboot flash logo logo.bin
Click to expand...
Click to collapse
yeah my device shows up and responds to the command to reboot bootloader but just hangs in bootloader...same for the .bat file...it responds and reboots but hangs in bootloader
patdroid1 said:
********EDIT*******
ok fixed it, disabled USB debugging and got the Verizon installer to pop up and installed the drivers that came with phone....FIXED working perfect now THX
yeah my device shows up and responds to the command to reboot bootloader but just hangs in bootloader...same for the .bat file...it responds and reboots but hangs in bootloader
Click to expand...
Click to collapse
What do you mean by hangs in the bootloader? Like the bootloader never comes up, or is frozen? When the bootloader comes up it should say "Device is UNLOCKED. Status code 3" and "Transfer Mode: USB Connected".
Also while in fastboot type "fastboot devices" and you should see your device. If you can see it, this will work. If not, there is a driver issue.
phatwcinfrcr said:
Same principle but I tried to flash that and it didn't work (everything was distorted and jacked up). So I made this.... This does the same thing but for the turbo.
Click to expand...
Click to collapse
Worked for me fine. Don't try to flash it in TWRP. You just need to ADB > fastboot flash logo <name of file>.bin after you first unzip the file to access the .bin file.
People screwed up on that thread because they tried to flash the zip file instead of the .bin file in ADB and got similar issues with distortion.
GeoFX said:
Worked for me fine. Don't try to flash it in TWRP. You just need to ADB > fastboot flash logo <name of file>.bin after you first unzip the file to access the .bin file.
People screwed up on that thread because they tried to flash the zip file instead of the .bin file in ADB and got similar issues with distortion.
Click to expand...
Click to collapse
I flashed it with fastboot as well and got distortion. When I have time I will look at that file with a hex editor and see if there is a difference.
don't have access to a computer for a while, any chance it can be made into a flashable zip?
phatwcinfrcr said:
Same principle but I tried to flash that and it didn't work (everything was distorted and jacked up). So I made this.... This does the same thing but for the turbo.
Click to expand...
Click to collapse
It works for the Droid Turbo too. It works on ALL Quarks. You did something wrong. You don't flash it in TWRP, you flash it in ADB.
And there are TWO Quarks Moto sells called Turbo -- Moto Turbo which I have and the Droid Turbo. They are both Quarks and everything is the same except for radio. What works on one will work on all.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
---------- Post added at 05:51 AM ---------- Previous post was at 05:51 AM ----------
McDastardly said:
Is this the same as this?
http://forum.xda-developers.com/moto-maxx/themes-apps/moto-maxx-remove-unlocked-bootloader-t2981608
Click to expand...
Click to collapse
Yes. It does the same thing.
Worked great after my unlock. Thanks for helping hide that annoying warning msg.
(I performed the Win .bat method without issue)
How do I get this thing installed? Ive got moto drivers and have SDK manger installed I just cant figure out how to get this to work. any help would be appreciated
mdcowby said:
How do I get this thing installed? Ive got moto drivers and have SDK manger installed I just cant figure out how to get this to work. any help would be appreciated
Click to expand...
Click to collapse
This has a twrp flashable bootloader warning image on the first post.
http://forum.xda-developers.com/showthread.php?p=64053878
Thanks mate, windows batch file did not work at all but manually did it like a charm.
Thank you for this. I really didn't like advertising to the world, that my device is unlocked at every boot.
Sent from my DROID Turbo via Tapatalk. Now with CM goodness.
Thanks, worked great and took a whole 5 seconds.
Put the extracted files in the minimal adb folder (program files) put phone in bootloader and hit the .bat file and it will be almost instantaneous.
phatwcinfrcr said:
Same principle but I tried to flash that and it didn't work (everything was distorted and jacked up). So I made this.... This does the same thing but for the turbo.
Click to expand...
Click to collapse
Then you installed it wrong. Works fine.
thanx bro
https://dl.twrp.me/cheryl
Razer Phone Install Instructions
Read these instructions and follow them carefully. Failure to do so may result in not being able to update the device in the future and there are no factory images available.
The Razer Phone uses the newer AB partition scheme first introduced on the Pixel 1. As such there is no recovery partition. Instead, the recovery is part of the boot image. Unlike the Pixel devices, Razer has disabled fastboot boot so there is no way to temporarily boot TWRP to perform an installation.
Getting into fastboot mode or recovery on the Razer Phone requires plugging the device into a USB cable. I would recommend against flashing or performing recovery-related actions unless you have access to a USB cable and port so that you can get back into recovery should something go wrong. Power off the device. Hold volume up to get into recovery or volume down to get into fastboot mode. Plug the device in while holding the appropriate button and the device should boot to the mode you selected. If it boots up to the charging screen, try a different USB cable or port. Make sure you are able to boot the device to fastboot via USB cable before flashing anything.
We are going to use the other boot slot to flash the initial copy of TWRP and boot TWRP. To do this you will need to turn on developer options and enable USB debugging. You will also need to enable OEM unlocking and unlock the bootloader. I am not going to discuss how to get the proper drivers installed or assist you with doing these basic steps. There's tons of guides elsewhere for these items if you need it. I will say that unlocking the bootloader requires using fastboot flashing unlock instead of fastboot oem unlock. Once you have adb working, run this command:
adb shell getprop ro.boot.slot_suffix
It should say:
[ro.boot.slot_suffix]: [_a]
Or:
[ro.boot.slot_suffix]: [_b]
Make note of whether you are currently using slot A or B. Next power off the device and boot to the bootloader using your USB cable and volume down. You want to switch to the other boot slot. If you are currently on slot A, type this:
fastboot --set-active=_b
Or on slot B type this:
fastboot --set-active=_a
You should see something like this:
Setting current slot to 'a'...
OKAY [ 0.042s]
finished. total time: 0.042s
I found the bootloader on the Razer Phone to be extremely finicky and I had to run the command multiple times until I got it to run successfully. You may have to hold the power button for 15 seconds to force power off the device and then re-enter fastboot mode. Keep trying until it works. Once it's on the right boot slot, type this:
fastboot flash boot twrp-3.2.1-0-cheryl.img && fastboot reboot
Your device should now boot into TWRP. From here, decrypt your device if needed at the password prompt. DO NOT swipe to allow modifications until after you make your initial backup; instead tap on the read-only button. Go to the reboot page and tap on the button at the bottom to switch back to the slot you were originally using. Go to the backup page in TWRP and back up Boot and System Image. It is HIGHLY recommended that you save this backup in a safe spot on your computer because you may need to restore it to take official OTA updates from Razer. Once you have finished making your backup, run this command:
adb push twrp-installer-3.2.1-0-cheryl.zip /sdcard
In TWRP, tap on Install and browse to the zip and install it. TWRP will now be installed to both slots. TWRP is now installed and you can reboot and use your device as normal, though with TWRP installed, you won't be able to take OTA updates without restoring the stock boot image.
MTP is disabled because it causes a kernel panic sometimes with the stock kernel. ADB also does not work with the stock kernel which makes transferring files between your PC and the device when using the stock kernel a bit of a challenge. The TWRP bootable image does have working ADB though and you can copy files to a SD card or USB stick if needed.
Reserved!
Thanks you so much @Dees_Troy
Let development begin
Awesome work! :highfive:
Awesome! Now we just need to let the dev fun begin! BTW You Rox!
Edit: Im trying to do a full backup of the current state of my phone. went into TWRP and selected every partition and hit backup. Was flying along till it got to Data and it just stopped. No movement @ 40% for about 5 minutes so far Is it working for anyone else? does it just take insanely long with no percentage increase, or am I just being paranoid cause its my new phone lol
Edit 2: I just cancelled it and backed up everything but Data and it went fine, I'm now attempting to backup JUST Data.. Ill have to restore 2 backups seperately, but it appears to be working
Final Edit: All good.. not sure what happened the first backup but doing them seperately worked. Rooted with Magisk 15.1 and running beautifully! Gonna try out some root stuff like Xposed.. Thanks for all your hard work devs & testers!
@Dees_Troy Thanks for your work. Broken link https://github.com/TeamWin/android_device_razer_cheryl
Please update when you have time
Another thing in your instruction consider that on european razer phone the right command is this (I've found problem only for slot b in slot a work without -i 0x1532)
ffastboot -i 0x1532 flashing unlock
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
i get the no devices/ emulators found
EDIT: I didn't realize you had to do that part with the phone on. so when I boot in to bootloader i have slot b and type the command to switch to a. all I see is waiting for devices. thats when I redo it until it writes correct?
RicardoSal24 said:
i get the no devices/ emulators found
EDIT: I didn't realize you had to do that part with the phone on. so when I boot in to bootloader i have slot b and type the command to switch to a. all I see is waiting for devices. thats when I redo it until it writes correct?
Click to expand...
Click to collapse
I've Uses this command to open bootloader?
fastboot -i 0x1532 flashing unlock
If yes command for your device work add -i 0x1532
raimondomartire said:
I've Uses this command to open bootloader?
fastboot -i 0x1532 flashing unlock
If yes command for your device word add -i 0x1532
Click to expand...
Click to collapse
I would still get the message saying <waiting for any device>
RicardoSal24 said:
I would still get the message saying <waiting for any device>
Click to expand...
Click to collapse
Verify your driver in setting. You must add google driver
raimondomartire said:
Verify your driver in setting. You must add google driver
Click to expand...
Click to collapse
link please
RicardoSal24 said:
link please
Click to expand...
Click to collapse
https://developer.android.com/studio/run/win-usb.html
not able to update the driver manually
---------- Post added at 12:49 PM ---------- Previous post was at 12:20 PM ----------
apparently there's no "compatible" driver software for a x64 bit system
RicardoSal24 said:
not able to update the driver manually
---------- Post added at 12:49 PM ---------- Previous post was at 12:20 PM ----------
apparently there's no "compatible" driver software for a x64 bit system
Click to expand...
Click to collapse
Use this
http://www14.zippyshare.com/v/ufYG71o0/file.html
I remember seeing something about no Wi-Fi in the other thread from the chat about source code. Is that still an issue? I ask because I completed this and have no Wi-Fi. Just double checking I didn't miss something
raimondomartire said:
Use this
http://www14.zippyshare.com/v/ufYG71o0/file.html
Click to expand...
Click to collapse
My problem is getting the drivers to work. I've tried Robin. That succeeded. But updating drivers in Device Manager doesn't work. It says there are no compatible drivers for the phone. And if I can't update drivers I can't get the phone to be recognized in Device Manager so adb can work
edit
DarkestSpawn said:
I remember seeing something about no Wi-Fi in the other thread from the chat about source code. Is that still an issue? I ask because I completed this and have no Wi-Fi. Just double checking I didn't miss something
Click to expand...
Click to collapse
Try switching slots in Twrp then restart.
I have a bit of an issue. TWRP has been flashed to both A and B because it didn't reboot to TWRP the first time so i did it again and now i can't boot into system. Stupid mistake i know but what can i do about it?
Xshooter726 said:
Try switching slots in Twrp then restart.
Click to expand...
Click to collapse
No problem also for me. I can share my slot b image
---------- Post added at 02:59 PM ---------- Previous post was at 02:44 PM ----------
Firebuster said:
I have a bit of an issue. TWRP has been flashed to both A and B because it didn't reboot to TWRP the first time so i did it again and now i can't boot into system. Stupid mistake i know but what can i do about it?
Click to expand...
Click to collapse
Try to boot in bootloader mode from twrp and after write fastboot reboot