yashsingh1/xdaforums huggingface dataset:
[Touch Pro2, Tilt 2 Android Development] highlandsun:
IMO, the NAND developers are premature. You have a perfectly viable system environment on SDcard. The Android and kernel problems you encounter on SD won't disappear just because now you're running on NAND. If you have a partitioned build on SD, then there's not much difference operationally to NAND. Figuring out how to use the NAND partitions is great, but there's plenty of basic system and kernel issues that remain, and will still remain regardless of SD or NAND.

Get the basics working first, get them all stable, and then go play with the NAND. If you can't stabilize an SD install, which is honestly the easiest possible install environment, then you're kidding yourself if you think you can get it any better on NAND.
[Touch Pro2, Tilt 2 Android Development] stefanm1:
the download doesn't work,

Its says: Invalid or Deleted File.

But i will try it if the download works.

Thanks !
[Touch Pro2, Tilt 2 Android Development] Lmiller1708:
Fist I respect your work! But...

How are we premature?????:confused: It's real hard to test stuff with no testers! It might work great on our devices but not work on another because they did something a bit different. You should know this...

Also the Kernels ARE different! I have found the NAND kernels to be more stable, for both me and my wife's phone. For example when my wife was running Haret she was getting the SOD many times during the day... Yeah you could say something was wrong on her end but I just took her exact data.img and moved it to NAND. Guess what? She no longer has the SOD, humm kernel?? Now nothing against the Haret developers because I'm reading most of these issues were resolved by now... :)

Yes, the system's for the most part are the same and some of the problems will still be there regardless of Haret or NAND. :eek:

We have made lots of progress on NAND from willing testers.

So Thanks to all!
[Touch Pro2, Tilt 2 Android Development] Lmiller1708:
Sorry about that. We recently made some more changes and removed those NBH's. It looks like we are going to NOT include the recovery, this will make things easier. Also ACL says he has a fix for the buttons but he forgot to push all the changes yesterday, so I hoping today he will have them done. :) Then I will release another NBH for all!
[Touch Pro2, Tilt 2 Android Development] galexandr:
Hello everyone,

I am on CDMI Sprint network, im really looking forward to thos!!

2 questions:

When i install nand, what happens to my WinMo rom? Can i go back easily?

Does it have the option to just run from SD?

Thank you much!
[Touch Pro2, Tilt 2 Android Development] gallahad2000:
Yes, I would recommend you using the SD version because the NAND version is still in testing phases now (why it says testing in the title).

Link to Android off SD

Flashing to NAND requires flashing over your winmo rom which would require you to flash back to be able to use winmo again.
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
As was stated above, you should probably run off the SD.

But assuming you do install this, it wipes WinMo from the phone - completely. It is easy to go back, just reflash a WinMo ROM.

The option to run from the SD is really the only option presently. This is just for testing, thanks.
[Touch Pro2, Tilt 2 Android Development] ghostrid3r:
1) Yes, boot into bootloader mode > power+end+vol up (tri color screen) > start WMDC > connect USB to device and flash ROM.

2) No
[Touch Pro2, Tilt 2 Android Development] stefanm1:
Does GSM works in the normal version ?

Or do i have to wait for the new NBH ?
[Touch Pro2, Tilt 2 Android Development] Zambowie:
Sooooooooooooooooooooooo any updates? Its been almost a month.
[Touch Pro2, Tilt 2 Android Development] Lmiller1708:
We are working HARD. :)

New method of creating NBH's can't be flashed with the sdcard, we are looking for help with that...

Also the recovery is about ready, we now will have only file "update.zip".

This will do everything we need, just like native devices. :) Thanks to ACL!!!
[Touch Pro2, Tilt 2 Android Development] ghostrid3r:
@Lmiller1708

Thank you and keep up the excellent work, as we former vogue users still follow, and are greatfull for your valuable contributions to XDA and PPCGeeks community. ;)
[Touch Pro2, Tilt 2 Android Development] ryannathans:
Might wanna update FAQ on post 2#

Eagerly awaiting GSM.
[Touch Pro2, Tilt 2 Android Development] DJGonzo:
Does anybody have a working combo of files? Whether old or new. I just need this phone to work.

Ive been trying for hours to make it works with the links posted here and on PPCGeeks and can't get it to work...

I have a RHOD210 (GSM)

Thanks.
[Touch Pro2, Tilt 2 Android Development] Lmiller1708:
Just hold off for a day or two. Some of the files are gone because they have been removed... Sorry.

