ROM upgrade failure - Upgrading, Modifying and Unlocking

I attempted to upgrade the ROM on my PW10B1 (siemens SX56/ ATT Wireless) from version 3.14 to the XDA-developers Special Edition ROM v1.2. Unfortunately, I was in a hurry and did not backup the ROM image of the XDA prior to the upgrade. The error msg stated that "Critical errors had been encountered during the upgrade and that the process had been terminated." My operating system is now inoperable. My device now displays a Wallaby Bootloader v5.15 screen when I do a hard reset and my PC does not recognize the device when it is placed in its USB cradle. I assume that I will have to do a SD card flash of the ROM but do not know how to begin. Has anyone else encounterd this problem?

Related

JASJAR always go to bootloader mode - how to fix it?

I downloaded the Dopod 900 rom, wishing to change my PPC into Traditional Chinese. But after running the no id exe file. It reboot my PPC and said the country ID is not correct.
Afterwards I run the bootloader.exe on JASJAR. And it automactially go to bootloader mode. I'm able to upgrade my PPC rom. But after the cold reboot the system go to bootload mode (ask me to insert serial or USB cable). How can I get PPC work?
you always have to start your device in bootloader mode manually before upgrading.
as you didn't, special bit in the device was set, to start it always in bootloader mode now.
rerun the upgrade with MaUpgradeUtil_noid.exe again. it will fix it.
buzz
I got the same problem after upgrade to a new version complately but always still on bootloader mode,I have rerun the upgrade but still got same problem.Help please.
Reset while holding the power button
xdaIIse said:
I got the same problem after upgrade to a new version complately but always still on bootloader mode,I have rerun the upgrade but still got same problem.Help please.
Click to expand...
Click to collapse
Reflash the Jasjar again. But use the Radio Rom 1.04.02 only. Then do a reset.
Is here nobody who can read?!
Here is the answer how to solve the problem:
http://forum.xda-developers.com/viewtopic.php?t=33191
Or if you're unable to open the link:
make the update w i t h o u t any card (sd-card and sim-card) and you'll see: it works. Maybe you've to run the update twice without changing anything!
Teja
Hi,
I had a similar problem, system and unit both indicated a successful ROM flash but after the reset remained in bootloader mode ("Serial v1.00).
In the end I did a final JasJar ROM flash, then did the radio only ROM flash and after radio done, a reboot worked.
Maybe try the 1.04.02 radio only ROM flash and see if that works.
Note: during the last two ROM flashes I too had removed the SIM and SD cards.
Note: I had removed the SIM and SD cards for a number of ROM flashes prior to that, so I know how you feel finding out that wasn't the quick fix I read. But try all that in combination.
Regards
Michael
most of the time reviving a dead universal is easiest with another rom upgrade of the radio flash.
If your universal boots in usb mode (bootloader), I can confirm your universal is dead. Mostly caused by using an upgrade program that was not made for the universal. For instance using a cracked magician upgrade program to force universal upgrades. In most cases this will get you a dead universal which can easily be repaired by doing an aditional radio rom upgrade (even if you already have that radio upgrade)
Hi,
I can confirm that in the 2 instances of bricking my device (unable to get out of bootloader mode) that the radio only upgrade (1.04.02) got it working again.
I've done this for both the JasJar and Qtek ROMs (currently running Qtek).
My unit is a Dopod 900 originally purchased in Taiwan.
Regards
Michael
i had the same problem with the QTEK of my principal after I upgraded his ROMs.
(after the hard reset, the pocket remained in bootloader mode).
you can solve this problem in a very simple way:
you have to launch the bootloader installation (BL1.01_RUU_UNI_V.1.2.EXE) from the PC (still connected with the PPC through USB) while the PPC is in bootloader mode (on your display you see "USB > Serial 1.01" or something like that).
then you do a SOFT reset and the pocket boot normally.
very simple.
i hope to be helpful to someone.
Yep, i agree with u parallel666killer, it worked by just reinstalling the bootloader (BL1.01_RUU_UNI_V.1.2.EXE).

Updating to Hardspl v7 and computer froze need massive help

well this is my last post for the night its 2:30 and I'm tired. I'll be checking up in the morning and maybe bumping my post for more answers.
while installing oprilo's hardsplv7 my computer froze and my phone was stuck on 47% I restart my computer and reset my phone only to find it stuck in the bootloader mode spl 2.03 from the official wm6 from cingular I had on my phone. so I reinstall the cingular 3.57 software onto my phone using the install wizard. it was the only way to unbrick it. when I went to try to download most roms I get the error [240] check update utility. reading the forum it says that code is given when you have a corrupt file.
Now you know my situation here is my question, How the h*** do I totally redo my phone back down to wm5 and spl 1.04 again? or is there another way to fix my semi bricked device? I've read the unbricking page and wasn't finding anything specific to my device.
Try using SD Card flashing
or
starting with phone in bootloader mode, then hook to PC, then start update and select the correct SPL version when prompted.
Crashing while flashing SPL can be a bad thing.
I was wondering about the SD way. its wierd I can flash using sspl with pandora kitchen and it uses the bootloader 1.09, but after its done flashing the new rom and go look at the bootloader screen again its back at 2.03.
I'll try the SD way if that doesn't work, I guess I'm stuck with the highest radio using install method from cingular. although I'd really like 1.50 radio. since I have gsm network over here
Yeah, you're playing with fire whenever you flash the radio. That's where unrecoverable bricking can occur, esp. if you don't have Hard-SPL installed.
Try another PC if you can't do SD flashing... sounds like flakey USB issues to me.
best to set your phone down and don't touch it or the cable until its finished.. also make sure you have a stable machine

Problems with my HTC Excalibur ROM Upgrade

I recently installed 3VO's Windows Mobile 6.5 ROM and i used it for a few days
Then i started having problems with it sowing down so i tried to get another ROM
But everytime i tried to install a new ROM my computer would say "The system cannot find the path specified "Excalibur<Dopod C720/720w, HTC S620/S621, T-mobile Dash> ROMUpdateUtility
I tried installing the official ROM back on to my phone and it worked
But now when i try to flash any other ROM's my compuer gives me that msg again.
I need a updated ROM because i have a 4gig SD card and it is not compatible with the Official ROM
Can someone please help me with this Problem???
Are you remembering to Application Unlock your phone prior to trying to update again?
yea i run the SDA application unlock and the screen comes up and i click remove lock
Then when i run the ROM update
it gives me that msg again
Are you making sure during the FLASHING process to click the center button on your phone to initiate the flashing mode?
---At one point after the cmd file copies and runs some files on your phone, it will tell you a disclaimer about flashing and ask you if you want to proceed. There is a button that says YES, you click the center button and then you enter the 'bootloader'/flashing mode (to my understanding). Someone else had this issue...they forgot this and that messed them up...
when i begin flashing it shows that msg
And when it gets to the step that your talking about my phone doesnt react and show anything at all

Error [244]: Invalid Model ID, on flashing a PTB rom

Hi
I had my S620 aside, haven't used for 3 years.
Now I'm trying to give it to a friend and i need to put a Portuguese rom on it.
I know I've change the stock rom to the 3VO.2.80.092509 and now I want to flash the official portuguese rom.
I've downloaded it (RUU_Excalibur_BRIGHTSTAR_PTB_1.30.514.2_4.1.13.47_02.98.90_Ship Extract) from official rom's page but when I try to flash it, it gives me the Error [244]: Invalid model ID, at 3%.
Well, the rom is for Excalibur, i flashed a rom before long time ago, do i need to update the HSPL ?
What am i doing wrong?
Thks for your help.
Regards
My Excalibur especifications:
On Bootloader
Excalibur
ONBL 1.30.0000
SPL 1.30.0000
Windows Mobile 6.5
OS: CE OS 5.2.23004 (build 23005.5.3.0)
ROM: 3VO.2.80.092509
Radio version: 4.1.13.47_02.98.90
read carefully
i overclock mine and i solve it. go to windows mobile center and disable usb connection. press and hold sym while pluging in usb( this will take you to bootloader mode) and run uspl from the cid bypass after that run the original rom. if it does work go back to stock rom and run cid bypass and ru the rom you metion.
http://forum.xda-developers.com/showthread.php?t=329605
http://forum.xda-developers.com/showthread.php?t=328690&highlight=cid
XicoBombas said:
Hi
I had my S620 aside, haven't used for 3 years.
Now I'm trying to give it to a friend and i need to put a Portuguese rom on it.
I know I've change the stock rom to the 3VO.2.80.092509 and now I want to flash the official portuguese rom.
I've downloaded it (RUU_Excalibur_BRIGHTSTAR_PTB_1.30.514.2_4.1.13.47_02.98.90_Ship Extract) from official rom's page but when I try to flash it, it gives me the Error [244]: Invalid model ID, at 3%.
Well, the rom is for Excalibur, i flashed a rom before long time ago, do i need to update the HSPL ?
What am i doing wrong?
Thks for your help.
Regards
My Excalibur especifications:
On Bootloader
Excalibur
ONBL 1.30.0000
SPL 1.30.0000
Windows Mobile 6.5
OS: CE OS 5.2.23004 (build 23005.5.3.0)
ROM: 3VO.2.80.092509
Radio version: 4.1.13.47_02.98.90
Click to expand...
Click to collapse
so weird
Ratchewer said:
i overclock mine and i solve it. go to windows mobile center and disable usb connection. press and hold sym while pluging in usb( this will take you to bootloader mode) and run uspl from the cid bypass after that run the original rom. if it does work go back to stock rom and run cid bypass and ru the rom you metion.
http://forum.xda-developers.com/showthread.php?t=329605
http://forum.xda-developers.com/showthread.php?t=328690&highlight=cid
Click to expand...
Click to collapse
Hi
I did what you've told, ran uspl from cid paypass, all good till the screen stayed almost white.
When i tried to install PTB stock rom the flasing frooze at 0%.
Had to unplug the usb cable, and now each time i turn on the pda it goes to bootloader mode everytime.
Tried to flash through sd card all the stock roms i found without success. All the attempts through usb cable didnt passed 0%.
It starts to check the sd contents but then goes straight away to 3 colour bootloader mode without doing anything.
Then i remembered i had to install the original stock rom, which was the BT brand, that i found yesterday.
Now comes the weird part.
First time i try to flash the BT brand rom, it installed the rom (i didnt quite saw the whole process), and when it restarted it self, went again to bootloader mode.
Tried hardreset, tried to flash again, it goes straight to bootloader.
What the hell is going on???????
In my whole flashing history, i had 100% success over 50 flashes, and now its freaking weird.
Can you lead me again?
Thanks for everything.
Greetings
Try this here
ok go back to the original phone stock rom from the service provider and start over. use the usb bootloader mode after run the xda applicationunlocker file and do the cid bypas. then run the utilityupdate from the other rom ( not the one in the cid bypas file in the link) meaning do not click yes to the windows security prompt skip and run the romm u want to use
XicoBombas said:
Hi
I did what you've told, ran uspl from cid paypass, all good till the screen stayed almost white.
When i tried to install PTB stock rom the flasing frooze at 0%.
Had to unplug the usb cable, and now each time i turn on the pda it goes to bootloader mode everytime.
Tried to flash through sd card all the stock roms i found without success. All the attempts through usb cable didnt passed 0%.
It starts to check the sd contents but then goes straight away to 3 colour bootloader mode without doing anything.
Then i remembered i had to install the original stock rom, which was the BT brand, that i found yesterday.
Now comes the weird part.
First time i try to flash the BT brand rom, it installed the rom (i didnt quite saw the whole process), and when it restarted it self, went again to bootloader mode.
Tried hardreset, tried to flash again, it goes straight to bootloader.
What the hell is going on???????
In my whole flashing history, i had 100% success over 50 flashes, and now its freaking weird.
Can you lead me again?
Thanks for everything.
Greetings
Click to expand...
Click to collapse

Device descriptor failed after bootloader update

Hi all, learning fast, not there yet, so forgive me if I ask something less than brilliant here
I can't connect my Tab S 8.4 wifi to any pc anymore (tried 4 different PCs and 4 different cables) after upgrading bootloader with Odin last year.
I keep getting "device descriptor failed" in Device Manager (both win7 and win10).
My son did drop and break the usb/power port which I replaced myself. Could be a hardware error, but everything worked before and after my repair, just not after bootloader upgrade. Forgive me, I don't know which bootloader is currently installed, in any case one which works with android 5.1 and not with 7.1, which I unsuccessfully tried to flash.
COderbear was so kind as to direct me towards the bootloader, which I thought TWRP was.
Since I cannot connect to a PC, I cannot update the bootloader....catch 22...
Thx for ur input.
Ps Hardware failure is a possibility, but not conclusive guys. Tablet is working fine.
In what way have you been flashing stuff have you been doing anything on trwp or oden......
stinka318 said:
In what way have you been flashing stuff have you been doing anything on trwp or oden......
Click to expand...
Click to collapse
I used ODIN to update bootloader 1-2 years ago to flash an original Samsung ROM which was already rooted. After the bootloader flash I cannot connect to a PC anymore.
I n the mean time I have learned about TWRP and used it to flash a custom ROM, all via SD card, as I cannot connect to a PC.
The only one which did not get me stuck at the black Galaxy TAB S screen is the cm12.1 custom ROM with android 5.1.
All others (see above) with android 7.1 have gotten stuck.
I thought TWRP was the bootloader, but it isn't, kindly pointed out by COderbear in another thread. :good:
As I understand it, the only way to update the bootloader to a current version to successfully upgrade to a custom 7.1 ROM.
Since I cannot connect to any PC => "device descriptor failed", I cannot update the bootloader with ODIN.
So I cannot upgrade to an android version above 5.1. That's the problem.
Mace73 said:
I used ODIN to update bootloader 1-2 years ago to flash an original Samsung ROM which was already rooted. After the bootloader flash I cannot connect to a PC anymore.
I n the mean time I have learned about TWRP and used it to flash a custom ROM, all via SD card, as I cannot connect to a PC.
The only one which did not get me stuck at the black Galaxy TAB S screen is the cm12.1 custom ROM with android 5.1.
All others (see above) with android 7.1 have gotten stuck.
I thought TWRP was the bootloader, but it isn't, kindly pointed out by COderbear in another thread. :good:
As I understand it, the only way to update the bootloader to a current version to successfully upgrade to a custom 7.1 ROM.
Since I cannot connect to any PC => "device descriptor failed", I cannot update the bootloader with ODIN.
So I cannot upgrade to an android version above 5.1. That's the problem.
Click to expand...
Click to collapse
I have had a lot of Samsung device and this is a first i have heard of this i have flashed the wrong stuff and soft bricked things but never heard of having issues with the bootloader up date........
stinka318 said:
I have had a lot of Samsung device and this is a first i have heard of this i have flashed the wrong stuff and soft bricked things but never heard of having issues with the bootloader up date........
Click to expand...
Click to collapse
Yeah, but ur not me
I have a sneaky suspicion that it's the usb port which I've swapped.
I've found two threads somewhere on Google relating to using another cable, must be a hardware failure or substandard part.
Can't explain it otherwise.
There is no way to update a bootloader via SD, right?
Logical, the bootloader's the first thing it reads to start up.....
Anyway, thought it was worth a try to post a thread, u never know what crazy solutions come to pass in android world.... (iOS too for that matter)
Mace73 said:
I have a sneaky suspicion that it's the usb port which I've swapped.
I've found two threads somewhere on Google relating to using another cable, must be a hardware failure or substandard part.
Can't explain it otherwise.
There is no way to update a bootloader via SD, right?
Logical, the bootloader's the first thing it reads to start up.....
Anyway, thought it was worth a try to post a thread, u never know what crazy solutions come to pass in android world.... (iOS too for that matter)
Click to expand...
Click to collapse
Bootloader can only be updated with oden only any thing else won't work.......
It is not issue of fleshed software. I have this issue during last 2 months. Official service center didn't find any clue during 2 weeks so i get back my Tab. All story starts, i suspect, after 1 month using magnet cable. Then suddenly charging current start to be lower then usual (Galaxy Charging Current App) and i decide to check different chargers and PC. I found that tablet cannot connect to any PC - "device descriptor failed". During playing with "USB debug" on/off and USB modes i connected tablet to PC once. But during Odin flash it stuck in "Getting PIT file..." and i still didn't update anything.
I suspect that it is some hardware issue in part that responsible for USB communication.
Issue solved. Tried on different ports with combination USB-hub. On some ports it completely invisible, on some "usb device not recognized". But after two weeks once i get connected and Tab was detected - then immediately flash stock CQB1 with TWRP 3.1.0. Now it still detected by PC.
I suspect micro-crack in motherboard or some HW issue on some SW combination (modem SW).

Categories

Resources