Related
I just tried to upgrade my MDA Compact from German ROM to English ROM. Downloaded the latest O2 Asia English ROM from FTP, then used NoID EXE to upgrade.
After step 1 of upgrading Radio was completed, error message 'EXTROM Upgrade Error' raised, then, the MDA only stayed in Bootloader. No matter matter how many times I re-tried, it failed before step 2 of upgrading the Extended ROM.
I tried SD Card Flashing method. But it was no way to read the ROM (with using Romupdate.exe) successfully.
Anybody could help? Really need your advice. Thanks!
Be sure your battery is fully loaded. I think, that was my problem when I tried to upgrade. During bootloader mode, your Magician will NOT charge through the USB Cable.
Cherek said:
Be sure your battery is fully loaded. I think, that was my problem when I tried to upgrade. During bootloader mode, your Magician will NOT charge through the USB Cable.
Click to expand...
Click to collapse
I used a fully charged battery (charged by another MDA) for upgrade. Problem still existed. Any further suggestion? Thanks!
Nope, maybe you can try another ROM?
BTW.Did you charge it between creating your ROM backup and your upgrade? Cause creating a backup also cost battery power, and if you don't charge between the failures, your battery will also be drained. I finally let my battery charge for about 1,5 hours on the normal adapter and after that mine did work. But like I said, maybe you should try a different ROM.
I tried several different ROMs, but failed again and again. Even using SD flashing method, error of 'Download Fail' occurred after pressing Power button to try to load the ROM image from the prepared SD card.
Any help there? Is my MDA totally dead?
I tried at least 5 different language ROMs, but failed all the time.
Seems there is no way out.
Hic ! I have the same error, so my XDA mini dead too ! hic
anybody can help me ??
Hmm. The one thing I can think of is that seems to happen if you try flashing a device *with the SIM card still inside*. Take out the sim card - heck, take out the memory card as well, unless you're using *that* to flash, and try again.
Funnily enough, I didn't run into this problem while I was on my old Mini, both original ROMs and BigStorage - but I see this quite often when trying to flash my Atom (message "Extended Rom Format Fail").
What I did was to ensure everything 'cept the battery was out, and to keep on trying until it goes right past flashing 6% of the extROM. >_>
(BTW: if you can find it, and don't mind having to go CAB hunting, go BigStorage. IIRC you'll skip the extROM bit. Eheh.)
I've have tried each Rom in the TNT 1437 series and they all shut down and restart my phone when I'm on a call. Does anyone know what could cause this.
thanks
nutathis said:
I've have tried each Rom in the TNT 1437 series and they all shut down and restart my phone when I'm on a call. Does anyone know what could cause this.
thanks
Click to expand...
Click to collapse
What IPL/SPL?
What Radio?
Did your try non TNT roms?
Did you flash your carriers official ROM before you flash a custom ROM first?
calouro said:
What IPL/SPL?
What Radio?
Did your try non TNT roms?
Did you flash your carriers official ROM before you flash a custom ROM first?
Click to expand...
Click to collapse
I just reflashed to a non tnt rom and it happened again so I'm sure its not TNT rom. I think the IPL/SPL was the same from the TMO 226 and the radio was 2.19. thanks for responding. I'll try it again using the cingular stock rom.
Radio Restart
Well first flash to a factory rom to make sure your extended_rom is clean and uncorrupted, it causes all kinds of problems if it is..
second, if this is happening on the 4min threshold then sounds like you have enableed the "grpsstallworkaround" found in some registry editor, turn that off...what the workaround does is just that, restarts the radio every 4min.
took me forever to figure this one out when I had it...I thought it was a good thing...nope its a gremlin!!
Hope this helps...
Phone maybe dead
I can get into bootloader mode to reflash the phone but now the phone will get to about 99% done and then restart again in bootloader mode. The phone will restart about 2 times before I can attempt to reflash again. Once I attempt to reflash the process starts all over again. Any ideas what could cause this or is the phone D.O.A.
thanks
I had the same problem, I charged the battery overnight (you might not need to charge overnight, but I bet your battery is low or going bad.) and used a small ROM I built so it would load faster. I think a factory ROM would have loaded once I got the battery level up but before it was rebooting after about 3 minuets into the load.
I have an unlocked 2125 on the T-mobile network. I upgraded it to WM6, there was no problem. I then decided to go with a different ROM so I flashed it to that one. Now my phone shuts off whenever I try to make a phone call or when i'm in the middle of something, if I reboot it, it will just shut off again. It is getting charged long enough. I Don't know what the problem is, but once I take out the SIM it powers on just fine.
Any insight will be appreciated.
Try to format BINFS and start everything all over again
I did try this, didn't work. The phone still shuts off. Decided to try it again, now it just shuts off when I try to go into the bootloader.
Assuming it's the battery now.
Dude, flashing when the battery is low is very dangerous
etnoo said:
I upgraded it to WM6, there was no problem. I then decided to go with a different ROM so I flashed it to that one.
Click to expand...
Click to collapse
Which ROM did you use? Did you upgrade the GSM/SPL as well?
http://forum.xda-developers.com/showthread.php?t=321665
Used this one. Didn't realize it was dangerous btw, but I didnt flash when it was low. Yeah I upgraded the GSM
It is a dangerous procedure if you do not know what you're doing. Andot's PEE is a very old version. I'd suggest to install vjgrace's latest ROM (v3.3).
ok, but I dont think the battery is getting a charge >< wont stay on for long
Ok, I really have read existing threads related to similar problems, but I am completely stuck on the boot screen (not bootloader screen) with my Tilt.
I flashed Dutty's 6.1 ROM last week and all had been working fine until last night. The phone was stuck with screen lock (screen nor buttons would respond). So, I performed soft reset and it just stopped at 'smart mobility' boot screen. I then performed hard reset, and again it just stopped and hung at 'smart mobility' screen.
This morning I got into the bootloader screen (power + camera + reset) and flashed original ROM (well, new officiall AT&T ROM released last month). Original ROM flashed successfully, but it now hangs on AT&T boot screen. I have tried hardspl, and flashing multiple ROMs, which all complete successfully, but it always hangs at the boot screen.
Thoughts?
what radio are u using?
Well, with Dutty's I was using 1.64.08.21 that came with the ROM... When I flashed to the stock AT&T ROM, I used the radio included with it as well (1.27.14.09).
tmac said:
Well, with Dutty's I was using 1.64.08.21 that came with the ROM... When I flashed to the stock AT&T ROM, I used the radio included with it as well (1.27.14.09).
Click to expand...
Click to collapse
Dutty's didn't come with a radio.
Well, I was using 1.64.08.21.. Right now, I have the stock ROM flashed with 1.27.14.09
I have a similar problem. I flashed alex rom yesturday then I flashed back to OEM to test something then today I flashed back to alex cube rom and it said flash was successful but when I did a hard reset during the "Tap screen to begin" my phone go stuck in the AT&T inital logo. I tried connecting to USB to reflash but USB won't detect the phone. I have hard reset, removed battery, and no avail. Does this mean I bricked my phone?
To clarify, I have been doing these for some time and also had and 8125 previously, so I understand the flashing process. I also understand that there are only certain radios that work with WM 6.1 and 6.0. This doesn't appear to be a radio incompatibility issue. As I mentioned, I was using Dutty's 6.1 ROM just fine for several days before this happened. I had been using Sleuth's 6.1 prior to that.
Tim
You always should re-flash the radio AFTER flashing the ROM. Pt yuor device into boot loader (hold camera, power & reset button). Reflash the Radio. If that doesn't work PM me & I'll walk you thru looking for bad memory blocks.
hchavarria said:
I have a similar problem. I flashed alex rom yesturday then I flashed back to OEM to test something then today I flashed back to alex cube rom and it said flash was successful but when I did a hard reset during the "Tap screen to begin" my phone go stuck in the AT&T inital logo. I tried connecting to USB to reflash but USB won't detect the phone. I have hard reset, removed battery, and no avail. Does this mean I bricked my phone?
Click to expand...
Click to collapse
NO, it does not mean brick. It means you may want to try another USB port, check the activesync connection settings, & possibly reflash using the SD card.
Edit: After looking at your MTTY feedback, & confering with a few of the Gods, I have to unfortunately tell you that your NAND chip appears to be damaged beyond flushing. The blocks can't even be erased, & that's the problem. When you reflash the blocks have previous ROM data still stored & because of the NAND damage they cannot be overwritten. Return under MFG warranty is all you can do. (Believe me, I really hate saying this & even got confirmation from Pof & Jocky) Sorry Guy.
My 30-day return policy date is tomorrow so I went to the AT&T store today and they swapped it out with a new device. They mentioned next time I have to ship it.
Could this have happened because of to much flashing? Or was this possibly an already existing defect?
I got a new one shipped to my overnight. There was obviously something wrong with it, as I tried everything under the sun. Flashed new ROM, then flashed new radio, flashed original ROM, etc. Everything gets stuck on the boot screen. At one point yesterday, I left it at the boot screen for a couple hours and it finally booted up, but then locked up again once it did. Then next time I reset, it got stuck on the boot screen again.
Please tell me you installed hardspl first?
Soft Reset Looping - Dead Kaiser
Hi all,
I have been flashing/testing many roms for a number of years now. I particularly enjoyed Jasjamming in my Tytn I days. Now...
Great work seen by many developers.
When I first got my Kaiser, i tried HardSPL, and had "white screen" issue, I then followed instructions on "white screen" thread....copied cab to kaiser....ran cab from kaiser..........eventually was able to flash to a new/ different ROM
However, I recently flashed my Kaiser and after using it for 6-7 hours after flash, it soft reset itself. It continued to keep soft reseting itself without geting to boot screen. It kept reading "smart mobility" and it would reset, vibrate, reset, vibrate, reset.......
I tried EVERYTHING - remove battery, flash back to original ROM, change radio (bootloader worked in safe mode - holding down camera button), but to no avail.
I then tried MTTY, and no go with this too. I eventually had to give my phone back in to HTC.
The question I ask is what is the cause of this? Is it excessive flashing? Is is HardSPL? Any comments/ suggestions would be welcomed...
Many thanks
P1Tater said:
Please tell me you installed hardspl first?
Click to expand...
Click to collapse
If you are asking me that question, the answer is yes I did run hardspl. As I mentioned, I have been doing this for long enough that I know what I am doing. I also mentioned that I was successfully running Sleuth's 6.1 for a month or two before switching to Dutty's new 6.1. I was only running Dutty's for a few days before all of this happened.
There is definitely something wrong.. if I let it sit long enough, it will eventually boot. It will work for a few minutes, and then lock up again. Once I reset, it sits on the boot screen for a couple hours again. I have flashed several different ROMs and Radios to get different results, but the results are always the same.. It hangs at the boot screen.
I guess you have also tried going to the tri-color screen and re-flashing as well as a HR or MTTY command
tmac said:
If you are asking me that question, the answer is yes I did run hardspl. As I mentioned, I have been doing this for long enough that I know what I am doing. I also mentioned that I was successfully running Sleuth's 6.1 for a month or two before switching to Dutty's new 6.1. I was only running Dutty's for a few days before all of this happened.
There is definitely something wrong.. if I let it sit long enough, it will eventually boot. It will work for a few minutes, and then lock up again. Once I reset, it sits on the boot screen for a couple hours again. I have flashed several different ROMs and Radios to get different results, but the results are always the same.. It hangs at the boot screen.
Click to expand...
Click to collapse
Please don't take offence to my probing, as my questions weren't directly directed to you. All I am saying is that we need to understand what is the actual cause of this problem, or we all will be "flashing in the dark", and fearing that this problem could be imminent every time we flash in the future.
Many thanks.
P1Tater said:
I guess you have also tried going to the tri-color screen and re-flashing as well as a HR or MTTY command
Click to expand...
Click to collapse
P1 - Since I can't get the phone to boot completely (well, except for waiting several hours), the only way that I have been flashing different ROMs is from the tri-color screen. Regardless of what ROM or Radio I try, it still just hangs at the boot screen. The only thing I haven't tried was MTTY.
AvinashDhaniraj said:
Please don't take offence to my probing, as my questions weren't directly directed to you. All I am saying is that we need to understand what is the actual cause of this problem, or we all will be "flashing in the dark", and fearing that this problem could be imminent every time we flash in the future.
Many thanks.
Click to expand...
Click to collapse
I was actually replying to P1, hence the reason I quoted him. So, I don't take offense to anything you said.
Well, I hope your not getting offended to my questions? I am just trying to cover all of the simple fixes first since those have been the majority of the things that fix "Most" people's issues. I suggest getting in touch with GSLeon3. He has a pretty good handle on what goes on in flashing and all of the fixes.
P1Tater said:
Well, I hope your not getting offended to my questions? I am just trying to cover all of the simple fixes first since those have been the majority of the things that fix "Most" people's issues. I suggest getting in touch with GSLeon3. He has a pretty good handle on what goes on in flashing and all of the fixes.
Click to expand...
Click to collapse
Not offended at all... I am appreciative of the suggestions.
My sensation is turning off randomly. Its very strange i think. sometimes turns off 2 -3 a day sometimes 5 - 10 times a day and sometimes never. i tried to fabrication reset but it cant help. after the reset it starts again in couple of days. My battery is about % 70 but after the turning off it says battery is % 6. then i restart my phone it turns normal % 70. I m not rooted my device yet. Today i spoke with support service they say try to use in safe mod. i used and my device doesnt turns off. but it could be coincidence. I dont know what to do. Any suggestions ?
hi, i have same problem, i am using official rom. i have found this:
http://forum.xda-developers.com/showthread.php?t=1160054
but there is no confirmed reason or method to solve this problem.
does anybody have an idea?? is it software or hardware issue?
soft-reset? hard-reset? or other rom??
help somebody please
I've also had this problem, I discovered that it was what I suspected, the battery. I took advantage and bought a new evo3d battery.
Already spent a month and never had this issue again.
Mains said:
I've also had this problem, I discovered that it was what I suspected, the battery. I took advantage and bought a new evo3d battery.
Already spent a month and never had this issue again.
Click to expand...
Click to collapse
I had the same problem, did a factory reset, a new ROm at the store and nowthey gave my phone a boardswap. i hope that helps....
Same problem here, but not with every Rom and only with the Anker battery... not with the officale htc battery.
i am using official htc battery, official android, now at version 2.3.4, sense version 3.0 and software number 1.45.401.3
i am not sure if flashing other rom helps and if no, i have a problem, bcs with flashing unofficial rom, it breaks warranty.
I try out various ROMs and various kernels including stock rom and kernel. The result was sometimes worked well for a while other times it turn off short time after installation. Turning off some things like wifi, bluetooth and making an underclock the processor helps the phone to hold up better. In my case, having less than 30% of battery life make a call the phone turns off immediately.
This has happened to me on sense miui and cm7 :/
Sent from my Sensation 4g using xda premium
aneroidsk said:
i am using official htc battery, official android, now at version 2.3.4, sense version 3.0 and software number 1.45.401.3
i am not sure if flashing other rom helps and if no, i have a problem, bcs with flashing unofficial rom, it breaks warranty.
Click to expand...
Click to collapse
Root your sensation and flash another rom, it seems like it's a software issue. Also, unlocking your bootloader is what voids the warranty, but there's a way to relock it as well (so if you do get any problems, all you have to do is install the RUU you initially had and relock the bootloader and no one will ever know it happened )
http://forum.xda-developers.com/showthread.php?t=1192300
Here's the thread with the guide to unlocking and relocking your bootloader
Hope this helps
I tried to flashing many roms but it didnt help. I think battery cause this problem. I will buy new battery but not htc`s battery.
snah65 said:
I had the same problem, did a factory reset, a new ROm at the store and nowthey gave my phone a boardswap. i hope that helps....
Click to expand...
Click to collapse
Factory reset doesnt help. Maybe 2 - 3 days it wont turn off then it starts again...
ababak said:
I tried to flashing many roms but it didnt help. I think battery cause this problem. I will buy new battery but not htc`s battery.
Click to expand...
Click to collapse
let us know, if it helps or no
ababak said:
I tried to flashing many roms but it didnt help. I think battery cause this problem. I will buy new battery but not htc`s battery.
Click to expand...
Click to collapse
As i said before, I bought the battery from evo3d and the problem was solved besides that the autonomy is great.
Tell us if with a new battery the problem maintained.