Database Info

[Q] NexusS (i9020T) hard bricked, at which step did I go wrong?

Hi everyone, I had a problem with my previous nexus s (I have since gotten a working replacement) and I was wondering where exactly I messed up so in the future I can avoid this
Here is what I did on my previous phone:
1. I flashed ics onto my device from the ota update package from androidcentral, it was 4.0.3. (This worked great and I had it on my phone for 2-3 months before I tried the next steps.)
2. I rooted my device successfully using the guide at nexusshacks.
3. I also flashed TWRP recovery (fastboot) and superuser using the above guide/links
4. When I would turn off my phone it would boot to a screen with a red triangle and an opened android bot. So what I would have to do is flash twrp recovery everytime I turned the phone on just to get it to work.
5. What I wanted to do was keep the stock rom but still have twrp recovery without it making me reflash it on every boot. So I clicked install and tried to flash the stock rom (update package from the link in step 1) with twrp recovery. It then turned off my phone and hard bricked it. I couldn't turn it on anymore and a new battery didn't fix it.
I was able to get a replacement now and I was just wondering at which step did I go wrong? I THINK that I should have wiped my cache before I tried to reflash the stock rom but maybe I'm way off base here. This is why I posted a question here so hopefully some of you guys can help.
I did think about posting in another thread, but I didn't wanna threadjack or anything... and his problem also seemed a bit different then mine. Also, sorry about not being able to provide the specific links it won't let me post them until I've posted 8 times.

I don't know for sure but team win recovery has been reported to corrupt the device's efs directory. I've even had problems myself using clockwork recovery. I've moved on to razor recovery and haven't looked back.
This is the most flash-friendly phone I've ever owned, and razor recovery rivals amon ra (which was awesome on my g1 and evo). I really think it may have just been the recovery you were using... Somebody correct me if i'm wrong.
Sent from my Nexus S 4G using Tapatalk

I had once corrupted one of the partition. I fixed to by flashing stock recovery and stock rom.
Use adam outler's unbrickable mod tool. It can be found in android development section.
Sent from my Nexus S using XDA

