Related
Helloo...
I had my nexus one updated to cm 6.1.1 stable.
The next day i noticed he keeps restarting the phone.
I thought let me pull out de battery and turn the phone on.
Now its stuck at the coloured x and i cant get in recovery.
When i boot into recevory it gets stuck again at the coloured x.
I have flashed stock kernel frg33 and flashed amon recovery with fastboot and tried the passimg method to but it still gets stuck.
My phone is rooted and unlocked bootloader.
What can i do now?
Thnxx in advance
Can you get into bootloader by--> holding down volume-dwn, then pressing the power button, and the releasing the power button while still holding down volume-dwn?
You might need to remove you battery in between tries of this (plus pressing the power button i hear, with the battery removed to drain and remaining power..for 5 secs at least).
If that doesn't work, you could try the three finger salute for Android: Volume dwn+trackball pressed, then tapping power button and letting go of power button, and then the other two.
in most cases you will still be able to use adb
try running 'adb reboot recovery'
Like i sad, i can boot into recovery using the bootloader. But when it start up in recovery it gets stuck at the coloured x.
Fastboot is working but i cant get the adb to work.
Fastboot sees my device an adb doesnt.
What can i do to make adb work?
I installed new sdk and htc sync.
Running on windows 7
try to flash a new recovery through fastboot
download amon ra
open up a cmd
"cd " to directory where you downloaded it
rename amon-ra-recovery.xxxx.img to recovery.img
fastboot flash recovery recovery.img
then try to boot to recovery again
I tried that 10 times but it doesnt work.
Still gets stuck at the coloured x
Fastboot flash the system, bootloader, userdata, etc, and seem if it will boot to system?
Sent from my Nexus One using XDA App
this might sound a bit daft but try taking your sdcard out of the phone and rebooting to recovery
Tried that all. But doesnt work
What sort of error messages are you getting?
Sent from my Nexus One using XDA App
Have you tried to erase cache and dalvik through fastboot commands?
Sent from my Nexus One using XDA App
Nothing!!
Everything what i try to do goes wel.
Update with passimg goes wel.
Fastboot system, boot, userdata, bootloader, everything goes wel.
I dont get any error.
But when i start my phone it gets stuck by the coloured x.
Looks like hardware failure, then...
Sent from my Nexus One using XDA App
Oke that is not good cause i have no waranty anymore.
danger-rat said:
Have you tried to erase cache and dalvik through fastboot commands?
Sent from my Nexus One using XDA App
Click to expand...
Click to collapse
What is the fastboot command to erase dalvik?
Good question - I've used the erase cache command, and just assumed there would be an erase dalvik command. I may be wrong...?
Sent from my Nexus One using XDA App
Ashvan said:
Oke that is not good cause i have no waranty anymore.
Click to expand...
Click to collapse
When did you get your phone?
Sent from my Nexus One using XDA App
I bought it second hand in september this year. I think its a year old now.
But since i have everything unlocked the waranty is void?
What is a dalvik cache exactly?
Does nobody knows the fastboot command to erase it?
Ashvan said:
I bought it second hand in september this year. I think its a year old now.
But since i have everything unlocked the waranty is void?
Click to expand...
Click to collapse
The very first nexus phones are just coming up to a year old, so the chance is that yours is still in warranty. Call HTC, and see what they say...
Sent from my Nexus One using XDA App
I was using my Incredible S normally, when it suddenly faded to black and was totally freeze so I decided to restart it (Taking the battery out)
Then after reboot, It got stuck on white Htc logo (with "quietly brilliant animation playing again and again"). So restarted it again and tried to use the fast reboot option (restarting and holding the VOL DOWN button), but this also didn't work.
Some details: I Have Android Revolution (ROM) with S-OFF
Hope somebody help me!
Bastian_n said:
I was using my Incredible S normally, when it suddenly faded to black and was totally freeze so I decided to restart it (Taking the battery out)
Then after reboot, It got stuck on white Htc logo (with "quietly brilliant animation playing again and again"). So restarted it again and tried to use the fast reboot option (restarting and holding the VOL DOWN button), but this also didn't work.
Some details: I Have Android Revolution (ROM) with S-OFF
Hope somebody help me!
Click to expand...
Click to collapse
Did you remove battery ,then replace battery then
volume down and power?(after the first restart).And im assuming also that you want to go to recovery to redo a backup..
Yes, I just did that (also tried with another battery). But when I pushed recovery, It restarts and still getting stuck on the boot screen. (but now with some vibrations and then goes off)
I was thinking about reinstall the ROM, but that's my last option because I don't have a way to make a backup
Bastian_n said:
Yes, I just did that (also tried with another battery). But when I pushed recovery, It restarts and still getting stuck on the boot screen. (but now with some vibrations and then goes off)
I was thinking about reinstall the ROM, but that's my last option because I don't have a way to make a backup
Click to expand...
Click to collapse
if it allows you to get to recovery screen,did you try to go to any of the other options it gives you to see if it just reboots then as well, or is it just the recovery that reboots? And are you sure your batteries have charge,is your phone plugged in to a charger?
I tried with fastboot>reboot, recovery, and factory reset, all having the same result (reboot and then nothing). I'm not sure what are HBOOT USB and IMAGE CRC used for, and of course, I have not checked the SIMLOCK option.
Thanks for your replies.
Is it possible to make a backup from the recovery mode?
I don't think making a backup of what's going on would help any..but yeah if you can get into recovery you can backup.
Sent from my HTC Incredible S using xda premium
Bastian_n said:
I was using my Incredible S normally, when it suddenly faded to black and was totally freeze so I decided to restart it (Taking the battery out)
Then after reboot, It got stuck on white Htc logo (with "quietly brilliant animation playing again and again"). So restarted it again and tried to use the fast reboot option (restarting and holding the VOL DOWN button), but this also didn't work.
Some details: I Have Android Revolution (ROM) with S-OFF
Hope somebody help me!
Click to expand...
Click to collapse
I would suggest booting to the HBOOT menu and then connect your phone to the coputer you used when you ran Revolutionary to gain S-OFF.
Then select the FASTBOOT menu selection and see if you get into FASTBOOT USB mode. If you do, then I would try to reflash ClockworkMod recovery.
Thanks, I'm going to try that, but first I have to find the drivers.
Thanks Again, tell you later.
After got FASTBOOT USD, how should I continue to reflash ClockworkMod recovery?. Doing this, will I lose everything?
Edit:
I realized I can't reach recovery mode, so I can't reflash :s.
I'm not sure if you'll lose everything but use the command
fastboot flash recovery (name of image)
Make sure the recovery image is in the same folder as fastboot and adb
Sent from my HTC Incredible S using xda premium
Bastian_n said:
After got FASTBOOT USD, how should I continue to reflash ClockworkMod recovery?. Doing this, will I lose everything?
Click to expand...
Click to collapse
FallenSuisydal said:
I'm not sure if you'll lose everything but use the command
fastboot flash recovery (name of image)
Make sure the recovery image is in the same folder as fastboot and adb
Sent from my HTC Incredible S using xda premium
Click to expand...
Click to collapse
Flashing a custom recovery will not cause you to lose anything. Once you get recovery installed, any backups you made should then be available to restore.
But based on what you described happened to your phone, restoring a previous backup sounds like the best thing you could do.
Anyone please?
I have gone so far, I mean, I've tried to flash the recovery using fastboot usb but I got an error that said: FAILED (remote: now allowed). I also tried using Android Flasher, but I got an error too. It said: Your phone require ENG bootloader. after that I tried to flash another bootloader, but with no success :/.
I'm starting to get stressed, every different way I try, there's another problem...
EDIT : I'm sure I connected everything well. On screen said FASTBOOT USB, so I supose I got into this mode correctly
Bastian_n said:
Anyone please?
I have gone so far, I mean, I've tried to flash the recovery using fastboot usb but I got an error that said: FAILED (remote: now allowed). I also tried using Android Flasher, but I got an error too. It said: Your phone require ENG bootloader. after that I tried to flash another bootloader, but with no success :/.
I'm starting to get stressed, every different way I try, there's another problem...
EDIT : I'm sure I connected everything well. On screen said FASTBOOT USB, so I supose I got into this mode correctly
Click to expand...
Click to collapse
Looks like you need to resort to reloading a stock ROM. I would suggest you use the PG32IMG.zip method (copy an official RUU ROM.zip to your SD card and rename it PG32IMG.zip) and install it from HBOOT.
tpbklake said:
Looks like you need to resort to reloading a stock ROM. I would suggest you use the PG32IMG.zip method (copy an official RUU ROM.zip to your SD card and rename it PG32IMG.zip) and install it from HBOOT.
Click to expand...
Click to collapse
It didn't work :/, I got a RUU.exe then I extracted Rom.zip file and put into my SD as PG32IMG.zip. The phone readed the file without problems, but after "parsing" it rebooted and the same, some vibes, and got stuck again. also tried to extract the recovery file and just parse that one, but still the same.
I think is not a recovery problem, should I parse something else?
Have you Got the RUU specific to Your Device..????
or try making a Gold card and then flash the Downloaded RUU to avoid CID mismatch error...
---------- Post added at 06:41 AM ---------- Previous post was at 06:36 AM ----------
And have you by any chance removed the battery while the device was stuck on the white HTC screen..???
and one more imporatnt do you have your warranty..???
Hey guys,
So I've been at this all day on another forum. Here is the link to ONE of the threads : (Edit removed, cant post links yet)
So I was trying to Flash to Android Revolution HD and it got stuck at 30% half way through the installation. This lasted a good 5 hours...
I finally managed to reboot the phone using "adb reboot bootloader"
But now I'm stuck on "HTC Quietly Brilliant" splash screen!
I JUST bought this phone last night off kijjiji and I'm reallly ****ting bricks now (no pun intended)
Any help whatsoever will be really appreciated
Added a screen shot of what it was stuck at a few minutes ago. I JUST managed to reboot it..but it's still stuck.
PoRco1x said:
Hey guys,
So I've been at this all day on another forum. Here is the link to ONE of the threads : (Edit removed, cant post links yet)
So I was trying to Flash to Android Revolution HD and it got stuck at 30% half way through the installation. This lasted a good 5 hours...
I finally managed to reboot the phone using "adb reboot bootloader"
But now I'm stuck on "HTC Quietly Brilliant" splash screen!
I JUST bought this phone last night off kijjiji and I'm reallly ****ting bricks now (no pun intended)
Any help whatsoever will be really appreciated
Added a screen shot of what it was stuck at a few minutes ago. I JUST managed to reboot it..but it's still stuck.
Click to expand...
Click to collapse
Hi, hold it under a bright light and hold down power until it turns off, then reboot into bootloader, select recovery, then reflash the ROM
MacHackz said:
Hi, hold it under a bright light and hold down power until it turns off, then reboot into bootloader, select recovery, then reflash the ROM
Click to expand...
Click to collapse
Hey I got the phone to restart and it goes almost immediately into the HTC screen again. I think "fastboot" setting is on or something. I just can't get it to go to the bootloader
MacHackz said:
Hi, hold it under a bright light and hold down power until it turns off, then reboot into bootloader, select recovery, then reflash the ROM
Click to expand...
Click to collapse
Just tried it under my bright lamp too. No dice
Okay so I used Hansoons AIO toolkit to get it to load into CWM-based Recovery... phew
What's next!?
you need to do this when in fastboot
type fastboot erase cache
just to be sure redownload his rom
expertzero1 said:
you need to do this when in fastboot
type fastboot erase cache
just to be sure redownload his rom
Click to expand...
Click to collapse
Not really sure how to get into fastboot. Will typing that command get me to fastboot and erase cache.
Here are my options now, using the Hasoon2000 AIO
1) Re-flash a recovery - ClockWorkMod, ClockworkMod Touch, TWRP AND THEN Install zip via sd card
2) Do above ^^ but install via sideload
3) Just erase cache with AIO and install zip from sim card
What should I do?
PoRco1x said:
Not really sure how to get into fastboot. Will typing that command get me to fastboot and erase cache.
Here are my options now, using the Hasoon2000 AIO
1) Re-flash a recovery - ClockWorkMod, ClockworkMod Touch, TWRP AND THEN Install zip via sd card
2) Do above ^^ but install via sideload
3) Just erase cache with AIO and install zip from sim card
What should I do?
Click to expand...
Click to collapse
It doesn't matter, once you're in cwm recovery, reflash the Rom with a full wipe and you should be good. Calm down dude.
Sent from my HTC One using xda premium
just like the gentleman above said, you need to calm down first. If your phone can boot, although it hangs midway, it has a big chance not to be bricked in anyway.
And I don't advice you to use the AIO tools, just try to follow every simple guides to flash custom recovery-root-custom rom and you'll get familiar with the process in no time.
So I assume that you can boot into recovery, these are the steps that I think you should follow:
- re-download the custom rom that you wanna flash (make sure that the download is not corrupted)
- boot into recovery (in your case,CWM)
- wipe cache . wipe dalvik (in advance settings)
- install zip --> choose zip --> point to your custom rom
- you'll see the aroma installer, pick your options until it begins to install.
- if the installation went smoothly, don't reboot phone yet, get back to recovery, wipe cache/dalvik then reboot system and let the phone install the OS (first boot usually take long timer)
- if the installation hangs at midway, reboot again into recovery (power + vol down until button blinks and phone boots into bootloader) then start again from first step
once again, I advice you not to use the AIO tools. it's safe but you need to know what you are doing and the process to conquer your phone is not that hard.
What are you holding to try to enter bootloader? I use power and volume down and it works every time. Just hold them until the bootloader screen appears then let go.
Also, like others have said, it's better to use adb and fastboot commands yourself in cmd or terminal, rather than using the toolkit - it's not too hard, there are plenty of guides, you learn quicker and it's more satisfying
Sent from my HTC One using xda premium
ryryzz said:
just like the gentleman above said, you need to calm down first. If your phone can boot, although it hangs midway, it has a big chance not to be bricked in anyway.
And I don't advice you to use the AIO tools, just try to follow every simple guides to flash custom recovery-root-custom rom and you'll get familiar with the process in no time.
So I assume that you can boot into recovery, these are the steps that I think you should follow:
- re-download the custom rom that you wanna flash (make sure that the download is not corrupted)
- boot into recovery (in your case,CWM)
- wipe cache . wipe dalvik (in advance settings)
- install zip --> choose zip --> point to your custom rom
- you'll see the aroma installer, pick your options until it begins to install.
- if the installation went smoothly, don't reboot phone yet, get back to recovery, wipe cache/dalvik then reboot system and let the phone install the OS (first boot usually take long timer)
- if the installation hangs at midway, reboot again into recovery (power + vol down until button blinks and phone boots into bootloader) then start again from first step
once again, I advice you not to use the AIO tools. it's safe but you need to know what you are doing and the process to conquer your phone is not that hard.
Click to expand...
Click to collapse
I really appreciate your reply man. Yeah, I need to calm down haha.
Alright, the problem is that I can't get into recovery mode unless I use the AIO tool. I've tried everything else. Using the volume down button, under the bright light etc etc. IT just goes straight to the HTC screen. It must be noted that I DID have problems getting into my bootloader before as well. A moderator of another forum made me download an app from the app store that let me either reboot int bootloader or reboot into recovery.
Rebooting in bootloader didn't work through that app either, it just restarted the phone, However,rebooting into recovery worked. Also, AIO tools doesn't seem to allow me to reboot into bootloader either... that command just restarts the phone and gets it stuck on HTC screen.... BUT the "reboot into recovery" works here too
Problem 2 ) The device is being detected by my pc but I can't access the file system in it. It just showing as a drive with no GB in it whatsoever . when I use "adb devices" in cmd it shows my device along with the serial id though.
So, what's your situation at the moment? You can get into recovery? What are you trying to do?
redbull123 said:
So, what's your situation at the moment? You can get into recovery? What are you trying to do?
Click to expand...
Click to collapse
Well, I'm not sure what my course of action should be.
I'm in recovery mode right now. Got there using AIO.
The Android Revolution HD rom is STILL in there.
However, I'm wondering if I should put in a new rom using adb push (just watched a youtube video that says I can apparently do that)
Or should I REFLASH with new recovery and then install the rom?
What should be by next step? Because I dont want to be making mistakes
PoRco1x said:
I really appreciate your reply man. Yeah, I need to calm down haha.
Alright, the problem is that I can't get into recovery mode unless I use the AIO tool. I've tried everything else. Using the volume down button, under the bright light etc etc. IT just goes straight to the HTC screen. It must be noted that I DID have problems getting into my bootloader before as well. A moderator of another forum made me download an app from the app store that let me either reboot int bootloader or reboot into recovery.
Rebooting in bootloader didn't work through that app either, it just restarted the phone, However,rebooting into recovery worked. Also, AIO tools doesn't seem to allow me to reboot into bootloader either... that command just restarts the phone and gets it stuck on HTC screen.... BUT the "reboot into recovery" works here too
Problem 2 ) The device is being detected by my pc but I can't access the file system in it. It just showing as a drive with no GB in it whatsoever . when I use "adb devices" in cmd it shows my device along with the serial id though.
Click to expand...
Click to collapse
It is not bricked, you should hold down your vol down+power a tad bit longer, you should hold it until the screen comes on and not until when it's turned off. If the installation is stucked in recovery you should be able to go to bootloader.
You need to mount usb to your computer first. If you cannot find the option to mount it, you probably need to push files through adb in fastboot mode.
Sent from my HTC One using xda premium
PoRco1x said:
Well, I'm not sure what my course of action should be.
I'm in recovery mode right now. Got there using AIO.
The Android Revolution HD rom is STILL in there.
However, I'm wondering if I should put in a new rom using adb push (just watched a youtube video that says I can apparently do that)
Or should I REFLASH with new recovery and then install the rom?
What should be by next step? Because I dont want to be making mistakes
Click to expand...
Click to collapse
I would just try flashing the ROM again - it sticks at 30% all the time, it's a common problem with Aroma (the installer), nothing to do with anything you've done, nor the ROMs fault. It sometimes takes a few tries to get it properly. I'd recommend using the volume and power buttons to navigate around aroma instead of using the touchscreen...
Sent from my HTC One using xda premium
JazLiew said:
It is not bricked, you should hold down your vol down+power a tad bit longer, you should hold it until the screen comes on and not until when it's turned off. If the installation is stucked in recovery you should be able to go to bootloader.
You need to mount usb to your computer first. If you cannot find the option to mount it, you probably need to push files through adb in fastboot mode.
Sent from my HTC One using xda premium
Click to expand...
Click to collapse
Yeah, I tried that too. The phone was INITIALLY just stuck and wouldn't even restart. Nothing I did made it restart until finally... I used adb reboot bootloader to make the phone finally restart into the HTC screen. But no matter what I try to do, it hasn't taken me to the bootloader even ONCE, ever since I got the phone in fact.
Should I push in a new rom using adb? And if so, which one? Android Revolution HD (fresh download) or a different one that you recommend?
Btw, I apologise for the delayed replies, the forum is making me wait between each message since I'm new
PoRco1x said:
Well, I'm not sure what my course of action should be.
I'm in recovery mode right now. Got there using AIO.
The Android Revolution HD rom is STILL in there.
However, I'm wondering if I should put in a new rom using adb push (just watched a youtube video that says I can apparently do that)
Or should I REFLASH with new recovery and then install the rom?
What should be by next step? Because I dont want to be making mistakes
Click to expand...
Click to collapse
While in recovery, on your computer try boot into bootloader with "adb reboot bootloader" and see if your phone can boot into fastboot mode. If it can, I strongly recommend you to COMPLETELY go back to stock by flashing your RUU.exe. After going back to stock, do the whole process of unlock/root again
redbull123 said:
I would just try flashing the ROM again - it sticks at 30% all the time, it's a common problem with Aroma (the installer), nothing to do with anything you've done, nor the ROMs fault. It sometimes takes a few tries to get it properly. I'd recommend using the volume power buttons to navigate around aroma instead of using the touchscreen...
Sent from my HTC One using xda premium
Click to expand...
Click to collapse
It's funny you mention that! I had serious issues navigating through the aroma installer, I would have to click the "next" button at least 2-3 times. And when I tried using the volume buttons, it would only go to the button inbetween "back" and "next" which was something like "more info"
Does this point toward any other issue? Or should I go ahead with flashing rom again?
ryryzz said:
While in recovery, on your computer try boot into bootloader with "adb reboot bootloader" and see if your phone can boot into fastboot mode. If it can, I strongly recommend you to COMPLETELY go back to stock by flashing your RUU.exe. After going back to stock, do the whole process of unlock/root again
Click to expand...
Click to collapse
I used adb reboot bootloader to get OUT of the installtion screen, but it didnt take me to the bootloader (as usual) it just restarted. The AIO tools also didn't take me to bootloader when I used one of the commands there. So going to booatloader is really being impossible now!!
I think u need to send it to repair or warranty. Since you can't go to bootloader there's a lot of things you can't do right now.
So now I have two options at hand now...
1) Go ahead with rom installation (this I know how to do)
2) Flash official stock using RUU (this I dont know how to do yet, since I'm not entire sure what carrier this was initially on)
Hi all, this is a last ditched effort at maybe saving my phone. I did an update on my SU and for some unknown reason it rebooted my phone. It then loaded up my rom until the kernel settings loaded then rebooted once again. I then tried to go into recovery to flash a backup and it booted me straight into my unlocked fastboot. I then tried to reboot once again in hopes I could fast navigate into twrp through rom manager, once in I was prompted that I no longer had root. I then decided to start over from scratch and load a recovery in fastboot. Once I had everything good to go I plugged everything in and instead of recognizing my phone as a drive, HTC manager popped up instead. I then updated my drivers to see if maybe that would fix the problem with no luck. I am at a loss at this point. I would greatly appreciate any help you guys can offer.
grimzen said:
Hi all, this is a last ditched effort at maybe saving my phone. I did an update on my SU and for some unknown reason it rebooted my phone. It then loaded up my rom until the kernel settings loaded then rebooted once again. This is completely normal, you should have just rebooted the phone and been done I then tried to go into recovery to flash a backup and it booted me straight into my unlocked fastboot. Again totally normal, thats the bootloader use the vol to move down and choose recovery and hit power this will boot you to TWRP I then tried to reboot once again in hopes I could fast navigate into twrp through rom manager, once in I was prompted that I no longer had root. I then decided to start over from scratch and load a recovery in fastboot. Why ? Once I had everything good to go I plugged everything in and instead of recognizing my phone as a drive, HTC manager popped up instead. You should not have Sync installed only the drivers I then updated my drivers to see if maybe that would fix the problem with no luck. I am at a loss at this point. I would greatly appreciate any help you guys can offer.
Click to expand...
Click to collapse
Is the whole point of this just to install SuperSU ?
does your phone still boot up ? at one point you mention using rom manager ?
clsA said:
Is the whole point of this just to install SuperSU ?
does your phone still boot up ? at one point you mention using rom manager ?
Click to expand...
Click to collapse
I was doing a SU update. It restarted into a loop that boots about 1 min after the splash screen then resets. I've tried to redownload root through SU app as I can no longer connect through usb but it reboots to soon. I used Rom Manager to try and get into recovery as a second alternative.
grimzen said:
I was doing a SU update. It restarted into a loop that boots about 1 min after the splash screen then resets. I've tried to redownload root through SU app as I can no longer connect through usb but it reboots to soon. I used Rom Manager to try and get into recovery as a second alternative.
Click to expand...
Click to collapse
http://download.chainfire.eu/372/SuperSU/UPDATE-SuperSU-v1.86.zip
flash in recovery
use adb push UPDATE-SuperSU-v1.86.zip /data/media/0
to get the file on the phone
Reboot to bootloader / fastboot USB
and from command line on pc
fastboot erase cache
fastboot reboot
I cant understand why people using those ROm manager apps to install stuff. And you said it rebooted after you update your SU. Then i tink you pressed reboot into recovery instead of NORMAL. Am i wrong?
clsA said:
Is the whole point of this just to install SuperSU ?
does your phone still boot up ? at one point you mention using rom manager ?
Click to expand...
Click to collapse
bihslk said:
I cant understand why people using those ROm manager apps to install stuff. And you said it rebooted after you update your SU. Then i tink you pressed reboot into recovery instead of NORMAL. Am i wrong?
Click to expand...
Click to collapse
I no longer have a recovery to be able to flash anything. When I try to load into recovery it just boots right back into fastboot. I was just using rom manager to boot into recovery after I couldn't get into recovery through fastboot, not to flash anything. I was updating Super Su through the actual app itself. it seemed to be downloading something when it rebooted itself and I lost root, recovery and the ability to connect to my computer.
grimzen said:
I no longer have a recovery to be able to flash anything. When I try to load into recovery it just boots right back into fastboot. I was just using rom manager to boot into recovery after I couldn't get into recovery through fastboot, not to flash anything. I was updating Super Su through the actual app itself. it seemed to be downloading something when it rebooted itself and I lost root, recovery and the ability to connect to my computer.
Click to expand...
Click to collapse
I have updated SuperSU many times and never got any problem so there is something you did. Are you on custom or stock rom?
Are you s-off / unlocked bootloader?
bihslk said:
I have updated SuperSU many times and never got any problem so there is something you did. Are you on custom or stock rom?
Are you s-off / unlocked bootloader?
Click to expand...
Click to collapse
My bootloader is unlocked and i'm running Viperrom. I've never gone through the process of s-off but for some reason it says it at the top of my fastboot screen...not sure if that's normal or not.
grimzen said:
My bootloader is unlocked and i'm running Viperrom. I've never gone through the process of s-off but for some reason it says it at the top of my fastboot screen...not sure if that's normal or not.
Click to expand...
Click to collapse
Ok. I think you need to reflash recovery again.
Boot into bootloader and fastboot usb
then download TWRP recovery from here http://techerrata.com/browse/twrp2/m7 and pick 2.6.3.3-m7.img
put it into your fastboot folder and flash it "fastboot flash recovery openrecovery-twrp-2.6.3.3-m7.img and hit enter
now try to reboot into recovery. When there Wipe Dalvik and Cache and reboot. If recovery ask you to root your device then accept it and reboot.
Remember to connect phone to right USB port not 3.0. Use 2.0 port and try annother cable also.
bihslk said:
Ok. I think you need to reflash recovery again.
Boot into bootloader and fastboot usb
then download TWRP recovery from here http://techerrata.com/browse/twrp2/m7 and pick 2.6.3.3-m7.img
put it into your fastboot folder and flash it "fastboot flash recovery openrecovery-twrp-2.6.3.3-m7.img and hit enter
now try to reboot into recovery. When there Wipe Dalvik and Cache and reboot. If recovery ask you to root your device then accept it and reboot.
Remember to connect phone to right USB port not 3.0. Use 2.0 port and try annother cable also.
Click to expand...
Click to collapse
I've tried a few different cords and all 3 ports I have still nothing but the HTC manager thing. It will recognize it but only for a split second while booting up but it says HTC BUTTERFLY as the drive and i'm not sure if that's a problem or not but it won't recognize it at all through fastboot.
you cant boot up. if it doesnt recognize it in bootloader mode then i dont know.
Try restart PC. Maybe you have several adb at same time. Adn uninstall htc sync if not but keep drivers
bihslk said:
you cant boot up. if it doesnt recognize it in bootloader mode then i dont know.
Try restart PC. Maybe you have several adb at same time. Adn uninstall htc sync if not but keep drivers
Click to expand...
Click to collapse
Ok will try that now. thanks so much for the help.
I hadthe same problem after flashing a kernel. I repeatedly tried the bootloader (audiodown key + power button) until it started. Recovery was not available, in the red triangle screen press audio up key,got the system recovery screen, wipe cache, reboot the system and then try installing Twrp recovery. It worked.
Sent from my HTC One using xda app-developers app
jpaulpra said:
I hadthe same problem after flashing a kernel. I repeatedly tried the bootloader (audiodown key + power button) until it started. Recovery was not available, in the red triangle screen press audio up key,got the system recovery screen, wipe cache, reboot the system and then try installing Twrp recovery. It worked.
Sent from my HTC One using xda app-developers app
Click to expand...
Click to collapse
I'm not familiar with the red triangle screen is there a way to boot into it?
Grizmen what are you talking about. Why should you boot into red triangle? There is no menu called red triangle. Only on stock recovery.
Sent from my HTC One using Tapatalk
grimzen said:
I'm not familiar with the red triangle screen is there a way to boot into it?
Click to expand...
Click to collapse
bihslk said:
Grizmen what are you talking about. Why should you boot into red triangle? There is no menu called red triangle. Only on stock recovery.
Sent from my HTC One using Tapatalk
Click to expand...
Click to collapse
I think @jpaulpra was telling him to reflash stock recovery
then boot to it and do clear cache.. then reflash twrp
When I got into bootloader, I lost the Twrp recovery. So when I selected recovery I got the screen with a "triangle and exclamation mark". If you leave it will reboot the system after couple of minutes. But if the audio up key is pressed, it will show a system recovery screen, where cache can be wiped
Sent from my LT26i using Tapatalk
bihslk said:
Grizmen what are you talking about. Why should you boot into red triangle? There is no menu called red triangle. Only on stock recovery.
Sent from my HTC One using Tapatalk
Click to expand...
Click to collapse
Basically all I'm trying to do now it's find a way to get my computer to recognize my phone as a drive. When I go into viper settings and go to advance menu (with the short time I have before boot loop) there is an option to mount drive. When I select the option to do so it hands on splash screen and I have to hold power button to recycle back on. Once back in it's no longer selected. I've never seen a boot loop go pay the flash screen. Is this normal?
Pretty SOL with my son's Nabi2
I'm having a issue with my sons Nabi2 pretty similar. I messed up bigtime guys I rooted it and started messing aroung with the system files. Then didn't get a boot afterwards, wiped everything from twrps system, data, the whole shabang! Even lost my root! and access to on board flash cause I've been trying to recover using twrp with absolutley no luck. I still have the original stock unrooted backup saved to my pc from when I first installed twrp. Can someone please help me? I'm really out here trying to reach out for some help. didn't even know where to post this. Thank you guys. Note to moderators: If this is the wrong place to post this then please point me to the right direction and I apologize.
Hi, i'm really desperate...
I have a HTC One rooted and S-0FF with latest firmware
In the afternoon i tried no flash a new rom (android revoluton HD) and then it started to bootloop, i tried to get into recovery mode (cwm) and again it reboorts and gent in bootloop, i tried accesing the adb and nothing, my devices not shows when using command "adb devices"
I have Windows 8 64-bit and lastest htc drivers installed
Please Help
i don't think recovery would get into a bootloop so you must be holding the wrong buttons (should be power + vol down to get into the bootloader). from there select the recovery option and it should enter.
you might need to wipe the dalvik cache or reflash the rom.
So you have a bootloop and you can't enter fastboot. I know exactly what you're talking about, It has happened to me twice. I think all I did was keep trying to hold down the Volume Down and Power buttons and at some point it got into the bootloader. I don't know why it happens but if I can say anything, it's that android devices can be extremely weird. Just keep holding the buttons. It's not such a big deal, if your screen shows something (splash or boot animation) then you're far from very extreme issues.
If you have S-OFF, the world is your oyster! Look in a few guides/threads how to recover.
The reason you have a boot loop is because you need twrp recovery to flash android revolution
Sent from my HTC One using XDA Premium 4 mobile app
Find the solution
Yep! after the adb command "show devices" didn't work, i started to search in the forums and i see one about a command with something like "asb getvar" kind a thing. That command works and show my HTC one information that appear in top of the bootloader screen, then i flashed TWRP and send Android Revolution HD by sideload, then install and everything works again.
The only drwback is that my sd card got completely wiped
Thank you for your replies guys :good:
That's why I always have a backup of my ad card on my pc just in case
Glad you got it working though!
Sent from my HTC One using XDA Premium 4 mobile app