Related
Dear reader,
I've currently been using Cyanomod for 2.3.7 Gingerbread.
My phone is rooted and everything (which took a little while )
Everything is running perfectly fine, but i would like to update my phone to android 4.0+ (whatever the lastest compatible version might be)
How should i go about this?
Do i basically uninstall everything and start from scratch or is there an easy method to quickly update my phone to android 4.
Kind Regards and Thank you for your time!
I believe the answer us first to backup your apps with titanium backup if you need them. Then go to recovery and backup your current Rom. (always be sure to do this). from recovery wipe factory reset and dalvik cache. Then install your new Rom from zip.
You cannot install an android 4.0 + over another version. Always backup and wipe.
Sent from my HTC One X using xda app-developers app
TJ007 said:
I believe the answer us first to backup your apps with titanium backup if you need them. Then go to recovery and backup your current Rom. (always be sure to do this). from recovery wipe factory reset and dalvik cache. Then install your new Rom from zip.
You cannot install an android 4.0 + over another version. Always backup and wipe.
Sent from my HTC One X using xda app-developers app
Click to expand...
Click to collapse
Do i need to re-root my phone when i install a new Rom? Or should i just install it through recovery?
Rom's are pre rooted (expect stock, stock BASED roms ARE pre-rooted), once you've installed the rom through cwm, it will be rooted and ready.
cashtecz said:
Dear reader,
Do i basically uninstall everything and start from scratch or is there an easy method to quickly update my phone to android 4.
Kind Regards and Thank you for your time!
Click to expand...
Click to collapse
If your bootloader is unlocked, you can easily flash a custom kernel (Based on ics, so it'll be compatible with ics rom) And boot into recovery, and flash a custom rom based on ics.
One last question, since i'm having trouble finding compatible roms.
Which one would any of you, recommend for me to use ?
I have a ST18i and i'd like the lastest compatible rom.
Thanks so much for the fast reponses and ofcourse the help.
Kind Regards,
Since you're using CyanogenMod 7 I would recommend you to use CyanogenMod 9.1 i.e. FXP 138 is the best in my experience.
Sent from my ST18i using xda app-developers app
mikii100297 said:
If your bootloader is unlocked, you can easily flash a custom kernel (Based on ics, so it'll be compatible with ics rom) And boot into recovery, and flash a custom rom based on ics.
Click to expand...
Click to collapse
cashtecz said:
One last question, since i'm having trouble finding compatible roms.
Which one would any of you, recommend for me to use ?
I have a ST18i and i'd like the lastest compatible rom.
Thanks so much for the fast reponses and ofcourse the help.
Kind Regards,
Click to expand...
Click to collapse
If your finding trouble with compatible roms are you saying your getting bootloops when trying them?, because a different Android Version requires a different kernel, So if you haven't or forget to flash the kernel recommended or provided then that would possibly be where your compatibility issues lye as you will get bootloops if you don't and you are changing version. As Mikii suggested earlier.
nh1402 said:
If your finding trouble with compatible roms are you saying your getting bootloops when trying them?, because a different Android Version requires a different kernel, So if you haven't or forget to flash the kernel recommended or provided then that would possibly be where your compatibility issues lye as you will get bootloops if you don't and you are changing version. As Mikii suggested earlier.
Click to expand...
Click to collapse
Ahhh that must be it then.. I've been using the same kernel for quite some time now because it was quite a hassle to flash it. Different roms come with different kernels (at times). I'll have to figure out how to flash kernels again. Gonna check around the forums to see if i can find a suitable thread.
Thanks so much
sarangkunte05 said:
Since you're using CyanogenMod 7 I would recommend you to use CyanogenMod 9.1 i.e. FXP 138 is the best in my experience.
Sent from my ST18i using xda app-developers app
Click to expand...
Click to collapse
When i look up Cyano 9.1 FXP 138, i get a list of downloads. FXP138-cm-9-20120916-UNOFFICIAL-haida.zip , FXP138-cm-9-20120916-UNOFFICIAL-mango.zip
What exactly are they and which one should i go for?
cashtecz said:
Ahhh that must be it then.. I've been using the same kernel for quite some time now because it was quite a hassle to flash it. Different roms come with different kernels (at times). I'll have to figure out how to flash kernels again. Gonna check around the forums to see if i can find a suitable thread.
Thanks so much
Click to expand...
Click to collapse
The fastest way to flash a kernel is to use the program called flashtool, click on the lightening bolt, select Fastboot mode, then select kernel to flash find the kernel you want to flash and it should be done within literally 2 seconds. once Flashtool gives you the all clear, disconnect your phone from usb, restart phone, and there you go, the old kernel will be overwritten, and so will that kernel's cwm version, with the one from the new kernel.
Try FXP138
cashtecz said:
One last question, since i'm having trouble finding compatible roms.
Which one would any of you, recommend for me to use ?
I have a ST18i and i'd like the lastest compatible rom.
Thanks so much for the fast reponses and ofcourse the help.
Kind Regards,
Click to expand...
Click to collapse
i would also suggest you to try FXP138 which is CM9.1 Android 4.0.4, Its pretty smooth and the brightness bug seems to be resolved:laugh: in FXP138 here's the link http://forum.xda-developers.com/showthread.php?t=1409053
Also here is a link for ROM comparison - http://forum.xda-developers.com/showthread.php?t=1843741
Hope this helps!
FXP138-cm-9-20120916-UNOFFICIAL-urushi
cashtecz said:
When i look up Cyano 9.1 FXP 138, i get a list of downloads. FXP138-cm-9-20120916-UNOFFICIAL-haida.zip , FXP138-cm-9-20120916-UNOFFICIAL-mango.zip
What exactly are they and which one should i go for?
Click to expand...
Click to collapse
1. http://ul.to/f/zwx5le
2. choose and download FXP138-cm-9-20120916-UNOFFICIAL-urushi.zip
3. Flash the kernal inside above archive.(using fastboot mode.)
4. Enjoy.....:good:
Note:
urushi is the modder for Xperia ray(ST18i)
ramakrishnanjk said:
1. http://ul.to/f/zwx5le
2. choose and download FXP138-cm-9-20120916-UNOFFICIAL-urushi.zip
3. Flash the kernal inside above archive.(using fastboot mode.)
4. Enjoy.....:good:
Note:
urushi is the modder for Xperia ray(ST18i)
Click to expand...
Click to collapse
Nevermind, i figured it out!
cashtecz said:
Nevermind, i figured it out!
Click to expand...
Click to collapse
Hey,
Everything is installed and running, however i am wondering about just one thing.
Whenever i reboot my phone i get, right after imputting my sim code, a Unlock Network SIM message.
What is this and how can i solve it?
Regards,
(oops just realized i made a double post, apologies!)
Hey there,
I've been using Cyanogen mod 10 for about a year now (actually probably 10 for 6 months and then moved to 10.1 as soon as it came out). But just today I decided to update to the latest version of the OS through cyanogens update feature on the phone. I was updating to 10.2 FROM 10.1, but I didn't realise the latest version was 10.2 until I checked after. Now my phone restarts by itself every 20 mins and my 3G is doing weird things :/
But the main problem is that I CAN'T boot to recovery mode anymore! I don't know why?! If I could, then I could fix everything :/
Any help would be much appreciated thanks. I can provide any further details if needed. I hope to get this fixed soon as I use it quite a lot! xD
Obviously broke recovery. You could try flashing an Odin version of a custom kernel, but this may not work (might as well try it tho). If it were me I'd go back to stock via Odin, re-root & restore nandroid backup or reflash rom/kernel & start again from scratch (tho I wouldn't need to do this because I make regular nandroids).
Personally speaking, I wouldn't use that update from the phone feature in future. Flash updates/nightlies from recovery. Takes a few extra minutes, but saves you a lot of grief.
MistahBungle said:
Obviously broke recovery. You could try flashing an Odin version of a custom kernel, but this may not work (might as well try it tho). If it were me I'd go back to stock via Odin, re-root & restore nandroid backup or reflash rom/kernel & start again from scratch (tho I wouldn't need to do this because I make regular nandroids).
Personally speaking, I wouldn't use that update from the phone feature in future. Flash updates/nightlies from recovery. Takes a few extra minutes, but saves you a lot of grief.
Click to expand...
Click to collapse
Thanks for the quick reply and tip! For now on I will definitely install from recovery only.
I tried reflashing the Clockwork recovery thing but it didn't seem to fix it.
So I was thinking about flashing the Siyah kernel? Is this a good idea? I flash just the PDA file only right?
Sorry for not knowing much about this flashing stuff xD
Yeah, you might as well try the Odin version of Siyah even tho it probably won't work. Can't hurt put it that way. Yep, flash it in the PDA section of Odin. If that doesn't work flash a stock rom with Odin as I mentioned (also in the PDA section). If you get stuck, look for Hopper8's 'Odin won't flash' thread.
MistahBungle said:
Yeah, you might as well try the Odin version of Siyah even tho it probably won't work. Can't hurt put it that way. Yep, flash it in the PDA section of Odin. If that doesn't work flash a stock rom with Odin as I mentioned (also in the PDA section). If you get stuck, look for Hopper8's 'Odin won't flash' thread.
Click to expand...
Click to collapse
Ok I tried flashing Siyah and didn't work :/ Ok I will give flashing a stock rom a try. I presume that puts it back to the way it is? Then I have to re root etc?
Thanks!
Yep.
MistahBungle said:
Yep.
Click to expand...
Click to collapse
Reflashed to a pre-release version of JB from Samsung Thanks heaps for your help! Appreciate it. Will probably go back to Cyanogen tomorrow.
One question though. Is Cyanogen 10.1 supposed to be quite stuttery? I know it's a nightly build and all. But using this official pre-release from Samsung, it's JUST SOOOOO MUCH MORE SMOOTHER! But I expect Cyanogen to be a lot faster :/ Maybe my kernel was just having problems the whole time?
Thanks!
Good man Can't comment on CM10 as I've never used it, used CM9 for ages & got fed up with various things not working as they should/being flaky & have never bothered with CM10 as a result, I'm sure someone else will be able to answer those queries.
I'm guessing you flashed the 0824 nightly of 10.2. According to the discussion thread, anybody who uses this nightly will experience the broken recovery....they've posted a link to a kernel + recovery which needs to be flashed before the phone is rebooted for the first time in order to replace the broken recovery. Concerning the stability of the ROMs.........
10.2.....IMO...NOT stable enough for daily use....
10.1.....fast and smooth, and no bugs that make me want to stop using it.......
10.0.....not as fast as 10.1 but just as smooth but with the same lack of noticeable bugs as 10.1.....
JB Firmware.....obviously the most stable, but simply not as fast.....even if rooted and debloated......
Back to 10.1 for now.....
keithross39 said:
I'm guessing you flashed the 0824 nightly of 10.2. According to the discussion thread, anybody who uses this nightly will experience the broken recovery....they've posted a link to a kernel + recovery which needs to be flashed before the phone is rebooted for the first time in order to replace the broken recovery. Concerning the stability of the ROMs.........
10.2.....IMO...NOT stable enough for daily use....
10.1.....fast and smooth, and no bugs that make me want to stop using it.......
10.0.....not as fast as 10.1 but just as smooth but with the same lack of noticeable bugs as 10.1.....
JB Firmware.....obviously the most stable, but simply not as fast.....even if rooted and debloated......
Back to 10.1 for now.....
Click to expand...
Click to collapse
Sorry about the late reply.
Yes that was the exact build! xD
Oh well I am actually quite happy with the official JB firmware from Samsung atm. It's A LOT SMOOTHER than 10.1 for some reason :/ I don't know why. Just is. I had lots of problems with 10.1. At times the RAM seemed to leak so much I would have to restart it otherwise it would just be so stuttery. ESPECIALLY with Swift Keyboard and Facebook heads xD It's ashame because I really liked Cyanogen. Missed some of the features.
My phone just gets stuck in a black screen when I try to boot into recovery. It happend once a few days ago, and i soloved it by going again to stock by odin and rooting it again. It booted to recovery the first time, i flashed carbon rom nightly 26 and now when I try to update, it doenst boot again. What is happening?
Info+New Kernel/Recovery
francantabria said:
My phone just gets stuck in a black screen when I try to boot into recovery. It happend once a few days ago, and i soloved it by going again to stock by odin and rooting it again. It booted to recovery the first time, i flashed carbon rom nightly 26 and now when I try to update, it doenst boot again. What is happening?
Click to expand...
Click to collapse
Firstly: Please give more detailed information (which kernel do you use, which ROM did you use before the problem occurred?)
Secondly: It is possible that you can't acess recovery mode anymore when flashing new updates. Happens with CM 10.2 OTA Update right now. The solution would be to flash a new recovery using Heimdall (Open-Source ODIN alternative) [Didn't try that, but should theoretically work] or, mor simple, a new kernel. Dorimany v9.34 is suited perfectly for that. Download here: http://dorimanx.shine.sk/ .
H3llwar said:
Firstly: Please give more detailed information (which kernel do you use, which ROM did you use before the problem occurred
Secondly: It is possible that you can't acess recovery mode anymore when flashing new updates. Happens with CM 10.2 OTA Update right now. The solution would be to flash a new recovery using Heimdall (Open-Source ODIN alternative) [Didn't try that, but should theoretically work] or, mor simple, a new kernel. Dorimany v9.34 is suited perfectly for that. Download here: http://dorimanx.shine.sk/ .
Click to expand...
Click to collapse
Well, i used Carbon Rom for a few weeks, so that was definitly the rom. Talking about the kernel, I dont even know how to install one.. haha Now in kernel version it says..
3.0.64 CM gb07657a
[email protected] #1 (I dont know what kernel it is)
Yeah but even if I dont want to flash an update, just boot recovery, I cant. Have you any link to know about Heimdall? Or how to install Dorimany? Im a beginner I have to say.
Thanks
francantabria said:
Well, i used Carbon Rom for a few weeks, so that was definitly the rom. Talking about the kernel, I dont even know how to install one.. haha Now in kernel version it says..
3.0.64 CM gb07657a
[email protected] #1 (I dont know what kernel it is)
Yeah but even if I dont want to flash an update, just boot recovery, I cant. Have you any link to know about Heimdall? Or how to install Dorimany? Im a beginner I have to say.
Thanks
Click to expand...
Click to collapse
You installed a Kernel while rooting your phone: Its the .tar that you have to put into the PDA section in ODIN. There are Kernels with .tar and .zip: .tar files are only flashable using Odin while .zip files are flashed using the recovery just like you flash ROMs. I guess your Kernel is a custom CM Kernel (CM for Cyanogen Mod). Carbon ROM is probably based on CM. There is currently no other workaround to get your recovery back then flashing a new kernel/recovery. I am currently working on an easy workaround for this problem, but it will take a while.
Dorimanx is downloadable here http://dorimanx.shine.sk/ and should be compatible: Just flash it like you did when rooting your phone in the beginning, just with Dorimanx .tar in PDA. Recovery should work again afterwards.
My mistake: It's Dorimanx, not Dorimany
Hit Thanks and just ask if you need additional help!
H3llwar said:
You installed a Kernel while rooting your phone: Its the .tar that you have to put into the PDA section in ODIN. There are Kernels with .tar and .zip: .tar files are only flashable using Odin while .zip files are flashed using the recovery just like you flash ROMs. I guess your Kernel is a custom CM Kernel (CM for Cyanogen Mod). Carbon ROM is probably based on CM. There is currently no other workaround to get your recovery back then flashing a new kernel/recovery. I am currently working on an easy workaround for this problem, but it will take a while.
Dorimanx is downloadable here http://dorimanx.shine.sk/ and should be compatible: Just flash it like you did when rooting your phone in the beginning, just with Dorimanx .tar in PDA. Recovery should work again afterwards.
My mistake: It's Dorimanx, not Dorimany
Hit Thanks and just ask if you need additional help!
Click to expand...
Click to collapse
Yeah, I remember.. it was siyah kernel.
So in your opinion I should flash Dorimanx by Odin then? No other way to fix isnt it? and.. in dorimanx page, which one of all them should I download?
francantabria said:
Yeah, I remember.. it was siyah kernel.
So in your opinion I should flash Dorimanx by Odin then? No other way to fix isnt it? and.. in dorimanx page, which one of all them should I download?
Click to expand...
Click to collapse
1. Yes you should
2. Not right now, maybe in the future, flashing recovery.img using Heimdall would probably help, but I didn't try it myself and using Heimdall is quite complex
3. In General: The newest .tar (9.34/8.34) as you can't use .zip files
When you want to use Stock Samsung ROM: Version 8
When you want to use CM/AOKP based ROM: Version 9
Remember: No ICS Support!
Hit Thanks and just ask if you need more help.
H3llwar said:
1. Yes you should
2. Not right now, maybe in the future, flashing recovery.img using Heimdall would probably help, but I didn't try it myself and using Heimdall is quite complex
3. In General: The newest .tar (9.34/8.34) as you can't use .zip files
When you want to use Stock Samsung ROM: Version 8
When you want to use CM/AOKP based ROM: Version 9
Remember: No ICS Support!
Hit Thanks and just ask if you need more help.
Click to expand...
Click to collapse
Ok.
But every aosp rom, like Carbon PA and these are based either in AOKP or CM, isnt it?
The newest one is 9/39, is that the one?
francantabria said:
Ok.
But every aosp rom, like Carbon PA and these are based either in AOKP or CM, isnt it?
Click to expand...
Click to collapse
CM & AOKP are actually based on AOSP, so Yes, every AOSP ROM should work.
H3llwar said:
CM & AOKP are actually based on AOSP, so Yes, every AOSP ROM should work.
Click to expand...
Click to collapse
I did what you said and after installing Carbon Rom again recovery is gone.. so I suposse it is Carbon problem. I will do it again and install a different rom
francantabria said:
I did what you said and after installing Carbon Rom again recovery is gone.. so I suposse it is Carbon problem. I will do it again and install a different rom
Click to expand...
Click to collapse
I agree, the problem results of the ROM: But you have to flash dorimanx after carbon because carbon replaces the current kernel with its own CM custom Kernel. It should work just fine with carbon when it's flashed after installing carbon.
So right now I'm running Task650s AOKP with Siyah Kernel, but an old version, thats still Android 4.0.4. In addition, I only have CWM 5. A lot of the KK ROM threads say that CWM 6 is required (and some JB ones imply the same thing, or tha I need JB bootloaders), but the one I want to flash (PACMan) doesn't have such a warning, but I'm still a bit apprehensive. Will I be fine if I just wipe, flash PACMan + GApps and reboot? Or is there an intermediary step I need like flashing a new kernel, and if so which one do I need?
Thanks guys
SupremeOverlord777 said:
So right now I'm running Task650s AOKP with Siyah Kernel, but an old version, thats still Android 4.0.4. In addition, I only have CWM 5. A lot of the KK ROM threads say that CWM 6 is required (and some JB ones imply the same thing, or tha I need JB bootloaders), but the one I want to flash (PACMan) doesn't have such a warning, but I'm still a bit apprehensive. Will I be fine if I just wipe, flash PACMan + GApps and reboot? Or is there an intermediary step I need like flashing a new kernel, and if so which one do I need?
Thanks guys
Click to expand...
Click to collapse
Well pacman isn't based on kitkat so I think you're good to go, the newest nightlies for that are still based on jellybean right? Or has it changed? I haven't downloaded one in a like two weeks.
SupremeOverlord777 said:
Will I be fine if I just wipe, flash PACMan + GApps and reboot?
Click to expand...
Click to collapse
Yes, you will be fine, as long as you install a JB kernel first (either STI or AJK 4.9 AOSP). I would suggest you install Milestone 1 (the download link is labeled PAC Release), instead of the nightly. Nightlies have a reputation for being finicky at times, so if you want stability you'd be better off sticking with known stable releases.
And don't forget to flash the gapps either, or you'll run into other problems.
SteveMurphy said:
Yes, you will be fine, as long as you install a JB kernel first (either STI or AJK 4.9 AOSP). I would suggest you install Milestone 1 (the download link is labeled PAC Release), instead of the nightly. Nightlies have a reputation for being finicky at times, so if you want stability you'd be better off sticking with known stable releases.
And don't forget to flash the gapps either, or you'll run into other problems.
Click to expand...
Click to collapse
Alright, sounds great. Thanks for the help, I'm downloading now.
Just got given an i9100 today with a faulty USB port. A new one is coming in the mail, but ebay is slow.
It charges fine so it can be used, just no data connection over USB (connects and disconnects, cleaning the port did not help)
Currently on 4.1.2, i9100XXLS9
I can get files to it via SD card, is there any methods to root it or get TWRP on it that can be done before i fix the USB port?
Mussels84 said:
Just got given an i9100 today with a faulty USB port. A new one is coming in the mail, but ebay is slow.
It charges fine so it can be used, just no data connection over USB (connects and disconnects, cleaning the port did not help)
Currently on 4.1.2, i9100XXLS9
I can get files to it via SD card, is there any methods to root it or get TWRP on it that can be done before i fix the USB port?
Click to expand...
Click to collapse
Mobile Odin
noppy22 said:
Mobile Odin
Click to expand...
Click to collapse
looks like its working, its loaded a stock rom and has its many options. How do i add a custom recovery with it? I'm fuzzy on the S2, since it combined kernel + recovery.
Mussels84 said:
looks like its working, its loaded a stock rom and has its many options. How do i add a custom recovery with it? I'm fuzzy on the S2, since it combined kernel + recovery.
Click to expand...
Click to collapse
You could use any kernel in .tar format to load a custom recovery. Philz or siyah kernel are normally used to root the s2, but I think any will work.
Alternatively you could download philz kernel in .zip format. You just need to find the correct kernel for your firmware HERE.
This guide is one of many for basic info on rooting etc
i figured it out, got philz on there for now.
Thanks for the idea of mobile ODIN, i tried flashify. TWRP manager, Rash, and terminal commands and none of them worked... mobile ODIN did however.
Now i get to read up on the custom roms available for the S2
Any recommendations?
Mussels84 said:
Any recommendations?
Click to expand...
Click to collapse
Marshmallow is quite stable now on the S2, so is Lollipop. Any of the recent MM roms are pretty good. I've been running AICP, Oct M, and AOKP recently(MM) and no real major bugs. On lollipop, Oct OS is good and Mokee is still releasing new builds. There are others that are good as well; too many to list...
On kitkat I love Slimsaber by fusionjack(and GreekDragon has released newer builds). Kitkat is a bit more battery friendly than LP or MM.
Many many options
noppy22 said:
Marshmallow is quite stable now on the S2, so is Lollipop. Any of the recent MM roms are pretty good. I've been running AICP, Oct M, and AOKP recently(MM) and no real major bugs. On lollipop, Oct OS is good and Mokee is still releasing new builds. There are others that are good as well; too many to list...
On kitkat I love Slimsaber by fusionjack(and GreekDragon has released newer builds). Kitkat is a bit more battery friendly than LP or MM.
Many many options
Click to expand...
Click to collapse
due to messing around with recoveries and getting into a no-boot situation, i've used the recovery i had to flash dirty unicorns android 6.0.1
hopefully that works, and all is well. So frustrating when recovery + kernel are paired.
edit: DU included the latest TWRP. Bliss.
Mussels84 said:
due to messing around with recoveries and getting into a no-boot situation, i've used the recovery i had to flash dirty unicorns android 6.0.1
hopefully that works, and all is well. So frustrating when recovery + kernel are paired.
Click to expand...
Click to collapse
Well good news on that front. @Lanchon has done some very nice work for the S2 community and come up with a solution to the bundled recovery/kernel. Read up on "isorec" HERE. Basically on the newer MM roms and some later LP roms, the kernel supports this isolated recovery. Just flash the isorec recovery and you have a seperated recovery and kernel
noppy22 said:
Well good news on that front. @Lanchon has done some very nice work for the S2 community and come up with a solution to the bundled recovery/kernel. Read up on "isorec" HERE. Basically on the newer MM roms and some later LP roms, the kernel supports this isolated recovery. Just flash the isorec recovery and you have a seperated recovery and kernel
Click to expand...
Click to collapse
only thing left - repartitioning without ODIN.
found some very vague guides on that...
Mussels84 said:
only thing left - repartitioning without ODIN.
found some very vague guides on that...
Click to expand...
Click to collapse
My first recommendation is if you need a 6.0.1 rom, then wait until your usb port is fixed.
If you don't want to wait for that, then take your time and read the link I gave you over on the DU thread for Lanchons re-pit tool. There is a link near the start of that thread to github where you will find downloads for the tool and a more detailed guide. In the xda thread(the one I linked), there are posts from users that will make clear how to use the tool. Basically you need to rename the file to re-partition how you want your layout
If you are not too worried about android version, then maybe try LP or KK. You don't need to re-partition for these roms as long as you use a pico/minimal gapps package and you will get better battery performance.
noppy22 said:
My first recommendation is if you need a 6.0.1 rom, then wait until your usb port is fixed.
If you don't want to wait for that, then take your time and read the link I gave you over on the DU thread for Lanchons re-pit tool. There is a link near the start of that thread to github where you will find downloads for the tool and a more detailed guide. In the xda thread(the one I linked), there are posts from users that will make clear how to use the tool. Basically you need to rename the file to re-partition how you want your layout
If you are not too worried about android version, then maybe try LP or KK. You don't need to re-partition for these roms as long as you use a pico/minimal gapps package and you will get better battery performance.
Click to expand...
Click to collapse
What i've ran into as a hurdle, is the following:
The latest TWRP doesnt work with that tool, there are no older links on the TWRP website.
The Isolated recovery is now merged with TWRP, so there are no older links there either.
If i can find the recommended 2.8.7.0 i guess it would work.
https://www.androidfilehost.com/?fid=24369303960684130
Edit: That link i posted above was correct and worked to repartition.