I was able to access the bootloader for 5 times using the softreset and holding the power button.
By the time I figured out how to use the patch to bypass it, it's too late.
It no longer boot to the bootloader.
Now it just by-pass the bootloader screen and goes directly to the T-Mobile screen.
I've tried everything . Hard cold reset. Hold power-on and softreset
numerous time without success.
Anybody knows of any other way to access bootloader?
Bootloader version 5.22.
Maybe the Bootloader has a malfunction.
You can try to fix the bootloader. In the XDA-Tools, there should be a little tool to fix it.....
Stefan
If you are referring to running from the command prompt:
"pnewbootloader bootloader_v5_15.b0"
It didn't work for me.
I cradle it and ran that command and this is what I got:
"
unable to find flash info offset, cannot disable bootloader writeprotect"
message.
Anything else I can try?
TIA
Chip
Yes, this program i´ve meant. WHich version are you using of this tool? There have been an update of it, about half of a year ago. Maybe you download again the XDATools of the ftp and retry it.
Stefan
Thanks, got the updated file and fixed my bootloader.
the version you are referencing to is included here in case anyone
else wants it.
"pnewbootloader_40116.exe"
Thanks to all the people working hard to bring us these features!
And a special thanks to "stefan" for bringing a great kitchen!
The machine by it's default is so "weak!".
Chip
Glad to hear all is working now again....
Stefan
Related
ok, now I am totaly screwed.... imate stuck in loading screen with version numbers etc... Not going further and bootloader not available.... Is there any way to communicate with unit while it's in this mode?
what you are saying is unclear. Does your device say "Serial" (or "USB") on top with "V 1.06" on the bottom?
If so, you ARE in bootloader mode. If not, then please specify what it actually says on the screen
no, it's not in bootlader mode. it's in Tmobile screen at the bottom it says R 1.12.00
G blah
D blah
it stuck there. and I can't enter bootloader mode. looks like it's totaly dead
What happens when you try to enter bootloader (Power - Action - stylus)?
What happens when you try to press (Camera - Record - Stylus)?
GO TO HELL ROM 1.72.104
F%@#&!?G FREAK ROM!! :evil:
Please calm down... in a day or two, this problem will be solved and everyone will probably be back to where they were
((and a lot smarter than they were too))
Victor said:
What happens when you try to enter bootloader (Power - Action - stylus)?
What happens when you try to press (Camera - Record - Stylus)?
Click to expand...
Click to collapse
It both cases it still sits in this screen
Try removing the battery and waiting for a period of time (20 Mins ??)
Then try the two things again (first without the battery -- for the heck of it -- and then replace the battery and try them)
...obviously, you need to remove it from the charger too :wink:
to be clear... nothing is expected to happen when you try to do these without the battery in, except perhaps (??) clear out any remaining charge held in capacitance, if any.
Kinda like removing the batteries in the remote control of a TV and then pushing a button on it (there is always enough charge in the capacitors for a single push/command to the TV
that once happent to me
and softreset dident help
so i did a hardreset and that fixed it
fixed my data too though :/
Rudegar said:
that once happent to me
and softreset dident help
so i did a hardreset and that fixed it
fixed my data too though :/
Click to expand...
Click to collapse
nothing happenes Sent email to imate tech support. I am not sure if they going to warranty unit with Tmobile betta screen stuck on IMATE. looks like i am short 700 USD........
Is there any way to communicate with XDA2 when it stuck in this loading screen? Terminal via serial cable doesn't work. anyother low level programs are out there? please, help.
Have figured out that the problem is in the Bootloader. If there is a way to (and I know there is) revert to an older Bootloader version, then the problems will all be solved.
Problem Solved : Dead devices due to tmob 1.72 + Downgrade
OK Guys. Problem Solved : Dead devices due to tmob 1.72 + Downgrade
http://forum.xda-developers.com/viewtopic.php?t=8606
That's great, but unfortunately my device is one step more screwed that others - no bootloader not even working Windows now.
Is there any way to boot directly from SD card?
victor,
can you upgrade or downgrade the bootloader ? If you can, HOW? please post the way to upgrade or to downgrade the bootloader. :shock:
ID64,
I had an XDA I and wiped the bootloader by accident. As far as I know, you have only two options. The first one is JTAG [http://www.xda-developers.com/jtag/] but I don't think the boards have been documented yet for XDA II. The other option is to bring it back to where you bought it from. Tell them there's something wrong with it and play dumb. If you're lucky they might replace it for you, if they assume that you are still within warranty.
Yes, there is a way to upgrade/downgrade the Bootloader. I just don't know how.
The bootloader is locked, that is the problem you have (except for those who cannot access the bootloader).
If you know the right syntax and use the password to the bootloader (it is BOOTLOADER), you can load the proper ROM back using the "LNB" command. However, they have changed the syntax since ITSME's doc on the subject, or he mis-documented the syntax to the bootloader. Or at least his syntax was wrong with 1.06 version.
I got mine fixed, but I have means available that 99.9% of the people out there do not have. If I knew more, I would tell you about the percise syntax in the bootloader -- but alas, I am not a developer.
Victor said:
Yes, there is a way to upgrade/downgrade the Bootloader. I just don't know how.
The bootloader is locked, that is the problem you have (except for those who cannot access the bootloader).
If you know the right syntax and use the password to the bootloader (it is BOOTLOADER), you can load the proper ROM back using the "LNB" command. However, they have changed the syntax since ITSME's doc on the subject, or he mis-documented the syntax to the bootloader. Or at least his syntax was wrong with 1.06 version.
I got mine fixed, but I have means available that 99.9% of the people out there do not have. If I knew more, I would tell you about the percise syntax in the bootloader -- but alas, I am not a developer.
Click to expand...
Click to collapse
Thanks for the reply, Victor. When you talking about commands for bootloder what connection to PC you are talking about? Serial or jtag?
I am referring to the device in the cradle, in bootloader mode. The screen in this mode should read "USB" on top and "V.1.06" (or whatever version) on the bottom. Very hard to read, as there is no backlight.
Anyhow, just for fun.... why don't you try the following:
Uncheck the USB option in Active Sync Connection Settings
Cold boot your system (hard reset)
place the device in the cradle
run the communications software (found on this forum)
When asked which COM port to use, click on the down arrow and see if there is a USB port listed (should be top entry in list).
If so... click it. (if not, you are basically done)
After clicked, then hit return (enter) on the pc a few times.
Anything happen?
Ok I have searched the forums pretty hard the last couple of days, and I have not found anyone that has the same issue as mine. It's not too big of a deal as everything operates but it is an issue all the same. This is all of course after I have succesfully ran HARD SPL v7 and upgraded to Black 3.0.1. Basically I decided to use POF's SuperCid Unlocker 3a (yes I know if I had HARD SPL 7 then why go through the trouble of Unlocking my CID, let's call it a need to mess with things) and everything went succesful. Then after the fact I read that it is still good even if you have SuperCID to upgrade the SPL to 2.10 and have read some peoples signatures and it appears that they have succesfully done this. Here is my issue;
When I run the CustomRUU it autodetects my SPL no problems, HARD-SPL? is checked, everything seems to go fine until it gets to the boot loader, once it is there, the progress bar pops up, zings to 100% and then reboots, cool? no because it didn't actually upgrade anything everything is still the same. Ok, so I tried the format SD card and rename *.nbh file to HERMIMG.nbh and put only it on the card, when I go to bootloader it does a quick flash to the screen like it recognizes the image but then goes to boot loader and nothing changes (the flash is so quick I can't even read whatever message it may be showing). I have tried pretty much every flashing method I can come across. MTTY wont recognize that I even have a USB port so I have been unable to try that method. So two questions:
I have SuperCID, so should I continue to even bother to get to 2.10?
If so, is there anything else I can try? Or do I need to get MTTY to work and try that as that is really the only thing left?
Thanks for any and all help anyone can provide.
PuckX said:
Ok I have searched the forums pretty hard the last couple of days, and I have not found anyone that has the same issue as mine. It's not too big of a deal as everything operates but it is an issue all the same. This is all of course after I have succesfully ran HARD SPL v7 and upgraded to Black 3.0.1. Basically I decided to use POF's SuperCid Unlocker 3a (yes I know if I had HARD SPL 7 then why go through the trouble of Unlocking my CID, let's call it a need to mess with things) and everything went succesful. Then after the fact I read that it is still good even if you have SuperCID to upgrade the SPL to 2.10 and have read some peoples signatures and it appears that they have succesfully done this. Here is my issue;
When I run the CustomRUU it autodetects my SPL no problems, HARD-SPL? is checked, everything seems to go fine until it gets to the boot loader, once it is there, the progress bar pops up, zings to 100% and then reboots, cool? no because it didn't actually upgrade anything everything is still the same. Ok, so I tried the format SD card and rename *.nbh file to HERMIMG.nbh and put only it on the card, when I go to bootloader it does a quick flash to the screen like it recognizes the image but then goes to boot loader and nothing changes (the flash is so quick I can't even read whatever message it may be showing). I have tried pretty much every flashing method I can come across. MTTY wont recognize that I even have a USB port so I have been unable to try that method. So two questions:
I have SuperCID, so should I continue to even bother to get to 2.10?
If so, is there anything else I can try? Or do I need to get MTTY to work and try that as that is really the only thing left?
Thanks for any and all help anyone can provide.
Click to expand...
Click to collapse
Did you look on the bootloader screen to see if your SPL changed? To my knowledge the only place you can see it is in the bootloader screen (tri-color screen) And flashing Olipro's Hard SPL only takes a couple seconds so it sounds to me like it is working as designed.
Or are you trying to flash a different rom? If so then try deleting everything you have in the directory you are using and re-downloading. You might have over-written the file you want to flash with the HardSPL one. You shouldn't be using the hard spl wrapper to flash a rom in any case, i believe that is mentioned in bold at the top of the Hard SPL thread.
Ok nevermind I was able to get it to work and MTTY was the answer. This is the 2 steps I had to follow:
From the thread: http://forum.xda-developers.com/showthread.php?t=291723
sp3dev said:
Hi. I`ve finally found the way to connect mtty and run rom update utility in Vista. tested on rtm 6000.
First of all, connect your device when it`s in bootloader.
next, open Windows Mobile Device Center and in connection settings uncheck Allou USB Connections.
next, goto contol panel-administrative tools-services and start windows mobile device connectivity and windows mobile device 2003 connectivity
next, goto device manager and find your device and update the driver to the one from AS 4, i attached it, wceusbsh.inf.
then, kill wmdc.exe with any taskmanager
You are Ready. run ruu or connect MTTY. I guess that vista default driver uses another port, not WCEUSBSH001, that`s why we have to use the old driver.
Click to expand...
Click to collapse
Then Do This:
http://wiki.xda-developers.com/index.php?pagename=Hermes_BootloaderMFG
Flashing SPL-1.01 MFG instructions
Put hermes in bootloader mode (side ok + power button + softreset)
Connect Hermes to computer using USB cable.
Open mtty.exe, select "USB" from the dialog box, then hit Ok.
Hit enter twice and you'll see the "USB>" prompt.
Then type these commands: (note the use of 'lnb*s*')
USB>task 32
Level = 0
USB> lnbs SPL-1.01.nbs 50020000
USB> task 8
Device will reboot after this, with bootloader 1.01-MFG on it.
Once I was able to do all this I was succesfully at 1.01 at which point I ran the Custom RUU and upgrade to 2.10 without issue. Once again all right there in the forums, just had to be pieced together to find a solution.
Thank you all for all your dedication to these projects, you make owning a PDA more fun than I am sure was originally intended. I love messing with things.
I have also attached the necessary files from the original posts to perform this for anyone else facing this issue.
PuckX said:
Ok nevermind I was able to get it to work and MTTY was the answer.
Click to expand...
Click to collapse
Cool, glad you got it working
Hey everyone,
i am so upset and lost; words cannot describe it.
So i installed WM6 black shadow and everything was working except for SMS and MMS. So i am like ok i can live with that for a day till custel' rom will come out. SO i decided to upgrade the radio to 1.43 and boom here is where the problem started, No GSM on boot up. Phone doesn't boot up. I tried install 1.40 over again, still nothing. No i tried upgrade the the rom itself, i tired custel 2.5 and nothing and i tried the new Cingular rom, still same problem. the roms flash all the way. I read the wiki, and saw the mtty.exe thing but that doesn't work for me either. I am really lost and don't know what to do.
Specs
cingular 8525
hardspl v7 cid and sim unlocked.
PLEASE HELP
4.13?? 4.10??
Where did you download these radios from??
or do you mean 1.41 or 1.43??
Yeah thats what i meant, 1.40 and 1.43 sorry. You can see how upset i am.
Thanks Again
Well, if your phone turnes on .. it's not a brick.. lol .. it IS fixable... When you turn the phone on does it go RIGHT to the 3 colored screen?
@dan5.5
You need to read the unbricking thread about this, all the info you need is there.
http://forum.xda-developers.com/showthread.php?t=286755
If you are superCID I don't see how flashing a radio could have messed up your phone.. that's weird.
mrvanx said:
@dan5.5
You need to read the unbricking thread about this, all the info you need is there.
http://forum.xda-developers.com/showthread.php?t=286755
Click to expand...
Click to collapse
I read everything there and nothing seems to be working for me. I woudnt post for nothing. i dont want to be annoying.
OK im going to repost what ive said on 4wm:
We need to check if your Radio BL is functional, firstly leave HardSPL v7 on there and connect to the bootloader via mtty (il assume you know how to do this).
Issue the following commands and tell us the results please:
1) checkimage (this shows the CRC checksums of each component...id expect the radio image to show a timeout....
2) info 2 (This will verify that your CID is intact)
3) info 8 (does a bad block check)
Once youve done this, flash SPL 1.10.oli to the device and once again connect up to mtty.
4) 'rtask a' this will enter the radio bootloader you will see "Enter Radio Bootloader" or something to that effect
from now on when you type the text does NOT appear on the mtty screen.
5) 'rversion' this should return your radio bootloader version...now unfortunatly if you see nothing...you radio BL is dead and sorry your device is royally bricked. If you get something returned back onto the screen (most probably containing the text '0108') then your radio BL is fine.
Click to expand...
Click to collapse
do as instructed in that text, post your results here.
I cant falsh spl 1.10 oli. it gives me the 260 error.
the 260 error is not connected via USB right? .. weird... have you tried taking your battery out for a couple minutes, then booting into BL mode? sounds weird but this worked for me when I didnt flash hardSPL firsl..
hey mrvanx's
I can't downgrade the hardspl to 1.10, anyhelp.
I cant active sync, the phone doesnt boot up.
Is there anyway to aviod having to respond on the phone.
hey,
i can get the phone to boot up into windows and then it freezes within a couple min. what should i do. Still no gsm message and no phone. thanks
Dan
OK, so let's try and get you to a working state - I've bricked mine a couple of times and it can be quite heart-stopping, eh?
The first thing I would do is re-download radio 1.43, just incase your current one is damaged somehow.
Secondly, download Black Shadow - I know it's not the ROM you ultimately want but the aim here is to get you working again and we can move forward from there.
First, boot up into BootLoader mode (hold down the OK button on the left side of the phone and the power button and then press the reset button on the bottom, just in case you didn't know
You should come to the three colour screen and it should be reading IPL-1.04 and SPL-2.10.Olipro. If it isn't, stop here and post what it does say.
If it everything is OK at this point, when you plug your phone into your computer, it should change to USB at the bottom. Just wait for the Found New Hardware prompts to clear on your PC and then flash the black rom - choose the hardspl option in the flash program.
Once that has finished and it is at the "tap screen to set up windows..." bit, put it back into bootloader mode as above and flash the radio.
This should hopefully give you a running phone again as I know this combination works OK as I am currently using it.
Fingers crossed, don't panic, and let us know what the results are
Cheers,
Smiffy.
Nothing is working, can some please help me. Is there anyt way i can restore the spl to the original one so i can send the phone back, i just got it like 2 weeks ago. thanks
Also i have a bad block thats what i think makes the phone freeze after i boot it up.
How can i get around this, thats seems to be the biggest problem.
Hey everyone, let me give you more info.
I can fully flash any rom and and radio,
phone will boot up like 1 out of 10 times and then freezes and thats it.
i have a bad block number 6. I have hard spl v7 installed before the phone got screwed up. I cant downgrader the spl to a lower one to check if radio stack is screwed up. Can someone please help me, if you need to ask me more info feel free.
Hey, my phone is an At&t 8525 and after finally fixing the white screen problem and flashing hard-spl v7 and a couple of roms I bricked the phone when flashing the last touch flo rom. During the flash the ruu wrapper stopped and indicated there was an error. I did the recovery and it supposedly completed succesfully if I can remember right. When it reboot it would not get past boot loader. And thats where I am now, the phone will not get past boot loader.
I've tried every method on these forum I could found
SD card flashing dosent work, I get the 002..... error in red.
Flashing the factory an at&t rom dosent work either, gets the same error
\
As for as I know the MTTY method dosent work, I don't know how to type in commands into bootloader and when I type in 14 0 in MTTY nothing happens
KITL is not enabled
IPL-1.04
SPL-2.03
The phone does not boot into bootloader when I hit the power button, I have to hold the comm button, power button, and soft reset in order to bring up bootloader.
When bootloader is up and the phone is connected to the computer via usb bootloader displays usb on the screen and windows detects the device as an HTC device.
Again i've spent about a week and a half trying to fix this phone and I don't know what to do anymore, i've tried more methods than listed above I can't remember though. If anyone can give me a hint on what to do I would highly appreciate it. Thanks
P.S Can someone please tell me how you type commands in bootloader or MTTY
You DON'T have Hard SPL V7 installed..... Otherwise your SPL would be 2.10.
Connect the Hermes to the pc, make sure active sync has benn disabled - got to settings, untick connect by USB. It should register on the pc. Go to bootloader then run the .nbh file for your stock rom... Make sure its the carrier rom that it was shipped with. It doesn't have to be WM05 but it DOES have to be your ORIGINAL carrier rom. Let it run through, you may gewt lucky.....
If it works, INSTALL HARD SPL V7....... Makes it so much easier to fix then...
Good luck...
Thanks for the reply, much appreciated
I tried downloading and sd card flashing a stock rom from a list of factory roms of all Hermes that I found here on xda. It gave me the same error though. I'm not exactly sure which exact rom to download from that list either. Any more help would be appreciated, thx
Wow I feel retarded, I used the wrong factory rom. After I used the right one it worked perfectly, I now have my 8525 back! Thx so much man, ur the friggin man!
Congrats bro you got it atlast. good luck & take care your baby in future. try to help others with your experience.
Glad you fixed it mate, but if I were you I'd also make sure you have Hard SPL V7 installed. It is the safety net to help when things go wrong... Never gonna be 100% safe but better odds with Hard SPL V7...
SPL - 2.10 oli
Cheers...
Ok... Rejoining the 8525 Clan
Is this Forum still alive???
Been a while guys, figured I would break out the 8525... charge it up and see what kind of things are new in this community. Unfortunately, it looks as if the radio is bricked on it. Seems like it will install ROM's that the radio is not included on. NO GSM is on the boot display, which is strange as I was using this phone until I got the Tilt about 1 1/2-2 yrs ago. I was a hardcore flasher back then... every other day it seemed, so I know it has (or had) everything it needed like the Oli 2.10 SPL... but it seems like I cannot recover this radio issue.
I am messing with the different original OEM and Carrier ROMs hoping I can get passed the 11-12% mark, and I will let you know if something changes. Any idea if un-installing SPL 2.10 Oli, and then trying to walk back through the old SPL steps could help? I am just trying to figure out another way to get around this radio issue... or basically I have a PDA, no phone Damn phone hasn't been touched in like 2 years, you think it would be just as fine as it was when I took the SIM out.
Cheers
Can u plz tell me how do you fix the white screen problem ?????
kashifmehmood said:
Can u plz tell me how do you fix the white screen problem ?????
Click to expand...
Click to collapse
Please try searching before posting.
Your answer lies within
Thread closed
Hola guys,
I've messed up with MTTY and I think I've totally fried my old NIKI 20Keys.
I don't remember what kind of commands I've issued (it passed a long time since) but I can tell you that once upon a time the device was cid unlocked (I think so by the way I was able to install every kinda rom).
Now even if i press PWR+CAMERA+RESET the device doesn't go on bootloader mode: it stays black without any hope.
On WinXP it's not recognised as a USB device; only as a Qualcomm device for which I've downloaded the drivers (Diag Device + NMEA) on COM4 and COM5.
I think I've formatted the bootloader and I'm not able to restore it.
Commands like "cego", "task" and whatsoever are not recognised, but, e.g. "setboot" works. I don't know why.
I've tried with Frankenkaiser but with no luck.
Any man of good will able to help me out? I can even consider to send the phone to some forum members for repair if anyone wants, but I'll prefer to do it on my own.
Thanks to all of you for your kindness.
Really?
No one able to lend me a kind hand?
I add a little thing: there are no great commands that work with PTTY or mtty.
I see that setboot and radata work.
Is there a way to have a list?
Is there a way to have a list?
Click to expand...
Click to collapse
http://forum.xda-developers.com/wiki/index.php?title=Hermes_BootLoader#Bootloader_commands:
Thanks a lot but how can I load a bootloader using radata or something similar?
Not all the commands in the page you linked now work with my phone...
sanric said:
Thanks a lot but how can I load a bootloader using radata or something similar?
Not all the commands in the page you linked now work with my phone...
Click to expand...
Click to collapse
To get an honest answer, I do not know, I've fortunately never need to use it.
The only thing I can do is help you search.
error in post