Hi all, hoping someone here knows whats going on! im so confused now haha.
i had the stock ROM that came with the HTC ONE X+ installed...
Followed the OTA popup Update that instructed me to update the firmware...
After this completed and restarted phone now wont boot past HTC screen.
Steps Tried So Far :
- I can get in to bootloader (pwr+vol dwn)
- I can get in to fastboot usb
- Phone has debugging off unfortunately (as it had stock rom on it; had no changes done whatsoever from factory settings)
- Pressing recovery does nothing does nothing to help
- Clearing Cache and Factory reset does nothing to help
- pressing bootloader does nothing
- Ive tried Fastboot flash recovery CWM.img
- Ive tried fastboot flash boot endeavorou.img (which i got from unzipping the CM file - however there was other folders that unzipped which wouldn't have been in the .img[?] so don't know if that was the best idea)
- Ive tried getting the identifier_token thing with Htcdev.com and unlocking it - which said it worked and flashed the file to the phone. However on HTC website it says it should have popped a screen up to ask and confirm some things which didn't occur)
No idea what to do now. .
Any ideas?
Thanks in advance!
Don't know if you can find one, but if you google a stock image of your phone and find one, you could fastboot flash it. Had to this before, but not on an HTC.
Sent from rooted carbon note 2, with the xda app.
My clocks I've built: http://forum.xda-developers.com/showthread.php?t=2404758
Were you rooted before you did the update? Since you should never use the OTA while rooted as far as I know
Thanks for the replies!
- It is a non-rooted phone; Everything before the OTA update was fully stock and how HTC had given it.
- I will give a go at flashing the stock ROM
Any other ideas?
Let me guess, UK Based? O2?
http://forum.xda-developers.com/showthread.php?t=2459808
The same issue after STOCK update. What the hell is going on?
Ghand0ur said:
Let me guess, UK Based? O2?
http://forum.xda-developers.com/showthread.php?t=2459808
The same issue after STOCK update. What the hell is going on?
Click to expand...
Click to collapse
Exactly this.... Does anyone know?!
sampollard said:
Exactly this.... Does anyone know?!
Click to expand...
Click to collapse
I think since you are on a contract you should go to O2 Customer service and report it and they should guide you through the steps to fix your issue. Since I don't see any issue with Other CIDs other than O2.
sampollard said:
Exactly this.... Does anyone know?!
Click to expand...
Click to collapse
Hi, I'm the poster from the other thread with the same issue.
Did you say you tried flashing an older stock image? Did you try flashing a custom rom image like cyanogen etc?
Just wondering if these are possible or not before I send for repair and have to wait weeks for it to come back.
Related
Ok, here's the deal:
Rooted the device, everything was a-ok.
Installed Clockwork, everything still a-ok.
Tried using mod manager to install Cyanogen nightly 9, phone rebooted and the progress bar for the mod install wouldn't move. I waited for a while and eventually manually turned the device off as it wasn't making any progress.
Ever since, it won't go past the screen you get at the beginning (w/ the yellow sign indicating an unsecured rom). It just stays there forever.
What I have to work with:
- Clockwork Recovery is available.
- The device is recognized by Odin when in download mode.
- The device is not recognized by the computer/Kies.
What I've tried:
- Followed the instruction for boot loop w/ both stock rom and Villain (no dice).
I'm sorta freaking out now. I have yet to see anyone having the same problem online and I really hope it's not bricked - a 600$ paperweight...
Is there something else I can try? Is it possible to flash stock PIT/Bootloader/PDA/everything else? If it is, would it fix the problem?
Please just point me in the right direction.
Thank You,
Edit: In recovery mode, the following error appears:
- Can't access to "/system/csc/VMC/system/"
Edit: In download mode, the current binary is set to "Samsung Official". Therefore I think this isn't the problem.
Edit: OMG OMG holy crap. Problem has been solved. Got a friend who had the same phone from the same provider to tell me what the firmware for the phone was. Downloaded it. Installed it w/ Odin. I almost turned religious when it booted a bit slower than what I remembered. It works well enough now, although I will probably go exchange it for a new one ASAP, before my warranty expires.
If anyone has similar problems. Don't panic and re-install stock firmware.
Cheers Folks!
Rovah said:
Ok, here's the deal:
Rooted the device, everything was a-ok.
Installed Clockwork, everything still a-ok.
Tried using mod manager to install Cyanogen nightly 9, phone rebooted and the progress bar for the mod install wouldn't move. I waited for a while and eventually manually turned the device off as it wasn't making any progress.
Ever since, it won't go past the screen you get at the beginning (w/ the yellow sign indicating an unsecured rom). It just stays there forever.
What I have to work with:
- Clockwork Recovery is available.
- The device is recognized by Odin when in download mode.
- The device is not recognized by the computer/Kies.
What I've tried:
- Followed the instruction for boot loop w/ both stock rom and Villain (no dice).
I'm sorta freaking out now. I have yet to see anyone having the same problem online and I really hope it's not bricked - a 600$ paperweight...
Is there something else I can try? Is it possible to flash stock PIT/Bootloader/PDA/everything else? If it is, would it fix the problem?
Please just point me in the right direction.
Thank You,
Edit: In recovery mode, the following error appears:
- Can't access to "/system/csc/VMC/system/"
Edit: In download mode, the current binary is set to "Samsung Official". Therefore I think this isn't the problem.
Edit: OMG OMG holy crap. Problem has been solved. Got a friend who had the same phone from the same provider to tell me what the firmware for the phone was. Downloaded it. Installed it w/ Odin. I almost turned religious when it booted a bit slower than what I remembered. It works well enough now, although I will probably go exchange it for a new one ASAP, before my warranty expires.
If anyone has similar problems. Don't panic and re-install stock firmware.
Cheers Folks!
Click to expand...
Click to collapse
Same problem. anyone?
Vincho said:
Same problem. anyone?
Click to expand...
Click to collapse
Did you read the answer ???
jje
Look online (samfirmware), ask friends or on forums for anyone who has the SGS2 w/ the same carrier in the same country and try to find the firmware version (I9100***** - the stars are letter codes). Then just download that firmware and use Odin to install it.
If you can't find it,you presumably could just flash any stock firmware and it might work (or it might make things worse, try at your own risk)
Rovah said:
Tried using mod manager to install Cyanogen nightly 9, phone rebooted and the progress bar for the mod install wouldn't move. I waited for a while and eventually manually turned the device off as it wasn't making any progress.
Click to expand...
Click to collapse
The progress bar not moving is a known issue with the CM7 Recovery. All you need to do is wait for it to say that it's finished. There is nothing wrong with your phone and no need to return it. You just cancelled the CM7 install part way through which meant not all required files were installed on the phone, causing it to not boot.
As for it taking longer to boot into android after the odin reflash. That's because it has to build up it's dalvik-cache again. This is completely normal any time you install a new rom. It only happens on first boot of a rom.
So again, no need to return your device and feel free to try CM7 again. Just remember to let it finish even if the progress bar isn't moving.
Ahh. Ok that makes sense. This ought to teach me to read before screwing around w/ my phone.
I wanted to exchange it because I wasnt sure i'd still be able to install official Samsung firmware updates through Kies.
Suppose an official 2.3.4 firmware comes out, would i be able to install it through Kies?
Sent from my GT-I9100 using XDA App
Rovah said:
Ahh. Ok that makes sense. This ought to teach me to read before screwing around w/ my phone.
I wanted to exchange it because I wasnt sure i'd still be able to install official Samsung firmware updates through Kies.
Suppose an official 2.3.4 firmware comes out, would i be able to install it through Kies?
Sent from my GT-I9100 using XDA App
Click to expand...
Click to collapse
Yes, as long as the firmware you're flashing is the same as the stock version that came on the phone. And even if not, you'll get the kies updates for whatever region firmware you did flash onto the phone.
I see. Thanks a lot!
Is there any danger to flashing firmware from a different region than the one youre from?
Sent from my GT-I9100 using XDA App
So I attempted to get my phone from Paranoid to back to stock but I completely messed up. I basically restored my phone to CM 10, then I tried to relock my phone from there. So I used this video:
youtube.com/watch?v=5yS7yy4XVA4
and now I have fastboot with no rom and no recovery (also everytime i reboot from fastboot, it goes straight back to it). If anyone could help, what should my next step be? it would greatly be appreciated.
If you locked the bootloader you will have to unlock it first, then flash recovery and a rom. Did you unlock manually or with regawmod?
om4 said:
If you locked the bootloader you will have to unlock it first, then flash recovery and a rom. Did you unlock manually or with regawmod?
Click to expand...
Click to collapse
I have noticed a lot of poeple have this same problem coming from cm10/aosp/aokp thier OS and recovery disappear
Some people are just wiping system by mistake
om4 said:
Some people are just wiping system by mistake
Click to expand...
Click to collapse
It happened to a friend of mine and now this is maybe the 10th time I have seen this
Yeah, I'll agree it's happening too often but all aosp ROMs are still in pretty early development despite working as well as they do
I actually got it back unlocked (manually) but to get back to sense, what would you suggest?
You still need to flash twrp if you haven't done so and for a bare stock rom there's stock with goodies and there is another one with out
PLEASE.
I have found lots of threads on this topic and nothing is working for me.
-I unlocked bootloader.
-Flashed Android revolution ROM
>WiFi stopped working..A device doesn't even show up to try and select just a blank menu (should be several routers showing)
-I have since tried using CyogenMod menu to do factory wipe/cache wipe then installed a new rom
- I have tried installing JmzStockATTOneDeodex, and RageOneV.1.1.0 after doing factory wipe/cache wipe
- I then found "RUU_Puccini_LTE_Rogers_WWE_1.26.631.4_Radio_1.05.550I.09v2_30.68.550I.12_release_219377_signed"
but this file doesnt seem to open at all it is a exe... and now .......I now am starting to lose my mind
PLEASEEEE HELP!
I am on Rogers LTE Network, HTC One, Canada.
I would really like to be able to flash the RageOne and have wifi work, PLEASE!!!!
millarrjm said:
please.
I have found lots of threads on this topic and nothing is working for me.
-i unlocked bootloader.
-flashed android revolution rom
>wifi stopped working..a device doesn't even show up to try and select just a blank menu (should be several routers showing)
-i have since tried using cyogenmod menu to do factory wipe/cache wipe then installed a new rom
- i have tried installing jmzstockattonedeodex, and rageonev.1.1.0 after doing factory wipe/cache wipe
- i then found "ruu_puccini_lte_rogers_wwe_1.26.631.4_radio_1.05.550i.09v2_30.68.550i.12_release_219377_signed"
but this file doesnt seem to open at all it is a exe... And now .......i now am starting to lose my mind
pleaseeee help!
I am on rogers lte network, htc one, canada.
I would really like to be able to flash the rageone and have wifi work, please!!!!
Click to expand...
Click to collapse
****. Now my ****ing internet wont work either **** me.
Please i need help asap!!! Someone pleaseeeeeeee
i cant believe i even tried this **** with my new device
i just want to go back to factory rogers setting for canada when my wifi and internet would work **** **** **** ****f uck :"(
Calm down. You found the solution yourself. That exe file is the ruu. Relock the bootloader put the phone in fast boot. Then run the program on your computer
gunnyman said:
Calm down. You found the solution yourself. That exe file is the ruu. Relock the bootloader put the phone in fast boot. Then run the program on your computer
Click to expand...
Click to collapse
So it didn't work..Also it said I have version 1.29.631.4 and this is 1.26.631.4 .. wouldn't I want the newer one? I never used a rom exe like this.. only flashed different rom zips from here.. the 3 available.
Also I am not posistive I MIGHT have used a "flash kernal" on one of the rom zips the android revolution one the very first time I installed it...
using "One_M7_All-In-One_Kit_v1.0" that is available here on at&t htc one part of forum. Then I kept reading and flashed it using recovery mode... and the rom worked well everything was fine except wifi... then today I flashed the others like I explained before trying to fix wifi and now the internet won't work as well. but the rest of the phone functions as it should and my carrier network works fine i can txt / call .
I follow your steps and it said this when I ran the exe..
ERROR[132]:SIGNATURE ERROR
The ROM Update Utility cannot update your android phone.
Please get the correct ROM update utility and try again.
--- Sorry this is kind of long, I just want to explain best for anyone reading this including yourself to understand what idiot things I did to bring myself to this conclusion, I am new to the community and a android noob
I have the same problem too,my HTC One wifi keep saying turning on and then error after root, i tried using the wifi tether app but its not working, any one can help please?
I've re-read your OP and you don't have the correct RUU for your device. You have an M7 not a Puccini, anyway like the At&T model a RUU for rogers doesn't exist yet.
As for fixing your wifi, your best hope is to restore your nandroid backup (I hope you made one) or find a Nandroid for your device. I know there's a thread over on the International forums with Nandroids in it, maybe find it there or make a request there.
Hi,
I'm a bit new here and running a good old-fashioned stock Inc 4G LTE, never rooted or flashed to new ROM. It DOES have the latest OTA update from Verizon a couple months ago.
This morning my phone suddenly went off after working OK. Then when trying to restart, I get an infinite boot loop and it won't get past the red Droid screen. I've searched various threads and tried what I think are the most obvious things, and nothing seems to help. But I want to make sure there are no other options before I throw it in the trash.
Here's what I tried:
- Tried entering Safe Mode by holding down volume key after HTC screen comes on. Makes no difference, does not enter Safe Mode.
- Get to HBOOT OK. Says 'LOCKED' and I am running HBOOT v.1.15.0000.
- - In HBOOT, I've tried running Recovery a couple times. Seems to go OK, but just starts looping when restarting.
- - In HBOOT, tried running Recovery > Wipe Cache Partition. Says cache is cleared.
- - In HBOOT, tried running Recovery > Wipe data/factory reset. Seem to go through OK.
- - In HBOOT, tried running Factory Reset.
- - In HBOOT, tried running Clear Storage.
- Pulled battery and tried spare.
- Removed SD card.
Some history - this phone has always been very sluggish. A few months ago started shutting down when doing camera intensive things (would jump to battery at critical level). So I did a factory reset a couple weeks ago and was slowly adding some of the essential apps back in. It crashed trying to upload photos to Facebook. Last night I had just moved some apps to the Phone storage and set my Sound Profile app to change profiles in the morning. This is about the time the phone crashed.
Anything else I should try before giving up?
Can I try to root and install a custom ROM to fix when in this state? Is this now possible with latest OTA update?
If custom ROM is last chance, is there a really solid one running 4.3 and Sense?
THANKS! May be time to get a HTC One or iPhoney, as I'm just not into huge phones that are coming out...
iRunNaked said:
If your on bootloader 1.15.0000 and now 1.16.0000, try using the stock Ruu and restoring the phone. If not, try rebooting in bootloader and factory reset.
If that doesn't work, gain root (if you haven't) and get s-off/unlock bootloader/CID set to 111111, and try a custom rom. If all else fails, take it back to stock and unroot/s-on/CID back to VZW/Relocked.
Call Verizon and tell them you need a replacement. The phone randomly gets real hot and reboots. They should send you a new one no problem.
I girlfriend had the random reboots, ending up getting it replaced. Now shes on her 4th or 5th incredible lte. (data Issues & random reboots)
Click to expand...
Click to collapse
I tried running a stock 2.17.. RUU, but got a "Failed" message because the software was too old. I'm guessing that is because I'm on the newer 2.19.. OTA update?!? Anyone know where to get a RUU file for the latest 2.19 version? I've been searching with no luck.
I'll have to research how to root/unlock the phone when it won't boot. Any specific threads that have fairly detailed instructions would be appreciated.
Thanks!
jethrodesign said:
I tried running a stock 2.17.. RUU, but got a "Failed" message because the software was too old. I'm guessing that is because I'm on the newer 2.19.. OTA update?!? Anyone know where to get a RUU file for the latest 2.19 version? I've been searching with no luck.
I'll have to research how to root/unlock the phone when it won't boot. Any specific threads that have fairly detailed instructions would be appreciated.
Thanks!
Click to expand...
Click to collapse
I looked at the thread about how to successfully root & flash the phone when it has the Verizon OTA update (2.19.xx) found here: http://forum.xda-developers.com/showthread.php?t=2664460.
But it appears at first glance that to do it the phone needs to be booted up and connected to the computer via USB. I can only get my phone to the HBOOT screen, nothing else.
- Can anyone confirm that to unlock and/or flash a new ROM on this phone that it has to be able to boot up? No way to do it on my phone with the 2.19 software and constant rebooting?
Thanks. It's cosmetically perfect, so I feel bad about throwing it away. If I can get it back up somehow I could at least sell it or give it to someone in need.
jethrodesign said:
I looked at the thread about how to successfully root & flash the phone when it has the Verizon OTA update (2.19.xx) found here: http://forum.xda-developers.com/showthread.php?t=2664460.
But it appears at first glance that to do it the phone needs to be booted up and connected to the computer via USB. I can only get my phone to the HBOOT screen, nothing else.
- Can anyone confirm that to unlock and/or flash a new ROM on this phone that it has to be able to boot up? No way to do it on my phone with the 2.19 software and constant rebooting?
Thanks. It's cosmetically perfect, so I feel bad about throwing it away. If I can get it back up somehow I could at least sell it or give it to someone in need.
Click to expand...
Click to collapse
If you want to use mdmower's "temp-root" trick, then you'll need to be able to access the device through Android Debug Bridge. Can you see the device if you type
Code:
adb devices
after booting up past the bootloader?
stringedonbass said:
If you want to use mdmower's "temp-root" trick, then you'll need to be able to access the device through Android Debug Bridge. Can you see the device if you type
Code:
adb devices
after booting up past the bootloader?
Click to expand...
Click to collapse
Hi. I've never tried running ADB. Not very familiar with it at all. But my phone will not boot past the HBOOT option. No matter what I've tried, it will just go into a rebooting loop. I'm assuming it needs to be fully booted up to work with ADB?!?
- Is there an RUU for the latest software update (2.19.xx) somewhere that I can try running to see if it will help it fully boot?
- Any other options?
Thanks!
jethrodesign said:
Hi. I've never tried running ADB. Not very familiar with it at all. But my phone will not boot past the HBOOT option. No matter what I've tried, it will just go into a rebooting loop. I'm assuming it needs to be fully booted up to work with ADB?!?
- Is there an RUU for the latest software update (2.19.xx) somewhere that I can try running to see if it will help it fully boot?
- Any other options?
Thanks!
Click to expand...
Click to collapse
Yes, my understanding is that to use adb, you need to be able to boot into the OS with usb debugging turned on. Hopefully someone will come along with a worthwhile response!
Is anyone aware of more current RUU's than are menteioned here?
http://forum.xda-developers.com/showthread.php?t=1770978
---------- Post added at 05:19 PM ---------- Previous post was at 05:07 PM ----------
If the phone failed as a completely stocked phone, why not try returning as opposed to figuring out how to root a broken phone?
So I got my new blloc zero18 today, and they advised me to update so I did.
The update failed and now my phone can't boot anymore...
It gets stuck on "fastboot mode...", I can enter the recovery menu so I tried wiping cache and doing a factory reset, but it didn't help.
I'm kinda out of options since I'm not very experienced and I don't know what to do.
Any help?
edit/ps: phone came with superuser already installed/active, when the phone is stuck and I turn it off it automatically turns itself on again, but it stays off when I power it off via the recovery room.
update: was looking on the starting guide of the blloc and I found out that, when clicked on the tab of the older version, in which it ships. It says that you shouldn't download android apks (these don't come with the phone). Which I did. Pretty stupid of me I guess, but my phone is still not working
(my account is too new so I can't post a link to the guide but it's on the official site but you change blloc.*** to wiki.blloc.***)
After upgrading to version 1.1.3, I have a dark gray screen and black letters. Using a phone is not possible. How to roll back the firmware?
It might seem dumb, but try to ask them if they could give you a rom which you could then flash on your existing phone via bootloader. Also as an added benefit, you could share the rom with us. Believe me, I've been waiting for some time to get my hands on that rom.
jesuskistus said:
It might seem dumb, but try to ask them if they could give you a rom which you could then flash on your existing phone via bootloader. Also as an added benefit, you could share the rom with us. Believe me, I've been waiting for some time to get my hands on that rom.
Click to expand...
Click to collapse
yes if it has superuser by default it means it is rooted already.. someone can dump the system files and can create a rom, so devs can work on porting for other brands...
even its launcher might be a great replacement to stock one... i liked the feed based monochromatic+minimalistic feel.. :fingers-crossed: