[Q] Trying to switch from SD to NAND - Touch Cruise Android Development

I have been unsuccessfully trying to get Android from NAND working. I followed the guide by crobs808: http://forum.xda-developers.com/showthread.php?t=636024
Since I only used SD-method in the past I was not really sure whether or not my phone is unlocked. But since the RUU keeps failing with an "ERROR [262] : UPDATE ERROR" message I assume it is not. In bootloader mode I can see the following information:
POLA100
SPL-3.13.0000
CPLD-2
Additional information from Windows mobile:
ROMversion: 3.13.413.0 SVE
Radioversion: 1.59.42.15
Protokollversion: 25.85.30.07W
So then I tried unlocking using ImCoKeMaN's instructions from: http://forum.ppcgeeks.com/showthread.php?t=20370
I am under Windows 7 64-bit so basically I just ran Vogue_unlocker.bat as administrator and followed the instructions. But after it installed JumpSPL.exe on the phone I lost the activesync connection and then it seems like it failed. This method seems to be for Vogue but I thought maybe it works for Polaris as well, can anyone confirm this? Or point me in the right direction for Polaris owners.
Any hints on how to unlock the CID on Polaris so that I can install Android on NAND is appreciated.
Do you think I should upgrade radioversion as well?

Follow this guide for hard-spl and my guide for install.

Thank you! The guide you provided for hard-spl worked perfectly. Gonna grab some lunch and then try your installation guide.

Problems it seems
Followed your guide but something happens after step 13:
12. Flash from sd (press power button when asked)
13. reset device when finished
14. system starts and after some time on the screen will appear fast line and a message:
press Vol-up or D-PAD
BUT DON'T PRESS VOL UP OR DPAD IF YOU USE install-seq.sh IT WILL AUTOMATICALLY INSTALL THE SYSTEM.
if you do so after some second on the screen will appear install script founded and some information about installation.
The update seems to have worked, I got this on the screen:
POLAIMG.nbh - OK
OS - OK
Update complete
UPDATE SUCCESS
Then I do a soft reset and I get the standard "smart mobility" on the screen, after a little while the phone vibrates two times and then the screen goes black. I waited for a couple of minutes but the system never starts.
I tried redoing the update as well but same result.
I have no SIM-card in the phone, could that be a problem?
*UPDATE* Should I avoid using the "more settings" in NBH Editor? - YES
I tried with a new .nbh leaving "more settings" untouched. Now the system started and the install script installed my Froyo rom.

Change pannel type with nbh editor and retray

Related

Stuck in bootloader, please help!

