[Q] Can't Boot Into Bootloader - AT&T, Rogers HTC One X, Telstra One XL

First, let me say I am a noob and not a developer, just more of a phone enthusiast. That said, my problem is that I cannot boot into the bootloader on my AT&T HOX. I have read through many threads on how this is done (Pwr+VolDown), but it simply doesn't work for me. After about 4 seconds, my nav button baklights flash a few times, then stop. From this point, I have tried two things...1) contine holdign pwr+voldown for well over a minute, nothign happens and 2) releasing the pwr+voldwn bottons and then pressing again and holding for what seems to be an eternity, but still nothing happens. Note that I'm having no issues with a normal boot.
The caviat: in order to sync my company's corporate email via exchange, I have to enable administrator rights by my company's IT policies (which totally blows, I know). This forces encryption on phone storage, even though I think it's really just the sector that houses files related to my exchange account. Regardless, I'm wondering if the administrative rights or encryption is what's preventing me from accessing my bootlader.
Thoughts? I know the thing I should so is just remove my exchange and disable the administrator rights, but to do so I am forced to factory reset the phone, which I'd like to prevent doing unless that's all there is left to do.
Any help is appreciated. If this is a dumb noob question and I missed a previous thread containing a solution, please link and I wont keep this thread going. thanks a lot.

Why are you trying to get into H-Boot? Are you trying to re-flash your phone with the stock ruu or something?
Anyways, to answer your question. No your admin stuff is in no way causing the phone not to get to h-boot, and it's there, I don't think I've ever heard of a phone that boots that can't h-boot.

HydroSkillet said:
Why are you trying to get into H-Boot? Are you trying to re-flash your phone with the stock ruu or something?
Anyways, to answer your question. No your admin stuff is in no way causing the phone not to get to h-boot, and it's there, I don't think I've ever heard of a phone that boots that can't h-boot.
Click to expand...
Click to collapse
To be honest, at this point I am only trying to access it out of curiosity. But ultimately I am checking it out because I have started to have a lot of connectivity problems with wi-fi and was looking into flashing the 1.82 update floating around. I was going to wait until the offical OTA update, but the wi-fi problem is getting worse, or at least it's effecting me more. Anyway, was just looking into accessing it. I initially noticed that I couldn't get in last week when reading a battery thread on calibration since my first couple days witht eh phone had very poor battery life. But it's improved since then and I never went back to check until the wi-fi issues proved annoying. Since I haven't rooted a device before, i figured I woudl familiarize myself with some of the basic steps before assuming I would just jump right in. Checking out how to h-boot seemed like a good place to start.

fitchpuckman said:
To be honest, at this point I am only trying to access it out of curiosity. But ultimately I am checking it out because I have started to have a lot of connectivity problems with wi-fi and was looking into flashing the 1.82 update floating around. I was going to wait until the offical OTA update, but the wi-fi problem is getting worse, or at least it's effecting me more. Anyway, was just looking into accessing it. I initially noticed that I couldn't get in last week when reading a battery thread on calibration since my first couple days witht eh phone had very poor battery life. But it's improved since then and I never went back to check until the wi-fi issues proved annoying. Since I haven't rooted a device before, i figured I woudl familiarize myself with some of the basic steps before assuming I would just jump right in. Checking out how to h-boot seemed like a good place to start.
Click to expand...
Click to collapse
disable fastboot in power options. turn the phone off. Hold down and power, you should see your h-boot
Also if you're looking to flash the unreleased it's just an exe that you run.... it's easy.

^This. Need to disable fast boot in your power options first.

HydroSkillet said:
disable fastboot in power options. turn the phone off. Hold down and power, you should see your h-boot
Also if you're looking to flash the unreleased it's just an exe that you run.... it's easy.
Click to expand...
Click to collapse
beaups said:
^This. Need to disable fast boot in your power options first.
Click to expand...
Click to collapse
Thanks guys, this is likely the case. I thought I disabled fast-boot mode the other day, but apparently I did not. I'll give it a shot in a little bit when I get back to my desk and let you know if I'm still stuck.
Also, re the unreleased RUU, yeah the thread made it sound pretty simple. there were various folks having issues after the update, so I'm just going to monitor for a few more days to see how my phone performs and if there comes official word of a carrier OTA update.
Thanks again.

Related

3 button Combo

