Hello,
I have a Wileyfox Spark since few months. At the beggining it was running with CM. Two weeks ago, I made the update from CM to Android Nougat, but after giving a try I dislike it. So I have tried (for the first time) to flash another ROM (CM or Lineage) but it is a pain.
As I was unable to root my device, I have used adb and fastboot to install twrp.
Here are the commands I enter :
Code:
adb reboot-recovery
fastboot flash recovery twrp.img
fastboot reboot
Then I press to volume down button to display the recovery menu but, instead of displaying the menu, the device boot again and again until I'm tired and I release the button. Then the phone boot normaly on Android...
For information, if I apply all these actions except the fastboot flash I can enter the recovery menu.
Am I wrong or missing something ?
Thanks for your help.
Slepwobo said:
Hello,
I have a Wileyfox Spark since few months. At the beggining it was running with CM. Two weeks ago, I made the update from CM to Android Nougat, but after giving a try I dislike it. So I have tried (for the first time) to flash another ROM (CM or Lineage) but it is a pain.
As I was unable to root my device, I have used adb and fastboot to install twrp.
Here are the commands I enter :
Code:
adb reboot-recovery
fastboot flash recovery twrp.img
fastboot reboot
Then I press to volume down button to display the recovery menu but, instead of displaying the menu, the device boot again and again until I'm tired and I release the button. Then the phone boot normaly on Android...
For information, if I apply all these actions except the fastboot flash I can enter the recovery menu.
Am I wrong or missing something ?
Thanks for your help.
Click to expand...
Click to collapse
Same here,but try releasing the Power-Button once it starts, helped for me booting into TWRP anyways.
BTW, how'd you manage to root that thing before? I am not able to do jacksh**t.
thanks a lot!
I can help you to get back booting up that phone again as it was. Is it still with that problem? I suspect you entered fastboot, unlocked bootloader and flashed TWRP on bootup the phone needed the stock recovery in order to factory reset due to the unlocking of bootloader. This way it boots to TWRP and runs the Open Recovery Script to decrypt and reset the device. This becomes impossible at certain progress and thus phone keeps on going to TWRP instead of booting. I shall address the issue well if you're still in need of this. I'm using the same phone also here
Sent from my Wileyfox Spark using XDA mobile app
Related
Hi all,
I have a Xiaomi Redmi 3 and I tried updating it to Android 6.0 today using a very helpful article from cyanogenmods
It was all going so well until the end when I came to flash the ROM, I downloaded the wrong one!! (I needed the ARM64).
Anyway my phone restarted and now I can't seem to rectify my mistake!
I can't access the recovery mode (Power button and volume up) It just shows me the Xiaomi sign and stays there but I can access Fastboot (Power and volume down) and it can communicate with the PC via CMD.
I'm super new to this and I've been looking online for the past 5 hours with no luck so maybe someone can help me out.
I tried fastboot update open_gapps-arm64-6.0-aroma-20160814.zip
But I got...
archive does not contain 'android-info.txt'
archive does not contain 'android-product.txt'
error: update package has no android-info.txt or android-product.txt
Any suggestions? I've found a few other threads but they're way too techy for me and I couldn't understand what to do!
Thanks in advance
I've realised that my initial post was pretty vague and I don't think I used the correct terminology so I'll explain in the hope that someone may be able to help.
So I wanted to update from 5.1.1 to 6.0.
I found an article from Cyanogenmods and I downloaded the Redmi 3 TWRP recovery, the ROM for Redmi 3 Cyanogenmods 13 and the GApps.
I installed the TWRP recovery,
Copied the GApps and CyanogenMod ROM ZIP to my device
Booted into recovery mode and backed up my data using TWRP,
Wiped data factory reset, Cache partition, Dalvik Cache and Formatted the System partition,
I flashed the custom ROM and it all worked well,
I then went to flash the GApps and thats when it said that I had installed the wrong version (I needed the ARM64 not the 32).
It then restarted and I've been stuck in a bootloop.
I can access fastboot.
I can't get into recovery, the phone just goes to the Xiaomi sign then gets stuck on the Cyanogenmod logo.
A few times it looked like it was doing an update but it was all in Chinese so I couldn't understand it then it briefly went to what looked like a set up screen but then rebooted and got stuck on the logo screen again.
Any help would be great;y appreciated.
I only bought this phone a few days ago, my stupid mistake for wanting to upgrade!!
Ramah.h said:
Hi all,
I have a Xiaomi Redmi 3 and I tried updating it to Android 6.0 today using a very helpful article from cyanogenmods
It was all going so well until the end when I came to flash the ROM, I downloaded the wrong one!! (I needed the ARM64).
Anyway my phone restarted and now I can't seem to rectify my mistake!
I can't access the recovery mode (Power button and volume up) It just shows me the Xiaomi sign and stays there but I can access Fastboot (Power and volume down) and it can communicate with the PC via CMD.
I'm super new to this and I've been looking online for the past 5 hours with no luck so maybe someone can help me out.
I tried fastboot update open_gapps-arm64-6.0-aroma-20160814.zip
But I got...
archive does not contain 'android-info.txt'
archive does not contain 'android-product.txt'
error: update package has no android-info.txt or android-product.txt
Any suggestions? I've found a few other threads but they're way too techy for me and I couldn't understand what to do!
Thanks in advance
Click to expand...
Click to collapse
if i was in your situation i'd probably go fastbootmode > EDL > then flash official dev rom from miui site(ido). from there'd id redo everything unlocking bootloader,flashing twrp,etc.
check out this post:
http://forum.xda-developers.com/redmi-3/development/redmi-3-pro-spacex-rom-t3406919
it has a "How to Unbrick Redmi 3 ? " on the first page.
helped me alot, hope it unbricks ur phone too! cheers!
have you unlocked your bootloader?, its very risky to change to custom rom when your bootloader is locked, if its already unlocked, all you have to do is go to en.miui.com and download official rom for redmi 3 and flash it using Miflash
Edl mode is the best bet to get back to stock. Vol up and down while plugging in if i recall, from an off state. I couldn't get it from fastboot.
Lets try this for reach to TWRP.
First press volume up and down button after press power button and wait.
Phone is going to restart and you see mi icon very short time and screen is going black, immediately release all buttons and wait. You have to reach recovery with this combination.
Open a terminal/command prompt and navigate to where you have the TWRP file. Put phone in fastboot mode and enter this command: "fastboot boot (name_of_TWRP.img)".
Then when you're in recovery, just flash the new Gapps.
Hi!
I have a OnePlus X and the year after I bought it, I flashed TWRP and installed Lineage OS. Since then, I've flashed many custom roms on my phone. A few weeks back, I decided to flash Resurrection Remix. The battery life on my phone with resurrection was pathetic so I assumed it could be fixed by flashing a custom kernel (franco kernel). I downloaded franco kernel, copied it to my SD card and powered off my phone.
Instead of pressing the VOLUME DOWN and POWER button simultaneously to enter TWRP, I pressed the VOLUME UP and POWER button by accident and went into Fastboot mode. When in Fastboot mode, I pressed the VOLUME DOWN and POWER button thinking my phone would boot into recovery, but it got stuck in a bootloop.
Now my phone can boot only into fastboot mode by pressing the volume up+power button. Any other combination of buttons and it goes into a bootloop.
All this is completely my fault and I would do anything to try and fix it.
Is my phone soft bricked or hard bricked? ( I have a feeling that it is soft bricked).
I've downloaded the android SDK and Minimal adb and fastboot on my pc. I'm able to run fastboot commands, but when I type 'fastboot oem unlock', I get an error saying
"FAILED (remote: oem unlock is disabled)". I've tried 'fastboot flashing unlock' too, but the screen just says "...". Hence, I'm not able to flash TWRP. I tried flashing even the stock recovery but it wouldn't work.
Is there any other way to unlock the bootloader?
I haven't tried the Mega unbrick guide for a hard bricked OnePlus X yet, since I'm able to boot into fastboot mode. Should I give it a shot?
And lastly, can I recover my phone from this mess or is it permanently bricked?
I would appreciate any help.
Thank you!
Sounds very similar to my situation. I did end up following that guide to get mine going again. The link is broken to get the recovery tool, the 2nd one below is the "minimal" version which isn't supposed to wipe data. That is the one that worked for me. I would backup any data if you can first, no guarantee it wont wipe it. Mine wouldn't boot into the stock rom after, but at least it would get to the stock bootloader (VolDOWN + PWR). From there I was able to adb sideload the stock rom (Install from USB). This completely restored it to stock.
23santosh24 said:
Hi!
I have a OnePlus X and the year after I bought it, I flashed TWRP and installed Lineage OS. Since then, I've flashed many custom roms on my phone. A few weeks back, I decided to flash Resurrection Remix. The battery life on my phone with resurrection was pathetic so I assumed it could be fixed by flashing a custom kernel (franco kernel). I downloaded franco kernel, copied it to my SD card and powered off my phone.
Instead of pressing the VOLUME DOWN and POWER button simultaneously to enter TWRP, I pressed the VOLUME UP and POWER button by accident and went into Fastboot mode. When in Fastboot mode, I pressed the VOLUME DOWN and POWER button thinking my phone would boot into recovery, but it got stuck in a bootloop.
Now my phone can boot only into fastboot mode by pressing the volume up+power button. Any other combination of buttons and it goes into a bootloop.
All this is completely my fault and I would do anything to try and fix it.
Is my phone soft bricked or hard bricked? ( I have a feeling that it is soft bricked).
I've downloaded the android SDK and Minimal adb and fastboot on my pc. I'm able to run fastboot commands, but when I type 'fastboot oem unlock', I get an error saying
"FAILED (remote: oem unlock is disabled)". I've tried 'fastboot flashing unlock' too, but the screen just says "...". Hence, I'm not able to flash TWRP. I tried flashing even the stock recovery but it wouldn't work.
Is there any other way to unlock the bootloader?
I haven't tried the Mega unbrick guide for a hard bricked OnePlus X yet, since I'm able to boot into fastboot mode. Should I give it a shot?
And lastly, can I recover my phone from this mess or is it permanently bricked?
I would appreciate any help.
Thank you!
Click to expand...
Click to collapse
Surely your bootloader is already unlocked isn't it?
You don't actually say what happens when you try to reboot into recovery using fastboot commands. Does that fail too? What happens when you try to flash twrp again? You don't actually say.
That's what I thought too. It would just say 'recovery.img' not found or something like that. But, I followed the Mega unbrick guide and was able to install the stock ROM through the stock recovery. My OPX is alive again!
i'm stuck here. the phone does not go into recovery at all .. stuck on oneplus logo .. I don't know what to do .. any ideas?
---------- Post added at 09:20 AM ---------- Previous post was at 08:24 AM ----------
I managed to get it alive again with this guide
Hi, so I flashed TWRP recovery and booted into it immediately. However, I forgot to flash the lazyflasher zip and rebooted straight away. Now the device is stuck at the logo and I can't seem to get to fastboot or recovery mode using the command line. I read a few other threads similar to my issue but apparently, they could access fastboot mode and I can't. Am I missing something?
ProBlast said:
Hi, so I flashed TWRP recovery and booted into it immediately. However, I forgot to flash the lazyflasher zip and rebooted straight away. Now the device is stuck at the logo and I can't seem to get to fastboot or recovery mode using the command line. I read a few other threads similar to my issue but apparently, they could access fastboot mode and I can't. Am I missing something?
Click to expand...
Click to collapse
Have you tried pressing Volume plus + power button to boot into recovery or Volume minus + power button to boot into fastboot mode?
Solution
It also happened to me but I booted into twrp and flashed an custom rom and also the lazy flasher.zip after couple of minutes it booted up. It may help you
HI,
I inherited this phone. ( D6503 )
Fixed a few hardware problems, now looking at software improvements.
I have unlocked the bootloader , but for the life of me I cannot get a recovery on this phone??
I have previoiusly done flashing on nokia, motorola and Nexus, but I am having no luck with this sony
I am able to connect using ADB, and can get to fastboot, but it stops there.
Issuing '' fastboot boot twrp.img'' ( to try and boot temporarily to twrp ) gives me a blank screen.
issuing ''fastboot flash recovery twrp.img'' does the same.
I cannot get a bootloader screen at all, even using the key combinations.
I cannot boot any recovery at all.
Is there someone here who can put me out of my misery
I am not looking to perform anything fancy, I just want to flash the latest lineage to see how it performs
Many Thanks in advance.
pootler.
Anybody???
I have rooted the z2 by dropping down to 5.11, installed the twrp app, then flashed recommended version of twrpl
Then when I power off the phone, and press the power and volume down buttons, instead of booting into twrp after 7 or so seconds, it just reboots after abour 2-3 seconds???
Can anybody help?-------please
I have even tried rooting , then installing twrp by either 1) fastboot or 2) twrp app.
I then installed NDR utils, to reboot to recovery - it still reboots to main system??
HEEELLPP !
I also tried flashing TWRP with 1) fastboot and 2)the twrp app,
I then installed NDR utils ( i have root ) , and it still wont boot into recovery, just straight into system???
HEELLPP!!
Thread closed on request of OP @pootler
Hi Community,
I read some posts how to fix my Problem, but i cant go to a service Point.
So I was using the Evolution X for a long Time (Installed with TWRP 3.1.0).
And now i wanted to change to the Nusantara Project (Vanilla), I did a clean Flash, everything worked i could access the System.
Than i had problems installing Play Store, so i rebooted into Recovery via the System. But now im Stuck in the Loop.
Can i Somehow connect my Phone to the PC and Reset?
Can someone tell me if i Hard/soft bricked my phone ?
Just a little advice, would be really appreciated.
Thanks a lot
Go to TWRP, wipe system, cache, data and dalvik. Now flash nusantra and whichever GApps are recommended for it (if there are no recommendations then use OpenGApps, make sure the architecture is correct). Now wipe dalvik and restart. Sometimes, certain roms begin to bootloop if you boot into the rom first, then try to install gapps later.
If you still have issues, just reflash the stock rom.
I cant access the TWRP anymore, im just stuck on the Bootloader, no matter how i turn on The Phone (Volume Up + Power ON ), (Volume Down + Power), (All 3 Buttons)
Nothing works anymore i dont understand ....
Im searching the net but i cant go to fastboot or something else, its just keeps on rebooting ...
So it's bootlooping, but you cant access recovery?
When the screen turns off, press the key combo and it should go to recovery.
Your best bet is to take it to a service centre, but if that really isn't possible for you, then wait for its battery to drain completely, then when you plug in the charger, instead of turning the phone on, press the key combo to enter the recovery. From there, wipe and flash some other OS.
I've also heard that certain versions of TWRP don't support some roms, leading to a bootloop. In that case, you'll have to use orangefox recovery to flash the rom (orangefox is flashable via twrp)
Yes its Bootlooping.
When i turn it on, on the Left Corner "Recovery Mode" blinks for one second. Than the usual Text appears:
"Orange State
Your Device has been unlocked and cant be trusted
Your Device will boot in 5 Seconds".
So after a couple of seconds (around 10-20 sec)
It turns off and immediately on again. I Just can turn it OFF when i hold all 3 Buttons.
Than i try starting it with Volume up + Power / Volume down + Power, But i cant access Recovery or TWRP.
So i should wait til the battery gets low and try it again ?
Like i said, my custom Rom (Evolutionx) and TWRP just worked fine. I dont know man ...
Well since your bootloader is unlocked, try flashing the stock rom again. Look for a tutorial and follow it.
Hi I managed to unbrick my device with this guide, and im back on a stock rom
Unbrick
i ran following commands to get to my custom rom:
I run adb reboot bootloader,
add executed following commands.
(Pitch Black recovery 3.1)
- adb reboot bootloader
- fastboot flash recovery recovery.img
-fasboot reboot recovery
It just hang up and booted after a while into the normal system.
But im not able to get to the recovery menu ?
When I restart and hold Volume up + Power, i go in a loop and the phone keeps restarting over and over again.
what have i Fu**ed up ?
Do i need another recovery tool ?
sorry guys, i appreciate your help a lot tho !
EDIT: Is my bootloader unlocked ?
I can access via "adb reboot bootloader" the phone
and on the blackscreen on the phone it is written:
oppo verfiy pass
fastboot_unlock_verify ok
Update:
So i tried some Stuff and i got Red State. No Problem i Unbricked it once again and now im on Stock Android 10.
Now im Trying to enable the bootloader again.
I downloaded the In Depth Test_Realme_6.apk but i keep getting the Error that i should update the system.
So should i update the system ?
I cant find a CURRENT Tutorial to make this work, please help...
If you cant find a tutorial for your version, why not downgrade back to a previous one if possible.