I give in - MDA III, XDA III, PDA2k, 9090 General

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.

Related

Phone is freezing while starting

Hello,
I've just installed HardSPL succesfully, after that I wanted to install MightyRom 4.6, so I did. That went succesfully too according to my computer. Now when i want to switch the phone on, it keeps hanging with the T-Mobile picture on it. I've done a hard reset for several times and also a few soft resets. I also took my battery out for a few minutes, but when I switch it on, the same thing happens.
Please help me out of this !
Ps. sorry for my bad english !
for taking a little stress from your brain take an other rom - orig. rom from your provider.....
(go bootloder from pda; if your orig. rom only one *.exe-file you have to extract (winzip/winrar) it before flashing; connect usb (bootloader screen change from serial to usb); than flash)
but before you do this, how long you have to wait and look to your screen?
it can be sometimes a very long time until a windows-screen is coming.
if your pda gets hot than dont wait and flash asap new rom.
after 5 minutes waiting without any changes you have to flash an other rom.
I think I may have the same problem with my Diamond. I also installed MightyRom 4.6. Now, when I power up my phone, I get through the RGB stage to a white backdrop with instructions in blue to push volume button up for a reboot to manufacturers settings or push volume button down to reboot to manufacturers settings and wipe the movinand....after I select either one, when it gets to the HTC logo (HTC Diamond in white on a black background), it freezes. My pc won't recognise my phone when I plug it in...
Do I now have a really gorgeous paperweight or can I hold my Diamond to my ear again? Insight into my problem would be much appreciated.
By the way, XDA Dev rocks. Thanks to all who made this site possible.
Brick or no brick ?
Oh, I forgot to mention that my phone was a non-branded HTC running a Duttys rom. I did not want to get a DOPOD Diamond from China Mobile as they cost more and I dunno if they put Big Brother software in there.
HateMan01 said:
I think I may have the same problem with my Diamond. I also installed MightyRom 4.6. Now, when I power up my phone, I get through the RGB stage and then when it gets to the HTC logo, it freezes. My pc won't recognise my phone when I plug it in...
Do I now have a really gorgeous paperweight or can I hold my Diamond to my ear again? Insight into my problem would be much appreciated.
By the way, XDA Dev rocks. Thanks to all who made this site possible.
Click to expand...
Click to collapse
hi try and do like okokur has posted
cobbs said:
hi try and do like okokur has posted
Click to expand...
Click to collapse
My pc won't recognise my phone when I plug it in...
HateMan01 said:
My pc won't recognise my phone when I plug it in...
Click to expand...
Click to collapse
do you have it in the boot loader before you plug it in to your pc?
Brickety brick, brick, brick...
My phone does not recognize my pc and vice versa. I tried plugging the phone in before booting it up. I tried while booting up. I tried at the white screen stage...nothing...help...
It also doesn't stay at the RGB screen for long...maybe 2 seconds...
Please break it to me gently if I have killed my HTC...I don't want to start drinking again...
...
My phone is a GSM Diamond. MightyRom 4.6 is for CDMA. If I combine the two(like I did) then am I screwed?
Can someone please give me some insight, please? I have been scouring the net for 3 days non stop now and my eyes are going to explode...
What is Jtag and can your average home user use it? Is it hardware or software...?
Cobbs: I assume when you say bootloader you mean something other than the RGB screen,,,cos as I stated in my first post, my phone does not stop on the RGB screen...

*UPDATE* Help - Phone won't boot after attempting Sim Unlock