This is a request, hopefully I will not get flamed for posting this.
I am not a programmer, I cant do what you guys do...just not my thing. There are MANY people that have problem with the 3 button combo stopping working. I experienced this myself on my second captivate. Is there anyone out there solid enough and willing to commit the time to solve this issue? It is obviously a software issue and I feel confident that if one of the senior solid members devoted time to it could solve it. I can say that if I have the ability to boot into download mode I will do just about anything to this phone because I will have the ability to always revert and start over. When I lost that ability, it crippled my phone in my mind cause problems occur, that is just how it goes eventually no matter if you follow directions perfectly or not.
Anyway, its easy for me to ask others to figure this out...its just beyond my current abilities and I think there are many on this board that would really love for a fix to be there. I also think its a worthy area to put time into considering the amount of people that have had issues with this. It doesnt always come down to people not knowing what to do, what combination works...for some of us it was a software issue that no options worked for. Anyway, that is my rant....I just have great faith that someone on here is solid enough to solve the issue...it just isnt me!!
FLAME WAR!!!
Seriously though, I feel your pain, I had two crappy cappies. Lucked out on the third.
Hope someone does figure it out.
Now let the FLAME WAR BEGIN!!!
I think froyo solved this issue because now my 3button combo works.
Some reported that JH7 fixed it too but it does not work for many and Im sure Froyo is the same deal. Anyway, just a thought as it would help many.
I would prefer adb to the button combos...
Just
1. connect ur phone in debugging mode
2. Press Win+R to open up a cammandline window
3. enter the folder with adb
for recovery mode, type in
adb reboot recovery
for download mode, type in
adb reboot download
This method does not require root, and extends the life of your buttons as well
adb usually comes with lagfix or sideloading patchs.
I agree that those methods are great but the problem is if you cant boot the device, the 3 button combos are your only choice.
gocats7 said:
This is a request, hopefully I will not get flamed for posting this.
I am not a programmer, I cant do what you guys do...just not my thing. There are MANY people that have problem with the 3 button combo stopping working. I experienced this myself on my second captivate. Is there anyone out there solid enough and willing to commit the time to solve this issue? It is obviously a software issue and I feel confident that if one of the senior solid members devoted time to it could solve it. I can say that if I have the ability to boot into download mode I will do just about anything to this phone because I will have the ability to always revert and start over. When I lost that ability, it crippled my phone in my mind cause problems occur, that is just how it goes eventually no matter if you follow directions perfectly or not.
Anyway, its easy for me to ask others to figure this out...its just beyond my current abilities and I think there are many on this board that would really love for a fix to be there. I also think its a worthy area to put time into considering the amount of people that have had issues with this. It doesnt always come down to people not knowing what to do, what combination works...for some of us it was a software issue that no options worked for. Anyway, that is my rant....I just have great faith that someone on here is solid enough to solve the issue...it just isnt me!!
Click to expand...
Click to collapse
The problem isn't necessarily "obviously software". The JH7 OTA "fixed" the problem, but really it didn't, because if you Odin'd back, you have the problem again. We looked and looked in that release to try to find what was in it that fixed the problem, we could not find it. Tell me why Odin will not take away or give 3 button recovery to phones that already have it, or don't have it, but it will if you get it from the OTA. Also, why does it take so long for Samsung to provide a fix, but the fix actually isn't a fix, it is just a cover up. I am leaning very heavily on this is a hardware issue. If you think about it, why is it that you can completely destroy your phone, but you can still get into download mode? This is because your second bootloader still works (I believe) but why is it impossible to break this? I think it is because this is a hardware issue, and we can never get a real, permanent fix.
DemonWav said:
The problem isn't necessarily "obviously software". The JH7 OTA "fixed" the problem, but really it didn't, because if you Odin'd back, you have the problem again. We looked and looked in that release to try to find what was in it that fixed the problem, we could not find it. Tell me why Odin will not take away or give 3 button recovery to phones that already have it, or don't have it, but it will if you get it from the OTA. Also, why does it take so long for Samsung to provide a fix, but the fix actually isn't a fix, it is just a cover up. I am leaning very heavily on this is a hardware issue. If you think about it, why is it that you can completely destroy your phone, but you can still get into download mode? This is because your second bootloader still works (I believe) but why is it impossible to break this? I think it is because this is a hardware issue, and we can never get a real, permanent fix.
Click to expand...
Click to collapse
word.
Also, for those of you who can get their phone to show the computer/phone screen, all you need to do is hold all the buttons and the screen will eventually restart, then you let go of the power button (but keep holding the others) this should get you in recovery mode... I read this somewhere on the forums and it has saved me many times!!! (my button combos only work this way)
We will just have to agree to disagree because I do not think it is a hardware issue and I do not agree with your logic. Mine worked perfect until I changed software. Others claim JH7 (software change) made theirs work again. I could go into more details about why I think the issue is software based but I wont convince you and you will not convince me. The request hasnt been met with much enthusiam so the thread should probably just close.
I was one of those who gained 3 button abilities with the update. we now know that JH7 and apparently Froyo will enable the 3 button combo. But if you ODIN back to 2.1, the 3 button combo no longer works.
My question is that once Froyo is officially released and we can ODIN back to stock on 2.2 (which we already can I think because of the leak), doesn't that mean we now have 3 button combo for good because technically, you won't need to ODIN back to 2.1 when Froyo is officially supported by samsung.
Or am i just confused? lol
gocats7 said:
We will just have to agree to disagree because I do not think it is a hardware issue and I do not agree with your logic. Mine worked perfect until I changed software. Others claim JH7 (software change) made theirs work again. I could go into more details about why I think the issue is software based but I wont convince you and you will not convince me. The request hasnt been met with much enthusiam so the thread should probably just close.
Click to expand...
Click to collapse
Probably because its old news. http://forum.xda-developers.com/showthread.php?t=784147 I've already made the same request, but we got nowhere on it. Like I said, we have tried to find the problem, or what is fixing it, but we just can't find it. It's amazing that it does at least temporarily fix the problem, because from what we found, it shouldn't.
n19htmare said:
I was one of those who gained 3 button abilities with the update. we now know that JH7 and apparently Froyo will enable the 3 button combo. But if you ODIN back to 2.1, the 3 button combo no longer works.
My question is that once Froyo is officially released and we can ODIN back to stock on 2.2 (which we already can I think because of the leak), doesn't that mean we now have 3 button combo for good because technically, you won't need to ODIN back to 2.1 when Froyo is officially supported by samsung.
Or am i just confused? lol
Click to expand...
Click to collapse
im in the same situation as you. froyo enabled the 3 button combo.
im thinking that since we dont have to odin back to 2.1 anymore, we will always have 3button combo. but can someone clarify this?
here is an easy way to get into recover/download mode without the 3 buttons:
First root your phone (most people on this site have done this)
then download Android Terminal Emulator from the market
once it is finished downloading, open and you should be at a blue screen, type "su" (without quotes obviously). It will ask for root access/super user permission. Click Yes. Now type "reboot download" to enter download mode, type reboot recovery for recovery, and reboot for plain old rebooting. It may say you don't have permission or something when you first try, just restart phone and try again.
Hope that helps. My button combos don't work either, so thats what I use flawlessly every time.
whenemusattack said:
here is an easy way to get into recover/download mode without the 3 buttons:
First root your phone (most people on this site have done this)
then download Android Terminal Emulator from the market
once it is finished downloading, open and you should be at a blue screen, type "su" (without quotes obviously). It will ask for root access/super user permission. Click Yes. Now type "reboot download" to enter download mode, type reboot recovery for recovery, and reboot for plain old rebooting. It may say you don't have permission or something when you first try, just restart phone and try again.
Hope that helps. My button combos don't work either, so thats what I use flawlessly every time.
Click to expand...
Click to collapse
this will definitely work but im thinking the main concern for people is when they brick their phone and cant get it to boot up. ADB and Android Terminal Emulator only works when the phone is booted up. With no 3 button combo support, idk what people can do when it wont boot up
It's possible to easily get into download/recover mode via the method posted above or adb shell. The problem is if your phone cannot boot. This almost happened to me today when I tried to remove the sl4a lagfix before DG switched to OCLF.
The button combos originally worked on my Captivate, but stopped working at some point after I one-clicked back to JF6 and then flashed Cognition 2.2, as at the very least Cognition 2.2 is not guaranteed to restore the button combos. I have not tried the stock Froyo leak, so I cannot comment on that. At some point this week or next weekend, I will one-click to JF6, update to JH7, then install Cognition 2.2 from there and see if that restores it.
BTW my phone's 3 combo now works after One-Click Froyo. So it seems to me the 3 button issue is software related.
whenemusattack said:
BTW my phone's 3 combo now works after One-Click Froyo. So it seems to me the 3 button issue is software related.
Click to expand...
Click to collapse
Which to me is weird because most recovery/debug modes are not or should not be affected by software. In which case it makes recovery totally pointless if your software is corrupt (point of recovery is to FIX the corrupt software).
it still doesn't make sense why SOME samsung phones will ALWAYS work with 3 button even on 2.1 and others wont at all.
In my case, I don't really care because I'm not an aggressive flasher and usually don't flash beta stuff etc.

G Tablet coming tomorrow...would like to get some things set straight. Thanks.

