Related
major update here, the dualizer has become a feature rich toolkit for dualbooting. this includes a modified version of amon ra's recovery image. you need it to use the dualizer toolkit, it is included and can be flashed with one command.
it is a beta version for now. i have tested each option, but i cannot foresee all conditions you might have on your phone... have a backup at all time! and don't forget to backup the stuff from your sdcard before installing dualboot, during the creation of this toolkit i accidently deleted everything on mine...
there is no logging at the moment, if you get any error messages please paste them here in full.
i haven't tried a nandroid backup at all yet, and wouldn't advice you to do it either. please use apps like titanium backup to backup your stuff. i will be looking into getting some kind of nandroid capability, but that is not a trivial topic. i can however imagine to have full pc-based backup capabilites, sometime in the future...
before you use any of the romX options make sure you have installed the dualboot environment, i have no idea what happens otherwise...
i have tried to include a full description, please let me know if something is unclear (i hope it is obvious that romX needs to be replaced with either rom1 or rom2):
Code:
kendon's dualboot toolkit for the HTC Hero
usage: ./dualizer <option>
place the two roms you want to use for dualbooting in the
rom1 and rom2 subdirectories. make sure directories do
contain other files. you can use the temp/ subdir of the
two rom folders to store your roms while you want to flash
another update.zip
you need a modified version of Amon_Ra's custom recovery image.
it can be installed with this tool, see the options.
options are:
help show this information
vmsetup prepare ubuntu vm for usage
check-dev check if your device is properly attached and connected via adb
boot-rec reboot hero to currently flashed recovery
check-rec check if RA-hero-v1.6.2-DBmod is currently flashed
boot-dbmod put hero in fastboot mode (back+power) first!
fastboot hero with RA-hero-v1.6.2-DBmod
no permanent changes are done, works with unlocked spl only
NOTE: the trackball doesn't select, use green key instead
unlocked-spl copies update.zip for unlocked spl to sdcard, so you can flash it.
if this goes wrong it can brick your phone, make sure you do it right!
flash-dbmod flash RA-hero-v1.6.2-DBmod to recovery partition (permanently)
NOTE: the trackball doesn't select, use green key instead
install-db ALL your data will be lost, so you better have a backup!
install dualboot environment on htc hero
this includes partitioning of the sdcard
place roms in folders rom1 and rom2 first!
romX wipedata wipe data/factory reset romX
romX wipedalvik wipe dalvik-cache for romX
for the following options place update.zip file in folder romX first!
romX flash flashes update.zip from folder romX
romX makeboot create boot.img-update.zip files for romX
romX makeboot push create boot.img-update.zip files for romX and push it to /sdcard
i don't see any potential to brick your phone, even if it fails, as the critical parts (spl, radio) are not touched at all. worst that could happen is that you have to do a full wipe and flash a rom... be careful while flashing recovery and/or bootloader though!
as always: use at own risk!
note: first (and maybe second) boot maybe painfully slow. after that it gets better, see for yourself if it is too slow for you. i have been using villainrom and slidevillain in a dualboot for a few days now, i haven't noticed too much slowdown. then again i don't care too much about this.
credits: huge thx to the ppl in this thread: http://forum.xda-developers.com/showthread.php?t=594077 the information in there helped a lot.
changelog:
v0.2: major update, toolkit for flashing, wiping etc.
v0.1: initial release
installation & usage instructions
please read the first post before you install dualboot!
instructions for windows:
instructions for windows said:
the dualboot install can now set up all necessary stuff in a fresh installed ubuntu virtual machine in virtualbox. you must have adb access to your hero from the windows command line, if you need help check theunlockr.com for their awesome video tutorials.
here is a great howto install virtual box in windows: http://www.psychocats.net/ubuntu/virtualbox
and this is the second part, howto install ubuntu in a virtual machine: http://www.psychocats.net/ubuntu/installing
once you are done installing ubuntu download the archive from the first post and follow these steps (the default download directory is "Downloads", so i'm gonna use that in this example):
- go to "Downloads", you find it in "Places" in the upper menu bar
- rightclick the zipfile you just downloaded and select "Extract Here"
- open a terminal window: goto Applications, Accessoires, Terminal
- execute these commands:
Code:
cd ~/Downloads/dualizer/
chmod +x dualizer
./dualizer setup
it will ask for your password once, then do some stuff and finally reboot the virtual machine.
once rebooted, connect your hero to your pc, rightclick on the usb sign in the lower right corner of the virtual machine window and select the "HTC Android Phone". some hardware installations from windows might pop up (happened to me), just click on next and let them do their stuff. if it doesn't work at first shut down ubuntu, then restart your pc and continue. "reboot tut gut", as the german likes to say
back to ubuntu, with your hero connected to pc and virtualbox, open a terminal and check if your hero is detected by adb with the following commands:
Code:
cd ~/Downloads/dualizer/
./dualizer check-dev
this will tell you if your device is properly connected. you can now continue with the options you can get from
Code:
./dualizer help
Click to expand...
Click to collapse
instructions for linux:
instructions for linux said:
you need java, perl and zip setup, make sure that these are available. then follow these steps:
- extract the attached zipfile from the first post on your pc (for this example i'll assume you extracted it on your desktop).
- get the two roms you want to dualboot, do not extract them.
- put one rom in the rom1 folder, the other rom in the rom2 folder inside the dualizer folder on your desktop.
- open a terminal, cd to the folder and make the main file executable by typing:
Code:
cd ~/Desktop/dualizer
chmod +x dualizer
- turn on your hero (recovery or normal, doesn't matter)
- connect your hero to your pc and check if your hero is detected by adb with the following commands:
Code:
./dualizer check-dev
this will tell you if your device is properly connected. you can now continue with the options you can get from
Code:
./dualizer help
Click to expand...
Click to collapse
reserved...
Holy... this is incredible. Great job on getting this out.
I use a virtual box and ubuntu 10.04 lts.The method seems to work but in step 3 on partition card my hero restarts and boots in recovery and i don't have time to mount the usb/htc device into virtual box so i get in step 5 an no device found error.The time is very short.I have to press USB-MS toggle on my hero and after that i have to mount it in virtual box.I've tried it over 20 times but i don't have time and in terminal get me the error.Is there a way to pause the process or a solution to my problem?
Sorry for my bad english
EDIT:SOLVED.Set the sleep from dualizer in step3 from 15 to 30.Wainting for setup to finish.Cross my fingers
EDIT2: Ok now this is getting awkward.Waiting on step 4 (push to sd) for 25 minutes now.I have checked the log.Last line says mounting /dev/block/mmcblk0p1 on /sdcard failed: No such file or directory.Should I wait for it any longer?Or what should I do now?
As I have said on the VillainROM forum; this is really outstanding work.
Well done, Kendon.
Zero00SM said:
EDIT2: Ok now this is getting awkward.Waiting on step 4 (push to sd) for 25 minutes now.I have checked the log.Last line says mounting /dev/block/mmcblk0p1 on /sdcard failed: No such file or directory.Should I wait for it any longer?Or what should I do now?
Click to expand...
Click to collapse
that shouldn't happen, and the pushing shouldn't take longer than a few minutes. you should cancel it by pressing ctrl-c, if you fancy debugging then check why it wouldn't mount. otherwise you can partition your sdcard, do a full wipe and should be able to flash a regular rom.
i guess i underestimated the complexity of the virtual machine solution, gotta look deeper into this... *sigh*
Hi, regarding the Apps2SD issue... Would it ever be possible for the two ROMs that are dual booting to have the same apps sourced from one place... if that makes any sense...
Like in windows... you can "install for all users" so if you log off and someone else logs in with there account the very same apps are there...
Ok bad analogy since we are talking about dual booting different versions like (Vista & Windows 7) ... but the same data on hdd is accessible...
is this possible with the dual booting scenario?
If I had Slide Villain and Villain 5.5 .. both being 2.1 ROMs which would make app compatibility a non-issue...
If I booted up Villain 5.5 and made changes to an app / save data .. could this not be accessible with the slide rom.. I would hate having to install the very same apps on another partition..worst of all if you have save data (such as a game) and wanted to play it on one of the ROMs your game progress would be different?
you could just use Titanium to transfer over the data but agaqin it is a long procedure.
It would be fantastic if we could mirror image exactly what we have on our main Roms to our "secondary roms" ...
Amazing !
Ciao
Fred
Yeah this is really amazing. I have read this on villainRom forum, and i was stupified .
But, if i want to flash another Rom as primary and need to wipe cache, i need to do this process again! Am i right?
for the shared apps:
a shared apps2sd directoy/partition is possible, although you'd have the problem that apps are installed to one market only, and idk what would happen when you update an app in one rom, would the update get market-linked in the other? you can solve this with titanium backup, but it isn't really comfortable at all. i'll think about this.
for shared data: in theory possible as well, but i don't think it would work out well. you cannot distinguish between system data and apps data that easily, and i don't think it would work to share system data (sense settings etc) between two different roms...
@masterxiter: easiest way to do this is to use the installer script again. you can wipe the cache manually, installing another rom would be really complicated (about as complicated as the installer script )...
Sweet. But is there any way i can run this in cygwin? every version of linux ive tried so far doesnt support my crap compaq wifi card or most things, or even wired for that matter, and running ubuntu in a virtual machine gives a reboot every time after step 1 (maybe cos i suck at terminal)
i'll try some time, but i have never used cygwin... so don't expect anything too soon.
joshman99 said:
Sweet. But is there any way i can run this in cygwin? every version of linux ive tried so far doesnt support my crap compaq wifi card or most things, or even wired for that matter, and running ubuntu in a virtual machine gives a reboot every time after step 1 (maybe cos i suck at terminal)
Click to expand...
Click to collapse
if you install ubuntu in an virtual machine like VMware(paid) or virtualbox(free) you can just use linux, it will automatically grab all your internet settings and stuff from the windows installation(main computer) so your windows will be like some kind of router for your virtual machine with everyhing working.
Very nice tutorial, i'm not going to try it.. because my phone has to be resend to HTC for fixing some dead pixels, there just messers with screens
BTW. you can also try another linux version sounds crazy, maybe try backtrack?? the only thing you need is linux, backtrack is..
I have backtrack 4 (I could never get wifi on that either, but tbh i couldnt work out how to try (that distro is soo confusing imo). I got backtrack 3 to work a while back, so if i can find the disk im gnna try that.
Also virtualbox didnt put my internet settings at all (maybe co im on win7 ultimate?)
Thanks for the suggestions, cos i know cygwin aint the most elegant solution
changing rom 1 and rom 2
i test lotz of roms.... everyday they are being updated...
say if i dualize with ahero0.8 and Kimera 1.7....
wud i be able to update aHero to 0.9 and leave kimera as it is???
simply can i update JUST ONE rom???
manual setup??
i tried it got error in step 3 and then 'Device not found errors...'
can u make a tutorial for doing it manually.....
kendong2 said:
please read the first post before you install dualboot!
instructions for linux:
you need java, perl and zip setup, make sure that these are available. then
Click to expand...
Click to collapse
hihi.. i am trying to do a dual boot, so im wondering what u mean by.. need java , perl and zip setup... can advice me?
He means that you need to have Java, perl and zip installed and configured on your Linux system. If you dont have that installed and configured correctly than the install script wont be able to run.
lolnl said:
He means that you need to have Java, perl and zip installed and configured on your Linux system. If you dont have that installed and configured correctly than the install script wont be able to run.
Click to expand...
Click to collapse
oh noes.. .i do not have those in my ubuntu, does that mean i cant do a dual boot? btw, i saw post 2 and post 3 ... are they the same instruction ? or different? (one for windows user and one for linux?)
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.
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. It has several modes; If you like to do everything yourself, then Ok, you can. If however you want Windows to do everything, it will.
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
Complete make over, now using a GUI!
Very explicit detailing of what the program is currently doing!
Install drivers - (USB + ADB/fastboot drivers)
List of ROMs/kernels
Help menus
What's to expect:In-program E-Mail subscription, to get notified about updates.
Better IE Engine for XDA Link.
Context menus, for faster checking of radiobuttons.
Maybe adding an advert or two. Because I am now slowly but surely needing more money, for phones, so that I can program programs like this, for them.
Maybe re-add the main menu music. But, with music, that is a bit more calming... And not House ^^
A fully functional fastboot menu.
A user experience program, so I can collect feedback!!
Working progressbars.... (-.-")
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...
Ok, we've done it!! (I've done it...) We've gone out of Alpha.
We beat the beta!
Now, I'm proud to present; Beatsleigher's Root Helper... VERSION 3.0.0.8!!!!!!!!!!!!!!!!!!
Each and every script, has been either re-written, or has just gotten a makeover!!
Everything unneeded, has been removed, It's more compatible, with Windows XP, loading time has gone down!!
I've added a few options, but not that many, to make a big changelog...
To upgrade/update, please, copy ALL the files, you created/copied/moved there, to a safe place, on your hard drive. Then, delete "C:\Beatsleigher_root_helper"
Run the installer (It's contained in an ISO image, so, download PowerISO, should you not ahave an image mounting system...) and done!!
Download here
Screenshots:View attachment 967846 View attachment 967847
View attachment 967848 View attachment 967849
View attachment 967850 View attachment 967851
View attachment 967852 View attachment 967853
View attachment 967854 View attachment 967855
View attachment 967856 View attachment 967857
View attachment 967859 View attachment 967860
View attachment 967861 View attachment 967862
View attachment 967863 View attachment 967864
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.
EDIT: The installer has been split in two!! They are both in an ISO image... Once mounted, the secondary installer will run (setup.exe). Just open the virtuall CD-ROM, and run "Install.exe"
Requests:If you have any requestes (features, etc.), please PM me, or send me an E-Mail!!
Or, visit: This page
Please read!!:Sorry for not updating this thread, as much, as the GSM thread. If you want to stay up-to-date, then click here every now and then
Changelog:
Version 3.0.0.8:
Full release, no BETA, anymore...
Two installers, instead of one...
All scripts have been re-written or have had a makeover...
Version 2.6.5.7 [Minor 3]:
Some tweaks and additions... Mostly hidden...
Some preparations, for full release.
Next version will be 2.7
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 (!!!)
ADB menu got a makeover.
Added CPU/RAM usage detection
Added option to enable/disable CPU/RAM usage detection in fastboot menu.
Fixed bug in ADB help menu.
Added options to the m,ain menu...
The rest has been forgotten, or you're ment to download the program, and check for yourself...
NOTE:
If you are interested in downloading this product, please download version 2.6.5.3, install and then download/install 2.6.5.4.
Then you can be rest assured, that everything is working as good, as it should in the BETAphase, of a program
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!
This post will be used for announcing updates and changelogs!
The first update, to be announced here, will contain some CDMA kernels and ROMs... They will all get QR-Codes, so you can download them directly on to your Android, if neccesary!
Only use this package to root your phone and flash recovery!!
The other images/ZIPs are on their way!! Before I get told off, for not telling you this.... I am making a package, that will delete all GSM files!
This reduces size, and no one gets confused!!
Cool. 400mb is the reason I wouldn't download it. Opinions:
Remove the extra crap. Include just your code.
Create a folder /flash and instruct people to just throw stuff in there. Then code your app to read and list the contents of that folder (If that's even possible).
Your program can't be more then a meg or two itself. This way people can just download your tool and flash whatever. It then won't ever be "outdated" with old files. Streamline it and it'll catch on.
EXT LTE Galaxy Nexus 4.0.3
Transformer TF101 ICS
player911 said:
Cool. 400mb is the reason I wouldn't download it. Opinions:
Remove the extra crap. Include just your code.
Create a folder /flash and instruct people to just throw stuff in there. Then code your app to read and list the contents of that folder (If that's even possible).
Your program can't be more then a meg or two itself. This way people can just download your tool and flash whatever. It then won't ever be "outdated" with old files. Streamline it and it'll catch on.
EXT LTE Galaxy Nexus 4.0.3
Transformer TF101 ICS
Click to expand...
Click to collapse
That's a good idea
I'll try and do something like that
player911 said:
Cool. 400mb is the reason I wouldn't download it. Opinions:
Remove the extra crap. Include just your code.
Create a folder /flash and instruct people to just throw stuff in there. Then code your app to read and list the contents of that folder (If that's even possible).
Your program can't be more then a meg or two itself. This way people can just download your tool and flash whatever. It then won't ever be "outdated" with old files. Streamline it and it'll catch on.
EXT LTE Galaxy Nexus 4.0.3
Transformer TF101 ICS
Click to expand...
Click to collapse
Have done Even though it took a bit longer, to get here... Sorry, about that...
I just kept on forgetting, to update this thread. But it will be different, from now on
Prerequisites:
- the phone should be connected to the computer via the USB cable provided in the commercial package;
- the Settings / Applications / Development / USB Debugging option should be enabled;
- the USB drivers for the S5690 phone should already be installed on the host computer.
Instructions:
0. download the S5690_unlock.zip file attached to this post;
1. unzip the S5690_unlock.zip archive in any place on your local hard drive;
2a. if you wish to UNLOCK the phone, execute the s5690_unlock.bat script as Administrator (right-click on the script file and select Run as Administrator);
2b. if you wish to RELOCK your phone, execute the s5690_relock.bat script as Administrator (right-click on the script file and select Run as Administrator);
3. follow the on-screen instructions and NEVER restart the phone by yourself.
WARNINGS:
- at the beginning the script waits for the sdcard to be mounted in your phone. If you have no sdcard at all, the script will wait forever! In this case you should disconnect the usb cable, turn off the phone, insert an already formatted microsd card, turn on the phone and finally reconnect the usb cable. The script will resume by itself when the card is detected;
- do not reboot the phone by yourself at any step! (neither in Recovery nor in standby); the script will do that automatically everytime it needs it;
- the ROOT.zip and UNROOT.zip files which are attached to the S5690_unlock.zip archive can be used ONLY on S5690/S5690L/S5690M phones. They won't work on other phone models;
- do not try to Relock a neverlocked phone, simply because the effects could be unpredictable (since there is no PLMN ID stored in the /dev/bml25 memory that would normally tell the phone on what network is it locked to);
- the scripts should also work on the S5690L and S5690M phone models. Please post some feedback here if you unlock/relock one of these models.
After the complete execution of the unlock/relock script, the tmp subdirectory will contain two files:
- bml25_before.bin -> backup of the original /dev/bml25 dump;
- bml25_unlocked.bin OR bml25_locked.bin -> dump of /dev/bml25 block device AFTER the unlock/relock operation.
What the script does:
1. installs root on the phone;
2. dumps the /dev/bml25 block device to a binary file;
3. changes the first two bytes of that file from 01 to 00 (for unlock) or viceversa (for relock);
4. writes back the binary file to the /dev/bml25 block device;
5. removes the root from the phone;
6. removes ROOT.zip and UNROOT.zip files from your sdcard.
If your phone is already rooted then skip the ROOT.zip installation step (from the Recovery menu) and just press any key in the script window to go to the next step.
After the execution of the script, the phone will be UNROOTED! If you want to keep the root, then you should either break the script (CTRL+C) when it reaches the INSTRUCTIONS FOR ROOT REMOVAL step or you should press any key in the script window without actually installing the UNROOT.zip from the Recovery menu.
There is no problem if you run the unlock script on an already unlocked phone or if you run the relock script on an already locked phone. In either of those cases, the phone will have the same status in the end as before running the script (either unlocked or locked). If you compare the bml25_before.bin and bml25_[un]locked.bin files you should have no differences.
I've already tested both unlock and relock scripts on several S5690 Xcovers and everything works OK.
UPDATES:
20130208 -> added support for the S5690R variant (Rogers Canada) - thanks to theshowman
Thanks a lot for the scripts! Excellent job. One question though: if my phone is already rooted (with your update.zip ) what should I (if possible) remove from the unlock script in order to perform strictly the steps for unlocking? Thank you in advance.
You don't have to remove anything. When the script displays the instructions for Root, just press any key in the script window (without actually following the instructions, i.e. without installing the ROOT.zip archive in the recovery menu) so the script goes directly to the next step (the unlocking step).
Also if you want to keep the Root in the end, do exactly the same at the Unrooting step.
The script does not verify if you really root / unroot the phone when it asks you to do so.
Regards
Thanks for your work.
Respect!
I tried the script but unfortunatelly it didn't work on my phone. In attach there is one print screen of the operation. My Xcover is locked on Orange RO. What could be the problem?
Copy the text from the cmd.exe screen and post it here or upload a full size print screen. The image resolution is too small and I can't understand what's the problem.
It seems that the "su -c" commands are executed directly under the cmd.exe and NOT within the adb shell prompt as they should be.
Post the WHOLE output of the script (from the beginning to the end). Do more consecutive print screens if necessary.
I tried again and you are absolutely right. The script is executed in cmd.exe, not in adb as it should. I didn't pay attention earlier. What can I do to force it to start in adb? The screenshot has been taken and saved at 1280x800 but it has been resized automatically at upload.
Upload the image(s) on imageshack and post only the links here. I need the whole output of the script.
http://imageshack.us/photo/my-images/846/unlocking.png/
First link. If neccessary, I will make/upload the missing screens from cmd.exe (the missing parts are the root and unroot ones, that I skiped by pressing a key without following instructions as my phone is rooted).
never mind
@PaulTT: I think I've found the problem. The double quotes were not interpreted correctly (probably due to different regional settings).
Please download again the zip archive from the first post (I've replaced it with a newer version) and try again.
Regards
Now it worked flawlessly! I have the 2 .bin files in temp file and the phone is working with any non Orange SIM. Thanks a lot for your help!
It is working, but i had to write every command in cmd, after i got su acces, thank you tlc76
Thanks !
it worked flawless ! many thanks
Worked like a charm. Thanx!.
Offtopic: no CFW so far for this phone? I'd like to try an 4.0.x ROM.
thanks for the post, do you think it will work with any career in american countries?
Problem
Hey tlc76,
first of all, i'd like to say thank you for the script, but unfortunately it doesn't work.
So i did everything in the description. (Turning on USB-Debugging, Inserting SD-Card, Installing the Drivers from Samsung)
But everytime i open the unlock.bat file, the screen turns white and the script doesn't do anything. The PC says, that adb doesn't work sometimes.
With the standard software from samsung or the adb in eclipse it functions quite well.
I would be thankful for some advice.
Thanks,
greendot_189
nice tool! my phone is more happy now
So, i eradicated the problem from yesterday, by running the script with a different version of adb, which was already on my harddisk.
There are good and bad news.
The good ones first:
It doesn't freeze and turn white anymore.
The bad ones:
The script waits endlessly searching for a SdCard. (It is inserted, and the phone works with it)
greez,
greendot
Edit:
It works now. Thank you very much!
Problem:
It didn't find the device. I installed Android SDK (with the USB Drivers) + JDK7 on another computer. Then everything worked fine.
Thanks!
If the script waits endlessly for the SdCard and the dots on the screen ARE NOT expanding, then you can try the following (in this particular order):
- stop the script (CTRL+C and Y) and restart it;
- unplug and replug the USB cable (with the script still running);
- reboot the host computer.
It seems that sometimes the
Code:
adb -d shell "mount"
command freezes and the script cannot advance. Normally every two seconds a new dot should be displayed:
Waiting for the SdCard to be mounted.................
so if you see only 4 dots which are NOT expanding
Waiting for the SdCard to be mounted....
then the script is waiting endlessly for the output of the mount command and is not actually running, so you can do one of the 3 actions described above.
The problem is most probably caused by the adb interface.
So, I decided to write this guide here as I couldn't find a complete one and had to jump from thread to thread (and sometimes even the sub-forum) for finding the answer.
First I wrote it in my blog and I decided to post it here. Maybe some steps are vague in details but I'm planning to detail it even more (remember, I wrote it in my personal blog first). So, here it is:
AIO LG Optimus Me P350 Guide
Some Personal History
My experience with Android. UF! Where to start? So, I got my phone from the United States. You have no idea how wonderful it was to have the phone in my hands. Anxiety and curiosity. For some reason I always read that the first thing anyone does is root the phone and then continue doing everyday activities that do not require root, so I tried to live without rooting the phone, but I couldn’t wait for the week to go by. I had to get the best! Small problems, fixes and updates. And since I have my phone on sale, I publish this step by step guide to modify it and not die trying.
Tech Specs
Let’s start from the beginning, know the phone. Mid/low-range phone created by LG for those in a short budget but want to have a good Android experience. It has a 600 MHz processor, 256 MB RAM and ROM capacity of 512 (140 MB available for applications and data). 2.8 inch capacitive screen, 240 × 320 screen resolution. Wi-Fi b/g wireless connection, Bluetooth 2.1 with EDR, and USB 2.0 up to 480 Mbit/s. 3.1 MP camera (no flash) and FM Radio. Not bad for a basic device. Complete specifications can be found here. Enough for a casual user. But if you’re not a casual user (hence a XDA member), read on.
First of all, everything you do on the phone number is on your own. You yourself are responsible for what you do, not do, stop doing, fail, fail to read and/or shortcut you may have taken. These steps are the ones that worked for me. I am not responsible if the phone dies in the process, the cat bites the cable in the middle process, the heavens begins to fall, the 3rd world war starts or if the neighbor has a heart attack … You’ll be calling 911 afterwards… You’ve been warned!
USB Debugging
The first thing you have to learn is to turn on USB debugging. Here is a guide how to do it (If you wanna see a pictorial guide). But essentially you have to go to Settings > Application > Development and check where it says USB Debugging. Pretty easy. What is this good for? Well, for starters. modify the phone however we see fit. But most important USB Debugging allows the phone to communicate verbosely with PC with the Android SDK installed. More on this later.
KDZ Updater
KDZ Updater is an application used by LG for flashing official operating systems themselves. How did this application saw daylight outside the company, I don’t know very well, but apparently a leak appeared on LG India, but not sure. In any case, this application is our last line of salvation and the main tool for our little friend.
To install official KDZs must follow these steps:
Install the updated drivers by following the steps listed on this page.
Connect the phone with USB Debugging activated
IMPORTANT: Disable the Virtual USB Modem device from Windows Device Manager. Omit this step and the device may brick in the upgrade process.
Run the application in Administrator mode (only required on Windows Vista / 7).
In the Type drop-down list select 3GQCT and in PhoneMode, DIAG. Where it says Version, will appear the version that is installed on the phone.
Select the KDZ file to install by clicking on the button with the folder icon. Preferably save the file KDZ in the root of the hard drive as there will be little chance for error when reading the file.
Press the button “Launch Software Update”. The phone will reboot into Emergency Mode. This is normal.
Pray all you know and go for a cup of tea. The process takes about 8 to 10 minutes.
If all went well, the phone will turn off and the program displays a line that says = FINISHED =.
To start, first go into recovery mode by pressing the following buttons: Vol- & Power. This will make any old or unnecessary information to be removed. The phone will reboot into the system normally.
Original Thread
Root (Gingerbreak and SuperOneClick)
Ok, what we came here for. Rooting the phone. How do I do? It’s scary! Says who?! Lets start with the choices we have. Ok, we have the phone, but we have not updated anything, How do I get root? Gingerbreak comes on the scene. Pretty simple process: download, Enable USB Debugging, run, press Root, wait for the restart, confirm. Simple, right? Also read the instructions and warning on the link above in case something I overlooked, but that basically is the process. By the way, install Busybox, very important for future processes.
Stop, stop, stop … And if I upgraded the phone? Gingerbreak seems not to work! What do I do?! Mainly, DO NOT PANIC! First things first. Go to “About phone” and see that version it says; something different than 2.2? Cool, no problem. SuperOneClick comes on scene. Download the application, unzip. I assume you already installed the drivers, right? Otherwise, do it and come back when you have done so. Ready? Continue. Turn on USB Debugging and connect the phone to the computer. Execute the application and press the button that says “Root”. Need more information? Here is a video explaining step by step (its in spanish, but graphics needs no language) and if the antivirus gets all paranoid, read the explanation here.
Recovery (Amon-RA and CWM)
Ok, moving on. Just as clarification: From this step on, the phone should already be rooted. Otherwise, you will mourn at the very end because the phone will brick and you’ll end with a very good and expensive paperweight. What is a Recovery? Here the answer.
This is essential before changing the insides of the phone and a step that I believe needs to be forever linked to rooting process. Why? Simple! Installing a Recovery allows full system backup and restore if something goes wrong. That linking to rooting process? Because if you install a root application, modify the system, and damage the system, it can be restored to a previous time and we’re all happy campers. See?
So this is where we get our hands dirty. Initially, I ask again, have you installed the drivers? (From this point on I shouldn’t ask) Have you rooted the phone? Responded twice yes? Perfect. Now, download the Android SDK or only the .zip attached here (unzip preferably in C:\ADB\) to continue this process. Also download the Recovery that you will install, we have Amon-RA and ClockworkMod (CWM) v5, v5 touch, and v6, extract the recovery.img file to the folder where adb.exe is (If you used the SDK installer, should be at C:\Program Files\Android\android-sdk\platform-tools\; if you used the .zip, and extracted as recommended, C:\ADB\). Which to choose? My recommendation, CWM v5 (either one). Connect the phone to the computer in with USB Debugging activated. By the way, how do you feel using command line in Windows? Moving on…
Open a command window, go to where adb.exe is and run the following commands:
Code:
adb push recovery.img /sdcard/
adb push flash_image /sdcard/
With this we have copied what we need into the phone’s SD card. Just to clarify: 1) the flash_image file can only be found in the recovery Amon-RA zip (not sure if it is generic or modified exclusively for the P350, then I’d rather play it safe) and 2) CWM recovery v5 and v5 touch files come in zip-installable, but you can open the file and use recovery.img in it. In CWM v6 there is an installable zip and another to follow this same process. Lets continue…
Code:
adb shell
$ su
# mount -o remount,rw -t yaffs2 /dev/block/mtdblock1 /system
# cat /sdcard/flash_image > /system/bin/flash_image
# chmod 755 /system/bin/flash_image
# sync
Up to this we have only prepared the area to install the Recovery. It it recommended to reboot the phone in this step, in case you run out of virtual memory but is not really so necessary (If you see an error message, then reboot). That’s yours decision. Continue…
Code:
adb shell
$ su
# flash_image recovery /sdcard/recovery.img
# sync
To confirm that everything is installed without issues it must happen one thing and do another thing. What must happen is when you execute the flash_image command, no errors should appear, if otherwise reboot and repeat the last block of commands. What must be done is execute the command reboot recovery and if everything is alright, you should go into Recovery menu, if not then all the information has been erased and back to square 1 (it happened to me the first time).
Kernel
Just for safety: are drivers installed? Root acquired? Recovery installed? Already made a backup of the ROM in use at the moment (so far should be the LG ROM)? Do it!!
So, what’s a kernel? Here’s the answer. What choices do we have? Well not too many, it depends. Are we still on the LG Stock ROM or a Froyo-based ROM (oh, getting ahead aren’t we?!)? Well, the truth, with this ROMs there are not many: Team Pecan Kernel would be my recommendation, RoQ Kernel which also works quite well. CM7 ROM or any other Gingerbread-based? Ron's RM CAF Kernel (updated weekly), pax0r kernel (discontinued), Vivek Kernel (also discontinued but higher than pax0r). Read how to use Recovery for the installation of installable zip files from Recovery. This is also applicable for the installation of ROMs.
ROM
Still with me? Still no cardiac arrest? Relax, breathe! As we reach the last modification process of the phone. After surviving this, you will have the full capacity to recover the phone from any eventuality. Dictionary, which is a ROM? Here the answer.
ROM, What options do we have? Well, although it may seems, there are many options to choose from! We have some created from source code, based-on and others that have been “ported” to work with the device. Among those created from the source we have: CyanogenMod 7.2, Pure CM Invasion and CyanogenMod 9 (Work in Progress, not quite stable), based-on: Androm x4.2 (CM7) Arc XP (CM7), Gingerbread Optimus UI (CM7) Gingerblur (CM7) and MIUI v4 (based on CM7, Arc XP with a theme very close to the real MIUI, Japanese ROM). Ports: JoyOS, ICS (Discontinued unstable), BeautySense (Decent and functional).
Further Development/Tweaks
At the moment a new tool has been released called LG P350 Pecan Toolkit, developed by antdking. Its in early development and so far it roots, unroots and installs recovery. Saves some the hassle of the command line but if we haven’t gone through all the problems and commands, what have we learned? Anyways, here’s the original thread where you can follow the development and post ideas or bugs.
If you wanna go all-in into ROM cracking and research, we have also the LGExtract tool, which unpacks the KDZ file into bits and pieces. DZ Extract Tool extracts the files within a DZ package very much into source code. I've used these tools but as my experience with coding and android development is very close to none all I've done is extract the files and read them. Antdking reminded me of a simple yet powerful tool to continue decompiling the LG filesystem called unyaffsmbn. I came across it when we were trying to decompile baseband (amss.mbn) for CM9 without success, just lo later know that the tool just decompiled system.mbn. Oh well. Antdking compiled unyaffsmbn into a nice little tool ready to work, here it is.
The volume on this phone, as many may know, is low. But there is a way to elevate it. Execute the phone app and press: 3845#*350#. This will bring up a Hidden Menu. Go to: Device Test > Sound Test > Audio CAL Tool > Subsystem Calibration. In the Gain Type dropdown list, select Speaker Gain. Set Data textbox gets focus, input the number 90 and press OK button. In Gain Type, select Input1 Gain, and we press Ok button again. Exit the Hidden Menu. This will elevate the speaker volume but just temporary, it will be restored to default values when rebooted. So either don't reboot or repeat this process everytime you reboot.
And that would be all. Happy hacking!
Great kudos to the real developers here:
drapalyuk: For the first ever recovery for P350, Amon-RA
pax0r: Started it all, Kernel, ROM
ron gokhle: ROMs, Kernel and Recovery builds
vivekkalady: Kernel, Touch Recovery, first ICS port, and some other fix work
nikhil4186: For the KDZ Guide (although written originally for LG P500
antdking: For a great-to-be toolkit
great guide good job
Nicely written.Its a really good guide for all those who are new to P-350 and I believe that it will help them to learn some of the basic stuff.Well done!
to go on the end of this guide, how to extract the files out of the system.mbn to get the system files
http://db.tt/7VruqEzr
it returns similar files to what you find in a rom
I did not make unyaffsmbn
I made the tool that uses unyaffsmbn
enjoy
antdking said:
to go on the end of this guide, how to extract the files out of the system.mbn to get the system files
http://db.tt/7VruqEzr
it returns similar files to what you find in a rom
I did not make unyaffsmbn
I made the tool that uses unyaffsmbn
enjoy
Click to expand...
Click to collapse
got the PM and you reminded me of that tool (I remembder I came across it when we were trying to crack amss.mbn for CM9)... I'll post the original thread and the tool you just mentioned...
Updated adding unyaffsmbn tool... Thanks antdking!
Added Volume tweak for speaker to sound harder.
Added P350 (and guide) to XDA wiki. http://forum.xda-developers.com/wiki/LG_Optimus_Me
dbarrera said:
Added P350 (and guide) to XDA wiki. http://forum.xda-developers.com/wiki/LG_Optimus_Me
Click to expand...
Click to collapse
thanks man :good::good::good::good::good::good::good::good:
Guys We have got Official Support From XDA Please Move This Thread To Our Device Section
Very good!!!
I placed some problem I am having, just in case you have time an patience for this case.
Tks
http://forum.xda-developers.com/showthread.php?t=2461183
Great Guide Man! Thanks a lot.