Hello.
I have Tablet S 4.0.3 R5, successfully rooted with this instrutions:
http://forum.xda-developers.com/showthread.php?t=1887447
Everything worked great until for unknown reason home screen would FC on boot (titanium backup showed that there was sony.nfx.automatiocvolumecontrol deleted, not sure how and why)
So I've tried ALLinONE v4.1 "Install "rescue-backdoor" [anti-bootloop protection]." after reboot it showed update available, which I pressed update, it rebooted into recovery, did it thing (no messages, just progress bar with 3 dots on top), then it booted into system, home app FC still was FC. Root was gone too. So I did another reboot, home screen still was FC, but root came back (I was pleasantly surprised) and also received a message that update failed with error code 0.
Now everytime I reboot it shows this update message, if I attempt install it, on first reboot nothing happens, no new updates available, but after second reboot it shows error message about failed update and offer download and install this update again.
Any ideas how I can fix this or even how can I return to virgin stock if possible?
Thank you.
In the allione tool pick disable update notificatin that will fix the update message
Sent from my Sony Tablet S using xda app-developers app
It's not the fix of the problem, it's like removing check engine light bulb instead of fixing the engine
In the root install instructions there was a step to backup system partition with:
Code:
dd if=/dev/block/mmcblk0p3 of=/mnt/sdcard/system.ext4 bs=128K
How do I flash this file back into partition? Do I just swap if with of?
Code:
dd if=/mnt/sdcard/system.ext4 of=/dev/block/mmcblk0p3 bs=128K
?
Dude he installed rescue backdoor which makes his system think hes on 3.2.1 there is no update so taking the system update off by allvin one makes more sense
Sent from my LT28i using xda app-developers app
Oh, ok, I see now. Thank you.
Dont forget to click the thanks button have a good day cheerssss!!!!
Sent from my Sony Tablet S using xda app-developers app
Ok, what the f.k is going on with this damn tablet. Now I loose root every other reboot:
reboot = no root, next reboot = root works fine, next reboot no root again, and so on. The superuser also disappears and appears after each other reboot.
Jeez...any way revert it to stock with no root and no that back door rescue and start over?
Tried flash OTA full update via recovery, but even though it seemed to be successful it didn't help.
Thanks.
[email protected] said:
Ok, what the f.k is going on with this damn tablet. Now I loose root every other reboot:
reboot = no root, next reboot = root works fine, next reboot no root again, and so on. The superuser also disappears and appears after each other reboot.
Jeez...any way revert it to stock with no root and no that back door rescue and start over?
Tried flash OTA full update via recovery, but even though it seemed to be successful it didn't help.
Thanks.
Click to expand...
Click to collapse
I had same problem.... see here.
Can someone with unmodified (maybe root required though) tablet pull system partition and share please?
with this adb shell command
Code:
dd if=/dev/block/mmcblk0p3 of=/mnt/sdcard/system.ext4 bs=128K
Thank you.
Attach ure log man
Sent from my Sony Tablet S using xda app-developers app
Ops, my bad, I meant to reply to my other topic:
http://forum.xda-developers.com/showthread.php?t=2028484
Related
Hi,
I'm using CM 7.03 on my Legend and it was working really good.
However yesterday i was stupid enough to install an update of superuser.
After this update root access was still functioning but i was getting a "su binary is outdated" message.
So i tried to update this,but the update failed.
So i went into rom manager,downloaded Super User 3 and flashed it,i shouldn't have done this.
After phone booted my root access was gone,and whenever a program asked root access it showed a forced close window of the su app.
My question now is....can i fix this without reflashing the device.
Keep in mind that rom manager isn't working and i can't boot into clockworkmod.
I also tried softrooting in order to gain access to the file system but this also failed.
Any help would be greatly appriciated.
Thanks!
Edit: Just a brainfart,but would it work if i copied the correct superuser version to my goldcard,rename it to update.zip and flash it?
try to update to the latest superuser..
btw.. you are on which cm7?
before this.. im on cm nightly 195.. got some error when updating superuser binary..
but now im on latest cm nightly with updated superuser from market.. successful update the binary through the superuser setting interface..
i had the same problem & was able to fix it after the same steps you've taken by installing the superuser.apk from the flashing-.zip file again. there have been updates of superuser application in the market since, maybe they will fix the problem too...
Rom Manager has the superuser 2.x,too.You can download it and reboot into recovery, flash the bag( at /sdcard/clockworkmod/download/goo-inside.me/superuser/(THE SU YOU WANT TO FLASH).ZIP
Flash it and the root access will back~
ps.It seems cm 7 haven't supported su3.0....About 1 month ago, I flashed the su 3.0 and it always told me access deny...Finally I have to flash the su 2.x back...
About the recovery,you can plug the phone to computer and in recovery mode(HAVE A RED ALERT TRIANGLE), run the recovery-windows.bat( it is in the r3(or 4)-legend-root.zip), and you can flash anything you want.The HTC raw recovery( with only 4 items)cannot flash the su package even with the goldcard....
Sent from my HTC Legend using xda premium
Hi,
thanks for the advice.
I'm gonna try to reflash the correct superuser.zip,that's how i wrecked it in the first place.
Also i didn't know it was impossible to do this with the raw HTC recovery so i will use the suggested batch file.
Thanks a lot guys,i'll come back and post my results.
My fix
Had the same problem on a nightly.
I did just download su-3.0.2-efgh-signed.zip from superuser website and flashed it and then it worked fine after that.
[SOLVED] CM7 lost root access after su update
Well,it isn't going like it should.
I just can't get into recovery.
I'm trying in VMware,running Windows XP (it never worked before on Win 7 x64),i've installed the correct version of HTC sync but when i run recovery-windows.bat (from hack4legend) i just keep getting errors...
failed to copy files etc/mtab.... (file system read only)
--install: applet not found.
nohup: appending....
Can't figure out what i'm doing wrong,it look like it needs root access but that's what i'm trying to fix.
Help?
Edit: Whoops,forgot about the red triangle...i can get into recovery now.
Edit2: Just flashed the correct su.zip and root access is restored!!!
Thanks a million guys!!!!!!
Sorry...but are there any screenshots?
Edit :errr...yes,you must get into the red triangle screen....
Glad to help~
Sent from my HTC Legend using xda premium
scx110a said:
Sorry...but are there any screenshots?
Edit :errr...yes,you must get into the red triangle screen....
Glad to help~
Sent from my HTC Legend using xda premium
Click to expand...
Click to collapse
It worked!
Thank you!
I had a similar problem:I installed the new su version (on cm7).everything worked fine but than I stucked on my boot img. but I have restored my nandroid backup successfully
Sent from my Legend using XDA App
Glad to hear you fixed your problem to.
scx110a said:
Rom Manager has the superuser 2.x,too.You can download it and reboot into recovery, flash the bag( at /sdcard/clockworkmod/download/goo-inside.me/superuser/(THE SU YOU WANT TO FLASH).ZIP
Flash it and the root access will back~
ps.It seems cm 7 haven't supported su3.0....About 1 month ago, I flashed the su 3.0 and it always told me access deny...Finally I have to flash the su 2.x back...
About the recovery,you can plug the phone to computer and in recovery mode(HAVE A RED ALERT TRIANGLE), run the recovery-windows.bat( it is in the r3(or 4)-legend-root.zip), and you can flash anything you want.The HTC raw recovery( with only 4 items)cannot flash the su package even with the goldcard....
Sent from my HTC Legend using xda premium
Click to expand...
Click to collapse
Thanks, same problem with update to cyanogen 7.35 flashed the 2.x and back to root agiain on my legend thanks alot!!!
Im trying just this. But where did you find that su.zip???
edit: ****ing YES! I did flash the: su-3.0.2-efgh-signed.zip and now i have rooot. thanks. im out
Software v1.4.0
Root messed up in middle of running nookandzergy.bat. Got to the part where it says GG Rooted or whatever and it wouldn't go past that (I allowed ample time for reboot of device also). Apparently it thinks it's rooted but gapps and launcher weren't installed. I tried doing the 1 click unroot, the zip file to sd card, nomoarzergys, erase/restore and failed boot restore multiple times and it still seems to think i have a root on the tablet
When I try 1 click unroot it wont let me run it as a superuser and I get a could not echojava.lo.ioexception: error running exec(). Command: [su] working Directory: null environment: null error
When I try nomoarzergys I get error: device not found rooting to unroot! error: device not found
Any help would be appreciated.
I have read that the failed boot has to function correctly 8 times in a row to work take you back to stock. Did you go that many times. I'm interested as mine is under the tree and rooting is the first thing I will do.
miniblue said:
I have read that the failed boot has to function correctly 8 times in a row to work take you back to stock. Did you go that many times. I'm interested as mine is under the tree and rooting is the first thing I will do.
Click to expand...
Click to collapse
This is correct. The 9th boot it will automatically go into a full reset mode. You have to release the n button on that time round too.
if failed boot restore doesnt work, manually download and install super user apk and then use unroot app.
dodgepot said:
This is correct. The 9th boot it will automatically go into a full reset mode. You have to release the n button on that time round too.
Click to expand...
Click to collapse
+1 on using the 9th boot method. Other unrooting strats did not work for me.
Additionally, if you followed Indirect's rooting directions, make sure you have the updated rooting script file.
miniblue said:
the failed boot has to function correctly 8 times in a row to work take you back to stock. Did you go that many times.
Click to expand...
Click to collapse
Mine did a factory restore after 2 failed boots. Assuming I'm doing it correctly. Powered off then upon restart I held power and home to turn off and then it asks me if i would like to restore. It is still recognized as being rooted though.
dodgepot said:
Additionally, if you followed Indirect's rooting directions, make sure you have the updated rooting script file.
Click to expand...
Click to collapse
Yep, it is updated
albertwertz said:
if failed boot restore doesnt work, manually download and install super user apk and then use unroot app
Click to expand...
Click to collapse
Upon restore I can get the rooting script to re-root the nook but super user apk doesn't work. I even tried deleting super user and reinstalling and every time I try the unroot.apk i dont have an option to run as super user.
I have tried the unroot script also but it doesnt detect a root installation.
sounds like you never rooted then. Make sure when you tried to run the root process, you actually extracted the files and ran them in the location you extracted them to
vickca86 said:
Mine did a factory restore after 2 failed boots. Assuming I'm doing it correctly. Powered off then upon restart I held power and home to turn off and then it asks me if i would like to restore. It is still recognized as being rooted though.
Yep, it is updated
Upon restore I can get the rooting script to re-root the nook but super user apk doesn't work. I even tried deleting super user and reinstalling and every time I try the unroot.apk i dont have an option to run as super user.
I have tried the unroot script also but it doesnt detect a root installation.
Click to expand...
Click to collapse
It was likely the data wipe, because the factory restore doesn't kick in until 9th or 10th forced reset/boot interrupt. I'd try again for the restore.
albertwertz said:
sounds like you never rooted then. Make sure when you tried to run the root process, you actually extracted the files and ran them in the location you extracted them to
Click to expand...
Click to collapse
Well, I know it was rooted bc I was using adw launcher and was able to install the unroot.apk
HMG10 said:
It was likely the data wipe, because the factory restore doesn't kick in until 9th or 10th forced reset/boot interrupt. I'd try again for the restore.
Click to expand...
Click to collapse
You're right, I see that now, finally got the factory restore. Going from there to try to asses whether or not the root is still on there.
vickca86 said:
Well, I know it was rooted bc I was using adw launcher and was able to install the unroot.apk
You're right, I see that now, finally got the factory restore. Going from there to try to asses whether or not the root is still on there.
Click to expand...
Click to collapse
After a factory restore, root is gone. You have to start over for the root process, and customizing/loading apps. Just pretend you opened it up out of the packaging brand new, and go from there.
Rooting was successful, tested unroot.apk just to make sure superuser permissions worked and it did. I'm good to go.
Thanks for the help guys, miniblue my confusion about factory restore was that I kept getting a prompt to restore after doing the boot process kill 2 or 3 times and I was doing that instead of going to 8 boot process kills and letting it automatically do a factory restore.
vickca86 said:
Rooting was successful, tested unroot.apk just to make sure superuser permissions worked and it did. I'm good to go.
Thanks for the help guys, miniblue my confusion about factory restore was that I kept getting a prompt to restore after doing the boot process kill 2 or 3 times and I was doing that instead of going to 8 boot process kills and letting it automatically do a factory restore.
Click to expand...
Click to collapse
Yeah, the data wipe, which I've been calling a factory reset, only clears user data and deregisters the device. A factory restore basically fixes most problems short of messing with the hardware itself.
So I used the rooting guide at http://forum.xda-developers.com/showthread.php?t=1996389 and found a different superuser/busybox package to use. (don't remember the link right now).
However, whenever I open SuperSU to try to update it, it says installation failed or just reboots. And if I try to use root things for AdFree, it can't find the partition or just restarts.
Is anyone else having this problem or is there a different SU package I should use? My bootloader IS unlocked.
xDexter said:
So I used the rooting guide at http://forum.xda-developers.com/showthread.php?t=1996389 and found a different superuser/busybox package to use. (don't remember the link right now).
However, whenever I open SuperSU to try to update it, it says installation failed or just reboots. And if I try to use root things for AdFree, it can't find the partition or just restarts.
Is anyone else having this problem or is there a different SU package I should use? My bootloader IS unlocked.
Click to expand...
Click to collapse
Ive been using ViperDNA which comes with what seems like a custom SuperUser type of all in it.
But when I origionally rooted my phone, i seem to remember having an issue with SuperSU, and the first time i rooted i said screw it and just installed Superuser without any problems. The second time i rooted, i Installed SuperSU, then had to download Superuser form the Android Market, to update the binary, which updated it for SuperSU, and that solved my problem.
When you try to open an app that needs to use root access, do you get the notification asking for permission?
perhaps the "other" superSU/busybox package that you used didn't properly do what it needed to do?
I see the link on that tutorial is broken, fortunately i have the file that i originally downloaded form that very same tutorial saved to my hard drive, and now uploaded to DropBox if you would like to download it and try flashing this zip while in recovery to see if it gives you a proper root.
I would recommend downloading the above file, and flashing that to see if it helps. I'll try to remember to check back here to see if you posted anything in reply, but let me know if it doesn't work. Ill try to help as much as I can
BigRed35m said:
I would recommend downloading the above file, and flashing that to see if it helps. I'll try to remember to check back here to see if you posted anything in reply, but let me know if it doesn't work. Ill try to help as much as I can
Click to expand...
Click to collapse
I installed your package, and get the same errors before in SuperSU. It wants to upgrade but then force restarts whilst trying.
I then tried the Superuser app by Chainsdd, and I make a little progress?
First, when I try to upgrade, it asks for root from SuperSU and Superuser. Since SuperSU came with the busybox package, I can't uninstall it.
When I first go to the updater, it shows me this: (See attachment 1, I can't do links :S)
After I upgrade it, I am left with this screen: (see attachment 2)
It looks like it reverts back to su v .98 from 1.02?
Either way, as soon as I hit lets do it again, the phone restarts. Did I screw up the unlock/root somehow? In the top left of my fastboot screen it shows ***TAMPERED*** and ***UNLOCKED***
I am using CWM 6.0.2.1
BigRed35m said:
When you try to open an app that needs to use root access, do you get the notification asking for permission?
Click to expand...
Click to collapse
If I do it right when I reboot my phone it usually asks correctly
Thanks again for the help so far!
xDexter said:
I installed your package, and get the same errors before in SuperSU. It wants to upgrade but then force restarts whilst trying.
I then tried the Superuser app by Chainsdd, and I make a little progress?
First, when I try to upgrade, it asks for root from SuperSU and Superuser. Since SuperSU came with the busybox package, I can't uninstall it.
When I first go to the updater, it shows me this: (See attachment 1, I can't do links :S)
After I upgrade it, I am left with this screen: (see attachment 2)
It looks like it reverts back to su v .98 from 1.02?
Either way, as soon as I hit lets do it again, the phone restarts. Did I screw up the unlock/root somehow? In the top left of my fastboot screen it shows ***TAMPERED*** and ***UNLOCKED***
I am using CWM 6.0.2.1
If I do it right when I reboot my phone it usually asks correctly
Thanks again for the help so far!
Click to expand...
Click to collapse
It's difficult for me to troubleshoot when i haven't had to fix this problem since december haha.
The tampered, and unlocked is standard that is what it shows for everyone who unlocked the boot-loader.
So let me get this straight,
Do me a favor, un-install Superuser, download RootChecker from the market by JoeyKrim, And run it, what does it say?
->When you run it, did it ask for permission from SuperSU?
With just the SuperSU installed, if you run a program that requires root permission (For example, RootChecker), Nothing shows up asking if you want to Allow/Deny?
->When you open SuperSU to update the binary, it fails to update and restarts the APP?
With the SuperSU/BusyBox package flashed, when you install Superuser from the android market and try to update the binary, it *appears* to revert back to an older version of the binary?
-> After updating the binary through Superuser (despite the appparent reversion), if you un-install Superuser, and try to run RootChecker, does it work?
Sorry, i know it is a lot and i'm not much help, i'm troubleshooting blindly and from a distance haha.
xDexter said:
So I used the rooting guide at http://forum.xda-developers.com/showthread.php?t=1996389 and found a different superuser/busybox package to use. (don't remember the link right now).
However, whenever I open SuperSU to try to update it, it says installation failed or just reboots. And if I try to use root things for AdFree, it can't find the partition or just restarts.
Is anyone else having this problem or is there a different SU package I should use? My bootloader IS unlocked.
Click to expand...
Click to collapse
you need to install a kernel with /system writing enabled. Such as lk's or cubed
htc has a line wrong in their code and it makes it so that /system cant be edited while booted into android, only while in recovery. Installing a kernel that fixed this bug will let you use supersu from the play store and other apps such as adfree which need to edit system files to function
Bigandrewgold said:
you need to install a kernel with /system writing enabled. Such as lk's or cubed
htc has a line wrong in their code and it makes it so that /system cant be edited while booted into android, only while in recovery. Installing a kernel that fixed this bug will let you use supersu from the play store and other apps such as adfree which need to edit system files to function
Click to expand...
Click to collapse
Yeah this is what I figured out too.
Sent from my HTC6435LVW using XDA Premium HD app
Even with a writeable kernel SuperSu gives a hiccup at first. Download SuperUser, update the binary of SuperSu, then uninstall SuperUser. SuperSu will be fine after that.
orangechoochoo said:
Even with a writeable kernel SuperSu gives a hiccup at first. Download SuperUser, update the binary of SuperSu, then uninstall SuperUser. SuperSu will be fine after that.
Click to expand...
Click to collapse
I never had an issue with supersu
Sent from my HTC6435LVW using xda app-developers app
Bigandrewgold said:
I never had an issue with supersu
Sent from my HTC6435LVW using xda app-developers app
Click to expand...
Click to collapse
Quite a few of us running a version of Supercharged Hatka had problems when they switched to SuperSu,but now they switched back to SuperUser and the problem hasn't reared its head.
Hi,
I'm not a newbie to Android by any measure, but this is my wife's phone, not mine (I have a Nexus 4) so I'm not familiar with a lot of the LG stuff.
Anyways, I rooted her phone to get rid of some of the bloatware and the stupid Qslide thing, and also to edit the build.prop so Netflix will have the Chromecast button. I had deleted quite a few bloatware system apps, and rebooted, everything was fine. I deleted a few more, then edited the build.prop. Rebooted.
Now it shows the LG logo, but then the screen goes blank, but is still on (you can see the backlight) and never boots. I only removed a few more of the LG and Tmobile apps and edited the model and manufacturer in the build.prop
Do I have any easy options to fix this? Or do I need to flash the KDZ?
Flash kdz then install cwm then backup the stock ROM THEN do your mods. Every time every phone. Good luck
Sent from my LG-P769(20F) using the xda-developers app. If I helped you please hit the "thanks" button.
swm5126 said:
Hi,
I'm not a newbie to Android by any measure, but this is my wife's phone, not mine (I have a Nexus 4) so I'm not familiar with a lot of the LG stuff.
Anyways, I rooted her phone to get rid of some of the bloatware and the stupid Qslide thing, and also to edit the build.prop so Netflix will have the Chromecast button. I had deleted quite a few bloatware system apps, and rebooted, everything was fine. I deleted a few more, then edited the build.prop. Rebooted.
Now it shows the LG logo, but then the screen goes blank, but is still on (you can see the backlight) and never boots. I only removed a few more of the LG and Tmobile apps and edited the model and manufacturer in the build.prop
Do I have any easy options to fix this? Or do I need to flash the KDZ?
Click to expand...
Click to collapse
Yes, offline flash the kdz. Always backup your rom whenever you so something like that.
Sent from my LG-P769 using Tapatalk 4
If it's just the build.prop causing it not to boot, you can flash (with fastboot) the boot.img for the kdz you are on. Look at my signature on how to extract it.
If that doesn't work, flash the ice cream x & u partitions for p769 in fastboot, and then run offline flash
Fastboot info and help
http://forum.xda-developers.com/showthread.php?p=43703982
Install the locked bootloader cwm
http://forum.xda-developers.com/showthread.php?t=2095825
And use this busybox
https://play.google.com/store/apps/details?id=com.bitcubate.root.busybox.complete
Next time make a backup (make sure the backup is good, try to restore it)
CM 10.1 P769
kuma82 said:
If it's just the build.prop causing it not to boot, you can flash (with fastboot) the boot.img for the kdz you are on. Look at my signature on how to extract it.
If that doesn't work, flash the ice cream x & u partitions for p769 in fastboot, and then run offline flash
Fastboot info and help
http://forum.xda-developers.com/showthread.php?p=43703982
Install the locked bootloader cwm
http://forum.xda-developers.com/showthread.php?t=2095825
And use this busybox
https://play.google.com/store/apps/details?id=com.bitcubate.root.busybox.complete
Next time make a backup (make sure the backup is good, try to restore it)
CM 10.1 P769
Click to expand...
Click to collapse
Get outta here kuma, no one wants you here. -___- lol im jk.
Sent from my LG-P769 using Tapatalk 4
Lol, okay
NOT!
CM 10.1 P769
kuma82 said:
Lol, okay
NOT!
CM 10.1 P769
Click to expand...
Click to collapse
Thanks for the suggestions guys. I've tried the offline KDZ flashing it, but I can't get my computer (tried two actually, mine and my wife's laptop) to do anything once its in the S/W Upgrade mode. I used the method previously to update her phone the JB when Tmobile pulled the update. Since then it downloaded the most recent OTA. But anyways, I don't know why it wont work. It just continally tells me that my phone isn't connected, even though I'm using the latest drivers and the phone shows up correctly in the device manager. It's driving me nuts since it worked previously!
Any ideas?
swm5126 said:
Thanks for the suggestions guys. I've tried the offline KDZ flashing it, but I can't get my computer (tried two actually, mine and my wife's laptop) to do anything once its in the S/W Upgrade mode. I used the method previously to update her phone the JB when Tmobile pulled the update. Since then it downloaded the most recent OTA. But anyways, I don't know why it wont work. It just continally tells me that my phone isn't connected, even though I'm using the latest drivers and the phone shows up correctly in the device manager. It's driving me nuts since it worked previously!
Any ideas?
Click to expand...
Click to collapse
What variant do you have 769? Flash recovery.img in fastboot.
Sent from my LG-P769 using Tapatalk 4
swm5126 said:
Hi,
I'm not a newbie to Android by any measure, but this is my wife's phone, not mine (I have a Nexus 4) so I'm not familiar with a lot of the LG stuff.
Anyways, I rooted her phone to get rid of some of the bloatware and the stupid Qslide thing, and also to edit the build.prop so Netflix will have the Chromecast button. I had deleted quite a few bloatware system apps, and rebooted, everything was fine. I deleted a few more, then edited the build.prop. Rebooted.
Now it shows the LG logo, but then the screen goes blank, but is still on (you can see the backlight) and never boots. I only removed a few more of the LG and Tmobile apps and edited the model and manufacturer in the build.prop
Do I have any easy options to fix this? Or do I need to flash the KDZ?
Click to expand...
Click to collapse
boot into stock recovery "vol+"&"home"+"power"
adb should work and you can :
adb push busybox /tmp
adb push build.prop /tmp
adb shell
try "su" or "/system/bin/su" or "/system/xbin/su"
chmod 755 /tmp/busybox
/tmp/busybox mount -o remount,rw -t auto /system
/tmp/busybox cp /tmp/build.prop /system
/tmp/busybox chmod 644 /system/build.prop
swm5126 said:
Thanks for the suggestions guys. I've tried the offline KDZ flashing it, but I can't get my computer (tried two actually, mine and my wife's laptop) to do anything once its in the S/W Upgrade mode. I used the method previously to update her phone the JB when Tmobile pulled the update. Since then it downloaded the most recent OTA. But anyways, I don't know why it wont work. It just continally tells me that my phone isn't connected, even though I'm using the latest drivers and the phone shows up correctly in the device manager. It's driving me nuts since it worked previously!
Any ideas?
Click to expand...
Click to collapse
Sorry I didn't break it down enough for you. You have to get fastboot up and running. Jellybean does not operate when starting in S/W mode, that's why you get the connection problem. Now ice cream, does operate when starting in the S/W upgrade mode. With fastboot you can flash everything you need to get the offline flash working. These three links are all the info you need.
Lelus fastboot
Select the option to flash x & u for p769
1. http://forum.xda-developers.com/showthread.php?p=41768774
Help if you can't get fastboot installed
2. http://forum.xda-developers.com/showpost.php?p=43210006&postcount=15
Info on how to use fastboot manually. Not really needed because lelus has everything needed in the first link.
3. http://forum.xda-developers.com/showthread.php?p=43642515
Please read each thread before starting and read the instructions txt found in Lelus fastboot zip
Sorry I told you flashing the boot.IMG will help(was thinking of default.prop), I just remembered the build.prop is in the system partition.
CM 10.1 P769
---------- Post added at 11:00 PM ---------- Previous post was at 10:52 PM ----------
Lelus said:
boot into stock recovery "vol+"&"home"+"power"
adb should work and you can :
adb push busybox /tmp
adb push build.prop /tmp
adb shell
try "su" or "/system/bin/su" or "/system/xbin/su"
chmod 755 /tmp/busybox
/tmp/busybox mount -o remount,rw -t auto /system
/tmp/busybox cp /tmp/build.prop /system
/tmp/busybox chmod 644 /system/build.prop
Click to expand...
Click to collapse
Thanks for sharing, I didn't know stock recovery allowed ADB commands :thumbup:
CM 10.1 P769
swm5126 said:
Hi,
Do I have any easy options to fix this? Or do I need to flash the KDZ?
Click to expand...
Click to collapse
Factory LG mobile support tool has an option to "update recovery" in top right menu. This will download latest factory rom via internet and reflash phone in software update mode to reset everything.
http://www.softpedia.com/get/Mobile-Phone-Tools/Others/LGMobile-Support-Tool.shtml
Works well.
might have to set phone into software update mode by pressing vol up and then inserting usb cable..
kuma82 said:
Please read each thread before starting and read the instructions txt found in Lelus fastboot zip
Click to expand...
Click to collapse
Ok, I got the timing down and fastboot seems to come up, but after I can see the logo on my phone with the v 0.5, the script just says < waiting for device >. Thats where it should flash the ICS xloader? Or am I missing something and I should flash the JB images with fastboot? Where can I get the images?
swm5126 said:
Ok, I got the timing down and fastboot seems to come up, but after I can see the logo on my phone with the v 0.5, the script just says < waiting for device >. Thats where it should flash the ICS xloader? Or am I missing something and I should flash the JB images with fastboot? Where can I get the images?
Click to expand...
Click to collapse
Just kidding, got it figured out. Flashed the ICS xloader. Looks like its letting me restore finally! Thanks!
It's been a long time since I've rooted a phone, and I used to be fairly good at it... as in I usually don't have problems.
I've managed to get TWRP recovery, I've flashed Magisk and SuperUser and the phhSuperUser.
Once the phone boots I can open the SuperUser app without issues. I've moved files to the System folder with ES Explorer.
BUT, after a couple minutes, or instantly after I try to use something like Titanium Backup, the permissions toast message from SU keeps popping up and when I open SU it says something about not being able to flash binaries and "this is a bad thing". At this point if I try to do something that requires root access it fails. Can someone tell me what I'm missing here?
thefatalepic said:
It's been a long time since I've rooted a phone, and I used to be fairly good at it... as in I usually don't have problems.
I've managed to get TWRP recovery, I've flashed Magisk and SuperUser and the phhSuperUser.
Once the phone boots I can open the SuperUser app without issues. I've moved files to the System folder with ES Explorer.
BUT, after a couple minutes, or instantly after I try to use something like Titanium Backup, the permissions toast message from SU keeps popping up and when I open SU it says something about not being able to flash binaries and "this is a bad thing". At this point if I try to do something that requires root access it fails. Can someone tell me what I'm missing here?
Click to expand...
Click to collapse
May you post some screenshots?
Pretty much stuck here. I did a factory reset, then tried flashing supersu again. Tried flashing Magisk and phh SU. Tried flashing an older supersu, reflashed the current supersu. Before I had root for a few minutes at least. Now I can't root at all...
Edit: using TWRP Recovery by the way.
Edit: it's messing up at "decompressing ramdisk , failed"
Are you on MM or Nougat?
I'm still on 6.0.1
thefatalepic said:
...
Edit: it's messing up at "decompressing ramdisk , failed"
Click to expand...
Click to collapse
I need a screenshot of this... take a pic of it.
enetec said:
I need a screenshot of this... take a pic of it.
Click to expand...
Click to collapse
I don't really have a way of doing that, I saw someone else post it verbatim if that helps...
*****Boot image patcher*****
- Finding boot image
--- Boot image: /dev/block/mmcb1k0p33
- Extracting ramdisk
- Decompressing ramdisk
--- Failure, aborting
Note, it may say someone else after boot image on mine, but this is basically what I see...
thefatalepic said:
I don't really have a way of doing that, I saw someone else post it verbatim if that helps...
*****Boot image patcher*****
- Finding boot image
--- Boot image: /dev/block/mmcb1k0p33
- Extracting ramdisk
- Decompressing ramdisk
--- Failure, aborting
Note, it may say someone else after boot image on mine, but this is basically what I see...
Click to expand...
Click to collapse
Problem seems to be here...
I would reflash original boot.img (do you have a twrp backup of it still untouched?) and then retry to root using my "hacking experiences" tips...