I have moto x dev ed, I just unlock the bootloader. i tried to install this custom recovery i keep getting this.
<bootloader> variable not supported!
target reported max download size of 805306368 bytes
etc etc...
im trying to download the twrp custom recovery
i dont why it keeps doing that
I know when fastboot flashing the system.img you must use mfastboot due to the partition size, but the recovery.img should flash with fastboot. Maybe give mfastboot a try?
Groid said:
I know when fastboot flashing the system.img you must use mfastboot due to the partition size, but the recovery.img should flash with fastboot. Maybe give mfastboot a try?
Click to expand...
Click to collapse
It worked But when I try to load it , now When I tried to load twrp it shows the dead android logo
Fastboot the recovery.img then type fastboot reboot and choose recovery in fastboot menu
dat010man said:
It worked But when I try to load it , now When I tried to load twrp it shows the dead android logo
Click to expand...
Click to collapse
Sounds like it did not flash correctly because the laying down android leads to the stock recovery. I would try redownloading twrp for ghost again and make sure that is in the folder with fastboot and verify your getting the file name correct when flashing. Just repeating the steps all the through may be successful, we all miss a step occasionally. Good luck [emoji106]
Edit: p.s. I did read somewhere that some people had issue with recovery not sticking after flashing. They got around this by typing the command fastboot reboot bootloader right after flashing the recovery. After that custom recovery would stick.
I'm still getting the same error. Am I suppose to hold the volume up button until the recovery loads?
If you are boot loader unlocked and rooted just use flashify to flash the image file.
---------- Post added at 03:37 AM ---------- Previous post was at 03:32 AM ----------
After you flash your recovery are you booting straight to recovery with the volume up button?
Travisdroidx2 said:
If you are boot loader unlocked and rooted just use flashify to flash the image file.
---------- Post added at 03:37 AM ---------- Previous post was at 03:32 AM ----------
After you flash your recovery are you booting straight to recovery with the volume up button?
Click to expand...
Click to collapse
Yes I am booting to recovery with the volume up button, immediately after I flash it. Alright I will use flashily when I get home after working. Wait no I am not rooted.. I just unlock the boot loader only. I thought you download twrp first and then download supersu to root?
dat010man said:
Yes I am booting to recovery with the volume up button, immediately after I flash it. Alright I will use flashily when I get home after working. Wait no I am not rooted.. I just unlock the boot loader only. I thought you download twrp first and then download supersu to root?
Click to expand...
Click to collapse
Are you opening the command prompt from the same folder as you twrp.img file and your fastboot.exe file?
Travisdroidx2 said:
Are you opening the command prompt from the same folder as you twrp.img file and your fastboot.exe file?
Click to expand...
Click to collapse
Yes they all are in the same folder. I actually had to rename it recovery.img for it to flash
dat010man said:
Yes they all are in the same folder. I actually had to rename it recovery.img for it to flash
Click to expand...
Click to collapse
Shouldn't have to rename it but sounds like you got it working. Great.
Travisdroidx2 said:
Shouldn't have to rename it but sounds like you got it working. Great.
Click to expand...
Click to collapse
Well the thing is if I don't rename it to "Recovery.img" it will not flash but when I get home I will try using flashify. If that doesn't work, I'd be willing to send anyone $20 through PayPal if they can install twrp with supersu on my phone from teamviewer or another Remote Desktop application
dat010man said:
Well the thing is if I don't rename it to "Recovery.img" it will not flash but when I get home I will try using flashify. If that doesn't work, I'd be willing to send anyone $20 through PayPal if they can install twrp with supersu on my phone from teamviewer or another Remote Desktop application
Click to expand...
Click to collapse
I thought you said when you renamed it that it worked? So still no?
Travisdroidx2 said:
I thought you said when you renamed it that it worked? So still no?
Click to expand...
Click to collapse
I have no problem Downloading the recovery to the phone, the only issue is trying to load it after I flash it
dat010man said:
I have no problem Downloading the recovery to the phone, the only issue is trying to load it after I flash it
Click to expand...
Click to collapse
Put the twrp.img file in your SDK folder with your fastboot.exe files. Not on your device.
Is USB debugging turned on?
If so in download mode when you type fastboot devices do you see your device?
If so you just shift right click and open command prompt from that folder you have the files in on your PC.
Then fastboot flash recovery "name of file". IMG
After that volume down to recovery and then volume up to enter twrp.
Just to be clear, you are using the command:
fastboot flash recovery twrp-2.8.4.0-ghost.img (assuming twrp-2.8.4.0.img is the recovery file) and you have copied 'SuperSU-v2.46.zip' into the root of internal memory (called sdcard). After flashing the recovery, you should definitely not boot directly to the system. You should issue the command fastboot reboot-bootloader. Then, choose recovery from the menu and up arrow to start it. I can't remember the exact order of things, but somewhere along the way twrp will prompt you about the supersu and near the end it will ask about making changes so the stock recovery isn't applied back over twrp. Let it make the changes. When you do boot into the system you should have root.
Related
Moto X Developer Edition. Got it unlocked. Flashed TWRP. Press down button to Recovery, press the up volume, phone reboots into Android. It will not reboot to recovery. Below are all the files I have: Any ideas?
ADB
ADBKEY
ADBKEY.PUB
ADBWINAPI.DLL
ADBWINUSBAPI.DLL
FASTBOOT
MFASTBOOT
MOTOROLADEVICEMANAGER_2.4.5
TWRP-2.6.3.1-GHOST-4.4
cw18306 said:
Moto X Developer Edition. Got it unlocked. Flashed TWRP. Press down button to Recovery, press the up volume, phone reboots into Android. It will not reboot to recovery. Below are all the files I have: Any ideas?
ADB
ADBKEY
ADBKEY.PUB
ADBWINAPI.DLL
ADBWINUSBAPI.DLL
FASTBOOT
MFASTBOOT
MOTOROLADEVICEMANAGER_2.4.5
TWRP-2.6.3.1-GHOST-4.4
Click to expand...
Click to collapse
flash again
after u flash the recovery u DON T MUST GO INTO ANDROID OR TO REBOOT UR PHONE
stay in fastboot
go down with the volume down key
when u got recovery highlighted go up with the volume key
and it will boot into twrp recovery
i have ur same problem and solved in this way
danger2u said:
flash again
after u flash the recovery u DON T MUST GO INTO ANDROID OR TO REBOOT UR PHONE
stay in fastboot
go down with the volume down key
when u got recovery highlighted go up with the volume key
and it will boot into twrp recovery
i have ur same problem and solved in this way
Click to expand...
Click to collapse
1) adb reboot bootloader
2) fastboot flash recovery twrp-2.6.3.1-ghost-4.4.img
3) pressed down button, highlighted Recovery, pressed up button.
Phone reboots to Android. Am I missing something?
cw18306 said:
1) adb reboot bootloader
2) fastboot flash recovery twrp-2.6.3.1-ghost-4.4.img
3) pressed down button, highlighted Recovery, pressed up button.
Phone reboots to Android. Am I missing something?
Click to expand...
Click to collapse
If flashing recovery is unsuccessful you're best bet is to flash the sbf firmware with rsdlite , this has happened to to more than a few including me
Sent on my Moto X
flashallthetime said:
If flashing recovery is unsuccessful you're best bet is to flash the sbf firmware with rsdlite , this has happened to to more than a few including me
Sent on my Moto X
Click to expand...
Click to collapse
This is what I am seeing on the screen:
Fastboot reason: Reboot to bootloader
Downloading 10090496 bytes
Done
Flashing Recovery
Done
Everything looks correct. This is a DE phone. Does that require flashing the SBF with RSDlite?
cw18306 said:
This is what I am seeing on the screen:
Fastboot reason: Reboot to bootloader
Downloading 10090496 bytes
Done
Flashing Recovery
Done
Everything looks correct. This is a DE phone. Does that require flashing the SBF with RSDlite?
Click to expand...
Click to collapse
look alot of people are having this issue it is a simple fix follow the directions step by step
Code:
mfastboot flash recovery twrp-2.6.3.1-ghost-4.4.img
as soon as you type the above command to flash TWRP we need to boot the phone into recovery before we let it boot to android we can do that via the command below.
Code:
adb reboot recovery
MAKE SURE THAT AFTER YOU TYPE THE FIRST COMMAND DO NOT LET THE PHONE BOOT TO ANDROID.
right after you hit enter for the mfastboot command type the reboot command it will boot into recovery. if not i would redownload the correct TWRP recovery for 4.4
there is a link here
http://forum.xda-developers.com/showthread.php?t=2603358
cw18306 said:
This is what I am seeing on the screen:
Fastboot reason: Reboot to bootloader
Downloading 10090496 bytes
Done
Flashing Recovery
Done
Everything looks correct. This is a DE phone. Does that require flashing the SBF with RSDlite?
Click to expand...
Click to collapse
If recovery flashes but is not available, your best bet is to flash the sbf firmware and flash recovery, its worked for numerous folks including me
Sent on my Moto X
cw18306 said:
1) adb reboot bootloader
2) fastboot flash recovery twrp-2.6.3.1-ghost-4.4.img
3) pressed down button, highlighted Recovery, pressed up button.
Phone reboots to Android. Am I missing something?
Click to expand...
Click to collapse
Step 2 should be done with Mfastboot, not fastboot.
Repeat all three steps with mfastboot and you should be good.
xawen said:
Step 2 should be done with Mfastboot, not fastboot.
Repeat all three steps with mfastboot and you should be good.
Click to expand...
Click to collapse
Tried returning to stock 4.2 from 4.4 with MOTDROIDULTRADEV_verizon-user-4.2.2-SU1-15-3-release-keys-cid2-Verizon-US.xml\CFC-obake-maxx_verizon-user-4.2.2-SU1-15-3-release-keys-cid2-Verizon-US.xml. I got this from Motorola so I know it's correct.
Flashing FAILED on SYSTEM.IMG. Now I am stuck on the "warning bootloader unlocked" screen. Phone won't boot to Android. Tried using RSD Lite, but it fails on 2/18 Phone Returned FAIL. Tried flashing again through FASTBOOT, failing on "fastboot flash partition gpt.bin" Help! :crying:
cw18306 said:
Tried returning to stock 4.2 from 4.4 with MOTDROIDULTRADEV_verizon-user-4.2.2-SU1-15-3-release-keys-cid2-Verizon-US.xml\CFC-obake-maxx_verizon-user-4.2.2-SU1-15-3-release-keys-cid2-Verizon-US.xml. I got this from Motorola so I know it's correct.
Flashing FAILED on SYSTEM.IMG. Now I am stuck on the "warning bootloader unlocked" screen. Phone won't boot to Android. Tried using RSD Lite, but it fails on 2/18 Phone Returned FAIL. Tried flashing again through FASTBOOT, failing on "fastboot flash partition gpt.bin" Help! :crying:
Click to expand...
Click to collapse
Like I said previously ,flash the kitkat firmware, forget jb. You can not flash back to the pre camera ota, gpt.bin is the bootloader which if is incompatible will fail, saving you from hard bricking your device
Sent on my Moto X
cw18306 said:
Tried returning to stock 4.2 from 4.4 with MOTDROIDULTRADEV_verizon-user-4.2.2-SU1-15-3-release-keys-cid2-Verizon-US.xml\CFC-obake-maxx_verizon-user-4.2.2-SU1-15-3-release-keys-cid2-Verizon-US.xml. I got this from Motorola so I know it's correct.
Flashing FAILED on SYSTEM.IMG. Now I am stuck on the "warning bootloader unlocked" screen. Phone won't boot to Android. Tried using RSD Lite, but it fails on 2/18 Phone Returned FAIL. Tried flashing again through FASTBOOT, failing on "fastboot flash partition gpt.bin" Help! :crying:
Click to expand...
Click to collapse
What errors are the RSD and fastboot actually failing with?
When you're trying to do the fastboot flash, does "fastboot devices" actually show your device as connected?
-----Edit----
Are you sure that is the right version of the firmware? I'm waiting for access to the files from the moto site right now so I can compare the full file name, but I'm pretty sure you have the Maxx Dev Edition firmware file there.
cw18306 said:
Tried returning to stock 4.2 from 4.4 with MOTDROIDULTRADEV_verizon-user-4.2.2-SU1-15-3-release-keys-cid2-Verizon-US.xml\CFC-obake-maxx_verizon-user-4.2.2-SU1-15-3-release-keys-cid2-Verizon-US.xml. I got this from Motorola so I know it's correct.
Flashing FAILED on SYSTEM.IMG. Now I am stuck on the "warning bootloader unlocked" screen. Phone won't boot to Android. Tried using RSD Lite, but it fails on 2/18 Phone Returned FAIL. Tried flashing again through FASTBOOT, failing on "fastboot flash partition gpt.bin" Help! :crying:
Click to expand...
Click to collapse
i have never seen that firmware name before so i would grab the 4.4 firmware from here
http://forum.xda-developers.com/showthread.php?t=2538394
if you want the 4.2.2 camera update get it from here
http://forum.xda-developers.com/showthread.php?t=2568334
and flash it via there steps instead of RSD Lite
Code:
fastboot flash partition gpt.bin
fastboot flash motoboot motoboot.img
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
mfastboot flash system system.img
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot reboot
if you want to wipe your device which i recommend use these.
fastboot erase userdata
fastboot erase cache
hope this helps
i would flash 4.4 sense you bootloader is unlocked then if you want to flash TWRP here is a guide.
Here is the Recovery download
http://goo.im/devs/Hashcode/motox/unlocked/twrp-2.6.3.1-ghost-4.4.img
SuperSU download
http://download.chainfire.eu/supersu
MFastBoot
https://drive.google.com/file/d/0B0dUKGxGylgNTk43eU0xc3VLekE/edit?usp=sharing
1.copy SuperSU over to your phone for flashing after we install TWRP
2. boot phone in bootloader
3. move TWRP.img to your adb folder
4. open a CMD and CD to the directory your ADB and TWRP.img is in
5. type below commands in CMD
Code:
mfastboot flash recovery twrp-2.6.3.1-ghost-4.4.img
fastboot reboot recovery
6. you will now be in recovery so click on Instal
7. locate your SuperSU.zip file and install it
8. Reboot your phone to android and you will now be rooted
@cw18306 just got turnt up
SuperSU.ZIP Move to Phone?
dray_jr said:
i have never seen that firmware name before so i would grab the 4.4 firmware from here
http://forum.xda-developers.com/showthread.php?t=2538394
if you want the 4.2.2 camera update get it from here
http://forum.xda-developers.com/showthread.php?t=2568334
and flash it via there steps instead of RSD Lite
Code:
fastboot flash partition gpt.bin
fastboot flash motoboot motoboot.img
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
mfastboot flash system system.img
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot reboot
if you want to wipe your device which i recommend use these.
fastboot erase userdata
fastboot erase cache
hope this helps
i would flash 4.4 sense you bootloader is unlocked then if you want to flash TWRP here is a guide.
Here is the Recovery download
http://goo.im/devs/Hashcode/motox/unlocked/twrp-2.6.3.1-ghost-4.4.img
SuperSU download
http://download.chainfire.eu/supersu
MFastBoot
https://drive.google.com/file/d/0B0dUKGxGylgNTk43eU0xc3VLekE/edit?usp=sharing
1.copy SuperSU over to your phone for flashing after we install TWRP
2. boot phone in bootloader
3. move TWRP.img to your adb folder
4. open a CMD and CD to the directory your ADB and TWRP.img is in
5. type below commands in CMD
Code:
mfastboot flash recovery twrp-2.6.3.1-ghost-4.4.img
adb reboot recovery
6. you will now be in recovery so click on Instal
7. locate your SuperSU.zip file and install it
8. Reboot your phone to android and you will now be rooted
Click to expand...
Click to collapse
You are THE MAN! Quick question regarding SuperSU.zip...Do I unzip it in windows and MOVE the 4 folders to the phone, OR do I only need to move the UNZIPPED SuperSU file to the phone? I am about to flash recovery and want to be sure. Thanks so much!!!
Boot into TWRP, open cmd prompt, type "adb push SuperSU.zip /sdcard" then hit enter, select install then SuperSU.zip.
nhizzat said:
Boot into TWRP, open cmd prompt, type "adb push SuperSU.zip /sdcard" then hit enter, select install then SuperSU.zip.
Click to expand...
Click to collapse
Flashed TWRP entering "mfastboot flash recovery twrp-2.6.3.1-ghost-4.4.img" OK. When I enter "adb reboot recovery" I get device not found and nothing happens. This is stopping me from rebooting to Recovery. On the phone, I highlighted RECOVERY, hit the UP button, and it booted to Android.
cw18306 said:
Flashed TWRP entering "mfastboot flash recovery twrp-2.6.3.1-ghost-4.4.img" OK. When I enter "adb reboot recovery" I get device not found and nothing happens. This is stopping me from rebooting to Recovery. On the phone, I highlighted RECOVERY, hit the UP button, and it booted to Android. I rebooted to bootloader again, reflashed TWRP, highlighted Recovery, hit UP, and the screen goes black and does not boot. If I press the power button, the phone will boot to Android. That is where I am now. Something must be up with my Recovery file?
Click to expand...
Click to collapse
@dray_jr
cw18306 said:
@dray_jr
Click to expand...
Click to collapse
OMG!!!!!!! The problem was my utter ignorance of a new device. I spent the last two days trying to boot to recovery using the up/down buttons or so I thought. I had no problems using the DOWN button...it was the UP button (I thought the POWER button was UP!!!) This is why I was not booting to Recovery...my Droid Bionic has two buttons on the side of the phone...its power button is on the top. I am sorry for being a pain everyone and I really appreciate all of your help! I AM ROOTED!!! :highfive::good:
cw18306 said:
OMG!!!!!!! The problem was my utter ignorance of a new device. I spent the last two days trying to boot to recovery using the up/down buttons or so I thought. I had no problems using the DOWN button...it was the UP button (I thought the POWER button was UP!!!) This is why I was not booting to Recovery...my Droid Bionic has two buttons on the side of the phone...its power button is on the top. I am sorry for being a pain everyone and I really appreciate all of your help! I AM ROOTED!!! :highfive::good:
Click to expand...
Click to collapse
no problem glad everything worked out for you enjoy
So, is there a way to flash the update to 5.0.1? I'm unlocked, rooted, and still encrypted. I want to stay encrypted. Sorry, just my own paranoia I guess. But is there a way to do it as an update without wiping the device and having to restore a backup? I have had too many backups fail in the past, and I'm kinda lazy. Plus its been a long time since I played with flashing an Android. since my old EVO 4G. LOL Thanks all. Oh yeah, if it matters, I'm on a T-Mobile Nexus 6.
scothern99 said:
So, is there a way to flash the update to 5.0.1? I'm unlocked, rooted, and still encrypted. I want to stay encrypted. Sorry, just my own paranoia I guess. But is there a way to do it as an update without wiping the device and having to restore a backup? I have had too many backups fail in the past, and I'm kinda lazy. Plus its been a long time since I played with flashing an Android. since my old EVO 4G. LOL Thanks all. Oh yeah, if it matters, I'm on a T-Mobile Nexus 6.
Click to expand...
Click to collapse
The flash-all.bat script doesn't work anyway, so don't use it. Just use fastboot and flash:
fastboot flash bootloader bootloader-shamu-moto-apq8084-71.05.img
fastboot reboot-bootloader
(wait for reboot)
fastboot flash radio radio-shamu-d4.0-9625-02.55.04.img
fastboot reboot-bootloader
(wait for reboot)
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img
Then, I like to boot directly into twrp and flash supersu.zip to reroot (I don't flash twrp on, just boot into it)
fastboot boot openrecovery-twrp-2.8.2.0-shamu.img
---------- Post added at 02:12 PM ---------- Previous post was at 02:02 PM ----------
You can turn that into a simple bat file to use if you like. Just copy and past the following (in between dashes) into notepad and save as something like nexus-flash.bat:
--------------------------
PATH=%PATH%;"%SYSTEMROOT%\System32"
fastboot flash bootloader bootloader-shamu-moto-apq8084-71.05.img
fastboot reboot-bootloader
ping -n 5 127.0.0.1 >nul
fastboot flash radio radio-shamu-d4.0-9625-02.55.04.img
fastboot reboot-bootloader
ping -n 5 127.0.0.1 >nul
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img
fastboot boot openrecovery-twrp-2.8.2.0-shamu.img
echo Press any key to exit...
pause >nul
exit
---------------------------------------
If you have named the twrp recovery something other than what it downloads as, be sure to adjust the file name in the script.
This assumes that all the files are in the same folder including the platform tools. So you would need to extract everything into the same folder.
livinginkaos said:
The flash-all.bat script doesn't work anyway, so don't use it. Just use fastboot and flash:
fastboot flash bootloader bootloader-shamu-moto-apq8084-71.05.img
fastboot reboot-bootloader
(wait for reboot)
fastboot flash radio radio-shamu-d4.0-9625-02.55.04.img
fastboot reboot-bootloader
(wait for reboot)
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img
Then, I like to boot directly into twrp and flash supersu.zip to reroot (I don't flash twrp on, just boot into it)
fastboot boot openrecovery-twrp-2.8.2.0-shamu.img
---------- Post added at 02:12 PM ---------- Previous post was at 02:02 PM ----------
You can turn that into a simple bat file to use if you like. Just copy and past the following (in between dashes) into notepad and save as something like nexus-flash.bat:
--------------------------
PATH=%PATH%;"%SYSTEMROOT%\System32"
fastboot flash bootloader bootloader-shamu-moto-apq8084-71.05.img
fastboot reboot-bootloader
ping -n 5 127.0.0.1 >nul
fastboot flash radio radio-shamu-d4.0-9625-02.55.04.img
fastboot reboot-bootloader
ping -n 5 127.0.0.1 >nul
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img
fastboot boot openrecovery-twrp-2.8.2.0-shamu.img
echo Press any key to exit...
pause >nul
exit
---------------------------------------
If you have named the twrp recovery something other than what it downloads as, be sure to adjust the file name in the script.
This assumes that all the files are in the same folder including the platform tools. So you would need to extract everything into the same folder.
Click to expand...
Click to collapse
Ok, so not to be a noob, where do I get the image files to flash?
Nexus images are all posted here - https://developers.google.com/android/nexus/images
Ok, so I used the toolkit to unlock/root, I'm assuming then that to use this script you posted, I would need to download the actual ADB/Fastboot files separately?
Sorry for the stupid questions, I'm learning all over again, and this is my first Nexus device.
EDIT: So it looks like I can use the toolkit to individually flash the system image and then the radio. Will that work doing it in that order?
scothern99 said:
Ok, so I used the toolkit to unlock/root, I'm assuming then that to use this script you posted, I would need to download the actual ADB/Fastboot files separately?
Sorry for the stupid questions, I'm learning all over again, and this is my first Nexus device.
EDIT: So it looks like I can use the toolkit to individually flash the system image and then the radio. Will that work doing it in that order?
Click to expand...
Click to collapse
Does anyone know if this is correct?
What I did to upgrade without wiping, i was on stock with elementalx kernel, root and twrp.
Only flashed radio and system img.
1. Downloaded images, extracted zip of the images.
2. Reboot to bootloader
3. Fastboot commands
fastboot flash radio radio-shamu-d4.0-9625-02.55.04.img
fastboot reboot-bootloader
fastboot flash system system.img
fastboot reboot
4. Reboot to bootloader again
Run chainfire autoroot script.
5. Done
Remember to read read read if you don't know what are you doing, nobody here is responsible if things go wrong.
With my past phones, there was always a stock rom posted shortly after the update came out. I would just flash that over what I had already to update. Is there some reason why no one has posted any stock roms for the nexus 6?
lion1750 said:
With my past phones, there was always a stock rom posted shortly after the update came out. I would just flash that over what I had already to update. Is there some reason why no one has posted any stock roms for the nexus 6?
Click to expand...
Click to collapse
I'm wondering the same. Usually it was out right away and I would do the same as you. Seems crazy to me that we would have to unroot update and reroot agaain.
Usually I would flash a stock rom with the update that the dev would also throw root into.
livinginkaos said:
Then, I like to boot directly into twrp and flash supersu.zip to reroot (I don't flash twrp on, just boot into it)
fastboot boot openrecovery-twrp-2.8.2.0-shamu.img
Click to expand...
Click to collapse
Can you do this as opposed to using the CF-Auto-Root-shamu-shamu-nexus6.zip to root for the very first time as well?
GMoGoody said:
Can you do this as opposed to using the CF-Auto-Root-shamu-shamu-nexus6.zip to root for the very first time as well?
Click to expand...
Click to collapse
You bet. You can be sure to have the most recent SuperSU that way as well. CF-Auto isn't always updated as quickly.
http://download.chainfire.eu/supersu
livinginkaos said:
You bet. You can be sure to have the most recent SuperSU that way as well. CF-Auto isn't always updated as quickly.
http://download.chainfire.eu/supersu
Click to expand...
Click to collapse
That su 2.4zip is for all devices? Not just for the n7 fhd? Thx
Via my NeXus™ 7FHD on XDA Premium app
Since pepole have no knolege of what they are doing and kind of blame me for it i will not provide the images anymore.
Please lock this thread.
First, woohoo!
Flashing now, thanks bud!
EDIT: Hey Bunny, maybe I'm missing something. Where are those bootloader images available?
@bunny0007 is this pre-rooted, or stock ?
All the bootloader files are in the ota file.
Yes this is stock system partition with root.
bunny0007 said:
All the bootloader files are in the ota file.
Yes this is stock system partition with root.
Click to expand...
Click to collapse
So then this point is moot then?
"...Since the 5.0.2 update contains new bootloader and stuff, you might have to flash those if neccesary...." it happens automatically when you do the single system flash?
---------- Post added at 06:24 PM ---------- Previous post was at 06:18 PM ----------
Is there a mirror link? Dev-Host seems to have been jacked by some crazy redirect malware...or maybe its just me...
Moe5508 said:
So then this point is moot then?
"...Since the 5.0.2 update contains new bootloader and stuff, you might have to flash those if neccesary...." it happens automatically when you do the single system flash?
---------- Post added at 06:24 PM ---------- Previous post was at 06:18 PM ----------
Is there a mirror link? Dev-Host seems to have been jacked by some crazy redirect malware...or maybe its just me...
Click to expand...
Click to collapse
I flashed the ota file before i made the system dump.
Im not sure if the new bootloader an stuff are required for this update, but the ota are not a new rom, just patched files, no new boot image or recovery image.
Am stuck in fastboot mode and can't get into ADB mode anymore to be able to do a sideload...any idea how to flash that OTA zip file in fastboot? Anyone got the boot and recovery images extracted?
Moe5508 said:
Am stuck in fastboot mode and can't get into ADB mode anymore to be able to do a sideload...any idea how to flash that OTA zip file in fastboot? Anyone got the boot and recovery images extracted?
Click to expand...
Click to collapse
The only way to flash the ota file are from stock non rooted 5.0.1 via sideload from recovery.
You might fastboot flash stock 5.0.1 system, boot and recovery, then you shuld be able to flash the ota from recovery.
bunny0007 said:
Here is a stock lollipop 5.0.2 system image that can be flashed in fastboot.
Flash with
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system-rooted.img
Stock 5.0.2 boot partition dump download (sorry for the partiton size): http://www68.zippyshare.com/v/4v4NAT5J/file.html
Stock 5.0.2 recovery partition dump download (sorry for the partiton size): http://www3.zippyshare.com/v/hpeV5W22/file.html
Stock 5.0.2 System rooted: http://d-h.st/IGov
Smaller 5.0.2 boot.img and recovery.img might fe found here http://forum.xda-developers.com/g-watch-r/development/stock-boot-recovery-g-watch-r-t2956964
Since the 5.0.2 update contains new bootloader and stuff, you might have to flash those if nessesary.
Extract the files and use the flash cmd file from windows cmd, or flash the files manually with fastboot.
bootloader.aboot.img
bootloader.imgdata.img
bootloader.rpm.img
bootloader.sbl1.img
bootloader.sdi.img
bootloader.tz.img
Download Bootloader Stuff : http://d-h.st/bDXl
Click to expand...
Click to collapse
Thanks for the bootloader stuff.But in flash.cmd.It should "fastboot flash sbl1 bootloader.sbl1.img"rather than "sb11".you can change it.then everyone can flash the newest sbl1
akaHardison said:
Thanks for the bootloader stuff.But in flash.cmd.It should "fastboot flash sbl1 bootloader.sbl1.img"rather than "sb11".you can change it.then everyone can flash the newest sbl1
Click to expand...
Click to collapse
I just caught that, too. sb11 should read "sbl1" (SBL1) in the commands list when flashing the "bootloader stuff", otherwise you'll get an error that sb11 partition does not exist.
fronc said:
I just caught that, too. sb11 should read "sbl1" (SBL1) in the commands list when flashing the "bootloader stuff", otherwise you'll get an error that sb11 partition does not exist.
Click to expand...
Click to collapse
yep have changed the error in new zip
@bunny0007 can you please post a step by step guide for how to flash this?
I am on rooted 5.0.1 and do not understand the order, or not even which imgs are necessary to flash?
you reboot to bootloader mode, flash boot/system/recovery and also dl his bootloader stuff and flash all of those (he included a .cmd with all the fastboot commands)
bunny0007 said:
Here is a stock lollipop 5.0.2 system image that can be flashed in fastboot.
Flash with
fastboot flash system system-rooted.img
Stock 5.0.2 System rooted: http://d-h.st/IGov
Click to expand...
Click to collapse
When I go to the devHost to download this system, I hit the "download" button and it takes me to spam where it asks me to download a 1-MB file that is called system-rooted.img.zip.exe.
Is the link bad, or am I just being a noob? I'm expecting a 256 MB img file with the stock 5.02 system rooted, not a 1 MB executable file with a deceptive name.
Any assistance appreciated.
Cheers,
B.D.
BostonDan said:
When I go to the devHost to download this system, I hit the "download" button and it takes me to spam where it asks me to download a 1-MB file that is called system-rooted.img.zip.exe.
Is the link bad, or am I just being a noob? I'm expecting a 256 MB img file with the stock 5.02 system rooted, not a 1 MB executable file with a deceptive name.
Any assistance appreciated.
Cheers,
B.D.
Click to expand...
Click to collapse
Just uncheck the "Download with Dev-Host Download Manager" box.
Spleeno said:
you reboot to bootloader mode, flash boot/system/recovery and also dl his bootloader stuff and flash all of those (he included a .cmd with all the fastboot commands)
Click to expand...
Click to collapse
hey, so boot then system and then recovery, followed by the bootloader stuff, in this order, right?
b0gd4n said:
hey, so boot then system and then recovery, followed by the bootloader stuff, in this order, right?
Click to expand...
Click to collapse
Boot into fastboot, then make sure you can use fastboot from windows in cmd shell.
Then use this to flash
1. Unzip and flash bootloader stuff with cmd file.
2. Flash system with "fastboot flash system filename.img"
3. Flash boot with "fastboot flash boot boot.img"
4. Flash Stock 5.0.2 recovery with "fastboot flash recovery recovery.img"
5. Reboot the watch
Is there coming a stock rooted 5.1.1?
TimV_ said:
Is there coming a stock rooted 5.1.1?
Click to expand...
Click to collapse
Yep here http://forum.xda-developers.com/g-watch-r/development/rom-stock-rooted-5-1-1-t3124921
How do you come around to get the watch listed in adb (adb devices command). I installed several drivers for my lg g watch r, tried both in win10 test and non test mode, but the watch is not recognized. DEvice manager lists it as "unknown usb device descriptor request failed".
I appreciate any type of suggestion. Thanks in advance!
Hello,
I recently flashed the latest TWRP beta for the OxygenOS 4.0.1 on my phone which has an unlocked bootloader. I managed to boot into recovery immediately after flashing the .img through my PC, so that's how I was able to install my SuperSU.
However, since I booted into the OS, anytime I'm trying to enter the TRWP recovery again, I'm stuck in the stock recovery which doesn't let me install anything. So the only way for me to boot into TWRP recovery is using my PC. Can anybody help me to fix that?
Thanks!
What command are you using to install TWRP to your bootpartition?
I think the correct one is something like:
Code:
fastboot flash recovery (file name).img
kwoad said:
What command are you using to install TWRP to your bootpartition?
I think the correct one is something like:
Code:
fastboot flash recovery (file name).img
Click to expand...
Click to collapse
Thanks for your reply! Exactly. And after installing it, I used the command 'fastboot boot TWRP.img", and that brought me into TWRP recovery. But I could only get there this way and still had the stock recovery.
Yuniboy said:
Thanks for your reply! Exactly. And after installing it, I used the command 'fastboot boot TWRP.img", and that brought me into TWRP recovery. But I could only get there this way and still had the stock recovery.
Click to expand...
Click to collapse
did you unlock bootloader first
Yuniboy said:
Thanks for your reply! Exactly. And after installing it, I used the command 'fastboot boot TWRP.img", and that brought me into TWRP recovery. But I could only get there this way and still had the stock recovery.
Click to expand...
Click to collapse
From what I understand, the command 'fastboot boot twrp.img' will boot the specified recovery once, but won't flash it to the device. So it has nothing to do with the recovery that is actually on your device. Perhaps something went wrong when you actually flashed twrp and it wasn't written at all.
xabat said:
did you unlock bootloader first
Click to expand...
Click to collapse
Thanks for both your replies. Yes, I did. An indicator is also that every time I boot up my system it even warns me that the bootloader is unlocked.
freepenguin84 said:
From what I understand, the command 'fastboot boot twrp.img' will boot the specified recovery once, but won't flash it to the device. So it has nothing to do with the recovery that is actually on your device. Perhaps something went wrong when you actually flashed twrp and it wasn't written at all.
Click to expand...
Click to collapse
Well, I flashed the twrp by booting into fastboot mode and then typing 'fastboot flash recovery twrp.img'. I don't know what's wrong there, so maybe you could help me out?
Yuniboy said:
Well, I flashed the twrp by booting into fastboot mode and then typing 'fastboot flash recovery twrp.img'. I don't know what's wrong there, so maybe you could help me out?
Click to expand...
Click to collapse
Unfortunately then I don't know how to help Because that's exactly what I did and I got TWRP running without any problem. If you flash via 'fastboot flash recovery' command will it be on the device after you reboot for the first time?
i remember, once i couldn't boot into recovery either when i used fastboot command. Then I flash recovery using tool below and it worked for me.
https://forum.xda-developers.com/oneplus-3t/development/toolkit-oneplus-3t-toolkit-unlock-t3507729
freepenguin84 said:
Unfortunately then I don't know how to help Because that's exactly what I did and I got TWRP running without any problem. If you flash via 'fastboot flash recovery' command will it be on the device after you reboot for the first time?
Click to expand...
Click to collapse
Apparently, you were right. I just wiped my device (accidentaly ) and flashed TWRP again, basically did the same steps as before, but now it works. Seems like somehow the installation of TWRP just failed on the first try. Thanks for your help!
xabat said:
i remember, once i couldn't boot into recovery either when i used fastboot command. Then I flash recovery using tool below and it worked for me.
https://forum.xda-developers.com/oneplus-3t/development/toolkit-oneplus-3t-toolkit-unlock-t3507729
Click to expand...
Click to collapse
Fortunately, it wasn't that bad. So the installation of TWRP failed somehow and I just reinstalled it. Thanks for your help!
kwoad said:
What command are you using to install TWRP to your bootpartition?
I think the correct one is something like:
Code:
fastboot flash recovery (file name).img
Click to expand...
Click to collapse
And For Samsung devices, any method via using ODIN
(Samsung E7/E700H)
freepenguin84 said:
Unfortunately then I don't know how to help Because that's exactly what I did and I got TWRP running without any problem. If you flash via 'fastboot flash recovery' command will it be on the device after you reboot for the first time?
Click to expand...
Click to collapse
Apparently "yes". Source this xda article- https://www.xda-developers.com/how-to-install-twrp/
my phoe is broken i need to flash twrp and i cant to do it ,i setup cyanogenmod recovery by mistake and this recovery is fault because i cant even transfer any files form computer to mobile .. i try to flash with sp tool but it give me error because my phone is broken ,i try also dirtycow v11 on my phone to try flash twrp but it cant read phone on the computer and i setup V21 rom ??
sorry for bad english
any HElp plaese?
meroher said:
any HElp plaese?
Click to expand...
Click to collapse
How you mean broken?
Can it boot to fastboot mode?
YEP IT CAN BOOT TO FASTBOOT ?! then what?
mrmazak said:
how you mean broken?
Can it boot to fastboot mode?
Click to expand...
Click to collapse
plaese man help me my mob is still broken ineed it now
meroher said:
plaese man help me my mob is still broken ineed it now
Click to expand...
Click to collapse
I don't get notified that you answer if you do not quote.
you only answered one of the questions. You did not tell what is "broke"
no help you if you do not know what you need help with.
mrmazak said:
I don't get notified that you answer if you do not quote.
you only answered one of the questions. You did not tell what is "broke"
no help you if you do not know what you need help with.
Click to expand...
Click to collapse
oki iget it
first i had a twrp recovery and i try to install other recovery so
i install this recovery
https://forum.xda-developers.com/r1-hd/development/beta-cyanogenmod-recovery-blu-r1-hd-t3462614
and this recovery cant let me to install any rom or to back to install twrp recovery
and blu cant boot up he freeze on blu white screen
any thing else i will tell you
thanks for you help
meroher said:
oki iget it
first i had a twrp recovery and i try to install other recovery so
i install this recovery
https://forum.xda-developers.com/r1-hd/development/beta-cyanogenmod-recovery-blu-r1-hd-t3462614
and this recovery cant let me to install any rom or to back to install twrp recovery
and blu cant boot up he freeze on blu white screen
any thing else i will tell you
thanks for you help
Click to expand...
Click to collapse
Ok you installed this cm recovery with twrp?
android is not booting. (v21)
the cm recovery does boot but not allow install anything.
And fastboot is loading.
probably need to fastboot flash boot.img , I will share a superSU patched version. (you do not need to root system if not wanted, but patched boot is needed to boot a moddified system)
and fastboot flash twrp.
download this zip.
extract files to your desktop
use these fastboot commands to test first
This one to boot the phone
Code:
fastboot boot %userprofile%\Desktop\su-boot.img
This one to boot twrp
Code:
fastboot boot %userprofile%\Desktop\twrp_p6601_7.1_recovery.img
mrmazak said:
Ok you installed this cm recovery with twrp?
android is not booting. (v21)
the cm recovery does boot but not allow install anything.
And fastboot is loading.
probably need to fastboot flash boot.img , I will share a superSU patched version. (you do not need to root system if not wanted, but patched boot is needed to boot a moddified system)
and fastboot flash twrp.
download this zip.
extract files to your desktop
use these fastboot commands to test first
This one to boot the phone
Code:
fastboot boot %userprofile%\Desktop\su-boot.img
This one to boot twrp
Code:
fastboot boot %userprofile%\Desktop\twrp_p6601_7.1_recovery.img
Click to expand...
Click to collapse
Quote:
FIRST WHEN SEE YOU POST I TRY THIS CODES BEFORE TRYING WITH YOUR CODES
Lets see how quick and easy this really is...
In the command line type:
Code:
fastboot devices
Seeing your serial number means we know all is good
Now lets type these commands:
Code:
fastboot erase system -w
fastboot erase boot
fastboot update superawesomerom.zip
Of course replace <superawesomerom.zip> with the correct file name
and last but not least:
Code:
fastboot reboot
THANKS IT WORKS BUT WHEN I GO TO RECOVERY IT GO TO BOOT directly again AND again
WHATS BROBLEAM !
meroher said:
Quote:
FIRST WHEN SEE YOU POST I TRY THIS CODES BEFORE TRYING WITH YOUR CODES
Lets see how quick and easy this really is...
In the command line type:
Code:
fastboot devices
Seeing your serial number means we know all is good
Now lets type these commands:
Code:
fastboot erase system -w
fastboot erase boot
fastboot update superawesomerom.zip
Of course replace <superawesomerom.zip> with the correct file name
and last but not least:
Code:
fastboot reboot
THANKS IT WORKS BUT WHEN I GO TO RECOVERY IT GO TO BOOT directly again AND again
WHATS BROBLEAM !
Click to expand...
Click to collapse
WOW
WTF
Idon't know who told you to use those commands, but I am not familiar with using
Code:
fastboot erase system -w
fastboot erase boot
fastboot update superawesomerom.zip
so i dont know what to tell you.
why do you say "it worked" but then say it "just boots again AND again"
to me that is not worked, that is mean it made bootloop. so not worked.
mrmazak said:
WOW
WTF
Idon't know who told you to use those commands, but I am not familiar with using
Code:
fastboot erase system -w
fastboot erase boot
fastboot update superawesomerom.zip
so i dont know what to tell you.
why do you say "it worked" but then say it "just boots again AND again"
to me that is not worked, that is mean it made bootloop. so not worked.
Click to expand...
Click to collapse
ok sorry
the mobile now in a bootloop as you say any solution to this issue and iam sorry again >>+
i get codes from here
https://forum.xda-developers.com/showpost.php?p=41374686&postcount=4
this post please stay with me to back up this phone
meroher said:
ok sorry
the mobile now in a bootloop as you say any solution to this issue and iam sorry again >>+
i get codes from here
https://forum.xda-developers.com/showpost.php?p=41374686&postcount=4
this post please stay with me to back up this phone
Click to expand...
Click to collapse
I am not aware of any zip file available to flash the way that guide had you try.
As it stands you wiped boot and system.
I am away from PC so typing is not as easy. I will be more detailed when I return.
Basically I suggest you to "flash" the boot.img I sent.
Then "boot" the recovery.
If the recovery then boots. Install a rom from my modifes stock roms thread.
oki i try install recovery but it same thing it go to white screen and restart again and again
i will wait for you to help me more thanks ><
mrmazak said:
I am not aware of any zip file available to flash the way that guide had you try.
As it stands you wiped boot and system.
I am away from PC so typing is not as easy. I will be more detailed when I return.
Basically I suggest you to "flash" the boot.img I sent.
Then "boot" the recovery.
If the recovery then boots. Install a rom from my modifes stock roms thread.
Click to expand...
Click to collapse
oki i will wait you thanks for your time
meroher said:
oki i will wait you thanks for your time
Click to expand...
Click to collapse
So this is what i suggest
use the files i gave before, unzipped to desktop.
This one to Flash boot.img
Code:
fastboot flash boot %userprofile%\Desktop\su-boot.img
This one to boot twrp.img
Code:
fastboot boot %userprofile%\Desktop\twrp_p6601_7.1_recovery.img
I expect that to give you a working twrp environment. Then go to linked thread and install really any version you want. But as you said you were on V21, so pick that one I supose.
https://forum.xda-developers.com/r1-hd/development/modified-8-3-stock-rom-t3602672
mrmazak said:
So this is what i suggest
use the files i gave before, unzipped to desktop.
This one to Flash boot.img
Code:
fastboot flash boot %userprofile%\Desktop\su-boot.img
This one to boot twrp.img
Code:
fastboot boot %userprofile%\Desktop\twrp_p6601_7.1_recovery.img
I expect that to give you a working twrp environment. Then go to linked thread and install really any version you want. But as you said you were on V21, so pick that one I supose.
https://forum.xda-developers.com/r1-hd/development/modified-8-3-stock-rom-t3602672
Click to expand...
Click to collapse
it works fine finally thanks very much for help :]:]:laugh::laugh: