My zenfone 2 laser are stuck in fastboot mode, can't go to recovery or any thing, using the adb and fastboot i can flash boot.img, system.img etc. but nothing happens. and the bootloader are locked too, and i don't find some way to unlock without the app from asus, tried to put 'fastboot oem get_unlock_ability' or 'fastboot oem unlock' but i just receive 'FAILED (remote: 'unknown command')'
i don't know what to do, someone know what i can do? pls
Reflash ofw via adb with stock boot/recovery
lukk321 said:
My zenfone 2 laser are stuck in fastboot mode, can't go to recovery or any thing, using the adb and fastboot i can flash boot.img, system.img etc. but nothing happens. and the bootloader are locked too, and i don't find some way to unlock without the app from asus, tried to put 'fastboot oem get_unlock_ability' or 'fastboot oem unlock' but i just receive 'FAILED (remote: 'unknown command')'
i don't know what to do, someone know what i can do? pls
Click to expand...
Click to collapse
Hi dude try flash boot and recovery from h**ps://drive.google.com/folderview?id=0B0aDjdU4gTwZRWxzLWxhYUZPbVk&usp=drive_web
then reboot holding volume down button once done should have recovery menu select install through adb sideload etc
download fw from here: h**ps://dlcdnets.asus.com/pub/ASUS/ZenFone/ZS550KL/UL-Z00L-WW-21.40.1220.2196-user.zip?_ga=2.175867362.1367738333.1539164489-1033220152.1538417076[/
then on pc copy downloaded fw to adb folder and type: adb sideload UL-Z00L-WW-21.40.1220.2196-user.zip
[/B]
and will begin to install and hope all goes well and good luck
Hi man, thank you for reply
Foggalias said:
Hi dude try flash boot and recovery from h**ps://drive.google.com/folderview?id=0B0aDjdU4gTwZRWxzLWxhYUZPbVk&usp=drive_web
then reboot holding volume down button once done should have recovery menu select install through adb sideload etc
download fw from here: h**ps://dlcdnets.asus.com/pub/ASUS/ZenFone/ZS550KL/UL-Z00L-WW-21.40.1220.2196-user.zip?_ga=2.175867362.1367738333.1539164489-1033220152.1538417076[/
then on pc copy downloaded fw to adb folder and type: adb sideload UL-Z00L-WW-21.40.1220.2196-user.zip
[/B]
and will begin to install and hope all goes well and good luck
Click to expand...
Click to collapse
But i alredy try to flash boot, recovery, twrp, even try use flashall.bat, but my bootloader are locked, so when i type 'fastboot flash recovery recovery.img' it appears that worked, but when i try to go to recovey, the phone just shows the asus logo with 'fastboot mode' on the top, even typing 'fastboot reboot-bootloader' or 'fastboot reboot' while holding the volume down button, it don't work. And typing 'fastboot getvar recovery or boot' shows nothing.
Probably i need to unlock the bootloader first, but i don't know how to do that.
lukk321 said:
But i alredy try to flash boot, recovery, twrp, even try use flashall.bat, but my bootloader are locked, so when i type 'fastboot flash recovery recovery.img' it appears that worked, but when i try to go to recovey, the phone just shows the asus logo with 'fastboot mode' on the top, even typing 'fastboot reboot-bootloader' or 'fastboot reboot' while holding the volume down button, it don't work. And typing 'fastboot getvar recovery or boot' shows nothing.
Probably i need to unlock the bootloader first, but i don't know how to do that.
Click to expand...
Click to collapse
sorry to hear dude and sorry for late reply I'm sure I used the app to unlock my boot loader ill do a bit of digging if I find anything
---------- Post added at 11:48 PM ---------- Previous post was at 11:36 PM ----------
Foggalias said:
sorry to hear dude and sorry for late reply I'm sure I used the app to unlock my boot loader ill do a bit of digging if I find anything
Click to expand...
Click to collapse
hi dude try here its flashing tarp without unlocking boot loader and its through fastboot mode
h***s:/.asus.com/zentalk/in/thread-128115-1-1.html
---------- Post added 11th October 2018 at 12:10 AM ---------- Previous post was 10th October 2018 at 11:48 PM ----------
Foggalias said:
sorry to hear dude and sorry for late reply I'm sure I used the app to unlock my boot loader ill do a bit of digging if I find anything
---------- Post added at 11:48 PM ---------- Previous post was at 11:36 PM ----------
hi dude try here its flashing tarp without unlocking boot loader and its through fastboot mode
h***s:/.asus.com/zentalk/in/thread-128115-1-1.html
Click to expand...
Click to collapse
try this unlock bloody via fastboot
h***s://drive.google.com/file/d/0ByzlvYYhluSdR3ZpdWYzX1ZfRUE/view?usp=drivesdk
Hi again dude how u getting on? I remember when I used the unlock tool app it just rebooted and nothing looked different at all and the only way I found putTit was u locked was on fastboot mode using this command:
fastboot oem device-info
Said something like bootloader unlocked: True
I'd give it a shot and hopefully its just the case of some bad img's good luck
thanks helping me
Foggalias said:
sorry to hear dude and sorry for late reply I'm sure I used the app to unlock my boot loader ill do a bit of digging if I find anything
---------- Post added at 11:48 PM ---------- Previous post was at 11:36 PM ----------
hi dude try here its flashing tarp without unlocking boot loader and its through fastboot mode
h***s:/.asus.com/zentalk/in/thread-128115-1-1.html
---------- Post added 11th October 2018 at 12:10 AM ---------- Previous post was 10th October 2018 at 11:48 PM ----------
try this unlock bloody via fastboot
h***s://drive.google.com/file/d/0ByzlvYYhluSdR3ZpdWYzX1ZfRUE/view?usp=drivesdk
Click to expand...
Click to collapse
the asus site are off now, so later i'll see that
the unlock tool look that worked, but the phone still stuck in fastboot
Foggalias said:
Hi again dude how u getting on? I remember when I used the unlock tool app it just rebooted and nothing looked different at all and the only way I found putTit was u locked was on fastboot mode using this command:
fastboot oem device-info
Said something like bootloader unlocked: True
I'd give it a shot and hopefully its just the case of some bad img's good luck
Click to expand...
Click to collapse
fastboot oem device-info shows that:
(bootloader) Device unlocked: false
(bootloader) Charger screen enabled: false
(bootloader) Display panel:
(bootloader) Adb Enable: 0
OKAY [ 0.017s]
finished. total time: 0.018s
even after using the unlock tool
Thank you for helping dude
I gonna send the phone to the support center, before i explode the phone haha, sorry for taking your time, bye.
lukk321 said:
I gonna send the phone to the support center, before i explode the phone haha, sorry for taking your time, bye.
Click to expand...
Click to collapse
no worries dude sorry coudnt sort it
---------- Post added at 12:26 PM ---------- Previous post was at 12:17 PM ----------
lukk321 said:
fastboot oem device-info shows that:
(bootloader) Device unlocked: false
(bootloader) Charger screen enabled: false
(bootloader) Display panel:
(bootloader) Adb Enable: 0
OKAY [ 0.017s]
finished. total time: 0.018s
even after using the unlock tool
Click to expand...
Click to collapse
hi dude sorry to hear but people have managed to flash boot using certain version img file and then able to flash the recovery on locked bootloaders
id say try before it costs you at service
here: https://www.asus.com/zentalk/in/thread-88877-1-1.html
Same issue with my phone but i'm getting different error
I guys,
I gone through your post and similar issue I'm facing. As suggested I tried unlock boot loader or whenever trying to flash getting below error. Can you help me to get this fix. Might be I'll recover my phone.
target reported max download size of 268435456 bytes
sending 'fastboot' (13273 KB)...
OKAY [ 0.419s]
writing 'fastboot'...
FAILED (remote: partition table doesn't exist)
finished. total time: 0.426s
rebooting into bootloader...
OKAY [ 0.001s]
finished. total time: 0.001s
Below device info i can see but still it boots into fastboot and not in recovery mode
(bootloader) Device unlocked: true
(bootloader) Charger screen enabled: false
(bootloader) Display panel:
(bootloader) Adb Enable: 0
OKAY [ 0.004s]
finished. total time: 0.004s
Hiya dude I know there's a certain fw version that it'll let u adb sideload, I take your getting this issue from trying to side load, I'll have a look and try and find fw I used. It does state device unlocked: true which I did mine using an app if I remember correctly
Are you able to flash recovery ar all ??
---------- Post added at 10:57 AM ---------- Previous post was at 10:55 AM ----------
Hiya dude again I think what u used is linked above in thread, have you tried thise by any chance?
---------- Post added at 11:02 AM ---------- Previous post was at 10:57 AM ----------
krahul99 said:
I guys,
I gone through your post and similar issue I'm facing. As suggested I tried unlock boot loader or whenever trying to flash getting below error. Can you help me to get this fix. Might be I'll recover my phone.
target reported max download size of 268435456 bytes
sending 'fastboot' (13273 KB)...
OKAY [ 0.419s]
writing 'fastboot'...
FAILED (remote: partition table doesn't exist)
finished. total time: 0.426s
rebooting into bootloader...
OKAY [ 0.001s]
finished. total time: 0.001s
Below device info i can see but still it boots into fastboot and not in recovery mode
(bootloader) Device unlocked: true
(bootloader) Charger screen enabled: false
(bootloader) Display panel:
(bootloader) Adb Enable: 0
OKAY [ 0.004s]
finished. total time: 0.004s
Click to expand...
Click to collapse
Try this dude:
https://www.asus.com/zentalk/in/forum.php?mod=viewthread&tid=128115&mobile=2
Let me know how u get on
---------- Post added at 11:09 AM ---------- Previous post was at 11:02 AM ----------
krahul99 said:
I guys,
I gone through your post and similar issue I'm facing. As suggested I tried unlock boot loader or whenever trying to flash getting below error. Can you help me to get this fix. Might be I'll recover my phone.
target reported max download size of 268435456 bytes
sending 'fastboot' (13273 KB)...
OKAY [ 0.419s]
writing 'fastboot'...
FAILED (remote: partition table doesn't exist)
finished. total time: 0.426s
rebooting into bootloader...
OKAY [ 0.001s]
finished. total time: 0.001s
Below device info i can see but still it boots into fastboot and not in recovery mode
(bootloader) Device unlocked: true
(bootloader) Charger screen enabled: false
(bootloader) Display panel:
(bootloader) Adb Enable: 0
OKAY [ 0.004s]
finished. total time: 0.004s
Click to expand...
Click to collapse
Hi dude try flash boot and recovery from here a little guide in there to (update error fix): h**ps://drive.google.com/folderview?id=0B0aDjdU4gTwZRWxzLWxhYUZPbVk&usp=drive_web
then reboot holding volume down button once done should have recovery menu select install through adb sideload etc
download fw from here: h**ps://dlcdnets.asus.com/pub/ASUS/ZenFone/ZS550KL/UL-Z00L-WW-21.40.1220.2196-user.zip?_ga=2.175867362.1367738333.1539164489-1033220152.1538417076[
then on pc copy downloaded fw to adb folder and type: adb sideload UL-Z00L-WW-21.40.1220.2196-user.zip
and will begin to install and hope all goes well and good luck
Tried this but still it comes in fastboot mode only
Yup i tried these methods earlier. It shows written but when I reboot and try to go to recovery it directly comes into Fastboot. Rather if I remove battery and just plug the usb cable even though it shows fastboot mode.
Foggalias said:
Hiya dude I know there's a certain fw version that it'll let u adb sideload, I take your getting this issue from trying to side load, I'll have a look and try and find fw I used. It does state device unlocked: true which I did mine using an app if I remember correctly
Are you able to flash recovery ar all ??
---------- Post added at 10:57 AM ---------- Previous post was at 10:55 AM ----------
Hiya dude again I think what u used is linked above in thread, have you tried thise by any chance?
---------- Post added at 11:02 AM ---------- Previous post was at 10:57 AM ----------
Try this dude:
https://www.asus.com/zentalk/in/forum.php?mod=viewthread&tid=128115&mobile=2
Let me know how u get on
---------- Post added at 11:09 AM ---------- Previous post was at 11:02 AM ----------
Hi dude try flash boot and recovery from here a little guide in there to (update error fix): h**ps://drive.google.com/folderview?id=0B0aDjdU4gTwZRWxzLWxhYUZPbVk&usp=drive_web
then reboot holding volume down button once done should have recovery menu select install through adb sideload etc
download fw from here: h**ps://dlcdnets.asus.com/pub/ASUS/ZenFone/ZS550KL/UL-Z00L-WW-21.40.1220.2196-user.zip?_ga=2.175867362.1367738333.1539164489-1033220152.1538417076[
then on pc copy downloaded fw to adb folder and type: adb sideload UL-Z00L-WW-21.40.1220.2196-user.zip
and will begin to install and hope all goes well and good luck
Click to expand...
Click to collapse
Same issue with my asus
krahul99 said:
Yup i tried these methods earlier. It shows written but when I reboot and try to go to recovery it directly comes into Fastboot. Rather if I remove battery and just plug the usb cable even though it shows fastboot mode.
Click to expand...
Click to collapse
I'm facing same issue with my device.. Pls can you hlp me
Mohanking6 said:
I'm facing same issue with my device.. Pls can you hlp me
Click to expand...
Click to collapse
Install recovery and boot image version 1531 then use adb sideload to flash latest version of ROM.
Foggalias said:
Reflash ofw via adb with stock boot/recovery
Hi dude try flash boot and recovery from h**ps://drive.google.com/folderview?id=0B0aDjdU4gTwZRWxzLWxhYUZPbVk&usp=drive_web
then reboot holding volume down button once done should have recovery menu select install through adb sideload etc
download fw from here: h**ps://dlcdnets.asus.com/pub/ASUS/ZenFone/ZS550KL/UL-Z00L-WW-21.40.1220.2196-user.zip?_ga=2.175867362.1367738333.1539164489-1033220152.1538417076[/
then on pc copy downloaded fw to adb folder and type: adb sideload UL-Z00L-WW-21.40.1220.2196-user.zip
[/B]
and will begin to install and hope all goes well and good luck
Click to expand...
Click to collapse
I just wanted to Thank you! I was about to give up and sell the phone because ive tried all countless methods and now i have recovery mode. Thank you so much forr keeping the google drive links alive..
frenchiejoshy said:
I just wanted to Thank you! I was about to give up and sell the phone because ive tried all countless methods and now i have recovery mode. Thank you so much forr keeping the google drive links alive..
Click to expand...
Click to collapse
unable to flash boot.img brother
fastboot flash fastboot boot.img
target reported max download size of 268435456 bytes
sending 'fastboot' (24547 KB)...
OKAY [ 0.775s]
writing 'fastboot'...
FAILED (remote: cannot flash this partition in locked state)
finished. total time: 0.803s
osm gkkkkkk said:
unable to flash boot.img brother
fastboot flash fastboot boot.img
target reported max download size of 268435456 bytes
sending 'fastboot' (24547 KB)...
OKAY [ 0.775s]
writing 'fastboot'...
FAILED (remote: cannot flash this partition in locked state)
finished. total time: 0.803s
Click to expand...
Click to collapse
which file did you use and how
Foggalias said:
Reflash ofw via adb with stock boot/recovery
Hi dude try flash boot and recovery from h**ps://drive.google.com/folderview?id=0B0aDjdU4gTwZRWxzLWxhYUZPbVk&usp=drive_web
then reboot holding volume down button once done should have recovery menu select install through adb sideload etc
download fw from here: h**ps://dlcdnets.asus.com/pub/ASUS/ZenFone/ZS550KL/UL-Z00L-WW-21.40.1220.2196-user.zip?_ga=2.175867362.1367738333.1539164489-1033220152.1538417076[/
then on pc copy downloaded fw to adb folder and type: adb sideload UL-Z00L-WW-21.40.1220.2196-user.zip
[/B]
and will begin to install and hope all goes well and good luck
Click to expand...
Click to collapse
pls help which file and how ,i have th same issue as was faced by one of the used
unable to install boot.img
unable to flash boot.img brother
fastboot flash fastboot boot.img
target reported max download size of 268435456 bytes
sending 'fastboot' (24547 KB)...
OKAY [ 0.775s]
writing 'fastboot'...
FAILED (remote: cannot flash this partition in locked state)
finished. total time: 0.803s
Related
Dear All,
A few days ago SPRINT moto X 1056 gets Firmware Update of about 5.4 MB.. After that update alot of people which have moto x 1056 and they are not using Sprint network get them sim locked.. Sim was not recognized and default network was selected "sprint" on the mobile and also the nv-items files were changed to Read Only Mode. Also after the update.. People keep getting UPDATE PRL on every restart.
Click to expand...
Click to collapse
I have also got in trouble after this update and researched about 3 days to get my problem solved.
The things u need to do is to
Install Motorola Drivers.
Backup Your Personal Data.
Install adb + fastboot (I recommend to use mfastboot).
Unlock Your Boot Loader.
Flash TWRP Recover throug fastboot.
Wipe Everything " System, Cache, Dalvik Cache, Internal Storage, Data" (After this u will have no OS in your mobile)
(OPTIONAL: If your phone have "SPC code" . Then you need to Flash "161.44.32.ghost_sprint.Sprint.en.US[1].zip" through TWRP. and get your SPC code then unlock the sim) In my Case i dont have SPC code set in my phone and i was able to unlock sim without giving SPC code on firmware 4.4.4 pre 5.4 mb update.
Click to expand...
Click to collapse
Flash Firmware "ghost_sprint-user-4.4.4-KXA21.12-L1.28-28-release-keys-cid9.xml"
Unlock Sim
Flash LolliPop 5.1 "Version: 222.21.15.ghost_row.Retail.en.US" (To Remove Update PRL messages/things)
Remove Bootloader Warning Message (Flash [GHOST] Moto-WinterBoot-20150419-STABLE)
Note: This GUIDE is for MOTO X SPRINT [XT1056]
Now Lets Get Starting with Steps.
1. Install Motorola Drivers.
Downlod the drivers from the following link and install it.
"https://motorola-global-portal.custhelp.com/app/answers/detail/a_id/88481"
Or
"http://motofirmware.center/files/file/41-motorola_end_user_driver_installation_640_32bitzip/"
Click to expand...
Click to collapse
2. Backup Your Personal Data.
Connect your device to your PC. Check Usb Options selected to "MTP" on your device.
Backup your personal data on phone.
Click to expand...
Click to collapse
3. Install adb + fastboot (I recommend to use mfastboot).
You can install adb + fastboot by installing Android-SDK. To Install Android SDK. Download the Standalone Android-SDK from following Link.
"http://developer.android.com/sdk/index.html#Other"
and now watch the following Guide to install and set parameters of Android-SDK.
"https://www.youtube.com/watch?v=oaNM-lt_aHw"
OR as i said i Recommend to use "mfastboot"
You can download mfastboot from following link
"http://www.mediafire.com/download/6b3aw3dq8omefyw/mfastboot-v2.zip"
Just download and unzip it to use
Click to expand...
Click to collapse
4. Unlock BootLoader:
You can easily unlock bootloader of your device by clicking
"https://motorola-global-portal.custhelp.com/app/standalone/bootloader/unlock-your-device-b"
OR watch this video for 100% Success.
https://www.youtube.com/watch?v=3sxgz7jxRMw
Click to expand...
Click to collapse
5. Flash TWRP Recover throug fastboot.
Download latest TWRP recovery from link
"http://techerrata.com/browse/twrp2/ghost"
Now, Install TWRP using this site method.
"https://twrp.me/devices/motorolamotox2013.html"
Click to expand...
Click to collapse
6. Wipe Everything " System, Cache, Dalvik Cache, Internal Storage, Data" (After this u will have no OS in your mobile)
After installing recovery . Go to recovery by following method.
Hold and press VOL DOWN + POWER button for 5 secs and release.
Now u r in bootloader. Go to recovery by VOL DOWN button and select by VOL UP button.
Now go to WIPE > Advanced > and then wipe All folders. except USB OTG.
Now you have NO OS installled on ur Moto X.
Reboot to Recovery to bootloader again.
Click to expand...
Click to collapse
7. Flash Firmware "ghost_sprint-user-4.4.4-KXA21.12-L1.28-28-release-keys-cid9.xml"
Now its time to flash the pre 5.4 mb update firmware to your moto x xt1056.
Download the firmware from here
"http://www.filefactory.com/file/6tiwapkl82jl/"
And flash through fastboot. just extract the zip file and copy all files and folders in "Mfastboot folder" 0r "android-sdk folder"
Now open Mfastboot folder and press "Shift key + Right Click" now click "Open Command Prompt here"
Perform the following steps as i have performed .
Click to expand...
Click to collapse
C:\mfastboot-v2>mfastboot devices
T063204CVP fastboot
C:\mfastboot-v2>mfastboot flash partition gpt.bin
(bootloader) Variable not supported!
target max-download-size: 768MB
sending 'partition' (32 KB)...
OKAY [ 0.275s]
writing 'partition'...
(bootloader) This may take a few seconds, if a
(bootloader) different partition table is being
(bootloader) flashed since we need to backup
(bootloader) and restore a few partitions
OKAY [ 0.468s]
finished. total time: 0.743s
C:\mfastboot-v2>mfastboot flash motoboot motoboot.img
(bootloader) Variable not supported!
target max-download-size: 768MB
sending 'motoboot' (1604 KB)...
OKAY [ 0.368s]
writing 'motoboot'...
(bootloader) flashing sbl1 ...
(bootloader) flashing sbl2 ...
(bootloader) flashing sbl3 ...
(bootloader) flashing rpm ...
(bootloader) flashing tz ...
(bootloader) flashing aboot ...
OKAY [ 5.049s]
finished. total time: 5.419s
C:\mfastboot-v2>mfastboot flash logo logo.bin
(bootloader) Variable not supported!
target max-download-size: 768MB
sending 'logo' (628 KB)...
OKAY [ 0.343s]
writing 'logo'...
OKAY [ 0.879s]
finished. total time: 1.224s
C:\mfastboot-v2>fastboot flash boot boot.img
(bootloader) Variable not supported!
target reported max download size of 805306368 bytes
sending 'boot' (10240 KB)...
OKAY [ 0.920s]
writing 'boot'...
OKAY [ 1.358s]
finished. total time: 2.280s
C:\mfastboot-v2>mfastboot flash recovery recovery.img
(bootloader) Variable not supported!
target max-download-size: 768MB
sending 'recovery' (10240 KB)...
OKAY [ 0.928s]
writing 'recovery'...
OKAY [ 0.968s]
finished. total time: 1.898s
C:\mfastboot-v2>mfastboot flash system system.img
(bootloader) Variable not supported!
target max-download-size: 768MB
Multi-Flash is enabled!
sending 'system' (262144 KB)...
OKAY [ 16.692s]
writing 'system'...
OKAY [ 10.502s]
sending 'system' (262144 KB)...
OKAY [ 16.684s]
writing 'system'...
OKAY [ 9.854s]
sending 'system' (262144 KB)...
OKAY [ 16.683s]
writing 'system'...
OKAY [ 8.245s]
sending 'system' (114215 KB)...
OKAY [ 7.443s]
writing 'system'...
OKAY [ 3.613s]
finished. total time: 89.725s
C:\mfastboot-v2>mfastboot flash modem NON-HLOS.bin
(bootloader) Variable not supported!
target max-download-size: 768MB
sending 'modem' (53804 KB)...
OKAY [ 3.664s]
writing 'modem'...
OKAY [ 2.468s]
finished. total time: 6.134s
C:\mfastboot-v2>mfastboot erase modemst1
erasing 'modemst1'...
OKAY [ 0.437s]
finished. total time: 0.439s
C:\mfastboot-v2>mfastboot erase modemst2
erasing 'modemst2'...
OKAY [ 0.445s]
finished. total time: 0.445s
C:\mfastboot-v2>mfastboot flash fsg fsg.mbn
(bootloader) Variable not supported!
target max-download-size: 768MB
sending 'fsg' (1223 KB)...
OKAY [ 0.386s]
writing 'fsg'...
OKAY [ 0.828s]
finished. total time: 1.216s
C:\mfastboot-v2>mfastboot oem lock
...
(bootloader) FAIL: Please run fastboot oem lock begin first!
OKAY [ 0.164s]
finished. total time: 0.165s
C:\mfastboot-v2>mfastboot reboot
rebooting...
finished. total time: 0.001s
C:\mfastboot-v2>
C:\mfastboot-v2>
Click to expand...
Click to collapse
Now please Proceed to Next POST.
2nd Post
After flashing the 4.4.4 firmware. Now the device should boot and start the Android. But notice after starting and every restart It automatically checks the Profile and PRL activations. Now time to unlock your Sim.
8. Unlock Sim.
To unlock your sim follow the following guide here on XDA.
"http://forum.xda-developers.com/showpost.php?p=54338871&postcount=2"
Note: In my case i have checked and there is no SPC code needed to sim unlock. No need to check spc code checkbox in NV-ITEMS-READER-WRITER software.
So the you just connect your phone to nv items reader writer software and flash only
nv-unlock.txt
nv-unlock2,txt
unlock-domestic.txt
nv-ruim files need SPC code to write . If u dont have SPC code set in your phone for enable / disable DIAG PORT then you dont need to write nv-ruim files.
Click to expand...
Click to collapse
Congrats. U have Sim-Unlocked Moto X Sprint .
9. Flash LolliPop 5.1 "Version: 222.21.15.ghost_row.Retail.en.US"
Download LolliPop Retail 5.1 from following link.
"https://drive.google.com/file/d/0BzTDEHw-bGypMGhfdEFVczd1dHM/view"
This is XT1053 untouched Retail ROM
Open TWRP recovery. and Flash the ROM by clicking Install . Select the location where you copy the zip rom in internal memory.
After installing the ROM , Reboot to TWRP Recovery again and WIPE CACHE and DALVIK CACHE.
Then reboot to system. Now it should start the OS 5.1 and there should not PRL updation on start and restart.
Click to expand...
Click to collapse
Now you have unlocked your sim and have Lolipop 5.1 with Stock System Version 222.21.15
10. Remove Boot-loader Warning .
Download your favorite Boot Animation Image from the link
"https://drive.google.com/folderview?id=0Bx0JlaDkWMGAfkpQcGl2M3NCWi11SmZ5N3hiV05EdFFERzRrNUhBcjNjb0JXRU5fQ2lDZjg&usp=drive_web "
Copy it in mobile memory. and Then install through TWRP. Again now wipe Dalvik Cache and Cache. Restart to System.
Click to expand...
Click to collapse
For StageFright Update:
Make your nandroid backup first.
Now Download this System image from "https://mega.nz/#!LwEXWRLB!NAQBXMwI6aoNNw7VXB_u3m3XjEOSiZ_bUGcbBL1ykTk"
Now flash this system.img through TWRP.
Clear your Cache and Dalvik Cache.
Download the Stagefright System 222.27.5 TWRP backup from the above link
Unzip the Stagefright System 222.27.5 folder to your computer
Copy the Stagefright System 222.27.5 folder to your phones internal storage, to the TWRP/BACKUPS/TA0000008VJ/ directory
Reboot your phone into recovery (TWRP)
Click Restore and select the Stagefright System 222.27.5 folder
Verify that the System partition is selected and then Swipe to Restore
Clear your cache
Click to expand...
Click to collapse
Now this update should flash and phone should work fine,
Credits Goes to mastarifla
Now You have Sim Unlocked Lolipop 5.1 with Removed Bootloader Warning Message.
Credits
All Credits Goes to
XDA-Developers
Ghost_Developer for
http://forum.xda-developers.com/moto-x/themes-apps/ghost-original-bootanimations-unlocked-t3087294
Perseus for
http://forum.xda-developers.com/moto-x/general/index-welcome-to-motorola-moto-x-t2558785
d_shadow for
http://forum.xda-developers.com/general/rooting-roms/motorola-usb-drivers-rsd-lite-firmware-t3042687
VitaTaf for
http://forum.xda-developers.com/moto-x/development/xt1053-retail-stock-lollipop-flashable-t3155843
samwathegreat for
http://forum.xda-developers.com/showpost.php?p=54338871&postcount=2
My Sprint 2013 Moto X just got an update last night and now this is happening to the phone. It has no calling capabilities now but has data. This is also not a developer edition phone so I don't see how iwould be able to do all of this like unlocking the bootloader and all this flashing. It seems like put simply, sprint pushed out an update and bricked my phone in terms of making and receiving calls. Is there no other solution to this? What would they do if I take it to the store?
Files for getting SPC
For those who needs the SPC, here are the links for the needed files:
4.4.2 TWRP Flashable ROM (thanks to Aaron Nickolopoulos for uploading and sharing the link)
4.4.2 Modem (can be flashed thru RSD Lite or fastboot) (uploaded by me )
Advice for the future: Use EFS Professional to change SPC to 000000
m0ndul said:
For those who needs the SPC, here are the links for the needed files:
4.4.2 TWRP Flashable ROM (thanks to Aaron Nickolopoulos for uploading and sharing the link)
4.4.2 Modem (can be flashed thru RSD Lite or fastboot) (uploaded by me )
Advice for the future: Use EFS Professional to change SPC to 000000
Click to expand...
Click to collapse
this in regards to me?
emerica243 said:
this in regards to me?
Click to expand...
Click to collapse
To all of us, happened to me also
fastboot.exe has stopped working when flashing system.img.
Any one had this problem ?
C:\android-sdk\platform-tools>fastboot flash system system.img
(bootloader) Variable not supported!
target reported max download size of 805306368 bytes
Invalid sparse file format at header magi
Thats all it gives me then crashes
you have to use mfastboot flash system system.img
m0ndul said:
For those who needs the SPC, here are the links for the needed files:
4.4.2 TWRP Flashable ROM (thanks to Aaron Nickolopoulos for uploading and sharing the link)
4.4.2 Modem (can be flashed thru RSD Lite or fastboot) (uploaded by me )
Advice for the future: Use EFS Professional to change SPC to 000000
Click to expand...
Click to collapse
hi there can u please tell me how to get spc on 4.4.4 motox sprint i would really appreciate ur help
EDIT: got my spc by downgrading to 4.4.2
yar_nl said:
you have to use mfastboot flash system system.img
Click to expand...
Click to collapse
If you're using mfastboot, then yes that's the command.
I'm using android-sdk. For android sdk comand is :
fastboot flash system system.img
Managed to make it work with RSD lite.
Sent from my iPhone 6s Plus using Tapatalk
Superpopsss said:
If you're using mfastboot, then yes that's the command.
I'm using android-sdk. For android sdk comand is :
fastboot flash system system.img
Managed to make it work with RSD lite.
Sent from my iPhone 6s Plus using Tapatalk
Click to expand...
Click to collapse
See this thread of why use mfastboot for details http://mark.cdmaforums.com/MotoX-mFastboot.htm
---------- Post added at 04:01 PM ---------- Previous post was at 03:53 PM ----------
For those who know their MSL/SPC code see --> http://forum.xda-developers.com/showpost.php?p=63585276&postcount=959
yar_nl said:
See this thread of why use mfastboot for details http://mark.cdmaforums.com/MotoX-mFastboot.htm
---------- Post added at 04:01 PM ---------- Previous post was at 03:53 PM ----------
For those who know their MSL/SPC code see --> http://forum.xda-developers.com/showpost.php?p=63585276&postcount=959
Click to expand...
Click to collapse
Good to know, but it's easier to use rds lite then manually flashing all the files needed :
Step One - Download and install RSD Lite. At the moment, I can't find where I got mine from, so anyone who wants to add a proper link to it would be appreciated. I used version 6.1.5 and it worked fine.
Step Two - proper driver installation. If you're like me, you probably at one point got drivers quasi-working but here's what I did that worked - download and install "Motorola Device Manager" and it *should* give you the proper drivers. This was necessary (maybe) because I could get adb to recognize my device, as well as fastboot, however RSD refused to see it. This install fixed that.
Step Three - download and install the proper firmware for your device. NOTE: You MUST MUST MUST choose the right firmware for your device or you will FUBAR your phone.....not my responsibility.
Step Four - Unzip your firmware zip file, open it up through the layers and find the file "VZW_XT1060_4.2.2-13.9.0Q2.X-116-MX-17-53_CFC_1FF" or whatever version/carrier/build number file yours is, its the XML Document file. Right click -> Open with.. -> Notepad/word editor/XML Editor/wordpad and find the line:
<step operation="getvar" var="max-download-size" />
^^^You need to select this entire line and just delete it out of the file. This is the line that gives fastboot flash error. Select it, delete it, then resave the file an exit out of it. Done.
NOTE: This is required or the firmware flash will immediately fail giving a "failed flashing process. Unknown fastboot command. (getvar)"
-For the sake of security, and not messing with important files, I'd actually recommend zipping the file back up after this and keeping as your final version (once you've confirmed yours works correctly)
Step Five - Plug in phone, enable USB debugging, then "adb reboot bootloader" - this will boot you into fastboot mode so RSD will recognize your phone
Step Six - Run RSD Lite - note that some people have had trouble and have to right-click run as administrator. In RSD Lite, make sure phone shows up in slot 1 - mine shows up, under Model, just says fastboot, USB port type, info N/A, important part is that it shows as Connected in status. Select the three-dot browse file button, then you can go down into the unzipped file you created of the XML folder, and select the XML file that we just edited earlier (or select the rezipped package). Select open and flash. (or decompress and flash)
Step Eight - Profit
Superpopsss said:
Good to know, but it's easier to use rds lite then manually flashing all the files needed :
Step One - Download and install RSD Lite. At the moment, I can't find where I got mine from, so anyone who wants to add a proper link to it would be appreciated. I used version 6.1.5 and it worked fine.
Step Two - proper driver installation. If you're like me, you probably at one point got drivers quasi-working but here's what I did that worked - download and install "Motorola Device Manager" and it *should* give you the proper drivers. This was necessary (maybe) because I could get adb to recognize my device, as well as fastboot, however RSD refused to see it. This install fixed that.
Step Three - download and install the proper firmware for your device. NOTE: You MUST MUST MUST choose the right firmware for your device or you will FUBAR your phone.....not my responsibility.
Step Four - Unzip your firmware zip file, open it up through the layers and find the file "VZW_XT1060_4.2.2-13.9.0Q2.X-116-MX-17-53_CFC_1FF" or whatever version/carrier/build number file yours is, its the XML Document file. Right click -> Open with.. -> Notepad/word editor/XML Editor/wordpad and find the line:
<step operation="getvar" var="max-download-size" />
^^^You need to select this entire line and just delete it out of the file. This is the line that gives fastboot flash error. Select it, delete it, then resave the file an exit out of it. Done.
NOTE: This is required or the firmware flash will immediately fail giving a "failed flashing process. Unknown fastboot command. (getvar)"
-For the sake of security, and not messing with important files, I'd actually recommend zipping the file back up after this and keeping as your final version (once you've confirmed yours works correctly)
Step Five - Plug in phone, enable USB debugging, then "adb reboot bootloader" - this will boot you into fastboot mode so RSD will recognize your phone
Step Six - Run RSD Lite - note that some people have had trouble and have to right-click run as administrator. In RSD Lite, make sure phone shows up in slot 1 - mine shows up, under Model, just says fastboot, USB port type, info N/A, important part is that it shows as Connected in status. Select the three-dot browse file button, then you can go down into the unzipped file you created of the XML folder, and select the XML file that we just edited earlier (or select the rezipped package). Select open and flash. (or decompress and flash)
Step Eight - Profit
Click to expand...
Click to collapse
http://www.droidviews.com/restore-moto-x-to-stock-firmware-using-rsd-lite/
yar_nl said:
http://www.droidviews.com/restore-moto-x-to-stock-firmware-using-rsd-lite/
Click to expand...
Click to collapse
Exactly, takes 1 min compared to the potential errors you could encounter by flashing manually.
Superpopsss said:
fastboot.exe has stopped working when flashing system.img.
Any one had this problem ?
C:\android-sdk\platform-tools>fastboot flash system system.img
(bootloader) Variable not supported!
target reported max download size of 805306368 bytes
Invalid sparse file format at header magi
Thats all it gives me then crashes
Click to expand...
Click to collapse
Please use mfastboot
emerica243 said:
My Sprint 2013 Moto X just got an update last night and now this is happening to the phone. It has no calling capabilities now but has data. This is also not a developer edition phone so I don't see how iwould be able to do all of this like unlocking the bootloader and all this flashing. It seems like put simply, sprint pushed out an update and bricked my phone in terms of making and receiving calls. Is there no other solution to this? What would they do if I take it to the store?
Click to expand...
Click to collapse
Take it to sprint store is the best solution.
Hi, can you please let me know how did you install 4.4.2 thought TWRP. I downloaded 4.4.2 from the link provided here.
Thanks
MAJID
ameraze said:
hi there can u please tell me how to get spc on 4.4.4 motox sprint i would really appreciate ur help
EDIT: got my spc by downgrading to 4.4.2
Click to expand...
Click to collapse
---------- Post added at 09:38 AM ---------- Previous post was at 09:35 AM ----------
Hello, I followed till step 8, but my phone is still giving sim card error, any other suggestion?
flopadmi said:
After flashing the 4.4.4 firmware. Now the device should boot and start the Android. But notice after starting and every restart It automatically checks the Profile and PRL activations. Now time to unlock your Sim.
8. Unlock Sim.
Congrats. U have Sim-Unlocked Moto X Sprint .
9. Flash LolliPop 5.1 "Version: 222.21.15.ghost_row.Retail.en.US"
Now you have unlocked your sim and have Lolipop 5.1 with Stock System Version 222.21.15
10. Remove Boot-loader Warning .
Now You have Sim Unlocked Lolipop 5.1 with Removed Bootloader Warning Message.
Click to expand...
Click to collapse
---------- Post added at 09:59 AM ---------- Previous post was at 09:38 AM ----------
Hi,
if i install only 4.4.2 modem file, shall it be helpful to run SPC utility?
and if yes....then do i have to execute all below commands or just the first one?
C:\mfastboot-v2>mfastboot flash modem NON-HLOS.bin
(bootloader) Variable not supported!
target max-download-size: 768MB
sending 'modem' (53804 KB)...
OKAY [ 3.664s]
writing 'modem'...
OKAY [ 2.468s]
finished. total time: 6.134s
C:\mfastboot-v2>mfastboot erase modemst1
erasing 'modemst1'...
OKAY [ 0.437s]
finished. total time: 0.439s
C:\mfastboot-v2>mfastboot erase modemst2
erasing 'modemst2'...
OKAY [ 0.445s]
finished. total time: 0.445s
m0ndul said:
For those who needs the SPC, here are the links for the needed files:
4.4.2 TWRP Flashable ROM (thanks to Aaron Nickolopoulos for uploading and sharing the link)
4.4.2 Modem (can be flashed thru RSD Lite or fastboot) (uploaded by me )
Advice for the future: Use EFS Professional to change SPC to 000000
Click to expand...
Click to collapse
hmajid_039 said:
Hi, can you please let me know how did you install 4.4.2 thought TWRP. I downloaded 4.4.2 from the link provided here.
Thanks
MAJID
---------- Post added at 09:38 AM ---------- Previous post was at 09:35 AM ----------
Hello, I followed till step 8, but my phone is still giving sim card error, any other suggestion?
---------- Post added at 09:59 AM ---------- Previous post was at 09:38 AM ----------
Hi,
if i install only 4.4.2 modem file, shall it be helpful to run SPC utility?
and if yes....then do i have to execute all below commands or just the first one?
C:\mfastboot-v2>mfastboot flash modem NON-HLOS.bin
(bootloader) Variable not supported!
target max-download-size: 768MB
sending 'modem' (53804 KB)...
OKAY [ 3.664s]
writing 'modem'...
OKAY [ 2.468s]
finished. total time: 6.134s
C:\mfastboot-v2>mfastboot erase modemst1
erasing 'modemst1'...
OKAY [ 0.437s]
finished. total time: 0.439s
C:\mfastboot-v2>mfastboot erase modemst2
erasing 'modemst2'...
OKAY [ 0.445s]
finished. total time: 0.445s
Click to expand...
Click to collapse
If u have downloaded 4.4.2 rom then open twrp recovery and click on install.. Then select zip file....
If u have downloaded 4.4.2 firmware then u need to flash through mfastboot or rsd lite...
Yes if u need only to flash modem then please execute the all three commands representing modem...
For unlock sim. Please tell me rather u can enable / disable ur DIAG port with spc code or without soc code ?
Hi, I have 4.4.2 rom with zim file. I did the same through twrp. But after that my phone goes black after showing statrup moto logo/animation..
Currently again i am back on 4.4.4 with sim card error.
And I am also unable to enable DIAG port.
Update : It is solved now.
Here's what exactly happened to my Oneplus2 -
I had successfully unlocked the Bootloader and flashed TWRP using Fastboot.
Using TWRP, I flashed SU Binary and got root privileges.
STUPID Step : I enabled ENCRYPTION on the device.
Which made it impossible for TWRP to mount the encrypted drives. But even after that I was able to boot into Recovery.
Everything was fine (obviously, I wasn't able to flash through TWRP though, due to encryption)
After some days, when I tried to boot into TWRP, the device got powered off promptly just after the boot animation flashed on screen (which hardly lasted for a second)
I don't know what happened. I was not able to reboot device into system either. It just flashes the boot screen for a second and then completely goes blank. Same is the case if I try to boot into Recovery (using Power button + Vol button)
[Currently] I am able to power off my device and boot into Fastboot Mode (using Vol Up + Power)
I tried flashing TWRP again but it fails giving the following error.
Command - fastboot flash recovery TWRP.img
target reported max download size of 536870912 bytes
sending 'recovery' (25956 KB)...
OKAY [ 0.859s]
writing 'recovery'...
FAILED (remote: device is locked. Cannot flash images)
finished. total time: 0.875s
Click to expand...
Click to collapse
So I checked whether the Bootloader is still unlocked? (And unfortunately it is locked, I have no idea how)
Command - fastboot oem device-info
...
(bootloader) Device tampered: true
(bootloader) Device unlocked: false
(bootloader) Device is_verified: false
(bootloader) Charger screen enabled: false
(bootloader) Display panel:
(bootloader) console_locked: 1
(bootloader) exec_console_unconsole: 0
OKAY [ 0.078s]
finished. total time: 0.078s
Click to expand...
Click to collapse
I tried to unlock the bootloader again but still the same result.
Command - fastboot oem unlock
(I'm sure that OEM unlocking was checked and even USB debugging was enabled last time I was booted into the system)
...
OKAY [ 0.000s]
finished. total time: 0.000s
Click to expand...
Click to collapse
The bootanimation flashed for a second and then again nothing happened. I again checked the bootloader status. It is still same as quoted above.
I rattled a lot around many forums to get a way to boot into the system.
So what tried was to use this command.
Command - fastboot continue
resuming boot...
OKAY [ 0.008s]
finished. total time: 0.009s
Click to expand...
Click to collapse
Only a charging screen appears. And on removing USB same thing happens. Device gets powered off and on trying to boot again bootanimation comes up for a second and then blank screen.
I really have no idea what to do? Any help would be appreciated.
Thanks!
Follow this
https://www.youtube.com/watch?v=R4SVSovw4Jo
Nothing to worry about, i was on MM(beta) when this happen... I try to revert back to LP but the oem is locked.. I cnt even boot my phone... But at least fastboot was ok though.. http://forum.xda-developers.com/oneplus-2/general/guide-unbrick-recover-oneplus-2-to-t3269543 this one
Flash Stock Recovery & Flash OxygenOS Zip
muk12 said:
Follow this
https://www.youtube.com/watch?v=R4SVSovw4Jo
Click to expand...
Click to collapse
This Video is awesome saved my life...thanks a ton......
SOLVED
The Chinese recovery tool did worked in my second attempt.
Just followed the video.
First time it didn't worked but second time it did.
In my first attempt it failed with some error. I uninstalled the device from the Device Manager. Reconnected it and updated the drivers again. Installed ADB. And then just followed as done in the video and it worked in this attempt.
After the recovery process was complete the device booted normally (And didn't went into Stock Recovery as I was expecting)
I rebooted the device into recovery mode(Stock Recovery)
Then I wiped the data to remove Encryption.
Thanks for the help. Cheers !!!
I'm having issues with my recovery after flashing the OOS 3.0 to the phone. My phone is working but when i boot into recovery, it stays on the page saying 1+ powered by android. Anyone else have this issue, or any ways to fix it.
I also tried re-flashing twrp, but i get "FAILED (Remote: dtb not found)" when i try to boot the recovery image.
FireForged said:
I'm having issues with my recovery after flashing the OOS 3.0 to the phone. My phone is working but when i boot into recovery, it stays on the page saying 1+ powered by android. Anyone else have this issue, or any ways to fix it.
I also tried re-flashing twrp, but i get "FAILED (Remote: dtb not found)" when i try to boot the recovery image.
Click to expand...
Click to collapse
u need modified twrp, here is the link: https://www.androidfilehost.com/?fid=24459283995297945
flo071 said:
u need modified twrp, here is the link: https://www.androidfilehost.com/?fid=24459283995297945
Click to expand...
Click to collapse
After using this twrp, and flashed with cmd: fastboot boot recovery.img, I return in twrp-recovery.
So I restart (with disable and/or not disable to change the recovery). But after that I am in the same situation. It is possible to flash the same twrp for another time but that is not what we want
This even doesn't work when I restart to recovery.
Is there another possible solution?
Thanks in advance.
retaliator said:
After using this twrp, and flashed with cmd: fastboot boot recovery.img, I return in twrp-recovery.
So I restart (with disable and/or not disable to change the recovery). But after that I am in the same situation. It is possible to flash the same twrp for another time but that is not what we want
This even doesn't work when I restart to recovery.
Is there another possible solution?
Thanks in advance.
Click to expand...
Click to collapse
i disabled reflashing the original recovery...whats is asked when you reboot in system...
for me this worked....
Thanks for answering me.
I did also disabling reflashing new recovery when reboot in system.
When reboot in recovery the 1+ logo apearred and nothing happens.
I have the same issue - I can get fastboot and flash recoveries, but the OP2 never gets beyond the boot screen. tried flashing different recoveries, no joy.
---------- Post added at 09:43 PM ---------- Previous post was at 09:02 PM ----------
update - got it working.
steps:
flashed recovery.img in this post.
booted into twrp
flashed oldmodem5.1.1 zip I had on my phone
rebooted into recovery
flashed twrp3.0.2.img
flashed new+modem.zip
flashed exdodus nightly
boom, back in business
you can keep that OOS rubbish
my phone also not going past the 1+ logo screen
as told i downloaded the recovery.img from above
restart my device in fastboot
C:\Users\imran\Downloads>fastboot oem unlock
...
OKAY [ 0.005s]
finished. total time: 0.006s
after this command my device again started n struck at that logo i restart again in fastmode to check
C:\Users\imran\Downloads>fastboot oem device-info
...
(bootloader) Device tampered: true
(bootloader) Device unlocked: false
(bootloader) Device is_verified: false
(bootloader) Charger screen enabled: false
(bootloader) Display panel:
(bootloader) console_locked: 1
(bootloader) exec_console_unconsole: 0
OKAY [ 0.073s]
finished. total time: 0.074s
please help
Hello, i've the solution
Download the FirstAid :
http://forum.xda-developers.com/devdb/project/dl/?id=16684
- Unzip files
- Boot your phone in Fastboot
- Go to Firstaid_v_2_0 -> Firstaid -> then lunch ' firstaid'
Thanks for the reply..
i run the file but still no use
F:\Firstaid>fastboot oem unlock
...
OKAY [ 0.016s]
finished. total time: 0.016s
F:\Firstaid>fastboot oem device-info
...
(bootloader) Device tampered: true
(bootloader) Device unlocked: false
(bootloader) Device is_verified: false
(bootloader) Charger screen enabled: false
(bootloader) Display panel:
(bootloader) console_locked: 1
(bootloader) exec_console_unconsole: 0
OKAY [ 0.078s]
finished. total time: 0.078s
F:\Firstaid>fastboot flash recovery TWRP.img
target reported max download size of 536870912 bytes
sending 'recovery' (28144 KB)...
OKAY [ 1.047s]
writing 'recovery'...
FAILED (remote: device is locked. Cannot flash images)
finished. total time: 1.063s
NOTE:if i enter command "fastboot continue" my device is getting started...
Try this, I think you bootloader is still locked
fastboot -i 0x2A70 oem unlock-go
Or follow this guide
http://forum.xda-developers.com/oneplus-2/general/guide-make-oneplus-2-adb-devices-t3218332
Sent from my ONE A2003 using Tapatalk
I had this problem and got the recovery working again with the modified version from above. Where did you get this? and what modification was needed? This is very strange. I never had that kind of a problem.
I flashed my phone back from OxygenOS 3 beta to OxygenOS 2.2.1 to get a working phone again and will now try to revert to the normal recovery again. From there I hope to get twrp 3.0.2.0 and cyanogenmod 13 to work.
UPDATE: normal twrp 3.0.2.0 works again. So my steps to recover from a brick with no accessable recovery to a working phone were:
1. flash modified recovery
2. boot into recovery
3. flash latest stable stock rom
4. flash latest stock twrp
Thanks a lot dude it worked for me
Keep up the good work guys.
What I did to get a working recovery:
1. flash modified recovery from first post in this thread with flashing recovery from pc
2. boot into recovery
3. flash latest stable stock rom
4. flash in recovery the latest recovery from first post
5. flash beta version Oxygen3
6. flash again twrp in recovery
7. flash superuser
8. disable replace recovery
All is well done.
Thanks for helping me mates!
I found out that it is enough when you:
1. copy modified recovery from first post in this thread to your phone
2. flash modified recovery from your pc to your phone
3. boot in recovery
4. flash the recovery you copied to your phone in installed recovery
5. restart with disable replace recovery
Thats enough to do the trick.
I am sorry to reply to an old post but I am unsure if other people are still having issues with this like I was. Here is some info from https://twrp.me/devices/oneplustwo.html :
"Note many devices will replace your custom recovery automatically during first boot. To prevent this, use Google to find the proper key combo to enter recovery. After typing fastboot reboot, hold the key combo and boot to TWRP. Once TWRP is booted, TWRP will patch the stock ROM to prevent the stock ROM from replacing TWRP. If you don't follow this step, you will have to repeat the install."
---------- Post added at 07:19 AM ---------- Previous post was at 07:18 AM ----------
I am sorry to reply to an old post but I am unsure if other people are still having issues with this like I was. Here is some info from https://twrp.me/devices/oneplustwo.html :
"Note many devices will replace your custom recovery automatically during first boot. To prevent this, use Google to find the proper key combo to enter recovery. After typing fastboot reboot, hold the key combo and boot to TWRP. Once TWRP is booted, TWRP will patch the stock ROM to prevent the stock ROM from replacing TWRP. If you don't follow this step, you will have to repeat the install."
Hi All,
Due to in ternal memory full, suddenly my home button stopped working and notifications were not appearing. I tried and followed advice written in one of the websites:
"f you didn't enabled developer settings and usb debug prior to the defect, you can create an icon to call this Activity using Nova Launcher.
After installing it and launching, long press home screen, select widgets, swipe right to find Activity icon, place on empty space in your home, search for setup wizard (it changes accordingly to your native language), select .SetupWizardTestActivity and voilá."
But, now my phone is stuck in SetupWizardTestActivity loop. I desperately need to recover my photos and other data on internal memory.
Please suggest.
Additional Info:
Using Moto X play (updated to Marshmallow)
Bootloader is unlocked
Can't you just boot into safe mode and try if that works.
Boot into Safe Mode
With the phone on, press and hold the power key until the on-screen “Power off” option shows up.
Long press on the on-screen button, and select “Boot into Safe Mode.”
or if you have an unlocked bootloader you can flash TWRP and use the build in file manager to transfer the files to your sd.
anujagraj said:
Hi All,
Due to in ternal memory full, suddenly my home button stopped working and notifications were not appearing. I tried and followed advice written in one of the websites:
"f you didn't enabled developer settings and usb debug prior to the defect, you can create an icon to call this Activity using Nova Launcher.
After installing it and launching, long press home screen, select widgets, swipe right to find Activity icon, place on empty space in your home, search for setup wizard (it changes accordingly to your native language), select .SetupWizardTestActivity and voilá."
But, now my phone is stuck in SetupWizardTestActivity loop. I desperately need to recover my photos and other data on internal memory.
Please suggest.
Additional Info:
Using Moto X play (updated to Marshmallow)
Bootloader is unlocked
Click to expand...
Click to collapse
If bootloader is unlocked then recovering data is easy, I guess you have TWRP recovery if not flash twrp then pop in a sd-card boot into recovery and copy everything to the card. Done.
Edit: the above comment says the same thing, I had not noticed that .
While flashing TWRP recovery, I am getting the following message in CMD:
target reported max download size of 268435456 bytes
sending 'recovery' (8362 KB)...
OKAY [ 0.276s]
writing 'recovery'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.310s
In phone's bootloader logs, I can see: "Mismatched partition size (recovery).
Please help!
Lennyz1988 said:
Can't you just boot into safe mode and try if that works.
Boot into Safe Mode
With the phone on, press and hold the power key until the on-screen “Power off” option shows up.
Long press on the on-screen button, and select “Boot into Safe Mode.”
or if you have an unlocked bootloader you can flash TWRP and use the build in file manager to transfer the files to your sd.
Click to expand...
Click to collapse
Hi,
Safe mode is not helping. Same loop is continuing.
Also, I am not able to flash TWRP custom recovery. I am getting the following message:
(bootloader) Preflash validation failed
FAILED (remote failure)
In phone bootloader logs I can see: "Mismatched partition size (recovery).
bablu048 said:
If bootloader is unlocked then recovering data is easy, I guess you have TWRP recovery if not flash twrp then pop in a sd-card boot into recovery and copy everything to the card. Done.
Edit: the above comment says the same thing, I had not noticed that .
Click to expand...
Click to collapse
While flashing TWRP recovery, I am getting the following message in CMD:
target reported max download size of 268435456 bytes
sending 'recovery' (8362 KB)...
OKAY [ 0.276s]
writing 'recovery'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.310s
In phone bootloader logs I can see: "Mismatched partition size (recovery).
Please help!
anujagraj said:
While flashing TWRP recovery, I am getting the following message in CMD:
target reported max download size of 268435456 bytes
sending 'recovery' (8362 KB)...
OKAY [ 0.276s]
writing 'recovery'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.310s
In phone bootloader logs I can see: "Mismatched partition size (recovery).
Please help!
Click to expand...
Click to collapse
is the bootloader unlocked, did you input the code to unlock??just checking
Yes. Bootlader is unlocked with input code to unlock.
I guess adb is not authorised then. when the phone is in setup wizard connect it to pc and type 'adb devices' there will be a pop-up asking you to authorise adb. select it. the try to flash recovery again .
---------- Post added at 07:47 AM ---------- Previous post was at 07:44 AM ----------
anujagraj said:
Yes. Bootlader is unlocked with input code to unlock.
Click to expand...
Click to collapse
or simply run
fastboot boot <enter twrp name>
bablu048 said:
I guess adb is not authorised then. when the phone is in setup wizard connect it to pc and type 'adb devices' there will be a pop-up asking you to authorise adb. select it. the try to flash recovery again .
---------- Post added at 07:47 AM ---------- Previous post was at 07:44 AM ----------
or simply run
fastboot boot <enter twrp name>
Click to expand...
Click to collapse
"adb devices" is not working during Setup wizard.
Do you mean to say that I run fastboot boot <enter twrp name> during setup wizard?
Also, alternatively, will flashing a rom without clearing user data help in any way?
Thanks a lot for the help..
bablu048 said:
I guess adb is not authorised then. when the phone is in setup wizard connect it to pc and type 'adb devices' there will be a pop-up asking you to authorise adb. select it. the try to flash recovery again .
---------- Post added at 07:47 AM ---------- Previous post was at 07:44 AM ----------
or simply run
fastboot boot <enter twrp name>
Click to expand...
Click to collapse
adb and fastboot are different things and are unrelated to each other. He doesn't need adb to flash the recovery.
anujagraj said:
"adb devices" is not working during Setup wizard.
Do you mean to say that I run fastboot boot <enter twrp name> during setup wizard?
Also, alternatively, will flashing a rom without clearing user data help in any way?
Thanks a lot for the help..
Click to expand...
Click to collapse
What happens when you just clear /cache in the stock recovery?
What recovery are you trying to flash?
Lennyz1988 said:
adb and fastboot are different things and are unrelated to each other. He doesn't need adb to flash the recovery.
What happens when you just clear /cache in the stock recovery?
What recovery are you trying to flash?
Click to expand...
Click to collapse
Clear /cache in the stock recovery didn't help. Also, I am trying to flash TWRP recovery 2.8.7.
no, boot phone in fastboot mode ...then run the command
fastboot boot <recovery>
try latest TWRP
bablu048 said:
no, boot phone in fastboot mode ...then run the command
fastboot boot <recovery>
try latest TWRP
Click to expand...
Click to collapse
Hi,
I tried re-unlocking the phone using code and got following message:
(bootloader) Check 'Allow OEM Unlock' in Developer Options.
FAILED (remote failure)
finished. total time: 0.008s
Any workaround?
unlocking bootloader will wipe the data in your phone.
I thought you had unlocked.
what is the problem when you try to setup the phone ? or skip the setup
---------- Post added at 05:15 PM ---------- Previous post was at 05:12 PM ----------
anujagraj said:
Hi,
I tried re-unlocking the phone using code and got following message:
(bootloader) Check 'Allow OEM Unlock' in Developer Options.
FAILED (remote failure)
finished. total time: 0.008s
Any workaround?
Click to expand...
Click to collapse
best option now is flashing the firmware manually without wiping data.
Read this, also read a few comments after it.http://forum.xda-developers.com/showpost.php?p=65715334&postcount=43
bablu048 said:
unlocking bootloader will wipe the data in your phone.
I thought you had unlocked.
what is the problem when you try to setup the phone ? or skip the setup
---------- Post added at 05:15 PM ---------- Previous post was at 05:12 PM ----------
best option now is flashing the firmware manually without wiping data.
Read this, also read a few comments after it.http://forum.xda-developers.com/showpost.php?p=65715334&postcount=43
Click to expand...
Click to collapse
Hi,
Where can I find firmware to flash on my phone?
Also RSDLite is not able to detect phone. Can I enter commands from fastboot?
Thanks!
anujagraj said:
Hi,
Where can I find firmware to flash on my phone?
Also RSDLite is not able to detect phone. Can I enter commands from fastboot?
Thanks!
Click to expand...
Click to collapse
RSD lite needs windows 7.
Yes you have to flash manually then using fastboot commands.
firmware
Just don't use the command to erase user data. Skip it. Open the zip there will be flashfile. xml/servicefile.xml open it , you will find the list of commands to run. Or the commands can be found here.
bablu048 said:
RSD lite needs windows 7.
Yes you have to flash manually then using fastboot commands.
firmware
Just don't use the command to erase user data. Skip it. Open the zip there will be flashfile. xml/servicefile.xml open it , you will find the list of commands to run. Or the commands can be found here.
Click to expand...
Click to collapse
Just to confirm, will any firmware will work or I need to download one specific to my phone/higher version?
Also, any risks of bricking the device while flashing?
anujagraj said:
Just to confirm, will any firmware will work or I need to download one specific to my phone/higher version?
Also, any risks of bricking the device while flashing?
Click to expand...
Click to collapse
If you are on 6.0.1 then flash 6.0.1...better flash the appropriate region firmware.
There is a risk of bricking if you are downgrading and flash old gpt.bin and bootloader
As long as you are flashing proper firmware it's safe thoughi haven't done it but as you can see the comments I linked previously others have done it.
bablu048 said:
If you are on 6.0.1 then flash 6.0.1...better flash the appropriate region firmware.
There is a risk of bricking if you are downgrading and flash old gpt.bin and bootloader
As long as you are flashing proper firmware it's safe thoughi haven't done it but as you can see the comments I linked previously others have done it.
Click to expand...
Click to collapse
Hi,
I have an Indian model and got the following error on flashing contents of XT1562_LUX_RETASIA_DS_6.0_MPD24.65-18.1_cid7_subsidy-DEFAULT_CFC.xml using fastboot:
AP Fastboot Flash Mode (Secure)
failed to validate system image
ERROR: Failed to pass validation, backup to fastboot
Fastboot Reason: Fall-through from charger boot mode
Please help!
Root Moto G5 With CF-AUTO-ROOT
This is depreciated - Please use the latest version of Magisk to root this device
Requirements
Unlocked bootloader
PC setup with fastboot/adb
Instructions
With phone booted goto
Settings > Developer Options (if you haven't got this goto Settings > about phone and click build number until it says you're a developer)
Enable Android debugging
Restart to bootloader
Goto Moto G5 CF-Auto-Root Page
Select firmware and follow instructions on website
Unzip and run root.bat
Note this will only root your phone if the firmware version matches that on the CF-Auto-Root site
If your firmware is not listed you need to upload your boot.img & recovery to the site
You can get these by Flashing twrp recovery - making a backup then extract those files from the backup
Alternatively for stock rom users you can try flashing magisk in twrp recovery
TWRP recovery is available in the Dev section of this device forum
For custom rom users on lineageos flash the lineageos su addon zip then enable root in developer options
If your firmware is not there you can try one anyway or upload your boot.img and recovery.img to the website
https://desktop.firmware.mobi/
not working for me, i can't flash it trough fastboot
woozie.2007 said:
not working for me, i can't flash it trough fastboot
Click to expand...
Click to collapse
User error most likely - no help just saying can't flash - provide output & commands used
I will create my own package & test it when I get a chance then I'll upload the package on the first post
TheFixItMan said:
User error most likely - no help just saying can't flash - provide output & commands used
I will create my own package & test it when I get a chance then I'll upload the package on the first post
Click to expand...
Click to collapse
maybe i don't know how to flash it, is in zip format and i cant flash via fastboot, it is other way to do this?
woozie.2007 said:
maybe i don't know how to flash it, is in zip format and i cant flash via fastboot, it is other way to do this?
Click to expand...
Click to collapse
You don't flash zips in fastboot you flash img files - Unzip the zip you downloaded - following the instructions
i don't know what is better to check when i made the package...sorry man
selinux permissive? is to many option there...if you have time maybe you give me a little hint what to made the package, thank you
---------- Post added 30th September 2017 at 12:10 AM ---------- Previous post was 29th September 2017 at 11:46 PM ----------
i flashed now cf auto root, but supersu and flashfire can't detect root....maybe the package made by me is not good
woozie.2007 said:
i don't know what is better to check when i made the package...sorry man
selinux permissive? is to many option there...if you have time maybe you give me a little hint what to made the package, thank you
---------- Post added 30th September 2017 at 12:10 AM ---------- Previous post was 29th September 2017 at 11:46 PM ----------
i flashed now cf auto root, but supersu and flashfire can't detect root....maybe the package made by me is not good
Click to expand...
Click to collapse
I will look into it but at the moment the website has an internal server error when trying to download the package so I'll have to wait until chainfire fixes it
i made a few package, the server is up....but noone works
woozie.2007 said:
i made a few package, the server is up....but noone works
Click to expand...
Click to collapse
I'm still getting internal server error after selecting the packages & being placed in the queue to download
When it finally works I'll upload it - its chainfires new website & I don't think it's working properly yet
i restore a backup from 27 sept with twrp, its working, but i cant updates ota to security patch august
woozie.2007 said:
i restore a backup from 27 sept with twrp, its working, but i cant updates ota to security patch august
Click to expand...
Click to collapse
You can't flash an ota if
You are rooted
Have changed the system partition
Do not have stock recovery
TheFixItMan said:
You can't flash an ota if
You are rooted
Have changed the system partition
Do not have stock recovery
Click to expand...
Click to collapse
Yes i know that, but this is my big problem, magisk broke my camera if i update ota, now the camera works with magisk, but i want to update ota. I want to change magisk with supersu, but i know the supersu and twrp will change the partition format
woozie.2007 said:
Yes i know that, but this is my big problem, magisk broke my camera if i update ota, now the camera works with magisk, but i want to update ota. I want to change magisk with supersu, but i know the supersu and twrp will change the partition format
Click to expand...
Click to collapse
Iv already given you the answer
Flash twrp
Root with supersu
Flash stock recovery
Use flashfire app from playstore to install ota
now i have twrp installed, i instaled supersu from play store, but i not have root
woozie.2007 said:
now i have twrp installed, i instaled supersu from play store, but i not have root
Click to expand...
Click to collapse
Of course you don't
You need to flash supersu zip in twrp
You just installed the app - you have no su binary - see supersu website
i'll try now
---------- Post added at 03:24 PM ---------- Previous post was at 02:26 PM ----------
i installed fresh all, all system, twrp, dm verity amd supersu, then i download from play store supersu apk and didnt see root, what can i do next?
---------- Post added at 03:34 PM ---------- Previous post was at 03:24 PM ----------
root undetected ((((
woozie.2007 said:
i'll try now
---------- Post added at 03:24 PM ---------- Previous post was at 02:26 PM ----------
i installed fresh all, all system, twrp, dm verity amd supersu, then i download from play store supersu apk and didnt see root, what can i do next?
---------- Post added at 03:34 PM ---------- Previous post was at 03:24 PM ----------
root undetected ((((
Click to expand...
Click to collapse
Can you try this package
Unzip it
Make sure adb is enabled in your dev options in phone settings
Reboot phone to bootloader
Connect usb cable to laptop
Double click on the file root.bat
Wait till its finished - your phone may restart a few times
I would test it but I'm compiling other things at the moment
https://mega.nz/#!At5R0SwI!HKYlA5aWazUAsp18YzkIZlJjSMn1Anz5Pxa0J9kBGm0
thank you, i will test it but not now, i fix the problem with full flash stock firmware, made all updates ota and after that flash twrp, dm verity(this file i forgot to flash everytime) and everytings works now
Unable to flash bootloader
My bootloader is unlocked and I have tried many different methods but nothing is working. I feel that I must be doing something wrong but I have run out of options. I get the following when I flash and don't know if this means it is or isn't correct: -
HTML:
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
downloading 'boot.img'...
OKAY [ 0.501s]
booting...
OKAY [ 0.110s]
finished. total time: 0.616s
I have also tried with different options and get this: -
HTML:
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slot:cache: not found
target reported max download size of 536870912 bytes
sending 'cache' (28384 KB)...
OKAY [ 0.899s]
writing 'cache'...
OKAY [ 0.721s]
finished. total time: 1.622s
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slot:recovery: not found
target reported max download size of 536870912 bytes
sending 'recovery' (11680 KB)...
OKAY [ 0.371s]
writing 'recovery'...
(bootloader) Image not signed or corrupt
OKAY [ 0.421s]
finished. total time: 0.794s
Please manually boot into recovery to continue. This can usually be done
by using the volume keys to select RECOVERY, then pressing the power button.
When I manually boot into recovery mode I get the 'No command' screen.
I am sure that I am selecting the right phone etc, what am I doing wrong?
GuyOxford said:
My bootloader is unlocked and I have tried many different methods but nothing is working. I feel that I must be doing something wrong but I have run out of options. I get the following when I flash and don't know if this means it is or isn't correct: -
HTML:
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
downloading 'boot.img'...
OKAY [ 0.501s]
booting...
OKAY [ 0.110s]
finished. total time: 0.616s
I have also tried with different options and get this: -
HTML:
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slot:cache: not found
target reported max download size of 536870912 bytes
sending 'cache' (28384 KB)...
OKAY [ 0.899s]
writing 'cache'...
OKAY [ 0.721s]
finished. total time: 1.622s
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slot:recovery: not found
target reported max download size of 536870912 bytes
sending 'recovery' (11680 KB)...
OKAY [ 0.371s]
writing 'recovery'...
(bootloader) Image not signed or corrupt
OKAY [ 0.421s]
finished. total time: 0.794s
Please manually boot into recovery to continue. This can usually be done
by using the volume keys to select RECOVERY, then pressing the power button.
When I manually boot into recovery mode I get the 'No command' screen.
I am sure that I am selecting the right phone etc, what am I doing wrong?
Click to expand...
Click to collapse
You are doing nothing wrong - that is the correct output for fastboot
No command in recovery mode means you have stock recovery - nothing wrong there
Note this will only root your phone if the firmware version matches that on the CF-Auto-Root site
If your firmware is not listed you need to upload your boot.img & recovery to the site
You can get these by Flashing twrp recovery - making a backup then extract those files from the backup
Alternatively for stock rom users you can try flashing magisk in twrp recovery
TWRP recovery is available in the Dev section of this device forum
For custom rom users on lineageos flash the lineageos su addon zip then enable root in developer options