[Q] Samsung Galaxy S3, I9300 weird problems - Galaxy S III Q&A, Help & Troubleshooting

HI.
I had installed Odin and flashed the touch CWM 6 to my phone then I installed PureHD custom rom.
I noticed that the phone would reboot on its own every now and then.
But when it reboots, it just goes into a boot loop up to the logo , then reboots again.
Till I take out the battery, wait a little while , then re-insert the batter.
After that the phone will boot "normally" and would be functional for some time again.
I decided to change the Firmware, so i downloaded the cm-10.1-20130701-crDroid-build5-i9300.zip and install it.
That loaded fine for the most part.
I say that because when i try to use the sms application i noticed 2x since last night.
It does the same thing. It just reboots and get stuck at the logo once again.
Also I cannot copy items to my phone when its connected to my computer via the usb cable.
It tells me "cannot copy to device, either the device has either stopped responding or has been disconnected.
All this is very frustrating.
I am thinking about trying to load a stock rom via Odin to see if that will help.
Any ideas will be greatly appreciated.
Thanks..
Protorianbz

[READ THlS FlRST] POST QUESTIONS IN THE Q&A SECTION AND NOT HERE!!!!
Wipe phone and flash stock rom.
jje

I tried that.
I tried to isntall the STock rom.
It was installed via Odin successfully.
I saw the green Android man for a split second.
And phone just reboots, and now is stuck in the boot loop to the logo..
then reboots again..

This is the output form Odin 3.07
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I9300XXEMC3_I9300NEEEMC1_I9300XXEMB6_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Odin v.3 engine (ID:3)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> tz.img
<ID:0/003> NAND Write Start!!
<ID:0/003> sboot.bin
<ID:0/003> system.img
<ID:0/003> boot.img
<ID:0/003> recovery.img
<ID:0/003> cache.img
<ID:0/003> hidden.img
<ID:0/003> modem.bin
<ID:0/003> RQT_CLOSE !!
<ID:0/003> RES OK !!
<ID:0/003> Removed!!
<ID:0/003> Remain Port .... 0
<OSM> All threads completed. (succeed 1 / failed 0)

have you tried a hard reset? format data , cache and dalvik in recovery? after you successfully flashed stock rom? hope that helps

Try using MegaWipe from here: http://forum.xda-developers.com/showthread.php?t=1832326&page=31
and then flash a ROM.
Just don't forget to backup the Important stuff.

Just wipe phone and install stock rom
Sent from my GT-I9300 using xda premium

Thread moved to proper forum.

DiDA™ said:
Try using MegaWipe from here: http://forum.xda-developers.com/showthread.php?t=1832326&page=31
and then flash a ROM.
Just don't forget to backup the Important stuff.
Click to expand...
Click to collapse
^^ What s/he said...
You don't mention the word wipe so I figure you didn't do that. If you can't get into the phone you should do your battery-removal thing and let the phone get into the OS, then connect USB and copy out the files you need to save. If you've got a backup to your extSDcard that would be helpful - you can always restore data from an advanced CWM Restore setting.
Copy the ROM you want across to the estSDcard using USB
Download megawipe, copy it to estSDcard and flash it in CWM.
Flash your ROM and restart phone, Set it up and once done, then start adding apps and restoring data, THEN make a full backup.
As a rule, the only time you do not do a full wipe of your phone is when you are flashing a point upgrade. i.e. going from AbcROM 7.1 to AbcROM 7.2 - if you are changing ROMs or doing a full step upgrade (AbcROM 7.x to AbcROM8.x) you need to do a full wipe to avoid problems.

Related

[Q][Troubleshooting] Soft Brick?

