[Q] Unable to update with wifi patch - Tilt, TyTN II, MDA Vario III Android Development

I installed Froyo to my Tilt NAND and it boots up fine. However, when I try to enable wifi, it tells me "rror". I read online that there is a wifi patch I could install but when I try to "install update" it via boot menu (hold center D button while booting up), it tells me my Tilt is out of space... I have 105MB left on the phone... Help!
Another method suggested was to add/replace the wifi.ko file in adroidinstall.tgz. However, I do not have programs to do that- I downloaded some windows program that claims to be able to but it does not seem to be working.
The version I have installed is 'KAISIMG-320-FROYO-27-11-10.NBH'.

phwang7 said:
I installed Froyo to my Tilt NAND and it boots up fine. However, when I try to enable wifi, it tells me "rror". I read online that there is a wifi patch I could install but when I try to "install update" it via boot menu (hold center D button while booting up), it tells me my Tilt is out of space... I have 105MB left on the phone... Help!
Another method suggested was to add/replace the wifi.ko file in adroidinstall.tgz. However, I do not have programs to do that- I downloaded some windows program that claims to be able to but it does not seem to be working.
The version I have installed is 'KAISIMG-320-FROYO-27-11-10.NBH'.
Click to expand...
Click to collapse
I recommend either downgrading to Eclair, or Donut, or use atools to modify your System/Data partition sizes so your System partition reads 110MB or more. Froyo builds require a minimum of 90-98MB, and the androidupdate files use an additional 6-8MB, so you're basically hitting your max /system size if your defaulted to 107MB. Plus you could be 1-2MB under your max and that error will still occur, as you need a bit of overhead for extracting compressed archives
Plus hate to say it, but after a Android install, you'll never have 107MB of free system space. It's impossible for a 256MB ROM, that's split 4 ways: Radio ROM which is 17MB, Kernel at 3MB, System at 107MB and Data at 101MB.

phwang7 said:
Another method suggested was to add/replace the wifi.ko file in adroidinstall.tgz. However, I do not have programs to do that- I downloaded some windows program that claims to be able to but it does not seem to be working.
Click to expand...
Click to collapse
A tools do it.

The Atools page says it does not work on windows.

now, where did you read that??
Install Python 2.7 and you can run atools

phwang7 said:
The Atools page says it does not work on windows.
Click to expand...
Click to collapse
As i have written windows user = stupid user.

Yep, it was that part that was confusing. If the program would work, why would the poster throw in telling Windows users to not ask questions... that, in itself, is just stupid.

i wrote that for the stupid windows user is totally unuseful to write question because they can't do nothing.
I also wrote for the clever windows user (and other) the guide.
If you consider yourself one of the first or if you don't like my software it's your problem.

Related

update 18-may dualizer major update: full toolkit(beta)!

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?)

[Q] DHD android most beginner know how

