[Q] The effect of Cache partition size on performance? - Desire Q&A, Help & Troubleshooting

Hello
I want to modify my partition table, I've read users get better 3D performance (in games) with a bigger Cache partition.
3D performance aside, what's the recommended minimum size I should set it to without compromising overall performance?
I'm using a Sense based rom if it matters.
Thanks!

Not sure... I'm running an AOSP ROM with the N1 table. No performance lag for me.

Android uses the cache partition, to cache memory, giving it much faster access to it, so obviously the bigger your cache, the more cached ram your device has access too, also the market uses the cache for downloads, so if you have a 10mb cache partition you cant download a 14mb app off the market ect...
Sent from my HTC Desire using Tapatalk

AndroHero said:
Android uses the cache partition, to cache memory, giving it much faster access to it, so obviously the bigger your cache, the more cached ram your device has access too, also the market uses the cache for downloads, so if you have a 10mb cache partition you cant download a 14mb app off the market ect...
Sent from my HTC Desire using Tapatalk
Click to expand...
Click to collapse
but how to modify the cache partition, or how to know the exact size of it?
Thanks,

williepeng said:
but how to modify the cache partition, or how to know the exact size of it?
Thanks,
Click to expand...
Click to collapse
This thread is nearly 3 years old and a bit redundant now.
You can modify the cache partition by using what is known as a custom hboot.
An hboot has 3 partitions: /system /data and /cache. Assuming you have not changed it, you are still on 'stock hboot' and your cache partition is 40MB. Your /system is 250MB, and your /data (internal memory) is only 147MB
However, nowadays we use custom hboots to change these sizes. We reduce /system and /cache in order to increase /data (-> more space for apps).
The /cache argument above is basically redundant because it is just used for temporary files. Most custom hboots actually reduce this cache partition from 40MB to 5MB.
Basically there is no real need to change the cache partition, certainly no need to make it bigger.
Also, you need to be "S-OFF" to achieve any of this. As this is your first post I'm not sure what other reading you've done and what your ultimate goal is.

Just got a notification for a thread about a device i havent even had for 3 years lol
Sent from my HTC One X+ using Tapatalk

eddiehk6 said:
This thread is nearly 3 years old and a bit redundant now.
You can modify the cache partition by using what is known as a custom hboot.
An hboot has 3 partitions: /system /data and /cache. Assuming you have not changed it, you are still on 'stock hboot' and your cache partition is 40MB. Your /system is 250MB, and your /data (internal memory) is only 147MB
However, nowadays we use custom hboots to change these sizes. We reduce /system and /cache in order to increase /data (-> more space for apps).
The /cache argument above is basically redundant because it is just used for temporary files. Most custom hboots actually reduce this cache partition from 40MB to 5MB.
Basically there is no real need to change the cache partition, certainly no need to make it bigger.
Also, you need to be "S-OFF" to achieve any of this. As this is your first post I'm not sure what other reading you've done and what your ultimate goal is.
Click to expand...
Click to collapse
Thanks you for your answer. Yes, I'm a beginner and only know the basic about Android system.
Actually I'm make a cache.img that can be flashed into a Samsung device with the recovery.img, but I don't know whether it would destroy the system if the one I made is bigger or smaller than the one in stock ROM.

williepeng said:
Thanks you for your answer. Yes, I'm a beginner and only know the basic about Android system.
Actually I'm make a cache.img that can be flashed into a Samsung device with the recovery.img, but I don't know whether it would destroy the system if the one I made is bigger or smaller than the one in stock ROM.
Click to expand...
Click to collapse
Well welcome to the Android world
Each device is different, so Samsung root methods are also different.
DO NOT flash any cache.img for this phone. You don't need to adjust any cache sizes...and you'll more than likely brick your phone if you manage to somehow flash it.
For this device, I always recommend you start here, read it many times

eddiehk6 said:
Well welcome to the Android world
Each device is different, so Samsung root methods are also different.
DO NOT flash any cache.img for this phone. You don't need to adjust any cache sizes...and you'll more than likely brick your phone if you manage to somehow flash it.
Click to expand...
Click to collapse
Actually flashing cache partition cannot brick the phone since it doesn't carry any unique content. For the same reason you don't need to flash it at all, system will create all necessary files by itself.

