As a new O2 xda exec user, I thought I should play safe and upgrade to latest ROM etc on the O2 web site. After a couple of false starts and after checking the excellent wiki advice, I got the thing to run through and complete the upgrade.
But on doing the final hard reset, I find myself with a completely garbled screen instead of the O2 splash screen. After a couple of seconds the 3 lines of text appear on the screen (the R, G and D numbers) but against the background 'snow' I can't read them. No response to keyboard or to 'random' pressing the screen. The screen eventually turns off after a few minutes but when switched back on remains with the same garbled screen as before.
Tried going through the whole process again but sadly got the same result.
Tried going into bootloader and doing a soft reset (as advised one of the many upgrade problem threads I've checked) but that also took me to the same garbled screen.
Can anyone help me out with this? I can't find anything quite like this on the Wiki or in any recent threads.
Should I try an alternative ROM? Stupid question, but is a Jasjar ROM OK on an O2 exec?
Hi - just thought I'd save people any wasted effort. This problem is now sorted.
It seems the O2 web site had linked to an out of date ROM which I downloaded and installed in blissful ignorance. Went back to the web site and found the link is now updated and gives the correct ROM version. This loaded and started up with no problems.
In case anyone reads this - although I didn't get any direct responses from the community I would still like to say a big thanks cos the Wiki and the responses to other threads are a real help. You guys have put a lot of effort into this and created a resource which is invaluable.
Top bananas!
lol...well i guess me and u were in the same boat my dude...i def did exactly da same thing u did..jus a new user getting the update and fu**ed my ish up...thanx 4 posting this tho it was some help*goes to download new update*
I cant even sync with my pc anymore i dont know wat to do
I'm no expert - as the screw up above amply demonstrates - but the failure to sync was one of the rage inducing steps I went thru too. Sometimes the PC would recognise the xda but other times it wouldn't. In my case, it was sorted by reading in another part of the forum how to get into bootloader mode by pressing the light and on/off button at the same time as using the stylus to press the soft reset. This should take you into boot loader - an apparently dead screen but if you look closely you should see 'Serial' at the top and 'v0.xx' at the bottom.
If you reconnect by USB cable to your PC the 'Serial' should change to 'USB' and in my case I was able to run the software on my PC to update the ROM.
Sorry if I'm stating the obvious but hope this works for you. Otherwise check out the Wiki section (wiki.xda-developers.com) which has lots of good tips.
i fixed it i had jus installed a new rom
Hi there,
your first thought might be: Ah jeez another one posting the same **** 2000 people posted before ^^. But anyways i think my problem is a special case:
yesterday i wanted to flash another radio to my htc magic via clockwork recovery. However something must have gone wrong. After the recovery rebooted my phone i got stuck at the "htc magic" splash screen. Pressing the home or the back or vol-down button or home and back button at the same time doesnt change the situation. still stuck at splash screen. fastboot and recovery dont seem to work.
After some really bad panicking minutes, i pulled the batery out of the phone and let it rest, while googling and searching the **** out of every forum on the net. Some minutes later i reassembled the battery and started the htc magic without pressing any other buttons, hoping it would juts boot and say "kidding ))" on the display. but yeah ... it didnt ^^.
Now im coming to the odd part, which differs from most other posts i saw on other forums and here on xda: after quite a while my htc magic suddenly made that "bling bling" sound, as it did whenever it started android successfully. i nearly burst into tears when i heard that sound, hoping that i would be able to access the phone via fastboot or adb. but ... i wasnt able to :S. the screen went black after that "bling bling" sound and stayed that way until i pulled the battery again.
i could repeat that procedure and reproduce the sound and behaviour, but i couldnt access the phone via any possible way i could find on the web :S.
hopefully somebody, who knows more can help. my last step would be jtagging the phone. but the tools are kinda pricy for such an "old" phone. and i couldnt find anyone in my area who could borrow me the tools or repair the phone for cheap money.
thanks in advance im counting on your knowledge
Try this low cost JTAG
tested by me with 2 T-Mobile Mytouch 3G
thanks for your fast response. if jtagging really is my last chance:
- what did you pay for all the parts of the schematic ?
- how long did it take you to put everything together?
- do i need a parallel port on my computer, or is it possible to use an usb port ?
- and do you think a newbie to smoldering and stuff could be successfully assembling all those parts?
- can you provide me with links and/or other pictures, which could help me?
thanks again for your effort
kinda exciting this whole thing :>
Hello all; apologies in advance if this is retreading old ground, but I couldn't find anything about this on the forum as is.
So, while taking some video the other night, my Razr M (all recent software/OS updates, stock software + commercial apps , no flashed ROM/no root/hell, I wasn't even using GoLauncher anymore) decided to freak out on me. By the end of the night, it got itself stuck on booting, and by the next day, it's more or less bricked. Called, got my replacement phone from Verizon, but before I ship this off, figured I'd plug it into the PC and see if there was anything I could do to salvage data -- most things are backed up, but the video/things from that day obviously aren't.
So, no screen. When I plug in, I get the little green light intermittently. For fun, I tried getting to a boot screen (Vol down/Vol up/Power), and now I have this fun thing where my PC tells me it's installed "Fastboot SMQ S" drivers, and is "searching preconfigured folder drivers". Every few seconds, the phone's light will be green, a few seconds later, it will go off. Likewise, my device manager keeps trying to recognize a Human Interface Device, and now and then Windows tells me a connected device has failed. (Once every now and again it tells me it can't recognize it, for about a half second.)
I should note that at no time during any of this does the screen on the phone itself give me any sort of image or feedback.
This leads me to think there's still something inside the phone fighting to work -- as stated, I don't need it to get back to functionality per se, but if there's enough left to work with to at least pull data off of it before it clinks out, I'd be quite happy.
This seemed like a question for the XDA folks, even though it isn't mod/dev related, because you guys are usually the forum I read when I have questions, as you all seem to really know the insides of the phones and systems. If there is a better forum/place for asking this question, please just let me know. I'd be grateful for any sort of advice/insight you may have.
Thank you, and have a great afternoon!
p.s. I assume, based on other similar threads, that the whole "stealthily open the case, yank out of the flash and kitbash it into my pc while somehow not voiding the warranty" route is unfeasable/undoable. If this is not the case, I'm game for that. I'm not a phone dev, but I've seen the inside of an electronic device or ten in my time, so I might be able to pull it off.
Hi,
Not sure if it's a right place to ask, but let it be my first post here. I own an S5 device, and it's sort of crazy. Let me explain.
Three months ago my device suddenly rebooted and got almost-soft-bricked in sense of being unable to boot to the operating mode normally: its display just got black after the splash screen, however I could tap the display and watch 1 FPS "live stream" using `adb screencap` at my PC. So the device was not dead and I could take out all private not synced data I needed (it was really hard once for an application that has the backup facility disabled in its application manifest) -- blind tapping everywhere. My first attempt to fix the device was re-flashing another compatible ROM having all important data backed up. Well, I got it bricked and could not boot anymore. The recovery mode was not available (the device just frozen if trying to enter the recovery), however I could enter the download mode.
Unfortunately, no reflashing helped, so I decided to let it be fixed by a repaire service (since an official Samsung service center in my country has rejected the repair request _with payment_ because the device was not intended for sale here -- well, "thanks Samsung"). Ok, the alternative service took the device and asked almost a half of the device price for the display replace. Honestly, I forgot to ask why there was an idea to replace the display if it worked perfect while it was waiting in the Download mode. Again, it just got black after the splash screen, but the display worked fine in the Download mode until the device was powered off or reset. So after a few days they gave it back to me, and the device was really good now -- it worked fine. They also re-fllashed the device to Android 6 (previously Android 5) and the device was unrooted. Well, that's fine to me.
But after a few hours of rooting, testing and re-installing the software and migrating the data back to the device, the device rebooted again being unable to boot to the "operating mode". Now it just got stuck at the Samsung S5 splash screen or rebooted in a loop. But after a long time (it might took more than a day; the battery seems to be inserted in the device and not pulled off) the device was able to boot normally and (this might be odd) upgrade the installed apps. If I remember, this was a cyan screen with two or three animated white gears. So about 150 apps were upgraded and the normal "operating" mode activated -- so I could use the device. Now after working a few hours, the device falls into a reboot loop / splash freeze coma again for undetermined time, and then, for unknown to me reason, the device woke up.
In short:
1) The device reboots or shuts down suddenly.
2) Instant rebooting does not work for whatever reason.
3) Just wait for some undetermined time without the device battery pulled off.
4) ... It boots again.
5) The upgrading process starts after the boot.
6) Working with the device until paragraph 1: "The device reboots or shuts down suddenly".
Now I don't know if it's a hardware or a software issue: the repair service guys didn't explain much, and now I'm feeling cheated for the replacement of the display that worked perfect in the Download mode that I gave half device price just because it was an idea of theirs. Yes, I have the repair warranty paper for their service, but I just would like to know the real context.
What I could be deservedly blamed for:
* I rooted the device after their repair in a wrong way.
* When I rooted the device, I removed most Samsung bloatware I used to remove earlier. I don't tend to think that I could kill some important software, though. But, to me, it's hard to believe that a software issue might cause such an odd device behavior (I mean the booting just after a certain period of time).
So... I would really and really appreciate getting the real issue behind the symptoms or just a hint spark of light to reveal possible root causes. And was I really cheated by the repair service?
* My device: Samsung SM-G900P S5, Sprint
* Firmware before the repair: stock, Android 5.0.x (?), root, most Samsung bloatware removed
* Firmware after the repair: stock, Android 6.0.1, root, most Samsung bloatware removed (yes, the bloatware list difference is significant now)
* The battery: seems to work fine and does not get drained when the device is in coma
Thank you!
hurricane flow said:
Hi,
Not sure if it's a right place to ask, but let it be my first post here. I own an S5 device, and it's sort of crazy. Let me explain.
Three months ago my device suddenly rebooted and got almost-soft-bricked in sense of being unable to boot to the operating mode normally: its display just got black after the splash screen, however I could tap the display and watch 1 FPS "live stream" using `adb screencap` at my PC. So the device was not dead and I could take out all private not synced data I needed (it was really hard once for an application that has the backup facility disabled in its application manifest) -- blind tapping everywhere. My first attempt to fix the device was re-flashing another compatible ROM having all important data backed up. Well, I got it bricked and could not boot anymore. The recovery mode was not available (the device just frozen if trying to enter the recovery), however I could enter the download mode.
Unfortunately, no reflashing helped, so I decided to let it be fixed by a repaire service (since an official Samsung service center in my country has rejected the repair request _with payment_ because the device was not intended for sale here -- well, "thanks Samsung"). Ok, the alternative service took the device and asked almost a half of the device price for the display replace. Honestly, I forgot to ask why there was an idea to replace the display if it worked perfect while it was waiting in the Download mode. Again, it just got black after the splash screen, but the display worked fine in the Download mode until the device was powered off or reset. So after a few days they gave it back to me, and the device was really good now -- it worked fine. They also re-fllashed the device to Android 6 (previously Android 5) and the device was unrooted. Well, that's fine to me.
But after a few hours of rooting, testing and re-installing the software and migrating the data back to the device, the device rebooted again being unable to boot to the "operating mode". Now it just got stuck at the Samsung S5 splash screen or rebooted in a loop. But after a long time (it might took more than a day; the battery seems to be inserted in the device and not pulled off) the device was able to boot normally and (this might be odd) upgrade the installed apps. If I remember, this was a cyan screen with two or three animated white gears. So about 150 apps were upgraded and the normal "operating" mode activated -- so I could use the device. Now after working a few hours, the device falls into a reboot loop / splash freeze coma again for undetermined time, and then, for unknown to me reason, the device woke up.
In short:
1) The device reboots or shuts down suddenly.
2) Instant rebooting does not work for whatever reason.
3) Just wait for some undetermined time without the device battery pulled off.
4) ... It boots again.
5) The upgrading process starts after the boot.
6) Working with the device until paragraph 1: "The device reboots or shuts down suddenly".
Now I don't know if it's a hardware or a software issue: the repair service guys didn't explain much, and now I'm feeling cheated for the replacement of the display that worked perfect in the Download mode that I gave half device price just because it was an idea of theirs. Yes, I have the repair warranty paper for their service, but I just would like to know the real context.
What I could be deservedly blamed for:
* I rooted the device after their repair in a wrong way.
* When I rooted the device, I removed most Samsung bloatware I used to remove earlier. I don't tend to think that I could kill some important software, though. But, to me, it's hard to believe that a software issue might cause such an odd device behavior (I mean the booting just after a certain period of time).
So... I would really and really appreciate getting the real issue behind the symptoms or just a hint spark of light to reveal possible root causes. And was I really cheated by the repair service?
* My device: Samsung SM-G900P S5, Sprint
* Firmware before the repair: stock, Android 5.0.x (?), root, most Samsung bloatware removed
* Firmware after the repair: stock, Android 6.0.1, root, most Samsung bloatware removed (yes, the bloatware list difference is significant now)
* The battery: seems to work fine and does not get drained when the device is in coma
Thank you!
Click to expand...
Click to collapse
someone said after an OTA to 6.0.1 it borked the phone into a reboot loop too. I had mine rooted for maybe a week or 2 and now I have reboot Loops, not even twrp can fix this issue. I am trying a battery like this person said here http://forum.xda-developers.com/galaxy-s5/help/marshmallow-6-0-1-ota-update-boot-loop-t3425838,
spending 9 bux and change beats spending 250 for another Unlocked G900T
http://forum.xda-developers.com/galaxy-s5/help/marshmallow-6-0-1-ota-update-boot-loop-t3425838
eidairaman1 said:
someone said after an OTA to 6.0.1 it borked the phone into a reboot loop too. I had mine rooted for maybe a week or 2 and now I have reboot Loops, not even twrp can fix this issue. I am trying a battery like this person said here http://forum.xda-developers.com/galaxy-s5/help/marshmallow-6-0-1-ota-update-boot-loop-t3425838,
spending 9 bux and change beats spending 250 for another Unlocked G900T
http://forum.xda-developers.com/galaxy-s5/help/marshmallow-6-0-1-ota-update-boot-loop-t3425838
Click to expand...
Click to collapse
Hm, that's interesting, thank you. I also noticed that the loop happens after some time only, it's like the more you have your phone running in the normal mode, the more your phone can get into the loop again. However, I don't think it's a battery overheat issue or so (sorry, I may use silly terms not being an expert at all). So in short:
1) After some pretty long power-off time you power on the device. It's working really stable unless...
2) ... unless something happens (battery? some intricate software or hardware issue?) and the device gets rebooted.
3) Here comes the boot loop, and usually no reboot helps to get out of the reboot loop.
4) Just power off the device and let it just be alone for some time, and now you're back to the step 1 until the "unless..."
My coma device is powered off for long time (thus I think that the step 4 still works for me after that long time) and I'm going to give it to the repair service again, just comparing what the service guys say and what the forum folks say.
I will follow up on the battery swap when mine arrives.
hurricane flow said:
Hm, that's interesting, thank you. I also noticed that the loop happens after some time only, it's like the more you have your phone running in the normal mode, the more your phone can get into the loop again. However, I don't think it's a battery overheat issue or so (sorry, I may use silly terms not being an expert at all). So in short:
1) After some pretty long power-off time you power on the device. It's working really stable unless...
2) ... unless something happens (battery? some intricate software or hardware issue?) and the device gets rebooted.
3) Here comes the boot loop, and usually no reboot helps to get out of the reboot loop.
4) Just power off the device and let it just be alone for some time, and now you're back to the step 1 until the "unless..."
My coma device is powered off for long time (thus I think that the step 4 still works for me after that long time) and I'm going to give it to the repair service again, just comparing what the service guys say and what the forum folks say.
Click to expand...
Click to collapse
I received a battery yesterday, charged it up and started using it today, no reboots or bootloops so far.
The battery that came in my phone was made in china, the one I just got yesterday was made in Vietnam.
I'm wondering if Samsung really needs to stop using china to make batteries lol, Surefire flashlights state not to use batteries made in china lol.
eidairaman1 said:
I received a battery yesterday, charged it up and started using it today, no reboots or bootloops so far.
The battery that came in my phone was made in china, the one I just got yesterday was made in Vietnam.
I'm wondering if Samsung really needs to stop using china to make batteries lol, Surefire flashlights state not to use batteries made in china lol.
Click to expand...
Click to collapse
Hm, that's really interesting. It's hard to believe that replacing the old battery might affect it that much and get rid of bootloops -- I mean, I just thought that it might be a software/firmware failure (let's say I removed some system apps [actually Samsung bloatware] improperly), or something very core hardware might fail, but I have never thought of a batter as the root cause. Hard to say, sorry. But I'll take your solution into account. Thank you!
hurricane flow said:
Hm, that's really interesting. It's hard to believe that replacing the old battery might affect it that much and get rid of bootloops -- I mean, I just thought that it might be a software/firmware failure (let's say I removed some system apps [actually Samsung bloatware] improperly), or something very core hardware might fail, but I have never thought of a batter as the root cause. Hard to say, sorry. But I'll take your solution into account. Thank you!
Click to expand...
Click to collapse
I thought it was a bad rom flash as well or SuperSU causing it, well I found another article stating they replaced the battery and the issue went away. I think the phone was stating a bad POST so it would restart
Android 8 prev 3 or whatever they call it. Never unlocked the bootloader. USB debugging is on I think.
I assume it is hopeless but just in case something to try, here's where I am now:
I think I was seeing "Phone is not available" and such on startup. I went to clear cache partition having not done it before on this 6P, after clearing call cache did nothing. The odd thing was it was instantaneous, meaning I assume it was doing nothing. Did a few of those. Somewhere in there I saw "No command" which I'd never seen but a button or 2 later was at recovery screen again.
Then just the google logo laughing at me. Or if looping: a flicker, black..., flicker, black... Won't shut off either. Has anyone's magically booted after a day and been fine?
I maybe can't get to the recovery screen. I did once in this state with some button mashing but normally it just goes straight to the logo when selecting recovery mode even with mashing about. I assume that alone ensures my complete and utter defeat.
I don't know the significance but on the power-Volume Down start up screen (not sure the name of that screen?) it says "Plug in USB data cable." I think I have USB debugging on so that was my only hope but I have no PC handy to check. On ChromeOS it does nothing plugging in.
I read that even locked bootloader could use a full OTA to flash but I think only for those on an older Android version.
So... Damn. My 2nd 6P after a screen failure. I'll certainly try anyway having read threads, but should I have a year on the RMA unit or only the time that remained on my original purchase?
Btw, has anyone heard of Hauwei excepting to exchange perhaps with additional cash for a new model (Mate 9, 10 Plus)?
Has anyone heard of Hauwei accepting a phone bought in another country? Not in the US now.
Thanks.
Hunter O. Unicorns
I don't like to bump a thread but before tossing $500 in the garbage I hope one little bump is acceptable if not addictive, just in case any new news.
Does anyone have any knowledge of my particular mess that could help on the questions above? Much appreciated if so.
Thanks