I have a Moto E for abt 10 months and today while I was using my phone (actually playing) my phone suddenly hangs so I restarted with long pressing power button but after restart phone went into several bootloop. After around 6 bootloop it went into the homescreen. Then I found that wifi screen always showed "turning wifi on" and I cant turn it off/on. Same thing with bluetooth and the worst part is both sims not working. It said no service
. I browsed here a bit and when I checked IMEI using *#06# both the IMEI shows as null. now
whenever I turn on my phone, it stucks into bootloop for around 10 times before going into homescreen and I dont know how to even turn off the phone as power key only restarting it.
Now please help me how to recover from this problem. the phone is unrooted and I didnt even unlock the bootloader.
EDIT : I even tried factory resetting. it does not help
naveenstuns said:
I have a Moto E for abt 10 months and today while I was using my phone (actually playing) my phone suddenly hangs so I restarted with long pressing power button but after restart phone went into several bootloop. After around 6 bootloop it went into the homescreen. Then I found that wifi screen always showed "turning wifi on" and I cant turn it off/on. Same thing with bluetooth and the worst part is both sims not working. It said no service
. I browsed here a bit and when I checked IMEI using *#06# both the IMEI shows as null. now
whenever I turn on my phone, it stucks into bootloop for around 10 times before going into homescreen and I dont know how to even turn off the phone as power key only restarting it.
Now please help me how to recover from this problem. the phone is unrooted and I didnt even unlock the bootloader.
EDIT : I even tried factory resetting. it does not help
Click to expand...
Click to collapse
I got the same problem today... no wifi, no bluetooth and no network for calls... I didn't realize the last one 'cause i still have internet access vía 3G.
I'll try a factory reset later, I hope it can fix it. If not... I hope someone can help us both.
:crying:
Added:
I just tried a factory reset, but that doesn't fix anything...
I just notice that audio/sounds are not working too... it seems like a hardware malfunction
Even i got the same issue. Tried all the reset option still no luck. Kindly help
NoSaBo said:
I got the same problem today... no wifi, no bluetooth and no network for calls... I didn't realize the last one 'cause i still have internet access vía 3G.
I'll try a factory reset later, I hope it can fix it. If not... I hope someone can help us both.
:crying:
Added:
I just tried a factory reset, but that doesn't fix anything...
I just notice that audio/sounds are not working too... it seems like a hardware malfunction
Click to expand...
Click to collapse
same here
naveenstuns said:
I have a Moto E for abt 10 months and today while I was using my phone (actually playing) my phone suddenly hangs so I restarted with long pressing power button but after restart phone went into several bootloop. After around 6 bootloop it went into the homescreen. Then I found that wifi screen always showed "turning wifi on" and I cant turn it off/on. Same thing with bluetooth and the worst part is both sims not working. It said no service
. I browsed here a bit and when I checked IMEI using *#06# both the IMEI shows as null. now
whenever I turn on my phone, it stucks into bootloop for around 10 times before going into homescreen and I dont know how to even turn off the phone as power key only restarting it.
Now please help me how to recover from this problem. the phone is unrooted and I didnt even unlock the bootloader.
EDIT : I even tried factory resetting. it does not help
Click to expand...
Click to collapse
Yes, I have too this issue and I am searching everywhere for this issue but I haven't find anything.
Please someone help us please......
hpanchal4u said:
Yes, I have too this issue and I am searching everywhere for this issue but I haven't find anything.
Please someone help us please......
Click to expand...
Click to collapse
i think you should try flashing stock 4.4.4
here is the solution
Hi Guys,
here is the solutions:
Please downgrade your lolipop to kitkat
before downgrade your phone you should unlock your bootloader from motorola website (Note: if you unlock your bootloader it will void the warranty)
I have done it and I am using my phone with kitkat very good.
Thanks
ponvarun said:
Even i got the same issue. Tried all the reset option still no luck. Kindly help
Click to expand...
Click to collapse
naveenstuns said:
I have a Moto E for abt 10 months and today while I was using my phone (actually playing) my phone suddenly hangs so I restarted with long pressing power button but after restart phone went into several bootloop. After around 6 bootloop it went into the homescreen. Then I found that wifi screen always showed "turning wifi on" and I cant turn it off/on. Same thing with bluetooth and the worst part is both sims not working. It said no service
. I browsed here a bit and when I checked IMEI using *#06# both the IMEI shows as null. now
whenever I turn on my phone, it stucks into bootloop for around 10 times before going into homescreen and I dont know how to even turn off the phone as power key only restarting it.
Now please help me how to recover from this problem. the phone is unrooted and I didnt even unlock the bootloader.
EDIT : I even tried factory resetting. it does not help
Click to expand...
Click to collapse
Which ROM?
same issue
:crying::crying:
i have flashed my moto e xt1022 with pure stock rom and lost my imei no.
after long searches i am near nothing .. . . .
anyone please help . . .
how to restore my imei no. i even dont have efs backup . . .
:crying::crying::crying::crying::crying:
Guys, I have the same problem with a friend's XT-1022.
And it's stock Android 4.4.4, haven't even flashed it.
Anyone ever find a solution?
[email protected] said:
Guys, I have the same problem with a friend's XT-1022.
And it's stock Android 4.4.4, haven't even flashed it.
Anyone ever find a solution?
Click to expand...
Click to collapse
Anyone looking for a solution, just flash a stock ROM, worked for me after flashing 5.1.1 Stock ROM for XT-1022
naveenstuns said:
I browsed here a bit and when I checked IMEI using *#06# both the IMEI shows as null. now
whenever I turn on my phone, it stucks into bootloop for around 10 times before going into homescreen and I dont know how to even turn off the phone as power key only restarting it.
Click to expand...
Click to collapse
Flash stock rom via fastboot: Ensure your phone's battery is atleast 50% charged. Just charge your phone for 45 mins,ead if yor phones seems dead. You DONT need to unlock bootloader for flashing official firmwares
1. Download and install Motorola device manager
2. Download and extract adb_fastboot.zip to any folder on your pc
3. Download Stock 5.1 rom file for your device model [thanks to lost101] and extract its contents to the same folder where you have adb_fastboot files
4. Reboot your phone to 'bootloader mode'. To do this turn of your phone completely. Hold volume down button and then press and hold power button. Release power button after 4-6 seconds and then release volume down button. Your phone is now in bootloader mode.
5. Connect your phone to pc via a reliable usb cable. Look at your phone screen. It should say 'USB connected'.
6. Now go to the folder where you have extracted all the files. Holding down shift key, Right click on any point on white screen. Then click on 'open command window here' from the menu that appears. Command Prompt will open now
7. On command prompt type
Code:
fastboot devices
and check if it is detecting your device.
8. Now run the following commands in the given sequence
Code:
mfastboot flash partition gpt.bin
mfastboot flash motoboot motoboot.img
mfastboot flash logo logo.bin
mfastboot flash boot boot.img
mfastboot flash recovery recovery.img
mfastboot.exe flash system system.img_sparsechunk.0
mfastboot.exe flash system system.img_sparsechunk.1
mfastboot.exe flash system system.img_sparsechunk.2
mfastboot.exe flash system system.img_sparsechunk.3
mfastboot flash modem NON-HLOS.bin
mfastboot erase modemst1
mfastboot erase modemst2
mfastboot flash fsg fsg.mbn
mfastboot erase cache
mfastboot erase userdata
fastboot reboot
proceed to each command after you get success message on command. If file name of system.img_sparsechunk is different then change the command accordingly. Just ensure to flash all system.img_sparsechunk files
Your phone may take 10-20 mins to turn on the first time. Dont panic this is normal. If it takes more time then power it off by holding power button till it turns off. Power it on after it cools down.
sziraqui said:
Flash stock rom via fastboot: Ensure your phone's battery is atleast 50% charged. Just charge your phone for 45 mins,ead if yor phones seems dead. You DONT need to unlock bootloader for flashing official firmwares
1. Download and install Motorola device manager
2. Download and extract adb_fastboot.zip to any folder on your pc
3. Download Stock 5.1 rom file for your device model [thanks to lost101] and extract its contents to the same folder where you have adb_fastboot files
4. Reboot your phone to 'bootloader mode'. To do this turn of your phone completely. Hold volume down button and then press and hold power button. Release power button after 4-6 seconds and then release volume down button. Your phone is now in bootloader mode.
5. Connect your phone to pc via a reliable usb cable. Look at your phone screen. It should say 'USB connected'.
6. Now go to the folder where you have extracted all the files. Holding down shift key, Right click on any point on white screen. Then click on 'open command window here' from the menu that appears. Command Prompt will open now
7. On command prompt type
Code:
fastboot devices
and check if it is detecting your device.
8. Now run the following commands in the given sequence
Code:
mfastboot flash partition gpt.bin
mfastboot flash motoboot motoboot.img
mfastboot flash logo logo.bin
mfastboot flash boot boot.img
mfastboot flash recovery recovery.img
mfastboot.exe flash system system.img_sparsechunk.0
mfastboot.exe flash system system.img_sparsechunk.1
mfastboot.exe flash system system.img_sparsechunk.2
mfastboot.exe flash system system.img_sparsechunk.3
mfastboot flash modem NON-HLOS.bin
mfastboot erase modemst1
mfastboot erase modemst2
mfastboot flash fsg fsg.mbn
mfastboot erase cache
mfastboot erase userdata
fastboot reboot
proceed to each command after you get success message on command. If file name of system.img_sparsechunk is different then change the command accordingly. Just ensure to flash all system.img_sparsechunk files
Your phone may take 10-20 mins to turn on the first time. Dont panic this is normal. If it takes more time then power it off by holding power button till it turns off. Power it on after it cools down.
Click to expand...
Click to collapse
Dude, I dont know who you are but you helped me give life to my Uncle's dead phone..Your steps are the only one which is so clear in layman terms and not very techie..
Some people post helps but not so clear...Words like "flash it with recovery" "Wipe cache" "TWRP" etc etc dont do any good for people like me who are looking for real help...
But you explained it clearly..Props to you man..Keep up the good work..
I can give the phone to my uncle now with Joy..He will think I'm a genius..Did I mention he has a beautiful daughter? !!!
I got the same problem (as stated below) about a week ago and I have also tried the options of factory reset. And erasing chased memory. But nothing has helped. In addition to this problem I also get at times constant failure messages as
unfortunately the process com.motorola.ccc has stopped
unfortunately the process andriod.launcher has stopped
My Andriod version is KitKat 4.4.4 and I also tried updating it to lollipop
but the update is never successful because of the above reasons...
Please let me know if anyones has a solution to this issue.
-----------------------------------------------------------------------------------------------------------------------------------------------------------
naveenstuns said:
I have a Moto E for abt 10 months and today while I was using my phone (actually playing) my phone suddenly hangs so I restarted with long pressing power button but after restart phone went into several bootloop. After around 6 bootloop it went into the homescreen. Then I found that wifi screen always showed "turning wifi on" and I cant turn it off/on. Same thing with bluetooth and the worst part is both sims not working. It said no service
. I browsed here a bit and when I checked IMEI using *#06# both the IMEI shows as null. now
whenever I turn on my phone, it stucks into bootloop for around 10 times before going into homescreen and I dont know how to even turn off the phone as power key only restarting it.
Now please help me how to recover from this problem. the phone is unrooted and I didnt even unlock the bootloader.
EDIT : I even tried factory resetting. it does not help
Click to expand...
Click to collapse
Psp005 said:
I got the same problem (as stated below) about a week ago and I have also tried the options of factory reset. And erasing chased memory. But nothing has helped. In addition to this problem I also get at times constant failure messages as
unfortunately the process com.motorola.ccc has stopped
unfortunately the process andriod.launcher has stopped
My Andriod version is KitKat 4.4.4 and I also tried updating it to lollipop
but the update is never successful because of the above reasons...
Please let me know if anyones has a solution to this issue.
-----------------------------------------------------------------------------------------------------------------------------------------------------------
Click to expand...
Click to collapse
Just see above your post and theres a detailed solution for flashing the stock firmware, Thats the real factory reset and it will bring even the dead phone to life..I tried it and its successful..just follow the steps and your phone will boot up brand new with no issues..
worked amazinly
josephkarthic said:
Dude, I dont know who you are but you helped me give life to my Uncle's dead phone..Your steps are the only one which is so clear in layman terms and not very techie..
Some people post helps but not so clear...Words like "flash it with recovery" "Wipe cache" "TWRP" etc etc dont do any good for people like me who are looking for real help...
But you explained it clearly..Props to you man..Keep up the good work..
I can give the phone to my uncle now with Joy..He will think I'm a genius..Did I mention he has a beautiful daughter? !!!
Click to expand...
Click to collapse
worked amazinly
works only if a person knows how to do it
thanks dude
sziraqui said:
Flash stock rom via fastboot: Ensure your phone's battery is atleast 50% charged. Just charge your phone for 45 mins,ead if yor phones seems dead. You DONT need to unlock bootloader for flashing official firmwares
1. Download and install Motorola device manager
2. Download and extract adb_fastboot.zip to any folder on your pc
3. Download Stock 5.1 rom file for your device model [thanks to lost101] and extract its contents to the same folder where you have adb_fastboot files
4. Reboot your phone to 'bootloader mode'. To do this turn of your phone completely. Hold volume down button and then press and hold power button. Release power button after 4-6 seconds and then release volume down button. Your phone is now in bootloader mode.
5. Connect your phone to pc via a reliable usb cable. Look at your phone screen. It should say 'USB connected'.
6. Now go to the folder where you have extracted all the files. Holding down shift key, Right click on any point on white screen. Then click on 'open command window here' from the menu that appears. Command Prompt will open now
7. On command prompt type
Code:
fastboot devices
and check if it is detecting your device.
8. Now run the following commands in the given sequence
Code:
mfastboot flash partition gpt.bin
mfastboot flash motoboot motoboot.img
mfastboot flash logo logo.bin
mfastboot flash boot boot.img
mfastboot flash recovery recovery.img
mfastboot.exe flash system system.img_sparsechunk.0
mfastboot.exe flash system system.img_sparsechunk.1
mfastboot.exe flash system system.img_sparsechunk.2
mfastboot.exe flash system system.img_sparsechunk.3
mfastboot flash modem NON-HLOS.bin
mfastboot erase modemst1
mfastboot erase modemst2
mfastboot flash fsg fsg.mbn
mfastboot erase cache
mfastboot erase userdata
fastboot reboot
proceed to each command after you get success message on command. If file name of system.img_sparsechunk is different then change the command accordingly. Just ensure to flash all system.img_sparsechunk files
Your phone may take 10-20 mins to turn on the first time. Dont panic this is normal. If it takes more time then power it off by holding power button till it turns off. Power it on after it cools down.
Click to expand...
Click to collapse
Registered and created an account - Just to write you a thank you note.
The steps that you've given are super perfect. My phone is back up and running now.
Thanks a ton. Sharing is caring and you live up to it. God bless!
Thanks sziraqui.
Add me to your list of very grateful people you've helped. My wife's Moto E was dead in the water with no Wifi. I searched high and low for a solution and was ready to throw in the towel until I saw this thread. Followed your instructions and we have it reactivated and running. Many thanks!
Finally Resolved!!!!!!!!!!!!
Friends don't worry. I also felt very bad about the moto company and product. But its not correct. I have a hope as a android developer I should fix this issue. Finally i done it.
getting remote failure
sziraqui said:
Flash stock rom via fastboot: Ensure your phone's battery is atleast 50% charged. Just charge your phone for 45 mins,ead if yor phones seems dead. You DONT need to unlock bootloader for flashing official firmwares
1. Download and install Motorola device manager
2. Download and extract adb_fastboot.zip to any folder on your pc
3. Download Stock 5.1 rom file for your device model [thanks to lost101] and extract its contents to the same folder where you have adb_fastboot files
4. Reboot your phone to 'bootloader mode'. To do this turn of your phone completely. Hold volume down button and then press and hold power button. Release power button after 4-6 seconds and then release volume down button. Your phone is now in bootloader mode.
5. Connect your phone to pc via a reliable usb cable. Look at your phone screen. It should say 'USB connected'.
6. Now go to the folder where you have extracted all the files. Holding down shift key, Right click on any point on white screen. Then click on 'open command window here' from the menu that appears. Command Prompt will open now
7. On command prompt type
Code:
fastboot devices
and check if it is detecting your device.
8. Now run the following commands in the given sequence
Code:
mfastboot flash partition gpt.bin
mfastboot flash motoboot motoboot.img
mfastboot flash logo logo.bin
mfastboot flash boot boot.img
mfastboot flash recovery recovery.img
mfastboot.exe flash system system.img_sparsechunk.0
mfastboot.exe flash system system.img_sparsechunk.1
mfastboot.exe flash system system.img_sparsechunk.2
mfastboot.exe flash system system.img_sparsechunk.3
mfastboot flash modem NON-HLOS.bin
mfastboot erase modemst1
mfastboot erase modemst2
mfastboot flash fsg fsg.mbn
mfastboot erase cache
mfastboot erase userdata
fastboot reboot
proceed to each command after you get success message on command. If file name of system.img_sparsechunk is different then change the command accordingly. Just ensure to flash all system.img_sparsechunk files
Your phone may take 10-20 mins to turn on the first time. Dont panic this is normal. If it takes more time then power it off by holding power button till it turns off. Power it on after it cools down.
Click to expand...
Click to collapse
E:\XT1022_CONDOR_RETAILDSDS_5.1_LPCS23.13-34.8-3_cid7_CFC.xml>mfastboot.exe flas
h system system.img_sparsechunk.0
target max-sparse-size: 256MB
sending 'system' (242987 KB)...
OKAY [ 9.055s]
writing 'system'...
(bootloader) Failed to erase partition
FAILED (remote failure)
finished. total time: 19.830s
all the earlier commands worked...
plz help
unik_abhi said:
E:\XT1022_CONDOR_RETAILDSDS_5.1_LPCS23.13-34.8-3_cid7_CFC.xml>mfastboot.exe flas
h system system.img_sparsechunk.0
target max-sparse-size: 256MB
sending 'system' (242987 KB)...
OKAY [ 9.055s]
writing 'system'...
(bootloader) Failed to erase partition
FAILED (remote failure)
finished. total time: 19.830s
all the earlier commands worked...
plz help
Click to expand...
Click to collapse
Then flash stock/custom ROM using twrp
Related
Hello I have a problem with my Razr xt910 eu.FR
after a flash via fastboot I have left the black screen that says AP fastboot flash failure
If I put it in recovery and normal powerup select the phone and start working, but if I turn it off and try to turn the screen back I usually flash failure
how do I restore the normal situation
my phone has no root and has the original recovery
Help me
I also tried to give the command fastboot continue but I get the following result
FAILED resume booting <remote unsupported command>
with fastboot erase kpanic instead
C: \ Users \ android-sdk \ tools> fastboot erase kpanic
erasing 'kpanic' ...
(bootloader) Command restricted
FAILED (remote
finished. Total time: 0.010s
What do you recommend?
send it for repair?
the guarantee is no longer valid?
thanks
mate, seriously this is not development...
as much as it pains me to see your problem it does not belong here...
in FASTBOOT
fastboot continue
Notice : wrong section
medo18 said:
in FASTBOOT
fastboot continue
Notice : wrong section
Click to expand...
Click to collapse
fastboot continue don't work for him
He needs to reset the fail status, anyway that should only be possible succeeding a flash.
kholk said:
He needs to reset the fail status, anyway that should only be possible succeeding a flash.
Click to expand...
Click to collapse
What does it say that I do to reset a flash
What should I flash?
Try this :
moto-fastboot flash radio radio.img
Its working with me in Atrix 4G .
I have the similar with topicstarter problem.
Every time I rebooting my device it boots in bootloader mode and I have to manualy boot it Normal boot mode.
I thought there is no solution, but you advised this:
medo18 said:
moto-fastboot flash radio radio.img
Click to expand...
Click to collapse
So please explain me where can i get that radio.img?
Khets said:
I have the similar with topicstarter problem.
Every time I rebooting my device it boots in bootloader mode and I have to manualy boot it Normal boot mode.
I thought there is no solution, but you advised this:
So please explain me where can i get that radio.img?
Click to expand...
Click to collapse
maybe you need someone to get it, or you need to remove battery and insert again.
I have an Atrix 4G ATT. During RSD it failed and sent me to a screen with
"SVF:105:1:2
Failed to boot 0x1000
no os detected, going to rsd mode in 5 seconds
press a key to stop count down
available modes are:
1:rsd
2:flashboot
..."
What caused this was while following http://forum.xda-developers.com/showthread.php?t=1302423, the rsd said failed, i waited till 100% like guide said, and then got this screen.
What can i do to fix this, from each forum i read, i don't understand, or follow old links. I am a noob.
edit: When i Choose fast boot nothing happens, when i check other forums, they have megaupload links (shut down). am i missing something?
I don't know it'll fix the thing or not But you should try this method. It may work.
Skip any steps you have already done.
A. Download a fruitcake from here. http://forum.xda-developers.com/showthread.php?t=1163009
B. Download a radio from that same thread, below the fruitcakes. Or if you prefer, download a different radio.
C. Put them both on your external (or internal if you really want to) SD card.
D. If you haven't, download RomRacer's recovery. Here. http://forum.xda-developers.com/showthread.php?t=1204500
E. Reboot into fastboot mode by holding volume down + power button until Fastboot appears on screen, then hit the Up arrow. This takes you into fastboot mode, I'm assuming you already have fastboot installed. If not, google how to set up fastboot or download moto-fastboot.
F. Make sure the recovery you downloaded above is in the same folder you downloaded fastboot or moto-fastboot to.
G. Connect phone to computer, open command prompt, navigate to fastboot or moto-fastboot folder (cd c:/(where you installed fastboot / moto-fastboot)
H. Type these in, after entering each one hit enter: Fastboot erase system fastboot erase userdata fastboot erase cache
fastboot erase webtop fastboot erase preinstall fastboot erase boot fastboot erase recovery
I. Type Fastboot flash recovery (name of your romracer recovery image)
J. Type fastboot reboot and when it reboots, hold down volume + power then keep hitting down when fastboot appears till you see android recovery, then hit the volume up key.
K. Enter recovery,erase Dalvik Cache under Advanced setting, then flash the new ROM you downloaded. * the fruitcake*. Let it completely do its thing.
L. Now if you've gotten this far, you're on a good path and most likely you wont have to flash the radio you downloaded. If not, you may have to. If none of this matters and after completely erasing all that stuff in fastboot mode you STILL get the same error on boot up I would have to assume it's an actual hardware problem and you will have to get a new phone.
My moto z before using RSD lite flash NPL 25.86-30, then OTA updated to NPL25.86-30.3. It seems that bootloarder is also updated. now I want to re-use RSD lite to flash NPL25.86-30. But RSD has shown an error in flashing GPT.bin, show "FAIL"
Who can help me?:crying:
You can't go back, if the Bootloader got updated.
jump the step of flashing gpt by editing the xml file(delete the line)
Now my device have a very strange question, if I use the battery mod, is unable to shutdown, automatically enter the bootloarder. Do not use the module can shutdown, but the connection charger will automatically enter the bootloarder,can not be charged in the shutdown state.
Sorry,my english is bad.
rakee said:
Now my device have a very strange question, if I use the battery mod, is unable to shutdown, automatically enter the bootloarder. Do not use the module can shutdown, but the connection charger will automatically enter the bootloarder,can not be charged in the shutdown state.
Sorry,my english is bad.
Click to expand...
Click to collapse
start fastboot in the cmd and start the following command
fastboot oem fb_mode_clear
this should solve your bootlader at reboot issue...
treibstoff said:
start fastboot in the cmd and start the following command
fastboot oem fb_mode_clear
this should solve your bootlader at reboot issue...
Click to expand...
Click to collapse
Its work for me,thanks man!:highfive::highfive:
treibstoff said:
start fastboot in the cmd and start the following command
fastboot oem fb_mode_clear
this should solve your bootlader at reboot issue...
Click to expand...
Click to collapse
After the last OTA (july) update has failed, I got an issue very similar, but in my case, everytime I restart or turn off the device, it gets to twrp recovery and I need do restart it on fastboot mode then choose START on side menu to get boot properly. Can you help?
Hi guys,
So I rooted my swift 2x but now I want to unroot it so I can use baking apps. Trouble is I'm having difficulty unrooting.
My method for root was
> Unlock bootloader
> Install TWRP
> Install Supersu
But now I can't unroot. I've tried unrooting via the supersu app but on one try it errored out and nothing changed and on another try when the phone rebooted it got stuck on the white wileyfox screen.
I've also tried to install the reocer image from here https://forum.xda-developers.com/swift-2/how-to/marmite-android-7-1-1-tos118c-fastboot-t3605101 via twrp but then once I reboot after installation from TWRP it gets stuck on the white wileyfox screen after seeing messages that the device is corrupt on a previous screen.
What can I do to unroot?
Thanks!
Return to stock via fastboot... it will fix everything. I had to leave LineageOS because nothing I tried would allow me to use my Banking app now they've really tightened security, thanks to Google's CTS. Shame.
(LOL on the "baking app")
EDIT: This Thread has all the files except the latest. Flash TOS319I and let the phone OTA to TOS373J.
Since you have already done this I thought maybe you might be able to help me with an issue I am having
From your thread I have used the first part of the following thread https://forum.xda-developers.com/showpost.php?p=72827221&postcount=7 - to fastboot "Android_7.1.2_Wileyfox_Swift2_2017_09_07 TOS249H - Signed Fastboot" -
Everything went as it should have (or so it appeared) but when I went to reboot, the new Wiley Fox logo appeared and then looped system errors i.e. "Unfortunately, system UI has stopped" , Unfortunately, the process com.android.phone has stopped etc
Can you give any insight as to my next move please? Would appreciate a noob response
PhilosAnthropos said:
Since you have already done this I thought maybe you might be able to help me with an issue I am having
From your thread I have used the first part of the following thread https://forum.xda-developers.com/showpost.php?p=72827221&postcount=7 - to fastboot "Android_7.1.2_Wileyfox_Swift2_2017_09_07 TOS249H - Signed Fastboot" -
Everything went as it should have (or so it appeared) but when I went to reboot, the new Wiley Fox logo appeared and then looped system errors i.e. "Unfortunately, system UI has stopped" , Unfortunately, the process com.android.phone has stopped etc
Can you give any insight as to my next move please? Would appreciate a noob response
Click to expand...
Click to collapse
Sounds like a problem easily fixed by doing a factory reset, have you tried that?
Just went today to try and factory reset through adb but now there is an "error:no devices found" - exactly the same conditions as yesterday
PhilosAnthropos said:
Just went today to try and factory reset through adb but now there is an "error:no devices found" - exactly the same conditions as yesterday
Click to expand...
Click to collapse
Hmm, is USB debugging on?
USB debugging is needed for adb commands. This setting you find in developer settings and to find and access developer settings you need to tap the version/build number 7 times.
How to Enable USB Debugging Mode on Android <- Check the bottom one #4
Once you do an adb command your phone may prompt you with a connection to pc message to confirm, go ahead and confirm it and do the adb command again.
But.. you need only to get into recovery mode and from there you select and confirm "wipe data/factory reset" and "wipe cache partition". You don't have to do an adb command.
https://www.hardreset.info/devices/wileyfox/wileyfox-swift-2-plus/recovery-mode/ <- I am actually not 100% sure if 5 and 6 are accurate but anyhow this should give you good enough idea on how to access the recovery mode. If in case you not already know this.
All your data will be wiped, make sure to do backup of things you don't want to lose.
May aswell also refer you to my post here, it's just an easy way of doing a fastboot flash.
RavZ75 said:
Hmm, is USB debugging on?
USB debugging is needed for adb commands. This setting you find in developer settings and to find and access developer settings you need to tap the version/build number 7 times.
How to Enable USB Debugging Mode on Android <- Check the bottom one #4
Once you do an adb command your phone may prompt you with a connection to pc message to confirm, go ahead and confirm it and do the adb command again.
But.. you need only to get into recovery mode and from there you select and confirm "wipe data/factory reset" and "wipe cache partition". You don't have to do an adb command.
https://www.hardreset.info/devices/wileyfox/wileyfox-swift-2-plus/recovery-mode/ <- I am actually not 100% sure if 5 and 6 are accurate but anyhow this should give you good enough idea on how to access the recovery mode. If in case you not already know this.
All your data will be wiped, make sure to do backup of things you don't want to lose.
May aswell also refer you to my post here, it's just an easy way of doing a fastboot flash.
Click to expand...
Click to collapse
I flashed stock via fastboot - But it got stuck on Wiley fox logo with process com.android.phone has stopped etc - hence it is not possible to go into the phone and turn on USB debugging, but it was on before I started the process - and I cant really do anything to the phone until I am able to get the PC to recognise the phone again
PhilosAnthropos said:
I flashed stock via fastboot - But it got stuck on Wiley fox logo with process com.android.phone has stopped etc - hence it is not possible to go into the phone and turn on USB debugging, but it was on before I started the process - and I cant really do anything to the phone until I am able to get the PC to recognise the phone again
Click to expand...
Click to collapse
oh I see, and you've tried factory reset and cache wipe from recovery?
That guide I linked to says volume up + power button but I belive it actually is volume down + power button that needs to be pressed, like this. Try both ways, you don't need connection to pc for booting into recovery mode.
But this is different if you have bootloader unlocked, with bootloader unlocked you will be greeted with this (making use of warj04's pic) when you power on your device.
At this screen you press the volume buttons to change boot option from "Start" to "Recovery". Press power button to confirm boot into recovery and your device will reboot and boot into recovery.
This screen will appear a second time before booting into recovery but you need not do anything else, wait 5 seconds or press power button to start boot.
RavZ75 said:
oh I see, and you've tried factory reset and cache wipe from recovery?
That guide I linked to says volume up + power button but I belive it actually is volume down + power button that needs to be pressed, like this. Try both ways, you don't need connection to pc for booting into recovery mode.
But this is different if you have bootloader unlocked, with bootloader unlocked you will be greeted with this (making use of warj04's pic) when you power on your device.
At this screen you press the volume buttons to change boot option from "Start" to "Recovery". Press power button to confirm boot into recovery and your device will reboot and boot into recovery.
This screen will appear a second time before booting into recovery but you need not do anything else, wait 5 seconds or press power button to start boot.
Click to expand...
Click to collapse
I have the bootloader unlocked and it behaves how you have described it but when I try and go into recovery from the options menu (power + volume down) it momentarily goes to a Wiley fox screen, then the loader (the image you added above), and then for a split second the green robot, then the screen blacks-out altogether. From the options menu I can also go to fastboot which also gives me the option to go into recovery but the same sequence starts as described before - recovery appears to be unavailable?
PhilosAnthropos said:
I have the bootloader unlocked and it behaves how you have described it but when I try and go into recovery from the options menu (power + volume down) it momentarily goes to a Wiley fox screen, then the loader (the image you added above), and then for a split second the green robot, then the screen blacks-out altogether. From the options menu I can also go to fastboot which also gives me the option to go into recovery but the same sequence starts as described before - recovery appears to be unavailable?
Click to expand...
Click to collapse
Yea by now I recommend you to redo the flash through fastboot again, In the thread post you linked to I only see 3 lines of fastboot flash cammands.
To fully fastboot flash a rom there needs to be a few other lines aswell, I'll list all the lines here.
Code:
fastboot flash modem NON-HLOS.bin
fastboot flash dsp adspso.bin
fastboot flash devcfg devcfg.mbn
fastboot flash aboot emmc_appsboot.mbn
fastboot flash keymaster keymaster.mbn
fastboot flash rpm rpm.mbn
fastboot flash sbl1 sbl1.mbn
fastboot flash splash splash.img
fastboot flash tz tz.mbn
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash cache cache.img
fastboot flash system system.img
Lastly, "fastboot reboot" to reboot your device.
RavZ75 said:
Yea by now I recommend you to redo the flash through fastboot again, In the thread post you linked to I only see 3 lines of fastboot flash cammands.
To fully fastboot flash a rom there needs to be a few other lines aswell, I'll list all the lines here.
Code:
fastboot flash modem NON-HLOS.bin
fastboot flash dsp adspso.bin
fastboot flash devcfg devcfg.mbn
fastboot flash aboot emmc_appsboot.mbn
fastboot flash keymaster keymaster.mbn
fastboot flash rpm rpm.mbn
fastboot flash sbl1 sbl1.mbn
fastboot flash splash splash.img
fastboot flash tz tz.mbn
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash cache cache.img
fastboot flash system system.img
Lastly, "fastboot reboot" to reboot your device.
Click to expand...
Click to collapse
You were a great help, thanks - I didnt think this was going to end well. I was wondering if I re-lock the bootloder will that intermitent screen dissapear? If so, How do I re-lock it?
PhilosAnthropos said:
You were a great help, thanks - I didnt think this was going to end well. I was wondering if I re-lock the bootloder will that intermitent screen dissapear? If so, How do I re-lock it?
Click to expand...
Click to collapse
Yes that screen will go away if you re-lock bootloader and if there isn't a dm-verity issue present.
To fix dm-verity issue you need USB debugging on and this command:
Code:
adb reboot "dm-verity enforcing"
If there is no dm-verity issue, great. No need for this command then.
The unlock and lock bootloader commands you do in fastboot.
The unlock commands are:
Code:
fastboot flashing unlock
fastboot flashing unlock_critical
So the re-lock commands are as simple as this:
Code:
fastboot flashing lock
fastboot flashing lock_critical
I am glad I could be of help
I have a Moto G Play 2021 (XT2093-4) (another one), that I made a mistake to relock the bootloader after I had it unlocked. I don't have access to the OS on the phone anymore. Previously I had the treble floss installed on it. I don't have TWRP installed. The only thing I have access to is fastboot. I realise I might have completely bricked this phone but I thought I ask here to see if there is any way to unlock the OEM again just using the fastboot.
the fastboot screen on the phone has a menu option to go into recovery mode. stock recovery might be able to restore your phone to working condition.
volume-down + power buttons > fastboot mode > volume button to 'recovery' option > power button to execute. if your recovery screen is broken with the 'no command' message, hold down the power button and quickly press and release the volume-up button. that should get you to the working recovery screen where you can try to factory reset your phone.
strumcat said:
the fastboot screen on the phone has a menu option to go into recovery mode. stock recovery might be able to restore your phone to working condition.
volume-down + power buttons > fastboot mode > volume button to 'recovery' option > power button to execute. if your recovery screen is broken with the 'no command' message, hold down the power button and quickly press and release the volume-up button. that should get you to the working recovery screen where you can try to factory reset your phone.
Click to expand...
Click to collapse
Thanks, but I think my phone is completely messed up now. If you can believe it, I can't even get to recovery mode. I can get to fastboot and then find the recovery mode and click to go to it but then it just starts the fastboot again. I'm basically stuck in fastboot forever. It's just weird cause there's nothing wrong with the hardware. Thanks again.
if you have nothing working on your phone but fastboot mode, that might still be enough to rescue your phone. boot it to the fastboot screen, connect it to a pc that has the fastboot program installed, open a terminal window on the pc wherever fastboot is, and type 'fastboot devices'. if your phone answers with its serial number, you'rr probably able to flash a whole stock rom to it piece by piece. get a stock rom from somewhere like lenovo, using their lmsa program, or just download the right one from lolinet or somewhere. unzip it. then, for instance, to flash the boot.img to your phone you would type 'fastboot flash boot boot.img'. that would replace your possibly broken boot partition with a known good one. then 'fastboot reboot' to see if that helped. there are tutorials on the net for flashing the rest of the rom. be sure to read one, because all of the flash commands aren't that straightforward.
strumcat said:
if you have nothing working on your phone but fastboot mode, that might still be enough to rescue your phone. boot it to the fastboot screen, connect it to a pc that has the fastboot program installed, open a terminal window on the pc wherever fastboot is, and type 'fastboot devices'. if your phone answers with its serial number, you'rr probably able to flash a whole stock rom to it piece by piece. get a stock rom from somewhere like lenovo, using their lmsa program, or just download the right one from lolinet or somewhere. unzip it. then, for instance, to flash the boot.img to your phone you would type 'fastboot flash boot boot.img'. that would replace your possibly broken boot partition with a known good one. then 'fastboot reboot' to see if that helped. there are tutorials on the net for flashing the rest of the rom. be sure to read one, because all of the flash commands aren't that straightforward.
Click to expand...
Click to collapse
Sorry for the really late reply. I tried what you said, but it fails right at the (fastboot flash partition gpt.bin) command and the output I get is:
Sending 'partition' (37 KB) OKAY [ 0.002s]
Writing 'partition' (bootloader) Validating 'gpt.default.xml'
(bootloader) flash permission denied
(bootloader) Cancelling 'gpt.default.xml'
FAILED (remote: '')
fastboot: error: Command failed
It keeps saying flash permission denied. I have another exact same phone with an unlocked bootloader and I did the same on that one and I was able to flash a stock ROM to it. I've tried every RETCA and RETUS on this site: https://mirrors.lolinet.com/firmware/motorola/guamna/official/ but it fails with the same error. I'm going to try all the rest later but it's a lot to download for now.
Thanks again for the help!