Disclaimer: I have only tested this on my own phone. Everything should work fine, but I am not responsible for anything lost on your phone..
Here is an application based on my Bell Deodex scripts. Still a work in progress, but I am running out of things to do with it so it may be ready for public consumption. I just ran through a test of all the features, so far, so good.
Features:
Full Phone Backup and Restore (partitions 1-14, 17)
Root / Unroot
Early usb enumeration recovery mode
2nd-Init support
Odex/Deodex system files. (Bell stock, Telstra and French supported, ATT firmware support would just be a matter of creating the right system_$version.tar.gz archive and putting it in my Dropbox account.)
There are some changes compared to my scripts:
I am not using /data/local/tmp anymore, instead I am using /cache.
Instead of suspending android vis setprop tcmd.suspend 2, which obviously wouldn't be good from something running within android, I am using my early usb enumeration wedge to do it on the next boot before android loads via a script run from /cache.
Slight mods to that have been made to support this functionality, it requires shsu to be installed from my root install. So, if you have rooted using something else, you need my shsu in /system/bin.
ApplyMods is not being used, I could possibly port apktools over, but for now, the mods are baked into the deodexed system files.
I have compiled my own version of Gingerbreak, based on the source for GingerBreak_v1.2.apk. It detects our Froyo better by seeing if there is a 2.2 in the version anywhere. Also, it now takes a path argument so it's not limited to running from /data/local/tmp, and not hard baked with an android application path. Also, the app installs SuperUser.apk as a regular application, not a system one, and prompts you to unmount your internal memory and sdcard, so preserve their contents while GingerBreak is active.
Still more testing needs to be done, I have been working with stock Bell for most of development.
Bugs and feature requests welcome.
Cheers!
Credits:
ChainDD for the Gingerbreak apk, and the The Android Exploid Crew.
edgan for the 2nd-int stuff, see his thread here.
Tested:
OLYLA_U4_0.37.4: 100%
OLYEM_U4_2.1.1: 100%
Fixes:
1.0.1: debloat script fixed when deodexing, it was working but the files were getting replaced by the archive.
1.0.2: check added for shsu
1.0.2: Fixed stupid backup bug, creating directory "backup" and copying to "backup_$version"
1.0.3: Added reboot dialog popup
1.0.3: Fixed force close when no sdcard mounted. (postexecute in asynctask was assuming initialized data, not done when aborted)
1.0.3: Backup/Restore now archives data partition.
1.0.3: Multiple Backups now put up a selection dialog.
1.0.4: Added settings menu option
1.0.4: Updated early usb recovery mode, osh mount moved and replaced, using flag to avoid rerunning the same code.
1.0.4: Reboot option moved to menu. Requires root, when rooting just turn phone on and off, Superuser.apk gets installed after you reboot.
1.0.4: ATT sideloading support added. Reason for the move for Superuser.apk to next boot.
1.0.4: Recompiled 2nd-int, it's now 5KB instead of over 400KB. Have to find some working source for taskset to do that same there.
1.0.5: Added long click to backup button to force a restore operation
1.0.5: finished off settings dialog to implement internal vs external storage.
1.0.5: Misc layout updates, smaller font description text.
1.0.6: Fixed root.sh script, missing / resulting in 0 byte files. Doh!
Some attempt at docs.
Root/Unroot
I am using Gingerbreak to gain a temp root, which then runs a root.sh script with elevated privileges to remount /system and copy su and sush to /system/bin, link in /system/xbin to su, and copy su over to /osh/sbin/frozenfish. Prior to running GingerBreak, the app brings up the system settings for memory cards, so you can unmount them. This will keep you from losing the contents of your internal memory and external sdcard, the app will wait until you have unmounted both. You still have to reboot however. Be sure to click install or replace for Superuser.apk when your phone reboots, around 10 seconds after you see the home screen again.
Unroot just uninstalls Superuser.apk and and deletes the files copied above.
Early USB enumeration:
How to enter:
Hold down volume down when you first turn the phone on, it will say fast boot.
Click volume down until it says early usb enumeration mode.
Press up volume to select.
What it is:
All this boot mode does is enable the usb port so it is available for adb access.
App_Process:
What this is:
It's what starts all the androidish things happening, otherwise you have just linux running on your phone. It is located in /system/bin and is called by init in init.rc. It invokes pre-zygote, zygote, and post-zygote classes (sets of functionality related to getting all the phone services running).
Early usb mode recovery:
What this is:
This is a script in /system/bin replacing app_process. This gets activated when there is an update.sh in /cache OR if you are in early usb enumeration mode and the usb cord is plugged in. In either case, the system partition is moved to /old_system and a copy of it is running from ram, system and root are in read write mode, both sdcards are manually mounted.
So long as you are booted into early usb enumeration mode and the usb cord is plugged into your PC, the phone will wait for the plug to come out, halting the boot process. You can fix your framework-res.apk files, do whatever, and the phone won't crash. When you are done you can pull the plug and the phone will continue where it left off. The system partition is remounted read only and put back as /system, the sdcards are synced and unmounted for vold to find later on.
(Your pc will beep saying usb is disconnected, that is the script turning off usb while it is copying the system partition, it will beep again when it reconnects usb. This is to avoid being in an adb shell and things are still in the works.)
If you have an update.sh script in /cache, regardless of whether you are in early usb enumeration mode, it will go through the same process above, the script will do it's thing while the real system partition is out of the loop, and continue on automatically.
2nd-Init:
This is implemented by adding (not replacing) mount_ext3.sh in /system/bin.
This script changes the affinity of init to be single core, and hacks into it to restart init. Everything already done up to the point in init.rc where mount_ext3.sh is located is not undone, there is a replacement init.rc stored in /system/etc/rootfs that leaves out the bits that were already done and disables some reboot detection. In my implementation of this, I make the phone insecure by replacing the root default.prop file, it gives root access to adb, and causes eclipse to freak out in it's console tab.
Deodex/Odex:
This app attempts to download a file to internal mem from my dropbox account named system_$version.tar.gz, where $version is the contents of your ro.build.id. This file contains the deodexed app and framework files, as well as some tweaks for build.prop in /system. It may also contain a bootanimation and apns list if you are running on Bell and have a foreign firmware loaded. A backup of the odexed files is also created in internal mem, as well as contents of any modified folders. The downloading is done right away, the deodexing is done via update.sh script on the next boot. Same process applies for reversing things.
Full Phone Backup/Restore:
This has nothing to do with nandroid or backing up personal settings.
The contents of /dev/block/mmcblk0p1 though mmcblk0p14, and mmcblk0p17 are dumped to internal mem in a folder called backup_$version, where $version is your ro.build.id. The data partition (mmcblk0p16) is 2GB, I create a tarball of that instead of a straight dump, you can do a factory reset to get that back to stock if anything goes wrong. The cache partition (mmcblk0p15) is just temp space, I leave that out.
To restore the process is reversed, it is implemented as update.sh in /cache for next boot. In this case the script reboots the phone and deletes itself. You can't replace the contents of system by essentially flashing it, and keep it's mount going.
Looks very cool! Will check it out.
BTW your Early USB Enum hack has saved me so many times, I cannot thank you enough! I wrap all my hackery in if [ $(getprop ro.usb_mode) != "debug ] ; then
Now! Keep up the good work =)
Nfhimself,
This looks really great! Three quick questions though. What do you need for this to work with an att atrix? Will this tool root a fresh sbf install? How should sideloading be enabled first to install?
Thanks
eval-, glad to be of service.
airbillion, I know little about the side loading issues with att, bit of a chicken and egg, nothing in an apk will enable it to be loaded. I thought I read side loading was possible now with ATT. Other than that, there is nothing intentionally Bell specific other than the deodex stuff I mentioned.
Cheers!
Will the rest of the features (other than odex/deodex) work on an AT&T Atrix? I was a bit confused about this and wanted to clarify.
Yes, it should, no reason why not.
Cheers!
This is awesome thank you!
Sent from my MB860 using XDA Premium App
NFHimself said:
eval-, glad to be of service.
airbillion, I know little about the side loading issues with att, bit of a chicken and egg, nothing in an apk will enable it to be loaded. I thought I read side loading was possible now with ATT. Other than that, there is nothing intentionally Bell specific other than the deodex stuff I mentioned.
Cheers!
Click to expand...
Click to collapse
Nfhimself,
Thanks for the reply. Att still needs to enable sideloading for atrix, but that can be done manually. Im still unsure what you need so we can deodex with your program though.
eval- said:
Looks very cool! Will check it out.
BTW your Early USB Enum hack has saved me so many times, I cannot thank you enough! I wrap all my hackery in if [ $(getprop ro.usb_mode) != "debug ] ; then
Now! Keep up the good work =)
Click to expand...
Click to collapse
NFHimself, what exactly does Early USB Enumeration do?
airbillion said:
Nfhimself,
Thanks for the reply. Att still needs to enable sideloading for atrix, but that can be done manually. Im still unsure what you need so we can deodex with your program though.
Click to expand...
Click to collapse
Don't need anything, just haven't made a deodexed archive available,yet.
Cheers!
Sent from my MB860 using XDA Premium App
n1ckr0th said:
NFHimself, what exactly does Early USB Enumeration do?
Click to expand...
Click to collapse
It's for using adb in early usb enumeration mode and for running scripts prior to android booting. Without it, android continues to boot and if there are any issues it auto reboots. That's the gist of it.
Cheers!
Sent from my MB860 using XDA Premium App
NFHimself said:
Don't need anything, just haven't made a deodexed archive available,yet.
Cheers!
Sent from my MB860 using XDA Premium App
Click to expand...
Click to collapse
Thanks nfhimself! Any plans on making one?
Really annoyed that it won't download from my phone.... anyone able to?
sent from my rooted,
and chillin, canadian Motorola Atrix
Edit: nevermind it worked Haha
marko! said:
Really annoyed that it won't download from my phone.... anyone able to?
sent from my rooted,
and chillin, canadian Motorola Atrix
Edit: nevermind it worked Haha
Click to expand...
Click to collapse
Cool, also downloads fine from xda app.
Cheers!
Sent from my MB860 using XDA Premium App
airbillion said:
Thanks nfhimself! Any plans on making one?
Click to expand...
Click to collapse
Sure, is the latest 1.83 these days? Or rather, is that what everyone is using on att?
Basically, I just be deodexing the files, applying some tweaks and uploading to dropbox. I would have to look up what is going on with webtop on att, to match the ones already done up.
Sent from my MB860 using XDA Premium App
NFHimself said:
Sure, is the latest 1.83 these days? Or rather, is that what everyone is using on att?
Basically, I just be deodexing the files, applying some tweaks and uploading to dropbox. I would have to look up what is going on with webtop on att, to match the ones already done up.
Sent from my MB860 using XDA Premium App
Click to expand...
Click to collapse
Thats great if you can do this for the att users! Yes 1.83 is the most recent and most used on att. Im not too sure about any differences on the att webtop compared to bell or the others, but if you need anything just ask.
Thanks
Sent from my Dell Streak using XDA Premium App
many many many thanks!!! ))))))
Btw how do we enter early usb enum?
About sideloadind and att, it will be on gingerbread enabled..
Until then if u can try install this app using adb, and then threw this app install modified gingerbreak.. Don't know for sure if it works..
Sent from my MB860 using XDA App
Can't get the deodex to work on stock bell.
{
"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"
}
sent from my rooted,
and chillin, canadian Motorola Atrix
Edit: what size is the deodex file?
Edit#2 : now it says everything works but after reboot still showing odex files I. System/app
i've the same probleme
can donwload deodex files for at&t 1.8.3
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.
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?
Hey all! This is the new home of the Droid 4 Utility (NOW WITH SAFESTRAP THANKS TO HASHCODE) for Windows/Mac/Linux!
There are (still) no fastboot files as of writing this (2/28/2012) so use Safestrap at your own risk
Once they come out I will be making a full version that includes fastboot restore. For now, the utility is only a few MB compared to a GB+.
From this point forward I will be taking charge of updating the Droid 4 Utility for Windows/Mac/Linux
This way mattlgroff has a little less work on his hands and can focus more on IMPORTANT things like bootloaders, ICS, etc...
MAC/LINUX: Be sure to read the instructions below (or README file) if you are not familiar with using terminal as root or executing bash scripts!
-Changes
~~as of 2/18/ 11:30PM PST
Fixed bug where Superuser.apk was pushed to /data instead of /system/app/
Fixed unroot script to properly remove Superuser.apk
~~as of 2/19 4:30 PM PST
Fixed chmod in root method from 4775 to 6775
~~as of 2/28 6:15PM PST
Added Safestrap recovery!!
~~as of 3/2
fixed script to chmod +x ./files -R so that you can actually run the files on mac and linux (that would be important huh?)
DOWNLOADS
WINDOWS
Size: 7.75 MB
MD5: f82bf8d8a085ff95b696712b8caa0f1b
Link: http://tinyw.in/KKB8
MAC
Size: 7.19 MB
MD5: dc8468d051d59963914a0b8a054b83b8
Link: http://tinyw.in/vx2A
LINUX
Size: 7.26 MB
MD5: 0c082efbff48e614b9d8ebffc7eca3eb
Link: http://tinyw.in/tpt0
Here's how:
Windows:
Simply Unzip the files, and run Droid4Windows.bat as administrator (right click>run as administrator)
Mac/Linux:
Simply extract the zip then
Code:
su
Then enter the root password NOTE: This is not YOUR password, this is the ROOT password. If you dont know it, you can always use
Code:
sudo passwd
to reset the root password
Next run:
Code:
cd /the path to where you extracted the files/
for example, heres what I have to type:
Code:
cd /home/skylar/Desktop/Droid4UtilityLinux/
next run the appropriate bash script:
Code:
bash Droid4linux
OR
Code:
bash Droid4mac
I'm sorry to say I don't actually own a Droid 4, so I'm doing this blind. Please report any problems or bugs you have.
Have fun and I hope you enjoy! [/SIZE]
CLICK HERE TO DONATE
SCREENSHOTS
{
"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"
}
CLICK HERE TO DONATE
I can not get this to unroot.
---------------------------------------------------------------
Easy rooting toolkit (v1.0)
UNROOTING SCRIPT
created by DooMLoRD
based heavily on FlashTool scripts (by Bin4ry and Androxyde)
Credits go to all those involved in making this possible!
---------------------------------------------------------------
MAKE SURE THAT THE SCREEN IS UNLOCKED
and if you get Superuser prompts ACCEPT/ALLOW THEM
ELSE THIS WILL NOT WORK
Note: This removes superuser from both possible locations
So seeing one error of now finding Superuser is NORMAL!
---------------------------------------------------------------
Press any key to continue . . .
--- STARTING ----
--- WAITING FOR DEVICE
The system cannot find the path specified.
--- TESTING FOR SU PERMISSIONS
MAKE SURE THAT THE SCREEN IS UNLOCKED
and if you get Superuser prompts ACCEPT/ALLOW THEM
ELSE THIS WILL NOT WORK
The system cannot find the path specified.
--- cleaning
The system cannot find the path specified.
--- pushing busybox
The system cannot find the path specified.
--- correcting permissions
The system cannot find the path specified.
--- remounting /system
MAKE SURE THAT THE SCREEN IS UNLOCKED
and if you get Superuser prompts ACCEPT/ALLOW THEM
ELSE THIS WILL NOT WORK
The system cannot find the path specified.
--- pushing unroot script
The system cannot find the path specified.
--- correcting permissions
The system cannot find the path specified.
--- executing unroot
MAKE SURE THAT THE SCREEN IS UNLOCKED
and if you get Superuser prompts ACCEPT/ALLOW THEM
ELSE THIS WILL NOT WORK
The system cannot find the path specified.
--- cleaning
The system cannot find the path specified.
--- rebooting
The system cannot find the path specified.
ALL DONE
Press any key to continue . . .
The system cannot find the path specified.
Please make a selection or hit ENTER to return:
Click to expand...
Click to collapse
prodigyweb said:
I can not get this to unroot.
Click to expand...
Click to collapse
Sounds like you aren't running this inside the folder that also contains the /files/ folder. If you have it by itself of course the path's won't find it...because you moved it or you aren't "cd" into the directory of the utility.
appears after a phone/computer reboot and canceling the ADB process in my tasks it now is rebooting the phone and working. Thanks!
prodigyweb said:
My setup is: http://i.imgur.com/Surbz.png
should it be within the adb package from android itself?
Click to expand...
Click to collapse
Is your USB Debugging Mode enabled and "Unknown Sources" in your application settings?
Hm, I turned on USB Debugging in the settings, but it's not starting up when I plug in a USB cable, and adb can't find the device. ???
highlandsun said:
Hm, I turned on USB Debugging in the settings, but it's not starting up when I plug in a USB cable, and adb can't find the device. ???
Click to expand...
Click to collapse
While your phone is plugged in, see what drivers are in device manager and remove them. Then restart your phone while its still connected through USB. See if that reinstalls all the necessary drivers and try again.
reigndropz said:
While your phone is plugged in, see what drivers are in device manager and remove them. Then restart your phone while its still connected through USB. See if that reinstalls all the necessary drivers and try again.
Click to expand...
Click to collapse
This is Linux, so no device manager. I think I needed to add the Motorola vendorID to my udev rules first, I got it working eventually. Rooted, great. Now to go and fix the character maps so I can fully use Connectbot.
highlandsun said:
This is Linux, so no device manager. I think I needed to add the Motorola vendorID to my udev rules first, I got it working eventually. Rooted, great. Now to go and fix the character maps so I can fully use Connectbot.
Click to expand...
Click to collapse
Ah ok.....how are you with deodexing? I have been trying to deodex the SystemUI but I am not having any success. I add the jars but it keeps going and going and doesnt seem to end. Soon as I get the SystemUI deodexed, I'll throw a battery percent icon here....
reigndropz said:
Ah ok.....how are you with deodexing? I have been trying to deodex the SystemUI but I am not having any success. I add the jars but it keeps going and going and doesnt seem to end. Soon as I get the SystemUI deodexed, I'll throw a battery percent icon here....
Click to expand...
Click to collapse
Hm, haven't done anything with theming tweaks. Dunno, sorry.
You need adb to be enabled at boot time, so you can adb logcat during the startup and see what failed.
By the way, the Linux archive is not immediately usable, you need to chmod +x everything under the files/ subdirectory to make them executable first.
highlandsun said:
Hm, haven't done anything with theming tweaks. Dunno, sorry.
You need adb to be enabled at boot time, so you can adb logcat during the startup and see what failed.
By the way, the Linux archive is not immediately usable, you need to chmod +x everything under the files/ subdirectory to make them executable first.
Click to expand...
Click to collapse
Hey thanks for pointing that out! I didnt notice because they were already executable on my computer. I added
Code:
chmod +x ./files -R
to the script on startup so no one should have to manually do it anymore, sorry about that
prodigyweb said:
I can not get this to unroot.
Click to expand...
Click to collapse
Make sure you have done all of the steps below
Prework
1. Plug in phone to computer.
2. Turn on USB Debugging. Menu -> Settings -> Application -> Development -> USB Debugging
3. Confirm latest Moto driver is installed. Go to Device Manager on Windows while the D4 is plugged into it and confirm you see ADB Interface listed with Mot Composite ADB Interface listed in the group. If you see that, skip #4 & #5. There are other ways to go about this, but this is the simplest and surefire way to confirm the driver is there and compatible.
4. Go get Moto driver and install it: USB and PC Charging Drivers - Motorola Mobility, Inc. USA It is an exe file that must be run and your computer has to restart when completed.
5. Go back into your Device Manager after reboot with the phone plugged in and confirm ADB Interface is there and no error exists.
Done.
I can't get this to root, it appeared to have rooted once since Superuser was installed but TBU said not root access. Now I get message " error more than one device and emulator" when I try to root again or unroot. any idea?
contemplating getting this through a client, any word on fastboot and unlocked updates?
or is the droid 4 destined to be like all other moto phones and lack a soul...
I really wanted the Photon, but dev on it was strangled to death!
Hammerfest said:
contemplating getting this through a client, any word on fastboot and unlocked updates?
or is the droid 4 destined to be like all other moto phones and lack a soul...
I really wanted the Photon, but dev on it was strangled to death!
Click to expand...
Click to collapse
The phone itself is great. Good build quality, fantastic keyboard, fast, etc. I have not heard any news on fastboot files yet. I assume it's just a matter of time but who really knows for sure. Unlock updates? As in unlock the bootloader? I don't ever expect to see that happen, personally.
Despite that, development seems to be coming along nicely with very usable AOSP CM9, AOKP, and Gummy ROMs. The relative ease with which Razr ROMs can be ported to the D4 (due to almost identical internal components) should help on that front as well as Razr development is seems very strong.
Does this Utility still work after the latest update?
I had previously rooted via this utility and had frozen a bit of bloatware w/ TB. I have since unfrozen the bloatware and unrooted. As soon as the install message pops up again I plan to run the update, but was wondering if I will be able to re-root the same way once I do that.
mancowmilitia said:
Does this Utility still work after the latest update?
I had previously rooted via this utility and had frozen a bit of bloatware w/ TB. I have since unfrozen the bloatware and unrooted. As soon as the install message pops up again I plan to run the update, but was wondering if I will be able to re-root the same way once I do that.
Click to expand...
Click to collapse
I've heard people having mixed results trying to re-root using the utility. Some seem to have no problem but others said they had to run the exploit directly. Not sure why.
I just used the Voodoo OTA Root Keeper app to hide root while the update was being applied and then restored root.
kwyrt said:
I've heard people having mixed results trying to re-root using the utility. Some seem to have no problem but others said they had to run the exploit directly. Not sure why.
I just used the Voodoo OTA Root Keeper app to hide root while the update was being applied and then restored root.
Click to expand...
Click to collapse
I installed the upgrade with no issues. I was able to re-root without complication as well. The only message I received was that the Superuser.apk installation "failed" because it was already there. Others have noted that unrooting doesn't delete the file. But, its presence did not stop my upgrade.
This time I installed Voodoo and will go that route for the next OTA.
Is there a mirror link for the Windows Utility? The download keeps timing out on me.
heres a link for an older copy
http://goo.im/apps/mattlgroff/Droid4Utility0.3.zip
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.
Okay if you do some work to make your Dell Streak 7 work right with the AOKP 4.2.2 here.
Everything you needed is linked in this post to get you up and running with 4.2.2.
Now for the stuff you need to do to make your 7 run big apps like this Rich! Free Casino Slots okay.
First once you have setup you install of 4.2.2 goto system settings. from there goto Developer options.
Once there goto Force GPU rendering and check that.
Now go get Memory Manager from the play store.
Now once you have that running set it's presets to Aggressive.
Once that is done check the Apply at boot.
Now head over to get Trickster MOD Kernel Settings from the store.
Now that you have that start it up and goto General tab.
In there set the I/O Control Scheduler to noop.
Then goto in the same tab, CPU Governor Control and set the Governor to smartassV2.
Now you can try playing around with overclocking the CPU, but I have found most of the 7's don't like anything over 1 GHz top end due to voltages.
But try at your own rick.
Anyway once you have those set then click the first app setting in the upper right and of the app.
Once in there set all of the On Boot setting to on i.e. check them all.
Now you can play with the delays but I have found if they are set to 0 it works better, don't ask why.
Now that we are done with that app the next app to get is Zram Settings Free.
Now once you have that installed.
open it up and check all the check marks you can. DON'T REBOOT THE SYSTEM YET.
Now close that out.
Now get Root Browser.
The reason for this app over others is because this one when it opens and edits files or makes new files or folders will make them so that Android will like them.
Because the next part is only for the brave of hart and mind. LOL
Okay open up Root Browser and get it setup.
Next head to /etc/sysctl.conf file. Open it up and add this to the last of the file.
vm.swappiness = 90
Click to expand...
Click to collapse
or what ever you like from 1 - 100. I set it to 90 so that my system will load most big apps. With out to much lag.
Now that is done and the file saved.
here come the real fun part.
Next head over to Terminal and open it up.
Now in here we put.
su
mount -o rw,remount /dev/block/platform/sdhici-tegra.3/by-name/APP /system
TARG=/system/.swapfile
dd if=/dev/zero of=$TARG bs=$((1024*1024)) count=400
Click to expand...
Click to collapse
The count=400 part is the size of the swap file we are setting up in the /system folder. So if you want something bigger then that put it in as a MB at the count part.
mkswap $TARG
chmod 600 $TARG
Click to expand...
Click to collapse
The last part sets the new swap file to root only keeps it from being deleted.
swapon $TARG
free -m
Click to expand...
Click to collapse
The last two things do this.
1: it tells Android to use the new file as swap.
2: should show you a 400MB size swap file being used.
Now to get this all to restore it's self after a reboot we are going to need to do a bit more, but it's fast should be the end of this.
Okay before we try a reboot head back over to the Play Store one more time and get yourself.
Script Manager - SManager
Now once you get this app setup we are going to make a .sh file.
A .sh file is a shell script file for *inux based systems. Yes that's OS X no matter what apple wants you to think other wise.
Okay to make this file open SManager
Then hit the menu key, then tap new script.
Name it what ever you would like. I called mine swap.sh
Next use the TB editor.
It should have this in the window to start with if not put it in.
#!/system/bin/sh
Click to expand...
Click to collapse
Now the next part to make this all work right.
TARG2=/system/.swapfile
mount -o rw,remount /dev/block/platform/sdhci-tegra.3/APP /system
swapon $TARG2
Click to expand...
Click to collapse
Now once that is saved in your internal SDCard then tap it and then tap the root icon and the boot icon.
Now when you reset the tab it can take up to 2 minutes to fully load out but now swap will be running and the tab will be fast and big apps like games and Netflix should load and work. Now I have only tested this on game like Hit It Rich or Fast 6. I have yet to try it with Netflix so don't blame me if it still don't work.
Can you show your swap output, I cannot remember if I even enabled that option in the kernel.
giveen said:
Can you show your swap output, I cannot remember if I even enabled that option in the kernel.
Click to expand...
Click to collapse
Here is the Terminal output as you asked. As you can see it's working with a swap file.
I have been unable to get it to work with a swap portion be it on the main internal SD Card or on an Ext SD Card.
I'm thinking that it may have something to do with the way Dell did there mounting system, but I have never really been a kernel guy.
{
"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"
}
Here is reading from ZRam Setting app.
And here is some more info for you to look at.
Now I only put the file in the system folder because when it was on the SD Cards it would do things to the system that was not good.
That and I kept losing data on the cards.
So I put the swap file in system folder and the script I put in /data/scripts/. The scripts folder I made.
That way when I did my Nandroid backups I would always have the file and scripts.
Any help you could give me to get my script to run at boot with indit.d would be great as I know android don't really have cron in any working form.
michaelcrossland said:
Here is the Terminal output as you asked. As you can see it's working with a swap file.
I have been unable to get it to work with a swap portion be it on the main internal SD Card or on an Ext SD Card.
I'm thinking that it may have something to do with the way Dell did there mounting system, but I have never really been a kernel guy.
View attachment 2901112
Here is reading from ZRam Setting app.
View attachment 2901113
View attachment 2901114
And here is some more info for you to look at.
View attachment 2901115
View attachment 2901116
View attachment 2901117
Now I only put the file in the system folder because when it was on the SD Cards it would do things to the system that was not good.
That and I kept losing data on the cards.
So I put the swap file in system folder and the script I put in /data/scripts/. The scripts folder I made.
That way when I did my Nandroid backups I would always have the file and scripts.
Any help you could give me to get my script to run at boot with indit.d would be great as I know android don't really have cron in any working form.
Click to expand...
Click to collapse
Tutorial [Guide] [Dec.15] How to Tweak and Mod Android Using Init.d Scripts
and, in the jb defconfig,
CONFIG_SWAP=y
Thanks for that link. But it don't help with showing how to make the script do anything that would need SU rights to do.
My script need to be ran as root. But thanks for the info.
And as far as your 2nd part. That's great for that info but what *.conf file does that setting need to be put into?
Sent from my Streak 7 using XDA Premium HD app
michaelcrossland said:
Thanks for that link. But it don't help with showing how to make the script do anything that would need SU rights to do.
My script need to be ran as root. But thanks for the info.
And as far as your 2nd part. That's great for that info but what *.conf file does that setting need to be put into?
Sent from my Streak 7 using XDA Premium HD app
Click to expand...
Click to collapse
I though all init.d scripts ran as root. Why not try it and see?
the second part, is from giveen's github kernel source, and unless the one built into your ROM uses another defconfig, you do have swap enabled.
in terminal, as su, zcat /proc/config.gz > /sdcard/config.txt
then you can look for SWAP in the text file and see what it's currently set to. You can't change whether swap is enabled or not without rebuilding the kernel.
This is after attempting to flash the test kernel.
ElfinJNoty said:
This is after attempting to flash the test kernel.
Click to expand...
Click to collapse
My kernel already has it on, no need to flash any other kernel
https://github.com/giveen/kernel_dell_streak7/blob/cm10.1/arch/arm/configs/streak7_jb_defconfig
giveen said:
My kernel already has it on, no need to flash any other kernel
https://github.com/giveen/kernel_dell_streak7/blob/cm10.1/arch/arm/configs/streak7_jb_defconfig
Click to expand...
Click to collapse
Has what on?
As far as I know, with @bigsupersquid helping, the kernel is missing some things
Like proper modules for logging
If swap is on already, that's good to know...
bigsupersquid was trying to help me make a new kernel, blindly. But could never compile it correctly to be a flashable zip or fastboot the IMG.
@giveen, think we tried to reach out to you via pm
giveen said:
My kernel already has it on, no need to flash any other kernel
https://github.com/giveen/kernel_dell_streak7/blob/cm10.1/arch/arm/configs/streak7_jb_defconfig
Click to expand...
Click to collapse
ElfinJNoty said:
Has what on?
As far as I know, with @bigsupersquid helping, the kernel is missing some things
Like proper modules for logging
If swap is on already, that's good to know...
bigsupersquid was trying to help me make a new kernel, blindly. But could never compile it correctly to be a flashable zip or fastboot the IMG.
@giveen, think we tried to reach out to you via pm
Click to expand...
Click to collapse
I built from that repo with that defconfig.
Not surprising that's what's in the ROM already.
Just couldn't recombine the boot.img in a way that the streak would accept.
You need more than the kernel to build a boot.img that the DS7 will take.
Steps:
1. Download CM10 (or CM10.1 or CM10.2)
2. Download the device tree AND the kernel tree from github
3. Place device tree in source/device/dell/streak7
4. Place kernel in source/kernel/dell/streak7
5. Run "make boot"
6. Fix any compile issues that come up
.....
10. Profit.
giveen said:
You need more than the kernel to build a boot.img that the DS7 will take.
Steps:
1. Download CM10 (or CM10.1 or CM10.2)
2. Download the device tree AND the kernel tree from github
3. Place device tree in source/device/dell/streak7
4. Place kernel in source/kernel/dell/streak7
5. Run "make boot"
6. Fix any compile issues that come up
.....
10. Profit.
Click to expand...
Click to collapse
I was trying instead to split and recombine the cm10.2 boot.img.
Got a readable ramdisk out of it, but when recombined with the new kernel with abootimg (or perl tools, or mkbootimg) I ended up sending off unbootable images. They stuck at the logo I believe.
I don't have a cm10 tree... just cm11. running out of hard drive space, too. But I appreciate the specific info on how to fix the problem. Thanks.
bigsupersquid said:
I was trying instead to split and recombine the cm10.2 boot.img.
Got a readable ramdisk out of it, but when recombined with the new kernel with abootimg (or perl tools, or mkbootimg) I ended up sending off unbootable images. They stuck at the logo I believe.
I don't have a cm10 tree... just cm11. running out of hard drive space, too. But I appreciate the specific info on how to fix the problem. Thanks.
Click to expand...
Click to collapse
I just put my streak on the charger.... Just in case
bigsupersquid said:
I was trying instead to split and recombine the cm10.2 boot.img.
Got a readable ramdisk out of it, but when recombined with the new kernel with abootimg (or perl tools, or mkbootimg) I ended up sending off unbootable images. They stuck at the logo I believe.
I don't have a cm10 tree... just cm11. running out of hard drive space, too. But I appreciate the specific info on how to fix the problem. Thanks.
Click to expand...
Click to collapse
CM11 is a whole 'nother animal, as CM changed a lot of things with the bootup files and how the disks are partitioned/mounted.
DJ Steve and I have an updated kernel for the cm10.1(really an aokp 10.1) ROM by Giveen that is optimized and increases available memory by about 70mb. Amazing how much improvement off of more available ram. Continuing to test and implement changes and add in features. Also working to convert for bootable lollipop ROM.... Stay tuned:
http://forum.xda-developers.com/showthread.php?t=3330564
I think its awesome that you guys are progressing so quickly! Picking up the torch and finishing the race!