Database Info

[Q] stuck on splash screen, please help!

im new at this please bear with me.
i rooted my shift last week. everything was fine, im not ready to get too crazy into flashing stuff yet (since the risk for bricking is higher with android). i like to take my time read, study, test small things here and there.
today i was browsing the forums and came across the battery icon mod
http://forum.xda-developers.com/showthread.php?t=892297
so i downloaded it, i had rom manager installed, and installed the battery icon manager.
i chose the icon i wanted rebooted, it looked ok, so i wanted to try the other icon and loaded that one, phone rebooted and got stuck on the sprint splash screen.
i can boot into the bootloader, not sure what steps i need to take next to restore my os.

BiffTirkle said:
im new at this please bear with me.
i rooted my shift last week. everything was fine, im not ready to get too crazy into flashing stuff yet (since the risk for bricking is higher with android). i like to take my time read, study, test small things here and there.
today i was browsing the forums and came across the battery icon mod
http://forum.xda-developers.com/showthread.php?t=892297
so i downloaded it, i had rom manager installed, and installed the battery icon manager.
i chose the icon i wanted rebooted, it looked ok, so i wanted to try the other icon and loaded that one, phone rebooted and got stuck on the sprint splash screen.
i can boot into the bootloader, not sure what steps i need to take next to restore my os.
Click to expand...
Click to collapse
once you're in bootloader, select recovery, then backup restore. Then restore. Then restore your backup that we're all sure you made before you made those mods right? RIIIIIGHT?????

You have to get to boot loader to get to recovery to wipe and flash your rom... (hold vol down and press power) in case you didn't know..you should being that its rooted..I dunno
Sent from my PG06100 using XDA App

RyteSyde said:
once you're in bootloader, select recovery, then backup restore. Then restore. Then restore your backup that we're all sure you made before you made those mods right? RIIIIIGHT?????
Click to expand...
Click to collapse
if you still have problems, come hit us up in irc:
Server: irc.freenode.net
Channel: #HTC_EVO_Shift
Port: 6667
Site: http://webchat.freenode.net/?channels=HTC_EVO_Shift

RyteSyde said:
once you're in bootloader, select recovery, then backup restore. Then restore. Then restore your backup that we're all sure you made before you made those mods right? RIIIIIGHT?????
Click to expand...
Click to collapse
hahaha, why would i create a backup!? that would make sense. i have not created a back up. i had not gotten around to doing it yet. it was on my list of things to do.

