Related
I want to install cwm recovery in my canvas a1 for backup my current rom android 4.4.4.
I m going to install lollipop 5.1 I heard about some bug in lollipop so for my safety i want a backup.
I used minimal adb and fastboot for installing cwm.
But when i type the command "fastboot flash recovery recovery.img"
End hit enter
Then it show a error.
"Failed (remote download for partition 'recovery' is not allowed'
What should i do now?
http://forum.xda-developers.com/cro...oolbox-android-one-toolkit-one-click-t3030165
Go to this thread and follow the simple instructions...dnt go through such command prompts..when an easy way is available hit thanks if i helped
MaxySpark said:
I want to install cwm recovery in my canvas a1 for backup my current rom android 4.4.4.
I m going to install lollipop 5.1 I heard about some bug in lollipop so for my safety i want a backup.
I used minimal adb and fastboot for installing cwm.
But when i type the command "fastboot flash recovery recovery.img"
End hit enter
Then it show a error.
"Failed (remote download for partition 'recovery' is not allowed'
What should i do now?
Click to expand...
Click to collapse
Before flashing CWM recovery, you have to unlock the boot loader, using the command:
Code:
fastboot oem unlock
Then press Volume Up in phone to confirm.
Now you can flash.
Note: Unlocking bootloader formats the User data (/data partition), such as apps and other settings. Take a backup using Titanium Backup Tools, then proceed
Your recovery partition is locked.
1. Make yourself a developer (go to Settings -> About Phone -> Tap on Build until developer
2. In Developer options turn on Enable OEM unlock
3. Flash the new recovery, don forget to "fastboot oem unlock"
4. Important: don't allow phone to complete a normal reboot after flash. When rebooting, press Vol Up + Vol Down + Power to enter CWM recovery directly. Otherwise the stock recovery will replace CWM again.
When I type the command "fastboot oem unlock" and press enter, my phone displays a long-ish disclaimer text about the dangers of unlocking the bootloader, ending with the instruction to use Volume Up key to confirm ("YES, unlock...") or the Volume Down key to cancel ("NO, don't unlock..."). Pressing Volume Down works as expected: the line "returning to fastboot in 3secs" is displayed, followed by a return to fastboot. But pressing Volume UP seems to have NO EFFECT at all!! NOthing highlighted, no change in the screen, pressing power afterward does nothing. It is not a hardware problem of the Volume Up button either -- Volume Up/Down keys work in normal apps and in recovery mode just fine.
I was hoping that perhaps it just silently succeeded, but when i next try to flash the CWM recovery img, I still get 'sending recovery' OKAY but 'writing recovery' FAILED??
what do I do to get the volume UP to work while the phone in this mode??
BTW the phone is a Rook 4G phone from EE here in the UK. This is apparently the same as a ZTE Blade 3 A410 phone with carrier branding.
THANKS in advance for any help!
sbpetrack said:
When I type the command "fastboot oem unlock" and press enter, my phone displays a long-ish disclaimer text about the dangers of unlocking the bootloader, ending with the instruction to use Volume Up key to confirm ("YES, unlock...") or the Volume Down key to cancel ("NO, don't unlock..."). Pressing Volume Down works as expected: the line "returning to fastboot in 3secs" is displayed, followed by a return to fastboot. But pressing Volume UP seems to have NO EFFECT at all!! NOthing highlighted, no change in the screen, pressing power afterward does nothing. It is not a hardware problem of the Volume Up button either -- Volume Up/Down keys work in normal apps and in recovery mode just fine.
I was hoping that perhaps it just silently succeeded, but when i next try to flash the CWM recovery img, I still get 'sending recovery' OKAY but 'writing recovery' FAILED??
what do I do to get the volume UP to work while the phone in this mode??
BTW the phone is a Rook 4G phone from EE here in the UK. This is apparently the same as a ZTE Blade 3 A410 phone with carrier branding.
THANKS in advance for any help!
Click to expand...
Click to collapse
Hi, I have exactly the same situation!
No effect on Volume UP. I can't understand...
marc2800 said:
Hi, I have exactly the same situation!
No effect on Volume UP. I can't understand...
Click to expand...
Click to collapse
Absolutely identical experience here with the Alcatel One Touch Pop 3 - 5015x. I was following this tutorial http://forum.xda-developers.com/and...lcatel-one-touch-pop-s3-t3060092/post65430049, had a problem with the OEM, solved it by finding the top post on THIS thread and now I have the exact same issue as you two gentlemen. Any help would be appreciated, cus the phone seems bricked as it is. It's stuck in boot loop and receiving no input.
Thi is NOT the exact same issue as we have: you are stuck in a boot-loop; we have a version of fastboot which seems to have disabled the volumeUp button, thereby making it impossible to confirm our request to unlock the bootloader. e can only press VolumeDown (which cancels our request to unlock the bootloader).
i posted at http://forum.xda-developers.com/showpost.php?p=65462453&postcount=48 a suggestion for how to proceed in your case: just use SP Flash tools to reinstall a stock recovery image, and then use that recovery to install a complete stock ROM.
,BTW, Sir, when you say:
> ...with the Alcatel One Touch Pop 3 - 5015x. I ... had a problem with the OEM, solved it by finding the top post on THIS thread
note that the solution given in the top post of this thread is designed for Android One devices, and your Alcatel One Touch does NOT appear in the list of supported devices for that "fix." can't say it's entirely surprising that you would get into a bootloader problem if you apply top your phone a bootloader unlock solution for some random other platform!! LUck would not likely be with you when doing that.
zeta274 said:
Absolutely identical experience here with the Alcatel One Touch Pop 3 - 5015x. I was following this tutorial http://forum.xda-developers.com/and...lcatel-one-touch-pop-s3-t3060092/post65430049, had a problem with the OEM, solved it by finding the top post on THIS thread and now I have the exact same issue as you two gentlemen. Any help would be appreciated, cus the phone seems bricked as it is. It's stuck in boot loop and receiving no input.
Click to expand...
Click to collapse
I can't understand why volume down is working fine and not volume UP...
zeta274 said:
Absolutely identical experience here with the Alcatel One Touch Pop 3 - 5015x. I was following this tutorial http://forum.xda-developers.com/and...lcatel-one-touch-pop-s3-t3060092/post65430049, had a problem with the OEM, solved it by finding the top post on THIS thread and now I have the exact same issue as you two gentlemen. Any help would be appreciated, cus the phone seems bricked as it is. It's stuck in boot loop and receiving no input.
Click to expand...
Click to collapse
Go in bootloader mode, connect your phone to your computer and tell me what do you get if you tape in your console "fastboot devices"
I want to know the number before fastboot.. mine is strange and maybe not the original
MaxySpark said:
I want to install cwm recovery in my canvas a1 for backup my current rom android 4.4.4.
I m going to install lollipop 5.1 I heard about some bug in lollipop so for my safety i want a backup.
I used minimal adb and fastboot for installing cwm.
But when i type the command "fastboot flash recovery recovery.img"
End hit enter
Then it show a error.
"Failed (remote download for partition 'recovery' is not allowed'
What should i do now?
Click to expand...
Click to collapse
That is also my problem with my phone!
---------- Post added at 05:56 AM ---------- Previous post was at 05:54 AM ----------
GokulNC said:
Before flashing CWM recovery, you have to unlock the boot loader, using the command:
Code:
fastboot oem unlock
Then press Volume Up in phone to confirm.
Now you can flash.
Note: Unlocking bootloader formats the User data (/data partition), such as apps and other settings. Take a backup using Titanium Backup Tools, then proceed
Click to expand...
Click to collapse
Hi, I had done that fastboot oem unlock command and pressed Volume Up but nothing happened and my bootloader still locked could you help? Thanks, my phone is Starmobile UP HD MTK6582 :laugh:
GokulNC said:
Before flashing CWM recovery, you have to unlock the boot loader, using the command:
Code:
fastboot oem unlock
Then press Volume Up in phone to confirm.
Now you can flash.
Note: Unlocking bootloader formats the User data (/data partition), such as apps and other settings. Take a backup using Titanium Backup Tools, then proceed
Click to expand...
Click to collapse
really thanks:angel:
I can't
I have an error installing a ROM, partition x not allowed.
I can't go in recovery mode + I can't open my phone to enable usb debugging.
I don't have root & and I don't have my OEM unlocked.
How can I install my ROM for Asus Zenfone GO ZC500TG? :'( :'(
Anyone, please?!!
ADB devices allowed?
I have the same problem, but i just resolve it now. First, i've connected my phone in normal mode, then i opened cmd and wrote: adb devices, and a popup displayed in my phone to allow adb debug. I allowed and reboot to bootloader and follow all steps to unlock bootloader.
I also have problems, my phone is a polaroid turbo c4 plus and i cand get through the setup, so i can't install cwm and i am searching for methods to recover it, it's pretty hard since theres nothing online about it
Hi, I use a Asus Zenfone 2 ZOOAD
A few days ago I decided to flash the CM13 (Marshmallow) ROM on my phone. My phone is rooted. Anyway, when I tried to enter the recovery mode using the bootloader screen ( I selected "recovery mode" by using volume up and down) I couldn't do it. So, I decided to use the adb method. I'd already done it to put the Xposed Framework. So I connected my phone to my Windows 10 laptop and tried to enter recovery. Same story. It got stuck on the bootloader. I even tried flashing the custom twrp recovery; twrp is getting installed (or so it shows on the command window) but I can't enter the recovery mode. Worst part is I can't even boot into my normal screen. When I connect my phone to my laptop, it's detected but when I try to use adb it says "device not found". I am able to execute the fastboot commands though. But all in all, I can't get out of the bootloader.
When you are in bootloader you must choose recovery then agreed (ON OFF Button) then when it reboots : "VOLUME UP + ON/OFF" *click several time*
Here it is : http://forum.xda-developers.com/zenfone2/general/asus-zenfone-2-flashing-recovery-mode-t3096596
Hi guys,
I have a nexus 7 2013 which boot loop (or any watchdog restart ?).
If I try to normal start this one, I will get the Google logo for few seconds, then it will restart on its own.
If i press the volume down during this process, I can boot to bootloader, but same way, after few second, device will restart.
Any clue on what can be wrong ?
Thanks
Nico_FR said:
Hi guys,
I have a nexus 7 2013 which boot loop (or any watchdog restart ?).
If I try to normal start this one, I will get the Google logo for few seconds, then it will restart on its own.
If i press the volume down during this process, I can boot to bootloader, but same way, after few second, device will restart.
Click to expand...
Click to collapse
Hello, connect external power and try again. If it works now, you will have to replace the battery.
If it does not work with external power and it can not stop in bootloader/fastboot mode, then the hardware is faulty or the bootloader is corrupt.
External power does not change anything. Still boot loop, so really should be a hardware issue.
If I keep volume up key pressed, it boots, but almost unusable if I have to continuously press the volume up key.
Same when in bootloader: if I continuously press the volume up key, it does not reboot.
I've tried to erase everything with fastboot, but cannot do most of the operation. When trying to format data, it says that partition does not exists (it exists, as it can boot !)
Bootloader is locked, so cannot go with TWRP for example, as I cannot validate the on screen confirmation needed to oem unlock.
Do you know any way to unlock bootloader without use of onscreen confirmation ?
I don't know if that would help, but when I was installing Lineage OS and updated TWRP, I also boot looped once on recovery (recovery itself was boot-looping), and re-downloading (from another browser) and re-installing recovery at fastboot mode fixed my issue.
I cannot unlock the bootloader because of this issue, so cannot flash anything
Could be broken power button, if it is stuck and pressing it continuously.
Are you able to reach your recovery to factory reset?
I mean can you reach it from the bootloader menu?
If not you could try to put twrp.img or recovery.img into your PC adb&fastboot folder and try
fastboot boot twrp.img
or
fastboot boot recovery.img
Don't know if this works with locked bl
Edit: may type
fastboot getvar all
and post your result, hide your imei if you got one
For those that, like me, could not get driver recognition on the latest Win 10 x64 no matter what you tried. And ,yes, using every tutorial I could find on this and two "other Forums". Odin failed to see my device (still can't) Cydia impactor allows rebooting into fastboot and D/L but doesn't connect in either alt. mode. Yes, drivers all removed and replaced in varying states (usbdeview, etc.).
But ADB/Fastboot works!
Make sure you have your adb/fastboot drivers installed universally (Check this Fabulous Forum)
Download device-specific TWRP - I used this one for the 4gb version - https://www.dropbox.com/s/b7u3k1mgpppxlyx/recovery.img?dl=0
L.Shift-R. click in the folder you downloaded to (Open Command Window Here) - "adb devices" (to make sure device registers) then - "adb reboot bootloader" gets you into fastboot. - "fastoot boot {your-recovery-name}.img"
I got a fully functional TOUCH CAPABLE TWRP. Which I proceeded to load this - https://www.dropbox.com/s/j1owqv7mjkdpo75/UPDATE-SuperSU-v2.46.zip?dl=0 - and, VOILA! ROOT!!
I had similar issues with my laptop and drivers. Used a friend laptop in the end to "see" the phone and install twrp.
Sent from my S7 using Tapatalk
When I try to boot the recovery.img with fastboot it says that my OEM is locked. I check OEM unlock in developer options, then I do: adb reboot bootloader, then fastboot oem unlock. A warning appears saying to press VOLUME UP button to continue, voiding the warranty or VOLUME DOWN to go back. I try to press VOLUME UP and nothing happens... how did you do it?
vaskovass said:
When I try to boot the recovery.img with fastboot it says that my OEM is locked. I check OEM unlock in developer options, then I do: adb reboot bootloader, then fastboot oem unlock. A warning appears saying to press VOLUME UP button to continue, voiding the warranty or VOLUME DOWN to go back. I try to press VOLUME UP and nothing happens... how did you do it?
Click to expand...
Click to collapse
Hi there, I have the same issue. No success
I found a way, instead of volume up, use the home button this worked for me.. however after I unlocked the OEM and flashed TWRP the phone didn't want to boot anymore. It was stuck on Elephone logo with warning: "Orange State: The phone has been unlocked and can't be trusted. Your device will boot in 5s", however it didn't boot and stayed like that for almost an hour. Had to flash back the stock firmware to boot. Tried 1 more time the procedure to root but again the same. Maybe I do something wrong?
stock fw flash back
Hi, please can you help me with how you flashed back the stock firmware?
I get an error message with twrp : invalid zip file format.
Thank you in advance!
dnsgtr said:
Hi, please can you help me with how you flashed back the stock firmware?
I get an error message with twrp : invalid zip file format.
Thank you in advance!
Click to expand...
Click to collapse
I read somewhere the is a zip inside the update.zip & is that one that is flash able with twrp.
Have a look
During the main time I managed to flash the 0218 stock rom.
I still got the orange message but the phone finally boot. Then I just called the twrp recovery img via atb. I did nothing only touch the reboot in the twrp screen and since then "Orange status...." again.
May be the twrp recovery img is not the right one...
Bad command "fastoot boot {your-recovery-name}.img"
after OEM alow (informacion phone/compilacion number touch fast 9 times/access/alow oem)
fastboot oem unlock
"fastboot boot {your-recovery-name}.img" for me is fastboot boot recovery.img and all OK
bat still not working (phone not thrust unlocked bootloader cleaning data in 5..4..3..2..1.. and rebot)
Hi
I was trying to add a custom rom and root my honor 7x.
So i installed a twrp-like recovery (with success), and with that, i sucessfully installed a new ROM.
But now my home folder (/storage/emulated/0) is not writable and seems to be encrypted :/
I cannot do a factory reset or install a new ROM:
- when i go to fastboot mode, i have:
- PHONE Unlocket
- FRP Lock
So i cannot flash anything with fastboot, and my recovery is no more accessible (don't know why...)
My question is, how can i unlock the FRP ?
Thank you very much,
boehm_e
boehm_e said:
Hi
I was trying to add a custom rom and root my honor 7x.
So i installed a twrp-like recovery (with success), and with that, i sucessfully installed a new ROM.
But now my home folder (/storage/emulated/0) is not writable and seems to be encrypted :/
I cannot do a factory reset or install a new ROM:
- when i go to fastboot mode, i have:
- PHONE Unlocket
- FRP Lock
So i cannot flash anything with fastboot, and my recovery is no more accessible (don't know why...)
My question is, how can i unlock the FRP ?
Thank you very much,
boehm_e
Click to expand...
Click to collapse
Look in developer options, the "enable OEM unlock" switch is the "frp lock"
You might already know but I will say anyway just in case.
To boot recovery while phone is rebooting unplug USB and press volume up
To boot from adb use "adb reboot recovery"
From terminal app on phone "reboot recovery"
From powered off, make sure USB in unplugged hold volume up and power
mrmazak said:
Look in developer options, the "enable OEM unlock" switch is the "frp lock"
You might already know but I will say anyway just in case.
To boot recovery while phone is rebooting unplug USB and press volume up
To boot from adb use "adb reboot recovery"
From terminal app on phone "reboot recovery"
From powered off, make sure USB in unplugged hold volume up and power
Click to expand...
Click to collapse
Thank you for your reply.
Yes i know for the oem option in developper mode, but this option is grayed out (and enabled) but the frp is still locked :/
I also know about rebooting to recovery, but this is the default Honor recovery (nothing very usefull).
I tried the dload folder method (by putting an update.app into dload folder of my sdcard and then booting with + and - and power, but the update failes at 5%. It must be because of the frp lock).
Thank you
boehm_e said:
Thank you for your reply.
Yes i know for the oem option in developper mode, but this option is grayed out (and enabled) but the frp is still locked :/
I also know about rebooting to recovery, but this is the default Honor recovery (nothing very usefull).
I tried the dload folder method (by putting an update.app into dload folder of my sdcard and then booting with + and - and power, but the update failes at 5%. It must be because of the frp lock).
Thank you
Click to expand...
Click to collapse
I keep seeing this frp lock issue, comes uP after a reset in twrp or attempted exposed install, some other system change.
Are you on stock ROM and stock recovery?
If so can try to relock bootloader, that will make OEM toggle not greyed anymore. Then can make it off and back on.
Then unlock bootloader again
But only relock if on unchanged stock
I already tried to lock the bootloader again, with no success (probably bcs of the frp lock itself)
:/
Hi
I have same issue too.
How I can relock bootloader and then unlock it?