arter97 kernel for Galaxy S3

[Rnirosh]

Need help. i just flashed arter97 with Slim-i9300-e210-5.1.1.beta and Temasek-12.1-V18.6 . both of them stuck in bootanimation. Model- Shv-e210K . any solution ??

 

[giannhs_n]

Galaxy s3 KT-LTE E210K

Op says supported devices

Galaxy S3 KT-LTE (SHV-E210K)

I downloaded the latest version 5.0 of the kernel.. But my phone stuck at kernel logo.. I can't use this kernel with stock 4.4? Any suggestions? This kernel is not for my device? Thanks

 

[iceman0826]

@arter97 if just incase you're bored, I hope you can port the Android Go Edition ported to Korean S3 I think they are capable as opposed to the other 2012 era devices

 

[Hamx5]

Question for @arter97
Does this kernel support i/o accounting?
I need this for i/o monitoring (cause of lag in my s3)

 

[De Gu]

lineage os 14.1 on work?

 

[mario6714]

Go to recovery, (If PhilZ, turn the screen off by swiping to the left - to prevent burn-ins.. )

Open adb shell,
umount /data
umount /cache
umount /system
umount /preload
dd if=/dev/zero of=/dev/block/mmcblk0p8 bs=16M
dd if=/dev/zero of=/dev/block/mmcblk0p9 bs=16M
dd if=/dev/zero of=/dev/block/mmcblk0p10 bs=16M
dd if=/dev/zero of=/dev/block/mmcblk0p12 bs=16M
sync

And reboot to download mode from the reboot menu, use ODIN to flash stock firmware.
After flashing stock firmware, it'll automatically enter recovery to apply CSC.
After recovery exits, be quick and enter recovery manually yourself.
It'll complain it can't mount /cache and /data. Ignore and do a factory reset, and reboot.

Don't flash anything custom until you get stock firmware running perfectly.

0p8 = cache
0p9 = system
0p10 = preload
0p12 = data (will take tens of minutes)

At the end of each dd command, it will complain that no more space is available. That's normal, however if you got some another error, that means your nand is hardwarelically corrupted..

Sent from my SHV-E330S using XDA Free mobile app

i have stock recovery, how i can open adb shell?

Sorry my bad english

 

[zlazaar]

i have stock recovery, how i can open adb shell?

Sorry my bad english

Choose "Apply update from ADB"

 

[mario6714]

Choose "Apply update from ADB"

What i need install?

 

[zlazaar]

What i need install?

Now you know how to open an ADB shell, you have to follow instructions in the post you already quoted.

 

[mario6714]

Choose "Apply update from ADB"

Dont Work

 

[zlazaar]

Dont Work

Please open a new thread with all infos you can give about your devise and problem in "Help & troubleshooting" section of this forum.

 

[mario6714]

Choose "Apply update from ADB"

Please open a new thread with all infos you can give about your devise and problem in "Help & troubleshooting" section of this forum.

New thread?

Here

https://xdaforums.com/galaxy-s3/help/help-able-to-flash-forward-t3857088

https://xdaforums.com/galaxy-s3/help/galaxy-s3-crapped-stuck-galaxy-screen-t3730285

https://xdaforums.com/galaxy-s3/help/stuck-splash-screen-logo-samsung-galaxy-t3843460

Same problem... why open another thread?

Here my thread:

https://xdaforums.com/galaxy-s3/help/stuck-splash-screen-logo-gt-i9300-t3860577

 

[mario6714]

Dont Work

Choose "Apply update from ADB"

Here, nother error

 

[zlazaar]

New thread?

Here

https://xdaforums.com/galaxy-s3/help/help-able-to-flash-forward-t3857088

https://xdaforums.com/galaxy-s3/help/galaxy-s3-crapped-stuck-galaxy-screen-t3730285

https://xdaforums.com/galaxy-s3/help/stuck-splash-screen-logo-samsung-galaxy-t3843460

Same problem... why open another thread?

Here my thread:

https://xdaforums.com/galaxy-s3/help/stuck-splash-screen-logo-gt-i9300-t3860577

A new thread was a try to know more about the device you use, its variant, current firmware, what you want to do, origins of your problem...
It was a polite manner to say : expose your problem in the right place with the right infos if you seek for help.
You'r good in using Search button, so keep up the good work...
BTW, you post in wrong thread, wrong section and wrong devise forum.

 

