If I had a third leg, I would be kicking myself in the butt right now.
I installed ESET mobile security in my tab. I just did it without reading the reviews because I use it at home and love it. It's the first time and last time that I don't carefully read the reviews.
I left the tab unattended and on for a few hours yesterday and when I picked it up, ESET had locked it. I tried the password and it doesn't work. Yes, I am typing the correct one. I am not the first person to have this problem.
You can add a phone number for a trusted person. The password can be reset by that person but I didn't put a number in. Apparently, if I had done that my friend would have been bombarded with texts saying that my tab had been stolen.
ESET is aware of the problem. There are people on their support forums begging for help and they're not answering.
This is what I have tried so far:
Someone in the ESET forums said to go in through adb and remove the eset.apk file. It is located in /data/app. I can't do that. I typed adb devices and nothing is attached.
I booted into recovery and typed adb devices. It recognizes the device, but won't allow me to run any commands. So, I know that my adb drivers are working.
Any suggestions? I am thinking about wiping it, but that may not work either since it is security software.
Thanks.
Can you run adb shell from recovery?
Boot into recovery and try the adb devices. then type adb root to reboot the daemon with root priv just in case and then try the adb pull /data/app/eset.apk (or whatever it is).
andyharney said:
Can you run adb shell from recovery?
Click to expand...
Click to collapse
No, that's the problem. I can type adb devices in recovery and see the tab, but I can't run any commands. They just hang.
If I type adb devices, I get a number, which is the tab and it says recovery beside that.
If I'm not in recovery and type adb devices, it can't find the tab.
Thanks anyhow.
slimdizzy said:
Boot into recovery and try the adb devices. then type adb root to reboot the daemon with root priv just in case and then try the adb pull /data/app/eset.apk (or whatever it is).
Click to expand...
Click to collapse
Thanks, but adb root just hangs too.
I'm really disappointed with these guys. Apparently, this has been a known issue for months. Why wouldn't they pull the download until it's fixed?
The mod on the ESET forum said to call tech support. I guess that I will have to wait until tomorrow.
Thanks for the help. I'll be back tomorrow after I talk to tech support.
if u ca go through recovery then why u dont wipe the whole damn data ????? then the apk will GONE , correct me if im mistaken , but your problem ain't that hard !!! to use adb >|<
if you can get into recovery, k0sh is right.. just do a data/cache wipe and you should be good to go.
k0sh said:
if u ca go through recovery then why u dont wipe the whole damn data ????? then the apk will GONE , correct me if im mistaken , but your problem ain't that hard !!! to use adb >|<
Click to expand...
Click to collapse
Well, yeah, that's what I ended up doing. I was just hoping that there was some way around this. And quite frankly, I didn't know how persistent the software was. Some of this security software will even survive a wipe.
According to ESET, with some devices, you can simply wipe the data cache from recovery and it will reboot and allow you to change the password. If someone had known that, it would have been much easier than wiping and I could have done it last night. Unfortunately, it didn't work for the Galaxy. I had to get a little uh, assertive to get that out of them. The first guy wouldn't tell me anything. I got that from his supervisor.
No need to be like that. If I could save someone a ton of work, I'd do it, but that's just me.
Anyhow, just stay away from this software. The release candidate is out now and apparently this problem still has to be fixed. Unbelievable. They've been bricking people's stuff for months.
Muttz said:
Well, yeah, that's what I ended up doing. I was just hoping that there was some way around this. And quite frankly, I didn't know how persistent the software was. Some of this security software will even survive a wipe.
According to ESET, with some devices, you can simply wipe the data cache from recovery and it will reboot and allow you to change the password. If someone had known that, it would have been much easier than wiping and I could have done it last night. Unfortunately, it didn't work for the Galaxy. I had to get a little uh, assertive to get that out of them. The first guy wouldn't tell me anything. I got that from his supervisor.
No need to be like that. If I could save someone a ton of work, I'd do it, but that's just me.
Anyhow, just stay away from this software. The release candidate is out now and apparently this problem still has to be fixed. Unbelievable. They've been bricking people's stuff for months.
Click to expand...
Click to collapse
That's seriously sad that a software company would have a known issue like that, and not at least post a warning, or a "if this happens, do this..." think companies gave up having their own Q/A dept's and just push crap software out on their users/customers to "test" then patch after they find out how bad it really is.
pvtjoker42 said:
That's seriously sad that a software company would have a known issue like that, and not at least post a warning, or a "if this happens, do this..." think companies gave up having their own Q/A dept's and just push crap software out on their users/customers to "test" then patch after they find out how bad it really is.
Click to expand...
Click to collapse
AAhhhhhh FFS
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I just googled how to try to do this. And a wipe is what you had to do? Thats just f*cked. This has not been my week seriously! I had to Malware apps on my system (one attempting to send premium sms *hidden* but was showing up in logcat the f%#*ing c*%#t of a thing. I used ESET to get back on my feet, thats all fine and good. I got everything back to square one all working good. Did a backup and everything.....oohh yeah I totally did a backup of ESET installed DIDN'T I!!,
Thats all well and good I removed it......but totally forgot about it being inside my backup. I flashed my own theme that I have been toying with and naturally we all know that if you go forward an Android version you're SOL to try restore aka roll back your system when the system apks have updated the databases.....Thats ok I will just do a restore! I am a good boy and did both a Nandroid backup AND a titanium backup.
Well, Titanium fails because it cannot write data to a newer db either, you short of phyically using root explorer and plonking each of the olver 4.12 databases in each and every app then it ain't guna happen.
So restored from my perfectly good Nandroid backup in recovery and all was sweet as till I a noticed ESET in there. I am like, I will just uninstall it! NOPE!
Guess what. This stupid app has a bug in the reset password. I saved my encrypted password inside of password safe and it still rejects the original password. ADB ignores my commands even in recovery! Actually it is like it processes, but soon as I adb shell, SU, then chdir data/app and then ls I STILL F*%#ING SEE ESET!!!! I even use the exact name I see of com.eset.ems-1.apk
Is there no way to remove this ar$ehole of a thing? Seriously I am so close to loosing it at the moment. I am meant to be working.....and that means building apps! That is my job at the moment....to build apps. And to test them on proper phone before going to Telstra on Wednesday!
I am right royally screwed. The Nandroid that I have is pretty much the only one that I can use too. I cannot affort to do a wipe right now. I can't be fart ar$ing around re-setting up my device. I already wasted time last week doing that after 2 Malware apps got in my system.
Screw you ESET.
Does adb pull actually take the apk from the device or does it pull a copy to the PC? I was under the impressing that adb pull made a copy and adb push overwrites the app?
Heeeeeey!!!! I got it. I will make a dummy apk and push write over the top of this prick and see what happens? Man I am furious right now
---------- Post added at 11:04 PM ---------- Previous post was at 10:38 PM ----------
HHHHOOOOOOORAAAAAAAYYY!!! GONE
ADB doesn't do ****. Simple fix was easy.
I just wrote a script that I flashed from recovery that deletes that sucker.
HTML:
ui_print("Removing ESET");
show_progress(1, 15);
run_program("/sbin/busybox", "mount", "/data");
delete("/data/app/com.eset.ems-1.apk");
delete("/data/app/com.eset.ems.apk");
ui_print("Everything is finished thank f*ck!....Rebooting");
run_program("/sbin/busybox", "umount", "/data");
reboot
Boy I was glad to see no stupid ESET screen when I unlocked my phone!:victory::victory:
My application has stuck unable to uninstall need help .
I just want to ask you that I have also install eset but now its not opening crash to home screen and message will appears unfortunately Eset mobile Security has stopped .can someone please help me. how do I uninstall this application I have gt-19500 rooted . Its very help full for me thanks indeed .
Muttz said:
If I had a third leg, I would be kicking myself in the butt right now.
I installed ESET mobile security in my tab. I just did it without reading the reviews because I use it at home and love it. It's the first time and last time that I don't carefully read the reviews.
I left the tab unattended and on for a few hours yesterday and when I picked it up, ESET had locked it. I tried the password and it doesn't work. Yes, I am typing the correct one. I am not the first person to have this problem.
You can add a phone number for a trusted person. The password can be reset by that person but I didn't put a number in. Apparently, if I had done that my friend would have been bombarded with texts saying that my tab had been stolen.
ESET is aware of the problem. There are people on their support forums begging for help and they're not answering.
This is what I have tried so far:
Someone in the ESET forums said to go in through adb and remove the eset.apk file. It is located in /data/app. I can't do that. I typed adb devices and nothing is attached.
I booted into recovery and typed adb devices. It recognizes the device, but won't allow me to run any commands. So, I know that my adb drivers are working.
Any suggestions? I am thinking about wiping it, but that may not work either since it is security software.
Thanks.
Click to expand...
Click to collapse
Related
Alright I have been reading and trying to root this device for days with no avail, now let me tell you what i did. Before I turned off the phone, you have to literally turn off every wireless connection anything that you connected to at all. Dont turn on air plane mode, just turn off every connection you can. Then What I did was click in the sd card after doing the adb reboot recovery. This worked like a charm. I also edited the drivers of the usb driver file called winusb.inf located at c:\sdk\usb_driver
if you dont have that folder that means you have not installed the usb driver which you can do by opening setup.exe clicking on usb drivers install.
you have to edit the file by including the lines under google nt 86 at end of section
;HTC Incredible
%SingleAdbInterface% = USB_Install, USB\VID_0BB4&PID_0C9E
%CompositeAdbInterface% = USB_Install, USB\VID_0BB4&PID_0C9E&MI_01
%SingleBootLoaderInterface% = USB_Install, USB\VID_0BB4&PID_0C94
also then put the exact same lines under [Google.NTamd64] at end of section.
Next your going to want to save the file. Then go under device manager, update the drivers that you already have with that file located at c:\sdk\usb_drivers.
Restart if it says you have to.
Then next step use the windows application
hxxp://incredible.groove2.net/IncredibleRooter.zip
mdawg made This. extract put file in location under "c:\sdk\tools".
Then boot into recovery mode.
run loop.bat and begin clicking in and out of the sd card until it changes the error from device not found to that great error. then exit out of loop.bat with ctrl+c. and finish with the application by pushing files and updating zip. This is the hardest card to do. But it worked very first time after i tried updating drivers! I got wireless Tether working and sending this from there .
I used windows xp sp3
This method will work with any windows machine.
New!!! Load USB drivers from http://tether.com/a/setup.exe
Make sure you update your drivers in Device Manager and restart if needed. These are same drivers I used first time, I just forgot that I downloaded tether before hand.
If you need help you can locate me on IRC
irc://irc.freenode.net:6667/rootmyincredible
This doesn't help if you cant get the phone into the adb recovery status...
This will help you get the phone into recovery status
Please read and try directions instead of thumbing your nose at me. I have put a lot of time into this and im trying to help. I would like to know if my instructions have helped people so we can try and figure out what exactly it is that helps the device. This helped mine and is considered one of the hardest cards to get working. But please at least try this before I get responses like "this wont help". Your not going to ever get rooted with that attitude.
Re: How to root any htc incredible phone with any SD Card. Full proof instructions!
Thanks for the tips, but I think you need to be more careful about using definite statements like 'any card' and 'any PC'. We know from the unRevoked guys that radios and cards play a role, so you're right there.
-------------------------------------
Sent via the XDA Tapatalk App
I believe that SD card does not matter
Let me tell you, The Unrevoked team is a great team. i give them all credit for actually rooting the device. There is still some bugs, im trying to fix those bugs, and provide help how to do that. And I do believe any card can be done on any pc. If your experiencing problems, i might be able to help. Recovery status is easy to achieve if you follow directions. They are wrong about SD cards playing a role though, this is a misguided conception. As my card is one of the hardest cards to get working and practically no one has it.
blue45 said:
Please read and try directions instead of thumbing your nose at me. I have put a lot of time into this and im trying to help. I would like to know if my instructions have helped people so we can try and figure out what exactly it is that helps the device. This helped mine and is considered one of the hardest cards to get working. But please at least try this before I get responses like "this wont help". Your not going to ever get rooted with that attitude.
Click to expand...
Click to collapse
I've already tried this exact method of getting into adb recovery for like past 2 days, my phone just will not co-operate with me.
The root method with the program is awesome, I told mDawg this in TRC the other night... All i'm saying is it doesn't help people who cant get into adb recovery.
I have all the correct drivers installed, because i can use adb shell and android screen monitor to take screen shots fine when the phone is on.
But my phone will not go into adb recovery no matter what i try, I have tried using 2 different sd cards, 8GB Kingston Class 4 and the 2GB that came with the phone, tried formating in FAT, FAT32, and even filling the cards up with junk.
I'm not shutting you down in anyway, trust me, I would love for this to work for me, but It will not let me into adb recovery no matter what i try, I'm on windows Vista Home 32 and just not having any luck, so you saying this will work every time with any card just isn't true.
Anyways, i hope this does help people.
Sorry to post on both forums, but I'm registered on both just like you, so just put it on both.
No disregards at all honest.
blue45 said:
Let me tell you, The Unrevoked team is a great team. i give them all credit for actually rooting the device. There is still some bugs, im trying to fix those bugs, and provide help how to do that. And I do believe any card can be done on any pc. If your experiencing problems, i might be able to help. Recovery status is easy to achieve if you follow directions. They are wrong about SD cards playing a role though, this is a misguided conception. As my card is one of the hardest cards to get working and practically no one has it.
Click to expand...
Click to collapse
Basically you just got lucky I think, it's happened to others, there is defo something conflicting the results.
might want to change the title of the thread to "Fool Proof" instead of "Full Proof"... otherwise you may be considered a fool for more than one reason.
It is full proof and I will be happy to help anyone who needs it and has windows
please come to irc://irc.freenode.net:6667/rootmyincredible
That is my channel and I will help you!
blue45 said:
They are wrong about SD cards playing a role though, this is a misguided conception. As my card is one of the hardest cards to get working and practically no one has it.
Click to expand...
Click to collapse
There's only one way I will believe this: make a video of you getting shell and rooting without an sdcard in your Incredible.
blue45 said:
please come to irc://irc.freenode.net:6667/rootmyincredible
That is my channel and I will help you!
Click to expand...
Click to collapse
I can on via http://www.droidirc.com/ using your channel, and no one was there, is there another way of getting in, I don't have an IRC client installed atm.
sorry it didn't work for me...the only thing that came close was formatting my card to ext4 but the I had permission issues in linux trying to push the files. That was once and now I can't get into recovery shell again.
pozer69 said:
sorry it didn't work for me...the only thing that came close was formatting my card to ext4 but the I had permission issues in linux trying to push the files. That was once and now I can't get into recovery shell again.
Click to expand...
Click to collapse
Permissions? Writing to SD shouldn't require elevated permissions. Anyhow, set up two partitions on the SDcard: ext4 (or another linux partition, shouldn't matter--try something crazy like XFS or reiserFS , followed by a FAT32 partition. I believe the linux partition should give you the 5s race window you're looking for, then you'll have a mounted FAT32 to put the decoy update.zip which recovery will read from when payload is pushed.
What OS are you using to make ext4? PM me if you have more questions, or my gtalk is rynosaur74. Anyone who has questions can contact me: I was a 5-day headache person until yesterday
FYI Sorry to say it is NOT that easy for me. My sdcards will only work if I leave them out until after I start recovery and insert at the sound. I have tried you method and I don't think I'd call if "Full Proof". I know I have the correct driver and the updated lines in the .inf file, because I have rooted my phone. Unfortunatly, I have to use the card insert method, which is a little tricky.
Nice try but I gotta tell you, I think your title is a little misleading.
immjg said:
FYI Sorry to say it is NOT that easy for me. My sdcards will only work if I leave them out until after I start recovery and insert at the sound. I have tried you method and I don't think I'd call if "Full Proof". I know I have the correct driver and the updated lines in the .inf file, because I have rooted my phone. Unfortunatly, I have to use the card insert method, which is a little tricky.
Nice try but I gotta tell you, I think your title is a little misleading.
Click to expand...
Click to collapse
It's like calling the Titantic an unsinkable ship
I appreciate you taking the time to post, but this method didn't work for me (though none of the others have either). I really do wish there was a fool-proof, non-sd card dependent method
Ive discovered something
Ive found out with most of the people that ive helped in the chat room of mine, that you guys have your drivers wrong installed. See when I go into device manager on my computer it says Android USB Devices- My HTC
Make sure your computer has those drivers just like that.
here is what you should have your computer looks like!
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
No one was in the chat room when I was i there...
im there now
im there now
Team,
This One-Click Root process will copy over the rooted-update.zip or unroot-update.zip file then reboot your phone. Follow the instructions in the CMD prompt that launches.
Credits:
LeshaK at Samdroid: for the original rooted-update.zip.
gunnarhafdal : for creating the Mac GUI for my app.
This has been tested on stock Android 2.1 Eclair only. If you rooted using another process you can use this process to unroot as long as you didnt load a rom that created links to busybox.
For the following models:
GT-I9000
Captivate SHG-I897
Vibrant SGH-959
GT-I9000M
Epic SPH-D700 (Untested but should work like other phones. Post with your results. This is harmless it will either work or it wont. It copies over 3 files to your existing build.)
Rooting adds the following to your system and unrooting removes them:
/system/xbin/busybox (version 1.17.1)
/system/xbin/su
/system/app/Superuser.apk (version 2.3.1)
and links /system/bin/su to /system/xbin/su
More will follow as they are released. PM me to add your Galaxy S Model.
Warning: I am not responsible for bricked phones, rooting can void your warranty....
PC Instructions:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Download the app: GalaxyS_One-Click_Root_All_Models-PC. Or down Below.
Watch the video for the full procedure on The Unlockr.
Video/Procedure Link Click Here
Requirements: Install Link: Dot Net Framework version 4
Rooting Instructions:
1. Make sure your phone is on USB Debug mode: (MENU > Settings > Applications > Developement > USB debugging = Checked )
2. For Windows x86 and x64 systems make sure that the Samsung Drivers are installed. You can get them here.
3. Extract the contents of GalaxyS_Vibrant_One-Click_Root.rar to a folder.
4. Connect your phone to your PC via the USB cable and launch the file "T-Mobile Vibrant One-Click Root.exe" file.
5. Click the "One-Click Root" button. This will launch a command shell follow the instructions in the CMD window.
Mac Instructions:
Download the app: OneClickRootMac. Or Down Below.
It requires Mac OS X 10.5 or higher.
Rooting Instructions:
1. Make sure your phone is on USB Debug mode: (MENU > Settings > Applications > Developement > USB debugging = Checked )
2. Connect the phone to your computer.
3. Click one of the buttons depending on what you want to do.
4. After the phone has rebooted into recovery select "apply sdcard:update.zip" for I9000 and I9000M and choose "Reinstall Packages" for the US models using the volume keys and then press the home button for I9000 and I9000M and the power button on the right top side for US models to start the process.
=====================================================================
Done! You are rooted.
=====================================================================
Un-Rooting Instructions:
To Un-Root follow the same instructions except click on the Un-root button. If you rooted using another process you can use this process to un-root as long as you didnt load a rom that created links to busybox. I would suggest to restore you phone back to stock ROM before even needing to unroot and if you are on stock un-root all you want otherwise what is the point of un-rooting.
=====================================================================
Getting Started with Android After Rooting:
Flash Clockwork Custom Recovery On your phone:
Follow this URL to find fill information on ROM Manager:
http://forum.xda-developers.com/showthread.php?t=734164
Install ROM Manager from Market.
Launch ROM Manager and click on Backup ROM and save you android O/S stock rooted making getting back to stock un-rooted much easier..
the simplest root just got simpler
So is this actually faster? Or just "easier" not to mess up...
sounds like more work than just DLing, moving, and renaming with your phone... expecially for those without a comp...
anyway, this method has been added to the sticky in dev section..
junkdruggler said:
So is this actually faster? Or just "easier" not to mess up...
sounds like more work than just DLing, moving, and renaming with your phone... expecially for those without a comp...
anyway, this method has been added to the sticky in dev section..
Click to expand...
Click to collapse
I'd say its easier to not mess up. Faster for sure, if you already have the drivers installed.
This is for our newer brethren or anyone else that want a straight forward root method. And for those having trouble entering recovery from the button presses. ADB is bundled in the rar file so you don't need Android SDK.
Another thing that will help most is when I add unroot to the app which I should have completed tomorrow.
Doon2 asked for it, so here it is.
I appreciate the effort and skill...
BUT, how is this easier than downloading a file directly to your phone, renaming it and putting it at the root of your sd card and going to recovery?
s15274n said:
I appreciate the effort and skill...
BUT, how is this easier than downloading a file directly to your phone, renaming it and putting it at the root of your sd card and going to recovery?
Click to expand...
Click to collapse
Good question because that is what I do. Just an alternative method. The upcoming unroot will probably be more helpful to some.
But this method will help some for sure. It will download it to your phone for ya and put you in recovery. Well most of the other phones have it so why not ours.
Someone made the request and here it is. I will also be adding other tweaks to the app over time and useful info after rooting to this thread.
Sent from my SGH-T959 using XDA App
TGA_Gunnman said:
Good question because that is what I do. Just an alternative method. The upcoming unroot will probably be more helpful to some.
But this method will help some for sure. It will download it to your phone for ya and put you in recovery. Well all most of the other phones have it so why not ours.
Someone made the request and here it is. I will also be adding other tweaks to the app over time and useful info after rooting to this thread.
Sent from my SGH-T959 using XDA App
Click to expand...
Click to collapse
this
I am stoked that someone would take the time to make this program. I dont have immediate access to a PC(I use a mac) but an easy unroot program clinches the decision to root my phone. thank you for taking the time to make this much props
please do it for Mac OS.
best wishes...
Awesome application thanks!
Sent from my SGH-T959 using XDA App
Great, easy app. Works!
Wish I had seen this a few hours ago! Just spent 30mins trying to get the button presses right to get into recovery mode before I finally got it.
alsatea said:
please do it for Mac OS.
best wishes...
Click to expand...
Click to collapse
Sorry I don't have a Mac to dev/test on. Neither do any of my friends. But, I will see what I can do.
Can't you dual boot windows on your Mac?
TGA_Gunnman said:
Sorry I don't have a Mac to dev/test on. Neither do any of my friends. But, I will see what I can do.
Can't you dual boot windows on your Mac?
Click to expand...
Click to collapse
If you write it in java, then it will run any OS, right?
Relase src code. I may be able to port to unix/macosx and/or java.
I have Windows 7 installed through Bootcamp and it worked perfectly. Thanks
kelmerp said:
If you write it in java, then it will run any OS, right?
Click to expand...
Click to collapse
Ok Let me see what I can do.
Yeah release the source... Ports will follow if necessary
jganyard said:
Wish I had seen this a few hours ago! Just spent 30mins trying to get the button presses right to get into recovery mode before I finally got it.
Click to expand...
Click to collapse
I know what you mean. I'm still used to holding down the buttons until the recovery screen pops up like on my G1. On the Vibrant, I have to remind myself to let go of the buttons as soon as the "Vibrant" screen comes up.
Yes, the overall process involved to use this program is longer, involves more steps, and, therefore, easier to screw up. Also, the fact that you have to download more than one file increases the chances of messing something up because of the possibility of corrupted files. Also, the "flash in recovery" method is OS agnostic, and technically doesn't even require a computer since you can download and rename the zip file right on your phone if you want to. Still, it's very easy to follow and would appeal to those who are new to rooting and don't feel comfortable with booting into recovery mode.
Updated the app to include unroot. Created a new update.zip file that will remove root. Also fixed the CMD shell launching minimized.
Lets see the java port. or even an APK to do so
jganyard said:
Wish I had seen this a few hours ago! Just spent 30mins trying to get the button presses right to get into recovery mode before I finally got it.
Click to expand...
Click to collapse
Why fuss with button pushes, just enable debugging, plug in your phone, open a command prompt and type the following
Code:
adb reboot recovery
It's easier than messing with those buttons I assure you.
Edited 12/30/11:
Thanks to everyone that helped put this together, and I'm glad people found it useful! However, this guide is now obsolete. I put it together before we could unlock the bootloader and get a permanent root. However, we now have a bootloader unlock, so there's a better way to get root. Please see this thread: http:// http://forum.xda-developers.com/showthread.php?t=1416836. I'll leave this guide here in case somebody has such an occasion to need only a temp root.
-----------------------------------------------------------------------------------------------------------------
Edited 11/11/11, 12:23 EST - V2 of Windows script - check for superuser.apk already installed
Edited 11/11/11, 14:42 EST - Linux/Mac script
Edited 11/11/11, 15:58 EST - V3 of Windows script - updated method for installing su binary to attempt to address it disappearing. Please let me know if the issue persists! (Linux script should be updated to V3 soon)
Ok, so I think we've gotten this process streamlined enough to make it easy, so I wanted to put together a step-by-step easy temproot for people who are confused. It will run zergRush to root your phone, then install busybox and the superuser app & binaries.
I've tested this on AT&T's Vivid, and it seems to work on the Canadian variant. Also, supposedly, if you're bootloader's unlocked, this should give you permroot.
I take no credit for actually developing most of this, I just packaged it up all nice and neat in an easy to run batch file. Both Windows & Linux/Mac versions are attached.
Thanks to:
Revolutianry for zergRush, ChainsDD/androidsu.com for SuperUser, stericson for busybox
arunp44, Jimmy273, DooMLoRD, and cyber_pete for some of the right commands
rpendrick for the Linux/Mac version
STEPS TO ROOT:
0. Install HTC Sync on your computer so that you'll have the proper drives
1. Download Vivid-Root.zip: Windows | Linux/Mac
2. Unzip somewhere on your computer
3. On your phone , enable USB Debugging (Settings > Applications > Development, check USB Debugging) & Unknown Sources (Settings > Applications, check Unkown Sources)
4. Connect your phone to the computer, make sure it's in Charge Only mode
5. Open the unzipped folder, double click RUNME.bat & Follow the prompts
6. Enjoy your root!
If you reboot your phone, just repeat steps 4-6.
Please let me know if you have any problems, questions, or concerns!
DISCLAIMER: I've tested this on my device and it works. However, i provide no guarantees or claim no responsibility for problems it may cause (however unlikely that may be). You know, the usual "please don't blame me for bricks...".
KNOWN ISSUES:
-Occasionally Superuser app won't recognize su binary even though phone has root access
-su binary disappears after a while (V3 attempts to fix this)
-zergRush method unmounts internal phone storage (/sdcard folder). Seems its still accessible from adb shell, and nothing seems wrong, but phone can no longer access it properly
Looks promising. Any possibility to repackage for linux and or Mac?
Sent from my HTC PH39100 using xda premium
drewdatrip said:
Looks promising. Any possibility to repackage for linux and or Mac?
Sent from my HTC PH39100 using xda premium
Click to expand...
Click to collapse
Absolutely! It'll just take me a little longer, as I only have access to windows machines at the moment. Perhaps later this afternoon I'll have the chance to port it to linux/mac.
Nice work, I just posted the manual version of this on the other temp root forum. Was going to start to automate but you beat me to it. I love it when there are several people all working towards a solution.
cyber_pete said:
Nice work, I just posted the manual version of this on the other temp root forum. Was going to start to automate but you beat me to it. I love it when there are several people all working towards a solution.
Click to expand...
Click to collapse
Yeah, I saw that. I actually have to thank you, because I was having one minor issue of it not recognizing the su binary, but your code got it working! So thanks!
bjg222 said:
Yeah, I saw that. I actually have to thank you, because I was having one minor issue of it not recognizing the su binary, but your code got it working! So thanks!
Click to expand...
Click to collapse
Team work, that's how we are going to get to perm root.
EDIT:
Just used your script, worked perfect. One suggestion. What do you think about adding a check for the SuperUser.apk and if it is already there, skip the install? I already have it installed and got the Failed message, might scare a few people. Anyway just a suggestion, great work.
Nice job man. This will def help out people new to the rooting world.
Question... If I use supercharger v6 to emprove my ram after I reboot will it still. E in effect?
Sent from my HTC PH39100 using xda premium
cyber_pete said:
Team work, that's how we are going to get to perm root.
EDIT:
Just used your script, worked perfect. One suggestion. What do you think about adding a check for the SuperUser.apk and if it is already there, skip the install? I already have it installed and got the Failed message, might scare a few people. Anyway just a suggestion, great work.
Click to expand...
Click to collapse
Sure, I'll work on that and get it up in a bit.
tacotino said:
Question... If I use supercharger v6 to emprove my ram after I reboot will it still. E in effect?
Sent from my HTC PH39100 using xda premium
Click to expand...
Click to collapse
Having never used the app, I couldn't tell you. But typically on reboot, you lose everything root-related, so my guess would be no.
In-app root
Is anyone working on an in-app temp root app (z4root anyone?)
If I change LCD density while temp rooted, will it survive reboot?
I really am considering this temp root cause I find bloatware annoying.... But if I can switch lcd density while im at it, that will make three decision much easier
Sent from my HTC Vivid using Tapatalk
How long should this process take?? Mine is just showing *daemon started successfully* for a few minutes.
ronj1986 said:
How long should this process take?? Mine is just showing *daemon started successfully* for a few minutes.
Click to expand...
Click to collapse
Should take a few seconds, less than a minute overall.
---------- Post added at 06:55 PM ---------- Previous post was at 06:52 PM ----------
After running this I tried opening Titanium Backup and it said no root. I did try earlier old temp root method without success, could that be the reason?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Well it is a good sign that we have temp-root so quick now HTC just needs to stop dragging their feet a bit and get this bootloader unlocked.
My device driver "did not install properly", maybe that's what's causing the *daemon started successfully* Ronj is having
I am hoping installing HTC Sync will fix hat little issue.
It is. I installed HTC Sync, and the problem went away
ronj1986 said:
It is. I installed HTC Sync, and the problem went away
Click to expand...
Click to collapse
figured... the Dell streak had a step like that too.
I am unable to install Titanium Backup:-(((
For those of you that have temp root working, are you losing root after a short amount of time? I keep losing the SU binary, root is still there but I have to repush SU. Really strange. Does anyone know if this is just the nature of temp root or is there something I can do to fix that?
So here's what's up....
I hold down power + home buttonn = gets stuck at Cyanogenmod Loading Screen.
I hold down power + up + USB cord in = giant white usb logo
I hold down power + down = nothing (weird, right?)
I can run ACMEInstaller, but it gets stuck at "Can't find CM .zip folder on media partition" (not the exact wording, but you get the idea).
I can't seem to do anything else though.....What do I do now?
Note - I have the latest TWRP installed, I just can't find a way to get to it....
in order to flash a new moboot bootloader or recovery or rom with acmeinstaller2 you need to have those .zip files in a folder called cminstall on the touchpads internal memory. are you able to get an ./adb connection when youre stuck at the cyanogenmod screen?
haxin said:
in order to flash a new moboot bootloader or recovery or rom with acmeinstaller2 you need to have those .zip files in a folder called cminstall on the touchpads internal memory. are you able to get an ./adb connection when youre stuck at the cyanogenmod screen?
Click to expand...
Click to collapse
I've been messing around with drivers and stuff for like 2hrs now....no adb connection yet
On my Device Manager it comes up under 'Portable Devices' as "MTP USB Device", but it has a triangle with an exclamation mark on it......also my ADB does not recognize it in when it's in the Cyanogenmod Loading screen, or USB mode.
I tested my ADB (first time every using it today) with my Evo, and it was recognized right away, so it does work.
I googled a lot of stuff about the touchpad drivers and such, and tried many different things....however I have no luck (yet). Any ideas?
Also added this picture:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
tm21fourt3 said:
I've been messing around with drivers and stuff for like 2hrs now....no adb connection yet
On my Device Manager it comes up under 'Portable Devices' as "MTP USB Device", but it has a triangle with an exclamation mark on it......also my ADB does not recognize it in when it's in the Cyanogenmod Loading screen, or USB mode.
I tested my ADB (first time every using it today) with my Evo, and it was recognized right away, so it does work.
I googled a lot of stuff about the touchpad drivers and such, and tried many different things....however I have no luck (yet). Any ideas?
Also added this picture:
Click to expand...
Click to collapse
ok this is why i hate windows. i used to be a total windows fanboy till i started getting into android hacking. everything is sooooo much better in linux.
ok anyways, since youre stuck using this windows box. you need to make sure youve got some things in line.
do you have the latest android-sdk installed on your computer?
what version of windows are you on?
is moboot working properly when you boot up the touchpad?
are you able to boot into webos at all?
are you able to establish a novaterm connection?
this should have been fixed by now, but you need to be clear on what exactly does, and does not work and what exactly you have and have not tried.
when you say "Can't find CM .zip folder on media partition" (not the exact wording, but you get the idea)
or
I've been messing around with drivers and stuff for like 2hrs now....no adb connection yet
exact messages that you get from the computer and device are important.
exact steps that you've done already are important too.
also one more question. was the touchpad like this when you got it?
if not then what was it you did to make it like this?
and when you say "i tested my ADB" does that mean you were able to actually get an adb connection in the command prompt or does that mean you saw an ADB device show up in the device manager?
haxin said:
do you have the latest android-sdk installed on your computer?
Yes, made sure everything was up to date
Click to expand...
Click to collapse
haxin said:
what version of windows are you on?
Click to expand...
Click to collapse
7
haxin said:
is moboot working properly when you boot up the touchpad?
Click to expand...
Click to collapse
I have it on the touchpad, but can't seem to access it.
haxin said:
are you able to boot into webos at all?
Click to expand...
Click to collapse
Can't seem to get that either
haxin said:
are you able to establish a novaterm connection?
Click to expand...
Click to collapse
I actually have to Google that, no idea what that means
haxin said:
this should have been fixed by now, but you need to be clear on what exactly does, and does not work and what exactly you have and have not tried.
when you say "Can't find CM .zip folder on media partition" (not the exact wording, but you get the idea)
or
I've been messing around with drivers and stuff for like 2hrs now....no adb connection yet
exact messages that you get from the computer and device are important.
exact steps that you've done already are important too.
Click to expand...
Click to collapse
The partition quote was actually very close to being correct. It just basically meant that the file wasn't there like you said.
haxin said:
also one more question. was the touchpad like this when you got it?
if not then what was it you did to make it like this?
Click to expand...
Click to collapse
I've had the touchpad since they first went on sale. It's been running CM since it was released as well. I was doing some searching a few nights ago and saw someone posted a Wifi fixer on here and with me being half asleep I decided to try it.
I downloaded it, went to TWRP, the directions were to wipe delvik cache, install zip. Upon installation it said error. So I backed out and went to reboot it. That's when it got stuck.
haxin said:
and when you say "i tested my ADB" does that mean you were able to actually get an adb connection in the command prompt or does that mean you saw an ADB device show up in the device manager?
Click to expand...
Click to collapse
It means that after I did all of the ADB steps I plugged in the touchpad, no luck there in the loading screen or the usb screen...... I plugged in my EVO 4G LTE.
My test was to open the cmd prompt in the sdk folder, and type in "adb devices".... When the touchpad was plugged in the response was "no adb devices found". But with the evo plugged in it showed the series of numbers and definitely indicated that the phone was found.
Is it simply a driver problem?.....
I've been googling touchpad drivers, but nothing seems to help me out.
Sent from my EVO using xda app-developers app
haxin said:
ok this is why i hate windows. i used to be a total windows fanboy till i started getting into android hacking. everything is sooooo much better in linux.
ok anyways, since youre stuck using this windows box. you need to make sure youve got some things in line.
do you have the latest android-sdk installed on your computer?
what version of windows are you on?
is moboot working properly when you boot up the touchpad?
are you able to boot into webos at all?
are you able to establish a novaterm connection?
this should have been fixed by now, but you need to be clear on what exactly does, and does not work and what exactly you have and have not tried.
when you say "Can't find CM .zip folder on media partition" (not the exact wording, but you get the idea)
or
I've been messing around with drivers and stuff for like 2hrs now....no adb connection yet
exact messages that you get from the computer and device are important.
exact steps that you've done already are important too.
also one more question. was the touchpad like this when you got it?
if not then what was it you did to make it like this?
and when you say "i tested my ADB" does that mean you were able to actually get an adb connection in the command prompt or does that mean you saw an ADB device show up in the device manager?
Click to expand...
Click to collapse
Just figured it out....I CAN get a novaterm connection.....I've been googling and youtubing it, but I can't seem to find (yet) a way to push files to the touchpad through novaterm though.....is there a way?
Anything?.....thanks.
tm21fourt3 said:
Note - I have the latest TWRP installed, I just can't find a way to get to it....
Click to expand...
Click to collapse
v2.3? That might be your problem... Someone else here said the latest TWRP is not Touchpad-compatible.
EDIT: here. He's not fixed yet, but that might be because of another problem. Try the solutions posted. http://forum.xda-developers.com/showthread.php?t=1934490.
bananagranola said:
v2.3? That might be your problem... Someone else here said the latest TWRP is not Touchpad-compatible.
EDIT: here. He's not fixed yet, but that might be because of another problem. Try the solutions posted. http://forum.xda-developers.com/showthread.php?t=1934490.
Click to expand...
Click to collapse
I appreciate that.... But I cannot boot into anything but cm, and I can't actually get to cm because it's not installed.
I can't get to moboot for whatever reason. And I can't get to recovery.
I can however get a novaterm connection, and cannot (yet) get a adb connection.
If I could simply get to recovery all of my issues would be solved.
Can I push files to the touchpad using novaterm? Or can someone help me get an adb connection?
Sent from my EVO using xda app-developers app
tm21fourt3 said:
I appreciate that.... But I cannot boot into anything but cm, and I can't actually get to cm because it's not installed.
I can't get to moboot for whatever reason. And I can't get to recovery.
I can however get a novaterm connection, and cannot (yet) get a adb connection.
If I could simply get to recovery all of my issues would be solved.
Can I push files to the touchpad using novaterm? Or can someone help me get an adb connection?
Sent from my EVO using xda app-developers app
Click to expand...
Click to collapse
Sorry about that; I must have missed that in your posts. Unfortunately, that's all I've got. Hopefully someone else with more knowledge will come along.
You can use Novaterm to run AcmeUninstaller. This will remove moboot. You can then boot into WebOS. From there. Make a cminstall directory under media. Put Moboot, cwm, twrp, update*.zip, etc. in that directory. Then, you can run Acmeinstaller2 (or 3) using novacom. This will get you running again. Your next boot should give you the option of getting to recovery through moboot. It should also retain all you old data and settings (I'm not sure about settings, but media and sdcard should be untouched).
Hope this helps.
drmarble said:
You can use Novaterm to run AcmeUninstaller. This will remove moboot. You can then boot into WebOS. From there. Make a cminstall directory under media. Put Moboot, cwm, twrp, update*.zip, etc. in that directory. Then, you can run Acmeinstaller2 (or 3) using novacom. This will get you running again. Your next boot should give you the option of getting to recovery through moboot. It should also retain all you old data and settings (I'm not sure about settings, but media and sdcard should be untouched).
Hope this helps.
Click to expand...
Click to collapse
Thanks man.... I'll try this as soon as possible and let you know the results.
Sent from my EVO using xda app-developers app
tm21fourt3 said:
So here's what's up....
I hold down power + home buttonn = gets stuck at Cyanogenmod Loading Screen.
I hold down power + up + USB cord in = giant white usb logo
I hold down power + down = nothing (weird, right?)
I can run ACMEInstaller, but it gets stuck at "Can't find CM .zip folder on media partition" (not the exact wording, but you get the idea).
I can't seem to do anything else though.....What do I do now?
Note - I have the latest TWRP installed, I just can't find a way to get to it....
Click to expand...
Click to collapse
Take a look at this thread : http://forum.xda-developers.com/showthread.php?t=1426244
Page 12 sounds like it could solve your problem. Read the whole thing.
Good luck.
Edit : I like cwm better than twrp. I've had problems with it.
So recently I ran into a problem where installing certain apps causes bootloop for me, such as:
SimSocial ( https://play.google.com/store/apps/details?id=it.rignanese.leo.slimfacebook )
Camera Roll - Gallery ( https://play.google.com/store/apps/details?id=us.koller.cameraroll )
Twidere for Twitter ( https://play.google.com/store/apps/details?id=org.mariotaku.twidere )
After installing the above apps, the launcher crashes, then the phone reboots itself. After restarting, the same thing happens again. The only way to end it is to remove the app using the recovery.
The problem seems to be very similar to the one described here
After some research, the problem seems to be caused by this
Someone made a fix here, but apparently it's made for the Moto G, and it doesn't work on Xperia SP (I've tried, the phone can't even boot afterwards)
I have no idea how to implement the fix myself because I'm a noob to all of this.
Does anyone have an idea on how to fix this without upgrading to a newer version of android?
The rom I'm using is Candy5 ( https://forum.xda-developers.com/xperia-sp/development/rom-candy5-t3196185 ), if that does any help.
Try "Low-RAM Property Patcher" by AdrianDC. Maybe it will work in "Candy".
ze7zez said:
Try "Low-RAM Property Patcher" by AdrianDC. Maybe it will work in "Candy".
Click to expand...
Click to collapse
Just tried and it didn't work. The amount of ram doesn't seem to be related to my issue too :/
Each time, on a clean ROM, install each application separately and save the logcat after running it.
When you do this, try different installation order of subsequent applications.
In this way, you have the chance to find out which application is causing problems.
ze7zez said:
Each time, on a clean ROM, install each application separately and save the logcat after running it.
When you do this, try different installation order of subsequent applications.
In this way, you have the chance to find out which application is causing problems.
Click to expand...
Click to collapse
I have tried a number of apps and found the apps I mentioned above cause the exact same problem. They cannot run at all. In fact the phone starts crashing right after finishing the installation. I have tried it on a completely clean rom installation too, and the same thing happens. I will try to get a logcat tommorow though.
You are correct about the bootloop. It affects old rom, pre-CM 13. I have applied the patch you have mentioned a few weeks ago and it did work on my phone, Samsung Galaxy S3 AT&T. I have shared the solution at the proper threads: https://forum.xda-developers.com/showpost.php?p=76721233&postcount=1215.
I think if you want to patch yourself, you might want to look at this. It's for KitKat but I think it should work on Lollipop.
https://forum.xda-developers.com/showpost.php?p=75958727&postcount=184
nehc_rm said:
You are correct about the bootloop. It affects old rom, pre-CM 13. I have applied the patch you have mentioned a few weeks ago and it did work on my phone, Samsung Galaxy S3 AT&T. I have shared the solution at the proper threads: https://forum.xda-developers.com/showpost.php?p=76721233&postcount=1215.
I think if you want to patch yourself, you might want to look at this. It's for KitKat but I think it should work on Lollipop.
https://forum.xda-developers.com/showpost.php?p=75958727&postcount=184
Click to expand...
Click to collapse
Yes I have tried the first solution in your post before making this thread. Unfortunately it caused bootloop (or stuck at the sony logo screen, I can't remember which). I'll try and see if I can get the second solution in your post to work though. Thanks for your reply.
Are there really no other solutions? I've been searching for months and everyone just link the same zip that doesn't work on Xperia SP.
steveglowplunk said:
Are there really no other solutions? I've been searching for months and everyone just link the same zip that doesn't work on Xperia SP.
Click to expand...
Click to collapse
The only options you do have is to do a edit with hex editor. The patch is specific to rom and os version. The person who made this patch did a good job on documenting the steps. https://forum.xda-developers.com/showpost.php?p=77174238&postcount=188
I think I have seen 3 different patches: KitKat, Lollipop, Marshmallow. Patch needs to be applied to proper OS.
I have finally fixed it by following the guide here ( https://forum.xda-developers.com/showpost.php?p=75958727&postcount=184 )
The guide only tells you how to disassemble the libandroidfw.so, but it didn't say how you can "reassemble" it. So I used another software called Binary Ninjia ( https://binary.ninja/demo/ ) to edit it, and it worked! (and yes the demo is enough already)
Tell me if you want the detailed steps on how I did it (I don't think many people still use CM 12.1 on their Xperia SP anyway so I'm not going write it now unless someone asks so)
steveglowplunk said:
I have finally fixed it by following the guide here ( https://forum.xda-developers.com/showpost.php?p=75958727&postcount=184 )
The guide only tells you how to disassemble the libandroidfw.so, but it didn't say how you can "reassemble" it. So I used another software called Binary Ninjia ( https://binary.ninja/demo/ ) to edit it, and it worked! (and yes the demo is enough already)
Tell me if you want the detailed steps on how I did it (I don't think many people still use CM 12.1 on their Xperia SP anyway so I'm not going write it now unless someone asks so)
Click to expand...
Click to collapse
I am glad you've fixed your phone. I was lucky enough that the patch worked on my phone. It's not an easy bug to fix. I am wondering how many people do know about this bug.
If you want to post the guide is up to you. But I think it's worth documenting everything. You never know who might need it.
Looking for this some help
I wouldn't mind a walkthrough on it (if you still remember/have it around)?
I'm trying to patch this for an older phone I have that only supports CM12.1 and it's a pain.
MattEffinTurner said:
I wouldn't mind a walkthrough on it (if you still remember/have it around)?
I'm trying to patch this for an older phone I have that only supports CM12.1 and it's a pain.
Click to expand...
Click to collapse
So obviously you'll need root access (which you should have already if you're using a custom rom anyway), and a pc
ALWAYS MAKE A NANDROID BACKUP FIRST, you never know if things will go wrong
Now install the Binary Ninjia demo ( https://binary.ninja/demo/ ) (There are other disassemblers but this one is what I used in my case, and the demo is free)
Afterwards, everything is basically just following the guide here ( https://forum.xda-developers.com/showpost.php?p=75958727&postcount=184 )
1. Get the libandroidfw.so from "/system/lib" somehow. The guide suggested using adb pull but you can also use whatever root browser of your preference to copy it out and send it to your pc with bluetooth or something
2. Open your libandroidfw.so in Binary Ninjia
3. Open "android::AssetManager::getPkgName(char const*)" on the left by double clicking on it
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Make sure it's set to "Disassembly Graph" at the bottom left
4. Right click on the highlighted line (the code "movs r3,#0") - Patch - Edit Current Line
5. Change the 0 to 1 instead and press enter
6. In the top toolbar, go to to File - Save and save it...somewhere
7. Send the edited libandroidfw.so back to your phone with adb push or bluetooth or whatever method you prefer
8. On the phone, with a root browser or a terminal emulator, copy the edited libandroidfw.so to "/system/lib" and replace the original one
You'll need to remount /system as rw first to be able to successfully replace it
I prefer using the terminal emulator so I'll use this method for demonstration. In the terminal emulator, enter these commands
Code:
su
mount -o remount,rw /system
cp /path/to/<your edited libandroidfw.so> /system/lib
9. Set its permission to -rw-r--r--
If you use a terminal emulator, use the following command to set its permission (in case if you don't know how)
Code:
chmod 644 "/system/lib/libandroidfw.so"
10. Reboot and pray you haven't broken your phone
11. If it boots up, you should be able to live happily ever after with the bootloop crash problem gone
I can't send my edited libandroidfw.so as the fix seems to be rom and device specific. But I hope my guide is clear enough for you to fix the problem on your own. :fingers-crossed:
Excellent!
Thank you so much for this!
After several hours of fighting with it yesterday (and lots of Google-fu) I finally managed to patch the file (and all for the sake of changing a 0 to a 1 in a library file).
Once I get enough posts in, I'll be able to post the patched file for my ROM in it's thread (though I doubt anyone's still using it at this point, lol)
MattEffinTurner said:
Thank you so much for this!
After several hours of fighting with it yesterday (and lots of Google-fu) I finally managed to patch the file (and all for the sake of changing a 0 to a 1 in a library file).
Once I get enough posts in, I'll be able to post the patched file for my ROM in it's thread (though I doubt anyone's still using it at this point, lol)
Click to expand...
Click to collapse
I'm glad to hear you have fixed this annoying problem too.
Just out of interest, was your method similar to mine?
steveglowplunk said:
I'm glad to hear you have fixed this annoying problem too.
Just out of interest, was your method similar to mine?
Click to expand...
Click to collapse
Yes, it was pretty well identical to your method (I used adb push/pull to move the file off and back on).
I knew what I was looking for in the file but it took some time to figure out how to use Binary Ninja.