Related
Just throwing it out there. As the title states. I attempted the S-off, failed a couple of times, more than likely due to my timing on the wire trick. Then my computer was unable to find device anymore. Long story short, I got my rom to reboot, however the phone will not connect to computer or charge. Tried Pc, Mac, different usb cords. Wiped, reinstalled rom, pulled battery, etc..
This is a risk that I took, and I take full responsibility for that. But just beware that this could affect your hardware and not just your software too, which makes sense because you are messing with the hardware. I am def in the minority here, but I thought I would share. But something to think about. The phone now still functions but I have to take out the battery to charge, and I can't push any files to the phone.
ive never heard of anyone's usb port getting fried with the s-off method but i guess it's possible since your basically grounding your device out.
I know it won't help you with fastboot, but you can still do ADB over wireless. Look for instructions on how to enable it via terminal, or just go the the store and find a widget or app to enable it. At least with functional ADB, you can still push files to your phone using wifi tether or if they are on the same wireless network.
Someone else had the same issue and is testing a possible fix for me. If it works ill post a thread but there is a good chance it is dead.
con247 said:
Someone else had the same issue and is testing a possible fix for me. If it works ill post a thread but there is a good chance it is dead.
Click to expand...
Click to collapse
do you think the wire trick is causing this? if soo that's kinda scary.
fix-this! said:
do you think the wire trick is causing this? if soo that's kinda scary.
Click to expand...
Click to collapse
I had the exact same thing happen to me on my original Rezound, while I was doing all sorts of fastboot stuff to completely wipe it and prepare it to be shipped back to Verizon. In the end, it shipped back to them in a state where it would ONLY boot to hboot, because it had no /boot or /system or /data or /recovery partitions or anything. I don't really know what happened, but before I could run the RUU to complete the job, the USB connection just stopped working and it wouldn't charge. Exactly the same situation, except it was on its way back to Verizon anyway with a dead screen so I didn't bother to investigate any further.
To the people who have had the problem, were you using an uninsulated wire?
tekhna said:
To the people who have had the problem, were you using an uninsulated wire?
Click to expand...
Click to collapse
Or else inadvertantly touched the wrong terminals ? Just trying to figure out how it could happen.
lack of usb function was a product of a corrupted misc image on the HTC Desire. It is possible the same thing happened here so that is being tested. It is worth looking into as a last resort before sending it back.
Yes I was using an insulated wire. I placed the wire exactly where the pictures show. I'm really not sure what happened. But at least I have a backup phone.
Sent from my Galaxy Nexus using XDA
con247 said:
Someone else had the same issue and is testing a possible fix for me. If it works ill post a thread but there is a good chance it is dead.
Click to expand...
Click to collapse
Thanks con
Sent from my Galaxy Nexus using XDA
Knew I didn't wanna do it.
Sent from my ADR6425LVW using xda premium
http://forum.xda-developers.com/showthread.php?t=1620803
Here's a case of fried USB but no s-off. Currently unlocked. Any ideas?
Snuzzo said:
http://forum.xda-developers.com/showthread.php?t=1620803
Here's a case of fried USB but no s-off. Currently unlocked. Any ideas?
Click to expand...
Click to collapse
Sounds like he is in the exact same boat as me. Will be following that thread as well.. Thanks.
Me three
In same Boat.
Please post a cure if you find one.
Another nice option for transferring files is SSHDroidPro used with something like WinSCP.
I know you tried wiping your rom, but did you try an RUU? On the off chance it is a corrupted partition that might be able to fix it. Worth a try anyway.
I was performing a nandroid backup when then the progress line stopped. I let it sit for over 4 hours and the line did not move. The phone was locked up. I took the battery out to reset the phone and now it will not turn on. I tired several different key comobs, including volume up+down and power, with no efffect. When I plug it in it does nothing. I was using ISCrewD with the Siyah kernal now for a couples months with no issues. That was actually the only custom rom I ever flashed to the phone, loved the rom. From reading the forums, it seems I am hard bricked. How did that happen? Any suggestions?
Do you remember what version of Siyah you were using? I read recently that 3.1RC6 had a major bug in it that was hard bricking people's phones.
Version 2.6.13.
OP, you must have done something weird (or power loss) during the backup as there is no way nandroid backup in CwM causing hardbricking.
jojo, that version of Siyah was for ICS, the OP ran GB.
votinh said:
OP, you must have done something weird (or power loss) during the backup as there is no way nandroid backup in CwM causing hardbricking.
jojo, that version of Siyah was for ICS, the OP ran GB.
Click to expand...
Click to collapse
no, it's for GB, just checked G's site. However, there are 4 download entries, one of which is the Korean based (possible bricker). What's more, G could've rebased the ATT version from the Korean... I'd be amazed if, after all the bricking going on, he'd still have a download for it. Weird.
Galaxy_Cat said:
no, it's for GB, just checked G's site. However, there are 4 download entries, one of which is the Korean based (possible bricker). What's more, G could've rebased the ATT version from the Korean... I'd be amazed if, after all the bricking going on, he'd still have a download for it. Weird.
Click to expand...
Click to collapse
For real? Siyah 3.1.rc6 is for GB?
You were doing a nandroid backup, not a restore, and on gingerbread, so it's hard to say what caused the problem. I don't believe I've seen any report exactly like yours.
You tried several button combinations, including recovery mode, which did not work, but did you try to get into download mode? First try to enter download mode with the battery in -- hold vol+ and vol- (but not pwr) and then plug in the usb cable. If no success with that, pull the battery and do the exact same sequence to enter download mode. The usb cable will provide the power. Sometimes there is a problem with the battery. If you can get download mode, you're not bricked.
votinh said:
For real? Siyah 3.1.rc6 is for GB?
Click to expand...
Click to collapse
what are you talking about? Read OP response.
votinh said:
OP, you must have done something weird (or power loss) during the backup as there is no way nandroid backup in CwM causing hardbricking.
jojo, that version of Siyah was for ICS, the OP ran GB.
Click to expand...
Click to collapse
My bad. I've only had this phone for a week and never used that ROM...just assumed it was ICS based on the name.
Galaxy_Cat said:
what are you talking about? Read OP response.
Click to expand...
Click to collapse
People on the net are freaking confusing me.
What the heck you are talking about? OP response of what?
Were you misquote/misread/misunderstand what I said?
I said to member "jojo" above when he mentioned the Siyah 3.1rc6.
Are we in the same page? I guess not.
---------- Post added at 05:12 PM ---------- Previous post was at 05:10 PM ----------
Here's what jojo said: "Do you remember what version of Siyah you were using? I read recently that 3.1RC6 had a major bug in it that was hard bricking people's phones."
ENTER
ENTER
ENTER
And that was my response to him.
Were you the dude misread my post earlier???
votinh said:
People on the net are freaking confusing me.
What the heck you are talking about? OP response of what?
Were you misquote/misread/misunderstand what I said?
I said to member "jojo" above when he mentioned the Siyah 3.1rc6.
Are we in the same page? I guess not.
---------- Post added at 05:12 PM ---------- Previous post was at 05:10 PM ----------
Here's what jojo said: "Do you remember what version of Siyah you were using? I read recently that 3.1RC6 had a major bug in it that was hard bricking people's phones."
ENTER
ENTER
ENTER
And that was my response to him.
Were you the dude misread my post earlier???
Click to expand...
Click to collapse
I misread you (had to reread this thread three times to get it straight!) sorry for confusion.
It is a GB rom/kernal...
I tried, as said above, to hold down vol up and down, then insert the usb cable, no go with or without the battery in. My wife has the same phone, so I tried her battery and no go, then put my battery in hers and all was fine. So battery seems ok. I have played around a good bit with it this evening, and read a good bit in the forums...all points to hard bricked. I have no idea how it happened, I have seen no others (at least from my seraches) have this problem with nandroid backup. For that matter I have used it before with this rom/kernal and no issue. Warranty is still good on it, guess I will try and get it exchanged, hopefully they don't get it to boot up with a custom rom on it. No way for me to restore it back to stock of course.
gandalf21502 said:
It is a GB rom/kernal...
I tried, as said above, to hold down vol up and down, then insert the usb cable, no go with or without the battery in. My wife has the same phone, so I tried her battery and no go, then put my battery in hers and all was fine. So battery seems ok. I have played around a good bit with it this evening, and read a good bit in the forums...all points to hard bricked. I have no idea how it happened, I have seen no others (at least from my seraches) have this problem with nandroid backup. For that matter I have used it before with this rom/kernal and no issue. Warranty is still good on it, guess I will try and get it exchanged, hopefully they don't get it to boot up with a custom rom on it. No way for me to restore it back to stock of course.
Click to expand...
Click to collapse
You need the USB dongle to force it to
Go in download mode.
Sent from my GT-N7000 using XDA
From what I have read, that will only work if you get 'some' response when turning it on. I get nothing, so the dongle will not work?
I called AT&T this morning, I can get a refurbished one to replace mine, guess I will go that route....
gandalf21502 said:
From what I have read, that will only work if you get 'some' response when turning it on. I get nothing, so the dongle will not work?
Click to expand...
Click to collapse
So just because it might not work, you're not going to try it? Try it!
Well...why not! I found one on Ebay for under $10 shipped, so it's on the way...
gandalf21502 said:
Well...why not! I found one on Ebay for under $10 shipped, so it's on the way...
Click to expand...
Click to collapse
Just to be clear, when we say USB dongle, we're not taking about a USB jig...we're talking about the USB-to-MicroUSB data cable that came with the phone.
I have already tried the micro usb cable that came with the phone and tried to get Odin to see the phone, no go. I ordered a Jig to see if it would force the phone into download mode...
Got my USB Jig today. Took the battery out (even tried wifes 'good' battery). Put the battery in, then the Jig...nothing. I would assume the phone has some form of hardware failure...guess time to get ahold of AT&T and get a warranty exchange.
AT&T is sending a 'refurb' phone today...should be here soon...hopefully they don't get my phone to work and see the custom kernal/rom...No matter what I try, it just won't come on.
I did do a quick search, but didn't find anything
I'm s-on running ViperRez 1.0.3 I put that on after the global RUU screwed everything up horribly. I was still having issues with overheating, but the guy at the Verizon store said they weren't exchanging any rezounds because they were still working out bugs. So, I decided to wait until it was cooler out to see if I was still having the issues, and they've only been getting worse. Anyhow, I want to take it back to as stock as I can to try exchanging it. I'm just really afraid of bricking it, since after a post on another forum about the issues I've been having.
Can someone give me the right steps, in order; or even be willing to walk me through it? When I flashed ViperRez, I had somebody from here help me out on google talk, that was really helpful.
Thanx,
Justin
VooDooCC said:
I did do a quick search, but didn't find anything
I'm s-on running ViperRez 1.0.3 I put that on after the global RUU screwed everything up horribly. I was still having issues with overheating, but the guy at the Verizon store said they weren't exchanging any rezounds because they were still working out bugs. So, I decided to wait until it was cooler out to see if I was still having the issues, and they've only been getting worse. Anyhow, I want to take it back to as stock as I can to try exchanging it. I'm just really afraid of bricking it, since after a post on another forum about the issues I've been having.
Can someone give me the right steps, in order; or even be willing to walk me through it? When I flashed ViperRez, I had somebody from here help me out on google talk, that was really helpful.
Thanx,
Justin
Click to expand...
Click to collapse
All you need to do is download the last factory ruu from android police or this site and run it like you did the global.
Here is the link to the official
https://rapidshare.com/files/2153199604/rezound_AndroidPolice_3.14.605.12_PH98IMG.zip
from my Rezound using Tapatalk 2
---------- Post added at 12:51 PM ---------- Previous post was at 12:43 PM ----------
Guess, I am not sure if you ran the Ruu successfully.. download file from previous post . Place on your Sd card. Make sure you relock phone if unlocked, if you HTC dev unlocked you should know how to relock.
Rename file on Sd card to PH98IMG.zip, just delete the androidpolice heading is the easiest. Boot to bootloader and press power button, it will start parsing the Ruu and ask if you want to update.
Press volume up to say yes ,then let it run. It will take awhile and run twice. It should then reboot and your back to factory
Just thought of something...if you did upgrade to the global Ruu..can't downgrade unless S-off...
Sent from my Rezound using Tapatalk 2
Thank you for that link. I thought I read somewhere about making sure to relock the bootloader or the phone will brick.
VooDooCC said:
Thank you for that link. I thought I read somewhere about making sure to relock the bootloader or the phone will brick.
Click to expand...
Click to collapse
Won't brick it just won't run the Ruu, hope it works for you !
Sent from my ADR6425LVW using Tapatalk 2
This may be kind of pathetic, but I've been racking my brain, and can not remember how to relock it. I'll have to search around.
My phone isn't charged enough to try it right now anyway. Needed to use it to record a school project for my wife. I plugged it in, turned on the camcorder and after about 2 hours, it went from being fully charged to 19% Awesome!!
VooDooCC said:
This may be kind of pathetic, but I've been racking my brain, and can not remember how to relock it. I'll have to search around.
My phone isn't charged enough to try it right now anyway. Needed to use it to record a school project for my wife. I plugged it in, turned on the camcorder and after about 2 hours, it went from being fully charged to 19% Awesome!!
Click to expand...
Click to collapse
First off bro.. you won't be able to brick that phone s-off. I assume its possible but I haven't heard of it happening. So don't worry about that.
The command for relocking is
fastboot oem lock
Granted.. you must have the android SDK installed and have a basic understanding of fastboot
Sent from my ADR6425LVW using Tapatalk 2
I think I messed up somewhere along the line. Who wants to save me. I assumed the link provided a few posts back was the same file as what I had already downloaded sometime back. Which I have saved on my computer in a folder I labeled .2 RUU so...
I copied that to the sd card
relocked the bootloader
let it do it's thing
hit <VOL UP> to start the update
It went through everything and booted to the bootloader again, so I'm trying the update one more time.
PLEASE HELP
EDIT: Just had to flash it a couple of times
VooDooCC said:
I think I messed up somewhere along the line. Who wants to save me. I assumed the link provided a few posts back was the same file as what I had already downloaded sometime back. Which I have saved on my computer in a folder I labeled .2 RUU so...
I copied that to the sd card
relocked the bootloader
let it do it's thing
hit <VOL UP> to start the update
It went through everything and booted to the bootloader again, so I'm trying the update one more time.
PLEASE HELP
Click to expand...
Click to collapse
Pull battery and then put it back in and see if it boots, otherwise use the link I provided and run that Ruu . No reason that a proper Ruu shouldn't run .
Sent from my ADR6425LVW using Tapatalk 2
Felt like updating this...
Got it back to stock, went to Verizon, got a replacement phone shipped out. That phone got here today, still having all the old problems, plus more. The really awesome thing is, the screen isn't even solid on this one. It's raised on all sides and I can press it down, slowly comes back up over about 2 minutes. Going to Verizon again tomorrow to see what to do this time. I haven't shipped my old one back yet, as it just came in today.
Did they send you a new battery with the phone?
Have you rooted the replacement yet?
Sent from my ADR6425LVW using xda premium
VooDooCC said:
Felt like updating this...
Got it back to stock, went to Verizon, got a replacement phone shipped out. That phone got here today, still having all the old problems, plus more. The really awesome thing is, the screen isn't even solid on this one. It's raised on all sides and I can press it down, slowly comes back up over about 2 minutes. Going to Verizon again tomorrow to see what to do this time. I haven't shipped my old one back yet, as it just came in today.
Click to expand...
Click to collapse
Had the screen lift issue on my first replacement. My second replacement was better...the screen wasn't lifting, but it wasn't solid feeling either. The USB port on that one died, and on this one, the screen is great.
No battery, they said to come back in if I'm still having the heat issues. Haven't rooted the new one yet, as I'm wanting to get it replaced because of the screen issue.
first i am new and dont know a lot about software/android
i used this guide to try to flash the liquid jelly bean
androidauthority.com/galaxy-note-i717-android-4-1-1-liquid-jelly-bean-custom-rom-114126/
since the ROM download link wasnt working i downloaded it from here
android.gs/install-liquidsmooth-custom-rom-on-att-samsung-galaxy-note-i717-android-4-1-2-jelly-bean/
in the first link i followed the steps BUT forgot to do a clean/wipe the factory data
now after the flashing completed i hit reboot now and waited 6min than i tried to hold down the power button and nothing. took out battery and try to restart but nothing
how do i go back to either the reflashing or to my old ICS flashed version (using tmobile sim with forced 4g)?
My battery was full and every time i try to plug it to my pc it keeps telling me to format the sd/internal storage.
Pull battery and put back
Hold power and both volume buttons
At Samsung screen, release ONLY power
Keep holding volume, recovery will come up
Wipe data/factory reset.
Wipe cache partition
While you're at it, go to Mounts and storage - Format system
Reinstall ROM
Sent from my SAMSUNG-SGH-I717 using xda premium
---------- Post added at 03:09 PM ---------- Previous post was at 03:07 PM ----------
Added step: Pray its not bricked. Liquid likes to turn phones into good looking paper weights.
Sent from my SAMSUNG-SGH-I717 using xda premium
no response from the phone expect when i connect to pc it keep telling me to format the internal storage.
what options do i have to fix this
The phone is likely bricked ...
The link you used is likely the same one another user tried yesterday.
It's not an I717 rom....it's actually a GS3 rom, and when flashed, instantly bricks the device.
You likely need a JTAG repair on the device, as it is hard bricked with no download mode.
Very sorry, it's a bad deal...but users "must" verify rom sources before flashing...
The link you used has bricked your device....g
Someone needs to report to the writer that they're referring people to an incorrect ROM. Granted its not their fault but damn. People do whatever the internet tells them to and we already have enough "bricked" threads.
Sent from my SAMSUNG-SGH-I717 using xda premium
so just one thing
should i try the usb download mode dongle thing first or try the JTAG service and are which ones on AMAZON are compatible with att note
Concerning this issue, there is room for improvement by devs and users both.
I have to say many of the liquid items are not organized well. After so many issues due to this you would think at some point they would be cleaned up. Also while I agree folks should confirm they have the correct rom,files,etc before flashing, it takes verry little to add safeguards to a rom making it device specific so it will not flash to an unintended device.
Just my two pennies.
Sent from my SAMSUNG-SGH-I717 using xda premium
savan1221 said:
so just one thing
should i try the usb download mode dongle thing first or try the JTAG service and are which ones on AMAZON are compatible with att note
Click to expand...
Click to collapse
Sorry but your phone is history. Get $50 and send it to the JTAG guy. www.mobiletechvideo.com
rangercaptain said:
Sorry but your phone is history. Get $50 and send it to the JTAG guy. www.mobiletechvideo.com
Click to expand...
Click to collapse
Agreed....
Very sorry, but it's toast until a JTAG restore is performed.....
And I agree with the above poster that the liquid links are a mess...
This is the second brick in a day I'm aware of, and I'm looking into reporting the faulty rom.....g
---------- Post added at 06:25 PM ---------- Previous post was at 06:23 PM ----------
joe3681 said:
Someone needs to report to the writer that they're referring people to an incorrect ROM. Granted its not their fault but damn. People do whatever the internet tells them to and we already have enough "bricked" threads.
Sent from my SAMSUNG-SGH-I717 using xda premium
Click to expand...
Click to collapse
I'm in the process of that, and would appreciate the help of others sending reports also.
The mis-labeled rom is a bad damn deal.....g
---------- Post added at 06:40 PM ---------- Previous post was at 06:25 PM ----------
I've contacted the general operations team for the site offering the rom...
I've also emailed the author of the site and asked for removal of the build..
It's really all I can do from here, as the build is hosted in Romania......g
oh man today has just been a bad luck for me
bricked my note
got two different blue screen error
burned myself while trying to shape metal
i will try to ship it to the JTAG
just one more thing do i need to get the usb dongle for $6 and also do i need to get the sim unlock.
when i bough the phone i had bough a unlocked version, will i be able to do that myself or since he is restoring it, it will need to be redone
No parts needed, and you'll likely need to unlock again..
Good luck with the note repair, and I'm sorry your day has sucked so badly.
It'll get better ...g
rangercaptain said:
Sorry but your phone is history. Get $50 and send it to the JTAG guy. www.mobiletechvideo.com
Click to expand...
Click to collapse
that link above is not valid ( unclaimed domain ?) ... closed ..
See goattamers link ..g
That link is wrong. The correct link is www.mobiletechvideos.com
bummer, sorry to hear about your phone.....seems like your best bet is jtag. check this out - http://mobiletechvideos.mybigcommerce.com/samsung-galaxy-note-jtag-brick-repair/
savan1221 said:
first i am new and dont know a lot about software/android
i used this guide to try to flash the liquid jelly bean
androidauthority.com/galaxy-note-i717-android-4-1-1-liquid-jelly-bean-custom-rom-114126/
since the ROM download link wasnt working i downloaded it from here
android.gs/install-liquidsmooth-custom-rom-on-att-samsung-galaxy-note-i717-android-4-1-2-jelly-bean/
in the first link i followed the steps BUT forgot to do a clean/wipe the factory data
now after the flashing completed i hit reboot now and waited 6min than i tried to hold down the power button and nothing. took out battery and try to restart but nothing
how do i go back to either the reflashing or to my old ICS flashed version (using tmobile sim with forced 4g)?
My battery was full and every time i try to plug it to my pc it keeps telling me to format the sd/internal storage.
Click to expand...
Click to collapse
I recently just went through the same exact thing, downloaded the same link and BOOM.......nice paper weight! But since my phone is from AT&T and I am in my first year, i just took it to the service center and they replaced it without asking any questions. Not sure where you live , but try the service center, not saying it's a guarantee, but maybe , just maybe, you'll get lucky
jrea77 said:
bummer, sorry to hear about your phone.....seems like your best bet is jtag. check this out - http://mobiletechvideos.mybigcommerce.com/samsung-galaxy-note-jtag-brick-repair/
Click to expand...
Click to collapse
So many URLs....so little time ....
This "is" the right one now ....g
---------- Post added at 05:06 PM ---------- Previous post was at 05:05 PM ----------
Agoattamer said:
That link is wrong. The correct link is www.mobiletechvideos.com
Click to expand...
Click to collapse
yup ....you got it ..
Thanks GT ....g
Sucks these things happen during the holidays.
. . . Or any time. But "things" didn't go wrong, although that is the first time I heard of a bad link.
TechGoon954 said:
I recently just went through the same exact thing, downloaded the same link and BOOM.......nice paper weight! But since my phone is from AT&T and I am in my first year, i just took it to the service center and they replaced it without asking any questions. Not sure where you live , but try the service center, not saying it's a guarantee, but maybe , just maybe, you'll get lucky
Click to expand...
Click to collapse
And what you did here and what you are recommending is fraud. You voided the warranty when you rooted it and flashed a custom rom to it. I wouldn't say you got lucky I would say you cheated the system
Have to RMA my hdx 7".. the light bleed is just insane, like 1/2" of blue around the sides of the screen.
Anyway... it has safestrap installed with 2 slots setup.. Could someone give me a quick rundown on the safe way to restore this to 100% stock? I did a quick search but fail at search. thank you
Icetech3 said:
Have to RMA my hdx 7".. the light bleed is just insane, like 1/2" of blue around the sides of the screen.
Anyway... it has safestrap installed with 2 slots setup.. Could someone give me a quick rundown on the safe way to restore this to 100% stock? I did a quick search but fail at search. thank you
Click to expand...
Click to collapse
I was dealing with a similar situation. Here are the steps to restore it to 100% stock.
I am not sure if you would need to delete manually the ROM slot you created first, but I assume not. I did, just to be safe. It might be my OCD though.
---------- Post added at 02:38 PM ---------- Previous post was at 02:23 PM ----------
Icetech3 said:
Have to RMA my hdx 7".. the light bleed is just insane, like 1/2" of blue around the sides of the screen.
Click to expand...
Click to collapse
Oh, I forgot to ask. Any chance that you could post a picture of your screen that shows the bleeding? I would like to compare it to mine. I have it too, but I am not sure if it's worth the trouble going through the replacement as many people report that their second or third replacement has it too. I wanna see how bad it yours.
Kindlik said:
I was dealing with a similar situation. Here are the steps to restore it to 100% stock.
I am not sure if you would need to delete manually the ROM slot you created first, but I assume not. I did, just to be safe. It might be my OCD though.
---------- Post added at 02:38 PM ---------- Previous post was at 02:23 PM ----------
Oh, I forgot to ask. Any chance that you could post a picture of your screen that shows the bleeding? I would like to compare it to mine. I have it too, but I am not sure if it's worth the trouble going through the replacement as many people report that their second or third replacement has it too. I wanna see how bad it yours.
Click to expand...
Click to collapse
Thanks.. will try it today, sorry for the late response.. busy weekend...
Ended up just going into recovery, deleting my slot2 which had the modified OS.. booted to slot 1 which was stock. remove Safestrap, did a refresh to wipe user data.. and back to amazon it goes
Icetech3 said:
Thanks.. will try it today, sorry for the late response.. busy weekend...
Ended up just going into recovery, deleting my slot2 which had the modified OS.. booted to slot 1 which was stock. remove Safestrap, did a refresh to wipe user data.. and back to amazon it goes
Click to expand...
Click to collapse
New HDX just showed up... same light bleed, must just be how they are.. I really like the devices other than the battery life is total ass.. my nexus 10 goes a week on a charge this thing wont make it 2 days on standby
Icetech3 said:
New HDX just showed up... same light bleed, must just be how they are.. I really like the devices other than the battery life is total ass.. my nexus 10 goes a week on a charge this thing wont make it 2 days on standby
Click to expand...
Click to collapse
that doesn't sound right at all. i can leave my 7" laying around for days without it dying, unless i've been using the hell out of it. i had one problem with bluetooth keeping it awake, and i turned bluetooth off and rebooted and it hasn't happened again
murso74 said:
that doesn't sound right at all. i can leave my 7" laying around for days without it dying, unless i've been using the hell out of it. i had one problem with bluetooth keeping it awake, and i turned bluetooth off and rebooted and it hasn't happened again
Click to expand...
Click to collapse
Well.. the replacement i got, all i have done is install moon reader and dropbox and a few other apps (i actually like the amazon OS once i can sideload things and get dropbox on it) And standby is 3 days.. i came in to work today it was at 4%.. so its better than my last one. but still same monster light bleed and stuff.. no big thing i don't use this much. My old nexus 10 is still the best i have used. and front speakers. mmmmm
weird..on standby mine lasts a lot longer than that