yashsingh1/xdaforums huggingface dataset:
[Touch Pro2, Tilt 2 Android Development] codedesignr:
You may have already tried, but hold only the volume down button while you do a soft reset with the stylus.
[Touch Pro2, Tilt 2 Android Development] mcnutty:
Can you both please make sure you are on the 12-15 rootfs? I had a permissions issue with the 12-14 one. Something wonky happened to it when it got uploaded to Dropbox as if the whole file didn't finish uploading. I rebuilt it as the 12-15 that is linked in the first post.
[Touch Pro2, Tilt 2 Android Development] SurfGuruJeff:
That's what I used.
[Touch Pro2, Tilt 2 Android Development] SurfGuruJeff:
I noticed that when it gets to screen calibration it immediately jumps ahead... isn't it supposed to wait until I touch the 5 points to calibrate it?
[Touch Pro2, Tilt 2 Android Development] MobileMini:
Thanks for your reply. I am pretty sure Android should work on the Mini, since there are Aria Android roms available. The HD Mini and Aria don't differ very much, they have pretty much the same hardware (except, trackpad and screen colors). So if this Nand boot utility does work on the Mini, I think there should be a change to make the Aria Android rom work on the Mini. Or am I completely missing something now...?
[Touch Pro2, Tilt 2 Android Development] helicopter88:
I have a diamond,and i'm really sad that this is for rhod only

Since we have all msm7xxxxx and we can run the same android rom without too much problems,would this nbh work on diamond?
[Touch Pro2, Tilt 2 Android Development] Bieka:
Hey,

i now tried a hell of options to get android running on NAND. But NO way. If some has a Rhod100 no matter if DE, IT, UK or anything else, please contact me or reply on this post how you get your NAND running and what files you installed to get it running.

I tried all that was posted here and on PPCgeeks but no way to get it running. I saw after one boot android made the data.img, an cache folder and some files (one was corrupted) i made a task29 and flashed many times now, also formated the SD Card with windows and HP Tool many times but also no better result. I must do something wrong but i don't get WHATS Wrong.

Best Regards
[Touch Pro2, Tilt 2 Android Development] Thordim:
Well it is hard to answer your question without knowing what steps you did or what error you have received. where does it fail/stop. is it just you are impatient and after 5 mins and a black screen you reboot???

always more information is good. Specific information is better.
[Touch Pro2, Tilt 2 Android Development] Bieka:
As i said on Page 3:

After Flashing and copying different Packages (Modules and NBH ALWAYS from same release), i restart the phone to boot into android. Touch Pro 2 Screen appears and after a few seconds i notice a double vibration and the Screen dims to black after that the phone vibrates again and the Touch Pro 2 Screen appears again. One time the Touch Pro 2 stays for longer but after 20 minutes I decided to restart. After that the TP2 does the same as i described. The reboot loops again and again. After 30 minutes i kicked the phone and checked the two described ways in the FAQs in First Post. No Betterment at all. I Flashed again and again many different versions from newest back to 20 versions earlier. All released Versions made the same thing. I downloaded all components which are posted as needed from xdandroid.com and tried. I also formated the SD Card with different tools (yes it is a class 6 sd and i also tried the HP Foramt Tool) and performed a task29 after i flashed back to windows mobile and flashed android again. I hope THAT is detailed enough and i don't forget a bit.

Best Regards
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
Doubtful, and I wouldn't risk it. Sure the processor is similar, but there's not much else that is...

Well does the HD Mini have haret builds available for it..? I wasn't aware of any.
[Touch Pro2, Tilt 2 Android Development] helicopter88:
I thought it was like wm,that is not to hard to port from device to device
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
Not sure how to respond to this one. All I know is, this NAND testing is for the Rhodium. You're more than welcome to test it, just be prepared to brick your phone - and please don't ask us for help when you do, as we won't be able to help you!
[Touch Pro2, Tilt 2 Android Development] TheJoester09:
Unfortunately, it didn't. :(

I've been having this problem for a while now with every build that I've tried, so I don't know what else to do. The other person reporting this problem said he/she had a Tilt 2, and I noticed that the testers at PPCgeeks are mostly CDMA, so could this be a problem with GSM phones? Anyone with a GSM phone get this to work?
[Touch Pro2, Tilt 2 Android Development] Thordim:
@Bieka

