Database Info

[Resolved] Stuck at boot screen in recovery

I have a commtiva z71 variant- Videocon V7500 Evolve.
When I boot it in recovery it's stuck at the boot screen.
It's booting properly and is rooted to cm 7.1 (2.3.7).
I flashed cwm lot of times but no luck.:crying:
I am a new to android.
Please help!!!

So you can boot your phone normally, but you can't boot on recovery...hm and you said that you "flashed" CWM many times? Well then I'm going to give you an alternative way to install CWM recovery. So
1. Go in bootloop. Well I guess you know how but I will describe the way just in case. Bootloop is when the phone is on the loading screen with the hourglass. And to enter in bootloop usually (On my phone atleast) I have to hold down the "volume down" and the "End call button" Red one, and press the power up.
2. Connect your phone with your pc via usb.
3. Download the attached file below.
4. Extract the file you downloaded and navigate from pc in the "fastboot" folder. Double click the "install-recovery-windows.bat" file.
After doing these steps you should have CWM 5.0.2.7 ready to boot.

mojito0 said:
So you can boot your phone normally, but you can't boot on recovery...hm and you said that you "flashed" CWM many times? Well then I'm going to give you an alternative way to install CWM recovery. So
1. Go in bootloop. Well I guess you know how but I will describe the way just in case. Bootloop is when the phone is on the loading screen with the hourglass. And to enter in bootloop usually (On my phone atleast) I have to hold down the "volume down" and the "End call button" Red one, and press the power up.
2. Connect your phone with your pc via usb.
3. Download the attached file below.
4. Extract the file you downloaded and navigate from pc in the "fastboot" folder. Double click the "install-recovery-windows.bat" file.
After doing these steps you should have CWM 5.0.2.7 ready to boot.
Click to expand...
Click to collapse
It's probably a bad flash, he needs to wipe/factory reset and then flash a rom again.

d3ac0n_luna said:
It's probably a bad flash, he needs to wipe/factory reset and then flash a rom again.
Click to expand...
Click to collapse
Well I recommended this way because it is guarantee sucess since that's how I have installed all the revocery modes that have passed from my phone.

thanks
mojito0 said:
So you can boot your phone normally, but you can't boot on recovery...hm and you said that you "flashed" CWM many times? Well then I'm going to give you an alternative way to install CWM recovery. So
1. Go in bootloop. Well I guess you know how but I will describe the way just in case. Bootloop is when the phone is on the loading screen with the hourglass. And to enter in bootloop usually (On my phone atleast) I have to hold down the "volume down" and the "End call button" Red one, and press the power up.
2. Connect your phone with your pc via usb.
3. Download the attached file below.
4. Extract the file you downloaded and navigate from pc in the "fastboot" folder. Double click the "install-recovery-windows.bat" file.
After doing these steps you should have CWM 5.0.2.7 ready to boot.
Click to expand...
Click to collapse
Thanks for your help I will try it and inform you asap.
Earlier it was working properly but suddenly it stopped.
Sorry for late reply
I have another question that the link that you gave me is of cwm 5.0.2.7 but my phone supports cwm 2.5.1.3.
Hope to look for a positive reply.
Thanks again
D

What do you mean by "supports" ?
Which version of recovery you should install on your phone just has to do with what Rom you want to install, or to be more accurate which version of android your ROM has.
So you should install your recovery mode depending on what you want.
1. AmonRA Recovery 1.6.2 - Link (for android 2.1)
2. V1.8.1.4 recovery - Link (For Android 2.2)
4. Recovery CMW Ascend - Link (For android 2.3+ )
5. Recovery 4.0.1.5 - Link (2.2-2.3+)
6. Recovery 5.0.2.3 - Link And instalation Link (for android 2.3+)
7. Recovery 5.0.2.6 - Link (For android 2.3+)
8. Recovery 5.0.2.7 - Link (For android 2.3+)
The example above is taken from this thread: http://forum.xda-developers.com/showthread.php?t=1608000 In the second post.
So to be quick, there is no restriction on your recovery you can use whichever you need to.

mojito0 said:
What do you mean by "supports" ?
Which version of recovery you should install on your phone just has to do with what Rom you want to install, or to be more accurate which version of android your ROM has.
So you should install your recovery mode depending on what you want.
1. AmonRA Recovery 1.6.2 - Link (for android 2.1)
2. V1.8.1.4 recovery - Link (For Android 2.2)
4. Recovery CMW Ascend - Link (For android 2.3+ )
5. Recovery 4.0.1.5 - Link (2.2-2.3+)
6. Recovery 5.0.2.3 - Link And instalation Link (for android 2.3+)
7. Recovery 5.0.2.6 - Link (For android 2.3+)
8. Recovery 5.0.2.7 - Link (For android 2.3+)
The example above is taken from this thread: http://forum.xda-developers.com/showthread.php?t=1608000 In the second post.
So to be quick, there is no restriction on your recovery you can use whichever you need to.
Click to expand...
Click to collapse
I tried everything step by step correctly but still no luck.
Do I need to remove the previously flashed recovery??
Also when I tried to do a factory reset, the phone rebooted and got stuck at boot logo. Please help!!
Thanks in advance.

Finally!!
I updated my Rom manger to the latest version and flashed the recovery again and it worked!!

spice mi-270 stuck on logo
Abhinav2 said:
I updated my Rom manger to the latest version and flashed the recovery again and it worked!!
Click to expand...
Click to collapse
sir spice mi-270 brick ho gaya he,jab on kerta hu to spice ke logo per ruck jata he,

[RECOVERY][BOOT][ROOT][VFD-1400] Vodafone Prime Tab 7

