Develop Bugs

I give in

I have searched the internet high and low - found many threads in many forums about the O2 XDA IIs being stuck on boot screen and wont hard reset and NO, I mean NOT a single solution posted anywhere despite the numbers of people with exactly the same problem as me.
It will enter boot loader mode and will flash with WM5 or 6 but neither have working camera or sound.
I have flashed it with Ship versions of O2 and even T-Mobile roms but both freeze at the boot screen and wont do anything else, pressing the usual buttons to get it to hard reset don't work.
So unless anyone can help me either restore the factory rom and solve the frozen boot screen or fix the sound / camera I am going to smash it to little pieces and throw it in the bin.

arcnet said:
So unless anyone can help me either restore the factory rom and solve the frozen boot screen or fix the sound / camera I am going to smash it to little pieces and throw it in the bin.
Click to expand...
Click to collapse
Don't do that, tell me the cost and post it to me. I can use the spare parts.
Seriously, what have you tried so far? (I missed the earlier posts).
Are you getting stuck at the four colour boot screen, or at the WM splash screen?

Thanks for the reply Jdc - lol - for a second I thought you were serious about the parts.
I have tried sooo much with this thing I cant remember what I haven't tried now. But to recap when I first got the Xda IIs it was locked to O2 and stuck on the boot screen with the O2 logo and the red writing in bottom left corner showing rom version. Nothing seems to shift from this state, no reset hard or soft makes any difference - take out the battery and when put back in and powered up sticks at the boot screen.
However - I can get it into bootloader mode and merrily flash WM5 or 6 which appear to work perfectly but there is no sound whatsoever and the camera says it fails to initialize the hardware please reset.
I then reflashed it with an O2 stock Ship rom - presumably WM2003 and it is exactly as it was at the start - stuck on the boot screen showing the O2 logo and rom versions.
I even tried a T-Mobile ship rom of the same version and it stuck on the T mobile boot screen.
Arrrgh!!!! I am at my wits end with it - maybe it is faulty somehow and this is not a software fault - I wish there was some diagnostic I could run on it and find out.
I currently have WM6.11 running well but as I said with no sound or camera.
Hope you can suggest something I may have overlooked or done wrong - I am new to this and it is very possible I have missed something.

arcnet said:
Thanks for the reply Jdc - lol - for a second I thought you were serious about the parts.
Click to expand...
Click to collapse
Well, I am, kind of. I have an XDA IIs as well that needs some replacement parts, so if you are going to smash the thing, I'll pay the post to send it my way.
Anyway...
arcnet said:
I have tried sooo much with this thing I cant remember what I haven't tried now. But to recap when I first got the Xda IIs it was locked to O2 and stuck on the boot screen with the O2 logo and the red writing in bottom left corner showing rom version. Nothing seems to shift from this state, no reset hard or soft makes any difference - take out the battery and when put back in and powered up sticks at the boot screen.
Click to expand...
Click to collapse
Hrm...
When it is stuck the boot screen, what does the R, G and D lines show? I'm wondering if the radio ROM might be buggered up. However, you do say that it's working... mostly...
arcnet said:
However - I can get it into bootloader mode and merrily flash WM5 or 6 which appear to work perfectly but there is no sound whatsoever and the camera says it fails to initialize the hardware please reset.
Click to expand...
Click to collapse
No sound... As in playing a sound file with WMP doesn't even produce anything?
Can you use it as a phone normally?
Have you opened it up to see if the camera and speaker(s) are loose?
One other thing to try, if you don't mind doing another hard reset:
1. Download mtty v1.42
2. Stop ActiveSync, by Task Manager (press Ctrl + Alt + Delete) kill two processes rapimgr.exe and wcescomm.exe
3. put your device into Bootloader Mode by pressing Power + Record Button and Soft Reset.
4. Run mtty (from downloaded) Choose WCEUSBSH001 (If you only see COM 1 and COM 2, try unplugging the USB and replugging it)
5. type "set 14 0" without the quotes to tell bootloader to boot the OS after reset.
6. type "task 28" to get your device formatted
7. type "task 0" to ask your device reboot
8. take the device out of the cradle, and manually reset it if it does not do that already.

