Related
PLEASE NOTE: If you are using a Canadian handset, I recommend switching over to my JL2 based ROM. It's the same speed (if not quicker), and I will be providing much more updates for it. The ROM can be found here: http://forum.xda-developers.com/showthread.php?t=906977
News
12/23/10 - v0.2 released! Includes an error-checking script to prevent possible errors from occuring, new Steam recovery, wipe and non-wipe versions and more! Check the changelog for more info.
12/22/10 - v0.1, initial beta release
Hey everyone,
This is a rom which aims to provide the absolute best user experience by being extremely quick without sacrificing any necessary features. The majority of Samsung bloatware is removed, however a good portion of the pre-installed apps are left untouched. This ROM is based on XXJPY (Froyo 2.2.1).
If you have any questions prior, while, or after installing this ROM, please read the first few posts, as I'll try to address every possible (major) problem which can occur. If, after reading the posts, you are still encountering a problem, please reply to this thread being as detailed as possible. This allows me to fix problems quickly and easily.
Now, this is my first ROM, so there are bound to be a handful of bugs. However, I've been using this ROM for a few days and have yet to encounter any major problems.
Note: Please don't complain about Quadrant, Linpack, or any other pointless benchmark scores. If you've used the ROM and it's sluggish, by all means tell me, but don't base your opinion of the speed merely on a benchmark.
Okay, so what now?
1. Download and Install Instructions
2. Changelog, To-Do
3. FAQ and Problems
4. Screenshots, Media, User Comments
Features
Based on XXJPY (Froyo 2.2.1)
Patched Speedmod kernel, version K12 hz=256(allows you to mount on computer without problems)
Steam multi-touch recovery: update.zip on SD card
Added an error-checking script which prevents errors when installing [thanks Darkyy!]
All-black Gingerbread theme (saves battery)
Fully deodexed
Fully zipaligned
Fully updated Google Apps (YouTube, Flash, Market, Gmail, Maps)
Latest Su and Busybox
All protected apps in market - modified build.prop
Big APN list, which allows instant internet + MMS access
Integrated ClockworkMod Recovery
Stock AOSP Lockscreen
Bell UGJK3 Modem
Backlight Notifications
Added Applications:
Nexus S Live Wallpapers
Swype v 2.15 (Newest)
Launcher Pro
Optional: Gingerbread Keyboard (install from SD Card)
Removed Applications:
AllShare
Diary
Aldiko Reader
Press Reader
Layar
Thinkdroid
Write and Go
Credits (in no particular order)
-Hardcore for the kernel
-santiemanuel for the Nexus S Live Wallpapers
-vukandric for the theme
-Darkyy for help on the update script, and for generally being awesome
Download and Install Instructions
Downloads
Latest and Greatest
-v0.2: seeARMS XXJPY (12/23/10)
Wipe: http://www.multiupload.com/L9SUOBKO88
No Wipe: http://www.multiupload.com/9F5E89AYTP
-v0.1: seeARMS XXJPY (12/22/10)
http://multiupload.com/G6XTJF07MO
Modems
To flash these modems, use Odin and select the "modem.bin" file in the PHONE box. Go to Settings -> About on your phone after flashing and look at Baseband to ensure it flashed correctly.
JL2: http://www.multiupload.com/TC1ME8VB20
JK4: http://www.multiupload.com/3HOKWMBHO2
Installation Instructions
Before installing, disable any lagfixes (which can typically be done by booting into recovery mode and selecting "Disable Lagfix").
Also, if you wish, backup everything! Perform a NANDROID backup in recovery, backup your music, files, etc. In case something goes wrong (it will eventually), you'll have peace of mind.
Please note: this rom will wipe all your data. It will not, however, format your internal or external SD cards. This means you'll lose apps and settings, but not music, movies, etc.
Lastly, I recommend performing a factory reset before installing any new rom.
If you're running a previous version of my ROM, feel free to install the non-wiping version. However, if you're switching roms, I recommend running the standard version, which will erase all data.
1. Download and copy this file to your internal memory card.
2. Boot into recovery, and select "Install zip from sdcard".
3. Select "Choose zip from sdcard", and scroll to the ROM.
4. Select OK, and wait for the file to flash.
5. Reboot. This reboot will take a while (upwards of 2-5 minutes), so be patient and don't shut off your phone!
Congratulations, you've successfully flashed!
After it boots, I'd recommend doing a few things in order to allow your phone to be as quick as possible:
1. Boot back into recovery, select "Advanced SpeedMod ULK Features". Choose "LAGFIX options", then "Faster: EXT4 ALL". This applies a lagfix, and converts the partitions into the faster EXT4 filesystem.
2. In recovery, go back to the Advanced SpeedMod ULK Features menu. Choose "TWEAK options", and enable every tweak. For more information about these tweaks, see HERE.
Also, window animations are disabled by default. You can enable them by going into settings -> Display, and selecting Animations.
3. If you'd like the Gingerbread Keyboard, open up the My Files application and navigate to the directory "Gingerbread_Keyboard". Open up the .APK file and install as usual.
Changelog And To-Do
Changelog
v0.2
-Google Voice Search updated
-Added option to install gingerbread keyboard
-Updated kernel version to K12
-Added error checking script - with help from Darkyys rom (This prevents possible errors when installing)
-added nowipe and wipe versions
-Modified build.prop to allow all protected market apps
-Added Steam recovery - check FAQ for info on how to access it
v0.1 - Initial beta release
To-Do
-Gingerbread Keyboard
-Extended Power menu
-Support for different themes
-Stock application pack (available for flashing through CWM)
-Better modem (JL2? JK4?)
-Faster browser
-Modded SMS Application
-Modded Camera Application
If there's anything else you'd like to see in this ROM, just ask.
FAQ And Problems
FAQ
I'm on stock Froyo and I have 3e recovery!
Click to expand...
Click to collapse
No worries. Follow these steps:
1. Download Odin from here.
2. Download the Speedmod kernel for whichever Android version you're running. Make sure to download the Odin kernel, not the CWM one!
3. After downloading, extract the .TAR file from the file you just downloaded.
4. Open Odin, and turn off your phone. Connect your phone to your PC via USB, and enter download mode by holding volume down + home + power.
5. Odin should detect your phone. Load up the .TAR file in the "PDA" box in Odin. Make sure the other boxes are left blank. Untick "Repartition". Start flashing.
6. Your phone should automatically reboot with the new kernel! To double check, shut it off and boot into recovery. If you see CWM recovery, you're successful!
7. Now you're required to download the patch for the Speedmod kernel, which will allow you to copy the ROM over to your internal SD card. If you don't install this patch, the internal SD card will be detected as a CD drive, and will be read-only. The patch is able to be downloaded from HERE. Simply copy this patch to your SD card, boot into CWM, and flash it using "install zip from sdcard". After doing this, follow the normal steps to install this rom!
I'm encountering force-close issues, and general app issues right after installation.
Click to expand...
Click to collapse
Simply perform a factory reset. Clear the cache + Dalvik cache in recovery as well, if you'd like.
What's this steam recovery and how do I access it?
Click to expand...
Click to collapse
Steam recovery is a new, semi-functional multi-touch recovery created by sztupy. This recovery has all the features the standard CWM one has and more. Check his thread for more info.
Please note: Because (currently) the only Steam-compatible kernel is based on a much older base version (ie: not XXJPY), a small amount of features are incompatible, such as lagfix options, kernel options, etc. However, the majority of features (such as mounting, wiping, etc) are working just fine. I'm working on getting everything working; as soon as it is, it will fully replace CWM on this ROM.
To enable it, just boot into CWM and go to "Apply sdcard: update.zip". After doing this, it will boot into the new Steam recovery. You must do this every time you want to access it.
My GPS isn't working! It takes forever to lock and displays my position inaccurately!
Click to expand...
Click to collapse
Try clearing the GPS data on your phone. Do the following: (Original poster unknown. Reposted by dpvu.)
1) Enter *#3214789650# into the dialpad.
2) Under "Application Settings" set the Start Mode to Coldstart.
3) At the main menu "Delete GPS Data".
4) At the main menu "Get Position Test".
If you're still not finding many satellites try setting Operation Mode to "MS Based" in the "Application Settings". I did all of this then set the GPS back to hot start.
Screenshots, Media, User Comments
Screenshots
Click for a larger image.
User Comments
°Dexter° said:
Impressive rom seeArms, really really fast...faster than others, indeed.
...
Very good work,no major issues by now,i'm eagerly waiting for next release
Click to expand...
Click to collapse
Existence. said:
it's runnin great, thanks seeARMS. can't wait for the JL2 version. i really dont wnt to brick my phone and i think the JL2 version fixes the SD dying problem so i cant wait!
Click to expand...
Click to collapse
hi. looks good. i will test it now and give feedback after.
thanks for your work and keep going.
btw: why are using this modem?
gonna try this ROM out!
Quadrant score? I will try it, looks good.
gonna try this release soon, good job
fenerbuuh said:
hi. looks good. i will test it now and give feedback after.
thanks for your work and keep going.
btw: why are using this modem?
Click to expand...
Click to collapse
I'm using this modem because I need the Canadian band, because, well, I'm located in Canada. And, according to this guide, this modem is very good on battery life and reception.
In later versions of this ROM I'll most likely include a different modem (or a flashable modem). Something like that.
Any modem you'd prefer to see included?
Place this zip into PDA on Odin and upload it.
Any chance to work this?
I would like to try this rom,but I've 3e and I can't do it the way been described...
Hey man, to bad i flashed Docs jpy rom just yesterday evening, and dont want to change rom on a daily base. But ill test it for sure just because id not have to change kernel afterwards...
so thanx for your work and keep it coming man...
Mparmpa-Nikos said:
Place this zip into PDA on Odin and upload it.
Any chance to work this?
I would like to try this rom,but I've 3e and I can't do it the way been described...
Click to expand...
Click to collapse
Flash the SpeedMod kernel (or any kernel which supports froyo and has integrated Clockworkmod Recovery).
I'll add a guide to do this in the FAQ.
seeARMS said:
Flash the SpeedMod kernel (or any kernel which supports froyo and has integrated Clockworkmod Recovery).
I'll add a guide to do this in the FAQ.
Click to expand...
Click to collapse
I'm looking forward to this,man!Thank's
Mparmpa-Nikos said:
Place this zip into PDA on Odin and upload it.
Any chance to work this?
I would like to try this rom,but I've 3e and I can't do it the way been described...
Click to expand...
Click to collapse
No way man, but you could get hardcores kernel as an odin package, it comes with cwm recovery, flash that first and then use cwm to install this rom.
Mparmpa-Nikos said:
I'm looking forward to this,man!Thank's
Click to expand...
Click to collapse
Done. See the FAQ.
Welcome new devinteresting rom,gonna try it...
Thank you
Welcome seeARM!
Nice to see another dev helping the SGS Community.
Feel free to PM me if you have a question or anything else
- darkyy.
Sounds good
Will likely give this a try as the XXJPX modem causes me to lose my 850 WCDMA connection all too frequently (even though I've enabled it). Just curious if there are any problems with Market, or will it come updated to 2.2.7 already?
Cheers mate!
Darkyy said:
Welcome seeARM!
Nice to see another dev helping the SGS Community.
Feel free to PM me if you have a question or anything else
- darkyy.
Click to expand...
Click to collapse
Will do Darky, thanks.
canad1an said:
Will likely give this a try as the XXJPX modem causes me to lose my 850 WCDMA connection all too frequently (even though I've enabled it). Just curious if there are any problems with Market, or will it come updated to 2.2.7 already?
Cheers mate!
Click to expand...
Click to collapse
Market comes updated to version 2.2.7 already. I haven't had any problems with it at all.
All,
Ok, time to re-wrte the OP as there are now MUCH better tools for flashing the update.zip (and you can make backups) Make sure to say thanks to the TWRP team!!!. The update.zip file available here is a derivation of the work originally started by JackpotClavin (he did an initial proof of concept but a number of features that I wanted didn't work so I figured I'd pick up where he left off and see if I could get the ROM working for me with the missing features)
The initial thread was here if you care to look.
At this point sound, video (both in the browser and standalone) and hardware acceleration are now working with CM7 on the Fire. I'm off now poking at the MAC address issue and then I'm off to see about Bluetooth.
UPDATE:
- 01/01/12 - Back from the break and starting to work on things again. I've had a number of people ask for my current configs so I set up a repo at https://[email protected]/whistlestop/CM7KF to let people track my progress. If you want to build your own KANG then below are the steps that I currently follow with the current repo files.
-Pull the CM7 source. Check out this link for a how to on that: http://wiki.cyanogenmod.com/wiki/Nexus_One:_Compile_CyanogenMod_(Linux)
Symlink the amazon directories from the CM7KF repo into the CM7 tree. Specifically:
-cd <path to the CM7 tree>/vendor
-mkdir amazon
-ln -s <path to CM7KF tree>/vendor/amazon amazon
-cd <path to CM7 tree>/device
-mkdir amazon
-ln -s <path to CM7KF tree>/device/amazon amazon
Copy the cyanogen_blaze.mk file from <path to the CM7 tree>/vendor/amazon/blaze into <path to the CM7 tree>/vendor/cyanogen/products and add the following line to the AndroidProducts.mk file in the same directory.
$(LOCAL_DIR)/cyanogen_blaze.mk \
Ok, go to the top of the CM7 tree and do ". build/envsetup.sh && brunch blaze" and go get a cup of coffee while it builds. It'll take awhile.
- 01/02/12 - New update.zip files uploaded that fix the MAC issue as well as the build issue with the gps.omap4.so library.
- 01/03/12 - New update.zip and update-wipeall.zip files uploaded that fix the regression on the hardware acceleration. Sigh...
- 01/13/12 - Update to remove the recovery option on reboot (as it continues to cause problems for folks), removal of the search from the soft buttons by default, addition of the home to the soft buttons by default (again as that seems to be a constant question) While I built and tested the changes I didn't make the updates. You have IngCr3at1on to thank for that.
Backlog of tasks (as of 01/02/12)
-FIXEDSeems that all Wireless MAC IP's are the same (meaning that everyone that flashes the ROM will have the MAC of 08:00:28:12:03:58. While the first three octets register the MAC as being owned by Texas Instruments (the manufacturer of the OMAP chipset), the fact that the last octets don't vary is BAD. From a little Googling, I'm not sure this is something specific to this ROM/device as other CM7 ROMs on different devices seem to have the same issue but with a different MAC address it sounds. I'll look to make sure I'm not doing anything that is causing this issue. A tip of the hat to "TheKid2" for this post which appears to provide a hand workaround to the issue for now.
-The update.zip file is now signed but the update-wipeall.zip isn't yet. I'll get to that but as it doesn't seem to cause any issue in flashing it's not too high on the list to chase given the two issues below.
-No Bluetooth (yet...) This is still my personal quest so once I get the base CM7 capabilities working then this is my next thing to poke at. From the postings/reading I've done so far this seems doable (just a matter of time and programming, no rocket science required it appears at this point)
Before you start, make sure your Kindle Fire is fully charged, rooted, you know your way around adb, your kindle fire actually connects to adb and works successfully and you've installed TWRP (and I recommend installing FireFireFire as well to keep from having to issue idme commands to get into the recovery image).
I used the directions here to get all the pre-requisites done. Assuming everything above is done, then it's time to install CM7.
First a note, installing CM7 will replace the current ROM on your device and I'm not responsible for any malfunctions :/ I've done this for versions 6.2 only so your mileage may vary (but there is a good group of members on this thread so they'll help out if possible)
If you're coming from a STOCK ROM then use this version to flash. It will wipe the data and cache partitions (as well as the system partition) as a part of the flash process which should get rid of any FC issues.
md5sum for update-wipeall.zip
e7c85c3bcc01bcea59ffcc5647a6be97 update-cm7-wipeall.zip
If you're upgrading from an EXISTING CM7 install then use this ROM instead. This one will NOT wipe the cache and data partitions which should mean that you can upgrade from one version of CM7 to another without losing any of your existing date (or that's at least the idea)
md5sum for update.zip
ab80c089d0c93f02bd7271c5e4401cf7 update-cm7.zip (CHECK THAT THIS MATCHES THE DOWNLOADED UPDATE.ZIP)
Copy the CM7 update.zip to the root of your sdcard, so it's /sdcard/update.zip (e.g. "adb push update.zip /sdcard/")
OPTIONAL STEPS FOR INSTALLING GOOGLE APPS
If you want to add in the Google apps then:
-Download the gapps zip from here
-Copy them to your sdcard (e.g adb push gapps-gb-20110828-signed.zip /sdcard/ )
NOTE: if you have issues with the included Google Market FC'ing, then download this versions and it seems to fix the issue (again thanks to detnap in this thread for that tip)
Reboot into TWRP (when the FireFireFire screen comes up hit the power button to launch TWRP.
-If you reboot by holding the power button until the power screen comes up make sure when you select reboot that you DON'T say boot into recovery as this will put you into a loop where the device always boots into TWRP (even if you don't press the power button during the boot) READ THIS PART AS ALMOST EVERYONE IS MISSING THIS PIECE: If you find yourself in this loop then connect with "adb shell" and issue "idme bootmode 4000"
-For me I hold the power button until it goes orange. Just pressing it quickly doesn't do the trick at least for me.
Once it boots into TWRP then I ALWAYS recommend you perform a backup before you start anything (that way you can go back in case of a problem) You can do this by hitting the backup button.
Now that you have a backup, on the main TWRP screen hit the install button. This should put a list of the possible .zip files on your /sdcard partition in the right window. Tap the file you want to flash and hit the flash button (right now don't do any MD5 or signature checks as I've not yet got that included in the update.zip) If you see some errors about not being able to load volume /misc don't worry, I see that right now as well and everything still seems to work. I'll chase that issue once some other bigger issues are run to ground.
If you are coming from a stock ROM then make sure to click the wipe Cache/Dalvik so that we rebuild everything for the new CM7 image. If you're coming from a previous CM7 ROM then you can skip this step (I at least have and everything appears to work fine and you don't have to re-install everything)
Now hit the reboot button and you should again see the FireFireFire yellow triangle again. It will sit there for a bit and then it will go away and you should be greeted with the CM7 boot screen. If everything goes well, then a few seconds later you should be sitting on the main page (in my case it takes me back to my lockscreen as I didn't wipe any of the cache or data partitions)
Ok, that's it or now. Have fun and I'll post an update when/if I get the MAC or Bluetooth issues resolved.
So is the link to the update.zip the one with the sound fixed or calvins original?
It's the updated ROM with the updated MD5SUM for the file.
I can confirm this works. Thanks!
Sent from my Kindle Fire using xda premium
Yeahhhhhhh
Sent from my Nexus S 4G using XDA App
woot woot! Can't wait til Christmas comes around so I can play with my moms new kindle fire
Sent from my SAMSUNG-SGH-I997
You mention the video is not working, is it meaning that the video player in CM7 can't play any format of video?
Or is it just the flash video in the browser?
YouTube works, does Netflix?
Sent from my HTC Incredible 2 using XDA App
Just curious, how long does it take to go from stock to this cm 7?
loki154: Veritass tested the update.zip for me and he said that netflix worked for him.
ck_looi: I haven't tried anything other than trying to play youtube videos in the browser and they cause the browser to exit.
Ah yeah, flashing it now then.
Can you please try out any video format which suppose to work in stock ROM? Maybe can try out the mp4 video.
someone should make a video on how to install this
Sent from my ADR6400L using XDA App
I'm just another "me too" from the crowd, but thanks for continuing this project.
I made the decision to pull the trigger on the Fire after seeing the efforts to port CM7 and ICS to the device, and especially with Transformer Prime availability up in the air.
I know JackpotClavin did most of the work so far, but it's great that others are continuing the work he started, now that he's moved on to ICS work.
Like all the others, I'm excited to be able to enjoy the fruits of everyone's labor when I unwrap my self-bought Fire in a week and a half.
Thanks again.
Hmm, to get the market on this rom, would we just go by the instructions on the thread for the stock rom or should we flash the gapps by renaming it to update.zip?
don't know about the stock rom's way to do it, but in cm7 gapps is the way to go and it's proven to work on clavin's port so my money is on gapps
Poler166 said:
someone should make a video on how to install this
Sent from my ADR6400L using XDA App
Click to expand...
Click to collapse
here is the video:
http://www.kindlefirewire.com/2011/11/16/how-to-root-kindle-fire-video-tutorial/
iluretar said:
don't know about the stock rom's way to do it, but in cm7 gapps is the way to go and it's proven to work on clavin's port so my money is on gapps
Click to expand...
Click to collapse
http://goo-inside.me/gapps/
Which one should I download?
The tegra looks tempting, so does HDPI. Or should I just stick with universal?
tannerzion said:
http://goo-inside.me/gapps/
Which one should I download?
The tegra looks tempting, so does HDPI. Or should I just stick with universal?
Click to expand...
Click to collapse
Universal for CM7 at the top.
foxdog66 said:
Just curious, how long does it take to go from stock to this cm 7?
Click to expand...
Click to collapse
I'm doing it over and over so I have it down but for me all of a couple of minutes once everything is in place (meaning you've already rooted, you've already set up your android SDK environment and can talk to the device...)
The act of flashing and doing the various commands is maybe 2min from start to finish.
NOTE: I DO NOT HAVE WINDOWS, AT THE MOMENT! THE DEVELOPEMENT HAS STOPPED TEMPORARILY!! I'M SORRY FOR THIS!
Welcome to the original thread, of Beatsleigher's Root Helper!!
This program is completely free, with no Xtra options for donators...
What this program will do:Well this program is designed for beginners, and advanced users.
Beginners, can learn, about flashing. And learn, what to do, to get a custom ROM running...
Advanced users & pros, have a few more options, they can flash their ROMs, even some advanced options, like RadioOptions (If you know, what that is).
If you need to setup ADB drivers, then follow the steps, in the ADB -> Help menu!!
List of features:Several Reboot options,
Backup/Restore
Unlock bootloader (fastboot)
Relock bootloader (fastboot)
Root (ADB+fastboot)
Flash recovery (fastboot)
All-in-one solutions (Some new ones, again ^^)
Using a complete GUI!
Very explicit detailing of what the program is currently doing!
Install drivers - (USB + ADB/fastboot drivers)
List of ROMs/kernels
Help menus
Install apps, as user apps.
Install apps, as system apps.
Push files, to SD.
Flash ROMs.
Flash stock ROM.
Context menus!!
And much, much more!
What's to expect:In-program E-Mail subscription, to get notified about updates.
User experience program…
More updates
Requirements::[/CENTER]
This program requires following, to run:
.net framework +Ver. 3.5 (SP1)
.net framework 3.5 Client Profile
.net framework 4.0 Client Profile
Windows Installer ver. 3.1 & 4.5
It uses just over 30 MB of RAM (Excluding the scripts) on average.
CPU usage is at 5% at the moment
If RAM usage goes over 90%, the program WILL shut down... (Not the computer)
ADB is the ONLY background process, used by BRH (The only 3rd party process)
FAQ:Q:When installing the drivers, why do I need to change my system configuration?
A:You need to configure your machine, to notice the device, but to leave it alone, instead of looking for, and downloading drivers for it. This just confuses the computer, meaning you can't do anything in the bootloader, because Windows Update doesn't yet have the needed drivers...
Q: Why have you gone over to making a GUI? The batch files, were just fine...
A: I'm going over to making a GUI, because it is easier to use, less work. And I have the option, to just, drag & drop a button, write two lines of code, to make the button functional and then it's just a matter of creating the batch file, converting it to an EXE. Easy as pie. Whereas, with the batch files, to create one more option, you have to write 6 lines of code, then the batch file, and then half of the stuff doesn't work properly, because you didn't debug... If you know, what I mean...
Q: Why are there so many files???
A: This program needs so many files, so it can perform different processes/options/tasks
. But it isn't hard, to find out, what file, does which job
Q: Why is there only a version for windows??
A: I am working on a version, for Mac users, but it will take some time. I'm glad to be nearly finished, with the Windows version
Q: I want to donate to you, but you won't allow it. Why?
A: I don't accept any donations, because I only wrote the program to flash files on to your phone... I don't want to take credit for things, that other people did.
Instead of trying to donate to me, donate to chainfire, ChainsDD, and Kousik Dutta; for creating such brilliant recoverys, Apps (like superuser and ROM Manager) and ROMs...
BTW: If you really want to donate (which you won't ), you can send me some albums ^^ I need house music, to work.. And all my songs/albums have been listened dead -.-
Q: Do you mind if I use this program for commercial use, and post videos(tutorials) on Youtube?
A: As long as you DO NOT create mirrors, and let me know, I'm not that fussed... But then please post the link of the video to me, so that I can tell you if I like the way you did it, or not.
Q: When are you gonna stop talking about things, that don't interrest anyone (the FAQ)??
A: Now, but still thx for reading, other good questions will be posted here, aswell...
Thanks:Many thanks to Kouschik Dutta for creating the recoveries for near-to all Android phones. Yo the man!
And not to forget the awsome app: ROM Manager ^^
Thanks to my good friend Accendare (baddinski), for creating the splashscreen. I appreciate it much
Thanks to Google, for creating the AOSP, for the great developers, to create even greater ROMs, for us!
Also, thanks to Google, for buying Android, and making suh a (rather) bug-free OS!!
If I forgot anyone, please let me know immediatly!!
Downloads:
If you want to flash stock firmware, you will need to install this. This contains all the neccessary files/folders you need:
GSM: to be downloaded, by clicking this...
CDMA: to be downloaded here...
Current version (From the 28.03.2012 02:58 GMT +!) is 2.6.5.5.
There are some new and juicy features, that have come in this update. Especially, for those fellow developers So, give this a try, if you're not too busy ^^ Download here
Before updating, please run this...
Fulll release!! Version 3.0.0.8!!
It's an ISO image. I'll provide a link, to power ISO, should you not have an Image-mounting software, on your computer… If you have Windows 8 CP, you do NOT Need this…
Well, I hope, you will enjoy this new version!!
Download: Beatslei9gher's Root Helper_Install_CD Power ISO 5
Screenshots:View attachment 928851 View attachment 928852View attachment 966857 View attachment 966858
View attachment 966859 View attachment 966860
View attachment 966861 View attachment 966862
View attachment 966863 View attachment 966864
View attachment 966865 View attachment 966866
View attachment 966867 View attachment 966868
View attachment 966871 View attachment 966872
View attachment 966873 View attachment 966874
View attachment 966876
If you want to see more, download it
Installer:The installer will install to your C:\ drive. Some older scripts, are still working with "%homedrive%" so, to make sure, that everything is working, please make sure, that your homedrive is your C:\ drive. Or, if you have a seperate C:\ drive (like me), copy a copy, of the "Beatsleigher_root_helper" folder, to your homedrive. Then it should do the trick. By the tiome, the program is released properly (full) all scripts should be working with "C:\".
Should you have NOT got a C:\ drive, because your homedrive is named differently/you deleted the C:\ partition, see: installation help.
Requests:If you have any requestes (features, etc.), please PM me, or send me an E-Mail!!
Please read!!:
Befor moaning, that there are not enough ROMs/kernels, remember, since 2.6D ALPHA, you can flash both kernels & ROMs via ADB & fastboot!
Download, and see for yourself
Changelog:
Verison 3.0.0.8 (Full release):
All scripts were re-written...
A few changes...
Full release(!!!)
Version 2.6.5.7 (BETA) [Minor 3]
Working context menus!! (On selected forms)
And that was really about it.
Version 2.6.5.5 (BETA) [Minor 2]:
Added some juicy developer features! (Using the ADB shell)
A few options, for n00bs, are in there, aswell...
Added options, to the ADB menu.
Added a complete new form. (Dev. options)
Added a few more scripts. Making the update zise about 6MB, on your HDD
Removed some buggy code.
When navigating, from ADB menu to Dev. Menu, ADB menu closes, but can be re-opened from the "File" menu.
Dev. menu has also got CPU/RAM usage detector!
Download, for more changelog
Version 2.6.5.4 (BETA) [Minor]:
Working progressbars(!!!)
Added CPU/RAM usage detection.
ADB menu has got a makeover.
Added option to enable/disable CPU/RAM usage detection in fastboot menu...
Fixed bug in ADB help menu.
Cleansed the code (again)
I probably forgot the rest, or just find out, for yourself
Version 2.6.5.3 (BETA):
Removed bug that caused phone crash, whilst prompting device name.
Cleansed the code.
Removed two un-used forms.
Repaired the menustripbutton.
Added scripts, to update package.
Removed other scripts, from update package.
Compressed some, of the files (drivers, executables)
Using traditional installer, again.
Installation path set to: C:\Beatsleigher_root_helper\
Version 2.6.5.2 (BETA):
Fastboot menu fully working.
Fastboot help menu, is popping up/has been created, though it has no content.
ADB help menu is working/all buttons have a task.
Some unneeded code has been removed.
A complete list of ROMs & kernels is present (CDMA + GSM).
No change in the IE engine...
All messages giving a tone/sound.
Options have ben added to the ADB menu.
New all-in-one solutions for ADB menu.
Scripts have been edited, for more friendliness
More tooltips.
Progressbars still not working ( )
Maximization has been disabled in ALL windows.
Better usage of RAM, whilst opening other exe - files
Version 2.6.5.1 (BETA)
Added update check-support.
Changed file hoster to mediafire (updates coming from there)
Added ADB reboot options.
Fastboot reboot options working.
Added (hidden) features.
Using a proper installer.
Can be installed anywhere on HDD, will work anyway
Two packages are to be downloaded, not one. This ensures, that updates are working, as planned.
(Hidden features will be released, when version is 2.6.5.3 (next update) )
Version: 2.6 D:
Everything you see, down the bottom is working.
You can now flash a recovery via fastboot menu!!
Kernel and ROMs, I have decided, to take them back out. They were a bit buggy...
The size of the EXE itself, has gone up to, ca. 2.4 MB.
Option to flash stock ROM (LTE + GSM) has been enabled, for fastboot.
Looks a bit more friendly
Icons have been added!
You'll have to find the rest out, yourself
Version 2.6C:
ADB menu has been carried on. You are now able to flash a kernel (LTE & GSM)
It will open the Explorer for you, when you need to copy the file!!
LTE menu is finally working!! It had problems opening, due to a minor type-error.
Though the LTE menu is working, you will only be able to use one button, in about an hour. Once I've completed doing the ADB menu...
(See: "What's to expect", for more info's on what's coming!!)
Version 2.6:
New GUI!
Complete new code.
In-program help.
Direct link to thread.
Seperate fastboot and ADB menus!
More explicit details...
Removed the music, that pops up, upon start. (To many house haters )
All batch files converted to executables... (This prevents tampering with the code)
Fully compatible with 64x machines. Doesn't use as much RAM, but therefore shows up as a process.
Installation help:
Not much can go wrong, when install9ing this program.
Mostly, the reasons, of failure, to use this program, are due to:
Not having a C:\ drive.
Not copying a copy of the root folder, to hamedrive, if C:\ is not the homedrive, of your windows machine.
Tutorial 1:
Problem: I installed the program, but my homedrive is not C:\. I installed to C:\, but I can't use half of the program.
Well, first of all; sorry, for this. I could of said this earlier... I forgot to edit the scripts, to use ONLY the C:\ drive, so it useshalf the C:\ drive, and half your homedrive. But, that's why I posted this tutorial.
It's quick & easy ^^
Tutorial:
Install the program, to your C:\ drive. Close the installer, and re-open it.
Once back in the installer, set the installation path to your homedrive (Where Windows is installed).
Install to that directory, and done
It should now work ^_^
Tutorial 2:
Problem, I don't have a C:\ drive, and the ROM-Full/Less version, isn't available for download... What to do??
This is also no problem!! With a few, simple clicks of your mouse, we will fix this minor problem
Tutorial:
Type following key-combination, on your keyboard; START(WIN)+R.
The "Run" prompt should now pop up.
In the RUN prompt, type: "diskmgmt.msc" and it enter.
Once the disk manager pops up, shrink your homedrive(or, if you have unalocated disk space, which is 3GB or more, right click on that)
Shrink your homedrive, about 3GB. If you can, allocate more space, because you will need quite some space, because of stock ROMs/custom ROMs/kernels and backups.
To shrink, right-click on the partition and select "Shrink Volume". Enter this amount, to shrink: 3072 MB, that should be 3GB. Like I said, feel free to allocate more space.
Now you should see a black field. This is unallocated disk space. Right click on this space and select" Create simple partition" Make sure, you create the exact space, you shrunk, other wise, you will have some unallocated space, on your HDD and this can cause problems, if unnoticed.
Name the partition : C:. Wait, for the Diskman. to create the partition (can take up to 5 Minutes, for that amount of space, depending on size of HDD, CPU clock speed and amount of RAM).
Now, just install Beatsleigher's Root Helper to your C:\ drive and again, to your homedrive. Done! You can now use Beatsleigher's Root Helper.
If you should notice any other problems, please let me know, so I can solve them.
EULA:Please read the EULA, should you not have, during installation. Or, you are interested in installing the prgram.
There is vital information, in this text document!
Some misc. text
Hmm... I'm at the end of my stream of thoughts...
Now, I'm asking YOU!
Please tell me, what would you like me, to add to this program.
Don't forget, if you like this program, and you are happy, to recommend it. Don't be shy, post your thanks, and a comment or two. Hit the thanks button. Even if you are dissatisfied, just post a comment, and I'll try and do it better.
If you are a junior member, send me a PM, and I'll post it for you
I'll ask again;
I know, I'm not that well known, and I know, I've done mistakes (ROM-Full version)
But, I'm trying to make this program, a better enviroment, for everybody. Please, would you give it at least a try, instead of just ignoring this...
NOTE: Short term for: Beatslleigher's Root Helper: "BRH"!!
To prevent confusion, in future!
Well, I mentioned there will be a working version on Linux, right? Well, I only just found out a few days ago, that you can use wine to emulate Windows... :O Well, there you are! It works pretty much fine, but then a agin, there will be a few bugs, so I'll get on to that...
Sorry for not updating this thread, for such a long time... I'm using UBuntu, and I've got quite a lott to do, as the schoolyear is coming to it's end
News, tips & tricks!!
News:
IMPORTANT:
Verizon has just released their version, of the GNex...
Beatsleigher's Root Helper, will be one of the first, to provide their images, for recovery... Other than that, everything will be the same!! I'm updating the files, right now!!!
New concept:Beatsleigher's Root Helper, is written and hosted by one person: me. I have been working hard, and have noticed, that I need to change the concept. Instead of being big, and cluttery. It is now small and efficient. Like a car manufacturer, I am working hard, on producing a very small, but powerfull piece of technology (in this case, virtual technology). And, instead of relying on the user, to type everything, this new version, needs only a few clicks of a button. As an example, the first version, which used a lot of RAM, and waisted processes, used up (with all ROMs/kernels/bootanims) over 1 GB. Now, you can download the ROMs, you wish and kernels, and just flash them, with the click of a button. The best thing is, all of the data, I provide version 2.xx with, the size comes out, at a maximum of 300-350 MB of disk space. (Counting both CDMA & GSM stock ROMs).
Beta has been released!!:After a few weeks of hard work, I can finally say: "I'm almost done!"
It took 4 weeks, 3 Albums, 5 DVDs, 5 Gigs of HDD space, and lot's of testing.
But now, It's nearly done, and I'm proud of it.
This project will NEVER be abandoned. (Unless the GNex gets boring, at some point in time)
It brings a lot of new features with it, including working help menus.
This is also a new part, of the concept, keep it in BETA, untill EVERYTHING works. Of course, I will keep it updated and will constantly change it, to make it better, and easier to use.
If you like it, you may also advertise!! (Just a tip. I also have competition...)
Askng for help?!:Yes, I'm asking you, for help.
After all my hard work. It seems, noone is downloading it...
That's why, I need you, to post requests, and suggest things
I think, it's important, for me to know, what YOU really want, in this program.
Don't be shy, just post your opinion, and suggest someti=hing, to make it better
And if this, doesn't help, I will probably close this thread, and leave this program, as it is, and start other projects, for other phone's, like: HTC devices.
I shall then declare this program as final. This is not giving up, it's you not giving it a chance... But anyways, back to the point: I need you, to tell me your oppinion!!!
Google has done it again!:
After some time, on 4.0.2 (Stock), Google has released the stock version, of 4.0.4, for it's flagship devices (Motorola Xoom WiFi, for some reason, aswell..)
I am currently downloading the factory image, and will be creating an installer, so you can enjoy the joys, of 4.0.4!
So, again, another thing, to look forward to, when using this program!!
Windows metro style app!:After the nearly complete nervous breakdown, of my computer, I have decided, to install Windows 8 Cons. preview.
Whilst installing the new OS, I was downloading the SDK, VS 2011, and decided, because Windows 8 will be available, next month, I shall start creating this program, also as a Metro-styled app.
I, however, have decided, to keep the style secret, and keep on developing, and as soon, as Windows 8 is officially released, I shall also release the new program. If, however, you are lucky, I will have enough time, to work on this new project, and release it in a week, or so
But, as I said it depends, on whether, this program get's downloaded a bit more, or not, and if I am quick enough, on deving this...
Having trouble, with Wndows 8?Well, I have found a solution, to all your ADB/fastboot problems...
Interested? Click here...
The thread contains all info, you need, to install and configure the ADB drivers, on Windows 8...
If you have a problem, please let me know, by either: Answering the thread, sending me a PM, or post your problem here...
New cooperation!!: Because so many of you, are wanting more kernels and ROMs, I have decided, to cooperate, with sonicxml This means, there will be an option, for you, to flash his kernel img, via fastboot. This means, there is one less step, in the al-in-one procedure!!
So, I'm thanking him, for accepting my request
CDMA issues I've come to notice, that some people, are having issues, with their CDMA devices...
This will be fixed, in the next update, release will be, in a few days. I'm very sorry, that this has happened, whilst testing, I didn't have any problems, what so ever...
But, because I guaranteed you, that I will fix ANY and EVERY bug, that you/I can find, I've already started, on a new and better flasher, for 4.0.2 stock flashers...
These will be hosted on my FTP server, in future, so the program can download the files, itself... So that shouldn't be a problem.
Should you have any more problems, please let me know, IMMEDIATLY, because, there is no point, in me updating, uploading the files, and literally half an hour, after release, someone tells me, that they're having problems, for a few days...
So, please. Tell me, I'm always happy to help. That's what I'm here for
Info's on updates...
All-in-one fix: Well, it looks like I've managed to fix the all-in-one problem... It seems, that there was an error, whilst in recovery. Added the feature; it flashes an insecure boot image... This allows the recovery, to stay put, and it grants the ADB remount access... This means, you are as close to stock, as possible, but you are fully rooted...
You shouldn't trust Windows. Period. I dont really get why you say scripting is harder on Linux though.
Batch files are nice, allows one to see what will be done. I would prefer them over a binary, but then again, I dont use Windows.
May the force be with you.
bk
bk201doesntexist said:
You shouldn't trust Windows. Period. I dont really get why you say scripting is harder on Linux though.
Batch files are nice, allows one to see what will be done. I would prefer them over a binary, but then again, I dont use Windows.
May the force be with you.
bk
Click to expand...
Click to collapse
Thx for the force
I said it's harder scripting for Linux, because I'm a noob, when it comes to Linux/Unix... I only just found out, that Linux has the drivers for my laptop a few days ago And I'm used to Windows, that's why I said it.
Is it possible to provide a version without rom to have a good size? 400Mb is big.
Thanks for the time you spent in this project
imfloflo said:
Is it possible to provide a version without rom to have a good size? 400Mb is big.
Thanks for the time you spent in this project
Click to expand...
Click to collapse
Currently working on it I'm just removing some scripts
To all size lovers!
The size has gone down, to under 60 MB.
I'm trying, to keep it under 80MB...
Thanks, for using Beatsleigher's Root Helper!!
Facebook page now open!!
Hey guys, I've created a FB page, for Q&A as well as the Q&A Thread, in the Q&A section (thx imfloflo)
There are also a few other things, which might interest you! So give it a looksee, it's not done yet, it will also take a while, because I'm busy with school and my root helper...
But, here's the link^^ Beatsleigher's Facebook page!
Info on 2.6 ALPHA (GUI version)
Please read!
This builds are only alphas. As most of you know, alphas are very buggy... I'm doing my best, on keeping them bug-free, so please don't complain about them not working properly... Some menus also haven't been taken care of, I know. If you are looking for the version, that works best (at the moment), take/download the ROM-Less 1.2.7 version.
Why did I jump from 1.2.x to 2.6?
There have been many unreleased version, during the batch period. Well, they weren't unreleased as that, they weremore or less kept for private use, because it was too big, to upload/for you to download. So I kept it on my HDD & USB flash drive.
Info on 2.6B ALPHA
ABTextBox1.Visible = FalsDB menu working properly. All buttons have got their purpose. All linken with an "OpenFileDialog" so you can flash like that. You just choose the file you want, open it and click on "push". The same goes for ROMs. Fastboot menu is planned to work in 2.6C or D.
BTW; have you noticed, that the size of everything has shrunk, again? Well, guess what, it will start to rise, soon. Why? The program you asked for is nearly 2 MB :O
Well, I hope you had fun reading, and I also hope, you know, why the updates are taking so long
Ok, the beta will be delayed, again.
I'm currently busy, and not near home...
I'm currently writing a EULA. So, please read it. It will prevent lots of miss understandings... It's not drastically big, nor hard to understand. It will be uploaded, as a txt file, and provided in the next update package. ...
I guess, the update will be released at about 18:00 o'clock GMT +1.
Who care's how I sent IT?
Hey familyguy59!
Thanks for pointing me to your thread, I've installed the helper...I've selected all in one, unlocked and booted the phone in to CWM recovery - the one screen instruction is saying to apply the zip? I think ive missed a step - I'm not sure what zip! I haven't copied one across to the phone!
Any help would be great.
My goal is to flash 4.04 (stock) to the phone.
I have superuser on the phone now...(so it must be rooted right?)
Sorry for my lack of knowledge!
HSKalay said:
Hey familyguy59!
Thanks for pointing me to your thread, I've installed the helper...I've selected all in one, unlocked and booted the phone in to CWM recovery - the one screen instruction is saying to apply the zip? I think ive missed a step - I'm not sure what zip! I haven't copied one across to the phone!
Any help would be great.
My goal is to flash 4.04 (stock) to the phone.
I have superuser on the phone now...(so it must be rooted right?)
Sorry for my lack of knowledge!
Click to expand...
Click to collapse
Well, once you have entered the CWM recovery-program, you should see an option, named: "install zip from sdcard". Once there select: "choose zip from sdcard", and on the SD, you should notice a zip called "su". Install that. That's what's ment with "Apply zip"
But, as you have got superuser, you should have done everything right .
And, it's no problem, your lack of knowledge I'm happy to help everyone, who asks. Should you not have root (no superuser prompts), use the other all-in-one option That should then do the trick.
Now, to installing stock 4.0.4. You can download the zip, and then install via ROM Manager, it should also be present, on your device.
Make sure, though, to create a backup.
Thanks for using Beatsleigher's Root Helper It's very much appreciated
familyguy59 said:
Well, once you have entered the CWM recovery-program, you should see an option, named: "install zip from sdcard". Once there select: "choose zip from sdcard", and on the SD, you should notice a zip called "su". Install that. That's what's ment with "Apply zip"
But, as you have got superuser, you should have done everything right .
And, it's no problem, your lack of knowledge I'm happy to help everyone, who asks. Should you not have root (no superuser prompts), use the other all-in-one option That should then do the trick.
Now, to installing stock 4.0.4. You can download the zip, and then install via ROM Manager, it should also be present, on your device.
Make sure, though, to create a backup.
Thanks for using Beatsleigher's Root Helper It's very much appreciated
Click to expand...
Click to collapse
Thanks for the swift reply!
Is there any way for me to get back in to clockwork (the touch recovery) via the phone alone? When I've tried it (vol up + down + pwr) then recovery...it seems to be the stock one (droid lying down, with red triangle)
I'm installing rom manager now though!
HSKalay said:
Thanks for the swift reply!
Is there any way for me to get back in to clockwork (the touch recovery) via the phone alone? When I've tried it (vol up + down + pwr) then recovery...it seems to be the stock one (droid lying down, with red triangle)
I'm installing rom manager now though!
Click to expand...
Click to collapse
Hmm... It seems, you didn't flash via ROM Manager, or worse, it didn't install onto your phone. I'll get onto that, as soon, as I've got my computer up and running again (The one I'm currenly using, is not mine...).
Well, as soon, as you have flashed via CWM, just choose "Flash recovery" from the fastboot menu, this should then give you the Touch-enabled version.
As I said; once the recovery has been flashed, via CWM, you should be able to access it, by the app, and using VOL UP+DWN and PWR...
No prob, by the way. I always try to reply ASAP.
HSKalay said:
Hey familyguy59!
Thanks for pointing me to your thread, I've installed the helper...I've selected all in one, unlocked and booted the phone in to CWM recovery - the one screen instruction is saying to apply the zip? I think ive missed a step - I'm not sure what zip! I haven't copied one across to the phone!
Any help would be great.
My goal is to flash 4.04 (stock) to the phone.
I have superuser on the phone now...(so it must be rooted right?)
Sorry for my lack of knowledge!
Click to expand...
Click to collapse
Oh, yes. I forgot to mention: The program pushes the zip file automaticly, to your SD, to make the whole process, as comfortable, as possible
familyguy59 said:
Hmm... It seems, you didn't flash via ROM Manager, or worse, it didn't install onto your phone. I'll get onto that, as soon, as I've got my computer up and running again (The one I'm currenly using, is not mine...).
Well, as soon, as you have flashed via CWM, just choose "Flash recovery" from the fastboot menu, this should then give you the Touch-enabled version.
As I said; once the recovery has been flashed, via CWM, you should be able to access it, by the app, and using VOL UP+DWN and PWR...
No prob, by the way. I always try to reply ASAP.
Click to expand...
Click to collapse
It's weird because, I have flashed CWM via the app on the phone, and the flashed the touch version...but still doesn't show up when I manually get in to recovery. But via the app it enters the touch recovery.
sorry, your thread is going a little off topic now!
HSKalay said:
It's weird because, I have flashed CWM via the app on the phone, and the flashed the touch version...but still doesn't show up when I manually get in to recovery. But via the app it enters the touch recovery.
sorry, your thread is going a little off topic now!
Click to expand...
Click to collapse
Yes, that is indeed strange. It could however just be a bug.
If you want to try, you could flash the recovery via BRH, and see if there's a difference.
familyguy59 said:
Yes, that is indeed strange. It could however just be a bug.
If you want to try, you could flash the recovery via BRH, and see if there's a difference.
Click to expand...
Click to collapse
BRH...sorry what is that?
HSKalay said:
BRH...sorry what is that?
Click to expand...
Click to collapse
Short term, for: Beatsleigher's Root Helper
familyguy59 said:
Short term, for: Beatsleigher's Root Helper
Click to expand...
Click to collapse
ha, I should of known that
You wouldn't happen to have a link handy, to the cwm rom i can flash? (or know where i can find it on my machine?!)
*edit its ok, i found it! it was under fastboot...i was in adb
* Second edit, nah, still didn't work.
i'm leaving it for now, don't wanna mess the phone up. I'll blank everything and start again one day.
Since the information for this device is so fragmented, I decided to attempt to keep it all in one (or a series of) posts. I aim to link to the original posts as well as outline what do to with your device from the time it leaves to box to running the latest and greatest modified rom or CM9 or whatever else is out there. I will not link directly to anything, rather I will link to the thread, and I very seriously recommend reading at least the post, if not the thread, before you begin ANYTHING.
This guide is a work in progress, it is not complete, and I will work on it bit by bit until it's completed!
Section 1: So its shiny and new...how can I MOD IT?
This will be assuming the new shiny toy in question is indeed an Acer Iconia Tab A100, this is not meant to cover any other devices. And, this is assuming it's coming with Honeycomb installed, in stock form. If its used, or comes with ICS, the next section will amuse you.
First thing most users that want to mod their devices do is root their device. Now, rooting is not unlocking, as carrier unlocking is not boot loader unlocking. Rooting a device allows you to access the system in a much more in depth manner, including read/write (R/W) access to the /system partition, among other things. It allows use of programs such as Titanium Backup (TB or TiBu) ROM Toolbox, overclocking or other clock setting utilities such as SetCPU or CPU Master for overclocking (if the kernel supports it) underclocking and undervolting.
So...how do I do that rooting thing? Well assuming you are running Honeycomb and are wanting to update to ICS plus root and unlock the bootloader, we will use the info from this thread Simple Root Method by ZeroNull to update you to ICS and then gain Root access on that new ICS install!
What about rooting Honeycomb? Well most users are already running ICS and prefer it, and those on Honeycomb are likely wanting to update to ICS, so I will leave this out for now. If I have the time I will come back and include the link for that as well.
Now, ICS is installed, and you're rooted, what else can I do? Well you can unlock your bootloader, and load up a custom recovery such as CWM or TWRP and using those, install Custom ROMS! For this, we visit this thread here Install unlocked bootloader by ZeroNull. Follow ALL directions in this thread for a fully unlocked bootloader!
Custom recoveries, what are they and how do I get that shiz? Custom recoveries, CWM and TWRP, allow the user to flash anything they want, provided its for their device and properly packaged. This included custom roms, some tools, and allows you to "wipe" various parts of the device's storage and backup/restore to a previous installation. Powerful, and dangerous, do not go pushing buttons to things you do NOT understand! Also, you MUST delete or rename /system/etc/install-recovery.sh prior to flashing recovery! This will restore stock recovery every time android boots, wiping out your custom recovery. The only time you want that file there is if you are using the crossix mount swap mod, which replaces that file with a modified version that leaves recovery alone.
Safe to do wipe:
Wipe cache, data, dalvik cache, system. Theonew also reports Flex and boot can be wiped as well as SD-EXT. This is not to be confused with External SD, this is a separate partition on your External SD card, wiping it will NOT wipe external SD, only what's installed on that partition, the rest is safe and requires a separate wipe.
If you wipe system you MUST install a new rom or restore from backup!
If you wipe boot please restore or install a new ROM before rebooting! Safety first.
Not safe to wipe:
Don't wipe anything else, and always install a new rom or backup after wiping system!
Never reboot system after wiping without first restoring or installing a new ROM!
Post 2 will cover custom recovery functions in more detail, for both recoveries.
Now that you have an unlocked bootloader, what can I do? Install that custom recovery! There is two flavors, CWM and TWRP, CWM available here CWM Recovery by ptesmoke. Follow the instructions in this post to the letter! Only attempt this after you have ICS, rooted, and unlocked the boot loader correctly! Next we have TWRP Recovery here TWRP Recovery by ZeroNull. Again, follow the instructions to the letter, and attempt only after ICS, root and unlocked boot loader are finished.
Ok, gots me some custom recoveries, what about custom roms? This is why we just did all that work, to prepare for this! Custom ROMs! I'll be listing some (all?) ROMs that you can use, besides stock HC and ICS.
The list in order of version, oldest to newest, updated to retired:
4.0.3
KEBBERSROM by Hardslog Stock based 4.0.3
Flex Reaper by civato ICS 4.0.3 Modified Stock
Green ICS by lgcmn & ZeroNull ICS 4.0.3 Modified Stock
4.0.4
KEBBERSROM SHELLSHOCK by Hardslog 4.0.4, based on A500 and A700 ROMs
Nightly Builds of CM9 by pio_masaki ICS 4.0.4
Aoikaze Modified CM9 by pio_masaki ICS 4.0.4
4.1.1
CM10 Preview builds by waydownsouth 4.1.1
4.1.2
Unofficial CM10 builds by pio_masaki (stock and modded, Phone UI and Tablet UI)
Jellytime Sosei by pio_masaki Jellybean 4.1.2
Cyanosaki_Flex by Hardslog
4.2.2
CarbonROM JB 4.2.2 Unofficial by pio_masaki
These are most of the ROMs. There are others that seem to no longer be in active development and are based on the old leaks that vache was kind enough to grab for us. Development is currently only active in the KEBBERSROM builds by Hardslog, and occasional updated in the CM10 builds by pio_masaki.
That ends Section 1, preparing for awesomeness, and Post 2 will continue with installing your new custom ROM!
Section 2: Recoveries and what they can do for you.
This section will cover recoveries and what they can do, and how to do it. I will be starting with TWRP, as I use that on all of my devices, and after that I will include a CWM section, as a lot, if not most, use that. They are similar in what they do, but different in where things are.
TWRP Recovery
Official TWRP for A100 by linuxsociety
This assumes you have already done everything in section 1, including installed ICS, rooted it, unlocked your bootloader, and installed TWRP custom recovery. Links for this information is provided in Section 1, in the post above.
First thing you should ALWAYS do when you enter recovery, before doing ANYTHING ELSE, is make a nandroid backup!
Getting into recovery: Depending on what ROM you use, this is done a couple ways. First is an AOSP ROM, like CM9/AOKP, which you can hold the power button, then select Reboot, then Recovery. In modified stock or rooted stock ROMs, this menu doesn't exist, you can either use an app like Quick Boot, and select recovery, or power off, then hold the Volume - key (closest to the rotation lock switch) and while holding it, hold power, once the acer screen comes up and starts saying Recovery kernel, release both and recovery will boot provided an update.zip is NOT on the root of your external SD card. This method works for any ROM.
Now I'm in recovery, what do I do? As I mentioned, make a nandroid backup before you do ANYTHING else! From the first screen (home screen) in TWRP select Mount. In mount you can leave everything alone and at the bottom will be two options with Circles. Select Using external SD Card for Backup. This will store your backup on your external SD card, never use internal SD if possible. After you select use external SD, press the Home button in the upper right corner. Now, back on the Home screen, select Backup. Double check the boxes checked are System, Data, Boot and Recovery. At the bottom is a nice little slide bar, slide that over and sit back. Takes about 4-5 minutes depending on how full your device storage is. This does NOT backup internal SD! After this is done, you have created a nandroid backup that when restored will put the system exactly how it was last time you used it. You can make multiple backups of multiple ROMs without issue, just however big your SD card is to hold them.
The restore menu, or the OOPS SAVE MEH menu is your best friend. This will restore you back to the last state your device was in for the backup that is restored. By default TWRP saves by date and time, however you can rename this with any file manager, never caused me any issues. Theonew reminded me of an MD5 issue that can happen on renaming backups, if this does happen, rename it back to the stock naming system to fix it. Generally I'll just append the ROM name to the front, so instead of 2012-6-14--18-25-01 it'll be CM9-2012-6-14--18-25-01. Make sense? That way to restore it in case of error, just drop the name. Easy. Theonew also did some testing, and confirmed that spaces in the folder name WILL cause MD5 errors and fail the restore, please use ONLY dashes and underscores (- and _ lol) in the folder name! To restore make sure you are on the Home screen, then select Restore. In the window you will see a list of your current backups, select one. Next screen has check boxes, make sure System, Data, Boot and Recovery are checked, then slide the bar to begin. This takes a bit, make sure you let it finish! Once done, your system will be at the last point it was used for that backup.
Advanced restore...I'm to lazy to reload and reset up my stuff after a ROM flash, so this is the fast and dirty way of doing it. If you flash a ROM and you don't feel like manually restoring your apps, you can uncheck System, Recovery and Boot, and leave only Data checked. This will restore your user installed apps and settings over the current ROM install. I don't recommend this for different ROMs, only for updates of the same ROM! Up to you but if you get alot of issues, you'll know why. After advanced restoring, go to the Home Screen and select Advanced, then Fix Permissions. Press Home again and select Wipe. Wipe Cache and Dalvik Cache, then reboot system.
Alright, enough already lets get our flash on! From the Home screen, select Wipe, then press on Cache, Dalvik Cache, Factory Reset, and System. Optional you can wipe Battery Stats if your battery seems off. Leave the rest alone. Once these are all wiped, go back to the Home screen, and press Install. The window on the left is your device folders, window on the right is contents of the current folder. I hope you remembered where your rom.zip is, because you select it here. Press on the zip for the ROM of your choice, then slide the bar to flash it. After that is done, select the left button Wipe Cache and Dalvik, then select Reboot system.
OK LETS ROCK THAT ROM! Woah, slow down scooter, there's a few things to do, or not do, first. After it boots, meaning it's past the boot animation and is sitting on the Welcome screen, set it down and leave it alone for 10 minutes or longer. Don't sign in, don't do anything, just leave it be for 10 minutes. If you can't think of what to do to manage the time you have to wait for awesomness of custom ROMs, read the thread of the ROM you chose. Set the thread for 50 posts and just read. After 10 minutes, hold the power key, and either choose Power off or Reboot, Reboot depending on ROM used. After it finishes rebooting (that was alot faster wasn't it?) you can go ahead and do the Welcome stuff, log in to Google, setup your device, download your apps, restore your apps etc. After restoring your apps (try not to restore app + data if possible, though I know games and stuff you'll want to) reboot one more time. After that second reboot, use the tablet as normal. From my experience this offers the BEST possible ROM usage, a vast reduction in lag, bugs, and oddness.
What else can I do with the TWRP Recovery? Well, the most useful tools are Backup, Restore (and advanced restore) and the wipe menu, plus fix permissions. Those generally can fix anything thats wrong. If you notice alot of lagging, FCs or general unruliness, wipe Cache, Dalvik Cache, and Fix Permissions. Another useful ability is ADB, which is beyond the scope of this section, but may be included generally in a later section. ADB can be used to repair otherwise bricked devices, and offers a very large amount of tools that you don't normally get to use in Recovery. Keep in mind ADB is powerful, and can quickly destroy your device, so please, be careful using it.
Placeholder for CWM Recovery section - coming soon!
CWM Recovery for A100 by ptesmoke
Section 3
Additional Recovery tools:
Blackhole Wipe/Nullifier by pio_masaki
These are tools I created to make wiping a little easier, but please read the post completely before deciding to use it! There are multiple versions, and they can and will wipe internal SD, as well as take up to 40 minutes to run (1, not all). Please ask questions if you have them there and I will help as best I can!
AROMA Recovery Touch Recovery
A touch file manger to be used in recovery, even on non touch CWM! Good for renaming backups as soon as you make them (I tend to forget afterwards and get confused by 6 backups with just dates). Also moving a downloaded zip from internal to external or whatever before running a system wipe, any number of things. Please read the post completely before using this tool! It can cause damage if not used properly and with care!
Kernels:
linuxsociety / godmachine's A100 OC Kernel
Plenty of extra balls thrown in for good measure, a good place to look if you like high benchmarks and plenty of extra goodies baked in. Available in a few flavors, with some GPU OC thrown in for good measure.
ezterry's A100 OC/UV Kernel
The only other option for a kernel that we have besides stock and CM9's included kernel. Excellent kernel, really wakes up the A100, allows up to 1.5 GHz for some extra umph and undervolting to help conserve power on our very weak batteries.
PRO TIPS:
The 10 minute rule:
The reason I mention waiting 10 minutes on first boot of a ROM install is this: Alot of things happen the first time the ROM runs, alot of scripts run, the kernel has to settle and search and move things, files are flying all over the nand. Think of a tornado in a cubicle. That's first boot for your device. Allowing it 10 minutes uninterrupted allows all of that to happen and settle down. The following reboot lets all that new info fire up from it's new home and continue settling in. After restoring and downloading apps, that reboot allows that new info to settle into it's new home and the system to catch up. This isn't device specific, rather a general rule of thumb for all devices. Does not really apply to restores unless something is changed.
Undervolting:
Undervolting on this device is only available on ezterry's excellent kernel. The following is a rough guideline of how to do it, and do it right:
Start small, don't just dump it -200 and expect it to work. For the time you're testing, make sure it is NOT set for boot. If something goes wrong you don't want it doing it everytime it boots, right? Go in small increments, -25 is usually OK. For now, don't overclock. Starting at 1 Ghz, lower every speed range down -25, and run the device for at least 10-20 minutes, normal use, hard use, benchmark, browse the web, watch a HD movie. If all is fine and its not lagging, freezing, force closing or heating up more then usual, move everything to -50, and repeat. My device freezes at -150 but runs stable at -145. Every device and chip is different, mine may do -145 yours may do -175 or only -50.
Overclocking
Overclocking is available on ezterry's bodacious (already used excellent) kernel, up to 1.5 GHz, and the CM9 kernel up to 1.4GHz. As with undervolting, this should be done in small steps and tested between to find your max. Generally 1.5 GHz is fine for every device, however all devices and chips are slightly different, and some may not be stable at it. Mixing undervolting and overclocking can be tricky, but following the steps above for undervolting you can find that sweet spot for your device.
Batteries and why they fail
This section is entirely my opinion, other's swear one way, other's another, but this is what I've concluded from multiple posts for this device.
Consider 10% to be 0%. There have been more then a couple posts that say they let their battery fall below 10% and they can NOT get the device to work properly again afterwards. I think there's a few reasons for this, and I'll explain them now. First, a lot of batteries tend to have some kind of breaker protection if the voltage drops below a certain level. This is to prevent damage to the cells, which it does, however we can't close that breaker to restore activity from the battery, IE, it's dead anyways. This threshold varies from one device to another, one battery pack to another, some can go to 0% and be ok, others can't. I say voltage level, because while draining the voltage can spike up, and it can also spike down, which can fall below this threshold even though it says you have 5% battery life remaining, and trigger the protection.
The acer does not seem to power on without a working battery. If the battery is "dead" it doesn't seem to boot. Its basically a brick until either the battery is replaced (by acer I would assume) or the motherboard is replaced due to some sort of damage causing this. Replacing the motherboard costs almost as much as a new unit, so at this point, just save up some more and buy a new one.
For this, I never go below 10% if ever possible. Even on my phones.
Another thing I try not to do is charge in bursts, or at random times. Basically, I plug in at 10%, then allow full charge to 100%, I don't charge in between those ranges, and I don't charge for periods less then 100%. So I don't plug in at 48% then unplug at 60%. I've learned this one from my Evo 4g, the battery was fantastic for months, then I started using the car charger to top off, and the battery life over the course of 2 weeks took a very noticable hit on overall life. I lost easily 4 hours a day usage on it. This on a phone and ROM combo that got me 16 hours a day.
Again this entire section is just what I've noticed and is purely my opinion, please do whatever you please with your device, it is yours after all!
ADB and Fastboot...is it really a faster boot?
No, fastboot isn't a toggle to boot at warp 9. Fastboot is a mode you can put your bootloader into for flashing the system for upgrades, repairs, mods, or general havok if you're not careful. The bootloader is what you see when you first turn on your device, that lovely Acer logo with the text up in the left corner (usually saying bootloader version and Unlocked Mode if unlocked, or nothing if it's locked). If you go into fasboot, it will say download usb protocol, so if you see that, you're in fastboot mode for whatever reason.
How do I get into fastboot mode?
Well you can do this in a couple ways, either Quickboot app (reboot bootloader), if you're on CM9, the power menu will give the option, or you can use ADB for it.
adb reboot bootloader
I'll explain some more about adb after fastboot, I know its odd, but one does have something to do with the other at times.
Once you've rebooted to the bootloader (device will turn off, vibrate, then boot to acer screen) you can then issue your fastboot commands assuming 2 things:
Acer USB drivers are installed and working correctly (if you use adb to reboot, then it is)
Your tablet is connected to your PC over USB.
Now, at this point, its up to you to do whatever you want, but BE CAREFUL USING FASTBOOT FLASH! It doesn't care or check what you're flashing, it'll just flash it. For example, I flashed CWM Touch recovery to boot once because I was distracted and mixed up the images for whatever reason. End result: Can't boot android. Why? Because boot was recovery, it only booted to CWM Touch recovery. Booting to actual recovery booted to TWRP, which was my previously installed recovery. I got it back easy enough once I figured out what I did wrong, but not all mistakes are reversible, or fixable!
General Fastboot uses and commands...
general layout goes like this:
fastboot (this is calling the command) flash (this is what fastboot will do) recovery (where it will send it to) recovery.img (the file it will send)
So, it looks like this:
fastboot flash recovery recovery.img
it will then flash whatever img to whatever partition you said, and let you know when it's done. You can flash any img to any partition, provided it fits, which means you do have to be careful about what you flash to where!
when you are finished with fastboot:
fastboot reboot
There are plenty of other commands, but the general basic use of fastboot is to flash a recovery or bootloader, so that is what I laid out above.
This section is hugely in need of improving, I know, but the guide in general is still rough, my apologies.
What about ADB?
ADB, or Android Debugging Bridge, can be used in System or in custom recoveries to interact with the device behind the curtain, meaning what you do isn't readily apparent on the device itself, unless you do something obvious like reboot it. ADB has a ton of commands, in particular in ADB Shell mode (you drop into the device shell itself, issuing commands from within itself, not from the PC).
Some random ADB commands:
adb reboot (where to reboot to) so:
adb reboot recovery
adb pull (what file to copy) /(where to copy file to) so for example, a recovery log to the adb working folder:
adb pull /cache/recovery/last_log recovery.txt
adb push /(file to copy to) /(file to send to device) so for example, placing that recovery file back into the device:
adb push recovery.txt /cache/recovery/last_log
Thats all the time I have for now, sorry in advance, I'm still working on all of this, I swear lol
Placeholder for additional tips and usage, some ADB stuff, and anything else I can think of.
Placeholder for Toubleshooting.
Placeholder for FAQS.
System Modding
justjackyl's Iconia A100 CM10 Setup & Use Tips/Tricks
A good guide to check out to try to get the most out of your A100 on CM10 (or any JB ROM like Sosei/black bean). A must read for those new to CM10/JB on these devices or in general. Not an outright mod, but a good source of information about some modding you should browse.
Hulu Flash Hack by NoSudo
What the Hulu Flash Hack by NoSudo does is allow you to use our android browser (setup according to the thread) to watch sites like Hulu to play on your android flash player. Its basic function is to scan for, then backup, then place a modified libflashplayer.so file. Setup with script manager and run at boot for best results. As always, read the thread for more information.
Mount Swap by crossix
What the Mount Swap by crossix does is pretty awesome, it mounts your external SD as internal, meaning your 32GB external SD card shows as internal, and is used for your apps, data, downloads, whatever, as if it was your internal SD. Internal SD is then mounted as external SD. It's operation is based on install-recovery being replaced with crossix's version. Instead of replacing recovery, it runs the mount swap. Requires Root, as the file is placed into /system/etc. Designed for stock/modified stock ROMs, it can be used with AOSP/AOKP ROMs by using script manager and setting it to run as Root at Boot. Please read the thread for the files and information on how to use it.
Adapted to ICS Build Prop Mods by patrick_spd4u adapted from crossix
What the Build Prop mods do is pretty basic, however can greatly increase the abilities of the A100, including faster boot times, more apps/games available for download in the Play Store, and tons of other stuff. Adapted from crossix's mods for HC.
Guide to 2 ways of running the crossix mount swap script, Acer based and AOSP/AOKP based
Direct paste from a post I made about this earlier...details using ES File Manager, however you can adapt it for any root file manager.
Using your tab, download the crossix mod zip file.
Unzip the file to get your epic mount swap mod by crossix, it can be unzipped anywhere.
At this point, I'm using ES File Manager but you can use Root Explorer or whatever. I'll be giving directions for ES.
Go into settings, scroll down and check the box for Up to Root.
Scroll a little futher down, same menu, and check the box for Root Explorer. Tap Yes, then allow when SU asks.
Now check the box next to Mount File System.
A little notice should pop up saying system is writable. If it fails at this point, you'll need to reroot, though it should work fine.
Press back, and go to where your crossix install-recovery.sh file is, hold your finger on it, and select Copy from the menu.
Press back and keep pressing it until you get to /. You'll see folders like acct, cache, config, d, etc.
Scroll down to system, and tap on it to go into system
Tap on etc to enter the etc directory.
You should now be in /system/etc, check up top there will be the address bar showing where you are.
You shouldn't have an install-recovery.sh file there, but if you do, long press it and select rename, then rename it install-recovery.bak.
On the upper buttons, select paste.
Now hold on the install-recovery.sh and select Properties, all the way at the bottom of that menu.
Next to where it says permissions, click Change
You will get a new window showing 3 rows of 3 colums of boxes with Xs.
Check the boxes so it looks like this:
XXX
XXX
XXO
Click on OK, then OK again, you should be back to the main ES window. Go ahead and hit home, or hit back over and over to exit.
Stock or Modified stock ONLY
Reboot the device by whatever method you prefer.
Once it finishes booting, wait a minute, then check your Settings>storage and your external SD card should show as internal. You only need to do this 1 time, it will continue to do this after.
AOSP/CM9/AOKP ONLY
Go to the Play store and download Script Manager(smanager).
After it installs, open the app then select Browse as root, Allow when SU asks, then click OK.
It will likely be listing /mnt/sdcard as your default directory, press the folder with .. to go back up until it says /
Click on system, then etc
It should now show /system/etc
Find your install-recovery.sh file, and it will open a new window.
Pay close attention here!
Right under the buttons that say Run Exit Edit Save are some icons,
Fav Su Boot Net Wick Ntfy
Press on Su and Boot, then click on Save.
Now exit smanager and reboot.
Wait a minute, then check settings>storage and your external SD should show up as Internal.
Don't disable smanager from running at boot! If you disable it, your script won't run. smanager must remain installed, or the script won't run.
Thanks to:
ZeroNull: For being one of the pioneers for getting our devices cracked open for our amusement!
ptesmoke: Also for being a pioneer in getting custom recoveries on our devices!
vache: For releasing the ICS leaks way ahead of schedule and hosting them for us to use and abuse!
civato: For releasing his Flex Reaper ROMs on our devices, his modified stock ROMs are still (IMO) the slickest available!
da-pharoah: For helping me understand how recoveries work a little better, allowing me to create Blackhole Wipe/Nullifier, and general encouragement for creating things for this device! (G2x and KF forums)
ezterry: For creating an OC/UV kernel that so far is the best EVER for any ROM on our device!
Theonew: reading ALL of that, and providing some nice info I missed and left out, and catching typos (Almost made it...)
crossix: that mount swap mod is just awesome, I never run a ROM without it!
NoSudo: creating a method to easily modify the system to watch HULU and other sites that normally won't allow it!
There's more I'm forgetting, I'll be adding more as I remember, I promise.
Even though I knew everything you posted, it was very interesting and I recommend everyone (even if you don't need it or already know) to read this guide. Its a marvellous read with some humor to keep you going. One thing though:
- You stated that its only safe to wipe "cache, dalvik cache, data, and system". Technically, this is not true. Flexrom and boot partitions are also safe to wipe (and for some roms for certain devices, the boot partition must be wiped for stable kernel performance, etc.). It's also a good idea to wipe sd-ext if you have it set up (in most cases). Once again, excellent guide (you even did a part of my job ).
Theonew said:
Even though I knew everything you posted, this is a brilliant guide and I recommend everyone (even if you don't need it or already know) to read this guide. Its a marvellous read with some humor to keep you going. One thing though:
- You stated that its only safe to wipe "cache, dalvik cache, data, and system". Technically, this is not true. Flexrom and boot partitions are also safe to wipe (and for some roms for certain devices, the boot partition must be wiped for stable kernel performance, etc.). It's also a good idea to wipe sd-ext if you have it set up (in most cases). Once again, excellent guide (you even did a part of my job ).
Click to expand...
Click to collapse
While sd-ext is safe to wipe, using factory reset wipes that for you, and I think, could be wrong, but cwm does it on data wipes. Part of why I missed it was I confused it with my phone, where wiping sd-ext bricks the phone, and also people mix it up with external SD. I'll add it in as its a very valid point, and I shouldn't let personal things interfere with the guide.
As for boot, our devices don't need that wiped and honestly asks for problems if someone doesn't restore or install a rom to cover it. I've never wiped it on any device, however I will also add that in as it is good info. I left it out of "safe" to prevent possible issues from wiping it.
I forgot about flex and I honestly don't know what it is for lol. Again thanks for reminding me and I'll add it in.
Of course I'm open to posts like these please give some input on what I missed or need to correct, I want this to be the go to guide for the a100 for anything needed!
Tapatalked from my Galaxy S II.
pio_masaki said:
I forgot about flex and I honestly don't know what it is for lol....Of course I'm open to posts like these please give some input on what I missed or need to correct, I want this to be the go to guide for the a100 for anything needed!
Click to expand...
Click to collapse
In your 4th to last sentence of the "Advanced Restore" section, you have a typo . Anyways, according to here: forum.tegraowners.com/viewtopic.php?f=10&t=149, Flexrom is "a partition on the nand that acer made to hold some proprietary apks and build information".
Oh damn almost made it without a typo...not bad for just running through all of that without really checking on it..other then it was english.
Corrections and additions added to the posts, thanks!
pio_masaki said:
Oh damn almost made it without a typo...not bad for just running through all of that without really checking on it..other then it was english.
Corrections and additions added to the posts, thanks!
Click to expand...
Click to collapse
One more thing - This occurred for one of my other devices, but the problem may still exist here. I haven't tried it with TWRP, but renaming CWM backups can cause a md5 mismatch error to occur. If this happens, simply rename it back to a date (in the default format).
I've never ran into that issue on any of my devices in CWM or TWRP, however I have heard of it occuring, definatly something I should add in there. Full of good catches tonight aren't you?
Awesome write up, thanks you guys!!
What about Zeronull's .014 v1.2 rom? http://forum.xda-developers.com/showthread.php?t=1574897
I'm still digging through all the threads for the ROMs, however I included the currently developed or recently released ROMs first, ZN has since released Green ICS, which is included already. I do plan to list every ROM, but it'll take some time to finish this guide up with as much info as possible, then go back and add things in.
pio_masaki said:
I've never ran into that issue on any of my devices in CWM or TWRP, however I have heard of it occuring, definatly something I should add in there. Full of good catches tonight aren't you?
Click to expand...
Click to collapse
I tested it to see if it occurs, and it turns out that it does. I made a backup with CWM, renamed it then tried to restore, and it immediately gave me the "md5 mismatch" error.
Theonew said:
I tested it to see if it occurs, and it turns out that it does. I made a backup with CWM, renamed it then tried to restore, and it immediately gave me the "md5 mismatch" error.
Click to expand...
Click to collapse
That is so weird I never have that issue cwm or twrp. I use es file manager..maybe why?
Tapatalked from my Galaxy S II.
pio_masaki said:
That is so weird I never have that issue cwm or twrp. I use es file manager..maybe why?
Tapatalked from my Galaxy S II.
Click to expand...
Click to collapse
I renamed it using Root Explorer. Have you tried renaming them to something including spaces?
Theonew said:
I renamed it using Root Explorer. Have you tried renaming them to something including spaces?
Click to expand...
Click to collapse
No, as its a Linux based environment I use dashes and underscores never spaces in directory names. That shouldn't cause md5 fails because the md5 is based per zip not the folder name. If you could try an experiment and rename with es I'd appreciate it, and maybe with and without spaces. I'll try root explorer when I get home and see if it causes issues.
Tapatalked from my Galaxy S II.
pio_masaki said:
No, as its a Linux based environment I use dashes and underscores never spaces in directory names. That shouldn't cause md5 fails because the md5 is based per zip not the folder name. If you could try an experiment and rename with es I'd appreciate it, and maybe with and without spaces. I'll try root explorer when I get home and see if it causes issues.
Tapatalked from my Galaxy S II.
Click to expand...
Click to collapse
Done. The error seems to only occur when spaces are used in the name.
Theonew said:
Done. The error seems to only occur when spaces are used in the name.
Click to expand...
Click to collapse
Thanks for taking the time to figure that one out, I've been testing a new rom on my phone plus a new test T20 kernel for ezterry and getting cm9 build 5 up, just kinda managed to forget that experiment lol
I'll have some time...maybe...to append that new bit into that section tonight. The "free" time has been spent trying to get aokp for the a100 but my lack of experience, random problems with the repos and devs ignoring my PMs its been going slow. And by slow I mean nowhere.
Tapatalked from my Galaxy S II.
Great read. Sorta like flashing for dummies. Thaanks for your work.
Sent from my HTC Glacier using Tapatalk
It's great to have all this information compiled in one location. Looking forward to your next installment. THX
This is an all new way to root and install bootmenu (2nd init) with only one click!
Just running runme.bat you will have a Bravo ready to use new roms in less than a minute.
Instructions:
1. Download: http://www.mediafire.com/?yfgvds9a1w8sbds
2. Extract files whenever you want.
3. Enable USB debugging (menu > Settings > Applications > Development) and connect your phone to the PC.
4. Run runme.bat, in folder Root+Boot-AIO.
5. Press Enter when script ask you to do it and READY!
Note: remenber to install motorola drivers first.
Reserved for instructions in spanish and other language!
Thanks. Finally find another one click option.
Sent from my HTC Sensation using Tapatalk 2
Tested, worked like a charm!
Thank you! :good:
Wow
Just one word, wow, works like a charm. Now we can install a custom rom with like 4 steps now. Your 1 click would be step one for sure!
Good job and lots of props man!
Junkyardjames87 said:
Just one word, wow, works like a charm. Now we can install a custom rom with like 4 steps now. Your 1 click would be step one for sure!
Good job and lots of props man!
Click to expand...
Click to collapse
I've looked into it. While there are a few options to install roms from the pc, some of the commands are known to hang on completion, which means you can't really script them safely (you could add in some kill and restart commands, but you'd have to put like 2-5 min buffers on them to make sure it was done).
I've found that the quickest way to install roms is to use TWRP in the Defy Forums. It allows you to select multiple zips at a time to flash at once. I haven't used clockwork touch recovery yet.
I'll look into it a little more, cause typing something like "./rom_install.sh /path/to/rom.zip -gbgapps" to install a rom and gb gapps would be easy. If I can find a way to execute edify scripts (the ones used to install roms) from adb then this can be done. I can only make and test linux scripts since I no longer have windows, but Josuearisty can port it to windows shell script. I formatted my old windows drive to use my android compile drive .
skeevy420 said:
I've looked into it. While there are a few options to install roms from the pc, some of the commands are known to hang on completion, which means you can't really script them safely (you could add in some kill and restart commands, but you'd have to put like 2-5 min buffers on them to make sure it was done).
I've found that the quickest way to install roms is to use TWRP in the Defy Forums. It allows you to select multiple zips at a time to flash at once. I haven't used clockwork touch recovery yet.
I'll look into it a little more, cause typing something like "./rom_install.sh /path/to/rom.zip -gbgapps" to install a rom and gb gapps would be easy. If I can find a way to execute edify scripts (the ones used to install roms) from adb then this can be done. I can only make and test linux scripts since I no longer have windows, but Josuearisty can port it to windows shell script. I formatted my old windows drive to use my android compile drive .
Click to expand...
Click to collapse
Im not using TWRP either Touch Clockworkmod, both of them are not working as they should sometimes.
I supose that a fully working Touch Clockworkmod would restore an old backup made with our actual Clockworkmod recovery, but does not.
In the case of TWRP, works fine for some time but later it seems to get tired and when you make a backup, it says its complete inmediatly but it is still creating backup files.
It would be great to install roms with just hitting Enter coming from froyo. Do you think that just making some changes to the script, is it possible to install a rom the pc?
josuearisty said:
It would be great to install roms with just hitting Enter coming from froyo. Do you think that just making some changes to the script, is it possible to install a rom the pc?
Click to expand...
Click to collapse
I'm sure its possible somehow, I've just never looked too deep into doing it. What ways I have found either used commands that would hang and require you to quit after 2 mins of activity and start the 2nd command which hangs the same thing -- not safe enough to script. The other ways were for broke\no sdcard and involved copying the rom to /data and then installing as normal.
What I think needs to be done is set up a script that copies the rom & gapps to the sdcard and executes their edify scripts. We need to figure out what command recovery uses to execute the script\install roms then incorporate it into an install script. You'd still have to reboot to bootmenu and enable adb, but that's all (unless we find a way to reboot and have adb already enabled (not good for all the time use, security concerns - it'd be possible to get around the bootmenu pin if adb was enabled on power up).
skeevy420 said:
I'm sure its possible somehow, I've just never looked too deep into doing it. What ways I have found either used commands that would hang and require you to quit after 2 mins of activity and start the 2nd command which hangs the same thing -- not safe enough to script. The other ways were for broke\no sdcard and involved copying the rom to /data and then installing as normal.
What I think needs to be done is set up a script that copies the rom & gapps to the sdcard and executes their edify scripts. We need to figure out what command recovery uses to execute the script\install roms then incorporate it into an install script. You'd still have to reboot to bootmenu and enable adb, but that's all (unless we find a way to reboot and have adb already enabled (not good for all the time use, security concerns - it'd be possible to get around the bootmenu pin if adb was enabled on power up).
Click to expand...
Click to collapse
Well, look at the rom manager, watch how it does it. I think that looking into adb commands we can make a script works like rom manager.
When you select the rom, rom manager lets you wipe data & cache and also install gapps. The rom manager goes to recovery and inmediatly do all steps it self, you can also backup your actual rom.
Try it, download it from market and try it, I see your roms there too.
Some windows commands are:
Adb reboot recovery = reboot into recovery mode
Adb push FILE = copy files to whatever place into out phones. Example to copy a rom.zip to sdcard
Adb push rom.zip /sdcard/rom.zip
Those are windows commands, dont know if they could work on linux. If my pc wasnt broke I would be making some tests!
Does this install a custom recovery? And if not how do I install one? Will a goo manager from the play store install one?
Sent from my Nexus 4
obsanity said:
Does this install a custom recovery? And if not how do I install one? Will a goo manager from the play store install one?
Sent from my Nexus 4
Click to expand...
Click to collapse
This will root and install a custom recovery.
Excellent tool, recommended! :good:
josuearisty said:
This will root and install a custom recovery.
Excellent tool, recommended! :good:
Click to expand...
Click to collapse
Great. Thank you. I'm rooting a friend's phone. He just wants something more reliable than stock. Would you say the CM7 is stable and reliable or should I put CM10 on it?
obsanity said:
Does this install a custom recovery? And if not how do I install one? Will a goo manager from the play store install one?
Sent from my Nexus 4
Click to expand...
Click to collapse
CM7 is more stable now, I have installed an official cm7 and then a patch for it.
Give me some minutes to upload it!
josuearisty said:
CM7 is more stable now, I have installed an official cm7 and then a patch for it.
Give me some minutes to upload it!
Click to expand...
Click to collapse
Which one should I use? Also, what is the SBF for Motorola Bravo? Sorry about the questions in this thread, I'm not familiar with this phone.
obsanity said:
Which one should I use? Also, what is the SBF for Motorola Bravo? Sorry about the questions in this thread, I'm not familiar with this phone.
Click to expand...
Click to collapse
Use cm7. Very fast and stable with no random hiccups, rare force-closes. The SBF is the Motorola Bravo "factory ROM". To install it, you can use RSDlite or do it in linux, both of those tuts are found in the bravo general section. You probably won't have to use the SBF unless you brick your phone, which is a possibility, but flashing the sbf will unbrick it 99% of the time.
Current ROM: CM7.2 Euroskank Cherry Picks | Bravo port
I think I have a problem. The sim I put in to this phone is asking to log in with moto blur and nothing I try is working. So I can't switch the debug mode on. I even tried the bypass suggested by someone but fastboot is not preinstalled on this phone. All I get is the bootloader or stock recovery.
I also tied resetting the password but after I go thru it it just says there is no phone on this moto blur account.
Any help would be appreciated.
Edit:
I got it. I factory reset the phone and then was able to use the bypass motoblur ****.
Sent from my Nexus 4
Ruined my device,now it won't even boot.
How do I fix it? factory reset doesn't help
shvelo said:
Ruined my device,now it won't even boot.
How do I fix it? factory reset doesn't help
Click to expand...
Click to collapse
Post a little more info.
What did you do?
Can you access custom, stock, or bootloader recovery?
Does it still charge?
And did you factory reset from Custom recovery or Stock recovery? Custom only wipes all data where Stock actually formats the partitions.
The easy way and a common issue we're having now.
Unless this is one of those CM10 ext4 issues, just flash the sbf and you should be good to go.
If you downgraded from CM10 and you were using ext4 /data and /cache, reinstall CM10, format back to ext3, then flash whatever you want.
skeevy420 said:
Post a little more info.
What did you do?
Can you access custom, stock, or bootloader recovery?
Does it still charge?
And did you factory reset from Custom recovery or Stock recovery? Custom only wipes all data where Stock actually formats the partitions.
The easy way and a common issue we're having now.
Unless this is one of those CM10 ext4 issues, just flash the sbf and you should be good to go.
If you downgraded from CM10 and you were using ext4 /data and /cache, reinstall CM10, format back to ext3, then flash whatever you want.
Click to expand...
Click to collapse
What is that issue with cm10 ext4? Is that very dangerous for us?
I have been sometime out of the forum and I have lost some things!
josuearisty said:
What is that issue with cm10 ext4? Is that very dangerous for us?
I have been sometime out of the forum and I have lost some things!
Click to expand...
Click to collapse
The CM10 ext4 issue is when you flash a CM10 custom kernel rom and select format /data & /cache to ext4 in the bootmenu. Only custom kernels can use the ext4 file system, so what happens is you format them as ext4, install CM9, and it doesn't load because it can't mount /data and /cache to write them because they're on an unsupported file system. The only things you can do are reinstalling CM10 and formatting back to ext4 of flash the sbf in extreme cases. Its not dangerous at all, just very annoying if you forget to format back to ext3 .