Related
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..
Hello xda people,
I tried to flash my TF201 with stock 4.1.1 ROM and 10.4.2.18 bootloader and I think I messed up the bootloader because now it can only go into USB mode - RCK, Wipe Data and Android all return "unrecoverable bootloader error" (0x0000000). And in USB mode, only fastboot commands work - ADB commands cannot be executed since it doesn't see the device.
I tried to follow a few troubleshooting guides posted here but hit a snag.
After running the following command:
Code:
fastboot -i 0x0b05 flash recovery twrp_tf201t.blob
I had this error message:
Code:
FAILED (command write failed (Unknown error))
finished. total time: 0.641s
so I went ahead and probably deleted more things that I should have.
Now I somehow managed to execute :
Code:
fastboot -i 0x0b05 flash recovery openrecovery-twrp-2.6.3.0-tf201-JB.blob
but after that the following command returns an error message:
sending 'recovery' (7934 KB)...
OKAY [ 1.373s]
writing 'recovery'...
FAILED (remote: (InvalidState))
finished. total time: 2.901s
Click to expand...
Click to collapse
Code:
fastboot -i 0x0b05 reboot-bootloader
so I had to reset the device with a paperclip in the reset hole on the side to be able to pick USB mode ( and fastboot)
I think I messed up big time and hope you can help me restore my Prime back to life.
Thank you!
Update:
After performing the following steps , I managed to revert it back to factory ROM:
1. Installed ADB Installer from : http://forum.xda-developers.com/showthread.php?t=2588979
2. Downloaded original ASUS blob from their website - make sure you pick the one for your SKU
3. Followed the steps posted in the Answer from this post: http://android.stackexchange.com/questions/28077/bricked-my-asus-tf300t-manual-jb-update
Hope this helps someone.
When I try to pick RCK from the bootloader options , I get the red exclamation mark with the laying android logo - that has been the case from the very beginning - even before having made any changes to the original stock 4.1.1. ROM.
I have a question: Since I have not unlocked the bootloader prior to upgrading to JB via OTA update, what are the next steps to put KitKat custom ROM to my tablet?
I just brought it back from the dead - I don't want to risk bricking my TF201.
Thanks!
Root Lenovo Vibe P1M
This guide will help you to root Lenovo Vibe P1M without bricking it.
Check this first.
Take backup of your important data at safe place.
Device must adequately charged.
Install USB drivers of your device PC.
Enable USB Debugging from Developer Options in Settings.
Enable Unknown Sources from Security in Settings.
Install TWRP
Follow the steps below.
Download ADB fastboot drivers [from here] and install it on PC.
Download TWRP recovery for Lenovo Vibe P1M from here.
Extract the zip file and find recovery.img file. Copy this file to your PC where you installed ADB fastboot drivers.
Now open Command Prompt.
Go to directory where you have installed ADB fastboot drivers.
Now enter the following commands.
Code:
adb reboot bootloader
fastboot oem unlock
fastboot flash recovery.img [B]OR[/B] fastboot boot recovery.img
fastboot reboot
After first command your device will reboot in fastboot mode. The second command will flash recovery image on your device. The third command will reboot your phone.
Now TWRP recovery is get installed on your Lenovo Vibe P1M.
Root Lenovo Vibe P1M
After installing TWRP on Lenovo Vibe P1M, follow the given steps to root it.
Download SuperSU from here.
Place the downloaded SuperSu zip in your extetnal SD card.
Now go to command prompt again and type the following command.
adb reboot recovery
Now your device will reboot in recovery mode. Flash supersu.zip from TWRP.
Reboot your device.
process completed.
Warning: I am not responsible if anything goes wrong, bricked device.
Does this method work with firmware ver S029. I am already rooted with kingoapp. But Flashfire app shows boot loader partitions to be protected . I suspect bootloader to be Locked. In such senario will this method work or will it brick my phone.
I also have another question if flash TWRP recovery on locked bootloader anyway, will it only fail to boot into recovery mode or will device fail to boot normally altogether
and it does boot normally then if i reflash stock recovery back on locked bootloader will that fix the issue of booting into recovery mode.
junkhunzai said:
Does this method work with firmware ver S029. I am already rooted with kingoapp. But Flashfire app shows boot loader partitions to be protected . I suspect bootloader to be Locked. In such senario will this method work or will it brick my phone.
I also have another question if flash TWRP recovery on locked bootloader anyway, will it only fail to boot into recovery mode or will device fail to boot normally altogether
and it does boot normally then if i reflash stock recovery back on locked bootloader will that fix the issue of booting into recovery mode.
Click to expand...
Click to collapse
This method will work ver S029 also. To flash recovery you need unlocked bootloader.
Well, I'm getting an error - (remote: not allowed), every time I try to boot the recovery.
ᵀᴴᴱ HUИTΞR said:
Well, I'm getting an error - (remote: not allowed), every time I try to boot the recovery.
Click to expand...
Click to collapse
Have you unlocked it?
1st command may be this
Fastboot oem unlock
Sent from my Redmi Note 3 using XDA-Developers mobile app
prajj said:
Have you unlocked it?
1st command may be this
Fastboot oem unlock
Click to expand...
Click to collapse
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot oem unlock
...
OKAY [ 7.103s]
finished. total time: 7.105s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot boot recovery.img
downloading 'boot.img'...
OKAY [ 1.075s]
booting...
FAILED (remote: unknown command)
finished. total time: 1.081s
C:\Program Files (x86)\Minimal ADB and Fastboot>
P.S: And now I have reboot loop... Reboot> Logo> Reboot > Logo...to infinity with a non-removable battry - just perfekt
P.S.: I can't get to recovery anymore...
ᵀᴴᴱ HUИTΞR said:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot oem unlock
...
OKAY [ 7.103s]
finished. total time: 7.105s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot boot recovery.img
downloading 'boot.img'...
OKAY [ 1.075s]
booting...
FAILED (remote: unknown command)
finished. total time: 1.081s
C:\Program Files (x86)\Minimal ADB and Fastboot>
P.S: And now I have reboot loop... Reboot> Logo> Reboot > Logo...to infinity with a non-removable battry - just perfekt
P.S.: I can't get to recovery anymore...
Click to expand...
Click to collapse
Have you extracted the zip file and copied recovery.img file from zip to your PC where you installed ADB fastboot drivers?? And use following command to flash recovery.img
Code:
fastboot flash recovery.img
Also take a look at this thread for reference --> http://forum.xda-developers.com/nexus-4/help/solved-fastboot-boot-recovery-img-t2380675
bravonova said:
Have you extracted the zip file and copied recovery.img file from zip to your PC where you installed ADB fastboot drivers?? And use following command to flash recovery.img
Code:
fastboot flash recovery.img
Also take a look at this thread for reference --> http://forum.xda-developers.com/nexus-4/help/solved-fastboot-boot-recovery-img-t2380675
Click to expand...
Click to collapse
Hi Bravo
fastboot flash recovery.img gives ->
unkown partition 'recovery.img'
error : cannot determine image filename for 'recovery.img'
and have the exact errors as Hunter but no loopboot until now
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot boot recovery.img
downloading 'boot.img'...
OKAY [ 1.075s]
booting...
FAILED (remote: unknown command)
finished. total time: 1.081s
finguers croosed
Edit :
some sites with roms are pointing to CPU MT6735M only , like needrom.com and techolite.com, mine is MT6735P, is there a difference ?
Nabil99 said:
Hi Bravo
fastboot flash recovery.img gives ->
unkown partition 'recovery.img'
error : cannot determine image filename for 'recovery.img'
and have the exact errors as Hunter but no loopboot until now
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot boot recovery.img
downloading 'boot.img'...
OKAY [ 1.075s]
booting...
FAILED (remote: unknown command)
finished. total time: 1.081s
finguers croosed
Edit :
some sites with roms are pointing to CPU MT6735M only , like needrom.com and techolite.com, mine is MT6735P, is there a difference ?
Click to expand...
Click to collapse
Hey bro use flashify app to flash recovery through phone...
Stock Recovery backup deleted.
Hi, my vibe p1m now is running twrp recovery, but i accidentally deleted my backup of stock recovery yeah i know im dumb, but if someone can provide a link.. please help me....
Can anyone share a boot.img plz.? I forgot to back up mine.. Thanks a ton!
mikkel19 said:
Hi, my vibe p1m now is running twrp recovery, but i accidentally deleted my backup of stock recovery yeah i know im dumb, but if someone can provide a link.. please help me....
Click to expand...
Click to collapse
http://firmwarefile.com/lenovo-vibe-p1m/
This link gives you stock firmware. I too have deleted my backup but used it to get it back. But however I faced problems like boot loop many times and even IMEI turned 000000000000000 for both sim slots but still it was recovered by using "MTK Engineering Mode" app which you can get from "Play Store" and follow the following steps.
Step 1) Open the the MTK Engineer mode app and swipe left side to go into Connectivity.
Step 2) In the Connectivity click on the CDS information.
Step 3) And then Tap on the Radio information.
Step 4) Then you will be able to see Phone 1 and Phone 2
Step 5) Just click on Phone 1 first. then enter the Command as AT +EGMR=1,7,"your first imei" (Put a Space between AT and +, Like AT +EGMR=1,10,"your imei") and then tap on SEND AT COMMAND it will show you that command sent,
Step 6) Now press back button and Tap on Phone 2 (if you have a Dual Sim phone) and Type AT +EGMR=1,10,"second imei" and tap on send at command.
Step 7) Now Just Restart you device and enjoy now Sim Card will Display the Network in the status bar.
And you are done!!!!!!!!!
You can see your IMEI by pressing *#06#
If you face boot loop problems again and again please inform me.
Just the problems I faced. They are the solutions. Please do reply to this message.
Okay thank you. I will try it. Thanks a lot
mikkel19 said:
Okay thank you. I will try it. Thanks a lot
Click to expand...
Click to collapse
Please do ask if you get any problems coz my device is same and I've tried with 3-4 different ROMs including stock so can help you with many problems.
---------- Post added at 04:42 PM ---------- Previous post was at 04:39 PM ----------
You can also root Lenovo Vibe P1m using SP Flash Tool. I've done the same and changed recovery from stock to TWRP easily without using any commands. Device works flawlessly and currently have installed MiUI 8 custom ROM.
mikkel19 said:
Okay thank you. I will try it. Thanks a lot
Click to expand...
Click to collapse
Oh and one more thing that zip file isn't for installing. You have to first extract it then you will get the instructions for flashing stock ROM. Happy flashing!!!!!
Sharath Guddad said:
Oh and one more thing that zip file isn't for installing. You have to first extract it then you will get the instructions for flashing stock ROM. Happy flashing!!!!!
Click to expand...
Click to collapse
Thank you, My vibe p1m is running on stock rom now, many thanks )))
Nabil99 said:
Hi Bravo
fastboot flash recovery.img gives ->
unkown partition 'recovery.img'
error : cannot determine image filename for 'recovery.img'
and have the exact errors as Hunter but no loopboot until now
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot boot recovery.img
downloading 'boot.img'...
OKAY [ 1.075s]
booting...
FAILED (remote: unknown command)
finished. total time: 1.081s
finguers croosed
Edit :
some sites with roms are pointing to CPU MT6735M only , like needrom.com and techolite.com, mine is MT6735P, is there a difference ?
Click to expand...
Click to collapse
Fastboot command given for flash recovery is wrong.
The right command is
Fastboot flash recovery recovery.img
Second recovery is the name of your recovery. If your recovery name is twrp then command is
Fastboot flash recovery twrp.img
Guys... If your device is new version (s036 pre installed) , use TWRP3 only.
Ashwinrg said:
Fastboot command given for flash recovery is wrong.
The right command is
Fastboot flash recovery recovery.img
Second recovery is the name of your recovery. If your recovery name is twrp then command is
Fastboot flash recovery twrp.img
Click to expand...
Click to collapse
C:\Fastboot>fastboot flash recovery recovery.img
target reported max download size of 134217728 bytes
sending 'recovery' (10642 KB)...
OKAY [ 1.063s]
writing 'recovery'...
FAILED (remote: download for partition 'recovery' is not allowed
)
finished. total time: 1.078s
cuci8202 said:
C:\Fastboot>fastboot flash recovery recovery.img
target reported max download size of 134217728 bytes
sending 'recovery' (10642 KB)...
OKAY [ 1.063s]
writing 'recovery'...
FAILED (remote: download for partition 'recovery' is not allowed
)
finished. total time: 1.078s
Click to expand...
Click to collapse
use TWRP3 only.. or install via sp flash tool.. it's very easy.. check this.. u can also get TWRP 3 here..
http://forum.xda-developers.com/android/general/how-to-install-twrp-root-lenovo-vibe-t3538088/page1
RN3P Kenzo, ROM is Global Dev 6.8.18.
I unlocked the bootloader officially (using the code and the MiFlashUnlock tool). I then used ADB to flash Cofface TWRP which did not work. These are the steps I used:
First I booted into fastboot.
Then I did this in Minimal ADB 'fastboot flash recovery twrp.img'.
The message was
sending 'recovery'
OKAY
writing 'recovery'
OKAY
finished.
Next I did 'fastboot reboot'.
Then I tried to get into TWRP recovery using the MIUI update app. Didn't work. Any help? Thanks in advance.
monsieurazizx said:
RN3P Kenzo, ROM is Global Dev 6.8.18.
I unlocked the bootloader officially (using the code and the MiFlashUnlock tool). I then used ADB to flash Cofface TWRP which did not work. These are the steps I used:
First I booted into fastboot.
Then I did this in Minimal ADB 'fastboot flash recovery twrp.img'.
The message was
sending 'recovery'
OKAY
writing 'recovery'
OKAY
finished.
Next I did 'fastboot reboot'.
Then I tried to get into TWRP recovery using the MIUI update app. Didn't work. Any help? Thanks in advance.
Click to expand...
Click to collapse
Try this, "fastboot boot twrp.img" NOT fastboot flash boot, just "fastboot boot twrp.img"
andersonaragao said:
Try this, "fastboot boot twrp.img" NOT fastboot flash boot, just "fastboot boot twrp.img"
Click to expand...
Click to collapse
OK. It boots into TWRP. But my question is, will I have to use "fastboot boot twrp.img" every time to boot into TWRP? That would be a hassle, but if that's the only way, I'll just deal with it.
Thanks though, it was nice to know the recovery image was working.
monsieurazizx said:
OK. It boots into TWRP. But my question is, will I have to use "fastboot boot twrp.img" every time to boot into TWRP? That would be a hassle, but if that's the only way, I'll just deal with it.
Thanks though, it was nice to know the recovery image was working.
Click to expand...
Click to collapse
No. You dont need to fastboot everytime. As you once booted into TWRP from "fastboot boot twrp.img" your recovery is perminantly TWRP. You can boot into by pressing the key combination or from the updater app..
Happy Flashing
Try fastboot reboot recovery but if not boot into recovery don't boot into system and reboot recovery via key combination. If you reboot system stock recovery erase twrp.
Note many devices will replace your custom recovery automatically during first boot. To prevent this, use Google to find the proper key combo to enter recovery. After typing fastboot reboot, hold the key combo and boot to TWRP. Once TWRP is booted, TWRP will patch the stock ROM to prevent the stock ROM from replacing TWRP. If you don't follow this step, you will have to repeat the install.
https://twrp.me/devices/xiaomiredminote3.html
"fastboot reboot" hold volume up until you see mi logo
Wipe:
/data
Then flash:
http://forum.xda-developers.com/redmi-note-3/how-to/modified-twrp-deleting-emmcappsboot-t3371667
@Up disables dm-verity and encryption on /data partition[that's why we wipe it inorder to format it].
By SharkcpN(Newbie Guide)
B) Prevent TWRP From Getting Over-written
After the TWRP gets flashed, disconnect the cable from the phone.
Hold power button + volume up buttons till phone gets restarted.
When the Mi Logo shows up, release the power button & keep holding the volume up button.
Release the Volume Up button after TWRP logo shows up.
If the language is in Chinese, select the right box, & select English.
Check the box & swipe to allow modifications.
it worked for me
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?