BiffTirkle said:
im new at this please bear with me.
i rooted my shift last week. everything was fine, im not ready to get too crazy into flashing stuff yet (since the risk for bricking is higher with android). i like to take my time read, study, test small things here and there.
today i was browsing the forums and came across the battery icon mod
http://forum.xda-developers.com/showthread.php?t=892297
so i downloaded it, i had rom manager installed, and installed the battery icon manager.
i chose the icon i wanted rebooted, it looked ok, so i wanted to try the other icon and loaded that one, phone rebooted and got stuck on the sprint splash screen.
i can boot into the bootloader, not sure what steps i need to take next to restore my os.
Click to expand...
Click to collapse
Boot in to CWM Recovery go to backup/restore /advanced restore, select restore /system only. Once that is complete clear the cache, reboot. you can then delete your dalvik cache (note: clearing the dalvik cache doesn't work via CWM currently). That's it.

If you didn't make a back up, just re flash the rom. If you were still stock, just flash preludedrew's or nfinitefx's base. You can even still keep your data. Just make sure from now on to back up before doing any mods.
Sent from my PG06100 using XDA App

he's squared away now. Make your backups y'all.

RyteSyde said:
he's squared away now. Make your backups y'all.
Click to expand...
Click to collapse
thank you again for taking the time to help me out. it would have been a much longer night had you not offered.

BiffTirkle said:
thank you again for taking the time to help me out. it would have been a much longer night had you not offered.
Click to expand...
Click to collapse
You're lucky. Usually when RyteSyde helps people, he helps them to pricking their device. Glad it worked out for you in the end.....
Sent from my PG06100 using XDA App

riggsandroid said:
You're lucky. Usually when RyteSyde helps people, he helps them to pricking their device. Glad it worked out for you in the end.....
Sent from my PG06100 using XDA App
Click to expand...
Click to collapse
That's a little f'ed up callin someone out like that no? I'm not a mod by far but I'm pretty sure the forums aren't for childish behavior as such..
Sent from my PG06100 using XDA App

JKILO said:
That's a little f'ed up callin someone out like that no? I'm not a mod by far but I'm pretty sure the forums aren't for childish behavior as such..
Sent from my PG06100 using XDA App
Click to expand...
Click to collapse
They're friends.
^ Shift Faced

jesusice said:
They're friends.
^ Shift Faced
Click to expand...
Click to collapse
Touchè lol apologies to you two
Sent from my PG06100 using XDA App

We take turns bricking phones in the IRC!
I guess I should've put an indication that I'm just trying to piss him off, but I know I pissed someone else off....

riggsandroid said:
We take turns bricking phones in the IRC!
I guess I should've put an indication that I'm just trying to piss him off, but I know I pissed someone else off....
Click to expand...
Click to collapse
you're such an idiot
love you mean it

Bricked after all this time

I had a lunch TB4g and it just bricked today, I was running ShiftAOSP 1.2 (I believe unrelated) and the .802 radio (possible) but it will just go to the HTC screen and reset and keep trying to boot. I can get into HBOOT and FASTBOOT, I have tried to reflash a root friendly RUU but it didnt fix anything and still cant boot. Just giving you a heads up. I had it overclocked to 1.22, I had it in my car on the way home, sent one text, 23% battery and I plugged it into my CPU USB to charge for a little waiting for some friends to show up and that is when it went into bootloop. Heat was not an issue as I had used it minimally the whole day sending small texts. It did sustain a major G shock 2 days prior but no excessive G or roughness today. Since it can get into HBOOT it might be recoverable but thats to the devs to decide, I have the unlocked 1.04 hboot installed.

i doubt the radio caused it, but that sucks man. see if you can talk verizon into a bionic for a replacement.

Does it bootloop in recovery?
Sent from my HTC Thunderbolt

JBO1018 said:
Does it bootloop in recovery?
Sent from my HTC Thunderbolt
Click to expand...
Click to collapse
he wont be able to get to recovery, hes bricked. i had this sorta happen to me weeks ago but my phone recovered on its own. to say the least i put full insurance on it.

fixxxer2008 said:
he wont be able to get to recovery, hes bricked. i had this sorta happen to me weeks ago but my phone recovered on its own. to say the least i put full insurance on it.
Click to expand...
Click to collapse
He said it boots to the splash screen and he can get into hboot. So I'm confused why you would think he couldn't select recovery in hboot and see what happens. If he already flashed a full stock RUU custom recovery will be gone tho.
Sent from my HTC Thunderbolt

JBO1018 said:
He said it boots to the splash screen and he can get into hboot. So I'm confused why you would think he couldn't select recovery in hboot and see what happens. If he already flashed a full stock RUU custom recovery will be gone tho.
Sent from my HTC Thunderbolt
Click to expand...
Click to collapse
if i were him id just replace it. i just hope my tbolt lasts until the vigor ships.

it will boot to hboot and not reboot, but it will not boot to recovery

Have you tried flashing one of the recoveries that were modified to install through hboot? you can take your sd card out, and using a computer, place the PG05IMG.zip (search here @ XDA) and place it on the root of the card, flash through hboot. then using the computer again, remove the PG05IMG.zip from the sd card and go back into hboot and select recovery. i had to do this not too long ago and it worked for me, maybe it will help you.

I pulled the battery and wont plug it in all night to see if it resets some error it maybe had, my new phone is delivered tomorrow so its not a big deal.

fixxxer2008 said:
if i were him id just replace it. i just hope my tbolt lasts until the vigor ships.
Click to expand...
Click to collapse
I would agree. The whole reason I asked about recovery boot looping is because if it is thats pretty much identical symptoms everyone who had the boot loop of death "brick" thing had. If that is what the situation is I would get it s-on and get VZW to replace because I doubt he caused it.
Sent from my HTC Thunderbolt

fillyo said:
All you cheap ****ers trying to get something for free, if he bricked, his loss. Period.
Click to expand...
Click to collapse
Ditto. He probably told insurance he lost the phone and paid his $100 bucks.
People are so greedy these days. All for nothing and nothing for all.

Doesn't sound design like there was much effort to fix it either.
Questioned posted and shortly after a new one is on the the way?
Keep an extra phone around for instances like this.
Not everything is an insurance claim.
Sent from my A500 using XDA Premium App

You wonder why all the major companies are starting to hate people who root phones. Some people will flash a Rom everyday just to do it and if they miss up their phone they don't seem to care. Now do I think a thunderbolt is worth 700 bucks retail hell no it only cost about 125 to build. But people need to hit up these forums to try to fix their phones before they call Verizon. I read a few post of guys who buy bricks phone fix them and sell them so any bricked phone can be fixed as far as he said. Read up and don't be so quick to clear data as first sign of a problem. Always try what got me out of the bootloop of death.
1. Battery pull
2. Power and hold down volume button
3. Never and I mean never keep a radio stored on root of SD card after install this will cause Hboot to install radio and that is not what we want to do here.
4. Go to recovery
5. Under download folders in your SD card always keep a updated ROM of what ever ROM you are currently using or at least a stable build inside that folder if you are using AOSP keep a stable ROM that last worked for you so no data clear is needed if you are using Sense do the same.
6. I never flash a recovery at this point follow this it saved my phone. Clear cache, clear delvik, format system under mounts and storage.
7. Format is most important since it will not delete recovery if you need to try again. Go to install zip file, select zip file, and install your fresh ROM or a stable build I never have flashed a normal ROM or have I flashed back to a down graded GB ROM.
8. Reboot after ROM has flashed and your phone will boot correctly.
I hope this has helped it saved me a few times in boot loop of death. Stop clearing data you lose your recovery and stop flashing old GB ROMs thinking they will save you, it might but message me so I can say I told you so.
****NOTE also make sure you are updated to newest CWM there was a problem with bootlooping after flashing a kernel and maybe Rom. I had the problem with flashing a kernel sent me into a bootloop. Update or roll back.******
Sent from my ADR6300 using XDA App

The OP probably gets into recovery for a few seconds then bootloops randomly. If you are not bootlooping in hboot, you are not bricked. Find the stock ruu file and flash that through hboot. Although you will lose root, the phone should work again.

If it's bricked, throw it to the ground and stomp on it til it breaks and claim insurance..... That should piss some people off here
Seriously tho some guy mentioned something about a HBoot friendly RUU. You should look into it
Sent from my SICKLY INFECTED VirusBolt Synergy 3.0 using XDA Premium App

As far as I have seen the random and sudden boot loop of death thing has happend to rooted and stock phones. Leading people much smarter than me to come to the conclusion it is most likely caused by some kind of hardware defect existent in a lot if not all Thunderbolts. If he bricked it trying to flash an hboot from an Incredible or a bad flash because of not taking 30 seconds to check MD5 sums then I would put the blame on him. I'm not trying to condone fraud but if the situation is what I was thinking it might be he shouldn't have to pay because HTC got cheap on some build lots or had some bad quality control. Bootlooping from a bad flash and being able to get into recovery and restore is NOT the same thing I'm talking about. In the situation I'm refering to the ROM and recovery both bootloop. You can still flash an RUU in hboot but even after that the phone still bootloops.
Sent from my HTC Thunderbolt

JBO1018 said:
As far as I have seen the random and sudden boot loop of death thing has happend to rooted and stock phones. Leading people much smarter than me to come to the conclusion it is most likely caused by some kind of hardware defect existent in a lot if not all Thunderbolts. If he bricked it trying to flash an hboot from an Incredible or a bad flash because of not taking 30 seconds to check MD5 sums then I would put the blame on him. I'm not trying to condone fraud but if the situation is what I was thinking it might be he shouldn't have to pay because HTC got cheap on some build lots or had some bad quality control. Bootlooping from a bad flash and being able to get into recovery and restore is NOT the same thing I'm talking about. In the situation I'm refering to the ROM and recovery both bootloop. You can still flash an RUU in hboot but even after that the phone still bootloops.
Sent from my HTC Thunderbolt
Click to expand...
Click to collapse
He could not get into recovery cause he cleared data, can't get there is there is not one. And it didn't seem to me like he tried to flashed CWM from HBoot either.
Sent from my ADR6400L using XDA App

Grnlantern79 said:
He could not get into recovery cause he cleared data, can't get there is there is not one. And it didn't seem to me like he tried to flashed CWM from HBoot either.
If he can't think of a way to fix it send it to me will have it running in a couple of google searches.
Sent from my ADR6400L using XDA App
Click to expand...
Click to collapse
Sent from my ADR6400L using XDA App

I tried to get into recovery a few times before doing anything, it would just go black and reboot to the HTC logo. As a last attempt I tried to load a rooted a ruu, it installed but didnt not boot. I have the 1.04 modded hboot so I dont think I can overwrite recovery. Either way, contrary to your beliefs I will not claim insurance on it, although this is a warranty issue, these phones are dropping left and right. I just moved to tmobile this week and my sensation 4g and G2x are supposed to be delivered today.

Thanks for your ideas but I tried to reflash recovery and it installed through hboot but it will just reset before it loads. I still have s-off and my emmc was the sem08g. I am going to plug it in and just let it boot loop all day while I am at work, maybe it will get out, maybe it wont, either way is it wont hurt anything.

[Q] Stuck on SGSIII Bootscreen

Before you post, "BLAKDSKF READ OTHER FORUMS BLUSDFLU!!!!!!!111!!!", please, PLEASE, read the whole post. I am not illiterate or a fool. I've spent the last few days researching similar posts, both on xda and other sites, and as far as I've found, this is the only post of this kind on the Verizon SGSIII forums, though there are some that are somewhat similar in the other SGSIII forums (though I think the root of the problem is different). If you can prove me wrong, please redirect.
The Long Story:
ok. SO. I was trying to root my SGSIII, unlock the bootloader, and install CM10. Simple enough, right? Not so. I got through the rooting tutorial at Link 1 relatively smoothly. For the record, I did the composite root and bootloader combo, and I installed CWM Touch Recovery, as per the guide. I also restored the Jellybean Bootchain. I think it was at this point I downloaded Titanium Backup (because forethought is not my forte) and backed up all my apps. I also made a backup with CWM Recovery, but there were errors. I forget the reason, but it aborted backup. I then tried to make a backup onto my external sd card, and some other errors popped up. Mainly that it couldn't find /android.secure (something along those lines) or /sd-ext (might have been something else. I'm going off memory) and skipped them. It still made the backup, so my illiterate, foolish self decided to roll with it and go ahead.
I then went ahead to Link 2, and with it being 2 AM, I stupidly decided to screw trying to figure out how to use Heimdall 1.4rc1 and continue to use ODIN for flashing. After all what's the difference, I thought. One flashing program is the same as another. I flashed the first two files. Well, in truth, I'm not sure if I flashed the first file. Since I just made a single folder for all the SGSIII Verizon flashing stuff, I had two files with similar names at the time. One from Link 1 and one from Link 2. The only difference was one was a boot chain, the other was a boot loader. Also, one ended with .md5 while the other ended with .tar. Sadly I tiredly picked one and flashed it. I think it was the .md5 one, but I'm not sure. Around this point, my micro sd card reader broke, so I decided to just use my other phone (Motorola Photon 4g running Joker's CM9) as a reader of sorts. I swapped them, used my phone to put the zip from Link 2 on it, and swapped them back. I say this because I'm not sure if that is what broke my md5sums or not (more on that in a sec).
Well, surprise, surprise, my phone got stuck on the animated, colorful "4G LTE" boot screen, except it was fully black, though the noise was playing. I think to myself, "No biggie. I'll just restore my previous backup," so I go back to restore it when I get the error 'md5sum mismatch'. I look up the problem, and after extensive, 3AM research (read: clicked the first link on google and blindly followed), I went with one guys advice, which was to create a blank nandroid.md5 file to force the restore. I figured, "Hey. This is pretty risky. I think I'll just restore the bootloader instead of the whole restore." Or at least that's what was going through my head as I went through with restoring the whole backup. Lo and behold, /system was corrupted, I assume, and it aborted restoring it. I reboot my phone only to find out that my phone gets stuck on the SGSIII boot logo. This is where I am now. I would go through with flashing a stock rom onto it to undo everything I've done, but ODIN won't recognize my phone anymore. I can still get into Download and Recovery Mode. All my backups are useless at the moment.
In Short:
I tried to root, unlock the bootloader, and flash CM10 on it
I messed up and ended up restoring a broken backup, md5sums be screwed.
Now ODIN won't recognize my phone and it's stuck at the SGSIII boot screen.
Is there any way to fix this or at least return it back to stock so I can start again?
If there's any other information you need, just ask. I'd be happy to give it. :laugh: This is my first post on these forums, so I'm not sure what information is standard. If you have any idea of what it might be, please drop a comment or something rather than just leaving. I'd like to know that people are actually reading this post.
And on an unrelated note, every time I try to flash with Heimdall, I get an error about there not being a certain .dll file, even though I downloaded the package from Link 2. Am I doing something wrong?
EDIT: I've already tried factory resetting and wiping the cache/dalvik cache. Most of my info is backed up anyway.
Links:
Link 1: http://forum.xda-developers.com/showthread.php?t=2046439
Link 2: http://wiki.cyanogenmod.org/w/Install_CM_for_d2vzw

