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
Related
Sorry if this has been covered before but I can´t get it to work. I desperatly need help because my One X+ does not boot into recovery. It started with me having CM 10.1 working and all was good. Then when I was using the cam it froze and rebooted but didnt start. I tried to get into recovery but after having chosen the recovery option the phone shows the HTC boot screen, blinks to Another HTC bootscreen and then goes black. I assume it shuts off because I cannot Contact it from fastboot or adb. I have tried flashing a number of different recovery and kernel combinations but the same problem remains. I have even tried the RUU to get it back to stock but even that gives me the same problem afterwards.
I have tried to erase cache and Everything I have found in this wonderful forum but now I dont know what to do. Pls help me
My Hboot is 1.35.0000 and it´s the international version.
Hi darkwing66,
You said...
darkwing66 said:
...I assume it shuts off because I cannot Contact it from fastboot or adb...
Click to expand...
Click to collapse
How did you managed to flash a different boot or another recovery if this device is not recognized by the SDK tool?
Lucky Thirteen said:
Hi darkwing66,
You said...
How did you managed to flash a different boot or another recovery if this device is not recognized by the SDK tool?
Click to expand...
Click to collapse
Sorry, it was after the boot that I cannot access it. If I boot into fastboot its possible to flash recovery and kernel. I´m new at this so I try my best
I have tried flashing openrecovery-twrp-2.4.4.0-enrc2b.img, ViperX+ 1.06 with venomkernelflasher etc. Everythings seems to go well until reboot, or trying to get into recovery. Could it be HW fault or is it just my incompetence to get it right?
And you said you tried to flash the appropriate boot.img for your ROM?
Bootlooping is usually caused by an inpropriate boot.img... Can you described how you do it please? There is something missing.
Are you using any sort of tool or you're doing all this via a command window?
Also are you sure you picked the right Recovery? Don't take the CWM, you must install the TWRP for the ENRC2B version since you have an International phone.
---------- Post added at 01:43 PM ---------- Previous post was at 01:19 PM ----------
Oops! Sorry I didn't saw you had edited your previous post.
It's hard to tell what you have done, you need to precise what you are doing....
At first you were at this :
...CM 10.1 working and all was good. Then when I was using the cam it froze and rebooted but didnt start...
Click to expand...
Click to collapse
then now you are at :
...ViperX+ 1.06 with venomkernelflasher...
Click to expand...
Click to collapse
First, if you have CM 10.1 installed on your phone you CAN NOT use VenomKernelFlasher, the latter is only usable with the Viper ROM. You need to flash the boot.img of CM 10.1 if this is the ROM actually installed on your phone.
You should try to flash the correspondent CM 10.1 boot.img located HERE
As I said i´m new at this
When it all happened I was using the CM 10.1. I flashed and rooted with Hasoon2000 v2.3 toolkit.
From the toolkit I flashed the CWM recovery which was working fine until this very moment..
I used the same toolkit to flash the blade boot img you so kindly linked to but same problem did occur after that.
Panicing as I was then I tried Another rom with it´s recovery and kernel but the problems remained the same. (viperX)
Is there anyway I can start over and get a fresh start so to speak? I thought the RUU would solve it but it didn´t. I relocked the phone Before trying the ruu...
update:
Just tried flashing the openrecovery-twrp-2.4.4.0-enrc2b.img with the "BLADE" boot.img but nothing Changes.
It says ok when flashing..
I know this may sound stupid but make sure when flashing a new boot.img you also have flashed the matching rom. I'd take a deep breath and reflash a whole new set. Use normal commands from a "CMD" box so you can track any problems.
Start here with recovery, http://forum.xda-developers.com/showthread.php?t=1995002
Then flash this rom and kernel http://forum.xda-developers.com/showthread.php?t=2010104
edit - just realized if you are not able to boot into android you will need to sideload your rom via recovery
edit - just realized if you are not able to boot into android you will need to sideload your rom via recovery[/QUOTE]
The problem is that I can´t boot into recovery.. can I do it some other way?
i trust you can get to the bootloader screen? if so, is it from there where you try and flash the recovery? Hmm without recovery you cannot flash any rom.
however if you have not been able to boot into recovery i trust you didnt wipe the system (other than when you relocked and then unlocked the bootloader) if so try just flashing the cm10.1 kernel again to see if you can return to a booting phone again.
edit - what error did you get when trying to flash the ruu?
ratcom said:
i trust you can get to the bootloader screen? if so, is it from there where you try and flash the recovery? Hmm without recovery you cannot flash any rom.
however if you have not been able to boot into recovery i trust you didnt wipe the system (other than when you relocked and then unlocked the bootloader) if so try just flashing the cm10.1 kernel again to see if you can return to a booting phone again.
edit - what error did you get when trying to flash the ruu?
Click to expand...
Click to collapse
I didn´t get any errors at all, it just installs then when it boots it shuts off after the HTC bootscreen. It feels like my main concern must be to get a working recovery again? But how??
darkwing66 said:
I didn´t get any errors at all, it just installs then when it boots it shuts off after the HTC bootscreen. It feels like my main concern must be to get a working recovery again? But how??
Click to expand...
Click to collapse
ok so if you boot into bootloader using the vol down and power I trust you are able to select recovery? if so does it then reboot show 2 htc screens then black screen?
ratcom said:
ok so if you boot into bootloader using the vol down and power I trust you are able to select recovery? if so does it then reboot show 2 htc screens then black screen?
Click to expand...
Click to collapse
Yes I can select recovery and then it shows the "HTC quietly brilliant" two times then goes black, or if it shuts off.
darkwing66 said:
Yes I can select recovery and then it shows the "HTC quietly brilliant" two times then goes black, or if it shuts off.
Click to expand...
Click to collapse
if you are using the correct recovery version (International) then I'm out of ideas Sorry I couldnt help
Make sure you downloaded the good RUU for your CID
Boot your phone in BOOTLOADER (Volume down + Power)
Make sure your phone is responding to adb command line with the following : fastboot devices (Enter)
Relock your BOOTLOADER : fastboot oem lock (Enter)
Rebooting
Boot the phone into FASTBOOT and then connect to the PC
Again make sure your phone is responding to adb command line with the following : fastboot devices (Enter)
If you have a your serial number in return you can run the RUU
Good luck!
Lucky Thirteen said:
Make sure you downloaded the good RUU for your CID
Boot your phone in BOOTLOADER (Volume down + Power)
Make sure your phone is responding to adb command line with the following : fastboot devices (Enter)
Relock your BOOTLOADER : fastboot oem lock (Enter)
Rebooting
Boot the phone into FASTBOOT and then connect to the PC
Again make sure your phone is responding to adb command line with the following : fastboot devices (Enter)
If you have a your serial number in return you can run the RUU
Good luck!
Click to expand...
Click to collapse
Thank you for not giving up on me
Did all the steps you said and everything went well except for the problem still remaining. Would it make any difference if I try to extract the recovery and boot from the RUU as I have seen mentioned somwhere in the forum?
You can give it a shot, but how are you gonna transfer the Rom.zip on your phone then?
Usually it's something like
Run the installer of the RUU with your phone unplugged.
Stop on the automated installer and put it aside on your Desktop
Follow this path in your computer : C:\Users\your_account_name\AppData\Local\Temp\{ABC1234D-56E7-8910-F11G-123AB4C56DE7}\{ABC1234D-56E7-8910-F11G-123AB4C56DE7}\Rom.zip (Your string will be different but the Rom.zip will still be there)
Extract from this Rom.zip : boot_signed.img & recovery_signed.img
Boot to fastboot, flash boot_signed.img and recovery.img .
Boot to recovery and flash the Rom.zip
Lucky Thirteen said:
You can give it a shot, but how are you gonna transfer the Rom.zip on your phone then?
Usually it's something like
Run the installer of the RUU with your phone unplugged.
Stop on the automated installer and put it aside on your Desktop
Follow this path in your computer : C:\Users\your_account_name\AppData\Local\Temp\{ABC1234D-56E7-8910-F11G-123AB4C56DE7}\{ABC1234D-56E7-8910-F11G-123AB4C56DE7}\Rom.zip (Your string will be different but the Rom.zip will still be there)
Extract from this Rom.zip : boot_signed.img & recovery_signed.img
Boot to fastboot, flash boot_signed.img and recovery.img .
Boot to recovery and flash the Rom.zip
Click to expand...
Click to collapse
I figured if I manage to extract those files from the rom.zip then I could flash them with fastboot? But at the moment I´m even struggling with extracting the darn files...
Do you Think it will make any difference doing the flashing this way or just running the RUU.exe (wich in my case doesn´t work)?
darkwing66 said:
I figured if I manage to extract those files from the rom.zip then I could flash them with fastboot? But at the moment I´m even struggling with extracting the darn files...
Do you Think it will make any difference doing the flashing this way or just running the RUU.exe (wich in my case doesn´t work)?
Click to expand...
Click to collapse
Hold on I will upload the International version of both of them for you...
Give me ~5 minutes
Edit (sorry if it took longer) :
Here it is :
ENRC2B_recovery_signed
ENRC2Bbootsigned
Hoping you will be able to do something with those. I'll catch later.
Lucky Thirteen said:
Hold on I will upload the International version of both of them for you...
Give me ~5 minutes
Click to expand...
Click to collapse
The recovery file can´t be dl, it says "This file, folder or group is private or does not exist."
edit:
Found one but still the same black screen and no recovery...
darkwing66 said:
The recovery file can´t be dl, it says "This file, folder or group is private or does not exist."
Click to expand...
Click to collapse
Links fixed, Sorry!
First I just want the conformation that you are doing all this manually via a command window and not throught any sort of flashing tool, right?
Lets try those...
Test 1 :
Put this FILE in your platform-tool folder of SDK and do not rename it.
Plug your phone on your computer USB cable
Open a SDK/ADB command window
Type at the prompt> adb devices (Enter) (Serial conformation)
Type at the prompt> adb reboot-bootloader (Enter)
Rebooting in BOOTLOADER
Unplug your phone while rebooting
Once in FASTBOOT plug in your phone and make sure FASTBOOT USB is highlighted
Type at the prompt>fastboot devices (Enter) (Serial conformation)
Type at the prompt>fastboot erase recovery (Enter)
Type at the prompt>fastboot flash recovery TWRPrecovENRC2B.img (Enter)
Type at the prompt>fastboot erase cache (Enter)
Unplug your USB cable and hit Power once.
Select via your Volume rocker -> Recovery
Again hit Power button again
Results?
Test 2 :
Put this FILE in your platform-tool folder of SDK and do not rename it.
Plug your phone on your computer USB cable
Open a SDK/ADB command window
Type at the prompt> adb devices (Enter) (Serial conformation)
Type at the prompt> adb reboot-bootloader (Enter)
Rebooting in BOOTLOADER
Unplug your phone while rebooting
Once in FASTBOOT plug in your phone and make sure FASTBOOT USB is highlighted
Type at the prompt>fastboot devices (Enter) (Serial conformation)
Type at the prompt>fastboot erase recovery (Enter)
Type at the prompt>fastboot flash recovery ENRC2BstockRecovery.img (Enter)
Type at the prompt>fastboot erase cache (Enter)
Unplug your USB cable and hit Power once.
Select via your Volume rocker -> FACTORY RESET
Hit your Power button once to confirm.
The phone should enter Stock Recovery mode and wipe EVERYTHING including "SD card" but also should fix all corrupted DATA (ROM, Directory, Etc)
Once done reboot your phone by holding volume down +power to enter manually the BOOTLOADER
Plug back your USB cable
Open a SDK/ADB command window
Type at the prompt> fastboot devices (Enter) (Serial conformation)
Make sure FASTBOOT USB is highlighted
Type at the prompt>fastboot flash recovery TWRPrecovENRC2B.img (Enter)
Type at the prompt>fastboot erase cache (Enter)
Unplug your USB cable and hit Power once.
Select via your Volume rocker -> Recovery
Again hit Power button again
Can you access Recovery now?
Lucky Thirteen said:
Links fixed, Sorry!
First I just want the conformation that you are doing all this manually via a command window and not throught any sort of flashing tool, right?
Lets try those...
Test 1 :
Put this FILE in your platform-tool folder of SDK and do not rename it.
Plug your phone on your computer USB cable
Open a SDK/ADB command window
Type at the prompt> adb devices (Enter) (Serial conformation)
Type at the prompt> adb reboot-bootloader (Enter)
Rebooting in BOOTLOADER
Unplug your phone while rebooting
Once in FASTBOOT plug in your phone and make sure FASTBOOT USB is highlighted
Type at the prompt>fastboot devices (Enter) (Serial conformation)
Type at the prompt>fastboot erase recovery (Enter)
Type at the prompt>fastboot flash recovery TWRPrecovENRC2B.img (Enter)
Type at the prompt>fastboot erase cache (Enter)
Unplug your USB cable and hit Power once.
Select via your Volume rocker -> Recovery
Again hit Power button again
Results?
Test 2 :
Put this FILE in your platform-tool folder of SDK and do not rename it.
Plug your phone on your computer USB cable
Open a SDK/ADB command window
Type at the prompt> adb devices (Enter) (Serial conformation)
Type at the prompt> adb reboot-bootloader (Enter)
Rebooting in BOOTLOADER
Unplug your phone while rebooting
Once in FASTBOOT plug in your phone and make sure FASTBOOT USB is highlighted
Type at the prompt>fastboot devices (Enter) (Serial conformation)
Type at the prompt>fastboot erase recovery (Enter)
Type at the prompt>fastboot flash recovery ENRC2BstockRecovery.img (Enter)
Type at the prompt>fastboot erase cache (Enter)
Unplug your USB cable and hit Power once.
Select via your Volume rocker -> FACTORY RESET
Hit your Power button once to confirm.
The phone should enter Stock Recovery mode and wipe EVERYTHING including "SD card" but also should fix all corrupted DATA (ROM, Directory, Etc)
Once done reboot your phone by holding volume down +power to enter manually the BOOTLOADER
Plug back your USB cable
Open a SDK/ADB command window
Type at the prompt> fastboot devices (Enter) (Serial conformation)
Make sure FASTBOOT USB is highlighted
Type at the prompt>fastboot flash recovery TWRPrecovENRC2B.img (Enter)
Type at the prompt>fastboot erase cache (Enter)
Unplug your USB cable and hit Power once.
Select via your Volume rocker -> Recovery
Again hit Power button again
Can you access Recovery now?
Click to expand...
Click to collapse
I have used both toolkit and cmd, another problem is that I cant get "adb devices" to return my device. I have tried in win 8, win 7, and now ubuntu but no serial nr returned. If I try fastboot devices it works fine. Is it important to get the adb to work or could I use fastboot instead? I dont know how I can make it work, maybe its my phone thats the problem? I will try now to flash the file you sent me in your latest post. I very very much appreciate you helping me
edit:
Test 1:
The fastboot erase recovery returns - erasing 'recovery'... FAILED (remote: not allowed)
Fastboot flash.. returns -
C:\sdk\platform-tools>fastboot flash recovery TWRPrecovENRC2B.img
sending 'recovery' (7370 KB)... OKAY
writing 'recovery'... INFOFormat partition SOS done
OKAY
Erase cache - OKAY
After reboot - same problem
Test 2:
The same result as test 1...
Must be something is broken in my ***** phone!?
I was messing with my old tracfone and trying to install a custom ROM on it. I pressed wipe on TWRP and selected advance wipe and selected everything for factory defaults. After this, I restarted and my phone is stuck on the LG logo and won't go past it. I can't even get back into TWRP by spamming the volume up button. I also have a backup image, but what's the point if I can't access TWRP? Any help is appreciated.
Thanks
Wipe doesn't restore factory defaults, it removes everything. If you wiped system partition there's no Android on your phone, thus no system to boot. If that's the case, you can try to reflash twrp or install original firmware
minimale_ldz said:
Wipe doesn't restore factory defaults, it removes everything. If you wiped system partition there's no Android on your phone, thus no system to boot. If that's the case, you can try to reflash twrp or install original firmware
Click to expand...
Click to collapse
I'm not sure how to reflash TWRP because I used android terminal to install it.
kchesley said:
I'm not sure how to reflash TWRP because I used android terminal to install it.
Click to expand...
Click to collapse
If so, you need a PC, if it's Windows then download this tool - it's a system-wide fastboot that lets you flash software on your phone. It should also download drivers.
If everything goes OK, boot your phone into bootloader (you need to find the right key combination to do that, could be (phone off) power button+ volume down held for about 5-10 seconds, but I don't really know how it's like with this particular phone).
Go to the folder where you've got your TWRP, hold shift and press right mouse button. From context menu choose "open command window here"
In command window enter:
Code:
fastboot devices
if it returns your phones serial number it's OK, if it doesn't - you probably don't have proper drivers so look for them
If everything is OK enter:
Code:
fastboot flash recovery your-twrp-image-name.img
If this step is OK you can reboot:
Code:
fastboot reboot-bootloader
In the bootloader there should be an option to enter recovery mode which is now TWRP. From there you can flash some ROM.
Alternatively you can get ffactory firmware and flash it with fastboot (that's actually a better option to start with).
I hope that helps
minimale_ldz said:
If so, you need a PC, if it's Windows then download this tool - it's a system-wide fastboot that lets you flash software on your phone. It should also download drivers.
If everything goes OK, boot your phone into bootloader (you need to find the right key combination to do that, could be (phone off) power button+ volume down held for about 5-10 seconds, but I don't really know how it's like with this particular phone).
Go to the folder where you've got your TWRP, hold shift and press right mouse button. From context menu choose "open command window here"
In command window enter:
Code:
fastboot devices
if it returns your phones serial number it's OK, if it doesn't - you probably don't have proper drivers so look for them
If everything is OK enter:
Code:
fastboot flash recovery your-twrp-image-name.img
If this step is OK you can reboot:
Code:
fastboot reboot-bootloader
In the bootloader there should be an option to enter recovery mode which is now TWRP. From there you can flash some ROM.
Alternatively you can get ffactory firmware and flash it with fastboot (that's actually a better option to start with).
I hope that helps
Click to expand...
Click to collapse
Thanks for the help, but unfortunately, I think that the phone is junk. My phone can't get into boot-loader for whatever reason, and I heard some people post that the phone was designed to make the boot-loader non-accessible. I already tried to flash it with ADB while it starts up, but no device is detected (no USB debugging I guess). So unless I can flash the phone while It's on the LG logo, I can't do nothing.
I am very new to this, I rooted my Moto G4 and now I need to download SUHide in order to play Pokemon Go. When I try to enter recovery via my fastboot/abd folder I get a < waiting for any device > message. When I hold down the power + volume down button my phone just turns on as normal without entering bootloader even though my bootloader is unlocked. I tried downloading an app that loads recovery for me but when I tried that I got a "no command" screen with a little green robot.
From what I've read, it's possible I didn't flash my trwp properly? I don't know how this is possible since I just rooted my phone. I would appreciate some help, I'm afraid to take any random guesses at the risk of ruining my phone. Sorry if I'm missing something obvious or not giving enough info, I'm not very tech savvy.
levijoseph said:
I am very new to this, I rooted my Moto G4 and now I need to download SUHide in order to play Pokemon Go. When I try to enter recovery via my fastboot/abd folder I get a < waiting for any device > message. When I hold down the power + volume down button my phone just turns on as normal without entering bootloader even though my bootloader is unlocked. I tried downloading an app that loads recovery for me but when I tried that I got a "no command" screen with a little green robot.
From what I've read, it's possible I didn't flash my trwp properly? I don't know how this is possible since I just rooted my phone. I would appreciate some help, I'm afraid to take any random guesses at the risk of ruining my phone. Sorry if I'm missing something obvious or not giving enough info, I'm not very tech savvy.
Click to expand...
Click to collapse
Try power plus volume up button to go to fastboot mode.
If it not working then connect your android to pc and enable adb. Type "adb devices" enter then type "adb reboot bootloader" and enter. It boots your android in fastboot mode.
If adb commands not working then install adb and fastboot drivers and try again.
https://forum.xda-developers.com/showthread.php?t=2317790
In most devices, volume up + power boots up the recovery options, volume down + power boots the device into fastboot mode (volume buttons first plus power, pressing power button first would boot the device normally).
levijoseph said:
When I try to enter recovery via my fastboot/abd folder I get a < waiting for any device > message. When I hold down the power + volume down button my phone just turns on as normal without entering bootloader even though my bootloader is unlocked.
Click to expand...
Click to collapse
How did you install the custom recovery? Try flashing the recovery.img again (I'm guessing, since you have root, that you did not "flash" (fastboot flash recovery recovery.img) TWRP but just "boot" (fastboot boot recovery.img) it and installed SuperSU).
Ashwinrg said:
Try power plus volume up button to go to fastboot mode.
If it not working then connect your android to pc and enable adb. Type "adb devices" enter then type "adb reboot bootloader" and enter. It boots your android in fastboot mode.
If adb commands not working then install adb and fastboot drivers and try again.
https://forum.xda-developers.com/showthread.php?t=2317790
Click to expand...
Click to collapse
Okay, so that did work, and I was able to enter fastboot mode. However, once I scrolled down to "recovery mode" and tried to enter, I got the same "no command" screen.
rolland.arriza said:
In most devices, volume up + power boots up the recovery options, volume down + power boots the device into fastboot mode (volume buttons first plus power, pressing power button first would boot the device normally).
How did you install the custom recovery? Try flashing the recovery.img again (I'm guessing, since you have root, that you did not "flash" (fastboot flash recovery recovery.img) TWRP but just "boot" (fastboot boot recovery.img) it and installed SuperSU).
Click to expand...
Click to collapse
I used the official moto g4 root guide on this website to root my phone and I'm pretty sure I booted, not flashed, the recovery img (mine is named twrp-3.0.2-0-athene). So, I tried using the command you provided to flash the recovery img and I got a < waiting for any device > message in the command prompt. My phone is plugged in and my recovery img is in the adb / fastboot folder. Any idea what this means? Thank you for the help guys
edit: If it helps to know this, my phone has usb debugging enabled and it is recognized by my pc. I type adb devices and my moto g4 serial number does indeed show up.
levijoseph said:
I am very new to this, I rooted my Moto G4 and now I need to download SUHide in order to play Pokemon Go. When I try to enter recovery via my fastboot/abd folder I get a < waiting for any device > message. When I hold down the power + volume down button my phone just turns on as normal without entering bootloader even though my bootloader is unlocked. I tried downloading an app that loads recovery for me but when I tried that I got a "no command" screen with a little green robot.
From what I've read, it's possible I didn't flash my trwp properly? I don't know how this is possible since I just rooted my phone. I would appreciate some help, I'm afraid to take any random guesses at the risk of ruining my phone. Sorry if I'm missing something obvious or not giving enough info, I'm not very tech savvy.
Click to expand...
Click to collapse
If you are trying to flash twrp recovery on your android then rename your twrp to recovery.
Boot your android in fastboot mode,
Navigate to folder that you have recovery. Press shift and right click and click on open command here and type "fastboot devices" and enter
"fastboot flash recovery recovery.img
It flash your recovery to your android.
Ashwinrg said:
If you are trying to flash twrp recovery on your android then rename your twrp to recovery.
Boot your android in fastboot mode,
Navigate to folder that you have recovery. Press shift and right click and click on open command here and type "fastboot devices" and enter
"fastboot flash recovery recovery.img
It flash your recovery to your android.
Click to expand...
Click to collapse
Did all that, getting:
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slot:recovery: not found
error: cannot load 'recovery.img'
Also, per the suggestion of other users on these forums, I tried to hold down power and press volume up during the "no command" screen after attempting to enter recovery. That sent me into Android Recovery but it's not the twrp platform I used when originally rooting my phone.
How did you unlock the bootloader? have you tried: fastboot oem unlock?
You need to "allow oem unlocking" on developer options (which I guess you already did). Then reboot in bootloader: (a) adb reboot bootloader. In fastboot, you need to unlock the bootloader first: (b) fastboot oem unlock (or unlock-go). Then you can try to flash that recovery.img: (c) fastboot flash recovery "name of the file.img"
edit: fastboot oem unlock restores the device to factory settings. You need to configure and enable again "usb debugging" and "oem unlocking" (which are disabled by default). You can then proceed to fastboot flash
Hi,
i tried to upgrade to the latest 11.0.6 global ROM and as usually I only booted to TWRP and sideloaded the ROM. Bootloader is unlocked, already flashed a lot of different stock & custom ROMs.
adb reboot fastboot
fastboot boot twrp.img (used 3.2.3 with working recovery)
[factory reset from within TWRP]
adb sideload [the new 11.0.6 ROM]
adb sideload had an error 7 at some point and did not finish. No big deal I thought -> [reboot system] from within TWRP and tried to enter fastboot again at first boot [volume down]
BUT: now I am not able to enter fastboot again. The phone starts with the orange 'POCOPHONE by Xiaomi' screen and seems to reset after a minute or so -> loop. Holding [volume down] while booting only brings a black screen (not off, a little grey but no fastboot logo etc.). Probably, fastboot didn't flash correcly. Also, it is not recognized either in fastboot or adb.
Anybody else had this before? Is there something I can try to revice it? Any helpful information is highly welcome,
thanks
I'm no expert, did you try another data cable? Just in case you could use a dry toothbrush and clean the phone's connector . What does the computer says in power+volume down mode? It should say what device you're connecting and add drivers.
There might be a way to repair the bootloader , it involves qcom tool. There's a guide somewhere. I'd try first change cable and computer.
Hi,
My ANE-LX1 seems to be stuck in a bootloop.
I was trying to install lineageos 16 (official) or 18 (unofficial).
First I used potatonv to unlock the bootloader.
This seemed to work OK, but in fastboot mode it said bootloader unlocked (red), FRP locked (green).
Maybe this is the problem, I'm not sure why FRP wasn't reset.
I flashed the latest TWRP 3.5.0 for anne from their site.
I was roughly following the instructions here: https://wiki.lineageos.org/devices/anne/install
I did "fastboot flash recovery-ramdisk twrp...".
I was able to boot to TWRP and then I did a wipe. This got to a certain point and seemed to hang.
Eventually I rebooted and now the phone just boots to TWRP initial screen and sits there. I can't get to fastboot mode or stock recovery.
ADB sees the phone in this mode but commands time out.
If I power off the phone and turn it on again I get the "your device is unlocked" screen but then it goes straight to TWRP.
I left the battery run out and when I booted the "your device is unlocked" screen had the option to press a key to boot recovery but if I press nothing it tries to boot and nothing happens, if I press the volume key it goes to TWRP and again just hangs on the initial screen.
In hindsight I probably should have left the stock recovery as the instructions on openkirin and the ROMs forum say it is required.
It's been a while since I played around with custom ROMs, since before treble etc. so I've probably done something wrong.
Any advice is greatly appreciated!
Thanks
jcul said:
I've probably done something wrong.
Click to expand...
Click to collapse
Yes, you have installed wrong TWRP (version 3.4.0.x and 3.5.0.x is not fully compatible with our device and it's strongly not recommended do 'wipe data' runnig stock ROM , it may brick the phone).
- Try in fastboot mode run commands
fastboot erase userdata
fastboot reboot
- Try boot into Recovery update mode (turn off, then press and hold Power + both Volume buttons) and post the result.
Ya I spotted the 3.4.0 thread here just after I had flashed the latest.
I had followed the link from the lineageOS wiki and just installed the latest...
I can't seem to boot into bootloader / recovery update mode.
No matter what I do volume up / down / both I get to teamwin initial screen and it hangs there.
I get the "can't be trusted" screen I posted above when the phone turns on and then it goes to TWRP.
I think when the battery is completely drained I get the "can't be trusted" with "press volume up to boot erecovery" message so maybe I need to wait until it is in that mode and then press both volume buttons.
So I don't get fastboot access but I actually have adb access.
$ adb devices
List of devices attached
89U7N18530003337 recovery
$ adb shell
anne:/ # df
Filesystem 1K-blocks Used Available Use% Mounted on
rootfs 1852668 68212 1784456 4% /
tmpfs 1912668 296 1912372 1% /dev
tmpfs 1912668 0 1912668 0% /mnt
tmpfs 1912668 4 1912664 1% /tmp
/dev/block/mmcblk0p43 112624 104 112520 1% /cache
Though if I run:
$ adb reboot bootloader
It just hangs.
jcul said:
So I don't get fastboot access
Click to expand...
Click to collapse
Install on PC "Minimal ADB and fastboot" tool, open it, turn off phone, hold Volume down and connect phone to the PC. It should work.
-Alf- said:
Install on PC "Minimal ADB and fastboot" tool, open it, turn off phone, hold Volume down and connect phone to the PC. It should work.
Click to expand...
Click to collapse
Sorry I mean I can't get the phone into bootloader mode. I do have ADB and fastboot installed.
The phone just goes straight to TWRP.
"fastboot devices" doesn't show anything. "adb devices" shows the phone once it's on the twrp screen.
jcul said:
Sorry I mean I can't get the phone into bootloader mode. I do have ADB and fastboot installed.
The phone just goes straight to TWRP.
"fastboot devices" doesn't show anything. "adb devices" shows the phone once it's on the twrp screen.
Click to expand...
Click to collapse
try one more trick - unplug phone, run command fastboot reboot (or fastboot oem get-build-number ) , ENTER. You will see a message Waiting for any device. Then use this method
-Alf- said:
turn off phone, hold Volume down and connect phone to the PC
Click to expand...
Click to collapse
Last chance - try get the phone into bootloader mode using Huawei Multi-Tool.
If it's just a software problem, dc-phoenix and the test point method (paid service) will help you. But it is possible that the emmc memory has died or the motherboard is damaged.
Thanks for the help with this.
I managed to get the device into bootloader mode eventually.
Code:
$ sudo fastboot oem get-build-number
(bootloader) :ANE-LX1 9.1.0.360(IRLC368E6R1P6)
OKAY [ 0.005s]
Finished. Total time: 0.005s
$ sudo fastboot erase userdata
Erasing 'userdata' (bootloader) success to erase cryypt info in oeminfo
OKAY [ 1.801s]
Finished. Total time: 1.818s
$ sudo fastboot reboot
Rebooting OKAY [ 0.024s]
Finished. Total time: 0.225s
I did the erase userdata and after that I was able to get into eRecovery like you suggested by holding both volume buttons.
I thought that would have been wiped after I flashed with TWRP but I guess not.
In eRecovery it said "Data Partition severely corrupted. To reset your device, please format the data partition", so I did that and now I'm back on the eRecovery screen.
I attached some images.
Should I be worried that the bootloader screen shows "FRP Lock"?
My goal is to install LineageOS so now that I've done a reset using the stock eRecovery should I be good to follow the steps here? Or do I need to first flash a stock recovery to the recovery-ramdisk over the TWRP I flashed before?
LOSQ/LiR - LineageOS 17.1/18.1-UNOFFICIAL-GSI
For those who want to try LineageOS 17.1/18.1-UNOFFICIAL-GSI . IMO stable enough to be used as your daily driver. LOSQ/LiR is not developed nor maintained by me! Credits: @eremitein Requirements: basically full stock EMUI 9.1, with stock...
forum.xda-developers.com
Thanks again
jcul said:
I was able to get into eRecovery like you suggested by holding both volume buttons.
I thought that would have been wiped after I flashed with TWRP but I guess not.
Click to expand...
Click to collapse
First of all - in Huawei devices we have two recoveries - Recovery and eRecovery.
- If I'm not mistaken, you have still TWRP on board (instead Recovery), can you boot into TWRP? (it's important)
- In eRecovery menu there's an option "Download latest version and recovery". Have you tried this method?
With FRP lock you cannot flash partitions from fastboot.
And yes, data partition is really corrupted ...
Unfortunately, there's no Service ROM for your build number, your phone is Single SIM, 'Three network' Ireland (correct me if I'm wrong), so you cannot restore your phone via dload method.
Hi,
Yes I selected the "download latest version and recovery" and it seemed to flash successfully.
I can now boot the device normally into the original stock 3 Ireland image.
Unfortunately, there's no Service ROM for your build number, your phone is Single SIM, 'Three network' Ireland (correct me if I'm wrong), so you cannot restore your phone via dload method.
Click to expand...
Click to collapse
Yes that's exactly right.
Is it possible to use a different single SIM variant stock image?
Now volume up takes me to stock EMUI recovery, with options to wipe etc.
Volume up + down takes me to EMUI saying update failed or something like that.
Volume down just boots normally, not to fastboot mode (do I need to have a USB cable inserted to get fastboot mode or is it somehow broken?).
I can get into fastboot by doing "adb reboot bootloader".
So now I have bootloader locked and FRP locked again.
Should I use potatonv again to unlock the bootloader and then try flash a custom ROM after doing a reset with the stock recovery?
Ideally I'd like to have a ROM with optional / hidden root so I can use banking apps but also have root access, but if I have to lose banking apps to have root then I'm OK with that.
jcul said:
Is it possible to use a different single SIM variant stock image
Click to expand...
Click to collapse
yes, but you have to rebrand the phone to another region, e.g. eu C432 - replace oeminfo and flash eu firmware (you get dual SIM because oeminfo for single is not available). The process will lock the BL again.
jcul said:
not to fastboot mode (do I need to have a USB cable inserted to get fastboot mode or is it somehow broken?).
Click to expand...
Click to collapse
Turn off the phone, hold Volume Down and connect to PC.
jcul said:
Should I use potatonv again to unlock the bootloader and then try flash a custom ROM after doing a reset with the stock recovery?
Click to expand...
Click to collapse
Yes, you can,
each bootloader code is permanent, it wont expire.
jcul said:
Ideally I'd like to have a ROM with optional / hidden root so I can use banking apps but also have root access,
Click to expand...
Click to collapse
Try CAOS
Thanks.
So I think this is what I will do.
1. Unlock bootloader using potatonv again (hopefully this time it will reset FRP Lock too as I have no google account on the phone this time).
2. Root phone using magisk so I can change oeminfo.
3. Flash oeminfo following this guide.
4. Download and flash ANE-LX1C432E5R1P7B132 from here using fastboot and do factory reset.
5. Flash CAOS rom over stock 9.1.0.132.
jcul said:
Thanks.
So I think this is what I will do.
1. Unlock bootloader using potatonv again (hopefully this time it will reset FRP Lock too as I have no google account on the phone this time).
2. Root phone using magisk so I can change oeminfo.
3. Flash oeminfo following this guide.
4. Download and flash ANE-LX1C432E5R1P7B132 from here using fastboot and do factory reset.
5. Flash CAOS rom over stock 9.1.0.132.
Click to expand...
Click to collapse
I've never done a rebrand running EMUI 9.1, I'm not sure if it works. Try downgrade to Oreo via HiSuite, then follow this tutorial - variant C/.
jcul said:
hopefully this time it will reset FRP Lock too as I have no google account on the phone this time
Click to expand...
Click to collapse
You can FRP unlock manually in Developer options - "Enable OEM unlock"
jcul said:
. Download and flash ANE-LX1C432E5R1P7B132 from here using fastboot and
Click to expand...
Click to collapse
Use only service ROM and dload method.
I decided to go straight for Lineage OS 18 unofficial.
Works great.
If I ever need to go back to stock then I guess I will have to go the rebrand route.
Thanks again for the help.
jcul said:
I decided to go straight for Lineage OS 18 unofficial.
Works great.
Click to expand...
Click to collapse
Yes, one of the best custom ROMs for hi6250 devices . Now fully compatible with Magisk !
jcul said:
Thanks again for the help.
Click to expand...
Click to collapse
No problem.