Related
Okay so I rooted my phone using Toast's method.
I get into recovery, after the wipe when I flash a ROM and reboot, my phone keeps rebooting, it doesn't go past the white HTC EVO 4G screen. It just keeps cycling through.
Should mention it was the FroYo ROM.
Seems like others are having the same problem, so help us out
Hero's Hero said:
Should mention it was the FroYo ROM.
Seems like others are having the same problem, so help us out
Click to expand...
Click to collapse
Mine got stuck on the N1 screen too, till i cleared the top 3 in the wipe list. Then it booted right up.
yep, what mrono said
mrono said:
Mine got stuck on the N1 screen too, till i cleared the top 3 in the wipe list. Then it booted right up.
Click to expand...
Click to collapse
Yeah, I did that but it's still being a little ****.
Idk, guess I have to wait for the next update to try again :/
OH NO, guys PLEASE help me.
My phone will not boot, at all. Not to normal or to recovery.
I was running MIUI 0.2.21, I was about to nand restore because of poor battery life.
So I booted into recovery, Did factory wipe. Then went to Nand and tried to run Nand restore. The phone gave error, I didn't pay enough attention to it I guess.
The message said something like "error, Nand Restore unsuccessful, run adb.restore.ssh via ADB"
Or something close to that.
I powered down and was going to reboot back to recovery to try again, however the phone now will NOT do anything, I don't know what to do. Can anyone help Me???
Nevermind. After sitting 20 minutes with no battery, I was able to boot as normal. WHEW!!! That was scary!
that error means you have insufficient battery, let it charge
[email protected] is my gf, NOT ME
rugedraw said:
[email protected] is my gf, NOT ME
Click to expand...
Click to collapse
yeah lol i get messages saying where you live girl im like stfu faq lol
iitreatedii said:
yeah lol i get messages saying where you live girl im like stfu faq lol
Click to expand...
Click to collapse
Yea, I figured that's why you added that to your sig.....that's what I found funny about it.
Okay, so im running kingsrom unleashed 4g, and its great i love it. Tired to flash another rom today, elite III. Preformed backup, flashed format_all zip first then was gonna flash elite III next like it states. But now after flashing format_all zip it restarted the phone and now its back to kingrom and its in safe mood. For some odd reason its not letting me load into bootloader so i can flash the next step. And whats really ticking me off is that rommanager is not working. Ive installed and uninstalled countless times and it wont let me open. Does it have to due with being in safe mood. Please help me , need someone to fill me in. Thanks for you time.
I'm confused in regard to your post. Anyway, to get to the bootloader, power off your device. Now simultaneously press the DOWN volume button and the power button until your device starts. After a short pause, a few lines of text will scroll across the screen and then you'll be shown a set of options. Viola, you're at the bootloader screen.
posting & replying via the XDA Premium app.
dougjamal said:
I'm confused in regard to your post. Anyway, to get to the bootloader, power off your device. Now simultaneously press the DOWN volume button and the power button until your device starts. After a short pause, a few lines of text will scroll across the screen and then you'll be shown a set of options. Viola, you're at the bootloader screen.
posting & replying via the XDA Premium app.
Click to expand...
Click to collapse
Thats what ive been trying to do for the last hour, i know how to get there. The problem here is that it wont load up, it just starts up once i let go of the power button.
I feel like a broken record: STOP USING ****ING ROM MANAGER!!!!!!!!!!!!!!!!!!!!!!!!!!!
Flash your **** in ****ing RECOVERY like it was designed for.....
10,000 posts about problem flashing ROMS on here, and 9,990 of them were because someone was using ROM manager
Now, I KNOW people are going post that ROM Manager works fine for them, well great! Welcome to the minority.....
HipKat said:
I feel like a broken record: STOP USING ****ING ROM MANAGER!!!!!!!!!!!!!!!!!!!!!!!!!!!
Flash your **** in ****ing RECOVERY like it was designed for.....
10,000 posts about problem flashing ROMS on here, and 9,990 of them were because someone was using ROM manager
Click to expand...
Click to collapse
Take a breather. And I feel like the problem is from him not disabling the function in applications/development that enables the 'fast' reboot.
teh roxxorz said:
Take a breather. And I feel like the problem is from him not disabling the function in applications/development that enables the 'fast' reboot.
Click to expand...
Click to collapse
Possibly.....
Still, I'm gonna start a revolution against ROM Manager and Kernel Manger...
Useless programs for people trying to shortcut a proven system...
HipKat said:
I feel like a broken record: STOP USING ****ING ROM MANAGER!!!!!!!!!!!!!!!!!!!!!!!!!!!
Flash your **** in ****ing RECOVERY like it was designed for.....
10,000 posts about problem flashing ROMS on here, and 9,990 of them were because someone was using ROM manager
Now, I KNOW people are going post that ROM Manager works fine for them, well great! Welcome to the minority.....
Click to expand...
Click to collapse
okay..., looks like i learned the hard way, time to get up and learn from my mistakes. But do you know how i get out of this pickle?
When you do vol-down/power, you don't get to bootloader? What does your phone do?
HipKat said:
When you do vol-down/power, you don't get to bootloader? What does your phone do?
Click to expand...
Click to collapse
Nothing at all. Then after mmm 45 seconds of holding it down i let go, it boots up, quickly too. Im not sure if its because of Kingsrom or what ( on the fast boot that is).
What about fastboot? (Vol up/Power)?
I'm no expert here, but I think you may want to try running the RUU form your PC if that doesn't work, go back to stock and start over. I'm sure someone will come up wit ha better option, but if it was me, that's what I would do.
conman123 said:
Nothing at all. Then after mmm 45 seconds of holding it down i let go, it boots up, quickly too. Im not sure if its because of Kingsrom or what ( on the fast boot that is).
Click to expand...
Click to collapse
You need to go into the settings and disable that 'fast reboot' setting.
teh roxxorz said:
You need to go into the settings and disable that 'fast reboot' setting.
Click to expand...
Click to collapse
Oh yeah, I already forgot about that......
HipKat said:
Oh yeah, I already forgot about that......
Click to expand...
Click to collapse
Its okay to forget things when leading a rebellion.
teh roxxorz said:
You need to go into the settings and disable that 'fast reboot' setting.
Click to expand...
Click to collapse
Thanks so much, it started right up in bootloader.
HipKat said:
Oh yeah, I already forgot about that......
Click to expand...
Click to collapse
Im never using rommanager again i suppose, thanks for the heads up though.
conman123 said:
Thanks so much, it started right up in bootloader.
Click to expand...
Click to collapse
Never a problem. And you can still use rom manager to fix permissions, if you get a whole bunch of force closes on apps for no reason.
teh roxxorz said:
Never a problem. And you can still use rom manager to fix permissions, if you get a whole bunch of force closes on apps for no reason.
Click to expand...
Click to collapse
Okay cool, when i did a google search on safe mode it seemed to me like i was about to have a pretty paper weight.. haha
teh roxxorz said:
Its okay to forget things when leading a rebellion.
Click to expand...
Click to collapse
Lmao.........
Swyped From The Hippest Phone Using XDA Premium
teh roxxorz said:
Never a problem. And you can still use rom manager to fix permissions, if you get a whole bunch of force closes on apps for no reason.
Click to expand...
Click to collapse
Remind me to add that to my Revolt thread that it is awesome for fixing permissions
Swyped From The Hippest Phone Using XDA Premium
conman123 said:
Okay cool, when i did a google search on safe mode it seemed to me like i was about to have a pretty paper weight.. haha
Click to expand...
Click to collapse
Lawlz, no paper weights while I'm around.
ok, so i turned my phone off, took out the battery, took out my sdcard, and replaced the back casing on my phone. now that i boot up, my phone is back to default as if i just flashed a new rom. i see that my apps are still there on my sdcard, but my homescreen and all my settings are gone. i tried fixing permission, but no luck, anyone got any ideas?
I assume you put the SD Card back, too??
Are you running A2SD?
What ROM are you running?? Kernel?? etc... need more info
You can try to Just reboot and let it sit for about 10 mins.
HipKat said:
I assume you put the SD Card back, too??
Are you running A2SD?
What ROM are you running?? Kernel?? etc... need more info
You can try to Just reboot and let it sit for about 10 mins.
Click to expand...
Click to collapse
yes sir i put the sdcard back in.. and yes i am running a2sd. i am currently running team dirt cm9 1.7 with mason kernel version .15rc4 sbc
tried rebooting several times and allowing it to load.. it's weird because it's not like i turned the phone on while the sdcard was out.. not too sure what could cause this, this is not the first time neither, usually i just reinstall everything but man.. it's been so long since ive ran into any sort of issues.. i nand restored an older backup without reflashing the ext partition, i got most of my settings back, so thankfully i was able to work from there. but i would still like to know what could have caused this. thanks for your reply hipkat, good to know someone cares to even try..
Why did you do the pull, etc. in the first place?
Sent from my PC36100 using Tapatalk 2
madunix said:
yes sir i put the sdcard back in.. and yes i am running a2sd. i am currently running team dirt cm9 1.7 with mason kernel version .15rc4 sbc
tried rebooting several times and allowing it to load.. it's weird because it's not like i turned the phone on while the sdcard was out.. not too sure what could cause this, this is not the first time neither, usually i just reinstall everything but man.. it's been so long since ive ran into any sort of issues.. i nand restored an older backup without reflashing the ext partition, i got most of my settings back, so thankfully i was able to work from there. but i would still like to know what could have caused this. thanks for your reply hipkat, good to know someone cares to even try..
Click to expand...
Click to collapse
My first thought was that card wasn't fully seated, but I know that's hard to miss. It's pretty odd, for sure.
dcharleyultra said:
Why did you do the pull, etc. in the first place?
Sent from my PC36100 using Tapatalk 2
Click to expand...
Click to collapse
i replaced my back casing.......... dot dot dot...
HipKat said:
My first thought was that card wasn't fully seated, but I know that's hard to miss. It's pretty odd, for sure.
Click to expand...
Click to collapse
seems to be the only logical explanation, im possibly assuming finger prints on the sdcard leads.. because i did turn my phone off and gave it a wipe to get the sdcard read by the phone, but my settings wouldn't come back.
madunix said:
i replaced my back casing.......... dot dot dot...
Click to expand...
Click to collapse
What happens when you try your old casing?
Sent from my PC36100 using Tapatalk 2
The whole process is pretty simple on what I have done. I will explain my situation here and my question that has got be baffled.
So it all started about two weeks ago, where I was flashing LiquidSmooth on my phone. I had a Touch-type CWM. It isn't mega old but it's pretty old for CWM, I haven't updated in a while (as i've seen there are updates to recent ones).
Anywho, I did a complete wipe, used the darkside wipe, alongside with the darkside cache wipe.
I think this was my fault, so please correct me anyone if I am wrong here. I accidentally hit "reboot phone" instead of "reboot bootloader"
I got a permabrick from this whole ordeal. It was a permabrick because It said QHSUSB_DLOAD in the device manager, looking this up further confirmed my reasoning. I didn't want to jtag because that invovles removing the phone to pieces and soldering on wires etc. etc.
So I resorted to send it out to Samsung.
All is well when it came back. I made sure this time the whole phone was setup properly.
So I use Odin install for CWM and SU was installed via CWM. I install an older version of CWM (non-touch, i believe 1st revision as i've posted in one of the threads).
I kept stock ROM, everything was working okay and suddenly, KERPLUNK, it went back into permanent brick after I deleted cache partition, dalvik cache, and battery cache wipe. I didn't do fix permissions or anything, just hit reboot afterwards.
This is a super head scratcher here..... Anyone know where I went wrong?
Any insight here is greatly appreciated! :good:
P.S. I am now sending in my phone TWICE to Samsung for repairs.
If you are on the most up to date CWM, do not use the scripts. They are no longer needed, and will cause problems( hard brick though, never heard of) The second time, im stumped. I suggest go to TWRP and ditch the scripts. Latest TWRP does not need it
LoopDoGG79 said:
If you are on the most up to date CWM, do not use the scripts. They are no longer needed, and will cause problems( hard brick though, never heard of) The second time, im stumped. I suggest go to TWRP and ditch the scripts. Latest TWRP does not need it
Click to expand...
Click to collapse
I finally jumped in the water and flashed twrp! Yay!
Sent from my SAMSUNG-SGH-T989 using xda premium
All the steps you say you did don't point to a brick. But one thing caught my eye! You said you were flashing liquidsmooth? What File did you flash? Did it have Hercules in the name? Because if it didn't then it's not for our phone.. I only ask because a lot of other people made that mistake
Sent from my SGH-T989 using xda premium
rymanh said:
All the steps you say you did don't point to a brick. But one thing caught my eye! You said you were flashing liquidsmooth? What File did you flash? Did it have Hercules in the name? Because if it didn't then it's not for our phone.. I only ask because a lot of other people made that mistake
Sent from my SGH-T989 using xda premium
Click to expand...
Click to collapse
great call on that I had to educate a few users that the d2tmo is not for our phone but indeed the S3. Good catch on your part and it sounds like user error as well
LoopDoGG79 said:
If you are on the most up to date CWM, do not use the scripts. They are no longer needed, and will cause problems( hard brick though, never heard of) The second time, im stumped. I suggest go to TWRP and ditch the scripts. Latest TWRP does not need it
Click to expand...
Click to collapse
Could you please educate me with a link referring to what TWRP is? Sorry, i'm still fairly new to the scene and all i've ever been educated upon is CWM.
suaverc118 said:
I finally jumped in the water and flashed twrp! Yay!
Sent from my SAMSUNG-SGH-T989 using xda premium
Click to expand...
Click to collapse
Nice! What is TWRP and how is it like?
rymanh said:
All the steps you say you did don't point to a brick. But one thing caught my eye! You said you were flashing liquidsmooth? What File did you flash? Did it have Hercules in the name? Because if it didn't then it's not for our phone.. I only ask because a lot of other people made that mistake
Sent from my SGH-T989 using xda premium
Click to expand...
Click to collapse
I've flashed the hercules ROM. I know this for sure because Liquidsmooth was working, it was extremely glitchy (playing games gave me pixelated actions sometimes, and using something like gameCIH/Game Guardian was unworkable). So i decided to ditch it and was getting ready to flash Jedi Mind Trick.
After the whole hard bricking ordeal, I decided to stick to stock rom, and even on that, I just flashed CWM and SU ONLY. Rebooted, and deleted the cache's (like i've posted to you) with absolutely no success. It baffled me that I bricked the phone AGAIN too!
playya said:
great call on that I had to educate a few users that the d2tmo is not for our phone but indeed the S3. Good catch on your part and it sounds like user error as well
Click to expand...
Click to collapse
Yes..... there is something wrong, i feel it is a user error also, but i'm very unsure where to even start
Once again, all of your insight is well appreciated! I just do not want to hardbrick my phone AGAIN and have to send it to Samsung. I am not allowed to even think of a replacement because this was a b-day present a year or two ago from my fiance.
You say that it is bricked again. Do you mean by that, that you cannot get into recovery?
Sent from my SAMSUNG-SGH-T989 using xda premium
XxGoKoUxX said:
Could you please educate me with a link referring to what TWRP is? Sorry, i'm still fairly new to the scene and all i've ever been educated upon is CWM.
Nice! What is TWRP and how is it like?
I've flashed the hercules ROM. I know this for sure because Liquidsmooth was working, it was extremely glitchy (playing games gave me pixelated actions sometimes, and using something like gameCIH/Game Guardian was unworkable). So i decided to ditch it and was getting ready to flash Jedi Mind Trick.
After the whole hard bricking ordeal, I decided to stick to stock rom, and even on that, I just flashed CWM and SU ONLY. Rebooted, and deleted the cache's (like i've posted to you) with absolutely no success. It baffled me that I bricked the phone AGAIN too!
Yes..... there is something wrong, i feel it is a user error also, but i'm very unsure where to even start
Once again, all of your insight is well appreciated! I just do not want to hardbrick my phone AGAIN and have to send it to Samsung. I am not allowed to even think of a replacement because this was a b-day present a year or two ago from my fiance.
Click to expand...
Click to collapse
Flash this in recovery, reboot recovery, and you will have TWRP!!
TWRP 2.3.1.1
DM_Sledge said:
You say that it is bricked again. Do you mean by that, that you cannot get into recovery?
Sent from my SAMSUNG-SGH-T989 using xda premium
Click to expand...
Click to collapse
Yes, it is perma-bricked, meaning the only method of fixing the brick is jtagg'ing
Upon plugging it into device manager, I get the prompt "QHSUSB_DLOAD" and phone doesn't even boot on no matter what combinations I make.
LoopDoGG79 said:
Flash this in recovery, reboot recovery, and you will have TWRP!!
TWRP 2.3.1.1
Click to expand...
Click to collapse
Thank you LoopDo, I will do this after I get my phone home again.
I have this phone, and none of the steps you listed would brick the device. Even with no ROM on the phone, you should still be able to get into recovery.
Is there something you aren't telling us?
Sent from my Galaxy Nexus using xda premium
Nope, wouldn't be a reason why I would lie because then the problem will never be resolved.... I'm kind of nervous on reflashing ONE more time after the phone comes home again....
The phone has been fixed once AGAIN, and it is in the process of being shipped back to me.
Phone will be home Wednesday and I will give it ONE more try
Wish me luck!
P.S. my PC has been glitchy lately, so that MAY or MAY NOT contribute to the permabrick, then again the brick doesn't happen until I flash stuff via CWM.
P.S.S. I've since re-installed Win 7 again, it hasn't been glitchy since
XxGoKoUxX said:
Nope, wouldn't be a reason why I would lie because then the problem will never be resolved.... I'm kind of nervous on reflashing ONE more time after the phone comes home again....
The phone has been fixed once AGAIN, and it is in the process of being shipped back to me.
Phone will be home Wednesday and I will give it ONE more try
Wish me luck!
P.S. my PC has been glitchy lately, so that MAY or MAY NOT contribute to the permabrick, then again the brick doesn't happen until I flash stuff via CWM.
P.S.S. I've since re-installed Win 7 again, it hasn't been glitchy since
Click to expand...
Click to collapse
You most likely flashed the Wrong Liquidsmooth ROM (incompatible Kernel), and it hard bricked the phone. It happened to me the same way, and I had to send it in for JTAG.
I have bricked my phone installing the Liquidsmooth ROM too. I downloaded the wrong ROM, though. The thread should have a big ****in warning to double check the ROM you are about to download, otherwise your phone is a toast. There were more people who bricked their phones by installing the Liquidsmooth.
Well, I got it back from the warranty and the phone looks good. Installed that Liquidsmooth again and played for a day. Tried other JB ROMs. Most of them are OK in terms of battery life and smoothness, but there is something wrong with the signal. People always say my voice isn't clear. I got tired of all this BS and testing new ROMs and went to back to ICS and won't look back, not anytime.
Don't use darkside scripts, btw. You don't need that anymore.
I'd like to say thank you for everyone's patience. All of your insight is more than helpful!
DroidDonX said:
You most likely flashed the Wrong Liquidsmooth ROM (incompatible Kernel), and it hard bricked the phone. It happened to me the same way, and I had to send it in for JTAG.
Click to expand...
Click to collapse
I might have, but the one i downloaded (which is still on the phone's memory card) is a hercules ROM. Either way on my second try there was a hard brick also, in return of which I had to resend it in. The second try was just simply: Odin---->CWM---->Root---->SU---->wipe cache partition+fix permissions+wipe dalvik cache via CWM (not the super scripts).
cipsaz said:
I have bricked my phone installing the Liquidsmooth ROM too. I downloaded the wrong ROM, though. The thread should have a big ****in warning to double check the ROM you are about to download, otherwise your phone is a toast. There were more people who bricked their phones by installing the Liquidsmooth.
Well, I got it back from the warranty and the phone looks good. Installed that Liquidsmooth again and played for a day. Tried other JB ROMs. Most of them are OK in terms of battery life and smoothness, but there is something wrong with the signal. People always say my voice isn't clear. I got tired of all this BS and testing new ROMs and went to back to ICS and won't look back, not anytime.
Don't use darkside scripts, btw. You don't need that anymore.
Click to expand...
Click to collapse
Thanks again for your insight I think i'm done with flashing for a little bit for now.... I kind of want as factory of a JB Rom as possible. :good:
If anyone has any idea where I can get that, please let me know as my Stock ICS is a bit laggy at times, with the facial recognition system, it lags even worse!
rymanh said:
All the steps you say you did don't point to a brick. But one thing caught my eye! You said you were flashing liquidsmooth? What File did you flash? Did it have Hercules in the name? Because if it didn't then it's not for our phone.. I only ask because a lot of other people made that mistake
Sent from my SGH-T989 using xda premium
Click to expand...
Click to collapse
that just happened to me today with liquid smooth. i had to unroot, flash stock, and start over. im pretty sure i got it from goo.im under hercules. unfortunate mislabeling? oh yeah, and if your phone shows anything other than nothing, youre not hard bricked. thats why its called Hercules, i think. ive been soft bricked so many times from dumb **** like. ****ing with the governors and all that **** cm gives you the option to do when there aint even a 1080p camera that works fully = / lol <3 Cm I Love Yew!! But yeah, odin will set you free!!!