No Bootloader , Only HTC logo [urgent]
Hello ..
today i received OTA on my HTC one m8, downloaded it .. installed it then the system rebooted , but stucked in the second boot screen " HTC one m8 " and took forever so i turned it off , restarted and again stuck, i gone into the recovery and applied factory reset , still the same , then installed custom recovery (CWM) to wipe delvik cache cuz mine didnt have that option, still after wiping same ,in the end i applied clean wipe .. and now i cant get into bootloader ..
please help ..
notice that i saw a thread have kinda same issue and solved by pressing power + volume up to shutdown then press volume down but it didnt work for me ..
UPDATE : Problem solved, delete please.
adb , also wont work with me ..
hello,
can you please let me know how did you fix the issue - my phone stuck on boot after last ota update.
Thanks
Martin
Edit: TWRP restore saved my phone
BTW it would be good to know how to apply this bloody update. I've stock rom so no sure why it bricked my phone
m112 said:
hello,
can you please let me know how did you fix the issue - my phone stuck on boot after last ota update.
Thanks
Martin
Edit: TWRP restore saved my phone
BTW it would be good to know how to apply this bloody update. I've stock rom so no sure why it bricked my phone
Click to expand...
Click to collapse
I've tried running the update once again but it completely bricked my phone.
I cannot get to the hboot I'm getting black screen only
Edit found a fix buy pressing up for 10 sec and then down without releasing power
Any help would be appreciated
Related
Hello,
I have a great problem with my Motorola. I installed battery icon mod without reading for which phone it's made and used it. Now I can't use my phone, because it's stopping at this logo before system. I had Cyanogenmod 7 (last nightly before RC), but when I destroyed it by this application first thing I did was wipe. After it nothing has changed, so I tried again and I flashed it with normal 2.2 Nordic but - as I "predicted" - nothing has changed again, but this time system was stopping at Android logo, not Cyanogenmod logo. I tried to flash again - nothing. The device can be charged (there appears this battery).
What should I do?
zielonek430 said:
Hello,
I have a great problem with my Motorola. I installed battery icon mod without reading for which phone it's made and used it. Now I can't use my phone, because it's stopping at this logo before system. I had Cyanogenmod 7 (last nightly before RC), but when I destroyed it by this application first thing I did was wipe. After it nothing has changed, so I tried again and I flashed it with normal 2.2 Nordic but - as I "predicted" - nothing has changed again, but this time system was stopping at Android logo, not Cyanogenmod logo. I tried to flash again - nothing. The device can be charged (there appears this battery).
What should I do?
Click to expand...
Click to collapse
Go into the stock recovery and wipe data. Then re-flash the sbf.
I did it already, but I forgot, that I can do wipe after flashing the device I thought about it and did it - everything is working. Sorry for useless thread.
Regards.
I wanted to ask at the same time. What if i can't enter stock recovery. My phone's rooted , slightly overclocked , and i can't download any apps , i can't do factory reset , and even when i'm trying to enter it , the android pic would appear with that "danger - triangle". What should be done?
sLvW said:
I wanted to ask at the same time. What if i can't enter stock recovery. My phone's rooted , slightly overclocked , and i can't download any apps , i can't do factory reset , and even when i'm trying to enter it , the android pic would appear with that "danger - triangle". What should be done?
Click to expand...
Click to collapse
The triangle IS the stock recovery! when you see the triangle with the little android dude, hit both up and down volume at the same time. This will bring up a menu that will allow you to do a factory wipe.
And another question. I've installed custom recovery , and it said that install was succsesful , but when I apply recovery boot , it just reboots my phone , or lefts screen blacked out, at which case i have to turn on my phone by removing and applying battery.
sLvW said:
And another question. I've installed custom recovery , and it said that install was succsesful , but when I apply recovery boot , it just reboots my phone , or lefts screen blacked out, at which case i have to turn on my phone by removing and applying battery.
Click to expand...
Click to collapse
Not sure I understand the questions, but I'll take a stab at it anyway:
Since we have a locked bl, the custom recovery does not overwrite the stock recovery.
As far as I know, the only way to get in to custom recovery, is to push the vol down when the blue light goes on during the boot cycle.
sLvW said:
And another question. I've installed custom recovery , and it said that install was succsesful , but when I apply recovery boot , it just reboots my phone , or lefts screen blacked out, at which case i have to turn on my phone by removing and applying battery.
Click to expand...
Click to collapse
If it was a first reboot after installing Custom Recovery than USB Debbug should be off...
Hey all,
Couple days ago i got the official update for my HTC ONE X to Jelly Bean 4.1.1.
I was extremely happy and installed it asap and the install worked great with 100% success.
Sadly , After the 1st launch the phone worked for couple seconds and then stuck for 2 seconds and just reboot it self , then it launched again and rebooted again after couple seconds.
It looks like a boot loop with official rom , I must say that the phone get to the "Desktop" main screen with the clock , but cant stay "alive" more then couple seconds and resets over and over.
FYI - When i enter Boot screen it doesnt reset , and when i plug the phone to the charger - it doesnt reset at all (even in the phone main screen - apps and stuff).
I dont wanna send it to repair because it can take up to 3 weeks without it.
I even started to think about Custom ROM , but i really want to avoid that when there's 4.1.1 official rom out there.
Any solution?
I will really appriciate that.
thx alot.
Does it stay enough for you to do a Factory Reset? If so do it (Both from Bootloader and from Settings) then you should have your phone good as new
Do a factory reset in bootloader menu,maybe it helps.....your phone is 100% stock now ?
Enter the bootloader menu by pressing and holding the power button and volume - button until it reboots into bootloader menu
I did factory reset both on settings and on boot screen , The problem doesnt solved.
My phone is 100% stock yeah.
Then i suggest you take it in for warranty ! If you unlock the bootloader and start rooting and custom romming you will definitely void the 100% warranty that you still have now !!!
Is there any option to Re-install the 4.1.1 update? or Roll back to 4.0.4 without unlocking the device?
Atm its 100% stock lock im reminding.
Rolling back to 4.04 is impossible without unlocking the bootloader. Installing the update again.....can't really answer that question ....sorry mate
doctorslay said:
Is there any option to Re-install the 4.1.1 update?
Click to expand...
Click to collapse
You can install the ROM from scratch if the RUU is avaliable, check htcruu.com.
hi ,
i was root my device yesterday.
after that my phone starting normally then after 1-2 min restart
i dont know what info write down here .
pls help me ^^ (sorry for bad english)
When i update HTC lock screen , my device rebooting then stuck in boot loop
capsacin said:
hi ,
i was root my device yesterday.
after that my phone starting normally then after 1-2 min restart
i dont know what info write down here .
pls help me ^^ (sorry for bad english)
Click to expand...
Click to collapse
Did you flash the SuperSU app? Let's try to reflash it again then clear cache afterwards.
fastboot erase cache
my boot loop problem is not about rooting.
i found that when update HTC lock screen then reboot my phone stuck in boot loop !!??
how can i solve this problem
capsacin said:
my boot loop problem is not about rooting.
i found that when update HTC lock screen then reboot my phone stuck in boot loop !!??
how can i solve this problem
Click to expand...
Click to collapse
i was root my device yesterday.
after that my phone starting normally then after 1-2 min restart
Click to expand...
Click to collapse
Notice that what you're saying now and what you said when you opened this thread aren't exactly matching
Does it reboot every 1 to 2mins regardless of what you're doing? Why not then run a logcat and share the file so that we can see what error you get that forces a reboot.
That or,
Restore stock nandroid for your device.
Or
Remove latest update for HTC Lock screen and see if it solves the issue. You could always do the update again to try again.
Greetings All,
So I did a very stupid move and kinda soft bricked my M8. I received my Lollipop update, restored my stock recovery, applied the update, rebooted phone, applied TWRP and flashed SuperSU. Once I booted back into phone I saw that I still had Xposed installed and bundled and the idiot that I am, ran the uninstaller. Now the phone boots up and after showing the white boot logo sits at a black screen.I can get into recovery mode so I am pretty sure that if I download a Lollipop custom ROM I can get booting again? Factory reset did not help and I did not do a nandroid either :/. I am still S-ON so I can't flash the RUU file :/.
Any assistance will be greatly appreciated.
Problem resolved. Please ignore this thread .
Hello, Pretty detailed title
So here's what happened .. I rooted the device, installed Eclipse rom, faced some bugs so i decided to revert to the stock software, went to sammobile and downloaded the firmware for my country and followed the instructions ..
Downloaded odin, went into recovery and flashed the room .. after it was done .. the phone got stuck in a bootloop .. clicked on the power button but it kept going to the bootloop .. so i took of the battery and went into ( volume up + home + power ) and made a factory reset and then wiped cache .. rebooted the phone and the bootloop problem was fixed ..
Now i want to know what happened exactly that caused this ? i won't risk doing that again but i'm pretty curious what was the problem and why it was fixed ..