Please help, I've been trying to do this for a while now. Excuse me if i'm being dumb, I am new to the rooting scene.
So long ago, a few weeks after buying my phone, I tried to root it. Idk if the info in this paragraph is important, but somehow the wifi stopped working in the magisk boot.img and even the stock boot.img and whatever I tried it would not work and after lots of time I was able to get a custom ROM working on it and wifi worked and I got android 10. Win win! And i later updated it without issue too.
The problems start when i found out there was another update to my ROM (Pixel Experience) and for some reason updating it in the android update menu doesn't work, it downloads fine but won't install. So I go to do it in my recovery of choice (OrangeFox, I tried TWRP during this and couldn't get it to work) and it won't boot. I must have flashed it and reflashed it different ways like 50 times and asked a friend how to do it and I could not get it to boot to an OS, I even tried another ROM and a fastboot only ROM. At this point I give up, leave the phone for like 10 days. I was missing my phone a lot so I decided to give it another go yesterday. Now when I try to flash OrangeFox (I have to run fastboot commands like setting the active slot and erasing boot partition) all the fastboot commands that used to work now give me some sort of error! It's usually something like:
Code:
Erasing 'boot' FAILED (remote: 'unknown command')
fastboot: error: Command failed
And also the device randomly goes on and off and I know for sure this USB port works but the phone sometimes appears in fastboot devices and sometimes it just goes away for no reason. I'm using Linux if it matters.
Sorry if I'm doing something dumb again or didn't give some info
Related
My almost two-year-old Hero froze this morning, so I had to take out the battery, but after this I've been unable to boot, it's stuck on the HeRO screen. I can't start recovery either, the only thing working is hboot / fastboot. Erasing user data using fastboot doesn't do anything.
Also, plugging the phone into charger doesn't signalize charging – the LED doesn't light up, and the PC doesn't recognize the phone either. Only fastboot does connect the phone to the PC, but adb doesn't work and all attempts to flash a new recovery or do anything else via fastboot end with "FAILED (remote: not allowed)":
Code:
c:\adb>fastboot devices
HT97JL903267 fastboot
c:\adb>fastboot boot recovery-RA-hero-v1.7.0.1.img
downloading 'boot.img'... FAILED (remote: not allow)
c:\adb>fastboot flash boot recovery-RA-hero-v1.7.0.1.img
sending 'boot' (3972 KB)... FAILED (remote: not allow)
I tried installing the official RUU updates (2.73.405.66, 2.73.405.5 and 1.76.405.1 too) but none of them could connect to the phone, Error [170]: USB Connection error.
I was using Elelinux-Hero-2.1-update1-Reloaded with radio 63.18.55.06SU_6.35.17.03 and recovery was Amon RA 1.6.2 I guess.
The phone did a similar thing 3 weeks ago but I was able to boot into recovery and erase data and cache and it worked fine afterwards. Now only fastboot is accessible.
Is there anything else I can do at this point or is the phone dead for good?
Disregard my previous post.
I left the phone booting for 30 minutes, the battery got uncomfortably hot, but the phone booted up eventually. Then I managed to install the official RUU from here.
It didn't solve anything though – it still takes around 20 minutes to boot, the touch screen doesn't work and I get an "android.process.acore" error all the time – but since the phone seems untouched (thanks to the RUU install) I can lodge a claim and get a replacement phone hopefully.
You could try putting HEROIMG.NBH on the sdcard and booting into hboot. If you go into fastboot and press vol-down it quickly scans for files on the SD, of which heroimg is one, and if it finds them, installs them.
Can't really help more than that. My phone did that last year, took it to the shop and ended up getting a new motherboard, cause the ROM chip was knackered.
One thing I would recommend though when you get it fixed is to flash an engineering bootloader, do if it breaks again you've got none of this "remote not allow" rubbish.
Of all the times to say disregard my last post.........
Sorry about that, thanks a lot though!
I suppose some hardware is broken in my Hero as well, I will take it back to the shop tomorrow.
Thanks again!
Hi,
I'm new here, so please excuse me if I am posting in the wrong category.
So I tried to root my Doogee F7 (not the pro version) using fastboot and TWRP, and it resulted in a sort of bootloop where it says:
Code:
Orange State
Your device has been unlocked and can't be trusted
Your device will boot in 5 seconds
And then it restarts and gives the same message again. This loop has been going on for some time and I can't stop it because the phone has a non-removable battery and I have tried every possible combination of buttons (i.e. Power + Volume Down + Volume Up).
The process I used in my attempt to root was as following:
1. I used
Code:
adb reboot bootloader
to go into fastboot. (I already set up everything like USB debugging and OEM unlocking in the developer options)
2. I then used
Code:
fastboot oem unlock
and pressed Volume Up to unlock the bootloader. All was successful.
3. I then tried to flash TWRP to recovery and I believe this is where everything went wrong. I flashed it using
Code:
fastboot flash recovery recovery.img
and it was successful, according to the command prompt:
Code:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash recovery "C:\Users\momen\Downloads\recovery (1).img"
target reported max download size of 134217728 bytes
sending 'recovery' (12832 KB)...
OKAY [ 0.562s]
writing 'recovery'...
OKAY [ 0.213s]
finished. total time: 0.779s
4. After it finished I used
Code:
fastboot reboot
to reboot the phone and that's when it got stuck.
At the moment I am just letting my battery run out, as I have no other way of turning off the phone, and neither adb nor fastboot is working.
I don't really know if my device was even supported, but I followed the instructions on various websites stating that I should first unlock my bootloader, then flash TWRP, then flash superSU onto it, and my phone would be rooted. I used the latest TWRP image, and I think that was where I went wrong. Is there anything I can do to get my phone to work again?
Hey! i´m sorry for your phone, can you tell me any updates, is it fixed now? what happened? i am about to do the same process to root my Doogee F7 and i´m very worried that my phone gets bricked, so please, i need your recommendations.
I hope everything is alright with your phone.
solartediego said:
Hey! i´m sorry for your phone, can you tell me any updates, is it fixed now? what happened? i am about to do the same process to root my Doogee F7 and i´m very worried that my phone gets bricked, so please, i need your recommendations.
I hope everything is alright with your phone.
Click to expand...
Click to collapse
Ah yes, sorry for not updating. I managed to connect my phone to my PC again using the flash tool and then I could flash the original ROM back onto it. I found the ROM by Googling for a bit tho I dont have a link. Be aware that if you do this, it basically factory resets your phone, locking your bootloader again and all. If you do manage to root your phone please contact me as I still have not managed to do so.
Edit: This process of flashing back your ROM always works as long as your phone powers on, so don't worry too much about bricking your phone. I think I've bricked my phone over 20 times trying to root it, and it worked every single time.
Hello there. I suggest that you use "fastboot boot recovery.img" than using "fastboot flash" if you are not sure if the custom recovery works (or if you just want to test/try it). In this way, you'll just boot the custom recovery temporarily (and your stock recovery is still in tacked).
For rooting your device, first you'll need a working custom recovery for your device (you used TWRP, very first if it works or compatible with your device).
Insyder28 said:
Ah yes, sorry for not updating. I managed to connect my phone to my PC again using the flash tool and then I could flash the original ROM back onto it. I found the ROM by Googling for a bit tho I dont have a link. Be aware that if you do this, it basically factory resets your phone, locking your bootloader again and all. If you do manage to root your phone please contact me as I still have not managed to do so.
Edit: This process of flashing back your ROM always works as long as your phone powers on, so don't worry too much about bricking your phone. I think I've bricked my phone over 20 times trying to root it, and it worked every single time.
Click to expand...
Click to collapse
Hi.How you actually managed to connect your phone to PC using flash tool if you were in a bootloop and had no access to fastboot mode or recovery?
ciubsy2004 said:
Hi.How you actually managed to connect your phone to PC using flash tool if you were in a bootloop and had no access to fastboot mode or recovery?
Click to expand...
Click to collapse
Im interested too in your process to flash TWRP again, as i am in the same boot loop than you with a Doogee S60. I´ve waited till the battery ended, but now flash tool doesn´t recognize my phone. If i charge the battery, i get a boot loop again..
TheBidan said:
Im interested too in your process to flash TWRP again, as i am in the same boot loop than you with a Doogee S60. I´ve waited till the battery ended, but now flash tool doesn´t recognize my phone. If i charge the battery, i get a boot loop again..
Click to expand...
Click to collapse
I have managed to get the flash tool recognizing my phone.Had to keep pressed volume up,if i recall properly(or try volume down) before connecting usb cable to phone with flash tool opened and . It was a while ago though and i can't remember exactly which key was for sure. Hope this helps
EDIT: I plugged a USB 2.0 hub in my pc, and now it works flawlessly. I'm leaving this here if someone faces the same problem I had.
I'm a long time user of custom roms, I was in Paranoid Android but wanted to try MIUI 12. Now, after using it for some days, I wanted to go back, but fastboot doesn't allow to flash recovery (TWRP 3.3, official).
If i put fastboot.exe devices, the output is my ID
Code:
dbb4eed4 fastboot
However, If I put it for a second time, the output is the following, and my phone screen turns black, asking for a key to shutdown.
Code:
???????????? fastboot
For fastboot.exe flash recovery twrp.img, the output is the following, also turning the screen black.
Code:
Sending 'recovery' (31068 KB) FAILED (Write to device failed (Invalid argument))
fastboot: error: Command failed
Both options regarding USB debugging are on (the second one asked for a Xiaomi ID), bootloader was unlocked long time ago.
Any ideas what's happening? Is MIUI 12 messing with fastboot?
Thanks in advance.
Did you did that after usb debugging turned on
Did you try command like adb shell?
If you did this usb debugging will pop up for the recognition with your pc to smartphone
Yes Miui ask for ID it is your phone number which was you put when you try to unlock bootloader
And for recovery try different recovery
I DO feel MIUI 12 messed up something on the internals. For example, earlier I was able to easily paste files to /system/xbin location, but after upgrading to MIUI 12 it has suddenly become read only. Very weird.
HearseRider said:
I DO feel MIUI 12 messed up something on the internals. For example, earlier I was able to easily paste files to /system/xbin location, but after upgrading to MIUI 12 it has suddenly become read only. Very weird.
Click to expand...
Click to collapse
It's because your space directory is full.
I had this problem there too, I solved it by reseting dalvik cache with twrp
I seem to have completely knackered my phone and maybe someone can help. I've spent days trying to install a custom rom on my G8 power XT2041-3. The bootloader was unlocked. I had TWRP on it and couldn't figure out why I couldn't go to fastbootd to install the Resurrection Remix ROM or HavocOS ROM. Eventually I found the stock firmware for my device and flashed the stock recovery.img to replace TWRP. I was hopeful when I finally saw fastbootd on my screen and went ahead to flash boot.img (all seemed fine) followed by flash system of the custom ROM. It got to 3/3 and then said something about Failed: Operation not Permitted. I can't remember the exact wording now and can't try again because my phone is pretty much useless.
If I try to power on my phone it takes ages trying to boot (alternately between the bootloader unlocked warning and the big M for Motorola), but eventually I get a message saying:
Boot Failed. Press Power Key to Retry
No bootable A/B slot
Failed to boot Linux, falling back to fastboot
Fastboot Reaso: Fall through from normal boot mode
Nothing seems to work. I can't boot into any recovery. The phone won't start at all apart from this very basic looking bootloader. My device is recognised by fastboot devices but that's about it. I can't flash fastboot commands. I tried flash partition gpt.bin. I tried to flash recovery.img again. A few things. But nothing works.
I'm using Linux so can't download RSD Lite that I wanted to try or the Motorola Research and Smart Assistant. Does anybody have any suggestions please? I'm at my wits end with the thing.
Thanks
jibbajobs said:
I seem to have completely knackered my phone and maybe someone can help. I've spent days trying to install a custom rom on my G8 power XT2041-3. The bootloader was unlocked. I had TWRP on it and couldn't figure out why I couldn't go to fastbootd to install the Resurrection Remix ROM or HavocOS ROM. Eventually I found the stock firmware for my device and flashed the stock recovery.img to replace TWRP. I was hopeful when I finally saw fastbootd on my screen and went ahead to flash boot.img (all seemed fine) followed by flash system of the custom ROM. It got to 3/3 and then said something about Failed: Operation not Permitted. I can't remember the exact wording now and can't try again because my phone is pretty much useless.
If I try to power on my phone it takes ages trying to boot (alternately between the bootloader unlocked warning and the big M for Motorola), but eventually I get a message saying:
Boot Failed. Press Power Key to Retry
No bootable A/B slot
Failed to boot Linux, falling back to fastboot
Fastboot Reaso: Fall through from normal boot mode
Nothing seems to work. I can't boot into any recovery. The phone won't start at all apart from this very basic looking bootloader. My device is recognised by fastboot devices but that's about it. I can't flash fastboot commands. I tried flash partition gpt.bin. I tried to flash recovery.img again. A few things. But nothing works.
I'm using Linux so can't download RSD Lite that I wanted to try or the Motorola Research and Smart Assistant. Does anybody have any suggestions please? I'm at my wits end with the thing.
Thanks
Click to expand...
Click to collapse
If you don't have a windows running computer, you can try a virtual machine with Virtual Box to emulate a Windows computer and try the Motorola Research and Smart Assistant
Constantinologia said:
If you don't have a windows running computer, you can try a virtual machine with Virtual Box to emulate a Windows computer and try the Motorola Research and Smart Assistant
Click to expand...
Click to collapse
Thank you very much for that. I'd never heard of Virtual Box before. I'll have more time tomorrow to install it and see how I get on. Hopefully I can fix it because I think I'm all out of other options. Much appreciated!
Hey community,
I have been running Poco F1 with twrp and PixelExperience for the last 2 years. Considering the past record of the OS and my experience with the OS, I decided recently to upgrade to the newer PE12 for Poco F1 (maintained by Lakshay Garg). It went smooth initially and after the last OTA update, the phone started behaving weirdly.
Long story short,
This morning the phone went into an automatic restart and is now stuck in a boot loop. It boots and reaches the "G" logo and reboots. However, the weird part is,
Code:
fastboot flash
and
Code:
fastboot boot
are not available, throwing errors. The device is visible in
Code:
adb devices
and
Code:
fastboot devices
. This problem occurs when the phone is not plugged in. Once plugged in, the phone runs fine and everything just works. TWRP is not accessible, as if it is not there anymore and the only recovery that I can reach is the pixel recovery which has no option to flash any custom recovery (newbie, so not sure if something like this should exists or not).
I've tried various threads here and wasn't able to find any solution. Let me know what commands/outputs you guys might need from the device to help me in this.
Thanks in advance. Hope this gets fixed soon.
tysonX5653 said:
Hey community,
I have been running Poco F1 with twrp and PixelExperience for the last 2 years. Considering the past record of the OS and my experience with the OS, I decided recently to upgrade to the newer PE12 for Poco F1 (maintained by Lakshay Garg). It went smooth initially and after the last OTA update, the phone started behaving weirdly.
Long story short,
This morning the phone went into an automatic restart and is now stuck in a boot loop. It boots and reaches the "G" logo and reboots. However, the weird part is,
Code:
fastboot flash
and
Code:
fastboot boot
are not available, throwing errors. The device is visible in
Code:
adb devices
and
Code:
fastboot devices
. This problem occurs when the phone is not plugged in. Once plugged in, the phone runs fine and everything just works. TWRP is not accessible, as if it is not there anymore and the only recovery that I can reach is the pixel recovery which has no option to flash any custom recovery (newbie, so not sure if something like this should exists or not).
I've tried various threads here and wasn't able to find any solution. Let me know what commands/outputs you guys might need from the device to help me in this.
Thanks in advance. Hope this gets fixed soon.
Click to expand...
Click to collapse
Seems to be a battery problem. How old is it? You may need to replace it.
However make sure you followed the clean install method before you come on a conclusion. Also try to not use any Magisk modules.
Best Clean Install method:
Backup all your data. All your data into Internal Storage will be lost during this process.
Download latest Official TWRP Recovery, Pixel Experience build.
Create one Folder and move all the files you downloaded there.
Reboot to Fastboot Mode
Connect your device to PC and Boot into to TWRP via ADB or Minimal ADB and Fastboot:
Code:
fastboot boot <recovery_filename>.img
Example:
Code:
fastboot boot C:\Users\Retrial\Desktop\twrp-3.6.1_9-0-beryllium.img
Select Wipe > Advanced Wipe -> Select Dalvik / ART Cache, System, Data, Internal Storage, Vendor, Cache and then Swipe to Wipe.
Go back and select Wipe > Format Data > type yes
While you are in TWRP, transfer the Folder with the files you downloaded above.
Flash Pixel Experience ROM.
Flashing the ROM will replace TWRP with PE Recovery so OTA updates can be installed without problems since TWRP currently doesn't support decryption on A12 encypted ROMs - If you need in future to change ROM just fastboot boot to twrp via adb and flash img of twrp to recovery partition.
Done! Reboot to system.
Thanks, turns out that it was a battery problem after all. After battery replacement everything is working just fine. I also installed Awaken OS as Pixel Experience was removing the TWRP recovery each time I flashed it. Now as for my fastboot, initially it was not working; it was showing this error whenever I tried to flash TWRP recovery or any stock recovery:
Sending 'boot.img' (38640 KB) FAILED (Write to device failed (Cannot send after transport endpoint shutdown)) fastboot: error: Command failed
After this, the fastboot mode was diconnected and my phone was showing this Error:
Press any Key to Shut Down
It was resolved by running this bat file (as admin) :
https://bit.ly/31T2LcB
After running this file, there was no error and I was able to flash the twrp Recovery smoothly. So thanks for all the help really appreciate it.
tysonX5653 said:
Thanks, turns out that it was a battery problem after all. After battery replacement everything is working just fine. I also installed Awaken OS as Pixel Experience was removing the TWRP recovery each time I flashed it. Now as for my fastboot, initially it was not working; it was showing this error whenever I tried to flash TWRP recovery or any stock recovery:
Sending 'boot.img' (38640 KB) FAILED (Write to device failed (Cannot send after transport endpoint shutdown)) fastboot: error: Command failed
After this, the fastboot mode was diconnected and my phone was showing this Error:
Press any Key to Shut Down
It was resolved by running this bat file (as admin) :
https://bit.ly/31T2LcB
After running this file, there was no error and I was able to flash the twrp Recovery smoothly. So thanks for all the help really appreciate it.
Click to expand...
Click to collapse
Did you face the problem again?
I am using PE11 since last 2 years but suddenly i started facing the same problem. When plugged in, works fine. When I unplug it, works until screen is on and when I use power button to lock or unlock, phone goes into bootloop. I opend it in twrp where it can work as long as battery lasts, that's why I am not sure if it's a battery problem or something else