Hi all,
How can I wipe the cache partition on a Poco F1 with 10.3.6.0 Global stable (stock, so not rooted)? Booting in recovery mode gives me a custom recovery with only the option to wipe all data. Can Mi Assistant help here? Or are there other options?
Google would have helped you... Reboot to recovery and try 'fastboot erase cache'. Sometimes you need a 'sudo su' before that.
guhvanoh said:
Google would have helped you... Reboot to recovery and try 'fastboot erase cache'. Sometimes you need a 'sudo su' before that.
Click to expand...
Click to collapse
Well, as I said: I have stock ROM. As far as I see I do not have any option to erase system cache in the default recovery.
As I said as well: I have stock firmware, perhaps should have added locked bootloader. So no possibility to use fastboot (again, correct me if I'm wrong).
If the only option is to unlock the bootloader I can just replace recovery with TWRP, but I'd like to avoid having to unlock...
Hi there,
First enable USB debugging in the developer options. To enable developer options, you have to tap five times on the miui version in the about phone. Connect your PC and accept the pop up in your phone to register the pc in your phone. Power off your phone first and press power button and volume down simultaneously to take you to fastboot mode. If it goes to bootloader mode, then select the option to go to fastboot mode. If the bootloader mode is in Chinese then search some forums to select the fastboot mode appropriately.
Before all these. Install minimum ADB tools in your PC. Execute fastboot commands once connected to your phone in fastboot mode.
This is very simple once you are familiar with the process. Until then these seems a nightmare'.
Cheers
sssyraj
Hit thanks if it helps you.
And just to add to the above instructions, you don't need an unlocked bootloader, just have USB debugging enabled, to use fastboot.
You use fastboot to unlock the bootloader and it would be a mite hard (and redundant) if you needed the bootloader unlocked to unlock the bootloader...
Also, just to confirm the phone is being detected in fastboot mode use the command "fastboot devices" to see if the phone is recognised.. It should show a number otherwise if it is just a blank space fastboot hasn't recognised your phone...
ultramag69 said:
And just to add to the above instructions, you don't need an unlocked bootloader, just have USB debugging enabled, to use fastboot.
You use fastboot to unlock the bootloader and it would be a mite hard (and redundant) if you needed the bootloader unlocked to unlock the bootloader...
Also, just to confirm the phone is being detected in fastboot mode use the command "fastboot devices" to see if the phone is recognised.. It should show a number otherwise if it is just a blank space fastboot hasn't recognised your phone...
Click to expand...
Click to collapse
Got it into fastboot, but now it throws an error. Google search did not give a real solution.
Error shown:
Code:
******** Did you mean to fastboot format this ext4 partition?
erasing 'cache'...
FAILED (remote: Erase is not allowed in Lock State)
finished. total time: 0.007s
jvdv360 said:
Got it into fastboot, but now it throws an error. Google search did not give a real solution.
Error shown:
Click to expand...
Click to collapse
With that error shown I'm not sure what formatting will do. If the current type is ext4, then you should be fine. But it is looking like you're a candidate for unlocking your bootloader...
Related
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
I flashed havoc os had some issues , tried restoring from my backup, got caught in a bootloop so i used lgup to flash a kdz and it worked.but now my enable oem unlock is turned off and it is greyed out. What can i do.
Mohammedbi said:
I flashed havoc os had some issues , tried restoring from my backup, got caught in a bootloop so i used lgup to flash a kdz and it worked.but now my enable oem unlock is turned off and it is greyed out. What can i do.
Click to expand...
Click to collapse
The same thing happens to me, I have not found much info about this, I hope you can help us.
Mohammedbi said:
I flashed havoc os had some issues , tried restoring from my backup, got caught in a bootloop so i used lgup to flash a kdz and it worked.but now my enable oem unlock is turned off and it is greyed out. What can i do.
Click to expand...
Click to collapse
I already found the solution, but it will erase your data.
with the adb commands you must restart the device in boorloader mode:
adb reboot bootloader
Then when I take you to the bootloader screen what you have to write next:
fastboot oem lock
(Remember the phone will be erased)
then to restart the device you have to:
fastboot reboot
And the device will reboot.
what you do is lock it, so that you can then unlock it in a simple way.
(If you do not know what the ADB is, warn man), I hope it helps you and those who enter here too :good:
@l3dson: Be careful before relocking the bootloader: The phone MUST be 100% stock or you will have a brick.
@Mohammedbi: Your bootloader is still unlocked, even after flashing the KDZ. It's just the newly flashed ROM doesn't know it, and you don't need it to.
Just go to fastboot (PowerOff, Vol- while plugging in cable) and flash TWRP. Follow ChazzMatt's root guide for the initial TWRP steps.
Have anyone found the solution for this problem...
vino90m said:
Have anyone found the solution for this problem...
Click to expand...
Click to collapse
What exactly is not working?
ADB doesn't require Enable OEM Unlock to be set. Just plug it in and ADB away - unless drivers or cable or port aren't working.
And your bootloader is still unlocked if it was unlocked before you flashed stock Oreo. You should be able to enter fastboot using the steps described in the post just before yours.
Edit: Of course you have to enable USB debugging in order to use ADB. I'm sure you knew that
l3dson said:
I already found the solution, but it will erase your data.
with the adb commands you must restart the device in boorloader mode:
adb reboot bootloader
Then when I take you to the bootloader screen what you have to write next:
fastboot oem lock
(Remember the phone will be erased)
then to restart the device you have to:
fastboot reboot
And the device will reboot.
what you do is lock it, so that you can then unlock it in a simple way.
(If you do not know what the ADB is, warn man), I hope it helps you and those who enter here too :good:
Click to expand...
Click to collapse
hey i have this same problem and been asking around... but the adb reboot command will not work because it says the phone must be "enabled oem unlock" mode before you can use adb commands... which is greyed out..so back to square one... how to enable it?? any suggestions on this??
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.
Hi guys I am having an interested issue,
I want to install custom rom in my phone
I have downloaded in depth test and applied for un depth test
my mobile do connect to computer when it prompt to select mod I do select file transfer and my mobile do connect to laptop
and it shows in "adb devices" but when it goes into bootloader mod my mobile gets disconnected I have done everything I could
I have install every possible driver i got from articles but non worked is it the issue with my windows 10 ? or driver issue I have spent my whole night on this but couldn't find the way
fastboot devices
0purple said:
fastboot devices
Click to expand...
Click to collapse
what does it mean ?
when i connect my phone it prompt me with this and usb debugging is on
i tried adb devices but it didn't showed anything but when i chose transfer file it do connect to the laptop and shows in adb devices
najam489 said:
what does it mean ?
Click to expand...
Click to collapse
Try it once you are in fastboot
wow its showing
najam489 said:
wow its showing
Click to expand...
Click to collapse
0purple said:
Try it once you are in fastboot
Click to expand...
Click to collapse
i have another problem now my device is showing with fastboot devices but my devices status is locked when i tried this command "fastboot flash recovery recovery.img" it didnt work i am follwing this article https://www.guidetoroot.com/root-realme-3-pro/
thank you for your help my bootloader wasn't unlock it is now thanks a lot
It appears your device's bootloader is locked. Try:
fastboot oem unlock
fastboot flashing unlock
If that doesn't help, search for a guide on how to unlock bootloader for your specific brand.
It also looks like don't really know what you are doing. Make sure you are following trusted guide. If no, I'll be happy to help.
0purple said:
It appears your device's bootloader is locked. Try:
fastboot oem unlock
fastboot flashing unlock
If that doesn't help, search for a guide on how to unlock bootloader for your specific brand.
It also looks like don't really know what you are doing. Make sure you are following trusted guide. If no, I'll be happy to help.
Click to expand...
Click to collapse
well i did installed custom roms few time but i dont know much, i did unlock bootloader now the problem is i do install custom recovery twrp and it do installed and rom manager shows that custom recovery is installed but pressing volume down + power button just shows fastboot logo and it restart my phone, and with command "
adb reboot bootloader" i am able to boot into fastboot mood and when i go to recovery from their it open stock recovery instead of twrp
Stolen from my guide:
7. Go into fastboot mode
8. fastboot flash recovery recovery.img
9. fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
10. fastboot reboot recovery
12. Sometimes recovery doesn't want to stick as a permanent one. To test it, hold the power button and select "Reboot to recovery". If you reboot to TWRP, you can move on, but if you reboot to stock one, flash recovery using fastboot again and from recovery flash recovery again (sounds crazy, right?). I won't give you instructions on this, research it yourself. Make sure guide you will find is for your device and your recovery.