when using the NAND version your phone will go immediately into the linux boot screen. that is the black screen with the text you need a magnifying glass to read. then into the xandroid animation and then the android home screen.

when you said

that describes more of the non nand haret boot.

using nand you should never see windows.

so before flashing you put the modules, system.ext2, and rootfs.img on your sdcard in the directory /sdcard/andboot

delete the data.img file from the andboot dir if there is one

then flash and reboot

you should see the linux penguin and the small text scrolling

do a search for how to initate a log file so you can have a better idea of what the error is. it should not take any longer then 10 mins to get to the android home screen and that is a really long time
[Touch Pro2, Tilt 2 Android Development] Bieka:
It seems you didn't understand me. I have all done what you described. The only thing i NEVER saw was the Tux and NEVER saw the scrolling text as in the haret version. So one time again:

I copied all needed files to SD.

I have done a Task29 so that i don't have any windows versions or even files on ROM/NAND.

I flashed the NBH File of NAND Android.

I restarted the phone after bootloader said "complete"

I saw the obligate Touch Pro 2 Splash Screen (First vibrate is noticed on starting the TP2)

After a few Seconds I noticed a double vibration and the Splash screen dims to black.

Then the Vibration from starting the TP2 is noticed again AND the TP2 Splash Screen apears AGAIN.

I waited cause i wanted to see if the phone boots up anytime. After a LONG time i pulled out the battery and tried again and again. Flashing again, changing the packages, formated again. Nothing helped. So i flashed back to winmob and AGAIN the procedures with Task29, flashing nand android nbh and booting. Nothing happend.

So was that all right or do i miss a step... And again i know the difference between android and winmob and i also know the difference between haret android and nand android.

I hope this was now detailed enough.
[Touch Pro2, Tilt 2 Android Development] liveordie56:
I had the same problem you had i did not try the new rootfs yet or the 12/16 nbh though. But it seems to be a problem with the nbh/module, on the ppcgeeks forum try test7 and see if it works for you, it stopped the rebooting for me, but it gave me another problem where it was stuck on "opening=>opened", hopefully you have better luck with it, this is your problem right? you see "touch pro2" it boots up then linux screen shows up but eventually fades out and it reboots and you're back at the touch pro2 screen followed by the same thing?
[Touch Pro2, Tilt 2 Android Development] blitzer320:
yeah i get that opening opened issue with the latest rootfs and everything. I dont know why but i've had that issue since day one with nand, but didnt really bother much because i was gonna wait until they ironed out the issues but it still doesnt work today.
[Touch Pro2, Tilt 2 Android Development] mcnutty:
It will use an existing tscalibration file if there is one in the andboot folder. I can't say that I've ever actually tried to run the calibration during startup since I've just had the same calibration file in my andboot folder since forever. I'll try that when I get to Alaska. Flying up for Christmas today.

I've learned a bit more about this from ACL since, and we think it is the panel init code in microp, so the rootfs isn't going to fix that part. ACL is currently working on a fix, but it won't get tested/committed until the .35 Framebuffer bugs are ironed out for Haret users (if there are any since he just committed the new FB today).

First, just so you don't brick your phone, this is not a NAND boot utility, it is an actual ROM installed to the NAND. Even if most of the components are the same, you have several major issues such as proper drivers for the flash memory used in the phone, having the correct offset for SPL to launch it, and I'm sure there are plenty of other things to consider.

I don't know enough about the Aria or Mini, but any differences in hardware (even if they are just revision changes), IPL, SPL, etc. will need to be identified and fixed before you could do that.

I honestly wouldn't try it, and the processor won't matter in this case. From what I understand, it's all about having the right MTD drivers so that when initrd.gz gets called, it can access the NAND flash memory to load up the kernel.

Hehe, I wish it were that easy, and WM doesn't get ported from device to device. The OS payload can be carried from device to device because the drivers are kept separate. What we have to do is use Haret to reverse engineer drivers and everything to port Android to unsupported hardware. It would be similar to trying to flash WM to an Android phone. Imagine trying to reverse engineer Android drivers and make WM drivers for a device that WM doesn't have drivers for.

You know, I believe we have a few GSM users over at PPCG, but you are correct that it is almost all CDMA users. I joined the project when Wozzer bricked his phone when he pulled the USB cable out just before he finished flashing, so I don't know what all changes were made before then, but all of the changes since then should apply to both GSM and CDMA without any hitches.

