Hello.
This my first thread. I have done some reading, but I can't find a similar problem, so I really hope that this is posted in the correct location...
I have an odd problem with my phone. I did a flash a few months ago, and I also (attempted to) update the modem and bootloader. After the reboot, I had to begin pulling the battery to get the phone to power back on after the power was off or after a restart. I've replaced the battery, charger, and installed SEVERAL new roms, but the problem persists. I don't know if I need to do something else, or if the phone is damaged...
But if it IS a programming problem, and not physical damage, then here's the real problem...
I have installed the latest version of CWM. I am running CM 11 with Kitkat 4.4.2. I would like to just flash the stock rom and see if that fixes it, but I have read that once you are running a 4.3 or beyond bootloader, you WILL brick your phone if you try to downgrade. So that stops that.
Another issue is that if I try to install a different/newer bootloader in CWM, it fails every time. I also cannot flash another version of CWM or TWRP. About halfway through the process, Odin says it has failed, no matter what version of Odin, CWM, or TWRP I am using.
So the short version of this is, based on what I've listed, how do I fix this rebooting issue?
I know that this is a long post, but I'm trying not to leave anything out. If anyone has any ideas, please feel free to let me know.
Thank you in advance
biga72112 said:
Hello.
This my first thread. I have done some reading, but I can't find a similar problem, so I really hope that this is posted in the correct location...
I have an odd problem with my phone. I did a flash a few months ago, and I also (attempted to) update the modem and bootloader. After the reboot, I had to begin pulling the battery to get the phone to power back on after the power was off or after a restart. I've replaced the battery, charger, and installed SEVERAL new roms, but the problem persists. I don't know if I need to do something else, or if the phone is damaged...
But if it IS a programming problem, and not physical damage, then here's the real problem...
I have installed the latest version of CWM. I am running CM 11 with Kitkat 4.4.2. I would like to just flash the stock rom and see if that fixes it, but I have read that once you are running a 4.3 or beyond bootloader, you WILL brick your phone if you try to downgrade. So that stops that.
Another issue is that if I try to install a different/newer bootloader in CWM, it fails every time. I also cannot flash another version of CWM or TWRP. About halfway through the process, Odin says it has failed, no matter what version of Odin, CWM, or TWRP I am using.
So the short version of this is, based on what I've listed, how do I fix this rebooting issue?
I know that this is a long post, but I'm trying not to leave anything out. If anyone has any ideas, please feel free to let me know.
Thank you in advance
Click to expand...
Click to collapse
Edit: --> I was able to install TWRP using Mobile Odin. Now I'm going to change the bootloader and see if that fixes the problem.
biga72112 said:
Hello.
This my first thread. I have done some reading, but I can't find a similar problem, so I really hope that this is posted in the correct location...
I have an odd problem with my phone. I did a flash a few months ago, and I also (attempted to) update the modem and bootloader. After the reboot, I had to begin pulling the battery to get the phone to power back on after the power was off or after a restart. I've replaced the battery, charger, and installed SEVERAL new roms, but the problem persists. I don't know if I need to do something else, or if the phone is damaged...
But if it IS a programming problem, and not physical damage, then here's the real problem...
I have installed the latest version of CWM. I am running CM 11 with Kitkat 4.4.2. I would like to just flash the stock rom and see if that fixes it, but I have read that once you are running a 4.3 or beyond bootloader, you WILL brick your phone if you try to downgrade. So that stops that.
Another issue is that if I try to install a different/newer bootloader in CWM, it fails every time. I also cannot flash another version of CWM or TWRP. About halfway through the process, Odin says it has failed, no matter what version of Odin, CWM, or TWRP I am using.
So the short version of this is, based on what I've listed, how do I fix this rebooting issue?
I know that this is a long post, but I'm trying not to leave anything out. If anyone has any ideas, please feel free to let me know.
Thank you in advance
Click to expand...
Click to collapse
If the phone powers on itself immediately the battery is replaced, i.e. without you having to press the power button, chances are 99% you have a stuck power button problem. It's not uncommon with this device and can be routinely fixed at any repair shop or by DIY if you have the right tools and technical resources.
If the phone is working OK (other than the booting issue), I'd stay off flashing bootloaders to avoid bricking
Larry2999 said:
If the phone is working OK (other than the booting issue), I'd stay off flashing bootloaders to avoid bricking
Click to expand...
Click to collapse
Thank you very much for the reply!
No its not a power button issue. I DO have to hold the power button to power on. Here's what happens when the restart fails...
I have to:
1) pull the battery
2) sometimes, I have to hold the power button WITHOUT the battery in for a few seconds (I've had laptops that have this issue before. I think it's a static buildup of some sort.)
3) reinsert the battery
4) hold the power button, and
5) if I'm lucky, the phone will boot up.
This is only about 50% successful. Sometimes I have to do this 3-4 times.
Now, I don't know if this is a hardware issue, or a firmware/software issue. If it IS a hardware problem, then I may just replace the phone. If it's a firmware/software problem, then hopefully it can be fixed. If it's a problem with the bootloader, and a fix isn't possible, then I'll just keep on truckin' till I get a new phone.
biga72112 said:
Thank you very much for the reply!
No its not a power button issue. I DO have to hold the power button to power on. Here's what happens when the restart fails...
I have to:
1) pull the battery
2) sometimes, I have to hold the power button WITHOUT the battery in for a few seconds (I've had laptops that have this issue before. I think it's a static buildup of some sort.)
3) reinsert the battery
4) hold the power button, and
5) if I'm lucky, the phone will boot up.
This is only about 50% successful. Sometimes I have to do this 3-4 times.
Now, I don't know if this is a hardware issue, or a firmware/software issue. If it IS a hardware problem, then I may just replace the phone. If it's a firmware/software problem, then hopefully it can be fixed. If it's a problem with the bootloader, and a fix isn't possible, then I'll just keep on truckin' till I get a new phone.
Click to expand...
Click to collapse
It's almost certainly an hardware issue. Very unlikely a firmware problem would cause this and even more likely the bootloader would. With a bootloader issue, your phone likely wouldn't even boot at all. Power button problems present in several ways and a loose power button could cause the kind of issues you've described. I'd take it to a local tech shop for a quick look before giving up on it.
Larry2999 said:
It's almost certainly an hardware issue. Very unlikely a firmware problem would cause this and even more likely the bootloader would. With a bootloader issue, your phone likely wouldn't even boot at all. Power button problems present in several ways and a loose power button could cause the kind of issues you've described. I'd take it to a local tech shop for a quick look before giving up on it.
Click to expand...
Click to collapse
I may just wait and get me a new phone in a few months. I'm expecting a bonus from work, and I'll likely just get the new S5. Thanks for the information
Related
Is anyone manage to brick the phone already?
How likely/ or stupidity you need to actually bricking the phone?
What is a NO NO and how to avoid it?
That's the question.. thanks!
Main thing is read as much as you can before you do any changes, it helps to check what few sites say.
When I rooted my phone I could not get it to run the update part, tried time and time again, one site said "rename the file to update.zip and paste it" then I read on another site to just call it update as it is already a zip file.....and then it worked, small bit of detail like that stopped it working to start with so if I was you I check a few sites and get all the info you need, but also as many would say if you are that unsure dont take the risk and wait for samsung updates with Kies.
voodoochild2008 said:
if you are that unsure dont take the risk and wait for samsung updates with Kies.
Click to expand...
Click to collapse
Kies actually failed to update my phone, I have the Korean Galaxy S SHW-M100S, and it showed an update was available. So, I thought I was bricked for about 30 mins, kept trying to get it to work itself out of the problem in recovery mode, after about 4 tries (1 reboot of Windows, plus changing USB ports and 2nd try with this static new config) eventually it did, thank God.
Do not remove usb while in the middle of flashing with odin
Wanna know HOT TO BRICK YOUR PHONE? Right when ODIN start flashing, pull the battery on your phone and see what happens.
I can't even boot up!
****
amerikian said:
Wanna know HOT TO BRICK YOUR PHONE? Right when ODIN start flashing, pull the battery on your phone and see what happens.
I can't even boot up!
****
Click to expand...
Click to collapse
I was gonna say something along the lines of a smart ass, but I can't. That sucks.
why would you do a battery pull?
madjsp said:
I was gonna say something along the lines of a smart ass, but I can't. That sucks.
why would you do a battery pull?
Click to expand...
Click to collapse
I've been flashing all night and wanted to do it "right" this time....realized my SIM and SD card were still in there mid-flash so wanted to pull them and start clean..........................
Yeah....don't do that.
Guess I'll be that "guy" paying a visit to the local AT&T shop tomorrow....
Luckily I'm w/in my 14 days since getting it....
delete. ......
amerikian said:
Wanna know HOT TO BRICK YOUR PHONE? Right when ODIN start flashing, pull the battery on your phone and see what happens.
I can't even boot up!
****
Click to expand...
Click to collapse
I've removed the cable half way and rebooted, and it was fine..
You simply remove the USB cable, battery again, put the battery in, and you'll be able to get to downloader mode.
The phone seems to have a component that ODIN doesn't touch that is read-only that handles download mode. Most hardware devices tend to have safeguards. I haven't confirmed this, but I've noticed the same applies to NAS devices (which tend to have a special redboot which uses tftp).
I have still yet to have seen any evidence of anyone permanently bricking their phone, but I've seen a few cases of "oops, got it working again".
Remember, Samsung are eager to reduce their support costs, and failsafe's are cheap and easy to add.
yes, the odin doesn't touch the 'bootloader' , or the small piece of code that enable the download mode, so there's no way you can brick the phone.
I have tried to repartition the phone while flashing firmware that has nothing except the csc data (i.e. no kernel, no factory rfs, etc) and the flash procedure went succesfully but in actual fact, my phone contains a new set of partitions that contain nothing except the small csc data.
and i still able to reflash, although I must make sure that the phone is totally shutdown (i.e. take out battery, let it stay for awhile before putting back)
andrewluecke said:
I've removed the cable half way and rebooted, and it was fine..
You simply remove the USB cable, battery again, put the battery in, and you'll be able to get to downloader mode.
The phone seems to have a component that ODIN doesn't touch that is read-only that handles download mode. Most hardware devices tend to have safeguards. I haven't confirmed this, but I've noticed the same applies to NAS devices (which tend to have a special redboot which uses tftp).
I have still yet to have seen any evidence of anyone permanently bricking their phone, but I've seen a few cases of "oops, got it working again".
Remember, Samsung are eager to reduce their support costs, and failsafe's are cheap and easy to add.
Click to expand...
Click to collapse
I thought in the Big FAQ, it said... do not disconnect the usb-cable but to remove the battery if want to interrupt it...
7.The phone will be flashed and once it’s finished, it will boot up. (Do NOT disconnect the usb-cable, remove the battery or otherwise interrupt this process!)
amerikian said:
Wanna know HOT TO BRICK YOUR PHONE? Right when ODIN start flashing, pull the battery on your phone and see what happens.
I can't even boot up!
****
Click to expand...
Click to collapse
Similar happened to me,although I didnt pull the battery, the phone just disconnected halfway through the flash.
Had half hour of panic,where I thought it was bricked.
Had to do a few battery pulls,restart PC a couple of times and mess around with different USB ports,but finally got it working.
Have flashed a 3 times since without a problem.
chluk2425 said:
I thought in the Big FAQ, it said... do not disconnect the usb-cable but to remove the battery if want to interrupt it...
7.The phone will be flashed and once it’s finished, it will boot up. (Do NOT disconnect the usb-cable, remove the battery or otherwise interrupt this process!)
Click to expand...
Click to collapse
That means you shouldn't do any of those things! So don't disconnect usb, don't remove the battery and don't interrupt the process.
zenkinz said:
yes, the odin doesn't touch the 'bootloader' , or the small piece of code that enable the download mode, so there's no way you can brick the phone.
I have tried to repartition the phone while flashing firmware that has nothing except the csc data (i.e. no kernel, no factory rfs, etc) and the flash procedure went succesfully but in actual fact, my phone contains a new set of partitions that contain nothing except the small csc data.
and i still able to reflash, although I must make sure that the phone is totally shutdown (i.e. take out battery, let it stay for awhile before putting back)
Click to expand...
Click to collapse
Are you sure that flashing (through ODIN) in any case never touch that "Download Mode" piece of code ? Even you select all the options in ODIN ?
Can anyone confirm this ? Actually I want to play with Kernel and RFS (have some ideas to try) but afraid of full bricking. So if this download mode is always present then I can play with it without any problem.
Waiting for response.
amerikian said:
I've been flashing all night and wanted to do it "right" this time....realized my SIM and SD card were still in there mid-flash so wanted to pull them and start clean..........................
Yeah....don't do that.
Guess I'll be that "guy" paying a visit to the local AT&T shop tomorrow....
Luckily I'm w/in my 14 days since getting it....
Click to expand...
Click to collapse
Believe me! you can still access the download menu
The bootloader is almost always writeprotected and cannot be overwritten. You would probably have to connect a cable to some internal port like Jtag to be able to reflash the bootloader section. Atleast that is the case in 99% of all bootloaders. Im very certain that you cannot cripple the bootloader.
Sent from my GT-I9000 using XDA App
jackiechan8 said:
That means you shouldn't do any of those things! So don't disconnect usb, don't remove the battery and don't interrupt the process.
Click to expand...
Click to collapse
gosh man, thanks correcting me but if that's the case, what should i do if it doesn't reboot by itself?
take out the battery, wait for 30 to 60 secs, put the battery in and start phone with vol down + menu + power
Don't disconnect the usb or do anything else while flashing!!!
I removed the usb cable when it started flashing (i thinked it was stuck, happens sometimes), and since it does not boot anymore. I press the power button, volUp + home + power, volDown + home + power... nothing happens.... it's dead, doesn't turn on at all...
after all i have read i think it's almost impossible to brick the sgs since you always get back into download-mode. the only case i read where i believe that it's a goner is flashing with the wrong (in this case the at&t) odin version. those guy's just got a white sreen with at&t logo at boot. they didn't get into download mode any more because the button mapping on the captivate is different ... so thats really bad luck, dont't try that at home
jodue said:
after all i have read i think it's almost impossible to brick the sgs since you always get back into download-mode. the only case i read where i believe that it's a goner is flashing with the wrong (in this case the at&t) odin version. those guy's just got a white sreen with at&t logo at boot. they didn't get into download mode any more because the button mapping on the captivate is different ... so thats really bad luck, dont't try that at home
Click to expand...
Click to collapse
well, mine doesn't boot at all, and i flashed (technically not, because i removed the usb cable at the very start) with the RIGHT odin version
Maybe if it fails when flashig sbl (secondary boot loader ) you can't go into download/recovery mode...
Hey i hope all is good.
I really need your help. I have a TILT 2 cell phone and by mistake a friend activated the bootloader. Previously the ROM has been updated. the phone got stuck in that screen and the only way to turn it off is removing the battery. so, i try to reboot the phone and it only loads the bootloader with a flash message saying "no image file". ok, i though, the ROM was damaged and after reading a lot in the forums, i followed the instruction to put a new ROM. I connected the phone the the computer and the message in the phone changed to USB and my PC installed the HTC USB Sync driver (but Active Sync does not detect the phone); anyways, i ran the task 29 and a new rom. I was able to see the progress bar in both (PC and Phone) but then the phone reboots and loads again the bootloader. I tried to use the HARD SPL 1.00 as well but it does the same thing after finishing the flash it loads again the bootloader.
can some help me pls?? i'm new in this and the phone is a work tool for me i really need your help.
rgds
You should do the HSPL before flashing a ROM (unless it was already done).
I would try to flash the newest HSPL, then a ROM.
Hi, and thank you for you reply.
I already did it and apparently it flashed the HSPL . Now in the bootloader says SPL 0.85 OliMex; then i flashed the ROM and it showed me the progress bar in both system (PC and phone) but when it finish it booted back to the bootloader. I just noticed that sometimes (after been off for a while) if i turn it on it boots to the rom but it happens randomly and if I turn it back off i just got the bootloader again.
I really need your help pls
jsolanon said:
Hi, and thank you for you reply.
I already did it and apparently it flashed the HSPL . Now in the bootloader says SPL 0.85 OliMex; then i flashed the ROM and it showed me the progress bar in both system (PC and phone) but when it finish it booted back to the bootloader. I just noticed that sometimes (after been off for a while) if i turn it on it boots to the rom but it happens randomly and if I turn it back off i just got the bootloader again.
I really need your help pls
Click to expand...
Click to collapse
Hrm, have you tried doing a task29? Re-flash the ROM after task29.
yes already tried the task 29 and then flash the rom but the same issue...i've been reading a lot of post regarding issue with the bootloader and follow the instruction but nothing seems to work. I even tried the update from the AT&T site but the same issue...i have no idea what else to do
jsolanon said:
yes already tried the task 29 and then flash the rom but the same issue...i've been reading a lot of post regarding issue with the bootloader and follow the instruction but nothing seems to work. I even tried the update from the AT&T site but the same issue...i have no idea what else to do
Click to expand...
Click to collapse
So you've flashed the stock ROM? Have you tried relocking? Probably won't do much, but worth a shot I guess.
When you flash back to stock you flash the stock ROM, then relock, then reflash stock.
Yes, but the issue persisted.
I have noticed something. If i leave the cell phone turn off for a while (hours) and then i turn it on. Most of the time it works and all the things are fin; but as soon as i turn it off and turn it back on the bootloader starts appearing.
So, now i can use the cell but i cannot turn it off or leave the battery died on me...any suggestions?
BTW, thank you very much for your help
jsolanon said:
Yes, but the issue persisted.
I have noticed something. If i leave the cell phone turn off for a while (hours) and then i turn it on. Most of the time it works and all the things are fin; but as soon as i turn it off and turn it back on the bootloader starts appearing.
So, now i can use the cell but i cannot turn it off or leave the battery died on me...any suggestions?
BTW, thank you very much for your help
Click to expand...
Click to collapse
My phone is never turned off. I'm not sure what else to suggest, you've tried seemingly every step that could remedy this problem. Radio firmware probably won't help, but it shouldn't hurt either - you could try a new radio...
hi , this happened to me, solved it by reloading the rom again via sd, once it finish maybe you will see the bootloader screen again, so with stylus pres the reset buttom a few times until the rom boot , this can take several times to make it boot. after revive your cell , do a task29 then reload the rom again then do a hard reset, this happened to my 2 times, and its still alive ,good luck.
Same Problem
Hi,
I'm having the same problem. Installed the latest official ROM from HTC/ATT (gorgeous), and same problem after install. Whenever you try to reboot, it gets stuck in the bootloader screen. The last 50 tries it will not reboot at all, even after removing the battery and hitting the power button. This used to work occasionally.
Any other process anyone knows for getting the device to read the ROM?
Is the phone just worn out?
I suggest you reflash the shipped rom to your device and after the flash finishes and your device begins to boot immediately remove the battery to turn it off before it boots. Then replace the battery and press and hold the Send and End keys and while holding them down press the Power button and follow the instructions to factory reset(hard reset).
I'm running CM11 on my M8 and use TWRP 2.7.1.0 as my recovery,
the problem is, when I charge my phone when turned off, it boots straight into TWRP, without me pressing volume down or something.
Then the screen flickers between TWRP and the charging screen, which is really annoying.
anytime I turn on the phone to check the battery status, it reboots into TWRP.
Is there a way to fix this?
I can't use stock recovery because I need TWRP in order to update CM11 nightlies.
I've googled about it but I haven't found ANYTHING :/
Far as I know, its a known issue for a long time, and don't know why TWRP hasn't been fixed.
Not really a solution, but why charge the phone with power off at all? I just about never turn my phone off. The only reason I noticed this at all was by mere chance. I think the phone had powered off during the root/s-off process, and that is the only time I've noticed this bug.
Have you tried CWM?
I give it a try.
Is this the correct file? http://download2.clockworkmod.com/recoveries/recovery-clockwork-touch-6.0.4.8-m8.img
I flashed CWM, the issue still exists!
Same issue as stated above. I wonder if Philz Recovery works better. Ill probably give that a try later.
Same Problem
jaxenroth said:
Same issue as stated above. I wonder if Philz Recovery works better. Ill probably give that a try later.
Click to expand...
Click to collapse
Anyone find a solution yet? Also seems to make the battery level jump around when you turn it on and off during charging.
What ever it may be the best recovery is TWRP for me anyways. For me I had several issues with CWM, like flashing and installing of ROMS.
Well I too have this bug but its not a great scene. Adjustable
Device is fine and can be used via bluetooth mouse / keyboard - however, touchscreen went completly dead
formatted it - changed image, same result
anyone have any idea how to fix it , like a link to a video - part needed - or even a UK store
thanks
I have a similar issue.
I've had my Pixel C for around 11 Months, purchased direct from the google store in November 2017.
Last week I opened the tablet and the screen was totally unresponsive. The physical buttons were working so after several forced reboots which did not help I went for the Nuclear option and restored the device to factory defaults. This didn't work either and I was still unable to interact with the screen so logged a call with Google. I was about to invoke the warranty when suddenly the device responded again after a further reboot. I agreed with the support person that I would keep it for the time being, hoping it was just a glitch
Unfortunately the problem has recurred twice again and the only way to recover seems to be to power the device off, leave it for a "while" and power on.. not exactly scientific.
Has anyone else experienced similar issues? The device received a security update mid last week so I wonder if this is more than coincidence.
Any road, in this state the device is completely unreliable so I'll be looking to return it. I'm assuming google will not have any new replacements so I need to find an alternative android tablet
touch screen pixel c unreliable
owens2000 said:
I have a similar issue.
Has anyone else experienced similar issues? The device received a security update mid last week so I wonder if this is more than coincidence.
Any road, in this state the device is completely unreliable so I'll be looking to return it. I'm assuming google will not have any new replacements so I need to find an alternative android tablet
Click to expand...
Click to collapse
Same for me. The touchscreen is unresponsive, thought it would be hardware damaged, but did a couple of restarts, and all of a sudden I was able to type ten letters, then unresponsive again. Were you able to resolve this issue? Thanks!
after the last few updates the screen would respond less and less. This last update last night killed the screen completely. Zero response! I honestly think this is an error on their part but even if they fixed it in an update I cant get in to install the update!
I wanted to root and install a custom rom to see if that would fix it but honestly Ive been out of the loop for so long and without going into dev mode Im not sure I can at all.
tevil said:
I wanted to root and install a custom rom to see if that would fix it but honestly Ive been out of the loop for so long and without going into dev mode Im not sure I can at all.
Click to expand...
Click to collapse
I know how you feel. Same here, touchscreen became unresponsive before I could do any settings to flash anything else e.g twrp. Please share your next steps. Thanks
milgrave said:
I know how you feel. Same here, touchscreen became unresponsive before I could do any settings to flash anything else e.g twrp. Please share your next steps. Thanks
Click to expand...
Click to collapse
Im working on trying to unlock the bootloader right now. I tried the toolkit but its giving me a syntax error on trying to flash in fastboot since thats the only thing I can get to. Whats crazy is even the android recovery option is corrupt and this is a stock tablet. I really think google did this to these devices on purpose or unintentionally but has no intention on fixing them. I couldnt even run the update any since there is no way for me to get to anything.
Im looking for instructions on how to do everything from fastboot and ADB but everything is so outdated.
milgrave said:
I know how you feel. Same here, touchscreen became unresponsive before I could do any settings to flash anything else e.g twrp. Please share your next steps. Thanks
Click to expand...
Click to collapse
Hey sorry to post twice but try these. I just tried these steps and got my tablet fully wiped (do caches first) and working. Im enabling USB debugging and bootloader unlock and doing it all now. This was proven to be a google update issue to me.
Perform a master reset
https://thedroidguy.com/2019/08/how...3-xl-touchscreen-not-responding-issue-1094388
To factory reset your Google Pixel 3 XL:
Turn off your Google Pixel 3 XL.
Press and hold the Power+Volume Down buttons until bootloader mode (image of an Android with Start above it) appears, then release.
Select Recovery mode. You can use the Volume buttons to cycle through the available options and the Power button to select. The device will flash the Google start screen momentarily and then restarts in Recovery mode.
If presented with an image of a broken Android with “No Command” printed on the screen, press and hold the Power button. Press the Volume Up button once. Then release the Power button.
From the Android Recovery screen, select Wipe data/factory reset.
Select Yes. Wait for several minutes for the factory data reset process to complete.
Select Reboot system now. Allow several minutes for the factory data reset and reboot processes to complete.
Set the phone up again.
from there I just now used wugfreshs tool kit to unlock the bootloader and Im going to install TWRP and probably a custom rom to avoid updating again.
Update: def a software issue. I worked fine with this tablet for a few hours. Installed 1 app then it locked again. Opera browser. I've had my suspicions of the app for a while which is why I tested this app first. I'm using those same steps again to wipe and seeing if the touchscreen works again. I had trouble getting twrp and a room loaded due to encryption. There is apparently a decrypt file you need to install recovery and root. I can't seem to locate the correct one but wugs toolbox sees the device fine once the drivers are installed.
Ill keep this running and updated with results.
Full wipe and reset again and the screens not working again. What stinks is I once again can't get it into dev mode. I guess maybe it is a hardware issue. Sad, this thing has always been in a case and babied. I still think tho it's a bug with newer releases and the hardware in certain C's. It's beyond warranty though so what can we say to Google at this point. It's not even an old tablet and was pretty pricey. My Nexus 9 still runs perfectly!
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!