Related
Guys -
I installed the Splashtop 2 on my Nexus 7 running AOKP and Trinity Krenel, and it bricked my device twice. Just running the software and suddenly it crashes, then no buttons work. Then the screen starts to flash and it shuts down. I was unable to get into recovery. I need to push a new recovery to get it running back again. This has happen twice today. Anyone else having this issue?
Its bricked?
So you put it in the trash or sent it back to ASUS?
I'm going to go out on a limb here and say this is not related to splashtop.
I had an issue using Splashtop 2 today that freaked me out a little. Going from Sharp to Smooth froze my N7 and when it booted back up, which took longer than usual, the speaker made a faint but distinct "hissing" noise then a louder "tap"
Everything is working again but that's never happened before. Not sure I liked Splashtop 2 enough to bother with it after that.
Hemidroids said:
Its bricked?
So you put it in the trash or sent it back to ASUS?
Click to expand...
Click to collapse
No.. I know how to get out of a jam. The device would not boot afterward the system froze, then rebooting I got stuck at Google screen. Then it wouldn't get into recovery from bootloader I had to flash a new recovery and flash back up. Sounds like it was bricked at the time to me.
Sent from my Nexus 7 using xda premium
tdrussell said:
I'm going to go out on a limb here and say this is not related to splashtop.
Click to expand...
Click to collapse
I would see why you would say this....however this happened twice when using the new splashtop. My set up or system has not changed in days. Only thing that changed was me installing splashtop. Once I stopped using it and went back to the old one. No issues. Someone else n the market review described the same thing to a t.
Sent from my Nexus 7 using xda premium
Installed HD2 this morning and same problem, freeze when changing from sharp to smooth. Hard reset twice, to get it to boot now the speaker sounds like its blown, was streaming some video from the PC. Running EOS + stock kernel.
Something isn't right with it that's for sure, avoid for now is my advice.
Sent from my Nexus S using xda premium
Knether said:
No.. I know how to get out of a jam. The device would not boot afterward the system froze, then rebooting I got stuck at Google screen. Then it wouldn't get into recovery from bootloader I had to flash a new recovery and flash back up. Sounds like it was bricked at the time to me.
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
Oh......so its not a brick. Might want to change the title.
Splashtop also froze my Nexus 7, fortunately hasn't knackered the speaker or anything. I was going to blame my undervolt though...
sensory said:
I had an issue using Splashtop 2 today that freaked me out a little. Going from Sharp to Smooth froze my N7 and when it booted back up, which took longer than usual, the speaker made a faint but distinct "hissing" noise then a louder "tap"
Everything is working again but that's never happened before. Not sure I liked Splashtop 2 enough to bother with it after that.
Click to expand...
Click to collapse
I had this same thing happen to me. Everything froze up then my Nexus rebooted itself. Other than that the app runs pretty damn good for me. No rooting or roms on mine.
PA 1.97a, Trinity Kernel @ 1640 (ondemand/deadline), Nova Launcher, Dark Jelly Theme.
Daily use out of Splashtop with absolutely no issue. It's one of the things I like best about this tablet.
my only negative view towards the nexus 7 is the influx of noobs that dont know what brick means. i have a g1 with a bad spl flash. that is a brick. you sir just need to flash a factory img. your not bricked.
xxmonsterx said:
my only negative view towards the nexus 7 is the influx of noobs that dont know what brick means. i have a g1 with a bad spl flash. that is a brick. you sir just need to flash a factory img. your not bricked.
Click to expand...
Click to collapse
The only reason he can't access recovery is because of a bug in boot loader 3.34 so its even less of a brick and more of a don't OV and OC
Sent from my Nexus 7 using xda app-developers app
xxmonsterx said:
my only negative view towards the nexus 7 is the influx of noobs that dont know what brick means. i have a g1 with a bad spl flash. that is a brick. you sir just need to flash a factory img. your not bricked.
Click to expand...
Click to collapse
Influx of noobs? I've been around XDA a bit longer than you. I am deeply sorry forum wordsmith for using the word brick not in the fashion you so desired.
Moving on:
I just wanted to get this word out there and just making sure its not my device. I spoke with Splash top and "they're on it." So we'll see :highfive:
Sorry good sir. I do suppose that was a bit rude. I may have taken out my dissapointment with what xda is becoming on you. My bad bud. I'm not here to compare the d!cks bro. I just can't stand seeing all these help I'm bricked threads.
xxmonsterx said:
Sorry good sir. I do suppose that was a bit rude. I may have taken out my dissapointment with what xda is becoming on you. My bad bud. I'm not here to compare the d!cks bro. I just can't stand seeing all these help I'm bricked threads.
Click to expand...
Click to collapse
No harm no foul. I don't hold grudges. Conflict resolution at its best. Thanks for that, means a lot and restores my faith in people. :laugh:
Harry GT-S5830 said:
The only reason he can't access recovery is because of a bug in boot loader 3.34 so its even less of a brick and more of a don't OV and OC
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
What is this bug you speak of?
Also, OC and OV is causing issues? Sorry If i dont know about this just yet, is there a thread that speaks about this?
Knether said:
What is this bug you speak of?
Also, OC and OV is causing issues? Sorry If i dont know about this just yet, is there a thread that speaks about this?
Click to expand...
Click to collapse
Try acessing recovery through boot loader on a healthy N7 and not plugged in, you will find that you can't access recovery. There's quite a few "Q" threads saying that I OC to 1600 and overvolted by 50MHz across the board, and my nexus fried? Why is this??
Sent from a Nexus 7 using my fingers
I've got the same problem with Splashtop and Nexus 7. Original ROM, no root. After switching smooth<>shart Nexus just reboots. Also there seems to be nothing interesting in logcat.
qrees said:
I've got the same problem with Splashtop and Nexus 7. Original ROM, no root. After switching smooth<>shart Nexus just reboots. Also there seems to be nothing interesting in logcat.
Click to expand...
Click to collapse
I seems to be fixed after todays update, but it's still strage that single app could crash the whole device.
I figured I would start this thread so that we can move all the non-development talk out of the development section. I hope people will use it so that when something that pertains to development is talked about it will be easier to find. We can discuss what kernels gives best battery life, which ones work and which one break things. We can post about our favorite apps, widgets, wallpapers, or how the weather is outside. Maybe someone will get help on an issue they are having. We can discuss anything within the guidelines of XDA, lets just try to help keep Jovy's thread clean.
I'll start, has anyone had an issue when coming out of sleep the screen is dim and you have to go into brightness and tap it to make it work? I think maybe I set my clock frequency to low or maybe I should be using a different governor. Another issue that bugs me is when I have ripple effect set and use a black background for my lockscreen the borders of the screen look slightly grey. I have read posts about this and by turning off ripple effect the color is like it should be. I like the ripple effect and I like black backgrounds, does anyone know about a fix for this, or does anyone notice this issue on their phone.
Here's the link to the Darthstalker ROM if you read this post and want to check out the actual ROM: http://forum.xda-developers.com/showthread.php?t=2014442
I am not the developer of this ROM, all credit for this great ROM goes to jovy23 and those he's listed in his OP.
~ Todd
Sent from my AT100 using xda premium
Good idea for a thread about the greatest rom! Here is a quick mod for all those interested, here is the stock boot animation and sound that work great!
http://forum.xda-developers.com/showthread.php?t=1706856
Sent from my SGH-T999 using Tapatalk 2
Thank you for this :victory:
tp2215 said:
Good idea for a thread about the greatest rom! Here is a quick mod for all those interested, here is the stock boot animation and sound that work great!
http://forum.xda-developers.com/showthread.php?t=1706856
Sent from my SGH-T999 using Tapatalk 2
Click to expand...
Click to collapse
This is a good example of what this thread is for. Thanks for posting.
Sent from my AT100 using xda premium
So to move my question to this thread. If I nand will it flash back my original kernel. Trying to remove kt747 and go back to stock kernel that came with this Rom.
Sent from my SGH-T999 using xda app-developers app
JohnnyNyQuil said:
So to move my question to this thread. If I nand will it flash back my original kernel. Trying to remove kt747 and go back to stock kernel that came with this Rom.
Sent from my SGH-T999 using xda app-developers app
Click to expand...
Click to collapse
Your nand restore should bring you back to whichever kernel was active during the backup
Sent from my SGH-T999 using xda premium
Awesome! Wasn't sure.
Sent from my SGH-T999 using xda app-developers app
edit28 said:
Your nand restore should bring you back to whichever kernel was active during the backup
Sent from my SGH-T999 using xda premium
Click to expand...
Click to collapse
I flash quite a few kernels, always making a backup prior so I can always restore. When restoring I always wipe like I'm installing a new ROM. Just to make sure nothing gets left behind.
Sent from my AT100 using xda premium
tmjohnsonfse said:
I flash quite a few kernels, always making a backup prior so I can always restore. When restoring I always wipe like I'm installing a new ROM. Just to make sure nothing gets left behind.
Sent from my AT100 using xda premium
Click to expand...
Click to collapse
Same here! I find 99.9% of ROM-related issues for us flashaholics stem from not performing a full wipe prior to a flash. I've been fully stable on every DaRTHSTALKER update, with LOTS of varying kernel testing, by using this method. Full data + cache + Dalvik wipe then flash than another cache/dalvik wipe before the boot is always a good strategy!
Sent from my SGH-T999 using xda premium
I always make backups for any change I flash too but the last phone I rommed was my g1. The vibrant was too much of a pain and there wasn't any good roms with Wi-Fi calling. I know these things are a different beast so I just wanted to make sure. Btw doesn't nand do all of the wiping process for you?
Sent from my SGH-T999 using xda app-developers app
JohnnyNyQuil said:
I always make backups for any change I flash too but the last phone I rommed was my g1. The vibrant was too much of a pain and there wasn't any good roms with Wi-Fi calling. I know these things are a different beast so I just wanted to make sure. Btw doesn't nand do all of the wiping process for you?
Sent from my SGH-T999 using xda app-developers app
Click to expand...
Click to collapse
I believe it does, but it only takes a few seconds to be absolutely sure it's done correctly. I'm a creature of habit.
Sent from my AT100 using xda premium
Much better. I guess I didn't even try the Rom tweaks on this one in the first place. Gonna see tomorrow how much better it will be. On another note, has anyone successfully connected to allshare play with another gs3? My girlfriend got hers (completely stock 4.1.1 w/no root) and everything else interacts except for that. Would like to group cast with her and I've followed the videos online to do it but our phones don't show up in each other's network, connected to WiFi of course.
Sent from my SGH-T999 using xda app-developers app
tmjohnsonfse said:
I figured I would start this thread...
Click to expand...
Click to collapse
Thank you for this thread, this is an excellent idea!
I've been a fan of this ROM since the very day the version 9 was uploaded. I got my SGS3 late December (this is my first android device), tried a few ROMs and stopped on this one. (BTW: a suggestion to put a link to the DARTHSTALKER S3 ROM thread http://forum.xda-developers.com/showthread.php?t=2014442 on OP so everyone new to this knows what it is all about).
This being my first post on the entire forum I was not allowed to ask questions on the original ROM's threads (and there are at least two I am following).
Now, if you don't mind a newbie question, here it is:
I am a T-mo subscriber using an unlocked AT&T phone. Currently I am on DARTHSTALKER v9 port for AT&T (here's the thread: http://forum.xda-developers.com/showthread.php?t=2087164 ). As the most of you I am eagerly awaiting version X1 of the DaRTHSTALKER, but my question is: can I just flash the T-mobile version or should I wait for when an AT&T PORT is available?
Thnks.
Pr0phess0r said:
Thank you for this thread, this is an excellent idea!
I've been a fan of this ROM since the very day the version 9 was uploaded. I got my SGS3 late December (this is my first android device), tried a few ROMs and stopped on this one. (BTW: a suggestion to put a link to the DARTHSTALKER S3 ROM thread http://forum.xda-developers.com/showthread.php?t=2014442 on OP so everyone new to this knows what it is all about).
This being my first post on the entire forum I was not allowed to ask questions on the original ROM's threads (and there are at least two I am following).
Now, if you don't mind a newbie question, here it is:
I am a T-mo subscriber using an unlocked AT&T phone. Currently I am on DARTHSTALKER v9 port for AT&T (here's the thread: http://forum.xda-developers.com/showthread.php?t=2087164 ). As the most of you I am eagerly awaiting version X1 of the DaRTHSTALKER, but my question is: can I just flash the T-mobile version or should I wait for when an AT&T PORT is available?
Thnks.
Click to expand...
Click to collapse
I would pm Jovy as he would know best, but maybe someone may be able to answer the question for you. I am new to phones also and the S3 is my first smart phone. I too have tried most of the roms, but keep coming back to this one. I do know that most at&t kernels are compatible, I would want to be 100% sure of ROM compatibility before flashing, might end up in a bad way. Thanks for the suggestion about seeing if Jovy would put the link in his OP.
Sent from my AT100 using xda premium
I had something happen last night that I've never had happen before and maybe sometime can tell me what it was. I was restoring back after messing with a few mods that didn't work and when my phone booted up in the lower left corner it said "Safe Mode". I went back into recovery and wiped cache and dalvik cache, fixed permissions, and then rebooted and safe mode was gone. What is safe mode?
Thanks,
Todd
Edit: Should have used Google first. Safe mode is similar to computer safe mode. It only loads base os to allow for removal of files. Still don't understand why it happened, but atleast I know it wasn't something bad.
Sent from my AT100 using xda premium
Pr0phess0r said:
Thank you for this thread, this is an excellent idea!
I've been a fan of this ROM since the very day the version 9 was uploaded. I got my SGS3 late December (this is my first android device), tried a few ROMs and stopped on this one. (BTW: a suggestion to put a link to the DARTHSTALKER S3 ROM thread http://forum.xda-developers.com/showthread.php?t=2014442 on OP so everyone new to this knows what it is all about).
This being my first post on the entire forum I was not allowed to ask questions on the original ROM's threads (and there are at least two I am following).
Now, if you don't mind a newbie question, here it is:
I am a T-mo subscriber using an unlocked AT&T phone. Currently I am on DARTHSTALKER v9 port for AT&T (here's the thread: http://forum.xda-developers.com/showthread.php?t=2087164 ). As the most of you I am eagerly awaiting version X1 of the DaRTHSTALKER, but my question is: can I just flash the T-mobile version or should I wait for when an AT&T PORT is available?
Thnks.
Click to expand...
Click to collapse
tmjohnsonfse said:
I would pm Jovy as he would know best, but maybe someone may be able to answer the question for you. I am new to phones also and the S3 is my first smart phone. I too have tried most of the roms, but keep coming back to this one. I do know that most at&t kernels are compatible, I would want to be 100% sure of ROM compatibility before flashing, might end up in a bad way. Thanks for the suggestion about seeing if Jovy would put the link in his OP.
Sent from my AT100 using xda premium
Click to expand...
Click to collapse
I WOULD NOT DO THAT! Although I cannot answer the question directly, every carrier has modified there own Galaxy S3. They are all completely different. I know that if you flash a Universal galaxy S3 rom onto a T-Mobile device, it will completely hard brick it due to a change in the partition structure. If you have an At&t device, I would still stick to the Galaxy s3 at&t roms even though T-mobile is your carrier.
tp2215 said:
I WOULD NOT DO THAT! Although I cannot answer the question directly, every carrier has modified there own Galaxy S3. They are all completely different. I know that if you flash a Universal galaxy S3 rom onto a T-Mobile device, it will completely hard brick it due to a change in the partition structure. If you have an At&t device, I would still stick to the Galaxy s3 at&t roms even though T-mobile is your carrier.
Click to expand...
Click to collapse
+1. Unlocking your phone only allows it access to a different carriers sim card. It does not change the base of the phone itself. I have a Tmobile SG3 that's unlocked for my travels but any ROM I flash must be a tmo based ROM. In your case stick with the ATT ROMs so you don't end up with a brick, and enjoy this great rom
My s3 is stalking your s3....
Does anyone have a flashable (zip) stock kernel?
I have looked and looked with no luck, I mean I can always just re flash the rom, but wanted to explore other alternatives first.
Thanks for creating this thread btw.
Sent from my SGH-T999 using xda premium
Hey guys been using this ROM for awile. I recently flashed a 4.2 ROM and know my GPS won't lock on I had made a back up before flashing ROM and reverted back to backup after I decided to switch back to this rom. Any suggestions on how to fix?
Sent from my SGH-T999 using Tapatalk 2
I have noticed a while ago when I receive text notification or miss calls, when i slide on them it takes about 10 second to open. I have reflashed this ROM several times n others just to see what's up but the problem only occurs with version x...anyone else experience this? just my phone?
Sent from my SGH-T999 using xda premium
Had my N72013 for 2 weeks now, and it boot loop'd four times on me twice in one day.
This can't be only happening to me.
I ordered from Google (big mistake), their rep said they can send me a new model but I would have to pay for it (dock the amount) first then once I receive it, send in my current model then wait to get my $$$ back.
Is this an issue with 4.3 or the device. I really don't want to return it if this problem could be patched away with an update...
Forgot to mention, I'm unlocked and rooted. 32gigs. No dead pixels, minor light bleed that doesn't bother me at all.
What would you do?
Sent from my SPH-L710 using xda premium
If its boot looping that's not normal obviously you know that so I would exchange it. Keep swapping until you get a good one.
Sent from my Nexus 7 using Tapatalk 4
Rican Bx Bomba said:
Had my N72013 for 2 weeks now, and it boot loop'd four times on me twice in one day.
This can't be only happening to me.
I ordered from Google (big mistake), their rep said they can send me a new model but I would have to pay for it (dock the amount) first then once I receive it, send in my current model then wait to get my $$$ back.
Is this an issue with 4.3 or the device. I really don't want to return it if this problem could be patched away with an update...
Forgot to mention, I'm unlocked and rooted. 32gigs. No dead pixels, minor light bleed that doesn't bother me at all.
What would you do?
Sent from my SPH-L710 using xda premium
Click to expand...
Click to collapse
wha?? I would return immediately.
Yea I don't know why its boot looping either. Maybe your factory images are corrupt and thus you keep restoring a bad image. Perhaps you have a bad sector in your memory.
You could test it by flashing a non-stock rom, such as CM10.2 which also uses a CM kernel.
Use it for a few days and See if the problem goes away or stays.
Either way, reflash stock using the Google Nexus 7 images. If the problem stays, then take it back. If it fixes it, then keep it.
Sent from my Nexus 7 using xda premium
player911 said:
Yea I don't know why its boot looping either. Maybe your factory images are corrupt and thus you keep restoring a bad image. Perhaps you have a bad sector in your memory.
You could test it by flashing a non-stock rom, such as CM10.2 which also uses a CM kernel.
Use it for a few days and See if the problem goes away or stays.
Either way, reflash stock using the Google Nexus 7 images. If the problem stays, then take it back. If it fixes it, then keep it.
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
Will try that. Thanks!
Sent from my SPH-L710 using xda premium
player911 said:
Yea I don't know why its boot looping either. Maybe your factory images are corrupt and thus you keep restoring a bad image. Perhaps you have a bad sector in your memory.
You could test it by flashing a non-stock rom, such as CM10.2 which also uses a CM kernel.
Use it for a few days and See if the problem goes away or stays.
Either way, reflash stock using the Google Nexus 7 images. If the problem stays, then take it back. If it fixes it, then keep it.
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
Thought I'll give you an update.. Installed CM10.2 for a few days, as you said.. No issues what so ever. Decided to try my luck with CoolRom and it bootlooped the moment I rebooted.
Decided on doing a complete wipe of the device and flashing a factory rom ( http://forum.xda-developers.com/showthread.php?t=2381582 ).
Don't want to give up hope yet.
Rican Bx Bomba said:
Had my N72013 for 2 weeks now, and it boot loop'd four times on me twice in one day.
This can't be only happening to me.
I ordered from Google (big mistake), their rep said they can send me a new model but I would have to pay for it (dock the amount) first then once I receive it, send in my current model then wait to get my $$$ back.
Is this an issue with 4.3 or the device. I really don't want to return it if this problem could be patched away with an update...
Forgot to mention, I'm unlocked and rooted. 32gigs. No dead pixels, minor light bleed that doesn't bother me at all.
What would you do?
Sent from my SPH-L710 using xda premium
Click to expand...
Click to collapse
Not sure why you would need to root this device. Its straight android and runs great without root or custom ROM.
Sent from my SCH-I535 using xda app-developers app
smurphdogg said:
Not sure why you would need to root this device. Its straight android and runs great without root or custom ROM.
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
Rooted it for some apps that required root access.
smurphdogg said:
Not sure why you would need to root this device. Its straight android and runs great without root or custom ROM.
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
There are tons of apps that require root access and are mandatory for many people including me.
I wouldn't bother to unlock and root. The N7 is flawless and fast out of the box.
Sent from my Nexus 7 using xda app-developers app
Again, root access is required for most decent backup programs and cloud data syncing apps. The issue doesn't require a debate about whether you need root or not. Yes the N7 is wicked fast and if you only use it as a bathroom reader for Facebook and light use, then that's cool. I like OTG support for my thumb drives when I'm in the field working.
Glad CM is working for you. That at least shows it isn't a hardware problem. I'd reflash stock images and see where that leaves you. Worse case you use CM (oh my!) until we see a patch.
It sounds like it just has a corrupted stock image. Kernels typically cause the reboots but a bad app or system file can too.
If you flash stock back and you still have issues, try just flashing a modified stock kernel (stock rom/custom stock kernel). CM has its own kernel which might be why it was working better.
You also should do a complete wipe between stock and CM and AOSP and vice versa. It typically bootloops if you dirty flash one type of rom over another. Stock and AOSP are pretty much the same thing but some custom ROMs like CM have different structures that hose you.
Sent from my Nexus 7 using XDA Premium 4 mobile app
player911 said:
It sounds like it just has a corrupted stock image. Kernels typically cause the reboots but a bad app or system file can too.
If you flash stock back and you still have issues, try just flashing a modified stock kernel (stock rom/custom stock kernel). CM has its own kernel which might be why it was working better.
Sent from my Nexus 7 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I flashed a stock image unroot, relocked. The process went without a hitch. Then I unlocked and rooted, flashed clean ROM, tried to see if I would get it to bootloop and it hasn't! Must've been a corrupt image.
I just want to thank you again, your advice saved me a lot of time and hassle with Google.
Sent from my SPH-L710 using xda premium
Rican Bx Bomba said:
I flashed a stock image unroot, relocked. The process went without a hitch. Then I unlocked and rooted, flashed clean ROM, tried to see if I would get it to bootloop and it hasn't! Must've been a corrupt image.
I just want to thank you again, your advice saved me a lot of time and hassle with Google.
Sent from my SPH-L710 using xda premium
Click to expand...
Click to collapse
I do not understand the hassle with Google.
I told them yesterday to get a new device, as wireless charging does not work. I talked max 10 minutes on the phone and I received an email 2 minutes after saying that I'll get a new device.
Yes, they will charge you "temporarily" for this, but you do not have to pay anything.
Anyway, it's me, I found it easy with Google.
Mine bootlooped today. Stock. No root or anything. I was forced to do a factory reset from recovery. Very troubling that this seems to be happening to a few people. There's a couple of threads over on android central of people having the same problem.
Sent from my Nexus 4 using XDA Premium 4 mobile app
I will admit this device is great without root but I prefer custom ROMs and titanium backup
Sent from my HTC One using XDA Premium 4 mobile app
Just sat here rebooting the n7 a few time and it happened. Held power and got it to re start the boot process and it loaded. As soon as I unlocked it I got an android process media force close
Sent from my Nexus 4 using XDA Premium 4 mobile app
Andro_pty said:
I do not understand the hassle with Google.
I told them yesterday to get a new device, as wireless charging does not work. I talked max 10 minutes on the phone and I received an email 2 minutes after saying that I'll get a new device.
Yes, they will charge you "temporarily" for this, but you do not have to pay anything.
Anyway, it's me, I found it easy with Google.
Click to expand...
Click to collapse
I rather not do the whole process of sending, receiving, ect. Call me lazy or whatever. Either way, it seems like my problem is solved, I'm once again happy.
Sent from my SPH-L710 using xda premium
Rican Bx Bomba said:
I flashed a stock image unroot, relocked. The process went without a hitch. Then I unlocked and rooted, flashed clean ROM, tried to see if I would get it to bootloop and it hasn't! Must've been a corrupt image.
I just want to thank you again, your advice saved me a lot of time and hassle with Google.
Sent from my SPH-L710 using xda premium
Click to expand...
Click to collapse
Super glad its worked. It worked for me. It worked for another guy. And worked for you. I think there is a bad rom image flashed on all of these that are causing lots of problems. The only fix is to clean slate and reflash the stock image, or move to custom ROMs.
Probably need to get someone to write a little app that just automates flashing the stock image again just for simplicity.
I'll probably create a new thread covering this.
Sent from my Galaxy Nexus using XDA Premium 4 mobile app
The stock images and the install script .bat file is simple enough.
Especially if you're rooted already. Since you already have the drivers installed on your computer.
Toolkits need to die a slow painful death.
You need root access a pen drive using an OTG cable, install app like titanium backup etc. Rooting doesn't mean custom rom or kernel
Sent from my Nexus 7 using xda app-developers app
So here is the fun story.
I was trying to get Firefox OS to work on my Sprint LG Optimus G and TWRP saud it failed. I have done this before with no issues really, but the second time made it angry. I know the device powers on because when I plug it up to my computer and hold the power button, the red LED light comes on. I can not get it to boot into anything. No Fastboot, TWRP, Download, or even CM11. All I can do is see a pretty red light. ? Can anyone help me?
Sent from my LG-LS980 using xda app-developers app
Try asking autoprime
http://forum.xda-developers.com/showthread.php?t=1984622
Sent from my LG-LS970 using xda app-developers app
did you try cwm instead
TWRP has been kind of picky when it comes to installing some roms like when i would try and install cm11 it would not work in TWRP but then after a quick flash to CWM it installs just fine i think its because cwm has the upper hand when it comes to installing possibly broken things where TWRP is for those people who don't want to accidentally ruin their devices because of lack of experience cwm has worked allot better for me and as far as your boot issue goes i would let it charge for a couple hours then hold the power button for 15 seconds so that way its powered off and then attempt to get into download mode. If you can do that then you can use LGNPST_ACG to do a secure boot loader unlock so that way you can flash cwm and go from there. I hope my experience and advice helps you out in your time of need. Good luck we are rooting for you
cpberndt said:
TWRP has been kind of picky when it comes to installing some roms like when i would try and install cm11 it would not work in TWRP but then after a quick flash to CWM it installs just fine i think its because cwm has the upper hand when it comes to installing possibly broken things where TWRP is for those people who don't want to accidentally ruin their devices because of lack of experience cwm has worked allot better for me and as far as your boot issue goes i would let it charge for a couple hours then hold the power button for 15 seconds so that way its powered off and then attempt to get into download mode. If you can do that then you can use LGNPST_ACG to do a secure boot loader unlock so that way you can flash cwm and go from there. I hope my experience and advice helps you out in your time of need. Good luck we are rooting for you
Click to expand...
Click to collapse
You have to use the freegee version of twrp to flash cm11.
Sent from my LG-LS970 using xda app-developers app
i have tried that before
mcog said:
You have to use the freegee version of twrp to flash cm11.
Sent from my LG-LS970 using xda app-developers app
Click to expand...
Click to collapse
I have tried using the FreeGee verison of TWRP and it doesn't play nicely with some roms however with the roms that are incompatible with twrp i have installed successfully using cwm v.6.0.4.5 non touch enabled and it has proven to be much more compatible with some roms due to CWM and their relationship with the cyanogenmod team. twrp has a nicer ui however it does tend to have some compatibility issues. I have been developing for about 3 years and i have mainly used cwm until i got a galaxy tab 2 7in wifi with ir blaster then i moved on to twrp and loved it but when i got my ls970 twrp proved to have some issues with a couple of roms. when i tried the same files on cwm they worked just fine. so give cwm a shot it might work let us know how it goes
achunt2143 said:
So here is the fun story.
I was trying to get Firefox OS to work on my Sprint LG Optimus G and TWRP saud it failed. I have done this before with no issues really, but the second time made it angry. I know the device powers on because when I plug it up to my computer and hold the power button, the red LED light comes on. I can not get it to boot into anything. No Fastboot, TWRP, Download, or even CM11. All I can do is see a pretty red light. ? Can anyone help me?
Sent from my LG-LS980 using xda app-developers app
Click to expand...
Click to collapse
I had the same problem but for a completely different reason a few days ago. I plugged it into the wall for a few minutes and finally got it past that red light and into TWRP. I can't say it will work for you because the causes are completely different(mine was a kernel overclock error - my battery went from 100% - 0% in around 10 minutes and overheated). I plugged it in and saw that red light but it wouldnt turn on - ofcourse panic sets in bc its my only phone and I thought I fried it by overclocking. But I took a deep breathe, left it plugged in and when I came back it booted up. When I got into TWRP my battery read 1%, so I did a full wipe and restored my backup, then my battery read 99%, lol. Again mine was a kernel issue so that may not work for you. Partimus is right, autoprime would surely know - but you may have to do the dreaded battery pull(there are videos on youtube) to reset the phone.
cpberndt said:
I have tried using the FreeGee verison of TWRP and it doesn't play nicely with some roms however with the roms that are incompatible with twrp i have installed successfully using cwm v.6.0.4.5 non touch enabled and it has proven to be much more compatible with some roms due to CWM and their relationship with the cyanogenmod team. twrp has a nicer ui however it does tend to have some compatibility issues. I have been developing for about 3 years and i have mainly used cwm until i got a galaxy tab 2 7in wifi with ir blaster then i moved on to twrp and loved it but when i got my ls970 twrp proved to have some issues with a couple of roms. when i tried the same files on cwm they worked just fine. so give cwm a shot it might work let us know how it goes
Click to expand...
Click to collapse
The only problems I've had with TWRP were AOSP 4.4.x related. TWRP 2.5.0.0 has still been the most stable and trustworthy for the ls970 imo. However you need TWRP 2.6.3.x for anything 4.4. And you are right the FreeGee version of TWRP works with CM11 but has issues with other roms. twrp-geespr from chadouming works well on the other roms but not with CM11. However most of the "failed" issues happen with TWRP because of the asserts in the updater-script. If you open the zip and edit or flat out delete the assert it will almost always flash perfectly. I've even flashed unported nexus 4 roms to my device this way(obviously not much worked network wise besides wifi but it still installed and booted into android). CWM 6.0.4.5 seems to flash 4.4 roms fine but since my efs backups are TWRP, I will personally always have to flash back to TWRP if something goes wrong.
But the reason TWRP has compatibility issues is because of those asserts in the updater-script, which are absolutely safety measures. Our phone has been named a lot of things by the devs(ls970, geespr, geehrc4g, etc) so if TWRP checks for geespr but thinks your phone is an ls970, the flash will fail. Even if they are the same thing just named differently - TWRP doesnt know that and will stop the install to protect your device. Noob or not, that's a good thing and could possibly save you from bricking your device. The other issue(and why we can't flash 4.4 from TWRP 2.5.0.0) has to do with the SELinux changes that came with 4.4. Only one 4.4 rom would install for me via TWRP 2.5.0.0 and that was a port of houstonns AOSP4.4 because he disabled the SELinux changes.
So while I agree that CWM 6.0.4.5 seems to work great when installing 4.4.x roms, for as long as Ive had this phone, TWRP 2.5.0.0 has been all around the most stable. If I want to flash 4.4 I will install CWM or TWRP from recovery but always end up going back to TWRP 2.5.0.0 because I know it keeps my efs safe. But if you are keeping your 4.4 rom, you have no choice but to stick with updated TWRP or CWM and in this case I have heard of less issues with CWM than TWRP.
Yeah, I never had compatibility issues until 4.4
Sent from my LG-LS970 using xda app-developers app
mcog said:
Yeah, I never had compatibility issues until 4.4
Sent from my LG-LS970 using xda app-developers app
Click to expand...
Click to collapse
It's that damn SELinux! :silly:
I tried plugging it in for like an hour and when I came back, it had the charging light. It still wouldnt boot. I have ordered a torx 5 and torx 6 screwdrivers so I can do a battery pull.
Sent from my LG-LS980 using xda app-developers app
Did you get the plastic pry bar as well? The outer case can be a pain in the as$ and you don't want to break anything. Also take your time with the battery, when I did mine I felt like they put way to much adhesive on it.
Sent from my LG-LS970 using xda app-developers app
Yes. I did. I also have a spare guitar pick if it doesnt work.
Sent from my LG-LS980 using xda app-developers app
I finally got the screwdrivers, which took forever to ship, and doing a battery disconnect does not help the phone reboot. What do I do now? Any help suggestions?
Sent from my LG-LS980 using xda app-developers app
achunt2143 said:
I finally got the screwdrivers, which took forever to ship, and doing a battery disconnect does not help the phone reboot. What do I do now? Any help suggestions?
Sent from my LG-LS980 using xda app-developers app
Click to expand...
Click to collapse
Ouch, battery pull didn't help? How long did you leave the battery out before putting it back in? And is still doing the exact same thing, no lg logo, nothing but red blinking light when trying to power on?
And how did you get this phone? Did you get it from Sprint or from a place like BestBuy, etc?
Well, it's still doing the red light thing and when I plug it into my computer, it shows that it shows up and wants me to install drivers for QHSHUB_DLOAD. LGNPST doesn't recognize the device. I got the phone from Sprint, but I have upgraded since and have flashed the phone a few times, so the warranty may be void. I left the battery unplugged for a few minutes.
Sent from my LG-LS980 using xda app-developers app
achunt2143 said:
Well, it's still doing the red light thing and when I plug it into my computer, it shows that it shows up and wants me to install drivers for QHSHUB_DLOAD. LGNPST doesn't recognize the device. I got the phone from Sprint, but I have upgraded since and have flashed the phone a few times, so the warranty may be void. I left the battery unplugged for a few minutes.
Sent from my LG-LS980 using xda app-developers app
Click to expand...
Click to collapse
The upgrade is your biggest worry for voiding the warranty. Rooting does not void a sprint warranty - they wont advertise it but it's true - so I would try to take it back to them. If you upgraded and it's no longer on their network, meaning your phone number was switched to your upgrade, they probably won't help. If you were still able to use it as a phone before it went down, meaning it's still a line on your plan, they might. QHSUB_DLOAD means it's hard bricked, I don't think there is anything you can do if you see that. QHSUB_DLOAD is pretty universal when it comes to being hard bricked across devices.
There is a fix for phones with removable storage but since we don't have an actual sd card slot, it's bricked, and sadly unless Sprint gives you a new one, you're screwed.
Oh, so if I activate it, will they help me?
Sent from my LG-LS980 using xda app-developers app
achunt2143 said:
Oh, so if I activate it, will they help me?
Sent from my LG-LS980 using xda app-developers app
Click to expand...
Click to collapse
That means it's no longer activated, so probably not. It's bricked so they can't activate that particular phone, and if it's no longer a line on your network I think it's warranty is up. However, I don't work for Sprint so I would still take it to them and see if they can do anything but I wouldn't get my hopes up. If it was still a line and had a phone number attached, you would still be under warranty and they would replace it with a new lgog.
HP's right. That Dload is a brick. The only fix I know if is "jtag". It a service that's getting more popular but at a price. I think, and I hope it's OK if I say this, but autoprime performs this service on our phones I think.
Sent from my LG-LS970 using XDA Premium 4 mobile app
engine95 said:
HP's right. That Dload is a brick. The only fix I know if is "jtag". It a service that's getting more popular but at a price. I think, and I hope it's OK if I say this, but autoprime performs this service on our phones I think.
Sent from my LG-LS970 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Learn somethin new everyday! And actually I did know about jtag, but I forgot about it, lol. It's where they send signals directly to 6 circular pins on the board. It's obviously more in depth than that, but yeah, good catch as always @engine95.
It can be expensive because the hardware boxes that deliver the code are very expensive. If Sprint doesn't do anything(and they probably won't), I'd ask autoprime - nicely.
EDIT: Thanks for reminding me @engine95. I'm yet again out of thanks for the day. You're the man!
Well, the phone is only a few months old. I took an upgrade on another phone because said person didn't want to upgrade. I will take it to Sprint sometime this week. It just snowed bland this is an area where it hardly snows, so everything is closed due to panic. I may take it Thursday and see if they can do anything.
Sent from my LG-LS980 using xda app-developers app
So I went with the d801 g2!! It's awesome. I just wanted to say bye to all the t989 FAM, everyone was pretty cool and helpful. See you on the other side!
Sent from my LG-D801
demoncamber said:
So I went with the d801 g2!! It's awesome. I just wanted to say bye to all the t989 FAM, everyone was pretty cool and helpful. See you on the other side!
Sent from my LG-D801
Click to expand...
Click to collapse
I see you had the t999L as well! How did you like that phone?
pubed said:
I see you had the t999L as well! How did you like that phone?
Click to expand...
Click to collapse
It seemed like a pretty solid phone, I only played around with it for a half hour to make sure it worked.
Sent from my LG-D801
Should went nexus but I guess her red headed step sister ain't so bad
Sent from my Nexus 5 using XDA Premium 4 mobile app
BATZ DA LOCC said:
Should went nexus but I guess her red headed step sister ain't so bad
Sent from my Nexus 5 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Lol.. I mean if you really want to call it that. I'd rather have the bigger display with the same exact specs as the n5. Knock on and WiFi calling (an option I cannot live without)
Sent from my LG-D801
demoncamber said:
So I went with the d801 g2!! It's awesome. I just wanted to say bye to all the t989 FAM, everyone was pretty cool and helpful. See you on the other side!
Sent from my LG-D801
Click to expand...
Click to collapse
Yeah G2 is awesome! Can't wait to see what the G3 is gonna bring to the table.
Sent from my LG-D801 using xda app-developers app
Don't need WiFi calling n the screen is plenty big for me n got dt2w but don't use it battery drainer could flash a ROM called mystery ROM that has it on multirom
Sent from my Nexus 5 using XDA Premium 4 mobile app
Both are great phones. LG has converted me from a Samsung galaxy fan.
Sent from my LG-D801
demoncamber said:
Both are great phones. LG has converted me from a Samsung galaxy fan.
Sent from my LG-D801
Click to expand...
Click to collapse
Same here...:thumbup:
Sent from my LG-D801 using xda app-developers app
Yeah I gotta agree with u guys there I love the build quality
Sent from my Nexus 5 using XDA Premium 4 mobile app
Alternate method to enter recovery?
Does anyone know of a way to enter recovery other than with using the power button? Is there a way to do it through ODIN?
I installed ICS Stock ROM, but I need to be able to enter recovery to do a factory reset.
My power button is broken. I can get into download mode (pressing volume up, volume down, and then inserting usb cable).
If the phone is off, I can also get the phone to power on (by inserting power cord, feeling vibrate, and then quickly removing power cord).
But I can't get into recovery. If anyone has any creative methods, that'd be awesome!
I'm saying goodbye, as well.
After installing ROM after ROM, I never found any that "just worked". Anything 4.4-based had all kinds of busted stuff (1080p video, Netflix, etc). 4.3 had camera/gallery issues. Even with 4.1 and 4.2 (including 4.1 stock), they still seem to suffer from "vbus_present" issues forcing me to reboot any time I unplug the device.
The device froze up on me and corrupted too many photos. I tried asking the community what the "best" ROM was, and mods closed the thread.
I wanted the T989 as a tool. Not something I had to babysit.
Maybe I'll get a Moto G or whatever Motorola's new phone is.
BitingChaos said:
I'm saying goodbye, as well.
After installing ROM after ROM, I never found any that "just worked". Anything 4.4-based had all kinds of busted stuff (1080p video, Netflix, etc). 4.3 had camera/gallery issues. Even with 4.1 and 4.2 (including 4.1 stock), they still seem to suffer from "vbus_present" issues forcing me to reboot any time I unplug the device.
The device froze up on me and corrupted too many photos. I tried asking the community what the "best" ROM was, and mods closed the thread.
I wanted the T989 as a tool. Not something I had to babysit.
Maybe I'll get a Moto G or whatever Motorola's new phone is.
Click to expand...
Click to collapse
The way I see it....ROMs made of 4.2.2 and higher may have their odd glitches... But that just life bringing android versions to phones who's official support ended. Its either accept the odd problem, or stick with last official update. In this case touch wiz 4.1.2. Which is pretty much perfect.
Flashing custom ROMs comes with the odd glitch, no matter the phone. That's just how it is.
Stock is for those that can't accept the odd issue.
Good luck with your next phone!! The moto g is nice, for its price for sure!!!
---------- Post added at 09:02 PM ---------- Previous post was at 08:25 PM ----------
A point I should have made.....the devs work hard and for free and for fun....and share with us lucky members.
They do their best with what they have to work with....especially on android versions not even created for our device.
They deserve our respect and thanks. If what's available disappoints anyone....they should keep it to themselves or choose their words wisely.
Without the devs.... We'd have nothing at all. Especially when Google stops giving us official updates.
Be grateful.
Still loving my Herc. Carbon rom with SaberMod Uber kernel and I have no complaints...
Sent from my SAMSUNG-SGH-T989 using XDA Premium 4 mobile app
BitingChaos said:
I'm saying goodbye, as well.
After installing ROM after ROM, I never found any that "just worked". Anything 4.4-based had all kinds of busted stuff (1080p video, Netflix, etc). 4.3 had camera/gallery issues. Even with 4.1 and 4.2 (including 4.1 stock), they still seem to suffer from "vbus_present" issues forcing me to reboot any time I unplug the device.
The device froze up on me and corrupted too many photos. I tried asking the community what the "best" ROM was, and mods closed the thread.
I wanted the T989 as a tool. Not something I had to babysit.
Maybe I'll get a Moto G or whatever Motorola's new phone is.
Click to expand...
Click to collapse
Current T989 kitkat bugs piss me off, lol. They seem to be putting finishing touches on it, then all of a sudden they make a bigger change that opens a whole new can of worms.
My power button got stuck several months ago, so I actually opened the phone up and removed the entire thing. To turn my phone on, I plug it in with a usb chord and hold volume up/down until I enter download mode, then I cancel it.
I use an app called Quick Boot to reboot, enter recovery and so on.
Also, I kind of agree with you guys. Sure, the latest 4.4 ROMs are a little buggy, but I've found 4.3 roms to be perfect, in terms of stability.
Got my T989 last november from a friend, second android device I had but the first to get serious with. Also tried to check for newer devices like that LG G2 but the chance for me to get a new one is far less than you can do.
Sent from my SAMSUNG-SGH-T989
I lucked out. I complained enough to tmobile about the screen blobs and lines from the amoled displays that they kept sending me as refurbs, wrote the CEO an email, then they called and agreed to send me a GS3 LTE, and let me keep my s2, so I immediately sold both phones and got the g2 new.
Sent from my LG-D801
demoncamber said:
So I went with the d801 g2!! It's awesome. I just wanted to say bye to all the t989 FAM, everyone was pretty cool and helpful. See you on the other side!
Sent from my LG-D801
Click to expand...
Click to collapse
Dude that's awesome! So you can send me a copy of your EFS folder then?