yashsingh1/xdaforums huggingface dataset:
[Touch Pro2, Tilt 2 Android Development] ghostrid3r:
In regards to VOIP/dailers functions, I think it might be a prefix and/or extension configurations differential between the 2 builds in terms of dialer settings. Might have to grab the old tgz tinboot files and recompile them over to CWM zips.

BTW, does anyone know if this build of CWM recovery supports edify scripts?

@Starfox - does CSipSimple support pbx trunks?
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
I might have figured out the power button not working for recovery & having to pull the battery...

I don't know why it happens tho - basically if you had WinMo and you're flashing to Android, the issue will occur (it did in all my tests).

However, if you already had Android flashed, and you re-flash Android, it works - so this is why the devs for NAND don't see the issue, they haven't flashed WinMo in ages! I'll see what else I can drum up, but these results have been fairly consistent for me.
[Touch Pro2, Tilt 2 Android Development] Homeryz:
recovery

For the people that can't get into recovery screen by holding the power button, try this.

after you flash the recovery.img

enter this... fastboot boot recovery.img

this will take straight into recovery mode without having to hold any buttons.
[Touch Pro2, Tilt 2 Android Development] Walker Street:
GSM Rhod100-Thanks for the tip :) .... We're not quite there yet (boot still fails)

I think you meant 'fastboot boot recovery.img' not 'flashboot'. LOL ... I often make the same spelling mistake when tinkering with my other device (a native Android).

OK now I get this far with my GSM Rhod100:

As suggested, I executed 'fastboot boot recovery.img' from the command line then (using the same numbered steps as in the "NAND How-to"....

11. Select "apply update from sdcard". SUCCESS :)

12. Select "Update.zip" and wait for it to finish installing. SUCCESS

13. Select "Kernal-Update.zip" and wait for it to finish installing. SUCCESS

14. If you want Root, Select "Root-Update.zip" and wait for it to finish installing. SUCCESS

15. Select "reboot system now" .....

16. Your device should now be installed and should load ..... FAILED: It just boots back in to fastboot.

So close!

Also: Pulling the battery at this stage (or when trying to boot in to recovery) made no difference to me. My device just booted back to fastboot.

