Related
EDIT: This information is out dated now but visit the link below for updated info.
taken from here http://www.samsungmomentforum.com/rooting/root-access-(finally-achieved!)/
1) Partition your SD Card to have first partition as fat16 and second ext3 [this tutorial assumes you have this setup exactly as stated]
2) Boot in Test Mode with Call+Center+Power
3) copy root into your tools directory of the sdk
4) adb push root /system
5) adb shell chmod 0755 /system/root
6) adb shell /system/root
7) unplug usb, remove battery, reboot into test mode when instructed
8) adb shell
9) /system/bin/btld_testmode
10) /system/root
Excellent. It work!. Just do exatly the steps above. Thanks for putting all this info together.
FYI... Samsung post the source code of the samsung moment.
Is this temp or persistent root? For temp root I don't think partitioning the sd card is necessary or at least I didn't partition it when I temp rooted my Moment.
Was a long time WinMo user, I was stuck with a Moto Q9c on sprint for way to long. I'm still stuck with sprint, but got the Moment in hopes of having a badass Android to start with.
Night and Day compared to my Q, the root is key though, custom rom's were so easy on the Q.
soooo im a newb to android, same question as johnbarry3434.
does it stick?
I've got two Moment's(thanks sprint for shipping me 2 and charging me for neither) ?maybe one for test purposes?
Anything I can do to help the rooting process, please let me know
Sorry guys but I'm very new to this android. Only had my phone for a week now. Is rooting like flashing a custom ROM for the Touch Pro?
Does this require seperate adb drivers for the Samsung phone?? If so where can I get them and are there any avaliable for Ubuntu???
Hi guys,
I have just gotten myself a Samsung Spica. Can I use this guide as well? Is there a ROM-update tool for the Spica?
I'm really n00b, so any help is appreciated
I need someone with this rooted phone to contact me, I need to get some data from it so I can work on something for it.
Please contact me at [email protected]
Thanks
hey look i am brand new to this whole root thing i just got my moment two days ago i am used to the simple jailbreak iphone stuff but this is a whole new level
i am on windows vista and i do not understand any of this at all please someone email me some simpler instructions or make a video or something just to help me out in some way please and thank you
my email: [email protected]
use the search Service people
Now that moment is rooted?
Will there be any chance of us getting a custom rom of andorid using sense ui?
i dont really see any point in rooting my phone if there is no MAJOR thing you can do with it..
I cannot get my samsung to root
I have the updated cupcake cl14 and when I boot my phone with talk+center+power, I boot into a test mode that lets me test the screen, keyboard, and so on. I did copy the root file (supplied from the instructions ) to the main part of my card on both partitions, and partitioned it just as it stated in the 1st step. I don't understand what the "adb" is and how to use it. Can this only be down with windows because I'm am using Ubuntu. I know adb is advance debugging bridge but after some google searches I still don't know how to use it. I now a little about chmod 0755 because of Ubuntu but any "hand-holding" instructions would be great thankyou to everyone who is willing to help me and others out with this problem.
Is there still no "real" benefit for root access for the Moment? As in no good reason to root the phone? My girlfriend has one and I was hoping that it was at least close behind my Hero by now in terms of root access benefits....TIA
bbv203 said:
Is there still no "real" benefit for root access for the Moment? As in no good reason to root the phone? My girlfriend has one and I was hoping that it was at least close behind my Hero by now in terms of root access benefits....TIA
Click to expand...
Click to collapse
try this
http://forum.samdroid.net/threads/13-How-to-get-Root-on-Samsung-i5700-EN-02-10-v-LK10
just got my phone and can't increase the size of the fonts was told rooting is the only way even with using spare parts.
first of what program can I use to partition the sd card I am running windows XP. and everything I have downloaded today would only see the internal drive.
For those of you still looking for how to root your Samsung Moment (you don't have to use your SDCard either) there are two HOW TOs posted at PPCGeeks under the NON-WM DEVICES>ANDRIOD>SAMSUNG MOMENT
One explains how to root phone with CJ05
The other explains how to root phones that have CL14 out-the-box or officially updated to CL14
I would post a link except I'm not permitted to post an outside link... just go to PPCGeeks(dot)com and click on their forum
So what Now!!!!
Okay I see you have this placed here.. I like... I have a Nexus and 2 Droids, wife and mine.. Nexus ALL mine.. HAHAHA..
My sister, wifes sister, she has the Moment.. I have always wanted to root this just cause of the 800mhz processor... This was the first device to almost meet up with the Nexus before it was even thought up..
Is there Roms, Themes, Kernels, etc.. I see nothing, but a root, useless, without an accommodation, thanks anyway, always good to have the key to the door first..
Somebody, PM me if not on, or reply here, I'll come back around...
cool that i made the front page but the info is out dated now.
yes this info is way outdated. just flash the kernel with speedyrabbit's or joeykrim's kernel and you'll have persistent root, plus a much faster phone.
also, speedyrabbit's kernel has wifi tether and flash_image support. you can download from www(dot)sdx-developers(dot)com.
Cant figure out for the life of me how to reroot after doing the 340 ota. I came from 2.2 ota.
I tried z4root multiple times, no dice.
Tried the DoRoot Automatic script. Didnt fully work.
Tried the manual method on the phone with term emu.
Tried the manual method...and im getting stuck here...
Factory Reset and did it all AGAIN... So annoyed
Mod note from Sleuth
Wispirer figured this out further down in the thread. It has to do with different versions of the superuser apk file confusing z4root. His post is here
nicely done btw
end mod note
[*] Searching for adb ...
[+] Found adb as PID 6025[*] Spawning children. Dont type anything and wait for reset![*][*] If you like what we are doing you can send us PayPal money to[*] [email protected] so we can compensate time, effort and HW costs.[*] If you are a company and feel like you profit from our work,[*] we also accept donations > 1000 USD![*][*] adb connection will be reset. restart adb server on desktop and re-login.
$
C:\Users\matt\Desktop\android-sdk-windows\platform-tools>adb kill-server
C:\Users\matt\Desktop\android-sdk-windows\platform-tools>adb.exe devices
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
List of devices attached
015A9D7E1303301A device
C:\Users\matt\Desktop\android-sdk-windows\platform-tools>adb shell
$ mount -o rw,remount -t ext3 /dev/block/mmcblk1p21 /system
mount -o rw,remount -t ext3 /dev/block/mmcblk1p21 /system
mount: Operation not permitted
$
z4root sat for 5-10 minutes on "running exploit" when I ran it. Others have also reported this.
I experiened that ONCE too, but i pulled the battery after a few minutes since it went through the full process so many times before.
anyone any ideas?
same problem here...can't get root back yet
Just to make sure, when you guys are rooting you have USB debugging on, yeah?
Also, does 1click root work? Several DX flavors. Check the Wiki. Link in DX android development.
Some questions:
What precisely happens when you try to use z4root? Give me the step by step.
Can you get temporary root with z4?
Sleuth255 said:
Also, does 1click root work? Several DX flavors. Check the Wiki. Link in DX android development.
Some questions:
What precisely happens when you try to use z4root? Give me the step by step.
Can you get temporary root with z4?
Click to expand...
Click to collapse
It goes through the whole process, says its rooting, getting shell, etc, goes white for a second, says rebooting, come back up and no root. And nope, tried both options.
Same here. The main thread about the update says it can take as many as 10 tires. I'm on about #5. we'll see.
That doesnt quite make any sense to me....
Same thing is happening to me, z4root says using exploit, acquiring root shell, goes to white screen then goes back and says rebooting. After it reboots still no root.
Tried 1 click method and it hangs at performing the rage command. Manually tried rooting and after applying the ./rage it kicks me off like its supposed to then says my device isn't found when I do adb devices command.
Yup, Same. I even factory reset twice.
Interesting. I have both copies of the update.zip. I did notice that they were slightly different in size. I used the very first one that was posted. I'm gonna do a quick hex compare to see if they're the same...
edit: uh oh, the two update files are totally different. The original one is slightly larger and HexCMP finds no similarities after the first 1K or so. The one I used had a size of 26,358. The other, more recent one has a size of 26,259.
So whats that mean exactly? Two versions of OTA were pushed out? One rootable and one not?
It sure looks like there's two different sizes and a hex compare shows significant differences. Take a look at your update.zip. What is the precise size? If everybody who can't root has a size of 26,259 then the validity of your thought is supported.
Remember, the original update only went out to a special beta test group and then was quickly pulled. The one I used was that update.
Where do i find the update.zip file? I did the ota update
Review the Droid X 2.3.340 Update thread in this forum. Good history about this update there including the information you seek.
I tried to root with Sil3ntK1ll Root X 2.2 and it looked like it was taking until about 3/4 of the way it said waiting for device. I left it for 5 min and it was then locked up solid. I had to pull the battery and reboot. No ill effects after the reboot but I am not rooted.
So I assume the root authors are already hard at work on fixing this issue?
same story as everyone else, had root, did update, cant get it back
Found this method, hxxp://forum.androidcentral.com/motorola-droid-2/40283-how-root-droid-2-without-computer.html (note: change x's to t's) and lo and behold it worked! Did from top to bottom and now back to being rooted. Hopefully this method works for you guys.
I will try to set up a guide to contain all of the information to get the most out of your I9000 Galaxy S. First the fineprint:
I am not responsible for any damage that any of these instructions may inflict to your phone, computer or any other device that is used in the processes described herein. I am also not responsible if you lose your warranty by flashing your phone with unsupported firmware or if any of these instructions brick your phone, if it will rape your wife or if it will eat your liver with some fava beans and a nice chianti.
I didn't test any of the programs specified herein for viruses/trojans/etc. I run Windows in a VirtualBox that doesn't have access to the internet and doesn't contain any private data, so I don't care for viruses, if you care for your OS though, you should check the programs for viruses before running them.
Use common sense when following such instructions, some of the things may differ because of different program versions, different operating systems or different setups.
Some of these instructions are based on a stock firmware, if your firmware is modded in any way, some of the things described herein may be inappropriate for your device.
1. NOT bricking your phone.
--Why, when, where: Everyone's afraid of bricking their phone. I see the term "bricking" is being a bit overused in these forums though. Everyone is using it, even for the case where the phone can actually be "repaired" with a few simple hacks, IMHO the term "bricking" should only be used in the case where you get your phone in a state where it is inoperable AND you can not in any way repair it yourself.
--Prerequisites: A bit of common sense.
There are a few simple steps that you can follow, to get the risk of "bricking" (as in, you can not repair it yourself and need to somehow get Samsung to either repair it for you, or give you a new device) to a minimum:
1.1. Before trying any of the other steps, make sure that you can get to both the "Recovery mode" and the "Download mode" using the 3-button-combo. If this doesn't work for your device you can try following the steps described here: http://forum.xda-developers.com/showthread.php?t=810686
1.2. Try to avoid flashing stuff that contains a bootloader. The only way to permanently brick your phone so that you can not repair it yourself (at least AFAIK) is to flash a bootloader and then interrupt that flashing. If the bootloader didn't get flashed properly and it's broken, there isn't much you can do about it, and you need to somehow get Samsung to either repair it or give you a new one (if you're lucky). If the bootloader is fine, there is almost always a way to "repair" your phone yourself.
1.3. Do not interrupt the flashing processes. When using Odin or Heimdall to flash stuff to your phone, there is always the risk of bricking it if you interrupt the flashing process. If the bootloader is fine though and you can get into the "Download mode", you might be able to repair it.
If you follow these simple advices, it might save you money, nerves and also some time without your phone (the time that it takes Samsung to repair it, which can sometimes, depending on country, be even a couple of months).
2. Flashing stock firmwares.
--Why, when, where: You should usually do this if your phone doesn't work with your current firmware, if there is a new firmware out that might work better or if you just want to go to a stock firmware.
--Prerequisites: Odin, a stock firmware (from www.samfirmware.com for example).
NOTE: Apparently there are people that report that using Odin v1.3 might interrupt the flashing and leave you with a soft brick and that v1.7 doesn't have this problem. I have always used v1.3 and never had problems because of it, but if v1.3 isn't working for you, you might give v1.7 (or even heimdall) a try before giving up.
The steps to flashing a stock firmware are already described in a couple of other threads, like: http://forum.xda-developers.com/showthread.php?t=818556
Nonetheless, here a quick sum-up of what you have to do:
2.1. Open up Odin.
2.2. Put your phone in the "Download mode" with the 3-button-combo (Volume Down + Home + Power).
2.3. Connect your phone to your computer (DO NOT CONNECT THE PHONE BEFORE OPENING ODIN OR THIS WILL NOT WORK).
2.4. Odin should recognize your phone and one of the "com" boxes should light up yellow. If this isn't the case, try repeating the previous steps and eventually connect your phone to another USB port.
2.5. Select your firmware in Odin.
2.5.1. --OPTIONAL-- If you want your phone to be like new, you can select "Re-Partition" in Odin, which will make it repartition your Internal SD. In this case you also have to use a .pit file (WARNING -- you will lose all of your installed applications and settings).
2.6. Take a deep breath and click the "Start" button.
2.7. Wait for the firmware to be flashed and for the device to be restarted.
2.8. You now have a stock firmware. If you also selected "Re-Partition" in Odin, all your programs and settings will be gone and your device will be like new.
3. Rooting your phone and flashing a custom Kernel.
--Why, when, where: Rooting your phone will get you super-user permissions to Android (super-user is Linux's equivalent of "Administrator rights" in Windows). This will allow you to execute some programs that need root permissions, access partitions that you otherwise couldn't and do other cool stuff with it.
--Prerequisites: Stock firmware (as most --if not all-- of the custom ROMs or kernels have root permissions already), Odin or Heimdall.
There are many ways to get root permissions on your device, like with special apps (OCLF for example), with CWM (aka ClockWork Mod) or, my preferred method, flashing a kernel that has this built-in. For this example I will use the SpeedMod Kernel, which is my preferred one. If you have another kernel that you like and that has root built-in, you can use that one.
3.1. Download your preferred kernel (the version for Odin, not the one for CWM).
3.2. Open up Odin or Heimdall.
3.3. Put you phone into "Download mode" and connect it to your computer (DO NOT CONNECT THE PHONE BEFORE OPENING ODIN OR THIS WILL NOT WORK).
3.4.1. If you are using Heimdall, unpack your kernel until you end up with a file called zImage. Select that in Heimdall in the box for "Kernel (zImage)" and click Start.
3.4.2. If you are using Odin, select the file you downloaded in the PDA box and click Start.
3.5. After your Phone reboots, go into "Recovery mode" and go to "Advanced Speedmod ULK features" -> "ROOT / Install Superuser".
3.6. After rebooting the phone again, you should have root permissions.
4. Deodexing your apps and framework.
--Why, when, where: The system applications and the framework files on the Android OS are normally 'odex'ed. By deodexing, you will get rid of the .odex files that come with every apk and jar file and you will be able to edit the apks like any other apk. It will also save you a wee bit of space, and make your apps launch a wee bit faster.
--Prerequisites: Stock firmware (as most --if not all-- of the custom ROMs are deodexed already), xUltimate (this is what I found to be the easiest, if you know any software that is better, please let me know), root permissions.
You can download xUltimate from here: http://www.droidforums.net/forum/xeudoxus/47283-release-xultimate.html
There are more ways to deodex your apps, but I found xUltimate to be the easiest.
4.1. First of all, you need to get the files from "/system/app" into the subdirectory "origi_app" and all of the files from "/system/framework" into the subdirectory "origi_frame". Both "origi_app" and "origi_frame" should be in the folder you extracted xUltimate to. If they don't exist, create them yourself. There are actually two ways to get the files there, either with xUltimate itself (options 1 and 2) or by copying them to your SD with "Root Explorer" for example and then copying them from your SD to your computer (or with adb of course).
4.2. Deodex the apps and framework with xUltimate, options 3 and 4.
4.3. After deodexing is finished, the deodexed files will be located in the directories "done_app" and "done_frame" in your xUltimate folder. You have to get these files back to their original directories, in /system/app and /system/framework. Again, there are a couple of ways to do this, either with adb (MOST RECOMMENDED ONE), or with "Root Explorer". For the adb method, you should open a command prompt and execute following code:
Code:
adb shell
su
stop
mount -o rw,remount /dev/block/mmcblk1p21 /system
rm /system/app/*.odex
rm /system/framework/*.odex
cp /sdcard/done_app/* /system/app/
cp /sdcard/done_frame/* /system/framework/
mount -o ro,remount /dev/block/mmcblk1p21 /system
reboot
5. Optimizing and zipaligning your apps.
I wasn't yet successful at optimizing or zipaligning. Optimizing (aka Compressing) the apps gave me a lot of FCs, optimizing the framework files gave me bootloops. If anyone has any advice on this, I'd be very thankful.
Also, see post #2
6. Protecting your screen.
--Why, when, where: This is not about protecting your screen from scratches, but rather about protecting it from degradation over time. As you might already know, AMOLED screens are prone to the "burn-in" effect. To elaborate a little: AMOLED uses Organic LEDs to display the amazing graphics you see on your display. These OLEDs are very good at displaying bright, colorful pictures, they have a downside though -- they fade over time. That means, the more a specific OLED is used, the less light it emits. If the whole screen would degrade at the same pace, that wouldn't be such a BIG problem, but the very nature of the OLED screens makes them degrade unevenly. That means the OLEDs that are used more frequently (like clock, phone signal, wifi, notification bar), get dimmer faster and this leads to ugly "shadows" on fullscreen apps. To be able to keep your screen as beautiful as new, I got a couple of tips, so that the display degrades more evenly and you avoid the ugly "shadows".
!! Most users won't even notice these degradations, also they won't be noticeable in 90% of use-cases and they will only appear after longer use (6 months+), but you can still use these tricks if you want your display to be almost as good as new a couple of years from now !!
6.1. Don't set brightness to 100%. At least not all the time. You should best be using a brightness setting that fits your ambient light, or the "Automatic brightness" setting. This will ensure that the OLEDs don't wear out as fast (the brighter you use them, the faster they will degrade).
6.2. Use a grey notification bar. The notification bar is the biggest "static" element on the screen. Most apps that are not fullscreen, will also show the notification bar, and this leads to an uneven degradation in that area if it isn't a neutral color. If you use a white notification bar, the OLEDs there will get dimmer faster and you will get an ugly shadow when using fullscreen apps, if you use a black notification bar, it will not degrade as fast as the rest of the screen and that area will be "brighter" in fullscreen apps, that's why I recommend a medium grey.
6.3. Use as little static elements as possible. If you don't need the clock in the notification bar, get rid of it. Get a theme that uses grey or green icons (see next step why) and try not to leave the phone on over night displaying the same static image.
6.4. Avoid blue. As you can see here for example: http://img24.imageshack.us/img24/8057/new1ls.png the blue OLEDs are degrading at a much faster pace than the green or red ones, this is why you should avoid using blue wallpapers or blue themes, they will make your display degrade faster than if you use a green theme and a green wallpaper for example.
These tips won't make your screen live forever, it will degrade too, but by using these tips, at least you can assure that you will have the most of your awesome display even in a year or two from now.
7. Theme-ing your phone.
Coming soon...
8. Unlocking your phone.
--Why, when, where: If you bought your phone with a contract, chances are that it might be locked in that specific network. If you want to also use other SIM cards in it, that are from another provider, you will have to unlock the phone (!! WARNING !! in most cases this will lead to a void warranty, please consult your contract).
--Prerequisites: Root privileges, adb.
8.1. Get the /efs/nv_data.bin file from your device to your computer. You can do this either with adb or by copying the file to your SD card with "Root Explorer" and then copying it over to your machine from the SD (Be sure to keep a backup of this file and the /efs/.nv_data.bin.md5 file.)
8.2. Open up the file in a hex editor, go to the address 0x181468, where you will see something like this:
FF 01 00 00 00 00 46 46 46...
We are interested in that first '01', that means the phone is locked. Just change it to '00' and save the file. Copy it back to your SD card and then with "Root Explorer" back to it's original location (or 'push' it directly with adb). Then remove the .nv_data.bin.md5 file and restart the device (Again, be sure to make copies of these files before modifying or deleting them!). After this, you should be able to insert any SIM card into your device and it should work without the need for any further hacks.
9. Setting up 'adb' on your machine.
--Why, when, where: adb (aka "Android Debug Bridge") is a tool that will let you execute remote commands on your android device. It is useful for debugging, accessing and copying files from/to your device and much more.
--Prerequisites: The android SDK, which you can download from here: http://developer.android.com/sdk/index.html and the USB drivers for your phone, which you can get by either installing Kies or by downloading and installing these drivers: http://www.mediafire.com/?a6ni32dk6nn953b (password is 'ragin' -- I didn't test them, so feedback on these is welcome).
9.1. Unpack the downloaded android-sdk.
9.2. Go to the unpacked directory and launch the SDK Manager.
9.3. Go to "Available packages" -> "Third party Add-ons" -> "Google Inc. add-ons" and tick the box next to "Google Usb Driver package" and the click on the "Install Selected" button. This will download and install the Google USB Drivers.
9.4. Whenever you want to connect to your phone through adb, make sure that you have enabled "USB Debugging" under "Settings" -> "Applications" -> "Development".
9.5. You should now be able to open up a command line ("Start" -> "Run..." -> Type "cmd" and click "OK"), cd to the subfolder "platform-tools" under the folder where you unpacked android-sdk and run "adb" in there.
Take some time to get used with the commands that adb offers, as these will help you to debug problems when you encounter some.
10. Lagfixing
--Why, when, where: It is said that the default filesystem that is being used for the partitions on the SGS (RFS) is having slow read times and thus the programs launch a bit slow, sometimes perceived as "lag". This can be fixed by converting the filesystem on the most used partitions to a more modern filesystem, like the ext filesystem, which not only has a bunch of improvements over such old filesystems like RFS, but also seems to be a bit faster.
--Prerequisites: A kernel that supports lagfix.
10.1. Since every kernel has it's own way of converting your FS, you should best look into the documentation of your kernel on how you can apply a lagfix. Some even apply it automatically for you (as in, "lagfix on" is their default setting).
11. Do NOT overcharge
--Why, when, where: Almost all new batteries have an overcharging protection. This means that the protection that is built into the battery will not let it charge to 100%. This is a feature, not a bug! This will help prolong your battery life while also keeping it safe from overheating/explosion/etc. Do not try to trick it and unplug and plug again until you see 100%, just get used to the fact that you can't have 100% battery anymore and live with it, or you risk destroying your battery.
12. Call recording
--Why, when, where: Most Galaxy S firmwares don't have the ability to record both streams of a call. This is not a bug, it was designed like this because in most countries it is illegal to record someone without their permission. Yes, there are apps that will let you record a call, but without software support, it will record the other end from the microphone, which will result in low quality, but there is a workaround.
This might be illegal in your country! I'm not responsible if you get sued for recording someone without their permission.
--Prerequisites: Root permissions, adb/root explorer, a 2.2.1 firmware.
12.1 Download the attached "CallRecord.zip" and unpack it.
12.2 After unpacking you should have 3 .so files. You need to get these files into your /system/lib folder with either adb or by copying them to the phone and then using "Root Explorer" to copy them to the proper folder.
12.3 Reboot.
12.4 After the phone has rebooted, you can use most apps that are on the market to record calls properly (that means not from the microphone). I use AllCallRecorder because it is simple and does the job. There are also Phone.apk's that have call recording built in, you could also install one of those and record your calls with it.
That is all for now. I will add more information as time goes by and I hope this will become a full guide on how to make the best out of our devices. If you have constructive criticism, questions or any ideas or tips on how to improve this, please let me know. If you don't have anything constructive to add to this thread, please DO NOT post. If my troll alarm goes off, I WILL ignore you.
Thanks goes to:
ragin for the USB drivers.
I have learned most of the stuff I put here from various searches on Google and the xda forums and I may not remember the exact threads I got them from. If you feel I have copied your work without giving you credit, I am very sorry for that. Please let me know via a post or a PM and I will link you in the "Thanks".
I am sorry if my English is bad, it's my third language though. I hope that the post is understandable by most people.
This post will contain instructions for *nix based operating systems
Because I am using Linux myself and because it is much easier to do stuff in the command line on Linux than it is on Windows, I will mostly post instructions for *nix systems. If anyone wants to help out by "translating" them over for Windows machines, I can include it in the next post.
Optimizing and zipaligning
I have managed to Optimize and zipalign the apps in /system/apps with the following code.
You need to run this on a *nix distribution (I used Ubuntu) with at least the following packages installed: bash, zip, unzip, optipng. Put all the .apk files from /system/app in a folder on your machine, cd to that folder and execute this code snippet.
Also, beware that some of the apps might not work (I had for example FCs with the camera and the phone app), I'll try to figure this out and make it pretty much foolproof. Currently everything but the .9.png files are optimized (the .9.png files are some special files that can't be treated like normal png files).
Code:
for apk_file in *.apk; do
file_name=`echo $apk_file | sed -r s/.apk//`
echo -ne "Unpacking\t$file_name.apk... "
mkdir $file_name
unzip -qq $file_name.apk -d $file_name
cd $file_name
echo -ne "Done.\n"
echo -ne "Optimizing\t$file_name.apk... "
for pngfile in $(find . -name '*.png' | fgrep -v .9.png); do
optipng -quiet -o 5 $pngfile
done
echo -ne "Done.\n"
echo -ne "Repacking\t$file_name.apk... "
zip -q -0 -r ../$file_name.apk *
cd ..
rm -rf $file_name
echo -ne "Done.\n"
echo -ne "Zipaligning\t$file_name.apk... "
zipalign -fv 4 $apk_file $apk_file.za
mv $apk_file.za $apk_file
echo -ne "Done.\n"
done
EDIT: I added the -0 flag to the zip command, since you should never "compress" apk files, because this leads to the FCs I was experiencing.
Post also reserved.
Last reserved post. You can start flaming now.
shantzu said:
Last reserved post. You can start flaming now.
Click to expand...
Click to collapse
Posted in the wrong place... try reading the faq's about where this belongs.
davidf said:
Posted in the wrong place... try reading the faq's about where this belongs.
Click to expand...
Click to collapse
Well, the rules of the development section state: "Rom Development - only meant for very advanced technical discussion directly related to ROM development activity and the delivery of actual ROMs and ROM components ONLY."
I'd regard this as an "advanced tehnical discussion", since it also contains information on how to deodex and (to come soon) optimize/zipalign your apps, that's why I thought it would belong here. I would also like this to be a place for advanced discussions on best practices on deodexing, theme-ing, and otherwise modifing a stock ROM manually. If the moderators still think that this doesn't belong here, I'm sorry, and would like to ask them to move it to the proper Forum.
Sticky Material.
Don't you think your Title is misnamed? The thread contains much more than just a guide getting most out of our SGS.
Very good effort anyway.
ragin said:
Sticky Material.
Don't you think your Title is misnamed? The thread contains much more than just a guide getting most out of our SGS.
Very good effort anyway.
Click to expand...
Click to collapse
Well, I didn't know what else to name it, and didn't want to use a really long name. I think this title best describes what it's about...
Thank you for your reply!
very good post. It'll be extremely helpful for new users i reckon.
question
can this method be used on almost any samsung galaxy? (i have galaxy 551)
and about deodexing...is xUltimate a general app for any Android phone or only for SGS ?
Awesome stuff thanks for this cleared up a few things
waveboy2u said:
can this method be used on almost any samsung galaxy? (i have galaxy 551)
and about deodexing...is xUltimate a general app for any Android phone or only for SGS ?
Click to expand...
Click to collapse
Well, the program seems to be posted in the "Motorolla Droid" forum, so I don't think it was even intended for the Galaxy S. If I were to guess, I'd say it might work on any Android device. Just be sure to make a backup in case anything goes wrong.
Thanks alot! Never knew the degrades display.
Sent from my GT-I9000 using XDA App
Shantzu, first, thank you very much for this valuable contribution!
While I agree that it is related to "highly technical discussion", it's not directly connected to ROM cooking/development. In fact, this is the kind of thing that people should read before they start mucking about in the dev section
I've gone ahead and moved it to the general section and made it a sticky topic for now. However, those are starting to pile up in this section, so we'll likely roll up several useful threads like this one into one unified reference sticky here soon.
sirphunkee said:
Shantzu, first, thank you very much for this valuable contribution!
While I agree that it is related to "highly technical discussion", it's not directly connected to ROM cooking/development. In fact, this is the kind of thing that people should read before they start mucking about in the dev section
I've gone ahead and moved it to the general section and made it a sticky topic for now. However, those are starting to pile up in this section, so we'll likely roll up several useful threads like this one into one unified reference sticky here soon.
Click to expand...
Click to collapse
I was thinking about this guide as some kind of "cook your own ROM directly on the device", that's why I was also including tips on how to deodex the apps and I'd also like to include tips on how to set up themes (not install third party themes, but rather explain where each icon can be found and how it can be modified) and other mods. Anyway, if you think it better fits in the General section, I'm fine with that, as you can see I'm pretty new in these forums and not that experienced (for example I have also seen a guide on how to manually unlock the phone that was stickied on the Developers section).
Anyway, sorry again for the trouble and thanks for clearing it up!
Very good post. Thank you!!
Very good work. One thing i noticed though: you use ext fs for the system rw remount. This i think will only work for ext converted system partitions not the original rfs system.
Sent from my GT-I9000 using Tapatalk
liraindon said:
Very good work. One thing i noticed though: you use ext fs for the system rw remount. This i think will only work for ext converted system partitions not the original rfs system.
Sent from my GT-I9000 using Tapatalk
Click to expand...
Click to collapse
I know, it normally shouldn't work, but it actually does. I don't have any lagfix applied and it works just fine. I will try and see though if I can come up with a more general command that 100% works in all cases.
EDIT: ok, not specifying any filesystem at all works too. I will have to see if this also works with a lagfix enabled, but I guess there shouldn't be any problems.
Thanks for your comment!
whoa didnt know about degradation... thanks!
nice
very good write up.. +1
I have made a script of the most popular guide for rooting the Thunderbolt right now.
http://www.androidpolice.com/2011/0...he-htc-thunderbolt-and-unlock-its-bootloader/
Long story short, I have not tested this enough to guarantee it will work for everyone. It can run on both Mac and Linux, and only requires that curl is installed (by default on Mac, and most Linux distros). I have made absolutely sure that the script did not run anything what-so-ever that is damaging without letting you verify that you want to continue several times.
Please only test at this time if you know your way around adb, and are willing to run into non-damaging issues (it may fail, but I assure you, no damage is done)
usage
Make sure the phone is plugged in and adb is installed and working, and device is showing. Start a terminal IN the adb directory and put this script in there. Start it as usual in a terminal? (rename oneClick.txt to oneClick.sh)
Both AndroidPolice & AndIRC are nor affiliated with this root process or responsible for it.
has anyone tested this? i have a mac but am not experienced in adb...was going to give it a shot when i got off work today.
@kdb424, is there some way you could provide more detailed instructions for adb noobs? if not, i'll try dbzfanatic's easy root or attempt this after learning adb myself first.
First off, thanks andrew8806 for doing that edit. I knew I had missed something.
Second, the only thing you should have to do on a mac to verify this is going to work is make sure adb is installed, and make sure your device comes up in adb devices.
If that's good, all you need to do is open a terminal and type "cd " and drag and drop the folder that adb is installed into (depending on where you installed it, it could be different or I'd just type it) then put the script in there and run
sh ./oneClick.sh
and follow the instructions in the script.
will this still wipe data?
Yes, absolutely. Long story short is that it requires that an old build be flashed on your phone so that can be hacked. It's the only know method of rooting now. All one clicks are just abusing that and simplifying as much as possible.
just got done rooting with my macbook pro. the script kdb424 wrote worked really well. there were a few hiccups along the way, not sure if they were from my terminal glitching or the script or my phone or whatever, but it worked, flashing clockworkmod right now to change the ROM.
for anyone curious, sometimes the script would just stop because some command missed or something. i would just edit kdb424's script to remove the portion that i already completed and rerun the script essentially starting it up again wherever it messed up. at the end i ran the last few lines myself but overall it was quite helpful to root, especially for someone new to ADB like me.
bkiminfinity said:
just got done rooting with my macbook pro. the script kdb424 wrote worked really well. there were a few hiccups along the way, not sure if they were from my terminal glitching or the script or my phone or whatever, but it worked, flashing clockworkmod right now to change the ROM.
for anyone curious, sometimes the script would just stop because some command missed or something. i would just edit kdb424's script to remove the portion that i already completed and rerun the script essentially starting it up again wherever it messed up. at the end i ran the last few lines myself but overall it was quite helpful to root, especially for someone new to ADB like me.
Click to expand...
Click to collapse
Thank you so much. I'm glad to hear success. I know ADB has some issues that I can not resolve. It's the same no matter how you root. Do you remember what portions gave you trouble specifically? I could take a closer look at it and iron hose things out. Once again, thanks again, and glad I could help!
Willing to try this once things get ironed out.
kdb424 said:
Do you remember what portions gave you trouble specifically? I could take a closer look at it and iron hose things out. Once again, thanks again, and glad I could help!
Click to expand...
Click to collapse
all of the md5 sums and outputs were correct so there were no brick possibility i think. if i recall correctly, sometimes pushing the PS05IMG.zip would not execute properly and the script would not continue until i reran it. i think that might've happened with both the downgrade and the s-off one, can't say for certain. some parts that hiccuped may have just been my tbolt needing extra reboots so i don't think that was the script's fault. towards the end i would just run the lines myself, i think i had to redo the ./adb shell /data/local/psneuter line the most before it took properly. i believe that was it, like i had said it was quite helpful and greatly expedited the rooting process.
Im expierienced with ADB and I have a mac. Will be trying this out now. Reporting back soon.....
Edit (after using scipt)
While the script is great, the end just turns into a #failfest. It refuses to the final file to my SD card and sites that its read only. The end I am doing manually. The rest of the script is amzing and gets a A+
Thank you so much for your feedback. I'll be looking into that. If I come up with any typos in the script, I'll update and let you know. ADB is known to act odd at times, so it may be pure ADB's fault. Definitely taking a look into though,. Enjoy your root!
I just got root using the OG method on my mac and it was a PITA. I think the big thing to know is you can use every step listed by jcase, but you need to use ./adb instead of JUST adb.
After completing root the long way, I imagine this would expedite things exponentially.
Hey i had two Fire HD 10 2019 (9th Gen) Devices.
With one i was playing around, using it casually. I used Amazon Fire toolbox for some personalization, mostly debloating and running it on Nova launcher but as an passionate Android User i wanted Root of curse. Well long story short this Device updated to FireOS 7.3.1.1 because i was not careful enough. But i still have the second (never used or turned on) Device with the not-updated firmware.
Now according to this Post: https://forum.xda-developers.com/showpost.php?p=81211523&postcount=228 it is somehow possible to gain root even if its only temporary (that would be enough for me atm and very nice if accomplishable) but i am actually a bit scared to turn it on and disable OTA with ADB because firstly i am not sure if that is a permanent fix or if i have to apply the command every time i turn the phone on (could possibly be done with tasker or something somilar?) and secondly if the update could be faster than me blocking it (maybe i'm to paranoid right now but i want to make sure i get root on that device and really dont want to miss my chance for it because of OTA updates.
Also i tried to root it but without sucess (well i didn't know there was another hard button combination when the white triangle was showing so i was really close away from the finish line it feels like) then i went to sleep and the next morning i had the new update applied.. really unfortunate. Well thatswhy i want to make a better job with the second device!
Thanks in advance for any help! Have a wonderful day and excuse any typings
M4XXX said:
Hey i had two Fire HD 10 2019 (9th Gen) Devices.
With one i was playing around, using it casually. I used Amazon Fire toolbox for some personalization, mostly debloating and running it on Nova launcher but as an passionate Android User i wanted Root of curse. Well long story short this Device updated to FireOS 7.3.1.1 because i was not careful enough. But i still have the second (never used or turned on) Device with the not-updated firmware.
Now according to this Post: https://forum.xda-developers.com/showpost.php?p=81211523&postcount=228 it is somehow possible to gain root even if its only temporary (that would be enough for me atm and very nice if accomplishable) but i am actually a bit scared to turn it on and disable OTA with ADB because firstly i am not sure if that is a permanent fix or if i have to apply the command every time i turn the phone on (could possibly be done with tasker or something somilar?) and secondly if the update could be faster than me blocking it (maybe i'm to paranoid right now but i want to make sure i get root on that device and really dont want to miss my chance for it because of OTA updates.
Also i tried to root it but without sucess (well i didn't know there was another hard button combination when the white triangle was showing so i was really close away from the finish line it feels like) then i went to sleep and the next morning i had the new update applied.. really unfortunate. Well thatswhy i want to make a better job with the second device!
Thanks in advance for any help! Have a wonderful day and excuse any typings
Click to expand...
Click to collapse
Try it to use NoRoot Firewall (VPN firewall) from Google Play, enable Stat on Boot, create VPN connection, select APPS tab, find DeviceSoftwareOTA app from list and set the check box to X (deny any internet access) on Wi-Fi and mobile data
Check boxes:
√ = Allow from internet access
X = Deny from internet access
@Supersonic27543 @dr_docdoc @diplomatic @DB126
Can somebody please confirm this? I can not trust this dude anymore regarding his latest posts. I think he is a troll in some sort..
I was thinking about adb shell pm hide but yeah as i said i have the concerns mentioned above.
M4XXX said:
@Supersonic27543 @dr_docdoc @diplomatic @DB126
Can somebody please confirm this? I can not trust this dude anymore regarding his latest posts. I think he is a troll in some sort..
I was thinking about adb shell pm hide but yeah as i said i have the concerns mentioned above.
Click to expand...
Click to collapse
I simply followed this post (below), and so far . . . no updates. As the OP suggests, others have suggested to him this *MAY NOT* be permanent. However, as the OP also reports, he had another device for 7 months with no update or even check for update. On all seven of my Fire HD 10 2019 devices, no update has occurred or even been checked - just the same:
https://forum.xda-developers.com/showpost.php?p=81095517&postcount=147
As for the adb shell stuff, that is beyond my current understanding. Learning about the bootless root that @diplomatic put together, I'm wondering that perhaps there is a script method that can be loaded after boot to ensure OTA is disabled every time. But then again, I'm not aware if it would still be considered permanent or what could re-enable the OTA (as the OP to post 147 above had said in the following post 149).
dr_docdoc said:
I simply followed this post (below), and so far . . . no updates. As the OP suggests, others have suggested to him this *MAY NOT* be permanent. However, as the OP also reports, he had another device for 7 months with no update or even check for update. On all seven of my Fire HD 10 2019 devices, no update has occurred or even been checked - just the same:
https://forum.xda-developers.com/showpost.php?p=81095517&postcount=147
As for the adb shell stuff, that is beyond my current understanding. Learning about the bootless root that @diplomatic put together, I'm wondering that perhaps there is a script method that can be loaded after boot to ensure OTA is disabled every time. But then again, I'm not aware if it would still be considered permanent or what could re-enable the OTA (as the OP to post 147 above had said in the following post 149).
Click to expand...
Click to collapse
Thank you very much for the help. I know I can not speed things up, from a development standpoint but I also wanted to use it until there is a viable root option available
M4XXX said:
Thank you very much for the help. I know I can not speed things up, from a development standpoint but I also wanted to use it until there is a viable root option available
Click to expand...
Click to collapse
Yo - I think you missed it!
This sucka HAS BEEN ROOTED!
https://forum.xda-developers.com/hd8-hd10/general/fire-hd10-2019-t3979343/post81211523#post81211523
dr_docdoc said:
Yo - I think you missed it!
This sucka HAS BEEN ROOTED!
https://forum.xda-developers.com/hd8-hd10/general/fire-hd10-2019-t3979343/post81211523#post81211523
Click to expand...
Click to collapse
I've seen that Post and i was REALLY excited about it but i couldn't get it to work.. Could you eventually guide me on the way?
Need help with Step 9 !?!?
https://forum.xda-developers.com/showpost.php?p=79626434&postcount=135
I am stuck at Part 9 !!
when i restart at this point nothing happens and when i start init.d scripts support app and "run scripts now"" i get the following execution results:
Code:
[COLOR="Red"]Can't aquire root privileges (date)[/COLOR]
[B]Executing scripts from /storage/emulated/0/init.d (date)[/B]
suboot.sh
[COLOR="red"]/storage/emulated/0/init.d/suboot.sh[121]: ./mtk-su: No such File or Directory[/COLOR]
In Magisk Manager i see that Magisk is not installed (and i can't without TWRP, right?)
I'm just stuck at this Point. I have read in some other Forum that there is a button combination that i can press while seeing that white triangle when trying to enter recovery mode to actually be able to enter it. and yeah from there on it would be easy i guess to install magisk and maybe init.d will recognize it then?
Thanks for helping
I got it to work! Thanks to the incredible help of @dr_docdoc :good:
I picked arm64. By changing to arm it worked
Very happy about it. thanks again!
I guess no luck when you are on 7.3.1.1?
BXM500 said:
I guess no luck when you are on 7.3.1.1?
Click to expand...
Click to collapse
not for now as far as I know it. my other device isn't working either
x
Try this:
Code:
adb shell pm disable-user com.amazon.device.software.ota
adb shell pm disable-user com.amazon.device.software.ota.override
adb shell pm disable-user com.amazon.kindle.otter.oobe.forced.ota
adb shell pm disable-user com.amazon.settings.systemupdates
Remove Amazon's crappy and stubborn Fire launcher (you must have another launcher installed before you do this):
Code:
adb shell pm disable-user com.amazon.firelauncher