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.
Related
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.
MOD EDIT: Full Root is now available. Please see this for Full Root
[GUIDE] One Click How to Root the Wildfire with Unrevoked 3.21
Hi all,
As posted the other day, I have managed to get a temporary software-only root solution that will allow you to run some applications that require su. I am currently in discussion with some of the unrEVOked team to take this a step further and get the NAND protection defeated, clockworkmod etc. For now, though, I present an extremely simple, low risk, software root. Yes, it's not quite 1-click (it's 1-click once you've done the initial steps), but it's pretty easy.
Prerequisites:
You must have adb working.
Root instructions:
Step 1: Download and install Superuser.apk from the Market. ( http://forum.xda-developers.com/showthread.php?t=682828 )
Step 2: Download my SoftRoot package ( http://www.martineve.com/wildfiresoftrootoneclick/SoftRoot.apk )
Step 3: Execute from a command prompt in the directory where you downloaded SoftRoot.apk:
Windows:
adb install SoftRoot.apk
Linux:
adb install ./SoftRoot.apk
Step 4: Run the SoftRoot application that is now installed.
The application will now crash. Wait 2 seconds, close it and you are rooted.
You will need to re-perform stage 4, only, each time you reboot.
Source code (all GPL):
http://www.martineve.com/wildfiresoftrootoneclick/DoRoot.java
http://www.martineve.com/wildfiresoftrootoneclick/R.java
http://www.martineve.com/wildfiresoftrootoneclick/rootshell
http://www.martineve.com/wildfiresoftrootoneclick/exploid.c
To compile Java app, you will need to create a project that has su, rootshell and compiled exploid inside the resources/raw folder.
Works great. Thank you.
Now I have access to paid apps easily via Market Enabler (v3.0.8). I've missed them.
Now I just hope Spotify will fix their playback issues og Wildfire (and Hero). THEN life will be good again.
MartinEve said:
Hi all,
I am currently in discussion with some of the unrEVOked team to take this a step further and get the NAND protection defeated, clockworkmod etc.To compile Java app, you will need to create a project that has su, rootshell and compiled exploid inside the resources/raw folder.
Click to expand...
Click to collapse
Hey Martin Awesome dude .. also where did u find contact info of unrevoked team.. I think Koush is here on xda.. it would be really nice if you can PM me ..
Thanks
Hi, Martin awesome work.. its working superb on my
0.802, 1.14.405.2, VodafoneCZ
thx man!
Excellent work, thanks Martin! So this means I don't have to follow anything in your other thread, I can just use this? Found it difficult to understand all that stuff!
Also, when downloading the Android SDK, as I'm about to, do I need to get the 2.1 component package as well, being as the Wildfire comes with 2.1 on it? Very new to the world of Android, so your help would be much appreciated!
normally you just need the adb not the whole SDK.
Simple to use :
download SDK :http://developer.android.com/sdk/index.html
extract the zip(or tgz if Linux) where you want
go to tools
copy the SoftRoot.apk in this dir
open a cmd prompt
type adb install ./SoftRoot.apk
Install the SuperUser.apk (http://forum.xda-developers.com/showthread.php?t=682828) or QR code :
{
"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"
}
Launch the SoftRoot app.
Wait 10 sec
Kill it
SOFT-ROOTED
Easy no ?
grate job Matrin, any idea's, plan's to bypass "mtdblock3" writing protection.
Dark_Balor said:
Easy no ?
Click to expand...
Click to collapse
Yeah I suppose it is! Thanks for that Balor
Dr_Death said:
grate job Matrin, any idea's, plan's to bypass "mtdblock3" writing protection.
Click to expand...
Click to collapse
Working on it; first job is, apparently, to build a clockworkmod recovery image from the stock rom...
Thread Stickied!
Great job MartinEve. Nice way to start off your experience here at XDA. Cheers
MartinEve said:
Working on it; first job is, apparently, to build a clockworkmod recovery image from the stock rom...
Click to expand...
Click to collapse
all the best my friend, YOU ARE THE MAN
what's the method you are going to try to bypass the protection >> I'm interested in knowing the mechanism of the NAND protection, how it's work
Well, from the fact I was told to make a clockworkmod recovery image, it seems that the route is going to be to get a custom recovery image booting which will allow full access to the system and then flash from that.
TBH, this is where it starts to get risky ;/ If people wanted to start pooling together a disaster fund should the Bricking Gods not smile favourably on me, I'd be a lot happier! Haha!
Hey Martin..or anyone else..can you confirm whether this will work on HTC Legend ..??
zabaknilesh said:
Hey Martin..or anyone else..can you confirm whether this will work on HTC Legend ..??
Click to expand...
Click to collapse
I'm afraid I don't know about the Legend, but I see no reason why it should not provided that:
/system is mounted from /dev/block/mtdblock3
You are running 2.1 or 2.2
If you get an adb shell up an paste me the output of the mount command, I'll be able to tell you more clearly.
MartinEve, I just copied the two .apk to my phone
1.Install with some explorer
2.Launch SoftRoot
3.Enjoy
no adb at all for me and worked
demolition23 said:
MartinEve, I just copied the two .apk to my phone
1.Install with some explorer
2.Launch SoftRoot
3.Enjoy
no adb at all for me and worked
Click to expand...
Click to collapse
Excellent, glad to hear it
Perhaps I'll put a more concise set of instructions up at the start
not work
I managed to do ROOT previous method. In this method, the system aborts SoftRoot. What could be the reason?
Piron said:
I managed to do ROOT previous method. In this method, the system aborts SoftRoot. What could be the reason?
Click to expand...
Click to collapse
When you say "the system aborts", I think you are referring to the fact the application crashes.
Which was in my original post.
It should still be rooted, despite the crash.
MartinEve said:
Excellent, glad to hear it
Perhaps I'll put a more concise set of instructions up at the start
Click to expand...
Click to collapse
Glad...I think its working!! i can now use set cpu...
Only did install these two apk's on HTC legend and its working...!!!
any others signs to confirm check that my device is rooted..please advice which is best apk to check my legend is rooted or not..?
zabaknilesh said:
Glad...I think its working!! i can now use set cpu...
Only did install these two apk's on HTC legend and its working...!!!
any others signs to confirm check that my device is rooted..please advice which is best apk to check my legend is rooted or not..?
Click to expand...
Click to collapse
Go to a terminal and type:
su
If the phone then prompts you to allow root, allow it and then type:
id
if it says uid=0 then you are root.
Let me know and I'll make a post in the Legend forum too.
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
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?
Greetings,
This is a rooted Rom for the Lenovo Ideapad K1. It also includes CWM version 5.5.0.4.
Original Thread at Rootz
-Already rooted with the latest version of Superuser.apk
-Google Apps
-build.prop changes to spoof Motorola Xoom (Was missing many apps from the market before, i.e. GTA III)
-Lenovo Market Removed
-Based off the 14_14_120109 US update
-Android Terminal Emulator
-OI File Manager
-Reboot to Recovery Widget/App
-init.d support
{
"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"
}
Flash at your own risk. I am in no way responsible for any damage done to your device. This will wipe your entire device except the EXTERNAL sdcard.
If you are using Windows make sure you have installed the APX drivers before continuing.
Nvflash Windows Drivers
md5sum: 9aa3a4814ca63366329d85a22ed01f64
To boot into APX mode
1. Power off
2. Hold down the Vol - and the Vol +
3. While holding the Volume keys down, Power on
4. The display should go black, and both LED's on either side of the home button should light up. This is APX mode. If using Windows make sure the drivers are installed
Instructions
Windows
1. Extract the K1_Stock_120109_nvflash_R2.zip contents to a directory
2. Double click the "flash-windows.bat" file
Linux
1. Extract the K1_Stock_120109_nvflash_R2.zip contents to a directory
2. Open a terminal and cd into the extracted directory
3. Copy and paste the following command
Code:
chmod a+x ./flash-linux.sh && chmod a+x ./files/nvflash
4. Run either
Code:
sudo ./flash-linux.sh
or from a root prompt
Code:
./flash-linux.sh
CWM Controls
Power = Back (Any submenu), Toggle Display (Main Menu),
Vol+ = Highlight Up
Vol- = Highlight Down
Home = Select
To boot into recovery
You can now use the built in app or widget to reboot to recovery
**Superuser may crash during the first couple of reboots to recovery. Dont worry
Or run 'k1recovery' from the terminal or adb
Notes
If you try to flash any of the OTA update.zip's, it will probably work, but you will be shut out of CWM and will not be able to get back in unless you reflash everything via nvflash
Downloads
K1_CWM_120109_Rooted_nvflash_R2.zip
md5: dc5264c761e96f9fb9f240924cf60217
K1_CWM_120109_M_GE_Rooted.zip
md5: 280e18ecf837bf030f0a0fe83ec3e824
updater_120109_R2.zip
md5: 48cb5fefac3dcfcb89cddde501ac3e27
updater_120109_M_GE_R2.zip
md5: ef45437e57d257e54054cf9b70a0fcd8
Honeycomb_statusbar_120109.zip - Idea by Shaztech
md5: df290cfd0125f1dde2255a8518cd493f
Restores the default Honeycomb Status Bar, with the favorites button hidden.
To Install:
1. Put the Honeycomb_statusbar_120109.zip on the external sd card storage (Internal will not work)
2. Boot into recovery (via Widget or App)
3. Go to install .zip from sdcard
4. Choose Honeycomb_statusbar_120109.zip and flash.
ThirdPartyAppsRestore.zip - People report loosing market apps after using this. Removing link until I have time to test
md5: dd3ed7584c4c4813277ec96f55e4023a
Restores all the third party apps that came with the stock Rom.
To install:
1. Put the ThirdPartyAppsRestore.zip on the external sd card storage (Internal will not work)
2. Boot into recovery (via Widget or App)
3. Go to install .zip from sdcard
4. Choose ThirdPartyAppsRestore.zip and flash.
If you want to remove any of the third party apps you can remove the apk from /data/app/temp
The device tree used to port CWM is posted in my github.
http://github.com/khanning
I will be in Freenode IRC room #ideapad-k1 if anyone wants to discuss development and to answer any questions.
Flashing this ROM. Finally taking a plunge to root the device - can't wait!
So far, the process has been simple and sweet - hope the entire flashing and post flashing process experience is sweet too!!
Thanks Khanning for such a quick turn-around to my request
---------- Post added at 02:59 AM ---------- Previous post was at 02:45 AM ----------
Ok, it really was extremely simple. I'm rooted with a 14_14 and EXTREMELY happy! This opens multiple doors for me with this device now. Thanks again Khanning - you'r the man!!
Thanks for the heads up, will try this out on mine, it has been quite limiting so far....
Any idea on how to change the country? Am in the UK so rather connect to the UK market etc.... Thanks
Hi, I got a European IdeaPad with integrated HSDPA and after flashing your rom, it doesn't show the 3g connectivity anymore, what can I do?
Please help!
Edit:
I also can't restore the original OTA .zip download from Lenovo because thet ablet isn't recognized as a K1 anymore! :'(
twe69 said:
Thanks for the heads up, will try this out on mine, it has been quite limiting so far....
Any idea on how to change the country? Am in the UK so rather connect to the UK market etc.... Thanks
Click to expand...
Click to collapse
Try Market Enabler, that might help with the market region, although not sure since that probably uses gsm values to trick the market..
Sent from my HTC Vision
Adrixan said:
Hi, I got a European IdeaPad with integrated HSDPA and after flashing your rom, it doesn't show the 3g connectivity anymore, what can I do?
Please help!
Edit:
I also can't restore the original OTA .zip download from Lenovo because thet ablet isn't recognized as a K1 anymore! :'(
Click to expand...
Click to collapse
That's because on this ROM, the tablet is cloaked to work as a Xoom tablet for full app compatibility on the market. If you can change that on the build.prop (I think that's where it is) manually, it should accept it.
Although like I was told the OTA aren't full version of the ROMS, you might want to find and use the full version? Just a thought - more experienced users can give better suggestions.
Sent from my HTC Vision
rezapatel said:
Try Market Enabler, that might help with the market region, although not sure since that probably uses gsm values to trick the market..
Sent from my HTC Vision
Click to expand...
Click to collapse
Will try that as is, since it currently thinks I am in America etc....
This includes google maps.... It will start off in USA then jump to the UK.....
Some websites seem to go to .com instead of sticking to co.uk......
Summer time started at the weekend here but the tablet did not change the time.....
Any idea what I can do for those problems? Thanks.....
twe69 said:
Will try that as is, since it currently thinks I am in America etc....
This includes google maps.... It will start off in USA then jump to the UK.....
Some websites seem to go to .com instead of sticking to co.uk......
Summer time started at the weekend here but the tablet did not change the time.....
Any idea what I can do for those problems? Thanks.....
Click to expand...
Click to collapse
Try disabling the Geolocation option, you should find that under -
Settings -> Location and Security -> "Use location for Google Search" and "Use GPS Satellites" (try disabling these option).
Super easy to flash and runs great and the status bar rocks.. that original was horrid
Sent from my Xoom using xda premium
Awesome
This was the easiest install I think I have came across for an android rooting method. Runs so much smoother now. does the status bar write over and remove the lenovo bar? Any issues, thinking I am going to run this. Has anyone ran any performance tweaks, V6supercharge etc. Any benefit? Running much better now.
I did notice all my google apps updated to Play versions but the market still has not changed to the google play icon or version. Do i need to do a wipe cache etc?
dc52317 said:
This was the easiest install I think I have came across for an android rooting method. Runs so much smoother now. does the status bar write over and remove the lenovo bar? Any issues, thinking I am going to run this. Has anyone ran any performance tweaks, V6supercharge etc. Any benefit? Running much better now.
I did notice all my google apps updated to Play versions but the market still has not changed to the google play icon or version. Do i need to do a wipe cache etc?
Click to expand...
Click to collapse
Am running autokiller memory optimizer and it definitely made the device faster. Also the free memory has been behaving nicely.
I flashed the stock staus bar too, ii have felt, this made the device faster too. The lenovo bar was pretty slow and would hang pretty frequently.
I have also change the home launcher to Go launcher ex, feels better and more standard as I have this on other devices too. Love the inbuilt task manager on go launcher.
I yet have to try out V6, would love to see the results. Although as earlier suggested by Khanning, delete the /data/firstboot folder prior to trying else the device won't be able to rebuild your Dalvik cache. I wouldn't try it without making a backup using CWM, incase it messes up and you need to revert.
Let me know the results if you try out V6.
Cheers
Sent from my HTC Vision
I will probably start with some of the tweaks you mentioned before I attempt any v6 type adjustments. Have you or anyone tried ROM toolbox for adjusting memory, build prop, etc. I have used this on my Droid INcredible, and works great but there is a good amount of information on the settings people have been using on phones. Thanks for the information.
rezapatel said:
Am running autokiller memory optimizer and it definitely made the device faster. Also the free memory has been behaving nicely.
I flashed the stock staus bar too, ii have felt, this made the device faster too. The lenovo bar was pretty slow and would hang pretty frequently.
I have also change the home launcher to Go launcher ex, feels better and more standard as I have this on other devices too. Love the inbuilt task manager on go launcher.
I yet have to try out V6, would love to see the results. Although as earlier suggested by Khanning, delete the /data/firstboot folder prior to trying else the device won't be able to rebuild your Dalvik cache. I wouldn't try it without making a backup using CWM, incase it messes up and you need to revert.
Let me know the results if you try out V6.
Cheers
Sent from my HTC Vision
Click to expand...
Click to collapse
dc52317 said:
I will probably start with some of the tweaks you mentioned before I attempt any v6 type adjustments. Have you or anyone tried ROM toolbox for adjusting memory, build prop, etc. I have used this on my Droid INcredible, and works great but there is a good amount of information on the settings people have been using on phones. Thanks for the information.
Click to expand...
Click to collapse
Haven't used rom toolbox to make any custom adjustments to the build.prop, but technically if it makes changes to the build.prop file, its pretty much the same risk of a bootloop as trying out v6. Just that it can be controlled by inducing one tweak / value at a time. You can also take a backup of the files and push the originals using adb.
I really wouldn't all that effort unless I find lots of free time soon
But pls do share your experience, most specifically modifying the build.prop and deleting the dalvik cache (and having it rebuild on startup). If this works, I will plunge in and try out other stuff.
P.S. I am now using RAM Manager Pro and feel, this has made the device much snappier. Experiencing the same snappiness on my HTC Vision too. So far, I feel its performing much better than v6 or akmo.
Sent from my HTC Vision
Installed the rom and its nice and snappy....
Can someone give a break down to wipe the dalvik cache please?
Got the can't install app from market problem to and I guess that is the way to fix it, to delete it?
Thanks.
ANY idea why I can't boot recovery to sdcard? Just dcim, android, and data folders
no usb connection to xp
I loaded rom and Honeycomb status bar fix. The speed and root is nice. But i just noticed I can not get a usb connection to be recognized by my windows machine, so I can copy over backup'd files.
Anybody know what needs to be done to restore USB connection? Is it because the device is no longer K1 and is now Xoom that it wont work wth lenovo usb drivers?
Please help. Thanx.
Is there a chance for a Version based on
K1_A301_12_12_120109_M_GE
for the UMTS/3G+wifi model?
Thanks.
Twist79 said:
Is there a chance for a Version based on
K1_A301_12_12_120109_M_GE
for the UMTS/3G+wifi model?
Thanks.
Click to expand...
Click to collapse
Yup yup
Can someone with the M_GE edition hop into freenode irc #ideapad-k1 with me to test it. If you don't have an irc client you can just go to http://webchat.freenode.net/?channels=ideapad-k1
[Edit]
Updated the first post with a link to K1_CWM_120109_M_GE_Rooted.zip for my mobile friends in Austria
thanks to isime13 for testing
Thanks I will try it ASAP. And this comes from Austria and not Germany.
Feedback for the DE Version.
look like rooted on the first look.
Superuser app installs fine.
BUT: Apps don't get super user rights. superuser cant update itself and busybox pro complains it cant install because it does not get superuser rights.
So on the second look...no it does not work right.