Related
I'm a geek, but a bit of a nub about Android's rom structure, as it comes from the factory, as new. I have the new N7 2013.
Now that I'm on the JSS15Q, I've got a question.
If I do a complete reset, that wipes the data and installs the Factory OS from the ROM, will it come back as JSS15Q, and if not, why not.
It seems it would be stupid to restore back to the original rom that came w/ my N7 that had gps, and other problems?
If it comes back w/ the older rom, is there anyway to replace this older/default rom w/ the the newer JSS15Q, if and when I have to do a factory reset?
Thxs
Markdek said:
I'm a geek, but a bit of a nub about Android's rom structure, as it comes from the factory, as new. I have the new N7 2013.
Now that I'm on the JSS15Q, I've got a question.
If I do a complete reset, that wipes the data and installs the Factory OS from the ROM, will it come back as JSS15Q, and if not, why not.
It seems it would be stupid to restore back to the original rom that came w/ my N7 that had gps, and other problems?
If it comes back w/ the older rom, is there anyway to replace this older/default rom w/ the the newer JSS15Q, if and when I have to do a factory reset?
Thxs
Click to expand...
Click to collapse
/system is where the ROM is and is untouched except when you flash it. Factory reset only formats user data, not /system. Therefore, if you update then factory reset it stays at them same ROM version.
Markdek said:
I'm a geek, but a bit of a nub about Android's rom structure, as it comes from the factory, as new. I have the new N7 2013.
Now that I'm on the JSS15Q, I've got a question.
If I do a complete reset, that wipes the data and installs the Factory OS from the ROM, will it come back as JSS15Q, and if not, why not.
It seems it would be stupid to restore back to the original rom that came w/ my N7 that had gps, and other problems?
If it comes back w/ the older rom, is there anyway to replace this older/default rom w/ the the newer JSS15Q, if and when I have to do a factory reset?
Thxs
Click to expand...
Click to collapse
As mentioned above, ROM is not touched by factory reset.
If you are using stock recovery, user data, cache, and virtual sdcard are wiped.
If you are using TWRP recovery, user data and cache are wiped but virtual sdcard is preserved.
Ok, I think I get it......so can I replace the existing/default/store bought rom in /system with the JSS15Q rom, and will it work and is this safe? Anybody do this?
And again, my reason would be that the factory/default/store bought rom sucks w/ bugs.
And, how does this relate to flashing custom rom's...do these delete the store bought rom? You know, you root, and then flash, say the CM 10.2 rom?
You are already on jss15q. You can replace it with any version you want. Bottom line, you can go to any version you want and revert any changes you make.
Sent from my SCH-I535 using Tapatalk 4
Markdek said:
Ok, I think I get it......so can I replace the existing/default/store bought rom in /system with the JSS15Q rom, and will it work and is this safe? Anybody do this?
And again, my reason would be that the factory/default/store bought rom sucks w/ bugs.
And, how does this relate to flashing custom rom's...do these delete the store bought rom? You know, you root, and then flash, say the CM 10.2 rom?
Click to expand...
Click to collapse
You can replace it and it works. At worst you might need to do a factory reset after you install a new ROM, but usually that isn't necessary going from stock to stock.
As to "safe" that is too broad a question and could mean different things.
Root is not really related to flashing ROMs other than some ROMs come pre-rooted. You have a stock or custom rom with and without root.
There is only one /system to store your ROM. If you flash a ROM, it overwrites what was there before. If you don't have a backup and nobody has made an image or backup available, it would be difficult to go back, though almost every useful ROM will have an image or backup available.
I think I'm getting more confused. Bare w/ me. Let's start simple.
My N7 came w/ build JWR66N.
W/ the update, it now has JSS15Q (I'm told there's also a JSS15J.
If I factory reset, will it come back as JSS15Q, or the original JWR66N.
Markdek said:
I think I'm getting more confused. Bare w/ me. Let's start simple.
My N7 came w/ build JWR66N.
W/ the update, it now has JSS15Q (I'm told there's also a JSS15J.
If I factory reset, will it come back as JSS15Q, or the original JWR66N.
Click to expand...
Click to collapse
It will stay on JSS15Q...
cowabunga said:
It will stay on JSS15Q...
Click to expand...
Click to collapse
Awesome...thanks......then I don't need to do anything.
I had assumed that it would go back to the rom/build that came with it when I bought it...and thought, that' stupid, because it was a buggy image/rom/build.
So, I'm good to go if I ever have to restore to factory, and it won't go back to that stupid version.
Some day I hope to either just root, or maybe try flashing a custom rom.
Markdek said:
Ok, I think I get it......so can I replace the existing/default/store bought rom in /system with the JSS15Q rom, and will it work and is this safe? Anybody do this?
And again, my reason would be that the factory/default/store bought rom sucks w/ bugs.
And, how does this relate to flashing custom rom's...do these delete the store bought rom? You know, you root, and then flash, say the CM 10.2 rom?
Click to expand...
Click to collapse
I was on JWR66N it was perfect from store. I did the OTA that came in. It made my Nexus 7 bad it wouldn't type worth a crap. I had the screen disappearing when I typing.
So what I did was easy I took this rom 35d9b692a660c2ea96ce1181b006c7fddf2cb208.signed-razor-JSS15Q-from-JWR66N.35d9b692.zip and side loaded it in on top of my other JSS15Q. It seemed to fix a lot but still have a little missed keys but the ghosting totally gone.
can anyone help me i have a g2 801 t-mobile version and flashed the cloudyflex rom and noticed i didnt have data working so i went to twrp and wiped everything and restored my old stock rom but notice nothing was working no wifi no notification bar and it keeps randomly rebooting and it cant be turned off i have flashed several backups i had stored and none of them work
1stloc said:
can anyone help me i have a g2 801 t-mobile version and flashed the cloudyflex rom and noticed i didnt have data working so i went to twrp and wiped everything and restored my old stock rom but notice nothing was working no wifi no notification bar and it keeps randomly rebooting and it cant be turned off i have flashed several backups i had stored and none of them work
Click to expand...
Click to collapse
I would suggest you to make a clean install of the stock rom!
That should fix the issue!
zacharias99 said:
I would suggest you to make a clean install of the stock rom!
That should fix the issue!
Click to expand...
Click to collapse
I tried and nothing works i even went back to stock using this thread http://forum.xda-developers.com/showthread.php?t=2432476
What recovery were you using and do you have any backups from then or is everything gone?
sp33dsk8 said:
What recovery were you using and do you have any backups from then or is everything gone?
Click to expand...
Click to collapse
the latest twrp....i have backups on my computer but cant transfer them because it keeps rebooting and since i went back to stock i cant root as it does not let cuz of the constant reboot
1stloc said:
the latest twrp....i have backups on my computer but cant transfer them because it keeps rebooting and since i went back to stock i cant root as it does not let cuz of the constant reboot
Click to expand...
Click to collapse
I'd try and get with this guy
"As usual, I'm on #lg-g2 in Freenode as IOMonster, if I'm around I'll be happy to help wherever I can."
http://forum.xda-developers.com/showthread.php?t=2432476
I had the exact same problem! Phone would boot into the rom, or stock and freeze after about a minute and reboot itself constantly. I had the updated version of TWRP and was flashing the new 1/30 Mahdi build and it happened after I did that! I tried flashing stock roms, aosp roms, and eventually did a Flash back to stock method, which non of them worked. I took the phone into T-Mobile and did a warranty replacement, got a new one overnight. Not sure if it is related to Mahdi or not, but it happened after a supposed successful flash.
I tried my TWRP Backups too, and those still restarted on me. Nothing helped me..Tried wiping the sd card, format the whole card, wipe cache, fix perm..
Hopefully you have a warranty or figure it out!
Good luck.
ZetterbergDatsyuk said:
I had the exact same problem! Phone would boot into the rom, or stock and freeze after about a minute and reboot itself constantly. I had the updated version of TWRP and was flashing the new 1/30 Mahdi build and it happened after I did that! I tried flashing stock roms, aosp roms, and eventually did a Flash back to stock method, which non of them worked. I took the phone into T-Mobile and did a warranty replacement, got a new one overnight. Not sure if it is related to Mahdi or not, but it happened after a supposed successful flash.
I tried my TWRP Backups too, and those still restarted on me. Nothing helped me..Tried wiping the sd card, format the whole card, wipe cache, fix perm..
Hopefully you have a warranty or figure it out!
Good luck.
Click to expand...
Click to collapse
Dam no I do not have warranty and I'm on a prepaid plan and bought the phone from swappa sucks the phone is a waste now
Sent from my Nexus 5 using Tapatalk
ZetterbergDatsyuk said:
I had the exact same problem! Phone would boot into the rom, or stock and freeze after about a minute and reboot itself constantly. I had the updated version of TWRP and was flashing the new 1/30 Mahdi build and it happened after I did that! I tried flashing stock roms, aosp roms, and eventually did a Flash back to stock method, which non of them worked. I took the phone into T-Mobile and did a warranty replacement, got a new one overnight. Not sure if it is related to Mahdi or not, but it happened after a supposed successful flash.
I tried my TWRP Backups too, and those still restarted on me. Nothing helped me..Tried wiping the sd card, format the whole card, wipe cache, fix perm..
Hopefully you have a warranty or figure it out!
Good luck.
Click to expand...
Click to collapse
Hey can you tell me how t-mobile insurance works i use to be with sprint and if they couldnt fix it they would send me a new at no cost...my friend has t-mobile insurance can he put his sim card in and they have a look at it and if they do will he be charged anything?
OK learn about adb sideload so you can sibeload a ROM or have you us LG G2 to go back to stock and start all over?
Sent from my LG-LS980 using XDA Premium 4 mobile app
Nicamarcel1 said:
OK learn about adb sideload so you can sibeload a ROM or have you us LG G2 to go back to stock and start all over?
Sent from my LG-LS980 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
ok read my other post as i have gone back to stock and it has not worked
I had the same problem. If you looked for other threads, you would find fix.
Problem is in CPU voltage.
http://forum.xda-developers.com/showthread.php?t=2612243
Wysłane za pomocą LG G2 przez TWRP
1stloc said:
Dam no I do not have warranty and I'm on a prepaid plan and bought the phone from swappa sucks the phone is a waste now
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
Should still be under warranty with LG. I'd call their support and give them the serial number to see if it still covered.
As far as the LG Warranty goes, all I did is walk into the store and show them the issue at hand, and he put in a order for a new one sent overnight to me. They send you a prepaid label and a box to ship your old one back(phone only). The new phone I have appears to be brand new, with all the crazy plastic protection on it... not sure if it is a refurbish or not. Didn't cost me a penny, as I have the JUMP w/ protection plan.
Well, hello there! So I recently came across this issue with my Google Nexus 4 and I am pretty sure it's a simple answer but I still want to double check before I screw this up. This is my first phone to actually root successfully, I am running an up to date version of purity rom, have a custom kernal to go with it,and on top of that I also have TWRP as my custom recovery. I recently bought the Nexus 5 and I want sell this one to one of my friends with the actual purity rom in the phone and dont know how to do a clean install without it having my personal data in it, should I factory data reset all the phone and reinstall the purity rom and gapps , or a friend of mine told me to just format the data and itll be fine. Like I said this is my first rooted phone and Im basically new to this. My friend wants the phone rooted with purity and I want to give him a like new experience to the phone. Also to start from the very beginning of the rom, like signing in to the google accounts and what not (like a new phone or like the very first time when you install a custom rom). Rather than just making it complicated for myself, I want to ask you, the experts. How would you solve this issue? And also what would be the best option for this problem that I am having? I just want to thank you guys in advance for not only your time and patience, but also for the future advice that you're giving me.
Blue.F150 said:
Well, hello there! So I recently came across this issue with my Google Nexus 4 and I am pretty sure it's a simple answer but I still want to double check before I screw this up. This is my first phone to actually root successfully, I am running an up to date version of purity rom, have a custom kernal to go with it,and on top of that I also have TWRP as my custom recovery. I recently bought the Nexus 5 and I want sell this one to one of my friends with the actual purity rom in the phone and dont know how to do a clean install without it having my personal data in it, should I factory data reset all the phone and reinstall the purity rom and gapps , or a friend of mine told me to just format the data and itll be fine. Like I said this is my first rooted phone and Im basically new to this. My friend wants the phone rooted with purity and I want to give him a like new experience to the phone. Also to start from the very beginning of the rom, like signing in to the google accounts and what not (like a new phone or like the very first time when you install a custom rom). Rather than just making it complicated for myself, I want to ask you, the experts. How would you solve this issue? And also what would be the best option for this problem that I am having? I just want to thank you guys in advance for not only your time and patience, but also for the future advice that you're giving me.
Click to expand...
Click to collapse
Boot into recovery
Wipe System, Data, Cache and Dalvik Cache
Flash Rom and Gapps.
That should do it.
Sent with my Nexus® 10 minus 3
Berrydroidcafe said:
Boot into recovery
Wipe System, Data, Cache and Dalvik Cache
Flash Rom and Gapps.
That should do it.
Sent with my Nexus® 10 minus 3
Click to expand...
Click to collapse
Alright thanks!
Hello xda community!
I received the nexus 6p christmas and after a few hours playing with it, I unlocked, installed twrp and installed cm13. I then installed ak kernal. My phone installs both fine and runs as normal without any FC. Then this is where it gets weird. When I had my new rom and kernal all set up. I go into TWRP and create a backup. I restart and I'm bootlooping. It tells me my device is corrupt. It did this with the original backup of stock rom, cm13, with and without ak kernal installed... and then sometimes my phone will soft-brick (gets stuxk on google logo) I really love cm engine as I habe a theme. But I'm unsure what is happening to my phone.
Any help is appreciated! - thanks.
Info
Xtra-arrow said:
Hello xda community!
I received the nexus 6p christmas and after a few hours playing with it, I unlocked, installed twrp and installed cm13. I then installed ak kernal. My phone installs both fine and runs as normal without any FC. Then this is where it gets weird. When I had my new rom and kernal all set up. I go into TWRP and create a backup. I restart and I'm bootlooping. It tells me my device is corrupt. It did this with the original backup of stock rom, cm13, with and without ak kernal installed... and then sometimes my phone will soft-brick (gets stuxk on google logo) I really love cm engine as I habe a theme. But I'm unsure what is happening to my phone.
Any help is appreciated! - thanks.
Click to expand...
Click to collapse
Wipe everything > Advance Wipe Phone in recovery
Reinstall CM13 through Recovery and don't flash another kernel
:good:
Geeks Empire said:
Wipe everything > Advance Wipe Phone in recovery
Reinstall CM13 through Recovery and don't flash another kernel
:good:
Click to expand...
Click to collapse
Whoa! Don't tell him to wipe everything in the advanced wipe menu, that'll wipe the internal storage too which is completely unnecessary.
Xtra-arrow said:
Hello xda community!
I received the nexus 6p christmas and after a few hours playing with it, I unlocked, installed twrp and installed cm13. I then installed ak kernal. My phone installs both fine and runs as normal without any FC. Then this is where it gets weird. When I had my new rom and kernal all set up. I go into TWRP and create a backup. I restart and I'm bootlooping. It tells me my device is corrupt. It did this with the original backup of stock rom, cm13, with and without ak kernal installed... and then sometimes my phone will soft-brick (gets stuxk on google logo) I really love cm engine as I habe a theme. But I'm unsure what is happening to my phone.
Any help is appreciated! - thanks.
Click to expand...
Click to collapse
Which partitions are you backing up when creating the nandroid with TWRP?
Heisenberg said:
Which partitions are you backing up when creating the nandroid with TWRP?
Click to expand...
Click to collapse
System, data, boot - Installing the kernel made no difference, the device still corrupted on reboot. and then sometimes at least twice it has soft-bricked
Geeks Empire said:
Wipe everything > Advance Wipe Phone in recovery
Reinstall CM13 through Recovery and don't flash another kernel
:good:
Click to expand...
Click to collapse
Already tried it mate, a number of times. no joy.
Xtra-arrow said:
Hello xda community!
I received the nexus 6p christmas and after a few hours playing with it, I unlocked, installed twrp and installed cm13. I then installed ak kernal. My phone installs both fine and runs as normal without any FC. Then this is where it gets weird. When I had my new rom and kernal all set up. I go into TWRP and create a backup. I restart and I'm bootlooping. It tells me my device is corrupt. It did this with the original backup of stock rom, cm13, with and without ak kernal installed... and then sometimes my phone will soft-brick (gets stuxk on google logo) I really love cm engine as I habe a theme. But I'm unsure what is happening to my phone.
Any help is appreciated! - thanks.
Click to expand...
Click to collapse
The bootloader message won't go away until you lock the bootloader. Its just there as a warning to you in case you did not unlock your phone. As for CM I'm sure there are still many bugs to be worked out. I know I'm going to wait before Flashing it until I see people enjoying it as a daily driver. There are some great devs here in the n6p forums though so I recommend checking out some other ROMs too.
XxMORPHEOUSxX said:
The bootloader message won't go away until you lock the bootloader. Its just there as a warning to you in case you did not unlock your phone. As for CM I'm sure there are still many bugs to be worked out. I know I'm going to wait before Flashing it until I see people enjoying it as a daily driver. There are some great devs here in the n6p forums though so I recommend checking out some other ROMs too.
Click to expand...
Click to collapse
i understand the boot message and CM - i have tried other roms too. i'm not the only one who is getting bootloops on every rom. not sure what to do mate. it says corrupted then boot loops upon restart
Xtra-arrow said:
i understand the boot message and CM - i have tried other roms too. i'm not the only one who is getting bootloops on every rom. not sure what to do mate. it says corrupted then boot loops upon restart
Click to expand...
Click to collapse
Maybe this will be helpful. I think you have the red level warning like this user. Seems like the exact same situation.
http://forum.xda-developers.com/showthread.php?p=64403982
Turns out it isn't bootlooping. Its taking at least 3 minutes to turn on. It looks like bootlooping. BUt if finally loaded. After doing my uninstalling of aomw system apps. Its rebooted and keeps optimising apps. 2-4 then restarts and does same
Info
Heisenberg said:
Whoa! Don't tell him to wipe everything in the advanced wipe menu, that'll wipe the internal storage too which is completely unnecessary.
Click to expand...
Click to collapse
It s necessary to Wipe everything when don't know which modification cause the problem.
+ Recovering the backup also not working for this situation.
@Xtra-arrow
Can u explain step-by-step what u did so far
more detail = better help
:good:
Geeks Empire said:
It s necessary to Wipe everything when don't know which modification cause the problem.
+ Recovering the backup also not working for this situation.
@Xtra-arrow
Can u explain step-by-step what u did so far
more detail = better help
:good:
Click to expand...
Click to collapse
No it isn't necessary to wipe the userdata partition. No modifications are stored in the userdata partition. It would only be necessary to wipe system, data, cache, and dalvik cache. And probably flash the vendor partition too. Not userdata though.
I had a similar problem when I botched a SU flash, same warning then it would take forever to boot, then the rom would degrade over the next several minutes. I know its not fun to start over, but it was the only thing that cleared all the problems. I didn't want to take more time finding another solution when going back to stock is so simple with this device. Follow the instructions in step #11 of Heisenberg's guide (great guide, I link it to friends a lot). Then start again, I know, not what you wanted to hear. Hope this helps!
I am also in agreement with Heisenberg in regards to the userdata partition.
Geeks Empire said:
It s necessary to Wipe everything when don't know which modification cause the problem.
+ Recovering the backup also not working for this situation.
@Xtra-arrow
Can u explain step-by-step what u did so far
more detail = better help
:good:
Click to expand...
Click to collapse
Thank you very much for replying. I have found the root of the cause but no solution. Uninstalling or disabling system apps will cause my phone to go into a "optimising apps" boot loop on the next restart. What do you think? ++ every restore I make on twrp either soft bricks or bootloops. Crazy!
Info
Xtra-arrow said:
Thank you very much for replying. I have found the root of the cause but no solution. Uninstalling or disabling system apps will cause my phone to go into a "optimising apps" boot loop on the next restart. What do you think? ++ every restore I make on twrp either soft bricks or bootloops. Crazy!
Click to expand...
Click to collapse
If you are sure about reason Forget ur Backups.
you should completely install Stock Kernel, Rom, Boot.img >> Back to Stock
But If I remember correctly u did this before...
I just have to say Retry Also Install and use Nexus Root Toolkit
:good:
I have reinstalled original stock files from google. I've wiped everything numerous times. Installed ROMs just after. It took me a while but I think it comes down to the system apps. I'm running a custom ROM, cm13 and my phone is running fine. I know if I was to delete all the unwanted apps off my phone, on next reboot it will try and optimise apps, finish. Says starting apps... Then reboots. Follows the same process.
Xtra-arrow said:
I have reinstalled original stock files from google. I've wiped everything numerous times. Installed ROMs just after. It took me a while but I think it comes down to the system apps. I'm running a custom ROM, cm13 and my phone is running fine. I know if I was to delete all the unwanted apps off my phone, on next reboot it will try and optimise apps, finish. Says starting apps... Then reboots. Follows the same process.
Click to expand...
Click to collapse
Can I ask what gapps are you using? Are you using your google account to recover your apps, or are starting fresh each time?
Sent from my Nexus 6P using Tapatalk
Thanks for your reply. I've actually now narrowed itnright down to a few apps, maybe gapps. Sound recorder, voice recorder app and the google app. Either one or more of these cause my optimising apps bootloop.
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?