Hi Guys,
I am aware of how to upgrade a ROM, how to Use HardSPL and how modifying in general works, although I think I may have really broken the phone now.
I had OliNex 1.40 installed since forever. I have used several Roms in the past including EnergyROM, Ahen's Roms and I have currently been using Makeveral's BSB6.5O Rom, and it was working great.
The last time I tried to use the unlock, i tried to flash it with the 'Subrata' unlock package (the one with Step 1,2 and 3' folders. It didnt work both times I tried so I gave up. It said it was unable to write to the phone. I reflashed with BSB Rom and all was well.
Today, I found a seperate unlocker. It was a simple .exe file that opened up what appeared to be the 'CustomRUU' application. The screen initially went black and then the program said that it lost connectivity. I did read that it used Cmonex HardSPL but I did it anyway (I take responsability for this error) and from then on, the phone will not boot. No matter what combination of Hard reset button combinations I use, nothing happens. No vibration, no light around the centre button that I can see, nothing.
So is there anything, anything at all that I can do? Or have i totally F**ked it?
I have also done alot of searching both on here, PPCgeaks, all the forums.
Let me know, cheers guys.
I had a similar problem: Screen was black, no reaction from the phone. But i was able to connect it to my computer, it was not really detected, even though
i was able to flash a new Rom with a Custom RUU. Perhaps you could try that?
Try to change the rom . Pull out the stylus , Press the reset button and hold the VOLUME DOWN and the right down button . After connect to pc
The phone is in an Off state - I recharged the battery in it overnight - no white glowing ring around the centre button. No combination of buttons work - nothing happens and the device is off still.
OK, regardless of what has happened, Ive sent the phone to Victoria (Australia) to be repaired or replaced under warranty.
I just hope that it is so scrambled that they cant figure out that the device has been toyed with - will keep everyone updated!
btw - does anyone understand what technicians with more advanced tools would be able to determine (if anything)? Do they use special hardware to view the contents of the ROM or how does it all work?
thanks friends
Well..not exactly, but they have probably tools to examine the flash/memory/parts of the phone. interesting question
Update!
I sent the phone away to the Three mobile repair centre - the phone is back, fully repaired and Running BsB again.... just awesome.
it seem they replaced all the components of the phone except for the shell itself, I dont really know why they didnt just replace the phone? lol
EDIT: I forgot to mention that I told them the phone wouldn't boot after an overnight charge - thanks 3!
Sorry for bumping.
I have the same problem! I used the same program; 'DiamonCustomRUU.exe'
The screen became black. I can't open the bootmenu, soft- and hardreset doesn't work
It's a Dutch branded Vodafone TD.
I have to send it to Vodafone for repairing?

Help Please!!!

I have flashed my at&t tilt 2 with core cell evo v1.2 & it was working fine for awhile but now my screen is just black i can hear the phone make sounds and all but can't see the screen at all i really need help fixing this as this is the only phone i have any help or suggestions will be greatly appreciated thanks in advance.
i may be wrong but from what u have described... ur having a Sleep of Death (SOD) problem. have u tried takin out the battery or soft reseting the phone?
heres a link to a potential problem solver. Try to stay away from CHT lock and auto update apps!
sagarc88 said:
i may be wrong but from what u have described... ur having a Sleep of Death (SOD) problem. have u tried takin out the battery or soft reseting the phone?
Click to expand...
Click to collapse
yes i have done both and after the phone reboots i can hear sounds but i am still unable to see anything on the screen
Edit - I take that back, if it's still not working after a reboot
Have you tried entering the bootloader and re-flashing with the stock ROM?
If you can't see anything at all on the screen, no splash screens etc, even after soft-reset or entering the bootloader, then it sounds like you have a hardware problem (screen failure).
steviewevie said:
If you can't see anything at all on the screen, no splash screens etc, even after soft-reset or entering the bootloader, then it sounds like you have a hardware problem (screen failure).
Click to expand...
Click to collapse
i can't even tell if i can enter the bootloader screen because i can't see anything on the screen is there any way to tell if it's in the bootloader screen without being able to see the screen at all & if i do have a hardware problem (screen failure) how can i put stock spl & stock rom back on the phone to get it serviced
steviewevie said:
Edit - I take that back, if it's still not working after a reboot
Click to expand...
Click to collapse
if its still not working after a reboot then what? please help me i need a solution to fix this because if i can't even fix this how can i even send it in to get fixed i won't be able to because it has been flashed & has hardspl on it
"PLEASE HELP"
It's a tricky situation. So if you hold down Volume Down (and keep it held down) and press the reset button, then you still don't have anything come up on the screen ?
How about if you try a hard reset, does anything come up then ? You can hear the phone making sounds, so it seems like it's just the screen ?
Putting the charger in doesn't help, does it ?
You could try flashing a stock ROM from SD card and seeing what happens.
You might well have to send it back under warranty with HardSPL still on. In that case, if it was me, then if they tried to say the warranty was void just because of HardSPL I would argue very strongly against that and ask them to prove it - e.g. how can HardSPL stop your screen working ? I don't know what country you're in, but in the UK I think our consumer protection laws would have something to say about that.
steviewevie said:
It's a tricky situation. So if you hold down Volume Down (and keep it held down) and press the reset button, then you still don't have anything come up on the screen ?
How about if you try a hard reset, does anything come up then ? You can hear the phone making sounds, so it seems like it's just the screen ?
Putting the charger in doesn't help, does it ?
You could try flashing a stock ROM from SD card and seeing what happens.
You might well have to send it back under warranty with HardSPL still on. In that case, if it was me, then if they tried to say the warranty was void just because of HardSPL I would argue very strongly against that and ask them to prove it - e.g. how can HardSPL stop your screen working ? I don't know what country you're in, but in the UK I think our consumer protection laws would have something to say about that.
Click to expand...
Click to collapse
how can i flash anything if i can't see the screen?
Doo Doo said:
how can i flash anything if i can't see the scrren?
Click to expand...
Click to collapse
I've never flashed via SD, so I could be wrong on this. But I thought it was still possible. I see that the instructions (in the sticky on flashing ROMs) say to put it into the bootloader and "follow the on-screen instructions". I wonder if it's possible to just wait for a while and then press the appropriate key ? Though I don't know what the "appropriate key" is.
Perhaps someone who has flashed via SD can comment further, e.g. as to whether it's possible to do this without seeing the screen ?
steviewevie said:
I've never flashed via SD, so I could be wrong on this. But I thought it was still possible. I see that the instructions (in the sticky on flashing ROMs) say to put it into the bootloader and "follow the on-screen instructions". I wonder if it's possible to just wait for a while and then press the appropriate key ? Though I don't know what the "appropriate key" is.
Perhaps someone who has flashed via SD can comment further, e.g. as to whether it's possible to do this without seeing the screen ?
Click to expand...
Click to collapse
man i really need to fix this maybe you can ask around for me since i'm new here & really don't know anybody on this board
I know it's frustrating, I'd be kinda worried if I had an apparently-non-working screen too. But please be patient, and wait for more people to see your posting. The folks in the US will be coming online around this sort of time, so there will be more people looking in and hopefully someone can help further.
Flash without seeing the screen
Enter boot loader even if you can not see the screen. You can flash your phone to stock then enter boot loader again and hard spl. I had a similar situation and was able to complete the process and warranty repair with AT&T no problems, or you can pay to have it fixed at an outside shop. I was quoted 150 and refused to spend that muck so I flashed the phone without seeing the screen...
I saw your post over on Sergio's thread but decided to answer you here.
You do have a blown screen, no doubt there. How that happened is not really relevant.
My best advise is to connect your phone to your PC and wait for the activesync connection to come up. Once that happens you know you have a good connection and can flash. Run the RUU (or exe) for your stock ROM, the on screen (PC Screen) prompts will let you know if it can't proceed. Once the stock ROM is back on it, follow the same procedure and put the stock SPL back. Then send it off to get the screen replaced.
Hope that helps
Russ
Russ741 said:
I saw your post over on Sergio's thread but decided to answer you here.
You do have a blown screen, no doubt there. How that happened is not really relevant.
My best advise is to connect your phone to your PC and wait for the activesync connection to come up. Once that happens you know you have a good connection and can flash. Run the RUU (or exe) for your stock ROM, the on screen (PC Screen) prompts will let you know if it can't proceed. Once the stock ROM is back on it, follow the same procedure and put the stock SPL back. Then send it off to get the screen replaced.
Hope that helps
Russ
Click to expand...
Click to collapse
well when i plug my phone to the computer activesync is not popping up what can i do to get activesync to recognize my phone
can somebody please help me i need to reflash my phone but i am unable to see anything on my screen when i plug it up to my computer activesync is not working so what can i do please i really need help with this
Flashing witout screen
Step 1
Enter boot loader mode (* Remove the back cover from the phone.
* Hold the Volume Down button.
* Use the stylus to press the reset hole.
* Or if the device was powered off, press the power button whilst holding down the Volume Down button.)
and attach to computer. (wait 30 to 60 seconds)
Step 2
Check device manager for HTC mobile sync under mobile devices.(Active sync will not work in boot loader mode)
Step 3
Flash using Rhodium CustomRUU on your PC. (use original ROM from At&T.
Step 4 repeat for Radio
Step 5 Use Stock_SPL_Restore_087.zip from http://forum.xda-developers.com/showthread.php?t=550131 repeat the process with it.
This should work it did for me. Let me know if you run into problems.

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!

Categories

Resources