please see the second and third posts on this page:
http://forum.xda-developers.com/showthread.php?t=1513583&page=8
any help would be greatly appreciated. Thanks
What OS do you have on your computer?
Win 7, 64 bit. Tried on both laptop and desktop (same os)
Have you found/tried Adam outler's thread on fixing bricks?
It's stickied in the development section.
Sent from my SGH-T959V using xda app-developers app
I had glanced at it before but was under the impression the computer had to be running ubuntu. Now that I've completely read it I see that's not the case. I will give it a shot later tonight. Thanks.
ok i put adams image file on the card and put the card in and ran it for about 6 hours. the screen still said something about factory settings. i cut it off at this point because i got a little impatient and tried to restart it and now i'm locked in the "n" screen boot loop. i reflashed the card and am trying it again now but its been running for about an hour already and is still in the "writing zeros to mlo" phase. why is this process taking so long? i'll post back with more results tonight...
edit: wow its actually chugging along right after i wrote that. in the past 5 minutes, it got all the way up to step 9, writing all zeros to system. might write back sooner than tonight. *fingers crossed*
Edit 2: well I let it run for a couple hours and it never moved from writing zeros to system. Then the battery ran out. Restarted the whole process and its been at that same step for hours again. I'm keeping it plugged in this time though. Any ideas?
no dice. i let run for hours and it seems to just hang. now when i start the nt i only get the "n" screen and it keeps restarting.
pournstarr said:
no dice. i let run for hours and it seems to just hang. now when i start the nt i only get the "n" screen and it keeps restarting.
Click to expand...
Click to collapse
You could try running the repart.img once again even if you already did it before you did the other stuff. Probabaly won't work, but it's worth a try! The reason I say this is when I messed up mine that's how it looked for me and the repart.img did the trick. Obviously mine wasn't as badly messed up, but still... After all, what do have to lose?
pournstarr said:
ok i put adams image file on the card and put the card in and ran it for about 6 hours. the screen still said something about factory settings. i cut it off at this point because i got a little impatient and tried to restart it and now i'm locked in the "n" screen boot loop. i reflashed the card and am trying it again now but its been running for about an hour already and is still in the "writing zeros to mlo" phase. why is this process taking so long? i'll post back with more results tonight...
edit: wow its actually chugging along right after i wrote that. in the past 5 minutes, it got all the way up to step 9, writing all zeros to system. might write back sooner than tonight. *fingers crossed*
Edit 2: well I let it run for a couple hours and it never moved from writing zeros to system. Then the battery ran out. Restarted the whole process and its been at that same step for hours again. I'm keeping it plugged in this time though. Any ideas?
Click to expand...
Click to collapse
What do people have against plugging in the Charger to fix their brick issues? You are only exacerbating the problem when you run out of power and the nook tablet won't come back on, if at all, until at 15% power level? Adam's method can take overnight to complete. Don't be impatient. Haste makes waste.
When this happened to me using Adams method, it was a messed up partition table.Celtic has a simple fix for that.I would then try the repart image solution.If you use Adams method without backing up the ROM, you won,t ever be able to register with BN again.
Sent from my NookTablet using xda app-developers app
asawi said:
You could try running the repart.img once again even if you already did it before you did the other stuff. Probabaly won't work, but it's worth a try! The reason I say this is when I messed up mine that's how it looked for me and the repart.img did the trick. Obviously mine wasn't as badly messed up, but still... After all, what do have to lose?
Click to expand...
Click to collapse
thanks but already tried that. now it seems like nothing is recognized on the card except for adams files or the cwm 5028 files. anything else i put on there just makes it go through the "n" screen bootloop.
hwong96 said:
What do people have against plugging in the Charger to fix their brick issues? You are only exacerbating the problem when you run out of power and the nook tablet won't come back on, if at all, until at 15% power level? Adam's method can take overnight to complete. Don't be impatient. Haste makes waste.
Click to expand...
Click to collapse
yea the thing is in his post, adam says it should take about 15 mintues to complete. i was at full charge, so didn't see the need to plug it in. after that first time, i've left it plugged in every time i've tried to use it and let it sit for 6-8 hours at a time and its still not finished.
sailerph said:
When this happened to me using Adams method, it was a messed up partition table.Celtic has a simple fix for that.I would then try the repart image solution.If you use Adams method without backing up the ROM, you won,t ever be able to register with BN again.
Click to expand...
Click to collapse
i have the parted text file, but no way to push it to the device since adb doesn't recognize there is anything hooked up to my computer. celtic does say you can put it on an sd card, but once in cwm, how do you process a text file from the sd card?
Related
Sorry. Duplicate subject.
http://www.androidpolice.com/2012/0...or-16gb-nook-tablet-users-beginning-in-march/
.....
but will they install cm7 for me?
I'm curious if anyone decided to take their nooks in to get them repartitioned. Also curious how it worked out for anyone who did.
I had mine done yesterday... it was a complete img flash... so anything you might have on the internal memory will be gone, anything sideloaded... it took about 20 minutes as it has to be deregistered and brought back to original new status.. then then flash is done.. then it has to go through all that again...
I asked how much I was getting back.. 8GB ... so they split the 16GB between them and you...
Had to reinstall everything I had sideloaded and figure out where I was in a book .. OH lost all my achievements in the different Angry Birds... LOL
Got home and put my CM7 mSD disk in... booted up fine
RickyT26 said:
I had mine done yesterday... it was a complete img flash... so anything you might have on the internal memory will be gone, anything sideloaded... it took about 20 minutes as it has to be deregistered and brought back to original new status.. then then flash is done.. then it has to go through all that again...
I asked how much I was getting back.. 8GB ... so they split the 16GB between them and you...
Had to reinstall everything I had sideloaded and figure out where I was in a book .. OH lost all my achievements in the different Angry Birds... LOL
Got home and put my CM7 mSD disk in... booted up fine
Click to expand...
Click to collapse
Great to hear you were pleased with the results. I assume you were running B&N ROM, with CM7 via SDCard.
I am internally debating handing my baby over to them, using the xda method, or leaving things be.
Swyped from NT CM7.1.Alpha Final using XDA Premium
That is great to hear cuz I am so mixed up with the repartitioning on my own. Did you go in with 1.40 or 1.41 and did you walk out with 1.42? Do they do it right away or do you have to come back later and pick it up? I guess I want to make sure I get the same tablet back.
SCClockDr said:
Great to hear you were pleased with the results. I assume you were running B&N ROM, with CM7 via SDCard.
I am internally debating handing my baby over to them, using the xda method, or leaving things be.
Swyped from NT CM7.1.Alpha Final using XDA Premium
Click to expand...
Click to collapse
Yes.. running the CM7 using the mSD version...
When I got the Nook Tablet (Christmas gift).. they paid for 2 year warranty.. so in a few years.. I will probably just move it to internal.. just want to keep the warranty that was bought and not have them have wasted the $...
I rarely boot into BN... loving CM7
2013 class said:
That is great to hear cuz I am so mixed up with the repartitioning on my own. Did you go in with 1.40 or 1.41 and did you walk out with 1.42? Do they do it right away or do you have to come back later and pick it up? I guess I want to make sure I get the same tablet back.
Click to expand...
Click to collapse
I had 1.4.2 on the Nook.. it came back with the same... I walked in went to the Nook desk told her what I wanted.. then sat right next to the her while she did the steps on a sheet of paper and the mSD with the img on it.. like I said.. I think it took about 20 minutes.. maybe less.. overall was pleased with it.. would have liked more back. lol but oh well 8 is better than 1
I recommend just doing the xda way. As another user mentioned already, they do a factory reset on your device, so it takes out all your content. If you do it yourself, you can atleast restore your data. What seems to happen is that, they do a factory reset, turn off the device, put their sd card in, and then boot via the cable connected to a wall adapter not by powering on the device normally.
Re-partitioned mine on Monday morning
StridAst said:
I'm curious if anyone decided to take their nooks in to get them repartitioned. Also curious how it worked out for anyone who did.
Click to expand...
Click to collapse
I was not asked for a receipt or anything. I was told to come back in 20 minutes. When I returned 20 minutes later, I was asked if I had a 8 GB Nook Tablet or a 16 GB tablet. I told them it was a 16 GB tablet. I was again told to come back 20 minutes later.
I watched the desk where my Nook was undergoing surgery and saw a female employee take over from the guy that had been working on it. About 15 minutes later she asked me to log into my B and N account. She continued for a minute or so then told me it was done. She also took me to the "Settings" page and showed me the new settings. I had 5.91 GB for B&N content and 7.99 of 8 GB available for "other storage available".
All in all a painless procedure. My NT was taken in completely stock and unrooted.
RickyT26 said:
I had 1.4.2 on the Nook.. it came back with the same... I walked in went to the Nook desk told her what I wanted.. then sat right next to the her while she did the steps on a sheet of paper and the mSD with the img on it.. like I said.. I think it took about 20 minutes.. maybe less.. overall was pleased with it.. would have liked more back. lol but oh well 8 is better than 1
Click to expand...
Click to collapse
To bad there was no way we could get a hold of that mSD so the devs could work with the image so we could do it ourselves that way.
Update
My wife works at B&N and is doing the memory update to hers today. She works mainly with the Nook sales and will be trained how to do the upgrade. I'll post the results later... hmm... wonder if the zip drive is with her.
I've been debating trying to do the repartition the xda way myself or take it into B&N. Not sure my skills are up to the xda way but want to make sure I can re-root it I get it back.
Did you get your NT back with version 1.4.2 and were you able to root it easily?
Thanks,
Nikkie
NikkieL said:
I've been debating trying to do the repartition the xda way myself or take it into B&N. Not sure my skills are up to the xda way but want to make sure I can re-root it I get it back.
Did you get your NT back with version 1.4.2 and were you able to root it easily?
Thanks,
Nikkie
Click to expand...
Click to collapse
I went to B&N to do it last tuesday. process was smooth, but it did update it to 1.4.2. I also unrooted my device prior to taking it there (after backing up with CWM of course). When I took it in, I was at 1.4.0 unrooted with the stock recovery flashed, not cmw
After leaving there. I popped my cm7 sd card in, ran the app to flash CWM to internal then flashed my CWM backup. and poof, I am back to CM7 running on my sd card, and rooted 1.4.0 internal. Quite simple really.
Now I just hope someone works out a SD card version of the B&N firmware so I can put that on the sd card, and put the CM7 internal....
The advantage of the XDA way is that you decide the size of your partitions and save the extra time recovering everything, even CWM.
~ Veronica
Sent from my Nook Tablet using xda premium
here is the boot image from the B & N mSD card for the partitioning of the 16gb Tablet.
Had mine done this morning. It took less than 10 minutes.
I had mine repartitioned this past weekend. I originally was running 1.4.0 with root by Indirect and decided I wanted to stay stock and play with CM7 on SD. I backed up a few files, then did a factory reset to unroot and took it in. It took them about 15 minutes. So now I'm completely stock internally (with a bigger partition), and I'm playing with CM7 on SD.
I took my nook into the local B&N today and had the repartition done. Used CWM stock recovery and nook unroot to return to factory settings before I took it in. Went in with 1.4.2. and the whole process went very quickly and smoothly. No one asked for receipts or checked for evidence of past rooting or even asked many questions at all. All I had to do was re-register when it was all over. When I got home, I rooted again using Albert Wertz's newest rom (4.6) and again, everything worked perfectly. I'm now rooted on 1.4.2 with the new partition sizes. Couldn't have gone better.
so I was trying to update the RUU when i did that i put a coustom rom too .. my htc booted up perfectly but ever time i touch an app it would just start shut down the phone when i was try to fix problem by just Using the new RUU i couldnt get in to hboot or turn on my phone
OK first your phone is not a brick. A brick is just that, a brick. It doesn't turn on at all.
Next did you allow the RUU to run fully? Meaning did you allow it to update the hboot, reboot and then finish the update?
Sent from my VIZIO tablet using xda premium
Sounds like it only ran the first set of updates. Run the RUU again and it will update everything else.
it wont turn on i check the battery with my dad's htc rezound i was trying to get back to hboot but phone wont turn on any help pls
Plug your phone in and remove the battery. Then boot into hboot.
Sent from my VIZIO tablet using xda premium
no luck it wont turn on
Did you try holding volume down while pressing power?
Sent from my ADR6425LVW using xda premium
Continue to hold volume down until it hits the boot screen. You shouldn't have to hold it that long, but it won't hurt.
Sent from my ADR6425LVW using xda premium
EmerikL said:
OK first your phone is not a brick. A brick is just that, a brick. It doesn't turn on at all.
Click to expand...
Click to collapse
I was just about to say that.
not bricked
It doesn't sound like you are bricked, just that the RUU didn't fully take. First, take your removable SD card and connect it to your computer. If you don't have a microSD card reader on your computer, hit radio-shack or something and get a usb microSD card adapter, costs like $10 and is a life saver. Now backup everything on your SD card and then wipe the card clean and just put the RUU on, renamed to PH98IMG.zip. Make sure that you didn't make it PH98IMG.zip.zip or it won't work. Next put the SD card back into the phone, hopefully you still have it locked, and when you boot it, it should update properly. Remember that it has to flash twice, the first time it like only updates the bootloader and radios or something, the second time (after it reboots) it will completely flash the rest of the RUU.
I hope that helps.
Oh and one more important thing, after you flash the RUU and you are sure it is working properly, delete the PH98IMG.zip from your external SD card. You really don't want it there after the phone has flashed and everything is working properly.
tcinfantino said:
If you don't have a microSD card reader on your computer, hit radio-shack or something and get a usb microSD card adapter, costs like $10 and is a life saver.
Click to expand...
Click to collapse
A micro SD reader is an Android hacker's best friend.
It has saved me many times!
thanks everyone but it wont turn on even if i'm holding the power & vol button down i even try cmd reboot not respond to my rezound i just going to get a new one... last thing i was trying to do before this happen i was trying to get the sd card out with out turning out the rezound so i pulled the battery slow to her i could get the sd card i pulled it out and the battery came out to after that it never power back on
cflo360 said:
thanks everyone but it wont turn on even if i'm holding the power & vol button down i even try cmd reboot not respond to my rezound i just going to get a new one... last thing i was trying to do before this happen i was trying to get the sd card out with out turning out the rezound so i pulled the battery slow to her i could get the sd card i pulled it out and the battery came out to after that it never power back on
Click to expand...
Click to collapse
Take the battery out and unplug it from the computer. Let it sit for a few minutes and chill out.
Then, put the battery back in and press volume down and power and keep holding until you see the screen turn on. Then you should be in hboot.
I had the SAME problem. I tried loading a rom that required the new RUU when I was on the outdated one. I simply downloaded the new RUU, renamed it, and went into HBOOT. I noticed that you need to run it 2 times, oddly enough. After that, I was golden.
A Brick is a Brick my friend, paperweight.
cflo360 said:
thanks everyone but it wont turn on even if i'm holding the power & vol button down i even try cmd reboot not respond to my rezound i just going to get a new one... last thing i was trying to do before this happen i was trying to get the sd card out with out turning out the rezound so i pulled the battery slow to her i could get the sd card i pulled it out and the battery came out to after that it never power back on
Click to expand...
Click to collapse
Seriously I have never had a phone not boot have you tryed using your dads battery and deffinetly let it sit for a half hour without a battery or plunged into anything then try it again mabey you do got a brick but I doubt it
Sent from my ADR6425LVW using XDA
mined might be bricked like yours
im not trying to hijack your thread just looking for help alright here is where i start. I'm running the new leak, just flashed BAMF 2.0 a day or 2 ago. i have been updating roms regularly without a problem. i tried to flash Sebastian 1782 OC kernel. When i did i got a main ver error. I went into Sebastian thread and was reading where other people had problems with the main ver error and i did what was said to do to fix it. They said to open the android text file in the kernel and change the main ver to the same this i was running and to change the hboot to what i was running. So i did that. flashed into recovery and flashed the kernel. It flashes and then heres where i get a problem. It says reboot to bootloader to complete. The phone shuts down and thats it. It wont turn on. It wont do anything. i have pulled the battery and left it out for a few minutes and put it back in but nothing. I tried to charge it and the amber led wont even light up. What went wrong? I need help. This absolutely blows
You do no have it plugged in right the only time i had this problem when it was
If I power down it boots, starts loading, then reboots. not sure if that counts as a soft brick or not, but I've discovered a work around, if I re-root it using roloracer's instructions, and let it boot a few more times while plugged in, I can get it back, then I dare not cycle power. It's almost like a tethered jailbreak on the old iphone.
Anyway, I've been unsuccessful in finding anyone else mentioning this type of issue, so obviously it's never happened to anyone on the face of the planet before.
Does anyone have any links, search terms i may know have thought of, solutions?
I rooted a couple of weeks ago. Nothing is frozen, what I did freeze was on the list of thinks that were ok, and i un-froze it with TB.
Sorry, this is the AT&T Galaxy Note i717.
Thanks.
Do u have cwm? ? If so get into recovery and wipe cache see if that works post back ill help as much.as i can
Sent from my SAMSUNG-SGH-I717 using xda premium
I haven't installed cwm, nor anything beyond the rooting. I presume I should, then wipe the cache?
Install and flash clockwork mod recovery and then do a wipe BUT PLEASE make sure u have a back up before u do any wipes and changing Roms and such
Sent from my SAMSUNG-SGH-I717 using xda premium
Do you have any backups?
Sent from my SAMSUNG-SGH-I717 using xda premium
armyboy11b said:
Do you have any backups?
Sent from my SAMSUNG-SGH-I717 using xda premium
Click to expand...
Click to collapse
yes. I've now installed CWM and did a backup there, a rather lengthy one, as far as time goes.
I wiped the cache, with no positive effect. I ultimately wiped the dalvik cache, and now i simply get the AT&T boot screen. So I am now restoring my cwm backup, hoping at least I'll be back where I was.
As it stands now, or before I wiped the dalvik cache, which you did not mention so that may well be my error, I was in a loop. unable to connect via USB for any length of time. BUT I additionally have everything backed up, as far as apps, settings and my data seperately of the cwm backup.
I am considering trying the odin unroot process.
later that day:
I had to get some sleep I was falling asleep at my laptop. I reinstalled cwm, using the touch one here earlier this morning, I again wiped the cache, it still looped, I did another backup in cwm, then went to bed with it plugged in beside me after about 30 minutes I saw it was done, and I rebooted it, and left it, it rebooted once maybe more, but when I got up later it was up.
I'd intended to do all this today, but I accidentally had the power button resting on my finger and that began this early morning session. I have a phone back, but will wait before I intentionally cycle power again. I do have a number of flashes counted today that weren't there yesterday. i'll see about zeroing those out later.
In download mode it doesn't boot loop, so I do not think it's a hardware issue. But at least now it's up long enough to back it all up to my PC.
Thanks very much
that is cool
Man, being over 50 I can barely make out those image verifications!
So no one else has run across this with mashi/roloracer root? I did it exactly as it said to to a stock i717.
I'm going to wait to cycle power again, to test if it's fixed, when I know I will have a few hours to dedicate to trying to get it all back. I'd rather have it rooted and when an ICS ROM is out try that. Like I said I'm a complete android noob, but not to Unix/AIX/Linux, PC's or Macs. I had to do macs because no one else wanted to back in the `90's when apple was failing.
So is this a "soft brick" this boot looping?
Thanks again.
bigbuc said:
Man, being over 50 I can barely make out those image verifications!
So no one else has run across this with mashi/roloracer root? I did it exactly as it said to to a stock i717.
I'm going to wait to cycle power again, to test if it's fixed, when I know I will have a few hours to dedicate to trying to get it all back. I'd rather have it rooted and when an ICS ROM is out try that. Like I said I'm a complete android noob, but not to Unix/AIX/Linux, PC's or Macs. I had to do macs because no one else wanted to back in the `90's when apple was failing.
So is this a "soft brick" this boot looping?
Thanks again.
Click to expand...
Click to collapse
hey buddy sorry been realllll busy with work and such how did everything go are u all set? is it working let me know if u need help!!! as i said before sorry i didnt reply back man been very busy but please feel free to ask for help if u still need it
armyboy11b said:
hey buddy sorry been realllll busy with work and such how did everything go are u all set? is it working let me know if u need help!!! as i said before sorry i didnt reply back man been very busy but please feel free to ask for help if u still need it
Click to expand...
Click to collapse
Well, it's still acting kind of like a tethered boot. It takes a few hours of it cycling power, plugging in/ unplugging and suddenly it 'decides' to stay up. No one else has reported this issue that I have found. I've uninstalled several apps I suspected, like 'The Weather Channel', and anything else I can find that runs in the background by itself, that I don't need... It does it everytime I power down... so I never let it get below 5% before I run to plug it in... Battery life is kind of sucky anyway.
My PC healed itself regarding seeing the phone MTP style.
I wipe the cache, re-root it ala mashi/roloracer then it'll start to settle down some. Curious about UNrooting it, but not real clear on how that's done, as most instructions are in shorthand leaving out (to me) an obvious step here and there.
I'd rather have it rooted, I've bought titanium backup, and use a few others utils that require root.
If I installed a different ROM that might help... or might not... I'm fairly certain it's not the phone, at least not a 'short' type thing where it reboots on it's own... I SAY reboot, it's actually not rebooting since it doesn't show the samsung and at&t logo, it just reloads the UI.
Point me anywhere and thanks again. I clicked the 'thanky' button.
bigbuc said:
Well, it's still acting kind of like a tethered boot. It takes a few hours of it cycling power, plugging in/ unplugging and suddenly it 'decides' to stay up. No one else has reported this issue that I have found. I've uninstalled several apps I suspected, like 'The Weather Channel', and anything else I can find that runs in the background by itself, that I don't need... It does it everytime I power down... so I never let it get below 5% before I run to plug it in... Battery life is kind of sucky anyway.
My PC healed itself regarding seeing the phone MTP style.
I wipe the cache, re-root it ala mashi/roloracer then it'll start to settle down some. Curious about UNrooting it, but not real clear on how that's done, as most instructions are in shorthand leaving out (to me) an obvious step here and there.
I'd rather have it rooted, I've bought titanium backup, and use a few others utils that require root.
If I installed a different ROM that might help... or might not... I'm fairly certain it's not the phone, at least not a 'short' type thing where it reboots on it's own... I SAY reboot, it's actually not rebooting since it doesn't show the samsung and at&t logo, it just reloads the UI.
Point me anywhere and thanks again. I clicked the 'thanky' button.
Click to expand...
Click to collapse
Have u done a factory reset before flashing to ur back up?? If not it will cuase serious issues factory reset/wipe cache/wipe dalvik cache
Sent from my SAMSUNG-SGH-I717 using Xparent ICS Blue Tapatalk 2
Do all three wipes like I said earlier then flash a fresh rom and u should be fine man hope that works for u pm me if need better instructions or help
Sent from my SAMSUNG-SGH-I717 using Xparent ICS Blue Tapatalk 2
Hello everyone,
I seem to be facing a singular issue, but I imagine it is much my fault, and just wanted a confirmation from those more experienced with the device...
I bought an Incredible 4G from eBay, that already had the a copy of Avatar on it, I believe almost the latest update. So when I confirmed the device worked after charging the battery, I flashed the latest copy of Avatar and the JB Gapps, and everything seemed hunkydory.
So, after that, I put in my old SIM, deactivated as I was using a non-4g device, and put it in the Incredible 4G. I started the activation process on the phone, following prompts to reboot the phone (Note: I did not know about CM10.1's issue regarding activation at the time, so one of the possible problems.)
After seemingly failing to activate after the first reboot, I "tried again" and it went down for another reboot. And it stayed down. Completely. I cannot get the phone to start, after charging the battery separately, cannot get into bootloader, nothing. I get QHSUSB_DLOAD when plugged into a computer using USB, but that's it.
A few notes: first time I started up, the screen went to recovery. I didn't think that was an issue; I factory reset from there, and rebooted into Avatar. Second issue: I used ROM updater on the phone to download and install the recovery, as I imagined that there was an automatic checksum done in the process (perhaps it was imagined?), and so when it went to flash, it had some issue, which didn't seem like a problem with the download, and I went through flashing it normally through recovery. Sorry I can't provide more details on that, but everything seemed to work all right after rebooting.
Finally, and this may be irrelevant, I put a 64GB SDXC card in the phone, I had already realized that it could not natively support exFAT, and so left the card in the device until the next time I could boot to recovery to partition it, and went through the activation process with the card inserted and not recognized.
So, I imagine that I have a hard brick, but can't tell if it's completely my fault, because it bricked in a peculiar fashion, at least from what I can tell, as no one seems to have encountered a similar issue after searching for the last 5 days.
If there's any hope for recovery, I would really appreciate some help regarding the device. I'm willing to provide some more info if necessary, and I'd like to find out sooner rather than later if it's a lost cause.
Thanks for any help you guys can give. XDA devs are awesome.
Quite the predicament. Just to clarify, have you tried the following?
1) Remove that super-big MicroSD
2) Remove SIM
3) Remove battery and wait a few minutes; also press the power button while phone is off
4) Only re-inserting the battery, hold vol-down and then hold power until screen comes on (then release power but keep holding vol-down)
I have tried them all; no SIM or SD card has been in there since the issue started. I hadn't tried pushing the power button while the battery was out, but it doesn't seem to change anything. So far, no reaction whatsoever even when holding power + vol down for a few minutes.
ChiqOmar said:
I have tried them all; no SIM or SD card has been in there since the issue started. I hadn't tried pushing the power button while the battery was out, but it doesn't seem to change anything. So far, no reaction whatsoever even when holding power + vol down for a few minutes.
Click to expand...
Click to collapse
Looks like you have a very hard to solve brick, I would like to help, have you tried using fastboot, I mean connected to pc and on that screen issue a fastboot command, also upload a picture of it please since this is new kind of brick, also I found this, our device is supported,
http://unlimited.io/qhsusbdload.htm
Sent from my ADR6410LVW using xda app-developers app
jose51197 said:
Looks like you have a very hard to solve brick, I would like to help, have you tried using fastboot, I mean connected to pc and on that screen issue a fastboot command, also upload a picture of it please since this is new kind of brick, also I found this, our device is supported,
http://unlimited.io/qhsusbdload.htm
Sent from my ADR6410LVW using xda app-developers app
Click to expand...
Click to collapse
You can't do fastboot if you can't reach the bootloader, and I've been assured the unlimited.io tool will not help for DLOAD resulting from non-racun related procedures.
Reading forum posts about QHSUSB_DLOAD suggest either jtag is necessary (which might not be worth it considering the phone can be purchased for $150 on ebay) or some strange strokes of luck after letting the phone sit for a bit. ChiqOmar, sorry I don't have great advice; do all the reading you can about QHSUSB_DLOAD mode.
jose51197 said:
Looks like you have a very hard to solve brick, I would like to help, have you tried using fastboot, I mean connected to pc and on that screen issue a fastboot command, also upload a picture of it please since this is new kind of brick, also I found this, our device is supported,
http://unlimited.io/qhsusbdload.htm
Sent from my ADR6410LVW using xda app-developers app
Click to expand...
Click to collapse
yes sounds like he is stuck in QSHUSB_DLOAD mode, but i don't know if the resolutiion on unlimited.io will help him or not.they say it's not supported for other reasons other than from running their exploit. it might work though.
mdmower said:
You can't do fastboot if you can't reach the bootloader, and I've been assured the unlimited.io tool will not help for DLOAD resulting from non-racun related procedures.
Reading forum posts about QHSUSB_DLOAD suggest either jtag is necessary (which might not be worth it considering the phone can be purchased for $150 on ebay) or some strange strokes of luck after letting the phone sit for a bit. ChiqOmar, sorry I don't have great advice; do all the reading you can about QHSUSB_DLOAD mode.
Click to expand...
Click to collapse
Maybe port HTC unbricking project to our device, and try to help him using it, since he can't do nothing about it right now, ChiqOmar, you ok with testing it ?, btw download ubuntu connect phone and see if the partitions get mounted, btw looks like you need to flash hboot from that mode, that's all then ruu, I have all the tools to do it if you want to
Sent from my ADR6410LVW using xda app-developers app
mdmower said:
You can't do fastboot if you can't reach the bootloader, and I've been assured the unlimited.io tool will not help for DLOAD resulting from non-racun related procedures.
Reading forum posts about QHSUSB_DLOAD suggest either jtag is necessary (which might not be worth it considering the phone can be purchased for $150 on ebay) or some strange strokes of luck after letting the phone sit for a bit. ChiqOmar, sorry I don't have great advice; do all the reading you can about QHSUSB_DLOAD mode.
Click to expand...
Click to collapse
i was able to bring my rezound back after a hard brick with a hex edited hboot that went bad with this tool but ported for rezound. its worth a try?
Thanks for the help everyone. Yes, although it states quite clearly that the Unlimited.io tool is only meant for devices bricked using their tool, I tried it anyway; obviously, nothing changed.
Though JTAG sounds interesting, I have no idea how to get started with that...nor do I really know if I want to travel down that route just now.
The HTC Unbricking Project sounds promising, but also no idea how to get started as it has not been ported for our device. The partitions don't get mounted in Ubuntu, as I connected it to the computer to use the Unlimited.io tool.
Finally, regarding the nature of the brick itself, I really wish I could pinpoint the issue better to help others if a similar issue happens in the future.
I am actually waiting on a battery, (ordered before I got the phone) and so will try that to see if anything changes.
Thanks again everyone. I've got a feeling I might have to write this one off pretty soon.
ChiqOmar said:
Hello everyone,
I seem to be facing a singular issue, but I imagine it is much my fault, and just wanted a confirmation from those more experienced with the device...
I bought an Incredible 4G from eBay, that already had the a copy of Avatar on it, I believe almost the latest update. So when I confirmed the device worked after charging the battery, I flashed the latest copy of Avatar and the JB Gapps, and everything seemed hunkydory.
So, after that, I put in my old SIM, deactivated as I was using a non-4g device, and put it in the Incredible 4G. I started the activation process on the phone, following prompts to reboot the phone (Note: I did not know about CM10.1's issue regarding activation at the time, so one of the possible problems.)
After seemingly failing to activate after the first reboot, I "tried again" and it went down for another reboot. And it stayed down. Completely. I cannot get the phone to start, after charging the battery separately, cannot get into bootloader, nothing. I get QHSUSB_DLOAD when plugged into a computer using USB, but that's it.
A few notes: first time I started up, the screen went to recovery. I didn't think that was an issue; I factory reset from there, and rebooted into Avatar. Second issue: I used ROM updater on the phone to download and install the recovery, as I imagined that there was an automatic checksum done in the process (perhaps it was imagined?), and so when it went to flash, it had some issue, which didn't seem like a problem with the download, and I went through flashing it normally through recovery. Sorry I can't provide more details on that, but everything seemed to work all right after rebooting.
Finally, and this may be irrelevant, I put a 64GB SDXC card in the phone, I had already realized that it could not natively support exFAT, and so left the card in the device until the next time I could boot to recovery to partition it, and went through the activation process with the card inserted and not recognized.
So, I imagine that I have a hard brick, but can't tell if it's completely my fault, because it bricked in a peculiar fashion, at least from what I can tell, as no one seems to have encountered a similar issue after searching for the last 5 days.
If there's any hope for recovery, I would really appreciate some help regarding the device. I'm willing to provide some more info if necessary, and I'd like to find out sooner rather than later if it's a lost cause.
Thanks for any help you guys can give. XDA devs are awesome.
Click to expand...
Click to collapse
Just got same issue, though for me I installed avatar rom, then rebooted at some point, but instead it hard bricked, can't charge pull battery out/in boot back up removed sim sd card didn't help me either. Any progress yet, or help?
Ill try to get a working htc unbriking Project soon for you guys to try, both please use ubuntu and have a working USB cable, I'm gonna try to reinstall hboot, also have teamviewr installed, also please tell me if you guys are supercid, also no usb 3.0 cable or port please
Sent from my ADR6410LVW using xda app-developers app
Some Information
jose51197 said:
Ill try to get a working htc unbriking Project soon for you guys to try, both please use ubuntu and have a working USB cable, I'm gonna try to reinstall hboot, also have teamviewr installed, also please tell me if you guys are supercid, also no usb 3.0 cable or port please
Sent from my ADR6410LVW using xda app-developers app
Click to expand...
Click to collapse
I'm on Ubuntu 13.04 64 Bit, I have a usb cable, Anker Battery Expert separate battery charger. And my Phone is S-OFF DirtyRacun Currently still hard bricked (Not by the Racun though) don't have any 3.0's, i have a onn usb cable and the stock, I also have a Ubuntu 12.04.2 LTS 32 Bit Live DVD. Battery Charging using a battery pack charger. Won't charge through USB
OldNut5 said:
I'm on Ubuntu 13.04 64 Bit, I have a usb cable, Anker Battery Expert separate battery charger. And my Phone is S-OFF DirtyRacun Currently still hard bricked (Not by the Racun though) don't have any 3.0's, i have a onn usb cable and the stock, I also have a Ubuntu 12.04.2 LTS 32 Bit Live DVD.
Click to expand...
Click to collapse
pm me with gtalk email and ill see what i can do, also install teamviewr
OldNut5 said:
I'm on Ubuntu 13.04 64 Bit, I have a usb cable, Anker Battery Expert separate battery charger. And my Phone is S-OFF DirtyRacun Currently still hard bricked (Not by the Racun though) don't have any 3.0's, i have a onn usb cable and the stock, I also have a Ubuntu 12.04.2 LTS 32 Bit Live DVD. Battery Charging using a battery pack charger. Won't charge through USB
Click to expand...
Click to collapse
I lost my first Dinc 4G LTE after I installed CM10.1, was working great for a while and just blinked off, never to recover. No charge light, no response to power button. I also had an aftermarket battery (Hyperion), but it would get so hot charging I replaced it with an OEM HTC battery. I think that damaged the phone.
Since I work with analog electronics, I assume something in the power path physically burned out. I never tried to talk to it via USB, but just cabling it to a computer generates no response.
I went back to the Stock RUU.zip from the unlimited.io site to get the firmware update. During the update it just sort of died. Now I can't get it to charge or get into the bootloader. Help! Please!:crying:
I was going through the DirtyRacun steps and finally got to the RabiesShot point. As it was running, I noticed it was stuck on "Is that a corndog?" Where I got to the point where it had about 5 lines of periods and nothing. The phone will no longer turn on. It's doing absolutely nothing. What the hell should I do?
Also, why the hell is it such a nightmare to get this phone S-OFF? Every other phone I've owned, it was so damn simple. This thing, it's like trying to wrestly a damn bear.
Please help.
Edit: Nevermind, I had to use the RacunHunter to get it out. Mods can close thread if they'd like.
cdboss said:
I was going through the DirtyRacun steps and finally got to the RabiesShot point. As it was running, I noticed it was stuck on "Is that a corndog?" Where I got to the point where it had about 5 lines of periods and nothing. The phone will no longer turn on. It's doing absolutely nothing. What the hell should I do?
Also, why the hell is it such a nightmare to get this phone S-OFF? Every other phone I've owned, it was so damn simple. This thing, it's like trying to wrestly a damn bear.
Please help.
Edit: Nevermind, I had to use the RacunHunter to get it out. Mods can close thread if they'd like.
Click to expand...
Click to collapse
I have done that same step getting stuck on the corndog part 3 times now and I was able to unbrick 3 times now and I am not sure what is going on. I had a launch day evo with a rooted 1.12, but its been having some issues and I had to rma it and now I am trying to unlock this new one and it is a real pia compared to first rooting it.
using a 2gb microsd with ubuntu live 13, were you able to get it working?
twist said:
I have done that same step getting stuck on the corndog part 3 times now and I was able to unbrick 3 times now and I am not sure what is going on. I had a launch day evo with a rooted 1.12, but its been having some issues and I had to rma it and now I am trying to unlock this new one and it is a real pia compared to first rooting it.
using a 2gb microsd with ubuntu live 13, were you able to get it working?
Click to expand...
Click to collapse
Yeah I was. The second time I ran it, the only things I changed was using the actual HTC USB cable. I don't really think this made a difference but, I gave it a whirl anyway.