Develop Bugs

[MOD][RECOVERY] Firerat's Custom MTD Partitions (resize Data,System and Cache)

If you don't understand what this Modification is doing, why it needs to be done, or what possible benefits come from it, then...
PLEASE DO NOT TRY THIS MOD.
***Even tho it is impossible to brick your phone when flashing this i still highly recommend you UNDERSTAND what you are attempting to do before you do it. If someone explains you are freeing up internal memory from other places not using it and you still have to ask what the benefit is, then you obvisouly dont fully understand the mod and your phone and should turn away now.***
Thank You.
Now onto the mod: Heres a quick description of what this mod is doing. Pretend your phone is a pizza cut into 3 even pieces. Each piece is memory for /cache, /system, /data. Your anorexic sister "aka cache" doesn't eat a lot so most of her slice will always be left, your fat obese brother "/data" always eats his whole slice and is left wanting more. You are healthy "/system" and only eat what you need and never less never more.
What this mod is doing is taking that original pizza and RE-CUTTING the slices to better fit whose eating them, so since your anorexic sister barely eats and your obese brother is always hungry it takes all the extra pizza "aka memory" from your sister and gives it to your brother. As for you "aka /system" you only eat exactly what you need "aka the size of the rom and files it install" so it resizes your own slice to exactly the number it needs to install the rom and its gapps/files and leaves you with just a little wiggle room.
I recently tried the v1.5.8 on the gsm hero n it worked pretty well,before i used2have 170mb of internal memory with my decked for life now after applying this mod i have about 300 mb + which means i dont need a freaking ext4 partition for all my crap! xD
PLEASE USE CLOCKWORK RECOVERY IT WILL NOT WORK ON AMON-RA:
although in the cdma forums they used adb,i didnt feel like using it n didnt cause any issues
Original Files and Instructions: Firerats Original G1/MT3G thread found Here
Media fire link - Download!
(please note i've tried only the 1.5.8 version n it runs fine!)
After you read through firerats original instructions just know that itll be slightly different on your hero!
1. Click on the link i posted above and download these files: FR-recovery-v1.5.3-CustomMTD_S.zip and FR-boot-v1.5.3-CustomMTD_S.zip
2. Put both those files onto your SDCard.
3. While in your SDCard, make a .txt file named "mtdpartmap.txt"
4. Open your new mtdpartmap.txt file and
if ur using an aosp rom cm6 or cm7 type this into the txt
Code:
mtd 95 15
(The 95 here refers to /system size, and 15 to /cache partition size)
If you are using a larger Sense Rom then type
Code:
mtd 175 15
(This is just an approximation)
5. Once all 3 files are saved on the root of your SDCard, reboot your phone into recovery
6. Format/Wipe your system and cache.
7. Flash the file: FR-recovery-v1.5.X-CustomMTD_S.zip
8. Once the file is done flashing, it'll prompt you to wipe cache, system, and dalvik again.
after wiping cache system and dalvik reboot back into recovery
9.Flash CM7 or CM6 rom if you used 95 for /system or Flash your larger Sense Rom if you used 175 for /system
9.a.Optionally, flash any kernel you may be choosing to use.
10.Flash the file: FR-boot-v1.5.X-CustomMTD_S.zip
11.Click the top option on your recovery menu to reboot your system.
12.Once your system is fully booted you can go into menu > settings > sd card and internal storage , and check all the new added internal memory you have.
FYI : anytime you flash a new rom after this mod, or flash a new kernel to a currently flashed rom, you will ONLY NEED TO FLASH THE SECONDARY FIRERAT BOOT file named "FR-boot-v1.5.X-CustomMTD_S.zip".
so say after this mod you want to try a new kernel, you flash the kernel, flash boot, and reboot the system.
or say you want to flash a new cm7 nightly update, you flash the new rom/update, flash boot, reboot.
or say u want a new nightly and a new kernel, you flash the nightly, flash the kernel, flash the boot, reboot.
its very simple, if anything u flash overwrites current kernel specifications, u need to flash the boot file to make sure it knows how to set itself up. this goes for nandroid back ups as well.
A lil more help- i was using the decked rom so to actually check how much memory was consumed by /system i opened the terminal emulator typed in this
Code:
# su
# df -h
to show me memory consumption.
the command will tell you what % you are using on your system. if you are at 60% then you can go ahead and decrease your /system value in your mtdpartmap.txt to about 2mb over the value it says you are using. so if your rom uses 115mb of /system you can change your mtd to "mtd 117 2".
So if you are getting an error while trying to flash a rom after doing this modification you most likely don't have enough /system space and will want to up your value to something more then enough like "mtd 200 4" then run the above code and re-scale down back to 2mb over what the current rom is using.
Credits-
Foo_Blyat over at the cdma forums based on whose guide i could get this work on our hero and rewrite this guide
Firerat for even making this mode which is BRILLIANCE!!!!!
Proof?
heres a couple of my personal screen-shots after using the mod
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
notice the internal memory and tell me i'm ****ting u ppl
Enjoy

Is it possible to do a nand backup of my current rom, do this mod, and then restore the nand backup? Or does it only work with a fresh flash of a new rom?
Also, could you please explain exactly what the two numbers in the mtdpartmap.txt file are referring to. Thanks.

Woohoo, it works!!
OK, first I'll answer my own questions. It is possible use a nand restore, which is what I did. Secondly, the first number in the txt file refers to the system partition and the second refers to the cache partition. Whatever is left over goes to the data partition.
I decided to be cautious in my numbers. I left the cache partition exactly as it was (130!) and only reduced my system partion by 60mb (still leaving ~10mb of wiggle room in the system partition).
So now I have 60mb extra in internal storage! Sweet!

treesurf said:
Woohoo, it works!!
OK, first I'll answer my own questions. It is possible use a nand restore, which is what I did. Secondly, the first number in the txt file refers to the system partition and the second refers to the cache partition. Whatever is left over goes to the data partition.
I decided to be cautious in my numbers. I left the cache partition exactly as it was (130!) and only reduced my system partion by 60mb (still leaving ~10mb of wiggle room in the system partition).
So now I have 60mb extra in internal storage! Sweet!
Click to expand...
Click to collapse
Nice
Sry I wasn't more accurate, the first number is the system partition and second is the cache partition, cache doesn't need alotta memory perhaps u should make it 35 thereby getting 100mb of data more btw which rom?
Sent from my Hero using xda premium

what can I say ? It simply worked. I used clockworkmod to make a backup of my current ROM first (I am running the latest Heroine) then repartitioned following your instructions, restored the previously backup and voilà, swimming in a sea of free megabytes :
# df -h
df -h
Filesystem Size Used Available Use% Mounted on
tmpfs 95.5M 0 95.5M 0% /dev
tmpfs 4.0M 0 4.0M 0% /sqlite_st
/dev/block/mtdblock3 180.0M 169.8M 10.2M 94% /system <<< was 100% before
/dev/block/mtdblock5 255.8M 153.6M 102.1M 60% /data <<< was more then 90% before
/dev/block/mtdblock4 30.0M 4.2M 25.8M 14% /cache <<< to be safe, I could probably lower it further to 15 as per instructions
/dev/block//vold/179:1
7.4G 5.9G 1.5G 80% /sdcard

I believe that was done earlier. But devs pulled out.
http://forum.xda-developers.com/showthread.php?t=913245
http://forum.xda-developers.com/showthread.php?t=755204
Cheers!
EDIT: I re-read the threads - it appears tha everything worked fine, maxima just bought a new phone

I'm so going to try this tomorrow, I have absolutely NO time today xD more cache is nice

bharat_goku said:
Nice
Sry I wasn't more accurate, the first number is the system partition and second is the cache partition, cache doesn't need alotta memory perhaps u should make it 35 thereby getting 100mb of data more btw which rom?
Sent from my Hero using xda premium
Click to expand...
Click to collapse
When I fill up my new 80mb of /data then I'll think about reducing the cache.
I'm using DeckedForLife ROM.

I always use a "move dalvik-cache to /cache" script. It is a tad safer I guess?

THIS IS CUTE. Gona try it ....
riemervdzee said:
I always use a "move dalvik-cache to /cache" script. It is a tad safer I guess?
Click to expand...
Click to collapse
Yeah, I tried it too. Pretty neat script, but unfortunately it does not increase system partition size.
Also I got suspicions that system is cleaning cache from time to time by deleting older files so as well dalvik files.
edit: proof pics are not visible. Maybe I did not understand everything, but is it possible to make it permanent mod?

It's permanent until you flash your next ROM. So you just need to flash the FR-boot-v1.5.X-CustomMTD_S.zip file after flashing any ROM/nand backup and it will continue to use whatever partition settings you have put in the text file.

For personal use this mod is fine, but if I'm building a custom ROM for public use I need to go through very complicate ROM flash explanation with possibility to brick the phone at the end.

Ok,tried this and it's super . However, I have some strange "problems".
I have set partitions to 100 for system and 30 for cache right from the beginning. If I boot into rom right after flashing, without changing kernel, everything is as it should be. Have over 300 MB on internal storage etc. As soon as I change kernel usb tethering becomes disabled (when I plug the cable it still says that's not connected when I enter "tether menu" ) and nothing helps, not changing kernel, reverting to old one, nothing. Second thing is "power menu", only three options appear in here, reboot, recovery and screenshot. Silent and airplane mode, profiles and power off options don't appear . And finally, when I try to wipe dalvik cache this message pops in recovery :
E: Can't mount /dev/block/mmcblk0p2
(File exists )
Dalvik Cache wiped.
It seems that dalvik is wiped in the end? What's this partition used for?
First two problems go away if I flash some rom without messing with partitions but last one stays
Can someone else please check usb tether and power boot thingy on their phone?
Sent from my Hero using Tapatalk

What ROM do you use?
What recovery do you use?
OP said that AmonRA is not tested, only CWM.

Using decked for life and cwm recovery.
Sent from my Hero using Tapatalk

aca89 said:
Ok,tried this and it's super . However, I have some strange "problems".
I have set partitions to 100 for system and 30 for cache right from the beginning. If I boot into rom right after flashing, without changing kernel, everything is as it should be. Have over 300 MB on internal storage etc. As soon as I change kernel usb tethering becomes disabled (when I plug the cable it still says that's not connected when I enter "tether menu" ) and nothing helps, not changing kernel, reverting to old one, nothing. Second thing is "power menu", only three options appear in here, reboot, recovery and screenshot. Silent and airplane mode, profiles and power off options don't appear . And finally, when I try to wipe dalvik cache this message pops in recovery :
E: Can't mount /dev/block/mmcblk0p2
(File exists )
Dalvik Cache wiped.
It seems that dalvik is wiped in the end? What's this partition used for?
First two problems go away if I flash some rom without messing with partitions but last one stays
Can someone else please check usb tether and power boot thingy on their phone?
Sent from my Hero using Tapatalk
Click to expand...
Click to collapse
When u changed kernel did u flash the boot.zip file again?
Also I believe ur changing from .29 to .35 kernel? Did u apply the USB fix by erasmux??
Abt the power menu just wait a bit it comes back...
I made a mistake of implementing move dalvik cache to SD,I think that's causing errors in the
Wipe
Just plug ur fone into ur comp and
Open console go to ur sdk directory and try this command adb remount /dev/block/mmcblk0p2
Not sure if the command is ryt,Bt just give it a try...
Sent from my Hero using xda premium

Thanks for your efforts.
I used Fireat's path already on my G1 (meanwhile I sold it).
It saved me from using ext partition for data, which is in no way a speed booster.
Maybe it's a dumb question, but shouldn't it be possible to integrate this patch in a ROM?
The steps described in your post are easy to understand and absolutely not complicated (for fellows that often change ROMs).

bharat_goku said:
When u changed kernel did u flash the boot.zip file again?
Also I believe ur changing from .29 to .35 kernel? Did u apply the USB fix by erasmux??
Abt the power menu just wait a bit it comes back...
I made a mistake of implementing move dalvik cache to SD,I think that's causing errors in the
Wipe
Just plug ur fone into ur comp and
Open console go to ur sdk directory and try this command adb remount /dev/block/mmcblk0p2
Not sure if the command is ryt,Bt just give it a try...
Sent from my Hero using xda premium
Click to expand...
Click to collapse
I've already done all of that several times (trying out on a few roms) and now I came back to decked and all of the sudden everything works . Menus are back and tethering works.
"/dev/block..." thing is still there. Tried your command but it doesn't help although it's properly written. I read somewhere that formating helps but in my case it doesn't, already tried. So, if you got any other idea I'll gladly try it. In the meantime I'm gonna enjoy the free space on internal storage .
Thanks for help btw.
Sent from my Hero using Tapatalk

Amon Ra
Well, I think I can definitively say this doesn't work on Amon Ra. The second reboot into recovery has to be done via a complete switch off. Tried reinstating from nand backup, but final reboot either sticks on HERO or (sometimes) semi boots into ROM, but without desktop...
Wanted to undo the error of trying this, so downloaded the REMOVE script and flashing that using same procedure, with and without BOOT script, same difference. Tried flashing ROM again, clean. Same difference. So actually I'm a bit stuck.
Any thoughts from anyone how to get back to a safe spot from here and starting over? (Prefer to avoid hard reset!)

Have you tried changing system and cache values in txt file to original ones, or at least something close to them, and then flashing boot.zip. Just a thought, don't know if It's actually going to change something.
Sent from my Hero using Tapatalk

[Q] Insufficient memory available - with a twist.

Acer Iconia A100 Tab, ICS, rooted, unlocked, backed up, CWM, Superuser.
The A100 comes from the factory with 8GB internal memory and I added a 32GB chip. Fine, but as expected, I soon got the dreaded "Insufficient memory available" message. The A100 has an inherent design flaw which does NOT allow apps to be transferred to SD (have tried everything).
I've successfully swapped the mount points and now have combined the internal 8GB and the external 32GB to act as one single drive. The machine now sees itself as having 40GB of internal storage. Works perfectly BUT...
...now I'm permanently getting the ol' "Insufficient storage available" message on EVERY app I try to install. Even worse - I've done massive uninstalling of almost ALL my programs, and now I can't re-install ANY apps with getting the insufficient storage message, either from Play Store, or as a standalone apk installer file.
I've tried;
- Lucky Patcher
- rebooted countless times
- set all system files and folders to RW
- every type of cache cleaning program
- increased my swap filesize to maximum
- every type of past-program-cleanup tidy program
- tested, verfified, but still replaced, the 32GB sd chip
- used a terminal emulator to properly rewipe the cache folder
- restricted the list or startup programs to only system-required apps
- using SDK, have tried both the "set install apps to internal" and external drives
There is very little left on my system now (95% free), and the system runs beautifully and passes all diagnostics. I've just reached the point now where I cannot install or reinstall even the tiniest tiny programs. Of the few remaining programs, I dare not uninstall CWM, Superuser or ADB Control, for fear of not being able to even restore past backups.
In short, the more capacity I give back to the system, the less capacity it has.
Any thoughts/suggestions? (other than using it as a doorstop)

IF you have GPS enabled, look for the GPS data files (I can't remember exactly where) as the GPS on some of these tablets (like mine) repeatedly download AGPS data at will filling up part of the memory. Not sure if this is your issue, but this caused me all kinds of insufficient memory problems with my A100.

Yup, check the /data/GPS folder. If you use GPS it gets loaded with dated .txt cache files. The only fix is deleting them every once and a while or factory reset if your not rooted,

Clear data from play store and google frameworks.
Tapatalked from my Galaxy S II.

pio_masaki said:
Clear data from play store and google frameworks.
Tapatalked from my Galaxy S II.
Click to expand...
Click to collapse
Thanks for your input. Yes, by this point I've ended up with a long checklist of regular things to do just to take any argument away from the machine. I regularly clear the data from Play Store and Frameworks. The GPS has been disabled for weeks, and was set to not update from any source other than straight GPS satellites (non-network). I killed off the few GPS data files I did find.
The available storage is now down to 382mb, and seems to be dropping by 50mb per day - while it simultaneously tells me I have 28GB free! WTF?
I now only have about 7 programs installed, excluding the obvious factory preinstalled ones.
CWM - 384kb
ES File Explorer - 5.7mb
Android Assistant - 1.74mb
Acer Recovery Installer - 2.55mb
Lucky Patcher - 5.62mb
ROM Manager - 5.32mb
Link2SD - 0.94mb
Wake Lock - 72kb
If I uninstall any of these in the vein hope of trying to clear any more space, I won't be able to put them back. Everytime I boot, I get the "Low space" warning, and no apps can be installed at all.
Just a thought - under Data Usage > Removed Apps > it shows an ever-climbing graph, and says Foreground: 0.00B, Background 2.70GB Is this just a record of past activity? Or does it show actual space that's being consumed? If so, I can see no way of clearing it. The View app settings button is greyed out.

I was having a similar problem although I never figured out what was the deal I used pio's black hole wipe and reinstalled my rom and everything works great now.
Sent from my SGH-I777 using xda premium

Are you sure its not Lucky Patcher (yes I know this app is frowned upon here on xda)?
Open Lucky Patcher > Go to troubleshooting > click "remove fixes and backup".

illego said:
Are you sure its not Lucky Patcher (yes I know this app is frowned upon here on xda)?
Open Lucky Patcher > Go to troubleshooting > click "remove fixes and backup".
Click to expand...
Click to collapse
I was going to mention that app tends to cause that error, its come up before. Any further discussion concerning that app should be taken to PM or off forum completely.
I would suggest the black hole wipe or at least a hard reset and leave that app out of the next install. No restores just fresh installs from play store.
Tapatalked from my Galaxy S II.

pio_masaki said:
I was going to mention that app tends to cause that error, its come up before. Any further discussion concerning that app should be taken to PM or off forum completely.
I would suggest the black hole wipe or at least a hard reset and leave that app out of the next install. No restores just fresh installs from play store.
Tapatalked from my Galaxy S II.
Click to expand...
Click to collapse
Lucky Patcher was the last app I was successfully able to install a few days ago, and I only put it on in a last ditch effort to try and solve the 'insufficient memory available' problem which had been growing steadily worse over the past two weeks.
I did a hard reset and confirmed a clean running virginal machine, although I still got the 'Low space' and 'Insufficient memory available' message, but I did a another backup just to be safe. I then followed the black hole wipe to the letter. Everything went smoothly through each step, and now when the phone boots, it just sits there displaying the Acer logo for eternity.
When I do a recovery boot, I can now only get
"Erasing Cache before SD update...
SD update cmd: recovery
Booting recovery kernel image
Recovery verified failed..."
Did this just brick my tab? Or does someone know of a way out? Obviously the PC or ADB no longer recognizes it.

sailboatamelia said:
Did this just brick my tab? Or does someone know of a way out? Obviously the PC or ADB no longer recognizes it.
Click to expand...
Click to collapse
Hmm. Silence.
Can anyone give me their humble private opinion if running the black hole wipe has indeed bricked my system?
- or - based on the message I'm now getting...
"Erasing Cache before SD update...
SD update cmd: recovery
Booting recovery kernel image
Recovery verified failed..."
Does anyone know if there's anything that can be tried first, before I send it back to Acer?
Has anyone themselves had that message before?

sailboatamelia said:
Hmm. Silence.
Can anyone give me their humble private opinion if running the black hole wipe has indeed bricked my system?
- or - based on the message I'm now getting...
"Erasing Cache before SD update...
SD update cmd: recovery
Booting recovery kernel image
Recovery verified failed..."
Does anyone know if there's anything that can be tried first, before I send it back to Acer?
Has anyone themselves had that message before?
Click to expand...
Click to collapse
What did you erase with the blackhole wipe?

Theonew said:
What did you erase with the blackhole wipe?
Click to expand...
Click to collapse
The black hole wipe:
Cache Wipe: Formats /cache and deletes /data/dalvik-cache.
System Wipe: Formats /cache /system and /data. Recovery mounts INTERNAL SD to /data/media
Please backup your INTERNAL SD before running this or you will lose everything on it!
Cache Nullify: Nullifies /cache and deletes Dalvik-cache.
System Nullify: Nullifies /cache /data /system.
http://forum.xda-developers.com/showthread.php?t=1682525
All of which is not necessarily to be feared - as long as you can still gain access to the recovery ROMs on the external SD. The problem is, after doing the above-mentioned processes, you cannot even boot into recovery, much less access the external SD. All you're left with is the Acer logo, and the ability to power up or down.
.

sailboatamelia said:
The black hole wipe:
Cache Wipe: Formats /cache and deletes /data/dalvik-cache.
System Wipe: Formats /cache /system and /data. Recovery mounts INTERNAL SD to /data/media
Please backup your INTERNAL SD before running this or you will lose everything on it!
Cache Nullify: Nullifies /cache and deletes Dalvik-cache.
System Nullify: Nullifies /cache /data /system.
http://forum.xda-developers.com/showthread.php?t=1682525
All of which is not necessarily to be feared - as long as you can still gain access to the recovery ROMs on the external SD. The problem is, after doing the above-mentioned processes, you cannot even boot into recovery, much less access the external SD. All you're left with is the Acer logo, and the ability to power up or down.
.
Click to expand...
Click to collapse
Uh no. It doesn't touch boot, recovery, external SD or bootloader. Recovery verified failed means your boot loader is locked.
Tapatalked from my Galaxy S II.

pio_masaki said:
Uh no. It doesn't touch boot, recovery, external SD or bootloader. Recovery verified failed means your boot loader is locked.
Click to expand...
Click to collapse
Wow! That's good news! (maybe) So... if I can unlock the bootloader then, in theory, I should be able to continue restoring the tab? Please excuse my vertical learning curve on this. If I understand correctly, there is no bootloader unlocker for the A100 iteself, but apparently there's a compatible one for the A200 that can be used.
From my tab's current state, could you please tell me what the next step(s) are?
I'd be eternally indebted to you.
.

[Q] Is it possible to wipe system partition before installing a ROM

This is regarding a recently bought tablet Note 8. The current usage of /system partition is at above 75%. I have been trying to wipe/delete all system data in an attempt to have a 'fresh' OS once I install new stock ROM. In CWM recovery, I have even tried to format system partition (in addition to normal data reset, cache wipe and delvek cache wipe).
I installed the new stock ROM 4.4.2 in Download mode. Afterwards I checked and my system partition was still above 75% full. I do understand that system partition is normally read only. I am trying to work out if there is there any way where I can flash the stock ROM whilst completely removing the current system files.
Please offer any guidance or advice regarding this matter. Thanks!

Possible? Yes. Necessary? No.
The installation script for a ROM will almost always format the system partition before setting it up with the new ROM files, unless the developer is doing some special testing and you would know if that is the case.
ramjet73

Yes I think most custom ROMs would wipe system partition too. Though I want to install the stock ROM of Android 4.4.2. I have flashed the ROM about four times now, everytime trying different settings such as wipe/format system drive.
But I always end up with /system drive same size as before.
Thanks for the reply ramjet73.

S2 user said:
Yes I think most custom ROMs would wipe system partition too. Though I want to install the stock ROM of Android 4.4.2. I have flashed the ROM about four times now, everytime trying different settings such as wipe/format system drive.
But I always end up with /system drive same size as before.
Thanks for the reply ramjet73.
Click to expand...
Click to collapse
Depending on how you flash the stock ROM, Odin will flash a .img file to the system partition and completely replace its contents or an updater-script in a stock ROM zip file will format it and then copy all the included /system files to the empty partition.
In either case you cannot control what goes into the initial configuration of the system partition, only delete things that you don't need after it is flashed, unless you flash from a stock ROM zip file and delete items from that before you flash it.
There are scripting tools that can help with ROM "slimming" but I don't know if any are available for the Note 8.0 or not.
ramjet73

the CPU and GPU frequency problem

Hi,guys.
I have my Mi 5s three months ago. I face this f-word problem: when I play demanding graphic games,it automatically decreases the CPU,GPU's clock results in the games lag as hell. I used CPU-Z to check,before playing the GPU has 624mhz,when you enter a game,it has 401mhz,sometime 133mhz Lol. Also the CPU.
Anyone has the same problem? How to solve it?
You know,have a powerful device but can't play games it's annoying as f.

Maybe it's just overheating.
What is the temperature (check in Security->Battery).

gnazio said:
Maybe it's just overheating.
What is the temperature (check in Security->Battery).
Click to expand...
Click to collapse
I dont even start the game,how the hell is it overheating? I checked,its about 33-35°C.
Im using Global Stable 8.0.30 Official Rom. And btw,how to up new rom when you cant erase all the system files? Mi5s doesnt support Sdcard,so how can I up new rom?(my phone is already unlock and flashed TWRP).

Remove / Cut thermal config
*Sorry for bad english
If your phone is rooted, you can cut/remove your thermal config in this path
/etc/thermal-engine-8996.conf
Becareful, it will raise your cpu heat upto 64°C
But your cpu freq will be stable @2,1 Ghz and Gpu @624 Mhz

Nhutlong010 said:
Im using Global Stable 8.0.30 Official Rom. And btw,how to up new rom when you cant erase all the system files? Mi5s doesnt support Sdcard,so how can I up new rom?(my phone is already unlock and flashed TWRP).
Click to expand...
Click to collapse
There is no need for SD to move files to the phone.
Just use MTP over USB or the FTP server built into MIUI's File Explorer over WiFi (File Explorer->Categories->FTP).

gnazio said:
There is no need for SD to move files to the phone.
Just use MTP over USB or the FTP server built into MIUI's File Explorer over WiFi (File Explorer->Categories->FTP).
Click to expand...
Click to collapse
Can I flash via TWRP instead?
I've read many threads that instructed to flash via TWRP,but as I read "wipe" part,I'm always confusing.

mumiji-lo said:
*Sorry for bad english
If your phone is rooted, you can cut/remove your thermal config in this path
/etc/thermal-engine-8996.conf
Becareful, it will raise your cpu heat upto 64°C
But your cpu freq will be stable @2,1 Ghz and Gpu @624 Mhz
Click to expand...
Click to collapse
Thanks a lot!

Nhutlong010 said:
Can I flash via TWRP instead?
I've read many threads that instructed to flash via TWRP,but as I read "wipe" part,I'm always confusing.
Click to expand...
Click to collapse
You do not have to wipe internal storage. Selecting wipe /data will not wipe /data/media (internal storage), so you can still store your ROM file in internal storage and flash it in TWRP after wiping /data, /cache and /system, which is the usual wiping procedure anyway. Or you could choose to ADB sideload it from your PC, but you still require TWRP.

NightRaven49 said:
You do not have to wipe internal storage. Selecting wipe /data will not wipe /data/media (internal storage), so you can still store your ROM file in internal storage and flash it in TWRP after wiping /data, /cache and /system, which is the usual wiping procedure anyway. Or you could choose to ADB sideload it from your PC, but you still require TWRP.
Click to expand...
Click to collapse
So all I need to do is put file rom,backup,.etc.. To /sdcard then wwipe cache,system,davik cache to flash things?
Are you SURE about it?
?

Nhutlong010 said:
So all I need to do is put file rom,backup,.etc.. To /sdcard then wwipe cache,system,davik cache to flash things?
Are you SURE about it? ?
Click to expand...
Click to collapse
Yes, the ROM file and backup will stay in /sdcard. Then you can proceed to wipe system, cache, dalvik and data in TWRP -> Wipe -> Advanced Wipe. Just make sure not to select internal storage for wiping. And I'm sure because I've flashed several ROMs without incident.

NightRaven49 said:
Yes, the ROM file and backup will stay in /sdcard. Then you can proceed to wipe system, cache, dalvik and data in TWRP -> Wipe -> Advanced Wipe. Just make sure not to select internal storage for wiping. And I'm sure because I've flashed several ROMs without incident.
Click to expand...
Click to collapse
Thanks a lot bud!

the problem is miui roms
just go with rr or linos roms

Edit: Sorry guys, wrobg thread...

How do I erase everything on galaxy s3 i747

Hi,
I have i747 that has a clockworkmod recovery. How do I erase as much as possible of everything so that my phone is as clean as possible before I install a new ROM on galaxy s3?
I tried to factory reset phone, did all the 'delete/erase' options within clockworkmod recovery (except advanced section) and yet I see some residual folders from the previous installation. is there a way to completely erase wipe out everything without bricking the phone?
Thanks!

user-747 said:
Hi,
I have i747 that has a clockworkmod recovery. How do I erase as much as possible of everything so that my phone is as clean as possible before I install a new ROM on galaxy s3?
I tried to factory reset phone, did all the 'delete/erase' options within clockworkmod recovery (except advanced section) and yet I see some residual folders from the previous installation. is there a way to completely erase wipe out everything without bricking the phone?
Thanks!
Click to expand...
Click to collapse
You should really flash TWRP recovery before proceeding. CWM hasn't been maintained or updated in a long time. It is likely to give you problems flashing anything new.
To completely blank a phone in TWRP I use Wipe -> Advanced Wipe -> Dalvik, Cache, System, Data. Followed by Wipe -> Format Data then type "yes" to confirm; always a good idea if you're switching between Touchwiz and AOSP in particular. That will leave you with totally blank internal storage. You'll have to flash a ROM from an external SD, or load a ROM zip over USB while booted in recovery because internal storage will be wiped clean.
It might be a good idea to look into what bootloader and modem you're running too. If you're still using CWM, you might be on pretty old firmware that isn't going to work right with newer roms. Just don't start flashing bootloaders/modems willy-nilly. Samsung made this phone kind of easy to hard brick on the newer firmwares. There's a right way to update it, if you find you have to.

jason2678 said:
You should really flash TWRP recovery before proceeding. CWM hasn't been maintained or updated in a long time. It is likely to give you problems flashing anything new.
To completely blank a phone in TWRP I use Wipe -> Advanced Wipe -> Dalvik, Cache, System, Data. Followed by Wipe -> Format Data then type "yes" to confirm; always a good idea if you're switching between Touchwiz and AOSP in particular. That will leave you with totally blank internal storage. You'll have to flash a ROM from an external SD, or load a ROM zip over USB while booted in recovery because internal storage will be wiped clean.
It might be a good idea to look into what bootloader and modem you're running too. If you're still using CWM, you might be on pretty old firmware that isn't going to work right with newer roms. Just don't start flashing bootloaders/modems willy-nilly. Samsung made this phone kind of easy to hard brick on the newer firmwares. There's a right way to update it, if you find you have to.
Click to expand...
Click to collapse
Thanks so much for providing such a detailed answer!! You make many very good points!!
Just to reflect on those...
1) Yes, CWM recovery has not been updated for about 2-3 years. I have 6.0.4.7 version. Where do I check how stale it really is? I tried googling for CWM recovery and saw tons of links with everyone talking about CWM but ZERO sites with actual CWM .zip or .img file
2) I did 'adb bugreport' and was able to find information on my bootloader and a modem:
Bootloader: I747UCUEMJB
Radio: I747UCUEMJB
I am not too sure for what I would need to use this information for though
3) when completely blanking the phone (doing all those wipe/erase actions you mentioned), would that erase the recovery as well or is recovery is kept on a some other partition that never gets touched
4) When installing TWRP over CWM, would TWRP override CWM or install side to side along with CWM?
Thanks!