Hello all,
Yesterday I tried to update my MDA Compact to qtek 1.06 and I saw to executables in the package:
getdevice.exe and enterbl.exe
I runned getdevice.exe for getting the device data for in the change.bat. That went oke, but out of curiosity I had to run the enterbl.exe, which made me go to the boot loader immediately. And now I'm stuck at the boot loader!
Whatever I do it won't boot to WME anymore! Soft reset, pressing the camera+power+reset, everytime it goes to the "Serial V1.00"screen.
When I remove and put back the backcover of the device (where the battery and sim are) it will go off and after a press on the power button it will boot to WME. But when I manually reset the device or when it automaticaaly reset itself after installing the ExROM tools, it goes back to the boot loader (Serial - V1.00) screen!
I even dumped the ROM with mmty to the SD card and flashed the device with that ROM again, but after it says Checksum is OK and I press reset it just goes straight to bootloader again.
I'm really out of clues of what to do. Can someone please help?
EDIT: When removing and putting back the backcover I can reset the device and it will boot back to WME so I can use it. But still when I softreset (with button or through software) it goes to boot loader. :-(
So using the backcover as a reset button is possible and does work, but it isn't very handy/usefull off course.
TIA
Regards,
Aurora13
Check the forum, the answer is there
Yes, you are still in bootloader mode and it's actually getting ready for you to flash.
Donno which part of it goes wrong, mine also have the same issue. What you need to do now is to restart your desktop pc / laptop (from the info I gathered from the forum). Then run that update thing again. This time, the same screen will appear saying it's trying to get the device data. Difference is, this time you no longer see the current version of ROM (as the Magician is in bootloader mode now). And you will see it show you the ROM that you going to upgrade to. Just follow the instruction, everything is straight forward. Hope this help.
cheers..
Thanks man!
You're the man cyberjaya!
It is working now, here is what I did (as told by cyberjaya):
- Rebooted my laptop
- Connected the MDA to the laptop
- Started the upgrade program of the qtek 1.06 ROM
- It didn't found my version, but it would let me update it to 1.06
- Flashing....(15 minutes is a LOOOONG time if you have to wait )
I did reset it a few times and it just boots normally!
Thank you ver much cyberjaya!
Regards,
Aurora13
No problemo
Am using laptop to flash also. Likely it's the USB hub thing (which listed in the "hardware devices" list). Read it somewhere, it's not recommended to flash using USB hub. Enjoy your new ROM!! .
cheers
I had a thought:
Isn't this the way to do a ROM upgrade without editing the ROM files?
Because it can't detect a different ROM and it will do the upgrade...
Or am I missing something?

Fatal error on HTC 710

HI,
I have a fatal error on my HTC S710. After switching the phone on I get 3 horizontal bars on top a red bar with VOX ONBL 1.34.000 in the middle a green bar with SPL 1.34.000 and the a blue bar with CPLD -04
I have tried to upgrade to 1.34 but no success
After about 30 hard reboots I can get the phone working for 5min and then it hangs again and the 3 bars pop up.
So I think I need to completely reinstall WM 6 but can't find the file on this site?
And what tool to use the flash the rom??
Thx,
Go to the HTC site and download the official ROM! http://www.htc.com/support/support.htm it's in the e-club section and is only for HTC devices (not SPV's etc).
BTW google "S710 rom" reveals a lot of results. You could try that first.
Tho,
thanks for your reply. Have Downloaded and upgraded the ROM from HTC E-club. However now the phone hangs completely can't if get it to start up normally. Tried Hard reboots soft reboots even pressing the menu buttons above the 1 and 3 key and then pressing the power button.
Where does it hang when booting? If you're able to get to at least the black HTC screen, then the ROM was written however might have bad blocks in memory.
Try a hard reset with SIM and SD out of the device, hold the two soft keys and press power, hit the Green call start button when it prompts you - leave the phone for at least 15 minutes to be on the safe side. Then flash this; ftp://xda:[email protected]_Vox_ARA_1.27.415.4_4.1.13.47_02.98.90.exe
and let us know what happens.
thx for the info h4waii.
However a hard reset does work. Acourding to the HTC technical helpdesk the boot loader is stuck, so it cant read the operating system files to boot the phone in to windows.
Also the Active Sync doens't reconises the phone any more.
H4waii,
I can get into the bootloader. I read on an other post that you said "If the ROM is corrupt, this is your best way of "recovering" your phone, if the ROM was flashed properly, after getting into the bootloader, run ruurun 0 and ResetDevice to boot it back into OS."
But how do run that ruurun. Still can't sync it with my laptop??
You need a terminal emulator, you can use MTTY. It's attached in the Vox USPL sticky and I will get you the link for the boot loader recognized commands.
EDIT: Here is a link to the USPL sticky that has MTTY attached: http://forum.xda-developers.com/showthread.php?t=330909
and here is a link to the the Wiki for Hermes boot loader, many of the commands will work on the Vox: http://wiki.xda-developers.com/index.php?pagename=Hermes_BootLoader
There is also a tool for the Universal that resets the DoC instructions, you might want to either give that a try or look at the command 'task 28 55aa'.
You do this at your own risk also, just wanted to throw that out there.

vox stacked at bootloader

Folks, really need help.
allready googled.. but i really behind from WinPhone update/recover process.
My vox suddenly stacked at bootloader (see attach)
How to exit from them?
Does my info still in phone, can i recover it?
If not how i can recover ROM ?
Can i just put some WM6.5 to SD card and recover it to phone?
(which wm6.5 rom is better? allso interest in Russian input support)
You still have access to the boot loader - as you see the confirmation of the initial SW stack components on the screen. Your device is not "bricked" yet
First step is to get back the OS which you need to get the USPL loaded temporarily. So get the stock ROM: just call the normal installation process while the device is connected to the PC.
Now follow the instructions of the cooked ROMs - I will not repeat them here.
So, i can`t get my data back, anyway ?
Well, if the device does not boot the OS, then also the FAT file system is not available where the files reside that hold the data. I have never seen that a new flashing of the OS would leave the other data intact or even accessible (if you knew methods to get them back from there). The initial boot of the OS after flashing will newly create all databases from scratch and thus kill all old items anyway - no hope here.
So quite frankly - yes all your data (on the device) are gone and the only hope is that you will at least get back the OS flashed and the device usable again.
thnx for the answers.
one question only - can i update ROM my vox from SD card only ?
(i have a problem with mtty connection (windows7) )
Not easily - look up the forum and wiki for the "goldcard method". It is much easier to connect to another PC and flash from there.
Once you did USPL you can flash easily from SD-Card (check the Wiki)!
He would need to permanently replace the stock-bootloader with the USPL first and for this he needs again a PC connection, or? I would leave the bootloaders onboard intact - as if anything goes wrong in replacing the bootloader your device is bricked for sure!
holly sh*** !
Today my phone start work normally without any reason !
And i undestood that the problem with some connections inside the phone.
I backedup all data that i need, then dismount everything and then mounted it back. During i played with that it backs again to bootloader on start few times.. now it works, but i still not found what the problem is... seems like something broken in motherboard or somethin like that
Hi,
i have the same problem.
the device doesnt start.
I have access to mtty in bootloader mode.
I can update the device, but after update iam again in bootloader mode.
No chance to leave.
Anybody an idea?
If your device does not boot at all (Green LED - then nothing):
- check your SIM Door, open and close completely to reset the switch inside the device.
Fixes if you are stuck in the bootloader (3 color screen):
1.) try to get the OS re-initialized (Cold Boot with keyboard):
- press both softkeys and keep them pressed until the last step - never release them
- press the power key to switch on the device
- wait for a prompt on the screen
- release the softkeys
- push the "Send Button" (green key)
- device should reboot and OS is initialized
If this does not work, next step:
2.) load a complete ROM of the operator - they usually contain all parts of the ROM (splashscreen, IPL, SPL, Radio and OS) and they match the security settings of the built-in SPL. This should bring back your device to operation state.
If this does not work you have a broken device or defective USB connection (PC port, cable or USB on the device).
If that worked, then you can start flashing custom ROMs using the USPL as the cooks describe their procedure.
ok,
i have two problems..
first the format command is not known in Bootloader mode
and the second.. i cant flash an other image than theImages from the provider.
Instructions below are not valid for VOX (they are for Tornado), please ignore
You have to enter when MTTY is connected:
1.) press enter -> you see the prompt
2.) enter "info 2" with out the "" and press enter
You get a list of information
3.) "format BINFS XY00000" where XY00000 is the calculated size of your ROM
3.) will not work if you miss 2.)
About loading cooked ROMs, please look up the relevant threads, they describe what to do in detail.
thanks
I came home and was reading your thread.
As i connected the phone and startet it... everything works fine without any impact
zerocool80 said:
thanks
I came home and was reading your thread.
As i connected the phone and startet it... everything works fine without any impact
Click to expand...
Click to collapse
In some cases - just remove battery, after plugging it on - windows should boot.
ruustart - should end any ruu comands and boot system - just connect device and inside mtty and after issuing password BsaD5SeoA type ruustart - will reset device.
m32
tobbie hav U seen "Key 1 is pressed ==> Clear HIVE !!!" in mtty ?
or "Soft1 and Soft2 are not pressed long enough" ?
m32
m32 said:
tobbie hav U seen "Key 1 is pressed ==> Clear HIVE !!!" in mtty ?
or "Soft1 and Soft2 are not pressed long enough" ?
m32
Click to expand...
Click to collapse
Don't remember, but I play more with Tornado currently. Vox is still on Stock ROM and bootloader is secured there (unless you flashed USPL). Google for the strings above in the XDA scope. HTC devices often share similar bootloaders.
tobbbie said:
You have to enter when MTTY is connected:
1.) press enter -> you see the prompt
2.) enter "info 2" with out the "" and press enter
You get a list of information
3.) "format BINFS XY00000" where XY00000 is the calculated size of your ROM
3.) will not work if you miss 2.)
About loading cooked ROMs, please look up the relevant threads, they describe what to do in detail.
Click to expand...
Click to collapse
hi ,
i also have same problem
but my mtty says invalid command
The SPL of the VOX is not allowing you to do this, possibly as there is no method to apply a Super-CID to this device afaik. Another method to bypass this however exists using the USPL, but I am not sure if this "format BINFS <size>" works on the USPL as well. It works ok on the stock SPL for the Tornado.
but i cannot use uspl
it says invalid vendor in while using RUU
so i must flash uspl

stuck during boot, do not know what to do

hi all...
...I hope that you can help. Some years ago, I have flashed my polaris from o2. i then got myself an iphone and some new computers (using vista now instead of xp), so that I do not have any of the old files that I used back then to flash the phone. my father was using the xda for quite a while now. however, suddenly the device is not working any more: if you turn it on, the boot screen will appear, but then it is stuck and nothing is happening (even no rom info in the lower right corner). also a hard reset doesn't help to overcome this problem.
what I am trying now is to flash it, because I guess (and hope) that this might help. But, to be honest, I completely forgot how this works. I downloaded an original rom from this website today, but I cannot flash it to the device (stuck at 0%, getting an communication problem error). If I turn on the phone with camera button pressed down, the tricolor-screen appears reading POLA200, SPL-3.13.0000, CPLD-2. what am I doing wrong? your help is greatly appreciated.
Try flashing the rom from the tricolour-screen just make sure at the bottom of the tricolour-screen it say's usb not serial.
You will only be able to flash official roms as you don't have a stock spl not hard-spl.
thanks. I tried this one from this forum: RUU_Polaris_o2_GER_1.24.207.2_withSplash_noRadio_schaggo_[fixed]
but it did not work.
however, I now downloaded the rom from the original o2-site and it is at the moment in the process of flashing it - let's cross fingers.
damn, it did not work. I mean, the flashing succeeded, but the problem still persists: if I start the device, the start-screen appears, but that's it - nothing happens afterwards, and after some seconds, the device turns itself off again.
what could that be?
Could be the battery if the device turns itself off,try booting with the charger or usb still in.Or flash hard spl and try a different rom.
hi all friends if you are stuck on 0% and u cant install spl then do this ,,,
You can try this:
1. Stop ActiveSync
2. Open Task Manager (press Ctrl + Alt + Delete) on your PC and
stop these two processes rapimgr.exe and wcescomm.exe
3. Plug in your device via USB. Your computer should be asking install a driver. Install and continue.
4. Now Run mtty and choose USB in 'PORT'
4. type "set 16 0" without the quotes to tell bootloader to boot the OS after reset.
5. type "task 8" to get your device formatted.
6. Now unplug your device and manually reset it.
i hope you will be happy after .. thanks

[Resolved] [Q] Flashing HD2 to Droid from WM6.5

Hello all,
I am kinda of new to the flashing of phones. Have been reading post and tutorials for three days now, have looked at countless pages containing instructions and videos on how to flash my HD2 over to Android. I have gotten as far as the HSPL4. Now I more or less have a brick waiting for an Android Rom. I was once on a page listing different roms with their known issues, as well as other details (have yet to be able to find that page again), I also understand that this question I am about to ask will have biased answers, but I am only trying to get some help in determining the best option for me when it comes to rom selection. The features I am most looking for is the availability to use most if not all android apps, download them from the marketplace, make and receive calls, surf the web, take pictures, take pictures, send and receive text/picture messages, play a few games, read the news, and the phone to recognize when I turn the thing sideways. Now I did notice that some roms have the detail of Sence:NO , I am taking that as meaning it does not have the HTC Sence included in the build? Am I misreading that? I thank all of you for your help, understanding , and patience with a noob. Thanks again in advance for all of your help.
Oh also now that I have the HSPL installed I am only getting the tri-colored screen. I have tried multiple times to restart and hold down the Volume Button when i turn it on and it still only goes to the tri-colored screen. Have I broken my phone?
Ok, I have let this thing sit for 3 days attempting to make connection with the phone and install HD2_Core_Droid_Desire_HD_V1.5_NAND_ONLY_LEO1024_TMOUS. I still am unable to get anywhere except the tmobile splash screen or the tri-colored screen. I have attempted to reinstall to the HSPL, with no luck. The following error is the error i received after 3 days of scanning:
An error has occurred
Read below for more information
Error Description: USB init failed
Info: .\RSPL\RSPL.cpp (736)
I am also getting the error
Error Description: Config load failed.
Info: .\RSPL\RSPL.cpp (725)
Error Description: CONFIG: can't open config file
Info: .\RSPL\RSPL.cpp (304)
when i attempt to install DFT Android flasher for HTC LEO
Any help would be gladly appreciated as I think I may have bricked my phone.
You do know you have to install MAGLDR after you have HSPL? If you have and you're getting that error - go to ActiveSync on your PC and untick 'Allow USB Connections'. Then try run the .daf again.
and make sure that you flash a current compatible radio BEFORE flashing magldr, or it will not work.
I am getting the 100% complete once I complete the MAGLDR113, and the phone restarts and stays on the T-Mobile splash screen.
Ok I mistated... I am not getting this to actually work.
You're using the RomUpdateUtility to flash MAGLDR right? Have you held down the power button while booting up to try get in to MAGLDR?
About the radio thing,
IF YOU HAVE A T-MOBILE USA phone (T-mobile at the top of the phone) make sure you never flash anything that has a 2.XX.51.XX as it will brick your phone.
Ok so far I have completed the Radio update (version 2.15.50.14). I have also completed the HSPL4 - 3.03.HSPL. Now I am stuck on the MAGLDR update. I have tried 113 as well as 110. Niether is working. I can still only get to the tri-colored screen. I have tried multiple times by removing the battery holding the volume down key, holding the power button, or both at the same time with the recult, either the tri-colored screen(vol. down, or vol. down and the power button, the power button alone boots to the TMO splash screen and just sticks there). I am very appriceative to all who have attempted to help. I am presently looking for a new MAGLDR to download and attempt again.
I completed the install of HD2_Core_Droid_Desire_HD_V1.5_NAND_ONLY_LEO1024_TMOUS and this is the message I received on the program window:
Congratulations! Installation successfully completed.
But then when the phone reboots I get the screen that states
aMAGLDR V1.13
Build: Feb 1 2011 03:46:07​by Cotulla 2011​--------------------------------------------------------------------------------------------
Boot Android from NAND
Android load at 11800000
from NAND
yaffs2 part is /boot
Load zImage
NAND kernel failed to open
But out of all of this I am atleast able to get to the bootloader screen with the 12 options. so I am hoping we are almost home with this operation. Once again thank you for your help.
The NAND kernel is just an error because it might not of flashed correctly. Go to the USB Flasher option in MAGLDR and then run the .daf file on PC. It should flash and restart and boot to Android.
I wanna know how though, how did you flash MAGLDR with HSPL 3.03? You're supposed to flash 2.08.HSPL from the HSPL4 drop down menu.
your guess is as good as mine I have become so lost reading posts doing this doing that..lol this has become harder than writing a prog in c#..(as to how i got 3.03 to install)
Thanks to all who have helped... I have completed the install after reinstalling the ROM...

Categories

Resources