Hi, I got my Nexus 7 yesterday. Everytime I leave it in sleep mode for more than 10 minutes it shuts down and i need to hard reboot. I've read somewhere that its possibly Sleep of Death. I tried shutting wifi of during sleep, installed an auto airplane mode app, reset to factory settings about 5 times but nothing seems to help. I run stock rom, not rooted. Do you think i should return it or is there a possible sollution? Greatings
I'd return it
What build number are you in? Settings/about tablet maybe its somthing to do with JR3O0S?
Sent from my Nexus 7 using Tapatalk 2
leelaa said:
What build number are you in? Settings/about tablet maybe its somthing to do with JR3O0S?
Sent from my Nexus 7 using Tapatalk 2
Click to expand...
Click to collapse
Build number is JRO03D
Goldcell said:
Build number is JRO03D
Click to expand...
Click to collapse
I'm the same build JRO03D and I can say that mine dies sometimes after I press the power button to turn the screen off.
I've noticed it happens when I'm reading a pdf book on adobe reader and when I turn my screen off it just doesn't turn on and I have to hold it so it resets and turns on.
Is this a bad build number? The one that ends with a D?
kris4o2 said:
I'm the same build JRO03D and I can say that mine dies sometimes after I press the power button to turn the screen off.
I've noticed it happens when I'm reading a pdf book on adobe reader and when I turn my screen off it just doesn't turn on and I have to hold it so it resets and turns on.
Is this a bad build number? The one that ends with a D?
Click to expand...
Click to collapse
Are you guys using a custom rom, or stock? I am showing JRO03D (MoDaCo Custom Rom Jr7) and have no issues.. so either his rom fixed the issue of the build, or perhaps the update you received is bad?
I asked somewhere else the best way to go back to stock, a way that re-writes the partitions.. like flashing a RUU with HTC, or using Odin on Samsung.. but never got an answer. I would recommend you find a way to get back to stock firmware, then allow it to update again, or update it yourself- or get a custom rom..
And what hardware version are you on? Mine is C80.. no issues whatsoever.
Silentbtdeadly said:
Are you guys using a custom rom, or stock? I am showing JRO03D (MoDaCo Custom Rom Jr7) and have no issues.. so either his rom fixed the issue of the build, or perhaps the update you received is bad?
I asked somewhere else the best way to go back to stock, a way that re-writes the partitions.. like flashing a RUU with HTC, or using Odin on Samsung.. but never got an answer. I would recommend you find a way to get back to stock firmware, then allow it to update again, or update it yourself- or get a custom rom..
And what hardware version are you on? Mine is C80.. no issues whatsoever.
Click to expand...
Click to collapse
I'm stock. I've never used a custom ROM or rooted my devices.
Silentbtdeadly said:
Are you guys using a custom rom, or stock? I am showing JRO03D (MoDaCo Custom Rom Jr7) and have no issues.. so either his rom fixed the issue of the build, or perhaps the update you received is bad?
I asked somewhere else the best way to go back to stock, a way that re-writes the partitions.. like flashing a RUU with HTC, or using Odin on Samsung.. but never got an answer. I would recommend you find a way to get back to stock firmware, then allow it to update again, or update it yourself- or get a custom rom..
And what hardware version are you on? Mine is C80.. no issues whatsoever.
Click to expand...
Click to collapse
I'm running the stock rom from google. I don't know what hardware version I'm on. Thanks for the replies so far!
If the device is otherwise perfect and free of any defects, I might take a stab at trying to fix it by wiping it and reflashing the stock Image. If you can't get it to work you can always return it then.
Goldcell said:
I'm running the stock rom from google. I don't know what hardware version I'm on. Thanks for the replies so far!
Click to expand...
Click to collapse
The first few letters on the sticker on the back of the tablet, at the bottom, will tell you the hardware version..
And you have a choice, if you just got it and can return it, it is unlikely you will have the issue with a new one.. if you can't, you may want to figure out how to flash a stock firmware, as I have a feeling the OTA update may have went wrong. Resetting your tablet(factory reset) just deletes your /data partition, the system partition is not rewritten.. so if there was something wrong with the update in the system files, that won't help.
I am pretty damn sure it is likely kernel related, yet another option to look into.. the nook color(I used to use) has that issue, so it is sad to hear anyone hear have that issue too.
If you are willing to root, you may want to try increasing the minimum clock speed just one step, or if you have undervolted(which I don't think you've said) you may want to raise the voltage or allow stock voltage, as that can also be the issue.
irishrally said:
If the device is otherwise perfect and free of any defects, I might take a stab at trying to fix it by wiping it and reflashing the stock Image. If you can't get it to work you can always return it then.
Click to expand...
Click to collapse
Is reflashing the stock rom the same as resetting it to factory settings?
Silentbtdeadly said:
The first few letters on the sticker on the back of the tablet, at the bottom, will tell you the hardware version..
And you have a choice, if you just got it and can return it, it is unlikely you will have the issue with a new one.. if you can't, you may want to figure out how to flash a stock firmware, as I have a feeling the OTA update may have went wrong. Resetting your tablet(factory reset) just deletes your /data partition, the system partition is not rewritten.. so if there was something wrong with the update in the system files, that won't help.
I am pretty damn sure it is likely kernel related, yet another option to look into.. the nook color(I used to use) has that issue, so it is sad to hear anyone hear have that issue too.
If you are willing to root, you may want to try increasing the minimum clock speed just one step, or if you have undervolted(which I don't think you've said) you may want to raise the voltage or allow stock voltage, as that can also be the issue.
Click to expand...
Click to collapse
I don't have my box anymore. Is there another way to see what your hardware number is?
kris4o2 said:
I don't have my box anymore. Is there another way to see what your hardware number is?
Click to expand...
Click to collapse
I'm not exactly sure, I know the sticker on the back of the tablet itself, toward the bottom has it.. I'm still somewhat new to this tablet yet.
Goldcell said:
Is reflashing the stock rom the same as resetting it to factory settings?
Click to expand...
Click to collapse
I said in my last post, restoring to factory just deletes the /data partition, and leaves the /system files exactly the same. Reflashing actually overwrites the system files.
I get it occasionally but I'm running a CM nightly and Clemsyns elite kernel so I chalk it up to that.
I've flashed stock rom and several other roms, but it did not help so I've returned it for a new device, i have to wait 3 weeks for a new one . Thanks for the replies!
Related
So before anything this is what I have.
SPL: Danger SPL
MOD:Cyanogen 4.0.4
RADIO: latest
THEME: CyanogenMod-4.0.4-CustomV7 by: Z҉A҉L҉G҉O
So what happened was after I installed this theme everything was running smoothly. My phone was low on battery so I pluged in my Charger. After being on the phone while charging for 30 - 60 minutes my touch stopped working, so I turned it off and on thinking it'll fix the problem and it didn't.
I leave it alone hoping the touch will comeback the the next morning and it didn't. So I wiped and reinstalled CyanogenMOD 4.0.4 hoping that'll do the trick and it juat made things worse.
Now I'm stuck a the "Tap the Android Screen To Begin" and I can't tap it because my touch isn't working.
Is there any way to fix this or just skip that screen?
I need to ge4t back to my gf or all hell is going to break loose.
You could restore your nandroid backup (you have one, dont you?) to get past the tap-the-android screen, or USB/adb kill the process.
Sounds like your digitizer is dead or disconnected. You might need to perform surgery.
lbcoder said:
You could restore your nandroid backup (you have one, dont you?) to get past the tap-the-android screen, or USB/adb kill the process.
Sounds like your digitizer is dead or disconnected. You might need to perform surgery.
Click to expand...
Click to collapse
i agree if a reflash didnt work your g1 needs to go under the knife
JJbdoggg said:
i agree if a reflash didnt work your g1 needs to go under the knife
Click to expand...
Click to collapse
He never said it was a "G1"...
lbcoder said:
You could restore your nandroid backup (you have one, dont you?) to get past the tap-the-android screen, or USB/adb kill the process.
Sounds like your digitizer is dead or disconnected. You might need to perform surgery.
Click to expand...
Click to collapse
No I don't, it would always say error when I tried that.
and how do I kill the process?
Thanks in Adavance if you teach me how.
Is your current issue related to your little trick?
http://forum.xda-developers.com/showthread.php?t=564592
marlopainter said:
Is your current issue related to your little trick?
http://forum.xda-developers.com/showthread.php?t=564592
Click to expand...
Click to collapse
No way!
This happened out of know where haha.
I think I'm going to just try and install cupcake 1.5 if I can find it.
AustinAce said:
No way!
This happened out of know where haha.
I think I'm going to just try and install cupcake 1.5 if I can find it.
Click to expand...
Click to collapse
Anytime you put a device in a freeze, or fridge, there will be condensation on the device. It will then create rust, or short things out. So it could 100% be because of your little "trick".
fenixnr said:
Anytime you put a device in a freeze, or fridge, there will be condensation on the device. It will then create rust, or short things out. So it could 100% be because of your little "trick".
Click to expand...
Click to collapse
Exactly, why would you think it's a good idea to put your phone in the fridge?!
THIS ENTIRE THING HAPPENED BEFORE I PUT MY PHONE IN THE FRIDGE.
Can someone just help me skip the initial process, or just teach me how change the Cyanogen image at the beginning to the original android image.
stop!!! i had this issue were you using a custom user.conf?
i messed up something on mine and phone would lock up nothing at all would happen i was cm 4.11.1 but i had just switch from xrom so went back to and went away but it bothered me so i rent back to rc29 then had more issues up graded to cupcake did one click root and all is good.
jmon777 said:
stop!!! i had this issue were you using a custom user.conf?
i messed up something on mine and phone would lock up nothing at all would happen i was cm 4.11.1 but i had just switch from xrom so went back to and went away but it bothered me so i rent back to rc29 then had more issues up graded to cupcake did one click root and all is good.
Click to expand...
Click to collapse
I kinda don't know what that is.
from the beginning:
I had the hard SPL and wanted the custom V7 them cyan 4.0.4 so I installed Danger.
Then installed the theme, and once I plugged my charger in my touch stopped working so I tried turning it off and on to fix it and it still wasn't working.
So i tried to wipe and reinstall 4.0.4 and got stuck into "tap android screen"
Now I'm back to the hard SPL but I still get stuck at the beginning.
I'm going to send it in, because I think it's a hardware issue not a software issue.
user.conf and userinit.sh and files you push to your ext to tell the ROM what CompCache/Swap settings to use. If you don't know what it is then it's clearly not causing the problem.
So I should jusr send it in?
AustinAce said:
So I should jusr send it in?
Click to expand...
Click to collapse
if i was you i would flash back to rc29 the flash back up to stock cupcake. and see if that helps because you should unroot before you send it in. hope this helps
AdrianK said:
user.conf and userinit.sh and files you push to your ext to tell the ROM what CompCache/Swap settings to use. If you don't know what it is then it's clearly not causing the problem.
Click to expand...
Click to collapse
you can also edit cpu speeds as well has some other things. but your right mainly used for swap settings.
jmon777 said:
if i was you i would flash back to rc29 the flash back up to stock cupcake. and see if that helps because you should unroot before you send it in. hope this helps
Click to expand...
Click to collapse
I flashed back to the rc29
And when I tried flasjing cupcake it said something about no signatures error
jmon777 said:
if i was you i would flash back to rc29 the flash back up to stock cupcake. and see if that helps because you should unroot before you send it in. hope this helps
Click to expand...
Click to collapse
I flashed back to the original radio
And when I tried flasjing cupcake it said something about no signatures error
AustinAce said:
I flashed back to the original radio
And when I tried flasjing cupcake it said something about no signatures error
Click to expand...
Click to collapse
Are you useing the one that came from tmobile? If its hard to find there a guy that has I like in his sig ill try and find it for u if u can't.
So, I have a backup of my rom from another device that I installed. What I need to do is change the sync account, but it says I can not remove it. Fine, so I try to add another and it says google can not establish a reliable connection.
If I factory reset the device, it will sit at the boot logo and keep crashing until I restore from backup.
If i install a new rom, only one actually worked but it seemed to be an older one (Different icons, missing the Hubs)
What can I do? I already completely bricked one device trying to get this fixed. I really gotta get this going, how can I either wipe it all out completely so I can set it up new again, or find the stock USA/Canada Rom?
Thanks!!
Ps, here is the thread I already have where i speak about bricking my other phone: http://forum.xda-developers.com/showthread.php?t=1175098
Dude please stop whatever you're doing. You seems to be getting yourself in a mess.
First do some reading on how to flash with Odin and then flash a stock firmware to the device and do a cache wipe and factory reset in the recovery menu. When you boot into the device do a hard reset and then stop messing with the device.
Intratech said:
Dude please stop whatever you're doing. You seems to be getting yourself in a mess.
First do some reading on how to flash with Odin and then flash a stock firmware to the device and do a cache wipe and factory reset in the recovery menu. When you boot into the device do a hard reset and then stop messing with the device.
Click to expand...
Click to collapse
The thing is, if i do a factory reset, it will not boot for some weird reason :/
Thats all I am trying to do, I just need to get back to stock then i'm sitting there. The only thing that actually seems to work is the backup I have on it right now, but I can not reset any of the settings to actually be able to start using the thing
this is the second one you've messed up? use one of the other 2 but don't try to do a restore just download all your apps manually. and send me one of the messed up ones.
boondoc said:
this is the second one you've messed up? use one of the other 2 but don't try to do a restore just download all your apps manually. and send me one of the messed up ones.
Click to expand...
Click to collapse
Yup, haha
I have a Jig on the way, ill see how that goes
Well I would also like to change the sync account, which it will not let me ://
I just reflashed like 8 times in the last hour trying different roms, none are working
Stop.
There is a bug when you wipe, which stops boot...
Affects older stock roms.
Newer ones should be OK, as should custom ROMs
pulser_g2 said:
Stop.
There is a bug when you wipe, which stops boot...
Affects older stock roms.
Newer ones should be OK, as should custom ROMs
Click to expand...
Click to collapse
So what can I do?
I also cant even find any Stock USA roms, which is weird
I just got it to finally boot with another rom
The only thing different is it by default has some widgets added, and the Messaging app has a different icon. All the hubs are also intact
*Roots, makes a backup*
bncplix said:
So what can I do?
I also cant even find any Stock USA roms, which is weird
Click to expand...
Click to collapse
that's because it hasn't been released here yet. seriously... send me one of those babies.
boondoc said:
that's because it hasn't been released here yet. seriously... send me one of those babies.
Click to expand...
Click to collapse
All seems to be working now. Woo whoo!
I have 4 And 2 of the 10.1 tabs
I am working closely with Samsung on one of their new marketing projects, which is why I get all of these
So, factory resetting this image screws up too.
But its okay, as I got a blank backup now with no accounts. So I'm all set
Also, just got the email confirmation that my jig shipped out.
You should probably donate one of the "b0rk3n" device to a dev.
Was happily on CM and for some reason decided to try stock kitkat. Did everything via tutorial and all went all well - but been getting some strange issues which has made my phone unusable.
When i press vol up/down it takes ten seconds to pop up. Sound does not work at all whether calling/playing music. Settings f/c when I attempt to click the sound menu. I believe everything else is working fine.
Tried reflashing stock firmware countless times... Tried flashing numerous custom 4.4 roms.
Australian bought phone if it makes any difference.
Please help as Im stuck using a spare iphone 4 and its killing me! haha.
Thanks,
Riimez said:
Was happily on CM and for some reason decided to try stock kitkat. Did everything via tutorial and all went all well - but been getting some strange issues which has made my phone unusable.
When i press vol up/down it takes ten seconds to pop up. Sound does not work at all whether calling/playing music. Settings f/c when I attempt to click the sound menu. I believe everything else is working fine.
Tried reflashing stock firmware countless times... Tried flashing numerous custom 4.4 roms.
Australian bought phone if it makes any difference.
Please help as Im stuck using a spare iphone 4 and its killing me! haha.
Thanks,
Click to expand...
Click to collapse
Let's start from the beginning.
Can you describe your method of flashing in case you are doing something wrong? Please describe as much information as possible.
What is your phone model?
y2kkingboy said:
Let's start from the beginning.
Can you describe your method of flashing in case you are doing something wrong? Please describe as much information as possible.
What is your phone model?
Click to expand...
Click to collapse
9005. sorry it was a couple of days ago so I dont really remember. I flashed a 4.4 bootloader (standalone) then tried flashing a 4.4 rom i believe it was sweetrom.
Riimez said:
9005. sorry it was a couple of days ago so I dont really remember. I flashed a 4.4 bootloader (standalone) then tried flashing a 4.4 rom i believe it was sweetrom.
Click to expand...
Click to collapse
I believe the best thing to do now is to flash stock ROM and make sure to full wipe everything even internal memory.
If you have external memory, back up what ever you think necessary to it, the remove it from the device and keep it out.
That clean start well give you a good indication whether the problem is based on a bad flash or there is something wrong with the device.
If everything is running smoothly, we will see about flashing custom ROM.
y2kkingboy said:
I believe the best thing to do now is to flash stock ROM and make sure to full wipe everything even internal memory.
If you have external memory, back up what ever you think necessary to it, the remove it from the device and keep it out.
That clean start well give you a good indication whether the problem is based on a bad flash or there is something wrong with the device.
If everything is running smoothly, we will see about flashing custom ROM.
Click to expand...
Click to collapse
Yep its what ive done, reflashed stock completly and removed sd card. Still no dice - running complete stock 4.4 still with this problem.
Could this be an EFS problem?
If it were an efs problem you wouldn't even boot in most cases.
Can you describe how you flashed stock ROM? Maybe you did it wrong.
Sent from my SM-N9005 using Tapatalk
Sorry to hear that..base on my experienced happened also on my S4..luckily still under warranty..have to wait for 2 weeks...company says faulty mother board and speaker. Hope this helps....
Sent from my SM-N900 using xda premium
Riimez said:
Was happily on CM and for some reason decided to try stock kitkat. Did everything via tutorial and all went all well - but been getting some strange issues which has made my phone unusable.
When i press vol up/down it takes ten seconds to pop up. Sound does not work at all whether calling/playing music. Settings f/c when I attempt to click the sound menu. I believe everything else is working fine.
Tried reflashing stock firmware countless times... Tried flashing numerous custom 4.4 roms.
Australian bought phone if it makes any difference.
Please help as Im stuck using a spare iphone 4 and its killing me! haha.
Thanks,
Click to expand...
Click to collapse
NEE region? - if so it has issues with 4.4.2, @nex7er had the same issues, and if you're using SweetROM I believe he pm'd not-i the fix for it. -- It can be fixed though.
Maybe completely wipe it (System, Data and all) and then Flash stock with Odin?
After kitkat upgrade.. if i use camera app such as camera 360 Or picsart, i can't save my photo to sdcard. It's error, Has anyone had or know how to resolve this problem???
Blancos4Lyf said:
Maybe completely wipe it (System, Data and all) and then Flash stock with Odin?
Click to expand...
Click to collapse
Yep. Still no dice.
Riimez said:
Yep. Still no dice.
Click to expand...
Click to collapse
I did post the reason on the last page what I think it might be...... if you're in a Nordic region or even have a nordic model it's a common problem, if you search around you'll see others that have the same issue (notably ne7xer). -- If it's not that, then it's a warranty job due to faulty HW
EDIT: you could try a complete wipe including re-partitioning, but that's a bigger job that you'd want to do in all honesty.
radicalisto said:
I did post the reason on the last page what I think it might be...... if you're in a Nordic region or even have a nordic model it's a common problem, if you search around you'll see others that have the same issue (notably ne7xer). -- If it's not that, then it's a warranty job due to faulty HW
EDIT: you could try a complete wipe including re-partitioning, but that's a bigger job that you'd want to do in all honesty.
Click to expand...
Click to collapse
Could be my last option considering knox is tripped..
Got a link to a tutorial for re-partitioning?
Grab a PIT file for your device; - then you flash firmware with Odin / PIT file. - I have never done it, nor do I fancy doing it, but have a read (journeyman posted asking how and done it, it's in this section Q+A) - I can never remember whether you flash the PIT first then the firmware or both together. I wouldn't want to hazard a guess just in case though.
But if you've tripped KNOX, then yes, seems like it could be your last option, unless you have tried some various custom ROMs? ( I know sweetROM seems to be the master fix for any issues peple have on KK atm) could just be a stock issue currently that will more than likely get a fix at some point.
EDIT As yours is an AU phone, possible it could be a HK model? - from KOGAN? I know some AU users have had HK models from them.
EDIT2: When I flashed HAL ROM, @theresident stated in his how to OP that we needed to format /system during install - It's possible this may also fix it, but that wipes your entire system obviously and *IF* it doesn't boot up you then have issues
EDIT3 : quote from HAL ROM OP
Instalation:
1. Copy the zip to the phone
2. Reboot to Recovery/CWM
3. Wipe Data/Factory Reset
4. Wipe Cache
5. Wipe Dalvik Cache
6. Mounts and Storage then click "Format /System" (This won't delete any of your data)
7. Install.. wait one minute and ROCK !!!
Click to expand...
Click to collapse
crazy_777 said:
After kitkat upgrade.. if i use camera app such as camera 360 Or picsart, i can't save my photo to sdcard. It's error, Has anyone had or know how to resolve this problem???
Click to expand...
Click to collapse
You are hijacking.
Anyway,
1. Install es file manager or any file reader with root.
2. navigate to /System/etc/permissions
3. open "platform.xml" file to edit
4. look for the stack that has "WRITE_EXTERNAL_STORAGE"
you will find something like <group gid="sdcard_r" />
5. make sure these lines are there, if not, add them
<group gid="sdcard_rw" />
<group gid="media_rw" />
That's it
Running an Australian N9005.
I was running Temaseks unofficial CM11 build just fine. Got bored and wanted to go back to a more Samsung styled phone.
Decided to flash X-Note. As I'd used it before CM11. It worked fine then.
Attempted to flash X-Note but it wouldn't boot, stuck at initial screen with the Kernel warnings at the top of the screen. Was told it was because I hadn't got the new 4.4 bootloader.
I was told to follow the instructions here: http://forum.xda-developers.com/showpost.php?p=46223545&postcount=2
Which I did.
Using these download links and instructions: http://forum.xda-developers.com/showthread.php?p=49931269
That fixed the boot issue. I suppose I'm not on the 4.4 bootloader.
However when I booted up the stock Polish ROM, the initial Samsung Setup Wizard would crash at the end of the setup and force me back to the start of the setup. Tried ignoring it and just flashing the custom recovery and then XNote. Same issue, the setup wizard in XNote crashes as well.
Someone then told me I should try repartitioning the device using a PIT. I don't know what that is, but it was suggested.
Using this ROM: https://mega.co.nz/#!QVwlVDgJ!QyAxmDMcsIA-56cX_28Ua2aPZLcJATVvdM07LOs0V10
And this PIT: http://forum.xda-developers.com/showpost.php?p=50614669&postcount=77
Completes successfully.
Same issue............... That being a third separate ROM (official? at that)....
Samsung Setup Wizard crashes...
I even tried flashing XNote and removing the setup wizard just to get past it. That fixes it for about 10 minutes or so. After about 10 minutes of use the phone freezes and I have to hold the power button to force it to restart. If I leave the phone off, it still freezes, as soon as I try to unlock it it freezes and need to force restart.
I really don't know what to do now... Any help guys? I'm trying my best here...
Please, if you need any more information, please ask.
Might not help, but have you wiped your phone clean using custom recovery ( data,cache, dalvik, internal sd ) before flashing xnote or factory reset on recovery when on stock?
Do you have reactivation lock enabled?
Sent from my fingers to your face using my Samsung Galaxy Note 3!
hey_joe said:
Might not help, but have you wiped your phone clean using custom recovery ( data,cache, dalvik, internal sd ) before flashing xnote or factory reset on recovery when on stock?
Click to expand...
Click to collapse
Yes.
nicholaschum said:
Do you have reactivation lock enabled?
Click to expand...
Click to collapse
No.
This has puzzled me, not sure why it's still acting up especially after re-partitioning and flatlining everything.
radicalisto said:
This has puzzled me, not sure why it's still acting up especially after re-partitioning and flatlining everything.
Click to expand...
Click to collapse
Yes indeed. I'm very confused...
So... I don't want to get ahead of myself, but my phone seems to have sorted itself out...
I decided to just send it back to the carrier to get it replaced. So I decided to just flash the official Firmware again. (I accidentally left repartition ticked)
Once it started I thought... Oh ****... But I was sending it back anyway so who cares. (the carrier said they will just swap it for me if they can see it not working)
So I let it finish and turn it on to see what happens, run through the setup to make sure it still crashes at the same spot so I can show them... and it doesn't crash... wtf?
So I flash the custom recovery and XNote... And it seems to be working now. Now freezing, no nothing... I... I don't know...
Crazy, least it appears somewhat sorted lol
radicalisto said:
Crazy, least it appears somewhat sorted lol
Click to expand...
Click to collapse
So far, yeah... I think I got the runt of the litter or something... Haha
Reynbow said:
So far, yeah... I think I got the runt of the litter or something... Haha
Click to expand...
Click to collapse
Just out of curiosity, as I see you have an AU model, did you buy it from Kogan? -- Reason I ask is that they used HK firmware on some models and HK models have issues flashing normal firmware (similar to the issue you had)
radicalisto said:
Just out of curiosity, as I see you have an AU model, did you buy it from Kogan? -- Reason I ask is that they used HK firmware on some models and HK models have issues flashing normal firmware (similar to the issue you had)
Click to expand...
Click to collapse
Not from Kogan, no. From Optus. Pretty standard.
Hey everyone I know you all probably get fed up helping noobs out and I do apologize in advance but have no idea what to do. My daughter has had gt-i9505 for a year and a half now she had an update about a week ago that she did. And now the phone was having sound problems and seems very unstable not sure if update has anything to do with it. Looked around the net tried a few different things did nothing serious just cleaned headphone jack and wiped cache nothing seemed to work. Just to say the phone was on 5.0.1 Now she has wanted me to root and install philz touch recovery for a while now but didn't really want to incase something went wrong. So given that all these problems were happening I decided I would do it for her and It all went smoothly so then I put new rom on it for her and that seemed fine to but sound problem still there and still seems very unstable is there any suggestions you guys can think of to fix it, would be greatly appreciated CHEERS :good:
Try flashing back to a completely stock rom using Odin.
Stock ROMs can be downloaded from sammobile.com.
Your best bet is to odin restore, if issue still pertains, then you have a problem in hardware, if you don't want to restore, then root device flash twrp, and factory reset there, if you have further questions, Google rooting flashing and bootloaders.
Just to say thanks to you guys I think back to stock is the only way cheers
Hey everyone just to say i have flashed back to stock now but no change even tried to update and still no sound,I even found this thread http://forum.xda-developers.com/showthread.php?t=2612167 and tried what they said and know go just notice now when i hit the volume control at all it crashes the phone. But if it was a hardware problem would it play music on the samsung logo screen on start up? any other idea of where to go from here would be great CHEERS AGAIN
Try a stock android based ROM.
Darth Vader said:
Try a stock android based ROM.
Click to expand...
Click to collapse
Can i try an android based ROM from where i'm at now or do i have to root again?
The phone is running the latest stock rom? Was it factory reset before booting for the first time? Possible hardware issue?
Sorry just a question is Cyanogenmod an android based stock rom?
audit13 said:
The phone is running the latest stock rom? Was it factory reset before booting for the first time? Possible hardware issue?
Click to expand...
Click to collapse
No its not running the latest stock rom i went back to 4.4.2 because the latest stock rom is where the problem seemed to start in the first place. And yes i did a wipe data/factory reset before restart.
eireusa said:
Sorry just a question is Cyanogenmod an android based stock rom?
Click to expand...
Click to collapse
Yup!You can try Viper4android, its a mod for audio and is really awesome.I'm pretty sure it can fix the issue
Here's the link: http://forum.xda-developers.com/showthread.php?t=2191223
It requires root.
Hey guys hypothetically if it was a hardware problem and i wanted to get it fixed is it hard to reset the knox counter?
Still no luck it seems to have gotten worse touch wiz has stopped and wifi won't turn on what the hell is happening?
I would try flashing the latest stock rom and perform a factory wipe before booting the rom for the first time.
audit13 said:
I would try flashing the latest stock rom and perform a factory wipe before booting the rom for the first time.
Click to expand...
Click to collapse
OK now i get what your saying before it starts, but do you not have to let it boot up for Odin to say pass and turn green?
Open Odin, uncheck everything except f.reset time. Flash the rom, when you see the word reset in the status window, remove cable from the phone, remove battery, wait 5 seconds, insert battery, use button combination to boot into stock recovery, factory wipe, and reboot.
audit13 said:
Open Odin, uncheck everything except f.reset time. Flash the rom, when you see the word reset in the status window, remove cable from the phone, remove battery, wait 5 seconds, insert battery, use button combination to boot into stock recovery, factory wipe, and reboot.
Click to expand...
Click to collapse
OK got it, I will try that hour of a download of sammobile.com thank you for your patience
Let us know how it goes. I suggested flashing a stock rom and wiping because, if it still doesn't work properly, it could be a hardware issue.
Good luck.
eireusa said:
Hey everyone I know you all probably get fed up helping noobs out and I do apologize in advance but have no idea what to do. My daughter has had gt-i9505 for a year and a half now she had an update about a week ago that she did. And now the phone was having sound problems and seems very unstable not sure if update has anything to do with it. Looked around the net tried a few different things did nothing serious just cleaned headphone jack and wiped cache nothing seemed to work. Just to say the phone was on 5.0.1 Now she has wanted me to root and install philz touch recovery for a while now but didn't really want to incase something went wrong. So given that all these problems were happening I decided I would do it for her and It all went smoothly so then I put new rom on it for her and that seemed fine to but sound problem still there and still seems very unstable is there any suggestions you guys can think of to fix it, would be greatly appreciated CHEERS :good:
Click to expand...
Click to collapse
Your daughter seems to know more than the average one Either that or kids just grow up fast these days!
It's highly unlikely that a software update would interfere with the phone's sound imo. How was the update done, e.g. wifi?
Me thinks your problem is hardware related. Also, you mentioned something about downgrading from 5.0.1 to 4.4. This might have something to do with your sound woes.
And then, once root counter has been tripped, there is no way to un-flag it. I believe there might be a way "trick" the counter to show "zero" but I haven't personally ever bothered to try it out.
Personally, I think it's the phone's hardware :good:
Hope you didn't get too much conflicting answers.
thundastruck said:
Your daughter seems to know more than the average one Either that or kids just grow up fast these days!
It's highly unlikely that a software update would interfere with the phone's sound imo. How was the update done, e.g. wifi?
Me thinks your problem is hardware related. Also, you mentioned something about downgrading from 5.0.1 to 4.4. This might have something to do with your sound woes.
And then, once root counter has been tripped, there is no way to un-flag it. I believe there might be a way "trick" the counter to show "zero" but I haven't personally ever bothered to try it out.
Personally, I think it's the phone's hardware :good:
Hope you didn't get too much conflicting answers.
Click to expand...
Click to collapse
No had my doubts about the update myself it was done over wifi I think she said it was one of the lollipop updates. Now regarding the downgrading from 5.0.1 the sound problem had already started on 5.0.1 only thing I done from that point forward was to root it an put philz recovery on it and then tried a custom rom to see if that would help which it did'nt sound prob still there, after that i was advised to try reverting back to stock then i downgraded to 4.4.2 stock to see if that would help no luck, just a question when i was rooting i was reading about triangle away does that not reset the counter?