dean15 said:
Actually flashing cache partition cannot brick the phone since it doesn't carry any unique content. For the same reason you don't need to flash it at all, system will create all necessary files by itself.
Click to expand...
Click to collapse
Actually eddie was on bout flashing the samsung cache.img the guy had so yh u could/would brick ur phone. And the desire's internal memory layout is divided into 3 partitions, system (250mb) cache (40mb) data (147mb) totally size is 437mb, soo if the guy flashed just the cache.img it would probably **** up the phone's memory leaving u with a paper weight

dean15 said:
Actually flashing cache partition cannot brick the phone since it doesn't carry any unique content. For the same reason you don't need to flash it at all, system will create all necessary files by itself.
Click to expand...
Click to collapse
All I can say is I don't recommend it at all...I also really hope you're not thinking about flashing something meant for a Samsung phone.
The cache partition may not carry any unique content, but flashing an hboot is a critical part of the phone. A corrupted hboot flash = brick
Even if you somehow successfully managed to flash a cache separately...ultimately you won't actually gain anything by doing so.
Choice is yours, but don't say we didn't warn you

eddiehk6 said:
All I can say is I don't recommend it at all...I also really hope you're not thinking about flashing something meant for a Samsung phone.
The cache partition may not carry any unique content, but flashing an hboot is a critical part of the phone. A corrupted hboot flash = brick
Even if you somehow successfully managed to flash a cache separately...ultimately you won't actually gain anything by doing so.
Choice is yours, but don't say we didn't warn you
Click to expand...
Click to collapse
)))
OK, we're talking about the same thing in different words.

Related

[Q] Android development newbie here with a couple questions

1) I have an ext3 partition on my SD card, which means my Desire is A2SD/A2SD+ compliant right? But whether A2SD or A2SD+ is in effect depends on the ROM I'm running - am I right to say this?
2) What exactly is Hboot? I seem to recall having read somewhere that Hboot is an alternative to A2SD... can anybody clarify? (And before you start flaming that there are a thousand and one topics on this already, I tried searching, but search was down)
1. Yes that's correct.
2. Hboot us essentially a different set of partitions for your desire's system. Currently your desire has internal memory split into 250mb system, 150mb data and a cache partition. The rom goes in system, apps in data. If the rom is small (aosp roms are smaller than sense due to the lack of sense which takes up tons of space) you can flash a different hboot which will change the layout of your phones internal memory. N1 table for instance has about 175 for system and a larger data partition, while the oxygen hboot has a tiny (90mb) system partition and a massive (300 odd mb) data partition negating the need for a2sd+ at all.
Hope that helps
Sent from my HTC Desire using XDA App
lick_the_fish said:
1. Yes that's correct.
2. Hboot us essentially a different set of partitions for your desire's system. Currently your desire has internal memory split into 250mb system, 150mb data and a cache partition. The rom goes in system, apps in data. If the rom is small (aosp roms are smaller than sense due to the lack of sense which takes up tons of space) you can flash a different hboot which will change the layout of your phones internal memory. N1 table for instance has about 175 for system and a larger data partition, while the oxygen hboot has a tiny (90mb) system partition and a massive (300 odd mb) data partition negating the need for a2sd+ at all.
Hope that helps
Sent from my HTC Desire using XDA App
Click to expand...
Click to collapse
Super informative, better than I could have hoped for Thanks!
Anyway I'm going to flash CM7 now, but on my previous ROM (GingerVillain), I'm pretty sure A2SD/A2SD+ was working fine, but in Titanium Backup it shows that my internal data partition was pretty congested. Any ideas?
fterh said:
Super informative, better than I could have hoped for Thanks!
Anyway I'm going to flash CM7 now, but on my previous ROM (GingerVillain), I'm pretty sure A2SD/A2SD+ was working fine, but in Titanium Backup it shows that my internal data partition was pretty congested. Any ideas?
Click to expand...
Click to collapse
I'm no expert and don't fully understand how a2sd+ installs apps etc. I don't know if it uses phone data first and then ext partition or what.
Sent from my HTC Desire using XDA App
fterh said:
Super informative, better than I could have hoped for Thanks!
Anyway I'm going to flash CM7 now, but on my previous ROM (GingerVillain), I'm pretty sure A2SD/A2SD+ was working fine, but in Titanium Backup it shows that my internal data partition was pretty congested. Any ideas?
Click to expand...
Click to collapse
Titanium Backup doesn't always show the correct info when it comes to available memory.
On gingervillian you have to use a dalvik-cache to ext script to create space on the internal memory, if you didn't do that then it can fill up quickly.
lick_the_fish said:
I'm no expert and don't fully understand how a2sd+ installs apps etc. I don't know if it uses phone data first and then ext partition or what.
Sent from my HTC Desire using XDA App
Click to expand...
Click to collapse
a2sd+ uses the ext partition on you sd card to move the apk file of applications. however, there are still some parts of the app, mainly the dalvik cache, which remain on the data partition in your phone's internal memory; that's why your internal storage still decreases, even when using an a2sd+-enabled ROM. there are some scripts which will move this dalvik cache to the sd card as well, but be sure you read carefully before applying and pay close attention to whether your card is fast enough so as not to generate performance issues (generally, you would need at least a class-4 card, with a class-6 or higher being recommended)

