Hi friends.
Yesterday I Flashed the ROM 15s through TWRP not sure about if it is Indian or Chinese ROM, my phone is x820, after the flash my phone booted with the screen split in the middle and opposite, however the touch was responsable like always in the original distribution, so was very annoying to navigate in the phone...
Anyway, some of you know why this happens? I flash in the wrong way? I missed something?
Why such an OLD ROM? I recommend you 20s from Madsurfer. Do a clean install.
I want to start over, and updating by OTa. I have tried all the Roms. In fact I am now with the dev21s from Madsurfer which for me is great. The problem is that I am having an issue with BT with many Roms. So I want to go back.
try the rom of "cuoco" works fine or "small eui 5.9"
icerebro said:
I want to start over, and updating by OTa. I have tried all the Roms. In fact I am now with the dev21s from Madsurfer which for me is great. The problem is that I am having an issue with BT with many Roms. So I want to go back.
Click to expand...
Click to collapse
Hi icerebro,
Were you able to solve the problem on the screen?
I'm having the same problem though, it occurred after restoring the device from a brick, with the dev-qfyl version.
Thanks!
SolecAsses said:
Hi icerebro,
Were you able to solve the problem on the screen?
I'm having the same problem though, it occurred after restoring the device from a brick, with the dev-qfyl version.
Thanks!
Click to expand...
Click to collapse
Yes I did, I realized that had to use another version of TWRP and be sure about the version of the ROM you are installing.
this happened to me today. i flashed 14s cn and got the splitscreen, even in twrp. flashed 16s cn and it's back to normal.
don't panic
Gesendet von meinem LEX820 mit Tapatalk
A.N.Droid said:
this happened to me today. i flashed 14s cn and got the splitscreen, even in twrp. flashed 16s cn and it's back to normal.
don't panic
Gesendet von meinem LEX820 mit Tapatalk
Click to expand...
Click to collapse
The TWRP version that you are using isn't compatible with the 014s that you just flashed. Until 015s the EUI was 5.6 and had a different kernel than 016s which is 5.8. Therefore the TWRP versions are different. Flashing wrong ROMs will render your phone with split screen issue or won't boot at all, it depends.
Simply put, search for TWRP 5.8 TeaMSpaiN that works with almost everything above 016s and TWRP 3.0.2 for any version below.
i experimented a lot yesterday with qfil/flashone. for me it looks like it is not kernel related. i flashed different kernel and the issue remained.
what i found is: if you replace the file emmc_appsboot.mbn (seems to be the bootloader, isn't it?) with a newer one (i took it from 20s), no splitscreen occurs. the qfil-dev and 14s roms boot up and behave absolutely normal. also there is no splitscreen in fastboot and twrp but there is a problem with stock recovery. the left side of the screen is covered by some kind of white-noise pattern and it reboots after a few seconds. it looks very much like the pattern we covered in the "screen flickering" thread.
Gesendet von meinem LEX820 mit Tapatalk
Related
No longer available
this is on 98.124.14?
is this new version to http://forum.xda-developers.com/showthread.php?t=2193275 ? or completely different?
xtam said:
this is on 98.124.14?
is this new version to http://forum.xda-developers.com/showthread.php?t=2193275 ? or completely different?
Click to expand...
Click to collapse
Look in screenshots and read features. This is completely different, also this one based on Au JB.
BMM 2nd System?
Hi Artur,
Can we flash this zip on the 2nd System using BMM? Currently running ICS 4.0.4 stock.
Thanks for the JB EMEA!
markshane said:
Hi Artur,
Can we flash this zip on the 2nd System using BMM? Currently running ICS 4.0.4 stock.
Thanks for the JB EMEA!
Click to expand...
Click to collapse
Yes, any Slot ok. After install this ROM you not able boot ICS ROM because kernel will change to JB automitcally, you need flash ICS kernel via BMM to run your 4.0.4 ROM again.
I was curious how you did it that boot.img will be flashed automatically, now i see:
package_extract_file("boot.img", "/dev/block/mmcblk1p14");
good work.
:good: What could i say, you really a great work, always thank you.
my xt910 was on stock EU JB( http://forum.xda-developers.com/showthread.php?t=2192532 ), installed BMM, did all wipes, installed rom.
I have red led and black screen... and nothing happens... surely i did backup, and reverted back to stock... any suggestions how to make this rom working?
p.s. i tried to erase cid, no juice.
amletinka said:
my xt910 was on stock EU JB( http://forum.xda-developers.com/showthread.php?t=2192532 ), installed BMM, did all wipes, installed rom.
I have red led and black screen... and nothing happens... surely i did backup, and reverted back to stock... any suggestions how to make this rom working?
p.s. i tried to erase cid, no juice.
Click to expand...
Click to collapse
This happened randomly with BMM. You need reboot and try boot again.
hmm...really installed again, works... thanks
Thank you very much! This will be my daily driver until CM or AOKP roms became stable enough
looks promising I'll definitely try it
thank you
This Rom looks nice inverted. The AOSP Deskclock Widget (the digital one) doesn't show up and gives a Error Message.
Thank You! It's my daily Driver now...
man, the THANKS button isnt large enough!
ill try it,
can i install it as stock rom via bmm and then remove bmm?
im asking because all the KEXEC thing, i have now the rom which you based on, there will be problems?
A very nice rom with little and big tweaks and set of useful additions. It will be hard for me to decide between this one and china.jb.retail if you continue to deliver roms rich and stable like this. Thank you Artur.
pretty stable & fast.
tks man, i install to stock slot.
no bug so far.
why this rom so good but less people try?
---------- Post added at 06:01 AM ---------- Previous post was at 06:00 AM ----------
heblu said:
looks promising I'll definitely try it
thank you
Click to expand...
Click to collapse
this is a very great rom. i have used as stock rom.
Awesome rom, have only used stock jelly bean leak before. However I got a weird problem. WHen I got all my settings right, I did a Nandroid Backup. Then i fiddled around with rom toolbox and wanted to revert to my "rom". I restored my backup and now I Only get into AP fastboot mode everytime i boot.
It says:
Ivalid CC OTC/CC:webtop):Invalid sp data
So now i'm downloading fastboot files for jelly bean: http://forum.xda-developers.com/showthread.php?t=2017200
I tried using my old ICS fastboot file but it didn't work, proably cuz I have a JB kernel. Then hopefully I can reflash this rom.
Edit:
Can't even use fastbbot, just keep saying the flasing process fails, got to reflash ics fastboot files, have no idea what will happen now. my CID is still erased.
AW: [ROM][GSM][XT910][BMM 0.3.4]DSEA0588 v1.22en JB 4.1.2 (30.03.2013)
You bricked your Phone, not the Rom.
When you try to flash an RazR M Firmware on an XT910 you shouldn't mess around with any kind of Rom :thumbdown:
Gesendet von meinem XT890 mit Tapatalk 2
HSD-Pilot said:
You bricked your Phone, not the Rom.
When you try to flash an RazR M Firmware on an XT910 you shouldn't mess around with any kind of Rom :thumbdown:
Gesendet von meinem XT890 mit Tapatalk 2
Click to expand...
Click to collapse
Have done it a million times, and each time it has ****ed it up, a Nandroid backup always work. Backups are kinda useless if the tend to brick the phone when you restore them.
I managed to use ICS flashboot files to flash the phone, but I ended up with the same problem.
AW: [ROM][GSM][XT910][BMM 0.3.4]DSEA0588 v1.22en JB 4.1.2 (30.03.2013)
http://forum.xda-developers.com/showthread.php?p=38189529
Gesendet von meinem XT890 mit Tapatalk 2
Hey guys... this is a tough one...
I have a i9300, and it is rooted, and I use Carbon Rom (a AOSP ROM).
My brother bought one i9300 this week. He asked me to root it, and install Carbon Rom too.
Ok, so I rooted the phone, using CF-Root-SGS3-v6.4, via odin. After that, i flashed philz_touch_5.07.1-i9300 recovery, and used it to flash a zip with the AOSP ROM and Gapps. Well, after i flashed the ROM, the phone boots into Carbon, but reboots EVERY 30 SECONDS. I thought it could be a problem with the download, so i flashed the same file that i flashed on mine, but problem still persisted. Then, i tried to Restore on HIS phone, a Nandroid from MY phone. Same thing.... boots normal, and reboots after 30 seconds. At this point, i realized that his Baseband version was different from mine. (it was the only difference i could find). Mine is BUEMA1 and his was UBELL1.
So, i downloaded, from sammobile.com the latest firmware/radio for his carrier. After flashing it, the phone boots Normal into Stock ROM, but it freezes ALL the time. It freezes on normal uses, such as email, whatsapp, etc...
Could something be corrupt? What would it be? IMEI seems to be fine.
I cant think of anything that could cause reboot every 30 seconds on AOSP, and freeze on Stock
Read the Freezing thread .
jje
JJEgan said:
Read the Freezing thread .
jje
Click to expand...
Click to collapse
where is this? couldn't find it
1. Root it again.
2. Install CWM Revovery
3. Copy a Custom ROM & the rightful Gapps to your SD Card.
4. Boot into Recovery and Select the Option "Format System" or use this tweak: http://forum.xda-developers.com/showthread.php?t=1832326 (install it like you would with a ROM) It will Wipe Everything from your phones Internal Memory.
5. Install the Custom Rom first, then Gapps. Then boot up your phone.
I would suggest using CM10.1 for starters.
yurividal said:
where is this? couldn't find it
Click to expand...
Click to collapse
General
Sent from my GT-I9300 using Tapatalk 2
yurividal said:
Hey guys... this is a tough one...
I have a i9300, and it is rooted, and I use Carbon Rom (a AOSP ROM).
My brother bought one i9300 this week. He asked me to root it, and install Carbon Rom too.
Ok, so I rooted the phone, using CF-Root-SGS3-v6.4, via odin. After that, i flashed philz_touch_5.07.1-i9300 recovery, and used it to flash a zip with the AOSP ROM and Gapps. Well, after i flashed the ROM, the phone boots into Carbon, but reboots EVERY 30 SECONDS. I thought it could be a problem with the download, so i flashed the same file that i flashed on mine, but problem still persisted. Then, i tried to Restore on HIS phone, a Nandroid from MY phone. Same thing.... boots normal, and reboots after 30 seconds. At this point, i realized that his Baseband version was different from mine. (it was the only difference i could find). Mine is BUEMA1 and his was UBELL1.
So, i downloaded, from sammobile.com the latest firmware/radio for his carrier. After flashing it, the phone boots Normal into Stock ROM, but it freezes ALL the time. It freezes on normal uses, such as email, whatsapp, etc...
Could something be corrupt? What would it be? IMEI seems to be fine.
I cant think of anything that could cause reboot every 30 seconds on AOSP, and freeze on Stock
Click to expand...
Click to collapse
hi man , I was having this problem before , try to mega wipe then flash a stock rom via odin
Geaquzzil said:
hi man , I was having this problem before , try to mega wipe then flash a stock rom via odin
Click to expand...
Click to collapse
Mega Wipe... what would that be?
I guess it is this: http://forum.xda-developers.com/showthread.php?t=1983489
right?
Anyways, i have flashed a TouchWizz ROM called WanamLite... the phone is SUPER FAST, and freezing is gone.
Too bad he cant use a AOSP (I LOVE Carbon ROM)... but i will let it stick to WanamLite since it is working and rooted. I kind of gave up
yurividal said:
Mega Wipe... what would that be?
I guess it is this: http://forum.xda-developers.com/showthread.php?t=1983489
right?
Anyways, i have flashed a TouchWizz ROM called WanamLite... the phone is SUPER FAST, and freezing is gone.
Too bad he cant use a AOSP (I LOVE Carbon ROM)... but i will let it stick to WanamLite since it is working and rooted. I kind of gave up
Click to expand...
Click to collapse
Did you at least read my post?
DiDA™ said:
Did you at least read my post?
Click to expand...
Click to collapse
I did. Thank you very much.
The thing is, the phone is running so smooth with this WanamLite Rom, that i am afraid of touchung it and it start freezing again. Not even stock ROM was so smooth. It hasnt frozen in 2 days. But I will for sure try your suggestion if i start to see issues with this Rom too.
I would love to be able to run CarbonRom on his device, but i dont want to take the risk of "touching what is working", specially because it is not my device.
Anyways, i appreciate the help i have received on this forum. Seriously, thank you very much, to each one of you.
yurividal said:
I did. Thank you very much.
The thing is, the phone is running so smooth with this WanamLite Rom, that i am afraid of touchung it and it start freezing again. Not even stock ROM was so smooth. It hasnt frozen in 2 days. But I will for sure try your suggestion if i start to see issues with this Rom too.
I would love to be able to run CarbonRom on his device, but i dont want to take the risk of "touching what is working", specially because it is not my device.
Anyways, i appreciate the help i have received on this forum. Seriously, thank you very much, to each one of you.
Click to expand...
Click to collapse
With a wipe it will work too. If u have PhilZ u can select in reset menu "Clean to install a new ROM".
Gesendet von meinem GT-I9300 mit Tapatalk 2
TheRealFelix0212 said:
With a wipe it will work too. If u have PhilZ u can select in reset menu "Clean to install a new ROM".
Gesendet von meinem GT-I9300 mit Tapatalk 2
Click to expand...
Click to collapse
I did this... Several times
yurividal said:
I did this... Several times
Click to expand...
Click to collapse
Strange.. On my device it works fine.
Gesendet von meinem GT-I9300 mit Tapatalk 2
TheRealFelix0212 said:
Strange.. On my device it works fine.
Gesendet von meinem GT-I9300 mit Tapatalk 2
Click to expand...
Click to collapse
I know, on mine too. The problem is with my brother's.
Are you certain they are both i9300s
Sent from my GT-I9300 using xda app-developers app
ads2996 said:
Are you certain they are both i9300s
Sent from my GT-I9300 using xda app-developers app
Click to expand...
Click to collapse
100% positive
You need to check its not a fake / clone first .
Settings about phone details .
jje
JJEgan said:
You need to check its not a fake / clone first .
Settings about phone details .
jje
Click to expand...
Click to collapse
It is deffinetely a Genuine Samsung device...
Phone was working perfect until this evening .
I flashed "Googy-Max2 Kernel 2.0.8 (Linux 3.0.101 / Linaro GCC 4.8.2)" kernel on "temasek's UNOFFICIAL Build - V21"
On reboot the touchscreen went unresponsive and yet the hardware keys and the softkeys were working! :crying:
I flashed various other kernels and roms as well as tried a hard factory reset installing the official firmware for India (4.1.2), yet the problem is there unresolved. :crying:
Any help would be highly grateful. :angel:
Touch screen problems after a flash are usually due to flashing the wrong file, probably a Note file, blowing the controller. You'll need a new digitizer.
Sent from my GT-I9300 using Tapatalk
boomboomer said:
Touch screen problems after a flash are usually due to flashing the wrong file, probably a Note file, blowing the controller. You'll need a new digitizer.
Sent from my GT-I9300 using Tapatalk
Click to expand...
Click to collapse
So it could be wrong kernel or ROM ?
Sent from my GT-I9300 using XDA Premium 4 mobile app
Either, as the rom would also contain a kernel.
Sent from my GT-I9300 using Tapatalk
Same thing happened to me, no way I flashed a Note file, used the 1.8 Googly Max kernel on PA 3.99RC2, trying lots of things but nothings working. I really hope the digitizer isn't gone, I replaced the whole screen unit just on Monday.
boomboomer said:
Either, as the rom would also contain a kernel.
Sent from my GT-I9300 using Tapatalk
Click to expand...
Click to collapse
If there isn't something completely wrong with either the rom or the kernel, it's impossible to flash a note kernel to a s3, because of different partitions used.
The only possibility would be an also wrong updater script inside the zip, which flashes the wrong kernel to the "right" partition (like it happened to psndna once).
Gesendet von meinem SAMSUNG-SGH-I317 mit Tapatalk 2
Did you flash 4.1.2stock rom maybe ur touch screen are broken I saw this issue some s3s to and phones touch screens was broken
GT-I9300 cihazımdan gönderildi
boomboomer said:
Either, as the rom would also contain a kernel.
Sent from my GT-I9300 using Tapatalk
Click to expand...
Click to collapse
S1N1ST3R said:
Same thing happened to me, no way I flashed a Note file, used the 1.8 Googly Max kernel on PA 3.99RC2, trying lots of things but nothings working. I really hope the digitizer isn't gone, I replaced the whole screen unit just on Monday.
Click to expand...
Click to collapse
Abo3mood said:
So it could be wrong kernel or ROM ?
Sent from my GT-I9300 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
boomboomer said:
Touch screen problems after a flash are usually due to flashing the wrong file, probably a Note file, blowing the controller. You'll need a new digitizer.
Sent from my GT-I9300 using Tapatalk
Click to expand...
Click to collapse
I didn't flash a wrong kernel. i had my "temasek's UNOFFICIAL Build - V21" Rom installed on my phone with "201113-1224-cm11-i9300-r3p2-linux30101-WOLFSON-temasek" as the current flashed kernel. Due to experiencing lag I decided to try a new kernel which was "Googy-Max2 Kernel 2.0.8 (Linux 3.0.101 / Linaro GCC 4.8.2)".
I wiped the dalvik cache after flashing the kernel, and rebooted my phone. the android updated apps and started with an unresponsive screen.
I just hop that the digitiser isn't screwed up.
P.S:- I've tried the following things.
1. flashing stock rom via odin after a mega/factory wipe technique mentioned in http://forum.xda-developers.com/showthread.php?t=1832326
2. flashing various different roms and kernels with apt procedures.
3. re-rooting the phone and flashing "CWM touch 6.0.4.5" via odin and repeating the process of flashing roms (both stock and custom).
None of the techniques have given me a positive response.
mskomek said:
Did you flash 4.1.2stock rom maybe ur touch screen are broken I saw this issue some s3s to and phones touch screens was broken
GT-I9300 cihazımdan gönderildi
Click to expand...
Click to collapse
Yes i did flash 4.1.2 stock rom after a complete wipe.
I had broken my screen by dropping it quite a while ago which i very recently (2 days ago) got replaced from Samsung carecenter.
Don't know what went wrong.
haseeb2009 said:
Yes i did flash 4.1.2 stock rom after a complete wipe.
I had broken my screen by dropping it quite a while ago which i very recently (2 days ago) got replaced from Samsung carecenter.
Don't know what went wrong.
Click to expand...
Click to collapse
if touchscreen doesnt response in recovery there is bad news for you bro your touchscreen is broken again
i dont think so its a software problem becase nothink work in recovery right!?
DerTeufel1980 said:
If there isn't something completely wrong with either the rom or the kernel, it's impossible to flash a note kernel to a s3, because of different partitions used.
The only possibility would be an also wrong updater script inside the zip, which flashes the wrong kernel to the "right" partition (like it happened to psndna once).
Gesendet von meinem SAMSUNG-SGH-I317 mit Tapatalk 2
Click to expand...
Click to collapse
And I'm sure that he never will make that mistake again:silly:
But sadly a few ppl where affected by his unfortunate mistake..
But humans are no way near perfect and sh.. happens
Hello everyone, I was using ultimarom till now and it worked like a charm. Today I thought hey lets upgrade to android 4.4 so I found temasek's rom and it seemed fine. After flashing the rom, it got stuck on boot screen. So I reflashed the stock rom (btw I wiped everything as required) and it was working. So I retried flashing the Temasek's rom and it booted this time, only thing is that my touch screen was not responding. The capacitive buttons are working also the touch screen is showing everything but not responding to anything. I searched a little bit, and it might be possible that my digitizer is broken which I hope is not since I am in a different country and it will be a pain to do it here. Also I read that if you tried to install Note 2 kernel/rom this might happen but I know that temasek's rom is definitely for s3 so it shouldnt be the case for me. Any help would be appreciated.
Thanks
Bektas
Darrier said:
Hello everyone, I was using ultimarom till now and it worked like a charm. Today I thought hey lets upgrade to android 4.4 so I found temasek's rom and it seemed fine. After flashing the rom, it got stuck on boot screen. So I reflashed the stock rom (btw I wiped everything as required) and it was working. So I retried flashing the Temasek's rom and it booted this time, only thing is that my touch screen was not responding. The capacitive buttons are working also the touch screen is showing everything but not responding to anything. I searched a little bit, and it might be possible that my digitizer is broken which I hope is not since I am in a different country and it will be a pain to do it here. Also I read that if you tried to install Note 2 kernel/rom this might happen but I know that temasek's rom is definitely for s3 so it shouldnt be the case for me. Any help would be appreciated.
Click to expand...
Click to collapse
have you changed your recovery?
if you flash now another rom or restore your old one does the screen still not work?
Darkened_Sky said:
have you changed your recovery?
if you flash now another rom or restore your old one does the screen still not work?
Click to expand...
Click to collapse
I tried with both stock and temasek once again and the touch screen still does not respond. I always used cwm for recovery though, and did a factory reset on the stock recovery once to see if that works. I can flash ultima as well I suppose but I am not sure if that will fix it.
Edit: I tried to flash ultima but the installation steps required the use of touch screen so I could not proceed.
Are you sure that you download Temasek's rom for I9300 not for another model? Because Temasek supports more devices.
And on Temasek's thread I didn't find any user complaining about touch screen issue after installing it,so I think that you flashed it for different model.
Darrier said:
Hello everyone, I was using ultimarom till now and it worked like a charm. Today I thought hey lets upgrade to android 4.4 so I found temasek's rom and it seemed fine. After flashing the rom, it got stuck on boot screen. So I reflashed the stock rom (btw I wiped everything as required) and it was working. So I retried flashing the Temasek's rom and it booted this time, only thing is that my touch screen was not responding. The capacitive buttons are working also the touch screen is showing everything but not responding to anything. I searched a little bit, and it might be possible that my digitizer is broken which I hope is not since I am in a different country and it will be a pain to do it here. Also I read that if you tried to install Note 2 kernel/rom this might happen but I know that temasek's rom is definitely for s3 so it shouldnt be the case for me. Any help would be appreciated.
Thanks
Bektas
Click to expand...
Click to collapse
Flash back to stock with odin if problem is still there then it is hardware issue....
I rechecked and it is temasek for I9300. I restocked ofc with odin and it is no use tbh. I mean it is weird as the first time I flashed stock rom the touch screen was not working for 30 seconds or sth than it started working so I was really happy for a second.. After another flash it was not working and I was like yea it will work soon, but it didnt. I tried with loads of roms and kernels and it is still no use.
Any help? I have no idea how to fix this! I may have to send my phone for replacement which will be costly I suppose.. Any little tip will be appreciated.
Darrier said:
Any help? I have no idea how to fix this! I may have to send my phone for replacement which will be costly I suppose.. Any little tip will be appreciated.
Click to expand...
Click to collapse
Didn't u install the new version of Cwm? I'm using ultimarom v16 & I try to use Android v4.4.2... It seemed good to me
Sent from my GT-I9300 using Tapatalk
Solution
Hey dude, I couldnt find any solution to that problem. What I did was to send it in for replacement but with warranty. For that you need to triangle away your phone and also install the official firmwares. I had to use a mouse in order to do that but you will need a usb to micro usb converter, which is not that hard to find( and also cheap). They couldnt tell that I installed unofficial firmware, I replaced my screen flawlessly. You can find how to triangle away your phone in this forum and also sammobile is the place to look for official firmware.
Cheers
wanerza77 said:
Didn't u install the new version of Cwm? I'm using ultimarom v16 & I try to use Android v4.4.2... It seemed good to me
Sent from my GT-I9300 using Tapatalk
Click to expand...
Click to collapse
"Unroot" Galaxy alpha 850f failed.... looks like soft bricked... any solution?
So i've got a Galaxy Alpha 850F that has been rooted and custom romed (Resurrection remix 5.9 done with TWRP). Everything worked fine untill I tried to put back the stock rom on my device using Odin.
Everything seemed ok untill it fully loaded and optimized everything, but after that, the display shows nothing but the network signal bar and the battery percentage. if i try to shot it down the options show up, so it seems to be working but there nothing really on the display that i can interact with. Fortunetally I switched to a new phone before that, so there's no more data that is needed from my Alpha.
Any solution?
Use odin again, if not working try to use a pit file. You can f*** up everything though, be careful. But i would try to download a new rom again with another Region
Gesendet von iPhone mit Tapatalk
XxpikaachuuxX said:
Use odin again, if not working try to use a pit file. You can f*** up everything though, be careful. But i would try to download a new rom again with another Region
Gesendet von iPhone mit Tapatalk
Click to expand...
Click to collapse
Flashing another rom from another region was my 2. option too, hopefully it will work .
What's a pit file btw?
It rewrites every partition of the phone. Ill link you a guide so you can read a bit before doing the pit flash: http://forum.xda-developers.com/galaxy-s2/general/guide-t2345831
Is for the S2 but procedure is same. Just get the right files though.
Cheers
Gesendet von iPhone mit Tapatalk
Thank you!
Reflashing helped, it's working so far... hopefully it'll stay this way.
XxpikaachuuxX said:
Use odin again, if not working try to use a pit file. You can f*** up everything though, be careful. But i would try to download a new rom again with another Region
Gesendet von iPhone mit Tapatalk
Click to expand...
Click to collapse