[Q] cant flash custom recoveries - Nexus 4 Q&A, Help & Troubleshooting

Hello I have recently bought a nexus 4 and updated to 4.3 via ota. I tried to flash custom roms but I am not able to open recoveries
I have successfully unlocked the bootloader but for some reason after flashing a custom recovery temporarily, it doesnt boot the recovery at all! its just a blank screen :/ help?

eeshlikhith said:
Hello I have recently bought a nexus 4 and updated to 4.3 via ota. I tried to flash custom roms but I am not able to open recoveries
I have successfully unlocked the bootloader but for some reason after flashing a custom recovery temporarily, it doesnt boot the recovery at all! its just a blank screen :/ help?
Click to expand...
Click to collapse
by "temporarily", do you mean you used the command "fastboot boot recovery.img" instead of "fastboot flash recovery recovery.img"?
Can you tell what are the output after you input the command?
If you wish to boot/flash the recovery via fastboot, the extension of the recovery file should be in .img instead of .zip. If you downloaded a zip file, you need to extract the recovery.img from the zip file.

eeshlikhith said:
Hello I have recently bought a nexus 4 and updated to 4.3 via ota. I tried to flash custom roms but I am not able to open recoveries
I have successfully unlocked the bootloader but for some reason after flashing a custom recovery temporarily, it doesnt boot the recovery at all! its just a blank screen :/ help?
Click to expand...
Click to collapse
With 4.3 the command for booting into custom recovery has changed.
With the help of hwti and el_charlie from this post you are able to boot into recovery.
Basically:
Code:
fastboot -c "lge.kcal=0|0|0|x" boot customrecovery.img
The command for flashing another recovery remained the same.

I just used the ncry tool kit in which when i clicked the recovery menu i could choose to temporarily boot into a custom recovery (wither TWRP OR CWM) But the thing is then it doesnt show up

Related

[Q] Cannot get it Rooted! Nexus 7

Hi folks,
after returned the 16gb version, i got my 32gb n7.
following the same step to root my 16gb one, i fail the root of my 32gb nexus7!
i donot why it kind of stuck in the step saying " booting the donowaled image' and just restart again. it should send me to the CWM [email protected]@
please HELP!!!!!!!!!!!!!!!!!!!! plase
fastboot OEM unlock, fastboot flash a custom recovery, flash the su binaries or a custom ROM, boot, and profit. that's all that is needed(without a toolkit). did you use a toolkit?
simms22 said:
fastboot OEM unlock, fastboot flash a custom recovery, flash the su binaries or a custom ROM, boot, and profit. that's all that is needed(without a toolkit). did you use a toolkit?
Click to expand...
Click to collapse
I succeeded to unlock the device............................ then when i flash the CWM into the device....i cannot get into the recovery mode. instead the device restart to the normal GOogle screen
seedzeng said:
I succeeded to unlock the device............................ then when i flash the CWM into the device....i cannot get into the recovery mode. instead the device restart to the normal GOogle screen
Click to expand...
Click to collapse
try twrp recovery. but cwm should work too. try booting recovery through fastboot..
fastboot boot recovery recoveryname.img
If you have installed the new boot loader latest official CWM will not work unless you flash an unofficial version (6.0.1.5 if I remember well).
Sent from my Nexus 7 using xda app-developers app

[Q] Can I root 4.3 without flashing customer recovery