DISCLAIMER: I WILL NOT BE HELD LIABLE FOR ANY DAMAGE TO YOUR DEVICE BY USING THIS METHOD
Warning: this will only work with the older firmware (Android 6.0.1/1BEBFDB1 )
What this will achieve:
You will flash a modified boot image that runs selinux in permissive mode.
You will flash a custom recovery that allows you to root the device.
After you are done, your userdata will most likely not be encrypted anymore. You can re-enable encryption in the system settings.
DOWNLOAD
1. Install the usb drivers that come with the device, in /system/etc/USBDriver.iso.
They are also in the download package, in USBDriver/.
Run Setup.vbs.
Also install SUGAR QCT_SP v11.1.2 Setup.exe from the download package.
2. Connect your device to your computer and boot it into EDL mode (enable usb debugging).
adb.exe reboot edl
3. Run SUGAR QCT_SP (use credentials from download package), select VF1400 device and click on the upgrade button.
It will download the latest official firmware update into "C:\Program Files (x86)\SUGAR QCT_SP_Gotu2\bin\VF1400-2AVXXXX" (VF1400-2AVDDE1, for me).
After the download is done and the flashing started, make a copy of the VF1400-2AVXXXX folder to your Desktop.
4. While the flashing is going on, we can start to modify out copy of VF1400-2AVXXXX.
In it should be a folder, most likely called 1BEBFDB1 (version number of the update).
Inside that folder should be the .mbn files we care about: B1BEB0B0CD00.mbn (boot image) and R1BEB0B0CD00.mbn (recovery image).
Possibly they will be called differently, but I assume the boot image always starts with B and the recovery with R.
You can check "C:\Program Files (x86)\SUGAR QCT_SP_Gotu2\tool\logs\Sugar_XXXXXXXX.log" to make sure which file is which.
Replace B1BEB0B0CD00.mbn with boot.img from the download and R1BEB0B0CD00.mbn with recovery.img.
5. After the flash is done and the device rebooted, put it in edl mode again (after enabling usb debugging).
adb.exe reboot edl
6. Now, *before* we start SUGAR QCT_SP again, copy the VF1400-2AVXXXX into "C:\Program Files (x86)\SUGAR QCT_SP_Gotu2\bin"
7. Start SUGAR QCT_SP, select VF1400 device and hit upgrade.
Congratulations! After flashing and after the next reboot you are running with selinux in permissive mode and you can flash SuperSU from the recovery.
Now copy the latest SuperSU flashable zip into your internal storage and install it from recovery.
The recovery used is CM-13.0, device tree based on https://github.com/zwliew/android_device_xiaomi_land
Being compiled with prebuilt kernel from boot.img.

Works great! Thank you

Cool! Thanks alot!

Hi fused#1,
thanks for this, have you tried to install Xposed on this device after rooting it?
Best regards,
misterfx

Hi,
i've now tested and installed xposed.
You need this files: xposed-v87-sdk23-arm.zip, XposedInstaller_3.1.1.apk and for safety the xposed-uninstaller-20160829-arm.zip.
Install the xposed-v87-sdk23-arm.zip with recovery, after reboot install the XposedInstaller_3.1.1.apk.
Best wishes,
misterfx

TWRP recovery
Hello.
All work as expected, thanks a lot for that.
I wonder if someone have manage to install TWRP recovery.
I mainly interesting of NANDroid Backup i can take with TWRP recovery.
How can i do that?
Thanks at advance.

Hello,
is there any way to get ntfs oder exfat support on the vodafone tab prime 7 ?
at the moment, it is original, without rom changes.

Hi, I tried your guide today, but it failed at flashing the alternative bootloader and recovery. System was not able to boot anymore after flashing the second time with your altered files.
Display only showed "powered by android" and nothing else happened. Luckily I found out that you are able to switch back into EDL mode when this happens:
- Shut down device (disconnect any cable and press power until display switches off)
- Press Vol+ AND Vol- for about 10 seconds and then insert USB cable
-> "powered by android" label flashes up and then display goes black and voila you are in EDL mode again
---------------------
Here comes my question:
Is it possible that your bootloader and/or recovery are incompatible with latest FW version? Could you have a look at the current bootloader and recovery to get selinux in permissive mode again? I attached the original bootloader and recovery that was downloaded with SUGAR QCT_SP.

Hi,
quite possible.
I wasn't even aware of the new firmware version. Obviously this only works with the old firmware. I will make that clear in the original post.
What firmware/android version is it? Maybe I'll look into that today or tomorrow.
Cheers
edit: I'm not even being offered the new firmware. Can you upload all of it somewhere?
gandharva said:
Hi, I tried your guide today, but it failed at flashing the alternative bootloader and recovery. System was not able to boot anymore after flashing the second time with your altered files.
Display only showed "powered by android" and nothing else happened. Luckily I found out that you are able to switch back into EDL mode when this happens:
- Shut down device (disconnect any cable and press power until display switches off)
- Press Vol+ AND Vol- for about 10 seconds and then insert USB cable
-> "powered by android" label flashes up and then display goes black and voila you are in EDL mode again
---------------------
Here comes my question:
Is it possible that your bootloader and/or recovery are incompatible with latest FW version? Could you have a look at the current bootloader and recovery to get selinux in permissive mode again? I attached the original bootloader and recovery that was downloaded with SUGAR QCT_SP.
Click to expand...
Click to collapse

Hi,
it seems there is again a new fw, files named like R1BEJ0J0CD00.mbn, with security patch level of April 2017. A user flashed this with the root-patch, but he has no wifi anymore.
Thanks for a update
Best wishes,
MrFX

The procedure works, but I can not install from Supersu.zip recovery mode. I tried many versions but I always get this error:
E:filed to veryfy whole-file signature
E:signature verification failed
Istallation aborted.
Can someone help me

Hey @fused#1 , i have a problem. after flashing and rooting my wifi does not work. do you know why?

x.0ldB0y.x said:
Hey @fused#1 , i have a problem. after flashing and rooting my wifi does not work. do you know why?
Click to expand...
Click to collapse
I don't think this is compatible with the latest update for the device. If you are running thatthat could be the reason. It's possible they updated the radio firmware or whatever the **** it's called these days...