The wierdest thing happened.
Have to say that none of the suggestions or ideas (though welcome) helped. I reflashed the WM6.1 after flashing latest radio rom. Still no sound and camera.
Last night I had kept the battery out for a few hours and then on replacing it had to do reset - hey presto after all this time the sound worked and so does the camera.???? I have absolutely no idea what I did to fix it - almost as if it needed resetting a few times - cant think what else I have done.
Anyway I am happy bunny now - it all seems to be working perfectly.

Excellent! Glad that it's working for you now, hopefully it stays working as well.
If it doesn't, don't bin it, PM me and we can talk.

Lol - sorry Jdc but i wont be parting with it now - it all works perfectly even the phone is superb now which just goes to show that even when it looks like a hardware fault it is often software - a typical PC in other words.
Cheers

arcnet said:
Lol - sorry Jdc but i wont be parting with it now
Click to expand...
Click to collapse
Well bugger. No worries, glad it's working for you.
arcnet said:
it all works perfectly even the phone is superb now which just goes to show that even when it looks like a hardware fault it is often software - a typical PC in other words.
Cheers
Click to expand...
Click to collapse
Well, a typical windows machine. My UNIX and Mac's rarely go and burble to themselves like my windows machines do at times.

[Q] Galaxy Nexus black screen of death

Basically, this: http://forum.xda-developers.com/showthread.php?t=1384415
No one responded to that thread because it was in the wrong forum.
I got the "Phone -- ! -- PC" screen, and was attempting to fix it before getting this black screen of death.
Galaxy Nexus GSM
Rooted, Codename ROM, don't think there is a Kernel in there
Carrier: Virgin Mobile
Edit: I won't be able to respond for a couple hours as I'm going to work. Any and all help is much appreciated.
Original post from above thread below:
Hello guys,
I have recently bought my first android phone, the Samsung Galaxy Nexus.
On the second day I decided to root it since I needed market enabler, as my local market (UAE) has literally no apps.
I rooted using the SDK tools, fastboot and superboot. Everything worked fine for 1 day.
However, the next day, the phone just died on me, and would not boot at all. It kept getting stuck on the "Google" image at startup. At that point, I could still go into the bootloader. I tried locking/unlocking the bootloader again, since that basically wipes all the date on the phone, but it still refused to load, it would get stuck at the startup animation.
After a few more attempts, it kept spam restarting every time I tried to switch it on.
At that point, I was downloading the default OEM ROM so I could reflash that onto the phone. However, I thought I could try using the superboot bat file again, and maybe that would fix the problem. BIG MISTAKE.
As soon as I ran that file, the phone COMPLETELY died. It will not start at ALL, it will not go into Bootloader, not go into Recovery mode, and not even go into Download (odin) mode.
The ONLY possible response you can get from it, is when you plug it into the PC. My PC seems to play that "detection" sound, same sound as when you plug in a USB, but it would just play that sound over and over again, as if im plugging/unplugging a device really quickly. It seems like the phone is continously restarting itself. When I connect the phone to the PC and that disconnect/reconnect sound comes up, I went into my device manager and I could see the following:
An item under "Other Devices" called "OMAP4440" keeps appearing and dissapearing all the time, with the little "!" mark next to it indicating that there is a driver error. The drivers for this phone are fully installed on this same PC, and it use to work fine before it went dead.
Now the problem is since I cant get into any mode whatsoever, its a bit hard to diagnose the phone. I know there is a "recovery" slot at the bottom of the phone that is accessible with a small pin, but I dont for the life of me know how that works or what it does. Does anybody know how to work that or what it actually does?
Any help would be appreciated! Thanks fellas.
Click to expand...
Click to collapse

What i with my little (almost nothing experience in android) would do its going to another computer with no drivers installed, would download the toolkit and install those drivers, then plug the phone and see what happen, im sure its not bricked since the computer recognice it.. I did lot of stuff with blackberry and there was a lot of ways to recover a phone like that... From here if the toolkit recognice it in any way.. Then you could try to do some of those steps.. As far as i tried doing all kind of stuff to my phone, toolkit its for much the Best Tool and way to do anything to your phone or at least for starters like me
Sent from my Galaxy Nexus using xda premium

