I just bought my phone last month and and when it was updating or installing, the green bar stops at only maybe 20 percent, and then stops with the red triangle sign appeared. and i have done this many times. i have tested it also on another htc one SV (my girlfriend's phone, we have the same phone) and the result is the same. please help me its freaking me out. hahaha
infos:
software update 2.14.401.2 (387.71MB)
4.1.2 HTC sense 4+
i still only got the htc sense 4
thanks a lot!
Is your bootloader unlocked? Do you have a custom recovery installed, like cwm or twrp?
now i got another problem. pfft. when i was going to open the Hboot or recovery to find out if it is unlock or not. it suddenly shut down and wont even turn on. i plugged it in a charger it wont charge there is no red led notification on top. it is still plugged in a charger up until now hoping it will turn on later. tsk. i still havent updated it now this...
i finally got my phone turn on, and i found out its bootloader is locked and not rooted
I've seen another couple of guys on a different forum have the same issue, they had to unlock their bootloader and flash 'custom' stock Rom then reflash the stock boot.img and stock recovery.img then relock the bootloader to be able to apply the update.
One of them just went ahead and S-Off(ed) via moonshine.io
I would try factory reset from bootloader menu first though.
I'm not really sure, why this can happen to a phone with locked bootloader. Because you can't change system files and the update should run through without any problems
I couldn't figure it out either, but both of the other users had locked bootloader also, untouched systems too.
i have these options, and im still thinking what would be the best.
* Unlock the bootloader and root it for better enhancements
* Wait for the 4.2.2/Sense 5 update if there will ever be.
* Or are there a way to manually update it on computer or flash it on a custom recovery?
Not sure if this has been resolved. This was my experience with a K2_CL. My phone died (battery life depleted) and I plugged it up as anyone else would had. However, my phone wouldn't turn back on. I unplugged the device and noticed the light signifying that it is charging was still on even though I had unplugged the device. This has happen to me a few times. The only solution I found was to take the battery out then place the battery back and it would be fine afterwards. As for the red triangle, this as well had happen to me a few times. However, I was already rooted and moonshine S-Off. When the 4.1.2 OTA enhancement update rolled out about a month ago or so I couldn't apply it due to that red triangle and it only going as far as 20% just like you. My solution? I reverted back to ICS. I won't explain how since russellvone has a tutorial on this already. Afterwards, moonshine was removed during the process but I retained S-Off and allowed the system to conduct a manual update for JB 4.1.2. Obviously at this point we can see it worked because I was back to JB again. Did another manual update and I applied the enhancement. My bootloader was locked during all of this. Once completed I used my code to unlock it again and voila.
I was freaking out myself when I had that problem.
Sent from my C525c using XDA Premium 4 mobile app
@Modding.MyMind
just so you know, since you're already s-off, you can apply OTA updates with out the need of relocking your bootloader.
this is my second OneSV from boost.
I bricked my first one by idiotically dreaming and thinking my CDMA phone would actually benefit from superCID.
lol soooooo wrong.
but anyways, back to the point. :thumbup:
the first OneSV I moonshined on jellybean firmware,
the second OneSV I moonshined on icecreamsandwich firmware.
then for the life of me, I couldn't figure out how to accept the jellybean OTA update. then I figured it out and made my thread.
but again, back to the point. lol
I've accepted ALL the OTA updates with out locking my bootloader.
just another time saving tip.
all thanks to the moonshine.io team!
Much appreciated to you sharing with me this knowledge. I figured it would be safe to not have to relock the bootloader again, but I had been playing it safe as to not hard brick the device. As for supercid, I once considered it but luckily I did a thorough research before proceeding and quickly learn it was pointless lol. Sorry you had to learn the hard way, but experience IS experience none the less .
Sent from my C525c using XDA Premium 4 mobile app
Related
Okay first off, i know this is the wrong section. I can not post in development because I am new here, but I am in need of help desperately. Okay so I am rooted on 1.85 and the bootloader is NOT unlocked. Well i decided today to take the update to 4.0.4 before I did research. (Stupid me eh?) Well I start the OTA and then do some research. I learn that the update to 4.0.4 might be harmful to rooted users. So I disconnect from WiFi knowing it will pause the download. Well now I have a download that is just paused in the notification bar, and any time i connect to wifi it will continue the download. While the download is paused, can i unroot and take the update safely? I have seriously been searching for hours on end to find someone with a situation that I am in and i can not.
If you do a factory reset the update will go away. But that would also make you loose root. You should unlock the bootloader, then flash the rooted 2.20 update from the dev section.
Sent from my HTC One XL using xda app-developers app
Yep, get that bootloader unlocked immediately and flash a rooted stock ROM or a custom ROM. Make sure you backup all your stuff with Titanium because the bootloader unlock will wipe your phone.
Also, just so you know, this thread most definitely did NOT belong in development, which is reserved for ROMs and kernels and root guides and the like ONLY. Threads like this belong in Q+A but nobody is gonna kill you for posting it in General.
After the download, you should get a prompt to either Install, Postpone, or you can press the "back" capacitive button to cancel. Cancel should stop the update notifications. At least this is how its worked on past HTC OTAs. I personally can't verify, as I haven't gotten the notification yet. But others seem to verify this: http://forum.xda-developers.com/showthread.php?t=1817429
But if you want to be safe, you should SuperCID and unlock bootloader first, as others have suggested. Pressing the wrong button for the method I suggested above will be catastrophic otherwise (lose the ability to root and unlock BL).
Thanks for your help guys!
I just did a factory data reset on my phone. Honestly, I've gotten myself into trouble with rooting. I really need to read up before i continue with things of this sort. So since i did a factory data reset, am i 100% unrooted? Will i be safe to take the OTA now? Thanks for your help guys!
If you were stock 1.85, and rooted using the one-click or "manual" method (which you must be, if you you are still BL locked), then you are now unrooted. You are either rooted or not, there is no "percentage" of rooted.
What kind of trouble have you gotten into rooting, and what do you typically use root for?
I've been debating on whether or not to just go ahead and install the OTA to 2.2. The only thing I've used for root was for WiFi-Tether and I don't even use that anymore so I think I don't even necessarily NEED root anymore. I'm just tired of the updater telling me there's a new update to install - frankly very annoying. I've been just using the back capacitive button to cancel it. BUT, the last time I did this when 1.73 went to 1.85, I was just stock rooted, no unlocked BL (just like I am now), when I tried to install the OTA, went to that error with the triangle and exclamation point and wouldn't let me install it. I had to reflash to stock RUU because it was giving me a bootloop. I just don't want that to happen again... What does that triangle and exclamation point even really mean? I can't find a definitive answer on it. Shouldn't the OTA just install as normal, but it'll remove root in the process?
extol1337 said:
BUT, the last time I did this when 1.73 went to 1.85, I was just stock rooted, no unlocked BL (just like I am now), when I tried to install the OTA, went to that error with the triangle and exclamation point and wouldn't let me install it. I had to reflash to stock RUU because it was giving me a bootloop. I just don't want that to happen again... What does that triangle and exclamation point even really mean? I can't find a definitive answer on it. Shouldn't the OTA just install as normal, but it'll remove root in the process?
Click to expand...
Click to collapse
Red triangle and exclamation point is the stock recovery. This appears if something about the ROM is missing or corrupted. Not sure why this happened to you in that particular case. But installing OTAs on rooted phones is always a crap shoot. Sometimes it works, and you just lose root. Sometimes you boot loop or other things.
redpoint73 said:
Red triangle and exclamation point is the stock recovery. This appears if something about the ROM is missing or corrupted. Not sure why this happened to you in that particular case. But installing OTAs on rooted phones is always a crap shoot. Sometimes it works, and you just lose root. Sometimes you boot loop or other things.
Click to expand...
Click to collapse
That's what I was afraid of. Actually, I remember trying to install the 2.2 OTA a few days ago as well. Same red triangle and exclamation point. This time wasn't a boot loop and I just rebooted again and ever since, just kept canceling the update. Not sure what's going on...
extol1337 said:
That's what I was afraid of. Actually, I remember trying to install the 2.2 OTA a few days ago as well. Same red triangle and exclamation point. This time wasn't a boot loop and I just rebooted again and ever since, just kept canceling the update. Not sure what's going on...
Click to expand...
Click to collapse
Is the update actually downloaded to your phone? You may need to locate and delete it.
It may be trying to install the OTA from recovery, which makes sense. Don't actually know what happens when an OTA installs.
I've never installed an OTA! I'm always rooted, always will be!!!!
Just to be sure.
I did a factory data reset the night of the problem, been good ever since! I have not done anything to the phone except install a few apps. Should i be okay to take the OTA now? Sorry i just really want to be sure. This is my 3rd phone is 3 months so... no second chances.
SOLVED
Okay, so i took a chance on the update. It worked! I will not be rooting anymore until i read up. Sorry guys if you feel this thread was unnecessary. Just an FYI to any who are worried about taking the newest update after a factory data reset, don't be! Thank you to all:highfive:
Did everyone got an update ?
I still do not see update notification
From beast called HTC One X
It's a little late for this probably but for future reference if you are rooted and want to stop receiving OTA updates remove/rename/delete HtcOMADM_ATT.apk and HtcOMADM_ATT.odex from system/apps, wipe cache and dalvik. If you want to remove "AT&T software update" from the "Settings" then remove HtcOMADM_SettingsPlugin_ATT.apk and HtcOMADM_SettingsPlugin_ATT.odex from system/apps, wipe cache and dalvik.
wantabe said:
It's a little late for this probably but for future reference if you are rooted and want to stop receiving OTA updates remove/rename/delete HtcOMADM_ATT.apk and HtcOMADM_ATT.odex from system/apps, wipe cache and dalvik. If you want to remove "AT&T software update" from the "Settings" then remove HtcOMADM_SettingsPlugin_ATT.apk and HtcOMADM_SettingsPlugin_ATT.odex from system/apps, wipe cache and dalvik.
Click to expand...
Click to collapse
Excellent info!
ssteven232 said:
Okay, so i took a chance on the update. It worked! I will not be rooting anymore until i read up. Sorry guys if you feel this thread was unnecessary. Just an FYI to any who are worried about taking the newest update after a factory data reset, don't be! Thank you to all:highfive:
Click to expand...
Click to collapse
Looks like you will not be rooting anymore for a while now, since there is no method to root the 2.2 update. AT&T / HTC made sure the current rooting method won't work on it. Hopefully, the devs will eventually crack this one too.
I hope you knew that before making the dive ... I would have just unlocked the bootloader and flashed a ROM with the update baked into it to get the best of both worlds. But that's just me. I can't own an android without root access. To reach his own.
Sent from my HTC One X using xda app-developers app
borets.boris said:
Looks like you will not be rooting anymore for a while now, since there is no method to root the 2.2 update. AT&T / HTC made sure the current rooting method won't work on it. Hopefully, the devs will eventually crack this one too.
I hope you knew that before making the dive ... I would have just unlocked the bootloader and flashed a ROM with the update baked into it to get the best of both worlds. But that's just me. I can't own an android without root access. To reach his own.
Sent from my HTC One X using xda app-developers app
Click to expand...
Click to collapse
Yeah, I hear what you're saying and you are right. The current rooting method does not work with the new hboot. But.... If you have your bootloader unlocked beforehand you can still still get root after taking the OTA... And you can still flash a custom rom afterwards, from what I understand you would just need to fastboot flash the boot.img. I haven't personally tried it because I like staying fairly stock, just seriously cleaned up with some mods (init.d support, wifi/usb tethering, missing apps replaced). One thing I am curious about and to be honest I haven't spent any time researching the answer, what kernel are the roms using that are based on the 2.23 (4.0.4) Asian RUU? I wonder because I know the combination of the AT&T 2.20 (4.0.4) update with the new kernel and radio is working very, very well on my phone! My quadrant went up 800 points and battery life is still ridiculously good! I also have to agree with "I can't own an android without root access" especially on AT&T. Personally I'm good to go until the Jelly Bean update! Decisions, decisions! :laugh:
wantabe said:
Yeah, I hear what you're saying and you are right. The current rooting method does not work with the new hboot. But.... If you have your bootloader unlocked beforehand you can still still get root after taking the OTA... And you can still flash a custom rom afterwards, from what I understand you would just need to fastboot flash the boot.img. I haven't personally tried it because I like staying fairly stock, just seriously cleaned up with some mods (init.d support, wifi/usb tethering, missing apps replaced).
Click to expand...
Click to collapse
I've never installed an OTA, so I wouldn't know either. Honestly, I don't know why one would do that, when the awesome devs here post ROMs with the latest OTAs and root prebaked into them. There are "modded" ROMs and "stock" (or close to stock) ROMs available to everyone's taste.
wantabe said:
One thing I am curious about and to be honest I haven't spent any time researching the answer, what kernel are the roms using that are based on the 2.23 (4.0.4) Asian RUU? I wonder because I know the combination of the AT&T 2.20 (4.0.4) update with the new kernel and radio is working very, very well on my phone!
Click to expand...
Click to collapse
Right now, I'm running CleanROM 4.5, which is based on the 2.23 RUU. I did install the 2.20 radio, thinking it would work better, since I'm on AT&T. I took a screenshot of the kernel screen for you.
wantabe said:
My quadrant went up 800 points and battery life is still ridiculously good!
Click to expand...
Click to collapse
Where was your improvement? Did the increase happen in the aspect/area that directly affects your daily use, or in some esoteric algorithm that the phone all of a sudden processes faster? I used to go crazy on quadrant scores, but now I don't really understand their value/accuracy. As long as the phone feels buttery smooth while lasting 5+ hours of screen time, I'm happy!
Since you're interested in the scores, I installed quadrant and ran it, so you can compare.
Sent from my HTC One X using xda app-developers app
in admiration, totally confused!
borets.boris said:
Right now, I'm running CleanROM 4.5, which is based on the 2.23 RUU. I did install the 2.20 radio, thinking it would work better, since I'm on AT&T. I took a screenshot of the kernel screen for you.
Click to expand...
Click to collapse
Hi, do you think you could point me in the right direction for this? I found the general thread on radios, but am at a total loss about what it means or what to do with it!
You knew this was the wrong section but posted here anyway? Not a good way to start your membership on XDA. First rule of thumb is to search before creating a thread. Google is a great source for information. For future reference, all questions belong in the Q&A section, where coincidentally, this is being moved to.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
"If you choose not to decide, you still have made a choice"
Sent from my HTC One X, using XDA Premium.
Hey
I just got a huge bootloop while attempting to flash new Venom Room to my HTC One X. http://forum.xda-developers.com/showthread.php?t=1868236
I cannot access the recovery.. After restart (power button+volume down) i can get to bootloader section, but when i try to get into recovery, the phone just restart and stop on the white htc screen.
I already tried to reinstall recovery. Installation was successful, but the problem persists..
Before i had Incert Coins room.
The phone is unlocked, new recovery is installed
Please, help
If you had Insert Coin working on your phone, you have an international (Tegra3) version of the One X. This forum (and the Venom ROM you linked) are for the Snapdragon S3 version. Completely different hardware.
If I'm correct, you flashed a ROM for the wrong phone. Try running the RUU for your phone, but if that doesn't work you may be screwed. Recovery partitions are not the same for the versions. The ROM overwrote the recovery partition of your phone.
You are right.. It WAS the wrong rom.. I have tegra3 processor and this rom comes from american section..
But - is the RUU reinstall only one thing what i can do? I heard its dangerous
Senbration said:
But - is the RUU reinstall only one thing what i can do? I heard its dangerous
Click to expand...
Click to collapse
RUU just returns your phone to the stock condition. Stock ROM and stock recovery. There should be nothing dangerous about it. Just use the right one for your version, carrier, etc. But the CID check should ensure that you don't run the wrong RUU (if RUU is for a different CID, the RUU will not run).
Only thing with RUU, is that it wipes all user data. That may be why you heard its "dangerous". But in the condition you are in, this is not even a consideration anymore.
RUU is not dangerous, and it may be your only hope at this point.
You will need to lock your bootloader before running the RUU.
I've relocked bootloop. But now there is an information "RELOADED, Security Warning"
Will be safe to flash stock RUU now?
Senbration said:
I've relocked bootloop. But now there is an information "RELOADED, Security Warning"
Will be safe to flash stock RUU now?
Click to expand...
Click to collapse
I'm assuming you meant relocked bootloader and now has security warning relocked if this what you meant then you are fine flash the ruu
Sent from my Nocturnalized One XL using Forum Runner
Senbration said:
I've relocked bootloop. But now there is an information "RELOADED, Security Warning"
Will be safe to flash stock RUU now?
Click to expand...
Click to collapse
You mean relocked and not reloaded? If so, you should be good to run the RUU. Redpoint, sorry for highjacking your help session
Sent from my One X using xda premium
ohh, its Relocked.. Im just a bit nervous right now hoping it will unbrick this phone..
Just 3min to complete RUU download.
Do U guys think this stock RUU will rewrite the partitions back?
I've noticed another problem.
Cannot load RUU because the battery level is lower then 30%.
But when i plug the charger the light doesnt flash. It starts to flash when i switch on the phone.
Also cannot switch the phone with the power button. It restart all the time. Only can do that from bootloader command "power down". But when the phone is off the power light doesnt flash..
Does it mean that the battery is not charging at all? Because the light can flash only because the power is low..
The phone shut down completly now.. Does not charge the battery at all.. Power gone off and i cannot even turn on the phone..
Is there any solution how to make it charge?
Ok, the problem is that the wrong ROM i tried to install changed partition and also it seems it destroyed Recovery..
Without recovery the phone cannot charge while being in bootloader mode...
Is there any way to make phone charging when Recovery doesnt work and cannot be flashed?
Please help
Take the phone apart. I mean all the way spart and hardwire a charger to the phone/ battery. Its a pain but you can do it.
Ohh..
I found a treat http://forum.xda-developers.com/showthread.php?t=1658084
There is a way to charge battery by running the script, which makes phone reinstalling constantly. Each time it is reinstalled, the battery is charged a little bit more.
After mayby 40min i went up from 3686 V to 3720 V.
It seems that my only hope is to reinstall RUU. I tried to flash wrong ROM, from wrong model and as one user wrote above, it has rewritten my partition. Same time it destroyed recovery.. I cannot flash recovery now because the partition is rewritten...
And without working recovery i cannot charge the battery being in bootloader.. If i understand it all correctly.
I already tried to install RUU with 3710 V. It started to install, but stopped after few min with information that battery is too low..
So i think ill leave this script running for a whole night, and hope, in the morning battery will be charged just enough to install RUU eventually..
Uff
Okey, finally its fixed..
After 7 hours of constant reinstalling the phone by the script, the battery was loaded enough to finish RUU instalation process.. (battery went to about 3830mV power)
After oryginal RUU was installed, everything went fine.
Now i already re-unlocked the bootloader, re-rooted the phone and all works correctly.
Thanks all people who helped. Mostly to redpoint73, who diagnosed the problem straight away and put me on the right track.
Amazingly impressive to me.
Thanks for following up with your success.
WR
Sent from a CleanRom-V OneX
THAT is AWESOME
Senbration said:
Thanks all people who helped. Mostly to redpoint73, who diagnosed the problem straight away and put me on the right track.
Click to expand...
Click to collapse
Your welcome, and no problem really. It was an easy problem to recognize, as I've seen it several times before on here.
Nice job getting the phone charged. Haven't seen that solution before.
Thanks people for not calling me a noob and not blaming for installing the wrong ROM. Even though it was a silly mistake..
Sent from my HTC One X using Tapatalk 2
Senbration said:
Thanks people for not calling me a noob and not blaming for installing the wrong ROM. Even though it was a silly mistake..
Click to expand...
Click to collapse
Sh1T! Did I forget to do that???? I must have been in a good mood . . .
Heh it must have been so
Sent from my HTC One X using Tapatalk 2
So I just got my phone back working properly by flashing a Ruu for a previous problem. I was notified of the Jellybean update and proceeded to download it.. Everything was going fine when it came down to installation, but all of a sudden the phone went black and will not turn back on. It had a full charge on it,so Idk whats the problem.. Any suggestions ???
Let me guess: You were rooted and had superCID?
Sent from my Nexus 7 using Tapatalk HD
Should have read this first:
http://forum.xda-developers.com/showthread.php?t=2181929
Sent from my One X using Tapatalk 2
No, I don't have neither..
iElvis said:
Let me guess: You were rooted and had superCID?
Sent from my Nexus 7 using Tapatalk HD
Click to expand...
Click to collapse
the whole process took awhile for me, felt like it rebooted a few times also. about 20 minutes i think, you could of got in a hurry during the process and messed it up. does the phone detect? maybe u can reruu?
Have you tried holding the power button down for a while (like 30 secs)? You can't get into bootloader via power+vol down? What happens when you plug into your computer? What do you see in Device Manager?
Bricks on stock phones from borked otas are not common, but they do happen. If so, AT&T is good about replacements.
If the charge LED does not come on when charging (use the wall charger, not USB), and the screen doesn't come on at all after charging overnight, the phone is probably not recoverable.
As iElvis mentioned, bricks caused be the OTA aren't common, but they do happen. For one thing, the OTA flashes a new hboot. So if something goes wrong during that process, it may brick the phone. If you are bone stock, its the fault of the update, so AT&T will replace it.
The LED does not come on, believe me I have tried keeping it on the charger all night, with no success.
redpoint73 said:
If the charge LED does not come on when charging (use the wall charger, not USB), and the screen doesn't come on at all after charging overnight, the phone is probably not recoverable.
As iElvis mentioned, bricks caused be the OTA aren't common, but they do happen. For one thing, the OTA flashes a new hboot. So if something goes wrong during that process, it may brick the phone. If you are bone stock, its the fault of the update, so AT&T will replace it.
Click to expand...
Click to collapse
I tried this, and nothing happened.. I will head to my nearest AT&T store soon to get a replacement hopefully.. I guess its not all bad though, I have been enjoying my Lumia 920 with Windows phone 8, but I am missing my Android!
iElvis said:
Have you tried holding the power button down for a while (like 30 secs)? You can't get into bootloader via power+vol down? What happens when you plug into your computer? What do you see in Device Manager?
Bricks on stock phones from borked otas are not common, but they do happen. If so, AT&T is good about replacements.
Click to expand...
Click to collapse
hrrsncrawford14 said:
So I just got my phone back working properly by flashing a Ruu for a previous problem. I was notified of the Jellybean update and proceeded to download it.. Everything was going fine when it came down to installation, but all of a sudden the phone went black and will not turn back on. It had a full charge on it,so Idk whats the problem.. Any suggestions ???
Click to expand...
Click to collapse
I am having the same problem, just updated using 3.18 ruu and the phone went blank it detects as Qhsusb_dload and the ruu doesn't detect anymore
nmupparaju said:
I am having the same problem, just updated using 3.18 ruu and the phone went blank it detects as Qhsusb_dload and the ruu doesn't detect anymore
Click to expand...
Click to collapse
Did you have SuperCID? S-on?
The OP is talking about updating via OTA, which is known to brick your phone if you have SuperCID and S-on. But I was wondering what would happen with the RUU, which was just posted by HTC a couple days ago.
redpoint73 said:
Did you have SuperCID? S-on?
The OP is talking about updating via OTA, which is known to brick your phone if you have SuperCID and S-on. But I was wondering what would happen with the RUU, which was just posted by HTC a couple days ago.
Click to expand...
Click to collapse
I'm sure it's the same thing.
redpoint73 said:
Did you have SuperCID? S-on?
The OP is talking about updating via OTA, which is known to brick your phone if you have SuperCID and S-on. But I was wondering what would happen with the RUU, which was just posted by HTC a couple days ago.
Click to expand...
Click to collapse
I did get supercid, unlocked bootloader installed cm10 relocked bootloader, ruu to 2.20 used for few days, used update tool from htc website to update to jellybean, after using the tool phone never booted back , dead (I guess brick)
When connected to windows pc qhusb_dload shows up
nmupparaju said:
When connected to windows pc qhusb_dload shows up
Click to expand...
Click to collapse
You've got a brick. Sorry. It's not clear why this is happening, but once you're in that mode, you're done.
Starting with where I am now: my ATT One X is totally unresponsive. Power button held, Power plus either of the volume buttons held, nothing produces any response. When I plug it into a wall adapter, the charging LED doesn't light up. It is both looking and talking like a brick.
Here's how I got here, and I'm hoping someone may have some kind of suggestion .
I had been running Tachi91's original Sense JB ROM. TWRP recovery. I used the AT&T JB update RUU from HTC's site.
Before doing this, I rebooted to bootloader and re-locked the bootloader. After this, I seemed to be unable to reboot back into system, so I just ran the RUU while the phone was sitting in the bootloader (figuring that the first thing the RUU seems to have done in the past is reboot to the bootloader).
The RUU went through its usual lengthy, multi-reboot thing. No errors whatsoever, everything seemed totally fine. Clicked "Finish" at the end...and my phone's screen went black. I figured it was rebooting, but unless it's taken the past 40 minutes to reboot (which seems unlikely! ), something is obviously amiss. See beginning of post for what I've tried since and results.
Any suggestions?
http://forum.xda-developers.com/showthread.php?p=38909732
[Public Service Announcement] Read before installing the AT&T Jellybean OTA or RUU
I fear the worst.
Sent from my HOX w/CM10.1 4.2.2 s-off
subarudroid said:
http://forum.xda-developers.com/showthread.php?p=38909732
[Public Service Announcement] Read before installing the AT&T Jellybean OTA or RUU
I fear the worst.
Sent from my HOX w/CM10.1 4.2.2 s-off
Click to expand...
Click to collapse
...yeeeeah, total violation of item #1 on that list. And here I figured I was relatively safe with an RUU. Oops.
Thanks for pointing that post out to me. At least I know where I stand now! Better than sitting here making my thumbs go numb trying different power/volume combinations.
Why oh why do many people persist in thinking they don't need s-off??
Sent from my Nexus 7 using Tapatalk HD
Please help!
Hey, does any one know if there is any solution i can do myself? or do i have to send it to a jtag repair, because i just received it a month ago from a earlier brick. I just can not believe i bricked it again doing a RUU update. Thank you
buy a jtag
Nicobesso said:
Hey, does any one know if there is any solution i can do myself? or do i have to send it to a jtag repair, because i just received it a month ago from a earlier brick. I just can not believe i bricked it again doing a RUU update. Thank you
Click to expand...
Click to collapse
Could try the JET. Check the Development forum.
Ok, yesterday morning my MAXX received the KitKat update. Brainlessly, I clicked upgrade. This put me into the oh so famous bootloop.
During one of the boot loops, I managed to unroot with Voodoo.
Then in fastboot, I had the brilliant (aka, incredibly stupid) idea of flashing an old recovery. I had thought it was the one from 4.2.2 but sadly, it was from the previous version.
This had the appearance of working as it then booted to KitKat upgrade, which after a couple minutes failed.
Now I'm completely stuck in fastboot mode. I can't flash the 4.2.2 recovery. I haven't tried anything else. FXZ back to 12.15.15 doesn't work. Gives the GPT failure.
So...my belief, based only on googling around, is that I need to wait for the FXZ for KitKat. Does that sound right?
Any other ideas?
Thank you in advance!!!!!!!!!!
killboredom said:
Ok, yesterday morning my MAXX received the KitKat update. Brainlessly, I clicked upgrade. This put me into the oh so famous bootloop.
During one of the boot loops, I managed to unroot with Voodoo.
Then in fastboot, I had the brilliant (aka, incredibly stupid) idea of flashing an old recovery. I had thought it was the one from 4.2.2 but sadly, it was from the previous version.
This had the appearance of working as it then booted to KitKat upgrade, which after a couple minutes failed.
Now I'm completely stuck in fastboot mode. I can't flash the 4.2.2 recovery. I haven't tried anything else. FXZ back to 12.15.15 doesn't work. Gives the GPT failure.
So...my belief, based only on googling around, is that I need to wait for the FXZ for KitKat. Does that sound right?
Any other ideas?
Thank you in advance!!!!!!!!!!
Click to expand...
Click to collapse
I think that's right. It's ridiculous that by locking things down and preventing us from unlocking bootloader Verizon actually causes bricks of this nature to occur. If you had an unlocked bootloader you'd be 100% fine right now.
Sent from my Nexus 7
There is a way. I posted in previous forum.
Use fastboot
Fastboot wipe cache
Fastboot wipe user data
Try this if not pm me and I will help you out one on one
That should fix your issue
Sent from my XT1080 using xda app-developers app
phositadc said:
I think that's right. It's ridiculous that by locking things down and preventing us from unlocking bootloader Verizon actually causes bricks of this nature to occur. If you had an unlocked bootloader you'd be 100% fine right now.
Sent from my Nexus 7
Click to expand...
Click to collapse
If he hadn't brute forced a root method and messed with his phone he'd be 100% fine too
codito said:
If he hadn't brute forced a root method and messed with his phone he'd be 100% fine too
Click to expand...
Click to collapse
Ha...well there is that But what fun would that be?
The sad part is that the manufacturers could care less about giving us an unlocked bootloader. Android is a great ecosystem to play with and learn with and improve with. It's the carriers that are so paranoid about taking any tiny dent in their enormous profits that want to keep us locked out. So shame on them.
But, to be fair, I know the risks of the world we live in and this is my first brick in four Android phones, so I'm fine with it.
codito said:
If he hadn't brute forced a root method and messed with his phone he'd be 100% fine too
Click to expand...
Click to collapse
My point was merely that it's somewhat ironic that, by trying to prevent bricks by locking bootloaders, Verizon actually causes some bricks that would be avoided with an unlocked bootloader.
Not saying anything about whether what he was doing is right or wrong, or whether Verizon prevents more bricks than it causes.
Sent from my Nexus 7
Edit: but you've got to wonder. Are you more likely to brick using one of these crazy complicated methods we have to use to get around Verizon security? Or using fastboot OEM unlock + flash superuser. I bet per hundred rooted phones, less Nexus's (and other unlockable phones) are bricked than phones that are tightly locked down. Pure speculation of course.
killboredom said:
Ok, yesterday morning my MAXX received the KitKat update. Brainlessly, I clicked upgrade. This put me into the oh so famous bootloop.
During one of the boot loops, I managed to unroot with Voodoo.
Then in fastboot, I had the brilliant (aka, incredibly stupid) idea of flashing an old recovery. I had thought it was the one from 4.2.2 but sadly, it was from the previous version.
This had the appearance of working as it then booted to KitKat upgrade, which after a couple minutes failed.
Now I'm completely stuck in fastboot mode. I can't flash the 4.2.2 recovery. I haven't tried anything else. FXZ back to 12.15.15 doesn't work. Gives the GPT failure.
So...my belief, based only on googling around, is that I need to wait for the FXZ for KitKat. Does that sound right?
Any other ideas?
Thank you in advance!!!!!!!!!!
Click to expand...
Click to collapse
It sounds like you're actually stuck partially on JB, partially on KK, hence why you're bootlooping. I had a very similar issue when I tried to install the KK update through update.zip .......... after a couple hours, I finally got it back up and running.
My method - use the Method 2 Manual flash steps I posted in Dev section here - http://forum.xda-developers.com/showthread.php?t=2580060
Let me know if it works. I had problems at first, but that should cover it. Getting system to flash was actually the hardest part