There is now a super thread over here with this root information and some more recoveries. I plan on expanding as more things are developed for the Rugby Pro.
I have added other hacks to this thread below the root download links. Enjoy.
The below guide outlines how to gain root on the Samsung Galaxy Rugby Pro (SGH-I547 ATT / Bell (Yes, Canada works!) / commanche). Please read through the full guide before attempting to root your device.
You will need ODIN v3.04 in order to gain root on the Rugby Pro (comanche), I will not post a link due to the nature of the package. Google has plenty of links for it.
BIG thanks to utkanos for all the help and making this a reality
Install instructions -- goldenlederhosen has provided some further information and detail about the below procedure here
Please read his post as well as the instructions before attempting this procedure
Install drivers from link below
Download necessary packages (clockwork recovery, root update) from the links below
Copy root update to your devices sdcard(s) -- Copy to both if external SD card is present
Charge phone to at least 80%
Power off the phone
Unplug from USB / Charger
Boot into download mode (Home + Volume Down + Power)
When asked if you want to continue, press Volume Up to enter download mode
Plugin phone and
Launch ODIN
Check the checkbox next to "PDA"
Click the PDA button
Select the comanche_cwr_6015_utkanos.tar.md5 file
Make sure only "Auto Reboot" and "F. Reset Time" are selected
Click start
Your phone will reboot one the flash is complete
You now have Clockwork Recovery, continue with the steps to get root
Power off your phone
Unplug from USB / Charger
Boot into Clockwork Recovery (Home + Volume Up + Power -- Release when Samsung logo appears)
Select "Install zip from sd card"
Select "Choose zip from sd card"
Navigate to zip
Select zip
Confirm
Reboot
You should now have root
I am not responsible for anything bad that comes to your device when using the information posted in this thread. Everything here is dangerous, may cause a brick, will void a warranty and has the potential to just plain wreak havoc. Do not complain you followed my instructions and met with a dead device. Consider yourself warned
I've tested to the best of my ability, but I am one person with one device, I cannot catch all potential failure modes. If you find a problem and a fix, or have information that should be added let me know and I will update the necessary information.
Download Links
Head over to the super thread here (link) for links.
CWR Touch / ODIN
Courtesy of childrenofthehorn there is a now a Clockwork Recovery Touch and ODIN images for the ATT varient. The thread is: http://forum.xda-developers.com/showthread.php?t=1990519
Rootz Wiki Forum
childrenofthehorn has gotten a dedicated forum setup over at Rootz Wiki. Check it out: http://rootzwiki.com/forum/556-galax...o-development/
Works like a charm!
Thanks for doing this guys. I was thinking I would have to create an insecure kernel for the stock ROM in order to get root. You saved me a lot of time & energy. Expect a donation coming from my way.
dweide9 said:
Thanks for doing this guys. I was thinking I would have to create an insecure kernel for the stock ROM in order to get root. You saved me a lot of time & energy. Expect a donation coming from my way.
Click to expand...
Click to collapse
Thank you much for the donation
Would you be willing to pull an image of the stock boot partition (dd if=/dev/block/mmcblk0p7) and PM me a link?
Also: check the OP, I've added some info on how to get tethering (after rooting) without the need for a dedicated ATT tethering plan.
re: post-root stuff
>Would you be willing to pull an image of the stock boot partition (dd >if=/dev/block/mmcblk0p7) and PM me a link?
I would if I had any experience. My plan to insecure the kernel would have been my 1st time getting my feet wet with such a thing.
>Also: check the OP, I've added some info on how to get tethering (after rooting) without >the need for a dedicated ATT tethering plan.
Thanks, I did but I don't find Tethering Manager. I did find Tethering Provision. Is that the same?
dweide9 said:
I would if I had any experience. My plan to insecure the kernel would have been my 1st time getting my feet wet with such a thing.
Click to expand...
Click to collapse
You can copy the contents of boot by:
Install a terminal emulator from the market
Launch terminal
su
Accept request for root
dd if=/dev/block/mmcblk0p7 of=/mnt/sdcard/mmcblk0p7_boot.img
Transfer mmcblk0p7_boot.img to your favorite cloud storage provider
Share link
If you run into trouble or have any questions let me know.
dweide9 said:
Thanks, I did but I don't find Tethering Manager. I did find Tethering Provision. Is that the same?
Click to expand...
Click to collapse
Provision is a separate app. When I'm back by my laptop in the morning I'll double check the paths and report back. I froze mine using Ultimate Backup or Titanium Backup. I forget offhand.
Sent from my SAMSUNG-SGH-I547 using Tapatalk 2
boot partition image
I tried to provide the link to both tarball & zipped files of my boot partition image, but I haven't done 10 posts yet, so xda has restricted me. Let see if a little disguise will work:
secured [email protected]/#folders/0BwUellf9svE3M01kampaMU54NWc
So what fun stuff can you do with this file & how would my image be any different then yours? Or is it another issue, like uploading being restricted because you're a developer?
Also, I'm interested in learning the process of how you created/edited the files , in order to root the Rugby Pro. I'm sure your busy, so pointing me toward a tutorial would be great.
kemonine96 said:
Provision is a separate app. When I'm back by my laptop in the morning I'll double check the paths and report back. I froze mine using Ultimate Backup or Titanium Backup. I forget offhand.
Click to expand...
Click to collapse
Looks like TetheringProvision.apk is the one to freeze (do not delete unless you have a backup). If you try this let me know.
dweide9 said:
I tried to provide the link to both tarball & zipped files of my boot partition image, but I haven't done 10 posts yet, so xda has restricted me. Let see if a little disguise will work:
secured [email protected]/#folders/0BwUellf9svE3M01kampaMU54NWc
Click to expand...
Click to collapse
Thanks for the file. I just finished pulling it.
dweide9 said:
So what fun stuff can you do with this file
Click to expand...
Click to collapse
I plan on using a stock boot image so I can put together an ODIN image that will flash the phone back to a stock state. If you root your phone or have a custom recovery / system / boot OTA updates will generally fail to apply. The best way to get an OTA update applied is to rollback to stock and install the OTA.
dweide9 said:
how would my image be any different then yours?
Or is it another issue, like uploading being restricted because you're a developer?
Click to expand...
Click to collapse
The boot partition should be the same across devices unless you make modifications.
I had to blindly update the boot partition on my device to get root, so I do not have an un-changed copy of it. In order to get an OTA update applied and to work with some Cyanogen / Clockwork Recovery stuff I will need a clean boot partition image.
dweide9 said:
Also, I'm interested in learning the process of how you created/edited the files , in order to root the Rugby Pro. I'm sure your busy, so pointing me toward a tutorial would be great.
Click to expand...
Click to collapse
I worked with a few people to get help putting together an ODIN image that allowed me to get custom recovery and the clockwork recovery update.zip. There is no general guide on the steps necessary.
If you are interested in diving into the custom rom / recovery stuff I will be doing some work with improving clockwork recovery for the Ruby Pro (commanche) and hopefully working on a Cyanogenmod 10 (JellyBean) port in the future. I am working on some items for the Rugby Smart (apache) at present, as soon as that stuff is taken care of I'll be focusing more on the Rugby Pro (commanche). If you are interested in taking a shot at updating the clockwork recovery for the commanche let me know and I can maybe point you in a few directions to get you going.
stuff
>I had to blindly update the boot partition on my device to get root, so I do not have an >un-changed copy of it.
You probably know this, but here's where I downloaded Samsung's ROM (disguised again, & I'm pretty sure the new "c" version is for Canada) Just search for sgh-i547:
[email protected]
>If you are interested in diving into the custom rom / recovery stuff I will be doing some >work with improving clockwork recovery for the Ruby Pro (commanche) and hopefully >working on a Cyanogenmod 10 (JellyBean) port in the future.
I am interested. Realize I have miniscule programming skills (http, xml & Google {now MIT} App Inventor).
Also, I did freeze TetheringProvision, but I rarely tether. Usually I only need to when it's raining & my home DSL slows too much. I'll let you know if I have any problems when I do finally try it.
dweide9 said:
>I had to blindly update the boot partition on my device to get root, so I do not have an >un-changed copy of it.
You probably know this, but here's where I downloaded Samsung's ROM (disguised again, & I'm pretty sure the new "c" version is for Canada) Just search for sgh-i547:
[email protected]
Click to expand...
Click to collapse
I pulled that package as well. Unfortunately it is only the GPL components they are required to release, not the full ROM sources. It does contain the kernel sources which will be very helpful down the line.
dweide9 said:
>If you are interested in diving into the custom rom / recovery stuff I will be doing some >work with improving clockwork recovery for the Ruby Pro (commanche) and hopefully >working on a Cyanogenmod 10 (JellyBean) port in the future.
I am interested. Realize I have miniscule programming skills (http, xml & Google {now MIT} App Inventor).
Click to expand...
Click to collapse
There is a lot of testing work and guess/check for the ROM building stuff. I was thinking of setting up an IRC channel on FreeNode for discussing work on the device. Would you be interested / willing to move some of the interactive discussion over there once I have a channel setup?
dweide9 said:
Also, I did freeze TetheringProvision, but I rarely tether. Usually I only need to when it's raining & my home DSL slows too much. I'll let you know if I have any problems when I do finally try it.
Click to expand...
Click to collapse
Keep me in the loop. I tend to only tether for the purpose of my tablet when I'm not near a WiFi AP. I wanted to point it out just in case, better to have it working before it's necessary.
Let me know if you want a modded stock kernel . I'l be willing to help, even though I don't have the device on-hand.
IRC channel on FreeNode is setup: #rugby-pro-dev for those that are interested.
Motorhead1991 said:
Let me know if you want a modded stock kernel . I'l be willing to help, even though I don't have the device on-hand.
Click to expand...
Click to collapse
I think we should be covered at the moment. The first priority will likely be getting a recovery nailed down and 100% before working on a customized kernel. I'm hoping to get recovery nailed sooner than later so we can do things like nandroid and similar before starting in on CM10 or another ROM.
I am also working on the Rugby Smart (apache) CM9/3.0 Kernel/CM10 stuff as well so my time with the Pro is limited at the moment. Hopefully the Smart stuff moves quickly so I can loop back around to the Pro quickly.
>I pulled that package as well. Unfortunately it is only the GPL components they are >required to release, not the full ROM sources.
Ah, learn something new every day.
>I was thinking of setting up an IRC channel on FreeNode for discussing work on the >device. Would you be interested / willing to move some of the interactive discussion >over there once I have a channel setup?
Sure, I already monitor #opennic on freenode, so I can just open another channel.
kemonine96 said:
Looks like TetheringProvision.apk is the one to freeze (do not delete unless you have a backup). If you try this let me know.
Click to expand...
Click to collapse
I deleted it, and now when I try and turn on the hotspot the device temporarily freezes and then I get the message "Unfortunatley, Settings has stopped."
MCKINLEC said:
I deleted it, and now when I try and turn on the hotspot the device temporarily freezes and then I get the message "Unfortunatley, Settings has stopped."
Click to expand...
Click to collapse
Odd, I'll have to double check my device again. Do you have a backup of the apk, or do you need a copy of it to restore?
kemonine96 said:
Odd, I'll have to double check my device again. Do you have a backup of the apk, or do you need a copy of it to restore?
Click to expand...
Click to collapse
Thanks, but I made a backup copy, Think the issue could be because it was deleted instead of frozen?
ETA, help, donation etc
I'm very interested in buying the Samsung Galaxy Rugby Pro for AT&T. However, there is no Cyanogenmod port for it yet. I really only want to have a phone if it can run a free ROM.
@kemonine96 et.al.:
When do you think a beta CM port will be ready?
I have not done any Android development and very little administration, but I am a seasoned Linux software engineer. Is there any way I can help with porting CM to this phone?
Finally, would a donation (kemonine96 has a paypal donations link) speed up the process? I can't afford to pay hundreds of dollars, but I could do something like 50....
goldenlederhosen said:
I'm very interested in buying the Samsung Galaxy Rugby Pro for AT&T. However, there is no Cyanogenmod port for it yet. I really only want to have a phone if it can run a free ROM.
Click to expand...
Click to collapse
You are not alone in that sentiment. I won't run a device I know won't receive a CyanogenMod port. The good news is as long as there is root, CyanogenMod can be made to work.
goldenlederhosen said:
When do you think a beta CM port will be ready?
Click to expand...
Click to collapse
"Soon". Myself and a couple others are working on a set of changes for the Rugby Smart (predecessor to the Pro) and once they are further along I will be looking into starting the CyanogenMod port for the Pro.
goldenlederhosen said:
I have not done any Android development and very little administration, but I am a seasoned Linux software engineer. Is there any way I can help with porting CM to this phone?
Click to expand...
Click to collapse
Most definitely, there are a few things that would help out a CyanogenMod port significantly. If you contact me via IRC (see OP) or via PM we can discuss some of the options and take it from there. Please note I leave my IRC connection active 24x7 so I may not respond right away.
goldenlederhosen said:
Finally, would a donation (kemonine96 has a paypal donations link) speed up the process? I can't afford to pay hundreds of dollars, but I could do something like 50....
Click to expand...
Click to collapse
As much as I may appreciate a donation, please hold off as I cannot commit to working on CyanogenMod for the Pro in a paid capacity I am comfortable with. I am working 50-60 hour work weeks at my day job so my free time is severely limited. I have every intention on bringing CyanogenMod to the Pro but it is a free time problem more than anything else.
Foreign anglopu
kemonine96 said:
Most definitely, there are a few things that would help out a CyanogenMod port significantly. If you contact me via IRC (see OP) or via PM we can discuss some of the options and take it from there. Please note I leave my IRC connection active 24x7 so I may not respond right away.
Click to expand...
Click to collapse
Okay, will do.
Related
Update (October 7, 2010)
Use ngholson's guide to root: http://forum.xda-developers.com/showthread.php?t=581869&page=53#post8358998
Posts in the first 40 or so pages of this thread are old old old. Try browsing through the last 10 or so pages if you have any problems.
I may put a guide for using an App to root in this first post, but I don't have time right now.
OLD OLD OLD Manual Root:
This will still work, but ngholson's guide is a lot easier and you should definitely try it first.
NOTICE / WARNING / READ THESE:
1. I give no guarantees for anything that may or may not result from following these instructions (or any mistakes made).
2. Doing this will probably void your warranty, BUT as long as you don't run some other carrier's RUU (not talking about ROMs here, talking about the official upgrade files. what's important is that your hboot version doesn't change) you can always just flash your carrier's RUU to go back to unrooted completely stock.
Known issues:
NONE! This is a clean procedure that leaves your current rom as is. Any issues you have will be related to whatever ROMs you choose to flash or additional packages you choose to flash to your current rom
Steps:
1. Upgrade to 2.1
We know this works with the initial 2.1 updates, but later updates may patch it. If you have installed additional updates from your carrier, you may have to flash the original RUU to be able to root.
2. Download and extract the Android SDK
http://developer.android.com/sdk/index.html
You really only need this for the adb binary. If anyone can suggest a better way to get it than downloading the entire SDK, let me know.
3. Download and install HTC Sync
Some carriers have specific versions of HTC Sync (I know Cellular South does).
You could also just install the adb drivers.
4. Download the hack and extract it to your SDK tools directory. (or wherever you have adb)
It's attached to this post.
5. Turn on USB Debugging on your phone
Settings -> Applications -> Development -> USB Debugging
6. Plug your phone in USB
7. Run the script
For Windows this is runindos.bat. You should be able to just double click it.
That's it. This will flash the Darch version of AmonRA's recovery.
8. BACKUP
At this point you should probably backup your current stock rom (see Recovery guide below) and backup your PRL. (navalynt has good instructions on this in his root guide).
Now you can flash a custom rom or just flash the provided su.zip (see Recovery guide below) for Superuser Permissions (root) within your current rom.
Recovery
Recovery is where you can backup, restore, and flash ROMs or additional app zips.
To enter Recovery mode on your phone, power the phone off. Then hold home and press the power button. Keep holding home until you get the recovery screen.
You'll see several options, but the first thing you'll want to use is Backup.I've always used the nandroid option, not sure of the differences between it and bart. Backing up does exactly what you'd expect: copies your current ROM to your sd card. It doesn't change anything on the phone. It does take a few minutes so be patient.
Most roms will suggest you wipe first, and there is a menu option for that in recovery also. Just choose wipe, then factory reset. This does nothing to your sd card and only wipes application data (app installed from the market, settings for any app, etc).
After you've backed up, Recovery is also where you flash new ROMs or additions to your current ROM. It's easiest to pick a rom you want on your pc, and transfer it to your phone over usb. you can either do this the normal way, or if you're already in recovery, there is a USB-MS option you can use. Some Recoveries require flashable zips to be in the root of your sd card (not in any directory). After the ZIP is on your sd card, choose "install zip from sdcard" and pick the zip of the ROM you want. That's it. After it's done flashing, reboot your phone. If you wiped and flashed a full ROM, the first will take several minutes.
If you flash a ROM and either get stuck in a boot loop or just don't like it, go back into recovery under the Backup option and choose nandroid restore. Pick the option you get (it's a directory named with your phone's serial number) and you'll see a list of backups named with the date/time they were created. Choose which one you want to restore, wait a few minutes, then reboot and you'll be back to exactly where you were.
I've learned that the exploit used on the Sprint Hero doesn't work on the CS Hero because it uses mmap_min_addr. This means that exploits which rely on a null pointer dereference (like the Sprint exploit) won't work.
So here's what I think I need:
1) I'll be watching bugtraq, etc... for non null pointer dereference local kernel vulnerabilities. (I don't think I know 100% what that means yet.)
2) I also need to learn how to know if a vulnerability is applicable. Like this one http://www.securityfocus.com/bid/36834 . I don't even know really where to begin to see if I can use that.
3) Once I've found a vulnerability, how do I exploit it? I realize there will probably be proof of concept for the exploit, but how will I turn that into something that executes a specified command like asroot2 does. Is the source available for asroot2?
4) I wonder if I need to bother figuring out if the source used to build the kernel for CS is different from Sprint. Is a change in config.gz enough to legally require HTC to provide me with source specific to the CS version?
Keep up the good work
I know there aren't many of us, but I'm really hoping to root my hero sometime soon. I wish I could help but I picked my engineering field because it didn't require learning any computer languages haha
cdiamond333 said:
I know there aren't many of us, but I'm really hoping to root my hero sometime soon. I wish I could help but I picked my engineering field because it didn't require learning any computer languages haha
Click to expand...
Click to collapse
Glad to see at least one person interested enough to join XDA!
Though I'm afraid we're going to end up waiting until someone roots the Droid and/or Droid Eris and hope that works for us as well.
Can anyone give us an idea about where to find the RUU specific to Cellular South? Do those come from HTC, the carrier, or do they just "magically" make their way to the net from whoever happens to have access to them?
Really Like To See a Root
I would also like to see some success to this post as well... I have been with cellular south for years and this is the best phone they have produced! It only needs root access! Im a computer engineer a Miss. State, and I would love to see what I could do with this phone.
Maybe I could find an exploit... but it might take me longer to find it seeing that I am still in the beginning stages of my discipline.
But all I wanted to say is: LETS GET THIS ROOT!!
Root cellular south hero
I agree I have the htc hero from cellular south and would like to share the internet with my computer but cant tether unless phone is rooted
Hey guys!
I, too, am a CellSouth Hero haver... and I'm searching high and low for the procedure as well! I'll be checking back here and also searching round and posting anything I find.
If anyone gets an update, please email me at [email protected]
Help
I too own a CS hero and i am looking all over the net for a way to root this phone. if a way can be found will any roms work on it or will new CS specific roms have to be developed. If that is the case then i am afraid we CS users won't gain access to this for awhile as the customer base is quite small compared to sprint
OBSt4l0n said:
I too own a CS hero and i am looking all over the net for a way to root this phone. if a way can be found will any roms work on it or will new CS specific roms have to be developed. If that is the case then i am afraid we CS users won't gain access to this for awhile as the customer base is quite small compared to sprint
Click to expand...
Click to collapse
Well I've been surprised by the response to this thread, so hopefully there is more interest specific to CS than we may realize.
Ideally, ROMs made with Sprint Hero in mind will work on the CS Hero. I haven't put much effort into it without having root access yet, but when I get a chance I'm going to take the time to compare things like the radio image, etc and see just how much they differ from one to the other. If nothing else, hopefully we can replace the different pieces in the custom ROMs and be able to use them.
I will update this thread with what I find, and hopefully others will contribute as well.
??
Any news??
MrDanger said:
Any news??
Click to expand...
Click to collapse
I know, right? Seriously, is anyone out there?
i have posted treads at various sites, and they all get buried fairly quickly.
Would love to solve this issue... surely someone out there would find this to be a challenge worth taking up...
i hope.
Oh, and happy thanksgiving...
markachee message
Check Ur profile for a message that I left u.
It's just going to be a waiting game.
First someone has to find an exploit, most likely in the Linux kernel. This doesn't have to be something specific to our phone. It's more likely that it will be a generic thing that will work for us, Droid, and Droid Eris (as well as Linux in general).
It's not likely I'd be able to discover one of these exploits, so I'm watching for exploits coming out (bugtraq, etc) that might work for us. There really hasn't been anything at all since the pipe.c vulnerability that worked for the Sprint Hero.
Really one thing we need that we should be able to get now is an RUU specific to Cellular South's Hero. From what I understand, an RUU lets you reset your phone to a factory/updated image in the event something goes wrong. It wouldn't directly help us get root, but it would be a "safety net" for those of us screwing with our phones trying to get root.
Anything you guys could help dig up on where/how to find it would be awesome.
This looks promising. At least have some people in this thread that know enough to be able to compile for the phone:
http://forum.xda-developers.com/showthread.php?p=5034122
Also, realized I never mentioned I was looking at the "enlightenment" exploit set from http://www.grsecurity.com/~spender/
Just chiming in, had my Cell South hero for about a month and have been following this thread with the hope of seeing our phones rooted. I am a technician/admin with some coding and linux experience, but I am unfamiliar with rooting cellphones. anything I can do to help let me know.
tether
you can usb tether useing pda net from the market without root
I have seen pda net, i'm not interested in just tethering but thank you.
mine comes in tuesday
markachee said:
This looks promising. At least have some people in this thread that know enough to be able to compile for the phone:
http://forum.xda-developers.com/showthread.php?p=5034122
Also, realized I never mentioned I was looking at the "enlightenment" exploit set from http://www.grsecurity.com/~spender/
Click to expand...
Click to collapse
Here's the compiled programs within that exploit
Hi there,
I am new to xda and new to Android hacking.
What I wanna ask is, (I guess it's of most newbies concern as well), can we have a 100% backup of our system (stock ROM)? Obviously, it is important because:
If we perform an official (OTA) update to a new Android version. And we don't like it. It is possible to get back to the old original one which we are used to. (not everybody likes new things, and/or not every new thing is good)
If our phones are having some problems. And we have to give it back to the company for a fix. In most cases they will flash a new ROM for us. If we wanna keep using the old one (explained in #1), we have to keep a copy of it by ourselves.
If we want to try new custom ROMs, we may want to switch it back after trying.
Whenever we do any modifications, it's always better to keep a backup/roll-back point. In case anything goes wrong, we have a safeguard.
For the official warranty issue.
Yup I do see there are some official stock ROMs downloads for some particular phones. But those are not really a backup of our original ROMs. And it's always hard to verify if those downloads are the original official releases. And, if those downloads are 100% stock ROMs, this means some guys out there could make it, so what is the way to do so?
Or, how those mobile phone companies do it in their labs?
I have been doing researches on this topic for a few days. Some posts claim that their methods are "backup stock ROM" or "backup before rooting". But after digging into it, they requires rooting and/or flashing CWM. Here comes a few questions:
Questions
Rooting will in fact changes some files/data of the system. So backup after root is NOT getting the original stock ROM. Is it?
Is there a method to "un-root", so ALL the changes are TOTALLY reverted?
Installing/flashing things like CWM in phone requires rooting, which would make the ROM not original. Is there a way to extract the system backup from a computer externally?
In addition, I have found some related pieces. which could be useful to anyone viewing this post, and might be useful for you to solve this (my) question. :fingers-crossed:
* as I'm a new user, I can't post links directly. Please delete the blank spaces in between.
ht tp://www .modaco .com/topic/351269-backup-original-rom/
In reply #5, user C3C0 raised a method of backing up the original stock ROM without root. But it seems he is flashing CWM and that method is only for ZTE Skate.
adb backup tool of Android SDK
At the first sight i came across this approach, I thought it is the official method to do whole system (ROM) backup (WOW - how nice!). But after studying for a few more posts, I think adb backup can only backup app+app_data, and possibly some system settings only. Am I correct? And also, adb backup is only for ICS (Android 4.0), isn't it?
adb backup usage: ht tp://forum.xda-developers .com/showthread.php?t=1420351
(But mentioned in the bottom of #1 the poster is having some issues on using adb backup. Perhaps there are some bugs and not reliable(?)
One more question on adb backup: Can it backup just one app+app_data, and restore just one app+app_data, without affecting other things? If yes, we don't need to root and don't need Titanium Backup (which requires root) for backup app+app_data. Isn't it?
** In case I have said anything or any terms wrongly in this thread, please DO correct me, for helping me and helping others.
P.S. i am using LG Optimus 3D.
Thanks a lot, wholeheartedly,
midnite_
Backup phone before root
Hello all this is my first post here...woohoo!:fingers-crossed: This forum is amazing as to the amount of information available. I just wish that in looking for what I need to do I did not need to look in so many places. I feel that if I want to root my T-Mobile GS3 that all the information should be in one subsection of the forum, but it is not that simple I guess....lol Anyway any help would be greatly appreciated.
I have a Samsung GS3 with T-Mobile that I want to root. Everyone says to back up the phone before you do it but I am not really seeing how to make a backup before I start. It appears that most of the guides to root just say to backup without telling you how to fo it. Another thing (correct me if I am wrong) I see the nandroid backup that I think is a backup of the phone however it seems to be done after you make changes to the phone and I thought the backup was supposed to be done before you do anything. Is it that there is not a way to make a complete backup with an unrooted phone?
My question is basically the same as the OP here. I have been reading and reading and reading posts here in the forum. There is much information here and much of it is duplicated with slight variances in some of the duplicates. I am not certain as to which rooting method I should use. There seem to be so many choices. As a new person to this forum I will say that you can find just about everything about any phone which is awesome. The hard thing is sifting through the many options to pick one to use for your issue.
I do see that Mr. Robinson has a thread with backups of the original roms. The only thing is that they are default roms that are like an out of the box phone and not my phone with my apps and my settings. That is what I want to backup...My phone with my settings and my apps.
:good: Thank you in advance for any one that can shed some light on this for me and the OP'er
ASharpEdge said:
Hello all this is my first post here...woohoo!:fingers-crossed: This forum is amazing as to the amount of information available. I just wish that in looking for what I need to do I did not need to look in so many places. I feel that if I want to root my T-Mobile GS3 that all the information should be in one subsection of the forum, but it is not that simple I guess....lol Anyway any help would be greatly appreciated.
I have a Samsung GS3 with T-Mobile that I want to root. Everyone says to back up the phone before you do it but I am not really seeing how to make a backup before I start. It appears that most of the guides to root just say to backup without telling you how to fo it. Another thing (correct me if I am wrong) I see the nandroid backup that I think is a backup of the phone however it seems to be done after you make changes to the phone and I thought the backup was supposed to be done before you do anything. Is it that there is not a way to make a complete backup with an unrooted phone?
My question is basically the same as the OP here. I have been reading and reading and reading posts here in the forum. There is much information here and much of it is duplicated with slight variances in some of the duplicates. I am not certain as to which rooting method I should use. There seem to be so many choices. As a new person to this forum I will say that you can find just about everything about any phone which is awesome. The hard thing is sifting through the many options to pick one to use for your issue.
I do see that Mr. Robinson has a thread with backups of the original roms. The only thing is that they are default roms that are like an out of the box phone and not my phone with my apps and my settings. That is what I want to backup...My phone with my settings and my apps.
:good: Thank you in advance for any one that can shed some light on this for me and the OP'er
Click to expand...
Click to collapse
Hi ya,
It's so nice that you are having the same concern as I do.
As far as i know, the approaches of rooting differ from phones to phones. So we may have to find our own specific rooting method in the phone model sub-forums. It won't be hard for your popular S3
I would like to have a look at that Mr. Robinson's thread. If he can backup the stock ROM, those app+app_data wont a big issue (i guess).
cheers,
midnite_
midnite_ said:
Questions
Rooting will in fact changes some files/data of the system. So backup after root is NOT getting the original stock ROM. Is it?
Is there a method to "un-root", so ALL the changes are TOTALLY reverted?
Installing/flashing things like CWM in phone requires rooting, which would make the ROM not original. Is there a way to extract the system backup from a computer externally?
Click to expand...
Click to collapse
Hi midnight, welcome to a new and exciting world of Android and trying new things. First, let me assure you, what you want is NOT something new. People have been doing this type of thing for years. That is flashing and testing roms. As you will learn, it actually becomes quite addictive. We call those folks that get addicted to flashing: Flashaholics or crackflashers, lol
First let me talk about "root". This process consists of unlocking a lower level of the Android system known as the bootloader. Unlocking the bootloader of your device allows you to flash a custom recovery, flashing a custom recovery allows you to flash the Superuser binary and Superuser.apk, This is what allows you to use apps that require "root". The bootloader is not an OS file. So when you are unlocking your bootloader you are not modifying your stock rom. Only when you have flashed the Superuser package have you modified your stock rom. And even that isn't really modifying anything. When you flash the Superuser package, it adds two files to your rom at certain locations of the file system. It adds the Superuser.apk file to system/app and it adds the SU binary to system/bin. Basically you CAN have a totally S-OFF (unlocked) bootloader and still have an entirely stock rom if you want. But the real benifit is flashing a custom recovery like ClockworkMod Recovery and then flash the superuser package.
As far as extracting the stock system, you should try giving adb a go. Do it right now if you like. Ensure you have the android sdk installed and properly set up on your computer and your computer can recognize your phone. Ensure your phone is in debugging mode, connect your phone to your computer, open up a command window, and run this command:
Code:
adb pull \
This command will pull everything off your phone except for data which is where your market or Google Play apps are stored.
Beyond XDA there are aso more resources to learn from. For example, http://www.android.com is a good place to start, and to learn more about adb check out http://developer.android.com/tools/help/adb.html
If you need to learn how to setup the sdk here is the place to learn how: http://developer.android.com/sdk/index.html
I'm sure others will add to this as well which is the good thing about this community.
Welcome to XDA, I hope you have fun learning, and maybe share back someday things you learn along the way.
wildstang83 said:
Hi midnight, welcome to a new and exciting world of Android and trying new things. First, let me assure you, what you want is NOT something new. People have been doing this type of thing for years. That is flashing and testing roms. As you will learn, it actually becomes quite addictive. We call those folks that get addicted to flashing: Flashaholics or crackflashers, lol
First let me talk about "root". This process consists of unlocking a lower level of the Android system known as the bootloader. Unlocking the bootloader of your device allows you to flash a custom recovery, flashing a custom recovery allows you to flash the Superuser binary and Superuser.apk, This is what allows you to use apps that require "root". The bootloader is not an OS file. So when you are unlocking your bootloader you are not modifying your stock rom. Only when you have flashed the Superuser package have you modified your stock rom. And even that isn't really modifying anything. When you flash the Superuser package, it adds two files to your rom at certain locations of the file system. It adds the Superuser.apk file to system/app and it adds the SU binary to system/bin. Basically you CAN have a totally S-OFF (unlocked) bootloader and still have an entirely stock rom if you want. But the real benifit is flashing a custom recovery like ClockworkMod Recovery and then flash the superuser package.
As far as extracting the stock system, you should try giving adb a go. Do it right now if you like. Ensure you have the android sdk installed and properly set up on your computer and your computer can recognize your phone. Ensure your phone is in debugging mode, connect your phone to your computer, open up a command window, and run this command:
Code:
adb pull \
This command will pull everything off your phone except for data which is where your market or Google Play apps are stored.
Beyond XDA there are aso more resources to learn from. For example, ht tp://www .android .com is a good place to start, and to learn more about adb check out ht tp://developer .android .com/tools/help/adb.html
If you need to learn how to setup the sdk here is the place to learn how: ht tp://developer .android .com/sdk/index.html
I'm sure others will add to this as well which is the good thing about this community.
Welcome to XDA, I hope you have fun learning, and maybe share back someday things you learn along the way.
Click to expand...
Click to collapse
Hi Wildstang,
Thanks very much for your warm welcome and very informative reply. So are you a Flashaholics or Crackflashers yet?
As I am a newbie, please forgive me if I am asking dumb questions.
As far as I understand,
The steps of root is
1. Unlock the bootloader
2. Flash Superuser binary & Superuser.apk
** does "flash a custom recovery" means "flash Superuser binary & Superuser.apk"?
"Flash Superuser binary & Superuser.apk" is just "add SU binary to system/bin" and "add Superuser.apk to system/app". Then why not just copy them into place?
I just found on the web that "flashing" means replacing the OS of the phone with a new ROM. Would that still keeping the stock ROM?
To have a backup of the original stock ROM, can I
1. Unlock the bootloader
2. Flash Superuser binary & Superuser.apk
3. Perform the backup
And later, after I have flashed a new ROM, or whatever I do, as long as I didn't brick it, when I want to rollback my phone to its original, I can
1. Restore the backup
2. Delete "SU binary in system/bin" and "Superuser.apk in system/app"
3. re-lock the bootloader
Is this correct?
I don't mean to challenge you. But does adb pull \ really backup the system, or just all the files?
Thanks very much again!
midnite_
Hey midnite_,
I am a newbie too and have a lot of blank spots in my understanding of what we can do with android. I also came here with same question. I found how to root, this isn't a secret. Like you, I want to know how do I fix it if I break it.
So, with regards to your questions.
1. Unlock the bootloader
Not clear on this one, as not every tutorial even mentions this part. My feeling is that this might be specific to some phones, like HTC.
2. Flash Custom Recovery (such as AmonRa, CWR, TWRP...)
Recovery is an intermediate stage of phone booting process after bootloader but before OS.
It is there to allow OTA (Over the air) updates. During those, the OS is halted and replaced with a newer one.
What this means for us is that the recovery is capable of replacing OS (ROM - are these terms interchangeable?).
Recovery is the same as hidden partition on windows, that is sometimes present on a PC. It has a limited interface.
It can replace one OS image with another. It probably checks the checksum and creates the new one after the update. It is probably the gatekeeper.
Stock recovery will not replace OS with an image from SD card or from PC through USB. Only OTA.
This is the reason for flashing the custom (hacked) recovery on.
Custom recovery is made to allow additional options, such as allowing image sources such as PC or SD card, and also a ROM backup (write OS image to PC).
3. Flash update file using "upgrade from SD card" function of custom recovery now in place.
In this step, the Superuser.apk and bin files are placed. Stock recovery will not let us do that.
Also, I think the reason we can't just use ADB to "copy" superuser package to phone is because the system is either running or exists as an image (compressed?), and is probably protective of its modification. (So, likely the superuser package also replaces the checksum that the OS uses to check if it has been compromised?) Yes, this modifies your rom.
I assume that unrooting could be done after this by updating again with a file that removes superuser package and that would make your rom stock again.
4 OR flash custom ROM, which usually includes superuser package. Of course using custom rom means you no longer have stock rom.
To have a backup of original ROM, you would :
1 Unlock bootloader,
2 Flash (install) custom recovery
3 superuser doesn't matter here
4 Use custom recovery function to back up your stock ROM.
I want to know the answers to the rest of your questions as well as some clarifications to mine.
Personally, I am looking for a way to backup the stock recovery as well.
I know there are some people asking about this. The procedure appears to be as follows:
(pieced together so don't take it as a tutorial)
1 Unlock bootloader (again, unclear on this. Also some mention S-OFF and others don't)
2 With USB debugging allowed (meaning connect as device requiring a driver), Connect to a PC with ABD, and a driver installed.
3 From ADB, issue a command "adb boot recoveryimage.name" instead of the usual "adb flash recoveryimage.name".
This will make the phone boot into a custom recovery image that is residing on PC, without first writing it to the phone.
4 Unclear how, but make that custom recovery now being live to back up stock rom to pc.
5 Unclear how, but make that custom recovery now being live to flash either root or custom rom to the phone.
6 Disconnect, reboot the phone. Once in OS, use root privileges to mount recovery partition ? (this makes it visible as drive)
7 Don't know how, but use root privileges to back up now visible stock recovery partition to PC as image.
( This should give you two out of three original parts.)
Keep in mind that even if my peace-by-peace "know-how" ever works, there is at least one clearly faulty step:
The back up of the original state of the boot loader has been never made. I do not know if it is easily can be toggled back and forth from lock to unlock and back without leaving any trace. Also, like yourself, I probably don't quite understand what am I talking about, but I have tried to make as much sense of what I have read here and there.
This is my first smart phone, and my experience with linux is limited to building a minecraft server on MineOS, which was pre-made so that not much was required to make it run. I have "mounted" a partition for the first time last week, trying to break Win7recovery, booting it with Knoppix. This is why I think this is probably will come in play here too, as the recovery partition on W7 was hidden. Until then I didn't understand what mounting means, as windows always does it for you. So, take everything I say with a bunch of salt.
Please, let me know too, if you find out more. I want to flash the hell out of my Prism, but I want to be smart about it.
bump... midnite_ r u still around?
Hi Descent2,
Yes i am still around but i am busy with other stuffs at this moment. Thanks very much for your reply. You have studied a lot and you really did good summarisations. Very informative and I learnt a lot from it. Hope some of the masters or experienced ones would come by and bring us out of the mist
cheers,
midnite_
Descent2 said:
Hey midnite_,
I am a newbie too and have a lot of blank spots in my understanding of what we can do with android. I also came here with same question. I found how to root, this isn't a secret. Like you, I want to know how do I fix it if I break it.
So, with regards to your questions.
1. Unlock the bootloader
Not clear on this one, as not every tutorial even mentions this part. My feeling is that this might be specific to some phones, like HTC.
2. Flash Custom Recovery (such as AmonRa, CWR, TWRP...)
Recovery is an intermediate stage of phone booting process after bootloader but before OS.
It is there to allow OTA (Over the air) updates. During those, the OS is halted and replaced with a newer one.
What this means for us is that the recovery is capable of replacing OS (ROM - are these terms interchangeable?).
Recovery is the same as hidden partition on windows, that is sometimes present on a PC. It has a limited interface.
It can replace one OS image with another. It probably checks the checksum and creates the new one after the update. It is probably the gatekeeper.
Stock recovery will not replace OS with an image from SD card or from PC through USB. Only OTA.
This is the reason for flashing the custom (hacked) recovery on.
Custom recovery is made to allow additional options, such as allowing image sources such as PC or SD card, and also a ROM backup (write OS image to PC).
3. Flash update file using "upgrade from SD card" function of custom recovery now in place.
In this step, the Superuser.apk and bin files are placed. Stock recovery will not let us do that.
Also, I think the reason we can't just use ADB to "copy" superuser package to phone is because the system is either running or exists as an image (compressed?), and is probably protective of its modification. (So, likely the superuser package also replaces the checksum that the OS uses to check if it has been compromised?) Yes, this modifies your rom.
I assume that unrooting could be done after this by updating again with a file that removes superuser package and that would make your rom stock again.
4 OR flash custom ROM, which usually includes superuser package. Of course using custom rom means you no longer have stock rom.
To have a backup of original ROM, you would :
1 Unlock bootloader,
2 Flash (install) custom recovery
3 superuser doesn't matter here
4 Use custom recovery function to back up your stock ROM.
I want to know the answers to the rest of your questions as well as some clarifications to mine.
Personally, I am looking for a way to backup the stock recovery as well.
I know there are some people asking about this. The procedure appears to be as follows:
(pieced together so don't take it as a tutorial)
1 Unlock bootloader (again, unclear on this. Also some mention S-OFF and others don't)
2 With USB debugging allowed (meaning connect as device requiring a driver), Connect to a PC with ABD, and a driver installed.
3 From ADB, issue a command "adb boot recoveryimage.name" instead of the usual "adb flash recoveryimage.name".
This will make the phone boot into a custom recovery image that is residing on PC, without first writing it to the phone.
4 Unclear how, but make that custom recovery now being live to back up stock rom to pc.
5 Unclear how, but make that custom recovery now being live to flash either root or custom rom to the phone.
6 Disconnect, reboot the phone. Once in OS, use root privileges to mount recovery partition ? (this makes it visible as drive)
7 Don't know how, but use root privileges to back up now visible stock recovery partition to PC as image.
( This should give you two out of three original parts.)
Keep in mind that even if my peace-by-peace "know-how" ever works, there is at least one clearly faulty step:
The back up of the original state of the boot loader has been never made. I do not know if it is easily can be toggled back and forth from lock to unlock and back without leaving any trace. Also, like yourself, I probably don't quite understand what am I talking about, but I have tried to make as much sense of what I have read here and there.
This is my first smart phone, and my experience with linux is limited to building a minecraft server on MineOS, which was pre-made so that not much was required to make it run. I have "mounted" a partition for the first time last week, trying to break Win7recovery, booting it with Knoppix. This is why I think this is probably will come in play here too, as the recovery partition on W7 was hidden. Until then I didn't understand what mounting means, as windows always does it for you. So, take everything I say with a bunch of salt.
Please, let me know too, if you find out more. I want to flash the hell out of my Prism, but I want to be smart about it.
Click to expand...
Click to collapse
check here
All your answers can be found here: [REF] [GUIDE] Welcome to your device, the Galaxy S III. For more XDA related issues check here: [GUIDE] - XDA New User Guide - Getting started on XDA
Good Luck!
mf2112
XDA Moderator
ASharpEdge said:
Hello all this is my first post here...woohoo!:fingers-crossed: This forum is amazing as to the amount of information available. I just wish that in looking for what I need to do I did not need to look in so many places. I feel that if I want to root my T-Mobile GS3 that all the information should be in one subsection of the forum, but it is not that simple I guess....lol Anyway any help would be greatly appreciated.
I have a Samsung GS3 with T-Mobile that I want to root. Everyone says to back up the phone before you do it but I am not really seeing how to make a backup before I start. It appears that most of the guides to root just say to backup without telling you how to fo it. Another thing (correct me if I am wrong) I see the nandroid backup that I think is a backup of the phone however it seems to be done after you make changes to the phone and I thought the backup was supposed to be done before you do anything. Is it that there is not a way to make a complete backup with an unrooted phone?
My question is basically the same as the OP here. I have been reading and reading and reading posts here in the forum. There is much information here and much of it is duplicated with slight variances in some of the duplicates. I am not certain as to which rooting method I should use. There seem to be so many choices. As a new person to this forum I will say that you can find just about everything about any phone which is awesome. The hard thing is sifting through the many options to pick one to use for your issue.
I do see that Mr. Robinson has a thread with backups of the original roms. The only thing is that they are default roms that are like an out of the box phone and not my phone with my apps and my settings. That is what I want to backup...My phone with my settings and my apps.
:good: Thank you in advance for any one that can shed some light on this for me and the OP'er
Click to expand...
Click to collapse
Thanks mf2112. But those resources are seem only for GS3. And it seems it is not teaching us to backup our stock ROMs, it provides stock ROMs for us to download instead. Is there a general way to backup our stock ROMs?
Thanks,
midnite_
mf2112 said:
All your answers can be found here: [REF] [GUIDE] Welcome to your device, the Galaxy S III. For more XDA related issues check here: [GUIDE] - XDA New User Guide - Getting started on XDA
Good Luck!
mf2112
XDA Moderator
Click to expand...
Click to collapse
You must unlock your bootloader then flash a custom recovery. You will then use that custom recovery to make a backup of your rom. That backup will be stored on your sd card.
Now, I have tried to help you and so have a couple other folks. You expect us to just give you answers step by step. I am sorry but this is simply not how XDA works. XDA is set up in a way which makes it for any users to find quickly what they want to know. Use the search feature on the site and you will find many answers. I tell you to go do your own research now and be proud of what you learn on your own. And if you cannot, please do not try to modify your phone further, you may just brick it if you aren't careful.
midnite_ said:
Thanks mf2112. But those resources are seem only for GS3. And it seems it is not teaching us to backup our stock ROMs, it provides stock ROMs for us to download instead. Is there a general way to backup our stock ROMs?
Thanks,
midnite_
Click to expand...
Click to collapse
I put in the GS3 links since the OP was using that phone. Every phone will be different so I don't think a general way or guide would be practical.
Sent from my HTC Sensation 4G using xda premium
This guide assumes that you are on a stock Pantech Flex P8010 running either ICS (v4.0.4). or the updated JB (v4.1.2) Please note that rooting a ICS phone has been known to cause issues when trying to run the over the air update. If you have already rooted and are looking for a way to update to JellyBean please skip to the section on updating, if this isn't you keep reading.
So at this point you have decided to continue. You shouldn't run into any issues if you follow the directions and you shouldn't mess your phone up even if root doesn't take. However, in the spirit of covering ones back side....
I am not responsible for anything that goes wrong.
Jelly Bean 4.1.2 or ICS 4.0.4
This method was found by LuneBear and has not been tested by myself so I cannot personally verify its effectiveness. I did check and it seems to work with both ICS and JB but your mileage may vary. You will need to download SRSroot and install it on a Windows machine.
SRS ROOT
SRS Homepage
Make sure that USB debugging is enabled on your phone. Connect your phone via USB and run the program. Select the button for all root methods. Then you will need to select the Legolas exploit. Once everything is done (may take some time) just reboot the phone and you should be good to go.
Ice Cream Sandwich 4.0.4 ONLY
Windows Option
This method has been tried on a number of Windows versions and some work some don't so your mileage may very. This method uses Bin4ry's Root method and was orgnially discovered by aaki_rocker and is WAY LESS COMPLICATED. However please note that some users have had issues using this method with Bin4ry's latest version of the root script. It is recommended that you download an older version if you run into any issues or the root doesn't take.
First lets get some drivers on your Windows box. To do this you will need to download the Pantech PC Suite and install it.
http://c724062.r62.cf2.rackcdn.com/PantechPCSuite_1.1.1.3437.exe
Next you will need to download and extract Bin4ry's root script.
http://ul.to/z7krermj
Once you have these two files you will need to plug your phone into the PC via USB and enable the USB type as Data Mode.
Next run the Bin4ry's script and follow the directions when in doubt about what to choose select the simplest option in all cases.
If everything goes well you will have a nicely rooted phone.
Linux Option
This is not a point and click root and is not for the faint of heart. This method of rooting is based off of Bin4ry's root for ICS/JB. Changes have been made to the srcipt to allow it to work with the Flex please follow the steps below and you will have root in just a few minutes. It will probably take you longer to download the files you need than to actually root the phone.
This method has been performed successfully using Ubuntu 12.10 64bit it may work with other versions of linux but it will not work with Windows due to the driver issues and the fact that I didn't alter the windows batch file, in fact I removed any windows related files from Bin4ry's original package.
First you will need to set up the linux machine if you don't already have it. This can be done in one of a few ways you can run a live copy using a Live CD/USB boot (this will not install linux on your computer unless you tell it to) or you can install it in the standard manner or using WUBI, the third option us setting up linux in a virtual machine. If you don't know how to do this google it, there is a wealth of information out there on these subjects and probably some you can even understand without a degree in astro-physics.
Second you will need to set your phone up so that USB debug mode is turned on [settings>developer options]. Make sure you phone isnt plugged into the USB or it won't let you change the setting.
Now plug your phone into to the (linux) computer with the USB. Next you will need to set the USB computer connection type to Media Device(MTP)
In order for the computer to communicate with the phone we will need to install Android Debug Bridge (ADB) and create a couple of files.
These files will basically trick the computer into thinking it has actual drivers for the phone.
Open a terminal window, and enter the following (this will install ADB):
sudo apt-get install android-tools-adb
Once this is done enter the following
sudo gedit /etc/udev/rules.d/70-android.rules
Gedit will open at this point copy the the following into it and then click save and close the window.
SUBSYSTEMS=="usb", ATTRS{idVendor}=="10a9:6055", MODE="0666"
In the terminal window enter this (yeah I know it looks the same just go with it)
sudo gedit /lib/udev/rules.d/70-android.rules
After the window opens paste the same line of code into the file that you did in the previous files, save and close.
Test your connection by issuing the following command in the terminal window:
adb devices
Should see something similar to:
OSCAR01111112010204 device
Your adb is now recognizing your phone and you can now move on to the next step if you are not getting this don't even bother moving to the next step it wont work. If you don't see this check your settings and go again.
Ok so you are now ready to actually root the phone. The first thing your going to need to do is download my modified Bin4ry script. See the attached file.
After you have it downloaded you will need to extract it you can do this by opening the file manager (click on the home folder icon) and going to download. Find the file called Root_Flex.zip. Right click on it and select EXTRACT HERE. After its done extracting you should see a directory called Root_Flex. In a terminal windows enter the following:
cd Downloads/Root_Flex
Your prompt should now look something like
[email protected]_name~/Downloads/Root_Flex$
From here just enter the command:
bash RunMeFlex.sh
At this point you should see a bunch of junk come up and a menu asking which way you want to try to root. Type 1 and press enter. It will give you 3 errors, ignore them. It should copy a bunch of files and ask you to press restore on your phone, do it. It should ask you to press Enter to reboot the phone, do so and the phone will reboot. It should be waiting on you to press enter again dont press enter until the phone is completely rebooted and for good measure give it an extra few seconds. The script should finish and the phone will reboot again this time you should see a little box with an update appear on the phone. At this point you should be rooted. If not try the script again.
I hope this helps out a lot of folks out there. Let me know if I need to change anything in this How to or if I made any mistakes along the way.
Updating If you're already rooted
So you rooted your phone and now you want JellyBean but when you run the update you get the dead droid image and the update fails OR you live in an area that isn't covered by AT&T and you want the update, what do you do? Well thanks to some hard work by Attn1 we have a solution and its pretty simple. First off you will need to have CWM running on the phone. Now there are a few ways to go about this but the method I used was here:
http://forum.xda-developers.com/showthread.php?t=2133857
You only need to go as far as getting CWM up an running on the phone you do not need to install it as the the update by Attn1 will take care of a full install of a better version. You will need to have a copy of Fastboot.exe and some img files. Below is a rar file that has all the necessary files to get CWM running (not installed) on the phone using windows (sorry I don't have the linux files for this one). Just unpack them into a convienent folder somewhere and follow the instructions on the link above.
http://tinyurl.com/oa2p48f
I recommend using the boot_external.img but if you do not have an external SD card and only have the internal storage just use boot_internal.img instead. This method relys on you being able to get into fast boot. If you do not have access to fastboot for what ever reason I suggest you jump ahead in the thread and read Attn1 methods for installing CWM:
http://forum.xda-developers.com/showthread.php?t=2008888&page=44
Next get the update files from this link (second post)
http://forum.xda-developers.com/showthread.php?t=2008888&page=47
Once you have all the files downloaded and copied everything to the appropriate SD cards on your phone your ready to go. If you don't know how to do this don't even think about anything else till you learn this. After this is all done follow the directions below (copied from Attn1's post)
Procedure if you ARE NOT running baseband JYUS06032013 (ICS Basebands) :
boot ICS CWM
flash FLEX-JB-JYUS06032013-FIRMWARE.zip from CWM
format system in CWM (will NOT wipe data, but makes sure old rom does not flash back stock recovery)
restart start recovery/adb reboot recovery (JB CWM is installed - do not try to fastboot boot ICS CWM)
flash FLEX-JB-JYUS06032013-ROM.zip from CWM.
reboot
Procedure if you ARE running baseband JYUS06032013 (JB Baseband) :
get root (Instructions HERE - use GANDALF)
install CWM (Instructions HERE)
flash FLEX-JB-JYUS06032013-FIRMWARE.zip from CWM
format system in CWM (will NOT wipe data, but makes sure old rom does not flash back stock recovery)
reboot to CWM
flash FLEX-JB-JYUS06032013-ROM.zip from CWM.
reboot
This ROM is Pantech stock with no mods other than CWM installation protection and all stock permissions and symlinks carefully maintained and consistent with the product of a successful OTA.
The firmware is also stock, with the exception of the open aboot allowing fastboot boot <bootimage>, and installation of JB CWM with nothing else added or changed. It runs well with nothing broken. You MUST be on JB firmware (below) to run it properly.
You can let the new CWM root it if you like when you exit - it will prompt you. It will also prompt you to disable CWM on reboot make sure this gets disabled or the phone will keep booting to CWM rather than the ROM.
Downloads:
md5: 1a0ca5f177bce2f4c428931616e0ecd1 FLEX-JB-JYUS06032013-FIRMWARE.zip
md5: 17c0e611ab6dfbca230571c1e40f3d14 FLEX-JB-JYUS06032013-ROM.zip
Make sure you check the md5sum on the files before you flash them if there wrong download them again this is vital.
If you need a program to check md5sums copy this .exe file to your c:\windows\system\ and run it from the command line.
http://tinyurl.com/l74wl9q
Thanks go to Bin4ry for the original script and all the technical help provided.
Check out the thread and give a thanks and donate a few bucks if you can.
http://forum.xda-developers.com/showthread.php?t=1886460
Thanks to Atadres for getting me going in the right direction and help testing along the way.
Thanks to Esau Silva for this post that helped get the drivers working for us in Ubutnu.
http://esausilva.com/2010/05/13/setting-up-adbusb-drivers-for-android-devices-in-linux-ubuntu/
Thanks to Aaki_rocker for coming up with the Windows version of this root method you can find his original post here.
http://forum.xda-developers.com/showthread.php?t=2141538
Thanks to LuneBear for finding the root method for JellyBean.
Thanks to Attn1 for the JellyBean update and CM 10.2 version of CWM Recovery.
jist a quick memo guys when you issue the command adb devices please cd to proper android sdk platform tools folder or else youll get an error like no command did you mean..... heres the proper way do this step before you do the adb devices step type in cd ~/android-sdk-linux/platform-tools press enter then type in ./adb devices
i am now trying to contact team win for help with porting the recovery image team win recovery so we can start roming this device and adding ports and roms
atadres said:
jist a quick memo guys when you issue the command adb devices please cd to proper android sdk platform tools folder or else youll get an error like no command did you mean..... heres the proper way do this step before you do the adb devices step type in cd ~/android-sdk-linux/platform-tools press enter then type in ./adb devices....
Click to expand...
Click to collapse
Acutally this assumes you are on a completely fresh install and did not have adb installed through the platform tools if that is the case everything I typed up will work. However you are correct too. Let me know if you think I should go ahead and rework the stuff to be a little more universal if so please PM me an update of the commands.
your right my apologies but one thing i noticed that i would like to say idk if its my experiance or universal after successfully rooting the flex the lockscreen fails to resize itself leaving a black space where the onscreen dock is usualy located no big issue though and the rooting was easy and painless once adb was set up correctly 100000+ points thanks so much
Good job guys. Respect! I have a Pantech Flex, which is an awesome device with the same specs (things that matter to me) as S3, but without big name. I like Pantech Flex because it's size is much better for me than.
The only thing now is to create a ROM! Is it difficult to make a pure Android ROM? Nothing additional, just a pure Android like in Nexus?
Again, thank you guys for your dedication! I'll definitely donate as soon as I have Jelly Bean loaded on my Pantech Flex!
Thanks, this worked great. I am gonna start on a ROM. Hope I don't get bricked.
Sent from the new Pantech Flex. Nominated best lowest priced new smartphone. U jelly I paid nothing, for a phone almost as good as the Galaxy S3?
HighCommander540 said:
Thanks, this worked great. I am gonna start on a ROM. Hope I don't get bricked.
Sent from the new Pantech Flex. Nominated best lowest priced new smartphone. U jelly I paid nothing, for a phone almost as good as the Galaxy S3?
Click to expand...
Click to collapse
lets not get ahead of ourselves here guys in order to create a rom we would need to get a custom recovery on our phone this can be achived by mapping out the devices bootloader extracting an img file of it and using koushes clockworks mod recovery creator only when we achive a port of a custom recovery can we make roms and be able to flash them if any of you have knowledge of this as i am a noob when it comes to recoveries pleasae feel free to input we need all the help we can get guys
---------- Post added at 02:03 PM ---------- Previous post was at 01:58 PM ----------
ivansana said:
Good job guys. Respect! I have a Pantech Flex, which is an awesome device with the same specs (things that matter to me) as S3, but without big name. I like Pantech Flex because it's size is much better for me than.
The only thing now is to create a ROM! Is it difficult to make a pure Android ROM? Nothing additional, just a pure Android like in Nexus?
Again, thank you guys for your dedication! I'll definitely donate as soon as I have Jelly Bean loaded on my Pantech Flex!
Click to expand...
Click to collapse
lol right now we need knowledge donations unfourtunatly we cannot start working on roms till we have a custom recovery ported over either team win or clockworks mod recovery this will take a little bit of time and knowledge and to answer your question about the stock nexus rom your talking along the terms of a cynaogen mod port? or akop port looking into it i would say untill we have mapped the bootloader we wouldnt know how diffcult it would be because the simlinks maybe difcult for a phone that has not yet caught fire in the dev world
i wish i had the time to do a recovery myself and get cwm working but with my family and my fulltime job i barely get any time. Im going to spend all my time on this amazing little phone to do what i can. props to the root method it worked flawlessly!!!
Sent from my PantechP8010 using Tapatalk 2
Awesome I'm glad im getting some good feed back on the root. I wasnt sure if I did the rightup correctly and im glad its working out for everyone.
If I get some time I will start looking into a custom CWM and all that junk I have a contact that should be a pretty good help in this just have to find the time to do it.
Yeah after coming from the LG Nitro HD I was surprised at how easy this was to root.
If you want to get together on gtalk we can work on this together. Right now I'm in the process of getting a ROM dump so we can recover our phones from stock images if we happen to mess them up, which I'm sure we will, but that's the best part! Lol.
I can smell CM9 and CM10 calling to this phone!!!
Sent from my PantechP8010 using Tapatalk 2
jSterling said:
Yeah after coming from the LG Nitro HD I was surprised at how easy this was to root.
If you want to get together on gtalk we can work on this together. Right now I'm in the process of getting a ROM dump so we can recover our phones from stock images if we happen to mess them up, which I'm sure we will, but that's the best part! Lol.
I can smell CM9 and CM10 calling to this phone!!!
Sent from my PantechP8010 using Tapatalk 2
Click to expand...
Click to collapse
Yeah I love this phone but I have to say the Pantech launcher kinda pisses me off.
donavan01 said:
Yeah I love this phone but I have to say the Pantech launcher kinda pisses me off.
Click to expand...
Click to collapse
Agreed lol im using nova
I actually don't mind the launcher, its pretty nice compared to other brand launchers. I'm probably going to try launcher pro though that's been my favorite sense I had my prepaid optimus V
Sent from my PantechP8010 using Tapatalk 2
jSterling said:
I actually don't mind the launcher, its pretty nice compared to other brand launchers. I'm probably going to try launcher pro though that's been my favorite sense I had my prepaid optimus V
Sent from my PantechP8010 using Tapatalk 2
Click to expand...
Click to collapse
I had launcher pro and hated it ... check out APEX seems like the stock ICS but with a lot of extras and without the annoying bits of the pantech that make me insane
donavan01 said:
I had launcher pro and hated it ... check out APEX seems like the stock ICS but with a lot of extras and without the annoying bits of the pantech that make me insane
Click to expand...
Click to collapse
hey guys... is there a pantech flex forum????????
also is it possible to unlock the device if you forget the log in pattern????? thanks
I don't know anything about mapping the device. So I am just going to work on a ROM for my infuse.
I will help with anything for testing. A stock image would be awesome. =-)
No flex forum yet.
_______
Sent from the new rooted Pantech Flex. Nominated best lowest priced new smartphone. U jelly I paid nothing, for a phone almost as good as the Galaxy S3?
jSterling said:
I actually don't mind the launcher, its pretty nice compared to other brand launchers. I'm probably going to try launcher pro though that's been my favorite sense I had my prepaid optimus V
Sent from my PantechP8010 using Tapatalk 2
Click to expand...
Click to collapse
sense is my fav launcher and no no forum yet ive requested and gotten no reply smh
did this thread die guys?
atadres said:
did this thread die guys?
Click to expand...
Click to collapse
Wait till after Xmas I bet you a lot of people will get this phone as presents.
donavan01 said:
Wait till after Xmas I bet you a lot of people will get this phone as presents.
Click to expand...
Click to collapse
Yeah I can see that happening. This weekend I am going to work on it to see what I can come up with. I've been so swamped with work and life bs that I haven't had a chance.
No this thread didn't die.
Sent from my PantechP8010 using Tapatalk 2
As our device gracefully ages I have often wondered if Droid Charge users will to have access to the files that were common during the earlier days. Well I did something about it, here...
TweakedROM.com - Other Files > SCH-I510
Download responsibly my friends!
Not everything has MD5 posted, not yet. I will update when validated against local working copy and/or original source if still available. Please, read the disclaimers.
(Be kind, for I am n00b.)
Note:
Please, don't ask me to host your stuff. I can take suggestions (if I missed something important), but this is the main package I fall back on when crack flashing.
Other Note:
[Q] Files, great now what?!?!? How do I root?
[A] Check HERE, and if that helps you be sure to thank JihadSquad for the concise summary. (Yes, it will still work on FP5... and FP8)
PS. If I am mirroring any of your original work, I have probably sent PM's... Let me know if there is an issue, I will make it right.
TweakTools Mirror [FP5] -- Continuity!
NEW TweakTools Mirror up and running! (As of 8/9/13)
This is all the files behind the tweaktools v36 .sh script that we have all come to love from our Android Terminal Emulator...
While I haven't procedurally tested every menu option, I've tried out a good many of the menu options. (Let me know if there are download issues, MIME extensions...)
There were like 3 stock bloat apk's I was unable to locate, but the files are is basically 99.9% there! (Not sure about the animated gif images of a flying raibow pooping pop-tart looking cat that represents some of the boot animations... HERE ...is there a back story to that?)
This time directory browsing has been enabled on the webserver. So... feel free to check out the script syntax right from your browser.
TT 36 for Tweaked 3.2 Repository Mirror:
http://tools.tweakedrom.com/SCH-I510/FP5E/tweaktools/
Note: The official repository auto updates your local scripts. NO "REAL" NEED TO POINT TO THIS MIRROR! If the powers that be want to point to this mirror they can make it happen in a way that most TT users may not even notice
However, if the http://www.tonsit.com/tweaktools/ repository goes down again I can and will post files/instructions on how to point your FP5 Tweaked 3.2 deployments at this mirror.
...feel free to play around.
bread crumbs...
there are 3 .sh scripts in "/system/bin" and "/system/xbin" just modify the variable "HOSTURL" to point to the my mirror.
Suppose you could also point "TWEAKSITE" to HERE.
Enjoy!
PS. If TT was ever forked/updated for FP8 this could serve as a fall back plan for those wishing to remain on the FP5 flavor, theoretically... (Don't hold your breath...)
Oh yeah...
Reserved cause it is cool.
Donate:
Truth is that domain names, servers, and bandwidth all have a cost. If you want to share the load feel free to chip in by clicking this:
DONATE (There is a paypal button down in the jheide44 section.)
That said, most of the real effort was put in by folks like Dwitherell and imnuts. Please consider sending your donation dollars in that direction.
PS. By donating you agree that you have read the disclaimer page, HERE... and THIS. As such, you are aware that donations formally entitle you to NOTHING.
awesome. just FYI, the links to the tweaktools (themes, applications, CWM mods) leads to a forbidden screen.
but glad to see the torch being passed on.
long live the Charge!
jco23 said:
awesome. just FYI, the links to the tweaktools (themes, applications, CWM mods) leads to a forbidden screen.
but glad to see the torch being passed on.
long live the Charge!
Click to expand...
Click to collapse
Not sure if there will be any "torch" passing... my mom doesn't let me play with fire. :silly:
Thanks, and thanks again for testing that other thing
I did throw out some RE-bloat FP8 "/system/app" goodies from my dedexing efforts. Poke around the repository, tools subdomain... Ya can't miss it (currently that is all I have to post out there).
Most folks probably just grab those bits out of the Deodexed Bloated zip that Dwith has posted here on XDA.
PS.
I left some "love notes" to the world at the top of the "repository" page. It is/was just a proof of concept thing, might lead to nothing...
Per the website...
...
This is just an sandbox/idea I dreamed up... it may go nowhere. Don't get your hopes up.
...
Quick and Dirty copy of the old TT instructions appears below... for informational purposes only... Links are Broke... This is not something I want to hear complaints about...
Click to expand...
Click to collapse
jheide44 said:
Not sure if there will be any "torch" passing... my mom doesn't let me play with fire. :silly:
Thanks, and thanks again for testing that other thing
I did throw out some RE-bloat FP8 "/system/app" goodies from my dedexing efforts. Poke around the repository, tools subdomain... Ya can't miss it (currently that is all I have to post out there).
Most folks probably just grab those bits out of the Deodexed Bloated zip that Dwith has posted here on XDA.
PS.
I left some "love notes" to the world at the top of the "repository" page. It is/was just a proof of concept thing, might lead to nothing...
Per the website...
Click to expand...
Click to collapse
ah.... well, I think they might exist somewhere still, as I was able to download them not toooo long ago (even the image of the theme was available). lone problem though is getting permission from the themers to re-post them. I still have ICA theme, BLN mod, some boot animations, and a few others if needed.
but in any event, thank you. i'm here for help.
jco23 said:
ah.... well, I think they might exist somewhere still, as I was able to download them not toooo long ago (even the image of the theme was available). lone problem though is getting permission from the themers to re-post them. I still have ICA theme, BLN mod, some boot animations, and a few others if needed.
but in any event, thank you. i'm here for help.
Click to expand...
Click to collapse
No problem.
Oh yes original credit for TT to Tonsit... Dwith and all the others that brought it together so nicely back in the day!
Credit: Original TT instructions here http://www.tonsit.com/tweaktools/ The links you mentioned are broken there also (my little thing was just a cut and paste to make sure the information is not lost forever).
The tonsit repository has been going up and down (noticed it kicking to mirror from TT terminal interface in recent weeks/months, it was back up last night).
I have been unable to make contact some of the original contributors. If I've done anything offensive let me know, I will make it right.
Permission is the Catch 22... may be no point in tryint to preserve it if there is nothing FP8 flavored to deploy.
...my last Daily driver device was FP5 Tweaked 3.2 all the way!
Thank you so much for this because i know one day the ota updates will no longer be ota available.
how do we use the OTA Updates (Stock from VZW)?
Stauf99 said:
Thank you so much for this because i know one day the ota updates will no longer be ota available.
how do we use the OTA Updates (Stock from VZW)?
Click to expand...
Click to collapse
It has been a while since I played with those... I remember how I plucked them from "/cache" better than than how I upgraded with the FP8 OTA zip. (I DID NOT RENAME THE FILES.)
I originally downloaded an FP8 OTA from XDA before it was formally rolled-out to my device. I remember trying a couple things to get on FP8 the first time (before the OTA roll-out formally hit my phone). After a return to stock, I might have just renamed it "update.zip" and installed from stock recovery, not sure anymore.
If I recall I later stumbled across this method:
Put the OTA zip files on your SD card, after an ODIN return to stock EP4D, flash custom recovery,battery pull, reboot into recovery, then install the CWM zip files like any other CWM zip install... just install the zip files in the proper sequence... I rebooted after each iteration (losing custom recovery each time), so had to re-flash CWM a lot. It was a rinse and repeat operation... (If I recall cutting corners on the full rinse & repeat turned out poorly...)
But it was so long ago I am a bit fuzzy... (so don't try anything I said from your daily driver device, cause I'm just a crazy guy from the internet!)
just a wild guess:
you might be able to temporary cwm, root via cwm install zip (without renaming/deleting "install-recovery.sh"), put the file in /cache, maybe reboot here, and install from "settings > about phone > system update" (maybe have to use stock recovery here instead) ... when it automatically reboots... repeat for each OTA zip
(I have never tried this, but it would be an interesting path to attempt)
If you do decide to play with it nandroid first... and please report your findings
Ultimately I'm sure if/when the OTA's go away someone will take the time to test and formally document the process (I know would).
PS
Wouldn't it be nice if we had an Odin return to stock FP8 option
(as always, no promises)
jheide44 said:
PS
Wouldn't it be nice if we had an Odin return to stock FP8 option
(as always, no promises)
Click to expand...
Click to collapse
haha for sure, unless a FP8 tweaked never comes out i'd probably wanna go back to FP5 for tweaked 3.2
Thanks for the response, I tried install .zip as usual with CWM 302 but it just kinda stopped when i tried.
Is there a way to ODIN the stock recovery, because no matter how many times i re-ODIN the EP4 thing i can't actually do anything, when i click on any of the options (with the power button of course) they don't work. even restart. I have to hold power to get the phone to do anything else
Stauf99 said:
haha for sure, unless a FP8 tweaked never comes out i'd probably wanna go back to FP5 for tweaked 3.2
Thanks for the response, I tried install .zip as usual with CWM 302 but it just kinda stopped when i tried.
Is there a way to ODIN the stock recovery, because no matter how many times i re-ODIN the EP4 thing i can't actually do anything, when i click on any of the options (with the power button of course) they don't work. even restart. I have to hold power to get the phone to do anything else
Click to expand...
Click to collapse
I've never had success with nandroid backups on the 302 "blue" recovery... I've never played with ext4 either... (As such no MD5 on the site and general missing MD5 disclaimer... If someone has a known working copy of the 302 "blue" ext4 friendly recovery please let me have a copy... I'd like to compare MD5s)
try "0817_charge_recovery.tar.md5" from the site, the Orange one
MD5: 681b53aedc889285d3e18e9e23bd199d
If you Odin back to stock again you will have the stock recovery, right? If your 302 CWM buttons aren't working from recovery that might be your only option...
If not, Dwith posted a stock FP8 recovery here (might also want to read up on what was said about ext4 and the stock FP8 Kernel)
Given the button thing, i am not sure about the stock recovery image from an odin thing... I've never tried that for this device (safe bet is another return to stock Odin party.)
Anyone try fastboot? I haven't yet on a samsung device....
Side Note:
I imagine lots of folks will return to Tweaked 3.2 FP5... That is where I stayed prior to the GN2...
TT 3.6 for Tweaked 3.2 Mirror:
I'm tinkering with creating a mirror for the FP5 back end of TT... (a piece of art like this needs to be preserved, or something like that...)
PS Don't try to put the FP5 bits on FP8... i'm not saying you can't or that some things won't work... it would just be IMPOSSIBLE to support/get help if/when the issues present
TT-ish like FP8 thing:
got a little ROM project floating around... I've also been tinkering with the back-end of the TT script stuffs ... may go nowhere on FP8 ... Without a bunch of flashy themes and UI tweaks (TSM Parts) most users would not appreciate it on FP8, and just complain. (Right?)
I MIGHT try to rebrand it "weaktools" on the little FP8 thing for my Jedi skills are weak. (Note: I fully reserve the right to not deliver on this!)
OOPS ignore this...
Please ignore...
Ever wonder how often a message board gets "butt-dialed?"
Sent from my SCH-I605 using Tapatalk 4
jheide44 said:
I've never had success with nandroid backups on the 302 "blue" recovery... I've never played with ext4 either... (As such no MD5 on the site and general missing MD5 disclaimer... If someone has a known working copy of the 302 "blue" ext4 friendly recovery please let me have a copy... I'd like to compare MD5s)
try "0817_charge_recovery.tar.md5" from the site, the Orange one
MD5: 681b53aedc889285d3e18e9e23bd199d
If you Odin back to stock again you will have the stock recovery, right? If your 302 CWM buttons aren't working from recovery that might be your only option...
If not, Dwith posted a stock FP8 recovery here (might also want to read up on what was said about ext4 and the stock FP8 Kernel)
Given the button thing, i am not sure about the stock recovery image from an odin thing... I've never tried that for this device (safe bet is another return to stock Odin party.)
Click to expand...
Click to collapse
the custom recoveries work just fine, but on my stock recovery i can't actually use the commands, i can scroll no problem, but when i hit the power button over any of the 4 options nothing ever happens
Stauf99 said:
the custom recoveries work just fine, but on my stock recovery i can't actually use the commands, i can scroll no problem, but when i hit the power button over any of the 4 options nothing ever happens
Click to expand...
Click to collapse
Ohhh I see...
Hit home
Sent from my SCH-I605 using Tapatalk 4
jheide44 said:
Ohhh I see...
Hit home
Sent from my SCH-I605 using Tapatalk 4
Click to expand...
Click to collapse
haha, oh my gosh if that actually works i'm gonna kick my self.
as long as ur in a could mood do u think u could help me out over here real quick?
http://forum.xda-developers.com/showthread.php?t=2244704
Reserve #2 Updated
BUMP... Reserve #2 Updated...
NEW TweakTools Mirror up and running! (As of 8/9/13)
Enjoy!
Note: The official repository auto updates your local scripts. NO NEED TO POINT TO UNOFFICIAL MIRROR! ...but feel free to play.
Accidentally quoted myself instead of updating the reserved.... Cheers to user error
*** stupid fat sausage fingers and tiny Tapatalk buttons ***
Sent from my SCH-I605 using Tapatalk 4
jheide44 said:
If I recall I later stumbled across this method:
Put the OTA zip files on your SD card, after an ODIN return to stock EP4D, flash custom recovery,battery pull, reboot into recovery, then install the CWM zip files like any other CWM zip install... just install the zip files in the proper sequence... I rebooted after each iteration (losing custom recovery each time), so had to re-flash CWM a lot. It was a rinse and repeat operation... (If I recall cutting corners on the full rinse & repeat turned out poorly...)
Click to expand...
Click to collapse
The upgrades work like a charm. Just put on to sd card and update .zip through stock recovery.
I'm not sure how well they actually "work" because I haven't actually done anything on the phone yet, but when i went to 'about phone' in settings everything was aces, with each upgrade
you da man jheide44
tweaktools
fwiw, i'm moving my web hosting solution around.
tweakedROM.com (tweaktools) will be back up and running after a few days.
Just an FYI...
Well, some of you might have had the same urge to buy one of these little wonder with almost the same data sheet than a LG G2 but with a Dual SIM functionality and at a much smaller price. If you are one of these crazy people that ordered their in China just like me, you might have the same disappointment that I felt when I finally received mine: the advertised SD Card slot is just a fantasy and all Google apps have been replaced by their Baidu counterparts. If the English language is indeed present in the Operating System, none of the installed application seems to understand this language. If you just don't speak Chinese just like me, you might end up wondering why on earth you bought a smartphone destined to Chinese people.
So I decided to turn this frustration into something positive and succeeded so I'm happy to bring you my home cooked ROM for the Lenovo K910. But first of all, the usual disclaimer:
Disclaimer
Don't hold me responsible if you brick your phone. This method have been successfully tested on mine but this is no guarantee for yours. You should obviously always have a backup of your data at all time if you're willing to install this ROM (or any other).
Safety measures
Like most Android phones, the Lenovo Vibe Z have many possibilities of recovery. I would advise you to be ready to apply at least this one:
Download the QSB file of your ROM (for example, mine is K910_SS_S_2_040_0039_131101.qsb). Google will point you to a Baidu site where it is downloadable
Put it in the folder /sdcard/SDFUSE/
Shut down your phone
Hold Volume Down and Power button for a few seconds
You end up in a menu with a "SD Card Update" entry. Move down to this entry using the Volume Down button then press ENTER or power button.
Make sure your ROM is available in the list
Cancel and reboot
If your QSB file is visible in the list, you should be pretty safe. If anything goes wrong, use the same method but apply the upgrade this time. Note that this method overwrite everything included your applications, SD Card, ...
What it is
The ROM I'm offering is:
An extract from K910_SS_S_2_040_0039_131101.qsb
Applying only to your system partition (your applications and data should be safe)
Rooted
Busybox-ed
Grossly freed from most vendor applications
Replaced by Google applications
What it is NOT
This was already some work to figure out how to reach that goal so it is not:
Bug free (I have at least observed a strange display glitch for the network icons which turn standard blue instead of Lenovo's white one)
A multi-language ROM
A ROM build from scratch like MIUI, Cyanogenmod, ...
A custom recovery (though this might come in a later stage)
...
Prerequisite
You should have installed:
K910 ADB Driver (available on the CD that appear when you connect the device)
ADB
Fastboot
Just check that your USB debug mode is enabled (in the USB Access Mode menu).
In any of these prerequisite is an issue for you, I'm ready to explain you further but you should also wonder if you are ready to go further because if anything goes wrong, you won't be able to properly act.
The installation
OK, enough talking, now some action. It is pretty simple actually:
Download the ROM and un-7zip it (mirroring in progress)
Reboot your phone in bootloader mode. Therefore, open a command prompt (no matter which OS you're using) and type:
Code:
adb reboot-bootloader
Now your phone is displaying the Lenovo logo
Check that you can access the system
Code:
fastboot devices
If fastboot just return displaying nothing, you might have to run in Administrator/root mode. Under Linux, I had to use sudo.
Unlock the bootloader (this should wipe all your data if it wasn't unlocked previously):
Code:
fastboot oem unlock
Flash the system:
Code:
fastboot flash system <path-to-file>system.img
Reboot:
Code:
fastboot reboot
That's all folks ! After your phone restarts, you should be able to use Google applications (though not all of them are there, at least the Play Store is allowing you to install the others).
What's next ?
I hope to be able to free some time to achieve these next steps:
Publish the script I wrote to extract content from Lenovo QSB files
Apply the same method to the last upgrade (K910_SS_S_2_040_0078_131203 ?). If you are lucky enough to have this version please contact me to see if you can provide the QSB file.
See if I can cook a custom recovery.
This is probably my very first participation to the community so I'll accept any comments as long as they are constructive :good:
Thanks!!!!!
Thank you so much, I'm crazy because I get the phone and to try, where is the link to download please??
Thanks again, you can post pictures?
---------- Post added at 04:44 PM ---------- Previous post was at 04:35 PM ----------
Another important question ... How did you rooteado?
What program did you use?
Thanks.
All need you help please.
I'll need just a few more hours since my upload just missed (I'm not sure why it only uploaded 437 Mb on the 659 Mb)
It will be for the first hours of 2014 (at least for me).
csu333 said:
I'll need just a few more hours since my upload just missed (I'm not sure why it only uploaded 437 Mb on the 659 Mb)
It will be for the first hours of 2014 (at least for me).
Click to expand...
Click to collapse
Thank you very much for your work, but you can tell us how you got to be root??
sakilxda said:
Thank you very much for your work, but you can tell us how you got to be root??
Click to expand...
Click to collapse
Probably in the most complicated way possible: I extracted the system partition from the upgrade file, mounted it in my Linux, put all the needed files and authorization then flashed it on my device.
I confirm that the file is now available but I need a few more messages before I can add the link. In the meanwhile, I can send it privately.
csu333 said:
Probably in the most complicated way possible: I extracted the system partition from the upgrade file, mounted it in my Linux, put all the needed files and authorization then flashed it on my device.
I confirm that the file is now available but I need a few more messages before I can add the link. In the meanwhile, I can send it privately.
Click to expand...
Click to collapse
Sure I get it, I also took little time here and leaves add links.
You could pass it private?
With your permission I'll share it on other sites of course directing people to this thread so they can see their creator and comment.
In several HTCMania we are waiting to receive the phone and while we're compiling everything.
Root on many threads where people are wanting to get and so far you're the only one.
I await your email with the link partner, and with your permission I'll share. A greeting.
sakilxda said:
Sure I get it, I also took little time here and leaves add links.
You could pass it private?
With your permission I'll share it on other sites of course directing people to this thread so they can see their creator and comment.
In several HTCMania we are waiting to receive the phone and while we're compiling everything.
Root on many threads where people are wanting to get and so far you're the only one.
Click to expand...
Click to collapse
As long as you don't ask money for it, feel free to share this as much as you want. My goal is sharing !
You should have received the link in the meanwhile. I'm also busy trying to mirror it on AndroidFileHost but it failed last time so just wait and see.
Latest ROM version release notes
By the way, here are the release notes of the next ROM (K910_SS_S_2_040_0078_131203).
What Google translate by:
Recommend
* Expand the system partition, a number of bug fixes
Update log
System
* Expand the system partition to 1.5G
* Boot and recovery signature added to the system
Show
* Fixed shutdown problem dialog scene mode switching
* Modify profile English translation error
* Adjust section shows the layout
Camera
* Pre-correction first picture black beauty
Click to expand...
Click to collapse
This means that next upgrade will most probably erase all the content of your phone (again) included your data and internal SD Card. This also means that flashing the first version of my custom ROM will make you "lose" 500 Mb, at least until a release based on the latest version of Lenovo's original ROM.
This also mean that:
Next Custom ROM upgrade won't be applicable to the not upgraded phone (you would be certain of bricking your phone)
You will lost 500 Mb worth of storage on your non expandable device
This isn't all good news ...
csu333 said:
As long as you don't ask money for it, feel free to share this as much as you want. My goal is sharing !
You should have received the link in the meanwhile. I'm also busy trying to mirror it on AndroidFileHost but it failed last time so just wait and see.
Click to expand...
Click to collapse
Thank you very much for sharing, of course I will not ask for money and in forums where I am at all costs to visit this thread.
csu333 said:
By the way, here are the release notes of the last ROM (K910_SS_S_2_040_0078_131203):
What Google translate by:
This means that next upgrade will most probably erase all the content of your phone (again) included your data and internal SD Card. This also means that flashing the first version of my custom ROM will make you "lose" 500 Mb, at least until a release based on the latest version of Lenovo's original ROM.
This also mean that:
Next Custom ROM upgrade won't be applicable to the not upgraded phone (you would be certain of bricking your phone)
You will lost 500 Mb worth of storage on your non expandable device
This isn't all good news ...
Click to expand...
Click to collapse
They are not good news. but I honestly what I need are 3 things:
1 Language Spanish, but we already you can not imagine not doing anything?
2 Root, to be able to use apps like Titanium Backup, Root Explorer, etc..
3 Very importantly, GAPPS (Play Store, Gmail), but of course in Spanish or English.
Your Rom has 2 I need and it is very important to me and very many users, it is a great job and the first to do so was you.
I do not mind losing 500mb, but I worry that the next official update is dangerous for us.
Thank you very much for sharing the link. If you write more answers in this thread at XDA have permission to put the link publicly, I think the requirement is 10 responses and almost have them.
---------- Post added at 12:28 PM ---------- Previous post was at 12:11 PM ----------
Apply the same method to the last upgrade (K910_SS_S_2_040_0078_131203). If you are lucky enough to have this version please contact me to see if you can Provide the QSB file.
You control by private (Because here I can not yet) a link to the version you want, I found on google, as I said I have not tested, I hope that this can do wonders lol
I also hope that I root Gapps and either Spanish or English: D
sakilxda said:
They are not good news. but I honestly what I need are 3 things:
1 Language Spanish, but we already you can not imagine not doing anything?
2 Root, to be able to use apps like Titanium Backup, Root Explorer, etc..
3 Very importantly, GAPPS (Play Store, Gmail), but of course in Spanish or English.
Click to expand...
Click to collapse
The few post I read about this are telling that it is close to impossible but I installed morelocale 2 on mine and it does add my language in the application that supports it.
Root is probably my top priority so it will stay available in the future releases
Play Store and GMail are present in the ROM and if you install morelocale 2, it will be in Spanish
sakilxda said:
You control by private (Because here I can not yet) a link to the version you want, I found on google, as I said I have not tested, I hope that this can do wonders lol
I also hope that I root Gapps and either Spanish or English: D
Click to expand...
Click to collapse
This is the link on Baidu I also found but for some reason, I can't flash it on my device so I can't cook it properly. I have to be able to flash it first
csu333 said:
The few post I read about this are telling that it is close to impossible but I installed morelocale 2 on mine and it does add my language in the application that supports it.
Root is probably my top priority so it will stay available in the future releases
Play Store and GMail are present in the ROM and if you install morelocale 2, it will be in Spanish
This is the link on Baidu I also found but for some reason, I can't flash it on my device so I can't cook it properly. I have to be able to flash it first
Click to expand...
Click to collapse
Of course, the priority is Root.
About the Gapps in Spanish or Englis, the could include a patch?
If not, do not worry that you use MoreLocale2.
I'll try to find more links ... it's a shame it does not work ...
The good news with root access is that you can do a lot of crazy things. For example, I'm starting to understand why it is so hard to get this upgrade thanks to a network dump:
Code:
POST /reaper/server/config2 HTTP/1.1
Host: fsr.lenovomm.com
Content-Length: 131
Content-Type: text/plain; charset=ISO-8859-1
Connection: Keep-Alive
User-Agent: Apache-HttpClient/UNAVAILABLE (java 1.4)
Config.2.1.2.imei.8628720201xxxxxxxxxxxxx
HTTP/1.1 503 Service Unavailable: [B][COLOR="Red"]Back-end server is at capacity[/COLOR][/B]
Content-Length: 0
Connection: keep-alive
That said, I'm sick of coming close to the end and receiving a connection time out
Patience friend, I do not really understand how you could do, but I'm sure you will. Good luck ...
sakilxda said:
Patience friend, I do not really understand how you could do, but I'm sure you will. Good luck ...
Click to expand...
Click to collapse
If I have latest version K910_SS_S_2_040_0109_131226 installed via ota update and push this system.img from previous version it's ok?
Really apreciate your work and hoping to be able to support you anyway. Keep working ! Respect.
katalinscrob said:
If I have latest version K910_SS_S_2_040_0109_131226 installed via ota update and push this system.img from previous version it's ok?
Really apreciate your work and hoping to be able to support you anyway. Keep working ! Respect.
Click to expand...
Click to collapse
This should work since the system it pretty much self contained but since I haven't tested it, I really can't be sure. Furthermore, this is a downgrade of your system.
If you have this version, could you check if you still have the image on your sdcard? This could be in folder /sdcard/lenovoota.
csu333 said:
This should work since the system it pretty much self contained but since I haven't tested it, I really can't be sure. Furthermore, this is a downgrade of your system.
If you have this version, could you check if you still have the image on your sdcard? This could be in folder /sdcard/lenovoota.
Click to expand...
Click to collapse
ok, here's the deal:
1. I tried to push system.img but no working, adb respond "failed: targed locked".
2. I don't have the ota file anymore BUT I have the K910_SS_S_2_040_0109_131226.qsb file. I poot this one in sdfuse folder and updated already before starting procedure with adb from above as you described, no problem just flashed it, btw it wipes everything.
So, my opinions:
1. Locked target issue could be determined by the bootloader beeing locked? Don't we need to unlock it somehow?
2. Can you reinsert root and gapps in this newer version K910_SS_S_2_040_0109_131226.qsb file?
3. How do you decompiled .qsbfile ?
Waiting for your feedback asap.
Respect.
Obs:
- we can use android-aio-flasher just to substitute from working with cmd commands... just sayin', works for me.
- reboot in recovery command doesn't work, just adb reboot bootloader, then lenovo logo appears.
- correct command for pushing system.img is adb fastboot flash system path to system.img.
katalinscrob said:
ok, here's the deal:
1. I tried to push system.img but no working, adb respond "failed: targed locked".
Click to expand...
Click to collapse
Just to be sure, is it an answer from adb or fastboot?
katalinscrob said:
2. I don't have the ota file anymore BUT I have the K910_SS_S_2_040_0109_131226.qsb file. I poot this one in sdfuse folder and updated already before starting procedure with adb from above as you described, no problem just flashed it, btw it wipes everything.
Click to expand...
Click to collapse
This is great news! Do you have any way of posting ithe QSB somewhere?
katalinscrob said:
So, my opinions:
1. Locked target issue could be determined by the bootloader beeing locked? Don't we need to unlock it somehow?
Click to expand...
Click to collapse
I had nothing to do but I did restart a few time with a custom boot.img that I never actually flashed. Maybe this helped?
katalinscrob said:
2. Can you reinsert root and gapps in this newer version K910_SS_S_2_040_0109_131226.qsb file?
Click to expand...
Click to collapse
I sure will!
katalinscrob said:
3. How do you decompiled .qsbfile ?
Click to expand...
Click to collapse
I wrote a script for that purpose. I have to clean it a bit before I can publish it but I'll definitely do it.
katalinscrob said:
Obs:
- we can use android-aio-flasher just to substitute from working with cmd commands... just sayin', works for me.
- reboot in recovery command doesn't work, just adb reboot bootloader, then lenovo logo appears.
- correct command for pushing system.img is adb fastboot flash system path to system.img.
Click to expand...
Click to collapse
You are right. I didn't know about android-auto-flasher, probably because I'm running Linux (which made my task easier to cook the ROM since the system partition can be mourned like any other).
I edited my first post with your correction and the link since I have now 10 messages on the board !
Well who are finding out that important things. Hopefully soon have new developments. I keep watching your work. I hope that more and more we are, I have put in all the sites I've found this link for more developers to come.
csu33 said:
This is great news! Do you have any way of posting ithe QSB somewhere?
Click to expand...
Click to collapse
I have it. please contact me in PM