The will need to run an updated bootloader and modem before installing the latest custom roms.

user-747 said:
2) I did 'adb bugreport' and was able to find information on my bootloader and a modem:
Bootloader: I747UCUEMJB
Radio: I747UCUEMJB
I am not too sure for what I would need to use this information for though
3) when completely blanking the phone (doing all those wipe/erase actions you mentioned), would that erase the recovery as well or is recovery is kept on a some other partition that never gets touched
4) When installing TWRP over CWM, would TWRP override CWM or install side to side along with CWM?
Thanks!
Click to expand...
Click to collapse
3 - Those wipes will just blank /system, /data and other partitions that would affect a rom. More critical areas like bootloader, modem, and recovery will remain untouched and intact.
4 - TWRP will overwrite CWM in the /recovery partition. They can't coexist.
2 - If you're comfortable with Odin, this thread might be the easiest and safest way to get updated. The Odin tar will get you up to NE4 firmware that should work with all the newest roms. Before modding, you could check for updates a few times in that stock rom. There should be two, one from NE4 to NJ1, and one NJ1 to NJ2. NJ2 is the newest and almost certainly last update for the i747.
If you don't like using Odin, there are recovery flashable zips to update the firmware for i747 too. You just have to be very careful how you go about it or you can brick the phone.

audit13 said:
The will need to run an updated bootloader and modem before installing the latest custom roms.
Click to expand...
Click to collapse
I was able to install the most recent octos just a few days ago with my stale configuration: old bootloader and old cwm recovery. My phone i747 currently has nougat.
When you speak of 'latest roms' what exactly do you have in mind?

