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.
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.
First of all phone data is crucial. Unfortunately I don't have any backup.
So after hardware maintenance (not even replacing any part, just gluing it back) phone seems to boot like normal but only wallpaper shows and only working feature is power button.
Power button event is being triggered and it shows normal shutdown/reset menu which works except record screen and screenshot option. Camera button triggers phone vibration but not showing anything on the screen.
Flashboot and fastboot mode are both working.
I tried to boot TWRP but it doesn't let me:
Using command:
PHP:
fastboot boot recovery.img
Always outputs that it's downloading boot.img
After that:
Scenario A - Happens on Windows:
Error saying "too many links"
Scenario B - Happens on Ubuntu:
Phone after boot.img flashing starts to boot and error occurs saying No device found technically it's correct because phone is starting to boot too early in my opinion.
Using command:
PHP:
fastboot flash recovery recovery.img
Outputs:
Command not allowed
Trying to unlock bootloader:
PHP:
fastboot -i {Code from Sony}
Outputs:
Command not allowed as well
Sony PC Companion when connecting phone with this wallpaper stuck issue keeps telling me to unlock phone (phone have just simple lockscreen without any pattern or password) but I am unable to do anything. I tried to swipe left or right but it doesn't work.
I ran out of ideas Please 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
Device: Nokia 3.2
Os: Android 10
So I accidentally flash boot without backups or anything to recover, so when I boot up my device it show up TWRP and I turned it off for like a whole day and turned it back up again it stuck on fastboot mode and I can't exit it, I tried to go to recovery mode, reboot, turned it off for a while. Then I tried flashing it with Qfil but the tool can't even detect device, I installed the drivers and still it "No port available" , and I tried to manually flash it with fastboot and after that I tried this command fastboot -w flashall , again no luck, it said that "fastboot: error: ANDROID_PRODUCT_OUT not set", and I can't do much with this phone that has no images and I don't know much stuff because I'm new to this, so anyone have an idea how to fix this, thanks.