Hi fused#1,
have you a hint, i've now a 2nd device with the old fw (and saved old firmware files), but sugar_qct always do a update and downloads the new firmware... is it possible to flash the old, saved files?
Update: got it, renamed all old fw files to the new names, copied they to the new created directory (replaced new fw), and sugar_qct installed the old fw with the new file names.
Thanks,
MrFX

Hey misterfx,
can u do an tutorial, how u did it to flash the old fw?
I tryed many things but he doesnt accept the old files (and i dont know the new folder-name).
Would help many guys i think, thanks ^^

Hi,
you can download the new fw with sugar_qct (but while downloading, unplug the tab)... you now have the new folder name and the files inside it.
Rename ALL old firmware files (from backup) to the new names and copy they to the new fw folder and replace all files.
Then exit sugar_qct and start it again, it will find the "new" files... make upgrade.
Good luck,
MrFX
Neeschar said:
Hey misterfx,
can u do an tutorial, how u did it to flash the old fw?
I tryed many things but he doesnt accept the old files (and i dont know the new folder-name).
Would help many guys i think, thanks ^^
Click to expand...
Click to collapse

df
thank you

TWRP
Someone can find TWRP for VFD1400?

Vdf 1400 Old firmware
Would someone please upload the vdf1400 old firmware before the update of April 2017!!
I would like to install that Rom instead..
WiFi is not working while using this method for the new firmware..
Thanks

Vdf 1400 Old firmware
Anyone has a link for the old firmware VF1400-2AVDDE1 ....
Thanks in advance

HOW-TO: Going back to Stock ROM/Recovery on Zenfone 3 ZE552KL/ZE520KL

Found this how-to guide and thought it might be nice to have it on site here in XDA. This is to go back to Stock ROM and Recovery. I know a lot of the roms right now are pretty experimental so here's a guide to go back to stock if you need a more solid daily driver for now. Anyway, onto the guide, but first, the sources:
Credit goes to Pedro Armindo over at: https://eusouandroid.co/instalacao-rom-original-zenfone-3-android-7-0-ou-6-0/
There's also a video here: Revert Zenfone 3 to Stock
HOW-TO: Go back to Stock Rom on ZE552KL/ZE520KL
Download the Original Rom
1. First things first, we need to download the original rom zip from ASUS for either Android 6.0 or 7.0. Go to the ASUS site and download the one that corresponds to your phone. The latest firmware for ZE552KL is WW-14.2020.1708.56:
Zenfone 3 ZE552KL - Download Original ROM
Zenfone 3 ZE520KL - Download Original ROM
2. Download the ROM, put it inside your SD (memory card) and put the SD in ZenFone. If you do not have a memory card, get one!
Install the Original Recovery
1. Download the original recovery for you ZenFone 3. Get the Recovery for the ROM you just downloaded eg. If you downloaded WW-14.2020.1708.56, donwload the corresponding recovery.
Download Original Recovery
2. Download the RootKit zip file that includes fastboot and extract it somewhere: Zenfone 3 Rootkit
3. Copy the recovery.img and boot.img to that folder from the zip you downloaded in Step #1.
4. Turn off your ZenFone 3 and turn on MODE Download (Fast Boot), to do this hold Volume Up + Power Button for 3 seconds.
5. Plug your Zenfone 3 into the computer.
6. In the RootKit folder, hold Shift and right-click anywhere on the screen and select Open Command Window here.
7. The next command will install Recovery Original, type:
Code:
fastboot flash recovery recovery.img
8. Now install the Original Boot, type:
Code:
fastboot flash boot boot .img
9. After that, wait for the success message to hold the power off button until Zenfone 3 reboots;
Installing the Original ROM
1. Turn on Recovery Mode by holding Volume Down + Power Button
2. You will be in the original Recovery.
3. Navigate with the volume buttons to Install update from SD.
4. Select the ROM you downloaded and wait for the installation to finish.
5. Go back and do the wipes
Code:
Wipe Data Factory Reset
Wipe Cache Partition
5. Restart and the Original Zenfone 3 Rom will be installed.

when i do the <fastboot flash boot boot.img> and reset go into recovery it shuts down instantly can u help had to <fastboot flash recovery twrp.img> again

CLIIV3 said:
when i do the <fastboot flash boot boot.img> and reset go into recovery it shuts down instantly can u help had to <fastboot flash recovery twrp.img> again
Click to expand...
Click to collapse
Did you make sure the boot.img was not corrupt. Maybe try downloading and flashing it again? Sounds odd.

CLIIV3 said:
when i do the <fastboot flash boot boot.img> and reset go into recovery it shuts down instantly can u help had to <fastboot flash recovery twrp.img> again
Click to expand...
Click to collapse
maybe a mismatched recovery/kernel version.
Which version of android are you running? Easiest way to test is just to flash a newer stock Rom. Since you have TWRP, do a full nandroid back up and then flash the latest nougat Rom and it should overwrite recovery. If recovery now works, extract the recovery partition, flash TWRP, restore your data backup and then restore your recovery backup.

got it done now just had to get the right rom for the phone and flashed it over on twrp but know it said it was rooted and then kinda just took itself off of it when doing root check its taking around 30secs to tell me unrooted when before it would tell me if it wqs or wasent in a few seconds

I have done every thing correctly, in original recovery when i press "install update from sdcard" i get "Couldent mount /sdcard" and thats it. iam stuck.
(BTW there is no sd card installed, only internal memory)
how can i resolve this?

UnKnOwN-1 said:
I have done every thing correctly, in original recovery when i press "install update from sdcard" i get "Couldent mount /sdcard" and thats it. iam stuck.
(BTW there is no sd card installed, only internal memory)
how can i resolve this?
Click to expand...
Click to collapse
try to use adb sideload

I used an external sdcard and all is working, thanks ?

Bootloader open.
ZE552KL bootloader relock isn't working.

Hi,
I would like to revert to stock but i cannot find the original recovery for my ZE520KL (ASUS_Z017D) because on your mega link there is only the original recovery for the Z012D_WW_14.2020.1708.56
Could you add "Z017D_WW_14.2020.1708.56" or indicate which one to use please ?

kyle_l88 said:
Found this how-to guide and thought it might be nice to have it on site here in XDA. This is to go back to Stock ROM and Recovery. I know a lot of the roms right now are pretty experimental so here's a guide to go back to stock if you need a more solid daily driver for now. Anyway, onto the guide, but first, the sources:
Credit goes to Pedro Armindo over at: https://eusouandroid.co/instalacao-rom-original-zenfone-3-android-7-0-ou-6-0/
There's also a video here: Revert Zenfone 3 to Stock
HOW-TO: Go back to Stock Rom on ZE552KL/ZE520KL
Download the Original Rom
1. First things first, we need to download the original rom zip from ASUS for either Android 6.0 or 7.0. Go to the ASUS site and download the one that corresponds to your phone. The latest firmware for ZE552KL is WW-14.2020.1708.56:
Zenfone 3 ZE552KL - Download Original ROM
Zenfone 3 ZE520KL - Download Original ROM
2. Download the ROM, put it inside your SD (memory card) and put the SD in ZenFone. If you do not have a memory card, get one!
Install the Original Recovery
1. Download the original recovery for you ZenFone 3. Get the Recovery for the ROM you just downloaded eg. If you downloaded WW-14.2020.1708.56, donwload the corresponding recovery.
Download Original Recovery
2. Download the RootKit zip file that includes fastboot and extract it somewhere: Zenfone 3 Rootkit
3. Copy the recovery.img and boot.img to that folder from the zip you downloaded in Step #1.
4. Turn off your ZenFone 3 and turn on MODE Download (Fast Boot), to do this hold Volume Up + Power Button for 3 seconds.
5. Plug your Zenfone 3 into the computer.
6. In the RootKit folder, hold Shift and right-click anywhere on the screen and select Open Command Window here.
7. The next command will install Recovery Original, type:
Code:
fastboot flash recovery recovery.img
8. Now install the Original Boot, type:
Code:
fastboot flash boot boot .img
9. After that, wait for the success message to hold the power off button until Zenfone 3 reboots;
Installing the Original ROM
1. Turn on Recovery Mode by holding Volume Down + Power Button
2. You will be in the original Recovery.
3. Navigate with the volume buttons to Install update from SD.
4. Select the ROM you downloaded and wait for the installation to finish.
5. Go back and do the wipes
Code:
Wipe Data Factory Reset
Wipe Cache Partition
5. Restart and the Original Zenfone 3 Rom will be installed.
Click to expand...
Click to collapse
Obrigado por dar meus créditos. Mas a pasta do MEGA com o Recovery esta offline. Você tem esses arquivos?
Thanks. But this folder on MEGA is offline. Do you have this files?

is there any way of doing this without and SD Card ?

boot and recovery
https://mega.nz/#F!LIhwiCia!b_pyuHXS9E7f2VbyXcLyXA
Rom
For ZE552KL
http://dlcdnet.asus.com/pub/ASUS/Ze...2.1095520231.1509020682-1437112090.1509020682
For ZE520KL
http://dlcdnet.asus.com/pub/ASUS/Ze...8.1095520231.1509020682-1437112090.1509020682

Link for stock recovery is dead

angeloamorato said:
Link for stock recovery is dead
Click to expand...
Click to collapse
https://mega.nz/#F!LIhwiCia!b_pyuHXS9E7f2VbyXcLyXA

I want to downgrade from latest stock to a previous version. Do I really need to install the recovery from the previous version?

jpeg725 said:
I want to downgrade from latest stock to a previous version. Do I really need to install the recovery from the previous version?
Click to expand...
Click to collapse
yes

I've installed TWRP & donwgraded to Android 6.
Now I want to upgrade to 7.0 because it supports VOLTE... do I really need to rollback twrp to the original recovery?

bibile said:
I've installed TWRP & donwgraded to Android 6.
Now I want to upgrade to 7.0 because it supports VOLTE... do I really need to rollback twrp to the original recovery?
Click to expand...
Click to collapse
yes

Stock recovery not working.
I have changed the ROM to my Asus Zenfone 3 ZE552KL many times. Tried again this morning,and last night.Failed.
Long story,please be patience with me.
- I managed to get the latest ROM from: https://www.asus.com/ro/Phone/ZenFone-3-ZE552KL/HelpDesk_Download/ (actually i got it from the english version) and installed the latest using the stock recovery.
- Previously i had root on my phone by flashing with TWRP, SuperSu. With the latest firmware from the official Asus site, SuperSu is not working anymore. I tried different versions of Supersu (flash versions and app versions) nothing worked. I was unable to get root back on my phone. For me root is very important.
- If i try to install stock rom's using TWRP 3.02. i can't. TWRP 3.0.2 does not recognize my sd-card, i can only copy rom's into internal storage. NO stock rom (even the old ones from 2016) will install on twrp 3.02.
If i install TWRP 3.1.0 or TWRP 3.1.1 i can access sd-card and install all the rom's. Installing is successful but it will boot about 5 times until i get message "your device has failed verification and may not work properly . The device will shutdown in 10 seconds"
- The solution that i found 1 month ago, is to flash stock recovery, and install using stock recovery a stock rom from asus website. I tried to do this last night & this morning. Failed to do so. Reason: no stock recovery works anymore. You can find stock recoveries here : https://www.asus.com/zentalk/thread-88883-1-1.html I also tried to ask for help on that forum, but it won't let me post in that thread.
- I had an old stock recovery, but i lost it. I need a stock recovery that will work. After i flash the stock recovery it gets stuck at "powered by Android" it does not continue from there.
- I can flash back custom TWRP recovery, but even if i install official stock rom it wont boot. I need a working stock recovery, or any solution.
I am stuck . Please help me!

