Related
Hola peoples!!! Ok so I just thought I'd create my own thread on this matter. Mustangtim started one in apps and themes (and here is the link to that thread) but since I'm taking over this project it was brought to our attention that this should be in the dev section as its no longer just an app.. I am actually tearing .imgs apart trying to figure out what the deuce.
FIRST OFF THIS IS A WORK IN PROGRESS, WE ARE NOT YET FULLY SUPPORTED. HOWERVER I'M DOING MY BEST TO CHANGE THAT.
Secondly if you want to help get this started please visit the market and grab the app here. Its a $3 dollar app for unlimited amount of roms, based on your SD card storage capacity anyway. And speaking of which you need AT LEAST a class 4 or better SD card to make this run smoothly.
Also feel free to visit the forums at http://forum.init2winitapps.com/
Ok so here it is, Boot Manager Pro. Its been a long time coming for the g2x to dual boot. First off let me say long story short, I currently have a bootable SD Rom, known as ROM1. I have yet to be able to recreate my findings tho. But it works and it doesnt brick at all. However it is a bit laggy on my class 4 SD card. Luckily I've already done my research on this project as there are many threads of such awesome info so I'm just going to be lazy about it and quote the good people of xda versus re-writing it based off of their info.
ChrisDDD said:
So here's a very basic description of how it works... It doesn't partition your SD card, it just creates a folder of its own, and then sub-folders to hold the different roms you install. When you install a rom, it basically creates images of the usual Android partitions - system, data, cache, & boot. These are standard .img files, just like the ones Clockwork creates when you do a backup. After the images are created and wiped (formatted, which you should do initially) it installs your rom into these essentially the same way as Clockwork installs a rom to your phone's actual partitions. I assume it modifies the kernel that comes with each rom to mount the image files on the SD card instead of the phone's partitions.
When you want to boot a rom, it just replaces your current boot image with the modified one and restarts the phone. With the modified boot image, the system, data and cache images on the SD card are mounted to the correct locations and Android starts up none the wiser. The rom will initially run a little slow, because the SD card is slower than the internal memory, but after things get cached it speed up considerably.
When you want to reboot to another rom, or back to the phone's rom, Boot Manager again swaps boot images that mount the desired rom's partitions (in the case of the phone's rom) or files (in the case of an SD card installed rom).
When you first run Boot Manager, it makes a Clockwork flash able backup of your current boot image, which you can flash if a rom hangs or loops on startup. Alternatively, you can also simply boot into recovery and do an advanced restore, choosing just the boot image to restore from a backup. It accomplishes the exact same thing.
It can be a little hit or miss, with some roms just plain refusing to start through Boot Manager, but it does work and when it does, it's pretty amazing given what it's actually doing.
Click to expand...
Click to collapse
So basically upon installing the app you need to setup your phone so that way you can properly install a ROM, follow these steps:
1. Go into the supersu(or superuser app) and then go to settings then disable logging or click none.
2. Then go into the BMP app and press the menu button on your phone, not the app, and go to settings. Once in settings put a check mark in force large boot.img, screen on during install, and then go into variables, leave tegra alone but change the sdcard block to show mmcblk1p1. Then press finish and let the app restart. By the way I didnt change any of the sizes of the .imgs but feel free to do so. But be warned do not decrease the size of the system.img only increase it, if desired.
3.Then after you've done the above you need to setup the phone rom. Click on 'Setup Phone' under phone rom and follow that process to setup your phone rom.
4. Once your phone rom is setup you may begin to install a zip to rom1 or rom2 or whatever slot you want. This is the tricky part. I have done tons of reading and most people say that if your using CWM, which us g2x'ers do, then you will probably have a better chance of getting a bootable rom by restoring from a nandroid backup you did versus installing new.
5. So after you decide which path you will take, nandroid backup or fresh rom install, choose install. If you choose a fresh rom, wipe system, data, and cache right away. If nandroid, then wipe after the install.
6. Now once you have clicked install put your phone down, DONT MESS WITH YOUR PHONE AT ALL! PUT IT DOWN AND WALK AWAY OR SOMETHING! Don’t mess with it, text from it, xda from it, dont even use the screen as a mirror!!!! lol seriously the app is picky and while under the .img creation process you want nothing to mess that up or you will not get it booted. You may however drag down the notifications bar to follow the progress of the install.
7. Once its complete, tap the install complete notification in the notification bar and let the app do its thing to finalize the install and get you back to your rom selection screen. Now if you did a nandroid back up here is where you click 'manage slot' and then factory reset the backup you did. Just do it, dont ask why.
7.1 Also so if you desire to install gapps and/or possibly a different kernel, now would be the time to do so while your here. I have read mixed reviews of doing this process right after the rom installs. However when I set up my rom1, I booted into it first all happily then realized I had no gapps. So I had to reinstall BMP on rom1 then boot back to phone rom and then I installed GB gapps and had no issues booting back into rom1.
8. Once the above steps are done if your feelin lucky go ahead and tap on boot the rom you installed, and if all goes well it will boot up.
9. If it boots up you need to post confirmation here!!! Provided info such as phone rom and the info on the sd rom you used and slot number and such.
Hopefully it will just work for you. I have done all the above steps using HFP 2.1 as my phone rom and only been able to get 1 bootable rom. Being it was for testing I used HFP as my phone rom and as well as my rom1.
So if the above steps dont wortk out for you and your boot lopped or what ever, then turn your phone off and reboot into cwm. You have 2 options to resolve the boot issue you just created. 1, you may go to restore then advanced restore then restore your boot. Or 2. select install a zip and nav to the bootmanager folder then phone rom then flash the update zip there.. then reboot and you should be back at your phone rom.
Here is a basic run down of everything that I have done so far:
When I first started working on this project I wasn’t doing any dev'ing to change any of the stuff in the boot.img. I just changed settings in the app per all the research I did. So when all was said and done I restored HFP 2.1 to ROM1 and it actually booted!! And it works lovely btw.. I can still boot into this rom today. I then decided to pass the word and ways that I created the working rom1, well I nor anyone else I passed the info to was able to get it working. Only one other person was able to confirm that rom1 works but only after I copied all my rom1 info and sent it to him for testing.. and he was able to boot into my created rom1… As I see it, it was a blue moon event that I have yet to repeat. So I thought eff it lets do some dev'in so I unpacked the boot.img from rom1 then compared that to the unpacked boot.img from rom2 that I created in my trial and error experiences. So in doing so I noticed 4 differences; 1, the mount points obviously, 2, in the sbin folder had a ueventd file from the working rom1 was a text file viewable by gedit in ubuntu. In rom2 it was just a non-readable file. 3, in the init.rc file was also missing a chmod command for system, (the command is in rom1 but not rom2) and 4, there was a ueventd.tegra file that was in rom1 that wasn’t in rom2, but everything else is the same. So I decided to plug and play with the differences to see if she boots and no go. I don’t understand why its boot looping because I am using the same rom as phone rom as for rom1 and rom2. So it boot looped. So I had to restore my boot.img many times in cwm.
So then I said eff it lets do some more research, then I noticed in the .zips folder plus the individual rom folder there are .zips that will let you flash via cwm if you get boot loops and 'should' get you booting to your desired sdrom. I then tried that way and no go.. so then I opened up the zip and had a look at the internals.. first there is the moveboot.sh file that the app runs in cwm flash the given boot.img. I then checked out the meta-inf and opened up the updater-script thinking that the app wasn’t actually flashing the boot.img which is why it loops... Well I think im half way right. However the script itself is lil dodgy... first thing I noticed was at the end of the script they have a command to cp the log from /tmp to /sdcard/bootmanager well the command was wrong so it never copied the log. So I fixed that. I also saw that the assert command was pointing to ‘boot’ instead of mmcblk0p5, so I changed that too. Then I decided to do away with the assert command and the moveboot.sh file they have going on to utilize the same functions that the kernel zips use, which is a kernel folder that holds the boot.img and a run_program that dd's the boot.img to 0p5. plus I even updated the update-binary that the file uses. I used the one from the g2x nullifier as I know that one was made for our phone and should have no issues.. plus there was a noticeable difference in the sizes of the provided binary to that replaced binary. So with the updated.zip file I then rebooted into cwm to flash that being that I was using a different command to flash the boot.img as well as the other changed stuff and still it boot looped. So as of now the only thing I don’t think ive done was grab the boot.img from rom1 then change the mount points, only change that, and then use that for rom2 and see if it boots. I don’t think I’ve done that yet. But every dam process I do I get boot loops. So basically I have came to the conclusion that it’s now NOT a boot.img issue being that I have done everything to change the boot.img and to make sure it flashes, which it does indeed and now creates the log too… I think maybe it has issues with the system.img as that’s what comes next in the boot process. But that’s just my hypothesis. I won’t be able to confirm this till I liberate rom1’s boot.img then change the mount points to point to rom2 and then see if it boots.. if it don’t work then that would mean to me that there is an issue with system.img created. But that’s just my hypothesis…
What I don’t understand is why the eff when I didnt hack the app I got a working sd-rom, but when I do change some stuff with it still don’t work!!???!! I guess maybe ill just edit/hack the apk to see what’s up.. This is getting way more complicated than it needs to be, since it worked prior to all my major changes to the script its using for flashing and the boot.img and what not. Anyone have any ideas feel free to add them.
My next steps are to edit rom1 boot.img one last time to change the mount points to point to rom2 and then if that’s a no go then it’s got to be the system.img that’s getting created. By the way this whole process I have only been restoring my nandroid backup for HFP 2.1. I have not attempted to flash new as with thru my research more times than not people would get a bootable rom via restoring versus flashing new.. so if anyone wishes to experience an sd rom let me know, ill send you a link to download my rom1 to get it going. Mind you that its not perfect and you need a class 4 or better sdcard. Everything works but it just takes a bit longer to load things and get things cached as its on the sdcard and not nand. Also if you have any input or are wishing to help pm me I need more heads to get this sorted as I can’t be the only one who knows how to edit scripts and unpack imgs and such. Either way I will continue to do this until I get it right damit!!! Oh and I just ordered a class 10 sdcard to help with this process…
That was copied from the other thread that mustangtim started. Last night when I went home the first thing I did was change the mount points on rom1 to reflect rom2, I changed nada else, then I tried to boot it... it boot looped. So maybe its a permissions issue or the system.img.
So just as a proof of concept and before anyone calls bs on my work/findings Here is the link to my rom1 that boots and is HFP2.1. *Update, 'm just going to
leave it on my DB for now till I find something better I guess. xda wont let me attach the file since its 233MB. Oh well here is the link :
Code:
[URL="http://db.tt/eBZwrOrs"][U][B]Here it is, my Rom1 HFP 2.1[/B][/U][/URL].
I have also attached my updated script file to flash back to rom1, for now.
The boot.img points to rom1 instead of phone rom, ill add to phone rom
as well, just not the now. :) Feel free to flash this via cwm versus
restoring...
Also this is part of the this: the ‘.zips’ folder you need to replace the file in
that folder as well. It’s an update file for rom1 to flash the boot.img.
..
If you’re going to use this you need install a random rom to rom1 then replace those created files in rom1 with these files in the 7z file..
So I am doing this new thread to get the devs or people with know how to help me out with my findings. I have edited the boot.img so much I could pretty much re-write everything in there by now including using magic to create to my own kernel eff!! lol jk but seriously I need people with knowhow to provide confirmation of go or no go. Basically I have people whom have helped out but It seems that I'm the only one who has dug this far into this app(unless i've been misinformed) and I have no one on my level to talk with except the init2winit devs. Which are very helpful btw.
And lastly:
Conap said:
Guys if it's failing to make the boot.img first make sure your using the market version....others have released cracked versions of our app which they broke...if your using the actual market version just send me a pm or email [email protected] and send your log.txt from BootManager folder on sdcard and we'll get it straightened out. Thanks.
Click to expand...
Click to collapse
or post here or PM me, I'm always down to help out.
Also thanks go to the init2win team, Gflam and Conap as they started this app. and as well to Mustangtim as he brought me into the light of BMP.
So you got all that???!!!??? Now lets get this party started and get full support for dual booting. I will not rest until I get this working. Thanks for your time and possible assistance.
Ok so since I have a book above I thought this is a good place for links and such...
So just incase anyone is curious, here is the Official Boot Manager Manual
Here is a nice link for Tips and Tricks while Installing ROM's that so far has good info to help you watch via adb what the BMP is doing in its creation process.
Some FAQs:
When should I set up my phone ROM?
Set up your phone ROM EVERYTIME you install a new ROM to your phone so you can get back to your phone ROM and won't get stuck on your SD ROM.
My SD ROM seems to lag how can I fix this?
SD ROM lagging may be due to a few things which all have easy fixes. First fix is that most of you have class 2 cards which are what usually come with your phones. These have a much lower read/write then cards of a higher class, we recommend a class 6 card or above. Another easy solution is overclocking merely install a better kernel and use CPU Boost (or any other overclock app) to overclock your phone.
Can I nandroid my SD ROM slots?
Yes and no you can't nandroid them in the traditional sense of the word using recovery but this app works as a recovery for your SD ROM slots and you can back up your ROM slots within the app in the Manage Installed ROMs section which works as a nandroid for your slots by fully backing up your slots to your sdcard which can later be restored.
What if I want to change the sizes of my images, how may I determine the individual sizes easily?
Easiest way is to open up terminal emulator in your app drawer. Type 'su', then grant permissions if need be, then type 'df -h' and it will display such information. You may also use adb in the same fashion. Connect via usb, open up command prompt/terminal and get adb connected and then type 'df - h' again and the same info will show. I will say this again just because, do not decrease the size of your system.img ever! Unless you want mad issues!
Here is the changlog link and just for heck of it the info based on that link:
Code:
V3.2.6
Fixed DroidX/Droid2 Install issue
Fixed UI theme issues
Fixed issue with spaces in name of pic when selecting photo for screen shot
V3.2.5
Fix to allow continue of install if no boot.img is found.
V3.2.4
Added support for HTC Rezound
Added support for rom's with multiple boot.img's
Added support for rom's made for multiple phones
AutoDetect sdcard for usb mounting
Fix for installing ICS gapps
Optimized SDRom Install process
Added support for Motorola RAZR
Added install queue
V3.2.3
Fixed issues with rom's not showing when on emmc on Droid Incredible
Fixed issues with not showing correct booted rom in app
More improvements to sms sync(all rom's will need updated app for changes to apply)
Fix issues with loader
Fixed issue with switching to backup server when main server goes down
Fixed 1x1 widget to show unlimited rom slots
Added 2x2 widget that works with unlimited rom slots
V3.2.2
Fixed force close for img's over 1Gb when resizing
Fixed current booted rom displaying correctly on gnex
Fixed issue with wrong busybox downloading on gnex which should fix alot of install/boot issues
V3.2.1
Fix for errors causing installs to fail.
Fix for some of the licensing stuff.
Removed sdbooster prefs from Galaxy Nexus(Since they don't have sdcard).
V3.2
Changed 4 sd slots to infinite slots!
Galaxy Nexus Support
Sms and Call Log synced between ROMs (you choose what ones too also requries updating boot manager in all slots)
License Check extended to a week
ROMs do not need market installed for boot manager to run (requires updating boot manager in all slots)
Hide su toasts (superuser elite only)
Fix for force close when setting screen shot in MIUI rom's
Thunderbolt defaulted to force large boot.img
Fixed unsupported device using a key
Manually setting variables only accepts numbers
V3.1.1
Fix for various force closes in rom installs and Nand restores
V3.1
Added su binary check
User selectable colors for everything
Better navigation (press title for quick action)
Added compatability for new twrp backups
Better compatiblitlity with memory tweak scripts(i.e. supercharger script and liquids default scripts)
Fix for install process being killed by android
Fix for some themes erasing img's
Fix more force closes during install
Force smaller boot.img option in settings(Fix for some phone's who's boot.img won't fit on the phone after BootManager edit's it)
Improved gapps checker
Improved security
Boot Manager now accepts keys pay for by paypal (see http://init2winitapps.com/stories/BootManager.html)
Added Evo 3d GSM Support
Added notifcation sound/vibrate for finished install (turn on in settings)
Improved data check
V3.0.3
Fix some force closes
V3.0.2
Added backup server (Sorry our server dropped out)
Fixed some force closes
2nd init fixes for Liquid's ROMs
V3.0.1
Last minute UI fixes
V3.0
UI Completely redone
Includes screen shot of each slot
Custom Info
Custom Dialogs
Custom Animations
Custom everything!
Bug Fixes
Added Droid 2 Global support
Screen shot with long press of search
V2.2.1
Bug fixes in file browsers
File browsers only show relevent files
Kernel installer fix
Droid 2 bug fix
V2.2
New security (more advanced and requires data only once a day)
Installs no longer require data
Added Italian translation thanks Black-Ice
Droid X support
Droid 2 support
Fixed status bar notifications
Fixed phone rom rebooter if gapps aren't installed
Bug fixes
V2.1
Restore android_secure to sd from nandroids
Added TWRP nandroid support
Added CWM tar nandroid support
Added Spanish translation
Made widgets easier to use
SD Booster added (Change SD read cache for better preformance)
Added current settings to manually set variables.
Added option to keep screen on during install in settings
Fixed usb layout
Updated Security
Bug Fixes
V2.0
Install now runs from the foreground (status bar)
Restore Nandroids to slots also in the foreground
User can cancel installs as they run
4 new themes added including one by apophis9283
Some phones such as tb moved to new install code (Fix for some sense rom's)
V1.3
Added third theme to app (Red Theme)
Added 4x1 widget and new widget styling
Fixed in app messenger
Added support for Htc Evo 3D
Added support for Htc Sensation
Added Support for Htc Incredible 2
Added Support for Htc Incredible S
Added Support for Htc Desire S
Added support for LG Ally
V1.2
Added option to reboot to phone rom to install gapps in license check dialog
Better error checking and error logging
Automatically install's ext2 libs if not present
Moved Set Names to Manage rom's
Fix for add-on's not installing correctly
Better compatiblility for rom's that use data2ext or apps2sd(user must set larger img's in manual variables)
Trash cleaner added to extras
Better Fix for WiFi issues on Droid 1
Added display to show what rom you are booted into
Fix for updater-script not found errors
Added support for Htc NexusOne
Added support for Htc MyTouch4G
More compatiblity for ext4 support
V1.1
Fix WiFi issues on Droid 1
Fix bug in rom installer for setting permissions correctly
Fix bug for cache size not setting correctly in setting variables manually
Fix for decimals entered into partition sizes causing force close
Fix force close in widget
Fix force closes in installer
Added Wipe data/Factory reset to Manage Rom's section
Added code to show what file's are being unzipped in dialog
Added support for rom's that extract files to sdcard so the files actually end up on your sdcard
Added support for Htc Desire (apps2sd and data2sd rom's support is experimental. Please email if you test it and it works/doesn't work)
Added support for Htc Inspire4g
Added support for Htc DesireHD
Added option to use ext4 filesystem if rom's support it-Experimental Won't work with all rom's.
Added log.txt file to sdcard to log errors during install
V1.0
Initial Release
YEZZZ
glad to finally see this here!
jookdakang23 said:
glad to finally see this here!
Click to expand...
Click to collapse
indeed... hopefully it wont be before too long that I get this app fully supported for us!
This app will be extremely useful for G2X owners and makes the G2X more versatile and desirable.
da-pharoah said:
indeed... hopefully it wont be before too long that I get this app fully supported for us!
Click to expand...
Click to collapse
idk how you get it booted. lol i keep getting bootloops
jookdakang23 said:
idk how you get it booted. lol i keep getting bootloops
Click to expand...
Click to collapse
Are you using the files I supplied or the ones that BMP created for you?
Woo hoo good job bud
Sent from my LG-P999 using xda premium
x0xhellx0x said:
Woo hoo good job bud
Sent from my LG-P999 using xda premium
Click to expand...
Click to collapse
LOL thanks bro.... Go Team Hellfire!!!!
da-pharoah said:
Are you using the files I supplied or the ones that BMP created for you?
Click to expand...
Click to collapse
i remember requesting the files but think you ever sent them
jookdakang23 said:
i remember requesting the files but think you ever sent them
Click to expand...
Click to collapse
no we had a miscommunication due to our avail times and GB's lacking ability to utilize two accounts on gtalk.... I have posted those files in the op however...
First, I want to thank everyone who has helped with us on this app. Second, I know I picked the right man for the job, did you see that OP! All kidding aside, a lot of you know I write for ACS under screen name artifintel. I just had too much on my plate to give this project the attention and direction it needs. The right guy is in charge, he's a stand up person and very knowledgeable with this app. Good luck everyone!
[email protected]
I tried installing CM9, it didnt work, stuck on first boot screen after the LG logo.
I'm using rooted stock 2.3.4
Rafase282 said:
I tried installing CM9, it didnt work, stuck on first boot screen after the LG logo.
I'm using rooted stock 2.3.4
Click to expand...
Click to collapse
what rom are using as phone rom? and you installed to rom1?
da-pharoah said:
what rom are using as phone rom? and you installed to rom1?
Click to expand...
Click to collapse
As phone rom i;m using rooted stock 2.3.4 v21y
The to rom1 I installed CM9 kang from oiwan with gapps and harsh kernel
Rafase282 said:
As phone rom i;m using rooted stock 2.3.4 v21y
The to rom1 I installed CM9 kang from oiwan with gapps and harsh kernel
Click to expand...
Click to collapse
and no bootloop you say?? well then it may be the stock rom your using... The app is very picky and if you get a bootloop, I feel that those can get booted with tweaks... but stuck on lg screen is just no bueno.. Try a different rom... maybe one that has its partitions at ext3 format just to try it.. I think owains rom uses ext4, but I could be wrong. I havent fully researched his rom yet..
hands down, a badass app...
SiL3nTKiLL said:
hands down, a badass app...
Click to expand...
Click to collapse
lol +1 for sure!
da-pharoah said:
I think owains rom uses ext4, but I could be wrong. I havent fully researched his rom yet..
Click to expand...
Click to collapse
positive on ext4
I Proudly Present the first Custom Rom available for the Samsung Galaxy Tab 2 10.1 (GT-P5113)
What is this you ask:
This is a slightly modified version of the most current stock ROM available for the Galaxy Tab 2 10.1 (GT-P5113).
Notice for CleanRom v1.0 users:
The update instructions are below the installation instructions. Updating to the newest version will NOT remove any of your settings or data as long as you do not Wipe Data / Factory Reset.
Changlog:
Code:
Version 1.1:
1. Moved Dropbox to Data so it can be removed
2. Removed SuperSU and added Superuser to resolve some issues.
3. Added download containing removed apk files (See details below)
Features so far:
-Stock, Rooted, Deodexed, Zipaligned
-Removed a bunch of bloat applications
-Removed crap bookmarks
That's about it.
Pre-requisites:
1. You must have the custom recovery installed from the Rooting thread. (If you are going to install this you do not have to install the root zip file, this rom is already rooted.)
Installation Instructions: (Update instructions below)
1. Download to external sdcard
2. Reboot to recovery
3. Make a nandroid backup Highly Recommended
4. Data Wipe/Factory Reset REQUIRED for new installations
5. Flash Rom
6. Reboot and enjoy
Update Instructions:
1. Download the latest version to your external sdcard
2. Reboot to recovery
2a. Looks like you may need to wipe data (Some people are reporting issues with Wifi if they do not wipe data.)
3. Flash Rom
4. Reboot and enjoy
Flashing the rom on my device takes about 1.5 minutes or less, but the first boot will take about 2.5 minutes, and then another 30 seconds or so to format the applications. After the first boot it will boot up much faster.
Further Information:
Since this is basically a very minimally modified version of the stock Rom there is no need to post screenshots.
Removed Apps:
Below in the download section you will find a zip file containing all of the apk files that have been removed from stock during the process of building this Rom. Some of them will allow you to simply install, but other will require a little more effort:
To install apks manually that will not install themselves you will have to do the following:
1. Move the apk file to the /system/app/ folder with a root enabled file explorer
2. Reboot you tablet.
Download Links:
Version 1.1 (Current release)
Dropbox Download v1.1
Google Drive Download v1.1
MD5: 530ba66c73a052a486f2e28a3d725a7c
Removed Apps download:
Removes Apps (Dropbox Link)
Removed Apps (Google Drive link)
MD5: ed75336fb4693b1c7361a9fa1a85d0a1
Version 1.0:
Dropbox link: Download v1.0
Google Drive link: Download v1.0
MD5: fff31853881ba6d7c6a91c5a013fdb23
Let me know if you have any issues with Google Drive, and I can look into hosting it somewhere else also.
Special Thanks to:
martijn.vanpoorten For providing faster Dropbox hosting for this Rom!
Saved in case I need in the future!
Will this also work on P5110? Will be getting mine next week.
Sent from my Galaxy Nexus using Tapatalk 2
zyonee said:
Will this also work on P5110? Will be getting mine next week.
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
I am not really sure if it will or not since I only have the P5113. Do you know what the difference in the P5110 is?
Edit:
Took a quick look at a spec sheet and the only thing I noticed was that it looks like the P5110 might not have the IR?
sgrant said:
I am not really sure if it will or not since I only have the P5113. Do you know what the difference in the P5110 is?
Click to expand...
Click to collapse
Regional stuff only, I think, but if there are firmware files that differ between countries because of wifi channels, etc, it could be a problem. Never mind, I'll try it anyway. Might steal vendor files from a backup made before the flashing of your ROM.
Sent from my Galaxy Nexus using Tapatalk 2
The P5110 is without 2G/3G GSM Unit.
thor670
thor670 said:
The P5110 is without 2G/3G GSM Unit.
thor670
Click to expand...
Click to collapse
The P5113 does not have 2G/3G either.
I am looking forward to test this rom
I'm looking at creating a similar ROM for the 5100 (3G version) but I'm running into some issues during the framework de-odex.
@sgrant: if you have any pointers as to the tools or methods you use to actually make it work, I'd appreciate it.
Peace,
C.
Omg! Soo excited to try this!
Sent from my Nexus S using XDA
cheatman said:
I'm looking at creating a similar ROM for the 5100 (3G version) but I'm running into some issues during the framework de-odex.
@sgrant: if you have any pointers as to the tools or methods you use to actually make it work, I'd appreciate it.
Peace,
C.
Click to expand...
Click to collapse
If I had to guess I would say that you are targeting the wrong framework. Make sure you are targeting framework 15.
Regarding tools, I use Android Kitchen, but I DO NOT allow it to convert my updater-script to an update-script. Basically this means I can only use a few of the features of Android Kitchen:
1. Deodex Files
2. Zipalign
3. Create and sign zip
You may be able to use a few more things without the update-script, but I had troubles anytime I let Kitchen create it.
If you need more help create a thread in the Q&A forum and PM me the link. That way others will have a better time finding the information.
Clean ROM test results
Before you install the Clean ROM v1.0, know the following:
1. You MUST do a factory/reset in CWM5 (the CWM you install from my OP)
2. Factory Reset will NOT delete EVERYTHING on your external SD card
3. Installing Clean ROM V1.0 will NOT damage your CWM5.
4. I personally tested the Clean ROM V1.0 today. Runs smooth and it has some of the "bloatware" that can't be removed from the standard stock ROM. I detected an ever-so-slight improvement in smoothness & speed.
5. This ROM has NOT been tested on ANY Tab2 other than GT-P5113 at this time.
Bottom Line: We have our first SAFE custom ROM for the Tab 2 10.1 GT-P5113.
Thank you sgrant !
Glenn
weltwon said:
Before you install the Clean ROM v1.0, know the following:
1. You MUST do a factory/reset in CWM5 (the CWM you install from my OP)
2. Factory Reset will delete EVERYTHING on your external SD card
3. Installing Clean ROM V1.0 will NOT damage your CWM5.
4. I personally tested the Clean ROM V1.0 today. Runs smooth and it has some of the "bloatware" that can't be removed from the standard stock ROM. I detected an ever-so-slight improvement in smoothness & speed.
5. This ROM has NOT been tested on ANY Tab2 other than GT-P5113 at this time.
Bottom Line: We have our first SAFE custom ROM for the Tab 2 10.1 GT-P5113.
Thank you sgrant !
Glenn
Click to expand...
Click to collapse
Thank you Glenn!
But are you sure that the factory reset is deleting stuff from your external SD card? It is not deleting anything at all from my sdcard.
Factory reset does NOT wipe external SD card
sgrant said:
Thank you Glenn!
But are you sure that the factory reset is deleting stuff from your external SD card? It is not deleting anything at all from my sdcard.
Click to expand...
Click to collapse
My mistake. When I tried to access my external card using Astro File Manager it said the card was 100% blank and not even formatted. Removed SD card from Tab, plugged into my desktop PC and saw that all my files/data is still on the external SD card. I have corrected my posts accordingly.
Glenn
Excited to test this when I get home today!! Thank you for your work!
Drive link isn't working for me. It takes me to a sign up page that tells me that I need to upgrade my Flash player ? After redirect to play store I get error saying I don't have enough storage space, I do have a 32 gb card installed with 28+ gb of free space. :-O
Pp.
Sent from my GT P-5113 using xda HD that does not force close everytime I hit submit.
PanchoPlanet said:
Drive link isn't working for me. It takes me to a sign up page that tells me that I need to upgrade my Flash player ? After redirect to play store I get error saying I don't have enough storage space, I do have a 32 gb card installed with 28+ gb of free space. :-O
Pp.
Sent from my GT P-5113 using xda HD that does not force close everytime I hit submit.
Click to expand...
Click to collapse
It shouldn't make you sign up. Let me see about putting up another link somewhere.
Give me a few.
Edit:
Try this: Download
We really really need the stock rom in odin flashable form lol Does anyone know if there's one out yet or how we could accomplish getting this?
kalel90 said:
We really really need the stock rom in odin flashable form lol Does anyone know if there's one out yet or how we could accomplish getting this?
Click to expand...
Click to collapse
perhaps sth. like this could help
http://forum.xda-developers.com/showthread.php?t=1405041
http://forum.xda-developers.com/showthread.php?t=717437
kalel90 said:
We really really need the stock rom in odin flashable form lol Does anyone know if there's one out yet or how we could accomplish getting this?
Click to expand...
Click to collapse
The 7 inch version has the stock odin tars for the 3113. I've seen stock tars for the p5100 and p5110 on sammobile and sampro.pl, but nothing yet for the p5113.
Sent from my GT-P5113 using XDA Premium HD app
Team Win Recovery Project 2.2, or twrp2 for short, is a custom recovery built with ease of use and customization in mind. It’s a fully touch driven user interface – no more volume rocker or power buttons to mash. The GUI is also fully XML driven and completely theme-able. You can change just about every aspect of the look and feel.
Phone look:
Tablet look:
CHANGELOG (for 2.2.2.0 compared to 2.2.0.0):
Mostly bugfixes:
Significantly improved sd-ext handling (ext partitions on sdcards)
Changes to kinetic scrolling in file selectors
Fixed a problem with using periods in backup names
Fixed problems in XML layouts with mounting system and USB storage
Fixed a problem with unmounting a partition before formatting during restore
Add Jelly Bean decrypt support
Updated 320x480 theme to match others (thanks to Llewelyn)
Improve "symlinking" of /data/media to either /sdcard or /emmc
Added sanitizing of device IDs for invalid characters (thanks to bigbiff)
Fixed free space calculation when switching backup devices on /data/media devices
Fixed a problem with using OpenRecoveryScript to create a backup without providing a backup name
DOWNLOAD:
The fastest and easiest way to install TWRP is to use the GooManager app:
Play Store Link
Direct Download
1) Install GooManager from the Play Store
2) Open GooManager and provide root permissions
3) Hit Menu (or the button with the 3 dots on your screen) and then Install OpenRecovery
OR:
You can find more information and download links on our website!
NOTE: If you're coming from another build of TWRP, you may need to go into settings and tap reset defaults to reset the storage paths so that you can see your zip files.
BUGS:
If you have found a bug, please consider posting it to our github issues log. It's pretty much impossible for us to keep up with the more than 30 threads that we have for the devices that we "directly" support. If you have a significant problem that cannot be answered in this thread, your best bet is to PM me directly, contact us via our website, or find us in our IRC channel below. If you see someone that's struggling, feel free to point it out to us. We need your help to help us keep track of all of our devices! Thanks!
SUPPORT:
Live support is available via #twrp on Freenode with your IRC client or just click this link.
thank you for this, ill test asap
if anyone wants a flashable zip, lemme know. i already have it done
edit: works good. only thing is i was flashing a rom (attempting to anyway) and somehow my zip got corrupted and unreadable. never had that happen before. any thoughts? (it was fine when i put it on my sd card, was flashing a 2nd time, so zip had worked previously and all other files on my sd are fine)
Going to flash this now and give it a try. Hopefully it works out good.
whoshotjr2006 said:
if anyone wants a flashable zip, lemme know. i already have it done
Click to expand...
Click to collapse
Throw it up brother!
thanks, always wanted a touch recovery and this one is great, if i could make a recovery touch it would be like this one again thanks
I flashed this a week or two ago and been working awesome! I love it.
i have been using cw recovery all time and always wanted to have a touch screen recovery and this one is sick, my only thing i have found is when i go to restore a backup it cannot find it,(one from cwm recovert). is it that it just cant restore those or did i miss something? no big deal to me ,just wanted to put it out there.
again thanks for this
they are in different folders on the SDCARD, im not even sure they are compatible.
ok cool im trying to do differant things and ill update you either way
would you know off hand where twrp folder would be? im looking if i get it before a reply ill post it
i got it twrp folder
alsp cani get the twrp 2220 in a zip format?
will this recovery work with firerats? on heroc?
dankdank11 said:
will this recovery work with firerats? on heroc?
Click to expand...
Click to collapse
Yes, Firerats has nothing to do with the recovery. Firerats just resizes your data/system/cache portion of the system really so you can install more apps.
I am using it and love it and works awesome on my Hero. :good:
thanks im trying it now, love the use of touch
I am going to leave the automated GooManager install for the Hero on version 2.2.2.0 due to the age of the device and the problems with recovery API 3 and older zips. TWRP 2.3.0.0 does work fine on the HeroC but I'm willing to bet that most zips are using old update binaries that will not install on the new version. If anyone wants to try, you're welcome to download and flash the newer versions manually:
http://techerrata.com/browse/twrp2/heroc
I was going to give 2.3.0.0 a try but like you stated, and someone in IRC said, that most of the zips online for the old Hero are prob all older so going to stick with 2.2.0.0 I think. Thanks for the update though.
Does TWRP require any particular hboot version, or will it function with any of them? I know you need to be on Android 2.3 in order to install TWRP, but I'm wondering... does it also mean that if you flash back to a stock ROM that TWRP won't work properly?
EDIT: My question was obviously stated with some knowledge missing. Recovery is obviously not dependent upon the ROM, as the ROM is loaded after the recovery program is done! But... I'm curious to know, if I made a nandroid backup with TWRP 2.2.2.0, will TWRP2 be able to restore it?
* DELETE *
There has been a small oversight with the GooManager route of distribution and the original post for this particular phone. You must have a PC or have a phone that can flash .zips or has a 2.3 or up ROM installed so it can run GooManager, even though this phones last OTA was Android 2.1, so it probably should have a .zip posted instead.
For example, I have a stock but rooted HTC Hero from Sprint as my backup with the latest OTA. So I can't use this method of install for this recovery without flashing a different recovery first, and then either flashing it as a .zip or upgrading my ROM to a 2.2 or 2.3 based ROM. In reality, I think most will just stick with whatever recovery must be flashed first in this situation as I will, even though I wanted TWRP. That said I think most of the users that use this will just want a .zip.
But there is no .zip posted for the guys that can flash it. This also makes it an overly cumbersome option if the handset is in stock state. As I said, I probably won't bother re-flashing, I kind of like sticking to one recovery on a phone and prefer to do minimal NAND writes.
DizturbedOne said:
There has been a small oversight with the GooManager route of distribution and the original post for this particular phone. You must have a PC or have a phone that can flash .zips or has a 2.3 or up ROM installed so it can run GooManager, even though this phones last OTA was Android 2.1, so it probably should have a .zip posted instead.
That said I think most of the users that use this will just want a .zip.
But there is no .zip posted for the guys that can flash it. This also makes it an overly cumbersome option if the handset is in stock state. As I said, I probably won't bother re-flashing, I kind of like sticking to one recovery on a phone and prefer to do minimal NAND writes.
Click to expand...
Click to collapse
As stated a couple of posts before you:
Dees_Troy said:
I am going to leave the automated GooManager install for the Hero on version 2.2.2.0 due to the age of the device and the problems with recovery API 3 and older zips. TWRP 2.3.0.0 does work fine on the HeroC but I'm willing to bet that most zips are using old update binaries that will not install on the new version. If anyone wants to try, you're welcome to download and flash the newer versions manually:
http://techerrata.com/browse/twrp2/heroc
Click to expand...
Click to collapse
Sent from my SCH-I535 using xda app-developers app
Hippie459MN said:
Yes, Firerats has nothing to do with the recovery. Firerats just resizes your data/system/cache portion of the system really so you can install more apps.
I am using it and love it and works awesome on my Hero. :good:
Click to expand...
Click to collapse
That's good to know. I think I'll give it a shot.
I am looking to try different rims for my HOX. I was wanting to know if I could download the roms I want to try and install each one then make a nandroid back up. So when I wanna switch I don't have to install each rom then I could just use the backup.
I'm currently running CleanRom 4.5. I am no expert at this. I have only rooted one other phone besides this, it was the Inspire.
Some roms I was planning on looking at were:
Viper
CM10
Nocturnal
CleanRom 5.0
Sorry if the grammar is bad. Sending this from my phone.
Yes, you can do that. Keep in mind you should wipe data before flashing different ROMs. So you need to re-setup each time. But you can still do what you stated in the OP.
NeverToLate said:
I am looking to try different rims for my HOX. I was wanting to know if I could download the roms I want to try and install each one then make a nandroid back up. So when I wanna switch I don't have to install each rom then I could just use the backup.
I'm currently running CleanRom 4.5. I am no expert at this. I have only rooted one other phone besides this, it was the Inspire.
Some roms I was planning on looking at were:
Viper
CM10
Nocturnal
CleanRom 5.0
Sorry if the grammar is bad. Sending this from my phone.
Click to expand...
Click to collapse
By all means go for it! I have a few tips for you, as one flasher to another
As redpoint said, each time you flash a new ROM you are starting from scratch. This only refers to your personal data and ROM settings, though. There are a few ways to guarantee that you won't be spending a long time configuring each ROM:
Cloud Storage is your friend! I personally use Dropbox to save anything important to my daily use since I can easily pull up documents stored there from anything connected to the internet. There are much more secure options to store files on the cloud, but you have to pay for the more secure options, and security is not of top importance to me (since I just store homework assignments and basic documents).
Use Google Backup! When you flash new android ROMs, there is a prompt that asks you if you would like to backup your phone to Google's servers. I usually hit yes to this prompt. After you have done this once, when you flash a new ROM and enter your Google account, any Play store apps you had installed will be redownloaded (including any personal data associated with the app, IF it's developer has enabled this feature). It's not a perfect way of restoring your apps, but it sure beats re-entering all of your data each time you want to try a new ROM.
Use services to store your contacts! I took a few days to enter ALL of my contacts into my Gmail account, and it was one of the best decisions I have ever made. Each time I restore my phone, I have all of my contacts available. People who complain about losing all of their contacts along with their phone need to learn about this point.
Remember that your SD card partition stays intact between ROMs! Just because you install a new OS doesn't mean you lose everything. Any music, movies, documents, or even app data that is stored on your SD card is unaffected by flashing something new. This is because your SD card is a completely separate partition of your phone's memory. The One XL may not have a real SD card slot, but you can still treat this partition as separate from the rest of your phone. Personal Tip: I store my backups and ROM zip files in a "Recovery" folder on my SD card partition. Having all of those files in one place simplifies flashing in TWRP.
Avoid using tools like Titanium Backup to restore apps! For a while I decided to use Titanium to restore apps. After a while I realized that all of the errors I was experiencing was the result of mismatched phone IDs, cache errors, and a bunch of other small glitches caused by Titanium backup. It is not the fault of TB and it is still a useful tool, but using Google backup to restore your apps is much cleaner and will result in fewer errors.
Save your text messages! Titanium Backup has the option of saving your text messages as a .xml file, but this is more complex than just using play store applications like SMS Backup & Restore. If you don't back up your SMS, you will look totally unpopular when you keep flashing your phone (and have no text messages at all)!
I hope this list helps you out in your flashing journey. Don't be afraid to try new things, and remember that if you can get into recovery mode, you will be fine (ESPECIALLY if you back up your data in the ways I described).
Thanks for tips
As far as saving everything as you posted. I don't have really that many documents I need and I am a big fan of dropbox haha. As far as my contacts any contacts I put in my phone automatically go to my google account so they always transfer over for me.
I usually delete most text messages at night and that's when I will flash these ROMS as I will not be texting anyone later in the night so, no worries there.
I really only have a few apps that I use, so even if they don't reinstall it doesn't take long to find em.
My main focus of now is just downloaded the roms I want and putting them all on my sd card. Whenever I have time to flash em all I will set them up kind of the way I want em with my apps, then set up the next ROM.
When that process is complete I'll just test each one for a few days/weeks till I find the perfect one for me haha.
I was planning on doing full wipe/reset between each one so I am glad yall confirmed that for me haha. Anything else I should keep an eye out for?
redpoint73 said:
Yes, you can do that. Keep in mind you should wipe data before flashing different ROMs. So you need to re-setup each time. But you can still do what you stated in the OP.
Click to expand...
Click to collapse
I don't have to do reset between nandroid backups do I?
NeverToLate said:
I was planning on doing full wipe/reset between each one so I am glad yall confirmed that for me haha. Anything else I should keep an eye out for?
Click to expand...
Click to collapse
Just two things - Most ROMs (especially AOSP) are constantly updating to newer versions, and if you are trying to make ONE snapshot of a ROM and flash back to it whenever you want, be sure that it is a stable version. CM10 and AOKP builds all have bugs, features tend to break each nightly/weekly build, and then get fixed later. Be sure you grab one of the stable builds or at least one that has all of the features you need (NOT necessarily the latest one), otherwise you will be relying on a (potentially) unstable ROM as your backup.
The other thing is, if you were potentially going to flash radio or kernel files, be sure to choose the correct one and flash it each time you install a new ROM or update. Each time you flash a ROM zip, the data for the kernel and radio are overwritten. Especially with radio files, you can break your phone or just cause general errors if you flash the wrong thing (example: flashing a radio+RIL zip on an AOSP ROM can cause serious errors, but the same file is actually preferred on Sense based ROMs). You don't have to worry about these files at all, but if you do end up flashing them, be careful!
NeverToLate said:
I don't have to do reset between nandroid backups do I?
Click to expand...
Click to collapse
Going between nandroids? No, recovery is going to overwrite the user data with the user data from the nandroid, so I don't think you need to worry about it.
---------- Post added at 04:25 PM ---------- Previous post was at 04:21 PM ----------
gridlock489 said:
Remember that your SD card partition stays intact between ROMs![/B] Just because you install a new OS doesn't mean you lose everything. Any music, movies, documents, or even app data that is stored on your SD card is unaffected by flashing something new. This is because your SD card is a completely separate partition of your phone's memory. The One XL may not have a real SD card slot, but you can still treat this partition as separate from the rest of your phone. Personal Tip: I store my backups and ROM zip files in a "Recovery" folder on my SD card partition. Having all of those files in one place simplifies flashing in TWRP.
Click to expand...
Click to collapse
In theory, that is supposed to be true. But many people (including myself) have had instances of some or all of the SD contents erased or corrupted. The exact cause has still not been found, but possibly just a bug of the phone. I've had it happen several times now. If you have anything irreplaceable on the SD, I would suggest backing it up to your computer, Dropbox, or whatever, before flashing anything. This includes photos of videos that you took, and anything else not easily replaced. Backing up one known good nandroid is not a bad idea, either, just in case.
gridlock489 said:
Just two things - Most ROMs (especially AOSP) are constantly updating to newer versions, and if you are trying to make ONE snapshot of a ROM and flash back to it whenever you want, be sure that it is a stable version. CM10 and AOKP builds all have bugs, features tend to break each nightly/weekly build, and then get fixed later. Be sure you grab one of the stable builds or at least one that has all of the features you need (NOT necessarily the latest one), otherwise you will be relying on a (potentially) unstable ROM as your backup.
The other thing is, if you were potentially going to flash radio or kernel files, be sure to choose the correct one and flash it each time you install a new ROM or update. Each time you flash a ROM zip, the data for the kernel and radio are overwritten. Especially with radio files, you can break your phone or just cause general errors if you flash the wrong thing (example: flashing a radio+RIL zip on an AOSP ROM can cause serious errors, but the same file is actually preferred on Sense based ROMs). You don't have to worry about these files at all, but if you do end up flashing them, be careful!
Click to expand...
Click to collapse
I don't plan on flashing any radios. As I did with the inspire, and it messed up my service bad and I didn't know how to fix it again. I didn't now too much about it then. Which I still don't but I know more now than I did then.
NeverToLate said:
Anything else I should keep an eye out for?
Click to expand...
Click to collapse
Be sure you are using TWRP, and not Clockworkmod. CWM has known problems, as our device is not really supported (its just a port) and also USB mount is not working (which may be relevant if you run into problems such as the SD corruption I've mentioned).
I will be using TWRP. If I'm not mistaken I did a nandroid back up of stock rooted. I plan on copying my sd card to my computer external hd just for safety. I have a HTC One X Folder that I will put my roms in stuff in as well.
I will try to take screenshots of battery life for each day I use a certain rom. The battery probably won't go below 30% but screenshots would give a good idea to other people. And I will try to update my thoughts on each rom. Not promising I will get to but I will try.
I am going to download and check md5s today.
Idk if I will flash one tonight or not.
Also I may try to have a nandroid back up of the same rom if it has Sense and a non-Sense version. I have never tried a non Sense rom so I am really trying to figure out what I like best.
NeverToLate said:
Also I may try to have a nandroid back up of the same rom if it has Sense and a non-Sense version. I have never tried a non Sense rom so I am really trying to figure out what I like best.
Click to expand...
Click to collapse
I hope you like blue If not, take a look at this thread for some CM10 themes.
Any ROM based on Sense will still have remnants of HTC's UI somewhere. When there are deSensed versions (such as CleanROM V), usually the dev is trying to get closer to the stock Android look. I personally either go all the way and flash an AOSP ROM, or stay with stock Sense, because anywhere inbetween usually lacks polish and continuity. I'm exceptionally picky though
gridlock489 said:
I hope you like blue If not, take a look at this thread for some CM10 themes.
Any ROM based on Sense will still have remnants of HTC's UI somewhere. When there are deSensed versions (such as CleanROM V), usually the dev is trying to get closer to the stock Android look. I personally either go all the way and flash an AOSP ROM, or stay with stock Sense, because anywhere inbetween usually lacks polish and continuity. I'm exceptionally picky though
Click to expand...
Click to collapse
Blue is actually my favorite color lol. Could you point me to the CM10 rom?
Here are the roms I am downloading as of now:
KingCobra
Nocturnal Special Edition
Viper
Clean Rom 5.0
Any other ideas on maybe one or two more roms?
I bookmarked that link you posted. I prob won't do much with themes until I find the right ROM. Even then the most I usually do is wallpapers lol. But will look more into after finding a ROM.
What rom would you suggest on CM or AOKP? What build? I don't know much about those. Never really looked in the original development forum lol.
NeverToLate said:
What rom would you suggest on CM or AOKP? What build? I don't know much about those. Never really looked in the original development forum lol.
Click to expand...
Click to collapse
I just flashed the latest build (cm-10-20121001-EXPERIMENTAL-evita.zip) a few hours ago and it has been just fine with me, very smooth with no crashes so far. You can download the nightly builds here, but like I said earlier not all of them are stable. CM10 is developed for multiple devices with different hardware. Our One XL is code named "evita", so before you flash ANYTHING be sure that it has "evita" in the file name. Be sure to look at the development thread, or at least the OP, if you want to get more information.
As for AOKP, it seems like build 4 (the latest) may be having some issues. I don't use that ROM so check out the dev thread if you need help.
gridlock489 said:
I just flashed the latest build (cm-10-20121001-EXPERIMENTAL-evita.zip) a few hours ago and it has been just fine with me, very smooth with no crashes so far. You can download the nightly builds here, but like I said earlier not all of them are stable. CM10 is developed for multiple devices with different hardware. Our One XL is code named "evita", so before you flash ANYTHING be sure that it has "evita" in the file name. Be sure to look at the development thread, or at least the OP, if you want to get more information.
As for AOKP, it seems like build 4 (the latest) may be having some issues. I don't use that ROM so check out the dev thread if you need help.
Click to expand...
Click to collapse
What's the different in the Nightly and Experimental? I would like to try a CM since I never have before. Probably will be the last one I download
Also on the CM10 forum it says something about find Gapps? Is that something I search for and download and flash?
Update
Downloaded Roms with md5 checked and now on my sim card:
Clean Rom 5.0
CM10
King Cobra
Nocturnal Special Edition
Viper
Just need help on what I need to download for Gapps to install CM10
What Rom should I test first?
King Cobra
Viper
Nocturnal
I'm on nocturnal and loving it.
Sent from my HTC One X using xda premium
Hi,
I am new this this whole Samsung Galaxy S3 customization. Yesterday, I took the big risk of getting my phone bricked and successfully rooted my phone. Now, I am interested in installing some interesting ROMs and uninstall some uninteresting bloatware. However, I do not know where and how to start.
Just a quick note. I have followed [GUIDE] Root for Jelly Bean 4.1.1 or 4.1.2 OTA ***UPDATED 3/5*** to customize my phone, using ClockworkMod Touch Recovery 6.0.2.3 and MD5: 8C3DA18BD5DEF7E38E03DD147A0E10A1 for VRBMB1 (Jelly Bean 4.1.2). My phone's Model Number is SCH-I535, Android Version 4.1.2.
The first thing I want to do is to reformat my phone. By that, I mean improving the battery life, speed, and practically everything else related to those two things I just said. I have read somewhere that custom ROMs can improve battery life, as well as make everything in the phone move faster and smoother. A few ROMs have caught my attention, but I am unsure of which ROM to use. I have also noticed that you can change the battery preferences without the need of a ROM, but nevertheless, a custom ROM couldn't hurt. Plus, I really want to change the theme of my phone, specifically replacing them with [OMG][THEME] 03.21 - Ultimate OMG Theme - 35 Choices - Aroma - CleanROM/Stock.
So the first question is, which is the most preferred ROM to use for my phone? (Or better yet, do I even need a custom ROM?) So far, my main goal is to improve the speed and battery life. But I have noticed that you must factory reset your phone. That is a little discouraging as there are many personal things in my phone that I would love to keep. I do have Titanium Backup, however, I am unsure of how to use it. Is there a guide on how to use Titanium Backup? I am also concerned that a factory reset can and will clear everything in Titanium Backup as well. The next thing is, I am using Next Launcher by Go Developers. I really enjoy the launcher and would like to continue using it. Will I still be able to use the launcher in custom ROMs?
Thank you for your help!
Zarotu said:
Hi,
I am new this this whole Samsung Galaxy S3 customization. Yesterday, I took the big risk of getting my phone bricked and successfully rooted my phone. Now, I am interested in installing some interesting ROMs and uninstall some uninteresting bloatware. However, I do not know where and how to start.
Just a quick note. I have followed [GUIDE] Root for Jelly Bean 4.1.1 or 4.1.2 OTA ***UPDATED 3/5*** to customize my phone, using ClockworkMod Touch Recovery 6.0.2.3 and MD5: 8C3DA18BD5DEF7E38E03DD147A0E10A1 for VRBMB1 (Jelly Bean 4.1.2). My phone's Model Number is SCH-I535, Android Version 4.1.2.
The first thing I want to do is to reformat my phone. By that, I mean improving the battery life, speed, and practically everything else related to those two things I just said. I have read somewhere that custom ROMs can improve battery life, as well as make everything in the phone move faster and smoother. A few ROMs have caught my attention, but I am unsure of which ROM to use. I have also noticed that you can change the battery preferences without the need of a ROM, but nevertheless, a custom ROM couldn't hurt. Plus, I really want to change the theme of my phone, specifically replacing them with [OMG][THEME] 03.21 - Ultimate OMG Theme - 35 Choices - Aroma - CleanROM/Stock.
So the first question is, which is the most preferred ROM to use for my phone? (Or better yet, do I even need a custom ROM?) So far, my main goal is to improve the speed and battery life. But I have noticed that you must factory reset your phone. That is a little discouraging as there are many personal things in my phone that I would love to keep. I do have Titanium Backup, however, I am unsure of how to use it. Is there a guide on how to use Titanium Backup? I am also concerned that a factory reset can and will clear everything in Titanium Backup as well. The next thing is, I am using Next Launcher by Go Developers. I really enjoy the launcher and would like to continue using it. Will I still be able to use the launcher in custom ROMs?
Thank you for your help!
Click to expand...
Click to collapse
You don't have to flash a custom ROM to improve battery just a custom kernel. There are a lot of custom tweaks that the developers put in their ROMs to further improve the ROM some you can put yourself. As for the themes the stock ROM has to be deodexed in order for the themes to work. Lastly Next launcher is an app and the last time I checked all launcher apps work on rooted phones.
jmxc23 said:
You don't have to flash a custom ROM to improve battery just a custom kernel. There are a lot of custom tweaks that the developers put in their ROMs to further improve the ROM some you can put yourself. As for the themes the stock ROM has to be deodexed in order for the themes to work. Lastly Next launcher is an app and the last time I checked all launcher apps work on rooted phones.
Click to expand...
Click to collapse
Thank you for the reply. Seeing how it is, where can I find custom kernels and/or a guide on how to install and use a custom kernel on my phone? I do not quite understand what you mean when "the stock ROM has to be deodexed in order for the themes to work." Lets say I am interested in one of those custom theme, does that mean I have to personally deodex the ROMs or can I just follow the instructions stated in the main thread? So far I do not have a custom ROM after rooting my phone. Everything is still the same since I did the last step, which was to flash the Jelly Bean Bootchain.
Edit: Is there a thread I can look at find to get more information on how to prepare my phone for theming and modding? Information such as deodexing my phone, and other preparation information. I can't seem to find a good thread.
Zarotu said:
Thank you for the reply. Seeing how it is, where can I find custom kernels and/or a guide on how to install and use a custom kernel on my phone? I do not quite understand what you mean when "the stock ROM has to be deodexed in order for the themes to work." Lets say I am interested in one of those custom theme, does that mean I have to personally deodex the ROMs or can I just follow the instructions stated in the main thread? So far I do not have a custom ROM after rooting my phone. Everything is still the same since I did the last step, which was to flash the Jelly Bean Bootchain.
Click to expand...
Click to collapse
In the original android development is where you will find the kernels. Most of the kernel threads will provide links and the information you need. If you are planning on flashing KT747 kernel here is some additional information: http://forum.xda-developers.com/showthread.php?t=2144004
Whoa, hold up on the custom kernels and custom rom stuff.
1. You need to make a back up with either twrp or cwm. Next put your important files on your external sd including your efi. Idk if titanium backup allows you to store app back ups on the external sd or not but I assume it does (I use a diff app). You don't have to format your internal sd to flash a custom rom, you have to format the system partition.
Take a minute to make sure you have the prerequisites before moding your phone more. You cannot possibly want to be doing all this so soon especially if you just got into this yesterday.
2. Your still on a stock rom, which is odexed. If you want to customize your rom you need to be on a deodexed rom most of the time. This is a the simple abbreviated difference between odexed and deodexed.
3. Luke took on Vader, even though he was a new rookie padawan. He didnt have a good grip on what he was doing, and karma took his hand and slapped him in the face with irony for it. You might find yourself falling a deep hole of problems if you don't read up more on what you're doing. Do yourself a favor and stay on the god damn dagobah system awhile.
One final thing I have to say is do some research it will help you a lot.
Well, if you want the pure AOSP feel with a CM base, yet uber customization and tweakability I would go with paranoidkangdroid. It mixes CM as a base, with AOKP and ParanoidAndroid. This is what I use and I love it. Cleanrom is a touchwiz rom and I personally feel that while TW roms are stable and usually butter, they are all missing some aspects of customization. Link to the rom: http://forum.xda-developers.com/showthread.php?t=2186838. However that's my opinion. I prefer the clean stock google experience, others may not. Happy flashing
EDIT: before you go flash anything make sure you do the following: (in this order)
1. Root device
2. Unlock the bootloader
3. Install TWRP (or CWM, I like TWRP)
4. Make a backup of the current stock rom
5. Take all the things you want to save (pictures) and back them up to your computer.
6. DO NOT UNDER ANY CIRCUMSTANCES TRY TO INSTALL A ROM MADE FOR THE INTERNATIONAL, AT&T, NOTE2, etc. You will brick your phone. Stick to the Verizon variant thread and you should be fine. If getting the rom from another website, make sure it is made for SCH-I535 or D2VZW.
nrock2256 said:
Well, if you want the pure AOSP feel with a CM base, yet uber customization and tweakability I would go with paranoidkangdroid. It mixes CM as a base, with AOKP and ParanoidAndroid. This is what I use and I love it. Cleanrom is a touchwiz rom and I personally feel that while TW roms are stable and usually butter, they are all missing some aspects of customization. Link to the rom: http://forum.xda-developers.com/showthread.php?t=2186838. However that's my opinion. I prefer the clean stock google experience, others may not. Happy flashing
EDIT: before you go flash anything make sure you do the following: (in this order)
1. Root device
2. Unlock the bootloader
3. Install TWRP (or CWM, I like TWRP)
4. Make a backup of the current stock rom
5. Take all the things you want to save (pictures) and back them up to your computer.
6. DO NOT UNDER ANY CIRCUMSTANCES TRY TO INSTALL A ROM MADE FOR THE INTERNATIONAL, AT&T, NOTE2, etc. You will brick your phone. Stick to the Verizon variant thread and you should be fine. If getting the rom from another website, make sure it is made for SCH-I535 or D2VZW.
Click to expand...
Click to collapse
Ok he is a newbie in this so pretty much AOSP especially those are a little bit advance for him.
jmxc23 said:
Ok he is a newbie in this so pretty much AOSP especially those are a little bit advance for him.
Click to expand...
Click to collapse
Haha! Seeing how there is so much to know before I can get started on anything, I believe I will be needing to do more research. So first thing's first. If all I did was root my phone, using the clockwork recovery mod, what should be my next move? Where do I go from here? I have been searching, but have not yet found a guide. How do I backup my stuff in clockwork recovery mod? What do I do if I do not have an external SD card? Haha, I didn't think customizing your phone would be this difficult.
Thank you.
Zarotu said:
Haha! Seeing how there is so much to know before I can get started on anything, I believe I will be needing to do more research. So first thing's first. If all I did was root my phone, using the clockwork recovery mod, what should be my next move? Where do I go from here? I have been searching, but have not yet found a guide. How do I backup my stuff in clockwork recovery mod? What do I do if I do not have an external SD card? Haha, I didn't think customizing your phone would be this difficult.
Thank you.
Click to expand...
Click to collapse
It is more confusing than it is difficult.
Essentially your next move is preparing yourself incase you fail flashing a rom. You need to do the following:
1. Get a micro sdcard, atleast 16gb
2. Make a back up on the external sd you acquired in step 1 above. This can be done from cwm by selecting "Back up and restore" from the menu, followed by selecting the back up option that says back up to external sd.
3. Now download the rom you want on to your external sd card. Find out if the rom requires gapps or any other supplemental downloads and put them on the external sd as well.
4. Next, report back here for further instructions.
(I havent used cwm for a while so the instructions I gave there are from memory, double check on that)
Surge1223
Surge1223 said:
Essentially your next move is preparing yourself incase you fail flashing a rom. You need to do the following:
1. Get a micro sdcard, atleast 16gb
2. Make a back up on the external sd you acquired in step 1 above. This can be done from cwm by selecting "Back up and restore" from the menu, followed by selecting the back up option that says back up to external sd.
3. Now download the rom you want on to your external sd card. Find out if the rom requires gapps or any other supplemental downloads and put them on the external sd as well.
4. Next, report back here for further instructions.
(I havent used cwm for a while so the instructions I gave there are from memory, double check on that)
Surge1223
Click to expand...
Click to collapse
Okay what if the person doesn't have the money as of now to purchase an sd card? Are there other ways to back up their data?
Sure you can back it up on your internal sd card, but generally you would only do that if you were very familiar with how your recovery works and know exactly what you were doing. Most of the time that means you've had previous experience with the rom your flashing and/or arent too woried about your stuff getting deleted. Usually its a good idea to keep a flashable zip of a deodexed stock rom, radio, recovery, bootchain, etc. In the internal if your doing that but since he's just starting out I wouldn't do that and I usually dont anyways. Its risky and not worth losing your stuff when you could just spend a couple bucks and get a external micro sd.
Surge1223
Surge1223 said:
Sure you can back it up on your internal sd card, but generally you would only do that if you were very familiar with how your recovery works and know exactly what you were doing. Most of the time that means you've had previous experience with the rom your flashing and/or arent too woried about your stuff getting deleted. Usually its a good idea to keep a flashable zip of a deodexed stock rom, radio, recovery, bootchain, etc. In the internal if your doing that but since he's just starting out I wouldn't do that and I usually dont anyways. Its risky and not worth losing your stuff when you could just spend a couple bucks and get a external micro sd.
Surge1223
Click to expand...
Click to collapse
Micro SD price range from $5-$100 retail when not on sale and the retail price depends on the storage size. So if the person is hard on cash or has more important things to spend their money she/he might not be able to buy the micro sd with the couple of bucks that you said it cost. The reason I asked those questions is that not everyone has a couple of dollars to spare on a micro sd card so all possible ways to back up data should be mentioned not just what you or I think is the best thing to do. For instance I have my data backed up on my computer via external hard drive as well as Google drive, box and Dropbox. I also use Carbon instead of the titanium backup app that everyone suggests to use. So they can use their computer, cloud storage service, external hard drive, micro sd cards and apps to backup their data.
Its not a matter of whether its possible or not, I mean yeah you can also make a system image of your pc using DVD's instead of a portable hdd or flash drive. I can understand people may be short on cash, but if you have enough time and money to root your phone, pay for a data plan, subscribe to the internet, you can budget 5 dollars. Hell, you could even start using bing rewards to get yourself a 5$ Amazon credit.
All I am saying mainly is that there are more ways to back up your data besides micro sd cards and that all people new to rooting should know more then one way as something can go wrong your micro sd card so your data should be backed up in other ways to insure that you can restore your data.
I hear ya, I guess I just think because I learned my own how to use other methods I assumed that as people got more familiar with flashing roms, etc, that they'd learn eventually too. But hey to each his own. IMO, the external sd is the easiest, fastest, and most reliable way so in this case, I think we should leave well enough alone.
Surge1223