Dalvik-cache to /system ?

Hi,
Since a little while i ditched sense roms for gingerbread aosp roms (Oxygen 2.0 not to name it) which take a lot less space on the internal memory, especially on /system. I know it is possible to change partition table with s-off phones to optimize this free space but i'm s-on and i don't really want to change this.
But the result is i that i end up having something like 160mb free on /system partition and i have to move the dalvik cache from /data to have enough free space from apps. (Once the dalvik is moved /data is large enough even with a lot of apps for those who use a2sd)
i currently use AdamG script in "dalvik-cache2SD-signed.zip" to move the dalvik to sd-card, but i was wondering if it was possible to move it to /system instead (since with sense-table there is a lot free space in it). Could-it result better performances or battery life ?
What do you think about this ?
No don't think so and definitively not when you are S-on since you don't have write access to the system partition while booted.
Lol. No, since you're S-ON. So, if you unlock the system write, you can easily put another HBOOT layout anyway.
Oops yes i forgot /system was read-only >_< well at least i got my answer, thanks ! xD
maybe i will try this s-off thing after all...
It's not a big deal, just read the instructions carefully, make sure you have the proper drivers for fastboot before flashing hboot instead (you can find the instructions on www.unrevoked.com) and you're good to go.

[Q] Internal memory even worse after reflashing