We are getting closer by the minute!!! :eek: But not yet there...
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
Indeed, please be patient as lmiller has requested - stick to SD card installs until the kinks are ironed out!
[Touch Pro2, Tilt 2 Android Development] DJGonzo:
Alright thanks.

I hate booting into WM just to boot into Andorid but oh well.

Ill wait :)
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
It'll be much more stable using this method in the meantime anyways - even when they do get NAND flashing functional/stable for all, there's a lot of work to do on the kernel.... Probably some other things to clean up too. Either way, it'll be in a 'testing' stage for a while - but I do encourage anyone to test who is capable :D
[Touch Pro2, Tilt 2 Android Development] DJGonzo:
This is my play phone but my Galaxy S broke and I have to send it in for repairs and got to use this in the meantime. I just loaded up the SD card build and its dog-slow. Plus I can't uninstall the slow (new) version of Google Voice that comes with it :(

Im glad to test anything you have after I get my Galaxy S back :)

Off topic: My friend is starting his own distro based on Debian for penetration testing (kindof like Backtrack) and I'll be "porting" (if you can call a ROM with a chrooted linux distro "porting") it to the Galaxy S :D
[Touch Pro2, Tilt 2 Android Development] Lmiller1708:
Ahh the good old days! And Thanks for you Kind words. :)

Yes testing will still be needed, we will let you know when the time is right. :)

Since Nate no longer has a functional device it is only ACL and I working on this currently (that I'm aware of), and hopefully Nate will get back in soon. ACL is doing most if not all the dirty work. I'm slowly getting up to speed with C which I have not used for a while... So in time I will be more of a help to him. But for now if there is anyone that can program in C and would like to help out let us know! :D Yes I know you could help out just as well in Haret... The decision is up to you!

Thanks!
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
So I guess I'm curious where you guys talk about NAND dev? I never see you folks on IRC...

As for Nate, I need to talk to him - there's some donor phones in the pipeline. Same with ACL - I heard he bricked his phone...
[Touch Pro2, Tilt 2 Android Development] Lmiller1708:
We do come on every now and then but we mainlly use Gmail chat.

Yes ACL did screw it up somehow, but he just ended up buying a phone himself.
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
Bastages. I need to add you guys to GTalk then it seems! :p
[Touch Pro2, Tilt 2 Android Development] Starfox:
I was looking at some other forum, and was curious how mtd was set up on the TP2. I insmod mtd_blkdevs & mtdblock, then "cat /proc/mtd". On an native Android, there are multiple mtdx corresponding to boot, recovery, etc. On the TP2, there is only mtd0 that spans the whole nand. Is the mtd layout something the .nbh sets up, or is it something that cannot be changed by the user?

-- Starfox
[Touch Pro2, Tilt 2 Android Development] Lmiller1708:
Currently we are setting the MTDparts by the Command Line.

Here is a spreadsheet I put together for a easy way to figure out what the mtdparts out:https://spreadsheets.google.com/ccc...Eh2dEl4OTFIbzI5VS1GM1E&hl=en&authkey=CPqYsrAD

You will notice there is one for LK, boot, and recovery. The big thing is they all should match there starting and ending location in memory. We should be able to just use LK's but the atags needed to do that are not yet working.

I'm guessing that when you are running the "cat /proc/mtd" you are using the SDcard which will give you that. If you were in NAND you would see this:

dev: size erasesize name

mtd0: 03100000 00020000 "nand"

mtd1: 00600000 00020000 "recovery"

mtd2: 0ace0000 00020000 "system"

mtd3: 0f800000 00020000 "userdata"

mtd4: 02000000 00020000 "cache"
[Touch Pro2, Tilt 2 Android Development] Lmiller1708:
New TEST build!!!

GSM "Should Boot"

NBH: <--- Will only work with with a USB Flash.

msm_unsigned_051011_151551.zip:<--- is the file to be placed in root of your SDCard

Here is Fastboot: <--- Need to have drivers installed, please don't ask how to do that here... Google it.

Here is the recovery.img <--- Add to your Fastboot folder.

Process:

When your phone boots you will see a blue screen. Hold down the End call button and your phone should then boot to fastboot. If not try again.

Open cmd window and cd to your fastboot folder...

Enter this cmd: Fastboot flash recovery recovery.img

Then: Fastboot reboot

Again: When your phone boots you will see a blue screen. Hold down the End call button and your phone should then boot to recovery. If not try again.

Once in recovery go to "install update Via Sdcard" and press the End Button to Select.

Select the update.zip you already placed on your SDcard from above.

Wait..............

Once completed, you can select "Reboot Device".

Your device will reboot and boot to Android. We all of the extra apps it might take a bit to load....

Enjoy!!!

Please Report any issues... Not sure about GSM service...
[Touch Pro2, Tilt 2 Android Development] Zambowie:
Sounds freakin awesome Lmiller. Now i just gotta figure out fastboot lol
[Touch Pro2, Tilt 2 Android Development] m2maynard:
I got into the recovery and can navigate up and down via the volume buttons...but how do I select anything? none of the other buttons respond. GSM RHOD 300 (ATT TILT2)
[Touch Pro2, Tilt 2 Android Development] Lmiller1708:
End Button should select... I guess I forgot that... :eek:
[Touch Pro2, Tilt 2 Android Development] m2maynard:
end button doesnt work but the enter button on the keyboard does!
[Touch Pro2, Tilt 2 Android Development] m2maynard:
I am currently stuck in a bootloop after selecting the MSM package. attempting to recopy to SD Card and try again.
[Touch Pro2, Tilt 2 Android Development] m2maynard:
ok. So I still am stuck in the bootloop. bluescreen prints out lots of stuff, then says booting linux...then reboots. I can still get to recovery by holding the end key though. Any other suggestions? I tried using the enter key since it worked to select once I was in recovery but that doesnt seem to have any effect.
[Touch Pro2, Tilt 2 Android Development] Lmiller1708:
Nope. But it does not sound good... I will talk with ACL and see.

Has any other GSM user tried it?

Thanks!
[Touch Pro2, Tilt 2 Android Development] popetorak:
Fuze

Does it work with the Fuze?
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
God no. You'll almost certainly end up with a brick, DO NOT USE THIS!!
[Touch Pro2, Tilt 2 Android Development] popetorak:
That was close
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
Same, on my RHOD400. None of the front keys worked (holding end got me into fastboot & recovery) but the enter key on the keyboard got it.

After installing the msm_unsigned.zip from the "apply update from sdcard" menu entry of off the main menu and rebooting... it rebooted right back to recovery, I didn't touch anything. So perhaps something with the front keys isn't working out...? None of the front keys seem to work, unlike the previous version of recovery I tried. Basically can't seem to escape recovery, always boots to it...
[Touch Pro2, Tilt 2 Android Development] Lmiller1708:
Well I'm not entirely sure why we are all of the sudden having this many issues. I'm going to roll back a patch or two and see if that will help, but we will then lose GSM. I can't even get into adb shell to see what's going on with the system or bootlog...

As for people not being able get out of recovery I have no idea why that is happening. That is something that I can not replicate, but I will try... Could be the button is still thinking it is pressed down??? That's why pulling the battery works... We are having issues with LK's buttons and this is one of them... It works for me on my 500.

I will hopefully have some answers soon. :)