jason2678 said:
3 - Those wipes will just blank /system, /data and other partitions that would affect a rom. More critical areas like bootloader, modem, and recovery will remain untouched and intact.
4 - TWRP will overwrite CWM in the /recovery partition. They can't coexist.
2 - If you're comfortable with Odin, this thread might be the easiest and safest way to get updated. The Odin tar will get you up to NE4 firmware that should work with all the newest roms. Before modding, you could check for updates a few times in that stock rom. There should be two, one from NE4 to NJ1, and one NJ1 to NJ2. NJ2 is the newest and almost certainly last update for the i747.
If you don't like using Odin, there are recovery flashable zips to update the firmware for i747 too. You just have to be very careful how you go about it or you can brick the phone.
Click to expand...
Click to collapse
I am actually quite familiar with Odin. I used to root i747 with it. Then I wanted to update to the latest official rom and ironically soft-bricked the phone to the point where it was dead...nothing worked at all. If I remember correctly I wrote i9305 Rom to i747 phone. Then I found out that during boot the phone internally still scans through sd card and was able to take advantage of that to install recovery and consequently cyanogenmod os. I remember tons of Adb done. Since then the phone regained all functionality and now works very smooth with freshly installed octos. However, I see I am missing some hard drive space ie unusually large usage by octos. This makes me wonder if the 'bad original partition + bootloader +modem' are still in there but not invoked for some reason and the explanation behind my what appears to be successful installs is working os, etc are written to a separate partition which is now invoked. Is this hypothesis legit or not real? Is it at all possible that my cwm somehow is installed on a partition that is delete-able or that cannot be a possibility and all recovery goes into write-protected space?
And while we are in this topic, what are the obvious advantages of a newer boot loader if I can still install whatever custom roms?