What happens when you plug your phone into your PC? Have you tried deleting the drivers then reinstalling them either from Samsung or from the Kies program? You really have to try to mess up this phone and it seems like you definitely tried very hard in this regard.
Edit: Idk anything about Heimdall, I use Odin only so I can't help you there.

SlimSnoopOS said:
What happens when you plug your phone into your PC? Have you tried deleting the drivers then reinstalling them either from Samsung or from the Kies program? You really have to try to mess up this phone and it seems like you definitely tried very hard in this regard.
Edit: Idk anything about Heimdall, I use Odin only so I can't help you there.
Click to expand...
Click to collapse
I hadn't noticed before, but my phone doesn't even show a charge screen when plugged in, but that might just be the settings on the phone pre-root. I'm not sure because I left the phone on to see if it was just a time thing. The phone died and I have to recharge it.
After goofing around with the phone while on the charger for a while, I can get a charge screen to show up for a second. The standard "battery with a loading circle" type symbol for this type of error.
I just reinstalled the drivers. I'll let the phone charge for about 10 minutes or so, then test the phone.

dudeman9199 said:
I hadn't noticed before, but my phone doesn't even show a charge screen when plugged in, but that might just be the settings on the phone pre-root. I'm not sure because I left the phone on to see if it was just a time thing. The phone died and I have to recharge it.
After goofing around with the phone while on the charger for a while, I can get a charge screen to show up for a second. The standard "battery with a loading circle" type symbol for this type of error.
I just reinstalled the drivers. I'll let the phone charge for about 10 minutes or so, then test the phone.
Click to expand...
Click to collapse
Well if it died you should leave it on the charger longer than ten minutes if it is charging. If Odin recognizes it, your first step would be to try flashing a stock image.