Hey all,
I'm getting my G Tablet tomorrow and I'd just like to get some things clarified.
I know, the first thing some will say is USE SEARCH! Well, I did - and that's actually why I just want to get some things straight before I go down the path of modifying the device software. See, reading it all has managed to confuse me more than help me get a definitive instruction set for forging ahead.
I'm seeing the update "****s on CWM" according to a user...and then a 'fix' for that. Than I see that Gapps causes FCs for some, while it works for others. So...yeah, a little back and forth on what to do and who's instructions to follow.
Alright, so first thing's first....Should I flash the Clockwork Mod that I'm seeing available - 0.8? or is there something else I should consider or that I've missed? or maybe wait for a newer version? Should I even flash CWM if I get the newest (and I WILL be getting the newest) S/W version? Are there any downsides at all to flashing CWM on there in terms of messing with OTA updates, etc?
I read this:
"All the ROMS use a standard firmware updater that can be used by non-technical users. Here is an explanation on how it works:...."
Sooo, does that mean I can live without CWM? If an update doesn't work for some reason, will I be able to fix it or overwrite it somehow if I can't get into the tablet at all from the tablet itself? I read something about going into APX mode and putting things on through Windows, is this an infallible method?
Second of all, I read the FAQ thoroughly (I think and hope) but I'm still not 100% on what Gapps to DL or how to put a working Android Market on there especially with this new S/W update. I've seen how to 'fix' the Market to see missing apps, but not how to actually install it on the G Tablet. I may have missed that post somewhere on here.
I'm also unclear if I should get Gapps or not at all, as I've read that some have FCs on there while others do not - so what's the general consensus in light of this update that was just released as of Dec. 21, 2010?
Ultimately, here is what I'd like from my GTab:
I'd like to run the new official Tapn'Tap released recently first and foremost.
I'd like to have the official/unofficial (w/e) Google Market.
I'd like to run Google Apps (Gtalk, Gmail, etc.).
IF I don't like Tapn'Tap, and this is a worse case scenario situation, as in if I HATE TnT - I'd like to have the option to slap something else on there and I'd like to make sure I don't brick my Tablet. Whether that means storing an original official TnT ROM or whatever.
Point me in the right direction please, especially considering things may have changed as of the new S/W update.
Thanks much and sorry for all the questions. I assure you I used search and I attempted to put it together on my own. It's been a long time since I've modded (G1 was the last time) and I don't do it often. Also, apologies if I posted this in the wrong section....I considered posting it in Dev. section but this one seemed better suited.
Thanks again, XDA rocks.
Neoprimal said:
Hey all,
I'm getting my G Tablet tomorrow and I'd just like to get some things clarified.
I know, the first thing some will say is USE SEARCH! Well, I did - and that's actually why I just want to get some things straight before I go down the path of modifying the device software. See, reading it all has managed to confuse me more than help me get a definitive instruction set for forging ahead.
I'm seeing the update "****s on CWM" according to a user...and then a 'fix' for that. Than I see that Gapps causes FCs for some, while it works for others. So...yeah, a little back and forth on what to do and who's instructions to follow.
Alright, so first thing's first....Should I flash the Clockwork Mod that I'm seeing available - 0.8? or is there something else I should consider or that I've missed? or maybe wait for a newer version? Should I even flash CWM if I get the newest (and I WILL be getting the newest) S/W version? Are there any downsides at all to flashing CWM on there in terms of messing with OTA updates, etc?
I read this:
"All the ROMS use a standard firmware updater that can be used by non-technical users. Here is an explanation on how it works:...."
Sooo, does that mean I can live without CWM? If an update doesn't work for some reason, will I be able to fix it or overwrite it somehow if I can't get into the tablet at all from the tablet itself? I read something about going into APX mode and putting things on through Windows, is this an infallible method?
Second of all, I read the FAQ thoroughly (I think and hope) but I'm still not 100% on what Gapps to DL or how to put a working Android Market on there especially with this new S/W update. I've seen how to 'fix' the Market to see missing apps, but not how to actually install it on the G Tablet. I may have missed that post somewhere on here.
I'm also unclear if I should get Gapps or not at all, as I've read that some have FCs on there while others do not - so what's the general consensus in light of this update that was just released as of Dec. 21, 2010?
Ultimately, here is what I'd like from my GTab:
I'd like to run the new official Tapn'Tap released recently first and foremost.
I'd like to have the official/unofficial (w/e) Google Market.
I'd like to run Google Apps (Gtalk, Gmail, etc.).
IF I don't like Tapn'Tap, and this is a worse case scenario situation, as in if I HATE TnT - I'd like to have the option to slap something else on there and I'd like to make sure I don't brick my Tablet. Whether that means storing an original official TnT ROM or whatever.
Point me in the right direction please, especially considering things may have changed as of the new S/W update.
Thanks much and sorry for all the questions. I assure you I used search and I attempted to put it together on my own. It's been a long time since I've modded (G1 was the last time) and I don't do it often. Also, apologies if I posted this in the wrong section....I considered posting it in Dev. section but this one seemed better suited.
Thanks again, XDA rocks.
Click to expand...
Click to collapse
I don't know how much direction pointing I can do but here goes..
Clockwork mod in my opinion is a necessity. Version 0.8 is the best one for most people because of how it deals with the memory locations. Yes, you can do things without it. The update process is as simple as putting an update.zip file, and a recovery folder with a command file in it on an sdcard and holding the vol + button while hitting power. It is easy. Clockwork has a lot of little features though that make life easier. You can make a complete system backup with it. You can install updates, and new firmware with it. You can completely lock up your tablet and using clockwork and your backup be back in business in about 3-4 minutes. You can load new roms and if you hate them you can go back to your old working stuff in minutes. Yes, there are ways to make one of these tablets work again when they get stuck. I don't think anyone has actually bricked one. Some may think they have, but I doubt it.
Unless you are dead set on wanting the stock TnT interface the easiest way to get what you want is to load one of the roms. Yes, there are ways to get most of it without loading a new rom. Most everyone that has gone the I have to stay stock but want all the mods has eventually just loaded a rom. TnT3.0 is based on the latest stock stuff. It has the market, flash, etc. already in it. VegaN is what I use mostly but they are both stable and fast.
Before you flash something brand new that just came out I would read about it and see what others have to say about issues. It usually only takes about 30 minutes until you can tell if it is going to be good or not.
All of the roms for this tablet have there own little quirks. The stock has gotten better with each update but it still is not as good as the ones I named.
Finally.. This tablet is very easy to play with. It is pretty much unbrickable. Anything you can possibly break one of us has probably already broken before and fixed. There are some people that seem to have problems doing every little thing. Most don't. So I wouldn't let any of it scare you off because none of it is that hard.
With a little bit of searching almost everything you may want it to do can be done. I really love mine, and when I got it almost 2 months ago I hated it...
"Finally.. This tablet is very easy to play with. It is pretty much unbrickable. Anything you can possibly break one of us has probably already broken before and fixed. There are some people that seem to have problems doing every little thing. Most don't. So I wouldn't let any of it scare you off because none of it is that hard."
"Sigh" of relief. Then I'm not too worried. As I said I've dabbled in modifying my G1 and it is mostly cake. But I've just been seeing conflicting posts on whether cwm works with the newest official tnt release or not so I wasn't sure what to do.
Thanks for your advice. And when I said pointers, I meant like this as well as pointing me to any posts I may have missed on how to do whatever. Though I THINK I found most of them.
Neoprimal said:
"Finally.. This tablet is very easy to play with. It is pretty much unbrickable. Anything you can possibly break one of us has probably already broken before and fixed. There are some people that seem to have problems doing every little thing. Most don't. So I wouldn't let any of it scare you off because none of it is that hard."
"Sigh" of relief. Then I'm not too worried. As I said I've dabbled in modifying my G1 and it is mostly cake. But I've just been seeing conflicting posts on whether cwm works with the newest official tnt release or not so I wasn't sure what to do.
Thanks for your advice. And when I said pointers, I meant like this as well as pointing me to any posts I may have missed on how to do whatever. Though I THINK I found most of them.
Click to expand...
Click to collapse
The new release overwrites clockwork. But it is not hard to put back. Always a good idea to copy the clockwork backups folder to your pc, or somewhere they won't be lost. The custom roms typically leave the recovery image alone and can be installed with or without clockwork by either extracting the zip contents for stock recovery, or installing it as is in clockwork.
Sprdtyf350 said:
Finally.. This tablet is very easy to play with. It is pretty much unbrickable.
Click to expand...
Click to collapse
I can vouch for that. Erased system, boot, data and cache in preparation for a new ROM. Accidentally rebooted and couldn't get into recovery. Booted it into APX mode, flashed stock and was on my way.
I would just run ZRoot, then upload the TnTLite 3.0 recovery and update.zip and then do the recovery mode process. You should have a microsd handy just in case it doesn't work, but so far I haven't needed that.
This tablet is much easier to work with and very forgiving since VS never took the time to lock down the bootloader etc like Motorola did with my Droid X. You really shouldn't fear changing files out etc, provided you're getting a ROM from one of the people providing them here. If you can press and hold two buttons at once, you can make your gTab an awesome little tablet. It benchmarks about 1000 points higher than my Droid X on quadrant. Can't wait to see what these guys can do with Gingerbread.
Sprdtyf350 said:
The new release overwrites clockwork. But it is not hard to put back. Always a good idea to copy the clockwork backups folder to your pc, or somewhere they won't be lost. The custom roms typically leave the recovery image alone and can be installed with or without clockwork by either extracting the zip contents for stock recovery, or installing it as is in clockwork.
Click to expand...
Click to collapse
It is also not hard to alter the update so that it does not overwrite clockwork.
Open update.zip
Find updater-script, Open in notepad++
Remove the line that references recovery.img
Flash update
hogasswild said:
I would just run ZRoot, then upload the TnTLite 3.0 recovery and update.zip and then do the recovery mode process. You should have a microsd handy just in case it doesn't work, but so far I haven't needed that.
This tablet is much easier to work with and very forgiving since VS never took the time to lock down the bootloader etc like Motorola did with my Droid X. You really shouldn't fear changing files out etc, provided you're getting a ROM from one of the people providing them here. If you can press and hold two buttons at once, you can make your gTab an awesome little tablet. It benchmarks about 1000 points higher than my Droid X on quadrant. Can't wait to see what these guys can do with Gingerbread.
Click to expand...
Click to collapse
with the new update however does the z4root still work? i heard it may not anymore. just curious also since im hopefully getting mine on sat for xmas
rothnic said:
It is also not hard to alter the update so that it does not overwrite clockwork.
Open update.zip
Find updater-script, Open in notepad++
Remove the line that references recovery.img
Flash update
Click to expand...
Click to collapse
Thanks for the info Rothnic! I had already flashed it before I figured out it removed Clockwork. Learning new stuff every day is good... Thanks..
dragonfly1113 said:
with the new update however does the z4root still work? i heard it may not anymore. just curious also since im hopefully getting mine on sat for xmas
Click to expand...
Click to collapse
The very first time I rooted, I used ZRoot and installed 2.4.0. I didn't change anything and used the exact same process of simply copying over the 3.0.0 files over to the root directory of the internal memory and did the recovery procedure (vol+ and pwr keys). It worked like a charm.
hogasswild said:
The very first time I rooted, I used ZRoot and installed 2.4.0. I didn't change anything and used the exact same process of simply copying over the 3.0.0 files over to the root directory of the internal memory and did the recovery procedure (vol+ and pwr keys). It worked like a charm.
Click to expand...
Click to collapse
Ok cool, thanks cant wait for my g tablet hopefully sat morning
I think you'll like it a lot. I also own an iPad. While they are similar they are also a little different. Merry Christmas!
hogasswild said:
I think you'll like it a lot. I also own an iPad. While they are similar they are also a little different. Merry Christmas!
Click to expand...
Click to collapse
my mom has an ipad and my dad could only buy it while i was on my honeymoon bc he knew i wouldnt approve of an apple device in the house haha.
rothnic said:
It is also not hard to alter the update so that it does not overwrite clockwork.
Open update.zip
Find updater-script, Open in notepad++
Remove the line that references recovery.img
Flash update
Click to expand...
Click to collapse
My device hasn't come yet (damn you FedEx!) but I'm eagerly awaiting it.
My plan:
Unbox, start it....do a factory reset from the getgo if it has enough juice.
Set it back up. Charge it to full. If whatever comes on it is as unbearable as I've seen in on Youtube - start modifications.
Will CWM install on it AFTER I do the update if it's available to me? I've seen that the update messes with it if it's already there - but noone's mentioned putting it on there after the fact. I may just go that route for simplicity sake.
Thanks for this!, and thank you all for chiming in with your experience. I feel much better about just getting my hands dirty in it all. I had wrote something to someone yesterday about jumping in and just doing it, but when it comes to dealing with it yourself it can be a daunting task - especially when it still has that new smell, lol. Anyway, thanks again. You guys really rock.
Will stop back later on after I've done my thing
I think they are both nice devices. There are trade off for both of them. I think the screen on the iPad is wonderful, where the gTab's is okay. But the gTab has a forward facing camera, you can print from it, and you can modify it fairly easily too.
Sprdtyf350 said:
Finally.. This tablet is very easy to play with. It is pretty much unbrickable.
Click to expand...
Click to collapse
...famous last words...
Seriously though...trust the directions from the great devs like roebeet. Follow their instructions word for word. You can switch ROMs and then flash back if you want. No worries...
Off topic!
Well...disappointment! Fedex had my package out for delivery at 8am and at 8pm, they're not here. This is why I like UPS, they show up at my door on the day of delivery, no exceptions - they have shown up at almost 9pm before. The Archos 101 I got was sent out at 8am as well but got here at 1:30pm - I suppose that was before the holiday rush.
Checking the details of my tracking I'm seeing a "delivery exception" at 7:30pm (I guess it was time to get back to the facility so they can clock out by 8pm?) and upon calling them I get a somewhat stumbling but polite CS who tells me the delivery went out "late" - upon which I asked if 8am was considered late, especially from a distribution facility WITHIN the same zip code as I am, and all he could say was "Very sorry about this".
Aaaanyway....I guess it will be tomorrow before I can report my adventures.
Think I'll be able to get my $3.99 back from Amazon? I have Prime and with that the package would have come tomorrow anyway. Basically my $3.99 is wasted. Imagine if I didn't have Prime though? Whew.
ima_UNC_fan said:
...famous last words...
Click to expand...
Click to collapse
If you can figure out how to brick it you will probably get an award.. It won't be a good award but probably one of those top ten dumb things people do awards. So far unless you plug the motherboard into a wall socket no one has bricked one. May think they have, but like I said before I doubt it..
And your right.. If it can be done, someone eventually will figure out how. And then we will all laugh at them.. At least I will
I finally got the G tablet tonight and...alright, don't flame me for this - but I don't see what all the complaints about the screen being horrendous or the device being molasses slow are about?
I don't know how people are trying to view it...but when looking at it or setting it on a stand to watch media, I'm not seeing any problem with the viewing angles. It's about the same as my laptop so I watch it the same way.
It's not even a 1/4 as slow as the stuff I've seen on Youtube or in some of the review videos I've seen around the net. I haven't gotten a single FC. Granted, I haven't put in a SD Card yet so maybe problems will start then?
I guess I should note, the very first thing I did was did a factory reset. Then I hooked it up to Wifi and got the 3053 update. I'm one of those who will be waiting for the 'official' update on the 24th.
I set up the time and date, restarted and everything works. I haven't installed flash yet (don't need it that much) and stuff that I DO want on there right now works fine (skype, pandora, fring, dropbox, evernote). I'm slowly figuring out a list of what I want/need from my Mytouch 4G to port to the VS GTab. Figure I don't really NEED Gtalk, Gmail on there because I have these on my phone AND PC - do I really want them making noises all around my home on 3 devices? I was concerned about getting the Google Apps on but now I'm finding I really don't need them. So it seems to me this will be a matter of learning to separate what I need on a tablet vs. my phone - I was of the mentality that I should just get whatever's on my phone on the tablet, this is something others apparently do as they seem to want everything that's on their phone, on their tablets as well.
I personally don't see the point in that. Had I had the Google Market, that would have escaped me as I'd have used Appbrain to just get my motherload of apps from the MT4G to the GTab. Not having it has slowed me, and now I get to re-evaluate before I do grab apps for it.
Now I just have to merge/convert my HTPC into a NAS device as well and find an app that will allow me to DLNA stream media from it and I'll be in mobile heaven.
I haven't had my wifi drop at all anywhere in my home and I've marched all over with it (I use full Wifi N, no G compat. so maybe my range is wider?). Tried email, etc. to replicate crashes and force closes but haven't so far. No surfing issues. I DID find that one app got 'stuck' being downloaded and I had to delete the file before the 'downloading' icon would go away, even after restart.
Maybe the trick to getting a workable GTab in the first place is to factory reset it before first use? Iunno. Things may change and issues may pop up the more I use it and as time passes - but so far, so good!
Again, I can't thank XDA enough for the advice and info. I've found and been given.
Sprdtyf350 said:
If you can figure out how to brick it you will probably get an award.. It won't be a good award but probably one of those top ten dumb things people do awards. So far unless you plug the motherboard into a wall socket no one has bricked one. May think they have, but like I said before I doubt it..
And your right.. If it can be done, someone eventually will figure out how. And then we will all laugh at them.. At least I will
Click to expand...
Click to collapse
I figured it out. Accidentally hit one of the devkit nvflash .cabs and boom