EDIT:

Renaming the update.zip is NOT necessary, I'm guessing it was just a fluke that is worked...
[Touch Pro2, Tilt 2 Android Development] Germypan:
I cannot try this, because my windows 7 64 bit don't have installed adb drivers which i downloaded from this link. i tried some methods but in device gesture of windows there is android but it stay in emergency becouse there aren't driver. if you have any ideas to repair this problem, i will can try. i have a rhod100_it

Germy
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
Sort out ADB before you even attempt fastboot. The FAQ has some adb tips.
[Touch Pro2, Tilt 2 Android Development] Germypan:
I tried same methods, but it don't work. i tried to use usbdeview too, but when i put the installation driver in the usb_device folder, my windows tell me which there isn't driver for this device... i don't understand where i mistake

sorry for my bad english!

Germy
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
That's fine, but I'm saying you won't be able to use fastboot until adb is functional. Sort out your issues with adb before attempting to flash this.
[Touch Pro2, Tilt 2 Android Development] Lmiller1708:
Fastboot should work. It does not use adb... It's broken in the kernal. Not sure why just yet...
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
Hrm, unless I'm just missing something, I needed the drivers for ADB to properly use fastboot - and my point is if he can't get adb working at a basic level, fastboot'll never work...
[Touch Pro2, Tilt 2 Android Development] Germypan:
Thanks for the answer but my problem is driver, because, when i put my device on pc, my windows (****) don't able to install drivers, then i take to install manually the drivers, but when i put the drivers folder in "installation drivers" it retuned to me which there aren't drivers for this device but in device gesture my device is loaded as "Android".... I hope to be able to explain what happens to me... when i used fastboot on my lg optimus one or on my htc dream, the drivers was installed from lg for the first and from Android SDK for the second, but for TP2 i don't be able to install those drivers which i linked 5 post ago. i think, is there another drivers for rhod100_it? if don't exist any drivers i can try whit ubuntu which i prefer. You tell me what i must do, and i do! :D
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
If you prefer Ubuntu, then use it. This thread is not a how-to fastboot or how-to configure the drivers for ADB, as was clearly stated in lmiller's post. If you can't test currently, then don't. But please don't fill the thread will stuff like this... this thread needs to be filled with feedback and dev work, not helping newbies setup fastboot, thanks!!
[Touch Pro2, Tilt 2 Android Development] dswaggz:
Wow that was kinda rude he just was trying to a help"GSM" owners.
[Touch Pro2, Tilt 2 Android Development] m2maynard:
Not really so much as rude, just sounded like business to me. He is trying to stick to the original point of the message and not get caught up in the fundamentals of getting somebody stood up. ADP is a fundamental part of communicating with your android device and deserves (and has) its own threads around it as it can be challenging when first discovering how to use and configure it.
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
You are constantly missing the point, and consistently posting off-topic drivel. Please, either help or go away - I haven't seen a single one of your posts being helpful.
[Touch Pro2, Tilt 2 Android Development] Germypan:
I tell you sorry, but, i tried with ubuntu, when i write the "./fastboot flash recovery recovery.img" it return to my "waiting device". if i write ./adb devices, my device there isn't. now i don't know how i can try another method. if you have any ideas please tell me how i can try.