I also tried task 29 and also fastboot erase ...(all the partitions in the 'Nand how-to'. Again, these made no difference for my Rhod100 (rebooted fastboot again).

I just got up to "Booting Linux" on the blue screen then it rebooted (boot-looping up to "Booting Linux"). I don't know why it suddenly decided to get even closer to working. (??) However after 4 boot loops it settled back in to fastboot again. So close .... yet so far .... again
[Touch Pro2, Tilt 2 Android Development] eddy4763:
This used to happen to me with my tilt2. My solution was just to remove the battery while it is in fastboot mode. I wait about five seconds after removing the battery. After that I just hold the power button as soon as the blue screen shows up (not before). Hope this helps.
[Touch Pro2, Tilt 2 Android Development] Walker Street:
fastboot erase data - ?bad block Error - Is this relevant?

Again with my rhod100 gsm device,

I noticed the following error on the blue fastboot screen in response to the command:

On Windows command line:

fastboot erase data

On device's blue fastboot screen

....

fastboot erase: data

skipping @2432 (bad block)

cannot erase @2432 (bad block?)

....

There were no errors when erasing the other partitions. I don't know if this is relevant to the trouble I'm having (i.e. the device won't boot even though everything is installed).
[Touch Pro2, Tilt 2 Android Development] Walker Street:
Thanks.... I thought that trick was for getting in to recovery, not booting the phone. Please let me know if I'm wrong: Once all zip files are installed from recovery, you should not have to press any button to get the phone to boot up to the normal Android OS.
[Touch Pro2, Tilt 2 Android Development] eddy4763:
You are correct, sorry I didnt read the last part of your post and thought you were trying to boot into recovery
[Touch Pro2, Tilt 2 Android Development] Walker Street:
(1) Should I see an /andboot folder on SD card (2) Could I use boot.img from fastboot

(1) In the second post of this thread it says, McNutty says: "Modules, rootfs.img, and system.ext2 must be stored under /andboot on the SD card".

I don't see an /andboot folder on my SD card after everything is installed (but still won't boot). Is this part of my (and my Rhod100 GSM device's) problem?

(Sorry if I've missed this being covered in earlier threads) :)

(2) .... sorry to be a pest .... I wonder if I could at least boot my device using a boot.img file, i.e.

fastboot boot boot.img

If this is possible, would someone be able to upload a boot.img to a file sharing site (or tell me how to create one from the .nbh and .zip files I'm using to install Android on my device)?

PS: I'm have both linux (in case I need to run an .sh script) and windows systems running.
[Touch Pro2, Tilt 2 Android Development] Walker Street:
GSM Rhod100-'Screenshots'

I took a couple of screen photos with a digital camera.

Everything (basically) went smoothly right up to (and including) installing all the zip files from recovery. After that it won't boot to Android. Instead the following happens:

After leaving the battery out for an hour, the device attempts to boot linux a dozen or more times , but ends up looping back to the same blue screen (the first photo below). It seems to keep trying for longer (more boot-loops) if I leave the battery out. After 5-10 minutes it 'gives up' and stays in fastboot mode (the second photo).

Also: Here's the output of an "ls" command in adb shell (while the phone's in recovery and connected by USB). Don't know if this helps:

c:\android-sdk\tools>adb shell

/ # ←[6nls

ls

←[1;34mbin←[0m ←[1;34mdev←[0m ←[1;32minit.recovery←[0m ←[

1;34mroot←[0m ←[1;34msystem←[0m

←[1;34mcache←[0m ←[1;34metc←[0m ←[1;34mproc←[0m ←[

1;34msbin←[0m ←[1;34mtmp←[0m

←[1;34mdata←[0m ←[1;32minit←[0m ←[1;34mrecovery←[0m ←[

1;34msdcard←[0m

←[1;32mdefault.prop←[0m ←[1;32minit.rc←[0m ←[1;34mres←[0m ←[

1;34msys←[0m

/ # ←[6nexit

exit

:) Thanks for your patience. I'll stop hogging the thread .... promise.
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
To Walker Street or any other GSM folk: you guys have to hack up a file that basically breaks the RIL. It allows the phone to boot, but it's useless as a phone. An actual fix would be nice, but I have a CDMA device so I have no clue why it's not working...

Edit - found the post I was talking about.
[Touch Pro2, Tilt 2 Android Development] Homeryz:
Thanks I edited the spelling mistake.

after doing all this my phone never boots into android, it always boots back into fastboot.

But the trick above also works for booting into android,

if you take the boot.img out the kernel zip and..

Copy boot.img to your C:\android-sdk-windows\platform-tools

you can then do fastboot boot boot.img and it boots the phone into android.

Again here my phone has never gotten past the boot animation.

Thanks

Homer
[Touch Pro2, Tilt 2 Android Development] ghostrid3r:
This!

After tinkering with boot timing & HOLDING power button when boot starts, I have confirmed above method by eddy4763 works like a charm for getting into CWM. :D

Mind you, most important part is leaving the battery out for those 5+ sec. so the power discharges from device. Also this procedure must be repeated in order to enter CWM each time.
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
You can just do fastboot boot recovery.img.... No need to pull the battery.

Also, I only had the issue when I had WinMo installed before. I reflashed from Android to Android, and it worked perfectly as expected...
[Touch Pro2, Tilt 2 Android Development] Walker Street:
boot.img ... thanks for the advice

Thanks for the tip on where to find boot.img. The first time I issued 'fastboot boot boot.img', I got to the black penguin screen and text started rolling (just like I remember when I tried haret.exe in the past). However it crashed and rebooted after just over a page of rolling text.

I could just make out some error message that included 'rild uses 32 bit capabilities (legacy support)..... SMD: Ch 0 opening' .... or something similar.
[Touch Pro2, Tilt 2 Android Development] Walker Street:
Thanks for pointing me to that post

I tried out the hack in the post (from PPC Geeks forum user 'eu0741924381'), i.e.:

"modifying sysinit.rc and removing " -- -d /dev/smd0" from:

service ril-daemon /system/bin/rild -l /system/lib/libhtcgeneric-ril.so -- -d"

I still get a crash at the same place when I do a 'fastboot boot boot.img':

i.e. an error message that included 'rild uses 32 bit capabilities (legacy support)..... SMD: Ch 0 opening' .... or something similar, shortly before the phone reboots. I never have gotten to see the Operating System in action. Over at PPC Geeks, eu0741924381 has posted some suggestions about modifying the ril.cpp, but says he can't try them out because his computer is broken. This is pre-compilation source code, something I have (less than) no skill or knowledge about, lol.
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
As I said on PPCG, NAND isn't so ready for GSM yet.

Anyone with some skills, feel free to jump into the development and help - the more the merrier! We definitely could use some knowledgeable folk with GSM devices/service...
[Touch Pro2, Tilt 2 Android Development] DJ_Synergy:
OK ... Now I will jump in ...

I'm not a Linux-Geek and also a bit unexperienced in android but i have a rhod100 and a lot of knowledgement in ... lets say 'electronic things' :D

my situtation at the moment:

flashed everything fine via CustomRUU and fastboot

device is booting up into linux without fastboot command or keypress during bootup

linux boots just fine til the ril 32-bit problem

i will try the ril hack today and post if this works fine for me. if it is working, we have a good and clean booting rhod100 for testing purposes :)

sorry for my non perfect english (i'm from germany) ... but i think everyone knows what i mean :)
[Touch Pro2, Tilt 2 Android Development] highlandsun:
"32 bit capabilities" message in rild is not an error. This machine is only a 32 bit architecture.
[Touch Pro2, Tilt 2 Android Development] Starfox:
And this is why leaving useless debug message is bad...

-- Starfox
[Touch Pro2, Tilt 2 Android Development] highlandsun:
Maybe. Most of the people who would ever read these messages already know what kind of hardware they're running on. If you	don't know these details, you're not the right person to be messing with these testing threads.
[Touch Pro2, Tilt 2 Android Development] DJ_Synergy:
Ok, Let's go!

I've tested a lot of things ...

the first thing that i found out is that the rhod100 only boots wwithout a sim. If a sim is in the phone the rhodium will reboot everytime LK tries to boot linux. this is for both, normal and recovery ...

then i found out, that the "hack" with the ril runs good. android was booting the first time from nand on my rhod100. i just couldn't test the gsm-part because of the missing sim.

Then i played a little with android and found a few things, that are allready fixed in the newest builds of xdandroid and the frx06 ... is this project using some oooold kernel as codebase for the nand one ??? o.O

So ... I think this is allready running as a good system. a lot of work to do to get this stable and fast but the first thing to do is just integrating the newest fixes in this build. If this is done the most things will work great, i think.

Q: The GSM-Thing with LK ... is this allready known ? Is there a way to get Linux running with a Rhod100 with sim inserted?
[Touch Pro2, Tilt 2 Android Development] wennes13:
I eagerly follow this thread, I flashed my husbands HD2 to android and it works perfectly. I really really would like to flash my TP2 to android as well.

I have no knowledge to help, but all the effort made to come any closer of making a stable rom is highly appreciated. Please keep up the good work.
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
HD2's a little bit different hardware. Those guys had it easy, lots of native Android devices with pretty much identical hardware to steal code from :p.

Our device is a little bit more unwieldy, and some think NAND development is premature. I'm glad the development is happening, but it's far from ready for prime-time. Devs are workin hard, and I'm trying to get more on board ;).

Yes, the kernel is significantly different. The build is FRX06 tho...

Well the RIL "fix" basically tells the RIL not to look for any radio device. So I would think you could boot with the SIM, or insert the SIM later, but it would have no effect as the RIL is not able to do its job.

We're trying to get GSM up & running, just not many GSM devs have helped. Any developer help on GSM is appreciated... and needed :).
[Touch Pro2, Tilt 2 Android Development] cyberscribe:
The links on the first post are broken, so I can't get any of the files to try nand booting android on my rhod400 or rhod210. Can anyone mirror them somewhere?
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
Server's httpd service is down. It should be back up shortly...
[Touch Pro2, Tilt 2 Android Development] Shadownn:
i try download this files but link's down

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...NORECOVERY.NBH

Recovery Image: http://htcdevs.wirelesstcp.net/files/LK/recovery.img

05-22 Kernel: http://htcdevs.wirelesstcp.net/files...nel-update.zip

FRX06 OS Files: http://htcdevs.wirelesstcp.net/files...RX6/update.zip

Optional - FRX06 Root: http://htcdevs.wirelesstcp.net/files...oot-Update.zip

please reup :( thank
[Touch Pro2, Tilt 2 Android Development] Tippfehler:
@ Shadownn

The most links are broken. ( ... )
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
Wait, the site is back up... those links you posted are invalid, I'm double-checking the first post.

It's just the .nbh that seems to not be working...

Go here as the first post clearly states:

http://htcdevs.wirelesstcp.net/files/
[Touch Pro2, Tilt 2 Android Development] DJ_Synergy:
This is what i thought when i followed the dev since the last weeks. That's why i really want to help you guys and try to give you any gsm feedback that is needed. I would also try any Dev-Version as first GSM-Phone for testing. So if you guys have some "Pre-Pre-Release" or something, just let me know. I will test it and give you feedback.

I would really like to have android working stable and fast on our devices. The TP2 is a cool device because of it's nice hardware like the hardware keyboard or the OC-able cpu. So this device would run nice for the next years if android is running on it.

LOOKING FORWARD FOR THIS! KEEP UP THE GOOD WORK! WE NEED YOU GUYS :D
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
lol, no pre-pre-release stuff that I'm aware of. We really need a dev with a GSM device (or someone willing to donate a GSM device!) to step up to the plate. Testing only goes so far, at this point I think we need someone to pick apart what's going awry with GSM. Probably many things, and yes I'm going to blame the kernel :p.
[Touch Pro2, Tilt 2 Android Development] DJ_Synergy:
lol ... i have many experience in PC's, Smartphones and even developement in C, Basic, etc. ... I'm not a developer but i can try to give you some - let's say - feedback of whats going on there. I just don't now, where to begin right now.

As i said, LK won't boot linux if there is a sim inserted in the phone, so that is the first thing that won't let me try what happens with gsm in linux.

LK tries to boot linux, but it just reboots exactly after the bluescreen of LK (so there even isn't the black linux screen)

Just let me know, where to begin right now. Is there a way to log some thing while LK tries to boot linux or during the first millisecs of linux booting ???

And if there's someone from germany in the dev-team ... it would reeeaaaaly help to speak german because of the technical vocabulary, you know :)

EDIT: I will try the new files and give feedback, while i try to find a way to find out whats happening there with gsm -.-
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
There is a German on the dev team, he goes by emwe. Look him up on IRC.

Only issue is, he hasn't worked on ANY of the NAND stuff to my knowledge. He's mainly been hackin at the kernel stuff on haret (AFAIK).

But all the code is available - check it out, play with it... see what you can do!
[Touch Pro2, Tilt 2 Android Development] DJ_Synergy:
ok, i will see what i can do.

the only problem that i have is, that my rhod100 is my main phone and runs on wm6.5 energy reference with 768MHz OC ... fast and stable as it should be ^^

so i will try to find a method to reflash my phone quickly to what it is before i play around with nand ^^

PS: what about a projectname for this like XDnAndroid or something? :cool:
[Touch Pro2, Tilt 2 Android Development] DJ_MiX:
tried to install LK Bootloader on a us cellular tp2 but on restart it went back to tri color boot loader but was curopted.

Does the LK Bootloader work on all versions of the pro2?
[Touch Pro2, Tilt 2 Android Development] nathanpc:
Any news on the GSM port?
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
Not to my knowledge, let us know if it works for you. Standing on the sidelines and asking questions like this doesn't do any one a damned bit of good.

LK *should* work on all versions of the TP2. Which RHOD do you have? USSC doesn't help, but I think that's the RHOD400...
[Touch Pro2, Tilt 2 Android Development] DJ_MiX:
Will check once I get home, but I can try on sprint tp2 and see results.

should I task29 before installing LK? I didn't do that on us cellular unit
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
You still fail to mention what RHOD you have.

task29 isn't required, but isn't a bad idea either.
[Touch Pro2, Tilt 2 Android Development] hasbrone:
I have a Tilt 2 and the LK Data not found "Corrupted"...
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
Uhm... Ok. Not sure why you quoted that post, it had nothing to do with you.

But, as it's been said many times before... GSM devices aren't so well supported. Really, at all. Stick to HaRET until issues get sorted out, unless you're a dev and can pitch in. Would really be nice to get some devs to pitch in, but feedback on what happens really isn't necessary at this point. We know it's broken, it just seems no one knows how to fix it (yet). Devs welcome, come join the NAND train!
[Touch Pro2, Tilt 2 Android Development] bigleague4040:
GSM fail...

Hmm, it doesn't seem to work on my RHOD210, gives the same error that the DJ_Mix was having... It used to work, new build killed it... Anyways, I hear tiad8 has made progress with GSM working, but you probably don't exactly want to hear about him... I came from his site here because his own bootloader's link is broken :rolleyes:
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
lol, you're kidding yourself if you think tiad8 has made any NAND progress. All he's done is steal the verbiage and files from ACL et al. It's a hilarious copypasta.
[Touch Pro2, Tilt 2 Android Development] bigleague4040:
Not that I'm entirely sure that he himself did any of it, but it IS on his site, and he does have people with decent english claiming that it somewhat works, I got a Sensation last Saturday so I don't mind bricking my phone :)

Here's a picture of what's going on with my RHOD210 if that helps you any. http://www.amazingcatsnews.com/IMAG0008.jpg

Off topic, went into the T-Mobile store today, they had some Touch Pro2 accessories left from way back when... they sold me the headphone adapter and other crap for $5 each. I am happy. :)
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
Well yea of course it's on his site. He wants it to seem like he did it, like everything else he pumps out... which very little is actually his own unique effort.

As for that pic, ew. That's not a good sign. I wish I had a GSM RHOD to play with, all I've got is a RHOD400 - which 'works' but NAND doesn't exactly 'work well' for any phone at this point.

Hoping to attract more developers, NAND is really being spearheaded by very few.
[Touch Pro2, Tilt 2 Android Development] bigleague4040:
Haha, I'd rather have a CDMA, at least I could use it as a 'lil iPod Touch (hate the comparison, I know...), I really wanna use my Class 10 SD card for something other than powering a phone I'm rarely going to use, but still the best for tinkering since the Sensation bootloader's locked :)

NAND GSM would be so awesome... I can tinker with Linux kernels and stuff just fine, but none of that works if I can't boot the phone... keep working guys, this is gonna be amazing! I'll stop clogging up the dev thread now :rolleyes:

Back to EnergyROM for me...
[Touch Pro2, Tilt 2 Android Development] Lmiller1708:
Does this happen with SDCard flash or USB Flash? If you haven't tried both please do. Also re-download the file just to be safe. :)
[Touch Pro2, Tilt 2 Android Development] DJ_MiX:
I got the same screen when installing on us cellular pro2.

maybe download source is corrupt?
[Touch Pro2, Tilt 2 Android Development] DJ_MiX:
it's a RHOD400
[Touch Pro2, Tilt 2 Android Development] dralibak:
TP2 reboots to HTC LOGO over and OVER no further..

Hi. I would greatly appreciate someone's cookbook style instructions as to what to do.

I believe some files were corrupted at the time of installation. I got a glimpse of the android, then it rebooted and it never worked again! since then I've been trying to reinstall all, but now my computer is not recognizing the phone, and the I get the phone keep going to HTC logo and rebooting over and over at HTC logo till battery runs out. the power and down arrow don't work any longer, and I get nothing happening. Can't get PDAnet connected, and can't get windows media connected and as a result adb does not recognize any devices!

How can I reinstall the basic startup stuff on the phone again?

Please please help if you could as the phone is now absolutely nonfunctional at present time.
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
Reflash to WinMo. Wait until it's more stable. The word 'testing' is in the thread title for a reason - stuff changes quickly, and quite often is broken.
[Touch Pro2, Tilt 2 Android Development] dralibak:
how to reflash to winmo when i don't even get bootloader or anything?

Hi, how do I reflash to winmo, when all i get is phone rebooting itself to htc logo and nothing else? power and volume down don't work, and power and end call button don't work, bootloader does not work, computer does not recognize the phone, .... so ... anything i do seems to have to come from placing a file in sd card and let it automatically boot itself!?

all things went corrupt after attempt of nand installation... so here I am.

Yes, understand it was testing....

Please let me know how to start if you could please.

thanks.
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
Can't reflash via SD?

Get a WinMo ROM, grab the .nbh file, rename to RHODIMG.NBH and put it at the root of your SD, then put the phone in bootloader mode.

This is for testing, and assumes you know the basics of flashing... if you don't, please don't try this.
[Touch Pro2, Tilt 2 Android Development] dralibak:
The thing is I can't even put phone to bootloader mode! Phone is not responsive to my push buttons now.

Any suggestions?

Thanks.
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
Is the battery dead? If that's not the case then I don't know to be honest...