Database Info

Can't seem to flash any roms... CID locked G4..

So I've spent the last two days either out drinking or recovering and studying this and a few other forums. I feel like I have a solid grasp on flashing a rom but I'm still having the same issue with every one.
First, I have a T-Mobile HTC Wizard, flashed with most recent OEM build, CID locked, SIM unlocked.
Usin Shelltools to extract the OS, I've tried NBD 9.1, and also the OS that comes with Faria's guide. I copy those two cab files Cert and enablerapi to my Wizard and installed them, and soft rebooted with the stylus hole on the side, activesync to my comp, and run shelltools.
About 5 minutes (shorter than it should be from what I've heard) in with either of these OS's I get a message saying that the install is done from shelltools and my wizard gets a message that says "Cannot load ndblog.exe" or something very similiar to that (Note to self: get a better memory or write things down! ><)
After that I get stuck at bootloader and have to reflash OEM.
Any idea what's going on here? I assume I'm missing some idiotic detail...I feel like I've got this process all processed mentally and that's always where dumb mistakes are made

I suspect the error your referring to might be 'cannot execute replog.exe'
What about Wizard Love, have you tried flashing this rom then using shelltool?
Alot of people advise to flash the rom that your device was shipped with and since you've pretty much exhausted that option I suggest you get some wizard love happening prior to using shelltool again.
Good Luck

elementxero said:
So I've spent the last two days either out drinking or recovering and studying this and a few other forums. I feel like I have a solid grasp on flashing a rom but I'm still having the same issue with every one.
First, I have a T-Mobile HTC Wizard, flashed with most recent OEM build, CID locked, SIM unlocked.
Usin Shelltools to extract the OS, I've tried NBD 9.1, and also the OS that comes with Faria's guide. I copy those two cab files Cert and enablerapi to my Wizard and installed them, and soft rebooted with the stylus hole on the side, activesync to my comp, and run shelltools.
About 5 minutes (shorter than it should be from what I've heard) in with either of these OS's I get a message saying that the install is done from shelltools and my wizard gets a message that says "Cannot load ndblog.exe" or something very similiar to that (Note to self: get a better memory or write things down! ><)
After that I get stuck at bootloader and have to reflash OEM.
Any idea what's going on here? I assume I'm missing some idiotic detail...I feel like I've got this process all processed mentally and that's always where dumb mistakes are made
Click to expand...
Click to collapse
I have this same problem when using shelltool on my desktop computer. My simple solution: use my notebook computer. My guess is that something installed on my desktop was stopping shelltool from doing its job. I.E. firewall, anti-virus software, something. I really don't know what it was, it might even have been some kind of virus that I dont have on my laptop due to better virus protection and wlan switch.
My reccomendation, try a different computer if you can before you give up totally or pay to have your device CID unlocked at IMEI-check.com and then you will be able to use RUU method.

Thanks guys, I'll try these two solutions tomorrow as its almost 2am and I have to be up for work in 6 hours ><.
Also funny thing is, I got so annoyed that I almost just rocked the damn pay service to get unlocked, but as I was checking out I saw that they had this drawn out process where you had to send them personal info (drivers license?!) to verify your paypal isn't stolen. Isn't that like, the ####ing point of paypal to begin with!? I'm not sending scans of I.D.'s so some shady cell phone hacking website!

I hear that. Thats just asking for your identity to be stolen...

Bricked Cingular 8125, help!!

Hello All,
I have the TNT 1933 image loaded on my Cingular 8125 and have been running it fine for almost a month with little to no issues. The issues I had were minor kinks here and there but did not hinder the phone usage at all and has been working fine till up to this point. I was reading my e-mails via the exchange setup to my company exchange server and then closed out of it via the task manager and decided to soft reset it. I always soft reset during the morning just because I noticed there are memory leaks and soft-resetting normally resets the memory back to normal. After soft-resetting, it would hang at the Windows Mobile 6 Professional boot loader screen and will not continue. I even left it sitting there thinking it would load but I even let it sit while it drained the whole battery. I then plugged it into the charger and proceeded to soft reset it again and still does the same thing. Yes, I originally flashed it to the Tmobile rom before flashing the Tnt1933 image and yes its both unlocked (forgot the terminology). I tried taking the battery out for awhile thinking it would clear the memory or whatever and that didn't do anything. What I can do though is enter it into the bootloader mode with the 3 color screen but I do not want to reflash since I have important files that were not copied to my SD card. If there is a way for my PC to recognize my phone so I can at least copy the files I need, then I can reflash the OS again via the bootloader screen since I can get to that mode at least.
EDIT- Could this have been caused by the battery mem program overclocked at 247Mhz (the recommended for the 8125)? Since I never installed anything else except the main programs that were included in the image of the TNT 1933, the only thing I could think of was the extended overclock and overtime, corrupted the files from overclocking...just my 2 cents

lenell86 said:
Hello All,
I have the TNT 1933 image loaded on my Cingular 8125 and have been running it fine for almost a month with little to no issues. The issues I had were minor kinks here and there but did not hinder the phone usage at all and has been working fine till up to this point. I was reading my e-mails via the exchange setup to my company exchange server and then closed out of it via the task manager and decided to soft reset it. I always soft reset during the morning just because I noticed there are memory leaks and soft-resetting normally resets the memory back to normal. After soft-resetting, it would hang at the Windows Mobile 6 Professional boot loader screen and will not continue. I even left it sitting there thinking it would load but I even let it sit while it drained the whole battery. I then plugged it into the charger and proceeded to soft reset it again and still does the same thing. Yes, I originally flashed it to the Tmobile rom before flashing the Tnt1933 image and yes its both unlocked (forgot the terminology). I tried taking the battery out for awhile thinking it would clear the memory or whatever and that didn't do anything. What I can do though is enter it into the bootloader mode with the 3 color screen but I do not want to reflash since I have important files that were not copied to my SD card. If there is a way for my PC to recognize my phone so I can at least copy the files I need, then I can reflash the OS again via the bootloader screen since I can get to that mode at least.
EDIT- Could this have been caused by the battery mem program overclocked at 247Mhz (the recommended for the 8125)? Since I never installed anything else except the main programs that were included in the image of the TNT 1933, the only thing I could think of was the extended overclock and overtime, corrupted the files from overclocking...just my 2 cents
Click to expand...
Click to collapse
I highly doubt that batterystatus was what caused this because I have used batterystatus with every ROM I have ever used and have never had this problem.
As much as I hate to say this... As for your important files, you might as well kiss them goodbye because they're already gone. If your device will do nothing buy enter bootloader then the boot sequence on your phone is corrupt and you have no other choice, if you want your phone to work again, but to flash that T-Mobile ROM(or you can flash the 8125 official ROM found HERE.)
I know this isn't what you wanted to hear but you cannot connect to your device from activesync if you can only reach bootloader and nothing else and if the files are not on your storage card, they're gone.

Well, even if you were running Battery status, did you actually do an overclock or did u just leave it on default settings upon installing? OMG I'm gonna cry Those files are like my life I just want to understand how this happened when I installed nothing at all and it had been working fine for almost 4 weeks with no issues. Just went to hell after soft-resetting.

Odd bootloader issues.

I had posted this in the stickied bootloader thread, but I'm pretty sure I posted to the wrong spot. If a mod wants to move this to another thread then by all means...
My kaiser is doing something I haven't heard of yet. Recently its started to act funny after 6 months of no new software, tinkering, flashing - nothing.
3 days ago I had to restart due to the sound cutting out and I got stopped at the bootloader. After fiddling with it, soft resetting multiple times, taking out the battery (just random low level troubleshooting) it booted into windows. This happened sporadically one or two more times.
I have also noticed that in the last 3 days the phone will suddenly drain to no battery without any warning. I will have 25% battery and be on a call for 20 minutes, then have the phone completely power off. normally, windows alerts me to high heaven with multiple warnings, etc. None - just powered off. After 30+ minutes of recharging in the off state, I powered on... bootloader again.
I hooked it into USB and sent the mtty "boot" command. This worked, it booted straight into windows. Due to my frequent sound problems I figured I'd load on a new radio "just in case" - so I loaded on the eMo radio via the sd card method, and soft reset. Again, bootloader. So I gave it the mtty BOOT command and got into windows... so far so good.
I soft reset just to see what would happen - bootloader.
Now I find myself having to soft reset frequently because the sound will just stop working at random. Of course when I soft reset I get bootloader but just today I found something very interesting: If I plug the phone into USB then simply soft reset it will restart and go right into loading windows. This works from inside windows as well as when I'm stuck at bootloader.
Is this common? My rom is Dutty's 6.1 from April 29. My radio is currently 1.71.09.01.emo. Thanks guys
*edit* now every time I hang up a phone call the earpiece starts making a "TV snow" or "power lines" kind of noise. This of course requires a soft reset which may or may not send me into bootloader. it varies.

I'm no flashing or rom expert by any means but if I were you, I would remove SD card, flash a different hardSPL other than what you're using now, flash a another cooked rom, and another radio. Starting from scratch sounds like the way to go. Good luck ...

I flashed a new SPL (3.29 fixed) and switched from dutty's to hyperdragon III Nov 6. I'm pretty sure this has fixed it.

Omg i f***ed up!!! Ryan mogul i know you can help pretty please with a cherry on top!

Ok i was forum jumping and i tried a titan rom... I hate it !!!!!!!!! It changed my windows 6.1 to something i have no clue what it is now and i just want everything back to normal. I reinstalled my raphael cdma hard spl and my windows is still on the ugly a** blue and orange screen and i dont know what to do. My email is [email protected] if you can help me you may have to call me or email me direcxtly ill be here all weeek night and day trying to fix this!!!!!

If you flashed another device(htc titan) rom onto your cdma htc raphael, most likely you brick't it, can you see a tri colour screen? if you can it means your device its sitting on bootloader mode since the rom image it has flash is not compatible with it, just grap a OEM cdma rom and flash it, everything should be fine, that is if that screen your phone is stuck in is the bootloader screen, which i bet it is.

Good advice above, follow it. And ffs, read your device wiki before flashing next time, what were you thinking flashing another devices rom to ur Rap?
As said above, if you cant get into bootloader, ur fu##ed, so i hope you can.
Good luck.

Ok so i didnt brick my phone i got everything back to stock now from here any suggestions on getting my wap to work and also my incoming pix? I have tried all methods i have found online and i actually had the wap working at 1 point but i messed that up as you can tell.

Now that doesnt make sense.
I also tried an upgrade to my Mogul from ryans stuff. Started going through boot loader and all of a sudden the screen went to red green blue and white. Very patriotic. but lost windows mobile center. So I wasn't sync'd anymore. so I could proceed in the install until. Sync'd. I can syn' I assume because the phone in a bootloader mode. Tried a hard shut down and everything else. Just trying to get back my 6.1 now. can't until I can sync. Can't sync until I have an OS to sync to. Im a little lost.

Neither bypass nor Filter Wizard recognizing the phone.

I think I killed my phone. I lil' story -- i decided to flash my Redmi 9A, flashed PBRP onto it and.. Black screen. I already faced it, so I just try to flash original firmware with SP Flash and... Error. Can't quite remember what it was. I try to use bypass, and although bypass does give the "Success" output, SP Flash still gives the same error. I google this error and it seems like it is an issue with drivers. OK, I remove all the drivers and try again. It got zero battery at this point. Now it's not recognized by PC at all, Windows gives no error, FIlter Wizard doesn't even recognize it, Bypass gives a driver error. I'm sure I installed all the drivers correctly. I also tried:
To use my installation of Arch Linux using this guide, no success, bypass doesn't recognize the phone
This LIveCD, where all the drivers should be properly installed, but no success, same as every other try
I'm very stuck. Any suggestions?

ignaycyhry said:
I think I killed my phone. I lil' story -- i decided to flash my Redmi 9A, flashed PBRP onto it and.. Black screen. I already faced it, so I just try to flash original firmware with SP Flash and... Error. Can't quite remember what it was. I try to use bypass, and although bypass does give the "Success" output, SP Flash still gives the same error. I google this error and it seems like it is an issue with drivers. OK, I remove all the drivers and try again. It got zero battery at this point. Now it's not recognized by PC at all, Windows gives no error, FIlter Wizard doesn't even recognize it, Bypass gives a driver error. I'm sure I installed all the drivers correctly. I also tried:
To use my installation of Arch Linux using this guide, no success, bypass doesn't recognize the phone
This LIveCD, where all the drivers should be properly installed, but no success, same as every other try
I'm very stuck. Any suggestions?
Click to expand...
Click to collapse
If u install a recovery rom and you did it wrong you can boot to fastboot, no?

Hey I faced similar or even worse (twice), I had a similar story to yours,
FIrst itme:
I first bricked my phone, but it was cool, the phone just flashed MIUI for a fraction of a second when trying to go to recovery, other than that, nothing, I tried flashing, wich made it much much worse, black screen, no key combo did nothing, windows not just did not recognize it,it told me there was no way of recognizing it, (error 43 in devices admin, its not posible to reinstall the driver, nor do crap at this point) filter wizard showed nothing, bypassing imposible, etc.
It got pretty similar to what you had:
I just left the phone do some charging discharging cycles (at least 4 days with me checking if the phone did anything at all almost once every day, just so you know the phone was really bricked) and it eventually responded after all that (Im not quite sure what fixed this, I dont kno if it was complete discharge or what, but something happened and it vibrated when holding the pwr button.
Once that worked, I managed to install the filter by pressing volup voldown and conecting the phone to the USB port (dont use 3.0, it works worse for some reason) at the same time, you need to connect and press the buttons and connect at the same time (
at 1:30 he does it, video on spanish) and then you can install the filter.
Then you can Bypass and attempt to flash with SPflash tool, I recomend autoconcect, UART never made it for me, Im thinking thats for when you can put it in EDL mode by presing the test points, but I dont know enough to say for sure, point is, UART never worked for me, even tho I eve know what comms I was using.
second time:
I was running Custom ROM ArrowOS 12, ArrowOS13 came out some weeks ago, so I decided to lash it, it was better in some areas and worse in others, the contacts app did not work, but now Volte fingerprint(irrelevant to us redmi 9a users) and face unlock did so I decide to test some stuff, I wasnted to flsh boot.img from original MIUI ROM on top of ArrowOS13, to check if that fixed some stuff (that worked wonders on ArrowOS12) that bootloped thephone but it was fixable from recovery, I did that and decided to flash MIUI ROM to check if flashing ArrowOS13 from MIUI ROM worked, and flashing MIUI bricked my phone.
unrecgnized with error 43, not posible to fix from software, black screen no response whatsoever from any key combo (all 7 combos) no charging, no filter, no nothing, I know I had around 50% battery (days ago I remembered the exact number, now I forgot it, but just so you know, its not a hunch, I knew it had battery) I tried doing the same stuppid crap, charging and leaving it alone for couple hours, but after one night nothing worked, so I assumed I would have to repeat the procees I did before (I wrote it complete on an unbricking thread so I knew I could go back there and redo that or variate it until it worked), but I decided to do one final thing.
I knew it had battery, so I decided to try and forcedrain the battery, I took a piece of TP and gave it a turn around the phone over the buttons (this is just to not dirty the phone) then with electrical tape, I left the power button and the vol down button pressed) this for around 7 hours my plan was leaving it like that for a full day, but around 6 hours I thought I heard a vibration from the phone, so I kept it with me, then after a while I thought it happened again, but I also had my own phone with me so I thought it was that and some other things distracted me so Im guessing I missed a few, but after that I started to take time from every vibration and yeah, around every 8 - 10 minutes the phone vibrated
I decided to connect the phone (I hadnt before because it would just slowdown the battery draining process) and the phone conected to the pc, still bricked, but it was a lot better, I quickly installed the filter, wich I dont quite remeber, but it wasnt easy, I had some hickups, cmd bluescreened my PC when using Bypass like 6 times, so I switched to powershell and that worked (to do that you need to press shift+right click and open powershell here, then run "python main.py") that worked, but I did not flash using SP flash tool.
I was trying to avoid turning on the phone for fear it would go back to the previus state, but after a while pluged on the PC it showed the no battery logo so I tried to tun it on and it was bootlooped, I was able to go to recovery and fastboot (not normally, I pressed the keys, the phone try to go into those menus, it showed no battery, and in the next cycle after splash logo no matter what you did it sent you to the previus key combo menu) I tried leaving it charging on fastboot, but that did not work, I tried flahing a rom from recovery (wich said I had 47% battery) and it successfully did but when trying to reboot to system it again showed no battery logo. so I put it on fastboot and tried flashing MIUI with Miflsh, did not work but it told me the ROM was bad (same one I had use before) I made sure to extract it again and again nothing, I assume it was the antirollback, so I downloaded the next one on line 12.5.6.0 (I was on 12.5.4.0) and that finally worked (Miflash actually gave me lots of errors but you can google them and most of them have easy fixes, like creating a log folder, etc)
that was yesterday, after it worked it showed me the phone had around 60% batterywich lasted around 30 minutes to 40%, then it took 10 minutes to spend the next 20% (it told me that) and then it drained 1% every second (Im not exagerating I thought I had fried my battery with all that power button pressing) but I had hopes of it just being a configuration issue of the phone not knowing how much battery it had so I just left it power of and pluged it then so the phone knew what was his zero, now the phone as been on 100% for like 2 hours (sharing internet), so yeah, I think the battery has some issues but its better than nothing so Im happy with that.
that is my whole experience, I hope it helps you, see if you manage to get any response from the phone and if you do you can try contact me for help in any point along the way.
Update, it just got to 99% after 2 hours 10 minutes aprox IDK, I would need to test more to be sure