SlimSnoopOS said:
Well if it died you should leave it on the charger longer than ten minutes if it is charging. If Odin recognizes it, your first step would be to try flashing a stock image.
Click to expand...
Click to collapse
Thanks. It would seem that it now recognizes the phone, from what I can tell. As soon as I get a stock rom, I'll flash it and post an update.

dudeman9199 said:
Thanks. It would seem that it now recognizes the phone, from what I can tell. As soon as I get a stock rom, I'll flash it and post an update.
Click to expand...
Click to collapse
Great! Use Droidstyle's guide or MrRobinson's thread for the proper images. Should be a good starting point.
Sent from my SCH-I535 using xda app-developers app

I just wanted to add that THIS is how you do a first post or any help needed post! Great details and is obvious you researchedyour problem as well.
The errors in cwm are actually normal. I think the corrupt backups are unrelated.
Sent from my SCH-I605 (AKA NOTE 2)

SlimSnoopOS said:
Great! Use Droidstyle's guide or MrRobinson's thread for the proper images. Should be a good starting point.
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
Thanks. I've finally booted up into the setup wizard. I guess from here on I can re-root, unlock the bootloader, and *hopefully* get a working backup and eventually flash CM10.
I guess this means Problem Solved? Again, Thanks.
kintwofan said:
I just wanted to add that THIS is how you do a first post or any help needed post! Great details and is obvious you researchedyour problem as well.
The errors in cwm are actually normal. I think the corrupt backups are unrelated.
Sent from my SCH-I605 (AKA NOTE 2)
Click to expand...
Click to collapse
Thanks. I'm just gonna assume that the problems stemmed from swapping the sd card and leave it at that.