user-747 said:
I was able to install the most recent octos just a few days ago with my stale configuration: old bootloader and old cwm recovery. My phone i747 currently has nougat.
When you speak of 'latest roms' what exactly do you have in mind?
Click to expand...
Click to collapse
Sometimes, a phone will not display the correct imei with the latest custom ROM unless the phone is running the most recent bootloader and modem for the particular phone.

audit13 said:
Sometimes, a phone will not display the correct imei with the latest custom ROM unless the phone is running the most recent bootloader and modem for the particular phone.
Click to expand...
Click to collapse
Thanks! Good to know.

I think this phone only has a 12 GB data partition. About 1.5 GB is reserved for /system, another 1 GB for /cache, and there are a host of other partitions. That's some of your used space. The rest could be cruft from old installs left over in userdata that a standard wipe of /data didn't get unless you format internal storage.
If what you have is working for you, then I wouldn't touch bootloader and modem.

jason2678 said:
You should really flash TWRP recovery before proceeding. CWM hasn't been maintained or updated in a long time. It is likely to give you problems flashing anything new.
To completely blank a phone in TWRP I use Wipe -> Advanced Wipe -> Dalvik, Cache, System, Data. Followed by Wipe -> Format Data then type "yes" to confirm; always a good idea if you're switching between Touchwiz and AOSP in particular. That will leave you with totally blank internal storage. You'll have to flash a ROM from an external SD, or load a ROM zip over USB while booted in recovery because internal storage will be wiped clean.
It might be a good idea to look into what bootloader and modem you're running too. If you're still using CWM, you might be on pretty old firmware that isn't going to work right with newer roms. Just don't start flashing bootloaders/modems willy-nilly. Samsung made this phone kind of easy to hard brick on the newer firmwares. There's a right way to update it, if you find you have to.
Click to expand...
Click to collapse
jason2678 said:
I think this phone only has a 12 GB data partition. About 1.5 GB is reserved for /system, another 1 GB for /cache, and there are a host of other partitions. That's some of your used space. The rest could be cruft from old installs left over in userdata that a standard wipe of /data didn't get unless you format internal storage.
If what you have is working for you, then I wouldn't touch bootloader and modem.
Click to expand...
Click to collapse
Thanks for the insight!
I went ahead and updated by recovery to TWRP via Odin just a few minutes ago...
I see Under Advanced Wipe another option for Wipe -> Advanced Wipe -> Internal Storage. Should I also wipe out internal storage? What is it for anyway? Whats the difference between 'internal storage' and 'system'?