I had rooted my Nexus 4 when on 4.2.x by putting it in bootloader mode first and typing fastboot boot <name of twrp custom recovery>.img at the command prompt to reboot it into TWRP custom recovery mode without if actually flashing the TWRP recovery on the device. Back then, this temporarily recovery mode allowed me to flash the supersu update zip file I needed to. Since 4.3, this command reboots the phone, but the screen is now blank, and I can't flash the zip file. I can reboot the phone normally into stock recovery mode using the volume keys and power button, but this does not allow me to flash the zip file to root it. Can I still use fastboot boot method like before, and how? The reason I want t stay on stock recovery for now is to keep future OTA updates from throwing an error message.
rajendra82 said:
I had rooted my Nexus 4 when on 4.2.x by putting it in bootloader mode first and typing fastboot boot <name of twrp custom recovery>.img at the command prompt to reboot it into TWRP custom recovery mode without if actually flashing the TWRP recovery on the device. Back then, this temporarily recovery mode allowed me to flash the supersu update zip file I needed to. Since 4.3, this command reboots the phone, but the screen is now blank, and I can't flash the zip file. I can reboot the phone normally into stock recovery mode using the volume keys and power button, but this does not allow me to flash the zip file to root it. Can I still use fastboot boot method like before, and how? The reason I want t stay on stock recovery for now is to keep future OTA updates from throwing an error message.
Click to expand...
Click to collapse
This is still possible but the command for booting into custom recovery changed.
This helps.
rajendra82 said:
I had rooted my Nexus 4 when on 4.2.x by putting it in bootloader mode first and typing fastboot boot <name of twrp custom recovery>.img at the command prompt to reboot it into TWRP custom recovery mode without if actually flashing the TWRP recovery on the device. Back then, this temporarily recovery mode allowed me to flash the supersu update zip file I needed to. Since 4.3, this command reboots the phone, but the screen is now blank, and I can't flash the zip file. I can reboot the phone normally into stock recovery mode using the volume keys and power button, but this does not allow me to flash the zip file to root it. Can I still use fastboot boot method like before, and how? The reason I want t stay on stock recovery for now is to keep future OTA updates from throwing an error message.
Click to expand...
Click to collapse
The short answer is no, you need a custom recovery to install superuser. The long answer is you can flash a custom recovery and install superuser and then flash back the stock recovery. If that doesn't work then your out of luck.
kzoodroid said:
The short answer is no, you need a custom recovery to install superuser. The long answer is you can flash a custom recovery and install superuser and then flash back the stock recovery. If that doesn't work then your out of luck.
Click to expand...
Click to collapse
You are absolutely wrong. I just booted into TWRP without flashing it and rooted my Nexus 4, which is otherwise stock 4.3. I still have the stock recovery on the device and can access it using the volume keys. Booting into TWRP was a temporary state achieved using the command line syntax:
fastboot -c "<your_default_command_line> lge.kcal=0|0|0|x" boot <name of custom recovery>.img
The 4.2.x version of this command was simpler, as it did not require the -c "<your_default_command_line> lge.kcal=0|0|0|x" part, but you do need it on 4.3, or the device just temporarily boots into a blank screen, instead of the custom recovery. So the long answer is you do need to boot into a custom recovery, but it does not have to be flashed to the boot partition. With a Nexus 4, you are never out of luck.
rajendra82 said:
You are absolutely wrong. I just booted into TWRP without flashing it and rooted my Nexus 4, which is otherwise stock 4.3. I still have the stock recovery on the device and can access it using the volume keys. Booting into TWRP was a temporary state achieved using the command line syntax:
fastboot -c "<your_default_command_line> lge.kcal=0|0|0|x" boot <name of custom recovery>.img
The 4.2.x version of this command was simpler, as it did not require the -c "<your_default_command_line> lge.kcal=0|0|0|x" part, but you do need it on 4.3, or the device just temporarily boots into a blank screen, instead of the custom recovery. So the long answer is you do need to boot into a custom recovery, but it does not have to be flashed to the boot partition. With a Nexus 4, you are never out of luck.
Click to expand...
Click to collapse
Can you please write a Step by Step guide to root without flashing custom recovery,
I am familiar with basic commands of adb and fastboot. But a step wise guide will hep me get my N4 rooted
ajay_zalavadia said:
Can you please write a Step by Step guide to root without flashing custom recovery,
I am familiar with basic commands of adb and fastboot. But a step wise guide will hep me get my N4 rooted
Click to expand...
Click to collapse
Follow @efrant's guide. Section E is enough assuming you are on stock android.
That will do the trick.
rajendra82 said:
I had rooted my Nexus 4 when on 4.2.x by putting it in bootloader mode first and typing fastboot boot <name of twrp custom recovery>.img at the command prompt to reboot it into TWRP custom recovery mode without if actually flashing the TWRP recovery on the device. Back then, this temporarily recovery mode allowed me to flash the supersu update zip file I needed to. Since 4.3, this command reboots the phone, but the screen is now blank, and I can't flash the zip file. I can reboot the phone normally into stock recovery mode using the volume keys and power button, but this does not allow me to flash the zip file to root it. Can I still use fastboot boot method like before, and how? The reason I want t stay on stock recovery for now is to keep future OTA updates from throwing an error message.
Click to expand...
Click to collapse
Sorry for asking about your reason, but if you install the TWRP (or some other) custom recovery then can't you simply manually flash the OTA yourself? That's how I upgraded to 4.3.
ajay_zalavadia said:
Can you please write a Step by Step guide to root without flashing custom recovery,
I am familiar with basic commands of adb and fastboot. But a step wise guide will hep me get my N4 rooted
Click to expand...
Click to collapse
Copy your custom recovery to where fastboot.exe is.
Open a CMD window and type
adb reboot-bootloader
Click to expand...
Click to collapse
Then, once you're booted into Bootloader, type
fastboot -c "lge.kcal=0|0|0|x" boot customrecoveryname.img
Click to expand...
Click to collapse
Flash SuperSU 1.51 zip and then reboot your device.
rajendra82 said:
You are absolutely wrong. I just booted into TWRP without flashing it and rooted my Nexus 4, which is otherwise stock 4.3. I still have the stock recovery on the device and can access it using the volume keys. Booting into TWRP was a temporary state achieved using the command line syntax:
fastboot -c "<your_default_command_line> lge.kcal=0|0|0|x" boot <name of custom recovery>.img
The 4.2.x version of this command was simpler, as it did not require the -c "<your_default_command_line> lge.kcal=0|0|0|x" part, but you do need it on 4.3, or the device just temporarily boots into a blank screen, instead of the custom recovery. So the long answer is you do need to boot into a custom recovery, but it does not have to be flashed to the boot partition. With a Nexus 4, you are never out of luck.
Click to expand...
Click to collapse
In your original post you said you tried using the boot into recovery method and it didn't work so how am I wrong in saying that your only other option was to flash the custom recovery, install su, then flash the stock recovery all without rebooting? It was just another way of accomplishing the same thing. I posted at the same time as the other guy did who knew the new fastboot command, which I was unaware of and obviously you were too.
Mercado_Negro said:
Copy your custom recovery to where fastboot.exe is.
Open a CMD window and type
Then, once you're booted into Bootloader, type
Flash SuperSU 1.51 zip and then reboot your device.
Click to expand...
Click to collapse
thank you, will try when I get chance :good:
kzoodroid said:
In your original post you said you tried using the boot into recovery method and it didn't work so how am I wrong in saying that your only other option was to flash the custom recovery, install su, then flash the stock recovery all without rebooting? It was just another way of accomplishing the same thing. I posted at the same time as the other guy did who knew the new fastboot command, which I was unaware of and obviously you were too.
Click to expand...
Click to collapse
I just prefer the command line booting instead of having to flash a recovery twice. I already knew that I could flash the custom recovery to get it done, although I didn't clearly state that in the original post.
Mercado_Negro said:
Copy your custom recovery to where fastboot.exe is.
Open a CMD window and type
Then, once you're booted into Bootloader, type
Flash SuperSU 1.51 zip and then reboot your device.
Click to expand...
Click to collapse
Thanks for you guide, but for use it, do I nerd unlocke the bootloader ?
Inviato dal mio Nexus 4 con Tapatalk 2
futuro82 said:
Thanks for you guide, but for use it, do I nerd unlocke the bootloader ?
Inviato dal mio Nexus 4 con Tapatalk 2
Click to expand...
Click to collapse
Yes
Thanks
Inviato dal mio Nexus 4 con Tapatalk 2
kzoodroid said:
In your original post you said you tried using the boot into recovery method and it didn't work so how am I wrong in saying that your only other option was to flash the custom recovery, install su, then flash the stock recovery all without rebooting? It was just another way of accomplishing the same thing. I posted at the same time as the other guy did who knew the new fastboot command, which I was unaware of and obviously you were too.
Click to expand...
Click to collapse
LOL.. You were still wrong though bro. Don't get upset about it. He didn't seem to be...
Sent from my Nexus 4 using xda app-developers app