Finally I got my DHD, the time where everything is rolling out, from perm root, to recovery...
The good thing, I'm very happy with my DHD, the bad thing, I'm not familiar yet with android system.
I revised a lot of android and DHD threads, and I faced many new terminologies that belong to android where I like to have explanation for each.
Please let me understand the following issues the beginner way, allowing me to maybe make a simple guide answers for most new android users coming from winmo.
I-General questions:
1-DHD should be multitouch. Then why games like Gameloft are not multitouch like on ipod or iphone?
2-What are the buttons combinations for the different operations like hard reset & boot loader?
3-I read that android can’t share internet via USB for those with no WIFI at home or office. As I knew it’s due to ad hoc issue so it's impossible to get internet via USB cable from desktop. When I plugged my DHD, I choose internet pass through and I got internet on my DHD, is it a new feature implemented in DHD only, or is it a 2.2 update that will work on other devices?
4-Winmo gives the choice to install applications on either the device or SD card. Android have nothing like this, so when I install applications, where do they go, and is there a workaround to put everything on SD card, or maybe give choice to where to install?
5-My DHD comes with an 8 GB mini SD card where there are some folders and files on it. Are they necessary to run the system, what if I replaced this card with another formatted one, what will happen, or what if I format this card?
II-System info:
1-Baseband version (is it like the radio in winmo?)
2-Kernel version (is it one kernel for the entire device? Does it updates like rom or like radio?) e.g. (kAmMa's OC&GOV&BFS Kernel - Performance and Stability. Is this a rom or just kernel that will update some parts of the rom without losing data on the device?)
3-Build number (is this the firmware?) e.g. (i have 1.32.405.3 CLxxxxxx release-keys, what does release keys means?)
4-Software number (or this is the firmware?)
III-OTA ACE with radio:
1-OTA (is it a rom, does it mean over the air, if yes what does that mean? Can we update OTA with no root?)
2-ACE
On winmo (HD2), I know HSPL will let me unlock ISPL so I can install any custom or cooked rom, languages and applications...
For android, as far as I know there is no one click solution. From what I understand to do everything in android with no restrictions u need to do the followings:
IV-How to root Desire HD install h-boot (S-Off) and Clockwork recovery?
Please identify which one is just a process that we do it once in order to unlock it, which is a boot loader run application and which one is an android application:
1-Root (is it what gives access to the root folders of the system that maybe are hidden by default or encrypted?)
2-Hboot
3-S-off (is it security off? if yes, it is security off for what? installing applications, or read write to some encrypted partitions?)
4-Clockwork (is it something necessary to do in order to install custom rom, no adds, backup and so on, or is it something totally independent and related only to unlock the speed of the CPU where you can leave it intact if you won’t play with the CPU speed?)
5-Recovery (from what I understand it seems that recovery is a system shell command like dos or more like bios for android but named as recovery, what can we do with the recovery other than recovering the device?)
6-Recovery image (is it a rom backed on the form of image and provided by developers, so we can install it directly on the device using only the recovery shell?)
V-More things to know about:
1-What is adb?
2-What is busybox?
2-What is fast boot?
3-What is eMMC write?
4-What is ext2 or ext4 (is it like the partition type of the SD card based on UNIX system? if yes, why should we change or modify this ext)
5-Rom manager (is it a desktop pc application or android device application? is it something like I can put the RUU file of the rom on my SD card and using the rom manager I can install the rom from there, nothing more nothing less?)
vuedesprit said:
Finally I got my DHD, the time where everything is rolling out, from perm root, to recovery...
The good thing, I'm very happy with my DHD, the bad thing, I'm not familiar yet with android system.
I revised a lot of android and DHD threads, and I faced many new terminologies that belong to android where I like to have explanation for each.
Please let me understand the following issues the beginner way, allowing me to maybe make a simple guide answers for most new android users coming from winmo.
I-General questions:
1-DHD should be multitouch. Then why games like Gameloft are not multitouch like on ipod or iphone?
2-What are the buttons combinations for the different operations like hard reset & boot loader?
3-I read that android can’t share internet via USB for those with no WIFI at home or office. As I knew it’s due to ad hoc issue so it's impossible to get internet via USB cable from desktop. When I plugged my DHD, I choose internet pass through and I got internet on my DHD, is it a new feature implemented in DHD only, or is it a 2.2 update that will work on other devices?
4-Winmo gives the choice to install applications on either the device or SD card. Android have nothing like this, so when I install applications, where do they go, and is there a workaround to put everything on SD card, or maybe give choice to where to install?
5-My DHD comes with an 8 GB mini SD card where there are some folders and files on it. Are they necessary to run the system, what if I replaced this card with another formatted one, what will happen, or what if I format this card?
II-System info:
1-Baseband version (is it like the radio in winmo?)
2-Kernel version (is it one kernel for the entire device? Does it updates like rom or like radio?) e.g. (kAmMa's OC&GOV&BFS Kernel - Performance and Stability. Is this a rom or just kernel that will update some parts of the rom without losing data on the device?)
3-Build number (is this the firmware?) e.g. (i have 1.32.405.3 CLxxxxxx release-keys, what does release keys means?)
4-Software number (or this is the firmware?)
III-OTA ACE with radio:
1-OTA (is it a rom, does it mean over the air, if yes what does that mean? Can we update OTA with no root?)
2-ACE
On winmo (HD2), I know HSPL will let me unlock ISPL so I can install any custom or cooked rom, languages and applications...
For android, as far as I know there is no one click solution. From what I understand to do everything in android with no restrictions u need to do the followings:
IV-How to root Desire HD install h-boot (S-Off) and Clockwork recovery?
Please identify which one is just a process that we do it once in order to unlock it, which is a boot loader run application and which one is an android application:
1-Root (is it what gives access to the root folders of the system that maybe are hidden by default or encrypted?)
2-Hboot
3-S-off (is it security off? if yes, it is security off for what? installing applications, or read write to some encrypted partitions?)
4-Clockwork (is it something necessary to do in order to install custom rom, no adds, backup and so on, or is it something totally independent and related only to unlock the speed of the CPU where you can leave it intact if you won’t play with the CPU speed?)
5-Recovery (from what I understand it seems that recovery is a system shell command like dos or more like bios for android but named as recovery, what can we do with the recovery other than recovering the device?)
6-Recovery image (is it a rom backed on the form of image and provided by developers, so we can install it directly on the device using only the recovery shell?)
V-More things to know about:
1-What is adb?
2-What is busybox?
2-What is fast boot?
3-What is eMMC write?
4-What is ext2 or ext4 (is it like the partition type of the SD card based on UNIX system? if yes, why should we change or modify this ext)
5-Rom manager (is it a desktop pc application or android device application? is it something like I can put the RUU file of the rom on my SD card and using the rom manager I can install the rom from there, nothing more nothing less?)
Click to expand...
Click to collapse
Congratulations. You win the "most questions asked in a single post" award.
Sent from my Desire HD using XDA App
That is a ridiculous amount of questions, and the thread is in completely the wrong area of the forum. I'm sure you'd find the answer to pretty much all your questions if you looked hard enough, but to answer the one about multi-touch. It is multi touch and all the games I've played from your example 'Gameloft' are multi-touch, so I don't know what you're smoking buddy, but ease off.
1. Inb4 "search".
2. Wrong forum.
3. No really, try searching. At least 30% of that is googleable.
Sent from my Desire HD using XDA App
Ok guys, thank you all for your replies, and yes I knew that a war and flames will go on here, but seriously if you think this is ridiculous or newbie or most dumb questions, do not turn the way of the thread or flame me, my intentions are to make this as a one small guide for most new androids functions, it's not a bad thing to do, in fact I will learn as much as other new users here, no one is asked to answer all those ridiculous questions, just answer what you know about, guys please take it seriously and easy, saying look harder will not help the thread, it may help me personaly, but be sure that I did a lot of search, and it will not hurt to put everything in one place, and as you can see, I answered most of the questions up to what I gathered, you can correct me about my answers, put your thoughts or not answer at all, but please be constructive here, and if you all think that i'm in the wrong forum, or asking too much, or asking ridiculous questions, please moderator feel free to do what you think is better for the forum.
Sorry guys for bothering you. Thank you for your response.
N.B.: just to be more accurate, I tried the prince of persia pre installed on the phone by the dealer, and it was not multi touch, so you cant walk and use any of the right actions at same time.
@vuedesprit: Good thread, and thanks for taking all the criticism from the more experienced users.
@all chimers chiming the "use search, wrong forum" tune: c'mon guys, there's at least 2 of us reading this thread going, it's about time all this information got consolidated into one place! The easier it is to find this information, the easier it would be for more of us to get engaged in the process and thus further development, enhancement and adoption.
While our "friendly" mod is doing his best to keep the forums clean, they're as fragmented as ever and from time-to-time, it becomes necessary to consolidate the information into a single thread. I'm sure most of you started some place too and remember the time not so long ago when it was difficult to find even the most basic info? I think by sharing your knowledge, you will gain a much better following and the platform will gain much better adoption.
My 2 cents worth anyways...I've had my DHD for 3 days now and I too am struggling to perform even the most basic tasks.
We really need a questions and answers sub forum
Fair enough, maybe my first comment was a bit rash, but I didn't mean to appear rude. I shall try to answer some questions here:
GENERAL.
1. From my own experience all games advertised as multitouch are exactly that. I don't know about the version of PoP that you have installed from carrier, but I do find that odd.
2. Hard reset is a little perverse with the new "fastboot" hibernation feature that HTC have implemented. You have to go to MENU>SETTINGS>APPLICATIONS and disable "fastboot" (this is where confusion may arise as this is not the bootloader fastboot that allows images to be flashed)!! Now when you hold down the power button and get the option to power off, you will properly power off the phone. Next if you hold "VOLUME DOWN" and "POWER" buttons you will reboot into HBoot, from here the VOLUME UP/DOWN keys navigate the menu and POWER selects menu options.
3. Not sure about this one.
4. Since the release of FROYO you can go to MENU>SETTINGS>APPLICATIONS>MANAGE APPLICATIONS then select any app and move to either SD or to phone memory.
5. The folders on the SD card are mostly generated by the phone when you first insert it. The user guide and HTC sync software are there to move onto your PC for safe keeping. If you insert a freshly formatted SD card, the phone will make fresh folders such as DCIM for pictures, etc...
SYSTEM INFO.
1. Baseband is radio software.
2. Kernel is the linux kernel that is running below Android, this can be updated separately from the main ROM, radio etc. HOWEVER CAUTION IS ADVISED AS CERTAIN KERNELS WILL NEED NEW MODULES FOR HARDWARE TO FUNCTION CORRECTLY as you will see from the wifi modules bundled with the OC kernels.
3. Build number pertains to HTC's internal software version classification (some are built specific for carriers) they are generally released via RUU (ROM Update Utility aimed at windows) or OTA (Over The Air update received on phone [again sometimes carrier specific]). Release keys pertains to the fact that the firmware has been signed by HTC (I think).
4. Software number, basically as above.
OTA ACE with Radio.
1. As Above.
2. ACE: internal HTC name for Desire HD (also reportedly known as "SPADE")
ROOT DESIRE HD ETC.
Most of what you have written is pretty much correct.
MORE THINGS TO KNOW ABOUT.
1. http://developer.android.com/guide/developing/tools/adb.html
2. http://www.busybox.net/about.html
3. http://android-dls.com/wiki/index.php?title=Fastboot
4. eMMC write basically means that you can write to the internal phone (normally protected) memory such as /SYSTEM, this is what S-OFF allows you to do whenever you want. However, the modules that allow the ENG HBoot image to be flashed are what really accomplish this in the first place so theoretically you could just run that module every time you wanted to write to /SYSTEM but that would become very tedious very quickly. I can't really explain further, as I don't have the knowledge.
5. EXT2 or EXT4 are filesystem structures just like FAT, FAT16, FAT32, NTFS, HFS+ etc, EXT4 is newer and more advanced than EXT2 and therefore is more efficient. (kinda general but you get the idea. NEWER=BETTER)
6. ROM manager, find this in the android market, it is free, you install it on your phone and with the addition of clockworkmod it gives you the ability of flashing ROMs etc. USE WITH CAUTION.
I hope that this answers or clarifies most of what you have asked or said, please feel free to cut and paste any of this info into your first post so that we can actually consolidate this.
P.S. I too am a complete android noob and this is my first android phone, I have picked this info up mainly from this forum so all credit for information goes to XDA-DEVELOPERS.COM and not me.
Cheers,
Dok
berek9999 said:
congratulations. You win the "most questions asked in a single post" award.
Sent from my desire hd using xda app
Click to expand...
Click to collapse
+1111111111^2
1-DHD should be multitouch. Then why games like Gameloft are not multitouch like on ipod or iphone?
Click to expand...
Click to collapse
an application must support multitouch and other gestures. eg, opera doesnt support multitouch (ie you cant zoom in and out) but the browser that comes with the DHD does.
2-What are the buttons combinations for the different operations like hard reset & boot loader?
Click to expand...
Click to collapse
boot loader = turn phone off. then, volume down + power on.
4-Winmo gives the choice to install applications on either the device or SD card. Android have nothing like this, so when I install applications, where do they go, and is there a workaround to put everything on SD card, or maybe give choice to where to install?
Click to expand...
Click to collapse
application must support running from /sdcard. When you install an app go to settings -> Applications -> manage applications. From here you can uninstall or move apps to the sdcard. Bear in mind if you have not rooted your phone you may not be able to uninstall some apps (eg amazon reader).
5-My DHD comes with an 8 GB mini SD card where there are some folders and files on it. Are they necessary to run the system, what if I replaced this card with another formatted one, what will happen, or what if I format this card?
Click to expand...
Click to collapse
some application data is stored on your sdcard, and apps are stored here if you have moved them by using the steps above. if you change sd cards this info is unavailable to the app but the app should still work. any settings you had need to be redone.
2-Kernel version (is it one kernel for the entire device? Does it updates like rom or like radio?) e.g. (kAmMa's OC&GOV&BFS Kernel - Performance and Stability. Is this a rom or just kernel that will update some parts of the rom without losing data on the device?)
Click to expand...
Click to collapse
the kernel is not part of a rom or the radio. It is stored in the boot partition in the emmc (where fastboot(aka hboot)/splash images/boot(kernel)/recovery/ are all stored). It is generally included with but not required by a custom rom. ie, a custom rom builder may choose to include a specific kernel with his rom but it is not mandatory.
1-OTA (is it a rom, does it mean over the air, if yes what does that mean? Can we update OTA with no root?)
Click to expand...
Click to collapse
yes, you can do OTA HTC updates. but, there are no custom (non signed) updates delivered OTA. An unrooted rom will not be able to flash non signed updates (or roms).
How to root Desire HD install h-boot (S-Off) and Clockwork recovery?[/U][/B]
Click to expand...
Click to collapse
there is a good thread here - http://forum.xda-developers.com/showthread.php?t=841076.
Please identify which one is just a process that we do it once in order to unlock it, which is a boot loader run application and which one is an android application:
1-Root (is it what gives access to the root folders of the system that maybe are hidden by default or encrypted?)
Click to expand...
Click to collapse
android application. eg, visionary+.
2-Hboot
Click to expand...
Click to collapse
hboot is also known as bootloader. it is the white screen with the skating androids when you do the volume-down + power combination when switching on your phone.
3-S-off (is it security off? if yes, it is security off for what? installing applications, or read write to some encrypted partitions?)
Click to expand...
Click to collapse
s-off stands for security off. you can check the status by doing the volume-down + power combo. At the top it will either say s-on or s-off. If you have s-on then your bootloader (hboot), boot (kernel) /system (android) and recovery (eg clockworkmod) partitions are all read only.
4-Clockwork (is it something necessary to do in order to install custom rom, no adds, backup and so on, or is it something totally independent and related only to unlock the speed of the CPU where you can leave it intact if you won’t play with the CPU speed?)
Click to expand...
Click to collapse
clock work is the recovery partition. you have 3 possible options before loading android when you do the volume-down + power on combo. hboot, then either fastboot or recovery. fastboot and recovery are both ways to flash images to your phone although through different ways (fastboot uses the fastboot command on your pc to send the image, recovery uses .zip's on your /sdcard). clockworkmod is a custom recovery image which you need to flash after achieving s-off. it's also where nandroid backups can be done. if you select recovery before doing this you will get the phone + red triangle icon. thats the stock recovery. the clockworkmod is the green menu selection one.
5-Recovery (from what I understand it seems that recovery is a system shell command like dos or more like bios for android but named as recovery, what can we do with the recovery other than recovering the device?)
Click to expand...
Click to collapse
see above.
6-Recovery image (is it a rom backed on the form of image and provided by developers, so we can install it directly on the device using only the recovery shell?)
Click to expand...
Click to collapse
clockwork mod can backup your phone's partitions (boot/userdata/system) so that if you mess up installing a rom you have a way to recover. this is known as a nandroid backup.
1-What is adb?
Click to expand...
Click to collapse
adb is android debug something. It is a way to send commands to the android operation system from your pc (either windows or linux). eg, you can run a single command, or run a shell (terminal session). it is part of the android sdk under tools.
2-What is busybox?
Click to expand...
Click to collapse
busybox is a single executable whihc runs under the android OS that provides standard linux commands (eg, ls, rm, cd) to any application. it is so that a script writer does not need to know the partiticular rom you have and then cater for it, but only that you have a certain version of busybox. eg, busybox 1.17.1 provides the same commands whether it is on a leedroid rom or a cyanogen rom.
2-What is fast boot?
Click to expand...
Click to collapse
fastboot is a way to flash images to your phone. it is accessed via hboot. you need the fastboot exe from the htc developer site. it can flash the boot (kernel), recovery (eg clockworkmod) and the radio (i think).
3-What is eMMC write?
Click to expand...
Click to collapse
the emmc is the storage device which holds hboot, fastboot, recovery, /system, /userdata and (not sure about this one) radio. when you switch on your phone the emmc is read-only due to the s-on flag being set by hboot. you need to flash the engineering hboot which does not set s-on when you switch your phone on.
4-What is ext2 or ext4 (is it like the partition type of the SD card based on UNIX system? if yes, why should we change or modify this ext)
Click to expand...
Click to collapse
ext2 and ext4 are linux file system types. eg, windows is ntfs, linux has ext2/3/4 and others.
5-Rom manager (is it a desktop pc application or android device application? is it something like I can put the RUU file of the rom on my SD card and using the rom manager I can install the rom from there, nothing more nothing less?)
Click to expand...
Click to collapse
rom manager is an android app available on the market place to help with the flashing process. it can flash recovery partitions (as long as your phone is s-off), make nandroid backups (as long as you have clockworkmod & s-off). it can also flash custom roms. it does not flash these from within the android OS (afaik) but it will reboot into (not sure on this one) the recovery partition and leaves it instructions to flash a particular rom.
This thread is amazing!!
We had a lot threads like this in the HTC Blackstone Board of pocketpc.ch....
Hope to get more threads like this in every device category....
Thumbs up
Perhaps Threadstarter can write the answers in the first post...??
50chickens said:
an application must support multitouch and other gestures. eg, opera doesnt support multitouch (ie you cant zoom in and out) but the browser that comes with the DHD does.
boot loader = turn phone off. then, volume down + power on.
application must support running from /sdcard. When you install an app go to settings -> Applications -> manage applications. From here you can uninstall or move apps to the sdcard. Bear in mind if you have not rooted your phone you may not be able to uninstall some apps (eg amazon reader).
some application data is stored on your sdcard, and apps are stored here if you have moved them by using the steps above. if you change sd cards this info is unavailable to the app but the app should still work. any settings you had need to be redone.
the kernel is not part of a rom or the radio. It is stored in the boot partition in the emmc (where fastboot(aka hboot)/splash images/boot(kernel)/recovery/ are all stored). It is generally included with but not required by a custom rom. ie, a custom rom builder may choose to include a specific kernel with his rom but it is not mandatory.
yes, you can do OTA HTC updates. but, there are no custom (non signed) updates delivered OTA. An unrooted rom will not be able to flash non signed updates (or roms).
there is a good thread here - http://forum.xda-developers.com/showthread.php?t=841076.
android application. eg, visionary+.
hboot is also known as bootloader. it is the white screen with the skating androids when you do the volume-down + power combination when switching on your phone.
s-off stands for security off. you can check the status by doing the volume-down + power combo. At the top it will either say s-on or s-off. If you have s-on then your bootloader (hboot), boot (kernel) /system (android) and recovery (eg clockworkmod) partitions are all read only.
clock work is the recovery partition. you have 3 possible options before loading android when you do the volume-down + power on combo. hboot, then either fastboot or recovery. fastboot and recovery are both ways to flash images to your phone although through different ways (fastboot uses the fastboot command on your pc to send the image, recovery uses .zip's on your /sdcard). clockworkmod is a custom recovery image which you need to flash after achieving s-off. it's also where nandroid backups can be done. if you select recovery before doing this you will get the phone + red triangle icon. thats the stock recovery. the clockworkmod is the green menu selection one.
see above.
clockwork mod can backup your phone's partitions (boot/userdata/system) so that if you mess up installing a rom you have a way to recover. this is known as a nandroid backup.
adb is android debug something. It is a way to send commands to the android operation system from your pc (either windows or linux). eg, you can run a single command, or run a shell (terminal session). it is part of the android sdk under tools.
busybox is a single executable whihc runs under the android OS that provides standard linux commands (eg, ls, rm, cd) to any application. it is so that a script writer does not need to know the partiticular rom you have and then cater for it, but only that you have a certain version of busybox. eg, busybox 1.17.1 provides the same commands whether it is on a leedroid rom or a cyanogen rom.
fastboot is a way to flash images to your phone. it is accessed via hboot. you need the fastboot exe from the htc developer site. it can flash the boot (kernel), recovery (eg clockworkmod) and the radio (i think).
the emmc is the storage device which holds hboot, fastboot, recovery, /system, /userdata and (not sure about this one) radio. when you switch on your phone the emmc is read-only due to the s-on flag being set by hboot. you need to flash the engineering hboot which does not set s-on when you switch your phone on.
ext2 and ext4 are linux file system types. eg, windows is ntfs, linux has ext2/3/4 and others.
rom manager is an android app available on the market place to help with the flashing process. it can flash recovery partitions (as long as your phone is s-off), make nandroid backups (as long as you have clockworkmod & s-off). it can also flash custom roms. it does not flash these from within the android OS (afaik) but it will reboot into (not sure on this one) the recovery partition and leaves it instructions to flash a particular rom.
Click to expand...
Click to collapse
Thank you very much.

NAND Testing - 05-25 Update: New LK, Recovery.img, Kernel Updates through Recovery

THIS IS FOR TESTING ONLY. DO NOT ATTEMPT TO INSTALL THIS IF YOU DON'T KNOW HOW TO GET INTO BOOTLOADER MODE AND FLASH A ROM FROM THE SD CARD.
Announcements​
We are currently replacing Tinboot with LK for boot. This will give us fastboot and many other enhancements and fixes to make our device more like a native Android device. This has already fixed some issues with GSM phones, sleep modes, and a few other things. The current issue being worked on is the power button not working (possible GPIO issue).
Introduction​
This thread tracks the most recent NAND development. A huge thanks to [ACL] and WoZZeR999 for dedicating time to NAND development for us, and again, thanks to Jonpry, PHH, stinebd, and the rest of #htc-linux for their contributions. It's truly amazing what these guys have done for us, so be sure to show them your appreciation :wink:
The original NAND boot testing thread can be found here:
http://forum.ppcgeeks.com/tp2-andro...und-test-7-single-nbh-serialno-tilt2-fix.html
File Repository​
Autobuild files can be found here: Index of /files/
The LK directory will contain the latest LK Bootloader and boot image code.
The rhodium_nand directory contains the latest kernels
The XDAndroid directory contains the latest OS files and updates (including the root update)
Note: We often disable autobuild when extremely experimental code is submitted, so this may not always be up to date but should be more stable than content we post in the threads.
Latest Files
LK Bootloader: http://htcdevs.wirelesstcp.net/files/LK/RHODIMG_NORECOVERY.NBH
Recovery Image: http://htcdevs.wirelesstcp.net/files/LK/recovery.img
05-22 Kernel: http://htcdevs.wirelesstcp.net/files/rhodium_nand/20110522_175721-kernel-update.zip
FRX06 OS Files: http://htcdevs.wirelesstcp.net/files/xdandroid/FRX6/update.zip
Optional - FRX06 Root: http://htcdevs.wirelesstcp.net/files/xdandroid/opt_updates/Root-Update.zip
Installation Procedure​
Obtain Install Files
You need 4 files to get NAND up and running:
LK Bootloader NBH
Recovery.img
Kernel
OS Files
Install Directions
1) Set up your computer to use fastboot: http://forum.xda-developers.com/showthread.php?t=532719
2) Flash your phone with the LK Bootloader NBH
3) Copy recovery.img to your fastboot/adb folder
4) Open bash/command prompt and run fastboot flash recovery recovery.img
5) If successful, type fastboot reboot, and hold the Power Button as your phone boots
6) Your phone should boot into recovery, and there you can apply the various update.zip files in this order:
- FRX06 Update.zip
- Kernel-Update.zip
- Root-Update.zip
To navigate in recovery, use volume up/down (or up/down on keyboard) to change selection, then use End Call key (or Enter on keyboard) to make a selection.
Here's a video from ACL
http://www.youtube.com/watch?v=4r4o2CCKwvU
Work in Progress
Panel init/power down
No data on first boot
Youtube app has issues
GSM can boot with no rild arguments (no data)
Not Working at all
Camera
No bluetooth
No 3.5mm headphone jack​
Frequently Asked Questions
What is NAND booting?
NAND booting uses code on the NAND to boot directly into Android without having Windows Mobile on the device. Currently, zImage and initrd.gz are stored on the internal NAND while the modules, rootfs, ext2, and data are stored on the SD card.
How do I setup NAND boot?
First, you need to download the Update Utility (CustomRUU) and the latest package. Extract the NBH to the same folder as the Update Utility and flash like you would a custom ROM. Put the included modules on the SD card (modules must be from the same package as the NBH) along with the modified rootfs.img (see first post) and system.ext2 from http://xdandroid.com/wiki/Main_Page (you can use system.ext2 from BLAZN, but XDAndroid will be better for testing)
Why don't my changes to Startup.txt work/How do I change boot options?
Because we are booting without Haret, Startup.txt is not used. Any changes to Startup.txt will have no effect. If there is a boot option you need enabled, you can either compile a new tinboot with those changes or let me know and I can compile one for you.
Where are the Android files stored and how do I update them?
Modules, rootfs.img, and system.ext2 must be stored under /andboot on the SD card. Every update will require flashing a new NBH (contains zImage) and replace the old modules file with the new one. Sometimes deleting the data.img file is necessary between builds if you experience major problems.
Wifi or other devices aren't working after an update...
The modules and zImage are a pair and must always be updated together. If you only flash the NBH but don't replace the modules file on the SD card, you will get a mismatch on the modules preventing the drivers from loading.
My battery drained and now my phone is stuck in a boot cycle! AHHHHHH!
Don't worry about it. You have two quick and easy options. First, unplug the USB cable, then remove the battery, then put the battery back in, and plug the USB cable back in. Now let it charge for 5 minutes, then turn it on, and you should be good to go. If it still does not work, unplug the USB cable, then remove the battery, then put the battery back in, attempt to enter bootloader mode and plug the USB cable back in as soon as the bootloader screen comes up. Now you can charge it for 5 minutes and restart back into Android (where you should continue charging).
Project Status
What is currently being worked on?
Battery life (up to about 9 hours now)
Backlight control (Dimming works and backlight can be turned off, but re-initializing is causing issues)
What is working?
Phone
Data
Sound
GPS
Keyboard
Wifi
Hardware 3d
What is NOT working?
Camera
Bluetooth
3.5mm headphone jack
Heh, only a matter of time before this thread made it over onto XDA. Thanks Nate
testing
has anybody here tested yet and if so... please note the outcome of the testing i would like to test but i would need more elaborate install instructions so that it is done right the first time ...also a couple of links are not working
ksper6986 said:
has anybody here tested yet and if so... please note the outcome of the testing i would like to test but i would need more elaborate install instructions so that it is done right the first time ...also a couple of links are not working
Click to expand...
Click to collapse
Thanks for the heads up. The copy/paste from PPCG killed some of the links. They should be working now
And this does work great. You can find the thread over at PPCGeeks here: http://forum.ppcgeeks.com/tp2-andro...esting-12-11-panel-power-off-now-working.html
First of all i want to thank all devs who are involved in the NAND Booting Section. I think i will test this in the next days but i must ask some questions first to do it .
1. So, do i need to do the Task 29 or is it just in case of problems.
2. Am i able to flash WinMob back if i'm failing?
yes u can go back to windows. infortunately i have been following all the steps correctly and it loads up the with letters showing its working and then i get a black screen so i think im stuck at boot any help. can someone tell me what im doing wrong. the files are in sd card/ andboot
Bieka said:
First of all i want to thank all devs who are involved in the NAND Booting Section. I think i will test this in the next days but i must ask some questions first to do it .
1. So, do i need to do the Task 29 or is it just in case of problems.
2. Am i able to flash WinMob back if i'm failing?
Click to expand...
Click to collapse
Task29 is just recommended to make sure everything is nice and clean. It makes troubleshooting much easier because it ensures nothing weird is being read from the internal nand.
You can easily flash back to WinMo by starting the phone in bootloader mode and flashing. Unfortunately, you will not be able to do the ActiveSync connection through USB and flash that way.
kabu said:
yes u can go back to windows. infortunately i have been following all the steps correctly and it loads up the with letters showing its working and then i get a black screen so i think im stuck at boot any help. can someone tell me what im doing wrong. the files are in sd card/ andboot
Click to expand...
Click to collapse
You should have three files in /sdcard/andboot: rootfs.img, system.ext2, and modules (don't rename the modules). Now flash the NBH and it should generate the data.img, and you should be good to go. It should be loaded in under 10 minutes, so if it isn't, I would check the contents of the memory card. Also note the card must be FAT32 formatted and have not be partitioned.
The panel power on/down is apparently fixed for some panels but not others. ACL and bzo have been working together on this and found that there are several different panels being used in our phones, and ACL is working on a patch to fix up the panels that aren't functioning perfectly.
mcnutty said:
RootFS
A custom rootfs.img is required to automatically configure the keyboard. You can override the automatic keyboard by creating a .kb file in your andboot folder. Accepted inputs are: rhod500.kb, rhod400.kb, rhod210.kb, and tilt2.kb
Click to expand...
Click to collapse
What about the rhod100? I have a modified rootfs.img for correct german keylayout in haret version of xdandroid. Can i use that too or do i need to delete all other .kb's? And is it even possible to get a working rhod100 keyboard? I know many questions but i think this should be BEFORE i get lost .
Bieka said:
What about the rhod100? I have a modified rootfs.img for correct german keylayout in haret version of xdandroid. Can i use that too or do i need to delete all other .kb's? And is it even possible to get a working rhod100 keyboard? I know many questions but i think this should be BEFORE i get lost .
Click to expand...
Click to collapse
Ahh yess the custom keyboard and how to create it. This threw me for a bit too and when i realized that all I had to do was open up notepad and then do a saveas rhod400.kb, I laughed at myself.
yep that easy a blank text file with the correct name and you are good to go
Well now that the thread is over on xda I tried again but still to no avail even tried two different SD cards both end with it booting but freezing at SMD: ch 0 OPENING -> OPENED. Pretty sure I have everything setup correctly three files in andboot folder on sdcard renamed rootfs to just rootfs.img but left the other two files. By the way this is on a tilt2.
Thordim said:
Ahh yess the custom keyboard and how to create it. This threw me for a bit too and when i realized that all I had to do was open up notepad and then do a saveas rhod400.kb, I laughed at myself.
yep that easy a blank text file with the correct name and you are good to go
Click to expand...
Click to collapse
Does that mean i just had to rename my rhod100_de.kb file to a rhod400 or something? That would be TO Easy ... ok i always think around corners ))
Bieka said:
Does that mean i just had to rename my rhod100_de.kb file to a rhod400 or something? That would be TO Easy ... ok i always think around corners ))
Click to expand...
Click to collapse
Actually, I didn't account for the non-US variants when creating the rootfs. I have some other modifications that I'm testing for the rootfs at the moment, so I will be sure to add the other variants back in for at least the KB overrides. I will need help with a variable for the automatic detection to work properly.
If anyone has any of the non-US variants, it would be extremely helpful for you to flash to NAND, hook up to ADB, and run "cat /sys/class/htc_hw/machine_variant" and let me know what yours is.
wifi
i want to start off by saying this is an amazing project.
But my problem is that wifi is not working for me. When i try to start wifi, it immediately says "error." I have done many flashes and used task29. i was just wondering if anyone else had this issue.
mcnutty said:
Actually, I didn't account for the non-US variants when creating the rootfs. I have some other modifications that I'm testing for the rootfs at the moment, so I will be sure to add the other variants back in for at least the KB overrides. I will need help with a variable for the automatic detection to work properly.
If anyone has any of the non-US variants, it would be extremely helpful for you to flash to NAND, hook up to ADB, and run "cat /sys/class/htc_hw/machine_variant" and let me know what yours is.
Click to expand...
Click to collapse
I will do that for you in the next days. Before Christmas it's a turbulent time for me. As soon as i can get the Time for it i will flash to nand and follow your instructions. If i need help, can i PM you?
Cheers
I'm using Neopeek's rom instead..how can i set it up? since this rom doesnt use the system.ext2 file
getting calibration without visible points to touch aka the boxes. also, boot ani glitches out on screen with a "solid" animation, and video glitchs on the bottom half of the screen. sits here indefinately.... still waiting..... haha
update: loads to lockscreen, so far can't get screen to stay on??? strange
update2: got it working, but keeps turning screen off immediately... any ideas>?
hmm, i have been trying this and i feel like i have everything right
tilt2.kb, rootfs.img, modules, and system.ext in an andboot folder in my storage card and then, a nbh with the same name as the module in a folder with customRUU.exe. I flash and then it gets to the linux boot screen, after a couple lines go by, the screen fades out and dies and restarts. My battery says 88 percent when i flash back to windows, anybody know what could be going wrong?
HTC Sense
will it only recognize only an ext2 or will it recognize squashfs.
blitzer320 said:
Well now that the thread is over on xda I tried again but still to no avail even tried two different SD cards both end with it booting but freezing at SMD: ch 0 OPENING -> OPENED. Pretty sure I have everything setup correctly three files in andboot folder on sdcard renamed rootfs to just rootfs.img but left the other two files. By the way this is on a tilt2.
Click to expand...
Click to collapse
I'm on the rhod210 (T-Mobile), and I've been having this exact issue. Any ideas?
btw, this is my first post here, but I've been reading and following this project for quite a long time. You guys are great! Thanks for all the work you do!

