Just saw this on Reddit. Not sure if anyone on the Skyrocket knows this or not.
Here is the OP: http://forum.xda-developers.com/showthread.php?t=1633938
No mentioning of our device in this post. This would mean we are not affected, or am I missing something?
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2
Danielk425 said:
No mentioning of our device in this post. This would mean we are not affected, or am I missing something?
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2
Click to expand...
Click to collapse
I was about to ask the same thing!
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2
UCLD3 ICS leak for the AT&T Samsung Galaxy S II (SGH-I777) - Other leaks may also be affected
Click to expand...
Click to collapse
That's all I see there too. Hmmm.. But, that's not our device it's the "Other Leaks" that worries..
I'm not educated enough on all of this and may be way off base, but the Note is mentioned...could this be why some people have had serious issues related to using the leak Note modem?
Well considering the Samsung Galaxy S II is listed, even though it .is a different model, I would think it would be safe to assume that the Skyrocket could also be effected by this since it is kernel based.
Swisser said:
Well considering the Samsung Galaxy S II is listed, even though it .is a different model, I would think it would be safe to assume that the Skyrocket could also be effected by this since it is kernel based.
Click to expand...
Click to collapse
It is also safe to assume that I will continue to use the leak. Happy star was day. May the forth be with you!
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2
Our kernel is nothing like gs2 we have totally different hardware
Sent from my SGH-T989 using Tapatalk 2
Remember those mystery bricks we thought were user error months ago? I think this is device specific and not kernel or rom dependent. Called this months ago
Sent from my SAMSUNG-SGH-I727 using xda premium
dakpluto said:
I'm not educated enough on all of this and may be way off base, but the Note is mentioned...could this be why some people have had serious issues related to using the leak Note modem?
Click to expand...
Click to collapse
Was wondering the same thing.
Reminds me of smoking pot in the late 70's. You enjoyed it too much to stop, but you worried about paraquat.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
This belongs in general section I think
Sent from my SGH-T989 using Tapatalk 2
Anyone who's been using the leak and flashed stuff in CWM over 20 or so times yet?
Just curious. Haven't heard of too many people bricking in our community that (most likely) wasn't user error. Of course I'm excluding dev's.
Sent from my SGH-T989 using XDA
slotstik04 said:
Anyone who's been using the leak and flashed stuff in CWM over 20 or so times yet?
Just curious. Haven't heard of too many people bricking in our community that (most likely) wasn't user error. Of course I'm excluding dev's.
Sent from my SGH-T989 using XDA
Click to expand...
Click to collapse
Lord knows I've flashed tons of ICS leak roms. No brick yet. But I also never had issues from the Note radio either.
That is disconcerting.
I guess there is no news yet what the source of the issue is exactly?
Here is my concern(s) with all of this. I'm not questioning the legitimacy of the original poster(s) of this, but:
A. Where is the origin of all of this? How was it discovered.
B. How can it be confirmed as a Kernel bug if it can't even be identified as to which exact source it originated from or how it works?
It seems to me that there will always be hard bricks when flashing because of user error, hardware failures, unexpected glitches, or a combination of all three. So how exactly was it determined that this is caused by a "bug" that Samsung put in certain kernels to hardbrick peoples phones?
Even though these are leaks and not "official" releases, Samsung would still be liable for damages because it is still reasonably argued that people will still use these leaks (even though unauthorized) and by doing so will damage their phones. Samsung would only purposely put a bug in the kernel for the sole purpose of damaging someone's phone. Thereby holding Samasung liable for knowingly damaging property. It is the same as if you put traps in your house to hurt people that might break in. You are still liable for enjuring them even though they illegally broke into your house because it is reasonable to assume that you knew the traps would cause harm. I'm not agreeing with it, but its is the law.
So people brick their phones. How do we know for sure it is due to a bug Samsung put in the kernel??
Yeah I am questioning the recommendation on recovery in the OP's link. The recovery has its own kernel, that does not seem to gel very well with that assessment (unless the recovery is using the same buggy kernel, at least the recovery I use for the SR, is based of 2.6.x kernel source).
But I will agree with the assessment that the buggy kernel (via ROM flash) can cause the eMMC corruption, although I would suspect the layers above (e.g. vold configuration, but cannot rule out kernel bug).
scott14719 said:
Here is my concern(s) with all of this. I'm not questioning the legitimacy of the original poster(s) of this, but:
A. Where is the origin of all of this? How was it discovered.
B. How can it be confirmed as a Kernel bug if it can't even be identified as to which exact source it originated from or how it works?
It seems to me that there will always be hard bricks when flashing because of user error, hardware failures, unexpected glitches, or a combination of all three. So how exactly was it determined that this is caused by a "bug" that Samsung put in certain kernels to hardbrick peoples phones?
Even though these are leaks and not "official" releases, Samsung would still be liable for damages because it is still reasonably argued that people will still use these leaks (even though unauthorized) and by doing so will damage their phones. Samsung would only purposely put a bug in the kernel for the sole purpose of damaging someone's phone. Thereby holding Samasung liable for knowingly damaging property. It is the same as if you put traps in your house to hurt people that might break in. You are still liable for enjuring them even though they illegally broke into your house because it is reasonable to assume that you knew the traps would cause harm. I'm not agreeing with it, but its is the law.
So people brick their phones. How do we know for sure it is due to a bug Samsung put in the kernel??
Click to expand...
Click to collapse
Read through the thread that first brought the issue up. It is provided in that warning thread. Under various occasions did people brick simply by CWM on their GS2's. In each case, they have flashed their version of the UCLD leak via odin and concequently bricked after a few CWM flashes. There is some credibility to these claims. Entropy is a great dev-I'd take his word for it. I am so glad I didn't flash the UCLD leak onto my girlfriends S2. Stuck with AOKP
BUT this leaves us with the question: Are we infected as a variant of the gs2 family?
Their leak was also provided by an unnamed source through DG and at the same time as ours was leaked. But...
So far I haven't seen any claims in our forums about a CWM brick after our UCLD leak. But then again I have limited internet access right now and can't search our threads to see if there actually were any. (Just basing off what I've read in the forums since the leak came out)
Also, no one is putting Samsung to blame. They are all just trying to pinpoint the issue. We understand it is our choice to use a leak. (Same with any rom. No one blames the rom builder if their flash goes bad) So far all occcurences have been from flashing a few times after the UCLD leak like I mentioned before, so it indicates that it most likely has something to do with it.
Edit: sorry misread your post. I still don't think I could blame Samsung for it. Its our choice to flash anything onto our devices and we should be held liable.
Sent from my SGH-T989 using XDA
From what I read it specified I-777. But still who knows for sure without further research.
Sent from my SAMSUNG-SGH-I727 using xda premium
Given the number and popularity of the many ICS roms for skyrocket and how many of them recommend one to three data wipes and system formats every time you flash it would seem like this is not a problem for the skyrocket.
Related
Returning your Evo anytime soon? Why unroot when you can just flash a completely plain Jane looking stock Froyo ROM that's lacking the Superuser apk? The geniuses over at Sprint or Best Buy will never be able to tell the difference.This is netarchy's HTC OTA Froyo 2.2, *FINAL*, build 3.36.651.6 (Rooted) Odexed ROM, the -only- thing that has been changed is the removal of the Superuser Permissions apk.
Wipe data, cache, and dalvik cache, then flash.
http://www.4shared.com/file/0XGojjon/StockROM.html
If you use this, feel free to gloat in this thread about how you just returned a rooted Evo to Sprint or Best Buy.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Are you trying to get over on the man?
If so, where's the" like' button?
It goes further than just the rom...truth be told, there's a system they can actually look in to see what rom the phone is running...(I worked for Sprint), but I don't think they're smart enough to look at it...I'll post shots of what it looks like...sometime this week...I've been meaning to give a shout to all the Devs to add something that allows a person to make the Rom look stock...
RavenII said:
It goes further than just the rom...truth be told, there's a system they can actually look in to see what rom the phone is running...(I worked for Sprint), but I don't think they're smart enough to look at it...I'll post shots of what it looks like...sometime this week...I've been meaning to give a shout to all the Devs to add something that allows a person to make the Rom look stock...
Click to expand...
Click to collapse
Yeah, this ROM totally preys on the not so clever reps that work at stores like Sprint and Best Buy. No offense, of course. I actually returned my last Evo with a stock ROM that was still sporting the Superuser Permissions apk. They didn't catch that.10 times out of 9 they're not going to even know about rooting or what to look for to spot a rooted device.
Anyone working for them that wouldnt catch this, wouldnt catch a non stock rom no matter what it is. Anybody actually looking to tell if a phone is rooted will look for a custom recovery.
dcmtnbkr said:
Anyone working for them that wouldnt catch this, wouldnt catch a non stock rom no matter what it is. Anybody actually looking to tell if a phone is rooted will look for a custom recovery.
Click to expand...
Click to collapse
I highly doubt any rep is looking for a custom recovery, although that would be the thing to look for. But seeing the Superuser Permissions app might cause a rep to grow a brain and do some investigating, which could potentially lead to some problems returning your Evo, if you are in fact, returning it rooted. I'm just trying to circumvent some hassle by eliminating that possible hitch.
Sheer genius.
Sent from my PC36100 using XDA App
neckface said:
10 times out of 9 they're not going to even know about rooting or what to look for to spot a rooted device.
Click to expand...
Click to collapse
Lmao!!!!! That's funny. 10 out of nine.
Sent from my PC36100 using XDA App
can i flash this on top of a 1.47 rooted rom?
jebus27 said:
can i flash this on top of a 1.47 rooted rom?
Click to expand...
Click to collapse
yes, of coarse
LOL even with a custom rom and boot screen Sprint took my phone back. Who cares? rooting doesn't effect your hardware so why would they even care? Flashing an official RUU undoes rooting for the most part anyway (minus unrevoked forever)
Thanks you saved me a hour before trading in my sons evo
Thx for that, you saved me from unrooting (again) and rooting my phone (again).
I have to take it to the service to fix my camera.
No-No
neckface said:
Yeah, this ROM totally preys on the not so clever reps that work at stores like Sprint and Best Buy. No offense, of course. I actually returned my last Evo with a stock ROM that was still sporting the Superuser Permissions apk. They didn't catch that.10 times out of 9 they're not going to even know about rooting or what to look for to spot a rooted device.
Click to expand...
Click to collapse
1st of all EVERYONE I worked with at Sprint and half of the upper management have rooted Evos, even rooted Epics. We know, we're not idiots you idiot
The reps aren't really going to care because the account that device was active on can get charged up to full retail for the new device if the Evo is discovered to be rooted. Most of the time these phones get recycled as refurbished replacement phones, and there's a simple check (a couple actually) to determine root, with or without Superuser. Got an e-mail about this from our service technicians about going into the About Phone section and how the phone betrays itself.
That and the bootloader screen shows S-Off at the top for most rooted Evo's which takes all of 60 seconds to check.
On a side note, it really is unlikely Sprint is wasting man-power checking every single evo coming in, especially with everyone trading up to the 3D. Just throwing it out there, YOU REALLY SHOULD JUST UNROOT the damn thing it's easy and could (possibly) spare you north of $450. I mean really, even if it takes an hour you theoretically made almost $500 an hour.
skatrwannabe3 said:
1st of all EVERYONE I worked with at Sprint and half of the upper management have rooted Evos, even rooted Epics. We know, we're not idiots you idiot
The reps aren't really going to care because the account that device was active on can get charged up to full retail for the new device if the Evo is discovered to be rooted. Most of the time these phones get recycled as refurbished replacement phones, and there's a simple check (a couple actually) to determine root, with or without Superuser. Got an e-mail about this from our service technicians about going into the About Phone section and how the phone betrays itself.
That and the bootloader screen shows S-Off at the top for most rooted Evo's which takes all of 60 seconds to check.
On a side note, it really is unlikely Sprint is wasting man-power checking every single evo coming in, especially with everyone trading up to the 3D. Just throwing it out there, YOU REALLY SHOULD JUST UNROOT the damn thing it's easy and could (possibly) spare you north of $450. I mean really, even if it takes an hour you theoretically made almost $500 an hour.
Click to expand...
Click to collapse
I'm pretty sure this method is intended primarily for those taking their phones in for service.
When actually sending the phone back to Sprint (to take advantage of their insurance, for example), a full unroot should always be done. That's where the technicians will be more likely to poke and prod.
neckface said:
Returning your Evo anytime soon? Why unroot when you can just flash a completely plain Jane looking stock Froyo ROM that's lacking the Superuser apk? The geniuses over at Sprint or Best Buy will never be able to tell the difference.This is netarchy's HTC OTA Froyo 2.2, *FINAL*, build 3.36.651.6 (Rooted) Odexed ROM, the -only- thing that has been changed is the removal of the Superuser Permissions apk.
Wipe data, cache, and dalvik cache, then flash.
http://www.4shared.com/file/0XGojjon/StockROM.html
If you use this, feel free to gloat in this thread about how you just returned a rooted Evo to Sprint or Best Buy.
Click to expand...
Click to collapse
awesome idea... I likey
skatrwannabe3 said:
1st of all EVERYONE I worked with at Sprint and half of the upper management have rooted Evos, even rooted Epics. We know, we're not idiots you idiot
The reps aren't really going to care because the account that device was active on can get charged up to full retail for the new device if the Evo is discovered to be rooted. Most of the time these phones get recycled as refurbished replacement phones, and there's a simple check (a couple actually) to determine root, with or without Superuser. Got an e-mail about this from our service technicians about going into the About Phone section and how the phone betrays itself.
That and the bootloader screen shows S-Off at the top for most rooted Evo's which takes all of 60 seconds to check.
On a side note, it really is unlikely Sprint is wasting man-power checking every single evo coming in, especially with everyone trading up to the 3D. Just throwing it out there, YOU REALLY SHOULD JUST UNROOT the damn thing it's easy and could (possibly) spare you north of $450. I mean really, even if it takes an hour you theoretically made almost $500 an hour.
Click to expand...
Click to collapse
....................so
Netarchy uses a custom kernal...not hard to figure out.
Sent from my PC36100 using Tapatalk
Why didn't I think of this?
I'd like to do some research on an Infuse 4g. If anyone has a busted phone, I'd like to do some reverse engineering on it. The work I do will benefeit the community and it will help out greatly with porting other OSs and working with alternate bootloaders. In order to get the information about the OM pins, I must remove the processor. I do not have the ability to replace the processor afterwards. The board will give it's life to help others.
It does not matter about condition.... won't turn on, water damaged, screen cracked, case broken.. I'd like to destructively examine the mainboard for component identification and location.
AdamOutler said:
I'd like to do some research on an Infuse 4g. If anyone has a busted phone, I'd like to do some reverse engineering on it. The work I do will benefeit the community and it will help out greatly with porting other OSs and working with alternate bootloaders. In order to get the information about the OM pins, I must remove the processor. I do not have the ability to replace the processor afterwards. The board will give it's life to help others.
It does not matter about condition.... won't turn on, water damaged, screen cracked, case broken.. I'd like to destructively examine the mainboard for component identification and location.
Click to expand...
Click to collapse
If I had an extra $125 lying around to pay the insurance deductible (soon to be $199...), I would gladly 'lose' my phone for the cause.
Otherwise, I've seen a couple on craigslist, but the cheapest was $75 due to "toilet damage".
I purchased my phone outright for $600. It has no insurance and a few months of warranty. I would not recommend anyone participate if their phone is under warranty or warrantable.
If you have an extra device around, I'd like to document it and make something for everyone to use as a reference for hacking their devices.
AdamOutler said:
I purchased my phone outright for $600. It has no insurance and a few months of warranty. I would not recommend anyone participate if their phone is under warranty or warrantable.
If you have an extra device around, I'd like to document it and make something for everyone to use as a reference for hacking their devices.
Click to expand...
Click to collapse
That would be awesome! I will keep an eye on eBay and craigslist for any dirt-cheap non-functional Infuses. I'd probably be willing to pay up to $25 for a cadaver.
Bump, we've got a bootloader hello world running on the Captivate. I'd like to get this up and running on an infuse. It won't be long until we have a download mode for our processor.
Once we get download mode, we will be able to run a tethered boot of just about any ARM compatible operating system.
Bump. This means unlocking the actual bootloaders.
AdamOutler said:
Bump, we've got a bootloader hello world running on the Captivate. I'd like to get this up and running on an infuse. It won't be long until we have a download mode for our processor.
Once we get download mode, we will be able to run a tethered boot of just about any ARM compatible operating system.
Click to expand...
Click to collapse
This mod work.and works well. Bump for my wife's infuse.
Sent from my unBrickablE captivate.
This is a reality, we just need a broken board to find out the mod.
it's one of the resistors near point B which needs to be removed and jumpered to another resistor.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I do have an infuse that has been in a pool but it works well enough to use
Just curious as to what other OS's would actually be ported to the infuse and what the actual bootloader unlock could do
Edit: WP7 and MeeGo would be really cool!
halfnelson117 said:
I do have an infuse that has been in a pool but it works well enough to use
Just curious as to what other OS's would actually be ported to the infuse and what the actual bootloader unlock could do
Edit: WP7 and MeeGo would be really cool!
Click to expand...
Click to collapse
For now I'm playing it safe and trying something about my level.. check this out. http://forum.xda-developers.com/showthread.php?t=1247962
We could get Nexus running on our devices too. For those who don't know, Nexus is the official Google Dev platform which they release the latest, greatest android versions.
Good luck adam that be great
Sent from my SAMSUNG-SGH-I997 using xda premium
I currently don't have debit card or Id totally get this.
http://www.ebay.com/itm/Samsung-Inf...0569291862?pt=Cell_Phones&hash=item1e66894856 its only $29 right now with less than a day remaining,
Ill keep looking for cheap ones when I get my new debit card ill get one if I can get it for under $50 bucks.
maybe we should start a donation thread to get a broken one for Adam?
Bump! Still need an Infuse4G mainboard. Anyone got one with water damage, a broken screen, or anything? I need it to pull the processor off for analysis.
AdamOutler said:
Bump! Still need an Infuse4G mainboard. Anyone got one with water damage, a broken screen, or anything? I need it to pull the processor off for analysis.
Click to expand...
Click to collapse
I'm going to look for another broken infuse to buy to give to you, and if the worst comes, ill try to get some money and report mine as lost, and get another one.
Just a question, if you get this mod working, what exactly does it do?
Sent from my phone. :3
Longcat14 said:
I'm going to look for another broken infuse to buy to give to you, and if the worst comes, ill try to get some money and report mine as lost, and get another one.
Just a question, if you get this mod working, what exactly does it do?
Sent from my phone. :3
Click to expand...
Click to collapse
It works like this, you do the hardware modification once, and you can unbrick your phone under ANY circumstances like this:
It enables uploading of the Hummingbird Interceptor Bootloader (HIBL). The HIBL enables uploading of unsecured code. You can upload bootloaders or kernels, or just about anything with the HIBL.
AdamOutler said:
It works like this, you do the hardware modification once, and you can unbrick your phone under ANY circumstances like this:
It enables uploading of the Hummingbird Interceptor Bootloader (HIBL). The HIBL enables uploading of unsecured code. You can upload bootloaders or kernels, or just about anything with the HIBL.
Click to expand...
Click to collapse
So.. your telling me (watched that video), that you HARD bricked your phone, did a little hardware, and brought it back from the dead thanks to the HIBL? You sir, are a god amongst tech folk.
Sent from my phone. :3
Longcat14 said:
So.. your telling me (watched that video), that you HARD bricked your phone, did a little hardware, and brought it back from the dead thanks to the HIBL?
Click to expand...
Click to collapse
Yes. I DELETED the Primitive and Secondary bootloaders totally from that device, used Ultimate UnBrick Resurrector to upload Download Mode to the device, then used Heimdall One-Click to reload firmware.
I have an infuse with a busted sim card reader and it wont turn on pm me if its good for you
Sent from my SGH-I997 using XDA App
pumasmedina7 said:
I have an infuse with a busted sim card reader and it wont turn on pm me if its good for you
Sent from my SGH-I997 using XDA App
Click to expand...
Click to collapse
Dude, that would be SO helpful.
If you can, do it, the Infuse will be useless after that though (Processor removed, from what he's said), but I think you can just warranty replace it for another after that.
So this is what we need to get other OS'es on the Infuse?
By other OS'es, you mean like the HD2 that has WP7, Android and everything?
OR does this mean better ROM's?
Ok, So I don't really see anything in the dev field for this phone. I have been trying to get root on it for close to a month now...
Now, Forget root for just a second. I noticed something on this device. There are 2 different download modes.
When I boot to download mode using Vol-down+power, It goes to a screen warning about installing a custom os, blah blah. It asks if I want to continue (Vol-up) or if I want to cancel and reboot (Vol-down). Hit Vol-up and it takes me to download mode. The one thing I find strange about this download mode is that it says "ODIN Mode".
When I use a USB jig that I purchased from MobileTechVideos, It skips the warning screen and goes directly to download mode, only thing different is that it says "Factory Mode".
These are 2 completely different modes.
I am curious to see if there is anybody willing to take on development with this device. I unfortunately do not have the skill whatsoever to do it, but I can help with it, if instructed on the proper procedures. I would love to see some stuff come out for this phone.
Also, on another note, if I am not mistaken, this phone also has the same processor that the Samsung Galaxy S series of phones have leaving it open for the Unbrickable Mod. I have torn into the device and believe that I have found the OM resistors, but again do not have the means of telling which one is what.
Anyways, I seriously see some potential with this device. I have seen many people post asking for root, ROM's, and all kinds of stuff involving this phone, on many forums to include this one, and all have been brushed off and ignored. It is sad really.
If I posted in the wrong section, I am sorry, There is no sub-forum for this phone.
Anyways, cheers!!
graydiggy
Here are some images, so you can see exactly what I am talking about.
Warning screen, Blah blah.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
By graydiggy at 2012-02-13
ODIN Mode screen (No Jig)
By graydiggy at 2012-02-13
Factory Mode scree (Jig Used)
By graydiggy at 2012-02-13
It just looks like you've discovered both recovery and download mode. I have an S2 and they're both standard, out of the box. With the S2 you hold the home button and volume up while turning on for recovery mode, and the home button and volume down while turning on for download mode. Sounds like what you've experienced.
Other than that, I'm sorry but I don't see a question there.
Development will only come for the device if developers get interested in it. If none of the developers on xda have it then no-one will do anything for it.
If you're requesting a forum for the specific device, then there's a thread for that, which is obviously the best place to make the request so it gets seen and heard...
http://forum.xda-developers.com/showthread.php?t=1416406
If you've got any specific questions about the device then it's always worth asking, despite the lack of a specific forum. There will be other members with the same device, and then there's always the fact that most things are common from device-to-device, within a common manufacturer.
Good luck
Archer said:
It just looks like you've discovered both recovery and download mode. I have an S2 and they're both standard, out of the box. With the S2 you hold the home button and volume up while turning on for recovery mode, and the home button and volume down while turning on for download mode. Sounds like what you've experienced.
Other than that, I'm sorry but I don't see a question there.
Development will only come for the device if developers get interested in it. If none of the developers on xda have it then no-one will do anything for it.
If you're requesting a forum for the specific device, then there's a thread for that, which is obviously the best place to make the request so it gets seen and heard...
http://forum.xda-developers.com/showthread.php?t=1416406
If you've got any specific questions about the device then it's always worth asking, despite the lack of a specific forum. There will be other members with the same device, and then there's always the fact that most things are common from device-to-device, within a common manufacturer.
Good luck
Click to expand...
Click to collapse
Oh, I forgot to mention, there is also a separate recovery mode. Similar to what you normally find on a stock Galaxy S phone. It is reached by holding both Vol-up/down and power. Same as Galaxy S devices.
I did not know that there was a request thread, so thanks for the link.
Also, Myself, and other members have asked quite a few questions about the device, like ways to root. All have been ignored. I'm not one to complain, but you would think someone would at least say that they don't know, or something. lol
I was thinking the same thing. Seems to be no way to root this phone and worse... no developers have said why it can't or can be done. Its like this phone doesn't exist :-(
Sent from my SCH-I110 using Tapatalk 2
I think it is a great little phone, but it would be so much better with at least root on it. Also, from my investigating, the development potential for ROM's would be really awesome.
A variant of this phone called the Samsung Vibrant (720C ?) is being offer for sale us by American Movil / Walmart Straight Talk MVNO (for VZW network). I wonder when someone will be figure out how to root it .
I thinkt he straight talk version of this is called the Proclaim (s720c)
Would also love to spark some interest in the root of this device. others have stated the oneclick root for all samsung devices but seems the problem is getting an unsecure kernel?
It is wonderful ¡¡¡
I think I found the oxm pads and believe that this phone has potential for the unbrickable mod as well. It has 2 different download modes and the regular recovery mode. There is some real potential on this device. If I had the skill and time, I would be more than happy to try to find root. But unfortunately, that is impossible for me. Is there a dev that is willing to look into root for this?
I want to root when I get this, I don't wanna downgrade from my dual core Tegra 2 beast but I have to.... prepaid verizon is better coverage than us cellular.... but verizon plan I would have to pay 400 down I can't afford so prepaid I go
moparfreak426 said:
I want to root when I get this, I don't wanna downgrade from my dual core Tegra 2 beast but I have to.... prepaid verizon is better coverage than us cellular.... but verizon plan I would have to pay 400 down I can't afford so prepaid I go
Click to expand...
Click to collapse
Go here http://forum.xda-developers.com/showthread.php?t=1392090&page=4
jcmarx said:
I am also interested in any progress on this phone.
I have the straight talk version S720C Samsung Proclaim which runs on Verizon service.
I assume that once a root for the paid Verizion is working that it should work as well on the Proclaim
Click to expand...
Click to collapse
wait a minute. a straight talk smartphone that uses verizon towers? I thought they all used sprint (cdma) or at&t(gsm)......
Sent from my Motorola Electrify using XDA
It's brand new... And awesome! (for those of us in the boonies at least) Going to replace my wife's feature phone... Will wait to see if it ever gets root for a technophile like me (or perhaps a better phone down the road)
Sent from my HTC Desire CDMA using Tapatalk
a shot in the dark
I believe I could root it if i could find a set of kernels... using ODIN and then S2root?
anyway, once able to root so I can free wifi tether I will get this device since there are no longer any other verizon smartphones available and you can not put old ones on the only prepaid smartphone plan now:-/.... sucks. then ics rom! what kind of processor duress thus device have? I know its not dual core tegra 2 like my current phone which sucks but...
Sent from my Motorola Electrify using XDA
krs2012 said:
I believe I could root it if i could find a set of kernels... using ODIN and then S2root?
Click to expand...
Click to collapse
lol the irony is in order to get a booting kernel.. you have to have root
krs2012 said:
I believe I could root it if i could find a set of kernels... using ODIN and then S2root?
Click to expand...
Click to collapse
is that all you need??? You do realise you NEED ROOT for that??? lmao
shabbypenguin said:
lol the irony is in order to get a booting kernel.. you have to have root
Click to expand...
Click to collapse
lmmfao
at least since its Samsung, it distant have a locked down so you can't do anything bootloader, right?
Sent from my Motorola Electrify using XDA
right, which is how we have been flashign kernels to root it.
LG can kiss my ass. After over 2 hours of trying to upgrade the damn baseband the tool still keeps messing up. This is insane. They should have gotten it right the first time. I'm done with LG. Notice the time lapse of my second attempt to upgrade this ****. ICS is more stable on my htc hd2. I'm pretty sure I'm now soft bricked. Good luck to the rest of you dealing with this nightmare of a phone. I'll be using my hd2 till I order a galaxy nexus. Also if you know what the problem could be please let me know. I have all of the drivers and its a brand new windows 7 pc I'm using.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Did you reboot both items and make sure you follow directions to the "T" in the threads for this stuff. Also look into other ways. And finally this didn't need its own thread lol, but I understand the need to vent, again read through the threads and you'll see people having your issue and then you'll probably find your solution. Also make sure you are bone stock recovery and all I can't remember if that was a problem or not for some.
Sent from my LG-P999 using xda premium
You could try the kdz app. Also upgrading the bb breajs bluetooth in every rom except stock. I actually upgraded mine and ended up down grading with kdz. New bb is only good if you stay stock or dont need bluetooth calling at all.
I know i was just curious to see how much it would improve the device. I know its only for gps but i was just curious. Anyway, ill look into flashing cwm tomorrow and just keeping the july baseband. I was just pissed because there is only so many errors a person can take before they vent. Thanks guys. I noticed that the ics roms are solvong data drops. Hopefully it becomes more useful to me.
zachpozniak said:
I know i was just curious to see how much it would improve the device. I know its only for gps but i was just curious. Anyway, ill look into flashing cwm tomorrow and just keeping the july baseband. I was just pissed because there is only so many errors a person can take before they vent. Thanks guys. I noticed that the ics roms are solvong data drops. Hopefully it becomes more useful to me.
Click to expand...
Click to collapse
Dont let it fool you, the new bb doesnt help gps, it still sucks. The only improvement it gave is that i was told i sounded louder to someone on the other end than i did on the old bb.
The newer bb also breaks bluetooth unless they fixed that. I'd stay away from the newer bb (maybe that's only on the ICS roms).
But I 100% agree with you, this phone should've been recalled. It would've been 1000x better for LG to cut their losses and recall the phone than to ruin their entire image for themselves. See you on the other side of this P.O.S. Goodluck!
Also disable any firewalls/antivirus. I was having similar trouble until I disabled everything.
Thanks. Yeah it sucks because this phone has a lot of potential but ****ty support. Maybe ill try disabling it and going for one more try. But i think im just gonna stick with the old baseband.
New bb is good in my opinion, but not really worth changing. To much risk for a phone that will eventually have little support, but the devs we do have are awesome and they support the new bb. Love my g2x,but can't wait to upgrade.
Sent from my LG-P999
I got my G2x the day it was released. I was so excited... All went down hill from there. I appreciate all the devs that worked on our phones, but today I ordered a nexus. I just can't take it anymore.
Sent from my LG-P999 using xda app-developers app
Are you on a stock rom?
Blazing angel said:
Are you on a stock rom?
Click to expand...
Click to collapse
If you are asking me, no. I have tried them all. I'm currently on CM7, it's the best on my phone. It still had lots of issues though.
Sent from my LG-P999 using xda app-developers app
I think it's about time for me to move on from the G2X. Too many problems still after all this time. Maybe the SGS3 will suit me better.
Sent from the nether regions of the black abyss under the battery of a G2X.
jnralp00 said:
If you are asking me, no. I have tried them all. I'm currently on CM7, it's the best on my phone. It still had lots of issues though.
Click to expand...
Click to collapse
CM7.2 was a nice little update.. until I overslept for work because my phone had another SOD. I noticed if I leave my Wifi or bluetooth on- it will sometimes SOD... i just have to make sure i turn those two radios off... its only happen 3 time since I updated about a month ago(?). maybe i'll go back to 7.1... i just hate reinstalling the apps even with Titanium backup..
AchilliesOmega3 said:
CM7.2 was a nice little update.. until I overslept for work because my phone had another SOD. I noticed if I leave my Wifi or bluetooth on- it will sometimes SOD... i just have to make sure i turn those two radios off... its only happen 3 time since I updated about a month ago(?). maybe i'll go back to 7.1... i just hate reinstalling the apps even with Titanium backup..
Click to expand...
Click to collapse
Must be some app you are running
Sent from my LG-P999 using xda premium
Nvdia too
The biggest barrier, IMO, is Nvidia's refusal to release driver code or binaries to support the chipset that runs our phone's graphics. I for one am not buying Nvidia's stuff again.
gpmartinson said:
The biggest barrier, IMO, is Nvidia's refusal to release driver code or binaries to support the chipset that runs our phone's graphics. I for one am not buying Nvidia's stuff again.
Click to expand...
Click to collapse
i said that too until i bought my Xoom a few days ago LOL
to the OP - do you have the stock recovery and stock firmware on your phone? if so have you tried the OTA update? this is how i did it
http://forum.xda-developers.com/showthread.php?t=1696266
After three-four days of usage I noticed considerable flicker on the screen.
I have tried factory resetting, turning off auto-brightness, turning off wifi. But nothing worked.
After some googling I have come to know that this is very frequent issue on nexus 5. There is huge number of threads online discussing the same. Below are some:
https://code.google.com/p/android/issues/detail?id=36417
https://productforums.google.com/forum/#!topic/nexus/o_Hj782Y_aY
http://www.reddit.com/r/Nexus5/comments/2448ws/weird_screen_flickering/
http://forum.xda-developers.com/google-nexus-5/help/screen-flicker-t2525881
http://androidforums.com/nexus-5/841381-nexus-5-screen-problem.html
http://community.koodomobile.com/koodo/topics/my_new_nexus_5_screen_keeps_flickering
http://bragnews.com/nexus-5-flickering-screen-fix/
In fact a user comment "#26 ndend.. @gmail.com" on below thread says that he got nexus 5 replaced 5 to 6th time for similar sounding issue:
https://code.google.com/p/android/issues/detail?id=36417
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I prepared a youtube video of my Nexus 5. Here is what is happening with me:
After more googling I came to know that google and LG has made some redesign of Nexus 5 to fix hardware issues, though silently:
http://www.fonearena.com/blog/90868...-issues-with-nexus-5-with-minor-redesign.html
So I believe both Google and LG knows that Nexus 5 has got some faulty design, but not just putting it straight to media but silently pushing the update in new devices.
In fact Google is replacing older Nexus 5 if you screw its screen, surprisingly by suddenly changing its accidental damage protection policy:
http://techcrunch.com/2014/09/03/ye...-replace-your-nexus-5-if-you-bust-the-screen/
Also some sites went on listing some mostly reported issues with Nexus 5:
http://au.ibtimes.com/articles/524834/20131125/lg-nexus-5-top-10-encountered-issues.htm#.VAm5MPldWb8
http://www.digitaltrends.com/mobile/nexus-5-problems/#!bP8d5j
Now I can feel that this is because Google want to take back some old design bad Nexus 5 back.
Am not at all a designer or electronics professional but from what I can read from this is that there is something wrong with the design of Nexus 5, something is definitely failing its screen stability, either a hardware issue or driver incompatibility.
I wish I could have realized this earlier before buying one.
Now I am in confusion whether to ask for replacement or refund, since I cant find any other flagship running stock android. The only one - Nexus 5 running stock android has these many issues. Is there any other? My requirements are 5"screen, 2 GB RAM, Quad Core Processor.
just get a replacement, got 3 N5 since release without that problem.
or get a refund and wait for newer nexus, if there are one
p.s. G3 is also a good choice if you don't mind.
DummyPLUG said:
just get a replacement, got 3 N5 since release without that problem.
or get a refund and wait for newer nexus, if there are one
Click to expand...
Click to collapse
without "that" problem..means you had different ones? And 3 different or in replacement you got 3rd one?
if you want, by also googling, you can find that aliens have taken over the earth.
i dont have sich issues with my n5, and the majority dont as well. some of the issues are even non issues. only a very small % actually see real issues. you can find info like this for any product. no device is perfect.
DummyPLUG said:
p.s. G3 is also a good choice if you don't mind.
Click to expand...
Click to collapse
Does G3 runs stock android?? Will it get quick updates in future and dont want get into rooting and custom ROMs.
Also Moto G do also get updates right? It also runs stock android?
Mahesha999 said:
without "that" problem..means you had different ones? And 3 different or in replacement you got 3rd one?
Click to expand...
Click to collapse
I mean I have 3 Nexus 5, all of them don't have any screen issue.
---------- Post added at 05:12 AM ---------- Previous post was at 05:08 AM ----------
Mahesha999 said:
without "that" problem..means you had different ones? And 3 different or in replacement you got 3rd one?
Click to expand...
Click to collapse
Mahesha999 said:
Does G3 runs stock android?? Will it get quick updates in future and dont want get into rooting and custom ROMs.
Also Moto G do also get updates right? It also runs stock android?
Click to expand...
Click to collapse
what you mean "stock android" ? if you refer to something like google play edition or AOSP, then no. I don't know the future, but every device will stop updating someday, include nexus.
and sorry, dunno anything about the Moto G.
Mahesha999 said:
In fact a user comment "#26 ndend.. @gmail.com" on below thread says that he got nexus 5 replaced 5 to 6th time for similar sounding issue:
https://code.google.com/p/android/issues/detail?id=36417
Click to expand...
Click to collapse
That's a complaint about the Nexus 7.
Wakamatsu said:
That's a complaint about the Nexus 7.
Click to expand...
Click to collapse
jeez, its even the old nexus 7. look at the date, 11/17/2012.
Huh, it's been 10 months or so and I've never seen a flicker on mine.
Some are just plain faulty, get it replaced and hope that the replacement works well!
Sent from my Nexus 5 using Tapatalk
Every mass produced product is going to have some defective units. Even with good QC, they cannot test every single unit thoroughly, it is impractical and would end mass production.
If you want something that will be thoroughly checked over to make sure there are no issues, you will have to pay a company to make a device just for you. That wont be cheap, your couple hundred dollar smartphone just into a couple hundred million dollar smartphone.
Thankfully, when there are genuine defects most companies take responsibility and give you a new one (though again, this will not be perfect with mass production). Companies will have different policies. Also, service reps, technicians, and the myriad of others involved in the transaction will vary (in competence, attitude, etc.).
But, if you have a screen flicker on this phone I do not see why a claim would be denied.