Thanks for the replies.
That's interesting about twrp... I didn't know that. Truth be told, the only reason I went for it over other ones like clockwork mod was because the UI looked pretty nice and easy to use. Also the guide I followed at nexusshacks used that, so I wanted to stay consistent with it.
jishnu7, it's a little late for that now however as I actually have already received a working replacement from my carrier, but in the future if something ever does go wrong (hopefully not) I will definitely check that out.
The main thing I'm wondering is if it messed up because I tried to reflash the stock rom essentially over top itself (was hoping that by doing that, it would stop making me reflash twrp on every reboot) or if it was because I didn't wipe the cache before the flash.
Also, what I really wanted to do with my phone was to keep the stock rom but be able to overclock my cpu/gpu. I was hoping I could set different overclocks for different things (I've heard of kernels where you can downclock your phone when the screens off and have it overclocked slightly while you're using it, that would be something I'd like to have). I figured to install those kernels I would have to root my phone, replace stock recovery and install superuser so that's why I tried to do that. Once again, I'm pretty new to all this stuff for my phone.

Sorry to bump this thread again, but I would really like to know how I could avoid what happened to me for the future. I think it's because I flashed the stock 4.0.3 rom over itself (was hoping that by doing that twrp recovery would stay on the phone after reboot).
What I would like to do is install something like CM9 or AOKP and use the Matr1x kernel so I could undervolt or overclock my phone.

I seriously dont get how u hard bricked your phone...
the reason you are thinking is you reflashed stock rom without wiping cache, as per my experiece its not at all the reason
now, whats my experience??
...I have some fault with my nexus device and I'm working on it,,and I did everything I could do...one of the thing out of those things was reflashing stock rom without wiping,and i did it quite a several times...my device never hard bricked,,however it was soft bricked for many times,,and i recovered from it
so reflasing a stock rom over stock rom, over ICS, over some themed custom rom,will not hard brick your device, you must be missing something none of your steps sounds suspecious
P.S:- pulling out battey while flashing something like this sounds suspecious, never tried though

I'm not sure what happened either to be quite honest with you. Since giving it another shot now with my new fresh phone I have had great success!
I did everything I wanted to do all in one go. Rooted it, install CWM touch, install AOKP (went with milestone 4 cuz I heard newest build 29 has some bugs) + gapps and installed matr1x kernel 18.5 bfs.
The only thing I did different from last time was installing CWM touch (instead of twrp) and flashed aokp this time (instead of reflashing 4.0.3 over itself).

I would just avoid step 2 at all cost.
The nexus s hacks dude is a tool.

Flashing Captivate - Questions

I am looking to flash my phone to ICS/Jelly Bean and have some questions.
1. Does updating to those ROMs impact multitasking? I wonder because they probably eat up a lot more RAM and when I use browsers, I tend to open a lot of tabs which is heavy on RAM usage
2. Is there a performance difference between JB and ICS on the Cappy?
3. Should I go with a built-in kernel or flash a separate one?
4. My phone has never had its kernel changed, same default filesystem, lag etc. etc., should I do anything extra before flashing?
5. I read on another post on the front page that the JB/ICS ROMs also use the internal SD card, mine is mostly full at the moment, how much space do the new ROMs take up?
Thanks for any help. Been considering flashing for a year but my phone recently got the lock screen button stuck problem and now I'm at a crossroads, either I buy a new phone entirely or maybe try to keep this one for a year until my contract runs out and deal with the lock screen problem.

skomes said:
I am looking to flash my phone to ICS/Jelly Bean and have some questions.
1. Does updating to those ROMs impact multitasking? I wonder because they probably eat up a lot more RAM and when I use browsers, I tend to open a lot of tabs which is heavy on RAM usage
2. Is there a performance difference between JB and ICS on the Cappy?
3. Should I go with a built-in kernel or flash a separate one?
4. My phone has never had its kernel changed, same default filesystem, lag etc. etc., should I do anything extra before flashing?
5. I read on another post on the front page that the JB/ICS ROMs also use the internal SD card, mine is mostly full at the moment, how much space do the new ROMs take up?
Thanks for any help. Been considering flashing for a year but my phone recently got the lock screen button stuck problem and now I'm at a crossroads, either I buy a new phone entirely or maybe try to keep this one for a year until my contract runs out and deal with the lock screen problem.
Click to expand...
Click to collapse
1. In my experience multitasking isn't a problem on either but I don't open a lot of tabs in my browser so could be different for you.
2. If you want good clean performance go with ICS. Jelly Bean roms are still more or less in beta.
3. As far as kernels go stick with the kernel built into the from unless it instructs you otherwise. Or if you are looking for some feature that one kernel offers that another doesn't.
4. Read, read, and then read the instructions again for whatever rom you are going to and follow them. Depending on where you are starting from you may have to do different things.
5. I've personally never paid attention to how much it uses the internal SD if at all. I do know that some ICS and Jelly Bean roms have potential to format your SD card during the flash so make sure you do a backup before moving forward.
When you say the lock screen are you talking about the power button? If yes be very careful moving forward with any flashing. I say that because the power button is used to put the phone into recovery. There are other methods to get into recovery but they don't work for everyone.
Sent from my SGH-I897 using xda app-developers app

m1batt1 said:
1. In my experience multitasking isn't a problem on either but I don't open a lot of tabs in my browser so could be different for you.
2. If you want good clean performance go with ICS. Jelly Bean roms are still more or less in beta.
3. As far as kernels go stick with the kernel built into the from unless it instructs you otherwise. Or if you are looking for some feature that one kernel offers that another doesn't.
4. Read, read, and then read the instructions again for whatever rom you are going to and follow them. Depending on where you are starting from you may have to do different things.
5. I've personally never paid attention to how much it uses the internal SD if at all. I do know that some ICS and Jelly Bean roms have potential to format your SD card during the flash so make sure you do a backup before moving forward.
When you say the lock screen are you talking about the power button? If yes be very careful moving forward with any flashing. I say that because the power button is used to put the phone into recovery. There are other methods to get into recovery but they don't work for everyone.
Sent from my SGH-I897 using xda app-developers app
Click to expand...
Click to collapse
I guess that is a good point. My lock screen buttons works but not 100% of the time. Originally the problem hit and it didn't work at all, now it works probably 70% of the time. I didn't remember that I would need it to get into recovery. Maybe I would need to buy a jig, but I guess I should flash now in case it stops working entirely down the line.
I'm also considering buying an S3 but it is quite expensive, at least $620 for it unlocked.
I had wanted to jump into JB because I was looking for decent performance and I don't think I'll be flashing a ton. I've got like 80 apps, tons of home screen stuff etc. that I don't want to restore many times. I just figured if JB is faster, I'd rather go with it.
Thanks for the helping me out.

A jig isn't the best bet because it forces it into download mode. If your button is currently working go for it. Jelly bean roms will eventually be the best thing out there but most of the roms for it haven't been perfected yet.
I have been on everything from 2.1 and up and I can tell you ICS is the best stable thing out there. At least in my opinion.
Sent from my SGH-I897 using xda app-developers app

skomes said:
I guess that is a good point. My lock screen buttons works but not 100% of the time. Originally the problem hit and it didn't work at all, now it works probably 70% of the time. I didn't remember that I would need it to get into recovery. Maybe I would need to buy a jig, but I guess I should flash now in case it stops working entirely down the line.
I'm also considering buying an S3 but it is quite expensive, at least $620 for it unlocked.
I had wanted to jump into JB because I was looking for decent performance and I don't think I'll be flashing a ton. I've got like 80 apps, tons of home screen stuff etc. that I don't want to restore many times. I just figured if JB is faster, I'd rather go with it.
Thanks for the helping me out.
Click to expand...
Click to collapse
I've run a rooted 2.2, a rooted 2.3.5, and a few different ROM's, I find that the easiest to use so far is JB, depending on the ROM itself you may run into a few issues with battery drain, but it's not horrible. Multitasking is fine, but I have OS monitor and a RAM booster for quick mem clearing. The only problems that I've ran into with JB ROM's is that you have make sure the internal memory card is backed up, otherwise you'll lose everything you have on it.
I too have thought about getting a SG3, but after flashing the JB ROM, I think I'm satiated until I absolutely have to upgrade my phone.... meaning I'm probably going to stick with this one for another year or so depending on if I'm able to keep it in decent enough shape. For the CM10 ROM's, they've removed the /datadata folder so that may affect slight performance. I got used to it after flashing a ROM that kept the /datadata folder and noticed that it wasn't giving me enough space to work my usual programs on a consistent basis. But overall I'm content with the ROM I chose and the performance so far.

You can always do adb reboot recovery
Sent from a jelly bean

korockinout13 said:
You can always do adb reboot recovery
Click to expand...
Click to collapse
That is true but adb wouldn't help him much if he's stuck in a boot loop. That's when a functioning power button is important.
Sent from my SGH-I897 using xda app-developers app

skomes said:
I am looking to flash my phone to ICS/Jelly Bean and have some questions.
1. Does updating to those ROMs impact multitasking? I wonder because they probably eat up a lot more RAM and when I use browsers, I tend to open a lot of tabs which is heavy on RAM usage
Click to expand...
Click to collapse
According to my expirience, ICS much better in multitasking, comparing with GB. ICS kernel consumes less RAM and more stable.
skomes said:
2. Is there a performance difference between JB and ICS on the Cappy?
Click to expand...
Click to collapse
JB for cappy is not stable yet.
skomes said:
3. Should I go with a built-in kernel or flash a separate one?
Click to expand...
Click to collapse
If you a going to install CM or AOKP, you defiantly have to install custom kernel. You will also have to install custom baseband (modem). I suppose, same goes to other roms.
skomes said:
4. My phone has never had its kernel changed, same default filesystem, lag etc. etc., should I do anything extra before flashing?
Click to expand...
Click to collapse
Yes. RTFM for the rom you are going to flash. You will have to wipe data and cache, and maybe update bootrom.

I am reading stuff, but a lot of guides say 'Coming from GB' BUT they DO NOT say 'coming from stock', so I wasn't sure if those guides were applicable.
Will CM10 wipe my SD card?
Thanks for all the help so far. Going to flash within a couple of days.
I was figuring Helly Bean but most of the JB roms want you to flash CM10 first anway, so I'll try that out.

^
See TRusselo's Flashin Guide for assistance... http://forum.xda-developers.com/showpost.php?p=19425513&postcount=1
Sent from my SAMSUNG-SGH-I777 using xda premium

Tried following that guide.
Heimdall links are all dead.
Opened Odin, downloaded speedmod kernel, figured I'd install it, then download the rom to SD card and go. I was pretty sure speedmod works with stock Captivate.
Flashed speedmod and now my phone is stuck on the Galaxy S boot screen.
So yeah...that sucked.
Now I'm trying to restore stock with Odin but the instructions don't even say how.
Yeah this is why I don't see myself flashing very often...
And that guide needs more detail.

Ok, well I managed to install CM9.
I'm going to stick with it for now because a couple of you guys warned me off of Jelly Bean.

skomes said:
Ok, well I managed to install CM9.
I'm going to stick with it for now because a couple of you guys warned me off of Jelly Bean.
Click to expand...
Click to collapse
I'm currently on the 8/13 nightly build of Helly Bean (http://forum.xda-developers.com/showthread.php?t=1783064)
I can say that this particular ROM is ready for use as a daily driver. I've been using it for about a week now and haven't experienced any problems.
With that said, it is important to note that as said before, JB roms are still in beta, including this one. Also it is important to say that I did a completely clean install of this particular ROM (Factory data reset, wiped cache, wiped dalvik cache, etc).
Just thought I let ya know that not all JB roms are scary right now. If you're interested in possibly flashing it, here's the official website: http://hellybean.site11.com/index.html
Don't forget to backup your /EFS folder though, recently some people have had problems with their imei being switched, but this is easily avoidable if you take the proper precautions. Other than that, this ROM is great.

Yeah, I actually mentioned Helly Bean on page 1, it was the JB rom I was considering because it was getting rave reviews.
I had a scare last night about my IMEI then I remembered my IMEI doesn't match my box because it was warranty replaced with a refurb for the shutdown issue, lol, I was freaking out but good thing is it made me backup the EFS folder.
Thanks for the support.
I'll give Helly Bean a try in a bit, I hear it is very snappy and I'm excited about that, coming from stock Gingerbread, I really appreciate an OS that doesn't run like crap!
Does Helly Bean wipe your internal SD card? I was searching for that and couldn't find anything, so I think that means no, but wanted to make sure!

skomes said:
Does Helly Bean wipe your internal SD card? I was searching for that and couldn't find anything, so I think that means no, but wanted to make sure!
Click to expand...
Click to collapse
As with any custom ROM there is a potential for odd things happening on one phone that doesn't happen on another. With that being said I flashed helly bean and it didn't format my SD card nor has it effected my efs folder like some people have had trouble with.
Your best bet is to backup everything important to you and the operation of your phone prior to flashing just to be safe.
Sent from my SGH-I897 using xda app-developers app

Backup your efs folder before flashing anything

A few questions before I try Helly Bean, I noted that the kernel is separately available on the download site, am I supposed to flash it separately or is it included with the ROM? The flashing guide doesn't say anything about flashing a kernel.
And I should be able to flash it directly from CM9, correct?
Also this ROM is a lot bigger than CM9, 180MB vs 300MB, does that mean I have far less internal SD space available?

skomes said:
A few questions before I try Helly Bean, I noted that the kernel is separately available on the download site, am I supposed to flash it separately or is it included with the ROM? The flashing guide doesn't say anything about flashing a kernel.
And I should be able to flash it directly from CM9, correct?
Also this ROM is a lot bigger than CM9, 180MB vs 300MB, does that mean I have far less internal SD space available?
Click to expand...
Click to collapse
Answering my own questions in case other people need help.
Yes
Yes
No
I installed Helly Bean but for me, it is laggier than CM9 so I am disappointed.

Odin, or just flash

I'm a little lost, I've been reading for days and can't seem to find my answer..here goes
Coming from droid1 were I could flash new to old and vice versa..had the s3 for a couple of weeks, I'm on beans 13 kernel lean1.0 and hd radio..the other day I was on clean 2.5, and before that on synergy..can I keep bouncing around like that, our do I need to do Odin thingie? I see were root'ers are Odin then taking this new update and looks like killer battery life..I don't really have a preference on roms , just nead a little help on doing it proper..txs

You can just keep flashing until you find a ROM you like. Odin is just basically when things are messed up and you need to go back to stock. I think it was RSD on the Droid 1.
Sent from my Galaxy S3 running Eclipse ROM V2.1

kintwofan said:
You can just keep flashing until you find a ROM you like. Odin is just basically when things are messed up and you need to go back to stock. I think it was RSD on the Droid 1.
Sent from my Galaxy S3 running Eclipse ROM V2.1
Click to expand...
Click to collapse
You can flash it just to go back to stock. Doesn't have to be cause you messed the phone up. I think it's also good to do it occasionally with a pit file to wipe/fix all partitions (not just /system and /data, but ones like the hidden radio/GPS partition etc.)
Sent from my SCH-I535 using xda premium

xsteven77x said:
You can flash it just to go back to stock. Doesn't have to be cause you messed the phone up. I think it's also good to do it occasionally with a pit file to wipe/fix all partitions (not just /system and /data, but ones like the hidden radio/GPS partition etc.)
Sent from my SCH-I535 using xda premium
Click to expand...
Click to collapse
Well of course you can use it to just go back to stock, but the average user only does it when they mess up. I do agree though I personally even I find my daily driver like to start fresh then flash the keeper ROM.
Sent from my Galaxy S3 running Eclipse ROM V2.1

Have been rooted since day of pre-order delivery. Have flashed multiple ICS/JB TW roms. I stay away from AOKP/CM roms just because of loss of features so can't report on those. I have never lost wifi or GPS. Never had sim card error. Had no problems with TWRP and haven't used CWM since worked with Koush on Tbolt problems. We worked those out and I still run CWM touch on Tbolt. Used Amon on Rezound. Recoveries are what you feel comfortable with. I use whatever works best for the device although that is irrelevant to this subject. I still use the old school clean wipe of data/cache/dalvic cache/system for all flashes on all devices and all recoveries. Ultimately have never had a reason to use Odin or go back to stock since initial root. Only bugs I have seen are rom related and nandroid back to working rom fixed it. There are differing opinions on what I have just posted but I have had no problems with flashing anything on my last 3 devices and have never bricked a phone even though I may flash 10 times a day for multiple devs on multiple devices. Maybe the old school recovery devs were on to something. Beats me.

Kool..I'm catching on., slowly..
Now If I do an Odin with pda can I use a rooted oem Rom to accomplish this newest leak that is said to have killer batt life?

takota6 said:
Kool..I'm catching on., slowly..
Now If I do an Odin with pda can I use a rooted oem Rom to accomplish this newest leak that is said to have killer batt life?
Click to expand...
Click to collapse
Yes you can but they all have killer batter life. No need to Odin you can flash it in recovery. Only have to Odin stock RUU to get firmware update. If you do it could loose root and ability to unlock boot loader. You will have it as long as you keep it. As soon as you flash another rom it will wipe that one and you will be on the base that the rom is based on. This is why the devs update to latest bases whether they be leaks or official. Best you can do is flash newer radios and kernels unless the ROM Gods tell us to update firmware and then it will be checked and deemed safe. Never Odin/flash an OTA/leak unless it has been cleared by the Android Gods. I have only used Odin once and that was because that was only way to root on original pre-order. :laugh:

be sure to back up internal sd card
takota6 said:
I'm a little lost, I've been reading for days and can't seem to find my answer..here goes
Coming from droid1 were I could flash new to old and vice versa..had the s3 for a couple of weeks, I'm on beans 13 kernel lean1.0 and hd radio..the other day I was on clean 2.5, and before that on synergy..can I keep bouncing around like that, our do I need to do Odin thingie? I see were root'ers are Odin then taking this new update and looks like killer battery life..I don't really have a preference on roms , just nead a little help on doing it proper..txs
Click to expand...
Click to collapse
Don't forget to back up internal sd card. Odin will wipe it when you flash.

[Q] Phone Randomly Reboots Itself?!

So after doing a wipe to my phone (was becoming slow) my phone randomly restarts itself for no reason as if it just crashes. I am running the latest version of the beanstalk rom. http://forum.xda-developers.com/showthread.php?t=2091900 I don't have the greatest understanding of flashing, roms, blah blah blah, but managed to get kit kat working for the last year or so, I don't understand why this is happening now, did I choose a bad rom or something? Everything else on the phone works but obviously constant restarts get to be very annoying.
Any help would be appreciated,
thank you!

Infused4life said:
So after doing a wipe to my phone (was becoming slow) my phone randomly restarts itself for no reason as if it just crashes. I am running the latest version of the beanstalk rom. http://forum.xda-developers.com/showthread.php?t=2091900 I don't have the greatest understanding of flashing, roms, blah blah blah, but managed to get kit kat working for the last year or so, I don't understand why this is happening now, did I choose a bad rom or something? Everything else on the phone works but obviously constant restarts get to be very annoying.
Any help would be appreciated,
thank you!
Click to expand...
Click to collapse
Try leaving it turned on in recovery mode (CWM). If it still reboots, then you have a hardware issue. If it stays stable, I would blame the ROM and try a different version or a different distro.
Sent from my MyTouch 4G Slide

joel.maxuel said:
Try leaving it turned on in recovery mode (CWM). If it still reboots, then you have a hardware issue. If it stays stable, I would blame the ROM and try a different version or a different distro.
Sent from my MyTouch 4G Slide
Click to expand...
Click to collapse
Thanks for the reply,
I don't think it is a hardware issue as it never did this when I had Jelly Bean or even the last time I had Kit Kat, never know though! Also, I will try to leave it in recovery and see if it does it but a few questions:
-What is "distro" (does it has to do with the OS of the phone?)
-Is there some ROM you could recommend to me for this phone that is stable.. When I install the beanstalk ROM there are like 10 to choose from, I'm guessing they are all older/newer versions!?
-Finally something I was wondering for the longest time but wasn't sure of is can I go back to say, Jelly Bean? Or is it "irreversible"?
Thanks again, glad there's people out there who can help the noobs like me!

Infused4life said:
Thanks for the reply,
I don't think it is a hardware issue as it never did this when I had Jelly Bean or even the last time I had Kit Kat, never know though! Also, I will try to leave it in recovery and see if it does it but a few questions:
-What is "distro" (does it has to do with the OS of the phone?)
-Is there some ROM you could recommend to me for this phone that is stable.. When I install the beanstalk ROM there are like 10 to choose from, I'm guessing they are all older/newer versions!?
-Finally something I was wondering for the longest time but wasn't sure of is can I go back to say, Jelly Bean? Or is it "irreversible"?
Thanks again, glad there's people out there who can help the noobs like me!
Click to expand...
Click to collapse
Methinks it is the specific ROM. I call the different types of OM out there distributions (or "distros" - in light of what is commonly used in the Linux world), but there may be a better term. It could be the version of Beanstalk you are using, it could be any version of BeanStalk with your phone. Hard to say.
In light of above, I would try CarbonROM. I tried it out briefly, and haven;t had a problem with it (and have heard no issues form the guy I sold the phone to with it installed).
But if you want to go back to JellyBean, there is still a version of 4.2 kicking around (CM 10.1) in the development threads. You can downgrade, at worst you may have to ODIN back to stock. But try to flash in CWM first. I was quite satisfied with that version. My biggest gripe is that the mobile data quick setting didn't work fully (but the long way around did). There is CM 10.2 as well, but I could never get that one installed on my phone (installer would break). Between the two, I would try 10.1 (and if you cannot find a copy, I can dropbox it to you).

5529
joel.maxuel said:
Methinks it is the specific ROM. I call the different types of OM out there distributions (or "distros" - in light of what is commonly used in the Linux world), but there may be a better term. It could be the version of Beanstalk you are using, it could be any version of BeanStalk with your phone. Hard to say.
In light of above, I would try CarbonROM. I tried it out briefly, and haven;t had a problem with it (and have heard no issues form the guy I sold the phone to with it installed).
But if you want to go back to JellyBean, there is still a version of 4.2 kicking around (CM 10.1) in the development threads. You can downgrade, at worst you may have to ODIN back to stock. But try to flash in CWM first. I was quite satisfied with that version. My biggest gripe is that the mobile data quick setting didn't work fully (but the long way around did). There is CM 10.2 as well, but I could never get that one installed on my phone (installer would break). Between the two, I would try 10.1 (and if you cannot find a copy, I can dropbox it to you).
Click to expand...
Click to collapse
YES!
So, after I left the phone in CWM for 25 minutes or so and it being fine I decided to get Carbon as I seen in your "signature" that you had that ROM on your Infuse, it has been good for 2 hours+, looking good! I guess it was the Beanstalk ROM after all.
Thanks for the downgrading information as well, wasn't sure if you could downgrade or what would happen!
Finally, what is flashing? (I could google it but since your here, could you give me a noob friendly definition!?)
Thanks for all your help

Infused4life said:
YES!
So, after I left the phone in CWM for 25 minutes or so and it being fine I decided to get Carbon as I seen in your "signature" that you had that ROM on your Infuse, it has been good for 2 hours+, looking good! I guess it was the Beanstalk ROM after all.
Thanks for the downgrading information as well, wasn't sure if you could downgrade or what would happen!
Finally, what is flashing? (I could google it but since your here, could you give me a noob friendly definition!?)
Thanks for all your help
Click to expand...
Click to collapse
Went to reply about the camera issue and notice it was no longer in the post. Glad you got it sorted.
So flashing, as I understand it, is just another term for installing something via recovery. Not sure of the origin, maybe have something to do with installing to flash memory.

joel.maxuel said:
Went to reply about the camera issue and notice it was no longer in the post. Glad you got it sorted.
So flashing, as I understand it, is just another term for installing something via recovery. Not sure of the origin, maybe have something to do with installing to flash memory.
Click to expand...
Click to collapse
Ah ok, so it's essentially as I thought it was. I thought I was doing something wrong in terms of "flashing" but guess not! Sounds like it should just be called "Installing custom ROM".. !
Yeah, in terms of the camera thing, I'm an idiot and had USB storage turned on *facepalm*, So it wouldn't let me open the camera app!

Infused4life said:
Ah ok, so it's essentially as I thought it was. I thought I was doing something wrong in terms of "flashing" but guess not! Sounds like it should just be called "Installing custom ROM".. !
Yeah, in terms of the camera thing, I'm an idiot and had USB storage turned on *facepalm*, So it wouldn't let me open the camera app!
Click to expand...
Click to collapse
I am not sure if you are still facing the same issue but if you are facing reboots, then considering doing a fresh install after cleaning your internal storage as well since the remnants of the apps from previous installs have caused me problems. Ever since I started doing a fresh install (Factory reset, wiping the cache, wiping the dalvik cache and even the cache partition along with the wiping of the internal storage), there have been no reboot issues.

[Q] VZW M8 - Sunshine S-Off - CM12 / GPE / Custom ROMs

I need some assistance please! I am truly baffled by what I am experiencing and would like to know why and hopefully how to fix it. Here's the details:
CARRIER: Verizon
MODEL: HTC One M8
S-OFF: Yes (Sunshine)
ROOT: Yes
HBOOT: 3.19
RADIO: 1.09.20.0926
OpenDSP: 46.2.2
OS: 3.28.605.4
First off, sorry for the book, but I figured more details would be better at this point to figure out what is up, so I appreciate any assistance in advance! PS: I bolded the key items to the story for those that like to skim.
Prior to S-Off and Root, I was on OTA version 4.4.4 waiting in anticipation for 5.0 to come to my device. Was unsure about spending $25 for Sunshine's method, but finally decided to take the plunge. At first things seemed great and very smooth. Following all instructions from Sunshine I was finally with S-Off status. I then used WeakSauce2 to gain temp root of the Stock ROM so that I could install Flashify and TWRP. Rebooted and loaded up TWRP Recovery and completed the first Nandroid. SUCCESS! Next up was Titanium Backup and such and copied everything off to my computer for safe keeping. So far so good and then loaded up a few ROM files and whatnot to the External SD Card so I could start flashing a new ROM. Feeling good up to this point, but here's where the troubles begin...
I have had great success with CyanogenMod in the past on previous devices and always very pleased. I read CM12 for others was great and stable and performed well, so I decided to grab the latest CM12 Nightly and the GApps package. Did the normal Wipe / System Wipe for initial flash of a new ROM and then installed both ZIPs no problem. The ROM boots up and everything seems okay, only I do not have LTE at all, only 3G. I also tried the GPE rom by Digitalhigh and experienced the same thing! Restoring from Nandroid also did not fix LTE, so at this point I got worried I broke my phone somehow.
To make a long story short after lots of testing I found a fix for getting LTE back on my original ROM. I found the 4.4.4 RUU and placed the 1.7 GB zip file (0P6BIMG.zip) on the root of my external SD Card, booted into HBOOT and ran the update. It did it's thing and booted up into the Stock ROM. Still no LTE! So then I found a comment somewhere about once that is done, do a Factory Reset from HBOOT using the Stock Recovery and it is supposed to reset the NV Radio Partition, so I did this and when it booted back up, SUCCESS! I have LTE back.
Once that was done I can now flash GPE, (but unusable because SMS is not working for some reason... I am using Google Voice BTW), so I am back to my original 4.4.4 TWRP Recovered ROM. I tried just for kicks to see if after the "fix" if I could make CM12 work, but again will bring it down to an unworking LTE status. Rinse and repeat the "fix" and got LTE back and did Nandroid Recovery. I paid the money to get S-Off and Root access so I could enjoy the Custom ROM's, but now I feel I am stuck...
All that being said... Can someone please explain to me what is going on?? And is there any way I can fix this so I can use CM12 and have LTE, and even then some other ROMs? I will post in Digitalhigh's forum for resolution to the SMS issue, but I have never had this much trouble with a device before and do not know enough about the different partitions and how they work and such. Any assistance and advice is MUCH appreciated!
Thank you!

Nobody has any advise or explanation?

I don't know the version numbers you posted from you bootloader off the top of my head but did you update your firmware to one of the unofficial ones around before flashing one of the lollipop roms? Is so, are you sure it took completely as sometimes you have to flash it twice.
Alternatively you could wait for our official firmware to drop any minute now and have pretty good odds of working for you.

cntryby429 said:
I don't know the version numbers you posted from you bootloader off the top of my head but did you update your firmware to one of the unofficial ones around before flashing one of the lollipop roms? Is so, are you sure it took completely as sometimes you have to flash it twice.
Alternatively you could wait for our official firmware to drop any minute now and have pretty good odds of working for you.
Click to expand...
Click to collapse
Yes I did use official firmware, and flashed twice per recommendations. I have it working with GPE, but every time I flash CM12 it breaks LTE. I have seen articles and posts of others running CM12 on their M8's with VZW and stating "zero issues"... Lack of LTE sounds like an issue to me. So my big question at hand is, why does CM12 break LTE, and is there a fix? Everything else seemed to work great otherwise.

kjparenteau said:
So my big question at hand is, why does CM12 break LTE, and is there a fix? Everything else seemed to work great otherwise.
Click to expand...
Click to collapse
I was reading the CM12 m8 thread earlier this week and many reported that LTE did not work on builds from late Feb. early March. CM12 is in no way stable and results will vary from phone to phone. Even the speaker issues have not been fully resolved. Bummer, because I'd really like it to be more stable.
http://forum.xda-developers.com/htc...genmod-12-0-nightlies-htc-one-t2998070/page75

Thank you for your reply. Definitely wanting CM since I used to run that regularly on my older devices with no troubles at all. The speed and simplicity are what I am going for. Sense is okay, but the difference of less than 300 megs with CM compared to over a gig for stock is unreal. WAY less overhead.