XT905 - flashing recovery overwrites system

Hey guys,
I have an stock, unlocked and rooted xt905 lying here with stock recovery right now.
For several times now I tried to flash either cwm or twrp but had no luck.
Thats what I did:
- complete backup
- unlock bootloader
- restore backup
- fastboot flash boot twrp.img
- fastboot reboot
Flashing twrp doesnt throw up any error but as soon as I say reboot, the phone reboots into twrp instead of booting the system.
If I try to reboot to system within twrp, it reboots to twrp again. Booting to recovery from twrp brings me to stock recovery.
Its the same thing with cwm and I dont have any clue why, as other users are saying that twrp is working fine.
Till now I tried several different versions of fastboot, twrp and cwm and none of them worked.
Any ideas?
You're using the wrong fastboot command.
By typing "fastboot flash boot twrp.img" you are flashing TWRP in place of the boot.img. You need to type "fastboot flash recovery TWRP.img."
RikRong said:
You're using the wrong fastboot command.
By typing "fastboot flash boot twrp.img" you are flashing TWRP in place of the boot.img. You need to type "fastboot flash recovery TWRP.img."
Click to expand...
Click to collapse
OMG....
I am working on this phone since yesterday and couldnt figure it out....till now.
Embarrassing! I flashed about a dozen phones before and never had any problems whatsoever and now this.....
Thanks anyway! I am glad that I didnt brick the phone with flashing the wrong partition.

Lost recovery, cant boot, only fastboot

