Related
I'm new here!
I had upgraded my Atom Rom to Atom Exec Rom (Chinese Rom 0721) weeks before.
Firstly, it ran faster, stable and seemed nothing wrong.
However, when detached the battery and then reinstalled, the nightmare appeared -- screen flicked, system unstable.
Then I tried to downgrade the rom, but error found even it was in Boot loader Mode. Someone suggested to copy "Eboot.nb0" into SD card and restart the device in Boot loader. It should then allow to downgrade any Rom.
However my story is ...
I copied, not only, but ALL files extracted from Rom (0426) into SD card and then restarted in Boot loader. The device loaded something and then reboot automatically. From that time, I no longer enter the Boot loader mode.
Every time I press CAMERA + RESET, my Atom just RESET and REBOOT. CAMERA button worked when in WM5. I don't know why.
I guess the Boot Loader Mode has been deleted or corrupted.
Can somebody help?
Thx.
Try this .. link.
http://forum.xda-developers.com/showthread.php?t=314896
jeffkewin said:
Try this .. link.
http://forum.xda-developers.com/showthread.php?t=314896
Click to expand...
Click to collapse
Thanks Jeffkewin. I will try leaving my Atom without the battery for a long period.
hi guys, I have a mogul for sprint but it is stuck at the bootloader. The message I see is: TITA100,SPL-2.07.0000,CPLD-9 and it says serial at the bottom. I have updated the rom via sd card and it completed succesfully but when I reboot I am back at the same screen. When I plug it into a computer it says the usb device as malfunctioned. I have tried the exitloader but with no usb connectivity its not working. So I have no connectivity that way. Can anyone help?? Thanks
by the way
By the way I should tell you It started after I was in windows and it froze up. I soft reset the device and have been in this screen ever since.
you did not update your bootloader correctly, as your are still in 2.07. that is the temporary BL in which no2chem's program uses to flash the 2.47 bootloader. if youre stuck, use exit bootloader, and run the thing again. make sure you go through the whole process.
Confused
I don't understand how I can do this. I cant access the device with usb so I cannot run exit bootloader on the computer and I cannot install nuespl update because I cant usb connect to the device and cannot get into the windows os on the device.
I don't understand how I can do this. I cant access the device with usb so I cannot run exit bootloader on the computer and I cannot install nuespl update because I cant usb connect to the device and cannot get into the windows os on the device.
Click to expand...
Click to collapse
You didn't update your bootloader before you flashed, that's what's causing your problems.
While in the bootloader, if you plug it in via USB, it should change to USB at the bottom. Flash the Official 3.56 Sprint Rom to be able to boot into Windows Mobile again. Then connect to Activesync and update your bootloader first BEFORE you flash any custom roms/radios.
hmm
ok i tried that but the ruu program gives me error 260 cannot connect to usb. Which doesn't surprise me becuase the second I plug the usb cable it windows says the device is not recognized. What am i missing?
Into windows
Ok I got into windows mobile by plugging the phone into the power outlet and soft reseting the phone. Then I can unplug it and Its fine and in windows but if i reset it without it being plugged into the wall its stuck at the boot loader again. Any ideas whats going on with this thing
missinglink2 said:
Ok I got into windows mobile by plugging the phone into the power outlet and soft reseting the phone. Then I can unplug it and Its fine and in windows but if i reset it without it being plugged into the wall its stuck at the boot loader again. Any ideas whats going on with this thing
Click to expand...
Click to collapse
I would start from scratch again like GC said. Get into Activesync... and do the Bootloader flash... then reflash the Radio/Rom.
advise
missinglink2 said:
hi guys, I have a mogul for sprint but it is stuck at the bootloader. The message I see is: TITA100,SPL-2.07.0000,CPLD-9 and it says serial at the bottom. I have updated the rom via sd card and it completed succesfully but when I reboot I am back at the same screen. When I plug it into a computer it says the usb device as malfunctioned. I have tried the exitloader but with no usb connectivity its not working. So I have no connectivity that way. Can anyone help?? Thanks
Click to expand...
Click to collapse
hit the 2 buttons with the dot on them,at the same time press the rest button at the bottom were the usb plugs in.make sure you have the right activesync for your OS.xp uses 4.5 and vista uses mobile center.also make sure when your flashing your ppc that you disable the stand by power mode,uncheck all option that would put your ppc in standby will your flashing it.
Stuck in tri-colour screen
I GOT MI HTC TITAN STUCK IN BOOTLOADER MODE FOR BOUT A MONTH NOW AND NOTING SEEM TO BE WORKIN
ON THE SCREEN I SEE A MESSAGE DAT SAY
TITA100
SPL-1.07.0000
CPLD-9
NEED U HELP PLZ AND THANKS IN ADVANCE
buzzinstudios said:
I GOT MI HTC TITAN STUCK IN BOOTLOADER MODE FOR BOUT A MONTH NOW AND NOTING SEEM TO BE WORKIN
ON THE SCREEN I SEE A MESSAGE DAT SAY
TITA100
SPL-1.07.0000
CPLD-9
NEED U HELP PLZ AND THANKS IN ADVANCE
Click to expand...
Click to collapse
Please stop typing in all caps.
Then describe what you did that resulted in this. Did you try to flash a custom ROM? If so, it probably failed because you didn't update your bootloader.
i'm having the same problem... tri-color bars:
TITA100
SPL-2.07.0000
CPLD-9
Serial (USB when i plug in the usb cable)
PC would not recognize the device so i can not run the exit boot loader that seems to solve the problem for a lot of ppl here.
The scenario with my device: i was not trying to update anything. the phone dropped onto the floor and the battery came loose. when i put the battery back in, it was stuck in the bootloader.
any help would be greatly appreciated.
eskargo said:
i'm having the same problem... tri-color bars:
TITA100
SPL-2.07.0000
CPLD-9
Serial (USB when i plug in the usb cable)
PC would not recognize the device so i can not run the exit boot loader that seems to solve the problem for a lot of ppl here.
The scenario with my device: i was not trying to update anything. the phone dropped onto the floor and the battery came loose. when i put the battery back in, it was stuck in the bootloader.
any help would be greatly appreciated.
Click to expand...
Click to collapse
I just had a similar problem though my phone didn't even drop, it went into bootloader while I was listening to a podcast via bluetooth. You could try to re flash via sd card(see the wiki), but if you're unable to connect with the pc, your phone is likely bricked. I tried the sd route and though I was able to get the update to complete, it always went back to the bootloader. The phone was swapped out (my 4th!) yesterday, unfortunately they had Moguls so no TP for me! Good luck!
i did get the mogul to reflash via the sd card but it would return to the bootload screen. so i left the battery out. i tried the next morning and the phone proceeded to boot up. it recognized that there is a new image and started to run thru the setup and installed all the files. when the setup completed, guess what, it required a reset. and back came the bootload screen. seems that, 99.9% of the time, after a reset (soft or hard), my phone would return to the bootload screen.
after countless tries, i finally managed to boot up my phone with my personal info restored. but if i need to reset or battery drains and a restart is needed, the bootload screen would return. and the only course of action is to remove the battery and keeping trying until the phone boots up properly.
obviously, i can not live with a phone this way... so i will be sending the brick back to UT starcom for a replacement.
in the mean time, i guess i will get one of those pay as you go sim card for a spare nokia i have laying around the house.
thank you for all the info and tips here... i think i know more about the mogul than some of the sprint employees at my local sprint store.
If your PC is not recognizing the phone when its in bootloader is probably because you don't have the correct drivers installed for your phone. Might wanna google the drivers and install it and then try going through the advice from the other members.
Meaning put into bootloader manually then install correct unlocker (Olipro 2.40 or Nue 2.47)-->run stock ROM (to install radio)-->install custom ROM
I'm not sure if this helps but I just ran in to a similar issue of getting stuck in the boot loader. What I did was use to flash back to the earliest stock from Verizon (for me it was 2.09 and radio 1.30) but I was still stuck in the bootloader screen. I then used titan_exitbl.exe (found here at XDA) and exit the boatloader. Afterwards I did the rom flash one more time and it worked. I was back in to a stock rom. The issue I'm having now is that if I try to upgrade to the next stock rom the process fails at 11% again, and since I never had this issue before with this rom (3.57) prior to oilpro 1.20, I suspect that is the problem. I have to uninstall oilpro 1.20, then try the 3.57 stock rom again or install nuespl 2.47 or something. You guys have any clue how to uninstall oilpro 1.2? Will titan_relocker do it for me?
Here is my thread, and thanks for all the guys who helped me on this one.
http://forum.xda-developers.com/showthread.php?p=3402819#post3402819
UPDATE:
Use this link if you are on Verizon to get the MR2 rom update back up and running on your phone.
http://www.pcdphones.com/phone_downloads.aspx?bid=89&cid=1&mid=287&carrier=Verizon Wireless
The whole
TITA100
SPL-2.07.0000
CPLD-9
keeps happening w/ my Sprint HTC Mogul a little more often now (it's about 1.5 years old). But it just goes away after a while, I really don't do anything.
On Monday I was shutting my Mogul down after fully charging the battery by holding the power button until the reboot prompt came up on the screen, I pressed yes and it shut down like it always has. I removed the battery and swapped to my other battery to charge it and when I tried to boot it up by pressing the power button again I just got the bootloader screen. I tried everything, with power plugged in an not, tried either battery, nothing, just stuck on the bootloader, I even tried the factory reset as a last resort thinking I wouldn't lose much, I sync pretty frequently. Even the factory reset holding the 2 soft keys while pressing the reset button it went blank then back to bootloader again. I am running everything stock from Sprint, no modifications or other software (WM 6.1 from HTC). I scoured the web and found on a ppcgeeks thread that someone had tried plugging the Y-adapter cable with the 2.5mm headset and mini-usb connectors on it and I happened to have it sitting around and plugged it in and pressed the reset button with the stylus again and it booted right up just fine. It also seems to boot fine with any of the other adapters I have (nothing needs to be connected to the adapters, just the adapter needs to be inserted into the phone in order for it to boot properly). I took it to Sprint and they had the techs look at it and had never heard of it before. They offered to reflash the rom but said that there is an equal chance that it could either fix it or brick it and they wanted me to sign a waiver that would release them of any liability if it bricked. I told them I can flash the rom myself with activesync at home, if they're not going to take any liability I'd be just as well off doing it myself.
I also found that sometimes when placing a call I can't hear anything, and when I have my Seidio 3.5mm audio adapter plugged in the audio will not pass through the adapter unless the phone is rebooted with the adapter plugged in all the time, as soon as I unplug the adapter it goes to the phone speaker for audio (music from windows media player) and it will not return the sound to the adapter when it is plugged back in until it's rebooted again.
Any ideas?
buzzinstudios said:
I GOT MI HTC TITAN STUCK IN BOOTLOADER MODE FOR BOUT A MONTH NOW AND NOTING SEEM TO BE WORKIN
ON THE SCREEN I SEE A MESSAGE DAT SAY
TITA100
SPL-1.07.0000
CPLD-9
NEED U HELP PLZ AND THANKS IN ADVANCE
Click to expand...
Click to collapse
same thing happened to me sept it says
TITA100
SPL-1.06.0000
CPLD-9
cant fix it
wmobilefrik said:
same thing happened to me sept it says
TITA100
SPL-1.06.0000
CPLD-9
cant fix it
Click to expand...
Click to collapse
There are some solutions 1 page behind http://forum.xda-developers.com/showpost.php?p=2516968&postcount=5.
I attempted to use SSK 2.6 R4R Gen.Y Edition Default Kitchen from
HTML:
http://www.sskusers.net/
on my phone earlier. It seemed like everything was going fine, until I was taken to the startup screen. It was frozen, and there was red writing at the bottom of the screen.
Because the phone is stuck on that screen, when I try to connect to ActiveSync, it doesn't recognize any USB devices.
I did try removing the battery. The phone turns off, obviously, but when I turn it back on, I'm back at the frozen startup screen again.
I have also tried doing a soft reset, and the hard reset. When I do a hard reset, it takes me to the bootloader screen, and lets me do everything, but when it reboots, I just end up in the same place I was before - with a frozen startup screen.
Any suggestions on what to do, and/or what could have caused it?
Just wanted to add:
I have Verizon, and did do the hard spl using Raphael_VZW_HSPL_035, which I got from
HTML:
www.ppcgeeks.com
Reflash a different ROM through usb from the bootloader.
dwizzy130
i would suggest flashing a new rom or maybe going back to stock first & then trying a new rom. i would say the most important part right now would be flashing from the bootloader. put the nbh file on the sd card using a media reader & then pop it back in the phone & flash it. thats the easiest way & wouldn't take but 10 minutes to accomplish. i wouldn't be too worried you should be fine. feel free to get at me privately if you need some help.
Help
If you installed Hspl then just hold volume down and power and press the soft reset key. it will reboot into the bootloader and will recognize via usb. Hope this helps. I had a endless loop when i tried flashing to energyrom and this got me back to mightyrom. u may want to try it http://www.mightyrom.com
I had installed Chucky rom(ChuckyROM-23136-Tabtastic.Sept.12.7z) on my htc hd2,i had also installed hspl( HSPL2_RUN.exe) around two months(in september 2010) back but i did not like it so today(25th november 2010) first i removed hspl through HSPL3_PKG.exe and put spl 2.08.0000( I DID NOT USE AN SD CARD TO FLASH THE SPL) and then flashed
Artemis_v430_0409_WWE.7z i.e RUU_Signed_0409.nbh through SSPL_RUU.exe and then it worked and was working properly but was hanging again and again so i soft reseted it two-three times and then i was installing a cab file but as soon as the installation started, it said "installation of so and so file.cab was unsuccesfull" then i tried dinik hybridia icon .cab again same thing happened so i soft reseted it and while soft reseting a complete black screen appeared and said "a program from an unrecognised software party was tried to install please press the upper volume button to reset the phone Note. you will lose all your data and the phone will completely reset itself or else press any other button to start normally" i pressed any button so it started loading normally but it has got stuck at that loading and is not doing anything after that ,
it is not connecting to the pc,the backlight of the keys is also not switching on , i have takin the video of it switching on and also of bootloader ,
what has happened to it and why is it not starting,please help?
also even after i flashed artemis gen 4 it is showing the chucky rom boot screen!
In the videos it gets stuck to where i have stopped the video and remains like that for hours(THE Video IS IN THE RAR FILE)
also i have warranty left so can i get it repaired by warranty???
PLEASE HELP ASAP
try a hard reset. turn the phone off, hold down both volume buttons, and turn the phone on, keeping the vol buttons held down. then when prompted,press vol up to reset it.
yes, you'll lose any data and modifications on your phone, it will be back to how it was right after you flashed it, but at least it will start up. better than how it is now, right?
nishankyadav said:
I had installed Chucky rom(ChuckyROM-23136-Tabtastic.Sept.12.7z) on my htc hd2,i had also installed hspl( HSPL2_RUN.exe) around two months(in september 2010) back but i did not like it so today(25th november 2010) first i removed hspl through HSPL3_PKG.exe and put spl 2.08.0000( I DID NOT USE AN SD CARD TO FLASH THE SPL) and then flashed
Artemis_v430_0409_WWE.7z i.e RUU_Signed_0409.nbh through SSPL_RUU.exe and then it worked and was working properly but was hanging again and again so i soft reseted it two-three times and then i was installing a cab file but as soon as the installation started, it said "installation of so and so file.cab was unsuccesfull" then i tried dinik hybridia icon .cab again same thing happened so i soft reseted it and while soft reseting a complete black screen appeared and said "a program from an unrecognised software party was tried to install please press the upper volume button to reset the phone Note. you will lose all your data and the phone will completely reset itself or else press any other button to start normally" i pressed any button so it started loading normally but it has got stuck at that loading and is not doing anything after that ,
it is not connecting to the pc,the backlight of the keys is also not switching on , i have takin the video of it switching on and also of bootloader ,
what has happened to it and why is it not starting,please help?
also even after i flashed artemis gen 4 it is showing the chucky rom boot screen!
In the videos it gets stuck to where i have stopped the video and remains like that for hours(THE Video IS IN THE RAR FILE)
also i have warranty left so can i get it repaired by warranty???
PLEASE HELP ASAP
Click to expand...
Click to collapse
What an utterly unfortunate situation!! Couple of questions/remarks:
1. Did you install HTC 3.14 ROM with your S/N from HTC's website before flashing Artemis?
2. You already removed HSPL, so I would advice to extract the 3.14 RUU file to your desktop and copy the custom.nbh file to your SD Card after having it renamed to leoimg.nbh (insert SD CArd into PC to do that).
3. Reinsert SD card in device and enter bootlader mode and the installation of 3.14 should start automatically.
4. After that download Artemis 43 and extract it to the folder where you're SSPL_RUU,exe resides. Bothe the custom.nbh and the SSPL file must be in the same folder!
6. Start SSPL_RUU and flash Artemis
7. After that first a hard reset and then a soft reset.
Also read page 1 - Flashing notes
This should to it for you,
regards, Kuzibri
P.S. I posted this also in Artemis thread
same problem
i've got the same problem, but i didn't install the rom artemis,
i restart the installation many time but i've got always the same problem
the display showing loading..... please wait with the chucky logo.
someone can help me???????
thank you
Hey XDA Dev,
I own a Z3TC (SPG612) for a while now. Maybe rooted with the kingroot (don't remember the exact name), didn't unlocked the bootloader, installed TWRP, flashed (well, the current and broken one) to 23.4.A.3.6 (5.1.1 ?) and all was fine for months.
And today, because I saw a stupid supersu notification, I say OK, let's update supersu binary (done that several times without issue).
Well, it ended in a bootloop where I could still use TWRP.
Because I found a thread which say "flash kernel fixed the issue", and because I also read that "recovery is totally separated from main Android and also for Kernel" and also probably because I forgot the weird Xperia recovery install (on the system ? Something like that ...) .. I decided to flash a kernel from a previous backup (after flash, I will remember to always backup .. so 1 before and 1 after ..) with version 23.1.A.0.690.
Definitely, it was the worst idea of the day. Now, I still have bootloop, but I lost the recovery access (no more vibration during bootloop).
For now, I take a break ... The device don't wont to stop with power button and I had to use power-vol+ to "force reset" which bring the tab down. I can still start it and continue the infinite bootloop if required.
I tested USB connection to my Linux (without anything set for not) and I'm not able to get the green light : vol- + connect = red light, green light then off (about 1s).
If I try with vol+, I'm able to get the blue light (not of the death I hope).
So of course, any help would be appreciated.
I am reading this for now : https://forum.xda-developers.com/showthread.php?t=1849170
I also read an article (in french) 2 days ago saying supersu had lots of problems and for Xperia, still not fixed. Well, I go through this (and I get caught).
Am I alone ?
What's your advise ?
Thanks
Good news, device is accessible via fastboot
Bad news, the device has normally a locked bootloader ...
Good news, I already backed-up the TA keys (several times with differents updates but I suppose they didn't change).
EDIT: Is that possible to flash only the kernel using fastboot ?
Because I could make it works back to the previous bootloop state, which is still better with TWRP.
EDIT2 : I analysed all my possibilities before going ahead. First, the FlashTool seemed to work in fastboot but not flash mode (because the green led was not staying green, only for 1s and both off). So, I thought only fastbootmode was working.
I tried to flash the fotakernel of the device but failed, probably because the BL was not yet unlock.
So, in order to avoid unlocking the BL, I tried with PC companion. I used the repair function, this also updated to Android 6 (was in 5, rooted, with recovery installed too).
It says to boot in flashmode (well, greenlight). I did and the led was off, as expected. I thought it was not working but at the and, I got a successful repair
started back the device ... it works
So, problem fixed, upgraded to MM, I've just lost the root and the recovery TWRP.
Here are some steps about what's happened :
---
In 2016-03, installed version SGP612_23.4.A.3.6_R3C_Japan Generic_1290-3027_PRFCreator-1.2_SuperSU-2.65_DualRecovery-2.8.26.zip on my z3tc.
On 2017-06-02, an update of supersu break the boot and goes to bootloop.
Trying to fix it by flashing an old kernel from the previous backup (I found easy to try with a backup of TWRP, flash only the kernel .. of a previous backup of a previous firmware version). Since then, lost access to TWRP and device wont power off : have to hard-reset and it sleep then.
Remaining access :
- flashmode (=ADB : green led) : not working, the device wake up after a short time and reboot in a loop, disconnecting the flashmode (saw it through FlashTool) => unstable and unusable
- fastboot (blue led) : working and stable, but could need to unlock the bootloader to permit flash.
Fortunately, there is several backup of the TA and I should be able to re-lock the firmware and restore TA files.
Tried to fix using PC companion (so, avoid to unlock the bootloader ... even if I have TWRP TA backup : better to avoid it ...).
It finishes with OK : now running on 23.5.A1.291-R3D
And this fixed the Z3TC
---
Please note that using the PC Companion for the fix in flashmode (vol down and connect) didn't trigger any restart of the device during the repair process.
At the end, I am surprised that it had worked that way.
But it's OK, the devices seems to works, have to reconfigure it now.