I was on Neutrino 2.5, I flashed to 2.5p (without wiping).
It wasn't working as I wanted so I went in to recovery to reflash the google apps zip.
After that I'm now stuck in a boot cycle loop and I can't even boot in to recovery mode. When I try to enter recovery it says "Entering Android Recovery Mode" then the screen just goes blank.
Really sorry to make this my first post but I'm kinda freaking out right now. Don't have any idea how to recover from this.
rodabi said:
I was on Neutrino 2.5, I flashed to 2.5p (without wiping).
It wasn't working as I wanted so I went in to recovery to reflash the google apps zip.
After that I'm now stuck in a boot cycle loop and I can't even boot in to recovery mode. When I try to enter recovery it says "Entering Android Recovery Mode" then the screen just goes blank.
Really sorry to make this my first post but I'm kinda freaking out right now. Don't have any idea how to recover from this.
Click to expand...
Click to collapse
flash the recovery again using fastboot
Thanks for the reply. So my problem so is that I'm trying to boot in to RSD mode but it get the message "Battery is too low to flash".
I'm trying to charge the battery but whenever i plug it in to charge phone starts up and ends up in the boot cycle, and the battery doesn't end up charging.
How can i force the phone not to turn on when I plug it in to the wall charger?
Ok, I was able to McGyver a usb charger from an old cable and I got the battery charged enough where it would enter fastboot.
However... now I can't get either of my laptops to recognize the phone in fastboot.
I attach the phone to the usb port, turn the phone on and hold the volume down button. I press the volume up button when fastboot appears, the message "Starting Fastboot protocol support" appears and then nothing happens. Windows just sits there, the phone just sits there...
If I do moto-fastboot devices at the command prompt there is no serial.
Any thoughts?
Well, normally nothing happens until you issue a fastboot command. I usually boot into fastboot mode first, THEN connect the phone & open a command line, etc.
What happens if you do the above and type "fastboot devices"? Does it see your phone then?
Ok, so I tried your method, and installing some different windows drivers and now windows does recognize the phone!
For the record, I am on windows xp and currently i'm using driver version 2.0.40 (same problem with 2.0.53).
Now windows isn't able to install the fastboot drivers, it comes up as an unrecognized device. Is there a way to manually install the fastboot drivers?
Although it's recognized by windows, issuing the moto-fastboot devices command still returns blank.
Hii I have a chinese yxtel g905 android mobile. I have rooted it and changed the build. prop file. After rebooting it the phone is not booting. It is just powering on and immediately after the boot animation is completed it is turning off and it also don't have fastboot mood or recovery option.I have tried this by long pressing all the possible combinations of buttons. So someone tell me friends is there any solution for such a problem?? Like feeding new build. prop file into the device or anything like that.
Some devices show no signs of activity in fastboot mode.
It might look like that the phone is switched off but it would actually be in fastboot mode.
To check, try power + volume up/volume down/both then connect the phone to the PC (with all the necessary tools and drivers) and type
Code:
fastboot devices
Into the command prompt.
It will show a list of all devices that are in fastboot mode and connected to the PC.
If you are able to confirm that the phone is now in fastboot, you can proceed to flash the stock ROM (given that you already have it) to your device.
Sent from my Xiaomi HMNote1W using Tapatalk
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
Hi guys,
This Is my first post so I hope I do it correctly. As the title says I am having problems with fastboot on my Acer Iconia One 10 B3-A40. I have enabled developer settings on my device and turned on the setting to unlock OEM. The problem is when I try to run the tablet in fastboot mode to unlock the OEM through ADB commands. When connected to my computer and running the command "adb devices" it shows my device Id and that it is connected. I then run the command "adb reboot-bootloader" to which the tablet switches off and makes the chime that it was disconnected from the computer and makes another chime and connects back onto the computer, the screen on my tablet remains blank with no indication it is in fastboot mode. When I run the command "fastboot devices" my device id shows up again that it is connected. When I originally tried to flash a patched boot image of my stock firmware it went through the process and failed mid way through saying it couldn be done cos the device was locked. After that I googled a bit to see what to do so that’s when I realised OEM unlock was to be switched on in developer settings and also using ADB commands. After returning to fast boot mode I ran the command "fastboot oem unlock" the 3 dots come up on command prompt to show the process is going but nothing happens on my device. Nothing will happen if I press the power button or the volume down button but if I press the volume up bottom, on command prompt it shows OKAY and then the amount of seconds it took to complete, the time changes based on how quick or long i take to press the volume up button but the device remains locked. I have being trying to find a solution for days and have searched everything i could find before making this post. It would be greatly appreciated if someone could help.
Hi, My Nokia 1 (TA-1047) is now in "No Command" mode.
I installed TWRP recovery previously and tried to root but failed. Then I installed stock recovery and phone started normally. As the phone started normally, I locked OEM through Fastboot mode and disabled OEM unlocking from "Developer Option".
But while installing "system update" from "Settings", it showed error and went to "No Command" mode.
Now I'm unable to flash anything through Fastboot mode because the OEM is locked. Also I'm unable to change OEM unlocking from "Developer Option" as the phone is not starting.
Is there any option to unlock OEM without the help of "Developer Option"?
salmanvai said:
Hi, My Nokia 1 (TA-1047) is now in "No Command" mode.
I installed TWRP recovery previously and tried to root but failed. Then I installed stock recovery and phone started normally. As the phone started normally, I locked OEM through Fastboot mode and disabled OEM unlocking from "Developer Option".
But while installing "system update" from "Settings", it showed error and went to "No Command" mode.
Now I'm unable to flash anything through Fastboot mode because the OEM is locked. Also I'm unable to change OEM unlocking from "Developer Option" as the phone is not starting.
Is there any option to unlock OEM without the help of "Developer Option"?
Click to expand...
Click to collapse
Edit. Okay, ignore most of what i said down there as after re-reading your post you seem to have a grasp on fastboot, the no command bit still applies though i think
"No Command" mode
If your talking about the recovery with the android image in the background, then there might still be hope, for some reason, the recovery starts up in this mode, showing the "no cammand" message, its fiddly, but you have to press the power button and either volume up or volume down repeatedly, in the end i was button spamming all the buttons and eventually the recovery menu showed up. Carefull to stop pushing buttons when the menu shows up as the buttons are how you navigate(v+,v-) and choose options(power button)
Whether that gives you any options i dont know, you could try a factory reset from the recovery menu, i suppose, or try the posted ota in the other thread if nokia has`nt released official firmware, although im not sure if you can use stock recovery to flash unofficial firmware, best bet is to try and boot into fastboot and use adb on another computer to flash the firmware that way, assuming the firmware files are available.
Most android devices have a way to boot into recovery or fastboot/bootloader using hardware keys
Quick google found this (works?)
Power off
Connect Micro USB to computer.
"In the next step hold down Volume Down + Power key for a short while"
Let go of the buttons when fastboot comes up
Using the computer with adb installed, go to a command terminal and type "fastboot devices" without quotes, you`ll know everythings working if your the device is listed in terminal after typing that command. From there look up fastboot flashing firmware or something to that extent, this is assuming you managed to find the correct firmware for your device and have it stored in your computer
I`d be real carefull here with fastboot, flashing wrong image file could make things much worse, at least it seems you can boot to recovery, so hopefully a factory reset fixes things, use fastboot as last resort i.e if its new job is a paperweight, as i dont think theres any particular guide on doing this specifically for the nokia 1, but i havent checked thouroughly so i could be wrong, take a look and see..............
And let us know if/how you managed to get it working
Goodluck