Database Info

[ROM]DocHoppyRom NEXTBOOK 7 Premium*updated DocHoppyRom Full On Rootv2.0*2/14/2012

I was working on a ICS based hoppy rom. Unfortunately I just had a catastrophic screen failure, apparently when my laptop bag fell last night, it landed with enough force to shatter the screen on my nextbook! Oh well. it may be a while before I can work on anything to further the version I was working on.
FYI- Due to work, my time is very limited for working on the next version of Hoppy Rom. I apologize in advance. The company I work for is
setting up new engine test cells in China, and my self and 2 other people are main points of support! again Sorry for anything new taking so long!
DOCHOPPY HAS BEEN SIGHTED (Other than on a DAYZ server...Stay tuned.
Ok I have decided to pass along what I have been working on.
Warning***
This is for the Nextbook 7 premium ONLY!
Known working on Nextbook 7 premium tablets with serial numbers starting:YF1011
DocHoppy Presents!
DocHoppyRom Full On Root v2.0
and
DocHoppy Cramfs Style 3.0
Based off the official update image released by nextbook.
Major thanks to FINLESS BOB!!! GREAT HELPFUL GUY!
PRESENTING DOC HOPPY ROM
CRAMFS STYLE 3.0
AND
FULL ON ROOT v2.0
Disclaimer: I am not responsible for Bricked Tablets. This is known to work on tablet with SN starting with YF1011, and some YF1211.
First you will need to decide which version of the Rom you are going to load. The CRAMFS Style version has SU but you CANNOT write to the /system directory. This is a good all around Rom for those who may need SU but do not need to write to /system.
Full On Root is just that, you have full read write to the /system and can customize the Rom to your hreats content.
HOW TO INSTALL:
TO FLASH CRAMFS STYLE 3.0 Put the UPDATE.IMG file from the Cramfstyle Folder onto your SD card, while tablet is on and follow the on screen instructions.
After running the self extracting Zip file you will have a directory containing the following folders and files.
Drivers (folder)
CramfsStyle(folder)
FullonRoot(folder)
Log(folder)
Language(folder)
Readmefirst.txt
Rkusb.log
RkusbComm.dll
Setting.ini
RK29update.exe
TO FLASH CRAMFS STYLE 3.0 Put the UPDATE.IMG file from the Cramfstyle Folder onto your SD card, while tablet is on and follow the on screen instructions.
To flash Full On ROOT, Plug your nextbook into your PC via usb cable. Turn your nextbook over and with a safety pin or something of similar size, press and hold the reset button for 2 to 3 seconds.
Run the RK29update.exe
Select your Rom files via the boxes containing the .... And navigate to the correct directory for the rom you want to install.
Insert eache file in order according to the update tool.
Clear IDB. (this is like a lowlevel format for the Rom tool:
After the Tool says OK. Select Run. This will begin to load the Rom onto your tablet. It will go through loading and then checking the Rom install.
After the Rom loads and the tool comes back with an OK, patiently wait for the tablet to reboot, and load the new ROM. If the tablet is still connected to the pc via USB when the rom boots it will show the screen allowing you to select weather or not to turn on USB storage. Press the home key and you will be given a choice of Golauncher or Rklauncher. (go lock is a screen lock program.)
Enjoy the Rom!
Disclaimer: I am not responsible for Bricked Tablets. This is known to work on tablet with SN starting with YF1011, and some YF1211.
Features for both Roms:
Complete and correctly working market. It now correctly associates the tablet to your gmail account allowing purchases from market.
Launcher 3.0 as well as Go launcher ex. Launcher 3.0 was pulled from an rk2918 firmware3.0 update and put into this rom.
Google Calendar is now back and working correctly.
Original Email is back and working correctly.
Included Kindle App
Included Estrongs file explorer.
Both have SU though the Cramfs version cannot write to SW.
Removed Apps Added in last release and return to more of a original rom state.
Rom is pretty clean. And seems speedy.
Cramfs Style 3.0 Rom has 200mb internal Ram +/-
Full On Root 2.0 has 894MB of Free Internal Ram.
Cheers!
DocHoppy
www.freaktab.com
Keep in mind this is the first version of this ROM. There will be updates and changes made.
FUTURE CHANGES:
Custom Theme Changes.
More Tweaks to the system.
Long Term Wants:
Power Menu change to include recovery boot.
Power Menu change to include restart.
This is a work in progress.
Known working on Nextbook 7 premium tablets with serial numbers starting:YF1011
Linked here for image.
Non Add Showing Link.
DocHoppyFullOnRoot2.0
New Cramfs style Rom is still Available Here.
DocHoppyCramfsstyle3.0
To install DocHoppyRomv3.0, rename .img file to update.img, download update.img file, copy to SD card, and follow the prompt.
DocHoppyCramfsstyle3.0
Enjoy.
Disclaimer:
Not responsible for bricked tablets.
Enjoy!
Also visit www.freaktab.com

So freaking sweet, great work on RW!

I used Wendal's tool to decompress the cramfs file system.
As for the /system, Because the device uses cramfs, and based on everything I have read, using Wendal's tool to decompress the file system, make the changes, and compress is the only way I can see to be able to
customize the rom for the device. The image is rooted, but after the update.img is compressed, the /system file remains read only. I tested this using root explorer, but anything requiring su works fine. But all hope may not be lost, I was reading on a chumby forum someone suggested using mkfs.jffs to make it writable, but further down it notes that you would need to change the kernel (easy enough to recompile I think), to utilize a different file system. The boot loader would also need to be modified, something I am not ready to try and tackle just yet, I think I would be bricking my nextbook pretty quickly.
It is a start and I am actually learning a lot as I go.
Any thoughts or suggestions are welcome.

I am definitely a long time user / cyanogenmod / aosp fan, but as far as ripping open .img files its definitely new territory, I tried to find an internal SD card like the nook has, to maybe dump it, but I cannot find such a beast. Any progress you make is awesome. So do things like root explorer work, just not on /system due to cramfs?

Correct, root explorer does work, but due to cramfs, it does not allow you to toggle to rw from ro on the /system.
Working on taking apart apk's and customizing and rebuilding and resigning next.

just flashed this rom and it works great!
How would I go about doing a custom boot animation or image?
... even if it means flashing a new rom from clean?

This is great. Thanks. The only question I have is why do I see so few items in Market? Does it have anyhting to do with compatability?

Calendar & Sync Access
First, thank you for your work.
Before I update by Next7P, have you included Google Calendar and Sync access in this update?
I use MyPhoneExplorer and will need calendar sync to work so I can fully use for business.
Thanks.
There is another method to get Google Market on the Next7P, I am a new user so I can not post the link, but google , forums Whirlpool net au archive 1756859
, very easy and works great, but cannot get sync to work.
Dan,

Thanks for the responses!
sgtfoo : You can use Wendal's rk29xx tool to take a copy of my rom image, or the original update downloadable from nextbookusa.com, and
unpack it. You then have access to the system directory in an editable format. you can go into the system folder /system/media and replace the bootanimation.zip file with another one. Just be sure the image format is 480x 800 and that the zip file has 0% compression ratio. After you make the changes, just repack .img file via Wendal's tool and reflash.
dodoclub : Not sure why. I have a full market. You might try clearing the data and cache for the market. My market shows pretty full, I.E. I got 31050 entries when I searched for facebook in the market.
Danno65: Actually that is something I have been working on. I can get my google calendar to sync, currently I am using a calendar from the market called Jorte, which works great, how ever, googles actual calendar.apk closes unexpectedly, I am thinking it is just a version problem with the calendar, but haven't had a lot of time to follow up on it.
FYI here is the link to Wendal's tool, which makes it much easier to work on the update.img file.
https://docs.google.com/leaf?id=0B8hUXYDeoy_hNTc1YTVkYTMtNTNjZS00YjI2LTgyNDYtYjRjZjFmODdiZTQ1&pli=1
Cheers!
If you have any request or questions please feel free to ask, I will help anyway I can.

Thanks Dochoppy
Got one of these tablets for Christmass to replace an old broken tablet I use for work.
Google hosts our work email, so I still need to get Contacts and Appointments going, but I maybe able to side load them.
Noticed build.prop still has ro.secure=1. This prevents adb from having root access??

Calendar & Sync Access
DocHoppy,
I came across a post where the "Calendar.apk" and "CalendarProvider.apk" files must be in the "system/app" directory to work properly, I tried to copy these files to the above directory but found it to be read/only, will wendalls tool have to be used to get access to the directory?
Also, did you get your google calendars on your desktop to sync with Jorte on the Next7P, I tried but no luck.
Thanks
Dan
The updated image file worked great, thanks again

Thank you so much for your work in building a new rom for this thing. I am anxiously awaiting a new filesystem so we can have true root. How do we manage to recompile the kernel for ext4 support and change the /system fs?

Hello, first of all, thanks for your work!
I am having trouble loading this rom. it says there's an invalid image file in my sd card and if I want to delete.
Now, I don't know if my tablet is a never or older version of what you guys have...
Next7p
2.3.1
kernel: 2.6.32.27
build: v2.0.7.....
my serial is also different from alot..it starts with YF0511
any help or tips?

markmatters said:
Hello, first of all, thanks for your work!
I am having trouble loading this rom. it says there's an invalid image file in my sd card and if I want to delete.
Now, I don't know if my tablet is a never or older version of what you guys have...
Next7p
2.3.1
kernel: 2.6.32.27
build: v2.0.7.....
my serial is also different from alot..it starts with YF0511
any help or tips?
Click to expand...
Click to collapse
I would say the serial number would have something to do with it, check on the site for nextbook and see if your serial is in the same *batch* as ours, if the original serial is in a different group, im assuming the hardware may be slightly different? If so, you can always use his method to repack the original with root.

First off I would like to say that I was very pleased when I came across this thread from another one. I haven't flashed this ROM yet, but plan to. Thank you for your work on this as I have been searching the whole internet since I got this thing [4 weeks now] for some sort of custom ROM. It is hard to use this tablet when I have ICS on my Captivate and Vibrant. GB just isn't as cool.
One thing I hope we can work on is root access, so we then can use Titanium Backup. Then we won't have to manually reload everything when new releases come out.
With all that being said, if there is anything I can do to help, I would love to. Like I said, I plan on flashing this probably tomorrow or Tuesday. Thanks again.

For the record, I got titanium backup working fine on this rooted rom. it is capable. You just need to reboot after it restores a backup.

i'm new to android. glad to see rooted rom finally, keep it up!!!
i have a clarification, any improvement in the booting time? my device took 1min30sec (power ON to ready to use, for me, 90sec seem like not fast enough).

Good luck on improving boot time. And besides a tablet is best used when on all the time... try using the suspend state to quickly wake it. We're just starting with the early versions of this rom... give it time to grow.
Sent from my N7p using XDA App

Build.prop editing
Okay so observation:
Our tablet is not recognized as a "tablet" by the Android market, only and android device.
What prop would I have to edit in order to have us recognized as I tablet. I noticed this when:
I finally managed (through some internet tutorial before this rom) get the market working (the first version, not 3.1+). And when I downloaded apps (I'll use Minecraft Pro as an example) I noticed that the way mine looked and the way the tablet version looked via android market photos and Youtube, ours looks like an enlarged phone version rather than a tablet optimized version. What can I edit to fix this?

Flashed this today... so for it works great. Love the new boot animation. Great work and can not wait for future releases!
Sent from my Nextbook Premium 7 (Doc Hoppy's Rom v02) from the XDA app.
---------- Post added at 12:16 PM ---------- Previous post was at 12:03 PM ----------
One thing that would be great on a future release [not sure if it is possible yet with out r/w], would be a bigger data partition for apps. Moving everything large to the SD is ok, just takes longer to boot those apps. A kernel that would allow voltage control app [like CPU Master] to work also. Just a thought!

[ROM] Custom Rom For ChaCha - GB

Hello everyone!
Finally, I am satisfied with my chacha. I was constantly shifting between stock custom rom and cm roms. In stock rom everything works but automatic backlight settings are just terrible (especially dim threshold and keyboard light settings) and status bar is bigger than in cm roms (32px vs 25px). Cm roms have all of this but there are other things that still need improvement (front cam, some stability issues etc.). Therefore I decided to create my own mod of stock rom. It is based on Europe RUU 1.3.3 android 2.3.3. I couldn’t find anywhere 2.3.5 Europe rom but to be honest I don’t see any difference between the two. There are two versions:
1. Full sense rom: Link
What is different: rooted, added busybox, support init.d, dta2sd included (you need to partition your sd to ext2 or ext3 after installation and enter dta2sd commands from terminal emulator – google for the commands if you don’t know them), changed the ugly calculator app, added file explorer, added latest play store, Flash player 11 is working. I haven’t removed any apps because in this version I wanted to leave that to the user according to his/her own preferences. Status bar is smaller (more space on the screen) and I themed it a little, removed charging icon (I know that it is charging because phone’s led is orange ). Automatic brightness is tweaked (added lower brightness level, lowered the max brightness of the f button, and added one level for the keyboard lights (sometimes, in stock roms, I couldn’t see my keyboard clearly and the damn lights just wouldn’t turn on so I had to do this tweak as well). And rom is fully deodexed.
2. Stripped rom (no sense): Link
What is different: rooted, added busybox, support init.d, dta2sd included (you need to partition your sd to ext2 or ext3 after installation and enter dta2sd commands from terminal emulator – google for the commands if you don’t know them), changed the ugly calculator app, added file explorer, added latest play store, removed sense, added widget locker, holo launcher, removed a lot of bloatware (at least, bloatware for me), f button is not assigned (I’ll leave that to the user, I use it to turn my screen off but didn’t changed it to this since several people reported issues). Same automatic backlight and status bar tweaks like in the sense rom and it is also deodexed.
3. Stripped rom (odexed): Link
What is different: Same as in stripped rom with the exeption of these: odexed (now 120mb free out of the box), status bar icons have an ICS look and color (wifi, signal, data, bluetooth etc.), notification toggles app added (fully functional and works great, just in the settings set it as an on-going notification and as old in order to be always on top; it has many different icons and styles and colors are changable as well, really nice app), fb button is set to turn screen off, dta2sd not included, different backlight values.
Automatic backlight and status bar tweak for odexed version: Link
Automatic backlight and status bar tweak (sense and stripped deodexed): Link
Flash Player 11: Link
Instructions:
1. Reboot into recovery; wipe data/factory reset; mounts and storage/format system; install from sd card; choose and install your rom; reboot your phone; finish your first boot setup.
2. Reboot into recovery; install from sd card; choose and install backlight.zip; reboot your phone.
3. Install flash player apk; reboot phone.
That’s it. Hope that someone will like it.
Sorry for the poor screenshots.
Regards
P.S. I am not going to support these mods. Everyone is invited to use them and do with them whatever you want. So please don’t ask me does it support this, does it support that, can you do this, can you do that. For me, it is perfect and I don’t need to do or change anything. Everything is working for me. I just wanted to share it with you. I hope that you can understand this.
Edit: I used this guide (thanks kylon) to improve wifi signal range and it worked for me, so I am going to share these settings with you. Mke sure you do this with your WiFi off. Here is what you have to do:
1. Copy your calibration file (found in proc in the root of your phone) to the sd card (it is best to do all steps with root explorer) and download from the attachments framework.jar (here is a link for an odexed version - extract jar and odex files) and symlinkv2.zip.
2. Move the calibration file to system/etc and set permissions as they are set in the screenshot.
3. Reboot into recovery and install symlinkv2.zip.
4. Open calibration file in system/etc (again, best with root explorer) and change this line: rssi_offset=0 into this: rssi_offset=-30
Delete created bak file if you are using root explorer.
5. Copy downloaded framework.jar (I already modified it according to the offset - 30, and if you are using odexed version copy both jar and odex files) to system/framework and set permissions according to the screenshot. Reboot your phone.
6. Done.
This trick did wonders for me and my wifi, hope it will help you as well. If it doesn't, try different values both in calibration file and framework.jar according to the original thread.
Cheers.

Looks noice
Is it faster/smoother than the stock rom? I would go back to the stock rom if it wasn't so hard to configure and it wasn't so damn sluggish compared to CM7/CM9.

ethancottier said:
Looks noice
Is it faster/smoother than the stock rom? I would go back to the stock rom if it wasn't so hard to configure and it wasn't so damn sluggish compared to CM7/CM9.
Click to expand...
Click to collapse
Every rom that I use is fast enough for me. Even the unmodified stock. I just wanted to get rid of some apps that are obsolete for me, and I needed to improve backlight settings because when it is night the original settings don't dim the lights enough which really hurts my eyes and I hate that because I have to manually dim. In this rom I don't have that issue. Lights dim automatically.
Although, I found out today that there is an issue with the dta2sd, or maybe the kernel itself. DTa2sd moves my apps and dalvik to sd-ext, clockworkmod creates a backup of sd-ext in a backup folder, and when I restore it my rom just will not mount my sd-ext on boot after that, thus I need to do a fresh install. I would appreciate if someone has an idea why this happened? It is not an issue for me, since I am going to use this rom for a while, but I would like to fix it for the others. When I don't use dta2sd there are no issues. I looked in init.rc in ramdisk, but couldn't find anything unusual. This happened to me with Void rom as well, so I really don't know where to start regarding this.
Regards
Edit: I have been using recovery for a different phone. I just realized this and now, with the proper recovery, everything is restoring fine.

didije said:
Every rom that I use is fast enough for me. Even the unmodified stock. I just wanted to get rid of some apps that are obsolete for me, and I needed to improve backlight settings because when it is night the original settings don't dim the lights enough which really hurts my eyes and I hate that because I have to manually dim. In this rom I don't have that issue. Lights dim automatically.
Although, I found out today that there is an issue with the dta2sd, or maybe the kernel itself. DTa2sd moves my apps and dalvik to sd-ext, clockworkmod creates a backup of sd-ext in a backup folder, and when I restore it my rom just will not mount my sd-ext on boot after that, thus I need to do a fresh install. I would appreciate if someone has an idea why this happened? It is not an issue for me, since I am going to use this rom for a while, but I would like to fix it for the others. When I don't use dta2sd there are no issues. I looked in init.rc in ramdisk, but couldn't find anything unusual. This happened to me with Void rom as well, so I really don't know where to start regarding this.
Regards
Click to expand...
Click to collapse
I don't know about data2SD, but I use link2SD, and that works perfectly but with the stock rom, you have to format the sd-ext partition in ext2 rather than ext4, and you can't do it with clockworkmod either, cos it doesn't format it properly :/ you have to use a tool like gparted (if you're a linux user) or some windows/mac equivalent to format it properly

Wow that does look pretty nice.thanks man.

ethancottier said:
I don't know about data2SD, but I use link2SD, and that works perfectly but with the stock rom, you have to format the sd-ext partition in ext2 rather than ext4, and you can't do it with clockworkmod either, cos it doesn't format it properly :/ you have to use a tool like gparted (if you're a linux user) or some windows/mac equivalent to format it properly
Click to expand...
Click to collapse
Link2sd works well. Just tested it. Thanks! I don't have the time to look deeper into the issue with dta2sd..

john9 said:
Wow that does look pretty nice.thanks man.
Click to expand...
Click to collapse
Thank you. In a couple of weeks I will tweak the backlight settings little more, and maybe build a similar 2.3.5 rom (if I find a RUU).
Cheers

Stripped with full stock Facebook Button Functionallity
Great work. This is a solid setup. Thanks for the hard work.
I appreciate that you left the F-Button unassigned for the end user, but is there a way to get back to stock functionallity using your Stripped Rom?
Thank you.

maxwellsk said:
Great work. This is a solid setup. Thanks for the hard work.
I appreciate that you left the F-Button unassigned for the end user, but is there a way to get back to stock functionallity using your Stripped Rom?
Thank you.
Click to expand...
Click to collapse
Unzip Stripped Rom, add attached apks to system/app and attached chacha-keypad.kl (unzip the keypad file) to system/usr/keylayout. Zip it and flash it. Let me know if it works.
Cheers.

didije said:
Unzip Stripped Rom, add attached apks to system/app and attached chacha-keypad.kl (unzip the keypad file) to system/user/keylayout. Zip it and flash it. Let me know if it works.
Cheers.
Click to expand...
Click to collapse
Thank you so much for the exceptionally quick response. Unfortunately I ran into an error. Let me walk you through what I did.
1. Dowloaded Sripped Rom, and all the files in the previous post.
2. I unzipped the Rom on my desktop
3. I inserted each of the files in their respective folders
4. Zipped the Rom back up
5. Transferred to SD
6. Booted to Recovery mode and tried to flash.
Here is what I got ....
CWM-based Recovery v5.0.2.7
-- Installing: /sdcard/Stripped-Chacha_1-3-3.zip
Finding update package...
Opening update package...
Installing update ...
Installation aborted.

maxwellsk said:
Thank you so much for the exceptionally quick response. Unfortunately I ran into an error. Let me walk you through what I did.
1. Dowloaded Sripped Rom, and all the files in the previous post.
2. I unzipped the Rom on my desktop
3. I inserted each of the files in their respective folders
4. Zipped the Rom back up
5. Transferred to SD
6. Booted to Recovery mode and tried to flash.
Here is what I got ....
CWM-based Recovery v5.0.2.7
-- Installing: /sdcard/Stripped-Chacha_1-3-3.zip
Finding update package...
Opening update package...
Installing update ...
Installation aborted.
Click to expand...
Click to collapse
That is weird. I just tested it, and it worked for me. Maybe you zipped it with high compression or sth. Try with normal compression. If that doesn't work, I will upload zip for you later today. I use recovery 5.0.2.8, but I don't think that it matters.
Edit: Here is the link - Link

Flash Player Stopping
Stripped down ROM is great - now have more room for downloading apps.
One problem I've come across on this ChaCha is that Flash Player stops working (returns to home screen) after around 2 seconds of playing anything.
Anyone else had a similar problem?

didije said:
That is weird. I just tested it, and it worked for me. Maybe you zipped it with high compression or sth. Try with normal compression. If that doesn't work, I will upload zip for you later today. I use recovery 5.0.2.8, but I don't think that it matters.
Edit: Here is the link - Link
Click to expand...
Click to collapse
That got it! I'm sooooo happy!!! Thanks!! It is perfect!!

maxwellsk said:
That got it! I'm sooooo happy!!! Thanks!! It is perfect!!
Click to expand...
Click to collapse
That's great. Glad I could help.
Regards
scgellion said:
Stripped down ROM is great - now have more room for downloading apps.
One problem I've come across on this ChaCha is that Flash Player stops working (returns to home screen) after around 2 seconds of playing anything.
Anyone else had a similar problem?
Click to expand...
Click to collapse
As you can see from the screenshot below I don't have that issue. Try different flash player for armv6 devices. There are few, just google it.

dta2sd
Little suggestion. If you are planning to use this rom for a longer time, after your setup, copy your data from your sd card to your computer, go into clockworkmod recovery, in advanced options partition your sd card (I set sd-ext to 256, don't need more) and reboot. After that download terminal emulator from play store. In terminal type this:
su (then press enter and allow superuser permissions)
a2sd reinstall (enter and wait for your phone to reboot. It will take some time)
After it is booted enter this:
su (enter)
a2sd cachesd (press enter and wait for your phone to reboot. It will take some time).
The end result you can see in the attached screenshot. After installing all my apps I still have over 120mb free.
Of course, after everything is done copy your data back to sd card.
Regards

Added wifi tweak to the first post. It works for me, hopefully it will work for you as well.
Regards

languages included in europe rom
What languages are included in this ROM?
Thx!

Thanks for this rom, great daily use

Great Rom, Thank you!
This is the best ChaCha rom I have used so far. Everything works great super fast flash even works!
YouTube can play 240p with no lag, any higher and it will.
BBC iplayer crashes but I have yet to find a rom that bbc iplayer will work on when it comes to the ChaCha.

Perfect rom but can u create a RTL fix for arabic support ?
thanks.

[Guide] Supercharger V6 for everyone, make your phone faster

I wrote this guide for originally in elk759's JB CM10 thread, but with some modifications it works with every ROM and every phone.
I thought other guides were too hard to understand so I concluded all neccessary information and nothing more.
This guide is for Windows, because it uses a Windows tool to make the process MUCH easier. This only affects the modding of services.jar, so look at the original Supercharger thread for instructions withot the Windows tool.
Here are the benefits of using SUPERCHARGER, I cn approve that it works, it's faster, more apps can run and no launcher redraws!
___________________________________________________________________________
Sources:
http://forum.xda-developers.com/showpost.php?p=12058585&postcount=1
http://forum.xda-developers.com/showpost.php?p=18703418&postcount=5021
zeppelinrox said:
What's it do?
It makes your phone FAST... super snappy with better multitasking!
It rearranges and fixes the OOM Groupings and Priorites and lowmemorykiller values.
So basically, it's a COMPLETE MEMORY MANAGEMENT FIX!
It's the ONLY one of it's kind
NO LAUNCHER REDRAWS, faster than ever, multitasking is better... why?
Because it works with the lowmemorykiller and letting it work the way it's meant to work.
Also, because of the rearrangement, it works the same on all roms!
The problem with using minfree tweakers like AMM or AKMO is that it doesn't work the same on all roms.
Secondary apps may be in slot 3 on some roms but in slot 5 in others!
That's why you hear people comment "I tried AKMO but it didn't do anything..."
Most likely it didn't do anything because the apps weren't sitting where they were expected to be.
So fasten your seat belts and enjoy the ride!
Click to expand...
Click to collapse
zeppelinrox said:
And -=Maximum Overdrive=- was born!
Upside: You can run up to 70 apps if you have enough RAM.
Downside: NONE
Click to expand...
Click to collapse
zeppelinrox said:
The Kick Ass Kernelizer
What Does The Kick Ass Kernelizer Do?
Memory Management++
MFK Calculator Info - explanation for vm.min_free_kbytes
LinuxInsight - The /proc filesystem documentation (Fantastic!)
XDA [REF] Startup script speed tweaks OP by hardcore
XDA Speed up your system with the noop scheduler
TCP Speed & Security
Security and Hardening the TCP/IP stack to SYN attacks
Click to expand...
Click to collapse
zeppelinrox said:
The 3G TurboCharger
In case of connection issues, see the notes in the 3G TurboCharger section at the top of /system/build.prop!
Homework/Background Info... see the folllowing links for resources used.
XDA Thread 1
XDA Thread 2
XDA Thread 3
Wi-Fi AfterBurner.
XDA Thread (Faster WIFI - N Standard Enabling)
The 3g build.prop tweaks aren't really anything new... but I did put a new spin on it! ;^]
You can find various individual configurations but as far as I know, my script is the only one that lets the user choose from more than one configuration.
Click to expand...
Click to collapse
___________________________________________________________________________
IF YOU HAVE ANY PROBLEMS, LOOK FIRST AT THE Q&A BELOW!
1. Prerequisites:
SuperCharger_Starter_Kit_xxx.zip (contins busybox, sqlite and zipalign)
[*]V6_SuperCharger_for_Android-Update9_RC11_xxx.sh.pdf
Script Manager for starting scripts (on first run enable root browse AND run every script with su rights, the skull and bones symbol)
ES File Explorer (with root rights in settings->root management)
optionally: Terminal Emulator
Recommended for everyone and REQUIRED for 4.0+ Roms:
pepcisko's Windows tool for patching services.jar
Place the V6_Supercharger script and the Supercharger_Starter_Kit.zip content to "/sdcard/V6"
Place the Windows tool somewhere on your Hard Drive
Install the required apps
2. Installation of Starter Kit:
Start SManager and confirm root rights when browsing
go to sdcard/V6/1_SuperCharger_Starter_Kit and click on StartMeUp.sh
select the SU button (skull + bones) and RUN it as script and follow the instructions (install at least busybox for being safe that everything works)
3. Patching services.jar
Background information (could be very useful):
Patching the services.jar gives you the multitasking mod. Apps shouldn't restart all the time, they will stay in RAM as long as they can.
Patching the services.jar is REQUIRED for Android 4.x.x, but you don't have to use multitasking mod.
For the other Android versions it isn't required, you only need this if you want to have multitasking mod, too.
If you have Sense 4.0+ and want multitasking mod, you have to follow this, more complex tutorial.
But you can also use this method, but your visible app limit stay at 8 Apps, instead of 50!
extract the Windows tool and launch it
You can choose between online mode (phone drivers needed) or offline mode, I'll explain offline mode:
make sure you have root rights in ES Explorer and that you mount system as R/W (read/writable)
copy the services.jar from /system/framework to your SD, and connect your phone to PC
move the services.jar to the framework folder of the Windows tool directory
in the windows tool specify your Android version + if the rom is odexed/deodexed
now press "enter" -> "y" for supercharge -> "enter" for die die-hard launcher -> "enter" -> "y" for multitasking -> "enter" -> "y" to delete temporary files
You have patched the services.jar, now you have two options (both files are in "dist" directory):
Place the update-signed.zip on sdcard and install it via recovery
OR
Place the modded services.jar (and if odexed rom the services.odex too) to /system/framework and overwrite. Then you have to set owner and permissions:
In Terminal Emulator
su
(confirm SuperUser Request)
busybox mount -o remount,rw /system
cd /system/framework
chown 0.0 services.jar
chmod 644 services.jar​
Now go into recovery (or stay there after flashing update-signed.zip) and wipe cache & dalvik cache.
On your next reboot apps should be optimized.​
4. Supercharger Installation
Remember: I can't promise, that the guide is always up to date. So it could happen that after an update of the script, the option numbers are different. Look at the text on the right side of the option
start the /sdcard/V6/V6_SuperCharger... script with SManager with SU rights
follow the instructions of driver options: You will be asked for Scroll Speed but also various tweaks which can improve the performance
The script calculates the preferred FreeMem size, you can use them or set your own prefered size:
After you have declined to use the calculated option you are in Driver's Console, you can choose between 33 options.
The Options 2 to 9 set the MinFree size, for the different Ram Size of the devices.
For the Desire I recommend option 6 which is called "balanced". You can try a lower or a higher option, too.
Lower values are better for Multitasking, higher values are better for the speed on the visible app.​
go back to driver options and type 21 for Nitro Lag Nullifier, confirm with N (could be unstable, you don't have to use this)
After you are finished press option 17 for Engine Flush and after that option 32 for SuperClean& Restart
After the restart you should open SManager again and navigate to /system/etc/init.d, click on S99SuperCharger and enable SU + Run on Boot.
Press Save. This should avoid issues if you want to launch Supercharger Script again (for me it worked without doing that)​
Widgets for easy and fast freemem change:
For compairing settings, you can make widgets, settings will be changed instantly:
- you have to select the option you want to use as a widget (e.g. option 5 of supercharger) one time in V6_Supercharger script
Your selected options will appear as a small script in sdcard/V6_Supercharger/PowerShift_Scripts
- long press on home screen, click on Widgets and select SManager
- choose the script you want to use (e.g. 512HP_UnLedded...)
Q&A Supercharger
Q: Supercharger says "sorry, your rom wipes service entries on boot". Is it an issue?
A: No you can ignore it. You'll stay supercharged. (thx to abelle_abelle for the hint)
Q: Supercharger says that I'm only 75%/50% supercharged. What is the reason?
A: Propably the services.jar hasen't been patched right. Check if the services.jar is replaced and if the owner and the permissions are right. Try it out with offline mode in the Windows tool.
Q: Do I have to patch the services.jar again after rom update?
A: If you flash the rom you have to replace the original services.jar again. I don't know if you can use the previous patched services.jar.
Q: Do I have to run the whole script again after a rom update?
A: You have to run the Supercharger script again, but it has stored the last settings and can restore them. Then you have to Wipe Cache & Dalvik, reboot and set /system/etc/init.d/S99SuperCharger to run with SU rights + at boot.
Q: Did my settings stick?
A: If Supercharger says "100% supercharged" everything should be fine. If you think there is something wrong, because of a particular message paste the log text in pastebin.com and give me the link in your post.
Q: Do I have to install the Supercharger StarterKit?
A: No, you cann try it without this first if you want. BUT some busybox versions doesn't work with Supercharger (everything below 1.16.2 and even some versions above 1.16.2.
The StarterKit installs a recommended version.
Q: My phone is getting slower from time to time.
A: This can happen if you don't reboot often (1 or 2 days). The cache is growing and there is less and less RAM.
If you don't want to reboot all the time you can make the EngineFlush in V6_SuperCharger (option 17) and a script will be created (!FastEngineFlush.sh). You can make a widget for it after you set it as favorite or launch it normally in Script Manager.
A more detailed guide about making widgets is written above.
Q: Everythings (apps and launcher) stucks after NitroLagNullifier/V6 Supercharger installation. What can I do?
A: The user abelle_abelle had this issue. He had to hard reset his device (hard reset wipes your partitions -> deletes your data) and had to reinstall the rom.
Q: Are there any possibilites to make my rom even faster?
A: Yes, with KickAssKernelizer (KAK):
http://forum.xda-developers.com/showpost.php?p=32508611&postcount=35
Maybe I will write a bit more detailed guide for this. You can see what it does at the benefits of Supercharger at the top of my first post.​----------------------------------------------------------------------------------------------------------------------------------------------------------
It took me long to test and to write please give a Thanks if I helped you
Also thank the creator of the scripts (check links)

Reserved for possible addition and Q&A

Have been using this for some time, and I can confirm it works.
Sent from my toaster.

I'm stuck in the CM logo screen after installing service.jar (online mode) and wiped davlink and cache.

aledex said:
I'm stuck in the CM logo screen after installing service.jar (online mode) and wiped davlink and cache.
Click to expand...
Click to collapse
Which Rom you are using?

Androidmarketuser said:
Which Rom you are using?
Click to expand...
Click to collapse
I'm sorry, I thought I edited the post. I'm using Elk's CM10 for Desire.
After trying several times to wait after having wiped cache and davlink (and fixed permissions) I re-flashed the rom and tried to apply the superchager script.
Problem 1: not enough spaces on the system (I'm using INT2EXT)
Problem 2: supercharger only at 50%
Problem 3: Apex launcher not recognized
Should I try to re-do everything, maybe this time with the offline method? But how to avoid the system space problem?

aledex said:
I'm sorry, I thought I edited the post. I'm using Elk's CM10 for Desire.
After trying several times to wait after having wiped cache and davlink (and fixed permissions) I re-flashed the rom and tried to apply the superchager script.
Problem 1: not enough spaces on the system (I'm using INT2EXT)
Problem 2: supercharger only at 50%
Problem 3: Apex launcher not recognized
Should I try to re-do everything, maybe this time with the offline method? But how to avoid the system space problem?
Click to expand...
Click to collapse
First off, I used it for CM10 too but without int2ext.
The reason for 50% is propably the unpatched service.jar(at beginning I had this issue too)
First, I would try to use the offline mode, the utility propably hasn't patched anything so try if it's working by manual way.
Just put the service.jar on PC, patch it and replace it. Then start the Supercharger V
script gain and it should be 100%.
otherwise do that:
On your SD Card there should be a Supercharger.html with a "log" or sth like that, please send it to me.
Additionally check if there is a "V6 Supercharger" folder on your SD, created by the script.
And check the output of the Windows tool! Be sure you have phone drivers on your PC and your phone is connected without SD Card Read if you use online.
-------------------------------------------
The space on system shouldn't be a problem, you have to use at least 250mb system (so stock hboot), int2ext only mounts /data on ext, so as I understood it is used for fatsys hboots which have 450mb system and NO space for data...
Why do you think that the space is a problem? Where did you notice it?
The APEX problem can be discussed after getting the rest work...
Please give feedback whether it worked or not

Androidmarketuser said:
First off, I used it for CM10 too but without int2ext.
The reason for 50% is propably the unpatched service.jar(at beginning I had this issue too)
First, I would try to use the offline mode, the utility propably hasn't patched anything so try if it's working by manual way.
Just put the service.jar on PC, patch it and replace it. Then start the Supercharger V
script gain and it should be 100%.
otherwise do that:
On your SD Card there should be a Supercharger.html with a "log" or sth like that, please send it to me.
Additionally check if there is a "V6 Supercharger" folder on your SD, created by the script.
And check the output of the Windows tool! Be sure you have phone drivers on your PC and your phone is connected without SD Card Read if you use online.
-------------------------------------------
The space on system shouldn't be a problem, you have to use at least 250mb system (so stock hboot), int2ext only mounts /data on ext, so as I understood it is used for fatsys hboots which have 450mb system and NO space for data...
Why do you think that the space is a problem? Where did you notice it?
The APEX problem can be discussed after getting the rest work...
Please give feedback whether it worked or not
Click to expand...
Click to collapse
Here's my problem:
1 - Installation of starter kit:
http://i50.tinypic.com/dqp5qf.png
2 - Patch of services.jar went ok with offline mode, but when I try to change permissions
http://i45.tinypic.com/34drlog.png
(this problem is obviously related to point 1)
Supercharger.html in attachments

aledex said:
Here's my problem:
1 - Installation of starter kit:
http://i50.tinypic.com/dqp5qf.png
2 - Patch of services.jar went ok with offline mode, but when I try to change permissions
http://i45.tinypic.com/34drlog.png
(this problem is obviously related to point 1)
Supercharger.html in attachments
Click to expand...
Click to collapse
Do you have stock hboot?
Try to delete some unnecessary preinstalled apps with file explorer.
(I search for some which you could delete...)
Edit: in system/app/ you can delete at least Calenar.apk, ES File Explorer.apk and Email.apk (after backup I think you can delete Gallery2.apk too, don't know how this affects on camera)
This should free at least 4mb and should be enough.
The file was just a help file and not a log, sorry for the mistake, thought it would create a og, but you have showed me the eroor with the pics...

Hey mate can you make a youtube video showing the steps. I understand better with visuals, and thanks for sharing.
Sent from my HTC Desire using xda app-developers app

Androidmarketuser said:
Do you have stock hboot?
Try to delete some unnecessary preinstalled apps with file explorer.
Click to expand...
Click to collapse
Yes I have stok hboot, and this is the first time I try to install V6 on a JB rom.
Concerning the lack of space I've done like you said, thank you!... BUT when I try to install binay 3.1 (which should fix the segmentation faults) it points out that it's only for ICS and aborts the installation. So I fixed the permission manually.
Now I'm going to check the rest and see what happens.
Fixed permission, flashed update-signed.zip, wiped davlink and cache, rebooted and... well, after HTC logo the screen turned off and only the hardkeys were illuminated
I'm going to flash the rom again and start from the beginning for the third time.

aledex said:
Yes I have stok hboot, and this is the first time I try to install V6 on a JB rom.
Concerning the lack of space I've done like you said, thank you!... BUT when I try to install binay 3.1 (which should fix the segmentation faults) it points out that it's only for ICS and aborts the installation. So I fixed the permission manually.
Now I'm going to check the rest and see what happens.
Fixed permission, flashed update-signed.zip, wiped davlink and cache, rebooted and... well, after HTC logo the screen turned off and only the hardkeys were illuminated
I'm going to flash the rom again and start from the beginning for the third time.
Click to expand...
Click to collapse
I saw that you are going to install Paranoid anyway, I have flashed CM10 recently so I have to redo my Supercharger and I will explain it in detail for you.
I will edit this post but give you a overview first.
I recommend to flash Gapps first and then enable a2sd.
Try installing Supercharger without the use of Starter Kit, Busybox, SQlite and SU binaries (v3.2) are preinstalled (if you want to check for update anyway check it in SuperUser app)
StarterKit is designed to give everyone the TESTED busybox version, to avoid problems, but try it without the installation of StarterKit, just if it doesn't work because of busybox get the one of StarterKit (I will try it with preinstalled version, not the one of StarterKit)
So here are my steps, I'll try:
1. patch services.jar with offline mode, then put the output service.jar with ES File Explorer in /system/framework
2. With terminal emulator I will set the permissions and the owner
3. I will launch the Superuser script.
You can try this while I am using this method, too, but in any case I will report if it works or not
Edit: I decided to make a video, for this I will use StarterKit too, to show everything.

chico1620 said:
Hey mate can you make a youtube video showing the steps. I understand better with visuals, and thanks for sharing.
Sent from my HTC Desire using xda app-developers app
Click to expand...
Click to collapse
I'll have to see, I have only a camera of the year 2005 or a old samsung phone of the year 2008/2009
I don't know if the quality would be good enough + I would do it only for 4.0+ ROM

Androidmarketuser said:
I'll have to see, I have only a camera of the year 2005 or a old samsung phone of the year 2008/2009
I don't know if the quality would be good enough + I would do it only for 4.0+ ROM
Click to expand...
Click to collapse
Does not matter my problem is the terminal coding i dont want to mess it up and change something crucial.
Sent from my HTC Desire using xda app-developers app

chico1620 said:
Does not matter my problem is the terminal coding i dont want to mess it up and change something crucial.
Sent from my HTC Desire using xda app-developers app
Click to expand...
Click to collapse
I'm currently making a video but I don't know if I can upload it today, but tomorrow you'll have it in any case
Quality is good I noticed.

Androidmarketuser said:
I'm currently making a video but I don't know if I can upload it today, but tomorrow you'll have it in any case
Quality is good I noticed.
Click to expand...
Click to collapse
Omg ty mate, i will be looking forward to it. Im also trying to follow your guide and see how things go, jopefully i succeed
Sent from my HTC Desire using xda app-developers app

Androidmarketuser said:
I saw that you are going to install Paranoid anyway, I have flashed CM10 recently so I have to redo my Supercharger and I will explain it in detail for you.
I will edit this post but give you a overview first.
I recommend to flash Gapps first and then enable a2sd.
Try installing Supercharger without the use of Starter Kit, Busybox, SQlite and SU binaries (v3.2) are preinstalled (if you want to check for update anyway check it in SuperUser app)
StarterKit is designed to give everyone the TESTED busybox version, to avoid problems, but try it without the installation of StarterKit, just if it doesn't work because of busybox get the one of StarterKit (I will try it with preinstalled version, not the one of StarterKit)
So here are my steps, I'll try:
1. patch services.jar with offline mode, then put the output service.jar with ES File Explorer in /system/framework
2. With terminal emulator I will set the permissions and the owner
3. I will launch the Superuser script.
You can try this while I am using this method, too, but in any case I will report if it works or not
Click to expand...
Click to collapse
Thank you, you are very patient and nice!
Yes I'm indeed trying Paranoid, because it solves the big problem I had with Elk's CM10 (wifi not working with wifi networks with PEAP), although it is slower and I intend to revert back as soon as the problem is fixed.
I will try your method, hoping that the hateful fragmentation fault problem doesn't occur anymore. :fingers-crossed:

aledex said:
Thank you, you are very patient and nice!
Yes I'm indeed trying Paranoid, because it solves the big problem I had with Elk's CM10 (wifi not working with wifi networks with PEAP), although it is slower and I intend to revert back as soon as the problem is fixed.
I will try your method, hoping that the hateful fragmentation fault problem doesn't occur anymore. :fingers-crossed:
Click to expand...
Click to collapse
Thanks for you thanks
I don't know if it is rally the segmentation (or whatever it's called) because it only occurs in ICS, if you want to install the su binary of the StarterKit it says NO because you don't need this (I think so)
I will upload a video tomorrow and I hope it solves your problem, for me everything's working fine

Does reinstalling the rom gets rid of the script? Because I'm currently using mildwild 5.0 and when I installed the supercharger script the rom got slightly slower, so I was wondering if reinstalling the rom gets rid of the script. Maybe I picked the wrong choices when installing the script I'm gonna wait for you to make a video so I can correctly do it.
Sent from my HTC Desire using xda app-developers app

chico1620 said:
Does reinstalling the rom gets rid of the script? Because I'm currently using mildwild 5.0 and when I installed the supercharger script the rom got slightly slower, so I was wondering if reinstalling the rom gets rid of the script. Maybe I picked the wrong choices when installing the script I'm gonna wait for you to make a video so I can correctly do it.
Sent from my HTC Desire using xda app-developers app
Click to expand...
Click to collapse
Reinstalling the rom deletes supercharger, because system is wiped (i think so)
The Video will show how you install the script, there aren't man decisions which you can choose incorrectly.
The speed is especially affeced by multitasking mod (keeps apps in memory, a bit less RAM for games) and freemem options which you choose in supercharger script, I recommend Option 6 for balanced settings.
AS I said the video only shows the basic things (and only for 4.0+)...
Edit: Video wont have many anotations, will be under time pressure
Sent from my HTC Desire using xda app-developers app

[INFO] ROM 101 + CWM Errors Solutions

Hi guys .You all know me.
I have created this thread for the sole purpose educating every newbie and noob about ROM and it's components...
Here goes
Parts of a ROM
i. The kernel.
Android (like many other Smartphone operating systems) runs on the Linux kernel. The Linux kernel was created in the early 1990’s by a gentleman named Linus Torvalds in Helsinki, Finland. It’s incredibly stable, incredibly friendly, and incredibly difficult for the layman to understand and modify. Thankfully it’s also very popular so it has been ported on to a multitude of hardware, including our Android devices.
Think of the kernel as an interface layer between the hardware and software on your device. The kernel decides when things happen, such as the LED indicator gets lit or when the soft button's LED gets lit. An application sends a request to the operating system to blink the LED. The operating system then sends the request to the kernel, which makes the light flash for the amount of time requested by the OS.
What sounds like a round-about way to get things done is also what makes the system so scalable and robust. Application developers only have to code in a way the operating system understands and the kernel makes it work on the hardware. This also keeps the application running in it’s own user-space and separate from the kernel. That means when you run the latest uber-cool app that wasn’t designed for your particular OS version, or is still very beta and it crashes, the kernel gives you the option to Force Close the application and the kernel can run untouched.
In a standard Android ROM (we will leave developer images and the like for another discussion) the kernel is bundled along with a set of instructions that tell the device how to load the kernel and the OS during boot. This is the boot.img that you see inside a zipped ROM that your not able to easily open. The device knows to extract this image to internal memory (the ramdisk) and follow a series of scripts (init scripts) to load the kernel and then the other portions of the OS. That’s what’s happening while you’re watching the boot animation. Interestingly enough this is done the same way for a PC, your smartphone, an Android tablet, or even a smart Linux powered toaster. If you’re feeling exceptionally geeky, plug your Android phone into the USB port on your PC and let the PC boot from the USB device. No, it doesn’t actually load, but you can watch the animation while it tries to match up the hardware support with what’s inside your PC. As I said, Linux is amazingly scalable and as a result so is Android.
What is a kernel? If you spend any time reading Android forums, blogs, how-to posts or online discussion you'll soon hear people talking about the kernel. A kernel isn't something unique to Android -- iOS and MacOS have one, Windows has one, BlackBerry's QNX has one, in fact all high level operating systems have one. The one we're interested in is Linux, as it's the one Android uses. Let's try to break down what it is and what it does.
Android devices use the Linux kernel, but it's not the exact same kernel other Linux-based operating systems use. There's a lot of Android specific code built in, and Google's Android kernel maintainers have their work cut out for them. OEMs have to contribute as well, because they need to develop hardware drivers for the parts they're using for the kernel version they're using. This is why it takes a while for independent Android developers and hackers to port new versions to older devices and get everything working. Drivers written to work with the Gingerbread kernel on a phone won't necessarily work with the Ice Cream Sandwich kernel. And that's important, because one of the kernel's main functions is to control the hardware. It's a whole lot of source code, with more options while building it than you can imagine, but in the end it's just the intermediary between the hardware and the software.
When software needs the hardware to do anything, it sends a request to the kernel. And when we say anything, we mean anything. From the brightness of the screen, to the volume level, to initiating a call through the radio, even what's drawn on the display is ultimately controlled by the kernel. For example -- when you tap the search button on your phone, you tell the software to open the search application. What happens is that you touched a certain point on the digitizer, which tells the software that you've touched the screen at those coordinates. The software knows that when that particular spot is touched, the search dialog is supposed to open. The kernel is what tells the digitizer to look (or listen, events are "listened" for) for touches, helps figure out where you touched, and tells the system you touched it. In turn, when the system receives a touch event at a specific point from the kernel (through the driver) it knows what to draw on your screen. Both the hardware and the software communicate both ways with the kernel, and that's how your phone knows when to do something. Input from one side is sent as output to the other, whether it's you playing Angry Birds, or connecting to your car's Bluetooth.
It sounds complicated, and it is. But it's also pretty standard computer logic -- there's an action of some sort generated for every event. Without the kernel to accept and send information, developers would have to write code for every single event for every single piece of hardware in your device. With the kernel, all they have to do is communicate with it through the Android system API's, and hardware developers only have to make the device hardware communicate with the kernel. The good thing is that you don't need to know exactly how or why the kernel does what it does, just understanding that it's the go-between from software to hardware gives you a pretty good grasp of what's happening under the glass. Sort of gives a whole new outlook towards those fellows who stay up all night to work on kernels for your phone, doesn't it?
Click to expand...
Click to collapse
ii. The operating system.
Once the kernel is loaded, the init scripts tell the Operating System to load. Android is the user interface for a custom built Java virtual machine called Dalvik. Dalvik was written by Dan Bornstein, who named it after the fishing village of Dalvik in Iceland, where his family originated from. The debate of which Java VM is superior is best left for another discussion, so I’ll simply say that DalvikVM is a register-based machine versus true JavaVMs which are stack based.
The Dalvik machine creates executable files (.dex files) which can be interpreted by the OS and run by the end user. These .dex files are OS version dependant. That simply means that applications and core functions built to work with one version of Android may or may not work well with other versions. Google provides the tools through it’s Software Development Kit (SDK) for applications to communicate with the OS.
Click to expand...
Click to collapse
iii. Core functions.
No smartphone would be complete without a set of functions that allow the device to be used as intended. Things like the phone and dialer interface, the calendar, the messaging system are core functions of the Operating System. In Android, these are run on top of the kernel as separate applications. The merits (or lack of) of providing these needed functions as separate applications is once again best left for another discussion, but this is what allows developers like HTC or Motorola to replace the standard functions with alternatives that provide a different look and feel from stock. HTC’s onscreen keyboard or Motorola’s MotoBlur contact list are great examples of this. The “little guy” isn’t left out of the mix either. Handcent SMS or Chomp SMS can integrate into the OS very well, as most of us already know.
An additional set of Core Functions are provided by Google. Popularly called GoogleBits, things like Gmail, sync, Gtalk and the Android Market are applications written by Google that give an extra set of useful functions to the OS. You’ll find these on all smartphones, as well as many other Android devices.
Click to expand...
Click to collapse
iv. Optional applications.
These are applications provided by the manufacturer to give the device even more usability. Things like the Amazon MP3 store, PDF readers, Corporate Calendar etc. allow you to do even more with your device. Remember - Droid Does
Click to expand...
Click to collapse
B. How is a ROM packaged?
In most cases a ROM will come packaged in a .zip file. The recovery image’s kernel (yes, it has one too!) has the ability to unzip and copy the contents into the correct place. Inside this zip file is a folder (META-INF\com\google\android\) that contains a script prepared by the ROM “cooker” (another of those techie terms - it means the person(s) who developed the ROM) that tells the system what to format, what to copy and where, and any file operations that need to be done. Each device does things a bit differently, but this script is where it all gets done. More on this folder later.
You’ll also see a /system folder. This is the meat of the ROM. It has the necessary OS files, the Core functions, and any optional applications the cooker decided to include. The folder is structured the same way it is on your device - /system/app, /system/framework, etc. The whole tree is usually copied over and the existing /system folder is overwritten. The cooker uses the script to tell the kernel to erase the existing system folder, copy the new folder over, and set the file permissions.
Sometimes you will also see a data folder. This usually is space set up for optional applications, including optional system tools like busybox or SuperUser white list. These applications could be placed in the /system folder, but placing them in the data folder makes it easier for the end user (you and I) to remove or update them as needed.
You’ll also notice a META-INF folder. This contains the update script we talked about earlier, as well as secure keys that need to be provided so the device knows the update can be trusted. A special note needs made here. Trusted means that the update is trusted to be in the correct form to load the device. It in no way means the ROM is safe from malicious code. Anyone is able to use a set of test keys and create a ROM that will flash and run your device - even those people with bad intentions. Flashing and running a custom 3rd party ROM is putting faith in the cooker that he or she not only knows what they are doing, but are honest as well. Also, some Motorola custom ROMs will have a small update.zip stored inside this folder to be run on first boot of the device.
Finally we are left with the boot.img file. This is the kernel and ramdisk image we discussed earlier. Your phone copies this over to be decompressed and run when the device boots.
Click to expand...
Click to collapse
2. How do I install a ROM?
In this section we’re discussing how to install a custom 3rd party ROM. ROMs from the manufacturer usually have a utility that runs on your PC to flash and load the new image.
A. Got Root???
Yes ?:good:!!!
Custom ROM’s simply will not load on devices that aren’t rooted. In theory, it may be possible to sign a 3rd party ROM with the keys that the stock recovery image will flash, but for the most part you need to have flashed a custom recovery image before you can change your device’s ROM. Instructions and tutorials on how to root your device are all over the internet. Some are good, some are bad. The hacking forum is a great place to go and learn more about rooting and how to successfully get it done on your device.
Click to expand...
Click to collapse
B. Recovery
Most Android devices have had a custom recovery image written for them. This will overwrite the stock recovery image, allowing you to flash 3rd party ROMs as well as giving extra functionality. Help with finding and flashing the custom recovery image for your device can also be found in the hacking forum. The installation of a custom recovery image also allows for a very important function. Backup and restore.
Click to expand...
Click to collapse
.C. Nandroid
Nandroid is a set of bash scripts and code written by that copies the state of your system and stores it in a folder on your SD card. You can then use the restore function of Nandroid to restore to this point at any time. This is a priceless feature and reason enough to root your phone. It’s included by default in most custom recovery images, and the code is freely available to use if you’re inclined to write your own recovery image.
Click to expand...
Click to collapse
In most situations, using Nandroid to back everything up is easy:
1. Verify you have a memory card with enough free space (~300MB to backup, ~500MB to restore).
2. Reboot your device into recovery. It’s slightly different for each device, once again hacking forum FTW!
3. Navigate through the menu and select the Nandroid Backup function.
4. Apply your choice and wait for the device to tell you it’s finished.
It’s always good practice to copy the entire nandroid folder from your SD card to a safe place. You can then copy it back to the SD card if the card is ever damaged, lost or erased.
D. Copy and Flash
You’re rooted, have downloaded a custom ROM, have your system backed up and are now ready to flash your device. This is not nearly as scary as it sounds.
1. Mount your SD card to your PC, and copy the .zip file to the root folder of the card. Don’t unzip the file, and don’t look for a folder called root. The root folder in this case means the base folder, what you will see when you mount your card to a PC or the device.
2. Reboot your phone into recovery.
3. Navigate through the recovery menu and select the flash update option. Depending on your recovery image, the file may need to be named update.zip, or you may be able to select any zip file on your card as long as it’s the correct format. The cooker knows this as well and if the ROM needs to be named update.zip it will be.
4. Apply your choice and wait for your device to tell you it’s finished.
5. Reboot.
Click to expand...
Click to collapse
It’s worth noting that many times a new ROM will require that you wipe and factory reset your devices data. While inconvenient, it’s often necessary to get rid of the old data as it may be incompatible. As long as you’re using the cloud for calendar and contacts, they will be re- downloaded and stored back on your device automatically.
Credits
The internet
And other sites related to android development
And of course me
My Galaxy R forum friends !!

ERRORS encountered in CWM Recovery
.
What is CWM Recovery ?
ClockworkMod Recovery is a custom recovery for many Android devices. It is considered to be the most popular recovery for Android due to its easily-ported nature, and integration with ClockworkMod ROM Manager by Koush(Koushik Dutta). The easiest way to recognize it is by the printed name when it first starts, and the background logo of a gear and hat.
Click to expand...
Click to collapse
ERROR STATUS 6
This is usually caused by CR/LF EOL(Windows style End Of Line) in updater-script. Change it to LF EOL(Unix Style EOL) using Linux command: dos2unix updater-script, then re-signing the ZIP, will usually fix this error.
Click to expand...
Click to collapse
ERROR STATUS 7
This is usually caused by a corrupt download, or bad file signature. Re-downloading (or re-signing) the ZIP will usually fix this.
Click to expand...
Click to collapse
We have been consistently seen and heard people facing error “Status 7″ error while trying to flash or install
custom ROMs or firmware packages on their Android smart phones or tablets with ClockworkMod Recovery. Many
of the users are nowadays facing this problem with CWM Recovery while flashing .zip files of modded or custom
Ice Cream Sandwich (ICS) or Jelly Bean (JB) ROMs on their devices. So, you have also downloaded a custom ROM,
placed its .zip file in your phone’s or tablet’s SD card, booted into ClockworkMod Recovery, selected – “install zip
from sdcard” and then chosen the .zip file of the ROM to get it installed on your device. But instead of getting
flashed successfully, if you are facing the issue mentioned below, then just keep reading this article to find out
what’s wrong and fix up the problem :
Finding update package…
Opening update package…
Installing update…
Error in /sdcard/custom-jelly-bean-rom.zip (Status 7)
Installation aborted
Click to expand...
Click to collapse
or the following error right after CWM recovery shows –
Installing update…
assert failed: getprop(“ro.product.device”) == “I9103″ || getprop(“ro.build.product”) == “I9103″ || getprop
(“ro.product.board”) == “I9103″
Error in /sdcard/android-4-1-1-ics-rom-latest.zip (status 7)
Click to expand...
Click to collapse
So, if you are facing any of these errors while trying to install the desired custom ROM package on your Android
phone or tab, then you may try a various things or steps which may turn out to be the workaround of this
problem. Here are a few tips to get this “Status 7” error fixed in ClockworkMod Recovery and flash the ROM
successfully on your device :
(1) First of all, make sure your device’s bootloader is unlocked. If it is already unlocked but you are still
not able to flash the ROM, then just extract the .zip file of the ROM into a new folder, find the boot.img file from
that directory and flash it up on your phone or tablet via fastboot on your PC.
(2) Make sure that you are having the appropriate Radio or Baseband version installed on your device which is
supported by the custom ROM you are trying to flash. Most of the ROMs requires the latest version of Baseband, so
just update or upgrade your device to the latest Baseband version and then try to install the ROM once again.
(3) Update your device to the supported / latest build of official firmware before trying to install the ROM. You can
do it from – Settings > About Phone / Device > Software Update.
(4) Make sure you are having the supported or required kernel installed on your phone or tab. If it’s not, then flash
a new kernel right away and try to install your custom ROM once again.
(5) Is the ROM which you are trying to flash really works ? Find out whether it is working for other users or not.
Click to expand...
Click to collapse
NOW
ERROR STATUS 0
This is usually caused by an incompatible update-binary in edify ZIPs. Replacing it with a compatible one, then re-signing the ZIP, will usually fix this error.
Click to expand...
Click to collapse

Now it's time for the partitions :good:
Let’s start with a list of standard internal memory partitions on Android phones and tablets. These are:
/boot
/system
/recovery
/data
/cache
/misc
In addition, there are the SD card partitions.
/sdcard
/sd-ext
Note that only /sdcard is found in all Android devices and the rest are present only in select devices. Let’s now take a look at the purpose and contents of each of these partitions.
/boot
This is the partition that enables the phone to boot, as the name suggests. It includes the kernel and the ramdisk. Without this partition, the device will simply not be able to boot. Wiping this partition from recovery should only be done if absolutely required and once done, the device must NOT be rebooted before installing a new one, which can be done by installing a ROM that includes a /boot partition.
/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.
/recovery
The recovery partition can be considered as an alternative boot partition that lets you boot the device into a recovery console for performing advanced recovery and maintenance operations on it. To learn more about this partition and its contents, see the ‘About Android Recovery’ section of our guide to ClockworkMod recovery.
/data
Also called userdata, the data partition contains the user’s data – this is where your contacts, messages, settings and apps that you have installed go. Wiping this partition essentially performs a factory reset on your device, restoring it to the way it was when you first booted it, or the way it was after the last official or custom ROM installation. When you perform a wipe data/factory reset from recovery, it is this partition that you are wiping.
/cache
This is the partition where Android stores frequently accessed data and app components. Wiping the cache doesn’t effect your personal data but simply gets rid of the existing data there, which gets automatically rebuilt as you continue using the device.
/misc
This partition contains miscellaneous system settings in form of on/off switches. These settings may include CID (Carrier or Region ID), USB configuration and certain hardware settings etc. This is an important partition and if it is corrupt or missing, several of the device’s features will will not function normally.
/sdcard
This is not a partition on the internal memory of the device but rather the SD card. In terms of usage, this is your storage space to use as you see fit, to store your media, documents, ROMs etc. on it. Wiping it is perfectly safe as long as you backup all the data you require from it, to your computer first. Though several user-installed apps save their data and settings on the SD card and wiping this partition will make you lose all that data.
On devices with both an internal and an external SD card – devices like the Samsung Galaxy S and several tablets – the /sdcard partition is always used to refer to the internal SD card. For the external SD card – if present – an alternative partition is used, which differs from device to device. In case of Samsung Galaxy S series devices, it is /sdcard/sd while in many other devices, it is /sdcard2. Unlike /sdcard, no system or app data whatsoever is stored automatically on this external SD card and everything present on it has been added there by the user. You can safely wipe it after backing up any data from it that you need to save.
/sd-ext
This is not a standard Android partition, but has become popular in the custom ROM scene. It is basically an additional partition on your SD card that acts as the /data partition when used with certain ROMs that have special features called APP2SD+ or data2ext enabled. It is especially useful on devices with little internal memory allotted to the /data partition. Thus, users who want to install more programs than the internal memory allows can make this partition and use it with a custom ROM that supports this feature, to get additional storage for installing their apps. Wiping this partition is essentially the same as wiping the /data partition – you lose your contacts, SMS, market apps and settings.
With this, we conclude our tour of Android partitions. Now whenever you install a ROM or mod that requires you to wipe certain partitions before the installation, you should be in a better position to know what you’re losing and what not and thus, you’ll know what to backup and what not.

Nice thread, maybe add error status 0 for CWM
Sent from my C6603 using xda app-developers app

krabappel2548 said:
Nice thread, maybe add error status 0 for CWM
Sent from my C6603 using xda app-developers app
Click to expand...
Click to collapse
Done !!!!

Great thread, You are seriously doing well.:good:

MY thanks just ended
will use the mob app to thank u bro !!
After all you inspired me for this thread not

Moved to android general as per OP request.

[GUIDE] WhatsApp Folder, Download Folder etc. on External Storage with Xposed (ROOT)

There's one thing I hate about living in Germany. It's that we never get the high storage capacity models of most Smartphone models. We always get the base models with 16 or 32 Gigabytes of internal storage. But the ads and people working at the big stores will tell you "Well, you can put a microSD card in it". Screw you, you idiot! We both know it won't help me! I need high storage because games have become huge and WhatsApp folders are at least 2 - 3 Gigabytes since the introduction of animated GIFs. We also know that Google's adoptable storage is A) complete BS B) it's disabled on almost all Samsung devices and C) even if you enable it, it doesn't work the way it's supposed to on Samsung devices. More on that some other time. We also know that moving apps to external storage doesn't do crap because it only moves 50 or 60 Megabytes which is completely useless if you ask me. So, here's my guide.
This should work on any ROM, be it AOSP or TW and Android version higher than 5.0.
Tested working on:
Samsung Galaxy S3 running LineageOS 14.2 (Android 7.1.2)
Samsung Galaxy S4 running deodexed Android 5.0.2
Samsung Galaxy S7 (Edge) running stock Android.
Samsung Galaxy S7 (Edge) running SuperMan ROM 2.7.x with SuperStock Kernel 2.10.x.
What you're going to need:
MAKE A F*#?!85 BACKUP OF ANYTHING YOU'RE GOING TO TOUCH!
- Root isn't necessary but advised.
- TWRP.
- Official Xposed Framework.
- XinternalSD.
- If your on a stock ROM or you know the ROM you're running doesn't have an SD card fix (RW for external storage) implemented, we're also gonna need Marshmallow SD fix. Don't get confused by the name. It works on Lollipop and Nougat, too.
- Alternatively you can use SDFix: KitKat Writable MicroSD by NextApp, inc. (FX File Explorer). This also works on Marshmallow but I haven't tested it on Nougat.
- Don't forget to enable XinternalSD and Marshmallow SD fix, if you chose to use it in Xposed Installers Modules menu!
After you've successfully installed all the steps above do the following:
- Open a File Explorer of your choice and move the WhatsApp folder to you external Storage.
- Open XinternalSD and tap on "Enable for apps".
- In this list you're going to want to check the box for WhatsApp.
- Reboot (Not sure if necessary. Just for good measure) and you're done.
- Test to see if new media is stored on external storage.
To store downloaded files from Chrome directly on external storage do the following:
- Open XinternalSD and tap on "Enable for apps".
- In this list, check the box for "Chrome".
- Reboot for good measure and you should be done.
This method works for almost any app, but to quote @MBariya
But supports only in that apps which has location modification option only in internal sd...
Click to expand...
Click to collapse
To be fair, his statement is from 2014. A lot of things changed since then. Maybe it's obsolete. I don't know, I'm not an engineer.

I reply here because I spent a lot of time searching through very old posts and trying outdated methods. I didn't know that actually today there is a very easy solution to move whatsapp media folder to SD card. It perfectly worked on my Samsung Galaxy A3 A320FL with Oreo:
1) Root (I used twrp + magisk method)
2) Download "App2SD" (the original by Vicky Bonick; it's free) and follow instructions on how to create partitions
3) Use "folder mount (app analyzer)" feature, which apparently was not considered in the old posts in this forum, so I suppose it was recently added to App2SD.
It's like folder mount, but it's pre-set for some common apps, including Whatsapp. With this feature, you can successfully move Whatsapp media folder to SD, in one clic.
In my case everything worked fine. When I reboot I have to re-mount folder, but it takes one second (just open Apps2SD, tap Folder Mount, slide "whatsapp other").