user-747 said:
Thanks for the insight!
I went ahead and updated by recovery to TWRP via Odin just a few minutes ago...
I see Under Advanced Wipe another option for Wipe -> Advanced Wipe -> Internal Storage. Should I also wipe out internal storage? What is it for anyway? Whats the difference between 'internal storage' and 'system'?
Click to expand...
Click to collapse
Honestly I'm not 100% sure what the Internal Storage wipe does under Advanced Wipe, and I don't feel like making then restoring a backup right now just to test it . I never use it. If I had to guess, I bet it wipes /data and possibly a few other partitions without preserving user files in /data/media/0, see below, but don't know that. It certainly won't blank the whole internal storage; some areas like recovery, modem, and aboot are far too important and won't be touched.
Here's what I can tell you. Doing Wipe -> Advanced Wipe -> system, data, cache, dalvik is typically good enough for flashing a new rom (switching from Touchwiz to AOSP can require some additional care), some would even say overkill the way rom installers are scripted today, but old habits die hard. However, Advanced Wipe -> Data will wipe /data without wiping /data/media. Since android got multi-user support, files reported to be in /sdcard are actually stored in /data/media/0 for the primary user, so that means that downloads, pictures, user app files and things like that can be left behind by just wiping data since /data/media is left untouched. It is useful if you don't want to shuffle your files off then back on the device to flash something new or if you're using a device without an external SD and have a rom zip stored on device in /sdcard, but it leaves stuff behind if you're looking for a clean start.
To completely blank /data pick Wipe -> Format Data and TWRP will format /data and leave nothing behind, not even /data/media like the normal Advanced Wipe -> Data preserves. Just make sure you're prepared for the phone storage to be blank. You'll have to flash from external SD or push files from a computer over usb. TWRP does automatically start up mtp and adb shortly after booting if you need to push files over usb.
/system is a partition of special reserved space just for the rom and system apps and not user files. It is usually mounted read only when booted up normally to keep us from messing anything important up. I hope this helps and doesn't just muddy the waters more.