Hi all. I thing my phone is struggeling to survive.
First I'll give you some background info:
Phone is SGS3 I9300.
[ROM] Has been running Omega Rom since one of the first versions. Been running v32 since it was released (not v32.1)
[Kernel] Been running Omega's tweaked stock kernel most the time, but installed SiyahKernel 1.7rc3 some days ago.
About a week ago I recieved a 64gb SanDisk MicroSDXC card and installed Mittiadj's ExtSD2InternalSd script.
[recovery] CWM V6.0.1.2
So, what happened?
Well, when I installed the extsd2internal it wouldn't apply on boot, so per his guide, I installed Script Manager and got it working.
Some days ago I wiped system, flashed omega 32, flashed siyah kernel and flashed the extsd2internal for custom kernels.
Now the script worked without script manager.
After I installed Siyah, the phone reboted twice, about a day or 2 apart. The 3rd time it rebooted automatically, it did not manage to boot again (stopped at the Siyah boot logo,the purple eye).
From here, I switched the phone off, and using vol-up+home+power, I am SOMETIMES able to get into recovery. However, in recovery, I am able to flash cache but not dalvik, I tried flashing Omega, but it froze during the install wizard, I tried wiping system (for another attempt at Omega) but it rebbots then also.
Now the phone only gets to the White Samsung logo or to recovery (but recovery only shows version and the text)
E: can't mount /cache/recovery/command
Click to expand...
Click to collapse
If I hold vol-down+home+power, I get to a question if I want to install Custom ROM, vol down for cancel, up for yes. Pressed down.
Warning!! A custom OS can cause critical....
If you want to download a custom OS, press the volume up key, otherwise, press volume down
Click to expand...
Click to collapse
Where can I go from here?
What has gone wrong?
I am suspecting the memory chip is fubar, but hope someone can tell me otherwise
For the record, I have tried booting with and without sim and microsd, no change comes from that.
In the mean time I guess it's time to resurrect the god'ol Nexus One
Requiem87 said:
Hi all. I thing my phone is struggeling to survive.
>>>>>>
f I hold vol-down+home+power, I get to a question if I want to install Custom ROM, vol down for cancel, up for yes. Pressed down.
Quote:
Warning!! A custom OS can cause critical....
If you want to download a custom OS, press the volume up key, otherwise, press volume down
This reads as totally bolocksd firmware and recovery .
Remove SD card and format it in windows as FAT 32 .
Boot to download mode and flash stock rom via Odin as alternative is a non warranty repair .
jje
jje
Click to expand...
Click to collapse
JJEgan said:
Requiem87 said:
Hi all. I thing my phone is struggeling to survive.
Remove SD card and format it in windows as FAT 32 .
Boot to download mode and flash stock rom via Odin as alternative is a non warranty repair .
Click to expand...
Click to collapse
Tried flashing CWM via ODIN, but get an error after Writing stage. (i shoulden't have done that, because before the flash counter was 0, and it showed stock, after it shows as modified
Any reason to believe that flashing a stock rom will work better than flashing CWM?
Click to expand...
Click to collapse
Confused flashed CWM >> do you mean root ???
Stock rom has a kernel and would at least be on the right road for a warranty repair .
jje
JJEgan said:
Confused flashed CWM >> do you mean root ???
Stock rom has a kernel and would at least be on the right road for a warranty repair .
jje
Click to expand...
Click to collapse
Phone is allready rooted, as i had Omega Rom installed.
CWM means ClockWorkMod Recovery. I allready had that installed to, but as i wrote in first post, I had trouble getting it into recovery mode.
Nothing's changed in that regard tho
Update:
Tried flashing a stock rom via Odin, and this is the error message I get:
Code:
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I9300XXDLJ4_I9300TENDLJ3_I9300XXDLID_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Odin v.3 engine (ID:3)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> system.img
<ID:0/003> NAND Write Start!!
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<ID:0/003> Added!!
<OSM> All threads completed. (succeed 0 / failed 1)
Requiem87 said:
Phone is allready rooted, as i had Omega Rom installed.
CWM means ClockWorkMod Recovery. I allready had that installed to, but as i wrote in first post, I had trouble getting it into recovery mode.
Nothing's changed in that regard tho
Update:
Tried flashing a stock rom via Odin, and this is the error message I get:
Code:
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I9300XXDLJ4_I9300TENDLJ3_I9300XXDLID_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Odin v.3 engine (ID:3)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> system.img
<ID:0/003> NAND Write Start!!
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<ID:0/003> Added!!
<OSM> All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse
not looking so good - I think I would have another go at flashing stock - my AV/ firewall sometime stop odin trying disabling them - I suspect it wont help but hopefully it will

[Q] Stuck in Odin mode and Odin flashes failing

So, was working on flashing a custom ROM on my wife's phone (I've flashed phones countless times, even plenty with Odin), but after an issue flashing the Recovery, the phone wouldn't boot and would go straight to the Download every time. I've tried flashing a couple ROMs via Odin, but kept getting an odd message until I applied a PIT file. The phone booted back to how it was successfully.
Seems the Recovery is messed up though, so I need to try and fix that.
I tried to use Odin to apply a factory image, but it failed (see phone screenshot attached and Odin log below)
Code:
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> ALL_I545VRUEMJ7_I545VZWEMJ7_1937946_REV06_user_low_ship_MULTI_CERT.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Odin v.3 engine (ID:3)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Set PIT file..
<ID:0/003> DO NOT TURN OFF TARGET!!
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> sbl1.mbn
<ID:0/003> NAND Write Start!!
<ID:0/003> sbl2.mbn
<ID:0/003> sbl3.mbn
<ID:0/003> rpm.mbn
<ID:0/003> aboot.mbn
<ID:0/003> FAIL! (Auth)
<OSM> All threads completed. (succeed 0 / failed 1)
Went to reboot back into the OS, but now it goes to "Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again." I tried this last night, but it said my phone was unsupported...
Ugh, finally convinced my wife to get a smart phone and now all of this...
You're trying to flash an MJ7 build. Is that the build you had when you started? I'm thinking you'll need to try the NC5 full wipe tar file with Odin.
The Verizon S4 is pretty locked down. Unless you have a phone with an MDK build, you will be extremely limited as to what you can do. Best to do a little research before you brick your phone permanently.
Sent from my NCC-1701 using Tapatalk.
I was able to get it to boot back to the prior running version after applying a .pit file (I thought that would have wiped everything)... Determined that it is FNC5 and flashed with that. It apparently didn't wipe the data, but I did a factory reset afterwards. I noticed though that now WIFI won't turn on... Really need to get this working well one way or another...
Interestingly enough, I have another of the same model phone that I haven't had any issues really with...
If I could just get a working recovery on it, I have a feeling I would be fine (I could just flash the same ROM as I have on my other phone AND make sure things are actually wiped!).
If I try to push about any recovery console via several methods, they all fail. Is it possible that the partition or something is messed up? Any sure fire way of fixing it (or a good route in the right direction)? I would LOVE to take this phone even back to 100% new phone, wiping out everything...
@riker147 MDK build? I don't see a version that had MDK in the version for my phone... SCH-I545 (Verizon)
MDK was a very early build.It was the only one that could have a custom recovery because of an exploit that was found. A later update fixed that exploit. (No, you can't revert to an earlier build) Now our only option for any type of recovery is Safestrap. Just be aware, Safestrap is very limited. Like I said earlier, best to do some research.
Sent from my NCC-1701 using Tapatalk.

[Q] Softbricked my S4 ;(

Hey everyone,
I tried updating my Verizon Galaxy S4 to Lollipop via Samsung Kies. The update process produced an error message (at app. 10%) and offered me to start the recovery process, which failed subsequently. Needless to say, Android OS does not work, however I can still boot into download/recovery mode.
I've been trying to flash various stock ROMs via Odin 3.10 with no success. The build numbers of the ROMs I've been trying to flash contained the I545VRUFNC5 number, since I tried preserving compatibility with the previous (Stock) ROM that had the same build number. Prior to flashing Lollipop via Kies, I made the made a screenshot (attached below) in case I ran into some kind of trouble. It contains the Model/Build of my S4.
I've also tried using a PIT file during the flashing process with no success.
The error message Odin gives me always reads:
Code:
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I545VRUFNC5_I545VZWFNC5_I545VRUFNC5_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Odin engine v(ID:3.1005)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Set PIT file..
<ID:0/003> DO NOT TURN OFF TARGET!!
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> SingleDownload.
<ID:0/003> aboot.mbn
<ID:0/003> NAND Write Start!!
<ID:0/003> FAIL! (Auth)
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/003> Removed!!
The main question is whether I need to stick to build I545VRUFNC5 to reflash. If not, which Stock ROM am I able to Install via Odin without bricking the phone further
For exact phone model/specs pls open the screenshot below. I would also be very grateful if someone could provide me a stock ROM (name/link/version) that I could flash via Odin to resolve the mess Kies and I created.
Any help is much appreciated.
Thanks in advance.
Make sure to get FULL WIPE AND REPARTITION. All data will be lost..
XxD34THxX said:
Make sure to get FULL WIPE AND REPARTITION. All data will be lost..
Click to expand...
Click to collapse
Thanks for the reply. Sadly, I don't have a custom recovery flashed on my phone. I already tried flashing TWRP and the process resulted in a similar error message as described above (auth fail/error). I've already performed a factory reset via the stock recovery, so the data is already gone
intel.fan said:
Thanks for the reply. Sadly, I don't have a custom recovery flashed on my phone. I already tried flashing TWRP and the process resulted in a similar error message as described above (auth fail/error). I've already performed a factory reset via the stock recovery, so the data is already gone
Click to expand...
Click to collapse
Bad mistake to do TWRP. With reading, you would have known that TWRP is restricted to MDK... Safestrap(@hashcode) is what you have to use. Or Flashfire(@chainfire) or the New Multisystem tool by @hsbadr... Use Odin, get the zip, and flash it in the PDA( or AP) slot. I fixed my friend's when he did that, but he got lucky...
XxD34THxX said:
Bad mistake to do TWRP. With reading, you would have known that TWRP is restricted to MDK... Safestrap(@hashcode) is what you have to use. Or Flashfire(@chainfire) or the New Multisystem tool by @hsbadr... Use Odin, get the zip, and flash it in the PDA( or AP) slot. I fixed my friend's when he did that, but he got lucky...
Click to expand...
Click to collapse
No mate, since the bootloader seems to be locked. It simply didn't flash TWRP - the stock bootloader is still present and running. Trying to flash TWRP was kind of a desparate measure, since I don't have OS access to flash/install any of the above. Also, my phone was 100% stock Kitkat 4.4.2 with no root access
Resolved the issue! =)
The problem was in that the Lollipop update process had already been started (unsuccessfully), Odin was "seeing" the flash process as a downgrade - so it wouldn't allow it.
I tried flashing a stock Lollipop ROM via Odin and it worked like a charm
Thanks for your support.
@mods: Please close/archive this thread.

[Solved] SGS2 stuck in boot animation after flashing stock rom

I need some help with my SGS2.
I was on custom rom CM (6.0.1) with Team win recovery. I wanted to give away my phone to an elderly person and tried flashing the stock firmware with ODIN 3.
All went well but after restarting the phone is stuck at Samsung boot animation for long time.
I tried reflashing, restarting, wipe cache partition, factory reset etc but nothing worked.
Any idea how to come off this?
galaxyII said:
I need some help with my SGS2.
I was omn custom rom CM (6.0.1) with Team win recovery. I wanted to give away my phone to an elderly person and tried flashing the stock firmware with ODIN 3.
All went well but after restarting the phone is stuck at Samsung boot animation for long time.
I tried reflashing, restarting, wipe cache partition, factory reset etc but nothing worked.
Any idea how to come off this?
Click to expand...
Click to collapse
You repartitioned your phone to install cm13
So you have to repartition your phone again with stock pit or a pit that have 1.5gb system and 512mb preload to install stock rom , you will find all needed pits in the repartition thread by Saber.
Flash the pit in odin with CWM kitkat compatible recovery, reboot to recovery and wipe data, cache, dalvik cache, system, and internal storage then reflash stock rom and it should boot
MigoMujahid said:
You repartitioned your phone to install cm13
So you have to repartition your phone again with stock pit or a pit that have 1.5gb system and 512mb preload to install stock rom , you will find all needed pits in the repartition thread by Saber.
Flash the pit in odin with CWM kitkat compatible recovery, reboot to recovery and wipe data, cache, dalvik cache, system, and internal storage then reflash stock rom and it should boot
Click to expand...
Click to collapse
Thanks. I followed Saber's thread and started with PIT file. all went well.
I tried to flash the stock rom, I am stuck in ODIN at Flashing factory.img
<ID:0/005> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I9100XWLSD_I9100XXLS8_I9100DBTLS7_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/005> Odin v.3 engine (ID:5)..
<ID:0/005> File analysis..
<ID:0/005> SetupConnection..
<ID:0/005> Initialzation..
<ID:0/005> Get PIT for mapping..
<ID:0/005> Firmware update start..
<ID:0/005> boot.bin
<ID:0/005> NAND Write Start!!
<ID:0/005> cache.img
<ID:0/005> factoryfs.img
Any ideas how I can proceed?
Update: it worked! i changed the ODIN version and flash was complete and I am able to use the phone.
Thank you very much @MigoMujahid
galaxyII said:
Thanks. I followed Saber's thread and started with PIT file. all went well.
I tried to flash the stock rom, I am stuck in ODIN at Flashing factory.img
<ID:0/005> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I9100XWLSD_I9100XXLS8_I9100DBTLS7_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/005> Odin v.3 engine (ID:5)..
<ID:0/005> File analysis..
<ID:0/005> SetupConnection..
<ID:0/005> Initialzation..
<ID:0/005> Get PIT for mapping..
<ID:0/005> Firmware update start..
<ID:0/005> boot.bin
<ID:0/005> NAND Write Start!!
<ID:0/005> cache.img
<ID:0/005> factoryfs.img
Any ideas how I can proceed?
Click to expand...
Click to collapse
galaxyII said:
Update: it worked! i changed the ODIN version and flash was complete and I am able to use the phone.
Thank you very much @MigoMujahid
Click to expand...
Click to collapse
Good to know it worked , always use Odin 3.07 or 3.09 , i always get issues with Odin 3.10.x
MigoMujahid said:
Good to know it worked , always use Odin 3.07 or 3.09 , i always get issues with Odin 3.10.x
Click to expand...
Click to collapse
for me the
PIT file flashing worked only in Odin3 v 1.85
Flashing ROM worked only with Odin3 v3.07
Thanks once again.

fail to flash stock rom with odin

I kind of brick my phone , after it stopped in the middle of a flash due to a bad cable. Now all i have is a black screen with a phone, a yellow triangle and a PC icons.
I changed the cable and when trying to flash with this rom: I9100GXXLSR_I9100GXXLSP_I9100GXEFLSR_HOME.tar
the flash process always stops at about 99%. This is the log:
Code:
OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/006> Odin engine v(ID:3.1205)..
<ID:0/006> File analysis..
<ID:0/006> SetupConnection..
<ID:0/006> Initialzation..
<ID:0/006> Set PIT file..
<ID:0/006> DO NOT TURN OFF TARGET!!
<ID:0/006> Get PIT for mapping..
<ID:0/006> Firmware update start..
<ID:0/006> SingleDownload.
<ID:0/006> cache.img
<ID:0/006> factoryfs.img
<ID:0/006> hidden.img
<ID:0/006> MLO
<ID:0/006> FAIL!
<ID:0/006>
<ID:0/006> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
HOW can I solve this, please.
PS: I live in Morocco.
AhmedElakrab said:
I kind of brick my phone , after it stopped in the middle of a flash due to a bad cable. Now all i have is a black screen with a phone, a yellow triangle and a PC icons.
I changed the cable and when trying to flash with this rom: I9100GXXLSR_I9100GXXLSP_I9100GXEFLSR_HOME.tar
the flash process always stops at about 99%. This is the log:
Code:
OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/006> Odin engine v(ID:3.1205)..
<ID:0/006> File analysis..
<ID:0/006> SetupConnection..
<ID:0/006> Initialzation..
<ID:0/006> Set PIT file..
<ID:0/006> DO NOT TURN OFF TARGET!!
<ID:0/006> Get PIT for mapping..
<ID:0/006> Firmware update start..
<ID:0/006> SingleDownload.
<ID:0/006> cache.img
<ID:0/006> factoryfs.img
<ID:0/006> hidden.img
<ID:0/006> MLO
<ID:0/006> FAIL!
<ID:0/006>
<ID:0/006> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
HOW can I solve this, please.
PS: I live in Morocco.
Click to expand...
Click to collapse
Try extracting a copy of the stock recovery.img from the firmware, then convert it to an Odin flashable .tar.md5, flash it via Odin, then boot into stock recovery, then factory reset and wipe cache, then reboot. Then try flashing the firmware.
Or, try flashing TWRP via Odin, then boot into TWRP, wipe everything, then reboot, then try flashing the firmware.
Sent from my LGL84VL using Tapatalk
Droidriven said:
Try extracting a copy of the stock recovery.img from the firmware, then convert it to an Odin flashable .tar.md5, flash it via Odin, then boot into stock recovery, then factory reset and wipe cache, then reboot. Then try flashing the firmware.
Or, try flashing TWRP via Odin, then boot into TWRP, wipe everything, then reboot, then try flashing the firmware.
Sent from my LGL84VL using Tapatalk
Click to expand...
Click to collapse
Thank you. It was a problem with the firmware. I Downloaded the right firmware for my country and it has flashed ok.
But now I have a bigger problem. The Phone over heats near the camera and randomly freezes and restarts.
Do you have any Idea why he's doing that.
AhmedElakrab said:
Thank you. It was a problem with the firmware. I Downloaded the right firmware for my country and it has flashed ok.
But now I have a bigger problem. The Phone over heats near the camera and randomly freezes and restarts.
Do you have any Idea why he's doing that.
Click to expand...
Click to collapse
Have you tried booting to stock recovery then factory reset and wipe cache partition? Sometimes there is stuff left on the device from before you flashed it, that remaining data causes bugs, factory reset and wipe cache fixes that.
Sent from my LGL84VL using Tapatalk
Droidriven said:
Have you tried booting to stock recovery then factory reset and wipe cache partition? Sometimes there is stuff left on the device from before you flashed it, that remaining data causes bugs, factory reset and wipe cache fixes that.
Sent from my LGL84VL using Tapatalk
Click to expand...
Click to collapse
Thank you, again.
I already did a factory reset but haven't cleared the cache yet.
I'm on it. And will tell how it goes.
AhmedElakrab said:
Thank you, again.
I already did a factory reset but haven't cleared the cache yet.
I'm on it. And will tell how it goes.
Click to expand...
Click to collapse
On stock? For me this was the horrid media scanner glitch. I had to root my phone to force the device from scanning for new content and this was via a play store app.
Sent from my iPhone using Tapatalk Pro
AhmedElakrab said:
Thank you. It was a problem with the firmware. I Downloaded the right firmware for my country and it has flashed ok.
But now I have a bigger problem. The Phone over heats near the camera and randomly freezes and restarts.
Do you have any Idea why he's doing that.
Click to expand...
Click to collapse
jr866gooner said:
On stock? For me this was the horrid media scanner glitch. I had to root my phone to force the device from scanning for new content and this was via a play store app.
Click to expand...
Click to collapse
I had similar problem a few years ago. Phone was extremally hot near the camera and a process called media scanner (I think that's it's name) was running all the time forcing CPU to go up to 1,2GHz
To fix that problem I had to install SD main pro and run it. It turned out I had many, many gigs of some kind of cache files. After painfull long time and boiling hot temperature near camera SD main managed to get rid off all of that useless staff. After that phone felt lighter and media scanning process after reboot was taking less then 45 seconds to finish
Sent from my whyred using XDA Labs

Categories

Resources