But the computer doesn't actually recognize it. The "detection" sound it makes is for an unresponsive device. It won't charge, won't be recognized, and no matter what combo I use, it doesn't turn it.
I played dumb, called Samsung, and now I'm going to send it in. Thanks for the help though.

sometimes my screen goes blank and I have to pull the battery and everything comes back to normal

Stock T-mobile G2 suddenly stuck in bootloop. No update. Want to backu

So, 2 nights ago I was just sending a message to someone when my phone rebooted. I wasn't downloading an update to my knowlege. Now it won't boot mostly. I can't get into download mode either. If I wait about an hour then hold the power button it will start and get to my home screen. It will stay on for about a minute then shut off and give me a LG splash screen or the t-mobile screen. When attempting to enter download mode I get the 8 red flashes. If I just leave it plugged into my laptop I'll get the charging screen. If I then power up, after some time my computer will recognize it's com port and modem but not as a hdd. There are files I absolutely need for work and school and they haven't been backed up. What does the craftiest android user do in this situation? I can get to the factory wipe screen. But, I really can't just wipe this phone yet. Help me PLEASE! I've watched hours of videos and read so much over at xda and haven't found anything that quite suits my situation other than a factory wipe. There's gotta be another way.
I can't get into the boot loader. Volume up and power only starts the boot loop again. Can't do download mode. I have gotten it to boot a few times but only for a second before restarting and giving me the LG screen
I've tried both the LG pc Suite and the Lg mobile support tool and tried the "restore upgrade errors" approach. Keeps getting to the end and telling me that the phone isn't charged. It's 100% charged. I have the ability to make videos but I wont have time until Sunday.
Can't get into fastboot. Fast boot for PC starts opens and shuts instantly. I also have the Minimal ADB and fast boot but it says it doesn't recognize a device.
I read another post where a nexus user had a similar issue and was able to root with CWM, though I believe he must have been able to get into the download mode.
This is stock. I've rooted my old galaxy S2 but kept this one stock. I've only skimmed the surface as far as the knowledge and ability many of you have and I'm hoping you have some kind of method of fixing this or at least eliminating the things I could try.
Very sorry for such a long post. It's late and I'm loopy. Thanks in advance for your help.

Pretty please!

You are in the wrong section my friend. This is T-mobile HTC G2 (aka HTC desire Z) section.
Thanks...

Oh, that makes a lot of sense! oops. Thanks.
arunal_123 said:
You are in the wrong section my friend. This is T-mobile HTC G2 (aka HTC desire Z) section.
Thanks...
Click to expand...
Click to collapse

Think ive killed it :/ Tab S2 T813

ok so bottom line is, I was in the middle of flashing official rom when at about 25% it failed. Don't ask why! (i still had recovery at this point) so I went ahead and cleaned absolutely everything thinking i'll just try and reflash as before. Now with power lead out it won't switch on at all and when power is supplied it shows message "An error has occured while udating the device software." loops at approx 3 sec intervals cant do anything with it.
Ive tried everything I can think of all to no avail! yes its my own fault bla bla bla just wondering if i act have f***** it.
Thanks to anyone with any ideas

You probably going to get a better help at TAB S2 board this is for the tab S1.
If it is hard bricked there is JTAG methods that can help, just need to find one for your device, not easy though.
But all I can do is share my experience with something like this, in a more "cheap" way than JTAGs, dunno if it helps:
I never had a similar problem on the tab S. But in the past a galaxy player 5.0 of mine had a very similar problem (as far I remember the screen just powered the back light but without any letters or simbols)
in 2012, I bricked it trying to mount a swap partition (280mb RAM ftw) accidentally pointing the wrong partition, and got the entire internal storage corrupted.. everything.. system, bootloader, recovery etc
My player was turning on only connected to a USB or charger, like yours. in fact It was hard bricked
I was able to recover it using Linux (because it is the only system able to communicate with the bricked device I had)
The problem is that everything need to be very specific, for example I used a software made for the galaxy s1 to "revive" my player 5 (both have the same hardware) it just made the device be detected via ADB. So I needed to prepare a SD with the same size as the internal storage (in this case 8gb) using the Linux terminal to mount in the SD an exactly schematic of the internal memory using a dump of another device that a xda user shared, (the dump was empty only with the bootloader, recovery etc) but it still had 8gb decompressed. So after that I used ADB to push the SD card content to the internal memory. And it get back to life \○/
Well.. it took me 1 week with a guide!! On the trial and error method. But it worked.. not perfectly, I get bootloops every time I try to flash a rom via Odin, but recovery works, and I have the device working until today

