Related
Hi, My DHD volume buttons no longer work and I've been reticent to send it off to get fixed as I can do with out the volume controls as opposed to being without a phone for 2-3 weeks.
However I used Rom manager to boot into CWR and was in the process of upgrading to revolution 5.2.4 from 5.1.8.
I ran the full wipe script then my fat fingers rebooted the phone rather than flashing the rom.
I now cant get back into CWR to flash the new rom. It just sits at the boot logo, obviously as all other partitions have been wiped.
Is there any other way I can force the phone to boot into CWR, perhaps using the sdk tools or similar?
I've tried adb devices, but it doesnt show up. Is there an external way to force the phone into flashing a new ROM or booting into CWRM ?
Thanks
Ron
I would like to help, first lets try using adb, command would be adb reboot recovery
Hi, thanks for the help.
As mentioned in OP. I have powered the phone on and have have already attempted this, but the device is not recognised by adb.
tools>adb reboot recovery
error: device not found
My question is how to get the device to be recognised if its simply sitting at the boot image?
R
Sorry I over looked that, it seems to me if adb (which is an sdk tool) won't recognize the device as being attached, i don't see any other sdk tool doing any different, also as far as I know there is no alternate method to scrolling through the boot loader that would allow you to choose recovery and flash a zip other then the volume keys , so it seems the solution is, to send the phone off, get the volume keys fixed, and then you will be able to get back into the boot loader, and select recovery, and reflash a rom. Other than that, I don't see any other method, if adb doesn't recognize the device as being plugged in, I am assuming you attempted to boot into boot loader as well, and see if adb recognized the device?
EDIT: stupid question you can't boot into boot loader without volume key
I just want to confirm that I need do nothing else other than configure the sdk and ENV path etc, such that if i can run adb and get the deafult output, eg switches fr command line options etc...
then all I should need to do is turn phone on and connect via usb to computer. I dont need to edit any config files for specific phone versions or whatnot?
If not then Ill try and bring it to a vodaphone shop and see if they can fix the volume button...
R
if you get the volume buttons fixed, we don't even need adb, I was simply thinking adb since your volume buttons are broken. Once the volume buttons are fixed, you simply need to boot into boot loader, then to recovery, mount USB mass storage, put a new rom on there, wipe the phone, flash the rom and your good
Good luck mate, do some mediation meanwhile and learn to keep patience, so when your phone is back, you can treat it gently while in the recovery.
You will be alright once your vol keys are fixed.
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 accidently erased everything from the KF2, all I have on it now is the recovery.
How can I get a rom back on the device?
When I plugged it in the computer under Device Manager it says Portable Devices >> F:/
When I go to my computer to try to enter f:/ its inaccessible.
How can I fix this?
Thanks!
Same issue here. Understood the instruction to wipe everything before installing ROM to mean "System" and "Internal Storage" as well. Now the downloaded ROM and "gapps" zip files are gone...
Found something called "ADB Sideload" in TWRP, could that help?
Like the OP, would appreciate some help. Kindle is a brick for now...
chipsndukes
Back Up & Running
First You need a Fastboot Cable.
Run The Recovery Tool. (Options 1 then 2)
When its completed unplug the Fastboot Cable and press and hold the power button until the KF2 turns off.
Turn it back on and you are all set to Root it!
Rooting
[ONE-CLICK] Automated Freedom-Boot and TWRP installer
OK, thanks LEGEND94, that helped !
Only difference to above: did not use a Fastboot cable to get into fastboot mode, rather fmkilo's technique here: http://forum.xda-developers.com/showthread.php?t=2117224
Held off button to shut down and restarted without having to do anything else, did not have to type any command to get out of fastboot mode.
Am restarting root and ROM flashing, hopefully will work this time.
Thanks again,
chipsndukes
chipsndukes said:
OK, thanks LEGEND94, that helped !
Only difference to above: did not use a Fastboot cable to get into fastboot mode, rather fmkilo's technique here: http://forum.xda-developers.com/showthread.php?t=2117224
Held off button to shut down and restarted without having to do anything else, did not have to type any command to get out of fastboot mode.
Am restarting root and ROM flashing, hopefully will work this time.
Thanks again,
chipsndukes
Click to expand...
Click to collapse
even though legend was OP, his method was a bit overkill, but totally fine.
Once you have recovery, or even the bootloader, you should NEVER need to restore. From the bootloader you can get into fastboot now, and from fastboot you can get the recovery.
As for putting files on, I'm not sure. I could look it up but you both got your issues solved. If someone coming here does need the help, PM me and I can look it up, but from what i remember on other android devices, usually the recovery somewhere has an option to mount USB like a storage device (probably bad wording there) but basically just like when you "turn on usb storage" in the android OS.
I am ASSUMING TWRP has something similar, and if I'm wrong, I'm sure you can always ADB to push the files onto the device from your PC in fastboot mode.
iytrix said:
even though legend was OP, his method was a bit overkill, but totally fine.
Once you have recovery, or even the bootloader, you should NEVER need to restore. From the bootloader you can get into fastboot now, and from fastboot you can get the recovery.
As for putting files on, I'm not sure. I could look it up but you both got your issues solved. If someone coming here does need the help, PM me and I can look it up, but from what i remember on other android devices, usually the recovery somewhere has an option to mount USB like a storage device (probably bad wording there) but basically just like when you "turn on usb storage" in the android OS.
I am ASSUMING TWRP has something similar, and if I'm wrong, I'm sure you can always ADB to push the files onto the device from your PC in fastboot mode.
Click to expand...
Click to collapse
Unfortunately usb Mount doesn't work in the kf2 twrp. I would love the option.
You CAN adb sideload from twrp though.
--
Sent from my Kindle Fire 2, CM 10.1
What I did above is the easiest way, the sideload didn't even work!
chipsndukes said:
Held off button to shut down and restarted without having to do anything else, did not have to type any command to get out of fastboot mode.
Click to expand...
Click to collapse
One change to the above statement. I did have to get out of fastboot mode, but it was confusing how because the terminal emulator was now gone.
I did this instead via a command window with the Fire plugged into the computer. I sent the "fastboot -i0x1949 oem idme bootmode 1" command while in the root directory for the KF2_SRT_10.2.3 restore package, there is a fastboot.exe file there.
Hope that helps.
chipsndukes
I recently tried to flash back from Lego Rom to stock ZVC and have hit some trouble. I used CWM to clear the caches/data, as per usual, but after installing the ZVC rom the phone just boot loops at the Lego Rom boot screen.
Normally, I would jump into recovery, but my volume buttons no longer work (they failed after a screen replacement, I suspect the ribbon cable is damaged). What are my options? Can ADB force it into recovery for me?
I've installed the latest USB drivers, but ADB is not recognizing any devices (at the ROM booting screen or at the charging/battery graphic). Do I have any options beyond buying a new volume button ribbon cable?
I have the same issue in windows and ubuntu. Will LGNPST be able to communicate with the device?
LordKyleOfEarth said:
I've installed the latest USB drivers, but ADB is not recognizing any devices (at the ROM booting screen or at the charging/battery graphic). Do I have any options beyond buying a new volume button ribbon cable?
I have the same issue in windows and ubuntu. Will LGNPST be able to communicate with the device?
Click to expand...
Click to collapse
well first of all yes you can reboot recovery using adb.
But if you installed the zvc rooted ROM then why is it booting Lego?
You can install philz or twrp for a full touch recovery and not need volume buttons. You'll still need to use cmd to do "adb reboot recovery" or adb reboot fastboot". You can also flash recovery from adb. Just get a recovery.IMG I think it's adb fastboot flash recovery.IMG or whatever the name of the recovery is.
But if ADB doesn't return any devices when I execute "ADB devices" how can I get it to send a reboot signal to the phone? When I tried "ADB reboot recovery" I was given an error about no device connected.
LordKyleOfEarth said:
But if ADB doesn't return any devices when I execute "ADB devices" how can I get it to send a reboot signal to the phone? When I tried "ADB reboot recovery" I was given an error about no device connected.
Click to expand...
Click to collapse
I must have not been thinking the whole picture. What can the phone do? What happens when you turn it on, do the volume buttons work at all? Because if you can get into recovery or fastboot at all then something can be done try multiple combinations as much as possible. I'm thinking hold the power button down and plug in USB. Wait for something to happen then let go of power. Does your computer ever recognize something is plugged in? Maybe during boot?
My N1 suddenly reboot and then it can't start, just continuosly bootloop and can't boot into droidboot or recovery by pressing Power+ Vol-. Any help!!!
anyone help me!
same problem
We need to know more to be able to help. What did you do before updating? root? update? nothing?
syddd said:
We need to know more to be able to help. What did you do before updating? root? update? nothing?
Click to expand...
Click to collapse
I followed this instruction http://forum.xda-developers.com/showpost.php?p=60925623&postcount=44. Root has been established successfully, then installed GApps and after the tablet does not boot
Shvonder said:
I followed this instruction http://forum.xda-developers.com/showpost.php?p=60925623&postcount=44. Root has been established successfully, then installed GApps and after the tablet does not boot
Click to expand...
Click to collapse
That's it, now it not work anymore, just reboot and play bootanimation then reboot
alan_greece said:
My N1 suddenly reboot and then it can't start, just continuosly bootloop and can't boot into droidboot or recovery by pressing Power+ Vol-. Any help!!!
Click to expand...
Click to collapse
I have same problem
Help me!!! Please
help us!
For me its working flawlessly.... may be u have done something wrong. Had u turned off mpt mode ? Did u format and cleared catch before installing gapps ?
still waiting for solution...
( help me
When my one was boot loop.
I 've solved loop problems like following process.
1. Open windows device manger for check N1 is ready to use ADB.
2. Ready CMD for use ADB.
3. Connect to PC and wait until can see ADB Device on windows device manager.
4. ADB devices
5. ADB reboot bootloader
6. Select recovery with volume button.
7. If success on recovery mode. just push once power button. (can see some menu)
8. select factory reset. ( I can't remember correct menu name) or wipe cache / data?
After this okay to boot initial setup.
I can't remember well what I do before .
It's passed 2weeks.
And My one on the way from seller cause fix from another problems.
soondin said:
When my one was boot loop.
I 've solved loop problems like following process.
1. Open windows device manger for check N1 is ready to use ADB.
2. Ready CMD for use ADB.
3. Connect to PC and wait until can see ADB Device on windows device manager.
4. ADB devices
5. ADB reboot bootloader
6. Select recovery with volume button.
7. If success on recovery mode. just push once power button. (can see some menu)
8. select factory reset. ( I can't remember correct menu name) or wipe cache / data?
After this okay to boot initial setup.
I can't remember well what I do before .
It's passed 2weeks.
And My one on the way from seller cause fix from another problems.
Click to expand...
Click to collapse
but when i run adb reboot bootloader, it said my device was unauthorized
soondin said:
When my one was boot loop.
I 've solved loop problems like following process.
1. Open windows device manger for check N1 is ready to use ADB.
2. Ready CMD for use ADB.
3. Connect to PC and wait until can see ADB Device on windows device manager.
4. ADB devices
5. ADB reboot bootloader
6. Select recovery with volume button.
7. If success on recovery mode. just push once power button. (can see some menu)
8. select factory reset. ( I can't remember correct menu name) or wipe cache / data?
After this okay to boot initial setup.
I can't remember well what I do before .
It's passed 2weeks.
And My one on the way from seller cause fix from another problems.
Click to expand...
Click to collapse
i cant use ADB now, always unauthorized device....
Anyone who had a way to fix it? I tried but my N1 dont connect with the PC..
plz help us!
i can not open recovery by pressing vol- + power. I got a bootloop N1,too.
kaikool said:
i can not open recovery by pressing vol- + power. I got a bootloop N1,too.
Click to expand...
Click to collapse
Iam russian... Use the phone flash tool intel v444. connect you device via usb. reboot rebooot rebooot.... when programm detect your device. check in "custom flash" option fastboot or adb. and flash ifwi file. wait min 15.... WHEN YOU DEVICE TURN ON BOOTLOADER CANCEL FLASH (PULL USB CABBLE!!!) volume - to recovery. open recovery menu and factory reset and cache clear. update with sideload and wipe data/ reboot!
@Andreko777 thank you, ill try it. Hope it works! But i think it doesnt work because, when i plug my usb cable to my computer and run Intel flashtool, it can not regconize my device. So i cant do anything else,........
@alan_greece i have found another method in a Chinese forum, but i dont have my device here to do. you can try this.
1. Tools required:
1, Nokia N1 ROOT tools:
link: http: //pan.baidu.com/s/1c0i1KU8 Password: c7i3
2, Nokia ROM package:
link: http: //pan.baidu.com/s/1c06OrhI Password: zfg3
above package Zhongguancun Forum "installed Daitou", "expect Dawn c466469156" offer. Some pictures cut from below "expectations dawn c466469156" rescue brick tutorial (need only be able to enter the official REC tutorial) Step:
Prerequisite: There is a station has already authorized under the USB debugging mode N1 computer; N1 boot card after death, in The computer's device manager can see Android Composite ADB Interface device.
1, the N1 is turned on, connected to the computer.
2, download IntelAndroid-FBRL-05-16-2015-PTR.rar, unzip it into a directory in the root directory of the disk,
Right-click launcher.bat, choose Run as administrator.
Follow the onscreen prompts for capital ACCEPT OK. (Must be capitalized, because LINUX is case-sensitive)
viewing screen, if the device is connected, a blue-green word, if the word is red, was not connected, carefully check the above-mentioned process is correct.
3. After the device is connected, press the T1 diagram interface, Enter. N1 will restart, and N1 official BOOTLOADER screen appears, and writes in execution. Until an error message. Stop.
4, according to N1 volume keys, select the recovery, press the power button to confirm. Reboot into official REC. Then select Options apply update from adb and even computers.
5, put the package before downloading rename the file update.zip pulled platform-tools folder unzipped. Open a command indicator cd into this folder.
6, in the command prompt, type adb sideload update.zip Enter.
7, prompted reboot the N1.
kaikool said:
@Andreko777 thank you, ill try it. Hope it works! But i think it doesnt work because, when i plug my usb cable to my computer and run Intel flashtool, it can not regconize my device. So i cant do anything else,........
@alan_greece i have found another method in a Chinese forum, but i dont have my device here to do. you can try this.
1. Tools required:
1, Nokia N1 ROOT tools:
link: http: //pan.baidu.com/s/1c0i1KU8 Password: c7i3
2, Nokia ROM package:
link: http: //pan.baidu.com/s/1c06OrhI Password: zfg3
above package Zhongguancun Forum "installed Daitou", "expect Dawn c466469156" offer. Some pictures cut from below "expectations dawn c466469156" rescue brick tutorial (need only be able to enter the official REC tutorial) Step:
Prerequisite: There is a station has already authorized under the USB debugging mode N1 computer; N1 boot card after death, in The computer's device manager can see Android Composite ADB Interface device.
1, the N1 is turned on, connected to the computer.
2, download IntelAndroid-FBRL-05-16-2015-PTR.rar, unzip it into a directory in the root directory of the disk,
Right-click launcher.bat, choose Run as administrator.
Follow the onscreen prompts for capital ACCEPT OK. (Must be capitalized, because LINUX is case-sensitive)
viewing screen, if the device is connected, a blue-green word, if the word is red, was not connected, carefully check the above-mentioned process is correct.
3. After the device is connected, press the T1 diagram interface, Enter. N1 will restart, and N1 official BOOTLOADER screen appears, and writes in execution. Until an error message. Stop.
4, according to N1 volume keys, select the recovery, press the power button to confirm. Reboot into official REC. Then select Options apply update from adb and even computers.
5, put the package before downloading rename the file update.zip pulled platform-tools folder unzipped. Open a command indicator cd into this folder.
6, in the command prompt, type adb sideload update.zip Enter.
7, prompted reboot the N1.
Click to expand...
Click to collapse
Now i cant authorized my device anymore