That was very detailed, and sorry it took a while to get back to you. Can you try the 11/29 build for me and let me know if you have better luck with that? I have a feeling most of the issues people are having right now have to do with the experimental panel init stuff. ALC thinks he is very close on a fix for most panels, so I'm just waiting for a solid build with panel init working on all devices (rather than just a few) before I build a full package like reefer does.

Bummer, any chance you could try an older build like 11/29. I really think that these current issues stem from the attempt to get panel init working. Gotta love being on the bleeding edge :P
[Touch Pro2, Tilt 2 Android Development] blitzer320:
actually i've had that issue since nand first started, so i think its something else. but i'll try that build and get back to you
[Touch Pro2, Tilt 2 Android Development] sean1197:
how do i reflash windows on it. my screen got cracked and needs to go in for warranty reasons
[Touch Pro2, Tilt 2 Android Development] devilcuban:
Same way you used to flash Custom/Original Roms before. :D
[Touch Pro2, Tilt 2 Android Development] Shadownn:
a friend did the same .. testing the new "kernel nand" .. he can not access to "bootloader"

you used kernel 20110704_234521-kernel-update.zip?

any solution ?

EDIT: The battery was dead -_- false alarm
[Touch Pro2, Tilt 2 Android Development] bigleague4040:
I did it via USB, I always thought that the SD card was the unreliable one, and half the time the bootloader doesn't pick up whatever RHODIMG.NBH is on the card anyways...
[Touch Pro2, Tilt 2 Android Development] whoshotjr2006:
lemme say first, im not part of tiad8's crew, im not even chinese, and im not a dev lol. (just in case acl is watching, i wont send you unsolicited emails in foreign languages)

was wondering though how to find ram addresses (ramstart, ramsize, etc) for tinboot for raph800 cdma, jamesallen and acl have great starts, but jamesallen has the raph100 addresses in his tinboot, acl has rhod addresses in his tinboot, any input would be greatly appreciated. if i can get nand booting on raph800 then i could start looking at the kernel to see what i can see.
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
I think they're working on a new set of files...

This stuff is pretty experimental, booting from SD is MUCH more stable (for the time being...)
[Touch Pro2, Tilt 2 Android Development] x12CHRIS18x:
The links dont work!!!
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
Yea, they're working on a new build. Calm down, this stuff is being provided free of charge.
[Touch Pro2, Tilt 2 Android Development] reukiodo:
Down again

htcdevs.wirelesstcp.net/files/ is down again. Should I assume they're working on a new build?

Even htcdevs.wirelesstcp.net is down... maintenance, maybe?
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
I think ACL is going to try some other builds first.

See here...

He just released that, but it's on a different site...
[Touch Pro2, Tilt 2 Android Development] reukiodo:
I got this same message (on both T-Mobile RHOD210 and AT&T RHOD300) when flashing via USB (Rhodium_SoftwareUpgrade.exe from EnergyROM release). I had success on both RHOD210 and RHOD300 when I put the RHODIMG.NBH onto a microsd card and flashing from the bootloader. Though both did get 'stuck' after flashing, which was fixed with a reset.
[Touch Pro2, Tilt 2 Android Development] [ACL]:
so some of you guys have been wondering why i dont post on this thread. Well truth is that xda is mostly gsm and i'm cdma. So all my efforts have been getting cdma up. Also i figured Cotulla would release a gsm magdlr by now but that still looks like its in the works.

For those of you who dont know, gsm/cdma have diff nand offset so this could be catastrophic if the recognition does not work. For example if a cdma phone is recognized as gsm LK and some of the bootloader can be wiped (No good). The next LK i upload will clearly display the rhod version. This way we can all test and make sure the correct one is being recognized. No gsm nand table will be set until this is perfected.

I'll start a new thread so consider this one obsolete .. thanks for the patience my good men. :D
[Touch Pro2, Tilt 2 Android Development] [ACL]:
We need to thank Erbid for lending me a gsm rhod. Should be here next week so hopefully 1 month is enough to get a solid build out.

:D
[Touch Pro2, Tilt 2 Android Development] GnobarEl:
Does this means we can flas android like we do with windows? no need to boot windows to run android?

Will it be faster or speed is the same? I'm using xdandroi 2.2.2, i really like it, but it gets very slow if I do more than one task at same time. I have to do only one task. Imagine, if I'm updating email and I get a SMS it goes very slow...