[mario6714]

A new thread was a try to know more about the device you use, its variant, current firmware, what you want to do, origins of your problem...
It was a polite manner to say : expose your problem in the right place with the right infos if you seek for help.
You'r good in using Search button, so keep up the good work...
BTW, you post in wrong thread, wrong section and wrong devise forum.

Ok, Thanks for the help

 

[r3actor]

Go to recovery, (If PhilZ, turn the screen off by swiping to the left - to prevent burn-ins.. )

Open adb shell,
umount /data
umount /cache
umount /system
umount /preload
dd if=/dev/zero of=/dev/block/mmcblk0p8 bs=16M
dd if=/dev/zero of=/dev/block/mmcblk0p9 bs=16M
dd if=/dev/zero of=/dev/block/mmcblk0p10 bs=16M
dd if=/dev/zero of=/dev/block/mmcblk0p12 bs=16M
sync

And reboot to download mode from the reboot menu, use ODIN to flash stock firmware.
After flashing stock firmware, it'll automatically enter recovery to apply CSC.
After recovery exits, be quick and enter recovery manually yourself.
It'll complain it can't mount /cache and /data. Ignore and do a factory reset, and reboot.

Don't flash anything custom until you get stock firmware running perfectly.

0p8 = cache
0p9 = system
0p10 = preload
0p12 = data (will take tens of minutes)

At the end of each dd command, it will complain that no more space is available. That's normal, however if you got some another error, that means your nand is hardwarelically corrupted..

Sent from my SHV-E330S using XDA Free mobile app

Thanks @arter97 for your post.
I don't think you will see the post, but if you do I'll appreciate it if you can (at least) read it.

I have a bricked S3 I9300 (INT version). It doesn't boot. Screen is full white (with some 'noise'). I cannot enter recovery. I can only enter in download mode.

I've tried to put twrp image by using ODIN but it fails. I also tried to put PIT file (which I downloaded here somewhere at XDA), and it returns 'Re-Partition operation failed.'.

I tried to install custom usb driver and use 'Heimdall-Suite'. Heimdall recognize the device but it also fail to load PIT file. I even tried to load sboot or recovery.img along with PIT in Heimdall, but it just simple fail everytime. I'm pretty sure that NAND (eMMC) is damaged. And probably the only solution might be to replace eMMC (or whole motherboard).

I cannot use your adb command because when I enter 'download' mode, and type in command prompt 'adb devices' (under windows 7), it list nothing. OFC I can't boot into android OS and put 'USB debugging' (although I think that was 'checked' before phone was bricked).

This phone was my sisters phone. She got it under contract (for 24 months period). After 2 years (24 months) she continued to use the phone (even after contract period was finished). After probably more 1-2 years, she got new phone and this one she gave to her kids to 'play with it'. Ofc , after some time this phone got stuck on Samsung logo.

I tried to enter recovery but I got a lot of 'red line' messges that it can't mount efs and other partitioins. I wanted then, to flash official ROM (it was official before but I thought that flashing same rom would 'fix things').

So, i've downloaded official Samsung ROM and tried to flash it in ODIN. Odin got stuck (withoug finishing the process). I waited probably 40 min but it was still stuck. (I had previous experience with flashing S2 I9100 and I knew that flashing process doesn't take that long). So after 40 min, I simply pull out the USB cable from the phone. I tried to reboot it, but from that moment, all I got was WHITE screen (with some 'dirt noise') and phone can't load. I also cannot enter recovery. (screen stays white). I only can enter download mode.

I tried loading different PIT files (as it was my 'last solution'). BUT nothing happen. (maybe I even fcked it more than it was, by using PIT files that I found 'around'). Maybe everything was because phone was not 'unlocked' after my sister had her phone past the 24 months contract. I don't know. I'm not an expert.

So, is there any way this can be fixed, aside from changing a whole motherboard or eMMC (NAND) chip? As I said, I can't use 'adb' since I can only put phone in download mode (and only in download mode I see what is written on the screen).

Thanks in advance for your help!

Here is an image that shows how it was 'before' and how it is now (after I tried to flash recovery via odin).

h*t*t*p://i.imgur.com/50i80rA.jpg

^ just remove 'stars' (****) from the link above. Since I don't have more than 10 posts, I'm not allowed to leave 'live' links, yet.