I bought a used MDA I recently and was quite happy with it for a while. First bought a 512MB SD for it and installed TTN5. Then noticed that I needed more space when I was in Belgium and wanted the Maps for France and got me a 1 GB SD.
I must tell a story first which also occured with the 512 MB SD (but I belileve it isn't SD related anyway): During fiddling with the TTN5 installation, Active Sync and all that (removing programs out of memory or deinstalling them) , it occured several times that the MDA got so slow in response that I had to do a soft reset. The effect when it was slow, was that clicking a menu item took about 5 seconds until the respective action occured. Not only menu items, also action in this bubble game - name escaped me for the moment - was in the same range of slowness.
Doing a soft reset cured the problem.
Now it happened that when I was in Belgium I had connected the cradle to my notebook and was dumping the France maps over USB into the unit. This took an hour or so and I left the setup unattended.
When I came back the notebook had powered down (idle mode). I took out the MDA from the cradle and wanted to switch it on but it didn't react on the on-switch.
Putting it back into the cradle suddelny lit the display and the T-Mobile screen appeared.
From then on the havoc started. I did a soft reset to no avail. A hard reset - nothing.
Accidently (or should I say intuitively) - without knowing that this combination existed - I
pressed the on switch and the soft reset at the same time and got into some strange
Wallaby bootloader which didn't do anything, I think. It timed out or something.
Anyway, I put back the MDA into the cradle, switched it on and left it there with the T-Mobile screen on.
After minutes, may be 10 minutes or so a WM 2003 initial screen had appeared which invited
me to do an initialization.
I went through the interactice dialog and suddenly had a working WM 2003 but is was again
very slow in the menu action.
Also shutting off (switch off) the unit worked but then I couldn't switch it on again.
So in a nutshell, my unit is messed up somehow and I want to get it back into a working state
looking for help in this forum.
How should I proceed now?
flash it with the latest ROM first. If that doesn't work send it off for repair.
saldous said:
flash it with the latest ROM first. If that doesn't work send it off for repair.
Click to expand...
Click to collapse
Thanks. Since I'm new to the matter: I remember that the version number of the T-Mobile screen
had - at the times it was working - some extra letters above the 4.01.19 (a G and some more
letters). These are gone as if some backup ROM is activated after the (hard) reset (?).
The person who sold me the MDA has unbranded it as she said. How do I get the ROM unbranded? When I download it from T-Mobile it is branded for T-Mobile, isn't it?
I got told of a site "lumpisteffan" which I visited already. Do they
carry the ROM I need? And do they have the instructions to do that or can that be found on this site here? Excuse my ignorance at the moment.
You could use nearly any rom of the kitchen to flash your device.
Because you have the 4.01.19 ROM installed on your device, you have to flash your device using a SD-Card.
Instructions how to do this could be found here in the forum, or in the wiki.
http://wiki.xda-developers.com/index.php?pagename=Wallaby
When you restart your device, what is shown on the Bootscreen, where also the 4.01.19 appears. The 2 Other lines, what do they contain?
Slowing down your device on using it for some time could be a memory outage.
If you "close" your running applications by pressing the (X) on the top of the screen, they are not closed, but put in the background. So they do use memory..... Just as little hint for you...
Stefan
LumpiStefan said:
You could use nearly any rom of the kitchen to flash your device.
Because you have the 4.01.19 ROM installed on your device, you have to flash your device using a SD-Card.
Instructions how to do this could be found here in the forum, or in the wiki.
http://wiki.xda-developers.com/index.php?pagename=Wallaby
When you restart your device, what is shown on the Bootscreen, where also the 4.01.19 appears. The 2 Other lines, what do they contain
Stefan
Click to expand...
Click to collapse
Thanks, Stefan. That's of great help. Probably gotta get me a card reader for my desktop first
or could I use my camera also? Probably I can.
> The 2 Other lines, what do they contain
It is puzzling me that I don't see any other letters or lines obove or beyond the line
4.01.19 in the bottom right corner.
But will have to look again at the device later when I have it with me after lunchtime.
LumpiStefan said:
You could use nearly any rom of the kitchen to flash your device.
Because you have the 4.01.19 ROM installed on your device, you have to flash your device using a SD-Card.
Instructions how to do this could be found here in the forum, or in the wiki.
http://wiki.xda-developers.com/index.php?pagename=Wallaby
When you restart your device, what is shown on the Bootscreen, where also the 4.01.19 appears. The 2 Other lines, what do they contain?
Slowing down your device on using it for some time could be a memory outage.
If you "close" your running applications by pressing the (X) on the top of the screen, they are not closed, but put in the background. So they do use memory..... Just as little hint for you...
Stefan
Click to expand...
Click to collapse
Regarding the lines above 4.01.19. They are indeed there (must have had hallucinations).
Comment (reedited):
I noticed that after a soft reset the T-Mobile screen appears with only
4.01.19 in the bottom right. Then after a few minutes the G and R are there.
It reads:
G
R
4.01.19
in magenta letters/digits.
Thanks for the explanation about possible causes for the slowness, but
it is already slow as soon as I have gone through the WM2003 initialization and want to chosse the first dropdown menu item. So no programs in memory at that point in time.
Another effect I forgot to mention:
The first time I put the XDA into the cradle the "charging" LED is red.
After some minutes, when the T-Mobile screen is there it is off.
Normally it is immediately orange when the devie is in the cradle.
I read in another thread that this might be an indication for a blown fuse.
Or blown fuses.
Since that happened in Belgium at the coast in a vacation area it could well be that power spikes have lead to this illbehaviour.
LumpiStefan said:
You could use nearly any rom of the kitchen to flash your device.
Because you have the 4.01.19 ROM installed on your device, you have to flash your device using a SD-Card.
Instructions how to do this could be found here in the forum, or in the wiki.
http://wiki.xda-developers.com/index.php?pagename=Wallaby
When you restart your device, what is shown on the Bootscreen, where also the 4.01.19 appears. The 2 Other lines, what do they contain?
Slowing down your device on using it for some time could be a memory outage.
If you "close" your running applications by pressing the (X) on the top of the screen, they are not closed, but put in the background. So they do use memory..... Just as little hint for you...
Stefan
Click to expand...
Click to collapse
Hi Stefan,
I downloaded the file 4.01.19_GER.exe from the site I was pointed to when visiting your site - I just wanted to go through the steps with an unmodified ROM.
I verified the MD5 sum ok, copied to 17 MB file to my notebook. I had the MDA in the cradle and connected via USB. MS Active Sync had a connection to the device.
At this point I wonder how that would be done with the XDATools OSImagetool which requires to name the source location of the ROM Image. But what I downloaded from your site is an installer .exe.
Anyway when I run the 4.01.19_GER.exe it tells me "Please plug the power adapter in your pocket PC".
Could this be a sign for the malfunction of my device?
How do I get the ROM Image ?
OK. I found that your kitchen builds ROM images while the link to the original ROM obviously delivers the full installer.
Will report further progress.
Looks like your fuse has been killed, or you have problems with your Radio Stack.
Flashing a new ROM wouldn't help to fix that problem......
You could try to repaor the Radio stack by following these instructions:
http://wiki.xda-developers.com/index.php?pagename=Wallaby_HT_GSMError
If you have a exe-file and you want to have a nb1/Nbf File, you have to extract the exe useing winzip.....
Stefan
LumpiStefan said:
Looks like your fuse has been killed, or you have problems with your Radio Stack.
Flashing a new ROM wouldn't help to fix that problem......
You could try to repaor the Radio stack by following these instructions:
http://wiki.xda-developers.com/index.php?pagename=Wallaby_HT_GSMError
If you have a exe-file and you want to have a nb1/Nbf File, you have to extract the exe useing winzip.....
Stefan
Click to expand...
Click to collapse
Since the connection via USB sometimes seems to work I tried the XDATools stuff, got me a .nbf file.
I tried the tools intuitively by clicking on the start.bat file.
It told me it had no .nbf file, so I created on from your site.
Thank it told me it didn't have the file in the English subdirectory.
OK, I put it there. The start.bat seems to invoke a adaptrom program. After that the English folder was named German. But some program still requires a GetConnectionType.dll which ain't there.
Anyway, what is pointing to a blown fuse is that I get with all these USB uploaders I'm getting this error telling me I should connect the power cable to my device.
I opened my device and bridged the one fuse (near the lower navigation button) to no avail. Didn't try the other fuse though since I thought that one would be for the piggy back battery, or is it also responsible for the power coming from the cradle?
Could it be my cradle is broken? Ah no, when I insert my spare MDA (the one with the broken display) the orange led lits immediately after inserting the device.
Related
Hello there.
I´m really new but certanly i have read a lot on the forums. Still I have managed to mess everything once more.
I have a wizard love G4
ROM Version 2.26.10.2.wwe
Rom date 06/07/06
Radio 02.25.11
Protocol 4.1.13.12
ExtROM 2.26.10.105
Messed around with the splash screen from equinoxe and to make it work i needed to update the RUU from 2.00.1 that was on the installation files to RUU 2.5.2 that was extracted from an HTC.exe rom update download.
Finally it worked just fine.
Then, i decided to give it a go on the SoftSPL procedure in order to install the Black Diamond 2.0 touch rom on my phone so I placed the downloaded "Safe ROM" on the ROM folder. Started the application and everything was looking good. Then the RUU came up with the 2.00.1 version so I was a little worried, but then the so called white screen on the cell phone started but with a progress bar (how convenient)... I´m not sure if i was supposed to see the progress bar at all on the cell phone or just a full white screen.
Anyway, after 10 minutes give or take, the bar got to 100% and the pc software said Congratulations... but then the cell phone automatically restarted and inmediatelly it went to the bootloader three color screen.
I proceded with a hard reset before anything, right on the bootloader screen, (radio and voice buttons hold with reset button and then the send button accepting the restore to factory). Then the phone restarted but also in bootloader screen. So i decided to turn it off by holding the power button for a while. It did turn of, but this is where everything goes crazy... it does not turn on again... it even don´t show no led light when connecting the phone to the usb or the ac wall adapter...
This happened to me a few days ago using the shelltool with the same Black Diamond 2.0 Touch rom but probably i made a different mistake back then.
Anyway I removed the battery and the sim card and reinserted everything again, even tryed it out without the battery and direct connection.
When this happened to me the first time, I just leaved the phone without the battery all night and on the next day it turned on but on the bootloader so I drove it to our local unlocker that managed to re-install the wizard-love once again.
I´m wondering if anyone is having this same issues, or something similar.
Probably i should have ask first if the Black Diamond 2.0 was a safe g4 rom, which i´m not sure but won´t dare to try it again.
I had the same problem.
i'm afraid using the SoftSPL now :S
Try the TNT 5. I used soft spl to install tnt 5 from the wizard love rom.
http://forum.xda-developers.com/showthread.php?t=328917
They have a touch version u can think about.
Yes!!!! I love it now!
I downloaded the last SoftSPF. Now it runs a little slower on the first checking part but then it turned the screen all white!!!! Beautiful scary little issue that fortunatelly equinoxe stated on the flashing instructions.
Then I went for the TNT 5.0 Professional with HTC Home Plug-in on my CID LOCKED QTEK-9100 (But that it´s actually looking exactly like a 8125 Cingular), and it did it!.
One question tough... I´m running windows vista on my personal computer so I flashed the cell phone on another computer at my office that has windows xp, but still inside the TNT 5.0 Professional installation pack there is a RUU that states Windows Vista Update Utility. I´m wondering if this would actually run under vista... If so, then I believe that you can make SoftSPF also run under vista by just changing the 2.exe file on the SoftSPF compilation with this Vista_ROMUpdateUtility.exe file on the TNT 5.0 Professional compilation release.
Anyone care to try?
Probably I will be trying to flash a new radio with this RUU Vista utility under vista, to see if it flashes... If it does, then i don´t see why you can´t run try it out under vista.
I´m attaching only the RUU for vista so you can put inside any nk.nbf with it to use it under vista.
danielvelez said:
Hello there.
I´m really new but certanly i have read a lot on the forums. Still I have managed to mess everything once more.
I have a wizard love G4
ROM Version 2.26.10.2.wwe
Rom date 06/07/06
Radio 02.25.11
Protocol 4.1.13.12
ExtROM 2.26.10.105
Messed around with the splash screen from equinoxe and to make it work i needed to update the RUU from 2.00.1 that was on the installation files to RUU 2.5.2 that was extracted from an HTC.exe rom update download.
Finally it worked just fine.
Then, i decided to give it a go on the SoftSPL procedure in order to install the Black Diamond 2.0 touch rom on my phone so I placed the downloaded "Safe ROM" on the ROM folder. Started the application and everything was looking good. Then the RUU came up with the 2.00.1 version so I was a little worried, but then the so called white screen on the cell phone started but with a progress bar (how convenient)... I´m not sure if i was supposed to see the progress bar at all on the cell phone or just a full white screen.
Anyway, after 10 minutes give or take, the bar got to 100% and the pc software said Congratulations... but then the cell phone automatically restarted and inmediatelly it went to the bootloader three color screen.
I proceded with a hard reset before anything, right on the bootloader screen, (radio and voice buttons hold with reset button and then the send button accepting the restore to factory). Then the phone restarted but also in bootloader screen. So i decided to turn it off by holding the power button for a while. It did turn of, but this is where everything goes crazy... it does not turn on again... it even don´t show no led light when connecting the phone to the usb or the ac wall adapter...
This happened to me a few days ago using the shelltool with the same Black Diamond 2.0 Touch rom but probably i made a different mistake back then.
Anyway I removed the battery and the sim card and reinserted everything again, even tryed it out without the battery and direct connection.
When this happened to me the first time, I just leaved the phone without the battery all night and on the next day it turned on but on the bootloader so I drove it to our local unlocker that managed to re-install the wizard-love once again.
I´m wondering if anyone is having this same issues, or something similar.
Probably i should have ask first if the Black Diamond 2.0 was a safe g4 rom, which i´m not sure but won´t dare to try it again.
Click to expand...
Click to collapse
Your screen should turn white, completely white... Not white with a progress bar. That is the RUU that you were seeing. Haret.exe cause the screen to crash and then it turns completely white. THIS IS NORMAL.
Try using this version: SoftSPL - RC1. Before I got a G3 and CID unlocked it, this version of SoftSPL worked for me time and time again.
Thank Dan.
Actually the new SoftSPL worked like a charm. The screen went blank as a crash, and 10 minutes later i was on a TNT 5.0 Professional Qtek.
danielvelez said:
Thank Dan.
Actually the new SoftSPL worked like a charm. The screen went blank as a crash, and 10 minutes later i was on a TNT 5.0 Professional Qtek.
Click to expand...
Click to collapse
No problem... I know before I got my hands on a G3, thats exactly what I used to upgrade roms.
Hi
When I turn on my phone all it shows is red, green, blue and white stripes across the screen with the following text:
ROSE100
SPL-1.54.0000
MicroP-Rose (LED) v10
MicroP-Rose (key) v5
PCBID 0x80
RID 0x0
At the bottom of the screen it also says "Serial", but displays no actual serial. Please see attached pic.
Please help guys. Problem initially started when phone collected dew on cold morning (camping).
Thanks!!!
You seem to be in the "flash screen".. I did that on my phone by accident, pressing power and one of the volume buttons.. Try pulling the battery out, put it back and see if it starts normally.
I have the exact same problem. Mine happened all of a sudden for no reason after turning my phone off and trying to turn it back on. Please post if you find a solution
Well, you can try to reflash your ROM. Many official ROMs can be found here.
Hi, I got the roms, but where can I read how to put the new one on my phone using my computer?
Ok, I got it I just run the .exe file to update my rom. However, there is just one problem, it says you should connect activesync to your phone. How tf do I connect activesync as my phone does not load any OS?! I tried without activesync but it doesnt work - it freezes on 0% update and after a while it runs some kind of recovery steps. So how do I get pass the activesync thing? Thanks
You can't upgrade ROM via activesync if u don't have acces to windows mobile, you can do it only from SD card.
Here http://www.megaupload.com/?d=M7OEOF2N (pass: xda) you find a Rose service manual and at the page 45 you find "ROM Image upgrade thru SD card" ...it's not complicated, read carrefuly.
Ok I read it but when I press the power button for the second time it says "No image file". I renamed the file to RoseIMG.NBH. What am I doing wrong?
I don't know what are you doing wrong ...try to rename the file to "ROSEIMG.nbh". Where did you download the ROM? ...I recomend you to put the same ROM you have on device because you don't have installed HardSPL (and I don't know if you can install it from SD card). Here http://forum.xda-developers.com/showthread.php?t=599520 are the officials roms for S740.
PS: I never tried this method on S740, I do it once on tytn II and works perfectly.
Here is how I got it to work:
Left it in the boot mode with the colorful screen until the battery is decharged enough, then tried to put it on again and it automatically turns off. So I put the USB cable in it and walla it started loading the battery and it turned on automatically and loaded WM. However, I still can not flush my ROM even through activesync.. but I am glad I can use it again.
something many forget with this fault, and I have seen quite a few is it is often not a rom issue but a hardware problem... in this case it may be a faulty up volume button, or maybe the plastic cap has shifted keeping the button held down, does the button still click ok?
The monet was a swine for the camera button giving up the ghost and doing nothing but dropping to boot loader......
Hi all,
I've got a problem with my hermes phone which I can't solve by my own I think :
My device gets stucked while booting. It just shows a "htc smart mobility" screen and displays the various red numbers on the bottom for some seconds (as usual I think). But it's not going any further (waited for about 20 minutes).
I flashed the "Hermes.DarkVisions.v5.17.23017.Manila" rom over my exisisting "Schap's 4.22" rom a few hours before. The rom was running good. Then I executed the "kill em all" app by mistake, which can be found in the accessory folder as far as I can remember. Then the phone began to work very slowly so I decided to restart it. And now its not really working any more.
By connecting the phone with my pc and trying to flash a new rom, I get the RUU Error "200 INVALID UPDATE TOOL" - what does this mean? The auto detection of the current bootloader obviously doesn't work due to no running windows mobile.
Is there any chance to flash the phone without a running windows mobile? Or what else can I do to get the current rom "Dark Visions" running again?
Thanks a lot for your help,
Michael
Press The Power, The ok button (usually found on the left side) and The reset button using your pen until this rainbow coloured thing comes up.
Plug it into your USB and then reflash your ROM, also don't forget to upgrade your radio as you will need it to stabilize your custom ROM which you will find under wiki part of this forum. Just search "Hermes Radio" and click the first thing you see.
Now your device should be back to life again.
OK, so I've been reading the Common Upgrade Problems on the wiki, and I saw this:
Important : Windows VISTA users need to make a change to their system to successfully use many ROM packages. See Mr. Vanx's guide here.
Click to expand...
Click to collapse
Since Mr.Vanx's website was taken down, I ask you what are the changes i need to perform and if I need to apply them to Windows 7.
Best wishes!
Any help in here?
Please, i have the same trouble. I didn't work with Windows 7. Does Anyone know a solution?
hey guys ...
there is the whole story
My friend's HD2 device was working in strange way, When restarting it gives a white screen and the HTC logo and freeze at this screen and then after a large number of re-starting it works, but when re-restart it again it return to the white screen
After a Hard Rest through the sound buttons the top and bottom were formatted but the device remain standing at the white screen after a Hard
the only solution to me was upgrade to new Rom and after read in the forum that This problem can be a lack of Compatibility between the Rom and the radio, but I think that the device had not been updated b4 by a lack of awareness of my friend, and then check the SPL version ,it was 1.42.000 (still locked) then try to ulock it by HSPL2_RUN as posted in some thread
it done right and the message "we hacked .." and enter boot-loader and checked it became 1.42.spl then I tried to upgrade by the following Rom:
RUU_Leo_HTC_WWE_GCC_1.43.488.1_Radio_Sig ned_15.26.50.07U_2.04.50_22_2_Ship
When updating the device whenit reached 9% did not complete the upgrade untill the upgrade process stopped by itself so I did restart the black screen appeared within a triangle inside the exclamation point.
now I started to be panic, and then search the net and found the advice from someone to use Task29 before the upgrade and when I run the program worked fine and after restarting the white screen returned with the HTC logo inside
I tried again to upgrade the same Rom and returned the same result ,searching again and found many advise to upgrade the SPL to version 2.0 which is recommended by most members
After the successful conversion of the SPL took off the device and swithched to boot loader to make sure the validity of conversion and the back of the version then after restating the white screen appeared and when I tried to reboot again the device turned off, I tried several times and did not work I said maybe the battery and when i connect the charger it did not ship and the orange led did not spark, tried the USB method but same result
I tried another charger and a another usb cord and it did not work and I check the battery by an electronics specialist, He assured that the battery is fully charged.
And now the device does not function at all, not even shaking when running and screen or charging
please guys i need ur argent assistance ...even a thought may help
Note: This is not the first time for me unlocking and flashing thin , my last devices was: JAM - k-jam - Jazjam - Omnia (current)
king roro said:
hey guys ...
there is the whole story
My friend's HD2 device was working in strange way, When restarting it gives a white screen and the HTC logo and freeze at this screen and then after a large number of re-starting it works, but when re-restart it again it return to the white screen
After a Hard Rest through the sound buttons the top and bottom were formatted but the device remain standing at the white screen after a Hard
the only solution to me was upgrade to new Rom and after read in the forum that This problem can be a lack of Compatibility between the Rom and the radio, but I think that the device had not been updated b4 by a lack of awareness of my friend, and then check the SPL version ,it was 1.42.000 (still locked) then try to ulock it by HSPL2_RUN as posted in some thread
it done right and the message "we hacked .." and enter boot-loader and checked it became 1.42.spl then I tried to upgrade by the following Rom:
RUU_Leo_HTC_WWE_GCC_1.43.488.1_Radio_Sig ned_15.26.50.07U_2.04.50_22_2_Ship
When updating the device whenit reached 9% did not complete the upgrade untill the upgrade process stopped by itself so I did restart the black screen appeared within a triangle inside the exclamation point.
now I started to be panic, and then search the net and found the advice from someone to use Task29 before the upgrade and when I run the program worked fine and after restarting the white screen returned with the HTC logo inside
I tried again to upgrade the same Rom and returned the same result ,searching again and found many advise to upgrade the SPL to version 2.0 which is recommended by most members
After the successful conversion of the SPL took off the device and swithched to boot loader to make sure the validity of conversion and the back of the version then after restating the white screen appeared and when I tried to reboot again the device turned off, I tried several times and did not work I said maybe the battery and when i connect the charger it did not ship and the orange led did not spark, tried the USB method but same result
I tried another charger and a another usb cord and it did not work and I check the battery by an electronics specialist, He assured that the battery is fully charged.
And now the device does not function at all, not even shaking when running and screen or charging
please guys i need ur argent assistance ...even a thought may help
Note: This is not the first time for me unlocking and flashing thin , my last devices was: JAM - k-jam - Jazjam - Omnia (current)
Click to expand...
Click to collapse
Hi,
Since you have enough experience in flashing custom ROM, I would suggest you the following ways:
1. Make sure battery is at least 50% and the battery pins are not bent
2. Format your micro sd card to fat 32
3. Find and download the CORRECT STOCK ROM. You can download it from htc website if your hd2 is non branded, or you can download it from your carriers website if your hd2 is a branded one. Make sure the downloaded file is not corrupt due to download process
4. Extract the downloaded file using 7 zip or winrar. Find the file named: RUU_signed.nbh Then, rename it to: leoimg.nbh then copy it to the root directory of your micro sd card
5. Go into boot loader and follow the onscreen instruction. If therenis no hardware issue, it should work.
Good luck ...
thanks m8 but I've checked the pins and changed the battery with fully charged one ..
but it's no boot loader mode ... its completely off
thanks 4 ur support
Not offering solution, just an observation,,,, hanging at HTC screen and only occasionally booting, plus flashing hanging at. 9% is a bad sign, sometimes associated with a stuck radio, and/or/caused by thermal issues.
Try chilling the phone with stock nbh ready to go on SD card, in sealed bag in fridge/freezer for a while, then try to SD flash.
If flashing starts, (white screen blue writing) keep an eye out for "rsa radio fail" or similar.
if the flash goes well, but then later the problem returns, it's pretty conclusively hardware.
thanks buddy for the advise but as I mentioned b4 ...
the device doesn't boot anymore ... and yeah it's Hardware bug I think.
best regards
Hi, think I know a bit of what I'm doing, read all I could, etc.
W7 laptop, SD SD with HP format, RHOD100.
(Can get serial # from Nexus 7 with ADB install, can reflash WM from SD, etc)
USB cable to computer.
I can 'flash' (update image) new Android RHODIMG.NBH to phone, I get filled progress bar, and then Update Complete, UPDATE SUCCESS and phone will not cut off (stuck in bootloader?) I do manual reset button.
Then I can 3 finger reset (SEND, END, + ON) to get tri-color, and then VolUp option. (So far, this is just like WM reflash) I push VolUp.
Screen goes to "Restore... Waiting for completed" and unfilled progress bar - and that's it. At this point, other resets can get me tricolor with USB, white HTC with NO radio, version, etc, and this waiting screen.
(I can use same process and get right back to WM.)
Where is my error?
THANKS!!
You can't flash Android with USB. SD is the only way to flash the NBH for Android.
Do you see the blue boot loader screen?
(I've also got the image for android on SD, just not getting there...)
I never get a completely blue screen (get tri-color), I go exactly as far as I mentioned - 2nd progress bar with no progress.
Using these instructions and downloaded files... http://forum.xda-developers.com/showthread.php?t=1566955 stuck at step 10 or 11 or so.
THX
tshephard said:
(I've also got the image for android on SD, just not getting there...)
I never get a completely blue screen (get tri-color), I go exactly as far as I mentioned - 2nd progress bar with no progress.
Using these instructions and downloaded files... http://forum.xda-developers.com/showthread.php?t=1566955 stuck at step 10 or 11 or so.
THX
Click to expand...
Click to collapse
Did you unlock your phone?
Unlocked long ago, olinex or something similar. Been trying various roms for years with no problems, played with SD android for awhile, wanted to try NAND.
I have good SDK, etc, put image on SD, phone finds it, first loading bar looks great, reboot, second loading bar never starts.
Do you guys never see 2nd progress bar ("Restore... Waiting for completed") - is my fault before that? Is there a better set of instructions that what I'm using?
tshephard said:
Unlocked long ago, olinex or something similar. Been trying various roms for years with no problems, played with SD android for awhile, wanted to try NAND.
I have good SDK, etc, put image on SD, phone finds it, first loading bar looks great, reboot, second loading bar never starts.
Do you guys never see 2nd progress bar ("Restore... Waiting for completed") - is my fault before that? Is there a better set of instructions that what I'm using?
Click to expand...
Click to collapse
So you flash the NBH... and it's never flashed successfully? Not sure what you mean by "second progress bar"... there's only one when you flash the NBH via SD.
OK - now we're talking!
I definitely see a second progress bar that never starts under "restore, waiting for completed" on a whitish screen as above.
Is the RHODIMG.NBH from that instruction set the correct one?
I will try downloading again and moving to SD again in case of file fault.
THX for helping...
tshephard said:
OK - now we're talking!
I definitely see a second progress bar that never starts under "restore, waiting for completed" on a whitish screen as above.
Is the RHODIMG.NBH from that instruction set the correct one?
I will try downloading again and moving to SD again in case of file fault.
THX for helping...
Click to expand...
Click to collapse
I guess I'm still not following.
Have you ever flashed via SD? The process is really quite simple. Just place the RHODIMG.nbh file at the root of the SD, and put the phone in bootloader mode. It should pickup the file and offer to start the flash.
Yes, and since I tried this I have also successfully flashed back to WM by SD, numerous times now.
I am not successful at flashing and then loading the small .nbh for Android
Am trying new download now...
tshephard said:
Yes, and since I tried this I have also successfully flashed back to WM by SD, numerous times now.
I am not successful at flashing and then loading the small .nbh for Android
Am trying new download now...
Click to expand...
Click to collapse
So to get things straight, you downloaded this file and put it on the SD. Now when you load it, you won't be able to get it to load using the recovery. Recovery is for Windows original files only as far as I get that.
Instead you just press and hold the volume down button while powering on the device. After you see the tri-coloured screen you can let go. You will get prompted with a white screen. On this you'll see:
Now the rhodimg.nbh is detected and by pressing the power button you can flash it. (or press volume down to cancel and return to the tri-coloured screen) After it said OK/Succesfull you remove the battery or press the reset button, after this there's no further steps, you just let it power on and you get a BLUE screen with some white texts called the LK bootloader / minipooploader by [ACL]
Here's a short instruction video to explain what I typed.
Al - THX for joining in!
That's the file (only one I can find), I do exactly as described, but at "battery or press reset" I get a white HTC (like would have 4 files listed on WM) that cuts off after 4 seconds, a three button push gets me a reload with no progress.
I made films...
files on SD - http://www.youtube.com/watch?v=ZbK8aWh9378&feature=youtu.be
process - http://www.youtube.com/watch?v=01Uq1dqtydE&feature=youtu.be
that show reset and 3 button reset (USB in here, same USB out) (Also, fresh solo Task 29 from RUU advanced...)
Any clues anyone?
(Could RHODIMG.NHB be bad on server?)
Not sure why you are doing a hard reset after you load the android NBH. Skip that.
Just let it load.
The instructions and post 11 above indicate reset.
I'm trying just leaving it at the Update Complete UPDATE SUCCESS progress bar now....
Nope - that just sits there after RHODIMG.nbh - OK, OS - , and UC/US,...
tshephard said:
The instructions and post 11 above indicate reset.
I'm trying just leaving it at the Update Complete UPDATE SUCCESS progress bar now....
Nope - that just sits there after RHODIMG.nbh - OK, OS - , and UC/US,...
Click to expand...
Click to collapse
Just a regular reset, not a hard reset is what I think they are meaning. I have lost count of the number of times I have loaded android onto my device, and I have never ever done a hard reset after the initial nbh load.
When I load android on my rhod400 it always hangs at the update success screen from the initial nbh load. Try just popping out the battery (and putting it back in) and letting it boot normally after you see the update success screen from the android nbh. You should get to a blue boot loader screen.
That (simple on or reset button) after android.nbh success gets me:
a white screen with HTC (that would normally [WM] fill in with b,r,s,something - 4 ?file versions) for 4-6 seconds, and then off and blank. Battery yellow will cycle 80% on. Subsequent on times out (HTC white) and off as above.
Have you loaded recently with the current file?
tshephard said:
That (simple on or reset button) after android.nbh success gets me:
a white screen with HTC (that would normally [WM] fill in with b,r,s,something - 4 ?file versions) for 4-6 seconds, and then off and blank. Battery yellow will cycle 80% on. Subsequent on times out (HTC white) and off as above.
Have you loaded recently with the current file?
Click to expand...
Click to collapse
Unless you're using some old file, yes I have flashed recently. Just flashed a TP2 the other day...
https://code.google.com/p/rhodium-nand/downloads/list
That's where you're getting all your NAND downloads from yes? Please ensure you have the newest stuff. This part is really the "easy" part. Just need to be SPL unlocked, then flash .nbh via SD. Seriously, that's the easy part... the hard part is getting your computer to recognize the phone in fastboot mode, and flash the recovery image - that's the step I always seem to have issues with.
This is an video from a Rhod 210, but it gives you a good idea what to expect. Useful info starts around 7:00.
http://www.youtube.com/watch?v=_qNCHqGPofI
Redid it all - exactly per video... fresh downloads. etc...
Where video shows carrier splash, then 4 circular buttons, and then blue with text, I get white HTC for 5-6 seconds and then off.
Just to be sure, since original thread evolved...
Mine is a RHOD100, SEA Roms work fine, SPL 0.85 olinex (AT&T freqs, they think it's a Tilt 2)
Seems it was only some phones early...
tshephard said:
Redid it all - exactly per video... fresh downloads. etc...
Where video shows carrier splash, then 4 circular buttons, and then blue with text, I get white HTC for 5-6 seconds and then off.
Just to be sure, since original thread evolved...
Mine is a RHOD100, SEA Roms work fine, SPL 0.85 olinex (AT&T freqs, they think it's a Tilt 2)
Seems it was only some phones early...
Click to expand...
Click to collapse
I did not intend for you to follow the video to the letter. It was just to give you an idea what to expect.