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.
Hello everyone, this is my first post on the forum.
I have a xiaomi redmi note 4 snapdragon with bootloader unlocked and when I try to install TWRP by ADB it installs it, but when I put the command "flashboot boot twrp.img" it stays in the fastboot logo.
Try using power and volume + to enter the recovery, but enter the original recovery
Can anyone help me? Thank you
Merli- said:
Hello everyone, this is my first post on the forum.
I have a xiaomi redmi note 4 snapdragon with bootloader unlocked and when I try to install TWRP by ADB it installs it, but when I put the command "flashboot boot twrp.img" it stays in the fastboot logo.
Try using power and volume + to enter the recovery, but enter the original recovery
Can anyone help me? Thank you
Click to expand...
Click to collapse
Which output do you get in ADB after you type in the command?
Merli- said:
Hello everyone, this is my first post on the forum.
I have a xiaomi redmi note 4 snapdragon with bootloader unlocked and when I try to install TWRP by ADB it installs it, but when I put the command "flashboot boot twrp.img" it stays in the fastboot logo.
Try using power and volume + to enter the recovery, but enter the original recovery
Can anyone help me? Thank you
Click to expand...
Click to collapse
Could be possible due to old drivers.
Try these platform tools
https://drive.google.com/file/d/13Sjej5zIJPm_yiJQOVR4rEocwbhDc9oh/view?usp=drivesdk
Noter2017 said:
Which output do you get in ADB after you type in the command?
Click to expand...
Click to collapse
downloading 'boot.img'...
OKAY [ 0.792s]
booting...
OKAY [ 0.558s]
finished. total time: 1.353s
After that, it disconnects from the PC and stays in the fastboot logo
MyNameIsRage said:
Could be possible due to old drivers.
Try these platform tools
Try and it does not work, the same thing happens :S
Click to expand...
Click to collapse
MyNameIsRage said:
Could be possible due to old drivers.
Try these platform tools
Click to expand...
Click to collapse
Try and it does not work, the same thing happens :S
Merli- said:
Try and it does not work, the same thing happens :S
Click to expand...
Click to collapse
What process do you follow?
I happened to do it, by copying the recovery file inside the platform tools folder.
Then inside the folder hold shift and right click. It will show an option to open command prompt window or open powershell window here. From there i wrote the commands, fastboot flash recovery recovery.img , and then manually booted to twrp by holding the vol up and power
MyNameIsRage said:
What process do you follow?
I happened to do it, by copying the recovery file inside the platform tools folder.
Then inside the folder hold shift and right click. It will show an option to open command prompt window or open powershell window here. From there i wrote the commands, fastboot flash recovery recovery.img , and then manually booted to twrp by holding the vol up and power
Click to expand...
Click to collapse
I followed that process and it did not work, try two different versions of Twrp and it still did not work. I resigne myself, and try to install the RedWolf recovery with the same process, and this time it works! :fingers-crossed: I could finally install another rom. Thanks for the help
Same problem here, really strange. First time I've this kind of problem.
Edit : Ok, problem solved. There is 2 things to do in addition of the main installation process (found here : https://wiki.lineageos.org/devices/mido/install#installing-a-custom-recovery-using-fastboot )
Firstly, you have to enable OEM Unlocking in Developer option menu. And not only enable USB Debugging. To enable it, click twice on the button "OEM Unlock" (if you click once, it will disable automatically when exiting Dev' menu).
Secondly, once you ran
Code:
fastboot flash recovery twrp-x.x.x-x-mido.img
, you also have to ran
Code:
fastboot boot twrp-x.x.x-x-mido.img
in order to reboot in recovery mode. Otherwise default recovery will automatically erase and replace TWRP.
These 2 steps are quite never documented, but are mandatory for Mido (Redmi Note 4) !!
Skip88 said:
Same problem here, really strange. First time I've this kind of problem.
Click to expand...
Click to collapse
In my case the problem appeared since repair and replace the screen. The unique twrp I could install from ADB was twrp RedWolf
Merli- said:
In my case the problem appeared since repair and replace the screen. The unique twrp I could install from ADB was twrp RedWolf
Click to expand...
Click to collapse
I've edited my post. There is 2 missing steps to be able to install TWRP correctly (then LineageOS^^).
thanks a lot u r a lifesaver.....
Skip88 said:
Same problem here, really strange. First time I've this kind of problem.
Edit : Ok, problem solved. There is 2 things to do in addition of the main installation process (found here : https://wiki.lineageos.org/devices/mido/install#installing-a-custom-recovery-using-fastboot )
Firstly, you have to enable OEM Unlocking in Developer option menu. And not only enable USB Debugging. To enable it, click twice on the button "OEM Unlock" (if you click once, it will disable automatically when exiting Dev' menu).
Secondly, once you ran
Code:
fastboot flash recovery twrp-x.x.x-x-mido.img
, you also have to ran
Code:
fastboot boot twrp-x.x.x-x-mido.img
in order to reboot in recovery mode. Otherwise default recovery will automatically erase and replace TWRP.
These 2 steps are quite never documented, but are mandatory for Mido (Redmi Note 4) !!
Click to expand...
Click to collapse
Thanks a lot u r a lifesaver.....trying it since last 2 days...now finally it worked after i followed ur above mentioned steps...now i just to wait to see if it isnt in bootloop and then i ll check my root status....thanks
Hey, I'm trying to install OrangeFox recovery in my Redmi 5 Plus but in the moment I boot up in Fastboot mode it automatically turns off, so it doesn't let me flash recovery because it reboots by itself, what could it be?
abrahamrhs said:
Hey, I'm trying to install OrangeFox recovery in my Redmi 5 Plus but in the moment I boot up in Fastboot mode it automatically turns off, so it doesn't let me flash recovery because it reboots by itself, what could it be?
Click to expand...
Click to collapse
after putting the phone into fastboot what you must quickly write the commands and run them otherwise the system will restart. Don't delay in writing the commands in the command prompt. Write them before hand and keep the commands ready
aniruddho69 said:
after putting the phone into fastboot what you must quickly write the commands and run them otherwise the system will restart. Don't delay in writing the commands in the command prompt. Write them before hand and keep the commands ready
Click to expand...
Click to collapse
Adb drivers are not properly installed in pc.... .. I've also been through this problem
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.