Hey All.. my nexus 6 is stuck in a boot loop. I tried up dating to 5.0.1 and now it's boot looped. Anyone have any suggestions?
Try wiping cache in recovery.
eddies92 said:
Try wiping cache in recovery.
Click to expand...
Click to collapse
I can get to recovery, how do I wipe the cache?
To get to recovery hold the power button until it shuts off then press volume down and power at the same time to boot into bootloader. Then use the volume buttons to choose recovery mode and press power.
Sent from my Nexus 6
housry23 said:
To get to recovery hold the power button until it shuts off then press volume down and power at the same time to boot into bootloader. Then use the volume buttons to choose recovery mode and press power.
Sent from my Nexus 6
Click to expand...
Click to collapse
Hi! Same problem here. Happened when tried to update to 5.0.1 using this guide:
fastboot flash bootloader bootloader.img
fastboot reboot-bootloader
fastboot flash radio radio.img
fastboot reboot-bootloader
fastboot flash system system.img
fastboot flash userdata userdata.img
fastboot flash boot boot.img (I used a decrypted boot.img for 5.0.1)
fastboot flash recovery recovery.img
fastboot erase cache
Click to expand...
Click to collapse
I didn't get any error during the installation. I only did step 1 and 2, and when rebooted before step 3, I got the boot loop.
Recovery mode doesn't work, it shows a "dead" android with a red exclamation sign. I can still go to bootloader mode.
Can you please help me?
Solved it flashing "cache.img".
Hope it helps anyone.
mattogodoy said:
Solved it flashing "cache.img".
Hope it helps anyone.
Click to expand...
Click to collapse
my situation is the n6 will boot and then attempt to boot twrp but the boot splash screen of twrp loops so i guess the recvery segment is in a boot loop. if i co
low.humidity said:
my situation is the n6 will boot and then attempt to boot twrp but the boot splash screen of twrp loops so i guess the recvery segment is in a boot loop. if i co
Click to expand...
Click to collapse
Follow these steps:
Download Android 5.0.1 for Shamu (Nexus 6) from Google servers.
In the terminal:
fastboot flash bootloader bootloader.img
fastboot reboot-bootloader
fastboot flash radio radio.img
fastboot reboot-bootloader
fastboot flash system system.img
fastboot flash userdata userdata.img
fastboot flash boot boot.img (I used a decrypted boot.img for 5.0.1)
fastboot flash recovery recovery.img
fastboot erase cache
fastboot flash cache cache.img (this one fixed my problem)
Hope that fixes it.
mattogodoy said:
Follow these steps:
Download Android 5.0.1 for Shamu (Nexus 6) from Google servers.
In the terminal:
fastboot flash bootloader bootloader.img
fastboot reboot-bootloader
fastboot flash radio radio.img
fastboot reboot-bootloader
fastboot flash system system.img
fastboot flash userdata userdata.img
fastboot flash boot boot.img (I used a decrypted boot.img for 5.0.1)
fastboot flash recovery recovery.img
fastboot erase cache
fastboot flash cache cache.img (this one fixed my problem)
Hope that fixes it.
Click to expand...
Click to collapse
Why are you rebooting it twice while flashing? I've never rebooted it until it was done and I haven't had any issues. Maybe I'm just used to flashing older Nexus devices.
Pilz said:
Why are you rebooting it twice while flashing? I've never rebooted it until it was done and I haven't had any issues. Maybe I'm just used to flashing older Nexus devices.
Click to expand...
Click to collapse
I asked myself the same haha. For no special reason, I was just following a guide, but I've seen other guides where you don't reboot until the end of the process. It's fast and harmless anyway.
mattogodoy said:
I asked myself the same haha. For no special reason, I was just following a guide, but I've seen other guides where you don't reboot until the end of the process. It's fast and harmless anyway.
Click to expand...
Click to collapse
yeah, thanks for that info, it helped. i keep logs of the stuff i enter so it is not until i reread the logs that i really know wjhat i did , and some of those commands i did not do but you basically pointed me in the right direction. anyway, my device is working again thank god, i had moments of panic when i thought i had trashed a 700 buck phone but its all good now. again, thanks.
low.humidity said:
yeah, thanks for that info, it helped. i keep logs of the stuff i enter so it is not until i reread the logs that i really know wjhat i did , and some of those commands i did not do but you basically pointed me in the right direction. anyway, my device is working again thank god, i had moments of panic when i thought i had trashed a 700 buck phone but its all good now. again, thanks.
Click to expand...
Click to collapse
Haha, I'm very glad to know!
Same happened to me and scared the **** out of me. Luckily everything is fine now.
Enjoy your new nexus! It's AWESOME
i'm having trouble understanding..my n6 is stuck in bootloop, twrp keeps showing up after boot screen.. what programs are you guys using to slove this problem..please help..
---------- Post added at 06:37 PM ---------- Previous post was at 06:30 PM ----------
i'm having the same problem..what program are using to slove this problem..please help..
mattogodoy said:
Follow these steps:
Download Android 5.0.1 for Shamu (Nexus 6) from Google servers.
In the terminal:
fastboot flash bootloader bootloader.img
fastboot reboot-bootloader
fastboot flash radio radio.img
fastboot reboot-bootloader
fastboot flash system system.img
fastboot flash userdata userdata.img
fastboot flash boot boot.img (I used a decrypted boot.img for 5.0.1)
fastboot flash recovery recovery.img
fastboot erase cache
fastboot flash cache cache.img (this one fixed my problem)
Hope that fixes it.
Click to expand...
Click to collapse
If I erase and flash cache… all my data and settings are gone?
Via my NeXus™ 7FHD on XDA Premium app
Nexus 6 Boot Loop
Im stuck in boot loop and im using the Nexus root toolkit to try to get me out of the of the loop. It downloaded the image and began to flash but gives me an error at the end saying boot.img was not found. Please help someone?
bitw_alex said:
Im stuck in boot loop and im using the Nexus root toolkit to try to get me out of the of the loop. It downloaded the image and began to flash but gives me an error at the end saying boot.img was not found. Please help someone?
Click to expand...
Click to collapse
http://forum.xda-developers.com/nex...sh-factory-images-nexus-6shamu-t2954008/page9
fastboot flash bootloader filename.img
fastboot flash radio filename.img
fastboot reboot-bootloader
fastboot flash recovery recovery.img
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash cache cache.img (in case you would like to wipe cache files)
fastboot flash userdata userdata.img (only in case you would like to wipe userdata)
fastboot reboot
Little different situation
Not sure what im doing wrong. my nexus was rooted for 2 to 3 weeks on android 5.1 . restarted today to only find myself stuck in a bootloop [ red green yellow blue ] nexus symbol continuously going, i booted into twrp and tried to restore my nexus to a backup i made after i rooted , but still stuck in bootloop , tried 1 more time to use my backup , but still in a bootloop , then tried to factory reset using twrp , and was still stuck in a bootloop , any tips would be awesome , thanks
EDIT: Think what put me in bootloop was making it where i need a password everytime i restart. just did it and seems some are having same problems .
EDIT 2: Well i got out of bootloop . appears i have also lost root . not sure what i did . after using twrp to install backups, format data , it finally restarted . im pretty positive the problem was caused by setting a restart passcode ! watch out guys ,
junior990 said:
i'm having trouble understanding..my n6 is stuck in bootloop, twrp keeps showing up after boot screen.. what programs are you guys using to slove this problem..please help..
---------- Post added at 06:37 PM ---------- Previous post was at 06:30 PM ----------
i'm having the same problem..what program are using to slove this problem..please help..
Click to expand...
Click to collapse
Same prob. Can't get into recovery
forcedairinduction said:
Same prob. Can't get into recovery
Click to expand...
Click to collapse
Can you get to bootloader? Stock or TWRP recovery?
Evolution_Tech said:
Can you get to bootloader? Stock or TWRP recovery?
Click to expand...
Click to collapse
Can get into bootloader, but if I try and go from there to recovery it goes back to team win splash repeatedly flashing
---------- Post added at 02:34 PM ---------- Previous post was at 02:33 PM ----------
Evolution_Tech said:
Can you get to bootloader? Stock or TWRP recovery?
Click to expand...
Click to collapse
forcedairinduction said:
Can get into bootloader, but if I try and go from there to recovery it goes back to team win splash repeatedly flashing
Click to expand...
Click to collapse
PS, I'm very noon at this still. Been flashing since having my n4 but never got into this kinda trouble before. When things have gone wrong in the past I've always managed to go back into twrp & flash nandroid backup...... Scared stiff now
Related
Hi folks,
I have a problem. I tried to flash SinlessRom GE Kitkat 5.1. It flashed allright, but then I got in a boot loop. It boots, but when the set up starts, and I see the screen where to choose the language, then device boots again (and it becomes a bootloop).
I interrupted the boot loop using Vol-down and power, but my recovery wasn't working. When I chose recovery, it didn't entered recovery but booted again.
Then I tried to flash a new recovery, but now I doesn't enter a new bootloop, but get's stuck at the white HTC Screen with in pink "entering recovery..."
I tried to erase cache in fastboot modus, but it didn't help.
Do you guys can help me? Any suggestions?
wybren said:
Hi folks,
I have a problem. I tried to flash SinlessRom GE Kitkat 5.1. It flashed allright, but then I got in a boot loop. It boots, but when the set up starts, and I see the screen where to choose the language, then device boots again (and it becomes a bootloop).
I interrupted the boot loop using Vol-down and power, but my recovery wasn't working. When I chose recovery, it didn't entered recovery but booted again.
Then I tried to flash a new recovery, but now I doesn't enter a new bootloop, but get's stuck at the white HTC Screen with in pink "entering recovery..."
I tried to erase cache in fastboot modus, but it didn't help.
Do you guys can help me? Any suggestions?
Click to expand...
Click to collapse
try erasing the userdata using fastboot. I has a similar problem earlier this week and I remember using that command. Sometime when I enter recovery it just goes to normal boot (randomly), not sure if thats your problem but try entering recovery multiple times. If not...
fastboot erase userdata
fastboot erase cache
fastboot flash recovery recovery.img
wybren said:
Hi folks,
I have a problem. I tried to flash SinlessRom GE Kitkat 5.1. It flashed allright, but then I got in a boot loop. It boots, but when the set up starts, and I see the screen where to choose the language, then device boots again (and it becomes a bootloop).
I interrupted the boot loop using Vol-down and power, but my recovery wasn't working. When I chose recovery, it didn't entered recovery but booted again.
Then I tried to flash a new recovery, but now I doesn't enter a new bootloop, but get's stuck at the white HTC Screen with in pink "entering recovery..."
I tried to erase cache in fastboot modus, but it didn't help.
Do you guys can help me? Any suggestions?
Click to expand...
Click to collapse
khhhhris said:
try erasing the userdata using fastboot. I has a similar problem earlier this week and I remember using that command. Sometime when I enter recovery it just goes to normal boot (randomly), not sure if thats your problem but try entering recovery multiple times. If not...
fastboot erase userdata
fastboot erase cache
fastboot flash recovery recovery.img
Click to expand...
Click to collapse
1- are you s-on or s-off, 4.4 is not compatible (at least for now) with S-On devices!
2- you need to "fastboot erase cache" after flashing recovery; personally i do it before and after, but the important part is after
3- why are you recommending "fastboot erase userdata", just wondering.
nkk71 said:
1- are you s-on or s-off, 4.4 is not compatible (at least for now) with S-On devices!
2- you need to "fastboot erase cache" after flashing recovery; personally i do it before and after, but the important part is after
3- why are you recommending "fastboot erase userdata", just wondering.
Click to expand...
Click to collapse
+1, s-off is required. I only recommend erasing userdata because I had a very similar issue, erasing userdata and a fresh recovery seemed to do the trick after no luck with simply flashing a new recovery and wiping cache Just going off past experience.
khhhhris said:
+1, s-off is required. I only recommend erasing userdata because I had a very similar issue, erasing userdata and a fresh recovery seemed to do the trick after no luck with simply flashing a new recovery and wiping cache Just going off past experience.
Click to expand...
Click to collapse
good to know, was "fastboot erase userdate" successfully? what kind of output did you get?
nkk71 said:
good to know, was "fastboot erase userdate" successfully? what kind of output did you get?
Click to expand...
Click to collapse
Thanks all for the response.
This did the trick:
erase cache
flash twrp recovery (first I tried cwm)
erase cache
Then I managed to enter twrp recovery and flash a new rom.
Don't know why, but I'm happy again
Thanks for the help.
Cool.. hit the users's thanks button!
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 one of my buddies took the OTA update for 4.4.2 while being rooted on 4.4 with TWRP as his recovery. Now he is stuck in an endless bootloop. Any idea what we could do to bring his phone back to life?
By the way, he is on Sprint and has his bootloader unlocked
Any advice would help!
Thanks.
AbstractXart said:
So one of my buddies took the OTA update for 4.4.2 while being rooted on 4.4 with TWRP as his recovery. Now he is stuck in an endless bootloop. Any idea what we could do to bring his phone back to life?
By the way, he is on Sprint and has his bootloader unlocked
Any advice would help!
Thanks.
Click to expand...
Click to collapse
This happened to me too.
Just flash the latest firmware for your device at http://sbf.droid-developers.org/phone.php?device=0
Then accept the OTA.
Re-install TWRP.
Hope this works for you too.
patspdaphone said:
This happened to me too.
Just flash the latest firmware for your device at http://sbf.droid-developers.org/phone.php?device=0
Then accept the OTA.
Re-install TWRP.
Hope this works for you too.
Click to expand...
Click to collapse
So to accept the OTA, did you go through the bootloader/recovery and flash it, or were you able to turn on your phone and accept it? Sorry I don't have his phone on me right now otherwise I would have done it .
Don't flash the full SBF..
boot the phone into fastboot mode... mfastboot erase cache... the reboot the phone. that will remove the OTA zip file from chache and stop the boot loop.
The bootloop is because the phone has TWRP on it rather than stock recovery.
To take the OTA properly, use mfastboot to reflash stock recovery only. Also have him undo any hacks that might have touched system files or the OTA will fail, (mfastboot system will also get /system back to normal)...
KidJoe said:
Don't flash the full SBF..
boot the phone into fastboot mode... mfastboot erase cache... the reboot the phone. that will remove the OTA zip file from chache and stop the boot loop.
The bootloop is because the phone has TWRP on it rather than stock recovery.
To take the OTA properly, use mfastboot to reflash stock recovery only. Also have him undo any hacks that might have touched system files or the OTA will fail, (mfastboot system will also get /system back to normal)...
Click to expand...
Click to collapse
We actually just ended up clearing the system cache and that seemed to do the trick .
I incredibly appreciate all the info! If anyone makes this silly mistake, all you need to do is clear the cache and everything works as intended.
AbstractXart said:
We actually just ended up clearing the system cache and that seemed to do the trick .
I incredibly appreciate all the info! If anyone makes this silly mistake, all you need to do is clear the cache and everything works as intended.
Click to expand...
Click to collapse
until the next time the OTA downloads and tries to install
I am having this very same problem. My phone just today went into boot loop. Running KangKat on unlocked 1053 with Faux kernel. No boot logo or anything. The phone just vibrates then after 30 seconds or so, it vibrates again. It does this non-stop.
I can plug my phone into USB and the phone's contents come up on my computer, but I can't get the screen to turn on!! Any ideas?
Globalrebel said:
I am having this very same problem. My phone just today went into boot loop. Running KangKat on unlocked 1053 with Faux kernel. No boot logo or anything. The phone just vibrates then after 30 seconds or so, it vibrates again. It does this non-stop.
I can plug my phone into USB and the phone's contents come up on my computer, but I can't get the screen to turn on!! Any ideas?
Click to expand...
Click to collapse
KangKat wtih Faux kernel? So you are not running the stock rom? I'm suprised the actually OTA installed.
I don't know anything about that rom, or kernel to begin to tell you how to fix this situation, short of reflashing your rom
KidJoe said:
KangKat wtih Faux kernel? So you are not running the stock rom? I'm suprised the actually OTA installed.
I don't know anything about that rom, or kernel to begin to tell you how to fix this situation, short of reflashing your rom
Click to expand...
Click to collapse
He probably flashed the "Flashable 4.4.2 ZIP" that is flashable through TWRP.
@Globalrebel :
You need to try to get into bootloader (AP Fastboot) mode. Try holding the VOL DOWN while the phone reboots (vibrates). Make sure the phone is unplugged from USB. If you can access fastboot, your best best would probably to flash the entire SBF back to stock.
Always check here first before you do something like trying to flash a stock update on a custom rom. We would have quickly informed you that this is ill-advised.
Good Luck
Ok, so I have held down the power button, and then when vibrating starts, I hold down vol down button. Then, it vibrates 2 times. What now? (Sorry, I'm freaked out as this is my only phones )
How can i check to see if it is actually in Fastboot mode? Since my screen doesn't show ANYTHING at all?
I started up an ADB server and connected my phone and tried "adb devices" but my phone isn't listed.
---------- Post added at 08:49 AM ---------- Previous post was at 08:40 AM ----------
samwathegreat said:
He probably flashed the "Flashable 4.4.2 ZIP" that is flashable through TWRP.
@Globalrebel :
You need to try to get into bootloader (AP Fastboot) mode. Try holding the VOL DOWN while the phone reboots (vibrates). Make sure the phone is unplugged from USB. If you can access fastboot, your best best would probably to flash the entire SBF back to stock.
Always check here first before you do something like trying to flash a stock update on a custom rom. We would have quickly informed you that this is ill-advised.
Good Luck
Click to expand...
Click to collapse
any ideas?
I just checked device manager and it shows "ADB Interface" and then MOT Single ADB Interface.
But its not showing up under devices when running command "ADB Devices" in CMD
Globalrebel said:
Ok, so I have held down the power button, and then when vibrating starts, I hold down vol down button. Then, it vibrates 2 times. What now? (Sorry, I'm freaked out as this is my only phones )
How can i check to see if it is actually in Fastboot mode? Since my screen doesn't show ANYTHING at all?
I started up an ADB server and connected my phone and tried "adb devices" but my phone isn't listed.
---------- Post added at 08:49 AM ---------- Previous post was at 08:40 AM ----------
any ideas?
Click to expand...
Click to collapse
Fastboot getvar all
If you get a response with that, proceed with the entire Sbf manual method as listed in the return to stock thread.
samwathegreat said:
Fastboot getvar all
If you get a response with that, proceed with the entire Sbf manual method as listed in the return to stock thread.
Click to expand...
Click to collapse
I got it to show some info after running the command. Now, I have the following guide open . .
[GUIDE][VIDEO] Moto X - Return to 100% stock (using RSD Lite OR manual flash)
But I don't see anything in RSDLite after running it and clicking "Show Device"
Can I just to the manual method?
For manual method, should I copy all the files into the same folder as my mfastboot.exe?
Globalrebel said:
I got it to show some info after running the command. Now, I have the following guide open . .
[GUIDE][VIDEO] Moto X - Return to 100% stock (using RSD Lite OR manual flash)
But I don't see anything in RSDLite after running it and clicking "Show Device"
Can I just to the manual method?
For manual method, should I copy all the files into the same folder as my mfastboot.exe?
Click to expand...
Click to collapse
Yes,I suggested manual method in last post. Faster and easier.
Yes extract the sbf to the folder containing mfastboot and fastboot.
The only thing you will do differently is one of the last lines that says carrier vzw, change it to carrier sprint.
Make sure u are using the 4.4.2 sprint sbf.
Good luck
samwathegreat said:
Yes,I suggested manual method in last post. Faster and easier.
Yes extract the sbf to the folder containing mfastboot and fastboot.
The only thing you will do differently is one of the last lines that says carrier vzw, change it to carrier sprint.
Make sure u are using the 4.4.2 sprint sbf.
Good luck
Click to expand...
Click to collapse
I am using Tmobile so I put tmo
But, after doing EVERYTHING, the phone reboots and I see it in PC, but screen is still not working?!?!?!
I did everything...
fastboot oem fb_mode_set
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 flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase userdata
fastboot erase customize
fastboot erase clogo
fastboot oem config carrier tmo
fastboot oem fb_mode_clear
then
fastboot reboot
The phone boots and the phone is seen by my computer, but the screen is not working AT ALL
No water damage, and the phone was literally working perfectly fine 15 minutes ago. Just all of a sudden stopped showing the screen
Globalrebel said:
I am using Tmobile so I put tmo
But, after doing EVERYTHING, the phone reboots and I see it in PC, but screen is still not working?!?!?!
I did everything...
fastboot oem fb_mode_set
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 flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase userdata
fastboot erase customize
fastboot erase clogo
fastboot oem config carrier tmo
fastboot oem fb_mode_clear
then
fastboot reboot
The phone boots and the phone is seen by my computer, but the screen is not working AT ALL
Click to expand...
Click to collapse
Bummer. You appear to have used the correct procedure.
This looks to be a hardware failure :/
Sorry, I don't have any further troubleshooting techniques for you...
Its all good. I think the screen just decided to die on me?!?! Which REALLY SUCKS! I'm still in my 1 year warranty policy. After fastbooting the original 4.4.2, will motorola know I did anything to the phone? IE, can they know I flashed anything?
Globalrebel said:
Its all good. I think the screen just decided to die on me?!?! Which REALLY SUCKS! I'm still in my 1 year warranty policy. After fastbooting the original 4.4.2, will motorola know I did anything to the phone? IE, can they know I flashed anything?
Click to expand...
Click to collapse
If you unlocked the bootloader they know it. Technically your warranty is void... But they might replace/fix it anyways. Don't mention it and see what happens. Let us know.
I am trying to back out everything I've done to the phone and start fresh with 5.1. I had rooted, decrypted, and installed TWRP. To undo this, I did a factory reset, downloaded the shamu-lrx22c factory image from google, and used adb/fastboot to put it all back the way I found it. These are the commands I used :
fastboot flash bootloader bootloader-shamu-moto-apq8084-71.05.img
fastboot flash radio radio-shamu-d4.0-9625-02.55.04.img
fastboot reboot-bootloader
fastboot flash recovery recovery.img
fastboot flash boot boot.img
fastboot flash system system.img
It appeared to all work. Now when I try to get back into recovery, the phone sits at the android with the red triangle and !. The bootloader logs state "Mismatched partition size (recovery)."
Did I do a bad thing somewhere along the way? Thanks in advance.
Try flashing the recovery again. I think if I was you I would also fastboot -w to format the userdata and cache since you already did a factory reset or use google's images by using "fastboot flash userdata userdata.img", "fastboot erase cache" and then "fastboot flash cache cache.img".
Also, check the md5 of the image you downloaded to make sure it was not corrupt.
Evo_Shift said:
Try flashing the recovery again. I think if I was you I would also fastboot -w to format the userdata and cache since you already did a factory reset or use google's images by using "fastboot flash userdata userdata.img", "fastboot erase cache" and then "fastboot flash cache cache.img".
Also, check the md5 of the image you downloaded to make sure it was not corrupt.
Click to expand...
Click to collapse
I used fastboot -w to format the userdata/cache. And I also tried the three fastboot commands you listed. They all seem to work, but the reflashing of the recovery still throws the same error.
MD5 checksum of the whole zip is the same. I re-extracted the recovery.img file just to be sure and it still throws the same error.
Kramit said:
when I try to get back into recovery, the phone sits at the android with the red triangle and !.
Click to expand...
Click to collapse
Thats normal though isn't it? With Stock recovery you have to press Volume up and power to get into the recovery menu from that screen
rootSU said:
Thats normal though isn't it? With Stock recovery you have to press Volume up and power to get into the recovery menu from that screen
Click to expand...
Click to collapse
Sadly, that doesn't do anything. Pressed repeatedly, held down for a while, nothing. up until the point where it reboots from the power button being held long enough.
rootSU said:
Thats normal though isn't it? With Stock recovery you have to press Volume up and power to get into the recovery menu from that screen
Click to expand...
Click to collapse
yes, thats norml
cmh714 said:
yes, thats norml
Click to expand...
Click to collapse
Hmm. And if it doesn't work?
Kramit said:
I am trying to back out everything I've done to the phone and start fresh with 5.1. I had rooted, decrypted, and installed TWRP. To undo this, I did a factory reset, downloaded the shamu-lrx22c factory image from google, and used adb/fastboot to put it all back the way I found it. These are the commands I used :
fastboot flash bootloader bootloader-shamu-moto-apq8084-71.05.img
fastboot flash radio radio-shamu-d4.0-9625-02.55.04.img
fastboot reboot-bootloader
fastboot flash recovery recovery.img
fastboot flash boot boot.img
fastboot flash system system.img
It appeared to all work. Now when I try to get back into recovery, the phone sits at the android with the red triangle and !. The bootloader logs state "Mismatched partition size (recovery)."
Did I do a bad thing somewhere along the way? Thanks in advance.
Click to expand...
Click to collapse
I have the same problem here but maybe i have found a solution for it:
what i did was i left the 5.1 bootloader.img and took all the other stuff from a 5.0 factory image such as: radio.img, system.img..... fastbooted everything and i was with a 5.0 LP stock out of the box, then i have rooted it, installed twrp with f2fs support and voila i'm now good to go
hope this will help you out
Kramit said:
Sadly, that doesn't do anything. Pressed repeatedly, held down for a while, nothing. up until the point where it reboots from the power button being held long enough.
Click to expand...
Click to collapse
When you see the android with the red triangle and !, you need to hold the power button, and while you are holding it down, press volume up. Pushing them both together, or one after the other, or holding them down together or whatever else won't work.
Sent from my Nexus 6 using Tapatalk
So i tried to change the global rom of my red magic 3 to the Chinese rom, i put the Chinese rom zip in the phone and i proceed to update it manually so it can be load, but when it was installing for the first time this error appears "your device is corrupt. it cant be trusted and will not boot", as i sais this error appears since the first time i tried to install it so did not have the opportunity to activate the developer options and check usb debugging and OEM unlock, i can use the bootloader to unlock the phone by using the command "fastboot oem nubia_unlock NUBIA_NX629J" but when i try to flash it by using this command "fastboot flashing unlock" this error appears "FAILED: (remote: flashing Unlock is not allowed)" so im stuck here, what can i do to continue or to go back to factory settings, i hope some one can help me.
im sorry for my bad English
Have you tried changing back to global rom using recovery mode through OTG cable?
kelv55l said:
Have you tried changing back to global rom using recovery mode through OTG cable?
Click to expand...
Click to collapse
i have not tried that, can you linkme how to do it?
Sinuhejrz said:
i have not tried that, can you linkme how to do it?
Click to expand...
Click to collapse
I went to this link https://forum.xda-developers.com/red-magic-3/help/stuck-fastboot-mode-t3937527
So basically you want to go into fastboot mode either using command "adb reboot bootloader" while plugging the phone into the computer or by holding down the volume down - and power button until it goes into fastboot mode.
Once you are in fastboot mode you go to "reboot to recovery mode" navigate while using the volume buttons and select by using the power button.
Now in recovery mode navigate by using volume buttons and select by using power button again. Its optional, but you can "wipe data" by wiping userdata partition and cache partition. I wiped data when I booted like this. Download the global from here https://global.redmagic.gg/blogs/news/red-magic-3-global-rom-flash-instructions I downloaded the North America version because that was the only version that worked for me. Put the zip file you downloaded into a flash drive USB. then connect the usb to the OTG cable you can buy from ebay, amazon or a nearby tech store. Then connect all that to your phone and click "Choose Update Package" and then click "Choose From OTG Device" then select the rom that you put in the usb drive and then everything should take care of itself from there.
Hope this helps!
kelv55l said:
I went to this link https://forum.xda-developers.com/red-magic-3/help/stuck-fastboot-mode-t3937527
So basically you want to go into fastboot mode either using command "adb reboot bootloader" while plugging the phone into the computer or by holding down the volume down - and power button until it goes into fastboot mode.
Once you are in fastboot mode you go to "reboot to recovery mode" navigate while using the volume buttons and select by using the power button.
Now in recovery mode navigate by using volume buttons and select by using power button again. Its optional, but you can "wipe data" by wiping userdata partition and cache partition. I wiped data when I booted like this. Download the global from here https://global.redmagic.gg/blogs/news/red-magic-3-global-rom-flash-instructions I downloaded the North America version because that was the only version that worked for me. Put the zip file you downloaded into a flash drive USB. then connect the usb to the OTG cable you can buy from ebay, amazon or a nearby tech store. Then connect all that to your phone and click "Choose Update Package" and then click "Choose From OTG Device" then select the rom that you put in the usb drive and then everything should take care of itself from there.
Hope this helps!
Click to expand...
Click to collapse
i cant go into recovery mode when i select that option the phone restarts and the same message appears "your device is corrupt. it cant be trusted and will not boot" , what can i do?
Sinuhejrz said:
i cant go into recovery mode when i select that option the phone restarts and the same message appears "your device is corrupt. it cant be trusted and will not boot" , what can i do?
Click to expand...
Click to collapse
Damn that happened to me to when I tried rooting my phone. My recovery mode was corrupt too. You can try to use the instructions given on this page https://forum.xda-developers.com/red-magic-3/help/device-corrupt-trusted-boot-t3940057/page2. Extract all img and bin files from the Global ROM and place them into the folder where the "cmd-here.exe" is. Also you need "system.img" you can download that here https://drive.google.com/drive/folders/16in6Jnyi4s5aIIuQwapQ1KK1LjysSfYm, but dont download the other files they might be the Chinese files.
After you extracted the img and bin files and placed them into the folder where the cmd is placed connect your phone to the computer, open the cmd exe and run the commands
fastboot oem nubia_unlock NUBIA_NX629J
fastboot flash parameter parameter.img
fastboot reboot bootloader
fastboot oem nubia_unlock NUBIA_NX629J
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash splash splash.img
fastboot flash modem NON-HLOS.bin
fastboot flash system system.img
fastboot flash dsp dspso.bin
fastboot oem nubia_lock NUBIA_NX629J
fastboot reboot
After all that you should be able to go into recovery mode through fastboot mode if not then try and flash dtbo.img and vbmeta.img in the line of commands so for example "fastboot flash dtbo dtbo.img" and "fastboot flash vbmeta vbmeta.img" looking something like this...
fastboot oem nubia_unlock NUBIA_NX629J
fastboot flash parameter parameter.img
fastboot reboot bootloader
fastboot oem nubia_unlock NUBIA_NX629J
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash splash splash.img
fastboot flash dtbo dtbo.img
fastboot flash vbmeta vbmeta.img
fastboot flash modem NON-HLOS.bin
fastboot flash dsp dspso.bin
fastboot flash system system.img
fastboot reboot
This was the line of commands I used when my recovery mode was corrupt and somehow worked
I hope this helps and let me know if it worked or if the issue is still there. Also the forum has several posts on this matter and they might have the answer you are looking for as it helped me with this issue. Good Luck!
kelv55l said:
Damn that happened to me to when I tried rooting my phone. My recovery mode was corrupt too. You can try to use the instructions given on this page https://forum.xda-developers.com/red-magic-3/help/device-corrupt-trusted-boot-t3940057/page2. Extract all img and bin files from the Global ROM and place them into the folder where the "cmd-here.exe" is. Also you need "system.img" you can download that here https://drive.google.com/drive/folders/16in6Jnyi4s5aIIuQwapQ1KK1LjysSfYm, but dont download the other files they might be the Chinese files.
After you extracted the img and bin files and placed them into the folder where the cmd is placed connect your phone to the computer, open the cmd exe and run the commands
fastboot oem nubia_unlock NUBIA_NX629J
fastboot flash parameter parameter.img
fastboot reboot bootloader
fastboot oem nubia_unlock NUBIA_NX629J
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash splash splash.img
fastboot flash modem NON-HLOS.bin
fastboot flash system system.img
fastboot flash dsp dspso.bin
fastboot oem nubia_lock NUBIA_NX629J
fastboot reboot
After all that you should be able to go into recovery mode through fastboot mode if not then try and flash dtbo.img and vbmeta.img in the line of commands so for example "fastboot flash dtbo dtbo.img" and "fastboot flash vbmeta vbmeta.img" looking something like this...
fastboot oem nubia_unlock NUBIA_NX629J
fastboot flash parameter parameter.img
fastboot reboot bootloader
fastboot oem nubia_unlock NUBIA_NX629J
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash splash splash.img
fastboot flash dtbo dtbo.img
fastboot flash vbmeta vbmeta.img
fastboot flash modem NON-HLOS.bin
fastboot flash dsp dspso.bin
fastboot flash system system.img
fastboot reboot
This was the line of commands I used when my recovery mode was corrupt and somehow worked
I hope this helps and let me know if it worked or if the issue is still there. Also the forum has several posts on this matter and they might have the answer you are looking for as it helped me with this issue. Good Luck!
Click to expand...
Click to collapse
OMG OMG OMG it works thank you so much dude you are THE MAN now i have more than an expensive weight-paper, i really appreciate it dude, the second code lines also works for me the only problem i encounter was in this code line "fastboot flash system system.img" throw this message "C:\adb>fastboot flash system system.img
target reported max download size of 805306368 bytes
Invalid sparse file format at header magi"
but i keep with the rest of the lines and works perfectly after that.
again thank you so much dude for the help :good::crying:
Sinuhejrz said:
OMG OMG OMG it works thank you so much dude you are THE MAN now i have more than an expensive weight-paper, i really appreciate it dude, the second code lines also works for me the only problem i encounter was in this code line "fastboot flash system system.img" throw this message "C:\adb>fastboot flash system system.img
target reported max download size of 805306368 bytes
Invalid sparse file format at header magi"
but i keep with the rest of the lines and works perfectly after that.
again thank you so much dude for the help :good::crying:
Click to expand...
Click to collapse
Awesome! glad I could help you out
kelv55l said:
Awesome! glad I could help you out
Click to expand...
Click to collapse
tnx man i really appreciate it, so could you change the ROM of you phone to the Chinese one?
Sinuhejrz said:
tnx man i really appreciate it, so could you change the ROM of you phone to the Chinese one?
Click to expand...
Click to collapse
Sorry man I haven't tried changing my ROM to Chinese yet. Don't want to risk corrupting my phone again :crying:
But I'll let you know if I decide to change my rom.
Sinuhejrz said:
tnx man i really appreciate it, so could you change the ROM of you phone to the Chinese one?
Click to expand...
Click to collapse
Pretty simple to change the ROM to chinese. Download the chinese ROM, place it in an OTG or the phone's root directory. You can either do it via local update from the system.update feature in settings or use the stock recovery and install it via the OTG. Personally I would.prefer you install it via the OTG.
Please help me !!! I have same problem with my rm3
Sinuhejrz said:
So i tried to change the global rom of my red magic 3 to the Chinese rom, i put the Chinese rom zip in the phone and i proceed to update it manually so it can be load, but when it was installing for the first time this error appears "your device is corrupt. it cant be trusted and will not boot", as i sais this error appears since the first time i tried to install it so did not have the opportunity to activate the developer options and check usb debugging and OEM unlock, i can use the bootloader to unlock the phone by using the command "fastboot oem nubia_unlock NUBIA_NX629J" but when i try to flash it by using this command "fastboot flashing unlock" this error appears "FAILED: (remote: flashing Unlock is not allowed)" so im stuck here, what can i do to continue or to go back to factory settings, i hope some one can help me.
im sorry for my bad English
Click to expand...
Click to collapse
Please help me !!! I have same problem with my rm3 :crying::crying::crying: PLEASE
---------- Post added at 09:57 PM ---------- Previous post was at 09:49 PM ----------
kelv55l said:
Awesome! glad I could help you out
Click to expand...
Click to collapse
PLEASE HELP ME Bro !!! I have same problem :crying::crying::crying:
hanif9067 said:
Please help me !!! I have same problem with my rm3 :crying::crying::crying: PLEASE
---------- Post added at 09:57 PM ---------- Previous post was at 09:49 PM ----------
PLEASE HELP ME Bro !!! I have same problem :crying::crying::crying:
Click to expand...
Click to collapse
Give me your address, I'll come to your house to fix the phone!
hanif9067 said:
Please help me !!! I have same problem with my rm3 :crying::crying::crying: PLEASE
---------- Post added at 09:57 PM ---------- Previous post was at 09:49 PM ----------
PLEASE HELP ME Bro !!! I have same problem :crying::crying::crying:
Click to expand...
Click to collapse
What seems to be the problem are you able to go into recovery mode?
If not then flashing the appropriate img and bin files should allow you to go back to recovery mode as explained on previous posts on this thread.
kelv55l said:
What seems to be the problem are you able to go into recovery mode?
If not then flashing the appropriate img and bin files should allow you to go back to recovery mode as explained on previous posts on this thread.
Click to expand...
Click to collapse
Mine has the same problem and tried all the steps in this thread. Not able to go into recovery mode, can go into fastboot mode and flash everything but phone is still corrupt and can not boot. New phone now no good, OH well
re-flashed the phone using the first version of the Chinese ROM v2.12 now can use the OTG update option. just need to get a usb adapter now
I'm hoping someone can help me. I've followed the fix on earlier pages and used the files including system.img a user uploaded.
Now when booting my phone I get a device is corrupt and cannot be trusted message. I read somewhere else that the command 'Fastboot flashing unlock' may solve this but I get an error message.
Would really appreciate some help, maybe I've done something wrong but I've followed the instructions and used the files an xda user uploaded.
Many thanks.
Johnnio said:
I'm hoping someone can help me. I've followed the fix on earlier pages and used the files including system.img a user uploaded.
Now when booting my phone I get a device is corrupt and cannot be trusted message. I read somewhere else that the command 'Fastboot flashing unlock' may solve this but I get an error message.
Would really appreciate some help, maybe I've done something wrong but I've followed the instructions and used the files an xda user uploaded.
Many thanks.
Click to expand...
Click to collapse
Have you tried to erase and then reflash again?
try something like this according from this user
em90256 said:
try this
fastboot -w
fastboot erase recovery
fastboot flash recovery recovery.img
fastboot reboot
try your stock recovery image
Click to expand...
Click to collapse
leipnacht said:
Have you tried to erase and then reflash again?
try something like this according from this user
Click to expand...
Click to collapse
Thanks but I managed to fix it yesterday, I had to flash the system image using 'fastboot flash -S 100M system system.img', turns out that although it reported flash as successful it wasn't actually sent correctly unless split into smaller chunks.
Johnnio said:
Thanks but I managed to fix it yesterday, I had to flash the system image using 'fastboot flash -S 100M system system.img', turns out that although it reported flash as successful it wasn't actually sent correctly unless split into smaller chunks.
Click to expand...
Click to collapse
Oh new information. What does "-S 100M" on fastboot command do?