Hope with this speed gets better.

Thanks for your hard work.
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
The speed is pretty much identical. The reason our phones are bad at multitasking is the hardware, not the fact that we're running off of the SD card.

Certain tasks where the SD is the source & destination speed up - like Titanium Backup I noticed works a heckuva lot better, for backing up and restoring.

There are perhaps less IOWAIT problems, where the SD card data is being flushed or written in bulk...

The main benefits to NAND are native support for stuff like USB mass storage. Don't expect the device to turn into a 1ghz snapdragon just because Android is moving from the SD card to the internal storage. They're both using the same basic flash memory technology... So again, there won't be a huge speed increase when flashing Android. Sorry.
[Touch Pro2, Tilt 2 Android Development] [ACL]:
haha .. couldn't have it said it better myself.

you test it yet? you know what i'm talkin bout :-p
[Touch Pro2, Tilt 2 Android Development] GnobarEl:
Lets wait and see. Sure I will test soon as it gets released.

=)
[Touch Pro2, Tilt 2 Android Development] milda25:
Will we get early Christmas present? :) It sound's fantastic! Can't wait.
[Touch Pro2, Tilt 2 Android Development] vityea:
Is it available now for any android version to run on HTC Touch Pro 2 fully without booting from SD Card?
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
Correct, see the OMGB thread.
[Touch Pro2, Tilt 2 Android Development] Bieka:
Hey mcnutty,

thanks for your reply but i've tried that release before. I downloaded and tried it again now with no betterment. I was wondering if this problem is the same that happend to the rhod100 device family (de,uk,it....) with the 10/23 (second) release and was solved at a later release.

I hope someone with a rhod100 gets nand boot to work and posts a solution for the problem here or do you have another idea?
[Touch Pro2, Tilt 2 Android Development] mcnutty:
I'm going to assume you have only flashed using activesync from within windows. You will need to power off the phone, then hold the power and volume down button at the same time until you get to the boot loader screen. Now plug the phone in using USB and run the official ROM update utility (use MR1 to avoid issues). After the OS is loaded, you ned to relock the phone. Search the forum on how to do that (would give a link, but I'm on my phone.
[Touch Pro2, Tilt 2 Android Development] mcnutty:
I'll try to discuss this with ACL and see if he has any ideas for a fix. I will also look into whatever changes were made in the kernels you mentioned. Thanks for sticking with providing feedback. I know it is hard when everyone assumes you must be doing something wrong since it works for others. I'm one of the unlucky ones whose panels are different than most others, so the latest kernels don't work for me either.
[Touch Pro2, Tilt 2 Android Development] MassStash:
Same here, running suuuuper well with 29th lid driver, but soon as screens off once, no gettin it back on. Can't wait til that's fixed cuz it'll all be pretty darn sound for me not counting wifi n the few other things.
[Touch Pro2, Tilt 2 Android Development] sean1197:
i knew how to do that.... i figured u couldnt flash it at all via usb and you had to do the nbh on the sd card way...
[Touch Pro2, Tilt 2 Android Development] MassStash:
Hey nate, have ne idea what i'm screwin up if my end key n power aren't mapping anything at all?
[Touch Pro2, Tilt 2 Android Development] JJHiemenz:
It's not just you. I have exact same issue with an AT&T branded Tilt2 flavor of hardware.

I task29'd my phone, then I used a clean SD card, created the /andboot folder and populated per instructions on post 1 of this thread.

I get the initial 'boot' screen on my phone (not the 'winmo' variety, but the one in nand), then I get a double vibration, can see android booting similar to a haret.exe boot, but the screen fades to black and then a single vibrate and the phone reboots to repeat the cycle in an endless loop.
[Touch Pro2, Tilt 2 Android Development] tiger2wander:
Same here! I was try to boot NAND version too much but still failed to get "locked screen" like HaRET way. My screen fade out after some text on boot console printed out, even can not see the boot animation!
[Touch Pro2, Tilt 2 Android Development] JackWater:
Stuck at opening -> Opened

Same here. I have similar issue which stuck at opening -> opened like the other 2 member.

I follow the procedure closely.

Following are my setup:

- touch pro2

- GSM

- 8gb sdhc class 4.

- SD file system is Fat32

- tried flash using both method via sd and custum_ruu method. Nbh used is "20101214_173248-RHODIMG.NBH"

