Related
Just like our USCC friends, I'm currently working on several mods for Cellular South's release of the Desire. I'll keep this post updated with new developments.
Linked is a custom boot.img from our stock ROM with apps2sd support. You will still need to download and flash the latest Darktremor apps2sd release and format your SD card accordingly.
How to flash?
Place the dphase-apps2sd-signed.zip file on the root of your sdcard and flash it as a zipped update.
Download Link (Cellular South, also confirmed working with Alaska Communications):
http://dphase.net/desire/dphase-apps2sd-signed.zip (2.3 MB)
MD5 checksum: 70df556ceb6891cbdcc3801d807d58af
US Cellular stock boot.img with apps2sd support
http://dphase.net/desire/dphase-USCC-apps2sd-signed.zip (2.3 MB)
MD5 checksum: e11b6f40b26811e252f0579f0ed5861c
Latest Darktremor apps2sd:
http://www.darktremor.info/files/a2sd/dtapps2sd-2.7.5.1-adv-signed.zip
------------------------------------------------------------------------------------------
Zipaligned and PNG optimized system apps:
Code:
% du -sh original optimized
62M original
42M optimized
As you can see above, I've zipaligned and optimized the images in the system apps, which shaved off 20MB from total files size. This should lead to faster load times.
To install, untar the optimized archive to the directory of choice and boot to recovery. Mount the /system partition then do the following command with adb from within the directory holding the apk's (adb should be in your binary path, if not, fix that to make life easier in the future):
Code:
adb push . /system/app
You'll then see, for example:
Code:
push: ./DCSImpl.apk -> /system/app/DCSImpl.apk
push: ./HtcDialer.apk -> /system/app/HtcDialer.apk
push: ./EnhancedGoogleSearchProvider.apk -> /system/app/EnhancedGoogleSearchProvider.apk
... (etc)
Link:
http://dphase.net/desire/system_app_optimized.tar.gz (40MB compressed)
MD5 checksum:
2dc5fe2683e657006d2a8026c4ac32dc
reserved for later use
So what exactly does this accomplish? Is it basically adding apps 2 sd to the stock 2.1 rom? Any chance it will run on my US Cell desire?
Yes, adds apps2sd support to the stock rom. The latest a2sd will automagically move portions of /data over once it sees a properly formatted card.
In theory, this should work on USCC, but ymmv.
It is likely I won't get time tonight, but if I do, I'll be sure to give it a shot. I would like to get a2sd without a full reflash
con247 said:
It is likely I won't get time tonight, but if I do, I'll be sure to give it a shot. I would like to get a2sd without a full reflash
Click to expand...
Click to collapse
If it doesn't work, we'll grab your existing boot.img and I can tweak it.
Updates posted, please test and enjoy.
dphase said:
If it doesn't work, we'll grab your existing boot.img and I can tweak it.
Click to expand...
Click to collapse
That is the link to my boot.img
If you have time, if you could tweak that one, it would be great. If not, I'll give yours a shot tonight.
con247 said:
That is the link to my boot.img
If you have time, if you could tweak that one, it would be great. If not, I'll give yours a shot tonight.
Click to expand...
Click to collapse
I've modified your boot.img and placed a link in the first post.
dphase said:
I've modified your boot.img and placed a link in the first post.
Click to expand...
Click to collapse
A Big Thanks I am testing it now. I had to remember to change the MD5 information otherwise you get a fail.
Also You have to remember to run the apps2sd after the restore otherwise you will not boot!
Just booted and WOW look at all that new Space!!! Time to get more apps
seesser said:
A Big Thanks I am testing it now. I had to remember to change the MD5 information otherwise you get a fail.
Also You have to remember to run the apps2sd after the restore otherwise you will not boot!
Click to expand...
Click to collapse
Yes, I recommend installing apps2sd, formatting card, then applying new boot image.
How do you change the MD5 of the file
dphase said:
Yes, I recommend installing apps2sd, formatting card, then applying new boot image.
Click to expand...
Click to collapse
I guess I did it a little differently. I already had the sd card partitioned so I just took a backup swapped the boot.img and edited the MD5 with note++. Restored the modified backup and then ran the apps2sd.zip and rebooted.
I did it this way just in case something went wrong I could restore the backup that I didn't modify.
Going to try out that app optimize next.
Thank again.
This might be a noobish ?
but couldnt I just use a custom recovery and flash this as a rom?
or do I still have to push stuff?
im a lil confused coming from winmo
Right now im running blitz's apps2sd 2.1 sense rom
but not sure im seeing any benifit from the apps2sd....although I do see somethings being moved...wondering if seesser had tried blitz's rom...
are u seeing more space with the above method?
and what do I change the md5 to?
thanks
byte
bytethegroove said:
This might be a noobish ?
but couldnt I just use a custom recovery and flash this as a rom?
or do I still have to push stuff?
im a lil confused coming from winmo
Right now im running blitz's apps2sd 2.1 sense rom
but not sure im seeing any benifit from the apps2sd....although I do see somethings being moved...wondering if seesser had tried blitz's rom...
are u seeing more space with the above method?
and what do I change the md5 to?
thanks
byte
Click to expand...
Click to collapse
Hello and yes I was running that rom but did not like that friend Stream did not have twitter. with that rom you still had to tell the phone to move the files (a little bit of command line codding). With this boot.img and apps2sd on my stock rom backup I went from 15mb to 71mb so this one works great right out of the box.
I Explained how I did it from a backup of my stock rom up a few lines hope this helps.
I too am a little lost on this push of the app optimize. Could you explain it a little more? I have done a little adb shell programming but am lost with your directions.
Thanks,
bytethegroove said:
This might be a noobish ?
but couldnt I just use a custom recovery and flash this as a rom?
or do I still have to push stuff?
im a lil confused coming from winmo
Right now im running blitz's apps2sd 2.1 sense rom
but not sure im seeing any benifit from the apps2sd....although I do see somethings being moved...wondering if seesser had tried blitz's rom...
are u seeing more space with the above method?
and what do I change the md5 to?
thanks
byte
Click to expand...
Click to collapse
No, none of this can be flashed as a rom.
I'm not sure why anyone is changing MD5's, I included those so one could verify there was no data corruption during the download.
fixed. no worries..
con247 said:
I keep getting an MD5 mismatch after I edited the nandroid.md5 to the one in the original post
Click to expand...
Click to collapse
There is zero reason to edit that. Are you trying to use nandroid to flash the image? If so, that's the wrong answer.
con247 said:
fixed. no worries..
Click to expand...
Click to collapse
Did you restart the phone after you modified the MD5? I had that problem also until I restarted the phone and It worked after that.
Update (2/26): Discontinued
Note: If you flashed this without first flashing the stock RUU, you may not be able to get into CWM. If you want CWM back, either flash the stock RUU and then this modified RUU or check out page 13 of this thread
Credit goes to angelchen1111 and nyckid58 for providing me with the information needed to put this together.
Features:
-Based on stock RUU and not de-odexed
-Rooted
-HSUPA enabled
-Unknown sources option added to settings for sideloading
-Browser home page set to Google
-Removed the following bloatware apps:
AT&T Code Scanner
AT&T FamilyMap
AT&T Hot Spots
AT&T Navigator
Blockbuster
Live TV
myAT&T
YPmobile
Installation
1) Use the HTC Inspire Hack Kit here to get S-OFF so that you can flash custom roms.
2) Download the zip file here [removed] and put it on your SD card. Don't rename it and don't put it in any folders.
3) On your phone, go to Settings > Applications, turn off fast boot, and then shut down your phone.
3) Boot into HBOOT by pressing volume down and power. Once you're in HBOOT, the installation will begin. A factory reset will be performed so have your data backed up.
Funny that you mentioned it's not de-odexed, I'm actually working on that right now using Android Kitchen. I'll let you know if it works with the HBOOT loader if you'd like.
nyckid58 said:
Funny that you mentioned it's not de-odexed, I'm actually working on that right now using Android Kitchen. I'll let you know if it works with the HBOOT loader if you'd like.
Click to expand...
Click to collapse
Sure, let me know. I'll post up your de-odexed version as well if it works.
What difference does de-odexed give us?
Great work gtg and whomever had a hand in helping with this.
I'm assuming we can expect the same sound quality as the stock Rom?
Sent from my illmatic Inspire 4G / Desire HD
yzlvr said:
What difference does de-odexed give us?
Click to expand...
Click to collapse
In layman's terms, de-odexing modifies the system apps so that they can be manipulated (themed, etc.) more easily. It's sometimes a pain in the ass though and can lead to little bugs if the apps aren't de-odexed just right, so I just left everything how it was from HTC (odexed) for now.
If nyckid58 de-odexes it I'll post that in the first post as well, but both will be kept up until we verify that no bugs were introduced in the de-odexed version.
legend221 said:
Great work gtg and whomever had a hand in helping with this.
I'm assuming we can expect the same sound quality as the stock Rom?
Sent from my illmatic Inspire 4G / Desire HD
Click to expand...
Click to collapse
Yup, this thing is mostly untouched stock so everything should work as it did from the factory
gtg465x said:
In layman's terms, de-odexing modifies the system apps so that they can be manipulated (themed, etc.) more easily. It's sometimes a pain in the ass though and can lead to little bugs if the apps aren't de-odexed just right, so I just left everything how it was from HTC (odexed) for now.
If nyckid58 de-odexes it I'll post that in the first post as well, but both will be kept up until we verify that no bugs were introduced in the de-odexed version.
Click to expand...
Click to collapse
Ok, thanks for explaining it.
I'm still here, I've extracted and de-odexed all the files, the problem I'm running into is reintroducing it to the system.img. The de-odexed framework files add fine but the apps files is freezing up my computer. I'll update if anything else comes down.
Thank you for this. I wanted a minimally invasive option, so this is perfect for me. I just wanna be able to get rid of unwanted apps and bypass ATT's app blocking.
Do you need to do a wipe first and if so how do you do that sorry for the noob question
Sent from my Desire HD using XDA App
mmr8cmh said:
Do you need to do a wipe first and if so how do you do that sorry for the noob question
Sent from my Desire HD using XDA App
Click to expand...
Click to collapse
No. This is a little different than other ROMs. Do not flash this with ClockworkMod. Follow the instructions in the OP.
I'm all ready s-offd so Ill give this a whirl. I just ruu back to stock so ill post results and what i think in a few min great work always good to see forward progress
@GTG: I got the image compiled with the de-odexed files unfortunately though it throws off the size of PD98IMG.zip by about 120 meg. I tried to apply regardless but it wouldn't take. I'm thinking there is a size constraint, any ideas?
gtg465x said:
No. This is a little different than other ROMs. Do not flash this with ClockworkMod. Follow the instructions in the OP.
Click to expand...
Click to collapse
Thanks for the info
Sent from my Desire HD using XDA App
nyckid58 said:
@GTG: I got the image compiled with the de-odexed files unfortunately though it throws off the size of PD98IMG.zip by about 120 meg. I tried to apply regardless but it wouldn't take. I'm thinking there is a size constraint, any ideas?
Click to expand...
Click to collapse
I would imagine the system.img needs to be the exact same size. Did you create a new image or mount and modify the original image?
gtg465x said:
I would imagine the system.img needs to be the exact same size. Did you create a new image or mount and modify the original image?
Click to expand...
Click to collapse
Mount and modify. I don't think I'm ready to try to make an image from scratch.
nyckid58 said:
Mount and modify. I don't think I'm ready to try to make an image from scratch.
Click to expand...
Click to collapse
So how did it throw off the size of the zip so much? If you mount and modify the system.img should be the same size when you're done no?
edit: Regardless, if you're de-odexing it you might as well just package it as a CWM flashable zip instead of a system image.
gtg465x said:
So how did it throw off the size of the zip so much? If you mount and modify the system.img should be the same size when you're done no?
edit: Regardless, if you're de-odexing it you might as well just package it as a CWM flashable zip instead of a system image.
Click to expand...
Click to collapse
System.img is the same size yes but I'm thinking the de-odexed files are throwing the compression off. I think you might be right about the CWM idea. I shall research how to do that. Thanks again GTG.
Does the wi-fi tether app works without a tether plan?
Thanks
Hi guys,
It's good to be back on xda. Looks like we've got lots of updates regarding ICS ports..
Anyways, I just want to ask where do I mount the "lib" partition on my updater-script? I'm using the official hboot v2.
Long story short-I accidentally deleted ALL of my files(music, vids, images, phone files) recently on my PC. I tested out a ROM, forgot to do NAND backup thinking I just want to reflash my phone as new, so when trying to get back, i also forgot that I don't have any files anymore. (Note to self and anyone: NO mingling on the PC when drunk. )
So then I need to cook out a new for my own personal pleasure. So thats why I'm asking where to mount the "lib" partition. I'm just going to cook out from an official rom.
Thanks guys..
Edit:
Where do I mount the "lib" partition?
Skanob said:
Hi guys,
It's good to be back on xda. Looks like we've got lots of updates regarding ICS ports..
Anyways, I just want to ask where do I mount the "lib" partition on my updater-script? I'm using the official hboot v2.
Long story short-I accidentally deleted ALL of my files(music, vids, images, phone files) recently on my PC. I tested out a ROM, forgot to do NAND backup thinking I just want to reflash my phone as new, so when trying to get back, i also forgot that I don't have any files anymore. (Note to self and anyone: NO mingling on the PC when drunk. )
So then I need to cook out a new for my own personal pleasure. So thats why I'm asking where to mount the "lib" partition. I'm just going to cook out from an official rom.
Thanks guys..
Edit:
Where do I mount the "lib" partition?
Click to expand...
Click to collapse
Where'd you disappear man? I thought you were gone for good... Welcome back man!
Sorry I'm not gonna be much help with your query though...
Beamed from the Dark Side using xda premium.
enigmaamit said:
Where'd you disappear man? I thought you were gone for good... Welcome back man!
Sorry I'm not gonna be much help with your query though...
Beamed from the Dark Side using xda premium.
Click to expand...
Click to collapse
Thanks man!
I already forgot who the fellow member is also using the "lib" partition when the sense 3 update came out.. really can't remember..
And I think I'm the only one who still has an official rom?
Looks like everyone's up for the ICS update.. And me too..
Here you can find the lib.img, packed as PG88IMG.zip as well as the mount location (partition in question).
But IMHO use a custom ROM it is better than Stock in any way. For example proxuser's Saga3D is pure Stock but without the crap and optimized. Anyway it is up to you. Happy lib flashing
found it here: http://forum.xda-developers.com/showthread.php?t=1236890
thanks guys!
Edit:
Thanks amidabuddha, looks like i haven't seen your post yet when I found it. thanks anyways..
@Skanob
Can you confirm that by flashing the lib linked by amidabuddha works? I.e. without it flashed your nandroid backup did not work.
foX2delta said:
@Skanob
Can you confirm that by flashing the lib linked by amidabuddha works? I.e. without it flashed your nandroid backup did not work.
Click to expand...
Click to collapse
I have informed madmaxx82 about this issue couple of days ago. Now the new version of the 4EXT Recovery supports the separate lib partition of the Stock ROMs so it is restored also if backuped. For more info - there was a discussion about it in the 4EXT Recovery Touch thread...
@amidabuddha
Thanks, been watching the thread, what I am more asking is; does the lib in the thread you linked work, for those who have old backups not made with the latest recovery. I.e. nandroid restore then lib flash.
foX2delta said:
@amidabuddha
Thanks, been watching the thread, what I am more asking is; does the lib in the thread you linked work, for those who have old backups not made with the latest recovery. I.e. nandroid restore then lib flash.
Click to expand...
Click to collapse
It should work on a Stock backup. Also depending on the version you can always extract the lib.img from the corresponding 2.10.xxx RUU /rom.zip inside/ put it in a PG88IMG.ZIP.zip and flash in hboot
Sent from my Desire S using Tapatalk
foX2delta said:
@amidabuddha
Thanks, been watching the thread, what I am more asking is; does the lib in the thread you linked work, for those who have old backups not made with the latest recovery. I.e. nandroid restore then lib flash.
Click to expand...
Click to collapse
I can't confirm it, but if your talking about a backup of a stock rom, it should work flawless, at customs it's a bit harder to tell when you don't know if there also have something been modded (but in common it shouldn't really differ).
foX2delta said:
@amidabuddha
Thanks, been watching the thread, what I am more asking is; does the lib in the thread you linked work, for those who have old backups not made with the latest recovery. I.e. nandroid restore then lib flash.
Click to expand...
Click to collapse
It should work on a Stock backup. Also depending on the version you can always extract the lib.img from the corresponding 2.10.xxx RUU /rom.zip inside/ put it in a PG88IMG.zip and flash in hboot
Sent from my Desire S using Tapatalk
amidabuddha said:
It should work on a Stock backup. Also depending on the version you can always extract the lib.img from the corresponding 2.10.xxx RUU /rom.zip inside/ put it in a PG88IMG.zip and flash in hboot
Sent from my Desire S using Tapatalk
Click to expand...
Click to collapse
Beaten me^^
But you posted it twice
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
Credit goes to developer, zroice, at the International Note 3 section for his work towards this.
DISCLAIMER: I AM NOT HELD RESPONSIBLE IF YOU BRICK/BOOTLOOP/ OTHERWISE INCAPACITATE YOUR DEVICE IN ANY WAY. YOU'VE BEEN WARNED!
This has been confirmed working for the AT&T Note 3 (Thanks to drakeymcmb and Bri315317) WITH SOME PROBLEMS. Therefore, probably with some changes, this *might* work for our device. I wanted to share the information here to simply see if anyone is able to confirm or deny this for the SGH-I337.
Original Thread: http://forum.xda-developers.com/showthread.php?t=2550120
AT&T Note 3 Thread: http://forum.xda-developers.com/showthread.php?t=2554411
OP from zroice:
zroice said:
Ladies and Gentlemen I present to you the
kn0x0ut Toolbox v1.03!
(notice the 0x0 reference! hehe)
This script allows you to install custom roms, and mods that you would normally have to flash with custom recovery.
,
But as we all know, if you want to keep knox warranty void at 0x0 you cannot use a custom recovery or kernel.
If your knox warranty is already void aka 0x1 then you can still use this tool but it wont bring back the warranty...
---
This kn0x0ut toolbox itself requires root! You will have to use "Root de la vega" or some other method to get rooted while keeping your warranty intact.
---
How to use:
Extract the download from below to your internal or external sd card.
Then browse into that directory with terminal or adb shell and type:
Code:
sh kn0x0ut.sh
or
Code:
sh kn0x0ut.sh help
and you will get all the commands supported currently.
---
Check post 2 for full command list!
To install a rom or other zip you will have to extract its contents to the "extract_files_here" subfolder of kn0x0ut and then run the install command.
Code:
sh kn0x0ut.sh install
or
Code:
sh kn0x0ut.sh new_rom
(this is the command to install a new rom basically, meaning: backup and clean base, clean dalvik, install rom, reboot)
or if you want to install a rom with all the mods currently available:
Code:
sh kn0x0ut.sh new_rom all_addons
NOTE: The install script looks inside the extract_files_here folder for data and/or system folders to be copied over to the system or data folder on your device respectively.
All other folders it finds will get "ignored" (they will be copied to a folder "not_installed" which is created if the script finds incompatible folders or files). After the seperation
of the data and system folder from the unsupported ones, some dangerous libs which cannot be copied while the system runs will get removed from the temporary installation
folder so to ensure that there is no crash during the copy process. Once these files are removed the safe files get copied to your system and the permissions get fixed with
my permission fixing script.
The files that have been installed will get moved into a subfolder called "installed" and into another subfolder with the date and time of the installation.
The files that could not be installed by the script in the first run get moved to "not_installed".
These files could still become installed if you copy or move them over to the extract_files_here folder again for a second run. But remember that a data and/or a system folder is expected by the script inside the extract_files_here folder - so you have to make sure the structure is alright if you do things like this.
---
Example:
X-Note has the following folders when extracted:
META-INF, data, system, xnote.
The data and system folder will get installed, while the metainf and xnote folder wont. Inside the xnote folder you will find stuff that would normally be installed by aroma through user choice.
If you look inside there at the acid mod folder for example, there will be a system folder. To install this mod with kn0x0ut in a second run, you would have to move that system folder back
to the extract_files_here folder and then run the install command again. Only things inside data or system folder will ever be installed. And even then you gotta make sure the folder structure is
as on the system or data partition itself. (so apks need to be inside ..../kn0x0ut/extract_files_here/data/app or ..../kn0x0ut/extract_files_here/system/app to be moved to the right folder, etc...
you get it. (if not you should not use it for stuff like that)
---
This is only version 1.03 - I got more ideas to integrate but I dont wanted to hold things back any longer...
A word of warning though:
This is made for lazy people (like myself) and not for dumb people! (aka: its made to save time and ease up things and should be used with caution to not mess up things)
(for example: dont clean_base or use new_rom without actually installing a new rom or you will most likely end up without system apps and device not booting correctly - like you wouldnt wipe system in a custom recovery without installing a rom...).
It can be used over adb or terminal, but if you install a rom (clean_base) the system ui gets stopped, so better do it over adb!
It basically does the steps I described in my guide to install custom roms on knox firmware in a script, plus some other nice little timesavers.
Dont worry about error messages that say files dont exist or that they already exist! (thats normal)
Feel free to check out the source code and suggest improvements or enhancements like new mods to integrate.
Click to expand...
Click to collapse
Sent from my SAMSUNG-SGH-I337 using Tapatalk
Interesting...but since it doesn't flash kernels we'd still only be able to use whichever ROMs are compatible with stock kernels? I wonder how different the libs used are between the s4 and note 3
prisonnet said:
Interesting...but since it doesn't flash kernels we'd still only be able to use whichever ROMs are compatible with stock kernels? I wonder how different the libs used are between the s4 and note 3
Click to expand...
Click to collapse
You're probably right. It would be preferable for someone on mf3 to test because they would have a way to odin back to stock.
This basically sounds like framework modification. It sounds as if it might be use-able with TW based type ROMs but I doubt CM, AOSP, AOKP, or MIUI ROMs will work. If it works, it should simplify modifying the framework because it allows Devs to create certain Pseudo-Roms with many modifications to be flashed all at one time via ADB instead of needing to do several individual changes.
Take a look at the P-ROM or Pseudo-ROM thread in Android development by Nottach. It seems to be the same concept just for MDL firmwares.
phobia09 said:
You're probably right. It would be preferable for someone on mf3 to test because they would have a way to odin back to stock.
Click to expand...
Click to collapse
I'd be interested to see if this works on MJ9 / MK2 since SafeStrap isn't available for those versions yet, but I don't think there's odin available for MK2. Might be a one-way trip to bricksville.
prisonnet said:
I'd be interested to see if this works on MJ9 / MK2 since SafeStrap isn't available for those versions yet, but I don't think there's odin available for MK2. Might be a one-way trip to bricksville.
Click to expand...
Click to collapse
That's the main reason I posted this. I wouldn't want to test since I'm on mk2. I was more hoping someone on mf3 could test it and then maybe see if we could somehow tweak it for mj9/mk2 users if necessary.
phobia09 said:
That's the main reason I posted this. I wouldn't want to test since I'm on mk2. I was more hoping someone on mf3 could test it and then maybe see if we could somehow tweak it for mj9/mk2 users if necessary.
Click to expand...
Click to collapse
Going to try this after work tonight. I'm still on MF3. Read through the kn0x0ut script and no changes need to be made for this to work on our device - the partitions listed are all the same. I'll try a 4.2.2 TW Rom, then 4.2.2 GPE, then upgrade to MK2 and try a 4.3 TW and 4.3 GPE rom.
I'd be more confident trying this on MK2 if it worked on MF3 without any problems.
prisonnet said:
Going to try this after work tonight. I'm still on MF3. Read through the kn0x0ut script and no changes need to be made for this to work on our device - the partitions listed are all the same. I'll try a 4.2.2 TW Rom, then 4.2.2 GPE, then upgrade to MK2 and try a 4.3 TW and 4.3 GPE rom.
I'd be more confident trying this on MK2 if it worked on MF3 without any problems.
Click to expand...
Click to collapse
I would definitely appreciate it. If we can somehow get in touch with the same individual who uploaded the mf3 tars we may be able to get a method to flash back to stock mk2. Then we would be all set up with a way to flash without waiting on bootloader unlock or custom recovery. Looking forward to what you find out.
phobia09 said:
I would definitely appreciate it. If we can somehow get in touch with the same individual who uploaded the mf3 tars we may be able to get a method to flash back to stock mk2. Then we would be all set up with a way to flash without waiting on bootloader unlock or custom recovery. Looking forward to what you find out.
Click to expand...
Click to collapse
We also might be able to restore MK2 if someone can back up their MK2 installation using this method: http://forum.xda-developers.com/showpost.php?p=44917036&postcount=1
Would it be possible to use this to downgrade from MF3 back to MDL?? This could be very awesome...
hexagonsunja said:
Would it be possible to use this to downgrade from MF3 back to MDL?? This could be very awesome...
Click to expand...
Click to collapse
Unfortunately not. That requires a whole different level of access which, to my knowledge, no one has been able to achieve yet. Think of this as a command-line version of safestrap, without the rom slot functionality.
Interesting. I've given up hope on unlocking the bootloader for the s4. Minds much better than mine have tried and failed. If there's a way to circumvent the bootloader problem completely, this could be the holy grail for ATT S4 users! I agree that we'd probably have to stick with stock kernel ROMs, much like SS does, but it does open up an avenue of options for users.
I would volunteer, but as far as I know, there's no way to flash back to stock MK2 just yet. I can root easily enough, but I'm not going to risk a brick until there's a known flash to stock method. >_>
prisonnet said:
Unfortunately not. That requires a whole different level of access which, to my knowledge, no one has been able to achieve yet. Think of this as a command-line version of safestrap, without the rom slot functionality.
Click to expand...
Click to collapse
Ah I see, I wonder if this is the first step though... I am currently on MF3 and rooted, so I would likely be willing to try this out once others report success. I am hesitant to brick my daily driver though...
Zephcemi said:
Interesting. I've given up hope on unlocking the bootloader for the s4. Minds much better than mine have tried and failed. If there's a way to circumvent the bootloader problem completely, this could be the holy grail for ATT S4 users! I agree that we'd probably have to stick with stock kernel ROMs, much like SS does, but it does open up an avenue of options for users.
I would volunteer, but as far as I know, there's no way to flash back to stock MK2 just yet. I can root easily enough, but I'm not going to risk a brick until there's a known flash to stock method. >_>
Click to expand...
Click to collapse
I can verify that the script works on MF3. Just used it to remove then re-install the 4.2.2 GPE rom I was using with safestrap. I'm now going to upgrade to MK2 and try a 4.3 GPE rom...wish me luck
prisonnet said:
I can verify that the script works on MF3. Just used it to remove then re-install the 4.2.2 GPE rom I was using with safestrap. I'm now going to upgrade to MK2 and try a 4.3 GPE rom...wish me luck
Click to expand...
Click to collapse
Good luck! If you can verify, I'll be getting a 4.3 GPE rom myself. Godspeed!
prisonnet said:
We also might be able to restore MK2 if someone can back up their MK2 installation using this method: http://forum.xda-developers.com/showpost.php?p=44917036&postcount=1
Click to expand...
Click to collapse
I think this would be awesome, I am much too ignorant to understand; Where/how is this script to be run? Terminal Emulator? ADB? Odin itself? If it's something relatively low risk (and assuming I'm capable of doing it) I'll attempt it because I'm on MK2.
prisonnet said:
I can verify that the script works on MF3. Just used it to remove then re-install the 4.2.2 GPE rom I was using with safestrap. I'm now going to upgrade to MK2 and try a 4.3 GPE rom...wish me luck
Click to expand...
Click to collapse
GOOD LUCK! Thanks again for your contribution! :fingers-crossed:
phobia09 said:
I think this would be awesome, I am much too ignorant to understand; Where/how is this script to be run? Terminal Emulator? ADB? Odin itself? If it's something relatively low risk (and assuming I'm capable of doing it) I'll attempt it because I'm on MK2.
GOOD LUCK! Thanks again for your contribution! :fingers-crossed:
Click to expand...
Click to collapse
Just in case, I'd make an odin backup using this script http://forum.xda-developers.com/showpost.php?p=44917036&postcount=1
That way you can return to the state your phone is in now if something goes wrong - it will probably take at least an hour, and is harder to restore than a backup would be in TWRP or similar, but at least it's possible.
If you do want to give it a shot (make a backup first!), all you need to do (which I'll be doing myself after my phone finishes updating to MK2) is extract this rom http://forum.xda-developers.com/showthread.php?p=47718525#post47718525 into the "put_files_here" folder of the kn0x0ut zip, then send the whole kn0x0ut folder somewhere to your phone, like /mnt/extSdCard or just /mnt/sdcard.
Then through adb (not terminal emulator because the GUI will crash - as expected - when you delete the rom you are currently running), do sh kn0x0ut.sh install and it should automatically install the rom in the "put_files_here" folder. I think there's a new update of the kn0x0ut script coming soon that allows flashing of straight zip files, but not sure when that will be released.
prisonnet said:
Just in case, I'd make an odin backup using this script http://forum.xda-developers.com/showpost.php?p=44917036&postcount=1
That way you can return to the state your phone is in now if something goes wrong - it will probably take at least an hour, and is harder to restore than a backup would be in TWRP or similar, but at least it's possible.
If you do want to give it a shot (make a backup first!), all you need to do (which I'll be doing myself after my phone finishes updating to MK2) is extract this rom http://forum.xda-developers.com/showthread.php?p=47718525#post47718525 into the "put_files_here" folder of the kn0x0ut zip, then send the whole kn0x0ut folder somewhere to your phone, like /mnt/extSdCard or just /mnt/sdcard.
Then through adb (not terminal emulator because the GUI will crash - as expected - when you delete the rom you are currently running), do sh kn0x0ut.sh install and it should automatically install the rom in the "put_files_here" folder. I think there's a new update of the kn0x0ut script coming soon that allows flashing of straight zip files, but not sure when that will be released.
Click to expand...
Click to collapse
@prisonnet Have you utilized this script on any previous versions? Actually used the tar ball to restore anything? I haven't tried and I'm a bit skeptical.
Sent from my SAMSUNG-SGH-I337 using xda app-developers app
brobinson2102 said:
@prisonnet Have you utilized this script on any previous versions? Actually used the tar ball to restore anything? I haven't tried and I'm a bit skeptical.
Sent from my SAMSUNG-SGH-I337 using xda app-developers app
Click to expand...
Click to collapse
I'm making one right now to see if it can work, though i had to build the commands into my own batch file as running the script through ADB or Terminal Emulator didn't work. Currently compressing the files and then hopefully when i test them it will work, but i am highly doubtful that it will because i believe they need to be signed and i remember Aou creating something like this for MF3 in his neutered update thread and I believe it didn't flash.
DeadlySin9 said:
I'm making one right now to see if it can work, though i had to build the commands into my own batch file as running the script through ADB or Terminal Emulator didn't work. Currently compressing the files and then hopefully when i test them it will work, but i am highly doubtful that it will because i believe they need to be signed and i remember Aou creating something like this for MF3 in his neutered update thread and I believe it didn't flash.
Click to expand...
Click to collapse
I'm working on the same thing now. If the tar file doesn't work, my next step is to try manually flashing the backed-up system.img.ext4 with busybox dd. Someone correct me if I'm wrong, but ROMs contain boot.img and system files, since we can't flash boot.img without bricking that leaves system.img? I know safestrap doesn't flash boot.img; I assumed it just flashed the system - so I'm just trying to do that manually.