True Brick...QHSUSB_DLOAD

Hey guys...As a few of you know, my phone met its demise last night for (seemingly) no reason. I had recently backed up my ROM through Rom Manager and tried out a few themes from the market.
Anyways, when I plugged my phone into my computer, I see that it tried to install some drivers and then I see "QHSUSB_DLOAD" as my phone.
Ive noticed that all TRULY bricked phones (not just the sensation) all have this "QHSUSB_DLOAD" in common. No one has yet to figure out what this is or how to fix this.
Tmobile chalked it up to hardware failure and has a new (likely refurbished ) on its way.
I think we need to figure out what the heck this is. A few mentioned a connection between Rom Manager, CWM, and QHSUSB_DLOAD. I, for one, will make dang sure that Rom Manager stays off my phone...Any other ideas?
Until this is worked out, its VERY likely that rooting COULD randomly cause the dreaded true brick, QHSUSB_DLOAD style.
Matt
Just swayed my decision on wether to root or not.
So does it turn on? You are a bit unclear about your situation. Does it charge, when you charge it. And does the PC recognize it when you connect it to the PC?
Actually this is well documented. You are in Qualcomm high speed USB download mode. It is typically caused by a problem with your processor and or it's software. Either it is crapping out or more likely something corrupted the software, either by flashing a custom kernel that isn't 100% stable with the hardware (since kernel source for this phone is incomplete this IS possible) or it's just bad luck. Voltage tweaks can have a long term detrimental effect on hardware.
Hey guys, it is dead as a door knob.
http://forum.xda-developers.com/showthread.php?t=1321110
That ought to sum things up...
Im sure its bricked...I just want to look more into this as I have yet to find a single case where this was solved. It just gets pushed aside since no one knows.
Behold_this said:
Actually this is well documented. You are in Qualcomm high speed USB download mode. It is typically caused by a problem with your processor and or it's software. Either it crapped out or more likely you corrupted the software, either by flashing a custom kernel that isn't 100% stable with the hardware since kernel source for this phone is incomplete this IS possible. Voltage tweaks can have a long term detrimental effect on hardware.
Click to expand...
Click to collapse
I was using cm7, build 9 and fauxs kernel build 8. I dont do UVing or OVing and have kept the CPU speed to 1.18Ghz.
My computer told me that it failed to install whatever it felt it needed.
So this is known? Am I correct in thinking that this is a 100% brick then, or is there anything, save from tearing it open, that can be done to fix it?
Although I have a new one coming, Id like to get to the bottom of this for everyone else.
Matt
Well, yes...and no. For all intensive purposes it is bricked, however, if it's just software HTC (or anyone with a leaked loader) could recover it easily. If it's hardware then nothing can be done. You can find the Qualcomm drivers online but still need the loader (all I've found are motorola sbf's nothing for HTC). Basically you did the only thing you can at this point, but now you have a little more info on it.
Behold_this said:
Well, yes...and no. For all intensive purposes it is bricked, however, if it's just software HTC (or anyone with a leaked loader) could recover it easily. If it's hardware then nothing can be done. You can find the Qualcomm drivers online but still need the loader (all I've found at motorola sbf's nothing for HTC). Basically you did the only thing you can at this point, but now you have a little more info on it.
Click to expand...
Click to collapse
Someone could get an XDA style Nobel prize for coming out with something that could fix this phone when this happens.
Im guessing that is what a JTAG does? Would be great once warranty time is over!
I am suspicious this could be another build quality issue with HTC...Day one with this phone had the same sort of thing happen, but it eventually booted. Perhaps this was just waiting to happen?
Or, I wonder if it is related to CWM and Rom Manager? This seems to be a RARE occurance considering how many people flash the above mentioned ROM and kernel without this happening. The last thing I did before charging was backing up in Rom Manager.
Jtag is a little extreme as it involves soldering and messing with internal components, plus don't think it's been done on this chip set, but I could be wrong. The ROM is usually less of a concern then custom kernels are. Also ROM manager sucks and many times is very buggy. It is safer to do all those kinds of things through recovery. Uninstall ROM manager and forget it ever existed (just my opinion).
Behold_this said:
Jtag is a little extreme as it involves soldering and messing with internal components, plus don't think it's been done on this chip set, but I could be wrong. The ROM is usually less of a concern then custom kernels are. Also ROM manager sucks and many times is very buggy. It is safer to do all those kinds of things through recovery. Uninstall ROM manager and forget it ever existed (just my opinion).
Click to expand...
Click to collapse
Okay, how about this...I intend to S-off and reinstall CWM the SECOND I get my new phone. LOL...Should I erase my ROMs+kernels from the SD card and start over from scratch, or can I just boot up again like nothing happened?
I guess its safer to start over, huh?
EDIT: I have been reading over stories involving a hard brick and QHSUSB_DLOAD. It seems it ALL came from SD card partitioning in CWM. I was also in recovery that day restoring my ROM when I accidentally touched the screen and the phone rebooted. (After restoring) I thought it was just rebooting recovery. I wonder if something else happened? The phone booted up fine and worked for some time after. The last thing done was charging the phone via wall charger, seeing it was done, and then unplugging.
Matt
it may not be necessary, but I would. I'd just redownload all the software I plan on loading from the start and give it a clean slate, but that's just me. Also be very careful with resorting apps and data since we really don't know the total cause of your issue. All in all you probably won't have to deal with this again as long as you minimize your risk.
nice. maybe there are aliens inside your phone! Just a thought as it seems everyone seems to just turn around when they see this problem. some of the brave ones got taken by the aliens too for snooping out too much
vitusdoom said:
nice. maybe there are aliens inside your phone! Just a thought as it seems everyone seems to just turn around when they see this problem. some of the brave ones got taken by the aliens too for snooping out too much
Click to expand...
Click to collapse
Im the alien!
Yea, I never saw this happening to me. I read carefully before I do anything and have never tried anything fancy.
Im guessing that QHSUSB_DLOAD lets you know the phone is fully erased and waiting for something to be flashed the elite way? (From the factory via their gadgets). To date, NO ONE has recovered from this.
Man Id love to be the one to recover! I crapped myself when I saw QHSUSB_DLOAD mentioned on my computer. Its the kiss of death.
I also have to wait till next week to get my replacement despite me opting for the fastest most $$$ method of shipping. UPS Express is the fastest and will take till monday (which means tuesday since no one will be around to sign for it).
Ugg..
Matt
Doh! that just sucks Matt. but then again, thats way better than having some hardware issue and being fixed (anything with hardware issue fixed surely ends up going back to the guys that fixed it. they seem to put some time bomb in there so you'll go back crying to fix it again and again. lol) haven't had this issue ever since.(was flashing my phones way back then) maybe im just lucky. hopefully i will not encounter this. (the only thing I bricked was my brand new PSP2002. just bought it from US and im way over in NZ mate - didn't have a option to return it. )
where does this QHSUSB_DLOAD appear? would this come up when you turn the device on? because i've seen some devices that are bricked, they just lit up and goes off and never charges and can't go to bootloader. thinking this is 100% bricked or this QHSUSB thingy is the pure brick?
vitusdoom said:
Doh! that just sucks Matt. but then again, thats way better than having some hardware issue and being fixed (anything with hardware issue fixed surely ends up going back to the guys that fixed it. they seem to put some time bomb in there so you'll go back crying to fix it again and again. lol) haven't had this issue ever since.(was flashing my phones way back then) maybe im just lucky. hopefully i will not encounter this. (the only thing I bricked was my brand new PSP2002. just bought it from US and im way over in NZ mate - didn't have a option to return it. )
where does this QHSUSB_DLOAD appear? would this come up when you turn the device on? because i've seen some devices that are bricked, they just lit up and goes off and never charges and can't go to bootloader. thinking this is 100% bricked or this QHSUSB thingy is the pure brick?
Click to expand...
Click to collapse
The message QHSUSB_DLOAD appears the first time I tried to connect via USB to my computer. It showed up on my computer down where usb notifications occur. After it told me it couldnt install hardware, that was it. No more action from either the phone or the computer. Its like the world just passed right by my poor phone.
Maybe I will get lucky and get a phone free of dust as well! I was waiting on calling in that care package for later...Oh well.
Matt
Oooh nice! so the device really has a black screen and that message appeared on driver installation on you computer.
most of the people in the net just mentions that this driver is missing. If the driver is missing, maybe it did really get corrupted(software because of rom-manager not pointing to this ) but yeah, could also be hardware failure. did it say on your computer that it was installing some drivers for that QHSUSB_DLOAD? and it failed? what about HTC? did you see anything from HTC about this?
vitusdoom said:
The message QHSUSB_DLOAD appears the first time I tried to connect via USB to my computer. It showed up on my computer down where usb notifications occur. After it told me it couldnt install hardware, that was it. No more action from either the phone or the computer. Its like the world just passed right by my poor phone
Click to expand...
Click to collapse
this is the EXACT problem im having! on my tmobile SGS2
not sure if this has already been mentioned but what do you guys think of this?
http://mobiletechvideos.mybigcommerce.com/samsung-galaxy-s-ii-jtag-brick-repair/
Hey guys,
I'm in the same situation too.... I've been flashing hundreds of roms and all kind of software on a lot of different android phones...but this is the first time ever I came across something like that where I feel that this is the end of it!!!! I made a mistake...by not paying attention flashing an HD2 rom to my sensation!!! You know some time s**t happens... and here we go...I got a completely dead bricked sensation with nothing i can do, even I've been searching and reading for 2 days with no luck what so ever...so I guess no one is able to find a solution for this issue yet!!!!Which is too bad: confused: .I wish I was able to find some solution to this problem so I can get my phone back to life and help every one else who might end up with this issue. Because I think a lot of people might be in this situation!!!. I tried every thing I can possibly do with m y knowledge and the results was all dead ends. I just hope that this issue will be taken to the next level by some one...like all the other phones that it can be unbricked...so why not the sensation!!!?. Any one can come up with and ideas for this please help us as a community to get pass by this dead end on our Htc sensations.
Guys i have absolutely same problem with my sensation, i believe there must be a way how to bring our phones back to life. Im sure that on my phone its just software problem caused by backing to s-on(got bricked right after adb rebootbootloader). So if some1 find out how to unbrick, PLEASE post it. I dont want to solve it by warrany, because its little far for me :-(

Is my Samsung Infuse DEAD?

Hey, guys. Hoping some of you experts can help me diagnose what's wrong with my Samsung Infuse. I bought it off Craigslist at the end of May, and the guy had the phone with the original screen protector on it, with the original case and all accessories, so I had no reason to believe it had any problems. He told me the phone was already rooted & unlocked, which I wanted since I signed up with Straight Talk. I used it for June & July and had a host of problems, so I put on the CM10 ROM last week to see if it helped. It didn't. Here are the problems I continuously encounter:
1. When going to unlock my phone with a pattern, once in awhile it won't detect my finger-presses. Sometimes nothing shows up at all, sometimes one of the dots will highlight as I pass over it, but it won't draw. Eventually the screen turns off, and I turn it on and try it again. Usually it ends up working.
2. The battery dies much quicker than I expect it should. I tried running JuiceDefender and not running JuiceDefender, and it doesn't seem to make a difference. Even without using my phone much for anything, even with the screen off, the battery will run out before the day is out. It's like if you were driving and had a hole in your tire... seems like some sort of a leak.
3. The cell radio seems flaky. Sometimes I won't get texts on time. A lot of the time I can't access any data, which is very important as I use Google Voice for lots of my texting, so I send a text and it won't go out. Loading web pages or reloading my email shows that it is a data problem.
Those are the primary problems, and I suspect that somehow they are all related. I'm not sure if the Craigslist guy sold me a lemon, or there is some other problem that came up. I've tried multiple ROM's and disabling every app I can think of. Can anyone think of anything that would cause these problems & any way to fix it? Or do I just own a broke phone that I have to throw in the garbage?
Thanks in advance for reading!
a whole slew of problems can lead to a whole slew of possibilities for your issues.
first, i wasnt aware that you could do any of this on a straight talk phone, but i could be wrong. i am not the "expert" you may be looking or hoping for, though one i am sure will show up.
second, i think the response you may get is......did you go to JB straight from Gingerbread??? that will cause HUGE problems.
dd you read OP and follow to a tee??? again HUUUUGGEE problems.
the "never fail" here.....READ READ READ. feel confident as to what you are doing and follow steps one at a time. UNDERSTAND steps one at a time.
first thing that never hurts.....return to stock and start from scratch.
"super everything thread" under development.
Odin "stock-root & modded 3e rcovery.
follow all directions TO THE TTT.
if that doesnt work, you might have to get some mortar, you've got yourself a BRICK.
i know almost everyone else here is more of a expert than i am, but i do believe that is where they will tell you to start
good luck and be sure and thank the experts
captemo said:
first, i wasnt aware that you could do any of this on a straight talk phone, but i could be wrong. i am not the "expert" you may be looking or hoping for, though one i am sure will show up.
second, i think the response you may get is......did you go to JB straight from Gingerbread??? that will cause HUGE problems.
dd you read OP and follow to a tee??? again HUUUUGGEE problems.
first thing that never hurts.....return to stock and start from scratch.
"super everything thread" under development.
Odin "stock-root & modded 3e rcovery.
follow all directions TO THE TTT.
if that doesnt work, you might have to get some mortar, you've got yourself a BRICK.
Click to expand...
Click to collapse
While I have no idea what you're getting at by your Straight Talk comment, as ST is little more than AT&T service that's sold through a 3rd party at a discounted rate, the fact that he's using ST may be part of his problems, at least in regards to the network issues. I'm also having an unbelievable amount of data issues on ST. ST is having some network problems that are affecting a decent amount of customers who are on their AT&T network.
One thing that the OP may want to try is this: Download DNS Changer from the Play Store, and change your primary and secondary DNS to OpenDNS1 and OpenDNS2. Or try different settings, as there are a bunch that are available. That has made at least some difference with my data connectivity issues.
Based on my own experience, having tried to go to JB directly from GB, is that if it's going to affect your radio, it's likely to completely wipe out your EFS data so you won't have ANY cellular or data networking capabilities. As stated, that's simply based on how it worked out for me, and there could easily be other side-effects that just didn't happen to show up for me.
I agree with returning completely to stock UCLB3, with the GB bootloaders. Then flash Entropy's 4.4.2012 Kernel, which will also install CWM Recovery. I'd personally reccomend Heimdall, as it seems to be somewhat simpler. Detailed information on returning to stock via Heimdall can be found in this thread:
http://forum.xda-developers.com/showthread.php?t=1629079&highlight=heimdall+uclb3
If you use it, be sure to thank qkster for making it available. He's probably the most helpful person you're likely to find on this forum, especially where us noobs are concerned.
I would take it back to stock and start all over.
Here is a very helpful thread.
http://forum.xda-developers.com/showthread.php?t=1700416
I agree with parrot head. When issues arise go back to stock. That's the best part of our phones. They are damn near impossible to really mess up. Just have to be ware of bootloader flash going wrong. If you got your gb rom from keis your good to go though.
Sent from my SGH-I997 using xda app-developers app
Appreciate the response, guys. I guess it doesn't hurt to try to start from scratch... AGAIN! It just seems like I'm putting an awful lot of hours into putting new ROM's and bootloaders on this phone. Going to be especially frustrating if I go through all the steps and it still doesn't fix my issues, which would mean my phone is broke. Oh well, guess I have little other choice.
All of the issues sound related..
It shouldn't take long to drop to stock and flash up to JB.. I've bobbled and missed steps here and there and have had to return from stock more times than I care to admit.. even rooting and flashing up the ladder only take about 20 minutes if even that..
Good luck!
drnecropolis said:
All of the issues sound related..
It shouldn't take long to drop to stock and flash up to JB.. I've bobbled and missed steps here and there and have had to return from stock more times than I care to admit.. even rooting and flashing up the ladder only take about 20 minutes if even that..
Good luck!
Click to expand...
Click to collapse
Yes, the flashing process isn't that long, it's getting back my phone to all of my customized settings that ends up taking weeks. Home screen icon positioning, logging in to every app, system settings, etc.
Didn't create a backup?
drnecropolis said:
Didn't create a backup?
Click to expand...
Click to collapse
I've always created backups with Titanium Backup, but when I restore the apps, a lot of them ask me to re-login or re-verify myself.
Thanks for the advice guys.
Spent a whole day going back to stock, then CWM red, then ICS, then Jellybean. Things seem to be markedly better, but the phone still seems laggy in a few places. Is this just because it's not the latest and greatest processor?
Also, the GPS just does not work right. It's still identifying me as being in Missouri even though I'm in Nevada. Consistently. Do I just have to live with that?
veeRob said:
Thanks for the advice guys.
Spent a whole day going back to stock, then CWM red, then ICS, then Jellybean. Things seem to be markedly better, but the phone still seems laggy in a few places. Is this just because it's not the latest and greatest processor?
Also, the GPS just does not work right. It's still identifying me as being in Missouri even though I'm in Nevada. Consistently. Do I just have to live with that?
Click to expand...
Click to collapse
Are you still using the Trebuchet Launcher that comes built-in to the JB ROM? If so, that may be part of your lag problems. I just use ADW EX launcher. Here's an excerpt from the Paranoid Android JB OP:
******* EVERYONE: If you experience a sudden lag for no reason, IT is due to Trebuchet. GOOD NEWS though... From reading the log cat on my end, there is a very simple fix... Go to settings -Launcher - Homescreen - And Check "Resize any widget" and you are good to go! Instantly fixes the lag problem that a few have been experiencing. I have located the source code that needs to be changed and this will be enabled by default on future builds. ********
Click to expand...
Click to collapse
As far as the GPS goes, I think Samsung just used ****ty receivers in the Infuse. My GPS isn't quite as bad as yours seems to be, but it's nowhere near as accurate or reliable as the GPS chipset in my crummy little Optimus V.

System Update

Prompted to install a system update today. I hesitate as hopeful to obtain at least root if not bootloader unlock and don't want an update to stand in the way of that (eventual) process. Any thoughts on this 5/10/16 update from developers and any recommendation on whether it's harmless or perhaps that we should hold off... Thank you.
I would like to know the same
Sent from my VS987 using Tapatalk
Its harmless because its an official update.
I looked it up and it said it is to improve the interface for visual voice mail, some changes to how you can enter airplane mode so you won't do it by accident, and allow display of data from the active exchange server, whatever that is. Nothing about security, but I would be skeptical. You never know what they might sneak into the update. It didn't sound like any big improvements so I didn't take it.
igomoto said:
Prompted to install a system update today. I hesitate as hopeful to obtain at least root if not bootloader unlock and don't want an update to stand in the way of that (eventual) process. Any thoughts on this 5/10/16 update from developers and any recommendation on whether it's harmless or perhaps that we should hold off... Thank you.
Click to expand...
Click to collapse
There's no reason not to take it.
I bought my G5 with the idea that the phone will NEVER be rooted or have an unlocked bootloader. Why? Because LG doesn't sell as well as Samsung or HTC or... and therefore has fewer developers working on unlocking/rooting and it's a very new phone, most newer phones have figured out how to permanently lock the bootloader and prevent rooting.
I certainly hope I'm wrong about this but.... :crying:
My Thunderbolt, Galaxy S3, Galaxy S4, M8 were bootloader unlocked, rooted and running TWRP and custom ROMs within an hour of getting them home so I had to think long and hard about buying a phone that I believe will never be unlocked or rooted but LG has nothing as horrible as TouchWiz or Sense and Nova Launcher make the phone suit my needs.
FWIW, I took the update yesterday and will take all future updates.
igomoto said:
Prompted to install a system update today. I hesitate as hopeful to obtain at least root if not bootloader unlock and don't want an update to stand in the way of that (eventual) process. Any thoughts on this 5/10/16 update from developers and any recommendation on whether it's harmless or perhaps that we should hold off... Thank you.
Click to expand...
Click to collapse
Hopefully @autoprime can take a look at it for us sometime and let us know the rollback situation with the new update. Until he lets me know its safe, I generally stay away!
Coycaine said:
Hopefully @autoprime can take a look at it for us sometime and let us know the rollback situation with the new update. Until he lets me know its safe, I generally stay away!
Click to expand...
Click to collapse
12A KDZ is out.
You can download it HERE. And as always.. I try to add all KDZ's to http://bit.ly/lgkdzlist
12A does not pop a version fuse... so there should be no issues going back to 11A from 12A as far as I can tell. :good:
I experienced issues after the update that were not there prior to its installation. Double tap to wake became hit or miss, although double tap to sleep worked just fine. And the power button became glitchy as well. On several occasions I couldn't wake the phone with either method and attempted a long press of the power button in order to shut the phone down which would not work. All this after only having had the phone less than 24 hours. Needless to say it went back and a replacement was obtained.
Thus far no problems with the new device but I have yet to install the system update (12A) which has downloaded and is pestering me to run.
jamesava said:
Its harmless because its an official update.
Click to expand...
Click to collapse
Is this your first android phone or something? :laugh:
No, but seriously, Verizon sends out updates that f*ck things up all the time. Marshmallow ruined my G4 and lollipop ruined my S4. Plus, each update you take makes your chances of getting root that much slimmer, because if a dev has been working to root a phone for X amount of months, they've only been trying it with the software at the beginning of those X amount of months. A security patch could make root impossible until further dev work is done.
---------- Post added at 11:53 PM ---------- Previous post was at 11:53 PM ----------
rapperman said:
I experienced issues after the update that were not there prior to its installation. Double tap to wake became hit or miss, although double tap to sleep worked just fine. And the power button became glitchy as well. On several occasions I couldn't wake the phone with either method and attempted a long press of the power button in order to shut the phone down which would not work. All this after only having had the phone less than 24 hours. Needless to say it went back and a replacement was obtained.
Thus far no problems with the new device but I have yet to install the system update (12A) which has downloaded and is pestering me to run.
Click to expand...
Click to collapse
In regards to your power button issue, have you noticed that your phone is slower to wake when you have just locked it? If I shut my screen off and quickly flip it back on, there's a good 3+ second delay. Otherwise, doubletap to unlock and finger print to unlock are both pretty much instant if I count a good 2-3 "Mississippi"s ;P
ryanpm40 said:
In regards to your power button issue, have you noticed that your phone is slower to wake when you have just locked it? If I shut my screen off and quickly flip it back on, there's a good 3+ second delay. Otherwise, doubletap to unlock and finger print to unlock are both pretty much instant if I count a good 2-3 "Mississippi"s ;P
Click to expand...
Click to collapse
With this G5 I've not experienced the issue you've described, or any of the other issues that plagued the first one I purchased. I've even installed the 12A update which I believed were responsible for the "doubletap" issues. There's no doubt in my mind now that the first device was defective.
The only problem I am experiencing at this point is this nagging sensation that I should give the HTC 10 a comparative look before the end of my 14 day evaluation period lol.
Please Help Me!!
autoprime said:
12A KDZ is out.
You can download it HERE. And as always.. I try to add all KDZ's to http://bit.ly/lgkdzlist
12A does not pop a version fuse... so there should be no issues going back to 11A from 12A as far as I can tell. :good:
Click to expand...
Click to collapse
Hello Good Day,how can i install the kdz file????,im a noob in this and i cant find how to do it,i search and i found that i need the program Lg Up and others files,but i was unable to find the right ones......
can you guide me???,please....
My Cellphone is recognized as a Lg g4 by the program VZW Software Upgrade Assistant.......
and i tell this because it show me that is an update but is VS98624C.........:silly::silly::silly:
rapperman said:
I experienced issues after the update that were not there prior to its installation. Double tap to wake became hit or miss, although double tap to sleep worked just fine. And the power button became glitchy as well. On several occasions I couldn't wake the phone with either method and attempted a long press of the power button in order to shut the phone down which would not work. All this after only having had the phone less than 24 hours. Needless to say it went back and a replacement was obtained.
Thus far no problems with the new device but I have yet to install the system update (12A) which has downloaded and is pestering me to run.
Click to expand...
Click to collapse
I cleared the update by booting to the bootloader and wiping cache. It rebooted and then I cleared away the unsuccessful update message. Then using adb, I run the short command that @autoprime posted in his topic for all things LG G5. It hides the system update and I haven't got the prompt since.
Sent from my VS987 using Tapatalk

Categories

Resources