dudeman9199 said:
Thanks. I've finally booted up into the setup wizard. I guess from here on I can re-root, unlock the bootloader, and *hopefully* get a working backup and eventually flash CM10.
I guess this means Problem Solved? Again, Thanks.
Thanks. I'm just gonna assume that the problems stemmed from swapping the sd card and leave it at that.
Click to expand...
Click to collapse
Perfect! Which thread did you end up using btw?
Sent from my SCH-I535 using xda app-developers app

SlimSnoopOS said:
Perfect! Which thread did you end up using btw?
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
I used droidstyle's thread for getting the stock rom.

[Q] Stuck in recovery mode, can't mount sd card

I messed up bad. :crying: I have some idea what I'm doing but I just made a terrible mistake. I was running Viperxl with exernalx kernel and I wanted to try cyanogenmod 10.1. I had a back up of the factory version that was rooted and a back up of viperxl/externalx. I tried flashing the cyanogenmod rom and it was stuck in the loading screen. So I rebooted back into recovery then tried to flash the rooted factory backup I had. Same thing. It was stuck in the loading screen. Here's where I went wrong. I rebooted back into bootloader and tried factory reset without really knowing what it did. Now I have no back up. When I try to mount the sd card my computer says it has to format it first. And to format it, my computer has to clear it. And luckily I didn't just go for that. Any idea of what to do next? I'm stuck lol. Thanks for the help
Edit: Ok it's not really an sd card. All I can describe is it says drive G: and it has 10gb of internal storage(but it it has 16gb total it just says it will wipe about 10gb storage, can someone explain?) that I would have to all wipe out to format. I thought you would just call it an internal sd card but I don't think that's right. I just don't want to wipe anything important

Mr_Staples said:
I messed up bad. :crying: I have some idea what I'm doing but I just made a terrible mistake. I was running Viperxl with exernalx kernel and I wanted to try cyanogenmod 10.1. I had a back up of the factory version that was rooted and a back up of viperxl/externalx. I tried flashing the cyanogenmod rom and it was stuck in the loading screen. So I rebooted back into recovery then tried to flash the rooted factory backup I had. Same thing. It was stuck in the loading screen. Here's where I went wrong. I rebooted back into bootloader and tried factory reset without really knowing what it did. Now I have no back up. When I try to mount the sd card my computer says it has to format it first. And to format it, my computer has to clear it. And luckily I didn't just go for that. Any idea of what to do next? I'm stuck lol. Thanks for the help
Click to expand...
Click to collapse
You corrupted sd card doing factory reset from bootloader.. don't ever do that on this phone. After formatting on pc copy Rom to sd and flash. If your on hboot 1.14 or higher you need to flash boot.img from rom.zip you installed. Unless your s-off
Sent from my HTC One XL using xda premium

I made the same mistake a few months back. Just RUU back to stock and you're good.

31ken31 said:
You corrupted sd card doing factory reset from bootloader.. don't ever do that on this phone. After formatting on pc copy Rom to sd and flash. If your on hboot 1.14 or higher you need to flash boot.img from rom.zip you installed. Unless your s-off
Sent from my HTC One XL using xda premium
Click to expand...
Click to collapse
Yeah I learned that the hard way lol. I usually check before doing stuff like that but... no excuse, I just went stupid. I thought it would be bad to format the disk since it wipes everything off? Is the important software on the other drive and not the 10gb sd card? Noob question but I just want to make sure before I make this irreversible
Edit: Ok I put more thought into this and I don't think you would call it an sd card. Just internal storage. But I see you have the same phone so I hope your advice is good. I just need to be reassured before doing anything else

RollTribe said:
I made the same mistake a few months back. Just RUU back to stock and you're good.
Click to expand...
Click to collapse
I can't mount the sd card though since I factory reset it. Unless I format it on my computer and doing that will wipe everything off. And I'm not sure how that will turn out. So until then I'll keep searching around or hopefully get an answer. Person above said to format it but I'm just not sure yet and would hate to brick it. I'm kinda new to this so forgive my noobish questions on this stupid mistake

Mr_Staples said:
I can't mount the sd card though since I factory reset it. Unless I format it on my computer and doing that will wipe everything off. And I'm not sure how that will turn out. So until then I'll keep searching around or hopefully get an answer. Person above said to format it but I'm just not sure yet and would hate to brick it. I'm kinda new to this so forgive my noobish questions on this stupid mistake
Click to expand...
Click to collapse
It will only wipe the sd card photos, downloads, music s**t like that.if you want stock unrooted then ruu... If you want custom Rom follow my instructions..
Sent from my HTC One XL using xda premium