Hi, I Greatly appreciate your reply and advice. Think tho that your solution is a bit beyond my know how I know a little about ADB etc but i would have difficulties in compiling necessary files to sideload. Also many tanks for the link din't realise. Thanks Pal!

Alpha1BA said:
ok so bottom line is, I was in the middle of flashing official rom when at about 25% it failed. Don't ask why! (i still had recovery at this point) so I went ahead and cleaned absolutely everything thinking i'll just try and reflash as before. Now with power lead out it won't switch on at all and when power is supplied it shows message "An error has occured while udating the device software." loops at approx 3 sec intervals cant do anything with it.
Ive tried everything I can think of all to no avail! yes its my own fault bla bla bla just wondering if i act have f***** it.
Thanks to anyone with any ideas
Click to expand...
Click to collapse
If you can get it in to download mode you can flash stock rom back on it.......refer to xda samsung tab s2 for more details on this........

thx for reply but it reboots approx every 3 seconds so I dont have enough time to do anything with it :/

Alpha1BA said:
thx for reply but it reboots approx every 3 seconds so I dont have enough time to do anything with it :/
Click to expand...
Click to collapse
Plug in changer and push power and volume up and down all together and you will see the battery charger icon then you can get it in to download mode from there.....

stinka318 said:
Plug in changer and push power and volume up and down all together and you will see the battery charger icon then you can get it in to download mode from there.....
Click to expand...
Click to collapse
Stinka ure a superstar (atm!) I did as you suggest to no avail but I noticed a slight increase in the time it took to start rebooting again. I do not know which buttons did this but some 20 later it lasted long enough for me to be able to flash twrp. Now i havent actually tried that as yet as i wanted to check with you first... I have the battery logo on screen, i tried recovery and it started as it should but then rebooted, now im unsure at this time whether the battery is almost dead or not so i got it on charge and have the grey battery with a white flash inside... is this what i want for now until its charged? if so i'll keep you informed thamnks more than u know if uve helped me fix this, the reason i was flashing was because when i received it (no warranty!!) the screen sometimes flickered and it would constaly end up rebboting after digging around re that im lead to believe it need a new battery and for the connecting wires to be resoldered. Anyways thanks again n as I say i'll keep this updated
Cheers
Tony

one of the probs i hab/have with this unit is that it takes approx a day to fully charge!!! when i received it the screen flickered on the odd occasion but it was rebooting much more frequently. It came with stock n not messed with previously (i new this prior to purchase so got it for right price thinking it only needed flashing, how wrong was I!!!) so I flashed and encountered the above mentioned problems! thanks to stinka I surprisingly managed to flash a recovery... now provided all goes to plan, which rom would one suggest for stability and generally hassle free and prusuming the aforementioned probs, rebooting etc are still there what could i try to stop that? other than a debloated stock I found Lineage an excellent rom but still the problems got so bad the unit became unusable and was lucky not to go out the window. Im thinking do i start with a replacement battery and check the wires etc or could this still be a software issue??

if i endevoured to do the hardware myself would I attempt it by removing screen or the base for access to battery/connector??
Thanks again

In the tab s1 the best way is removing the back cover, but for some reason tab s2 seen to be the screen... at least in this guide: https://www.ifixit.com/Guide/Samsung+Galaxy+Tab+S2+Battery+Replacement/56616
Look like alot more complex than the s1 :/