So I posted this question and I did not get a helpful reply so I am trying again because the problem is even worse.
Basically, I rooted with unrEVOked over a year ago and I have flashed several ROMs, always doing a factory reset andwiping the dalvik cache with Clockworkmod.
I tried Leedroid, AuTrax, Ginervillain, Cyanogen then Oxygen. Perhaps another. When using Cyanogen I noticed I had very little internal memory (about 19Mb) even though all apps were on the SD card. I switched to Oxygen and nothing changed.
NOW I have done a factory reset, wiped dalvik, and reflashed Oxygen and I only have about 800Kb of internal memory.
I thought a factory reset would make my phone go back to pristine condition (albeit rooted) and I could start over from the beginning if I'd totally mucked something up and bricked or crippled it--but wipingand relashing has just made the problem worse!
Is there any solution here?
Youre doing the factory reset via recovery?
If thats not working, try formatting /data via recovery
S-off then change your hboot?!
Are you 100% sure apps2sd is working properly?
use a custom mtd or use one of the hboots at alpharev.nl
Yeah if you want more space you can always S-OFF and then flash a different SPL (hboot).
Also before you flash a new ROM remember to go to mounts and storage and format boot, data, system, cache.
rootSU said:
Youre doing the factory reset via recovery?
If thats not working, try formatting /data via recovery
Click to expand...
Click to collapse
Yes, I'm doing "wipe data/factory reset" from the green ClockworkMod menu. And "Wipe Dalvik Cache" from the "Advanced" menu beneath that.
Can you tell me in fairly simple terms what formatting /data is likely to accomplish? I'm up for it if there's a logical reason, certainly. But since every wipe&reflash chews up the little remaining memory I don't want to just be trying every option in the menu until SOMETHING works because at the rate it is losing internal memory I only have 1-2 more wipe-reflashes until it's a brick.
bortak said:
Yeah if you want more space you can always S-OFF and then flash a different SPL (hboot).
Also before you flash a new ROM remember to go to mounts and storage and format boot, data, system, cache.
Click to expand...
Click to collapse
OK, I'll try this (formatting boot, data, system, cache) but is there a simple explanation for why this is necessary and will fix the problem? I was pretty sure every rooting-flashing guide I'd read said only data wipe/factory reset (and sometimes dalvik cache) was necessary.
An explanation suitable for a noob like me, but a little more detailed than "it's a deeper, better wipe"
Thanks!!!
if you don't do it, sometimes it's possible that some of the data and crap from the past ROM gets left over and just uses space.
k.p. said:
NOW I have done a factory reset, wiped dalvik, and reflashed Oxygen and I only have about 800Kb of internal memory.
Click to expand...
Click to collapse
U get only 800 kb after reflash only the rom or even after restoring ur apps?
(maybe a stupid question, but i always prefer to make clarify everything)
andQlimax said:
U get only 800 kb after reflash only the rom or even after restoring ur apps?
(maybe a stupid question, but i always prefer to make clarify everything)
Click to expand...
Click to collapse
Yes. I did a factory reset, wiped the dalvik cache, flashed Oxygen and had 800kb of internal memory before doing anything else (and a barely functioning phone that couldn't even receive a text message but would sendone).
bortak said:
if you don't do it, sometimes it's possible that some of the data and crap from the past ROM gets left over and just uses space.
Click to expand...
Click to collapse
OK, that's what I figured it would do (and what I figured the problem was, since memory decreased with succesive flashes). So format data, boot, system, and cache but NOT sd-ext (I don't think there's a format /boot option).
In any particular order? And before or after "wipe data/factory reset"?
doesn't matter in what ordered. you only format sd-ext if you have an EXXT3/4 on your sd-card
k.p. said:
Can you tell me in fairly simple terms what formatting /data is likely to accomplish? I'm up for it if there's a logical reason, certainly. But since every wipe&reflash chews up the little remaining memory I don't want to just be trying every option in the menu until SOMETHING works because at the rate it is losing internal memory I only have 1-2 more wipe-reflashes until it's a brick.
Click to expand...
Click to collapse
This is a really simple explanation, which means that it will not be technically accurate, but will give you an idea.
When you delete a file, its not really deleted. It is there until something else overwrites it.
What actually happens is the reference to that file is removed from the File system (be that EXT, FAT, NTFS etc etc). The File system is basically table, or even an address book. The operating system uses this table to locate files that are there (when you request the file is opened etc). But also to locate spaces where new files can be written to.
When the next file is written, it will find a place via the file system that is empty and write to the location. This is usually when a past file is overwritten, although not neccessarily by the next new file.
Even when you do a factory reset, this is still the case. The files are still there, but the file system's "table" is cleared, making it appear empty, therefore able to accept new files.
It could be there is a corruption or failure of the file system where these entries are not properly being removed.
A format also will not delete these files. This is how anyone with a little bit of knowledge can recover some or all of your data after you format your Hard drive, SD card etc etc. What it will do though, is format the drive with a new file system, which will be clean and hopefully free of corruption.
Of course, the cause may be something else but it always a good idea to rule it out.
Thank you very much bortak and rootSU. I surmised generally that the problem was repeated flashing leaving debris and knew there had to be some solution to clean it up instead of going beyond simple root-and-flash. I very much wanted to fix it in one go instead of having another failed attempt and even less memory to work with for a fix. And thank you very much for taking the time for that explanation--I am now a little wiser and it let me know this wasn't an ill-informed "hail mary pass".
For anyone who finds this searching in the future, I formatted boot, system, data and cache and then did a factory reset. Rebooting got me stuck on the bootloader screen. I went back into recovery and flashed Oxygen. Now I have a working Desire with Oxygen and 109MB free on the internal memory.

[Q] Arc's /cache partition

Hey,
I've got Arconium ICS rom installed on my Xperia Arc. I'm running low on internal memory, and while trying to find more space on the device I've found this:
Code:
Filesystem Size Used Available Use% Mounted on
/dev/block/mtdblock2 225.0M 1.1M 223.9M 1% /cache
So my question is - what is the cache partition used for on ICS? How big should it be? I found this in the description of some Nexus HD ICS rom:
Cache partition (/dev/block/mtdblock4) is only used by CWM.
Cache partition size is not important because the data partition (/dev/block/mtdblock5) is used as the cache space when running Android.
Click to expand...
Click to collapse
Of course partitions path varies, but the info seems to be relevant.
And a final question - fdisk doesn't seem to work (getting "fdisk: can't read from" error) - how do I go about changing partition table?
To my knowledge (based mostly on HTC phones), in normal use the cache partition is used for downloading apps prior to installing, and for downloading OTA updates (which is why it's so big).
If youre running custom ROMs then this partition doesnt need to be anything like this size, because youre not going to be installing OTA updates. HTC desire owners resize this down to as little as 5meg (though this seems low to me, IMO it should be at least as big as the biggest app youre ever likely to install, so i'd say 25-50 meg is a safer bet.
Now, i have no idea how CWM works, so if this is using the partition to perform installs or nandroid backups or something then your probably wouldnt want to make it much smaller.
There is also a lot of space which could be freed up on the system partition, particularly if youre using a stripped down ROM.
All of the above is all well and good, if there is a way of changing the Arc's partition table. I have no idea how this is done, or if it is even possible. So would love someone who knows about this stuff to respond. BUT: i very much doubt FDISK (you mean windows fdisk?!?!?) is the answer - at the very least i'd expect that you'd need a specially modified kernel in order to boot with a modified partition table. The fact that it fdisk with an error instead of giving it a try is probably the only reason your phone still boots.

Format /System Question

From my understanding formatting the /system partition through CWM will remove the android OS completely from your device and you would have to flash a new one to replace it. Found the following information on the below website:
http://www.addictivetips.com/mobile...plained-boot-system-recovery-data-cache-misc/
/system
This partition basically contains the entire operating system, other than the kernel and the ramdisk. This includes the Android user interface as well as all the system applications that come pre-installed on the device. Wiping this partition will remove Android from the device without rendering it unbootable, and you will still be able to put the phone into recovery or bootloader mode to install a new ROM.
My question is, if I format the /system partition, does it remove all my currently saved pictures and videos on my internal memory? When I install a new ROM I typically wipe data /factory reset, then perform TDJs super wipe before installing the new ROM.
However, the instructions for installing the newest CM10 ROM also says to wipe /system partition. I know this will remove the OS, but will this also remove my pics and videos or should I back them up first before performing this step? Thanks.
Chochiwpg said:
From my understanding formatting the /system partition through CWM will remove the android OS completely from your device and you would have to flash a new one to replace it. Found the following information on the below website:
http://www.addictivetips.com/mobile...plained-boot-system-recovery-data-cache-misc/
/system
This partition basically contains the entire operating system, other than the kernel and the ramdisk. This includes the Android user interface as well as all the system applications that come pre-installed on the device. Wiping this partition will remove Android from the device without rendering it unbootable, and you will still be able to put the phone into recovery or bootloader mode to install a new ROM.
My question is, if I format the /system partition, does it remove all my currently saved pictures and videos on my internal memory? When I install a new ROM I typically wipe data /factory reset, then perform TDJs super wipe before installing the new ROM.
However, the instructions for installing the newest CM10 ROM also says to wipe /system partition. I know this will remove the OS, but will this also remove my pics and videos or should I back them up first before performing this step? Thanks.
Click to expand...
Click to collapse
Now i could be wrong as i am no Dev by any means but i do not think it will wipe your emmc as well. Reason i think it will be fine if you wipe /system is if you go in with root explorer and go to your /system folder your emmc is not located there so therefore if you were to wipe your /system patition it sould leave the emmc partition in tact.
But as always i would backup your emmc to your pc and give it a try. Hope this helps :good:
sinfulgray said:
Now i could be wrong as i am no Dev by any means but i do not think it will wipe your emmc as well. Reason i think it will be fine if you wipe /system is if you go in with root explorer and go to your /system folder your emmc is not located there so therefore if you were to wipe your /system patition it sould leave the emmc partition in tact.
But as always i would backup your emmc to your pc and give it a try. Hope this helps :good:
Click to expand...
Click to collapse
I was thinking the same thing as well but just had to ask because I have never processed the format /system action before. I am currently running a TW ROM ATM and looking through ES File Explorer my sdcard (which is the same as emmc on AOSP ROMs) isn't located located in the /system folder either.
Thanks for your reply, I tried to give you a thanks but I have reached my limit today
sinfulgray said:
Now i could be wrong as i am no Dev by any means but i do not think it will wipe your emmc as well. Reason i think it will be fine if you wipe /system is if you go in with root explorer and go to your /system folder your emmc is not located there so therefore if you were to wipe your /system patition it sould leave the emmc partition in tact.
But as always i would backup your emmc to your pc and give it a try. Hope this helps :good:
Click to expand...
Click to collapse
I'm no Dev either, but your right. Formatting system will not touch your emmc or sd cards. If you format system when flashing a new nightly (which I do every 3rd flash), you won't lose any user data at all. Only ROM and system apps, this is why you need to reflash Gapps as well if you format system.
When you use TDJ's wipe script, it formats everything (including system) except emmc and external sd cards.
Sent from my SAMSUNG-SGH-T989 using Tapatalk 2
RikkKeith said:
I'm no Dev either, but your right. Formatting system will not touch your emmc or sd cards. If you format system when flashing a new nightly (which I do every 3rd flash), you won't lose any user data at all. Only ROM and system apps, this is why you need to reflash Gapps as well if you format system.
When you use TDJ's wipe script, it formats everything (including system) except emmc and external sd cards.
Sent from my SAMSUNG-SGH-T989 using Tapatalk 2
Click to expand...
Click to collapse
Thanks so much, I run TDJ's wipe script with each install of a new ROM and completely didn't realize that is also wipes the /system partition. I just re-read his Superwipe thread and right in the OP it says
"This exceeds anything that CWM is capable of from the menu options. This will format and erase EVERYTHING on your /system, /data, /cache partions with EXT4 file system. It WILL NOT wipe SD CARD or EMMC... After it is complete with format and e****, it will align all disks partitions properly."
I was up extra early this morning, forgive me, I need to learn how to read better as well :laugh:
Thanks again.
Remember guys, wiping doesn't wipe everything. However, not wiping everything can bring its own issues.
Sorry for bumping up an old thread but it was very relevant to this topic. If I wipe the system before flashing a new ROM will my apps remain intact with their data? I know system apps will be gone but they will come back anyway so it doesn't matter.
Chochiwpg said:
From my understanding formatting the /system partition through CWM will remove the android OS completely from your device and you would have to flash a new one to replace it. Found the following information on the below website:
http://www.addictivetips.com/mobile...plained-boot-system-recovery-data-cache-misc/
/system
This partition basically contains the entire operating system, other than the kernel and the ramdisk. This includes the Android user interface as well as all the system applications that come pre-installed on the device. Wiping this partition will remove Android from the device without rendering it unbootable, and you will still be able to put the phone into recovery or bootloader mode to install a new ROM.
My question is, if I format the /system partition, does it remove all my currently saved pictures and videos on my internal memory? When I install a new ROM I typically wipe data /factory reset, then perform TDJs super wipe before installing the new ROM.
However, the instructions for installing the newest CM10 ROM also says to wipe /system partition. I know this will remove the OS, but will this also remove my pics and videos or should I back them up first before performing this step? Thanks.
Click to expand...
Click to collapse
No, I flash all the time and always format system, you will not lose your internal or SD memory
Inagalaxyfaraway said:
Sorry for bumping up an old thread but it was very relevant to this topic. If I wipe the system before flashing a new ROM will my apps remain intact with their data? I know system apps will be gone but they will come back anyway so it doesn't matter.
Click to expand...
Click to collapse
Yes, they will stay intact with a /system wipe. However, with a factory reset or /data wipe, your apps will be gone.
Sent from my Nexus 7 using xda app-developers app
Sorry to bump old thread. I just deleted system, data, cache etc everything. Now when i attempt to
Reboot it warns that no OS installed. I m using TWRP. is it safe to power off the device? Will i be able to get back to recovery to flash a new rom afterwards, as i dont have one ready now??
Btw i hav nexus 7 , but didnt find this discussion there so i am posting here.
Thanks in advance for help....
I accidentally formatted system on my HTC desire HD. but i'm unable to install rom in it. If anyone can help me make it working(instruct how to install ROM in it) i'd be grateful.
Sawrose said:
I accidentally formatted system on my HTC desire HD. but i'm unable to install rom in it. If anyone can help me make it working(instruct how to install ROM in it) i'd be grateful.
Click to expand...
Click to collapse
You might want to post your question here : http://forum.xda-developers.com/forumdisplay.php?f=754
Careful with that with new versions of TWRP and CWM! http://forum.xda-developers.com/showthread.php?t=1966887
I format my system through xrecovery but after that first it stuck in sony ericsson logo.. sometimes it doesnt boot and the red light flashes
Accelerator00000 said:
I format my system through xrecovery but after that first it stuck in sony ericsson logo.. sometimes it doesnt boot and the red light flashes
Click to expand...
Click to collapse
I think you're lost friend. LOL.
Sent from my Moto X cellular telephone...
kj2112 said:
I think you're lost friend. LOL.
Sent from my Moto X cellular telephone...
Click to expand...
Click to collapse
it stucks at the sony ericsson and i cant enter the xrecovery sorry it just low battery thats why red light flash.. LOL
Accelerator00000 said:
it stucks at the sony ericsson and i cant enter the xrecovery sorry it just low battery thats why red light flash.. LOL
Click to expand...
Click to collapse
Buttttt...this is the t989 S2 forum.
Sent from my Moto X cellular telephone...

Categories

Resources