Database Info

PLEASE HELP!! :S Bricked?

I installed the new jelly Bean ROM for the tf300, forced it really with a forum in the general section, everything was working fine except i had lost my recovery.
I tried installing the recovery back on but i couldent, then i tried wipe user data waited a long time for that but nothing happened so i rebooted and now it is stuck at the Asus logo and i cant access the boot loader!! please im desperate! hope its not totally messed up.

I did EXACTLY the same. You are ****ed no way to fix it. I will be sending my tf300 for RMA later this day.

sparky28000 said:
I did EXACTLY the same. You are ****ed no way to fix it. I will be sending my tf300 for RMA later this day.
Click to expand...
Click to collapse
Let us know how that goes - rumor has it that Asus doesn't service tablets with unlocked motherboards. So they'll throw your board in the trash, place in a new one, then charge you for it.

krhainos said:
Let us know how that goes - rumor has it that Asus doesn't service tablets with unlocked motherboards. So they'll throw your board in the trash, place in a new one, then charge you for it.
Click to expand...
Click to collapse
what about locked tablets but w/ rooted w/ SU installed? any rumors that they wouldn't service it? I think I should be fine. My JB update is causing tons of Gapps force closings, must have been a corrupt update. Sending it in since I want to keep the BL/warranty intact

paedz718 said:
what about locked tablets but w/ rooted w/ SU installed? any rumors that they wouldn't service it? I think I should be fine. My JB update is causing tons of Gapps force closings, must have been a corrupt update. Sending it in since I want to keep the BL/warranty intact
Click to expand...
Click to collapse
If your bootloader is intact, your warranty is completely intact. I think there are ways to force the unit to flash stock firmwares.
If you have your root, check this out: http://forum.xda-developers.com/showthread.php?t=1622628
Method 2 worked for me going back to 9.4.3.30/ICS, then I was able to go to JB afterwards. Bootloader unlock NOT required.

krhainos said:
If your bootloader is intact, your warranty is completely intact. I think there are ways to force the unit to flash stock firmwares.
If you have your root, check this out: http://forum.xda-developers.com/showthread.php?t=1622628
Method 2 worked for me going back to 9.4.3.30/ICS, then I was able to go to JB afterwards. Bootloader unlock NOT required.
Click to expand...
Click to collapse
oh nice! I may need to try this. I assume you were unrooted when you tried Method 2. curious, why did you have to go back to .30/ICS before going to JB? and did the JB OTA update come down again for you or you had to try that workaround method?

paedz718 said:
oh nice! I may need to try this. I assume you were unrooted when you tried Method 2. curious, why did you have to go back to .30/ICS before going to JB? and did the JB OTA update come down again for you or you had to try that workaround method?
Click to expand...
Click to collapse
The JB update script will fail when it tries to patch APK's that you removed. I removed a bunch to de-bloat, so you need a 100% complete stock 9.4.3.30 ICS before the JB update from Asus will work.
I was rooted and unlocked, so I couldn't use the traditional method -- I used a modified zip file that I flashed through TWRP.

krhainos said:
The JB update script will fail when it tries to patch APK's that you removed. I removed a bunch to de-bloat, so you need a 100% complete stock 9.4.3.30 ICS before the JB update from Asus will work.
I was rooted and unlocked, so I couldn't use the traditional method -- I used a modified zip file that I flashed through TWRP.
Click to expand...
Click to collapse
thanks for the info

paedz718 said:
thanks for the info
Click to expand...
Click to collapse
Couple other things -- you will lose TWRP or CWMR upon flashing, attempting to flash one* will brick your unit.
Make sure you back up your root with Voodoo OTA Rootkeeper and SuperSU (not Superuser) -- there's a couple threads about this floating around. I was following this one:
http://forum.xda-developers.com/showthread.php?t=1840504
* - they are currently working on making a new JB-compatible recovery after a bunch of us bricked our tablets

krhainos said:
Couple other things -- you will lose TWRP or CWMR upon flashing, attempting to flash one* will brick your unit.
Make sure you back up your root with Voodoo OTA Rootkeeper and SuperSU (not Superuser) -- there's a couple threads about this floating around. I was following this one:
http://forum.xda-developers.com/showthread.php?t=1840504
* - they are currently working on making a new JB-compatible recovery after a bunch of us bricked our tablets
Click to expand...
Click to collapse
I read that about the custom recoveries since they need to be JB compatible. looks like TWRP is on the case. My instance, I kept my bootloader intact and wanted to keep it still like that just in case I screwed it up like cracking the screen. I've only had it for a few months. That's why I may have to try the Wolf method for rooted users w/ locked bootloaders. I just need to verify thru ADB that I still have root after I upgraded or try the unrooted method to go back to ICS.
Just read that link closely and I def did not have SuperSU installed only Voodoo OTA RK, guess I'm no longer rooted after the update then. I should have waited a few days before I updated and scoured the forums. oh well, I'm just hoping to get a working tablet back. I can only get to the "Welcome" setup screen on JB and immediately get gapps force closes, popping up one after the other. Def a corrupt flash.