jason2678 said:
Honestly I'm not 100% sure what the Internal Storage wipe does under Advanced Wipe, and I don't feel like making then restoring a backup right now just to test it . I never use it. If I had to guess, I bet it wipes /data and possibly a few other partitions without preserving user files in /data/media/0, see below, but don't know that. It certainly won't blank the whole internal storage; some areas like recovery, modem, and aboot are far too important and won't be touched.
Here's what I can tell you. Doing Wipe -> Advanced Wipe -> system, data, cache, dalvik is typically good enough for flashing a new rom (switching from Touchwiz to AOSP can require some additional care), some would even say overkill the way rom installers are scripted today, but old habits die hard. However, Advanced Wipe -> Data will wipe /data without wiping /data/media. Since android got multi-user support, files reported to be in /sdcard are actually stored in /data/media/0 for the primary user, so that means that downloads, pictures, user app files and things like that can be left behind by just wiping data since /data/media is left untouched. It is useful if you don't want to shuffle your files off then back on the device to flash something new or if you're using a device without an external SD and have a rom zip stored on device in /sdcard, but it leaves stuff behind if you're looking for a clean start.
To completely blank /data pick Wipe -> Format Data and TWRP will format /data and leave nothing behind, not even /data/media like the normal Advanced Wipe -> Data preserves. Just make sure you're prepared for the phone storage to be blank. You'll have to flash from external SD or push files from a computer over usb. TWRP does automatically start up mtp and adb shortly after booting if you need to push files over usb.
/system is a partition of special reserved space just for the rom and system apps and not user files. It is usually mounted read only when booted up normally to keep us from messing anything important up. I hope this helps and doesn't just muddy the waters more.
Click to expand...
Click to collapse
Thanks!
I will try to do wipe and reinstall Rom tonight and will update this thread. While we are in this topic, when flashing twrp via Odin in phone's download mode, I noticed that it says: Qualcomm secureboot: enabled. Does this mean my bootloader is locked?

user-747 said:
Thanks!
I will try to do wipe and reinstall Rom tonight and will update this thread. While we are in this topic, when flashing twrp via Odin in phone's download mode, I noticed that it says: Qualcomm secureboot: enabled. Does this mean my bootloader is locked?
Click to expand...
Click to collapse
No, the i747 never had a locked bootloader. You couldn't boot unsigned stuff like CWM, TWRP, or octos if it did.

jason2678 said:
No, the i747 never had a locked bootloader. You couldn't boot unsigned stuff like CWM, TWRP, or octos if it did.
Click to expand...
Click to collapse
Thanks!

user-747 said:
Thanks!
I will try to do wipe and reinstall Rom tonight and will update this thread. While we are in this topic, when flashing twrp via Odin in phone's download mode, I noticed that it says: Qualcomm secureboot: enabled. Does this mean my bootloader is locked?
Click to expand...
Click to collapse
I went ahead and did all the wipes and formats you recommend and all worked like a charm. OctOs installed like a charm, my disk space is regained, gapps are working, IMEI is good. so far I cannt find anyting that does not work. Thank you @jason2678 for your valuable feedback on my questions!!