Wileyfox Spark X

Hi all,
This is not the right forum, but I didn't see one specifically for Spark X models, so I'm sorry.
A friend of mine has a Wileyfox Spark X device, which was bootloader unlocked, had TWRP 3.0.2 installed and was running on the original firmware (6.0.1) but rooted and xposed installed.
Now an update came out for Android 7. To update the device, I put back the original firmware and recovery, started doing the upgrades and all went smooth.
Device is up and running on Android 7, however when I now try to install TWRP again, it won't work.
(fastboot flash the TWRP recovery (same version as before - 3.0.2) seems to work ok. I then go to pull the battery after flashing, put battery back, and start recovery by pressing vol down and power.
I see the device going to a black screen, then reboot and keeps doing this as long as I keep the vol down pressed. Once I release the device continues normal boot and goes into Android.
I assume this has to do with a change in Android 7?
Seems I can get TWRP working again, if I flash the original boot image, however then ofcourse the Android boot doesn't work anymore. (additionally once in TWRP, it seems /system cannot be mounted anymore and TWRP thinks no system is installed)
So in short, I believe I should get a newer TWRP version that is compatible with Android 7. I tried the different versions available on twrp.me (up to 3.1.1.0) however to no avail. None works with the latest android.
As such, the device is able to run in android 7, but without root. (no adb root option in developer options, adb root doesn't work either, kingroot etc also no go)
Does anyone have any options that I can still try? or could help me with a proper TWRP version that should work? (I did find some TWRP recoveries on 4pda (russian website) for Spark + that claim to be for Android 7, but those didn't work either))
Thanks !

@Asansi
I'm sorry I can't help you, but may I ask how you rooted the phone? I can't get mine to be properly rooted.

I can help you with any problem. I'm a senior person in that model since I have been using it ever since. If you could like
Sent from my Wileyfox Spark using XDA

HackerAce said:
I can help you with any problem. I'm a senior person in that model since I have been using it ever since. If you could like
Sent from my Wileyfox Spark using XDA
Click to expand...
Click to collapse
Apologies for ressurecring a zombie thread but, OP has a spark X and you have a Spark, so it would appear that you SENIOR person in that model failed at the very first hurdle.
Am still wonderng if there is an sign of a 7.0 compatible twrp for spark X? Don't suppose anyone has a link to the latest Spark X firmware either?

TWRP versions
Asansi said:
Hi all,
This is not the right forum, but I didn't see one specifically for Spark X models, so I'm sorry.
A friend of mine has a Wileyfox Spark X device, which was bootloader unlocked, had TWRP 3.0.2 installed and was running on the original firmware (6.0.1) but rooted and xposed installed.
Now an update came out for Android 7. To update the device, I put back the original firmware and recovery, started doing the upgrades and all went smooth.
Device is up and running on Android 7, however when I now try to install TWRP again, it won't work.
(fastboot flash the TWRP recovery (same version as before - 3.0.2) seems to work ok. I then go to pull the battery after flashing, put battery back, and start recovery by pressing vol down and power.
I see the device going to a black screen, then reboot and keeps doing this as long as I keep the vol down pressed. Once I release the device continues normal boot and goes into Android.
I assume this has to do with a change in Android 7?
Seems I can get TWRP working again, if I flash the original boot image, however then ofcourse the Android boot doesn't work anymore. (additionally once in TWRP, it seems /system cannot be mounted anymore and TWRP thinks no system is installed)
So in short, I believe I should get a newer TWRP version that is compatible with Android 7. I tried the different versions available on twrp.me (up to 3.1.1.0) however to no avail. None works with the latest android.
As such, the device is able to run in android 7, but without root. (no adb root option in developer options, adb root doesn't work either, kingroot etc also no go)
Does anyone have any options that I can still try? or could help me with a proper TWRP version that should work? (I did find some TWRP recoveries on 4pda (russian website) for Spark + that claim to be for Android 7, but those didn't work either))
Thanks !
Click to expand...
Click to collapse
I've tried TWRP 3.0.2-0 (i.e. latest from https://dl.twrp.me/porridgek3/): it flashes Ok but it won't boot up afterwards. I've tried 3.0.2-0 but as you say "it seems /system cannot be mounted anymore and TWRP thinks no system is installed)". After letting it finish, Root Checker (not unsurprisingly) says that device is not rooted. Have you progressed with this issue? BTW I've emailed TWRP Support (from their web page) asking if they have a working version.

Same problem here, It's pretty annoying. My sister's getting this same phone (on Android 6) soon so I might just make a full backup with TWRP on it and somehow restore it on my phone.

Systemless Root
I can't decide whether to try the rooting method given in https://android.stackexchange.com/questions/160130/how-do-i-install-systemless-supersu-in-samsung
The method is:
Sometimes the need for a systemless installation of SuperSU is not detected by the installation script, to force this to occur follow the following steps.
Start TWRP 3.0 or higher on the device
Go to Advanced - Terminal
In the terminal, enter echo SYSTEMLESS=true>>/data/.supersu
Press Enter
Exit to the TWRP main menu
Flash the current SuperSU as per normal
When flashing SuperSU, you should see in the TWRP recovery log screen mentions of system-less installation and patching of the boot image.
Has anyone had experience of this method?

Resurrection! This post shall LIIIIVE!
No, seriously tho, does anyone have any updates on the issue? Or could at least point me in the right direction to root a Wileyfox Spark X? At this point, any help is much appreciated, since I have not been able to get ANY method working for me.
Thanks a lot
Sent from my Wileyfox Spark X using XDA Labs

Systemless Root
ScreamingSteve said:
Resurrection! This post shall LIIIIVE!
No, seriously tho, does anyone have any updates on the issue? Or could at least point me in the right direction to root a Wileyfox Spark X? At this point, any help is much appreciated, since I have not been able to get ANY method working for me.
Thanks a lot
Sent from my Wileyfox Spark X using XDA Labs
Click to expand...
Click to collapse
Steve,
Have you tried the method detailed in post #7?

johnaaronrose said:
Steve,
Have you tried the method detailed in post #7?
Click to expand...
Click to collapse
I am afraid not, since I can't install TWRP. One info would help me out a lot tho: would an Android-Downgrade (from 7.0 to CM13) help with installing TWRP and rooting?
Steps taken earlier:
quite literally everything (that would make sense even remotely)
Steps taken today:
- Downloading TWRP 3.2.1-0 (https://twrp.me/wileyfox/wileyfoxsparkx.html)
- fastboot-unlocking the bootloader (no issues)
- trying to install TWRP (no issues there either)
- when trying to reboot straight to recovery, I don't get past the bootlogo, suggesting to me that either the install or TWRP was corrupted.
Any help one might get?
Thanks a lot?

TWRP
ScreamingSteve said:
I am afraid not, since I can't install TWRP. One info would help me out a lot tho: would an Android-Downgrade (from 7.0 to CM13) help with installing TWRP and rooting?
Steps taken earlier:
quite literally everything (that would make sense even remotely)
Steps taken today:
- Downloading TWRP 3.2.1-0 (https://twrp.me/wileyfox/wileyfoxsparkx.html)
- fastboot-unlocking the bootloader (no issues)
- trying to install TWRP (no issues there either)
- when trying to reboot straight to recovery, I don't get past the bootlogo, suggesting to me that either the install or TWRP was corrupted.
Any help one might get?
Thanks a lot?
Click to expand...
Click to collapse
The only version that I had success with was 3.0.2 from https://dl.twrp.me/porridgek3/"]https://dl.twrp.me/porridgek3/[/URL]
Even then, It's all hit & miss getting into TWRP:
1. If I do anything after flashing (e.g. booting as normal), I have to go into fastboot & flash TWRP again.
2. Once I have flashed TWRP (i.e. still in fastboot mode), I can't leave fastboot mode. Also, the phone will not switch off unless I remove the battery and put it back in after approx 10 seconds.
3. Even then it often refuses to load TWRP i.e. it goes into the Android Boot menu.
AlwaysLivid suggested that you can boot to TWRP by executing "fastboot boot recovery.img" (where recovery.img is the TWRP img file renamed) on MSDOS Prompt / Terminal according to whether you're using Windows or a Linux distro (e.g. Ubuntu which I use). Presumably this would be after you have taken the battery out for a few seconds before inserting it again and have then booted into the appropriate mode with the Volume Down & Power buttons held down.

johnaaronrose said:
The only version that I had success with was 3.0.2 from https://dl.twrp.me/porridgek3/"]https://dl.twrp.me/porridgek3/[/URL]
Even then, It's all hit & miss getting into TWRP:
1. If I do anything after flashing (e.g. booting as normal), I have to go into fastboot & flash TWRP again.
2. Once I have flashed TWRP (i.e. still in fastboot mode), I can't leave fastboot mode. Also, the phone will not switch off unless I remove the battery and put it back in after approx 10 seconds.
3. Even then it often refuses to load TWRP i.e. it goes into the Android Boot menu.
AlwaysLivid suggested that you can boot to TWRP by executing "fastboot boot recovery.img" (where recovery.img is the TWRP img file renamed) on MSDOS Prompt / Terminal according to whether you're using Windows or a Linux distro (e.g. Ubuntu which I use). Presumably this would be after you have taken the battery out for a few seconds before inserting it again and have then booted into the appropriate mode with the Volume Down & Power buttons held down.
Click to expand...
Click to collapse
Thanks a lot, I'll try your method, the explicit call to boot the TWRP image could really help.
Thanks for your extended explanation tho, showed me some new ways to eventually get this stuff to work.
Sent from my Wileyfox Spark X using XDA Labs

johnaaronrose said:
I can't decide whether to try the rooting method given in https://android.stackexchange.com/questions/160130/how-do-i-install-systemless-supersu-in-samsung
The method is:
Sometimes the need for a systemless installation of SuperSU is not detected by the installation script, to force this to occur follow the following steps.
Start TWRP 3.0 or higher on the device
Go to Advanced - Terminal
In the terminal, enter echo SYSTEMLESS=true>>/data/.supersu
Press Enter
Exit to the TWRP main menu
Flash the current SuperSU as per normal
When flashing SuperSU, you should see in the TWRP recovery log screen mentions of system-less installation and patching of the boot image.
Has anyone had experience of this method?
Click to expand...
Click to collapse
Finally, your advice with "Fastboot boot twrp.img" worked magic!
Got twrp installed, but now I'm facing the same problem as you with the systemless root. I'll dig around a little and see what I can find.

ROOT BLU R1 PLUS - R0051UU ROM 6.0 V13 - MT6737m

Unlock Bootloader and Root BLU R1 Plus
Yes it has been done
Thanks to @lopestom for all his help and porting TWRP to this device
Thanks to RootJunky for FRP Unlock.img
Thanks to Larry Miller for testing with his device
This has been done to Three 16 G devices and One 32 G device to date
WARNING:
Code:
[B][COLOR="red"]
DO NOT FLASH RECOVERY WITH SP FLASHTOOL AS IT
COULD BRICK DEVICE!![/COLOR][/B]
For use SPFT you need special file. So here's the best way is using ADB-fastboot to unlock bootloader, flash FRP Unlock.img and recovery!!
At all times it is necessary to think in safety not to have a bricked device.
Then for the uninformed users:
Code:
[B][COLOR="Red"]MAKE A BACKUP OF THE ROM WITH TWRP AND COPY FOR YOUR PC![/COLOR][/B]
This method uses adb and fastboot commands to achieve root
Before any actions: copy all that you need from SDcard internal to PC!
If you want backup calls, messages, contacts (different by goggle contatcs or if you can record all the contacts in your google contacts account directly through the contacts application).
For backup, use any application from google play! Save in your PC! After all the processes you can restore them using the same application that you used.
- Instructions to PROCESS:
1. On phone open setting
about phone, tap 7 times in build number
Enable Developer Options
Enable USB Debugging
2. On PC search the folder of adb and fastboot minimal ( included in zip to install }
Unzip and Place unlock.img , recoveryTWRP.img and SR3-SuperSU-v2.79-SR3-20170114223742.zip in adb and fastboot minimal folder
Open adb terminal
Code:
adb devices
to ensure connection
Code:
adb reboot bootloader
Code:
fastboot flash frp unlock.img
Code:
fastboot oem unlock
( Confirm with volume up select on phone )
Code:
fastboot flash recovery recoveryTWRP.img
Fastboot will show image flashed but due to BLUs locking of device fastboot reboot will not function
So ….
Unplug device , Hold power off until device turns off
Hold Volume up and Plug device back into PC ,
Continue to hold volume up until TWRP boots fully
Select Wipe , Select Format Data ( don’t worry if any errors show )
Reboot TWRP Recovery
Select Mount , Select Mount USB Storage
Open Device on PC , Move SR3-SuperSU zip to device external_sd
Unmount
Select Install
Select external_sd
Select SU zip and install in TWRP
Select Reboot System
Phone May reboot several time do not interrupt boot
Unlocked bootloader and TWRP
xposed arm v89 has been tested and works , Gravitybox 6.5.3 has been tested and works
Download link
TWRP_Root_R1_Plus.zip
mirror: TWRP Root R1 Plus.zip
William Smith
XDA:DevDB Information
[TUT] Unblocking & Unlocking - Installing TWRP - ROOT, Kernel for all devices (see above for details)
Contributors
lopestom, donnasbrt1
Source Code: https://forum.xda-developers.com/android/general/blu-blu-vivo-kernel-sources-t3767993
Kernel Special Features:
Version Information
Status: Stable
Current Stable Version: 1.0
Stable Release Date: 2018-09-18
Created 2018-09-19
Last Updated 2018-09-24

More in info: Stock ROM - TWRP - TWRP Backup - Lineage 14.1 (almost bug free)
Link of Stock ROM - TWRP - TWRP Backup - Lineage 14.1 (almost bug free)
Click me post #13
.

lopestom said:
Unlock Bootloader and Root BLU R1 Plus
Yes it has been done
Click to expand...
Click to collapse
This is too late for me. I returned this phone long ago.

Add one more 32G device, very happy now, this has been in the closet waiting for root and today it comes to life! Can't thank you enough!!! Works great!!!
---------- Post added at 12:53 AM ---------- Previous post was at 12:20 AM ----------
I installed SuperSU without thinking. Is it too late or is it possible to install Magisk instead?

Donphillipe said:
Add one more 32G device, very happy now, this has been in the closet waiting for root and today it comes to life! Can't thank you enough!!! Works great!!!
---------- Post added at 12:53 AM ---------- Previous post was at 12:20 AM ----------
I installed SuperSU without thinking. Is it too late or is it possible to install Magisk instead?
Click to expand...
Click to collapse
both of them have built in part of there install, a series of commands that remove other root, But is best to remove su before flash majisk. From the superSU app. in the menu is option to full remove superSU. Do that, then reboot make sure it is ok. Then try magisk. Note that it 'should' work, but it seems you will be first to try it.

Just tried to uninstall SuperUS and it no longer boots, locks up at the BLU screen. I was following these steps: https://android.gadgethacks.com/how-to/magisk-101-switch-from-supersu-magisk-pass-safetynet-0177578/
Should have made a backup when I had the chance. Oh, well it's like they say, live and forget and forget again.
So I guess I'll cross my fingers that this factory image I downloaded is not full of malware and is on the up and up.

The factory image I downloaded must be corrupt or something else is wrong. I tried flashing the factory image I downloaded "Blu_R0051UU_MT6737M_V13_REPAIR" and I received the error: ERROR: SBROM_DOWNLOAD_DA_FAIL (2004)
I still can boot to TWRP but I have no backup image in this format. If anyone has a factor or TWRP to share, please let me know.

Tried a different laptop, a couple of new cables and the error is still the same (see above) using the latest version of Flash Tool (v5.1828.01) to download the supposed stock ROM found online (http://www.mediafire.com/file/25su5934zm65vgb/Blu_R0051UU_MT6737M_V13_REPAIR.zip). I also deselected everything in Flashtool from the scatter file except "system" and it still would not load. Note that the only way to put the phone in a state that will communicate with the flash tool is to first hold the vol up and power button for a long time and keep holding them in until the BLU logo disappears and the TWRP menu appears. Here you select Reboot and then Power Off and only then will the flash tool try to communicate with the device when you plug the USB cable in. That's when the long red bar moves across the footer of the screen with 100% and a little later the error messages I named above occurs. Looks like I'm bricked unless I can find a kind soul to share a TWRP backup.

Donphillipe said:
Tried a different laptop, a couple of new cables and the error is still the same (see above) using the latest version of Flash Tool (v5.1828.01) to download the supposed stock ROM found online (http://www.mediafire.com/file/25su5934zm65vgb/Blu_R0051UU_MT6737M_V13_REPAIR.zip). I also deselected everything in Flashtool from the scatter file except "system" and it still would not load. Note that the only way to put the phone in a state that will communicate with the flash tool is to first hold the vol up and power button for a long time and keep holding them in until the BLU logo disappears and the TWRP menu appears. Here you select Reboot and then Power Off and only then will the flash tool try to communicate with the device when you plug the USB cable in. That's when the long red bar moves across the footer of the screen with 100% and a little later the error messages I named above occurs. Looks like I'm bricked unless I can find a kind soul to share a TWRP backup.
Click to expand...
Click to collapse
Larry Miller has also supplied a TWRP backup for this device ..thanks Larry
TWRP backup
Donphillipe said:
I installed SuperSU without thinking. Is it too late or is it possible to install Magisk instead?
Click to expand...
Click to collapse
With Supersu installed you can install Magisk and after remove suspersu......
Donphillipe said:
Just tried to uninstall SuperUS and it no longer boots, locks up at the BLU screen. I was following these steps: link
Should have made a backup when I had the chance. Oh, well it's like they say, live and forget and forget again.
So I guess I'll cross my fingers that this factory image I downloaded is not full of malware and is on the up and up.
Click to expand...
Click to collapse
After removed Supersu or Magisk the ROM can't start because have Custom recovery installed and made modified system option..... So in this case need install again supersu or magisk!
At all times it is necessary to think in safety not to have a bricked device.
Then for the uninformed users: MAKE A BACKUP OF THE ROM WITH TWRP AND COPY FOR YOUR PC!
Sent from my BLUBOO Xtouch using XDA Labs

Fixed, can't thank you enough!

Wiped the phone and did a full restore, everything looked good. I rebooted to TWRP tried to install Magisk V 17, 17.1 and 17.2 and all of them fail install with error;
! Boot image patched by unsupported programs
! Please restore stock boot image
Updater process ended with ERROR : 1
Error installing zip file xxxxxx
---------- Post added at 03:25 AM ---------- Previous post was at 03:10 AM ----------
Also fails SafetyNet check, not sure if it is supposed to or not. This is after restoring from the TWRP image supplied above and without rooting with SuperSU.

I no have the device in my hands. So you can install old version of magisk v15 or v16?
So if you need more information so you can enter here: BLU Development Team
Donphillipe said:
Wiped the phone and did a full restore, everything looked good. I rebooted to TWRP tried to install Magisk V 17, 17.1 and 17.2 and all of them fail install with error;
! Boot image patched by unsupported programs
! Please restore stock boot image
Updater process ended with ERROR : 1
Error installing zip file xxxxxx
Also fails SafetyNet check, not sure if it is supposed to or not. This is after restoring from the TWRP image supplied above and without rooting with SuperSU.
Click to expand...
Click to collapse

More in info on device R1 Plus
For anyone having issue with root or device issues .
If you can return to twrp and select power off this will allow required selection for so flashtool .Or if bootloop press and hold button combo and insert USB during power down of bootloop . Button combo for preloader is volume up and then power button then plug in device
Stock ROM here
https://www.mediafire.com/download/nbm2vt2dne5s2pc
TWRP
https://www.mediafire.com/download/hjmjpgepfbnjy7h
TWRP Backup
https://www.mediafire.com/download/eaxx8fla8a9a247
Lineage 14.1 (almost bug free)
https://www.mediafire.com/folder/fqqj9hqqascs0/Lineage 14.1 R1 Plus
Lineage has bug in OFF charging animation phone charges just no animation and rear camera macro focus
No other bugs have been found at this time
Xposed does work with this build v89-sdk25 arm
Thanks to Lopestom and Larry Miller for there support with this

donnasbrt1 said:
For anyone having issue with root or device issues .
If you can return to twrp and select power off this will allow required selection for so flashtool .Or if bootloop press and hold button combo and insert USB during power down of bootloop . Button combo for preloader is volume up and then power button then plug in device
Stock ROM here
https://www.mediafire.com/download/nbm2vt2dne5s2pc
TWRP
https://www.mediafire.com/download/hjmjpgepfbnjy7h
TWRP Backup
https://www.mediafire.com/download/eaxx8fla8a9a247
Lineage 14.1 (almost bug free)
https://www.mediafire.com/folder/fqqj9hqqascs0/Lineage 14.1 R1 Plus
Lineage has bug in OFF charging animation phone charges just no animation and rear camera macro focus
No other bugs have been found at this time
Xposed does work with this build v89-sdk25 arm
Thanks to Lopestom and Larry Miller for there support with this
Click to expand...
Click to collapse
Hello, which driver did you use? I can't get download mode work right

When loading bootloader ..power off device ...press volume up ..then power ( at the same time ) then plug device into pc ..device should load ..then device should flash .. do not flash preloader or imei issues may result

Any update on the progress lineage 14.1 on this phone? I use it for a day waa bit laggy

Not at this time Lineage 14.1 was a test run for the device and I have not had time to finish yet and am also working Resurrection Remix right now .Camera porting has been a bit tricky as there are alot...alot of simlinks on stock rom for camera functions . I will have more time soon to work on it a bit more

donnasbrt1 said:
Not at this time Lineage 14.1 was a test run for the device and I have not had time to finish yet and am also working Resurrection Remix right now .Camera porting has been a bit tricky as there are alot...alot of simlinks on stock rom for camera functions . I will have more time soon to work on it a bit more
Click to expand...
Click to collapse
Any update or ETA? I might put off a phone purchase if a build with a working camera comes along.... P.S. Another annoying bug I face is that videos don't play in some apps e.g. google photos, WhatsApp statuses and on Snapchat. Videos on Youtube and Facebook play fine. Fingers crossed for some good news! Wishing you a happy holiday season!

You can allways run stock rooted with xposed and gavitybox until bugs are worked out. Just a thought .Happy holidays to you also

+1 32G successful
Thanks for this! Waited for so long for a method.
Now: since I'm kinda newbie to root, I'm doubtful on how to detect custom kernels to flash based on this device model. Or is it possible to flash whatever?
I need something like 'ElementalX' or related.