Sorry for my bad english

Germy
[Touch Pro2, Tilt 2 Android Development] Lmiller1708:
Sorry But look here for a guide for Ubuntu. http://xdaforums.com/showthread.php?p=11823740

Please post any other questions regarding ADB there... Thanks.
[Touch Pro2, Tilt 2 Android Development] stefanm1:
My rhod 100 doesn't boot,

It says dma 4 4 busy..( for a long time.. )

What can i do ?

btw: great work..
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
Ah, sorry I just noticed RHOD100.

GSM isn't supported yet, sorry. I heard it'll boot if you pull the SIM tho...
[Touch Pro2, Tilt 2 Android Development] Lmiller1708:
Yeah I guess I should update my post.

We are getting closer... But there are a couple of tweak that need to be done on the user end that might help too. Like nodding the sysinit.RC
[Touch Pro2, Tilt 2 Android Development] Trekfan422991:
i do not need data .. i dont have a data plan... i have a tilt 2 ... if you wann a send me it with a modded sysinit.rc i will test
[Touch Pro2, Tilt 2 Android Development] stefanm1:
THanks for the info,

I will wait for gsm !
[Touch Pro2, Tilt 2 Android Development] hoatienii:
wait and hope ;)
[Touch Pro2, Tilt 2 Android Development] dswaggz:
^DIDO^

sent by DAN SWAGGER via tapatalk/simple mobile
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
I'm assuming you mean 'ditto'...

Anyhoo, seems GSM folk might have a workaround, although it seems like the user that reported it only got it to boot - still no service.

See this post. Seems to have a solution to get GSM folk booting, perhaps then someone can figure out the service issues.
[Touch Pro2, Tilt 2 Android Development] Lmiller1708:
Yes! Please test this out and we will add this fix.

Let us know if it works.
[Touch Pro2, Tilt 2 Android Development] highlandsun:
That's not a fix. That just broke the ril by *not* telling it what device to talk to.

Naturally there will be no 3G data service after doing that.
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
Indeed. But at least it allows the device to boot, which normally has been a hurdle for GSM NAND folk...
[Touch Pro2, Tilt 2 Android Development] Lmiller1708:
@ ALL

I put together a "NAND How to". ACL, Natemcnutty, Arrrghhh and myself will all have RW access so if something needs to be changed it can be right away. :)

You can find it here:NAND How-To
[Touch Pro2, Tilt 2 Android Development] eu0741924381:
Yes, i know that's not a fix, it only bypasses smd check, the only reason i did this is so i can test other things like Wi-Fi and overclocking...
[Touch Pro2, Tilt 2 Android Development] sp3dev:
I wonder why gsm's not working for rhod folks. Maybe cause of old/broken smd in 27 kernel? One good thing would be to make logcat and dmesg dumps with smd debug enabled. When i fixed that clock poop on kovsky, i was always getting network registration and stuff with 2.6.35.7 on nand
[Touch Pro2, Tilt 2 Android Development] eu0741924381:
I will try to make some logs with smd debug enabled if that will help... i hope i can pull them though ADB as i get a boot loop with " -- -d"...

