Hi
I got my HTC One replaced because of some screen issue . On my earlier phone i had the bootloader unlocked and had Trickdroid running great.
I got the replacement and unlocked the bootloader and flash CMW recovery , but i am not able to boot into recovery i tried both the AIO kit and
power + up and power + vold down the phone just keeps rebooting doesnt ever going into the recovery . Is there something i am missing ?
dint have this issues first time aroung on my other HTC ONe.
any help is appreciated
THanks
if i flash the stock att recovery and reboot to recovery , i am able to boot into recovery. this is strange
i flashed back CWM and see that it again keeps rebooting . i tried the perm root tool and this is the error i am gettign
E:\HTC_One\One_M7_All-In-One_Kit_v1.0\data>adb shell "echo 'boot-recovery ' > /c
ache/recovery/command"
/system/bin/sh: can't create /cache/recovery/command: Permission denied
E:\HTC_One\One_M7_All-In-One_Kit_v1.0\data>adb shell "echo '--update_package=SDC
ARD:SuperSU.zip' >> /cache/recovery/command"
/system/bin/sh: can't create /cache/recovery/command: Permission denied
E:\HTC_One\One_M7_All-In-One_Kit_v1.0\data>adb shell "reboot recovery"
reboot: Operation not permitted
E:\HTC_One\One_M7_All-In-One_Kit_v1.0\data>pause
Press any key to continue . . .
event tried
fastboot boot Recoveries\TWRP.img
it still reboots the phone
assuming flashing the recovery was successful (fastboot flash recovery recovery.img), have you tried fastboot erase cache ?
what is the output of those two commands when running them from your pc's cmd prompt?
colmustrd said:
assuming flashing the recovery was successful (fastboot flash recovery recovery.img), have you tried fastboot erase cache ?
what is the output of those two commands when running them from your pc's cmd prompt?
Click to expand...
Click to collapse
E:\HTC_One\One_M7_All-In-One_Kit_v1.0\data>fastboot flash recovery Recoveries\TW
RP.img
sending 'recovery' (7916 KB)...
OKAY [ 1.183s]
writing 'recovery'...
OKAY [ 0.640s]
finished. total time: 1.829s
E:\HTC_One\One_M7_All-In-One_Kit_v1.0\data>fastboot erase cache
erasing 'cache'...
OKAY [ 0.054s]
finished. total time: 0.057s
one thing i notice is in the bootloader mode it just says unlocked , but on my earlier HTC One it use to say both
Tampered and unlocked does that matter ?
i even tried to relock it and unlock it again hoping it would say tampered.
Thanks
anilkuj said:
one thing i notice is in the bootloader mode it just says unlocked , but on my earlier HTC One it use to say both
Tampered and unlocked does that matter ?
i even tried to relock it and unlock it again hoping it would say tampered.
Thanks
Click to expand...
Click to collapse
unlocked is for your bootloader, and tampered I dont remember exactly if it showed up after I flashed the new recovery or later (after rooting it).
I would try the following:
unlock your bootloader again
erase the cache again: fastboot erase cache
attempt to flash the recovery one more time: fastboot flash recovery recovery.img
reboot via adb: adb reboot recovery
thanks for your help
i was trying this and finally got it working
http://forum.xda-developers.com/showpost.php?p=40516203&postcount=40
anilkuj said:
thanks for your help
i was trying this and finally got it working
http://forum.xda-developers.com/showpost.php?p=40516203&postcount=40
Click to expand...
Click to collapse
you are very welcome, glad you were able to get the phone into recovery.
Related
im on hboot 1.50000 and ive fastbooted on windows 7 many times with no problems well my windows is down and now all i got is my ubuntu pc. so i have all the files i need to fastboot but when i type "./fastboot-linux flash recovery cwm-4.0.1.4-shooter.img" into the terminal all it says is "waiting on device" what am i missing any help would be greatly appreciated. something has happend to my MIUI rom and it has rendered my phone useless
Rally187 said:
im on hboot 1.50000 and ive fastbooted on windows 7 many times with no problems well my windows is down and now all i got is my ubuntu pc. so i have all the files i need to fastboot but when i type "./fastboot-linux flash recovery cwm-4.0.1.4-shooter.img" into the terminal all it says is "waiting on device" what am i missing any help would be greatly appreciated. something has happend to my MIUI rom and it has rendered my phone useless
Click to expand...
Click to collapse
fastboot is much simplier on linux as no drivers are required. the only catch will be ubuntu requires the user to be root by default before allowing usb access which fastboot requires.
the easiest work around is adding "sudo" in front of your fastboot command, assuming you have root access on the ubuntu machine.
the better method is to modify the usb permissions to allow non root users access.
hope that helps!
I appreciate your help and im getting one step closer.
[email protected]:~/Desktop/rootevo3dnew$ sudo ./fastboot-linux flash recovery cwm-4.0.1.4-shooter.img
sending 'recovery' (4832 KB)... OKAY
writing 'recovery'... OKAY
Thats what im getting to nothing on the phone happens and nothing happens on the terminal. any ideas. thanks again for your help
Rally187 said:
I appreciate your help and im getting one step closer.
[email protected]:~/Desktop/rootevo3dnew$ sudo ./fastboot-linux flash recovery cwm-4.0.1.4-shooter.img
sending 'recovery' (4832 KB)... OKAY
writing 'recovery'... OKAY
Thats what im getting to nothing on the phone happens and nothing happens on the terminal. any ideas. thanks again for your help
Click to expand...
Click to collapse
yea, those results look correct. your command is flashing the recovery to the "recovery" partition on the device.
once you've flashed the recovery to the device, you should be able to reboot the device into recovery mode and load cwm version 4.0.1.4.
if you used the htc unlock method, you'll probably prefer to use the fastboot boot cwm-4.0.1.4-shooter.img command as that will temporarily load the custom recovery but will grant it write access to the boot partition. the htc unlock method blocks write access to the boot partition while booted into recovery mode, but allows write access to the boot partition while fastboot booting the recovery image.
hope that helps!
joeykrim said:
yea, those results look correct. your command is flashing the recovery to the "recovery" partition on the device.
once you've flashed the recovery to the device, you should be able to reboot the device into recovery mode and load cwm version 4.0.1.4.
if you used the htc unlock method, you'll probably prefer to use the fastboot boot cwm-4.0.1.4-shooter.img command as that will temporarily load the custom recovery but will grant it write access to the boot partition. the htc unlock method blocks write access to the boot partition while booted into recovery mode, but allows write access to the boot partition while fastboot booting the recovery image.
hope that helps!
Click to expand...
Click to collapse
YOU ARE A [email protected]! GENIUS THANK YOU THANK YOU!! as soon as i saw fastboot boot cwm-4.0.1.4-shooter.img i knew exactly what i was doing wrong i cannot believe i overlooked this for so long. i wish i could thank you more then just once. THANK YOU!!
Hi, i have an unlocked tf201 and tried to install recovery-clockwork-touch-5.8.1.8-tf201.img which seemd to go fine:
Code:
sudo ./fastboot -i 0x0b05 flash recovery recovery-clockwork-touch-5.8.1.8-tf201.img
sending 'recovery' (5380 KB)...
OKAY [ 2.432s]
writing 'recovery'...
OKAY [ 7.011s]
finished. total time: 9.443s
hamlet:Console_Connection michael$ ./fastboot reboot
rebooting...
finished. total time: 0.001s
Thing is the recovery console will not load, after i select it (RCK) nothing happens? The message at top of screen says
Code:
Booting into recovery kernel image
If power off and on again it will boot fine into latest Asus jelly bean rom.
I have tried to re-flash, but now i can no longer find the device in OSX?
Code:
adb devices
List of devices attached
This is the same in both fastboot and when booted normally?
Any ideas?
many thanks
Seems i can find it as a device with adb when booted normally, but not when in fastboot?
ah seems it does not matter if not seen as device when in fastboot as i tried flash again it it seems to work
Code:
sudo ./fastboot -i 0x0b05 flash recovery recovery-clockwork-touch-5.8.1.8-tf201.img
Password:
sending 'recovery' (5380 KB)...
OKAY [ 2.427s]
writing 'recovery'...
OKAY [ 6.286s]
finished. total time: 8.713s
but still it will not boot into recovery?
Thanks
Even tried flashing openrecovery-twrp for jb, but still won't boot into recovery?
any help here would very much appriciated
carperman said:
Even tried flashing openrecovery-twrp for jb, but still won't boot into recovery?
any help here would very much appriciated
Click to expand...
Click to collapse
You are not saying what we need to know.
What bootloader are you on ? Where is the "NVIDIA" logo when you first power on the device? Bottom center or bottom right ?
flumpster said:
You are not saying what we need to know.
What bootloader are you on ? Where is the "NVIDIA" logo when you first power on the device? Bottom center or bottom right ?
Click to expand...
Click to collapse
flumpster said:
You are not saying what we need to know.
What bootloader are you on ? Where is the "NVIDIA" logo when you first power on the device? Bottom center or bottom right ?
Click to expand...
Click to collapse
Sorry thought i had made it clear?
Thanks for the reply i will try and be clearer.
In answer to your question about nvidia logo, it is bottom right.
What i have:
New TF201
unlocked when running ICS
Updated to latest Asus Jelly Bean rom
What i want to achieve:
I wish to root tablet (super user) and eventually install a custom rom.
What i need to do:
Flash clockwork-touch
install superuser.zip via recovery console
Results:
adb devices - report device
fastboot devices - shows no devices
boot to fastboot with 'power/vol ok
fastboot -i 0x0b05 flash recovery *.img - seems to work, see OP
fastboot reboot-bootloader works though recovery never loads
boot to recovery with 'power/vol never loads
For the last 2 it just says
Booting into recovery kernel image
I tried installing rtr_recovery-clockwork-touch which patched version, which again seems to work
Code:
fastboot -i 0x0b05 flash recovery rtr_recovery-clockwork-touch-5.8.1.8-tf201/recoveryblob
sending 'recovery' (5398 KB)...
OKAY [ 2.387s]
writing 'recovery'...
OKAY [ 6.398s]
finished. total time: 8.785s
Code:
fastboot reboot-bootloader
rebooting into bootloader...
OKAY [ 0.001s]
finished. total time: 0.001s
This worked, but as before nothing happens it just sits at B]
Booting into recovery kernel image[/B]
The two issue i have are:
fastboot cannot see devices (seem to work though)
recovery is not loading
I can only assume that even though fastboot seems to flashing device, blue load bar appears on tablet and reboot-bootloader commands works, it is not actually flashing the device?
thanks
carperman said:
Sorry thought i had made it clear?
Thanks for the reply i will try and be clearer.
In answer to your question about nvidia logo, it is bottom right.
What i have:
New TF201
unlocked when running ICS
Updated to latest Asus Jelly Bean rom
What i want to achieve:
I wish to root tablet (super user) and eventually install a custom rom.
What i need to do:
Flash clockwork-touch
install superuser.zip via recovery console
Results:
adb devices - report device
fastboot devices - shows no devices
boot to fastboot with 'power/vol ok
fastboot -i 0x0b05 flash recovery *.img - seems to work, see OP
fastboot reboot-bootloader works though recovery never loads
boot to recovery with 'power/vol never loads
For the last 2 it just says
Booting into recovery kernel image
I tried installing rtr_recovery-clockwork-touch which patched version, which again seems to work
Code:
fastboot -i 0x0b05 flash recovery rtr_recovery-clockwork-touch-5.8.1.8-tf201/recoveryblob
sending 'recovery' (5398 KB)...
OKAY [ 2.387s]
writing 'recovery'...
OKAY [ 6.398s]
finished. total time: 8.785s
Code:
fastboot reboot-bootloader
rebooting into bootloader...
OKAY [ 0.001s]
finished. total time: 0.001s
This worked, but as before nothing happens it just sits at B]
Booting into recovery kernel image[/B]
The two issue i have are:
fastboot cannot see devices (seem to work though)
recovery is not loading
I can only assume that even though fastboot seems to flashing device, blue load bar appears on tablet and reboot-bootloader commands works, it is not actually flashing the device?
thanks
Click to expand...
Click to collapse
First off, awesome report. Far more than I needed but I won't have to ask you another question along the way from now on.
You are on the jellybean bootloader. You should not even be flashing CWM while on that because that is how so many people hard brick their devices.
Can you please try downloading the custom TWRP I have in the following link that I have installed myself and made for the jellybean bootloader so I know this is where we are both at. The zip file has a bat file and you just run it and follow onscreen instructions.
http://forum.xda-developers.com/showpost.php?p=26595675&postcount=2
You want Hairybean TWRP Updater (normal).
Please do not try to install CWM at any point from now on.
flumpster said:
First off, awesome report. Far more than I needed but I won't have to ask you another question along the way from now on.
You are on the jellybean bootloader. You should not even be flashing CWM while on that because that is how so many people hard brick their devices.
Can you please try downloading the custom TWRP I have in the following link that I have installed myself and made for the jellybean bootloader so I know this is where we are both at. The zip file has a bat file and you just run it and follow onscreen instructions.
http://forum.xda-developers.com/showpost.php?p=26595675&postcount=2
You want Hairybean TWRP Updater (normal).
Please do not try to install CWM at any point from now on.
Click to expand...
Click to collapse
Thanks, will give it a try.
Must have done something as cannot get adb to find device when in fastboot now?
Tried rebooting workstation and tablet a few times, but no joy
and your bat file did not find device either?
carperman said:
Must have done something as cannot get adb to find device when in fastboot now?
Tried rebooting workstation and tablet a few times, but no joy
and your bat file did not find device either?
Click to expand...
Click to collapse
adb does not work in fastboot. Only the fastboot command does. The only places you can use adb is either while in the OS or while in recovery.
The .bat file would have tried to run a fastboot flash command.
Here is odd thing though, even though adb devices shows nothing and the .bat can't find connection the command fastboot reboot-bootloader works?
Note the error i get with .bat is
./HairyBean TWRP Recovery Flasher.bat: line 1: @echo: command not found
************************************************
HairyBean TWRP Jelly Bean Recovery Flasher
: command not foundcovery Flasher.bat: line 4: echo.
1. Turn OFF the device
./HairyBean TWRP Recovery Flasher.bat: line 6: syntax error near unexpected token `('
'/HairyBean TWRP Recovery Flasher.bat: line 6: `echo 2. Turn ON the device (hold power + vol down)
hamlet:HairyBean TWRP Updater 2.4.1.0 (normal) michael$ ./HairyBean\ TWRP\ Recovery\ Flasher.bat
./HairyBean TWRP Recovery Flasher.bat: line 1: @echo: command not found
************************************************
HairyBean TWRP Jelly Bean Recovery Flasher
: command not foundcovery Flasher.bat: line 4: echo.
1. Turn OFF the device
./HairyBean TWRP Recovery Flasher.bat: line 6: syntax error near unexpected token `('
'/HairyBean TWRP Recovery Flasher.bat: line 6: `echo 2. Turn ON the device (hold power + vol down)
hamlet:HairyBean TWRP Updater 2.4.1.0 (normal)
Just noticed that fastboot now find device though
fastboot devices
015d0787bf2fee07 fastboot
thanks
carperman said:
Here is odd thing though, even though adb devices shows nothing and the .bat can't find connection the command fastboot reboot-bootloader works?
Note the error i get with .bat is
./HairyBean TWRP Recovery Flasher.bat: line 1: @echo: command not found
************************************************
HairyBean TWRP Jelly Bean Recovery Flasher
: command not foundcovery Flasher.bat: line 4: echo.
1. Turn OFF the device
./HairyBean TWRP Recovery Flasher.bat: line 6: syntax error near unexpected token `('
'/HairyBean TWRP Recovery Flasher.bat: line 6: `echo 2. Turn ON the device (hold power + vol down)
hamlet:HairyBean TWRP Updater 2.4.1.0 (normal) michael$ ./HairyBean\ TWRP\ Recovery\ Flasher.bat
./HairyBean TWRP Recovery Flasher.bat: line 1: @echo: command not found
************************************************
HairyBean TWRP Jelly Bean Recovery Flasher
: command not foundcovery Flasher.bat: line 4: echo.
1. Turn OFF the device
./HairyBean TWRP Recovery Flasher.bat: line 6: syntax error near unexpected token `('
'/HairyBean TWRP Recovery Flasher.bat: line 6: `echo 2. Turn ON the device (hold power + vol down)
hamlet:HairyBean TWRP Updater 2.4.1.0 (normal)
Just noticed that fastboot now find device though
fastboot devices
015d0787bf2fee07 fastboot
thanks
Click to expand...
Click to collapse
I see a michael subfix in there. Are you running this zip from desktop or a link? Can you please try extracting the zip to a physical drive (e.g. make a folder on d: and call it wookie then extract the zip in it.
I have seen before this script failing on desktop.
edit... I have just looked back at your earlier outputs. Are you in linux because I presumed you was on windows when I started? The .bat file is for windows and it will probably not even work in linux because of the links.
ok sorted, checked the .bat and is for windows i am on OSX so did
fastboot -i 0x0B05 flash recovery fastboot/recoveryTWRP.blob
and it works
great many thanks, now to try your custom rom
carperman said:
ok sorted, checked the .bat and is for windows i am on OSX so did
fastboot -i 0x0B05 flash recovery fastboot/recoveryTWRP.blob
and it works
great many thanks, now to try your custom rom
Click to expand...
Click to collapse
Cool, glad you got it sorted.
Just know that you don't need to root first. Root is built into the roms and is not needed to flash.
Also please never try CWM again... From now on if you grab the official TWRP as needed make sure you get the JB version.
gl mate.
Awesome man this worked fine for me, had the same problem I guess koush needs to do his homework on the devices, or I do one..
Hi all,
I have a small problem, my phone does not boot and hanging on Logo. Now i can boot to fastboot menu, but i cannot really use it since i have FRP lock . Is there any chance to baypass it to make possible to flash recovery boot.img ?
When i try any command getting this error :
Code:
target reported max download size of 266338304 bytes
sending 'revocery' (4096 KB)...
OKAY [ 0.142s]
writing 'revocery'...
FAILED (remote: Necessary to unlock FRP! Navigate to Settings > Develope
finished. total time: 0.154s
Since my phone not booting i cannot use this option Please help
Hi, back again
As i can see, try not to mess with the names :revocery...
When you want to flash the boot.img don't change that name.
Just flash it like : fastboot flash boot boot.img
Use my last boot.img which i sent you. That's a good one out of my backup.
For the FRP (perhaps edit your thread tiltle ) i have no answer in a minute. Did the "fastboot oem unlock" gave anything better ?
raystef66 said:
Hi, back again
As i can see, try not to mess with the names :revocery...
When you want to flash the boot.img don't change that name.
Just flash it like : fastboot flash boot boot.img
Use my last boot.img which i sent you. That's a good one out of my backup.
For the FRP (perhaps edit your thread tiltle ) i have no answer in a minute. Did the "fastboot oem unlock" gave anything better ?
Click to expand...
Click to collapse
I have try also boot , try everything, not matter if youhave FRP lock fastboot oem unlock is only to unlock bootloader, which i have, that is not a problem.
See if this method works for you
http://forum.xda-developers.com/showthread.php?t=3261846
Sent from my Nexus 6 using Tapatalk
joyrida12 said:
See if this method works for you
http://forum.xda-developers.com/showthread.php?t=3261846
Sent from my Nexus 6 using Tapatalk
Click to expand...
Click to collapse
You cannot use this method since i have only FastBoot feature, adb is not possible to use, since phone never boot. This method can be used only for phones what can boot correctly, so unfortunately useless for me. but thx for link
michalss said:
You cannot use this method since i have only FastBoot feature, adb is not possible to use, since phone never boot. This method can be used only for phones what can boot correctly, so unfortunately useless for me. but thx for link
Click to expand...
Click to collapse
i have exactly the same problem. FRP is locked but my phone doenst boot. so how can i unlock the frp with the fastboot mode?
stiggu said:
i have exactly the same problem. FRP is locked but my phone doenst boot. so how can i unlock the frp with the fastboot mode?
Click to expand...
Click to collapse
same problem on my mate s
good to know that adb is not working for others
i thaught it was just me
I've the same problem , any idea ??
michalss said:
Hi all,
I have a small problem, my phone does not boot and hanging on Logo. Now i can boot to fastboot menu, but i cannot really use it since i have FRP lock . Is there any chance to baypass it to make possible to flash recovery boot.img ?
When i try any command getting this error :
Code:
target reported max download size of 266338304 bytes
sending 'revocery' (4096 KB)...
OKAY [ 0.142s]
writing 'revocery'...
FAILED (remote: Necessary to unlock FRP! Navigate to Settings > Develope
finished. total time: 0.154s
Since my phone not booting i cannot use this option Please help
Click to expand...
Click to collapse
activate "Developer options"
playing several times "compilation"
go to options and enable developer
"Enable OEM unlock"
Hey , the problem is the device won't boot , so how can we enable developer option?!!!!
Sent from my iPhone using Tapatalk
There was a time when xda where the place to get the right answer and quick!
nowadays most topics are full of people with same problem and no dev to come to help, pity.
on topic: I have the same problem, ( mine is a Y6 pro) and before bricking it I had debugging and oem unlock enabled but now can't flash boot etc using fastboot ( error , denied ..) and can't use spflashtools either : preloader vcom appears for 1 second and then disappears and phone turns on.
tried many drivers, 3 Os'es (7, 8.1 ,10) still no luck.
porcha18 said:
activate "Developer options"
playing several times "compilation"
go to options and enable developer
"Enable OEM unlock"
Click to expand...
Click to collapse
Danke!!!!!!!!!!!!! Nach ewigem Suchen diese einfache Lösung. Vielen Dank!! Tag gerettet
the same issue
Good day, i have the same issue on my p9 EVA-L19.
FRP lock. And i can't do anything...
My warranty says that they cannot recover data from the phone, but the information is very important. I need to unlock FRP and somehow boot into TWRP or something to recover my data.
Please help someone if you had a same issue and results.
For the Huawei Y6 you can return to Stock.
Try to fastboot boot recovery-twrp.img and put your stock firmware (dload) folder to the rootdir at your sdcard.
Reboot your device to bootloader and hold down vol+ + vol- and use the command: fastboot boot stockrecovery.img (keep the keys pressed until the stock recovery comes up and starts installing your stock rom.
You will see an emui logo and the recovery will install the complete stock rom if you did everything right.
Retry to boot the stock recovery with this way if it is not working at the first try.
EDIT: after i wiped /system and and all the other stuff i was able to flash stock recovery via fastboot.
Runner85sx said:
For the Huawei Y6 you can return to Stock.
Try to fastboot boot recovery-twrp.img and put your stock firmware (dload) folder to the rootdir at your sdcard.
Reboot your device to bootloader and hold down vol+ + vol- and use the command: fastboot boot stockrecovery.img (keep the keys pressed until the stock recovery comes up and starts installing your stock rom.
You will see an emui logo and the recovery will install the complete stock rom if you did everything right.
Retry to boot the stock recovery with this way if it is not working at the first try.
EDIT: after i wiped /system and and all the other stuff i was able to flash stock recovery via fastboot.
Click to expand...
Click to collapse
Is there a way to do this on a mac?
Ive got adb enabled on terminal and I have a recovery.img file in my downloads though Im not sure if its the right one.
I typed in fastboot devices and then fastboot flash recovery recovery.img but it said cannot load recovery.img
anditan said:
Is there a way to do this on a mac?
Ive got adb enabled on terminal and I have a recovery.img file in my downloads though Im not sure if its the right one.
I typed in fastboot devices and then fastboot flash recovery recovery.img but it said cannot load recovery.img
Click to expand...
Click to collapse
your recovery location in adb is wrong probably. try changing it to the correct path. atleast thats what worked for me
man u can'T do anything because FRP is ACTIVATED !!!
No solution till now
Use the Huawei Swype bypass Method
michalss said:
Hi all,
I have a small problem, my phone does not boot and hanging on Logo. Now i can boot to fastboot menu, but i cannot really use it since i have FRP lock . Is there any chance to baypass it to make possible to flash recovery boot.img ?
When i try any command getting this error :
Code:
target reported max download size of 266338304 bytes
sending 'revocery' (4096 KB)...
OKAY [ 0.142s]
writing 'revocery'...
FAILED (remote: Necessary to unlock FRP! Navigate to Settings > Develope
finished. total time: 0.154s
Since my phone not booting i cannot use this option Please help
Click to expand...
Click to collapse
Try to do:
fastboot boot recovery.img
This will boot up the device with the given image. With that you can put a custom rom to your sd-card and flash it.
I will upload a Nandroid (stock system, recovery, boot) from my Y6 SCL-L01 soon.
With that you can restore boot and recovery with twrp. For this way you don't need to have a frp unlock.
Procedure:
fastboot boot recovery-twrp.img
Put your stock firmware (dload folder) to the sdcard.
Put my Nandroid to your sdcard.
Restore my Nandroid, reboot your device with Vol+ and Vol- pressed.
This way only works for SCL-L01 up to SCL-L04.
I need to create an extra recovery.img that includes a dt image that fits for all SCL variants.
Work in progress...
I have just removed frp today, but its not free method, unfortunately
Hi guys, my phone is Infocus M2 3G and I have rooted it earlier. Now I accidentally removed some services and now getting errors. I want to flash stock rom so it can be like previous one.
I installed ADB and fastboot in my system.
When I tried the command
Code:
fastboot flash recovery recovery.img
the following error came:
Code:
sending 'recovery' (10240 KB)...
OKAY [ 0.417s]
writing 'recovery'...
FAILED (remote:
Security deny - Err:0x2017
)
finished. total time: 0.430s
I searched and I got to know that this may be because of bootloader lock.
So I tried the command
Code:
fastboot oem unlock
and
Code:
fastboot flashing unlock
For oem unlock it showed unknown command and for flashing unlock it showed all options of fastboot.
I installed Rom Manager and select boot into recovery option, it took me to Android Recovery System 3e.
I have stock rom files downloaded and just want to put stock rom in my phone. Any Ideas that can help?
sumit77seo said:
Hi guys, my phone is Infocus M2 3G and I have rooted it earlier. Now I accidentally removed some services and now getting errors. I want to flash stock rom so it can be like previous one.
I installed ADB and fastboot in my system.
When I tried the command
the following error came:
I searched and I got to know that this may be because of bootloader lock.
So I tried the command and
For oem unlock it showed unknown command and for flashing unlock it showed all options of fastboot.
I installed Rom Manager and select boot into recovery option, it took me to Android Recovery System 3e.
I have stock rom files downloaded and just want to put stock rom in my phone. Any Ideas that can help?
Click to expand...
Click to collapse
You can try putting the stock ROM zip file on the root of your sdcard (As in not located in any sub folders) and renaming the ROM file to update.zip then use the stock recovery to flash the ROM. Let me know if you still have questions!
Hello guys...
So, without going too much into details of how I idiotically f-ed up pretty much everything... I just want to say that I've already lost about 12 hours reading through the forum trying to solve the problem and to understand how everything works, and by what I understood... I bricked the phone?
Firstly, I managed to unlock the bootloader with the HCU Client (Phone unlocked, FRP unlocked). At some points I've managed to boot into TWRP's, but I flashed them without understanding that I should have installed the recommended ones by the guys on this forum instead of the official one, with which I wiped System and Data partition.
I've tried hard but never managed to boot any of the Custom ROMs available, especially the LineageOS 16 which I wanted but later on, through a specific TWRP which gave an error information that it's meant for Hisilicon, and not for Kirin SoC...
I also had no idea when I was booting into recovery, and when into erecovery, because I flashed TWRP over both of them... I have really no idea what was the last thing to happen, but now it seems as if I can't boot into eRecovery anymore, and whatever I try flashing to the recovery_ramdisk over Fastboot, I just always get the same error when trying to boot into recovery
Error! Func NO : 11 (recovery image)
Error NO : 2 (load failed!)
Now I'm also having an issue because my battery has drained and it doesn't seem to turn on without it being connected to the charger or a PC.
Is there anything that I can do to make it work with any Custom ROM?
returnedinformation said:
I've managed to boot into TWRP's, but I flashed them without understanding that I should have installed the recommended ones by the guys on this forum instead of the official one, with which I wiped System and Data partition.
Click to expand...
Click to collapse
This is the result of some people posting nonsense here.
In fastboot mode run commands:
fastboot oem get-build-number
fastboot oem get-product-model
fastboot getvar vendorcountry
fastboot oem oeminforead-CUSTOM_VERSION
fastboot oem oeminforead-SYSTEM_VERSION
and post the results.
-Alf- said:
This is the result of some people posting nonsense here.
In fastboot mode run commands:
fastboot oem get-build-number
fastboot oem get-product-model
fastboot getvar vendorcountry
fastboot oem oeminforead-CUSTOM_VERSION
fastboot oem oeminforead-SYSTEM_VERSION
and post the results.
Click to expand...
Click to collapse
> fastboot oem get-build-number
(bootloader) :ANE-LX1 8.0.0.126(C432)
> fastboot oem get-product-model
(bootloader) ANE-LX1
> fastboot getvar vendorcountry
vendorcountry: hw/eu
> fastboot oem oeminforead-CUSTOM_VERSION
FAILED (remote: 'The reason of failed input oem_nv_item error!')
fastboot: error: Command failed
> fastboot oem oeminforead-SYSTEM_VERSION
(bootloader) :ANE-LX1 9.1.0.132(C432E5R1P7)
-Alf- said:
This is the result of some people posting nonsense here.
In fastboot mode run commands:
fastboot oem get-build-number
fastboot oem get-product-model
fastboot getvar vendorcountry
fastboot oem oeminforead-CUSTOM_VERSION
fastboot oem oeminforead-SYSTEM_VERSION
and post the results.
Click to expand...
Click to collapse
Click to expand...
Click to collapse
Alf is right:
Gather info about your phone with the fastboot commands -Alf- provided.
Using this info, find TWRP that 100% supports your phone. TWRP that is recommended in the "p20 lite basics" thread on XDA.
Start phone in fastboot mode. Use the fastboot boot twrp.img command to TEMPORARILY boot into TWRP (twrp.img must be in the same folder as fastboot.exe)
If TWRP hangs, reboot, try another TWRP
Once you are in TWRP, perform wipe and advanced wipe to clean up EVERY PARTITION (except sdcard) that you've messed up in the internal memory.
wipe data again to enable USB file transfer
Find a ROM for your phone. USE THE INFO FROM STEP 1 to figure out if the rom is REALLY for your model AND hardware revision of the phone. Pay attention to the device serial number and codename! ROMS developers use device codenames to indicate what model is compatible and what isnt. Huawei p20 lite has a total of 7(!!!) hardware revisions, and ROMS for each are different and likely NOT cross-compatible, which means if you install the wrong one, you will end up with a brick or a bootloop.
While TWRP is still on, Transfer ROM.zip to the phone.
In TWRP, use "Install" option to flash the ROM.
DO NOT FLASH TWRP PERMANENTLY! LET THE STOCK RECOVERY BE. FLASHING TWRP TO A/B (DUAL SLOT) DEVICES WILL 99% RESULT IN A BOOTLOOP. MOST MODERN DEVICES ARE A/B.
Flash Gapps if you need.
Reboot. Will take longer to start on the first boot.
Totesnochill said:
Alf is right:
Gather info about your phone with the fastboot commands -Alf- provided.
Using this info, find TWRP that 100% supports your phone.
Start phone in fastboot mode. Use the fastboot boot twrp.img command to TEMPORARILY boot into TWRP (twrp.img must be in the same folder as fastboot.exe)
If TWRP hangs, reboot, try another TWRP
Once you are in TWRP, perform wipe and advanced wipe to clean up EVERY PARTITION (except sdcard) that you've messed up in the internal memory.
wipe data again to enable USB file transfer
Find a ROM for your phone. USE THE INFO FROM STEP 1 to figure out if the rom is REALLY for your model AND hardware revision of the phone. Pay attention to the device serial number and codename! ROMS developers use device codenames to indicate what model is compatible and what isnt. Huawei p20 lite has a total of 7(!!!) hardware revisions, and ROMS for each are different and likely NOT cross-compatible, which means if you install the wrong one, you will end up with a brick or a bootloop.
While TWRP is still on, Transfer ROM.zip to the phone.
In TWRP, use "Install" option to flash the ROM.
DO NOT FLASH TWRP PERMANENTLY! LET THE STOCK RECOVERY BE. FLASHING TWRP TO A/B (DUAL SLOT) DEVICES WILL 99% RESULT IN A BOOTLOOP. MOST MODERN DEVICES ARE A/B.
Flash Gapps if you need.
Reboot. Will take longer to start on the first boot.
Click to expand...
Click to collapse
As I said before
-Alf- said:
some people posting nonsense here.
Click to expand...
Click to collapse
Totesnochill said:
Alf is right:
Gather info about your phone with the fastboot commands -Alf- provided.
Using this info, find TWRP that 100% supports your phone. TWRP that is recommended in the "p20 lite basics" thread on XDA.
Start phone in fastboot mode. Use the fastboot boot twrp.img command to TEMPORARILY boot into TWRP (twrp.img must be in the same folder as fastboot.exe)
If TWRP hangs, reboot, try another TWRP
Once you are in TWRP, perform wipe and advanced wipe to clean up EVERY PARTITION (except sdcard) that you've messed up in the internal memory.
wipe data again to enable USB file transfer
Find a ROM for your phone. USE THE INFO FROM STEP 1 to figure out if the rom is REALLY for your model AND hardware revision of the phone. Pay attention to the device serial number and codename! ROMS developers use device codenames to indicate what model is compatible and what isnt. Huawei p20 lite has a total of 7(!!!) hardware revisions, and ROMS for each are different and likely NOT cross-compatible, which means if you install the wrong one, you will end up with a brick or a bootloop.
While TWRP is still on, Transfer ROM.zip to the phone.
In TWRP, use "Install" option to flash the ROM.
DO NOT FLASH TWRP PERMANENTLY! LET THE STOCK RECOVERY BE. FLASHING TWRP TO A/B (DUAL SLOT) DEVICES WILL 99% RESULT IN A BOOTLOOP. MOST MODERN DEVICES ARE A/B.
Flash Gapps if you need.
Reboot. Will take longer to start on the first boot.
Click to expand...
Click to collapse
Sorry, but I'm already stuck at step 3:
PS C:\adb> fastboot boot twrp.img
Sending 'boot.img' (15652 KB) OKAY [ 0.411s]
Booting FAILED (remote: 'Command not allowed')
fastboot: error: Command failed
returnedinformation said:
Sorry, but I'm already stuck at step 3:
PS C:\adb> fastboot boot twrp.img
Sending 'boot.img' (15652 KB) OKAY [ 0.411s]
Booting FAILED (remote: 'Command not allowed')
fastboot: error: Command failed
Click to expand...
Click to collapse
I see. Some phones have this issue. where bootloader will not allow the "boot" command. Can be for a number of reasons:
1. Bootloader isnt "fully" unlocked, please check with the unlocking guide/service provider (if unlock was a paid service)
2. Bootloader is in "retail" mode, not a "service" mode. Some manufacturers do not intend for bootloader to be unlocked, and ship the devices with a restricted "retail" version that blocks certain commands.
also, why is your fastboot sending the "boot.img" while the command had " twrp img" as a payload?
I take it the bootloader still lets you use the "flash" command? If true, flash TWRP temporarily by "fastboot flash boot twrp.img", restart teh phone using the recovery menu keycombo
returnedinformation said:
> fastboot oem get-build-number
(bootloader) :ANE-LX1 8.0.0.126(C432)
> fastboot oem get-product-model
(bootloader) ANE-LX1
> fastboot getvar vendorcountry
vendorcountry: hw/eu
> fastboot oem oeminforead-CUSTOM_VERSION
FAILED (remote: 'The reason of failed input oem_nv_item error!')
fastboot: error: Command failed
> fastboot oem oeminforead-SYSTEM_VERSION
(bootloader) :ANE-LX1 9.1.0.132(C432E5R1P7)
Click to expand...
Click to collapse
you've mixed apples and oranges nicely .
Try this way out, using HuRupdater
Guide
Downloand TWRP
Here
Totesnochill said:
Some phones have this issue. where bootloader will not allow the "boot" command. Can be for a number of reasons
Click to expand...
Click to collapse
No, there is only one reason - on Huawei devices we do not have a "boot" partition since Android 7.
-Alf- said:
you've mixed apples and oranges nicely .
Try this way out, using HuRupdater
Guide
Downloand TWRP
Here
Click to expand...
Click to collapse
Thank you, I've put them in blender and set it to "lightspeed" mode
I'm sorry, but flashing that TWRP gives me the exact error I've been getting before when trying to boot into Recovery... the fact that the phone can't charge also gives some headache to actually even try to boot into the recovery. I just can't get into.
Edit: The furthest I can get to is that recovery error message.
hi there..was reading about your problem..i'm not sure if the same rules apply to all or most phones with regards to flashing twrp or using fastboot..i'm assuming that they do.
So, are you able to boot into fastboot and/or recovery?
if no to recovery, i guess it may be the wrong twrp, i hope you can at least boot into fastboot without any issues.
Personally i had a xiaomi poco f2 pro 6/128 and then i bought another same model phone but 8/256 from a fellow who almost bricked his phone..it was just blinking, when i restarted the phone, it went straight into blinking whenever i tried to boot into recovery, and it wouldnt boot into system anyway cos there was nothing there. so i figured it was stuck in recovery loop.
i was fortunate that i was able to hook up to it using my pc...then using command prompt, i was able to switch to fastboot mode..then i tried downloading and flashing different twrps, over 10 different twrps, and finally one worked..then it was smooth sailing from then on..and presto, that became my daily use phone.
returnedinformation said:
Thank you, I've put them in blender and set it to "lightspeed" mode
I'm sorry, but flashing that TWRP gives me the exact error I've been getting before when trying to boot into Recovery... the fact that the phone can't charge also gives some headache to actually even try to boot into the recovery. I just can't get into.
Edit: The furthest I can get to is that recovery error message.
Click to expand...
Click to collapse
Can you boot into eRecovery (into TWRP installee over eRecovery)? If so, try to flash eRecovery_ramdisk.img in TWRP,
download Here for EMUI 9.1
or Here for 8.0 (I'm not sure what is your current version).
In eRecovery mode you can charge the phone ( charging should also work in TWRP which is installed instead of eRecovery).
flashgordon65 said:
hi there..was reading about your problem..i'm not sure if the same rules apply to all or most phones with regards to flashing twrp or using fastboot..i'm assuming that they do.
So, are you able to boot into fastboot and/or recovery?
if no to recovery, i guess it may be the wrong twrp, i hope you can at least boot into fastboot without any issues.
Click to expand...
Click to collapse
-Alf- said:
Can you boot into eRecovery (into TWRP installee over eRecovery)? If so, try to flash eRecovery_ramdisk.img in TWRP,
download Here for EMUI 9.1
or Here for 8.0 (I'm not sure what is your current version).
In eRecovery mode you can charge the phone ( charging should also work in TWRP which is installed instead of eRecovery).
Click to expand...
Click to collapse
I can boot to the Fastboot, but unfortunately I can't boot to either recovery or erecovery... When trying to boot to the recovery by holding the power+volume up button until I see the "Your device has been unlocked" warning message + 2 seconds (which is when I see the recovery error message), or when trying to boot while plugged into USB also holding the power+volume up button just leaves me at "Your device is booting now...." forever
returnedinformation said:
I can boot to the Fastboot, but unfortunately I can't boot to either recovery or erecovery... When trying to boot to the recovery by holding the power+volume up button until I see the "Your device has been unlocked" warning message + 2 seconds (which is when I see the recovery error message), or when trying to boot while plugged into USB also holding the power+volume up button just leaves me at "Your device is booting now...." forever
Click to expand...
Click to collapse
doesn't look good bro, try the following :
in fastboot mode run commands
fastboot erase user data
fastboot reboot
-Alf- said:
doesn't look good bro, try the following :
in fastboot mode run commands
fastboot erase user data
fastboot reboot
Click to expand...
Click to collapse
PS C:\adb> fastboot erase user data
Erasing 'user' FAILED (remote: 'Command not allowed')
fastboot: error: Command failed
returnedinformation said:
PS C:\adb> fastboot erase user data
Erasing 'user' FAILED (remote: 'Command not allowed')
fastboot: error: Command failed
Click to expand...
Click to collapse
Sorry!
fastboot erase userdata
PS C:\adb> fastboot erase userdata
Erasing 'userdata' (bootloader) success to erase cryypt info in oeminfo
OKAY [ 0.215s]
Finished. Total time: 0.236s
PS C:\adb> fastboot reboot
Rebooting OKAY [ 0.024s]
Finished. Total time: 0.024s
Okay, what can I do now? I've tried flashing twrp right after that but solely rebooting get's me stuck at "Your device is booting now...", and trying to boot to recovery gives me the same error again
returnedinformation said:
PS C:\adb> fastboot erase userdata
Erasing 'userdata' (bootloader) success to erase cryypt info in oeminfo
OKAY [ 0.215s]
Finished. Total time: 0.236s
PS C:\adb> fastboot reboot
Rebooting OKAY [ 0.024s]
Finished. Total time: 0.024s
Okay, what can I do now? I've tried flashing twrp right after that but solely rebooting get's me stuck at "Your device is booting now...", and trying to boot to recovery gives me the same error again
Click to expand...
Click to collapse
Download stock Recovery Oreo
Link
Flash it in fastboot
fastboot flash recovery_ramdisk RECOVERY_RAMDISK-ANE-8.0.img
- fastboot reboot
Then try to boot into Recovery.
What exactly did you do after unlocking your phone? Did you upgrade back to A9? If so, then flash recovery_ramdisk A9
Download here
-Alf- said:
Download stock Recovery Oreo
Link
Flash it in fastboot
fastboot flash recovery_ramdisk RECOVERY_RAMDISK-ANE-8.0.img
- fastboot reboot
Then try to boot into Recovery.
What exactly did you do after unlocking your phone? Did you upgrade back to A9? If so, then flash recovery_ramdisk A9
Download here
Click to expand...
Click to collapse
I've tried both, they give me the same error.
After I flash the recovery I can't really reboot straight into recovery because of the issue with the battery... somehow I gotta hold the Volume UP key, while catching exact moment when I can unplug USB after the low battery status page passes, and before Huawei logo appears...
After unlocking the phone I flashed TWRP over either recovery or erecovery (idk anymore)... then I probably installed Pixel Experience 13 ROM (https://github.com/ponces/treble_build_pe/releases)
And after that... I tried too many things I can't even remember anymore.
returnedinformation said:
then I probably installed Pixel Experience 13 ROM
Click to expand...
Click to collapse
Under EMUI 8 ??? Which TWRP?