so i tried to unzip a file with a backup assistant apk on it. when i boot into my phone with cyanogen cm7, im getting constant popup messages like adw.launcer and rom manager and android market etc has stopped expectedly. please try again. the only option i get is to click okay. i can't do anything else. is there a way to whipe my phone? i can't even boot into clockwork recovery because i can't get past my lock screen. any help would be amazing. thanks
Pull the battery. Boot into hboot by holding volume down plus power Untill the bootloader screen appears. Select recovery. Restore backup/reflash ROM.
Sent from my HTC Thunderbolt
just figured it out before you posted that - im an idiot. thank you.
ElectroFetish said:
just figured it out before you posted that - im an idiot. thank you.
Click to expand...
Click to collapse
It's all good. Stuff happens and I've never met anyone who has never had a duhh moment. lol
Sent from my HTC Thunderbolt
If your phone is bricked, go buy a new one. By definition, a bricked phone cannot be fixed. But then again, I suspect you don't know what "bricked" means.
mike.s said:
If your phone is bricked, go buy a new one. By definition, a bricked phone cannot be fixed. But then again, I suspect you don't know what "bricked" means.
Click to expand...
Click to collapse
Job well done on a post that contributed nothing and was just an attempt to make someone feel stupid.
Sent from my HTC Thunderbolt
JBO1018 said:
Job well done on a post that contributed nothing and was just an attempt to make someone feel stupid.
Sent from my HTC Thunderbolt
Click to expand...
Click to collapse
Truly bricked phones won't make it past the boot animation.
He needs to stop freaking out and follow instructions.
This is a PERFECT example of why people should NOT root until they know what they're doing.
Sent from my Synergized Thunderbolt via XDA Premium App
Related
so i tried to flash the full rooted ruu rom via hboot, i had it sitting on my table with the batt door off and knocked it on the floor ( accident ofcourse ) and the batt came out halfway during the process so now it goes into the htc screen then blank htc screen then blank and i cant get into cwr so my question is can i salvage it or am i f**ked?
Have you tried hbooting to recovery? Volume up and power down when the phone boots up.
cant keep it in cwr long enough to do anything, keeps rebooting and when it does go into cwr it says something like cant mount cache i think
snowbdr89 said:
cant keep it in cwr long enough to do anything, keeps rebooting and when it does go into cwr it says something like cant mount cache i think
Click to expand...
Click to collapse
Flash the stock ruu in hboot. Would be my only guess.
Sent from my ADR6400L using XDA App
eh im done with the tbolt, i took it to a wireless repair place here in slc and the tech guy gave me 100 for it for parts so im goin back to my dx and im much happier!! but thanks for the advice and help!!
Wow glad everyone doesn't give up that easy or we would never get any roms or root =P
Sent from my ADR6400L using XDA App
Feel good thread of the year! Or it could be the beer I just had.
Sent from my ADR6400L using XDA App
i wouldnt say i gave up way easy, i know i could have fixed it but im just not into the tbolt anymore!!
miketoasty said:
Flash the stock ruu in hboot. Would be my only guess.
Sent from my ADR6400L using XDA App
Click to expand...
Click to collapse
+1. That's exactly what would have worked. I know it's too late for the lad now, but for future users...
If you're ever stuck in a boot-loop and can't hboot into recovery, you'll need to copy and past the PGIMG05.ZIP file onto the root of your SD Card. This will be about a 200-400 meg file and would usually be a stock rooted RUU or stock signature RUU. After it's on the root of your SD, make sure it's the only PGIMG05.zip file on there! Then start the phone by holding down power + volume up. This will force the phone to hboot the PGIMG05 file which will get you past the boot-loop.
For some it's a good idea to have insurance too.
You can get a replacement minus the deductible if you "lose" your phone.
Just make certain you call VZW as soon as you lose it.
I don't suggest selling the phone for parts and saying it's lost, but I'm sure others have done this to cover their deductible.
Those without insurance...I have heard people have had great success with warranty replacement when using over the phone support when the phone doesn't boot or bootloops.
Since you send the phone back to VZW by mail, their replacement standards are much lower than dealing with their retail and face to face support.
raider3bravo said:
+1. That's exactly what would have worked. I know it's too late for the lad now, but for future users...
If you're ever stuck in a boot-loop and can't hboot into recovery, you'll need to copy and past the PGIMG05.ZIP file onto the root of your SD Card. This will be about a 200-400 meg file and would usually be a stock rooted RUU or stock signature RUU. After it's on the root of your SD, make sure it's the only PGIMG05.zip file on there! Then start the phone by holding down power + volume up. This will force the phone to hboot the PGIMG05 file which will get you past the boot-loop.
Click to expand...
Click to collapse
I'm new to this, just rooted my thunderbolt the week before last (have rooted a total of 4 phones though since and created my own bootimage with sound and everything! lol!), and that's what came to mind when I read the original post but I didn't "know" for sure. Thanks for confirming it. This stuff is fascinating to me. I like to understand what is going on. I'd like to someday write my own rom. Perhaps it's a pipe dream but is there someplace you could point me where I could start my education?
Heather
Putting the stock Rom on took the root off of it but didn't fix my boot loop. So I returned it and got a free thunderbolt.
Sent from my ADR6400L using XDA App
jaymccoubrey said:
Putting the stock Rom on took the root off of it but didn't fix my boot loop. So I returned it and got a free thunderbolt.
Click to expand...
Click to collapse
Your the reason Verizon hates rooters you are wasting there money on a device that is out of warranty because you would rather send it back than fix it yourself.
Thanks, jerk.
Sent from my ADR6400L using XDA App
F u dude. I tried everything to fix it. I spent over 60 hours working on it
Sent from my ADR6400L using XDA App
Nonetheless YOU damaged ur phone so it really doesn't matter how long you spent trying to repair it...
Sent from my ADR6400L using XDA App
hjborder said:
I'm new to this, just rooted my thunderbolt the week before last (have rooted a total of 4 phones though since and created my own bootimage with sound and everything! lol!), and that's what came to mind when I read the original post but I didn't "know" for sure. Thanks for confirming it. This stuff is fascinating to me. I like to understand what is going on. I'd like to someday write my own rom. Perhaps it's a pipe dream but is there someplace you could point me where I could start my education?
Heather
Click to expand...
Click to collapse
I believe you could start with os kitchen or another UI for extracting certain parts of a rom. I think in large part its knowing java script.
jaymccoubrey said:
F u dude. I tried everything to fix it. I spent over 60 hours working on it
Sent from my ADR6400L using XDA App
Click to expand...
Click to collapse
Hey Chevy I crashed my car into a tree and now it doesn't work. Oh dont worry I spent hours trying to fix it with no luck. So yea go ahead and give me a new one don't worry its still under warranty.
Sent from my ADR6400L using XDA App
Okay I was just wondering if I was one of the unlucky ones to instal the leak gingerbread Rom and my tbolt gets brick.. ..... Has anyone figure it out how to Unbrick tbolt ...just wondering.. if is possible. To Unbrick if it was to happened
sent from my rooted tbolt using XDA app
I"m pretty sure it's not possible because the phone resets every three seconds or so.
if there were a solution, it would be posted in the sticky threads in the developers forums.
If it is continuously bootlooping even in recovery, then you are truly fubar. No fix available. No amount of prayer/voodoo/exorcism will raise it from the dead. Donate it to science & send it to jcase. Maybe he can figure out why your phone was affected.
Sent from my ADR6400L using XDA App
Like sublimaze said, if it bootloops in recovery there is no known fix at this time but you could help everyone out a lot by going to this thread http://forum.xda-developers.com/showthread.php?t=1098363
sublimaze said:
If it is continuously bootlooping even in recovery, then you are truly fubar. No fix available. No amount of prayer/voodoo/exorcism will raise it from the dead. Donate it to science & send it to jcase. Maybe he can figure out why your phone was affected.
Sent from my ADR6400L using XDA App
Click to expand...
Click to collapse
so this may be a silly question but its not possible to do a battery pull and boot right back into the bootloader? perhaps even keep a stock froyo radio on the root of the sd card incase the worst should happen?
I could have sworn the definition of a brick means it's not recoverable.
If you can recover, then it's technically not a brick.
Dnakaman said:
I could have sworn the definition of a brick means it's not recoverable.
If you can recover, then it's technically not a brick.
Click to expand...
Click to collapse
It does, or at least did back in my day...
Sent from my ADR6400L using XDA App
funkybside said:
It does, or at least did back in my day...
Sent from my ADR6400L using XDA App
Click to expand...
Click to collapse
Can I get an AMEN!!!!
Dnakaman said:
I could have sworn the definition of a brick means it's not recoverable.
If you can recover, then it's technically not a brick.
Click to expand...
Click to collapse
I also thought that was the case. hence the word "brick" but if its still booting, why cant anyone figure out how to fix it?
littleguevara said:
I also thought that was the case. hence the word "brick" but if its still booting, why cant anyone figure out how to fix it?
Click to expand...
Click to collapse
The problem is that the phone reboots every few seconds, apparently not leaving enough time to apply any kind of 'fix'.
There is no fix yet but that thread that was linked to previously would probably be your best bet.
ok so i hooked up my fresh out the box (unrooted) galaxy s2 to odin and installed CWM in hopes i could back up the stock ROM so if i ever have a problem and need it for insurance purposes with at&t i could make the phone completely stock... i am certain i messed up because when i boot in recovery anything i do in CWM it just shows the hat refresh symbol and does nothing else. please help this newb out.
Make sure you're using the home and back soft keys at the bottom, not the power button.
Sent from my SAMSUNG-SGH-I777 using xda premium
hahaha wow!!!! i feel like a effing idiot. thanks so much for recognizing my tard/newb mistake. thanks a bunch kadin lol
TAK209 said:
hahaha wow!!!! i feel like a effing idiot. thanks so much for recognizing my tard/newb mistake. thanks a bunch kadin lol
Click to expand...
Click to collapse
We all did it. At least, I did.
Sent from my SAMSUNG-SGH-I777 using xda premium
I am and Idiot, too.
TAK209 said:
ok so i hooked up my fresh out the box (unrooted) galaxy s2 to odin and installed CWM in hopes i could back up the stock ROM so if i ever have a problem and need it for insurance purposes with at&t i could make the phone completely stock... i am certain i messed up because when i boot in recovery anything i do in CWM it just shows the hat refresh symbol and does nothing else. please help this newb out.
Click to expand...
Click to collapse
I am the same idiot. I would still be wondering if I wouldn't have found this post. So you are my idiot hero as without you I wouldnt have found the answer post here either.
took me a while to.figure it out as well
Hello all, I was walking my friend through rooting his phone over Google talk. He rooted all went well a few days later he wanted to Rom it. He made a mistake and flashed the international omega Rom on his US ATT samsungi747. His phone is now dead. No way to get into recovery or download mode. Just dead. Bricked. What can I do to help him? As I am partially responsible cause I was helping him. I did not know much about the Rom he was flashing.
I was reading about a possible fix with a jig but can not find a jig for.the Samsung i747.
Please any and all advice would be greatly appreciated.
Sent from my ADR6400L using Tapatalk 2
Sorry but looks like its gone. Have seen a few ppl able to recover with mskips fix but only if theyre able to turn phone on.
DeathGrind said:
Hello all, I was walking my friend through rooting his phone over Google talk. He rooted all went well a few days later he wanted to Rom it. He made a mistake and flashed the international omega Rom on his US ATT samsungi747. His phone is now dead. No way to get into recovery or download mode. Just dead. Bricked. What can I do to help him? As I am partially responsible cause I was helping him. I did not know about the Rom he was flashing.
I was reading about a possible fix with a jig but can not find a jig for.the Samsung i747.
Please any and all advice would be greatly appreciated.
Sent from my ADR6400L using Tapatalk 2
Click to expand...
Click to collapse
A compatible jig may be your only solution if you can't get into download mode manually. A jig would force the phone into download mode, once in download mode you'd be able to flash the stock AT&T firmware through Odin.
Sent from my SAMSUNG-SGH-I747 using Tapatalk 2
Has anyone ever tried just returning it and saying it randomly died? If they can't turn it on then there's no way to tell it's rooted
Only joking
"All this knowledge is giving me a major brainer!"
In the blacked Screen try flash with Odin.
Sent from my Hybrid Note using Tapatalk 2
DakiX said:
In the blacked Screen try flash with Odin.
Sent from my Hybrid Note using Tapatalk 2
Click to expand...
Click to collapse
he's in oregon and I'm in california. I think he is freaking out. But he did say ODin was not recognizing the device.
ADB? ^^
Sent from my Hybrid Note using Tapatalk 2
Error 1. Not reading
Error2. Wrong section... not reading
If he cant get cwm or screen to show something who knows what he did...fix: there is none get another device and read before u do stupid stuff.... u can't expect us to fix lack of reading or not knowing what ur flashing....
im on my phone. expect terrible typos.
DeathGrind said:
oh no. Its his first android phone. He only had it about a week. I can't believe this. I feel so bad for him.
Thanks for the reply
I have been looking for a jig that is compatible with the att samsung galaxy s3 sgh-i747 and had no luck. Do they exist?
Click to expand...
Click to collapse
A jig is a jig the one I bought for my captivate works 100% on gs3, get the jig put into phone if don't boot into download mode, hold down power button with jig still in if that don't work ur screwed .... your better off trying make ur own jig ( YouTube it ) cause if the phone runs out of battery and won't charge then u have another issue...
---------- Post added at 12:38 AM ---------- Previous post was at 12:27 AM ----------
Moh_Jay said:
Has anyone ever tried just returning it and saying it randomly died? If they can't turn it on then there's no way to tell it's rooted
"All this knowledge is giving me a major brainer!"
Click to expand...
Click to collapse
Just cause "we " can't turn it on don't mean they eventually can't ..
Btw you maybe able to save your friend
http://forum.xda-developers.com/showthread.php?t=1743757
"All this knowledge is giving me a major brainer!"
Moh_Jay said:
Btw you maybe able to save your friend
http://forum.xda-developers.com/showthread.php?t=1743757
"All this knowledge is giving me a major brainer!"
Click to expand...
Click to collapse
Thanks man! I ordered him one. Hopefully it will work. He's also going to make one tomorrow.
A huge thank you to all the people that provided helpful information and friendly advice.
I was actually expecting more ridicule, but it was minimal. . I know we messed up, but I never knew you could "brick" a phone from flashing a Rom.
Anyway thanks again guys! I will keep you posted on if the jig works or not.
Sent from my ADR6400L using Tapatalk 2
Moh_Jay said:
Has anyone ever tried just returning it and saying it randomly died? If they can't turn it on then there's no way to tell it's rooted
Only joking
"All this knowledge is giving me a major brainer!"
Click to expand...
Click to collapse
The morning I was picking up my phone...a dude walks in and says that his phone doesn't turn on anymore after having it a week. I thought to myself..."he flashed an international ROM...what a douche".
Some people actually have there phones just stop working. Happened to my friend that had a Samsung galaxy nexus, stock unrooted. Just died. There was nothing I could do to fix it.
Sent from my ADR6400L using Tapatalk 2
DeathGrind said:
Thanks man! I ordered him one. Hopefully it will work. He's also going to make one tomorrow.
A huge thank you to all the people that provided helpful information and friendly advice.
I was actually expecting more ridicule, but it was minimal. . I know we messed up, but I never knew you could "brick" a phone from flashing a Rom.
Anyway thanks again guys! I will keep you posted on if the jig works or not.
Sent from my ADR6400L using Tapatalk 2
Click to expand...
Click to collapse
If you didnt know a rom could brick a phone you shouldnt be flashing period. Theres always ALWAYS bold letters that says this may brick your phone an or we are not responsible if this breaks your phone... no one with there first android should be flashing till they know android smoothly... *sigh*
Usually 90% of the time your always able to get into recovery mode. From what I've read this only happens when flashing the omega Rom. People make mistakes.
I've rooted and rom'd 100s of phones, and never not been able to get back to recovery.
Sent from my ADR6400L using Tapatalk 2
SiNJiN76 said:
The morning I was picking up my phone...a dude walks in and says that his phone doesn't turn on anymore after having it a week. I thought to myself..."he flashed an international ROM...what a douche".
Click to expand...
Click to collapse
The good and bad of brand new phone on the market. Some people do not like reading and want to be handed the solution.
Noobs....read.....read...read some more....go to bed....get up...read some more...have cookies for snack time....read some more... and then read some more... and for the love of GOD....read some more before flashing anything!
I mean that in the nicest way, becasue I have questions on a semi-regular basis also.
jcbofkc said:
The good and bad of brand new phone on the market. Some people do not like reading and want to be handed the solution.
Noobs....read.....read...read some more....go to bed....get up...read some more...have cookies for snack time....read some more... and then read some more... and for the love of GOD....read some more before flashing anything!
I mean that in the nicest way, becasue I have questions on a semi-regular basis also.
Click to expand...
Click to collapse
If ppl read things 95% of there questions would be answered. The other 5% could be found by google
I understand telling him to read. And he did so for about a week. He succesfully used odin to root his phone. A few days later he said he wanted to Rom, and asked me how to do a proper back up with titanium backup. I ran him through the backup procedure.
I mean I totally thought that if he made it through the rooting procedure that he was good to go. Rom'ing has always been to me something fairly easy, and if something went haywire, just boot to recovery.
I've had people ask for help that flashed an incomplete or corrupted download, but have always been able to at least power the phone on, or at the very least have it recongnized in adb.
I have been reading and googling about a fix, but information seems minimal on this current circumstance. So I reached out to the community for advice.
Sent from my ADR6400L using Tapatalk 2
DeathGrind said:
I understand telling him to read. And he did so for about a week. He succesfully used odin to root his phone. A few days later he said he wanted to Rom, and asked me how to do a proper back up with titanium backup. I ran him through the backup procedure.
I mean I totally thought that if he made it through the rooting procedure that he was good to go. Rom'ing has always been to me something fairly easy, and if something went haywire, just boot to recovery.
I've had people ask for help that flashed an incomplete or corrupted download, but have always been able to at least power the phone on, or at the very least have it recongnized in adb.
I have been reading and googling about a fix, but information seems minimal on this current circumstance. So I reached out to the community for advice.
Sent from my ADR6400L using Tapatalk 2
Click to expand...
Click to collapse
Personally i wait a bit to root rom a brand new phone... however ive never had a issue untill i fried my gs mesmerize so im a lil hesitant
Yeah, this is the first serious issue I have ran into in almost 3 years of mod'ing android phones.
Sent from my ADR6400L using Tapatalk 2
So was flashing everything everything i had on a SD card like usual, dumb thumb hit wrong file
just like that i was shooting Threes' BRICK. So is there anything i can do? if you got some insight
holla at your boy and let me know something.
BigTexastrev said:
So was flashing everything everything i had on a SD card like usual, dumb thumb hit wrong file
just like that i was shooting Threes' BRICK. So is there anything i can do? if you got some insight
holla at your boy and let me know something.
Click to expand...
Click to collapse
can you boot into the bootloader to get into the recovery? i have flashed all the kernels here on top of each other without any issues....
p.s. incase you forgot, i believe it is hold volume down + power to get into the bootloader
When you install a kernel it replaces the one that was there.
That did not brick your device.
If you can get to recovery do a full wipe and flash a ROM
i doubt your bricked boss.. bricked is phone not turning on at all.. and charge light not coming on when u plug it in.. just a stright dead phone
nope my phone is total out of there, no bootloader no light when charging, plug it into computer and it says that Qhsusbd-load, ive tried drivers, the unbricker i got ubuntu all that. i was running evil aroma and flashed yp-g70 and dead
BigTexastrev said:
nope my phone is total out of there, no bootloader no light when charging, plug it into computer and it says that Qhsusbd-load, ive tried drivers, the unbricker i got ubuntu all that. i was running evil aroma and flashed yp-g70 and dead
Click to expand...
Click to collapse
yea i think thats bricked.. i dont understand how u did u though? u were running evil kernel and u flashed what over it????
evo401 said:
yea i think thats bricked.. i dont understand how u did u though? u were running evil kernel and u flashed what over it????
Click to expand...
Click to collapse
yeah i flashed this off of freEVOLTE [Kernel]7/13/12 StockMOD 1.22.651.3 CoreDuo/ScreenOff Script/MemManagement/DimLights
Try running the Lazypanda unbricker, or the other Evo LTE unbricking tool. It might just be that it accidentally went into QHUSB mode even though nothing was wrong.
Did you check MD5 hash before flashing it? You should ALWAYS do this, I know it wont help now, but for the future. That ensures that the file is identical to what was uploaded. Also (and I know you're probably aware of this, but in case anyone else is reading) only flash files that are specific to our device. Another kernel for another device will most definitely brick you.
I would try to see if the HTC unbrick project helps you, otherwise if you have sprint insurance (not the fancy 11 dollar one) that covers software issues (4 dollars a month) will cover this since it is a software problem.
Racer Of All said:
I would try to see if the HTC unbrick project helps you, otherwise if you have sprint insurance (not the fancy 11 dollar one) that covers software issues (4 dollars a month) will cover this since it is a software problem.
Click to expand...
Click to collapse
They'll cover the issue even if you're rooted? I think I need this insurance, thanks!
BigTexastrev said:
nope my phone is total out of there, no bootloader no light when charging, plug it into computer and it says that Qhsusbd-load, ive tried drivers, the unbricker i got ubuntu all that. i was running evil aroma and flashed yp-g70 and dead
Click to expand...
Click to collapse
what is yp-g70?
Being rooted does not prevent sprint from working on the phone or filing an insurance claim
Sent from my EVO using Tapatalk 2
bog3nator said:
what is yp-g70?
Click to expand...
Click to collapse
thats what im tryin to figure out??
I have no idea. I Googled it and it came back as a Samsung Galaxy player. So if the op flashed something meant for this Samsung music player then no wonder the phone is bricked.
"We're coming from a pure power source"
metalfan78 said:
I have no idea. I Googled it and it came back as a Samsung Galaxy player. So if the op flashed something meant for this Samsung music player then no wonder the phone is bricked.
"We're coming from a pure power source"
Click to expand...
Click to collapse
It's a kernel for Samsung galaxy player 5.0, why would the person flash it on evo lte i have no idea.
Sent from my lair.
Well, that explains it. That's a tough lesson to learn.
"We're coming from a pure power source"
Guys, he said he accidentally flashed it...
Sent from my Evo LTE using Tapatalk 2
Emerl said:
Guys, he said he accidentally flashed it...
Sent from my Evo LTE using Tapatalk 2
Click to expand...
Click to collapse
There are still precautions that shouldve been taken.
The kernel shouldn't even have it on the device, and if it was fastboot flashed he shouldve had seperate folders for each device
Rxpert said:
There are still precautions that shouldve been taken.
The kernel shouldn't even have it on the device, and if it was fastboot flashed he shouldve had seperate folders for each device
Click to expand...
Click to collapse
Gonna do that right now
Sent from my EVO using xda premium
damn that sucks bro might be like way out there but did u try the lazy panda unbricker probaly wont work but its worth a try