31ken31 said:
It will only wipe the sd card photos, downloads, music s**t like that.if you want stock unrooted then ruu... If you want custom Rom follow my instructions..
Sent from my HTC One XL using xda premium
Click to expand...
Click to collapse
And chances are, since you've corrupted the memory, the data will be gone anyway unfortunately.
Sent from my Evita

timmaaa said:
And chances are, since you've corrupted the memory, the data will be gone anyway unfortunately.
Sent from my Evita
Click to expand...
Click to collapse
It's already gone.. I did it once, just to see what it did lost everything. And has anyone noticed the newbies posting strange answers around here lol. Guess u gotta get ur ten posts somehow
Sent from my HTC One XL using xda premium

31ken31 said:
It's already gone.. I did it once, just to see what it did lost everything. And has anyone noticed the newbies posting strange answers around here lol. Guess u gotta get ur ten posts somehow
Sent from my HTC One XL using xda premium
Click to expand...
Click to collapse
Oh yeah. My heart skips a beat when I see that lol.
Sent from my Evita

Just format it... If your that concerned you shouldn't be messing with the phone.. look at it this way it's corrupted and won't boot... No choice anymore..
You should read read read before doing stuff like this... It's easy to brick these phones. When I root and modify phones I'm prepared for something to screw up. But I personally spent days learning what to do before I started..
Sent from my HTC One XL using xda premium

31ken31 said:
It will only wipe the sd card photos, downloads, music s**t like that.if you want stock unrooted then ruu... If you want custom Rom follow my instructions..
Sent from my HTC One XL using xda premium
Click to expand...
Click to collapse
Thanks for the quick reply! That's what I thought. I just scared myself away from doing anything else. I don't always f up but when I do, I f up real bad lol. Most profound way to learn imo. And not to jack my own thread but can you run elementalx 6.7 with cyanogenmod 10.1? Can't seem to find answer and I'm not familiar enough with this stuff yet(obviously)

No you absolutely cannot use elemental kernel with aosp based ROMs. It's only for use with sense ROMs. It probably says that in the OP of the kernel thread. You really need to do some reading.
Sent from my Evita

Mr_Staples said:
Thanks for the quick reply! That's what I thought. I just scared myself away from doing anything else. I don't always f up but when I do, I f up real bad lol. Most profound way to learn imo. And not to jack my own thread but can you run elementalx 6.7 with cyanogenmod 10.1? Can't seem to find answer and I'm not familiar enough with this stuff yet(obviously)
Click to expand...
Click to collapse
Elemental x is for sense only
Sent from my HTC One XL using xda premium

Yeah, exactly like I said, it's the first line of the kernel thread.
Sent from my Evita

31ken31 said:
Just format it... If your that concerned you shouldn't be messing with the phone.. look at it this way it's corrupted and won't boot... No choice anymore..
You should read read read before doing stuff like this... It's easy to brick these phones. When I root and modify phones I'm prepared for something to screw up. But I personally spent days learning what to do before I started..
Sent from my HTC One XL using xda premium
Click to expand...
Click to collapse
Didn't see this till now. Is it that easy? I thought it took something more technical and risky than this. I read into this for two days straight before doing anything and everything went smooth. And I did back it up. Not sure what went wrong there when trying to flash it because it worked earlier. There's just a few things I'm not too familiar with like the factory reset. And for some reason I tried it assuming it just reset it back to how it came out of the factory. It's all a learning process

I guess you leaned the hard way huh, just remember never to factory reset in bootloader again, only in recovery. And do some more reading, your question about elemental kernel would have answered itself if you took the time to read properly.
Sent from my Evita

timmaaa said:
No you absolutely cannot use elemental kernel with aosp based ROMs. It's only for use with sense ROMs. It probably says that in the OP of the kernel thread. You really need to do some reading.
Sent from my Evita
Click to expand...
Click to collapse
31ken31 said:
Elemental x is for sense only
Sent from my HTC One XL using xda premium
Click to expand...
Click to collapse
Ok that makes sense. Idk why I didnt just check the kernel thread. I was just being lazy. Well.. you're definitely right. I got plenty of reading to do. I just always over analyze things and search stuff too specific which makes asking these questions on threads easier

There's nothing wrong with asking questions. But usually the same question has been asked and answered before, so be sure to search effectively first, it's part of xda rules.
Sent from my Evita

Yeah I understand that lol. I thought about that before asking. I was mostly just wondering if it was ok to wipe the memory to format it. And I explained everything just to check and make sure there was nothing else that could be done. Which I probably could've found the answers myself but it's a bit overwhelming making these mistakes without knowing what to do. Just want to cry out for help. Things always look so much easier retrospectively lol. And they usually are too

All in all I think you did the right thing, you have the right information we need to tackle the problem. You'll find xda to be a great place, it's full of like minded people that are willing to lend a hand when the **** hits the fan.
Sent from my Evita

[Q] First time rooting/S-Off/new ROM

