Related
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?
Any Help Appreciated. Anyone ever seen this type of "Brick"?
After flashing a new ROM (Tilt XDA-Live v1.0 - fully flashed to 100% and said finished), the device won't boot. It just gets stuck in an endless loop. It trys to boot, shows the AT&T screen, then reboots/resets back to the beginning before getting to the Windows mobile screen.
The only way to get it to stop the loop is to pull out the battery. Put the battery back in and power on and you get the loop again.
I have loaded HARD SPL (1.0.OliPof).
I can get into Bootloader mode by pressing power/camera then reset.
In this mode, I can get it to reflash the ROM (and even other ROMS) but it still ends up in the same loop.
I have tried flashing the Official ATT WWE ROM from this thread but it still loops at boot.
I did the "original/problematic" flash using Vista. Could that be the issue? I have done subsequent "recovery" flashing using XP to no avail.
I have flashed several ROMs to my Tilt in the past (Mostly Dutty ROMs).
I had a Hermes before and flashed that a million times no issue so I'm not a complete noob.
Any ideas? I'm stuck with a brick!
Thanks in advance.
I'm in the same boat. I've flashed over and over (with different ROMs) and am still stuck. But I did every flash from MicroSD card. Did you get any help?
No input yet.
What ROM did you flash that started the problem for you?
dutty's touchflo rom beta for the tilt. i was on dutty's hybrid rom version 3. after flashing the OEM at&t ROM, i'm out of ideas. stay in touch if you find a fix. i'll keep searching.
- J
Bump...
Anyone else seen the issue with a Tilt stuck in a "boot loop" after flashing (see first post)?
Paypal reward for anyone who helps me recover - otherwise I'm going to have to go buy another Tilt (which I could live with but worse yet, I may be stuck with the stock ROM because I'm too gunshy to go back to my flashing ways)
Tried all day to find a fix. Think I made things worse. Read up on some threads using the mtty tool and ran a command (task 2a) that cleared the flash. But now it doesn't even boot to a splash screen, and I can't get back to bootloader mode.
This might sound a bit stupid, but I have taken note that my device upon flashing the new at&t rom actually held some of the information, you would think that a hard reset is performed after a rom flash, but that just wasn't how it worked out for me, anyway I had a radio that wouldn't come up, but would after a hard reset, this was directly after flashing my tilt...
?Glitch
Glitch,
Yeah, I have heard in several places that you need to hard reset after a flash to clear out all the settings from the old ROM. Seems odd since you just overwrote ROM - I think of it as a format (HDD mindset) but I guess it's not a clean format.
Jerich007,
Sorry to hear you went backwards. I stopped flashing my Tilt for the same reason - worried about getting farther in the hole without some expert advice. My next step was to try the MTTY tool just as you noted. Guess I'll go that route as a last resort. If it's any consolation, I seem to remember reading about plenty of people recovering from a "brick" that won’t go into bootloader mode.
Hopefully someone trolling the waters will see this thread and take up the offer for a Cash Reward (Paypal) for help recovering this Brick!
ill put up some paypal $$ for a fix as well. i'm at the end of my rope on this one. i'm subscribed to some other threads so hopefully we'll get some feedback.
It is not so serious as you think! Try the following way:
1- Download the original rom from AT&T (the 1st rom was installed on your device)
2- Turn your bricked Tilt to bootloader ( http://wiki.xda-developers.com/index.php?pagename=Kaiser_Resets )
3- Start flashing your Tilt with the above AT&T rom.
Evething should be OK after that! (but your device need to be installed Hard-SSPL before!!!)
try...
try this link
http://forum.xda-developers.com/showthread.php?t=286755
and maybe these
http://wiki.xda-developers.com/index.php?pagename=Hermes_Unbrick
http://forum.xda-developers.com/showthread.php?t=334693&highlight=how+to+unbrick
http://forum.xda-developers.com/showthread.php?t=344402&highlight=how+to+unbrick
don't forget that some of this info isn't for the tilt...
good luck, and be careful
This ROM solved my issues
try this thread
http://forum.xda-developers.com/showthread.php?t=327482
and DEFINETLY download the ROM, flash it. Once it's flashed,then ya can reflash any ROM ya want. Get the newest stock ROM from the sticky and reflash it (if ya want the ATT ROM)
That will fix it.
(I reflashed Tilt XDA-Live v 1.0, and it's working GREAT.)
I did the same thing to my Tilt.
That ROM saved me.
Alemaker
Problem is I can't get to a bootloader screen now. I press Camera+Power+reset, but all that happens is the green LED goes off then on, and then the screen is blank. Anyone know any other tricks? I think I may have erased my bootloader using mtty command 'task 2a'.
...
Hate to say it, but if after hours of searching on the forum you can't find an answer, i'd pm a pro like pof. I don't know if that will work, but their advice is the only thing i'd listen to.
Don't forget to give a lot of detail and maybe mention what you've tried.
Thanks. I've already PM'd pof and olipro. Hopefully they can come up with something.
jerich007 said:
Problem is I can't get to a bootloader screen now. I press Camera+Power+reset, but all that happens is the green LED goes off then on, and then the screen is blank. Anyone know any other tricks? I think I may have erased my bootloader using mtty command 'task 2a'.
Click to expand...
Click to collapse
****, I should have replied after someone posted all those links to Hermes unbrick procedures, to never do a task 2a from hardSPL. It reformats entire flash including SPL and the problem with hardSPL is that you can't flash another SPL, even if you would have tried before rebooting
Anyhow, your only chances to unbrick your device are to try to enter radio bootloader (there is a radio bootloader running on the mARM (ARM9)) and then to flash it. However, only service centres have such flashx utilities I'm afraid. Furthermore I'm not sure if radio bootloader can be entered directly, usually you can enter it via the normal CE SPL. You can try to first connect USB and then press reset with the stylus while holding the Voicecmd key. If you are in XP, then three new devices should be found (composite USB, a modem and a diagnostics port). Download the Motorola "Q" usb drivers, these will work just fine. In this mode you will have to authenticate to the radio bootloader before you can start entering commands. We'll get to that if you manage to connect. Your other chance to unbrick is via JTAG. I know the kaiser has JTAG points scattered on PCB.
Ok, thanks, I'll search for those drivers and let you know. By Voicecmd key do you mean the push-to-talk key along the side or the talk key with the green phoneset icon?
The top button at the left hand side
Ok here's what happens:
1. downloaded Motorola USB drivers (32-bit) from their site, installed and rebooted.
2. plugged in Tilt via usb cable, 'found new Hardware wizard' starts.
3. clicked next to auto-search for drivers, but the wizard fails with 'cannot install this hardware' message. I have 3 yellow question marks in Device Manager for 'Data Interface' devices.
4. held down Push-to-talk button and hit soft reset. No change, no leds are lit, screen is off.
Did I grab the right drivers?
Not bad at all. Apparently your phone is in Qualcomm DIAG mode, probably as a consequence of task 2a Now you can forget about rebooting with Voicecmd pressed.
Either you've got the wrong drivers or you don't install them in the correct way. Go in device manager, right click one of the 3 and update driver, then 'install from a list or specific location (Advanced)', then check 'Include this location in search' and enter the driver path. I'll take a quick look if I can find the drivers for you, I vaguely remember they were on mobile-files dot com.
EDIT: found the drivers, attached. The VID and PID of the found usb devices should be VID_05C6&PID_6000. Take a look in the device's advanced tab in device manager.
PS: Although diagnostics mode sounds great, I haven't yet found a way to flash the device. Perhaps it works with that Hermes radio flasher MaUpgrade_NoID.exe
Guys with a working SPL can enter radio bootloader DIAG mode via "rtask b", exit MTTY and install drivers. It would be great to know if someone has a htc/qualcomm radio flash utility (perhaps MaUpgrade_NoID.exe is what you need)
Hi to all,
I have an AT&T TILT HTC 8925,
ROM: 1.57.502.2
RADIO: 1.27.12.11
VE: 22.45.88.07H
Installed the kaiser-HardSPLv1 with no problems.
After this I Flashed (via USB) Q-Mobile_v1.2 ROM, that went perfect. Made a soft reset and then a Hard Reset after this I configured the phone.
After everything was working I made a Radio flash with KAIS Radio Only 1.27.12.17 CustomRUU, all seemed normal until it got to 95%, it suddenly interrupted the update (error 262), and took me to recovery dialog 1-4 steps which I did.
From that moment until know I get the tricolor screen with the following text:
RUUNBHKAIS 1*0
SPL-1.56.0000
CPLD-8
USB
Click to expand...
Click to collapse
And when I try to flash ANY ROM, It gets past the tricolor screen, to a white screen with a percentage bar that gets to 0%, after a minute or so the customRUU screen goes to error 262 and I get to the recovery screen, etc...
I run on WinXP SP2, and have already tried several roms with the same result, with the exception of original ATT RUU_Kaiser_CINGULAR_WWE_.exe, it then gets to 1% and displays error code 294 Invalid Vendor ID.
When I tried the MicroSD method with the rom it gets to the tricolor then the "Loading..." screen, and keeps there (I waited for about 30 min)...
There was no SIM or MicroSD card on the phone at the moment of flashing, and I did dump the original ROM to the 4 raw parts as per instructions.
I live waaay out of the countries with AT&T or HTC servicing routes, so I am stuck with it until I fix it, which I know I can do, and to be honest with myself, can't afford to waste the money spent on this thing.
Until now the best similar thing I found about this was with the hermes unbrick phone thread, and I am not sure this works on the KAISER, but to be honest, I get cold sweats to use any more procedures (without reconfirmation) on this as I have a phone that at least still shows "some" signs of life.
After reading days of threads (my eyes are burning) I know the knowledge is within this site, but I need guidance since I am new to this thing (smartphone flashing) although familiar with computers.
Any kind of help will be very appreciated and valued.
Best Regards.
----------------------
As an update, I solved this thing. Thanks for your help.
After seeing that there was some sort of problem with the boot mode screen not showing the kaiser-HardSPL data, I went in that direction. After some suggestions and much trying I decided to download all / any original roms I found in here for my phone (ATT Tilt) then I worked my way from top to bottom based on the versions of the radio.
The one that solved my problem was 1.5.502.3 Radio 1.27.12.11 although strangely it shows on my phone after the successful flashing. 1.5.502.1
Just out of curiosity I went and installed again kaiser-HardSPLv1 and it gets to this text on tricolor screen:
Kais1*0
SPL-.JumpSPL
CPLD-8
Doing a hard reboot (camera button + soft reset) gives me a different screen:
Kais1*0
SPL - 1.56.0000
CPLD-8
Really don't know if this is normal, and after flashing a cooked rom I had to reinstall it (kaiser-HardSPL).
I have now reflashed QMobile rom and have no problems. Although I didn't flashed again new radios
For flashing the Original rom I did make sure of the following steps in addition to normal ones (Just in case)
1) Disconnected fisically from LAN (Unplugged LAN Cable)
2) Disabled all firewall protections
3) Disabled all antivirus and spyware protections
4) Run RUU original files
5) Pray
Thanks again people
I had the same issue (I mean exactly the same). After failing the radio upgrade (Luckily I had my trusty Universal, so I started playing around (MTTY, Radio Roms etc.). The only thing that saved my TytnII was the original ROM!!
ftp://ftp.xda-developers.com/Uploads/Kaiser/Roms/
I just tried it again (See I am not so scared anymore), and received the same results (Radio upgrade fails on 95%).
I have burned the original ROM back and all is well again!
I also can't get past the same screen and try as I might Activesync won't recognise the phone. When going through the recovery process on Kaiser Custom RUU it says its recovered but then when trying to go through the update it sticks on 0% and then says there are communication problems etc.
On the tricloloured screen it says
KAIS130
SPL-1.81.0000
CPLD-8
Will a hard reset do anything?
Any help much appreciated.
Bump
Now managed to boot via MTTY but power off etc returns me to bootloader screen
Looks to me like you guys have had problems flashing hardspl. Your tri-colour screen should have:
KAIS130 MFG (or Kais 120 etc)
SPL-1.0OliPof
CPLD-8
I don't know about the CPLD number but you MUST have the OliPof SPL. Check this after running hardSPL to make sure that it's there before flashing another ROM.
If you have this but still get trouble flashing, try going to the tri-colour screen and then run the kaiser_RUU.exe to upgrade.
http://forum.xda-developers.com/sho...ked. (One without a radio)
- Flash a radio...
i had the same thing with my MDA Vario 3,but with no success finding the original ROM, since I`m from a small country. I`ve tried to reboot to normal screen via MTTY but it gives me the error: Command error . So - now I`m left with two options: to dump and reconstruct an original ROM from the same type of phone or to find what`s wrong with MTTY.
Anyone had a similar problem, I mean with MTTY and command error???
yes, i`ve searched trough the posts regarding this problem but I didn`t find any saying that MTTY gave this error.
any idea?
THX in advance!
Focus on HARD-SPL - get that on the phone and make sure its there.
If you cant get it on try this method:
http://forum.xda-developers.com/showthread.php?t=354061
Martinhdk said:
Focus on HARD-SPL - get that on the phone and make sure its there.
If you cant get it on try this method:
http://forum.xda-developers.com/showthread.php?t=354061
Click to expand...
Click to collapse
if you`re reffering to my problem-how can I copy the JumpSPL1.56-KAIS.exe file and execute it from the phone if I can`t boot it normaly,it always stays in tri-color boot screen?
actually, I`ve bricked my phone with that HardSPL procedure.It was the first step for unlocking. I`ve copied the JumpSPL1.56-KAIS.exe file, executed it and then rebooted and tried to flash with the modified ROM from the jockyw2001`s unlocker. it stopped at 95% and now it seems that it is still CID locked and bricked in boot mode. i`ve already said what MTTY gives as an error.
any idea what may be the problem?
like always:the problem is in RTFM
while i was working on my Kaiser i was doing lots of other things on other computers so i`ve skipped the step with flashing the HardSPL,that`s why all went wrong now,as i`m at home i have more time to read the posts and i`ll try with the jockyw2001`s procedure from the MTTY, with the task8 command.
hope it will help,unless the only solution is to dump the same ROM....
i`ll higly apreciate if anyone has a different solution....
will post results
The problem is that I can't flash the phone with anything be that HardSPL or the original Orange ROM or whatever you care to mention because the PC can't communicate with the device via the USB cable after Activesync ceases to operate. As such everything works up until the % progress bars come on both screens and then they stay at 0% before the communication error message appears.
Funny thing is that the phone is communicating with the PC as USB/Serial alternate depending on whether the cable is plugged in or not and the PC recognises the USB device when its plugged in and when Activesync isn't controlling the situation.
I've been stuck like this with a Hermes but not the Kaiser (yet). As far as I'm aware, you don't need activesync running to run a rom upgrade. If you are in bootloader mode (tricolour screen) you can run the upgrade directly with activesync not connected. If hardspl isn't installed then you should flash the original rom, and if you're unlocked then any rom should do.
Also it might be worth trying the SD card method for flashing. But either way I'd use the original rom and then when you get the phone working again keep trying with HardSPL until it's successful - don't flash any other roms without it.
Laubscherc said:
I had the same issue (I mean exactly the same). After failing the radio upgrade (Luckily I had my trusty Universal, so I started playing around (MTTY, Radio Roms etc.). The only thing that saved my TytnII was the original ROM!!
ftp://ftp.xda-developers.com/Uploads/Kaiser/Roms/
Click to expand...
Click to collapse
Thanks for your help.
I did try other "original" rom I got in here http://wiki.xda-developers.com/index.php?pagename=Kaiser_ROMs
The version corresponding my rom is (1.57.502.2 (radio 1.27.12.11)), however I got the error code 294 Invalid Vendor ID after 1%.
I did try the ftp address you mentioned, but I can't login neither anonymously nor with user & psw for xda-developers.
I would like to try the rom you are referring to, please give me another link to download the file.
Best Regards.
Martinhdk said:
http://forum.xda-developers.com/sho...ardware devices list.
Thanks for your help.:)
Click to expand...
Click to collapse
Stuck in Tri color screen
I have been fighting the same issue for several days. Radio gets to 95% and errors. Then hung up in tri color screen. I used MTTY - "set 14 0" command then "boot" command inMTTY to get the phone to boot. I have had to do this a number of times, sometimes more than once per incident. Hope it works for you too. P.S. once you have a successful flash the phone returns to normal operation until then it will go back to tri color screen on reset. I just flashed a startup splash screen to get mine back to normal.
pennco can you expand in further detail on what you actually did with MTTY cause I have the EXACT same problem....
Ok, So I had dutty's rom running perfect for about 5 months. Decided I wanted to revert back to the stock ATT rom and play with it. I tried to revert and somewhere along the way, I did a soft reset and it screwed me up. I can still flash roms no problem, but for some reason, when the phone goes to start up, it gets to the first screen of the boot process (white with ATT logo) and then it freezes. After about 10-15 seconds, it automatically soft resets and tries again. So, I can hit the reset button while holding cam and pwr to get to the bootloader. I have tried flashing every rom I have downloaded, and nothing seems to work. I am trying the stock ATT rom as I type this but we will see what happens. That is what I was running when it F'd. I wanted to restore it to stock completely, thought about trying to have it replaced because the hinge is really loose on my handset. Anyway, any help would be appreciated. Thanks!
boot command from mtty reads:
Cmd>boot
InitDisplay: Display_Chip=1
Fill RSVD information for block 288 to 309
Storage start sector=0xAB80, total sector=0x10740
Storage start block=707, total block=1053
Total Bad Block in CE: 0
Erase physical block from 995 to 2032
formatstorage Bad block found: 1045
si backup: Erase physical block from 2032 to 2048
No card inserted
OSSIPreLoad ++
Try this
Try flashing this ROM and see what happens.
http://www.4shared.com/file/3857459...ULAR_WWE_157_-_Originaly_Shipped_ATT_ROM.html
What does your bootloader screen show?
Please Help!
Okay. I tried to flash the OEM rom back to my ATT Tilt. While doing this, somehow my phone entered an unending cycle of soft resets. I can still get to the bootloader, but as soon as I flash a rom, it tries to boot, gets to the first boot screen, then resets. My computer keeps popping up "install drivers for new hardware found".
I tried booting through MTTY, no dice.
My bootloader screen reads:
KAIS1*0 MFG
SPL-1.0.01OliPof
CPLD-8
I tried flashing hardspl. RUU opens and it runs instantly. The phone reboots and the boot loader screen still reads this. I flash a new rom, the bootloader still reads this. I'm at a loss. I've been working on this for 3 hours and I haven't gotten anywhere. I don't have a backup phone, so I have to figure this problem out. I have searched the forums and haven't found anyone with the same problem. Please, anyone who feels they can help, let me know what I can try to fix this problem. Thanks!
Threads merged.
Metzex08 said:
Ok, So I had dutty's rom running perfect for about 5 months. Decided I wanted to revert back to the stock ATT rom and play with it. I tried to revert and somewhere along the way, I did a soft reset and it screwed me up. I can still flash roms no problem, but for some reason, when the phone goes to start up, it gets to the first screen of the boot process (white with ATT logo) and then it freezes. After about 10-15 seconds, it automatically soft resets and tries again. So, I can hit the reset button while holding cam and pwr to get to the bootloader. I have tried flashing every rom I have downloaded, and nothing seems to work. I am trying the stock ATT rom as I type this but we will see what happens. That is what I was running when it F'd. I wanted to restore it to stock completely, thought about trying to have it replaced because the hinge is really loose on my handset. Anyway, any help would be appreciated. Thanks!
Click to expand...
Click to collapse
Some people go to far ahead before figuring out the real issue. Don't **** yourself.
Hold down your power, camera, and insert your stylus then tell us what your bootloader screen displays.
Metzex08 said:
Okay. I tried to flash the OEM rom back to my ATT Tilt. While doing this, somehow my phone entered an unending cycle of soft resets. I can still get to the bootloader, but as soon as I flash a rom, it tries to boot, gets to the first boot screen, then resets. My computer keeps popping up "install drivers for new hardware found".
I tried booting through MTTY, no dice.
My bootloader screen reads:
KAIS1*0 MFG
SPL-1.0.01OliPof
CPLD-8
I tried flashing hardspl. RUU opens and it runs instantly. The phone reboots and the boot loader screen still reads this. I flash a new rom, the bootloader still reads this. I'm at a loss. I've been working on this for 3 hours and I haven't gotten anywhere. I don't have a backup phone, so I have to figure this problem out. I have searched the forums and haven't found anyone with the same problem. Please, anyone who feels they can help, let me know what I can try to fix this problem. Thanks!
Click to expand...
Click to collapse
ok post was moved from another thread. sorry. It appears that you do have hardspl installed.
Metzex08 said:
Okay. I tried to flash the OEM rom back to my ATT Tilt. While doing this, somehow my phone entered an unending cycle of soft resets. I can still get to the bootloader, but as soon as I flash a rom, it tries to boot, gets to the first boot screen, then resets. My computer keeps popping up "install drivers for new hardware found".
I tried booting through MTTY, no dice.
My bootloader screen reads:
KAIS1*0 MFG
SPL-1.0.01OliPof
CPLD-8
I tried flashing hardspl. RUU opens and it runs instantly. The phone reboots and the boot loader screen still reads this. I flash a new rom, the bootloader still reads this. I'm at a loss. I've been working on this for 3 hours and I haven't gotten anywhere. I don't have a backup phone, so I have to figure this problem out. I have searched the forums and haven't found anyone with the same problem. Please, anyone who feels they can help, let me know what I can try to fix this problem. Thanks!
Click to expand...
Click to collapse
and your bootloader screen will not change because it does not display the rom version. You have hardspl installed what more do you want?
Did you believe your bootloader screen would change after you flashed a rom?
Damn!!!
Metzex08 said:
Ok, So I had dutty's rom running perfect for about 5 months. Decided I wanted to revert back to the stock ATT rom and play with it. I tried to revert and somewhere along the way, I did a soft reset and it screwed me up. I can still flash roms no problem, but for some reason, when the phone goes to start up, it gets to the first screen of the boot process (white with ATT logo) and then it freezes. After about 10-15 seconds, it automatically soft resets and tries again. So, I can hit the reset button while holding cam and pwr to get to the bootloader. I have tried flashing every rom I have downloaded, and nothing seems to work. I am trying the stock ATT rom as I type this but we will see what happens. That is what I was running when it F'd. I wanted to restore it to stock completely, thought about trying to have it replaced because the hinge is really loose on my handset. Anyway, any help would be appreciated. Thanks!
Click to expand...
Click to collapse
Dude it has been five months since you flashed a rom why bother getting all neurotic and worried For a common situation? I complained to mods because they closed your thread now I look like a douche bag. Thanks.
I had the same problem (continuous reboot) as before, see this thread:
http://forum.xda-developers.com/showthread.php?t=383678
but the problem that I had is because of bad blocks, post your info 8 and maybe I can help
ok, I got the phone to startup, eventually it stopped trying to soft reset. I hit the power button and it turned on. Now, I run jumpspl and it doesn't ever bring up the USB connection, so I can't change the bootloader back to oem. any suggestions?
I used the other version of jumpspl (1.56) and it brought up the USB connection (atleast it says it did). But, when I try to run RUU from the ATT_SPL folder it cannot connect to my phone. MTTY says USB connection is unavailable as well. What should I do?! I want the phone to be able to be sent in for warranty replacement as the hinge seems to keep getting looser and looser. Any ideas? Bootloader still reads the same as before.
Metzex08 said:
I used the other version of jumpspl (1.56) and it brought up the USB connection (atleast it says it did). But, when I try to run RUU from the ATT_SPL folder it cannot connect to my phone. MTTY says USB connection is unavailable as well. What should I do?! I want the phone to be able to be sent in for warranty replacement as the hinge seems to keep getting looser and looser. Any ideas? Bootloader still reads the same as before.
Click to expand...
Click to collapse
If your sending it for warranty replacement via AT&T just put it in the microwave for 2 seconds....problem solved.
Please help.
I have the Verizon TP World Phone w/SIM card.
I downloaded the HARDSPL described as such: this package is for Rhodium CDMA-GSM worldphone version only (CDMA Touch Pro 2, not the original Touch Pro) devices. only RHOD400, RHOD500 modelids are accepted. this Hard-SPL supports WM6.5.
This process went successfully and I made it to the tri-color bootloader screen.
Next I ran this flashed this ROM NRGZ 21864, which appeared to complete successfully via PC, but when phone rebooted it just shows black w/Touch Pro 2 in middle of the screen.
Tried resetting, batter pull everything can't get anything to happen.
**Update: I was able to now get it into tri-color boot loader so what should I do with it now? It says SPL-1.00.Olinex, so its still unlocked. Should I just retry the rom again?
What did I do wrong? Is this phone dead? How do I get to bootloader? What should be my next step if phone is not dead.
Thank you!!!
Get a different rom that one didnt load or you could try reflashing doesnt seem as it took properly but no fears your phone is not bricked
Make sure you get a rom built for CDMA phones. this isnt the proper section for that goto RHODUIM CDMA
To Flash from the SD card, the .nbh file needs to be named "RHODIMG.nbh"
copy the .nbh file to a micro sd card, prefarably a 2gb or lower formatted as a FAT32
plug it in
get into the boot loader
i would recommend getting the stock ROM for your carrier and flashing that before moving to a custom ROM
hope that helps
ME TO
How do you get it to load in the bootloader menu ? Any luck with fixing it?
LECKEY73 said:
How do you get it to load in the bootloader menu ? Any luck with fixing it?
Click to expand...
Click to collapse
To enter the bootloader hold volume down and power (the red end key, not the sleep key on top) and press the stylus into the reset button. Once you see the tri-color screen you can release volume and power.
Same thing happened to me on my flash to that exact ROM. I guess sometimes it just doesn't flash correctly for some reason. No worries, enter bootloader mode and try flashing to MightyROM. After that, I was able to flash to whatever ROM I wanted. (But then I flashed back...MightyRom rules!!)
the spl 1.00 is fine. just go here it's for cdma phones only.
thanks everyone, got it back into bootloader via the challenging (hold both buttons and hit reset) Years of cosole gaming clearly paid off for those acrobatics.
Reflashed to original rom/radio, will put MightyRom back on..think I just needed to bump my head a bit, start over after some lessons and get this running better.