RoIlingThunder said:
In the tab s1 the best way is removing the back cover, but for some reason tab s2 seen to be the screen... at least in this guide: https://www.ifixit.com/Guide/Samsung+Galaxy+Tab+S2+Battery+Replacement/56616
Look like alot more complex than the s1 :/
Click to expand...
Click to collapse
Thanks for that!!!
Tony
does look somewhat OTT!!!

will i have to odin stock first then flash rom i want or will it go straight from first flash via twrp considering there is absolutely nothing on phone at mo apart from twrp.

Alpha1BA said:
if i endevoured to do the hardware myself would I attempt it by removing screen or the base for access to battery/connector??
Thanks again
Click to expand...
Click to collapse
My guess is your issue is lack of charge in the device. That's the reason for the flashing failure and the reboot loop with the firmware error.
Bang it on charge for a while then irrespective of what it's doing, whether it's looping or not, hold POWER + HOME + VOL DOWN until download mode appears.
Reflash the stock firmware with odin.

swapped battery and reflashed stock via odin. It has helped although the issues are all still there its just they happen less frequently which doesnt mean its any less frustrating.

Question A52s random “Can’t load Android system.” when rebooting

Hi all,
I am encountering this strange bug randomly: sometimes the device Is rebooting itself and it goes automatically in recovery mode, sometimes after a reboot it does the same. The error is always: Can’t load Android system. clicking on “try again” solves the issue (sometimes at the first retry, sometimes after some retries).
I’m attaching the error screens, also because the error message is not every time the same (Attaching also a normal way to enter recovery).
Has someone encounter this bug?
Any hints on how to solve this? I haven’t already do a full reset of the phone, but i think it wilL be the next step I’ll do if the phone is continuing like this.
Thanks!

Hi Arobase40, thanks for your answer.
Yes i know that this things could happen if you do some strange things to the phone (and in my past i was used to that ) but in this case, all is pure and untouched, no unathourized apk and no modding at all. (My use is quite noob-ish now eheh)
And that's seems very strange! :/ I made only ota update and this happened both with android 11 and 12.

Arobase40 said:
This mostly happens when you did some tricky things on your phone. lol
If full reset is not enough (specially when the system is missing....) you'd have to restock it with an official Samsung firmware... ^^
Click to expand...
Click to collapse
Hi Arobase40, thanks for your answer.
Yes i know that this things could happen if you do some strange things to the phone (and in my past i was used to that ) but in this case, all is pure and untouched, no unathourized apk and no modding at all. (My use is quite noob-ish now eheh)
And that's seems very strange! :/ I made only ota update and this happened both with android 11 and 12.

Arobase40 said:
Well ok, in your case try to flash back a stock firmware from Samsung with Frija or Samfw (don't forget to supply the correct model and CSC) using PC Odin.
If that don't fix the problem then get in touch with your local Samsung website and you should find a phone number for the after sale service and they will give you the nearest Samsung official repair center from your home.
They should fix this issue very quickly using most probably the same tool which is PC Odin.
If you go to the repair center don't forget to backup all your apps and data, remove your scard if you have one and also your sim card...
Click to expand...
Click to collapse
Thanks for your help and explanations.
Just to be updated and make some laugh: today the phone while was charging has become completely unresponsive, showing "Samsung Galaxy" on a black screen when touching Power Button or connecting to Power. After a while (hard pressing Power Button and Power+vol up) it restart itself and works again. Never had such an experience with a phone (a COMPLETELY stock phone)

IvanCattaneo95 said:
Thanks for your help and explanations.
Just to be updated and make some laugh: today the phone while was charging has become completely unresponsive, showing "Samsung Galaxy" on a black screen when touching Power Button or connecting to Power. After a while (hard pressing Power Button and Power+vol up) it restart itself and works again. Never had such an experience with a phone (a COMPLETELY stock phone)
Click to expand...
Click to collapse
Idk, seems like a hardware issue to me. Try and have a go at where you've bought it and have them check it over.

My first thought too is hardware.
A few years ago I had something similar with a different phone (Moto G) - as a last ditch effort I popped out the SIM and SD cards and reseated them and it worked perfectly after that. If you have an SD card you might even want to leave it out a few days just to see.
Not saying this is your issue but couldn't hurt to try!