Is there such thing as a guide like this one but that is up to date and with working links? I want to flash a new ROM onto my phone, but the guides I've found here and elsewhere have broken links, or use language that I don't understand, or skip vital steps. I've been working on this for four hours straight and I haven't gotten a single guide to work, or get stuck, or something else that's really dumb. For someone who has worked on computers for the last 17 years this is extremely frustrating. I'm very new to the android modding scene and apparently it's not just a community, but an entirely different culture and I'm feeling a bit shocked and confused. I have like 30 tabs open with guides, info, different ROMs, different ways to do it, etc and the more I learn the less I understand how to do this :/ I just want to get my phone working with a ROM that's very similar to stock Sense but without the crappy bloatware and memory issues. Miktouch is the one I thought I wanted, but apparently hasn't been updated in almost a year, and bulletproof/doubleshot is confusing. I can't even figure out how to root and get S-Of... Gah!
Please help.
This guide is confusing and skips steps or lacks real explanations.
Thank you.

First thing you want to do is root your phone, this is done by unlocking you bootloader through the HTC dev website. There is a tutorial that is stickyed in the developer section called something like root from any bootloader. I suggest to read that a bit.
Once you followed those steps and unlocked your bootloader you can decide if you want to remove all security flags (highly recommend this, but some find it difficult) in the same guide it explains what radio s-off is and links you to the jbear site to do the wire trick (needs Linux) (or find weekendstoshort for a way to do it in windows)
Feel free to ask more questions but all answers should be found in these xda threads and jbear site, no need to Google anything for this
Sent from my Nexus 4 using xda premium

I hope so...I'll give it another go tomorrow. I'm still quite frustrated at it. I wish I knew someone who had done it and could show me in person.

GiftigDegen said:
I hope so...I'll give it another go tomorrow. I'm still quite frustrated at it. I wish I knew someone who had done it and could show me in person.
Click to expand...
Click to collapse
MikTouch is optimized stock... So updating it farther would take it a direction we wasn't going with it.
Bulletproof is even older. We don't have much here... But what's here is solid
Sent from my Nexus 4 using Tapatalk 4 Beta