Guys... when i tried to flash oos 3.0 on my op2 through twrp, i first wiped the data to install new rom, then install oos 3.0, it failed. I then flashed the recovery i downloaded from the thread, then restart the recovery
I cant boot into the recovery.
System can't boot
Is it called "brick"?
So i tried to flash stock recovery in pc by command, but it says "remote: device is locked. cannot flash images". any solution to this problem?
I can boot into fastboot mode
You need to run the phone in Qualcomm mode on a PC and run the recovery tool to fix you bootloader.
I did the same and it was a royal ball ache trying to find out how to fix it
Don't do what rosswaa said
Why not?
What you should do is boot your phone into fastboot mode, connect it to your pc. Flash this modified TWRP recovery img to your phone https://www.androidfilehost.com/?fid=24459283995297945. After that you have to flash this modified SuperSU (through the new recovery) https://www.androidfilehost.com/?fid=24459283995297946.
The normal recovery doesn't work in OOS 3.0 (just like in HOS) and it's the SuperSU that gives you the soft brick. A dirty flash of the modified SuperSU should fix it.
I also had your problem and I did what rosswaa said which shouldn't be necessary (I lost all my data and backups).
I didn't lose anything, but I tried doing what you said and my bootloader was screwed so wouldn't take a flashed recovery or anything (yes the modified one)
Wish I hadnt been so excited and just flashed but all sorted now
Hmm okay, if it doesn't work with flashing the new recovery img then do what rosswaa said and after that follow this post https://forums.oneplus.net/threads/installation-instructions-faqs-oxygenos-3-0-0.439108/
Obviously try what green says first, if it works then happy days
first i am really glad that someone give some advices on me. But since i am a noob, how can i flash twrp in fastboot mode? using command? "fastboot flash recovery xxx.img"? thx
SPiCa39's said:
Guys... when i tried to flash oos 3.0 on my op2 through twrp, i first wiped the data to install new rom, then install oos 3.0, it failed. I then flashed the recovery i downloaded from the thread, then restart the recovery
I cant boot into the recovery.
System can't boot
Is it called "brick"?
So i tried to flash stock recovery in pc by command, but it says "remote: device is locked. cannot flash images". any solution to this problem?
I can boot into fastboot mode
Click to expand...
Click to collapse
1 Install official TWRP 3.x via fastboot twrp.me/devices/oneplustwo.html
Reboot to recovery
2 install this modified version of TWRP
forum.xda-developers.com/oneplus-2/development/recovery-teamwin-recovery-project-3-0-0-t3310713
Reboot to recovery
3 install oos3 (And supersu)
Sorry i can't post link

Unable to flash TWRP on Moto e3 power with latest software update

I'm trying to flash TWRP (twrp-3.2.1-0-taido.img) on my Moto E3 Power. I had successfully rooted this phone once, and that's why the phone is unlocked. So when I try to flash custom recovery using the command "sudo fastboot flash recovery twrp-3.2.1-0-taido.img", it says it completed successfully, but instead of booting into twrp, my phone is starting up completely. When I tried booting up custom recovery using "sudo fastboot boot twrp-3.2.1-0-taido.img", the same thing happened again.
The software on my phone is "23.0.XT1706_S151_180706_ROW". So far I've been unable to flash twrp on this phone, but I got it to work an year ago. Please, can anyone help me what's going wrong here? I'm following the tips on xda-forums using which other users were able to flash the same recovery on their phones.
you can try this
ajyotirmay said:
I'm trying to flash TWRP (twrp-3.2.1-0-taido.img) on my Moto E3 Power. I had successfully rooted this phone once, and that's why the phone is unlocked. So when I try to flash custom recovery using the command "sudo fastboot flash recovery twrp-3.2.1-0-taido.img", it says it completed successfully, but instead of booting into twrp, my phone is starting up completely. When I tried booting up custom recovery using "sudo fastboot boot twrp-3.2.1-0-taido.img", the same thing happened again.
The software on my phone is "23.0.XT1706_S151_180706_ROW". So far I've been unable to flash twrp on this phone, but I got it to work an year ago. Please, can anyone help me what's going wrong here? I'm following the tips on xda-forums using which other users were able to flash the same recovery on their phones.
Click to expand...
Click to collapse
Get into the fastboot mode try again unlock your oem
'fastboot oem unlock'(volume up on your phone and select yes ) --->'fastboot format userdata' now flash the twrp recovery the link is below try this it may work worked fine for me and dont know really why the updated twrp is not flashing
My Google Drive link for TWRP recovery:-https://drive.google.com/file/d/0BylQ6RZ2mIP_cElxMzFoRVEyRDg/view?usp=sharing

Categories

Resources