[GSM + CDMA]Beatsleigher's Root Helper. Getting root access, has never been easier!!!

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.

[Q] FP1 - 1.6 unified storage upgrade: Problems

hi!
i installed the regulat 1.6 update to my FP1 and everything was just fine.
then I tried to install the "unified 1.6 update" which worked but the problems begun:
things I noticed:
1. backup ist not really a backup for the apps but just a way to reinstall the apps I had installed without any settings. not a fun way to find that out when reopening your apps.
2. the update to the 1.6 unifyed also messed with my SD card and deleted files and put new ones there. not something I was expecting. luckily I had a backup of the SD card.
the thing I am looking for a solution:
after merging the partitions I cannot acces the phone storage on my PC (mac osx 10.9.4). not directly as a drive. the android fil transfer tool works, but it does not have all abilities finder/explorere provides. how do I get acces to the phone storage again?
As all my settings are gone anyway I am open to reinstall the phone from scratch.
fivel_ said:
the thing I am looking for a solution:
after merging the partitions I cannot acces the phone storage on my PC (mac osx 10.9.4). not directly as a drive. the android fil transfer tool works, but it does not have all abilities finder/explorere provides. how do I get acces to the phone storage again?
Click to expand...
Click to collapse
Because of the partition layout it no longer is possible to expose the internal storage as mass storage device. Adb will work but the preferred way of transferring files is using the MTP protocol.
I am not a mac user but I think you need to install some additional software.
https://www.android.com/filetransfer/
_keesj said:
Because of the partition layout it no longer is possible to expose the internal storage as mass storage device. Adb will work but the preferred way of transferring files is using the MTP protocol.
Click to expand...
Click to collapse
thanks a lot, that is what I feared.
hi, i'm also have an upgrade problem: mine is that i can't upgrade at all.
i've repartitioned earlier with the app mentioned in the wiki (wiki/Fairphone_Fairphone/Guides#How_to_partition_your_Fairphone).
i've also done the steps _keesj descripes in thread "unified storage setup on re-partitioned FP1" ("Steps for "fiixing" your upgrade").
i'm having Cherry 1.6, and two 7 GB partitions.
does anyone has a solution?
see other (missplaced) post
This post might be of help:
http://forum.xda-developers.com/fairphone/general/unified-storage-setup-partitioned-fp1-t2834642
Donat.Callens said:
This post might be of help:
http://forum.xda-developers.com/fairphone/general/unified-storage-setup-partitioned-fp1-t2834642
Click to expand...
Click to collapse
thanks, i've read it again and tried _keesj's solution again, unfortunately it didn't solve my situation.
i'm a layman in this area, so probably i shoudn't haved 'played' with partitions at all (but with the app it was easy).
my previous post wasn't quite complete... i have had an unified partition before...
because of an app that didn't work, i used the repartition app again to see if that could solve the problem.
it did, but later i wondered if a wrong install in the unified sistuation was the problem... so i thought 'let's try the unified partition again'...
i thought i could simply re-use the Fairphone Updater...
so maybe i'm now having a unified partition divided in 2?
and lost the ability to ever upgrade to newer versions of the Fairphone OS?
i hope someone can help me...
jjjanssen said:
i could simply re-use the Fairphone Updater...
Click to expand...
Click to collapse
Make sure you allow it to reinstall the default recovery.
Donat.Callens said:
Make sure you allow it to reinstall the default recovery.
Click to expand...
Click to collapse
how do I allow it? i didn't get the question you've got ("ROM may flash stock recovery on boot. Fix?").
i downloaded Cherry 1.6 again and chose Install, gave it SU (forever) access, it automatically restarted to the Android with the text “Installing system update…” (no progress bar), and after a few minutes it restarted and nothing is changed. After starting the Fairphone Updater again, it immediately gave the Install option again. Same after selecting the Storage Upgrader.
I also tried restoring from the recovery (default, never replaced), from sd and adb (1.6 does install, 1.3 doesn't, and 1.6 partition upgrader doesn't either, gets aborted)…
Hi,
jjjanssen said:
how do I allow it? i didn't get the question you've got ("ROM may flash stock recovery on boot. Fix?").
i downloaded Cherry 1.6 again and chose Install, gave it SU (forever) access, it automatically restarted to the Android with the text “Installing system update…” (no progress bar), and after a few minutes it restarted and nothing is changed. After starting the Fairphone Updater again, it immediately gave the Install option again. Same after selecting the Storage Upgrader.
I also tried restoring from the recovery (default, never replaced), from sd and adb (1.6 does install, 1.3 doesn't, and 1.6 partition upgrader doesn't either, gets aborted)…
Click to expand...
Click to collapse
Non unified images have a different signature. The moment you use the partition upgrader it will change the accepted signature and will no longer allow older images. If all is as I expected your running image is still the parition upgrader image and it contains the tools to perform the last step of the re-partitioning (e.g. calling the script and performing a recovery with format).
If you want to know what is going wrong with the zip install check the /cache/recovery direcotry. it will contain logs of the failing install.
As for a solutions I think you either need to run the script or flash your device using a 1.6 FUSE image.
_keesj said:
If you want to know what is going wrong with the zip install check the /cache/recovery direcotry. it will contain logs of the failing install.
As for a solutions I think you either need to run the script or flash your device using a 1.6 FUSE image.
Click to expand...
Click to collapse
I couldn't find any (log) files in /cache/recovery, but...
flashing the EBR1 from the FUSE binaries (FP1U) to my FP1 solved it! :victory:
thanks to _keesj, Rick (from Fairphone) and Christian (Fairphone forum)!
here is Rick's tutorial (with a few notes of my own):
You can only fix this by flashing your phone:
For GURU's only! (flashing with ADB). The alternative is to use the windows flasher tool.
1) Download the original image binaries from Fairphone's site (as a new user I, jjjanssen, can't post links yet).
(Download FP1U's zip: Fairphone_Cherry_1.6_FUSE_Image_2014-07-31.zip)
2) unzip the file
(I chose to unzip to location D:/FP1U.
after that i moved all content from the directory which contained EBR1, to D:/FP1U.)
3) enable usb debugging (on your phone: Settings, Developer options, turn USB debugging on)
4) push EBR1 on the phone: (Open (if you're using Windows) the Command Prompt)
adb push FP1U/EBR1 /mnt/sdcard/
(For instructions on how to use ADB search this site)
5) become root:
adb shell
(after that I also became super user (command su), but maybe that's not necessary; Rick didn't mention it. )
6) override the partition inforation:
dd if=/mnt/sdcard/EBR1 of=/dev/ebr1
7) reboot into recovery:
reboot recovery
8) choose to wipe data and cache
(after that, choose reboot)
Click to expand...
Click to collapse

Categories

Resources