First timer here as well (although long time computer user/programming familiar so I might have a better understanding of some things than you) and I was able to fully unlock, S-OFF, and load up a JB rom to my phone using the guide right on this site (http://forum.xda-developers.com/showthread.php?t=1801106) and some help from some online friends that have done this kind of thing before. I found all links to be working, and pretty much all steps to be covered. The I guess hardest part was the permanent S-OFF using the wire trick. I had to burn an Ubuntu live cd and boot a laptop with it, but I was even able to get that step done. A little frustrating with the timing, I think it took me about 8 tries until it finally unlocked. The only thing I think I initially missed was wiping all 3 caches, so I did a dirty flash that got stuck on the boot screen. After I wiped and loaded again, no problems. If you'd like any additional help, I get pretty bored at work, so find me on aim or gchat, or just shoot me a PM here, I think I should get notified
Good luck, it's not as bad as I thought it would be
Also I haven't personally tried it, but feel free to peruse this thread as well: http://forum.xda-developers.com/showthread.php?t=1696373
Note you'll need to have already achieved HTCDev unlocked and be rooted to use this (covered in that first link)
Hope that helps!

PsychoPhreak said:
First timer here as well (although long time computer user/programming familiar so I might have a better understanding of some things than you) and I was able to fully unlock, S-OFF, and load up a JB rom to my phone using the guide right on this site (http://forum.xda-developers.com/showthread.php?t=1801106) and some help from some online friends that have done this kind of thing before. I found all links to be working, and pretty much all steps to be covered. The I guess hardest part was the permanent S-OFF using the wire trick. I had to burn an Ubuntu live cd and boot a laptop with it, but I was even able to get that step done. A little frustrating with the timing, I think it took me about 8 tries until it finally unlocked. The only thing I think I initially missed was wiping all 3 caches, so I did a dirty flash that got stuck on the boot screen. After I wiped and loaded again, no problems. If you'd like any additional help, I get pretty bored at work, so find me on aim or gchat, or just shoot me a PM here, I think I should get notified
Good luck, it's not as bad as I thought it would be
Also I haven't personally tried it, but feel free to peruse this thread as well: http://forum.xda-developers.com/showthread.php?t=1696373
Note you'll need to have already achieved HTCDev unlocked and be rooted to use this (covered in that first link)
Hope that helps!
Click to expand...
Click to collapse
I'm following the first guide you linked. So far it's working I just flashed CWmod on and I loaded it according to the instructions in the guide "After fastboot finishes, disconnect your MT4GS, go into bootloader, and go to “RECOVERY.” You should now be in ClockworkMod Recovery 5.0.2.7. The first thing I would do in CWM Recovery is make a backup of your stock ROM for safe keeping. "
But I forgot to d/c my phone. It still loaded CWmod and I navigated to backup/restore and clicked it. Right now my phone has the clockwork logo in the middle but it didn't give me any prompts after selecting backup/restore. What's it doing? It's been doing this for like 5 minutes. Should I be worried that I forgot to d/c the cable and whatnot?
Thanks

GiftigDegen said:
I'm following the first guide you linked. So far it's working I just flashed CWmod on and I loaded it according to the instructions in the guide "After fastboot finishes, disconnect your MT4GS, go into bootloader, and go to “RECOVERY.” You should now be in ClockworkMod Recovery 5.0.2.7. The first thing I would do in CWM Recovery is make a backup of your stock ROM for safe keeping. "
But I forgot to d/c my phone. It still loaded CWmod and I navigated to backup/restore and clicked it. Right now my phone has the clockwork logo in the middle but it didn't give me any prompts after selecting backup/restore. What's it doing? It's been doing this for like 5 minutes. Should I be worried that I forgot to d/c the cable and whatnot?
Thanks
Click to expand...
Click to collapse
I wouldn't worry, and I'm not entirely sure what it's trying to do, perhaps the possibility of USB storage is throwing it off. At this point I'd say just try to disconnect it, pull the battery, and start back up into recovery, but without the USB attached this time. I imagine then you'll be fine and able to backup the stock image like they say for safe keeping.
One more dummy question (tech support for many years, always check the simple stuff first...) you do have SOME SD card in there right?

PsychoPhreak said:
I wouldn't worry, and I'm not entirely sure what it's trying to do, perhaps the possibility of USB storage is throwing it off. At this point I'd say just try to disconnect it, pull the battery, and start back up into recovery, but without the USB attached this time. I imagine then you'll be fine and able to backup the stock image like they say for safe keeping.
One more dummy question (tech support for many years, always check the simple stuff first...) you do have SOME SD card in there right?
Click to expand...
Click to collapse
Yeah, 32gb =)

booted into recovery, clicked on bacup/restore...still just showing the logo in the middle.
(PS any mods out there listening, I'd love to have that 5 minute restriction removed =D )
Okay, so the select button changes from power to the scroll pad once in recovery...good to know.

GiftigDegen said:
booted into recovery, clicked on bacup/restore...still just showing the logo in the middle.
(PS any mods out there listening, I'd love to have that 5 minute restriction removed =D )
Okay, so the select button changes from power to the scroll pad once in recovery...good to know.
Click to expand...
Click to collapse
NVMD....You got it now.

strapped365 said:
MikTouch is optimized stock... So updating it farther would take it a direction we wasn't going with it.
Bulletproof is even older. We don't have much here... But what's here is solid
Sent from my Nexus 4 using Tapatalk 4 Beta
Click to expand...
Click to collapse
Using CWM to flash Miktouch now. Hopefully it works... =D

Just remember, if you are "S-On" you're going to need to fastboot flash boot boot.img after your ROM is thru flashing or you will hang up at the boot animation.

strapped365 said:
MikTouch is optimized stock... So updating it farther would take it a direction we wasn't going with it.
Bulletproof is even older. We don't have much here... But what's here is solid
Sent from my Nexus 4 using Tapatalk 4 Beta
Click to expand...
Click to collapse
K. First impressions:
When I restart the phone, the first thing it does is force stop Gmail and Youtube several times. Is this supposed to happen?
Also, I'm extremely impressed with the speed of the restart. It's at LEAST twice as fast as stock.
And, Genius button doesn't work even after installing the patch linked to on your website (universal.zip).

WeekendsR2Short said:
Just remember, if you are "S-On" you're going to need to fastboot flash boot boot.img after your ROM is thru flashing or you will hang up at the boot animation.
Click to expand...
Click to collapse
Thanks Weekends. I did that and it's installed, though I fastboot flash boot boot.img before I used CWM to flash the rom. Does that make a difference? Do you think doing it that way will fix the force close mentioned above?

If there's not a fix for the gmail/youtube force closes, is it possible to do bulletproof with s-on? Thoughts? I really want to stick as close to stock MT4GS but with as solid a system as possible.

Flashing boot image before ROM will overwrite kernel
Wipe all
Flash ROM
Flash boot
Reboot
Sent from my Nexus 4 using xda premium

demkantor said:
Flashing boot image before ROM will overwrite kernel
Wipe all
Flash ROM
Flash boot
Reboot
Sent from my Nexus 4 using xda premium
Click to expand...
Click to collapse
Another noob question. How do I wipe all?
Also, when I use CWM to install Mikrom it atuo restarts and loads up. Then do I restart again and go fastboot the new kernal?
Thank you all for how much help you have given me.

At the end of the updater-script there must be a reboot command, but being this ROM is based of stock you may not need to flash the kernel anyway.
Best methods for wiping is one of bluex's superwipe scripts or with fastboot
fastboot erase system -w
But being you are s-on that command may fail.
But always do a wipe data/factory reset, wipe cache, and wipe dalvik in recovery.
It also good practice to make a nandroid of current ROM before you flash anything
Sent from my Nexus 4 using xda premium

demkantor said:
At the end of the updater-script there must be a reboot command, but being this ROM is based of stock you may not need to flash the kernel anyway.
Best methods for wiping is one of bluex's superwipe scripts or with fastboot
fastboot erase system -w
But being you are s-on that command may fail.
But always do a wipe data/factory reset, wipe cache, and wipe dalvik in recovery.
It also good practice to make a nandroid of current ROM before you flash anything
Sent from my Nexus 4 using xda premium
Click to expand...
Click to collapse
Mmkay, working doing this now.
Quick question, hopefully someone can give me a link, but I'd love the install the depaginated app drawer, genius fix and menu wake up mods for this, but the links are broken (dev-host times out). Any help?

See weekends mirror thread
Sent from my Nexus 4 using xda premium