as title states hard bricked after install of orthus eight then rebooted and nothing. followed instructions and still bricked. i have flashed many roms i don't know what went wrong with this flash. Will a jig work to unbrick to download mode? I have tried several methods to get into download and cant seem to succeed.
Re: [Q] Orthus eight hard bricked phone
I don't think the rom had anything to do with it. I've flashed it and it's fine.
What was the best thing before sliced bread?
baddogie said:
as title states hard bricked after install of orthus eight then rebooted and nothing. followed instructions and still bricked. i have flashed many roms i don't know what went wrong with this flash. Will a jig work to unbrick to download mode? I have tried several methods to get into download and cant seem to succeed.
Click to expand...
Click to collapse
What exactly did you do? And don't just say, "I followed the instructions." I need to know exactly what you did every step of the way from downloading Orthus Eight to laying the cornerstone of your new brick house.
I'll ask this first obvious question because so often it reveals the true problem: what kind of phone do you have?
Lets not go straight in to flaming a user just because he has no posts. I know for a fact there is a brick problem in AOSP 4.2.2. Lets hear him out.
baddogie said:
Will a jig work to unbrick to download mode?
Click to expand...
Click to collapse
I'm not an expert but if you really hard brick the phone then jig would be your solution.
You may want to read the posts on "[ROM][10.1]SUPERLITE CM10.1 JB 4.2.2 > 79mb < | SLGAPPS 10MB | FEB28/13" page 2 and 3 and try to get in touch with the user who bricked the phone and was going to try "JTAG brick repair"
BTW I also installed the ROM and is working smooth.
P.S. I don't think anyone is blaming Ortus8 ROM while the question ... and request for support ... was regarding jig
Re: [Q] Orthus eight hard bricked phone
prbassplayer said:
Lets not go straight in to flaming a user just because he has no posts. I know for a fact there is a brick problem in AOSP 4.2.2. Lets hear him out.
Click to expand...
Click to collapse
A Randomly appearing brick that only affects some and not others this i want proof of sir mod or not i want validation.
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2
---------- Post added at 05:28 AM ---------- Previous post was at 05:27 AM ----------
err1max1 said:
I'm not an expert but if you really hard brick the phone then jig would be your solution.
You may want to read the posts on "[ROM][10.1]SUPERLITE CM10.1 JB 4.2.2 > 79mb < | SLGAPPS 10MB | FEB28/13" page 2 and 3 and try to get in touch with the user who bricked the phone and was going to try "JTAG brick repair"
BTW I also installed the ROM and is working smooth.
P.S. I don't think anyone is blaming Ortus8 ROM while the question ... and request for support ... was regarding jig
Click to expand...
Click to collapse
A jig does nothing for a hard brick. You don't need a jig to get to DL mode if soft brick. In short a jig is worthless.
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2
mtdew said:
A Randomly appearing brick that only affects some and not others this i want proof of sir mod or not i want validation.
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2
---------- Post added at 05:28 AM ---------- Previous post was at 05:27 AM ----------
A jig does nothing for a hard brick. You don't need a jig to get to DL mode if soft brick. In short a jig is worthless.
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2
Click to expand...
Click to collapse
In my opinion it has to do with the kernel, course I could be wrong. However I had 2 testers brick with CM's kernel. I've seen similar reports with the 4.2.2 AOKP around here. In the 2 cases I'm sure the phone booted and ran fine, then randomly locked up and dead. No life afterwards. I understand we all make mistake by both my testers where doing something different when it happen, and the fact the device booted fine THEN bricked (again my particular case) means it flashed fine and whole booted something happen (I believe it blew partitions, possibly secondary or third, if this device has a third, bootloader). If I had any better proof I would have found a solution, or tried to already.
Re: [Q] Orthus eight hard bricked phone
prbassplayer said:
In my opinion it has to do with the kernel, course I could be wrong. However I had 2 testers brick with CM's kernel. I've seen similar reports with the 4.2.2 AOKP around here. In the 2 cases I'm sure the phone booted and ran fine, then randomly locked up and dead. No life afterwards. I understand we all make mistake by both my testers where doing something different when it happen, and the fact the device booted fine THEN bricked (again my particular case) means it flashed fine and whole booted something happen (I believe it blew partitions, possibly secondary or third, if this device has a third, bootloader). If I had any better proof I would have found a solution, or tried to already.
Click to expand...
Click to collapse
I find it hard to believe this was random or attributed to to cm's kernel if nothing else it would be based on something particular to their hardware or your build as you would see a ton of these on cm's thread. You are placing blame in an unlikely place as well.
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2
Re: [Q] Orthus eight hard bricked phone
mtdew said:
I find it hard to believe this was random or attributed to to cm's kernel if nothing else it would be based on something particular to their hardware or your build as you would see a ton of these on cm's thread. You are placing blame in an unlikely place as well.
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2
Click to expand...
Click to collapse
Well I was using cms device folders and my qcom hardware folders are constabtly updated with cms commits. Only difference are overlays files and that we use slim.mk which is mostly a copied cm.mk only fixed source locations. Don't know what I did different to create a brick zip. Not my first rodeo, though I'm no expert that's for sure.
Sent from my Nexus 4 using Tapatalk 2
Re: [Q] Orthus eight hard bricked phone
prbassplayer said:
Well I was using cms device folders and my qcom hardware folders are constabtly updated with cms commits. Only difference are overlays files and that we use slim.mk which is mostly a copied cm.mk only fixed source locations. Don't know what I did different to create a brick zip. Not my first rodeo, though I'm no expert that's for sure.
Sent from my Nexus 4 using Tapatalk 2
Click to expand...
Click to collapse
Again if it was cm's doing this would be far more widespread. Something's not adding up, also several people have successfully flashed orthus this is user error nothing more.
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2
mtdew said:
Again if it was cm's doing this would be far more widespread. Something's not adding up, also several people have successfully flashed orthus this is user error nothing more.
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2
Click to expand...
Click to collapse
Mate Tell me something I don't know. Same thing with Slim. My test builds where flashed by 50+ people only 2 bricked, so happen both I had most communication with as they where helping me debug the camera problem I had. Like I said if I had a better idea of where the problem laid I wouldn't have stopped working with it (I still fiddle with the code) I just don't have any concrete evidence to work with to merit the chance of bricking other members devices. I originally thought it was me but not the case. There has been posts about this happening on AOKP, I believe on CM (not sure if it was here or not). I'm not saying its a wide spread problem, however its there.
Re: [Q] Orthus eight hard bricked phone
Aokp for this device? Cm for this device? Were the members who bricked very experienced? I'm not saying you don't know what you're talking about but i never trust testers and i especially don't trust people saying such and such ROM bricked my device. I've seen this all too often and all it does is spread fear and give good devs bad names.
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2
Re: [Q] Orthus eight hard bricked phone
Just as an fyi, I loaded Orthus onto my skyrocket just now. Booted fine, restoring apps now
Sent from my SGH-I317 using Tapatalk 2
Re: [Q] Orthus eight hard bricked phone
Been running it since it dropped absolutely no issues smoothest 4.2.2 ROM out.
Sent from my SGH-I727 using xda premium
Re: [Q] Orthus eight hard bricked phone
I'd love to try and help this user.
What methods have you tried to get into download mode?
You said you can reboot, then get nothing. Is that a blank screen? Does the backlight come on?
What recovery were you on? What steps to flash?
Can you get to the device via adb?
Even if I can't help you, maybe we can narrow down the issue.. Whatever it may be.
Sent from my SGH-I727 using Tapatalk 2
damn another brick bug, i thought it was all done with
as for blaming the op, if he had the sr and flashed an sr rom whichever rom that would be, we cant blame the op since theres nothing he could do wrong to actually hardbrick the phone , yes he could softbrick but not hardbrick it.
definition of the bug imo is its totally random, 1 out of x phones it will happen to
T.J. Bender said:
What exactly did you do? And don't just say, "I followed the instructions." I need to know exactly what you did every step of the way from downloading Orthus Eight to laying the cornerstone of your new brick house.
I'll ask this first obvious question because so often it reveals the true problem: what kind of phone do you have?
Click to expand...
Click to collapse
I have a samsung galaxy s2 skyrocket sigh i727. I downloaded the rom from the forums here (i think the link was goo.im) and transfered to my internal sd. I wiped data factory reset, wiped cache patroon, wiped system, wiped delvil cache then flash downloaded zip and half way through the android in background fell over and triangle showed up. I tried restoring backups and eving wiping did not work so I went to advance and restart recovery and the device turned off and now will not respond to anything.
Re: [Q] Orthus eight hard bricked phone
Be careful with goo. I've never been sure what I've downloaded from it.
Most likely not a problem with the rom.
Sent from my SAMSUNG-SGH-I727 using xda app-developers app
mtdew said:
Aokp for this device? Cm for this device? Were the members who bricked very experienced? I'm not saying you don't know what you're talking about but i never trust testers and i especially don't trust people saying such and such ROM bricked my device. I've seen this all too often and all it does is spread fear and give good devs bad names.
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2
Click to expand...
Click to collapse
I'm not trying to give any dev a bad name I was just trying to specify what rom I was flashing when this happend
baddogie said:
I have a samsung galaxy s2 skyrocket sigh i727. I downloaded the rom from the forums here (i think the link was goo.im) and transfered to my internal sd. I wiped data factory reset, wiped cache patroon, wiped system, wiped delvil cache then flash downloaded zip and half way through the android in background fell over and triangle showed up. I tried restoring backups and eving wiping did not work so I went to advance and restart recovery and the device turned off and now will not respond to anything.
Click to expand...
Click to collapse
OK. Moving the file from external to internal could cause a corruption. It could have been a bad DL from the start. Hence the reason checking MD5s is so imortant. Either way you should still be able to enter recovery. No ROM that is flashable touches the recovery partition. Pull out your external sdcard and access it with a comp. Copy that files full name here.
Related
Since it says I can't post a reply in the Liquid's thread because I'm a new user. Yes, I'm actually a newb user. Here's what happened.
I did a backup of everything, including my current ROM which was rooted stock VZW ICS. MyBackup Pro'd everything, used Clockwork Recovery Mod and flashed the touchy GUI for the recovery mode. Backed up the nandroid as stated. Downloaded the Liquid ROM zip and then went into the CWM recovery mode. Wiped cache partition, then Dalvik cache and did a wipe factory data reset (bad idea, probably) and then it was done flashing in about 5 seconds (which I thought was a bit quick.. it said success!) so then I rebooted. Now it's dead.
It won't even turn on, did a battery pull (this is while the battery was at 100% because I was still plugged in via USB) and put it back in 5 mins later. It won't turn on at all, even with all of the methods like holding down the volume and home buttons, so I'm guessing it's bricked.
I'm already thinking of calling Verizon to add insurance on this to get a replacement if there's no other solution.
Wow that's terrible I've never heard of this situation but I will look into it and post any solutions
Unleashing the force using my new Jedi powers!
---------- Post added at 03:53 AM ---------- Previous post was at 03:41 AM ----------
So far this is what I've found - > http://mobiletechvideos.mybigcommerce.com/samsung-galaxy-s-iii-jtag-brick-repair/
Unleashing the force using my new Jedi powers!
I'm not liking the cost of this thing... I've had this phone for two weeks so I may just call them and tell them that it stopped working and get a replacement.
Good idea I'm sure that'll work
Unleashing the force using my new Jedi powers!
Sorry for not looking. There's a thread on this already here: http://forum.xda-developers.com/showthread.php?t=1846682
Mods please close this.
Thought so, a friend pointed it out for me. Apparently I forgot to put on a Jelly Bean bootloader of some kind, which resulted in this. I didn't fully pay attention to the fact that the Liquid ROM I installed was a Jelly Bean OS. Called Verizon, they're sending me a reconditioned phone. Hopefully it isn't as bad as it sounds...
N0wy0ud1e said:
Thought so, a friend pointed it out for me. Apparently I forgot to put on a Jelly Bean bootloader of some kind, which resulted in this. I didn't fully pay attention to the fact that the Liquid ROM I installed was a Jelly Bean OS. Called Verizon, they're sending me a reconditioned phone. Hopefully it isn't as bad as it sounds...
Click to expand...
Click to collapse
It's better than the one in your hand.
Sent from my SCH-I535 using Tapatalk 2
N0wy0ud1e said:
Thought so, a friend pointed it out for me. Apparently I forgot to put on a Jelly Bean bootloader of some kind, which resulted in this. I didn't fully pay attention to the fact that the Liquid ROM I installed was a Jelly Bean OS. Called Verizon, they're sending me a reconditioned phone. Hopefully it isn't as bad as it sounds...
Click to expand...
Click to collapse
Please take this kindly...but you need to do ALOT more research before flashing anything on your device. There is no jelly bean bootloader, you have to unlock the stock bootloader so you can flash custom roms/kernels. If you fail this step, then you get a soft brick. Please read the stickies in dev section.
N0wy0ud1e said:
Thought so, a friend pointed it out for me. Apparently I forgot to put on a Jelly Bean bootloader of some kind, which resulted in this. I didn't fully pay attention to the fact that the Liquid ROM I installed was a Jelly Bean OS. Called Verizon, they're sending me a reconditioned phone. Hopefully it isn't as bad as it sounds...
Click to expand...
Click to collapse
Wow. Just wow. Never thought I would say it, but I actually feel bad for Verizon for having to replace your phone due to you not researching things.
N0wy0ud1e said:
Thought so, a friend pointed it out for me. Apparently I forgot to put on a Jelly Bean bootloader of some kind, which resulted in this. I didn't fully pay attention to the fact that the Liquid ROM I installed was a Jelly Bean OS. Called Verizon, they're sending me a reconditioned phone. Hopefully it isn't as bad as it sounds...
Click to expand...
Click to collapse
I'd buy your "bricked one". With a little work you could have prevented this.
Sent from my SCH-I535 using xda app-developers app
It makes one wonder why verizon decided to lock the bootloader.
jtiger12 said:
It makes one wonder why verizon decided to lock the bootloader.
Click to expand...
Click to collapse
Well it surely couldn't be because of all the warranty fraud :/
Sent from my htc_jewel using Tapatalk 2
bobloblaw1 said:
Well it surely couldn't be because of all the warranty fraud :/
Sent from my htc_jewel using Tapatalk 2
Click to expand...
Click to collapse
Lulz
bobloblaw1 said:
Well it surely couldn't be because of all the warranty fraud :/
Sent from my htc_jewel using Tapatalk 2
Click to expand...
Click to collapse
Warranty fraud? You mean where someone breaks their phone by improperly flashing something onto it, then lies to Verizon to get the phone replaced at Verizon's expense? That NEVER happens.:silly:
what does "not turn on" mean
I flashed LIQUIDSMOOTH - Gaps and the awsome Koontz kernel a few days ago and my phone won't reboot. I have no idea what happened (My battery might have run down durring the install. The primary symptom is -- It doesn't "turn on" and I can't get to CWM recovery but I can get to Samsung download mode. Home, Power Vol down opens Samsung download mode.
I was a click away from sending it off to the fixer (Don't want to report another one lost or stolen) -- The fix costs $100+ and I would be without my device for at least 1 week.
I have been researching solutions for 2 days and while it has been time consuming and has taken time away from the family, I think I will be able to un-brick, re-root, flash an AOKP or AOSP ROM + the KT747 (I think thats the name) and be up and running in an hour or two....
Not all bricks are lack of research
tomc99999 said:
I flashed LIQUIDSMOOTH - Gaps and the awsome Koontz kernel a few days ago and my phone won't reboot. I have no idea what happened (My battery might have run down durring the install. The primary symptom is -- It doesn't "turn on" and I can't get to CWM recovery but I can get to Samsung download mode. Home, Power Vol down opens Samsung download mode.
I was a click away from sending it off to the fixer (Don't want to report another one lost or stolen) -- The fix costs $100+ and I would be without my device for at least 1 week.
I have been researching solutions for 2 days and while it has been time consuming and has taken time away from the family, I think I will be able to un-brick, re-root, flash an AOKP or AOSP ROM + the KT747 (I think thats the name) and be up and running in an hour or two....
Click to expand...
Click to collapse
was running clean rom, went to jelly beans V15,, after a few weeks battery drain was bad reflashed all was ok,, then went to flash carbon rom and same issue, cant reboot, cant do anything, battery pull and Vol up with power and home does nothing.. seems samsung also has a motherboard flaw that shorts out. not rom related but i am sure all the rebooting is not helping. around 150-200 reboots it dies,.,. xda has a whole write up on it. so maybe the people worried they researched to little might have been doing it right and the junk portion of the phone gave out. I will take my replacement thank you very much. call it warantee fraud if you will but if its not software related it not from a bad flash.. those you can recover from, odin or one click should save your bacon. A fried pico or micro fuse or other bad part is different.
Alright, I'm hoping I can get some quick useful feedback on this. I'm currently on AOKP Official Milestone 6, and every time I reboot it reverts me settings I had on August 28th. I've been going thru this all day long, Google searching, scanning forums for our device and the T989.
I've attempted Odin flashes 13 times today to go back to Stock Gb and Stock Ics, the flashes show successful, yet AOKP boots right back up. Recovery does nothing to wipe, currently on Clockworkmod Touch Recovery.
Formatting all caches and partitions, Dalvik wipes all 5x each do nothing, even flashing something after this does nothing. I can't even reset AOKP, it takes me right back to the same condition from August 28th, same theme, apps, etc, all there. I've even formatted both emmc and sdcard, nothing. Whatever I do gets overwritten to the previous condition.
Can someone please help me out with this. I'm not even sure what to classify an issue like this as.
Sent from my SGH-I727 using xda premium
you are not the only one who had this issue, its a failure to write to the nand, for the lack of a better word, i have some links in my ref sticky, 1st link in my sig, under the info section on other users who had this problem, one thing i don't think they tried is using adb to push files
edit: damn i forgot to add those posts to my sticky, i/ll search for them and post them up
EDIT: here is one , couldnt find the other one http://forum.xda-developers.com/showthread.php?t=1751338
Thanks a lot man, what exactly causes something like this to happen? Is it Galaxy specific?
Sent from my SGH-I727 using xda premium
KillaT21 said:
Thanks a lot man, what exactly causes something like this to happen? Is it Galaxy specific?
Sent from my SGH-I727 using xda premium
Click to expand...
Click to collapse
it seems to be a ram hardware failure, but unless i had the problem myself, cant rule out user error, dev's write and wipe the phones constantly, and ive only seen it happen to two users.
read this http://forum.xda-developers.com/showthread.php?t=1704646 and see if it applies to you.
or you can try to push files through adb if phone accepts an adb connection, never tried it so cant help you there
vincom said:
it seems to be a ram hardware failure, but unless i had the problem myself, cant rule out user error, dev's write and wipe the phones constantly, and ive only seen it happen to two users.
read this http://forum.xda-developers.com/showthread.php?t=1704646 and see if it applies to you.
or you can try to push files through adb if phone accepts an adb connection, never tried it so cant help you there
Click to expand...
Click to collapse
I don't think it applies 100% to me. I can write to system, it just gets ignored lol. I read that Mightyoj had the exact issue and adb did nothing for him. I'm within my 30 days, I may need to either find another way to hard brick it or call at&t like he did.
Regardless, thanks for your help Vincom.
Sent from my SGH-I727 using xda premium
Your phone got "lost" / "stolen"
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2
vincom said:
or you can try to push files through adb if phone accepts an adb connection, never tried it so cant help you there
Click to expand...
Click to collapse
I remember this issue. The guy who's post you linked to did try adb to no luck. The only thing I can think to try through adb is changing the permissions of emmc? Some one with more knowledge then me might chime in but I'd say
Code:
adb shell
chmod 666 /emmc
That should give read/write to emmc if it will stick. Again you might want to get confirmation on this before attempting it as it is my best guess for your issue. If it's a bad nand you may just be SOL.
Illnevertell said:
Your phone got "lost" / "stolen"
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2
Click to expand...
Click to collapse
There's a thought...hmm
Sent from my SGH-I727 using xda premium
All right, after a few weeks of headache, I thought I'd update this thread as to whats going on.
Sent my phone off to Samsung twice for a fix. Twice due to the support rep not having any clue what the issues were that I was describing to her the first time over, so they sent it back in the same condition as when I sent it to them. Their solution: Applied stock SW.
They didnt even attempt to turn it on to see if the issue was resolved. So fast forward to 3 days after receiving it back and I called Samsung back and carefully worded my problem again and pointed out that I sent it to them before and no solution was found.
So I sent it back off, and 3 days later they called me asking me what exactly was wrong with my phone and I mentioned that it was some issue with the internal memory upon boot that locked everything into a specific setting from August 28th, and that it must be hardware related. She said she would inform the technicians.
So finally, I got my service ticket and the solution they reached was:
Replaced PBA, which is the Print Board Assembly. Looked around on Xda and for the definition and found that a few Samsung devices that were having similar issues as myself and a few others were remedied by replacing it. Currently waiting on them to reship it to me.
So, the "moral" of the story is, if you are within your Manufacturers warranty with Samsung, give Support a call and try as best as you can to explain your problem to them, but dont let them know you're rooted. They are not "supposed" to troubleshoot/fix your issue when rooted. But when they get hands on, they know that the average person that roots would have likely reversed any software issues/damage aside from a brick.
Hopefully this tidbit of information can help future Androidians with Samsung Devices on whats going on and expedite their efforts for a solution. Thanks again to all that were involved
Sent from my SGH-I997 using xda premium
I just hard bricked my sgs3. FIRST TIME EVER!! I've been flashing roms,kernels, etc since the MyTouch3.
Little back story.....
I flashed the LSmooth - Linaro 4.2.1 Jelly Bean Rom with CWM6. I noticed that I could not find my nandroid backups. Searched XDA and saw a thread that stated that TWRP is compatible with 4.2.1 and it will move the internal /sdcard from /0 back to its original file location, etc, etc. I went to GooManager, downloaded the twrp.tar (d2vzw), then went to MobileOdin, loaded the .tar file and flashed.
BOOM!!! No power, DOA. dead ass!! :crying::crying:
(( FACE SLAP )) then I remembered via build.prop it was configured as "maguro" and not "d2vzw". So, I'm assuming that since I failed to edit the build.prop before flashing the d2vzw TWRP recovery, it bricked my phone.
-- No power via wall, usb
-- No download / recovery mode
-- NOTHING!
My question is, if I were to call in and ask for a warranty exchange, what is the likely hood of Verizon troubleshooting, reviving my phone and figuring it out that its been rooted?
Or, should I just send my phone to someone that can JTAG it for me?
Idk if you're permanently hard bricked. Reason being is because this person flashed the latest twrp using GooManager but it installed the Maguro version. Different method but they were able to get out of it. Have you tried pulling the battery then booting holding all three buttons for like 15-20 seconds? Might take a few tries.
Verizon could care less I think.
I have had three droid razrs replaced just because of a boot loop and if they would look into the memory, they could clearly see I rooted if.
Sent from my SCH-I535 using xda app-developers app
SlimSnoopOS said:
Idk if you're permanently hard bricked. Reason being is because this person flashed the latest twrp using GooManager but it installed the Maguro version. Different method but they were able to get out of it. Have you tried pulling the battery then booting holding all three buttons for like 15-20 seconds? Might take a few tries.
Click to expand...
Click to collapse
I saw that post, lol. I tried that, but I will try it again. thanks
barrackOBAMA said:
Verizon could care less I think.
I have had three droid razrs replaced just because of a boot loop and if they would look into the memory, they could clearly see I rooted if.
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
Cool! Thanks!
MOD Close Thread, pls
MOD,
Can you close this thread please. Got my replacement today, so I'm Good.!!
I am not trying to place blame on anyone here I only want others to be aware of this. I know of one other guy who bricked his in the 4.2 AOKP Unofficial thread. I am not sure what this guy did.
This is exactly what I did.
Coming from the UCLL3 DeOdexed I rebooted to CWM v6.0.2.7.
Wiped and or formatted cache/system/data/dalvik accordingly.
Flashed the ROM (after previously checking MD5SUM), it seemed to go okay.
Flashed SuperSU v1.04 (MD5SUM checked and used before)
Flashed 12/20/2012 GApps (MD5SUM checked and I had flashed on two other JB CM ROMs), looking back I should have known right then something was wrong because it seemed to take longer than it should have.
Flashed JustunBean’s Aroma (themes only and had flashed that on at least two other ROMs)
Tried to flash MrMad’s TW Add on v1.3.3 (which I used on two other CM10.1 ROMs)
That is where things went bad. CWM came back saying something to the effect of “some errors cannot be overlooked” I said “WHAT”? I tried to flash it again with the same error.
I then tried to reboot system. No signs of life. No Samsung Logo.
After pulling battery and trying to boot again I pulled the battery again then hooked it up to pc. That is where I got windows needs to install drivers for your device “DHSUSB_DLOAD”.
I am looking into getting it fixed at MobileTechVideos.
Like I said not blaming anyone just letting people know that it can happen. This may be my first post and I am no Pro or a Dev but I have been flashing on the Skyrocket for almost two years to the day. I admit I am a Flash-Aholic.
Clarification. Nearly two years to the day plus or minus six or seven months
I've seen this error on other devices and it happens when some one flashes a international ROM on a north american phone. I'm not say that's what u did. only way to fix is jaytag. you wrote over the partition that communicates with the CPU.
It also happened to me when I flashed the AOKP 4.2 couple days ago and my phone just replaced by AT&T under warranty. Below is what I learned might result in this:
-Wipe internal SDcard in recovery
-Flash ROM at low battery level (was about 40%)
ka724ka said:
It also happened to me when I flashed the AOKP 4.2 couple days ago and my phone just replaced by AT&T under warranty. Below is what I learned might result in this:
-Wipe internal SDcard in recovery
-Flash ROM at low battery level (was about 40%)
Click to expand...
Click to collapse
that wouldnt do it, but since you and op flashed aokp4.2 could be something within the rom that did it or internal ram failure, or it could be user error
xstokerx said:
I've seen this error on other devices and it happens when some one flashes a international ROM on a north american phone. I'm not say that's what u did. only way to fix is jaytag. you wrote over the partition that communicates with the CPU.
Click to expand...
Click to collapse
It was the ROM for the skyrocket out of the Skyrocket thread. Thanks for the info though.
[/QUOTE] ka724ka It also happened to me when I flashed the AOKP 4.2 couple days ago and my phone just replaced by AT&T under warranty. Below is what I learned might result in this:
-Wipe internal SDcard in recovery
-Flash ROM at low battery level (was about 40%)
[/QUOTE]
Thanks for the info. I did not wipe internal SD although I have wiped internal SD many times before and battery was over 90%.
[/QUOTE] vincomthat wouldnt do it, but since you and op flashed aokp4.2 could be something within the rom that did it or internal ram failure, or it could be user error
[/QUOTE]
Thank you for the info. I hope it was not user error I took the same steps and procedures for all the ROM flashes that I have flashed and I have flashed many a ROM. I hope it is not RAM problems because I plan to get it Jtag-ed so my son can use it. The Skyrocket is an awesome phone.
One question. Why would you try to root the phone again after installing aokp zip?
Sent from my SAMSUNG-SGH-I727 using xda app-developers app
xstokerx said:
I've seen this error on other devices and it happens when some one flashes a international ROM on a north american phone. I'm not say that's what u did. only way to fix is jaytag. you wrote over the partition that communicates with the CPU.
Click to expand...
Click to collapse
holeindalip said:
One question. Why would you try to root the phone again after installing aokp zip?
Sent from my SAMSUNG-SGH-I727 using xda app-developers app
Click to expand...
Click to collapse
Some developers use SuperUser and I prefer SuperSu so I flash the SuperSU file that I have.
CodeNameRedNeck said:
Some developers use SuperUser and I prefer SuperSu so I flash the SuperSU file that I have.
Click to expand...
Click to collapse
could u not have just deleted superuser then downloaded supersu from the market?
You could do that or just flash it while you are already there.
why woul you flash the SUperSU when all you have to do is download the app from market and click switch and reinstall superSU doesnt mess with any of the files tha could cause this issue
Well given many others have dl'd installed and successfully used aokp I'm going with user error.
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2
mtdew said:
Well given many others have dl'd installed and successfully used aokp I'm going with user error.
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2
Click to expand...
Click to collapse
Yes thank you mtdew. With just about 250 downloads of the 4.2.1 ROM and 60 of the 4.2.2 I would have to agree with that.
I'm sorry that it has happened while trying to use my ROM, it is in no way intentional.
You do however root, flash ROMs at your own risk. Its a chance you take and sometimes things like this do happen.
Thanks
Toyes
Sent from my SGH-I727 using Tapatalk 2
I also recently had experience with qhsusb download but unofficial aokp port and just for future reference jtags are not always the solution; mobiltech repairs was unable to unbrick it through JTAG as the onboard emmc controller was unresponsive and I'm currently waiting for a repair through samsung; it gave me a new respect of the dangers of flashing.
killablack said:
I also recently had experience with qhsusb download but unofficial aokp port and just for future reference jtags are not always the solution; mobiltech repairs was unable to unbrick it through JTAG as the onboard emmc controller was unresponsive and I'm currently waiting for a repair through samsung; it gave me a new respect of the dangers of flashing.
Click to expand...
Click to collapse
Erm.. You should change your user name dude..
Ladies and Gents,
I made sure I chose the correct RUU based on my CID (CWS__001)
I relocked my phone and attempted to install "RUU_EVITA_UL_JB_45_S_Cingular_US_3.18.502.6_Radio_ 0.24p.32.09.06_10.130.32.34_release_signed.exe". After the RUU finished my phone seems to be hard bricked.
Won't Boot.
No power lights.
I knew this could happen when flashing an international version. AFTER getting owned I also found this post http://forum.xda-developers.com/showthread.php?t=2181929. Which was blatantly in the beginning of the forum. Has anyone found a fix for this issue, or is my only option JTAG repair?
Thanks,
Ryan
ryan9316 said:
Ladies and Gents,
I made sure I chose the correct RUU based on my CID (CWS__001)
I relocked my phone and attempted to install "RUU_EVITA_UL_JB_45_S_Cingular_US_3.18.502.6_Radio_ 0.24p.32.09.06_10.130.32.34_release_signed.exe". After the RUU finished my phone seems to be hard bricked.
Won't Boot.
No power lights.
I knew this could happen when flashing an international version. AFTER getting owned I also found this post http://forum.xda-developers.com/showthread.php?t=2181929. Which was blatantly in the beginning of the forum. Has anyone found a fix for this issue, or is my only option JTAG repair?
Thanks,
Ryan
Click to expand...
Click to collapse
You could take your phone back and tell them it won't boot etc.
If you can't get it to boot neither can they, so no-one will know it's been unlocked/rooted.
Some people will say this is fraudulent, but hey, if you can live with yourself who cares what anyone else thinks?
Pft I returned mine to Telus when the same thing happened to me. The way I see it, it was HTC's RUU that bricked my phone, not me. Like you, I did not have supercid and was S-ON.
You could try the unbrick Evita thread. If you make it past step 3 you can save your phone.
You'll need to boot to Linux.
Sent from my One X using xda app-developers app
exad said:
Pft I returned mine to Telus when the same thing happened to me. The way I see it, it was HTC's RUU that bricked my phone, not me. Like you, I did not have supercid and was S-ON.
You could try the unbrick Evita thread. If you make it past step 3 you can save your phone.
You'll need to boot to Linux.
Sent from my One X using xda app-developers app
Click to expand...
Click to collapse
I saw this and will give it a try, thank you for the advice!
ryan9316 said:
I saw this and will give it a try, thank you for the advice!
Click to expand...
Click to collapse
I bricked my phone trying to install elementalx and phone wouldn't boot at all and no lights. sent it in for jtag and they told me emmc controller was unresponsive and sent it back to me. looks like I may have to trash the phone... or make a few bucks on ebay.
mkalbarc said:
I bricked my phone trying to install elementalx and phone wouldn't boot at all and no lights. sent it in for jtag and they told me emmc controller was unresponsive and sent it back to me. looks like I may have to trash the phone... or make a few bucks on ebay.
Click to expand...
Click to collapse
Did they refund you? I was going to send it into mobiletechvideos for JTAG. I don't see the phones selling for more than 100$ on ebay.
ryan9316 said:
Did they refund you? I was going to send it into mobiletechvideos for JTAG. I don't see the phones selling for more than 100$ on ebay.
Click to expand...
Click to collapse
If the emmc controller isn't responding, it's worth even less than that.
Sent from my One X using xda app-developers app
ryan9316 said:
Did they refund you? I was going to send it into mobiletechvideos for JTAG. I don't see the phones selling for more than 100$ on ebay.
Click to expand...
Click to collapse
they did refund. minus the cost of shipping and something else, however. it was worth a try though... All I know though is I will never touch an elemental kernel again... not worth it that's for sure...
mkalbarc said:
they did refund. minus the cost of shipping and something else, however. it was worth a try though... All I know though is I will never touch an elemental kernel again... not worth it that's for sure...
Click to expand...
Click to collapse
Just curious about your situation. Did the kernel flash successfully and then just not boot? What ROM were you flashing it over? Tons of people, myself included, have flashed that kernel without issue so I'm interested in what exactly happened.
pside15 said:
Just curious about your situation. Did the kernel flash successfully and then just not boot? What ROM were you flashing it over? Tons of people, myself included, have flashed that kernel without issue so I'm interested in what exactly happened.
Click to expand...
Click to collapse
Sure, I too have used their kernels and have never had an issue until this time. So I started to install the kernel and it froze at I believe 60%? Then it sat... It said the flash could take awhile so to just wait so I did... For 2 hours. I knew something wasn't right because no elemental flash has taken my phone longer than a few minutes before this one so without thinking i'd hurt anything I held the buttons to hard power off the phone. After it shut off it's been completely dead since. No charge lights, no sign of any life at all other then the QHSUSB_DLOAD under device manager when plugged into my PC. the rom that I had flashed was the latest cleanrom. super bummed but i'll get over it. the worst part about this was I had pics of my kids that I had not backed up that are now lost.
mkalbarc said:
Sure, I too have used their kernels and have never had an issue until this time. So I started to install the kernel and it froze at I believe 60%? Then it sat... It said the flash could take awhile so to just wait so I did... For 2 hours. I knew something wasn't right because no elemental flash has taken my phone longer than a few minutes before this one so without thinking i'd hurt anything I held the buttons to hard power off the phone. After it shut off it's been completely dead since. No charge lights, no sign of any life at all other then the QHSUSB_DLOAD under device manager when plugged into my PC. super bummed but i'll get over it. the worst part about this was I had pics of my kids that I had not backed up that are now lost.
Click to expand...
Click to collapse
That does suck about the pictures. That would upset me more than the phone as well. I went and looked at the thread after I saw your post and saw a couple of other bricks aside from yours in the last couple of hundred posts. Very unfortunate that flashing a kernel bricked it. I try to stay away from anything that uses the Aroma Installer unless there are no other options, not saying that was the problem, but I've had numerous issues with it previously. After seeing multiple bricks from a basic kernel flash I'm going to definitely be more cautious about what I flash from now on. I'd be totally screwed if I bricked this phone. Anyway, hope you end up with something better out of this, like the HTC One.
pside15 said:
That does suck about the pictures. That would upset me more than the phone as well. I went and looked at the thread after I saw your post and saw a couple of other bricks aside from yours in the last couple of hundred posts. Very unfortunate that flashing a kernel bricked it. I try to stay away from anything that uses the Aroma Installer unless there are no other options, not saying that was the problem, but I've had numerous issues with it previously. After seeing multiple bricks from a basic kernel flash I'm going to definitely be more cautious about what I flash from now on. I'd be totally screwed if I bricked this phone. Anyway, hope you end up with something better out of this, like the HTC One.
Click to expand...
Click to collapse
Funny thing about the One... I was thinking about getting it but after this issue I will never look at another phone that doesn't have a removable sd card...
I think a key thing to note here is that you are flashing software that has been altered by someone you don't know and you can never be sure that things will work out. There's huge risks associated with rooting/unlocking your phone. If there wasn't HTC would warrant your phone regardless of what you do.
If you don't have an answer to the question "What will I do when I brick my phone?" don't root. Whenever modding anything, consoles, phones, set top boxes, I always assume that I will render it unusable. If that doesn't sit well with me, I don't modify it. That should be the general rule of thumb to follow.
Sent from my One X using xda app-developers app
3 words: Dropbox Camera Upload.
exad said:
I think a key thing to note here is that you are flashing software that has been altered by someone you don't know and you can never be sure that things will work out. There's huge risks associated with rooting/unlocking your phone. If there wasn't HTC would warrant your phone regardless of what you do.
If you don't have an answer to the question "What will I do when I brick my phone?" don't root. Whenever modding anything, consoles, phones, set top boxes, I always assume that I will render it unusable. If that doesn't sit well with me, I don't modify it. That should be the general rule of thumb to follow.
Sent from my One X using xda app-developers app
Click to expand...
Click to collapse
Very well said... I always get a little nervous when screwing with a new $500+ device.
Sent from my HTC One X using xda app-developers app
iElvis said:
3 words: Dropbox Camera Upload.
Click to expand...
Click to collapse
Thank you for the advice! I will remember that with my next phone.
I just use g+ to instantly upload my photos. Unlimited space is hard to argue with
Sent from my One X using xda app-developers app
phone not able to boot
guys please help me out I flashed stock root JB ROM after that my device wont boot just white screen with HTC logo. The phone boots into recovery but I wiped the sd card SD card mount error is being returned.
Clockworkmod recovery v6.0.3.1 S off
anuj.sherawat said:
guys please help me out I flashed stock root JB ROM after that my device wont boot just white screen with HTC logo. The phone boots into recovery but I wiped the sd card SD card mount error is being returned.
Clockworkmod recovery v6.0.3.1 S off
Click to expand...
Click to collapse
Install twrp 2.3.3.1 and reformat sd card with a pc. Move Rom to sd and reflash. And also what hboot? I know you said s-off bit did you fastboot the boot.img and see is that helped?
Sent from my HTC One X using xda app-developers app
31ken31 said:
Install twrp 2.3.3.1 and reformat sd card with a pc. Move Rom to sd and reflash. And also what hboot? I know you said s-off bit did you fastboot the boot.img and see is that helped?
Sent from my HTC One X using xda app-developers app
Click to expand...
Click to collapse
thanks first of all I was on CMW, formatted the drive as computer prompted, lost the data but was able to flash the ROM and fastboot the boot image to phone.
Now only one problem the phone restarts and then goes to boot loop everytime I have to fastboot the boot image file.
DO I need to change the recovery and is there any way to by pass the fastboot process? Sorry for noob question