How is the rma thing have u gotten word back? I bricked mine upgrading to jb. The fast boot USB method errors and locks up the unit.
So I opened an RMA ticket and am sending my tablet in a day... my boot loader is unlocked as well.

Happened to me too. I'm hoping that ASUS will fix it for a reasonable price. Otherwise I'm just going to get a Nexus 7.

[Q] Did the JB ATT RUU brick my phone?

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.

One XL owners who accepted 3.18 OTA then unlocked/S-OFF still needs boot.img flashed

So this is a general word of caution that i'd like to relay to everyone.
Back in October or Nov of '12, I bought a One XL. I did not know you needed to be S-OFF after unlocking to run a RUU after installing the 3.18 OTA without bricking my phone. Lesson learned. I got a warranty replacement. I loaded the 3.18 OTA not realizing that the old exploit wouldn't work. I decide to wait until the new exploit/3.18 RUU/successful S-OFF/whatever comes out and decided to wait a few months after that for Hasoon to update his all in one kit.
That time has come and passed, and last night I decided I wanted to try it again. I read, read, and read some more, redownloaded everything, checked the md5s on everything, and started to unlock the bootloader. Ok, Easy enough, I've done this before. I flashed recovery, and successfully got S-OFF. No big deal.
Ok. So far, so good! Now, i just need to make a nandroid backup, and flash the rom, right? Not so fast... I read that people were having trouble installing ASOP based roms when on newer hboot (updated from taking the 3.18 OTA). But, this was nothing to be worried about if you already have S-OFF successfully done (which I have). I wanted to install Cleanrom or ViperXL (both sense based) so I should be good, right? All posts I found said this was the case, don't worry, no need to flash the boot.img separately.
WRONG, WRONG, WRONG, NO. NO. STOP. FAIL. You are a moron, and everything you have researched is wrong, stupid!!!!!--this is what I felt like my phone was trying to tell me.
The install took like 2 seconds, and it was stuck at the htc boot screen after a reboot. I had to RUU and start over (my nandroid got accidentally deleted because I checked the wrong box during a wipe).
It doesn't matter if you already have S-OFF, or if you don't want to even mess with AOSP roms, you have to (or at least I had to) use adb/fastboot to manually flash boot.img first, then install the rom. It took me many hours of frustration to realize I had to do this.
Now, my question is, if I do this once, do I have to do this every time I flash a new ROM? It just pisses me off how everyone in multiple threads said this wasn't necessary at all, and not to worry, when it totally meant failure for me. The point is, you can do all the reading, research, over and over, and still it might completely fail.

If you have s-off you never have to flash boot image.
Sent from my evita

If you have s-off you never have to flash boot image.
Click to expand...
Click to collapse
The whole point of my post was that, for reasons unknown to me, I couldn't successfully install a custom rom without doing. just. that.
No clue why...I spent all night trying to figure it out, but as soon as I flashed the boot image, bingo. everything worked like it was supposed to.
I'm not saying it is the case for everyone, just wanted people to know my experience.

That's really weird... That shouldn't happened. You could try ruuing again. Idk that is odd.
Sent from my evita

I'm guessing it has something to do with the fact that I started the whole process (unlock/S-OFF) with the 3.18 OTA installed. maybe since I RUUd, it will be ok.
I'm going to try another ROM tonight and see what happens. Seeing as I've never actually restored from a nandroid backup (I'm offloading them to my laptop each time), I hope it won't take too long.

I agree with leogibson.
My phone is exactly the same, even with s-off I still need to flash boot.img separately.
I can also not install radios since hboot 2.14 except via RUU or ruu mode.
My phones also did not brick with 3.17 OTA, supercid and s-on. Although personally I am not sold that any update except AT&T 3.18 does that in the first place (it probably has something to with why there is 2 packages delivered in AT&T 3.18).

I just installed another rom, I did not have to flash the boot separately this time.

new htc one xl user
Good day, i m a new htc one xl user, i was wondering if any could be of help. I need jelly bean on my xl( it is not a carrier phone). I also do not want to root my phone in the process. Is this visible??

slumbee said:
Good day, i m a new htc one xl user, i was wondering if any could be of help. I need jelly bean on my xl( it is not a carrier phone). I also do not want to root my phone in the process. Is this visible??
Click to expand...
Click to collapse
Don't hijack other peoples threads. Start your own.
Sent from my HTC One XL using Xparent Red Tapatalk 2

ImagioX1 said:
Don't hijack other peoples threads. Start your own.
Sent from my HTC One XL using Xparent Red Tapatalk 2
Click to expand...
Click to collapse
I m sorry about that, i m stl very new here

[Q] Red triangle sign when updating

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

De-bricking time!

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