- I do not rename module file. remain "20101214_173248-modules-2.6.27.46.tar.gz"

- I rename the file from "rootfs-20101215-42b44e2.img" to 'rootfs.img'

- I tried include and also exclude the file "initrd.gz". Stuck at same place.

- I tried to remove the modules file and it stuck at the same place too.

- I tried to remove the system.ext2. It stuck at black screen b4 "opening -> opened" occur.

- I tried to remove rootfs.img. It stuck at screen b4 "opening -> opened".

- I tried to remove SIM and with SiM. It stuck at the same place.
[Touch Pro2, Tilt 2 Android Development] mcnutty:
Thank you guys for the feedback on which devices are not working properly. Unfortunately, I posted this thread right when we started working on some really experimental code for the panel stuff. I will hopefully get a chance to chat with ACL here within the next week (limited Internet access here in Alaska). Will be back in the lower 48 next week and hoping to get rootfs merged with ext2 at the very least. Also taking a look at the performance considerations of moving the files to the root of the sdcard instead of running from andboot as reported in some of the 3d testing threads.

As an update: ACL has identified some issues with the actual microp code which means fixes coming for both Haret and NAND. Once those fixes are in place, he is hoping to have panel power on/off ironed out.

For those who cannot boot, I am currently working on a full package to test with so we can make sure everyone has the right files. I will be building it off the 11/29 since that was before we started mucking with panel init code.
[Touch Pro2, Tilt 2 Android Development] tiger2wander:
Thank you for information, so my problem was happen from the first version of NAND project since: 05/20/10 version. I tried many ways and many times to get it boot up on my device but no luck. I'll give some try when full package come.
[Touch Pro2, Tilt 2 Android Development] mcnutty:
I just uploaded the first full package for you guys (see first post). I have tested it on a rhod400 and rhod500. Please report back on how it works for you guys. I have included the latest 3d drivers and am pulling a score of 512 on quadrant and averaging 30 fps on FPS2d.

I will update the full packages with an OC version and a version with better power management once the commits that are coming soon go through.
[Touch Pro2, Tilt 2 Android Development] PNut:
Not booting on RHOD100 (tried latest autobuild NBH-kernel, the 12/22 Full Package and the kernel archive 11/22, 11/29, 12/11). The kernel must be the culprit, because when there was no NAND version i tested many kernel-modules pairs, and the last stable to boot and NOT freeze on the RHOD100 was the "zImage_20101124_215731" - "modules-2.6.27.46-01226-g645b1ff.tar.gz" pair (other zimage/kernel just froze in WM without getting to the tiny textmode bootscreen).

Similar thing happens, just now i only see the "Touch Pro 2" bootsplash on the screen that Task29-flashes, boot begins, as i hear the vibra motor vibrate 2 times (as when using haret in winmo), but after that phone does not do anything displays TouchPro 2 logo, backlight stays on, already waited 15 minutes and nothing happened.

Could someone please compile a NBH file with the mentioned zImage (zImage_20101124_215731) or (zImage_20101204_010857) ? (available from the kernel autobuild service).

http://zimages.googlecode.com/files/htc-msm-linux-20101124_215731-package.tar.bz2

http://zimages.googlecode.com/files/htc-msm-linux-20101204_010857-package.tar.bz2

Thanks!
[Touch Pro2, Tilt 2 Android Development] ATT-Half:
touch pro 2

first time with android on SPRINT touch pro 2 today got it for $130 on craigslist :D girl who hated it cause of slow windows mobile 6.5 who can blame her i immediately flash a sprint basic 1.4 wm 6.1 rom and it got alot better.

just like to say amazing so far comparable to my LG optimus s. I also have an evo but just for keyboard alone i got touch pro 2 ;)

I used the Full Package

first did wipe with task 29

then RUU with Full Package

just got to say that i did try "RAR - Android v2.2 Froyo: BLAZN" before this and it did boot but not data and voice ( no service was display) wifi did work and i didn't want to do the work to get it working .

but just decided to give this a try and data and voice is working wifi too out the box.

few issues i found:

gps is not working at all and gps test app confirms it although it says on in settings menu no location can be found.

another issue is: " know issue "

when you turn off the screen back light remains on that will kill battery life.

" too bad or else i would keep it " don't want to be stuck with no battery during work day would have to flash back to windows for now.

thx for the rom