For some reason I can't get my Polaris to run the latest Android version (i.e. Froyo).
1. Downloaded latest kernel (polaimg-panel3-320-froyo-07-07-10.nbh)
2. Downloaded last build (Incubus26Jc's Super FroYo RLS10)
3. Put last build (.tar or .tgz file) on SD card in directory /andboot
4. Flashed by using NBH file together with RUU Update Utility
Now it gets tricky:
a) or the system reboots, vibrates twice, I see a red and blue line and then a black screen and nothing;
b) or the system reboots, I get the Android installation menu after pressing middle button, install, but after soft reset I get a "No such file found" kind of system error
Can someone help me getting Android on my old Polaris? Thanks!
SnoopThaDoctor said:
For some reason I can't get my Polaris to run the latest Android version (i.e. Froyo).
1. Downloaded latest kernel (polaimg-panel3-320-froyo-07-07-10.nbh)
2. Downloaded last build (Incubus26Jc's Super FroYo RLS10)
3. Put last build (.tar or .tgz file) on SD card in directory /andboot
4. Flashed by using NBH file together with RUU Update Utility
Now it gets tricky:
a) or the system reboots, vibrates twice, I see a red and blue line and then a black screen and nothing;
b) or the system reboots, I get the Android installation menu after pressing middle button, install, but after soft reset I get a "No such file found" kind of system error
Can someone help me getting Android on my old Polaris? Thanks!
Click to expand...
Click to collapse
Same for me with polaimg-panel3-320, but it works great with polaimg-panel1-320-24-05-10.nbh
Thanks! Got it working with the older NBH file. Not completely flawless, but it works!
Don't use the old polaris panel 1 nbh, instead download the latest and then use this utility to change it to panel 1.
http://forum.xda-developers.com/showthread.php?t=689812
Thanks!!! Got it working with the latest NBH files! Great!!!
Hey, Could anybody unswer me on two questions.
1. why we have to change from panel3 to panel1 in this nbh file?
2. what is that mean panel3 or 1? why DZO do this type of the nbh (with panel3 i mean)?
thanks a lot, ithin it will helps not only me but everyone in future who didn't know about this modification
skydemon said:
Hey, Could anybody unswer me on two questions.
1. why we have to change from panel3 to panel1 in this nbh file?
2. what is that mean panel3 or 1? why DZO do this type of the nbh (with panel3 i mean)?
thanks a lot, ithin it will helps not only me but everyone in future who didn't know about this modification
Click to expand...
Click to collapse
The panel type depends on revision of your polaris, more specifically the make of the lcd panel, see here. I just tried every panel until I found one that works, I use panel 1.
Thanks a lot, but could you please answer me again. How i will know what kind of LCD panel in my Polaris and which number i should use?
these parameters is placed in my start-up file for the haret launcher
#alloctest 0x2000
set RAMSIZE 0x08000000
set MTYPE 1723
set KERNEL zImage
set initrd initrd.gz
set cmdline "board-htcpolaris.panel_type=1 pm.sleep_mode=1 mddi.width=240 mddi.height=320 no_console_suspend clock-7x00.mddi=0xa51 hw3d.version=1"
boot
can i use panel type from here?
i have opened this polaimg-panel3-320-froyo-07-07-10.nbh file in NBH editor and saw that the HW3D is set in Eclair. Should i change this to Froyo or left as is?
Thanks a lot for the conception)))
pannel type 1...
Did I brick my Polaris?
Well, it makes me laugh looking at the last post dated back July 2010 but I decide to post anyway because I feel somebody might have passed through my problems and might help.
Following indications on this forum:
1. I downloaded:
- Kernel: polaimg-panel3-240x320-2.6.32-froyo-09-09-10_21.nbh
- Last build: Incubus26Jc's Super FroYo RLS16 All Languages
2. Put last build (androidinstall.tgz) on SD card in directory /andboot
3. Used RUU Update Utility to flash the nbh file
Everything when smoothly. When it reboots, it vibrates, "Smart Mobility" message shows up, vibrates twice and then a blank screen is displayed.
Going through this forum I think I might have used the wrong type of panel and should have used Panel 1 instead of 3. So I downloaded Windows NBH Editor and managed to change the nbh into Panel 1. Then I shall try again.
This time my Windows 7 is unable to recognize my Polaris and all it can see is a new Disk Drive with no ADB device displayed. So I installed PdaNet302.exe to implement the USB driver for HTC Android Phone but it still cannot see my device and the process aborted.
What worries me is that one step of the process requested to change a setting on the Polaris (On your phone, click Settings > Applications > Development and make sure USB Debugging is on.). Obviously I can't do that as the screen is completely white!
I believe if I can manage to have my PC talking with my device then the problem will be fixed with the panel1-based flash. But every attempt to install the USB driver for Android Phone regularly fails on my PC.
All that time the Polaris remains with the lighted blank screen and there is no way to turn it off as the on/off switch refuses to work.
Shall I buy a new phone? Thanks for your help.
Did you try flashing the phone with a regular oficial HTC rom? just try it. Put the phone in the boot mode (press camera button and another one, dont recall which one) It will change to the tri color screen. Then connect it and try it.
Also there is a modified nbh rom which includes nothing, just the tool to recover your rom. Do a search to the forum.
I recently tried to install on my Polaris and it went really wrong. And finally could recover. The file is called ROMUpdateUtility_task29. I will erase everything on the phone but later you will be able to recover it
Form that point no more experiments. Polaris was made to work with Windows Mobile. It's really unstable, video camera is useless. And so on.
PC Carvalhon rom and I can use my phone as I want.
regards.
---------- Post added at 08:16 PM ---------- Previous post was at 07:57 PM ----------
With this you can recover your phone: http://forum.xda-developers.com/showpost.php?p=6227425&postcount=7160
A second life for my Polaris
Kafkacell,
1. Following your suggestions, I successfully started the bootloader (camera touch while reset), the 3-colour screen appeared, Windows 7 recognised the device. I then flashed the offcicial RUU_Polaris_HKCSL_WWE_3.19.831.3_radio_sign_25.85.30.07_1.59.42.15_Ship and everything successfully completed. With enormous pleasure I see again my Polaris back to activity. Thanks for giving my Polaris a second life.
2. Back to Feb 2009, I flashed a pcarvalho eXtreme ROM. I don't recall any longer the version of this ROM but it was very stable and never ever crashed. Recently I downloaded and flashed most recent ROMs. From that moment on, I have no peace. It crashed 2, 3 times a week. Now I wish I could go back to the old version but couldn't find it. Perhaps pcarvalho removed them to save space? May I ask you which pcarvalho eXtreme ROM version do you currently run. Thanks.
Im currently running 29022 version (latest update from PCCarvalho).
Notes:
UPDATE:
29022 is up
this is a fix release...sound issues should be gone...had to remove htc volume control is it still has issues...fixes minor gfx glitches...updated to lastest and probably final leak version of wm6.5.3 (29022)...will from now on work on unresolved issues and finalize rom...this will still take some time due to work...
updated physics engine and utask app by ultrashot...my thanks to him...
patched htc album to novsync, faster scrolling once cache is made...
removed no longer supported apps (my phone and marketplace)...if u need them install via cab...
Here is the link for the rom: http://forum.xda-developers.com/showpost.php?p=15707730&postcount=8079
it was posted on July of this year, and so far it runs great. The trick is to not install a lot of apps in your main memory. Do it on your SD card. Also a hard reset is a must to avoid all kind of problems.
regards and glad you have your phone back to life
Related
I have tried both Incubus26jc's Super Froyo (RLS8) and VaniljEclair RLS7c . I manage to install them in sd card (I want to use them via haret.exe) but when I reach the welcome screen where I have to touch the android to continue, the screen does not respond ( D-pad and center button work). Could someone help me? I decided to open a new thread because of what I have searched, I found only one member with a similar (but not the same) problem
The installation method I follow is this (mostly copied from a SuperJMN's post):
1º Run HaRET
2º From the installer, select Install System
3º Choose install update (if any)
4º Choose to fix permissions (if there had been an update)
5º Reset (don't select "Quit", just reset, this is to avoid problems)
6º Wait for Windows Mobile to start and run HaRET again.
Although I am flashing to nand and you are using haret/zimage, we may have the same problem with the unified touch screen driver that DZO implemented around 16 June. Is there is a way to use the kernel .nbh and system .tar with haret, rather than zimage? If so, you might try using an older kernel from before 16 June ... or perhaps an older zimage.
I have similar problem, if not the exactly the same. Using an older kernel seems to be a workaround of this problem. hxxp://forum.xda-developers.com/showpost.php?p=7041656&postcount=21 (You need to fix the hxxp as appropriate as I am not allowed to link URL yet)
i have the similar problem too, havent fixed it :/
I tried zImage-12-06-10 (the last one before the 16th of June) and installation procedure did not even start. But zImage-29-04-10 worked for me. However, Froyo is not that fast. If I change any files (zImage or something else) is it possible to have a speed improvement?
Same problems.
All Android realeases work on my pola100 only with zImage 29.04.10.
No work with other kernel.
I suggest to developers to analyse 29.04.10 and try to understand WHY this works and others no.
Regards.
regarding screen response, panel and changes on kernel module for touchscreen please see this post from dzo
also check this for solution from k_k
HTH
mensa07 said:
regarding screen response, panel and changes on kernel module for touchscreen please see this post from dzo
Click to expand...
Click to collapse
Those are the changes after which my touchscreen stopped working.
mensa07 said:
also check this for solution from k_k
Click to expand...
Click to collapse
It would be nice if this worked for the Polaris ... how would I change the value of this parameter before flashing the kernel? Thanks!
tmcfarland said:
Those are the changes after which my touchscreen stopped working.
It would be nice if this worked for the Polaris ... how would I change the value of this parameter before flashing the kernel? Thanks!
Click to expand...
Click to collapse
you can use terminal or adb to change the value
files for a fast android version
Could someone with a fast and stable version of eclair or froyo please tell us what files did he/she used to make that happen because I installed incubus froyo build and it is a bit slow? I am talking about installing it in my sd card and run it using haret.exe
TO ALL PEOPLE:
PLEASE STOP POSTING IN THIS TOPIC ABOUT "THIS PART DOESN'T WORK ECC ECC" WRITE IN THE TOPIC OF THE RELEASE (KERNEL OR SYSTEM), PLEASE LOOK IN THIS THREAD FOR WORKING SETUPS AND TRICKS, AND SEARCH ON THE FORUM BEFORE POSTING!
I start with thread with a information for all users:
Haret system sucks so if you want a full working android system left windows behind you and move to the new android world flash on nand.
With this how-to you will not erase any part of your system but you do at your own risk.
Main problem: screen
For polaris there are 3 type of screen. Usually pola100 (the old one) use panel 1, and pola 200 (09 edition) has panel 3 but ... not always works...
The best mode to test is try to install and after double reboot you have black screen change panel type.
What you need:
phone
sd card (1 Gb or more) 500 mb free
time
Update guide: http://sourceforge.net/apps/trac/androidhtc/wiki/HowToInstallWithAtoolsHaret
reserved by me
Do we have to delete/remove the install-seq.sh after installation?
Are both files (system & data) cleared with the installation script?
Thanks for the help.
install-seq.sh disable automatically after correct install.
This how-to is fir first install on disk on images so it format both data an system.
If you want to make only un update use bsg select partion and select update.
partition
I believe you should make this sticky
Don't post without reading!!!!
This method doesn't use sd partition, it create two imagedisk on sd!
working android
l1q1d said:
Don't post without reading!!!!
This method doesn't use sd partition, it create two imagedisk on sd!
Click to expand...
Click to collapse
hi there,
i made all you told here, booting..after more minutes...the logo appears...but when i press the android logo from the screen.. the touch screen dosent work..i can not start..only with buttons..and after pressing buttons..get over wizard..the phone need SIM PIN..but i can not typed.
please help
i changed BORAD PANEL in 1,2,3 and in 2,3 is black screen.
please help me
You have to disable pin code before installing.
For the screen problem look in kernel thread...
waiting for not busy
What about "waiting for not busy" - im2c error ?
The only Zimage working for my pola100 it's an old 29-04-10 Version !
I am very disperate!
Bye !
touch screen dosent work
foxct2005 said:
What about "waiting for not busy" - im2c error ?
The only Zimage working for my pola100 it's an old 29-04-10 Version !
I am very disperate!
Bye !
Click to expand...
Click to collapse
Dear All,
i tried and deactivate the PIN of sim card..read all posts from previous thread that you gave me..but nothing..
all ok..
bootin..starting..apears the logo and final...
before i need to press the screen, appears a message ''Android system stop responding..and a button FINISH"...after pressing finish, i need to press the middle of the screen on the android logo and nothing, only 2 buttons Emergency Call and Choose Language. to can press these 2 buttons, i use the buttons and i can press them..but touch screen do not working.
please all of you..the masters of this softwares..give me a solution.
thx
Try to reinstall the system...
(rename /andboot/install-seq-disabled.sh to /andboot/install-seq.sh and boot)
touch screen problem
l1q1d said:
Try to reinstall the system...
(rename /andboot/install-seq-disabled.sh to /andboot/install-seq.sh and boot)
Click to expand...
Click to collapse
hi there..
i solved the problem..i took an older Z image..and working fine
the problem is that more applications like camera..media player screen adjust don't work..
they try to run..(i mean ..in camera..i can see..but appears a messages with stop working..sorry). i don't know why..
nothing work well
and what about the contacts..how can i get them from my Sim card?
i don't know..
if you can help me will be great.
thx allot for yours assistance.
best regards.
The information from sim card are very limitated (neither pin code works) so if you want to export contact sync before starting with google and configur your google account on android.
old zimage are full of bugs and all developers install android on nand so starting android from haret has many unfixed bugs.
I've been playing around with the haret install for a week or so now, and I've found that, for me at least, it makes a huge difference which initrd.gz file I use.
The one dated 22-05-10 doesn't let me install any zImages newer than 29-04-10. After trying all sorts of combinations of base files with different dates (haret, zImage) and additions to the default.txt, changing the initrd.gz file to the one dated 20-02-10 fixed most of my problems and lets me install the most recent zImage files without a glitch.
No clue why, just that it works.
I'm running a Pola100 with the original WM6.0 ROM still on it, and radio version 1.58.25.14. Yeah, I need to upgrade to at least the official WM6.1 ROM and probably something better. But I'm a newbie at this, so I need to work up some courage first ;-)
hello,
I tried to install android on sd following your instructions, everything seems to go well until the screen where it says:
"Welcome to htc vogue Frøya
touch the android to begin "
I'll try, but the touch does not work, I tried using the d-pad, which does work, but I can only select the language and the emergency call.
zImage as I used: zImage-Frøya-15-07-10
androidinstall.tar as I used: Incubus26Jc's Super Frøya RLS11 Themed
please help me because I would switch to Android!
thanks
Try with latest kernel version on kernel (i release it yesterday)
l1q1d said:
Try with latest kernel versin on kernel (i release it yesterday)
Click to expand...
Click to collapse
where can I find it?
thanks
I tried it unsuccessfully. Boot starts regulary, always ending on repeating error, looping forever.
I can read something like:
==============
ERROR no local apt for prog ... replying anyway
...
Setting function 4 for gpio ... that I don't own
==============
Is it related to which system file ? Loader? Kernel ? Or what ?
Thanks
What did you use for your installation?
I used the files mentioned at the very beginning of this post.
Regarding zimage: zimage-24-05-10
Hey guys,
I just downloaded the following Android Build for my HTC Diamond 2 (Topaz):
Package date: March 25th 2011
Build Froyo 2.2.2
Bundle package FRX06 Final NEW:
With the first boot it seems to have gotten stuck at a particular point in the run. I'm gonna try to retype the info on the screen and if anyone can give me an idea of how to fix this problem...
Thank you
(There is more than this, but seems to be of a repetetive sort. Please let me know if there)
INFO: task rpcprouter: 15 blocked for more than 120 seconds
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message
mdp irg already on 4 4
mdp_mda: busy
Hello!
I have the same problem with the release March 25th 2011 2.2.2 FRX06 Final bundle from http://forum.xda-developers.com/showthread.php?t=509493 on a HTC Topaz.
I have tried several kernels from glemsom and formatted my SD with Panasonic SD Format 2.0 to no avail.
Edit:
Fixed - I downloaded a ts-calibration file for Topaz from http://forum.xda-developers.com/showthread.php?t=951962 and now that error dissapeared and I can reach the "Insert PIN panel".
Edit 2:
The "ts-calibration" from the above thread behaves in mirror-like fashion.In portrait mode when I touch the left side it clicks on the right side.I made a custom ts-calibration using data from SPL.
http://forum.xda-developers.com/showpost.php?p=10807361&postcount=515
http://forum.xda-developers.com/showpost.php?p=10817104&postcount=529
Thanks for the reply edward-andrew,
It's been a while since I posted this topic and haven't really tried fixing the problem yet. Also I'm very new to development and OS installations on cell phones. Was wondering if I could get the ts-calibration file from you and if you could inform me how to go about fixing the problem...
Also, since that first run whenever I've tried to run haret I get an error...
'The file 'HARET' cannot be opened. Either it is not signed with a trusted...'
I have deleted all the files from that build from the memory card and recopied it onto the memory card, but still get the same message. Is there some log file on the phone I have to edit?
Thank you
Like i've posted in the setup thread from Liquid, this setup is the best i've tried until now, the only one that make missing call an old history in fact
Another better than ever pola 100 nand / nand setup
Download rom (5.5 version - 6 doesn't work with polaris kernel) : Scoot CyanogenMod (RLS5.5) [16.03.2011] and put it on your sdcard in a directory named andboot (at the root level)
with atool download the latest 2.6.32 kernel, modify it as desired
flash your unlocked phone following this tutorial or use atool scripting ability
update needed : none
work : everything except camera !!!! very smooth and very reliable(no missed call for 1 week, that's a revolution) and not so bad battery life
finally, development kernel seems to be not so far from "ready to production" status, with even better nand stability
we're waiting rom update and next krazykilla's kernel with polaris support, for a better stability and ability tu put data on ext4 partition
Thank you to scooter, liquid nr2jt and all androidhtccrew for their tuff work
Nand is not perfect and run corruption sometime that crash your setup : use the nand startup "backup/restore" data ability after you have configured your rom and favorite applications, to avoid loss of everything : it will create a 256Mb image of nand memory in your SD card /andboot directory that you can restore later in case of crash.
you can increment this backup later if you are happy with future modification of your rom
TIPS : noticed that setup as it is is good enough, people at cyanogenmod know their business
- Tip 1 : in atool, you can try to increase advanced battery capacity to improve accuracy because N2jrt has noticed battery calculation is not good and there's a correction factor of 1.6 to apply (i put 1900 but you can increase to 2200 in theory)
- Tip 2 : you can download Roguetool from the market to overclock your phone
- Tip 3 : try the app named killerauto from the market, it does a very good job with very comprehensive settings to free your ram in real time (and increase battery life)
- Tip 4 : In cynogenmod parameters/performance : check the "keep home in memory option" and activate compcache (10%) to get better result - i don't activate JIT
- Tip 5 : i've noticed that's the battery widget is cause of some trouble sometime, you can get rid of it in this case
what's next
- make polaris' atool development kernel compatible with release 6 : thx to scooter and liquid by advance
- Make crazykilla kernel with ext4 support available for polaris (release from his #54 thread doesn't work for me) or maybe unified every kernel to get the best one
crazykilla's kernel is a usual kernel without the polaris support compiled, i don't know why the #54 version don't work and i can't test it anymore (my polaris has a toasted nand).
l1q1d said:
crazykilla's kernel is a usual kernel without the polaris support compiled, i don't know why the #54 version don't work and i can't test it anymore (my polaris has a toasted nand).
Click to expand...
Click to collapse
i get the error message
"install module for this kernel
apply modules/androidupdate.tgz
Failed
from sourceforge"
maybe i missed something
Blinking screen
I've tried it with my XDA Orbit II and all I get is the white blinking screen after running haret. It's written in the man that it takes a lot of time, so I left it and went to sleep When I woke up, the screen was still blinking the same way and had to remove the battery to reboot. WM booted fine, there were files system.img and data.img created on the microsdcard of the size of 300mb (I don't want to flash it on NAND as it is my first attempt to install new software on phone). I tried Froyo, now trying Eclair and after an hour it looks the same. What might be wrong? Should I try stable kernel or other setups?
Krysiul said:
I've tried it with my XDA Orbit II and all I get is the white blinking screen after running haret. It's written in the man that it takes a lot of time, so I left it and went to sleep When I woke up, the screen was still blinking the same way and had to remove the battery to reboot. WM booted fine, there were files system.img and data.img created on the microsdcard of the size of 300mb (I don't want to flash it on NAND as it is my first attempt to install new software on phone). I tried Froyo, now trying Eclair and after an hour it looks the same. What might be wrong? Should I try stable kernel or other setups?
Click to expand...
Click to collapse
i don't know such setup sorry, i work on nand only to get real speed
I don't want to try flashing on NAND until I find a setup that would satisfy me and work well as I would in practice lose the phone for some time while trying to make it work. So far I've succesfully installed this, but I can't make the PIN code work. I tried to disable it in WM in phone settings, but when I do it, it requires me to enter the PIN, and doesn't accept it, just as Android does :/ Does the PIN code problem occurs in NAND installation as well?
this setup is really not ready. i tried so many times and it always hangs and at the end you'd be reinstalling the system back. I'm sticking back to the Not-So-Super-Froyo setup and has since found it to be very very stable although no camera and no GPS working on it. Just a bit of tip to all those who try and occasionally reinstall, after you have found a good stable setup, install your basic favorite apps and games, then get reboot the phone, access the Android Boot Menu and choose Backup Data on the choices. The system will save your stable setup on an image file on your sdcard. So anytime you have a system crash, you can just choose to Restore Data from the Boot Menu. Saves you a lot of installation.
arzakem said:
this setup is really not ready. i tried so many times and it always hangs and at the end you'd be reinstalling the system back. I'm sticking back to the Not-So-Super-Froyo setup and has since found it to be very very stable although no camera and no GPS working on it. Just a bit of tip to all those who try and occasionally reinstall, after you have found a good stable setup, install your basic favorite apps and games, then get reboot the phone, access the Android Boot Menu and choose Backup Data on the choices. The system will save your stable setup on an image file on your sdcard. So anytime you have a system crash, you can just choose to Restore Data from the Boot Menu. Saves you a lot of installation.
Click to expand...
Click to collapse
Yes i've read this technique somewhere, maybe i will try it next time
thank you for the tip anyway
Krysiul said:
I don't want to try flashing on NAND until I find a setup that would satisfy me and work well as I would in practice lose the phone for some time while trying to make it work. So far I've succesfully installed this, but I can't make the PIN code work. I tried to disable it in WM in phone settings, but when I do it, it requires me to enter the PIN, and doesn't accept it, just as Android does :/ Does the PIN code problem occurs in NAND installation as well?
Click to expand...
Click to collapse
yes if i remember well my past haret experience, i had to deactivate PIN in WM to make android work
arzakem said:
although no camera.
Click to expand...
Click to collapse
what kernel do you use ? i use liquid's 2.6.25 + kernel update
I finally follow your advise and came back to "not so super" and begin to use the "backup data" function...
The best setup so far
I've tried deactivating in WM, but that doesn't work as I've written above. I also tried to disable PIN using my friend's LG AT&T and it didn't work either so I guess I have to try some PC software or go to my service provider and ask them to do it. Thanks for replies.
chourmovs said:
what kernel do you use ? i use liquid's 2.6.25 + kernel update
I finally follow your advise and came back to "not so super" and begin to use the "backup data" function...
The best setup so far
Click to expand...
Click to collapse
lol i've read about the 2.6.25 working camera several times yet i chose to follow the blunt idea that "everything current is best ever" setup.
Anyway ill follow your advise now hehe and finally will have a working camera back again. anyway we have a backup hehe. Thanks man!!!
by the way, i liked your post title a lot haha.
arzakem said:
anyway we have a backup hehe.
Click to expand...
Click to collapse
yeah that's why i try other roms today (i'm in a rom rush ) to see if situation is better with backup trick
i saw the great nr2jt say in a topic that he save is data every morning to prevent its loss
that's why i give another try with scoot 5.5 with liquid's 2.6.32
Hey liquid do something for us to use 6 release
post 1 updated
After numerous builds+kernels, loads of frustration (and the inevitable revert to wm for a while) I think I like this setup. Simplicity at its best, Scoot CyanogenMod (RLS5.5) and latest 2.6.32 from atools as per 1st post. Just re-purposed the camera button as 'home'. Even my headset works, albeit intermittently.
Which settings for ATools for pola200?
Hi,
i tried to install this rom on my german pola200. But on the Linux Bootscreen the text is scrolling down and sayes that it installs the rom. But than it scrolls down error messages.
I tried this for houres but it shows no final error or something. The Text is scrolling on and on.
So i think that i used the wrong settings in atool. I used this tutorial to set up atool: http://sourceforge.net/apps/trac/androidhtc/wiki/HowToInstallWithAtoolsNand
What settings should been used?:
- What version to select?: Donut, Eclair or Froyo?
- Best settings for sd-card-partition? I used first partition 3 gb fat32, second partition 1 gb ext2.
- where should i install system and data? Both on second sd-partition? Or should there be a third partition? (the first time i tried to install the system on intern memory but install runs out of space)
Can you please explain the right settings in atool?
best version is froyo.
to choose sd-card partition, you must have your sdcard PREPARED beforehand. Atool does not partition your sdcard for you. As of what to use to partition your sdcard you can search it at google. (im sorry im a little bit short on time now). choose NAND on both system and DATA.
atools has sd partioner inside so you can repart sd card (boot script editor Y), but the sdcard must have only one partition on it (fat32).
i stand corrected thanks l1qu1d.
This thread is for the custom Froyo rom for the Flytouch 2. It is a port of the first Flytouch 3/Superpad 2 Froyo rom, adapted to run on the flytouch 2. I will update this post whenever a new version has been released.
This rom will only run on tablets which display a version number in the bottom-right "Infotmic" screen when first turned on.. If yours doesn't display a number there, you will need to flash firmware v2852 first, see below in FLASHING V2852
INSTALLATION
Installation is slightly different from normal releases because it requires flashing in 2 steps. Luckily, it's really easy:
1. Download bootable SD-card image and unzip. Pick an image from the RELEASES section at the end of this post.
2. Write image to an SD-card that's at least 1GB in size using Win32DiskImager:
Get Win32DiskImager here: https://launchpad.net/win32-image-writer
In Win32DiskImager: When you open it, there is a button to browse the .img file and after that, at the right of this button there is a selector for the SD-card. Select it, then click write and it's done.
When finished, take out the card.
In linux, you just unzip the file and use dd to write it to the sd-card:
Code:
dd if=/path/to/sdcard.img of=/dev/sdX # (where sdX is your scsi disk device, check dmesg)
3. Turn off tablet and put sd-card in TOP slot (between the 2 usb ports).
4. Turn on tablet. It will report that it is booting off the sd-card, and that it's flashing kernel + filesystems.
5. Take out the sd-card when the tablet asks you to do so (takes less than a minute). Put it in the OTHER sd-card slot (bottom one), and reboot the tablet by holding down the power for 10 seconds to turn it off, then press it again to turn it on.
6. You will now see the tablet booting with a *GREEN* screen. The screen will flash twice to indicate it's starting. The flashing itself will take longer than in the previous step, a few minutes. If succesful, it will automatically reboot, after which you're done and you're booting the new firmware! You'll see a different boot screen (equalizer on a black background)
7. After it has booted and you have unlocked the screen, reboot the tablet first thing! First boots in android always tend to be behave erratically. This is unrelated to this firmware and applies to all Android setups.
If step 6 fails (which is very unlikely), it will stay on the green screen and it will keep on flashing the screen. In that case, you'll have to turn it off. Most likely problem for this is a corrupt SD-card. See troubleshooting below.
Make sure to never put that sd-card back in the top-slot without erasing it first, as it will reflash your tablet!
TROUBLESHOOTING
The 'green screen' keeps flashing!
The installer will dump a text file on the root of the sd-card which you can inspect. The file is called fail_reason.txt. If no such file exists, things are seriously wrong and the tablet couldn't even properly write to the sd-card. If using another SD-card, or rewriting the SD-card doesn't help, please upload the fail_reason.txt file here.
Flashing was succesful, but the system freezes at the android animation!
For this firmware to work, you need to have a recent version of u-boot. You can tell if you have this by looking at the INFOTMIC bootscreen you see when you turn on the tablet. If the bottom right corner does not show a version number, then you don't have it.See instructions below.
FLASHING V2852
You need to flash this firmware to install a new version of u-boot. To flash this firmware, you will need to connect your tablet to your PC using an USB A-A cable, OR create a bootable SD-card.
Download firmware V2852: http://www.mediafire.com/download.php?3bkklw36b1414nd
Download and unpack IUW: http://www.mediafire.com/download.php?3572bd7zfjo0r0y
Start IUW
If you use an USB cable: Click 'Link USB' on the left, select 'easy burn' from USB Mode pulldown in the right. Connect tablet to PC with the tablet turned offf, then turn it on by pressing & holding the menu+home buttons, then pressing the power button until it turns on. Release the menu+home buttons after a few seconds. Windows should now detect a new USB device. Install the drivers that are in the iuw1.1/otg_driver directory.
If you create a bootable SD-card, Click 'boot disk' on the left instead. Select sd-card to flash on the right
Select the IUS file form the v2852 firmware under 'Choose a wrapped image'
Click 'burn' to flash the tablet or create the sd-card. If you created an sd-card, boot the tablet with the sd-card in the top-slot, between the 2 USB connections.
TODO
How to enable 3G support for USB dongles?
(**) Tested:
wifi, ethernet port
battery status works, g-sensor works
touchscreen works, including calibration
HD video playback works (I recommend Meridian player)
Market works (full), Youtube works
angry birds works ( thought I'd mention it )
The firmware has already been rooted! You can connect using adb over wifi, and type 'su' to become root. Find your IP address using the Android System Info app.
GPS confirmed
VIDEO
Video demonstrating how to flash the tablet after having created the bootable SD-card: http://www.youtube.com/watch?v=47kf4-Vbba8#t=3
RELEASES
April 24th 2011, V5: http://www.mediafire.com/?1ka7ngpi82grmfm
Added older version of YouTube (1.6.21) which works
Fix touchscreen calibration
Added LauncherPro as alternative launcher
March 2011, V4: http://www.mediafire.com/?oc1bwnq71smb09k
verandi said:
Hi everyone.
I just made a personal version of system.tar.gz, and I thought it could be usefull for someone.
Most considerable changes:
Calendar and contacts synchronization now working again.
Simple stock froyo keyboard, without chinese characters.
Replaced youtube with the old working version.
Market updated to last version (no paid apps, though.).
Default launcher replaced with launcher pro, which is considerably faster.
Removed phone and telephony settings (see below)
Other changes:
Removed stock browser, replaced with dolphin browser HD.
Removed default file explorer, replaced with File expert (first free file explorer with working root that I found).
Changed alarm clock.
Changed calculator (but has wrong visualization).
Changed music player with music mod.
Added facebook, maps (+ navigation + latitude +places), chrome to phone, google search, google reader, terminal emulator, Titanium backup, voice search. adobe reader.
Maybe I deleted some other stupid flytouch stock apps, but actually I don't remember.
Warning, notes etc...:
All apps are free apps from market.
Phone apps (Phone.apk, TelephonySettings.apk) removed for test, due to suspected battery drain (Someone said so...), so:
Phone settings don't work (gives you force close when you tap on mobile settings menu)
Don't install if you use 3g adapters, as I think you won't be able to use them.
Maybe some future workarounds for paid apps on market won't work.
App2sd doesn't work. (Didn't even work before. I think there's some problem in the kernel with device mapper and crypto). I'll try to implement the fake app2sd that uses an ext partition on sd.
This is just a personal versionof stargulus' system files with apps I'm used to have on my phone, so maybe it won't fit you.
How to install:
First important step: boot in recovery mode (back + home +power until you get in recovery menu), and wipe cache and data. This must be done. It also helps to have stragulus' calibration file installed correctly.
Prepare the sd as described in the first post of this thread using the last Stragulus' sdcard image (v4, See link in this post).
Go to "stage2" directory and replace system.tar.gz and system.tar.gz.md5 with the downloaded ones.
Flash.
The first boot will be quite long, but it's normal.
While using the flytouch for the first time, it will probably lag and hang. Just reboot and it won't happen anymore.
File link: http://www.multiupload.com/Z9CONJVPQO
I hope this will be usefull. Advices are welcome.
Click to expand...
Click to collapse
Cheers! I welcome custom mods of the base rom. I'm willing to add them as alternatives to the first post by linking to the introductory posts. In this case, it looks like parts of it are suitable for integrating into the base froyo rom (e.g. calendar & contact sync fix). What exactly did you do to fix those?
Wonderful, downloading now at 7.8K/sec (why sooooo slow?)
Is Google Sync fixed?
Thanks,
Barak
Later:
Well, if I add Verandi's MOD I get sync but I loose calibration option.
Still, I prefer the MOD with sync.
Thank you guys. Amazing Job !!!
1-5-2011
Please note that verandi has created a V5 mod that adds sync option without eliminating calibration.
http://forum.xda-developers.com/showpost.php?p=13343444&postcount=54
Good luck.
Your uboot - 0.6.1.2 (587) http://www.mediafire.com/?4hx8xt38vnhh22b
My uboot - 0.6.1.5 (587) http://www.mediafire.com/?bv4ixzeq34q5bi7
what's the latest?
which should I use?
EDIT:
If possible enable a swap partition to optimize tablet in ROM? (we have little RAM)
Camera have a problem. Green image in V5 (24/04/2011)
@ Stragulus
I've been waiting for
Thank you for your work
Market will not dowload
Well once again my hats off to you Straguls for a job well done I installed the version 5 rom with no issues however the Android Market still only displays the free apps and will not download and install any of the apps it states download unsuccessful any help with this matter would be greatly appreciated.
Thanks
Steve
stragulus said:
This rom will only run on tablets which display a version number in the bottom-right "Infotmic" screen when first turned on.
Click to expand...
Click to collapse
In my case loader version number is missing. But u0 is 0.6.1.2_1.4.587_OV2655 and u-boot from 2852. And all work fine.
Probably condition is flashing firmware 2852 in the tablet instead of only u0?
IMHO.
Because the firmware is full image and contained u-boot and u0. Flashing u0 need only if camera don't work with 2852 from full image. Of course, if the tablet has not been purchased already with firmware 2852 and above. Without this step you will get many reports of "fre-e-e-ezing" or "stop in android on screen" like in the previous thread.
hello
I have stitched from card Froyo V5
The tablet is loaded and asks calibration, but it does not work: (
Was 3245, but it has ceased to be loaded and I have updated on Froyo
I do not know what at me uboot how it to look? Probably to update it with sd?
jp08 said:
загружатся
Click to expand...
Click to collapse
По русски спроси. Я tuzzz c форума china-iphone.ru.
Ask question in Russian. I tuzzz from the forum china-iphone.ru.
Вообщем поставил Froyo (v5)
после прошивки при первом запуске появляется калибровка экрана, но на нажатия никак не реагирует
поставил назад 3245, на ней все нормально
Возможно ли это из-за загрузчика uboot, как можно посмотреть его версию и возможно ли обновить его с SD, т.к. возможности с ПК нету?
google translate:
In general set Froyo (v5)
after flashing at the first startup, a calibration screen, but clicking does not react
put back 3245, her everything is ok
Is this possible because of the boot uboot, as you can see its version and whether it is possible to update it with SD, because capabilities with a PC no?
Answer on russian forum.
Also read from here and below.
_barsuk_ said:
In my case loader version number is missing. But u0 is 0.6.1.2_1.4.587_OV2655 and u-boot from 2852. And all work fine.
Probably condition is flashing firmware 2852 in the tablet instead of only u0?
IMHO.
Because the firmware is full image and contained u-boot and u0. Flashing u0 need only if camera don't work with 2852 from full image. Of course, if the tablet has not been purchased already with firmware 2852 and above. Without this step you will get many reports of "fre-e-e-ezing" or "stop in android on screen" like in the previous thread.
Click to expand...
Click to collapse
That could be true indeed! I thought those who fixed their problem only flashed U0, but maybe all of them actually tried to flash all of v2852 with the IUW tool. Upshot here is that it should be possible to flash the entire firmware using a bootable SD-card, e.g. not requiring an USB cable.
Can anyone confirm that creating the bootable SD-card for FW2852 using IUW as described in the first post fixed their install of the froyo setup?
If you create a bootable SD-card, Click 'boot disk' on the left instead. Select sd-card to flash on the right
Select the IUS file form the v2852 firmware under 'Choose a wrapped image'
Click to expand...
Click to collapse
After Burn a card sd the empty
This way does not work
Used Win7 x64 and virtual WinXP x86
Excellent Work
Many thanks stragulus!!!!!!!
Now I once again have a usable Pad - the Calibration works perfecly!!!
My route to Froyo was from 3245 to v4. I HAD to flash U-Boot-Nand FIRST. This gave me the Infotm code in the bottom R.H.corner. The only problem was with the calibration.
Again MANY THANKS. Please continue to develop for the Pad.
jp08 said:
After Burn a card sd the empty
This way does not work
Used Win7 x64 and virtual WinXP x86
Click to expand...
Click to collapse
Hmm. I do now recall that someone tried all those methods before to no avail. When I flashed this firmware, I think I did:
* Flash all of FW2852 (over USB)
* Found out that it didn't work 100% as it still booted an older ramdisk
* So after that, flashed U0 with u-boot-nand.bin. That triggered the 2-minute tablet going crazy on first boot.
* Then flashed all of FW2852 again, and now it worked.
Soo.. I think bottomline is, if you haven't seen the tablet go crazy for 2 minutes, it probably didn't work. Question is, is just flashing U0 once with u-boot-nand.bin enough..? It appears this does not work for everyone!?
stragulus said:
Cheers! I welcome custom mods of the base rom. I'm willing to add them as alternatives to the first post by linking to the introductory posts. In this case, it looks like parts of it are suitable for integrating into the base froyo rom (e.g. calendar & contact sync fix). What exactly did you do to fix those?
Click to expand...
Click to collapse
Hi!
I replaced GoogleContactsSyncAdapter.apk and GoogleCalendarSyncadapter.apk with the ones from my phone. I am 98% sure I replaced only these two, because I didn't note down the names.
Now I'm trying to solve the next problem I have in the list: I can't leave the pad in standby, as it drains the battery like it was awake.
Yesterday I had a look at proc/wakelocks file to see which processes are requesting wakelocks.
Comparing this file to others around the net and the one of my phone, I found out that some processes were active during standby (they had 0 value in sleep_time row).
Now I haven't here my flytouch, so I can't be precise (I'll edit this lines next days), but I remember that some processes and powermanager were never sleeping (in all other wakelocks files, powemanager was sleeping on standby but main process not, so I think powermanager is faulty and main process not.).
Powermanager is a class contained in system/framework/services.jar so I tried replacing this file with my phone's one. It worked as the wakelocks file was showing that powermanager began to sleep on standby, but I had no improvement in battery life on standby, as, I'm quite sure, the other processes prevent the full sleep of the device.
To you and everyone who reads this: can you give me a help?
Can you fully recharge the flytouch, then disconnect the power supply, note down the start time, live it in sleep mode and then measure how long it takes to get discharged?
It tried myself today: unplugged at 16.30, left it in standby, died at around 19:20 ---> 2h50m of battery power on standby.
(If you also can tell me how long it stays on when you use it, and what kind of use you made, I would really appreciate too! )
Hail to Stragulus.. unlocking the beast!!!!
stragulus,
as usual.. I am riding on someone else's brilliance.. thanks for the update..
Will load it up tonight when get home from work..
My only wish is app2sd...
it has made such an improvement to my Evo with ability to load programs in..
So if someone wants to come up with a fix.. I am sure you will make many internally grateful!!!!
Edit after flashing:
Flashed the clean version WITHOUT verandi addons..
the Calibration works perfectly
feels fast and clean..
had problems with launcher pro .. and Titanium backup..
for some reason using Launcher pro it would not allow Titanium to see the sdcard.. thus couldnt restore my backups..
Played round for a while.. upgraded to Titanium 3.6.1.1 same thing..
went in and wiped Dalvik cache.. still no go..
have shut down launcher pro and installed ADWlauncher (almost the same as launcher pro)
walla.. now Titanium is seeing the SDcards and backup.. confirmed that it restored backed programs and data..
Market is working for me.. just wondering if we can port market from Myn’s Warm TwoPointTwo - RLS 5 into this rom..
as this may be the workaround that will get past the only free apps showing.. I am using it on my Evo and in China..
so usually only get to see free apps.. but with MWTPT I am getting all apps.. I do understand there is a app floating round that is suppose to be able to reset Market in to thinking it is in a zone that will allow it to show all apps.. may need it to load in to this Rom..
Will put it through its paces and report back over the coming week..
verandi said:
It tried myself today: unplugged at 16.30, left it in standby, died at around 19:20 ---> 2h50m of battery power on standby.
(If you also can tell me how long it stays on when you use it, and what kind of use you made, I would really appreciate too! )
Click to expand...
Click to collapse
Hmmm. This time is extremely low for standby mode. I use kernel from 3245. With this kernel battery indicator won't work properly but OS works more stable.
Also I removed Phone.apk and TelephonyProvider.apk. I don't need 3g modem. And 3g modem still does not work with this firmware.
With full charged battery I disconnected charger from tablet at 22:00 (in my local time). Now is 5:25 in my local time and tablet has ~4% battery indicator. From my experience tablet shut down after 5-10 minutes. All this time tablet is in standby.
Verandi
Excellent work and thank you for the Google sync fix - it makes my wowpad WOW!!!
Can you please add these files to the V5 version? Without them there's no sync. If I add your V4 files to the V5 rom there's no calibration. I wonder what else is lost !!!
Thanks,
B
stragulus said:
Cheers! I welcome custom mods of the base rom. I'm willing to add them as alternatives to the first post by linking to the introductory posts. In this case, it looks like parts of it are suitable for integrating into the base froyo rom (e.g. calendar & contact sync fix). What exactly did you do to fix those?
Click to expand...
Click to collapse
Great job. Thank you about that. I've a little question.
I've updated my Flytouch with you sdcard V5. Everything works fine, but i can't get the connection with USB 3G dongle. How i can do ?
There's a program to get the connections ?
I've tried with "quick setting" but nothing happens.
I'm looking forward to hearing from you about that.
Best regards