Develop Bugs

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).

bricked or not bricked

hi guys, following this giude ( http://forum.xda-developers.com/showthread.php?p=20365299#post20365299) now, my dhd won't start. After flashing in bootloader mode, pd98img, phone ask to me to restart, then 3 minutes of vibration before start. I decided then, after booting, to install update proposed by HTC in software update;then the phone locks in the update screen without moving forward.What can I do now?tnxx.... can't access to bootloader

I'm not really clear on what you were trying to do here... You've gone through the process of downgrading to an older software version (seemingly successfully), then as soon as you've booted you've tried to upgrade back to where you were before you started?
Have you tried pulling the battery and then trying to boot into bootloader? Does adb recognise the device?

[Q] PC Unable to Recognize Device After 4.3 update

I was looking to root my phone and flash a custom ROM onto it as I had done a year prior. I opened up my Galaxy Note 2 toolkit and applied a stock ROM and rooted it as normal with TWRP recovery and SuperSU. After doing so I realized that the ROM I wished to installed used the 4.3 Android firmware for the phone. So I found and installed the 4.3 firmware for the device, but after doing so it seems as though TWRP recovery and SuperSU have been removed. Also, whenever I try to use the Galaxy Note 2 to re-root my device, it doesn't acknowledge the device is connected. Also, I get this error on my computer where it says it doesn't recognize the hardware connected, yet I can still use it as a media device and move files. Has anyone had the same problem or can help provide some insight?

[Q] Bricked my SM-G925T while attempting to root. PC doesn't detect it anymore.

My phone was on stock rom, 5.1.1, and I tried to root it using zedomax's guide (found on youtube here: /watch?v=G5HDG6caoog) but I ended up bricking it.
When attempting to flash the root kernel provided in that guide, Odin gave me a FAIL result, and after that I've been stuck in a blue screen with a message that says: "An error has occurred while updating the device software. Use the Emergency recovery function in the Smart Switch PC software."
So I downloaded both Smart Switch and Kies 3.0 and both have unable to detect my device, and Odin as well.
Can anyone tell me how to proceed from here? I cannot even turn off my phone, with either holding the power button. Holding volume down, home, and power button resets the screen into the same error above

I tried 4 different cables on different USB ports on my laptop, the phone is still not getting recognized. The phone is still stuck on the same blue error screen.
Device manager looks like this:
imgur.com/XhsQf3B

update:
upon reinstalling Samsung USB drivers and rebooting the laptop, it's now recognized in the device manager and Odin, but not Smart Switch or Kies.

Try flashing the stock firmware from Samsung several times, you may get lucky and return to stock. If you do and need your phone in order to make/receive calls/messages, leave it stock, root is not safe for this phone anymore.
Pp.

I managed to flash it back to stock firmware, however it has triggered the knox count by 1. It's working fine now.
So is it not possible to root this phone at this point?

sssiriusly said:
I managed to flash it back to stock firmware, however it has triggered the knox count by 1. It's working fine now.
So is it not possible to root this phone at this point?
Click to expand...
Click to collapse
This root method works just fine --> Here
Except I use the newest Unikernel --> Here

Start up failed motorola z2 play

Hi Team, I was using a custom rom aex based on pie for a while now. Suddenly my phone rebooted and stuck on screen:
Start up Failed:
Your device didn't start up successfully. Use the software repair assistant on computer to repair your device. Connect your device to your computer to get the software repair assistant.
I can't reboot into twrp, not able to flash stock rom using adb fastboot (fasboot commands working fine, but after restart coming to same screen).
Used rsd lite on win10 but, my device not getting detected. Tried LMSA - fails at 68% on flashing. Not able to do anything for the past 2 days.
Please help. Really appreciated.

Do you have your unlocked bootloader?
As long as you have your bootloader unlocked, it is possible to unbrick the phone.
If you don't, then your phone is irreversibly toasted.