View Single Post
  #4 (permalink)  
Old 05-26-2008, 04:52 PM
gguruusa's Avatar
gguruusa
Deep Thinker
Offline
Location: Mountain top
 
Join Date: Jan 2007
Posts: 3,252
Reputation: 4726
gguruusa should be added to the payroll for their contributionsgguruusa should be added to the payroll for their contributionsgguruusa should be added to the payroll for their contributionsgguruusa should be added to the payroll for their contributionsgguruusa should be added to the payroll for their contributionsgguruusa should be added to the payroll for their contributionsgguruusa should be added to the payroll for their contributionsgguruusa should be added to the payroll for their contributionsgguruusa should be added to the payroll for their contributionsgguruusa should be added to the payroll for their contributionsgguruusa should be added to the payroll for their contributions
Mentioned: 0 Post(s)
Tagged: 0 Thread(s)
Re: 1ST WM6.1 ROM Update failed, stuck on boot screen, now what?

Quote:
Originally Posted by shonn.burton View Post
So let me clarify. The ROM flash did not fail. It said it flashed successfully. My problem is that it doesn't boot into the new ROM, it just hangs on the bootup screen. I did put mu phone in bootloader mode but when I tried to reflash it gave me a connection error. I will try all of the suggesiton posted here and post my results. Thanks for all the help!
I understand. It is possible to build a rom that is too big, yet there is no error generated. The current rom size limit is set for the same for all bootloaders, but is only accurate for v1.00 bootloaders (the biggest possible ROM) These roms will flash, but fail to boot. Putting your phone in bootloader mode and flashing a smaller rom will usually fix the issue. In rare cases, 2.04/2.05 bootloader phones will get an Invalid contry code error, which usually is only solvable by reverting bootloader to 2.02 and using the no_id RUU.
__________________
Grammar: The difference between knowing your shit and knowing you're shit.
Reply With Quote