Update: can't pull logs because of the boot loop
[Touch Pro2, Tilt 2 Android Development] mcnutty:
It's because Wozzer and ACL removed a bunch of stuff when trying to get NAND to boot initially. ACL being the only dev working on NAND for the rhodium has left him a little behind on some of this stuff, and it's a lot of work for one guy to keep in his head :)

Anyway, I just updated the first post with the latest information. I apologize that it has been extremely quiet on my side lately. We have several massive projects going on that I am the PM on. Everything is on schedule and running great, but it's been very hectic trying to keep it that way, lol.
[Touch Pro2, Tilt 2 Android Development] Zambowie:
Lol I still dont know if i should test cuz I dont think i set up that fastboot stuff right. Any rhod210 users tried it yet?
[Touch Pro2, Tilt 2 Android Development] eu0741924381:
Do a little reading and see if that helps you make up your mind...
[Touch Pro2, Tilt 2 Android Development] Zambowie:
A little reading? Wha? If youre referring to that thread that says "ADB and USB" ummmm i posted that question before that thread was even published. Fenna read it now
[Touch Pro2, Tilt 2 Android Development] slycker:
On this note, I had written that guide with the SD installation in mind. I'd be interested to hear if anyone in the NAND community has experience with whether either the PDANet or HTCSync drivers work for them.
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
Once I had the drivers installed, NAND was no different than haret for ADB for me... It 'just worked' once I had the drivers installed.
[Touch Pro2, Tilt 2 Android Development] jamtoday:
i flashed recovery.img , and reboot , but stop blue screen

[dex] waiting for ARM9... STATE=0
[dex] waiting for ARM9... STATE=0
[dex] waiting for ARM9... STATE=0
[dex] waiting for ARM9... STATE=0

welcome to minipooploader
PLL ...

[AC[UCLOCK]:Switching VDD from 0 -> 7
nandid: ...
ptn 0 name="recovery" start=000000198 ...

...

udc_start()

my phone is rhod100 GSM ,how can i do ,i try hold end call key ,but not work , and can't use VOL up VOL down select , help me .
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
Sorry to say, but I don't think the NAND team have *quite* sorted out the issues with GSM. Please, be patient. There's workarounds for GSM, but it involves turning off the RIL basically - so the phone is useless as a phone.
[Touch Pro2, Tilt 2 Android Development] jamtoday:
Thank you, I thought I could take the test :(
[Touch Pro2, Tilt 2 Android Development] Walker Street:
Rhod100 GSM problem

I have a GSM rhod100 and get the exact same problem. I installed fastboot and recovery.img flashed fine (or so fastboot on the command line said ..."success"). However none of the keys work (it seems), so when I hold down power (or end call) to try to boot recovery, it just boots in to fastboot again (and again and again ... lol)
[Touch Pro2, Tilt 2 Android Development] m2maynard:
I have the exact same results as above on GSM ATT Tilt 2 (Rhod 400)
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
That's a RHOD300 FYI... the 400 is a Sprint worldphone with dual CDMA and GSM capabilities... and a 3.5mm jack. You definitely don't have one of those :p.
[Touch Pro2, Tilt 2 Android Development] m2maynard:
oh. yep. you are absolutely right. I remember thinking "that Rhod400 wasn't quite right" when I posted that but then thought, "no Rhod400 is right no need to check that." heh. :-} my mistake and why it doesn't hurt to include the friendly name when posting things like this.
[Touch Pro2, Tilt 2 Android Development] ghostrid3r:
Remedy - After a successful recovery.img flash via fastboot commands, pull battery and put it back then HOLD power button while booting. That will load the device into CWM (recovery.img) so you can flash OS, kernel, and root zips.

Confirmed to work on my RHOD-400 device

Let us know if pulling the battery works. :)

On a side note: Utilizing the CWM nand method with kernel and FX06 OS provided in OP, I lose SIP/VOIP calling functions in Sipdroid & GV over WIFI worked just fine with tinboot nand install. If anyone can shed some light on this issue, that would be great! :confused:
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
Yea I noticed I had to pull the battery as well.

I've never used Sipdroid, sorry... Google Voice seems to work fine tho.
[Touch Pro2, Tilt 2 Android Development] Starfox:
Have you tried CSipSimple? If that doesn't work either we can narrow it down to it being something on the build itself.

-- Starfox