Related
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 guys,
So I rooted my swift 2x but now I want to unroot it so I can use baking apps. Trouble is I'm having difficulty unrooting.
My method for root was
> Unlock bootloader
> Install TWRP
> Install Supersu
But now I can't unroot. I've tried unrooting via the supersu app but on one try it errored out and nothing changed and on another try when the phone rebooted it got stuck on the white wileyfox screen.
I've also tried to install the reocer image from here https://forum.xda-developers.com/swift-2/how-to/marmite-android-7-1-1-tos118c-fastboot-t3605101 via twrp but then once I reboot after installation from TWRP it gets stuck on the white wileyfox screen after seeing messages that the device is corrupt on a previous screen.
What can I do to unroot?
Thanks!
Return to stock via fastboot... it will fix everything. I had to leave LineageOS because nothing I tried would allow me to use my Banking app now they've really tightened security, thanks to Google's CTS. Shame.
(LOL on the "baking app")
EDIT: This Thread has all the files except the latest. Flash TOS319I and let the phone OTA to TOS373J.
Since you have already done this I thought maybe you might be able to help me with an issue I am having
From your thread I have used the first part of the following thread https://forum.xda-developers.com/showpost.php?p=72827221&postcount=7 - to fastboot "Android_7.1.2_Wileyfox_Swift2_2017_09_07 TOS249H - Signed Fastboot" -
Everything went as it should have (or so it appeared) but when I went to reboot, the new Wiley Fox logo appeared and then looped system errors i.e. "Unfortunately, system UI has stopped" , Unfortunately, the process com.android.phone has stopped etc
Can you give any insight as to my next move please? Would appreciate a noob response
PhilosAnthropos said:
Since you have already done this I thought maybe you might be able to help me with an issue I am having
From your thread I have used the first part of the following thread https://forum.xda-developers.com/showpost.php?p=72827221&postcount=7 - to fastboot "Android_7.1.2_Wileyfox_Swift2_2017_09_07 TOS249H - Signed Fastboot" -
Everything went as it should have (or so it appeared) but when I went to reboot, the new Wiley Fox logo appeared and then looped system errors i.e. "Unfortunately, system UI has stopped" , Unfortunately, the process com.android.phone has stopped etc
Can you give any insight as to my next move please? Would appreciate a noob response
Click to expand...
Click to collapse
Sounds like a problem easily fixed by doing a factory reset, have you tried that?
Just went today to try and factory reset through adb but now there is an "error:no devices found" - exactly the same conditions as yesterday
PhilosAnthropos said:
Just went today to try and factory reset through adb but now there is an "error:no devices found" - exactly the same conditions as yesterday
Click to expand...
Click to collapse
Hmm, is USB debugging on?
USB debugging is needed for adb commands. This setting you find in developer settings and to find and access developer settings you need to tap the version/build number 7 times.
How to Enable USB Debugging Mode on Android <- Check the bottom one #4
Once you do an adb command your phone may prompt you with a connection to pc message to confirm, go ahead and confirm it and do the adb command again.
But.. you need only to get into recovery mode and from there you select and confirm "wipe data/factory reset" and "wipe cache partition". You don't have to do an adb command.
https://www.hardreset.info/devices/wileyfox/wileyfox-swift-2-plus/recovery-mode/ <- I am actually not 100% sure if 5 and 6 are accurate but anyhow this should give you good enough idea on how to access the recovery mode. If in case you not already know this.
All your data will be wiped, make sure to do backup of things you don't want to lose.
May aswell also refer you to my post here, it's just an easy way of doing a fastboot flash.
RavZ75 said:
Hmm, is USB debugging on?
USB debugging is needed for adb commands. This setting you find in developer settings and to find and access developer settings you need to tap the version/build number 7 times.
How to Enable USB Debugging Mode on Android <- Check the bottom one #4
Once you do an adb command your phone may prompt you with a connection to pc message to confirm, go ahead and confirm it and do the adb command again.
But.. you need only to get into recovery mode and from there you select and confirm "wipe data/factory reset" and "wipe cache partition". You don't have to do an adb command.
https://www.hardreset.info/devices/wileyfox/wileyfox-swift-2-plus/recovery-mode/ <- I am actually not 100% sure if 5 and 6 are accurate but anyhow this should give you good enough idea on how to access the recovery mode. If in case you not already know this.
All your data will be wiped, make sure to do backup of things you don't want to lose.
May aswell also refer you to my post here, it's just an easy way of doing a fastboot flash.
Click to expand...
Click to collapse
I flashed stock via fastboot - But it got stuck on Wiley fox logo with process com.android.phone has stopped etc - hence it is not possible to go into the phone and turn on USB debugging, but it was on before I started the process - and I cant really do anything to the phone until I am able to get the PC to recognise the phone again
PhilosAnthropos said:
I flashed stock via fastboot - But it got stuck on Wiley fox logo with process com.android.phone has stopped etc - hence it is not possible to go into the phone and turn on USB debugging, but it was on before I started the process - and I cant really do anything to the phone until I am able to get the PC to recognise the phone again
Click to expand...
Click to collapse
oh I see, and you've tried factory reset and cache wipe from recovery?
That guide I linked to says volume up + power button but I belive it actually is volume down + power button that needs to be pressed, like this. Try both ways, you don't need connection to pc for booting into recovery mode.
But this is different if you have bootloader unlocked, with bootloader unlocked you will be greeted with this (making use of warj04's pic) when you power on your device.
At this screen you press the volume buttons to change boot option from "Start" to "Recovery". Press power button to confirm boot into recovery and your device will reboot and boot into recovery.
This screen will appear a second time before booting into recovery but you need not do anything else, wait 5 seconds or press power button to start boot.
RavZ75 said:
oh I see, and you've tried factory reset and cache wipe from recovery?
That guide I linked to says volume up + power button but I belive it actually is volume down + power button that needs to be pressed, like this. Try both ways, you don't need connection to pc for booting into recovery mode.
But this is different if you have bootloader unlocked, with bootloader unlocked you will be greeted with this (making use of warj04's pic) when you power on your device.
At this screen you press the volume buttons to change boot option from "Start" to "Recovery". Press power button to confirm boot into recovery and your device will reboot and boot into recovery.
This screen will appear a second time before booting into recovery but you need not do anything else, wait 5 seconds or press power button to start boot.
Click to expand...
Click to collapse
I have the bootloader unlocked and it behaves how you have described it but when I try and go into recovery from the options menu (power + volume down) it momentarily goes to a Wiley fox screen, then the loader (the image you added above), and then for a split second the green robot, then the screen blacks-out altogether. From the options menu I can also go to fastboot which also gives me the option to go into recovery but the same sequence starts as described before - recovery appears to be unavailable?
PhilosAnthropos said:
I have the bootloader unlocked and it behaves how you have described it but when I try and go into recovery from the options menu (power + volume down) it momentarily goes to a Wiley fox screen, then the loader (the image you added above), and then for a split second the green robot, then the screen blacks-out altogether. From the options menu I can also go to fastboot which also gives me the option to go into recovery but the same sequence starts as described before - recovery appears to be unavailable?
Click to expand...
Click to collapse
Yea by now I recommend you to redo the flash through fastboot again, In the thread post you linked to I only see 3 lines of fastboot flash cammands.
To fully fastboot flash a rom there needs to be a few other lines aswell, I'll list all the lines here.
Code:
fastboot flash modem NON-HLOS.bin
fastboot flash dsp adspso.bin
fastboot flash devcfg devcfg.mbn
fastboot flash aboot emmc_appsboot.mbn
fastboot flash keymaster keymaster.mbn
fastboot flash rpm rpm.mbn
fastboot flash sbl1 sbl1.mbn
fastboot flash splash splash.img
fastboot flash tz tz.mbn
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash cache cache.img
fastboot flash system system.img
Lastly, "fastboot reboot" to reboot your device.
RavZ75 said:
Yea by now I recommend you to redo the flash through fastboot again, In the thread post you linked to I only see 3 lines of fastboot flash cammands.
To fully fastboot flash a rom there needs to be a few other lines aswell, I'll list all the lines here.
Code:
fastboot flash modem NON-HLOS.bin
fastboot flash dsp adspso.bin
fastboot flash devcfg devcfg.mbn
fastboot flash aboot emmc_appsboot.mbn
fastboot flash keymaster keymaster.mbn
fastboot flash rpm rpm.mbn
fastboot flash sbl1 sbl1.mbn
fastboot flash splash splash.img
fastboot flash tz tz.mbn
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash cache cache.img
fastboot flash system system.img
Lastly, "fastboot reboot" to reboot your device.
Click to expand...
Click to collapse
You were a great help, thanks - I didnt think this was going to end well. I was wondering if I re-lock the bootloder will that intermitent screen dissapear? If so, How do I re-lock it?
PhilosAnthropos said:
You were a great help, thanks - I didnt think this was going to end well. I was wondering if I re-lock the bootloder will that intermitent screen dissapear? If so, How do I re-lock it?
Click to expand...
Click to collapse
Yes that screen will go away if you re-lock bootloader and if there isn't a dm-verity issue present.
To fix dm-verity issue you need USB debugging on and this command:
Code:
adb reboot "dm-verity enforcing"
If there is no dm-verity issue, great. No need for this command then.
The unlock and lock bootloader commands you do in fastboot.
The unlock commands are:
Code:
fastboot flashing unlock
fastboot flashing unlock_critical
So the re-lock commands are as simple as this:
Code:
fastboot flashing lock
fastboot flashing lock_critical
I am glad I could be of help
Hi,
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.
Hello i wanted to ask about this since i dont see any other thread related to my issue, im trying to install magisk root and im at the stage of accessing fastboot/bootloader, when i go to recovery mode and select "reboot to bootloader" it just restarts the phone, i have tried adb commands didnt work either, same result, just restarts. The "unlock oem" option under developer options is enabled, i could flash another firmware of the same phone with SPD upgrade tool and its still not letting me get into bootloader, (to do this i must press down vol down and connect the usb while the program is on, and it is detected, otherwise it just restarts adb and fastboot tools will not detect it as download mode) any idea or suggestions on how I could root the phone, been thinking about twrp but not sure it would let me install that, looked into many pages about rooting this device and none show anything related maybe its not possible, i saw there are phones with blocked bootloader. the phone is android 9
Have you tried to
- flash the boot.img from the stockfirmware;
- install a recovery (twrp, orangefox, etc.) and rebooted to fastboot from recovery?
wenyendev said:
Have you tried to
- flash the boot.img from the stockfirmware;
- install a recovery (twrp, orangefox, etc.) and rebooted to fastboot from recovery?
Click to expand...
Click to collapse
TWRP and orangefox dont support my phone, there may be something unnoficial for twrp as i search and im not sure i can flash the phone with a specific boot file since to flash i use a single .pac file that contains the rom ill look into this
For now im not able to flash the phone with custom boot.img or recovery.img maybe i need to pack specific files i dont know about i give up for today
Sorry to hear that...
Have you tried the following command?
Apache config:
adb reboot bootloader
wenyendev said:
Sorry to hear that...
Have you tried the following command?
Apache config:
adb reboot bootloader
Click to expand...
Click to collapse
yes both that and adb reboot fastboot just restart the phone
Have you tried the method in the following page?
Hold volume up & power buttons. Otherwise, try volume down & power buttons.
How to get into fastboot and How to exit fastboot ZTE Blade A5 PRO? - HardReset.info
The Fastboot Tutorial will show you the easiest way to access the hidden model called fastboot. Check out the secret combination of keys that will boot your device into fastboot.
www.hardreset.info
wenyendev said:
Have you tried the method in the following page?
Hold volume up & power buttons. Otherwise, try volume down & power buttons.
How to get into fastboot and How to exit fastboot ZTE Blade A5 PRO? - HardReset.info
The Fastboot Tutorial will show you the easiest way to access the hidden model called fastboot. Check out the secret combination of keys that will boot your device into fastboot.
www.hardreset.info
Click to expand...
Click to collapse
This is not my phone model, its zte blade a5 plus 2020, vol up and power restarts the phone normally