Related
Hello!
I have a HTC One X (EU-version), and it's unlocked.
I used to have Android Revolution HD ROM installed, and would try a new kernel. So I downloaded the new faux kernel (faux_004b5_arhd_7.0.0_modified.img)
Somehow it didn't work, and my phone keep restarting. So I go to the recovery mode, and tried to reinstall the ROM, without whip.
After that I made a reboot, my phone keep reboot. Now I can't go to the recovery mode, either can I flash my device.
I really don't know what to do now.
I hope someone can help, and I posted in the right section.
DownClock said:
Hello!
I have a HTC One X (EU-version), and it's unlocked.
I used to have Android Revolution HD ROM installed, and would try a new kernel. So I downloaded the new faux kernel (faux_004b5_arhd_7.0.0_modified.img)
Somehow it didn't work, and my phone keep restarting. So I go to the recovery mode, and tried to reinstall the ROM, without whip.
After that I made a reboot, my phone keep reboot. Now I can't go to the recovery mode, either can I flash my device.
I really don't know what to do now.
I hope someone can help, and I posted in the right section.
Click to expand...
Click to collapse
I had that problem before too. If the "hold power button for 10 seconds then press volume down and power buttons simultaneously" doesn't work, download Quick Boot from playstore and it would allow you to choose to either Reboot, boot to recovery, or the bootloader
Sent from my HTC One X using xda premium
trick is to run 'adb reboot bootloader' or 'adb reboot recovery'.
wtfshouldidonow said:
I had that problem before too. If the "hold power button for 10 seconds then press volume down and power buttons simultaneously" doesn't work, download Quick Boot from playstore and it would allow you to choose to either Reboot, boot to recovery, or the bootloader
Sent from my HTC One X using xda premium
Click to expand...
Click to collapse
When I hold the power button and volume down for 10 secounds, I come to the fastboot menu.
How can I download Quick Boot, when I don't have acces to my memory. I can't see what I have on my memorycard (obs. because I can't go to the recovery part), either can't connect to the computer, since I'm in a bootloop.
I'm afraid while I was doing this stuff, my battery was low. But it didn't die under the process.
Tyvm for the reply, but I can't install the quick boot.
seadersn said:
trick is to run 'adb reboot bootloader' or 'adb reboot recovery'.
Click to expand...
Click to collapse
Can you please explain more?
My Skype is: Dichatz, if a awesome soul could help me there, it would be the greatest thing ever. I'm afraid of that my HTC One X has seen the daylight for the last time
Ty both for the reply.
EDIT: I followed my friends advise, and tried to erase fastboot cache, which seems not able do to. I just getting the message: < waiting for device >.
Dear God, what have I done with my phone!
Dear OP, I believe there is a solution. This situation has occurred with my device more than once. I too believed I had lost it until it resolved itself. There are several things you can do to ensure it works again. I wiped the ROM on my phone before the problem began, so I was stuck with a dead phone until I found a way to get recovery to work again. If it's possible, enter Fastboot and install a new kernel onto it, and THEN use fastboot erase cache. If that is not a viable option, make sure the USB wire is not plugged in when the device boots. By this I mean holding down the lower volume button and initializing the menu that allows you to select Fastboot, Recovery, Factory Reset and other command options. Once the device boots into the menu, you may then plug in the cable and enter Fastboot mode. If none of the above work, let the battery deplete itself until device turns off. Once you have done that, plug it into the wall charger, and then volume down and power up. If the device says something like "reading SD card", disconnect the USB and the menu will fully load. That is when you select Fastboot. Keep the device on, plug it into the pc and send your kernel commands to your device. Ensure that you also erase the cache via Fastboot. Your device should now be fully operational. I hope I was able to help.
Have found myself in a similar position, all the following assumes you're using windows as you desktop OS...
To double check your recovery is broken, get into fastboot mode (power on while holding volume down), use volume down to highlight "hboot" then press the power button to select. Then press volume down to highlight "recovery" and press power button to select. If that works, then recovery is fine, just go ahead as you normally would to recover the system.
If you can't get into recovery then you have a slight problem.
Since you can get the device into fastboot mode, the priority is to get it to talk to your PC. Get the device into fastboot (power on while holding the volume down button). Once you're into fastboot, plug in the USB cable and verify the connection to your device using the following command :
Code:
fastboot devices
This should show you a single entry for your device. If it doesn't show anything, then unplug the device, download the naked driver pack (available at http://forum.xda-developers.com/showthread.php?t=1161769) and unpack it into a sensible location. Plug the device back in, if it can't install software automatically or nothing appears you may have to use device manager to update the driver for the device. Find its entry in the device tree (it will probably be listed as an unknown device), RMB on its entry in device tree then select "Update Driver Software..." from the menu that appears, tell it to search automatically then point it at the location where you unpacked the naked driver pack. That should sort out any misconceptions windows has about not being able to talk to the phone.
Once you have fastboot access, you can reflash clockworkmod. You can obtain the latest version here : http://forum.xda-developers.com/showthread.php?t=1594819
flash from fastboot using the command
Code:
fastboot flash recovery recovery-clockwork-touch-5.8.4.0-endeavoru.img
Once flashed, unplug the usb cable.
Use the volume up and down to highlight "hboot" on the fastboot menu, then press the power button to select. Once in the hboot menu, scroll to the "recovery" menu item and press power again to select. You should find yourself in familiar territory at this point.
hth
EDIT : Sorry, it's nearly 2am here, I'm very tired and I've just re-read your initial post. If you've flashed a custom kernel then you MUST have fastboot access (or it's subsequently broken). Download your ROM (if you haven't already got a copy on your PC) and extract boot.img from it. Get into fastboot mode (vol down + power on) and plug into your PC. Do the following :
Code:
fastboot flash boot boot.img
fastboot erase cache
Unplug USB cable, use vol up/ down to highlight "REBOOT" then press power to select.If you get stuck in a bootloop, you can try going into recovery via fastboot (select "hboot" from the fastboot menu then "recovery" from the hboot menu), then select "erase cache", then go to "advanced" and "wipe dalvik cache". Then go back and reboot the device. See if that helps. If not, then go back to recovery using the aforementioned method and re-install your rom, then erase cache and wipe dalvik cache.
Thanks for replies.
Elemental_Fire said:
Dear OP, I believe there is a solution. This situation has occurred with my device more than once. I too believed I had lost it until it resolved itself. There are several things you can do to ensure it works again. I wiped the ROM on my phone before the problem began, so I was stuck with a dead phone until I found a way to get recovery to work again. If it's possible, enter Fastboot and install a new kernel onto it, and THEN use fastboot erase cache. If that is not a viable option, make sure the USB wire is not plugged in when the device boots. By this I mean holding down the lower volume button and initializing the menu that allows you to select Fastboot, Recovery, Factory Reset and other command options. Once the device boots into the menu, you may then plug in the cable and enter Fastboot mode. If none of the above work, let the battery deplete itself until device turns off. Once you have done that, plug it into the wall charger, and then volume down and power up. If the device says something like "reading SD card", disconnect the USB and the menu will fully load. That is when you select Fastboot. Keep the device on, plug it into the pc and send your kernel commands to your device. Ensure that you also erase the cache via Fastboot. Your device should now be fully operational. I hope I was able to help.
Click to expand...
Click to collapse
Yes, I was dumb, started at low battery level, even tho, everywhere says: Make sure you have more than 70 %.
I can't wipe, or install anything, since it's recovery mode that doesn't work
Atm., I charge my phone, because I need to have 10 %, I use "Stuck in fastboot with low battery. Use this BATCH file!" guide. So far it works.
amacrobie said:
Have found myself in a similar position, all the following assumes you're using windows as you desktop OS...
To double check your recovery is broken, get into fastboot mode (power on while holding volume down), use volume down to highlight "hboot" then press the power button to select. Then press volume down to highlight "recovery" and press power button to select. If that works, then recovery is fine, just go ahead as you normally would to recover the system.
If you can't get into recovery then you have a slight problem.
Since you can get the device into fastboot mode, the priority is to get it to talk to your PC. Get the device into fastboot (power on while holding the volume down button). Once you're into fastboot, plug in the USB cable and verify the connection to your device using the following command :
Code:
fastboot devices
This should show you a single entry for your device. If it doesn't show anything, then unplug the device, download the naked driver pack (available at http://forum.xda-developers.com/showthread.php?t=1161769) and unpack it into a sensible location. Plug the device back in, if it can't install software automatically or nothing appears you may have to use device manager to update the driver for the device. Find its entry in the device tree (it will probably be listed as an unknown device), RMB on its entry in device tree then select "Update Driver Software..." from the menu that appears, tell it to search automatically then point it at the location where you unpacked the naked driver pack. That should sort out any misconceptions windows has about not being able to talk to the phone.
Once you have fastboot access, you can reflash clockworkmod. You can obtain the latest version here : http://forum.xda-developers.com/showthread.php?t=1594819
flash from fastboot using the command
Code:
fastboot flash recovery recovery-clockwork-touch-5.8.4.0-endeavoru.img
Once flashed, unplug the usb cable.
Use the volume up and down to highlight "hboot" on the fastboot menu, then press the power button to select. Once in the hboot menu, scroll to the "recovery" menu item and press power again to select. You should find yourself in familiar territory at this point.
hth
EDIT : Sorry, it's nearly 2am here, I'm very tired and I've just re-read your initial post. If you've flashed a custom kernel then you MUST have fastboot access (or it's subsequently broken). Download your ROM (if you haven't already got a copy on your PC) and extract boot.img from it. Get into fastboot mode (vol down + power on) and plug into your PC. Do the following :
Code:
fastboot flash boot boot.img
fastboot erase cache
Unplug USB cable, use vol up/ down to highlight "REBOOT" then press power to select.If you get stuck in a bootloop, you can try going into recovery via fastboot (select "hboot" from the fastboot menu then "recovery" from the hboot menu), then select "erase cache", then go to "advanced" and "wipe dalvik cache". Then go back and reboot the device. See if that helps. If not, then go back to recovery using the aforementioned method and re-install your rom, then erase cache and wipe dalvik cache.
Click to expand...
Click to collapse
Thank you very much for your answer!!! I read this this guide: 9/6 Mandatory Update Official Clockworkmod Touch Recovery 5.8.4.0.
If that doesn't work, I will take closer look at your reply. No matter what, thank you very very very very much. I'm sure that reply will help some soul outthere (if not me, if it fail).
Thank you guys. You are the best. I will be right back here if I find a solution!
Tip: try 'Quick Boot' available on Google Playstore, it's a payed app but
it let you go straight into recovery mode.
Hi
Laurentius26 said:
Tip: try 'Quick Boot' available on Google Playstore, it's a payed app but
it let you go straight into recovery mode.
Click to expand...
Click to collapse
I could't turn my device on, so I could't install any programs.
Anyway, after 6 hours work, I finally got it.
I use that guide ^, so I could charge my phone to 10%, and installed new Kernel.
Thank you guys, for quick replies!
My apologies, I wasn't reading your first post properly.
Anyway congrats you have it working again.
DownClock said:
I could't turn my device on, so I could't install any programs.
Anyway, after 6 hours work, I finally got it.
I use that guide ^, so I could charge my phone to 10%, and installed new Kernel.
Thank you guys, for quick replies!
Click to expand...
Click to collapse
Can't flash cwm recovery.
amacrobie said:
Have found myself in a similar position, all the following assumes you're using windows as you desktop OS...
To double check your recovery is broken, get into fastboot mode (power on while holding volume down), use volume down to highlight "hboot" then press the power button to select. Then press volume down to highlight "recovery" and press power button to select. If that works, then recovery is fine, just go ahead as you normally would to recover the system.
If you can't get into recovery then you have a slight problem.
Since you can get the device into fastboot mode, the priority is to get it to talk to your PC. Get the device into fastboot (power on while holding the volume down button). Once you're into fastboot, plug in the USB cable and verify the connection to your device using the following command :
Code:
fastboot devices
This should show you a single entry for your device. If it doesn't show anything, then unplug the device, download the naked driver pack (available at http://forum.xda-developers.com/showthread.php?t=1161769) and unpack it into a sensible location. Plug the device back in, if it can't install software automatically or nothing appears you may have to use device manager to update the driver for the device. Find its entry in the device tree (it will probably be listed as an unknown device), RMB on its entry in device tree then select "Update Driver Software..." from the menu that appears, tell it to search automatically then point it at the location where you unpacked the naked driver pack. That should sort out any misconceptions windows has about not being able to talk to the phone.
Once you have fastboot access, you can reflash clockworkmod. You can obtain the latest version here : http://forum.xda-developers.com/showthread.php?t=1594819
flash from fastboot using the command
Code:
fastboot flash recovery recovery-clockwork-touch-5.8.4.0-endeavoru.img
Once flashed, unplug the usb cable.
Use the volume up and down to highlight "hboot" on the fastboot menu, then press the power button to select. Once in the hboot menu, scroll to the "recovery" menu item and press power again to select. You should find yourself in familiar territory at this point.
hth
EDIT : Sorry, it's nearly 2am here, I'm very tired and I've just re-read your initial post. If you've flashed a custom kernel then you MUST have fastboot access (or it's subsequently broken). Download your ROM (if you haven't already got a copy on your PC) and extract boot.img from it. Get into fastboot mode (vol down + power on) and plug into your PC. Do the following :
Code:
fastboot flash boot boot.img
fastboot erase cache
Unplug USB cable, use vol up/ down to highlight "REBOOT" then press power to select.If you get stuck in a bootloop, you can try going into recovery via fastboot (select "hboot" from the fastboot menu then "recovery" from the hboot menu), then select "erase cache", then go to "advanced" and "wipe dalvik cache". Then go back and reboot the device. See if that helps. If not, then go back to recovery using the aforementioned method and re-install your rom, then erase cache and wipe dalvik cache.
Click to expand...
Click to collapse
Hey, I am having similar problem with my htc one x here. I did some stupid stuff, tried to install jelly bean and now my device is broken.,
So the thing is, phone is stuck at HTC logo, I cant access recovery mode. And my phone now says tempered and relocked at the top so I cant get it fixed with my carrier which is rogers.
I tried installing RUU for rogers but it says image error and wrong ruu. I can't find the right one and trust me i've searched everywhere.
I can connect my phone to computer and see fastboot usb. But other than that I can't do anything with it.
I tried flashing cwm but it says failed. I'll attach image here with it.
If there is any way to fix it, please help, I just bought this device and I love it, dont wanna lose it.
Also, I read that I can add custom recovery to the phone but without recovery menu I can't do that either.
Thanks!
saagar_mistry said:
Hey, I am having similar problem with my htc one x here. I did some stupid stuff, tried to install jelly bean and now my device is broken.,
So the thing is, phone is stuck at HTC logo, I cant access recovery mode. And my phone now says tempered and relocked at the top so I cant get it fixed with my carrier which is rogers.
I tried installing RUU for rogers but it says image error and wrong ruu. I can't find the right one and trust me i've searched everywhere.
I can connect my phone to computer and see fastboot usb. But other than that I can't do anything with it.
I tried flashing cwm but it says failed. I'll attach image here with it.
If there is any way to fix it, please help, I just bought this device and I love it, dont wanna lose it.
Also, I read that I can add custom recovery to the phone but without recovery menu I can't do that either.
Thanks!
Click to expand...
Click to collapse
How much battery you think you had on your device, and how much do you think you have now?
Sendt fra min HTC One X med Tapatalk2
Htc One x
DownClock said:
How much battery you think you had on your device, and how much do you think you have now?
Sendt fra min HTC One X med Tapatalk2
Click to expand...
Click to collapse
I have been charging my device with the wall charger, eventhough I cant see the battery level I'm pretty sure it's around 80. Cuz before I go into fastboot usb when I attach my phone to computer I charge the phone first.
saagar_mistry said:
I have been charging my device with the wall charger, eventhough I cant see the battery level I'm pretty sure it's around 80. Cuz before I go into fastboot usb when I attach my phone to computer I charge the phone first.
Click to expand...
Click to collapse
To be honest I don't know what to do. Try to make a new topic, and hope for help
Good luck.
Sendt fra min HTC One X med Tapatalk2
Htc One x Cant flash into recovery thus unable to root
I followed every single step correctly in xda's official htc one x root guide and unlocked the bootloader but in the last step where the cwm has to be flashed and booted into recovery i am unable to boot into recovery even after clearing fastboot cache and trying every possible cwm available.
my bootloader is unlocked and i am desperate to root my htc
the details are as follows
evita pvt ship s-on rl
hboot - 1.11.0000
its cid is rogers 001
please help
GridBreak said:
I followed every single step correctly in xda's official htc one x root guide and unlocked the bootloader but in the last step where the cwm has to be flashed and booted into recovery i am unable to boot into recovery even after clearing fastboot cache and trying every possible cwm available.
my bootloader is unlocked and i am desperate to root my htc
the details are as follows
evita pvt ship s-on rl
hboot - 1.11.0000
its cid is rogers 001
please help
Click to expand...
Click to collapse
man are you sure you have international Htc One X?
I think you may have AT&T One X.
GridBreak said:
I followed every single step correctly in xda's official htc one x root guide and unlocked the bootloader but in the last step where the cwm has to be flashed and booted into recovery i am unable to boot into recovery even after clearing fastboot cache and trying every possible cwm available.
my bootloader is unlocked and i am desperate to root my htc
the details are as follows
evita pvt ship s-on rl
hboot - 1.11.0000
its cid is rogers 001
please help
Click to expand...
Click to collapse
Here is the right forum for your device http://forum.xda-developers.com/forumdisplay.php?f=1538
Cannot boot
i also accidentally flashed an img into boot and now my phone is not booting and is stuck ina bootloop please help !!!!!!!!!
GridBreak said:
i also accidentally flashed an img into boot and now my phone is not booting and is stuck ina bootloop please help !!!!!!!!!
Click to expand...
Click to collapse
you should ask for help in the respective forum for your phone.
This is for Tegra 3 HTC ONE X
seadersn said:
trick is to run 'adb reboot bootloader' or 'adb reboot recovery'.
Click to expand...
Click to collapse
i didnt know about adb reboot recovery, just found this via google, cheers mate!
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
I can't boot up my device it's have blink sleeping android error. (my device is ze551ml running WW_2.19.40.22 firmware and never ever ROOT!!! )
I tried hold power button and press volume up button but its doesn't work.
I also can't access to recovery mode too.
It's have the same blink error message and can't pass by hold power button and press volume up button.
Oh but i can access to fastboot page.
and my computer don't recognize my phone at all(i already install driver)
Before this problem happen I get in to recovery mode try to wipe cache but i miss press and i selected "apply update from adb"
and that time my phone doesn't connected with PC. I don't know what to do so I turn off my phone.
then I open recovery mode again and select wipe cache then I go out to take a bath.
I came back and see my phone is off so I boot it.
It's booting about 2-3 mins and nothing happen so i go to recovery mode again but this time they have problem like i explain before(blink error message that can't pass by hold power button and press volume up button)
So anyone have a solution for my problem. please I really need your help!
Sorry for my bad english
Hi,
I had this when I went to wipe my system cache and it failed. Your best bet, especially if you can't get into recovery is to fastboot flash the recovery again if you have an unlocked bootloader.
If you don't you'll want to unlcok the bootloader and follow the instructions for using ADB if you're new to it: http://forum.xda-developers.com/zenfone2/general/asus-zenfone-2-flashing-recovery-mode-t3096596
How can I unlock my boot loader when i can't even open up my phone.
stultus136 said:
How can I unlock my boot loader when i can't even open up my phone.
Click to expand...
Click to collapse
If you hold volume down and power, it should go to bootloader first, then you have your choices for recovery....Get it to the bootloader screen, then run the commands to unlock it...
Could you please tell me everything step by step on how to cure my phone?
I'm very noob.
okay thank you.
I can start it now
THANKS!!!!!!!
p.s. i use fastboot erase cache code
stultus136 said:
okay thank you.
I can start it now
THANKS!!!!!!!
p.s. i use fastboot erase cache code
Click to expand...
Click to collapse
Glad you have it working...It seems that wiping the system cache can be problematic at times - Perhaps it's a bug.
Same Problem
smokinjoe2122 said:
Glad you have it working...It seems that wiping the system cache can be problematic at times - Perhaps it's a bug.
Click to expand...
Click to collapse
Hey I'm having the same problem, how'd you get the computer to recognize that the phone was plugged in? My computer does not recognize that the phone is on when I have the flashing error screen, so ADB doesn't recognize that there is a device connected.
Hi,
I had the exact same problem, and I managed to boot up again thanks to you!
What I did :
Install ADB and Drivers
Boot my phone into Fastboot (Power+Volume Up at boot, keeping VolumeUp button pressed while booting). Don't go into any menu (do not select recovery or so). At this point your computer should recognize your Android phone when you plug it in through USB.
Open up a cmd with admin rights, navigate to adb install path by typing : cd C:\adb
Then type : fastboot erase cache
It should trigger an action on your device, and the prompt should display sth like "Cache successfully erased" (I don't remember exactly)
Finally type : fastboot reboot, press volume up while booting again, and access Recovery like usual!
Now you can try wiping your partition cache again.
Worked like a charm for me! Thanks a lot
Hi,
I have a unique problem. I cant go into fastboot. Yes, fastboot on my OPT is not a opltion.
I cant instal TWRP. I can't wipe the OS to flash a new one.
My question is this:
Is there a way to wipe the partitions on a android phone via windows or something?
This problem is created by me. Somehow I flash OOS over CM (??)
So when my phone boots (bootloader is unlocked) I will see 2 boot sequences wich prevents me from accesing the fastboot menu.
The solution I see is this: Enter TWRP --> Wipe all but USB-OTG ...
Anyway, I hope there is a android Einstein here because I'm at a loss..
Feel free to ask any questions and pls help me!
Grt TwoChill
TowChill said:
Hi,
I have a unique problem. I cant go into fastboot. Yes, fastboot on my OPT is not a opltion.
I cant instal TWRP. I can't wipe the OS to flash a new one.
My question is this:
Is there a way to wipe the partitions on a android phone via windows or something?
This problem is created by me. Somehow I flash OOS over CM (??)
So when my phone boots (bootloader is unlocked) I will see 2 boot sequences wich prevents me from accesing the fastboot menu.
The solution I see is this: Enter TWRP --> Wipe all but USB-OTG ...
Anyway, I hope there is a android Einstein here because I'm at a loss..
Feel free to ask any questions and pls help me!
Grt TwoChill
Click to expand...
Click to collapse
Here you can find a recovery guide:
https://forums.oneplus.net/threads/guide-mega-unbrick-guide-for-a-hard-bricked-oneplus-3.452634/
I'd recommend methode 2, because it seems more east to do.
Good luck!
TowChill said:
Hi,
I have a unique problem. I cant go into fastboot. Yes, fastboot on my OPT is not a opltion.
I cant instal TWRP. I can't wipe the OS to flash a new one.
My question is this:
Is there a way to wipe the partitions on a android phone via windows or something?
This problem is created by me. Somehow I flash OOS over CM (??)
So when my phone boots (bootloader is unlocked) I will see 2 boot sequences wich prevents me from accesing the fastboot menu.
The solution I see is this: Enter TWRP --> Wipe all but USB-OTG ...
Anyway, I hope there is a android Einstein here because I'm at a loss..
Feel free to ask any questions and pls help me!
Grt TwoChill
Click to expand...
Click to collapse
If you are getting two boot screens, please confirm if this is what you see in your first boot screen:
some text which goes like "Your device cannot be trusted etc etc. fastboot oem lock something something"
If yes, press the volume buttons at this screen, which will take you to an "Options menu"
This will have options to power off, restart, recovery, fastboot, back to previous page.
use volume down buttons to move selection to fastboot and press power button to select fastboot.
This will take you to bootloader.
Alternatively:
Is the device getting identified by your computer when connected?
If yes, and if you have adb tools installed, try this command, after connecting to computer and selecting usb configuration as transfer files
adb devices
The result of this should show your device
then type:
adb reboot bootloader
This should take you to your bootloader screen.
pvramk said:
If you are getting two boot screens, please confirm if this is what you see in your first boot screen:
some text which goes like "Your device cannot be trusted etc etc. fastboot oem lock something something"
If yes, press the volume buttons at this screen, which will take you to an "Options menu"
This will have options to power off, restart, recovery, fastboot, back to previous page.
use volume down buttons to move selection to fastboot and press power button to select fastboot.
This will take you to bootloader.
Alternatively:
Is the device getting identified by your computer when connected?
If yes, and if you have adb tools installed, try this command, after connecting to computer and selecting usb configuration as transfer files
adb devices
The result of this should show your device
then type:
adb reboot bootloader
This should take you to your bootloader screen.
Click to expand...
Click to collapse
Thank you for your replay.
I have done all of this and i do understand how this works.
I have adb drivers installed, my computer does reconizes my phone and everything works even the reboot to bootloader via CMD. (adb devices, it shows, etc)
When my phone then tries to access the bootloader, it will show those messeges " this devices cant be trusted etc etc." afther 5 seconds again I see the the android logo (with a few lines of static on the bottom) (( that clearly is not right )) but it will show me again the same message " this devices cant be trusted etc etc" ... then it will just show me the battery icon and power precentage (this if I choose to boot to bootloader) or else it starts normally..
Clearly the flashing of CM failed. And with a sideload to install OxygenOS I can use it.. But it does prevents me from accessing the fastboot mode..
So Is there an alternative way to install TWRP without using the fastboot mode? Or is there an other way i can try to wipe the partitions inc. the os?
From there I know what to do.
TowChill said:
Thank you for your replay.
I have done all of this and i do understand how this works.
............
So Is there an alternative way to install TWRP without using the fastboot mode? Or is there an other way i can try to wipe the partitions inc. the os?
From there I know what to do.
Click to expand...
Click to collapse
well if you are rooted you can try using an app called flashify or flashfire to install twrp
pvramk said:
well if you are rooted you can try using an app called flashify or flashfire to install twrp
Click to expand...
Click to collapse
Thanks! Unfortunatly my phone isn't rooted anymore ..
I'm screwed right?
TowChill said:
Thanks! Unfortunatly my phone isn't rooted anymore ..
I'm screwed right?
Click to expand...
Click to collapse
When the display shows the battery % check if fastboot devices shows your device?
If not I'm sorry, I would not be of any more help to you my friend.
Hope someone more knowledgeable comes along and clears your problem....
TowChill said:
Thank you for your replay.
I have done all of this and i do understand how this works.
I have adb drivers installed, my computer does reconizes my phone and everything works even the reboot to bootloader via CMD. (adb devices, it shows, etc)
When my phone then tries to access the bootloader, it will show those messeges " this devices cant be trusted etc etc." afther 5 seconds again I see the the android logo (with a few lines of static on the bottom) (( that clearly is not right )) but it will show me again the same message " this devices cant be trusted etc etc" ... then it will just show me the battery icon and power precentage (this if I choose to boot to bootloader) or else it starts normally..
Clearly the flashing of CM failed. And with a sideload to install OxygenOS I can use it.. But it does prevents me from accessing the fastboot mode..
So Is there an alternative way to install TWRP without using the fastboot mode? Or is there an other way i can try to wipe the partitions inc. the os?
From there I know what to do.
Click to expand...
Click to collapse
If nothing works, try method 2 from the Hard Brick guide from Naman Bhalla.
Some informations at first:
XT1676 Moto G5, Fine Gold, 16GB
(TYPE M2675/ FCC ID: <known>/ SEQ#: <known>)
2017-10-30
Problem: Stuck in unlocked Bootloader
Hi all,
i am stuck on bootloader and cant get out.
On my PC I have "Minimal ADB and Fastboot"(v. 1.4.2.) installed and after i open a command prompt(admin) and type
- "fastboot devices" my phone is listed as <NR> fastboot
so that works as the only positive thing i can say
- "adb reboot", *daemon not running. starting it now on port 5037*
*daemon started successfully*
error: no devices/ emulators found
- "adb reconnect", error: no devices/ emulators found
i am not into the adb commands at all, i am a dummy and i would be so glad if someone could lead me out of my problem.
Maybe a word how i got into there:
1) i installed the minimal adb and fastboot(v1.4.2.)
2) i unlocked the bootloader by doing that over the Motorola UNLOCK Bootloader site
3) then i rooted & Flash Twrp Recovery (twrp-3.1.1-0-cedric)
with "fastboot flash recovery twrp-3.1.1-0-cedric.img"
4) first time entered into twrp recovery and i did the following:
A) a factory wipe-> reboot back to recovery mode->
B) install no-verity-opt-encrypt-5.1-> reboot and let system start before i turn off phone and enter bootloader(vol down+start) again
C) after entering recovery mode again, i install Magisk-v11.6 -> reboot->
D) now everything seemed to work, the system started properly rooted.
E) but then i decided to flash once again the Magisk-v11.6 followed by wipe data/ factory reset cause i wanted to completly do the flashing all over.
(dont ask me why i did it.. i could explain and tell you my intention but well it happened anyway and brought me to where i am stuck now)
but that was on this move not all yet: i also wipe dalvik cache
so after wipedalvik/ cache , since that moment i couldnt access to my SD Card anymore as it simply didnt show up anymore.
after a restart i was my first time in an endless bootloop of that Screen with "Erasing"(, the letters sourrounded by a spectral colored circle)
i had to disconnect the phone from power . also i tried to remove the battery for a day. but it would only get me back into that bootloop and only get me out by removing the battery...
i dont know anymore what happened then when the phone now got stuck in the bootloader instead of the bootloop. But yea, now i am stuck here, appreciating any help :highfive:
more infromation from my bootloader screen:
AP Fastboot Flash Mode(secure)
BLB8.12 (<known>, 2017-04-19 11:00:47)
Baseband <known>
Product/ Variant: cedric XT1676 16GB P5
Serial Number: <known>
CPU: MSM8937
eMMC: <known>
DRAM: <known>
Console [NULL]: null
Tools Mode Config: DISABLED
Battery OK
flashing_unlocked
Software status: Official
Connect USB Data Cable
- When pressing <Start>
Your device has been unlocked and can't be trusted.
to learn more, visit:
motorola,com/ unlockbootloader
ID: bad key
Your device will boot in 5 seconds.
->
bevor the Phone drops back to Bootloader
when pressing <RESTART BOOTLOADER>
it restarts to BOOTLOADER
- When pressing <Start Recovery>
Your device has been unlocked and can't be trusted.
to learn more, visit:
motorola,com/ unlockbootloader
ID: bad key
Your device will boot in 5 seconds.
->
after 10 seconds another screen poops up:
"Erasing", the letters sourrounded by a spectral colored circle for 3 seconds,
bevor the Phone just drops back to Bootloader
(talking about Erasing ..)
- When pressing <POWER OFF>
Power Off works
- When pressing <FACTORY RESET>
Your device has been unlocked and can't be trusted.
to learn more, visit:
motorola,com/ unlockbootloader
ID: bad key
Your device will boot in 5 seconds.
->
bevor the Phone just drops back to Bootloader
- When pressing <BARCODES>
Barcodes are shown
- When pressing <BP TOOLS>
Your device has been unlocked and can't be trusted.
to learn more, visit:
motorola,com/ unlockbootloader
ID: bad key
Your device will boot in 5 seconds.
->
bevor the Phone just drops back to Bootloader
- When pressing <QCOM>
Your device has been unlocked and can't be trusted.
to learn more, visit:
motorola,com/ unlockbootloader
ID: bad key
Your device will boot in 5 seconds.
->
bevor the Phone just drops back to Bootloader
- When pressing <BOOTLOADER LOGS>
Display shows:
AP Fastboot Flash Mode(secure)
Fastboot Reason: UTAG "bootmode" configured as fastboot
When connecting an USC- cable
Transfer Mode: USB Connected
...shows up but i cant get any adb commands to work tho ofc i am a dummy at it...
oh my, i just helped myself by reading my first poste here on the forum from 2016.
i made it now to start twrp by downloading the twrp_cedric_3.1.1-0 once again putting the recovery in my adb folder and type
<fastboot flash recovery twrp.img>
followed by <fastboot reboot-bootloader>
i am curious if i can get going now and if my SD card will be read and if i can get a new flash going...
now back in twrp i go first again to wipe/ factory reset.
now going to reboot, and reboot back into recovery. only gets me back to bootloader from where i can enter twrp manually now(but there is already an indication of the problem i have?)
also before the reboot, it doesnt ask me to install the twrp app anymore where i usually choose "do not install".
now i go to install the <no-verity-opt-encrypt-5.1>, flashing it successfully as it says at the end of the process but there is also some error message in the log before the ...done:
Failed to mount '/data' (invalid argument)
now i thought i should be able to boot the system again but i only get back into the bootloader...
can someone help me how to proceed correctly?
did i miss something to flash?
Techcri said:
now back in twrp i go first again to wipe/ factory reset.
now going to reboot, and reboot back into recovery. only gets me back to bootloader from where i can enter twrp manually now(but there is already an indication of the problem i have?)
also before the reboot, it doesnt ask me to install the twrp app anymore where i usually choose "do not install".
now i go to install the <no-verity-opt-encrypt-5.1>, flashing it successfully as it says at the end of the process but there is also some error message in the log before the ...done:
Failed to mount '/data' (invalid argument)
now i thought i should be able to boot the system again but i only get back into the bootloader...
can someone help me how to proceed correctly?
did i miss something to flash?
Click to expand...
Click to collapse
For failed mount data goto wipe & select format data (option on the right)
Reboot to recovery
For always going into recovery either you don't have a rom installed or read the faq section on my twrp thread as the answer is there
First of all thanks TheFixItMan, that you are behind it and your thread looks really cool and i will immediatly read and try to understand it!
For now i am stuck in the following:
TheFixItMan said:
For failed mount data goto wipe & select format data (option on the right)
Reboot to recoverye
Click to expand...
Click to collapse
i went to "wipe" & "select format data"
the process shows successfully and "...done" but in the log there is a line of red letter:
<Red Letter>"Failed to unmount '/data' ( Device or resource busy)"
<White Letter> You may need to reboot recovery to be able to use / data again.
i went back and to reboot and recovery.
but recovery wouldnt be booted but i get back to the bootloader(maybe that is still an indication of the problem i have here?)
manually entered recovery i did the select format data again but <red letter> line remains.
TheFixItMan said:
For always going into recovery either you don't have a rom installed or read the faq section on my twrp thread as the answer is there
Click to expand...
Click to collapse
i will parallel read your thread now, thx for being behind it solving the questions! :good:
Techcri said:
First of all thanks TheFixItMan, that you are behind it and your thread looks really cool and i will immediatly read and try to understand it!
For now i am stuck in the following:
i went to "wipe" & "select format data"
the process shows successfully and "...done" but in the log there is a line of red letter:
<Red Letter>"Failed to unmount '/data' ( Device or resource busy)"
<White Letter> You may need to reboot recovery to be able to use / data again.
i went back and to reboot and recovery.
but recovery wouldnt be booted but i get back to the bootloader(maybe that is still an indication of the problem i have here?)
manually entered recovery i did the select format data again but <red letter> line remains.
i will parallel read your thread now, thx for being behind it solving the questions! :good:
Click to expand...
Click to collapse
You have to select recovery from the bootloader menu to enter recovery
You can also type in a terminal window whilst phone connected to pc in fastboot
fastboot erase userdata
This will erase all internal data (the same as format data in twrp)
Important Notes For Stock Rom Users
When you first start TWRP it will ask you to swipe to allow modifications - If you do this your stock rom will no longer boot unless you disable dm-verity.
This can be done either by flashing a disable dm-verity zip or by flashing SuperSu zip which will disable it for you
Click to expand...
Click to collapse
ok, stock rom didnt boot so i flashed the "no-verity-opt-encrypt-5.1" .zip
and voila, i could boot the stock again finally! yipie!
but three things i noticed:
1) the boot progress is suspicous / wrong/ stuck at a moment:
"hello" and "moto" i still see and before the letters of moto start spinning around, the screen freezes for like 2-3 seconds and the next ting i see is the red mouth and cameleon and so on
2) i tried to test camera real quick and it says camera is busy
camera unable to start. if this repeats please power off your phone and restart.
(i did already 5 restarts now and still same problem)
anyway, i wanted to install a ROM now, something like Cyanogenmod.
in this context i wonder what the Magisk-v11.6 does? Does it just give superuser permission and is it always required?
3) system only gives me option to Power Off System(no reboot possible)
and that power off and turn on always gets me first into bootloader tho i dont press vol down+start
Edit:
ok, i have here 3 issues still but it goes offtopic already. i throw a thanks first of all at TheFixItMan and then i think thread cna be closed.
I will soon try to install a ROM, like LineageOS 15.1 , and hope that my previous 3 issues will be solved in the process. . .
Techcri said:
ok, stock rom didnt boot so i flashed the "no-verity-opt-encrypt-5.1" .zip
and voila, i could boot the stock again finally! yipie!
anyway, i wanted to install a ROM now, something like Cyanogenmod.
in this context i wonder what the Magisk-v11.6 does? Does it just give superuser permission and is it always required?
Click to expand...
Click to collapse
Cyanogenmod is now lineageos
Use the latest version of magisk to root (see official magisk thread on xda)
You can run modules to mod phone without tripping integrity or dm-verity which if false will stop apps that check if you are rooted from working
Magisk hide can hide apps from detecting you are rooted on a per app selected basis
3) system only gives me option to Power Off System(no reboot possible)
and that power off and turn on always gets me first into bootloader tho i dont press vol down+start
Click to expand...
Click to collapse
Phone should power off normally
If it can't be started normally without going in bootloader and selecting normal startup see my faqs in twrp thread & follow guide to wiping the misc partition
Note if flashing lineageos 15.1 you will require the 64bit version of TWRP available on the lineageos thread - I did not compile this & don't support it
It also doesn't support encryption as far as I know so if you are encrypted you will need to format data & remove it else the rom will get stuck at the decryption screen
TheFixItMan said:
Phone should power off normally
Click to expand...
Click to collapse
it can be powered off normally as long as its not connected per usb (power or pc)
If it can't be started normally without going in bootloader and selecting normal startup see my faqs in twrp thread & follow guide to wiping the misc partition
Click to expand...
Click to collapse
that was not exactly the problem. my problem is that either i press restart system from system or from recovery, i first get a stop at the bootloader. from there i can just toggle to START and confirm. then my system boots. its just that i first need to confirm in bootloader the Start, always!
at this point i tried now anyways from your Official TWRP For Moto G5 Cedric- Thread |||||| your solution from your faq. But yea, it obviously doesnt fit my problem cause putting the lines in cmd prompt gave me that result and boot still does a stop at bootloader.. before i can start system or recovery..
So yea, after the first codeline didnt trigger for an unknown reason for me...
i hadnt the courage to even try the second more relevant codeline!
Note if flashing lineageos 15.1 you will require the 64bit version of TWRP available on the lineageos thread - I did not compile this & don't support it
It also doesn't support encryption as far as I know so if you are encrypted you will need to format data & remove it else the rom will get stuck at the decryption screen
Click to expand...
Click to collapse
btw, Thx a lot for the information, i appreciate it! i choose LineageOs 15.1 and it runs now. atm i am reading myself into magisk. Also big thanks for your tipp looking up the official thread.
Techcri said:
it can be powered off normally as long as its not connected per usb (power or pc)
that was not exactly the problem. my problem is that either i press restart system from system or from recovery, i first get a stop at the bootloader. from there i can just toggle to START and confirm. then my system boots. its just that i first need to confirm in bootloader the Start, always!
at this point i tried now anyways from your Official TWRP For Moto G5 Cedric- Thread |||||| your solution from your faq. But yea, it obviously doesnt fit my problem cause putting the lines in cmd prompt gave me that result and boot still does a stop at bootloader.. before i can start system or recovery..
So yea, after the first codeline didnt trigger for an unknown reason for me...
i hadnt the courage to even try the second more relevant codeline!
btw, Thx a lot for the information, i appreciate it! i choose LineageOs 15.1 and it runs now. atm i am reading myself into magisk. Also big thanks for your tipp looking up the official thread.
Click to expand...
Click to collapse
That error means your phone is not connected to your pc
Make sure you have enabled adb debugging in phones dev settings before booting into recovery
If you type
adb devices
It will list all devices attached
Once your device is listed the commands will work
TheFixItMan said:
That error means your phone is not connected to your pc
Make sure you have enabled adb debugging in phones dev settings before booting into recovery
If you type
adb devices
It will list all devices attached
Once your device is listed the commands will work
Click to expand...
Click to collapse
and you think that your commands fromyour solution here helps me with my issue that i can start straight to everywhere i want? Cause atm I just always have to go over the bootloader -"stop". From there i have then to manually "START" in order to start system (now: LineageOS 15.1:victory or where i have to manually toggle down to "RECOVERY MODE" and start TWRP.
Well, i would give it a try, but yea dunno what i am doing wrong here atm. i just realized that the command "adb devices" never worked for me yet, cause i got in conflict with the command fastboot adb devices which effectivly works for me. Cause before i installed lineageOS 15.1 i had to flash the twrp cedric 3.2.1-0 x64. i did that over the adb command prompt:
Code:
fastboot flash recovery twrp.img
and in that process i even let my phone restart to bootloader with
Code:
fastboot reboot bootloader
.
now i went to tab build nummer 7 times-> dev options "on" -> android debugging enabled.
when i go to bootloader now or to recovery, and connect my device, for a strange reason in command prompt "adb devices" shows that:
... i dont know why the cmd "adb devices" doesnt show my device. maybe there is a twrp setting i need to change?
Techcri said:
and you think that your commands fromyour solution here helps me with my issue that i can start straight to everywhere i want? Cause atm I just always have to go over the bootloader -"stop". From there i have then to manually "START" in order to start system (now: LineageOS 15.1:victory or where i have to manually toggle down to "RECOVERY MODE" and start TWRP.
Well, i would give it a try, but yea dunno what i am doing wrong here atm. i just realized that the command "adb devices" never worked for me yet, cause i got in conflict with the command fastboot adb devices which effectivly works for me. Cause before i installed lineageOS 15.1 i had to flash the twrp cedric 3.2.1-0 x64. i did that over the adb command prompt:
Code:
fastboot flash recovery twrp.img
and in that process i even let my phone restart to bootloader with
Code:
fastboot reboot bootloader
.
now i went to tab build nummer 7 times-> dev options "on" -> android debugging enabled.
when i go to bootloader now or to recovery, and connect my device, for a strange reason in command prompt "adb devices" shows that:
... i dont know why the cmd "adb devices" doesnt show my device. maybe there is a twrp setting i need to change?
Click to expand...
Click to collapse
Does it display a device when the phone is fully booted
If yes than the recovery you are using doesn't support adb (my official recovery does)
If no I recommend downloading the full android sdk and using the adb that comes with that (you will find it in the platform tools folder where you installed it)
Hello, thx for your support.
I linked the wrong picture. This Screeny shows the related cmd (when dev enabled, booted to recovery, connected via usb to pc and typed adb devices).
Does it display a device when the phone is fully booted. If yes than the recovery you are using doesn't support adb (my official recovery does)
Click to expand...
Click to collapse
it shows the same like linked above and when in recovery mode
so no , the 64bit version of twrp cedric 3.2.1-0 prolly isnt the problem.
If no I recommend downloading the full android sdk and using the adb that comes with that (you will find it in the platform tools folder where you installed it)
Click to expand...
Click to collapse
ok i will try that. and the command prompt i have to open from the directoryy<platform tools folder> then right?
would you deinstall minimal ADB and fastboot before installing full android sdk?
TheFixItMan said:
If no I recommend downloading the full android sdk and using the adb that comes with that (you will find it in the platform tools folder where you installed it)
Click to expand...
Click to collapse
still my phone isnt found
- sdk tools installed
- dev enabled
- adb debugging enabled
- command prompt opened at "...\android-sdk\platform-tools"
either in recovery nor in booted system nor in bootloader "adb devices" finds my phone
so the problem with the "bootstop" (have always to manually press "START" at bootloader) persists..
oh wait... i am not connected as admin! is it possible to open an admin command promp:silly:t?
so i am am reading here atm how to open command prompt in specific folder(platform-tools)
but wife is waiting for dinner so i better do that first..
Techcri said:
still my phone isnt found
- sdk tools installed
- dev enabled
- adb debugging enabled
- command prompt opened at "...\android-sdk\platform-tools"
either in recovery nor in booted system nor in bootloader "adb devices" finds my phone
so the problem with the "bootstop" (have always to manually press "START" at bootloader) persists..
oh wait... i am not connected as admin! is it possible to open an admin command promp:silly:t?
so i am am reading here atm how to open command prompt in specific folder(platform-tools)
but wife is waiting for dinner so i better do that first..
Click to expand...
Click to collapse
On windows 7 - hold shift then right click a white empty space of the window where adb is & select open command prompt here
Windows 7 or 10 - search for cmd then right click on cmd and select run as administrator then navigate using cd commands to adb location or copy & paste location (if any spaces in path then put the entire path in quotation marks)
On windows 7 - hold shift then right click a white empty space of the window where adb is & select open command prompt here
Click to expand...
Click to collapse
yes i did that before as non admin
Windows 7 or 10 - search for cmd then right click on cmd and select run as administrator then navigate using cd commands to adb location or copy & paste location (if any spaces in path then put the entire path in quotation marks)
Click to expand...
Click to collapse
i use win7 and cd'ing to the path was almost getting annoying
as screenshot shows, it still doesnt work
in my desperation i deinstalled now all adb drivers(minimal+ sdk)
ran a ccleaner and cleaned registry and reinstalled minimal adb again (btw, there was a new version by now out, 1.4.3)
so the episodes still goes on and i could figure out some new details
because i bought the same phone again for a relative who needed a phone..
in the process of setting it up correctly( thankfully xda is around ) i enabled dev options and the adb debugging
here is the result for the new phone
that shows now that executing as admin or standard user wasnt the problem. i just did it as standard user..
then i thought "hey cool, wait, i connect now my own G5 and see if i can get the phones' Nr displayed there and make sure my phone can communicate with my pc over adb( dunno if the sentence just made sense- greetz from a dummy)"
what happened is shown in this screenshot .. same picture as before! :crying:
(dont get irritated by the screeny because i used the same command prompt for
first, the new phone and
second, my "old" phone which doesnt boot properly, if you look at the command and the result
i am lost!
is it possible to reinstall a bootloader? or how come my phone doesnt communicate with the pc anymore?
and how come that effects the booting process so that i always get this "stop" at the bootloader although i pressed for a restart?
can i do any more tests that indicates what problem i have here?