Related
I killed my phone while trying to install a ROM, so I re-flashed a bunch of stuff and it's back. Some problems though - it has Superuser installed still. Even though I did a factory reset, Superuser is still there. When I try to re-root it, it goes through the whole things and gives me "error: device not found". I don't understand why it finds my device in the beginning of the process, but doesn't find it at the end.
1. How do I delete Superuser for good so I can start fresh, and re-root again?
2. What do I do now?
Could you list everything you've done in chronological order starting with the first thing you flashed and ending with the last thing you flashed?
Sent from my oc'd Voodoo Fascinate using XDA App
AlgorithmX said:
Could you list everything you've done in chronological order starting with the first thing you flashed and ending with the last thing you flashed?
Sent from my oc'd Voodoo Fascinate using XDA App
Click to expand...
Click to collapse
1. I was playing nice with the clean, magic roms, etc, everything was cool.
2. Then I tried to install Blue Breeze the same way and it froze the phone (later found out it was the wrong way to do it).
3. Then I followed the restore to stock thread (flashed system, kernel, etc), and brought it back to life, and Superuser was still installed. I tried to uninstall the root, and that doesn't work either.
So right now I can't uninstall Superuser, OR re-root it again because it just keeps giving me the error: device not found.
If you go into settings and check your internal phone memory...what is it saying you have?
Can you download apps from the market?
I got this same error when the voodoo bit me and gave me the 0.00 internal memory issue.
Try either flashing your stock+root CWM backup (you made one, right?) or the nandroid "stock" image in the forum through CWM.
(Wipe data/cache on reboot in stock recovery and then from the "privacy" menu of your stock settings do a "factory reset".)
PhoenixPath said:
If you go into settings and check your internal phone memory...what is it saying you have?
Can you download apps from the market?
I got this same error when the voodoo bit me and gave me the 0.00 internal memory issue.
Try either flashing your stock+root CWM backup (you made one, right?) or the nandroid "stock" image in the forum through CWM.
(Wipe data/cache on reboot in stock recovery and then from the "privacy" menu of your stock settings do a "factory reset".)
Click to expand...
Click to collapse
1. I have 1.50 GB free.
2. Yes, I can download apps from the market.
3. Where is the stock image located?
4. I did that factory reset like 3 times.
Have you attempted this?
http://forum.xda-developers.com/showthread.php?t=782204
Visit the first thread in this forum for info on stock recovery (including where to find the "stock" nandroid recovery image).
I take it you did not create a CWM recovery backup immediately after rooting your phone?
So about 2 months ago I rooted my phone. I followed the method here:
http://forum.xda-developers.com/showthread.php?t=928160
Everything was ok, until my super user permissions program stopped working. The program opened but its a solid black screen and I cannot give any new program SU permission. At first the programs that already had permission could still have SU permission, but, in an attempt to fix the issue I cleared the program cache and those programs lost their SU permission(like TT and terminal).
Their is a new SU permissions program on the market that I paid for from the same company but I assume because the old one is still installed that it is not showing up for that reason and cannot be opened.
I cannot figure out how to get rid of the original Superuser Permissions program. I have tried every program I could find by surfing forums, I have factory reset the phone... but that SU permissiosn program is still there upon a clean factory reset!
I have the ADB installed on my PC, but when I try to run a remount I get an error that I am not allowed to do that. After my factory reset I tried running back through the walkthrough I listed. Visionary says its temp rooted, but in terminal the SU command says "access denied." I think this all has to do with that bad SU program being in stalled and if I can get that off and install the replacement one I paid for, then the SU could grant access to terminal and I could re-root the phone.
My theory is only speculation. Can anyone tell me how to remove this SU program. Its located in directories that are read only and all the commands I have found to remove it so far have required a rooted terminal command, or ADB remount commands that I cannot use. Please help. Thanks
Couple of things to try. First can you boot into recovery? What Rom are you using if any? Since you already did a factory reset I assume you don't have any data you want to save so I would just reflash a Rom from recovery. I don't remember off the top of my head but I think you hold vol - plus power when booting to get to recovery? Or if your current Rom has the permissions still to boot to recovery from the power menu?
Another thing to try is the "rage" method to gain root. I know there are issues with using visionary after you already have root. So give rage a search and try that. Come to think of it you might just try the rage method first. Let me know how its goin I might be able to help more
Sent from my HTC Vision using XDA App
shortlived said:
First can you boot into recovery?
Click to expand...
Click to collapse
A: Not sure I will try.
shortlived said:
What Rom are you using if any?
Click to expand...
Click to collapse
A: Stock that came on the phone
shortlived said:
I don't remember off the top of my head but I think you hold vol - plus power when booting to get to recovery? Or if your current Rom has the permissions still to boot to recovery from the power menu?
Click to expand...
Click to collapse
A: Again, I will try, but nothing has SU permissions anymore.
shortlived said:
Another thing to try is the "rage" method to gain root.
Click to expand...
Click to collapse
A: I will try this too. I will look on our forum, but since you are familiar with the process maybe you can provide me with a link to make things easier? Would you happen to have a link to the rage method for the G2?
Thanks for the reply!!
Nothing has worked. The original superuser permissions is still installed. I get errors when trying to push files to those read only directories even though ADB.
Any ideas on how I can get everything back to factory settings?
What do you mean "a new SU permissions program that I paid for"?
There's only one SU program that I know of. The only paid one that I know of is just a license file for an upcoming, yet to be released, program. You'll need to be specific in order for this to get resolved but it sounds like you may need to reinstall the SU binaries and the SU program.
To uninstall the current one you just need to go to applications>manage, click on the program and then click uninstall. Then use ROM manager to download and install SU for you.
Thanks for the reply but I am way past that. The OS will not let me uninstall the current SU program. The "paid" SU program is a separate program because it asked me to install the file rather than "update" like the free one says when I open it from the market.
I am very specific in my original post.
Somehow the SU program stopped working. New programs that require SU access were not givign the pop up that allowed me to grant SU access. When I open SU its just a black screen with no options. I cleared the cache to try to fix and this removed SU permissions from all the programs that I had already granted SU permissions to(like terminal). I cannot uninstall the program from the built in manager or any of the several file managers I have tried. I also cannot overwrite the current file by "updating" the existing installed version. I paid the 1$ for the paid version because its a different program all together. My thought process was if android sees it as a separate program, it will install it as a separate program and I can use it independantly of the original non-functioning version. That did not work. It says its installed but the icon is no where to be found and I cannot run it, even from a file manager. The old SU icon(of a ninja) still stays in the program list even after I wiped the phone and dida factory reset.
The point is its going to take some advanced procedure to remove the SU program. Its in adirectory that is read only. It takes SU permissions to make that directory read/write and I cant get SU permissions, even temporarily with visionary or Z7. I have tried ADB and it also says permission denied.
So this is NOT resolved yet.
At this point:
-I have reset the phone several times, each time SUpermissions is still installed when the phone comes back up.
-USB debugging is enabled.
-I have googled possible solutions that all have not worked(using ADB failed, updating the SU program failed, clearing the cahce failed, disabling usb debugging then hooking to cpu and reenabling it and using adb to try and use SU command failed...etc
-using 3rd party apps to uninstall failed
-using other SU apps failed
A rough rundown of my problem is:
Phone is rooted. At some point when I opened a NEW app that would require SU access, the pop up generalted by SUpermissions stopped popping up allowing me to give access. Programs I had already granted SU access to would still work(like terminal and titanium backup). Per someones request I tried to clear the cache. When I did this all the programs that DID have SU access lost SU access and I still could not add new programs to the SU list. I have tried ADB commands, file managers, factor resetting the phone. Nothing works. The SUpermissions program is there when I factory reset the phone as if it is one of the preinstalled apps. Apps tell me that I DO have my phone rooted, but that I still need to allow it SU access. I have not been able to uninstall the SU program and if I could get that program updated/re-installed then I believe that I could get the root access back.
Any real suggestions?(not the "is usb debugging enabled" Tier I troubleshooting steps that I am WAY past)
Thank in advance
Kk do you have s-off and the eng-bootloader? Do you have a custom recovery?
If you have s-off and custome recovery you can back up your rom using nandroid, then do a wipe and install a freshly new rom
Also you can boot into clockwork and try to run fix permissons
If you don't have custome recovery (clock work) you will need to have eng-bootloader to do fastboot commands to flash recovery
Also have for adb make sure debuggin is on and boot into bootloader from there try to do adb commands there
If your able to do so and get access
You can go into adb shell and remount to rw then push a new SU.apk in and reboot and su should work as well
This if you don't remember commands
Adb shell
Su
#mount -o remount,rw /dev/block/mtdblock3 /system
#
Then exit out of shell then do adb push
Adb push (where ever su user location on pc) /system/app
I installed rom manager by clockworkmod, which I believe is the program you were refering too.
I tried to "fix permissions" and it failed there.
How would I reload the stock ROM?
If I backup the current ROM, and reload it, then it will reload it as it is with SUpermissions already installed.
Where can I find a copy of the stock rom that came on the G2?
BTW
I do have S-off, but I did not install the engineering hboot.
Let me know the best way to go about getting a stock rom put back on.
Do you have clockwork recovery, not rom manager, turn off phone hold vol dwn and power.. you should boot in custome recovery all letters should be orange,
If you have that good! Jus go to dev section and download a stock rom that is rooted put in sdcard and boot in cwm recovery go to back up and restore, do a back up after back up is down do a wip/factory reset, when down click install zip from sdcard, then choose zip from sdcard and look for rom that is in sdcard and flash that.. or you want you could also get cyanogenrom too but also get gapps too
You never answered if you could get to recovery. If you really have soff then your fine. So when your phone boots it says s off correct? And what happens with you hold vol down while booting? Even if you dont have clockwork recovery you can still install the original rom which you can find in the forums.
Sent from my HTC Vision using XDA App
when chick the superuser ,it always display "force close"
but other app can be supported to get root permission by superuser.
but ,
when i get the superuser update in the google market,nightmare coming.
well ,i have the same issue like yours.
i try to fix ti anywhere ,but i flash other rom to replace.
do you have the solution?
shortlived said:
You never answered if you could get to recovery. If you really have soff then your fine. So when your phone boots it says s off correct? And what happens with you hold vol down while booting? Even if you dont have clockwork recovery you can still install the original rom which you can find in the forums.
Sent from my HTC Vision using XDA App
Click to expand...
Click to collapse
I assume that its s-off. The link that I posted the the root method that I used said that it would root with S-off. The only thing I did not do is install the eng hboot. I assume that the root is done with S-off.
I have not had time to sit and try this yet. I will try soon and get back with my results.
ilostchild said:
Do you have clockwork recovery, not rom manager
Click to expand...
Click to collapse
I know at one point I had it, but as I said I factory reset my phone. I want to make sure that I install the correct app, so who manufacturers clockwork?
If you had the cwm recovery b4 and all you did was a factory reset then you should still have it, only time you lose recovery if you update to official rom or you flashed another recovery, clockwork recovery is made my koush, and rom manager is also made by koush
derricks2 said:
So about 2 months ago I rooted my phone. I followed the method here:
http://forum.xda-developers.com/showthread.php?t=928160
Everything was ok, until my super user permissions program stopped working. The program opened but its a solid black screen and I cannot give any new program SU permission. At first the programs that already had permission could still have SU permission, but, in an attempt to fix the issue I cleared the program cache and those programs lost their SU permission(like TT and terminal).
Their is a new SU permissions program on the market that I paid for from the same company but I assume because the old one is still installed that it is not showing up for that reason and cannot be opened.
I cannot figure out how to get rid of the original Superuser Permissions program. I have tried every program I could find by surfing forums, I have factory reset the phone... but that SU permissiosn program is still there upon a clean factory reset!
I have the ADB installed on my PC, but when I try to run a remount I get an error that I am not allowed to do that. After my factory reset I tried running back through the walkthrough I listed. Visionary says its temp rooted, but in terminal the SU command says "access denied." I think this all has to do with that bad SU program being in stalled and if I can get that off and install the replacement one I paid for, then the SU could grant access to terminal and I could re-root the phone.
My theory is only speculation. Can anyone tell me how to remove this SU program. Its located in directories that are read only and all the commands I have found to remove it so far have required a rooted terminal command, or ADB remount commands that I cannot use. Please help. Thanks
Click to expand...
Click to collapse
Try flashing another ROM or a kernel. this could be an error or corruption in the folder located in the root folder of your phone. Flash a new ROM and try it again but set a backup and see if this error continued to another ROM. Hope I helped
ilostchild said:
Do you have clockwork recovery, not rom manager, turn off phone hold vol dwn and power.. you should boot in custome recovery all letters should be orange,
If you have that good! Jus go to dev section and download a stock rom that is rooted put in sdcard and boot in cwm recovery go to back up and restore, do a back up after back up is down do a wip/factory reset, when down click install zip from sdcard, then choose zip from sdcard and look for rom that is in sdcard and flash that.. or you want you could also get cyanogenrom too but also get gapps too
Click to expand...
Click to collapse
When I hold the vol down button the text is in orange.
I will try this process. I am at work and may not have a lot of time here today. If you can point me to where I might find the stock ROM w/ root that would be wonderful.
I assume that rooted version comes with SU and clockwork etc already installed?
ilostchild said:
Do you have clockwork recovery, not rom manager, turn off phone hold vol dwn and power.. you should boot in custome recovery all letters should be orange,
If you have that good! Jus go to dev section and download a stock rom that is rooted put in sdcard and boot in cwm recovery go to back up and restore, do a back up after back up is down do a wip/factory reset, when down click install zip from sdcard, then choose zip from sdcard and look for rom that is in sdcard and flash that.. or you want you could also get cyanogenrom too but also get gapps too
Click to expand...
Click to collapse
Ok... maybe I was mistaken. When I boot into recovery, it says S-off, and the options I have to choose from are orange, but ALL the text is not orange.
When I go through ROM manager to flash a ROM(which is the stock rom i downloaded that I want to flash) it says I need to have CWR installed and to use the option at the top to install it. When I click that it says its asking for permissions to install, which means I need SU permissions, which is my problem in the first place.
I have the rom loaded on my SD. As I said, the 4 options I have in the initial recovery mode are orange(though the rest of the text is now orange) but I do not know which one to choose. Any advice? Do I have clockwork recovery installed? If not, is their any way to flash a ROM?
derricks2 said:
The only thing I did not do is install the eng hboot.
Click to expand...
Click to collapse
Did someone miss this? I thought you had to have the ENG-Hboot?
But, what do I know, I'm a newb.....
this morning was dead at work, so i decided to go ahead and tinker with my phone. i was on 1.8.3, rooted, and running gingerblur 4.5.
i followed the instructions for the bootloader and root, everything went smoothly updating to 2.3.4 at first, but it doesnt seem to hold root. superuser kept corrupting, then when i got that settled, CWM started hanging up, and now when i try to use that, i get an error saying the path is null. aaaand now superuser says my su binaries are out of date. anyone have any idea? i tried searching, but couldnt find anything relative to my problem...
EDIT: super user is jacked up again.. so basicly my phone wont hold root...
EDIT 2: my home key doesnt seem to do anything now either...
Sounds like you did a titanium backup restore on your phone? Try doing a factory reset and try re-rooting the rom you have and give it super user access. A factory reset should work.
Sent from my MB860 using XDA App
i didnt do a titanium backup... but i did just try a factory reset, and i think it bricked my phone... i have the little android guy standing next to the yellow triangle with an exclamation point... now what? lol
can you boot into fastboot or Android Recovery?
yes. should i use android recovery, or reflash 2.3.4 or kenn's alien rom?
PParcells said:
yes. should i use android recovery, or reflash 2.3.4 or kenn's alien rom?
Click to expand...
Click to collapse
who's recovery/CWM are you currently using?
i had the latest of tenfars CWM, but like i said, it kept botching since root wouldnt stick
i seem to be able to access the CWM in android recovery mode though. should i try reflashing kenn's alien rom, or start from scratch with 2.3.4?
Try booting into fastboot mode and trying the command: fastboot -w
Then: fastboot reboot
Does it boot up now? Still have some more stuff to tell you.. just wanted to see if that got the phone booted first.
PParcells said:
i seem to be able to access the CWM in android recovery mode though. should i try reflashing kenn's alien rom, or start from scratch with 2.3.4?
Click to expand...
Click to collapse
Yeah, but can you still put flashable .zip files on your phone, if you can't boot?
it booted up just fine, as if the factory reset did nothing. all my apps and stuff are still there, root still isnt working, and neither is the CWM app in the app drawer. so im not sure if i should try re-rooting again, or what to do. this is weird, i never had any issues fiddling with gingerblur or any of that stuff...
PParcells said:
it booted up just fine, as if the factory reset did nothing. all my apps and stuff are still there, root still isnt working, and neither is the CWM app in the app drawer. so im not sure if i should try re-rooting again, or what to do. this is weird, i never had any issues fiddling with gingerblur or any of that stuff...
Click to expand...
Click to collapse
Ok, here we go...
1) Check to see if you have file "install-recovery.sh" @ /system/etc. If you do, delete it.
2) Uninstall Tefnar's CWM you have installed.
3) Download RomRacer's CWM/Recovery, and install via fastboot, or install via ROM Manager via the instructions in my N00B Guide thread.
4) Once you have RomRacer's CWM installed, boot into CWM and wipe dalvik cache, cache partition and format data.
5) Flash Alien ROM (not theme, just ROM). - Make sure to put this on you phone before booting into CWM and clearing everything; want to flash immediately after clearing things listed in step 4.
6) Reboot and see what you have and if everything is working correctly...
rom manager says i need root. which i dont have. i tried installing via fastboot, but couldnt figure it out. i cant remember if im supposed to use the command prompt, or rsdlite, rsdlite says the CWM zip isnt a valid compressed file...
PParcells said:
rom manager says i need root. which i dont have. i tried installing via fastboot, but couldnt figure it out. i cant remember if im supposed to use the command prompt, or rsdlite, rsdlite says the CWM zip isnt a valid compressed file...
Click to expand...
Click to collapse
Need to use command promt for fastboot... put RomRacer's CWM .img file in the same place as your fastboot files, and then type the commands in Rom Racer's OP, except if your using fastboot, you can ignore the "moto" part of the commands and just type fastboot ....
You need Romracer's fastboot file, which is on the left side... not the flashable .zip file which is for CWM.
you are my new favorite person in the whole wide world. its currently formatting, and i'll be sure to log on in the morning to post my results. but this is far enough for the night i think. im beat. thanks for ALLLL the help and patience!
Oh. I guess I should add this piece of advice since no one else has. Don't get bored at work and try flashing roms. You don't have recovery available or another rom available. I speak from experience.
I voided my warranty.
just wanted to say i have everything up and running. super fast, super smooth, and so far, no errors or issues. thanks alot guys!
Hey guys,
Recently rooted using unrevoked and wifi tether was working but after updating superuser to 3.0.7 tethering no longer works and asks if I have root? It says S-OFF in the bootloader. Tried to run unrevoked again but it failed to get root access. Also tried clearing cache and data but still no luck. Any ideas? Thanks.
Running 2.2
Open the Superuser app and make sure permissions is on, then reboot
still no luck. I tried z4 and temp rooted and it seems to have added the permissions to superuser but after reboot same thing happens. I guess the apps cant see the root?
Might try to downgrade superuser to like su-2.3.6.2-efgh by flashing within recovery and then go back in and updating from market.
If you're S-Off, you don't need to keep trying to root. You're rooted.
What I would do is make sure you have Amon Ra for recovery, wipe everything as outlined in the guide I wrote (link in my sig) and flash a ROM. That will give you SU and you should be fine.
Just clearing Cache and Data is not enough. You need to clear Dalvik Cache, System, etc...
tried this and it didnt work for me.. any other suggestions?
bossman1 said:
tried this and it didnt work for me.. any other suggestions?
Click to expand...
Click to collapse
http://downloads.androidsu.com/superuser/su-bin-3.0.3.2-efghi-signed.zip flash this in recovery
I just flashed a 802d stock ROM through TWRP 2.7 (AutoRec). I started out by wiping dalvik cache, cache and data. I then pressed Install and found the zip and installed that. After it was done, I did a dalvik + cache wipe again just to be safe (It asked if I wanted and I complied). Rebooted into system. It was quite buggy to begin with, so I wanted to try re-flashing, but it looks like my custom recovery has disappeared. I assume my root access went with it.
Everytime I try to get into recovery. It doesn't show the TWRP recovery, but merely ask if I want to factory reset my phone.
Currently, I'm downloading a clean kdz of the 802d ROM (it's taking a while) and aim to start all over with rooting and installing custom recovery and re-installing apps, but if anyone has a different solution, it would be most welcome. I'm quite the noob here. I thought TWRP would be fool-proof and would therefore allow me to restore a backup at any time. But currently, that does not appear to be the case.
Please do prove me wrong
Depends on what custom rom you were installing.
Trixanity said:
I just flashed a 802d stock ROM through TWRP 2.7 (AutoRec). I started out by wiping dalvik cache, cache and data. I then pressed Install and found the zip and installed that. After it was done, I did a dalvik + cache wipe again just to be safe (It asked if I wanted and I complied). Rebooted into system. It was quite buggy to begin with, so I wanted to try re-flashing, but it looks like my custom recovery has disappeared. I assume my root access went with it.
Everytime I try to get into recovery. It doesn't show the TWRP recovery, but merely ask if I want to factory reset my phone.
Currently, I'm downloading a clean kdz of the 802d ROM (it's taking a while) and aim to start all over with rooting and installing custom recovery and re-installing apps, but if anyone has a different solution, it would be most welcome. I'm quite the noob here. I thought TWRP would be fool-proof and would therefore allow me to restore a backup at any time. But currently, that does not appear to be the case.
Please do prove me wrong
Click to expand...
Click to collapse
Ok first if you really do have custom recovery in the factory reset screen clicking the power button three times will boot you into recovery, if you can boot into the Rom then download a root checker app to check if you still have root
Sent from my LG-D800 running stock kk, rooted with philz using XDA app
XxZombiePikachu said:
Ok first if you really do have custom recovery in the factory reset screen clicking the power button three times will boot you into recovery, if you can boot into the Rom then download a root checker app to check if you still have root
Sent from my LG-D800 running stock kk, rooted with philz using XDA app
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2736854 <- this is the ROM I flashed. It's a stock ROM containing the latest d firmware for the D802.
I just checked for root access - it's not there anymore. I will try to boot into recovery now through the method you suggested. I'll edit my post with the results.
Edit: Your method worked My recovery is there. Great! I thought it would boot straight into recovery, so the factory reset option mislead me. Now, I have to ask: did I do anything wrong in my flashing? For example. In the Mount section, only Data and Cache is mounted. Should system be mounted or is it irrelavant? Is there anything in particular I need to do in Wipe? I merely pressed Advanced Wipe and seleceted Dalvik Cache, Data and Cache and swiped to wipe. That's it.
Trixanity said:
http://forum.xda-developers.com/showthread.php?t=2736854 <- this is the ROM I flashed. It's a stock ROM containing the latest d firmware for the D802.
I just checked for root access - it's not there anymore. I will try to boot into recovery now through the method you suggested. I'll edit my post with the results.
Click to expand...
Click to collapse
well if you would have noticed in the install process it states to flash supersu after flashing the rom
XxZombiePikachu said:
well if you would have noticed in the install process it states to flash supersu after flashing the rom
Click to expand...
Click to collapse
Yeah, I did read that. This might sound stupid, but I figured that the listed SuperSU update was meant for people with an older version of SuperSU as in making sure to have the latest version of SuperSU, since I already had the latest version, I neglected to do that step. My bad. I will copy the zip in question to my phone and try re-flash both zips and see what happens. At least I have my backups to fall back on.
Another dumb question if you will. Since I didn't wipe any of my data. My apps are still present in the file system, but they are not installed nor do they have market links. Is there a way to install them or should I try to recover them through Titanium Backup? Or is it easier to simply wipe the data as well and use Titanium Backup to restore my apps?
Trixanity said:
Another dumb question if you will. Since I didn't wipe any of my data. My apps are still present in the file system, but they are not installed nor do they have market links. Is there a way to install them or should I try to recover them through Titanium Backup? Or is it easier to simply wipe the data as well and use Titanium Backup to restore my apps?
Click to expand...
Click to collapse
I think you should wipe and restore from tibu since there isn't a guarantee that redownloading your apps from the playstore will keep there old data
Thank you so much for taking your time to answer my questions. The second flash seemed succesful, but it didn't fix my biggest reason for flashing the ROM in the first place: the hissing audio bug. So I'll just try to do a restore of my latest backup and I'll make do with my temporary fix that actually works.
While it may seem to that I have wasted everyone's time, I think I've learned some valuable lessons, so I don't think it was entirely a bad thing
Hopefully, my restore will be succesful
Trixanity said:
Thank you so much for taking your time to answer my questions. The second flash seemed succesful, but it didn't fix my biggest reason for flashing the ROM in the first place: the hissing audio bug. So I'll just try to do a restore of my latest backup and I'll make do with my temporary fix that actually works.
While it may seem to that I have wasted everyone's time, I think I've learned some valuable lessons, so I don't think it was entirely a bad thing
Hopefully, my restore will be succesful
Click to expand...
Click to collapse
just in case since you don't mention the fix, I know the kk audio bug has a fix with g2tweaksbox over in the faq of first post it explains what needs to be done
XxZombiePikachu said:
just in case since you don't mention the fix, I know the kk audio bug has a fix with g2tweaksbox over in the faq of first post it explains what needs to be done
Click to expand...
Click to collapse
I did try that fix. It didn't remove the hiss entirely for me. Maybe removed 50% of the hiss, but I've heard of it working 100% for a lot of people. I've been using the ELT > Audio Loopback test from the hidden menu. It removes the hiss by about 99%. Only annoying thing is that I need to do it on every reboot which is why I wanted a more permanent fix.
Seems like my restore has caused a bootloop. Everything went accordingly, except the installation of SuperSU afterwards. Kept saying it failed to copy to the system folder despite system being mounted. The bootloop started when trying to boot into system after restore + failed SuperSU installation.
Edit: Fixed the SuperSU failure to install by wiping dalvik etc. but bootloop persists. I somewhat assume this is because the restore function doesn't work when the current ROM is different from the ROM the backup was made with? The backup was made with D802 20b firmware and the current ROM which is the one I flashed was the D802 20d firmware. Am I on to something?
Trixanity said:
I did try that fix. It didn't remove the hiss entirely for me. Maybe removed 50% of the hiss, but I've heard of it working 100% for a lot of people. I've been using the ELT > Audio Loopback test from the hidden menu. It removes the hiss by about 99%. Only annoying thing is that I need to do it on every reboot which is why I wanted a more permanent fix.
Seems like my restore has caused a bootloop. Everything went accordingly, except the installation of SuperSU afterwards. Kept saying it failed to copy to the system folder despite system being mounted. The bootloop started when trying to boot into system after restore + failed SuperSU installation.
Edit: Fixed the SuperSU failure to install by wiping dalvik etc. but bootloop persists. I somewhat assume this is because the restore function doesn't work when the current ROM is different from the ROM the backup was made with? The backup was made with D802 20b firmware and the current ROM which is the one I flashed was the D802 20d firmware. Am I on to something?
Click to expand...
Click to collapse
A backup restore should always work whether different versions or not, are you able to get into download mode?have you tried kdz to stock?
Sent from my LG-D800 running stock kk, rooted with philz using XDA app
XxZombiePikachu said:
A backup restore should always work whether different versions or not, are you able to get into download mode?have you tried kdz to stock?
Sent from my LG-D800 running stock kk, rooted with philz using XDA app
Click to expand...
Click to collapse
I just fixed it by going into recovery and flashing the D802 20d firmware again. It'll do for now. Honestly don't know why the restore from backup didn't work. Either the backup was corrupt or I've done something wrong.
I did restore my apps (so far) flawlessly and the rom does appear to perform similarly to my older firmware. Plus there's added features such as knock code so it's not all bad.
I do have a D802 20d kdz firmware available on my computer in case I want to go completely stock and/or start over. But I'll give this one a try over the next few days and see whether I'll keep this.
Trixanity said:
I just fixed it by going into recovery and flashing the D802 20d firmware again. It'll do for now. Honestly don't know why the restore from backup didn't work. Either the backup was corrupt or I've done something wrong.
I did restore my apps (so far) flawlessly and the rom does appear to perform similarly to my older firmware. Plus there's added features such as knock code so it's not all bad.
I do have a D802 20d kdz firmware available on my computer in case I want to go completely stock and/or start over. But I'll give this one a try over the next few days and see whether I'll keep this.
Click to expand...
Click to collapse
yea I'm still waiting for that knock code update on my g2, times like these make you hate being with carriers