Database Info

Strange screen turning up when fiddling..

I was installing my invisibleSHIELD last night with my phone turned off, and apparently managed to do something while trying to fiddle it on as the screen turned on with some small amount of data, and it was colored like some color test screen, red blue green and white horizontal areas(or something like that).
So what did I manage to do? Was it dangerous in anyway for the phone? Probably not, but I'd like to know how I did it and what's its purpose =)

This is called the bootloader screen (popularly known as the Tri-colour screen), you got to this screen by starting up the phone with the Volume Down button held.
Not dangerous at all, unless you had a RAPHIMG.nbh file on the root directory of your fat32 formatted storage card
[along with a wrapper] (Having that file in the root and starting up to the bootloader would allow one to initiated a flash)
This mode is used to flash a new rom, radio or spl to the device, either run to it automatically by a Wrapper from your computer or forced by the user. From this screen one can even flash any of those items from a storage card instead of from the computer. (I do this from time to time when I dont have access to a computer with active sync and wish to flash a rom.
Of course, one needs hard spl to flash anything custom.

no bootloader - phone still working

hi,
I'm on WM6.5 by Gregory which works fine - only issue is that I have no bootloader. The update worked nicely and it almost feels like I have a brandnew phone. But then I saw NitroGenious' signature with links for updated IPL and SPL and thought - well higher numbers must be better. Issue is that during one of the installs of a ?PL not sure if it was the I or the S - I was panicking slightly the installation program stopped and windows (xp) said an error had occurred and the program needed to be terminated. Instead of a bootloader I have a blank screen - removing the battery and switching on the phone gives a working phone again.
So I'm left with a perfectly working phone but cannot access the bootloader anymore. I have no immediate need for it as I have a working phone but I would feel better if I had a 'complete' phone again. You would have thought I had learned my lesson but would consider an attempt to get a bootloader back on.
silly99

Try to access bootloader this way:
Press and hold 2 buttons - Camera and CommManager, further press Power button and release it (release only Power button, keep first 2 buttons held). It should load into bootloader mode, at last. A must.

hi,
Thanks for the suggestion - both ways of accessing bootloader give the same result: Cam + CommMan and power or Cam and usb cable. Blank screen. Removing battery and putting it back in restart the phone.

I had faced same problem. In my case it was after formating BINFS, it was only whitescreen and nothing else. After some sweating I found the culprit, it was the minisd card slot, I remove, reinsert, some movement of the card.. then ok the bootloader comes back..with great relieve. Now my phone is back with new 6.5 ROM.

thacen said:
I found the culprit, it was the minisd card slot, I remove, reinsert, some movement of the card.. then ok the bootloader comes back..
Click to expand...
Click to collapse
Thanks for the tip - similar issue here - I have a 4 GB micro sd in a mini-sd adaptor. I simply removed it and tried to go to bootloader mode and then it worked fine. So it could be a thought to put that as a warning in the guides.

cannot get past 0% flash progress - TP2 CDMA Sprint

This is certainly a new one for me.
Phone information:
Touch Pro 2 (Sprint)
Battery about 90% charged
Unlocked SPL-1.00 OliNex
Process:
Generally, when I flash I do it one of two ways. I either put the IMG file on SD card and flash that way, or I go into bootloader and flash via USB having manually put the phone into bootloader. I don't sync the phone with my desktop PC so I don't have activesync or WMDC installed.
In a little over two years with this phone, I've never had an issue.
Detail Scenario One - microUSB:
Unplug from USB and/or AC (result is the same with our without AC adapter)
Pull battery
Insert mSD card (I've full FAT32, not quick formatted three different cards) with RHODIMG.NBH.
Insert battery
Trigger bootloader (volume down + power)
Bootloader (tri color screen - SPL-1.00 OliNex) comes up
Immediately transitions to an all grey screen that reads
Loading ...
And then nothing else happens.
Detail Scenario Two - PC/USB:
unplug from AC / usb
Pull battery
remove microSD card
insert battery
Trigger bootloader (volume down + power)
Bootloader (tri color screen - SPL-1.00 OliNex) comes up
White part at bottom reads Serial
Plug into PC USB cable
White part at bottom changes to USB
Run "RUU_Rhodium_W_S2_Sprint_WWE_2.04.651.4_RS_2.32.00WF" ROM installer - using something from HTC/Sprint to avoid issues with bad NBH or RomUpdateUtility
Next
Next
Update
Next
Next
PC screen updates to "Updating the ROM image on your PDA Phone" at 0%
Touch Pro 2 screen toggles to grey screen with 0% update progress
Nothing else happens ... some time later, the desktop PC updater flips out of update mode and walks through the flash recovery steps
the Touch Pro 2 screen stays at 0% until I pull the battery and start over.
Thoughts ?
Best regards,
-boggsie

If you unplug and plug back in the USB while sitting at 0%, can you get anything to happen. Had this issue with my hero a few months ago. That seemed to do the trick. Seemed like the drivers were hanging up. The phone did say FU a few months later. Worth a shot anyway.

[Q] Drained battery = unable to charge properly & continuously boots [SOLVED]

In a nutsell: when I plug the charger in (wall), after a while red led starts blinking, after a longer while phone turns on all by itself and starts booting up, <CM loading animation>, homescreen shows up and pretty much immediately phone goes off. During the one second of homescreen battery status seems to be 0%. This is then repeated for as long as the phone is plugged in and between the attempts to boot up manages to recharge a miniscule amount of power.
Problem has it roots in when I dropped the phone, backcover came off and battery was displaced. After that, phone booted correctly and worked, but battery status was stuck at 51%, which I didn't notice until the phone forced a shutdown (I think this happened the safe/soft shutdown way).
phone: Sony Ericsson Xperia pro (MK16i)
rom: CM-based LegacyXperia
So, now I can do these things:
- the continuous rebooting loop while plugged in
- boot to CWM recovery
- sometimes (and if I plug it into USB port), I get the battery charing icon (standard CM one?) which is what is supposed to come instead of automatic boot up (?). Usually at first it shows two yellow bars, quickly changing to one blue bar. Red led stays on (does not blink), so everything looks ok... until after a while the phone again goes off. If left plugged in, boot loop commences soon.
The phone can barely keep itself on while in CWM recovery menu for a couple of minutes maybe. Full wipe is going to the be last resort because I don't know how I'm able to take backups with so limited uptime.
I have tried:
- wiping cache & dalvik cache, since I can get to CWM recovery.
- I've googled a lot about this and one left-field suggestion was that the power button may be stuck (that thread was about entirely different phone). I guess that would make sense because I did drop the phone.
- removing the battery and kept it removed for several minutes. Also tried the trick of plugging the phone in first and then installing the battery.

I'd say that your power button is stuck, you should try another ROM however.

I would try a different rom

wirelesscord said:
In a nutsell: when I plug the charger in (wall), after a while red led starts blinking, after a longer while phone turns on all by itself and starts booting up, <CM loading animation>, homescreen shows up and pretty much immediately phone goes off. During the one second of homescreen battery status seems to be 0%. This is then repeated for as long as the phone is plugged in and between the attempts to boot up manages to recharge a miniscule amount of power.
Problem has it roots in when I dropped the phone, backcover came off and battery was displaced. After that, phone booted correctly and worked, but battery status was stuck at 51%, which I didn't notice until the phone forced a shutdown (I think this happened the safe/soft shutdown way).
phone: Sony Ericsson Xperia pro (MK16i)
rom: CM-based LegacyXperia
So, now I can do these things:
- the continuous rebooting loop while plugged in
- boot to CWM recovery
- sometimes (and if I plug it into USB port), I get the battery loading icon which is what is supposed to come instead of automatic boot up (?). At first it shows two yellow bars, quickly changing to one blue bar. Red led stays on (does not blink), so everything looks ok... until after a while the phone again goes off. If left plugged in, boot loop commences soon.
The phone can barely keep itself on while in CWM recovery menu for a couple of minutes maybe. Full wipe is going to the be last resort because I don't know how I'm able to take backups with so limited uptime.
I have tried:
- wiping cache & dalvik cache, since I can get to CWM recovery.
- I've googled a lot about this and one left-field suggestion was that the power button may be stuck (that thread was about entirely different phone). I guess that would make sense because I did drop the phone.
- removing the battery and kept it removed for several minutes. Also tried the trick of plugging the phone in first and then installing the battery.
Click to expand...
Click to collapse
if you confirmed the power button not stuck, i would say either, the phone has some internal damage from being dropped, or the battery has been damaged.
of the 2, i would guess battery damage, but this is just my opinion.

Daniel120201 said:
I'd say that your power button is stuck, you should try another ROM however.
Click to expand...
Click to collapse
ArYaNsH said:
I would try a different rom
Click to expand...
Click to collapse
It's going to be a bit risky because like I said, even in CWM menu it has barely enough juice for a minute or two and USB port is going to give even less power :/ The rom itself is ok (CM11 + added support for these ancient models, because the official one dropped them).
bweN diorD said:
if you confirmed the power button not stuck, i would say either, the phone has some internal damage from being dropped, or the battery has been damaged.
of the 2, i would guess battery damage, but this is just my opinion.
Click to expand...
Click to collapse
The stuck button: at least the phone can be turned off by the button, also key tester in CWM recognizes it. I would also lean towards battery damage or at least some kind of a miscommunication between it and the phone which makes the phone think it is not empty when in reality it is.
About the dropping: after that it booted and worked correctly, because I specifically tested that sound, camera etc. still worked, I did not see anything weird other than the battery % being stuck and used it until the battery emptied.

I can manage to use fastboot at least. I don't know if this a related issue, but I can't seem to get it return any values for battery information.
fastboot devices shows the device, but e.g.
Code:
fastboot getvar all
all:
finished. total time: 0.001s
Output should be something like this: http://pastebin.com/4vv9g7Hg
Won't return anything for battery-status and battery-voltage either.
but these work:
Code:
fastboot getvar version
version: 0.3
finished. total time: 0.003s
fastboot getvar version-bootloader
version-bootloader: Sony Ericsson S1Boot Fastboot emulation CRH1099189_R9A029
finished. total time: 0.010s
fastboot getvar version-baseband
version-baseband: 1243-7775_4.1.B.0.587
finished. total time: 0.007s
And probably many others I didn't test. a) commands/variables not supported b) battery/something so messed up that won't return anything?
I found this script which is supposed to slowwwwly recharge the battery in fastboot mode:
http://lesterhein.com/how-to-charge-your-android-phone-battery-in-hboot/
but of course it won't return any battery-voltage value either and secondly, after it does this cycle a few times, the phone shuts off.

Problem solved for now: one of the battery connector pins was bent inside because of the drop, the middle one (googled example pic) so I never noticed it. I simply pulled it back and phone has now returned from the dead, charges properly and seems to hold the charge too.
That for sure explains everything.

[Q] Phone Keeps Rebooting After It Dropped

My girlfriend dropped her phone yesterday and despite that it's encased in a bulky Ballistics case it appears that the power button is broken now. When I plug the phone into my laptop using her USB cable the phone automatically boots up the Google screen with the lock icon, vibrates and then shuts off and reboots again resulting in a boot loop. Unfortunately she's out of warranty. She opened the phone and the iron nub of the power button appears to be unmovable. She also tried going into recovery, but the phone continues to reboot.
Is there any way we can fix this? I read that some people can get theirs repaired at a repair shop, but I'm not sure how viable that is in Canada. Please advise.

Getting the power button fixed isn't too expensive. Hopefully that's all you need. ?

whyareallusernamestaken said:
My girlfriend dropped her phone yesterday and despite that it's encased in a bulky Ballistics case it appears that the power button is broken now. When I plug the phone into my laptop using her USB cable the phone automatically boots up the Google screen with the lock icon, vibrates and then shuts off and reboots again resulting in a boot loop. Unfortunately she's out of warranty. She opened the phone and the iron nub of the power button appears to be unmovable. She also tried going into recovery, but the phone continues to reboot.
Is there any way we can fix this? I read that some people can get theirs repaired at a repair shop, but I'm not sure how viable that is in Canada. Please advise.
Click to expand...
Click to collapse
I have had this issue for the past 4 days. After many attempts of trying to bang the phone a lil onto my hand (for where the power button is located at), sometimes the phone will boot fine, for as long as you do not click the power button again it won't act up.
(I am pretty sure I didn't drop my phone when I was napping in the car, it just started out of nowhere after I have been using lollipop 5.0 with franco kernel for like 2 months without any problem).
Same sypmtoms, bootloop (looked like the power button defective / boot IC on mobo defective), can't even stay on recovery/bootloader screen/system for longer than 5 sec.
Try these :
- spam click power button, until it is able to boot into system, you will have to keep clicking, for every click you either screen on/off you will realize Power Off options may pop up, it looks like the power button has been holded for few sec to trigger the power off, but all you do was spamming the click to keep the button active, you have to click until you feel that certain point the power off doesn't pop up, then stop clicking ( remember never to touch that power button again for NOW), if after a few sec of using the phone and it doesn't force shut down (result from power button defective where it sense its being clicked and hold for like 8-15 sec). Then you are good to carry on whatever I am to tell here.
- go to about phone, click the build number for 5-10 times until you get the unlocked developer mode
- back, click on developer options, enable usb debugging mode (this will pop another message asking you if you want the device to memorise your pc's mac address) that way it is synced with your pc.
- before you proceed with any other thing, go to playstore, download power button to volume button, enable volume power, check start volume power on bootup, check screen off. This will help you greatly for not touching the power button to unlock the screen when you are working on your pc.
- if you have all the correct nexus usb driver installed onto your pc, you need to get Minimal ADB and Fastboot installed onto pc. After installing, run Minimal adb and fastboot, a command prompt windows will pop out and is automatically redirected to the minimal adb folder. key in this command
"adb devices" to see if it detects your device or not. There should be at least a device listed if you have the usb driver installed correctly
- now you can make use of adb commands to reboot into bootloader/recovery to do any flashing of system, backup all your data that you needed to PC. Download official 5.0.1 nexus 5 image and extract it into the Minimal ADB folder.
- is your bootloader unlocked? if not do adb reboot-bootloader
- fastboot oem unlock (this will wipe all your data on the phone)
- fastboot reboot after the wipe is done
After that you can actually carry on with flashing back to stock images. Look at this link http://forum.xda-developers.com/google-nexus-5/general/tutorial-how-to-flash-factory-image-t2513701 for flashing to stock factory image.
I am not sure which step has actually solved my problem, because on my first flashing of factory image, booting into system as a brand new device (no extra softwares, yet to recover any of my data). the problem persists as long as I clicked on power button once, it'll act up again random power off and bootloop.
I actually was on a follow-up cases with google play support team from Aus as my device was bought from Aus. After the last step of factory image setting, doesn't help, I intended to ship it back for RMA as my device is still under warranty and I suspected it was the hardware issues from power button too. They will send me another refurbished device. After ending the call, they sent me link to proceed with warranty claims where I need to fill in several forms and ship the device back to them.
I decided to give it one more try, due to my phone was previously unlocked, rooted, changed to franco kernel.
By restoring to stock images made my device unroot, I was afraid of google will accuse me for unlocking bootloader voided the warranty and not willing to replace another unit for me. I locked back the bootloader, then I remembered in bootloader, fastboot oem device-info shows that a record of a phone if it has been unlocked, it will show Tampered status as True, google probably can use that to track if a device has been unlocked before. So I unlocked my bootloader again (which causing another wipe for whatever data is in the device).
So I looked up on google again and found source for changing that tampered status to False in addition to locking the bootloader again, but to change that tampered status, I need to use TWRP to run the scripted zip file, so I used fastboot boot path (it is stated in the link I gave you above) to boot into TWRP images temporarily from my desktop and ran the zip file, I always practice wiping data, cache and everything before I boot the device back into a brand new factory image.
So I went to wipe dalvik cache. Rebooted the system - it was running the Optimizing x numbers of Applications.
Upon finished with that. I was surprised that, after a few clicks of power button, the random power off issues is no longer there. I even test clicking on the power button for entire day. The symptom isn't coming back. So I emailed google play support team to cancel my warranty ticket and close the case for now.
Should there be any problem again I will probably then claim the warranty for replacement.
Its been more than 24 hours now that I am using the device without any problem of random power off and on or stuck in bootloop due to power button defective.
I suspect it is either the 5.01/5.0 lollipop with ART that is causing something wrong with the boot IC / power button defective in a long run.
Or maybe it was some settings I have changed in franco kernel ? but it was running fine for 2 months which made me doubt that it is franco kernel
Or it could be some of the apps I used to tweak my phone settings - LLama and tactile player (which I have set something condition and actions for power button) but I doubt it is caused by these either.
I will observe and see if the problem comes back after some time of using the 5.0.1 stock image now.
Oh I am also back to using franco kernel, unlocked bootloader and rooted again. Haha...
Hopefully you are able to solve the problem by trying some factory reset method + wiping cache, partition and dalvik.
If not, you probably may have the hardware issues, I have seen some other forum/websites with n5 users upon replacing the mobo, no longer encounter such problem.
Regards,
Kean

Thanks for the replies. My girlfriend was able to get the power button repaired for $80 and replaced the external button for $7 + tax, she paid $98. At least it's cheaper than a new phone.