Hi guys,
As title says, I just lost my lock screen after flashing the official jb. After made few tests and feedback from various people, here what I've done to solve my problem. I just want to share with everyone. So I'm making this guide as noob as I can.
All this done from terminal apps (download from play store) and yes, rooted phone is mandatory. Type in to terminal emulator everything I wrote below (each line mean new command, press enter to execute):
su
cp /efs/imei/keystr /efs/imei/keystr.bak
echo ON >> /efs/imei/keystr
chmod 0744 /efs/imei/keystr
chown 1000.1000 /efs/imei/keystr
reboot
p/s: you might received an error after entered cp command because you don't have any keystr file, so just ignore it. If no error, mean you just created backup file of keystr named keystr.bak, you can restore it later by using this command:
mv /efs/imei/keystr.bak /efs/imei/keystr
kunterk said:
Hi guys,
As title says, I just lost my lock screen after flashing the official jb. Below are the details:
1) using cm10.1
2) full wipe (using full wipe script zip as downloaded from apriliam3)
3) installed official jb from odin
> at this point, I started to lose my lock screen
4) afraid of this bug came from cm10.1, I tried to flash wanam leaked jb, and the lock screen just fine.
5) So after waiting for wanam to release his v14, I flashed again and the bug say hi again to me.
Got pissed off, I even try to use so many type of wipe, from philz to nukewipe.
Yes, I can get my lock screen from any other rom except from this official jb based.
Hope someone can answer this or at least give me some idea.
p/s: sorry to mentioned name above, I love your work, but I can't post directly to your thread as I don't have enough privilege to post there.
p/ss:sorry for my bad English
Cheers.
Sent from my GT-I9100 using xda app-developers app
Click to expand...
Click to collapse
What you mean you lost your lockscreen?
And by Official JB you mean Stock Official 4.1.2?
Re: Official JB - Lock screen not working
gastonw said:
What you mean you lost your lockscreen?
And by Official JB you mean Stock Official 4.1.2?
Click to expand...
Click to collapse
I'm unable to lock my screen. I've used stock official LS8, wanam LS8 based and neat LS8. Seems the problem just with LS8 but not with LSJ
Sent from my GT-I9100 using xda app-developers app
kunterk said:
I'm unable to lock my screen. I've used stock official LS8, wanam LS8 based and neat LS8. Seems the problem just with LS8 but not with LSJ
Sent from my GT-I9100 using xda app-developers app
Click to expand...
Click to collapse
Did you check the lock screen settings?
If so, flash stock 4.1.2 (now that is hot).
Oh....you already been there. That's not a bug, no bug can be present in 3 diffrent roms.
Re-flash, wipe all data & see if it pops up again.
Latest result
gastonw said:
Did you check the lock screen settings?
If so, flash stock 4.1.2 (now that is hot).
Oh....you already been there. That's not a bug, no bug can be present in 3 diffrent roms.
Re-flash, wipe all data & see if it pops up again.
Click to expand...
Click to collapse
yeah, i think so, maybe it's my device. just now i re-flashed LSJ(oxx) with PIT, yes, i re-partitioned and re-formatted my internal-sd as well, booted and everything working fine. so i decided to give one more chance to LS8(oxx) and the result as expected. now, again, reverting back to LSJ and not planning to install LS8 yet.
here the new thing that i found out when i'm using LS8,
- my power button act weird, it's not just can't lock the screen, but even mid-long press will directly reboot my device(suppose power menu will come out right?)
btw thanks man.
Re: Official JB - Lock screen not working
np man.
just so we're clear.....you get your lockscreen in jb leak? not in ls8....am I right?
Keep away from that spanish ROM then.
Man..I too am thinking about going back to leakland...no media scanner there
Sent from the little guy
Re: Official JB - Lock screen not working
Yeah, just finished setting up my leaky rom.
Everything working fine now. So, from my made up theory, the Europe rom might not works well with my Asia device (lsj is global build). Maybe I should give a shot for China rom or I'll just wait for Singapore rom.
Sent from my GT-I9100 using xda app-developers app
Re: Official JB - Lock screen not working
what you got there? i9100g?
Sent from the little guy
Re: Official JB - Lock screen not working
gastonw said:
what you got there? i9100g?
Sent from the little guy
Click to expand...
Click to collapse
Nope, I9100.
Sent from my GT-I9100 using xda app-developers app
kunterk said:
Nope, I9100.
Sent from my GT-I9100 using xda app-developers app
Click to expand...
Click to collapse
After flashing the stock rom in ODIN go back into download mode and flash Siyah v6 beta4, boot into recovery and then do a wipe data/factory reset. This should fix the lock screen issue.
If not just flash latest Wannam rom, Its better then stock sammy anyway.
Re: Official JB - Lock screen not working
TheATHEiST said:
After flashing the stock rom in ODIN go back into download mode and flash Siyah v6 beta4, boot into recovery and then do a wipe data/factory reset. This should fix the lock screen issue.
If not just flash latest Wannam rom, Its better then stock sammy anyway.
Click to expand...
Click to collapse
Thanks mate, but I've done exactly as what you suggested and just they don't work with my phone.
p/s: Actually I don't really mind now. Switched back to Samsung 4.1 just because of it's most "workable" mail app, splanner and I love the Samsung keyboard with swipe function which has multi languages support.
Sent from my GT-I9100 using xda app-developers app
see this : http://forum.xda-developers.com/showthread.php?t=1611796
P.S MAKE A BACKUP!
I had some problem on stock 4.0.4
This worked
Re: Official JB - Lock screen not working
Qwerty123 \m/ said:
see this : http://forum.xda-developers.com/showthread.php?t=1611796
P.S MAKE A BACKUP!
I had some problem on stock 4.0.4
This worked
Click to expand...
Click to collapse
Something new for me to try. Excited mode activated. LOL
Sent from my GT-I9100 using xda app-developers app
solved
Qwerty123 \m/ said:
see this : http://forum.xda-developers.com/showthread.php?t=1611796
P.S MAKE A BACKUP!
I had some problem on stock 4.0.4
This worked
Click to expand...
Click to collapse
:good: so many thanks for your hint. after reading linked post, i did some search for /efs of i9100 device and got the correct path:
# /efs/imei/keystr
Same issue !
kunterk said:
yeah, i think so, maybe it's my device. just now i re-flashed LSJ(oxx) with PIT, yes, i re-partitioned and re-formatted my internal-sd as well, booted and everything working fine. so i decided to give one more chance to LS8(oxx) and the result as expected. now, again, reverting back to LSJ and not planning to install LS8 yet.
here the new thing that i found out when i'm using LS8,
- my power button act weird, it's not just can't lock the screen, but even mid-long press will directly reboot my device(suppose power menu will come out right?)
btw thanks man.
Click to expand...
Click to collapse
I face same issue as described above. No lock and pressing power key for long gives reboot. I just flashed official LS8 using Odin 1 day back. I had same problem with 4.0.3. In addition to that, FM Radio doesn't pick up any station. Applications resets to default doesn't reset. Thank you.
---------- Post added at 11:31 PM ---------- Previous post was at 11:19 PM ----------
kunterk said:
:good: so many thanks for your hint. after reading linked post, i did some search for /efs of i9100 device and got the correct path:
# /efs/imei/keystr
Click to expand...
Click to collapse
I am noob here. Learning from this forum. I shall be very thankful if could spare few minutes and help me with steps you have taken to resolve the issue. Thank you.
Help please !
kunterk said:
Hi guys,
As title says, I just lost my lock screen after flashing the official jb. Below are the details:
1) using cm10.1
2) full wipe (using full wipe script zip as downloaded from apriliam3)
3) installed official jb from odin
> at this point, I started to lose my lock screen
4) afraid of this bug came from cm10.1, I tried to flash wanam leaked jb, and the lock screen just fine.
5) So after waiting for wanam to release his v14, I flashed again and the bug say hi again to me.
Got pissed off, I even try to use so many type of wipe, from philz to nukewipe.
Yes, I can get my lock screen from any other rom except from this official jb based.
Hope someone can answer this or at least give me some idea.
p/s: sorry to mentioned name above, I love your work, but I can't post directly to your thread as I don't have enough privilege to post there.
p/ss:sorry for my bad English
Cheers.
Sent from my GT-I9100 using xda app-developers app
edit:
i will write down as simple as i can on how to fix this issue. first of all, u will need a rooted rom / kernel. in my case, i've flashed this wipe script, wanamlite v14, dorimanx kernel and installed terminal (from PlayStore)
my steps:
open terminal and login as root: $ su
go to /efs/imei/ folder: # cd /efs/imei
check if keystr file exist: # ls
if you can see keystr listed, just remove it: # rm keystr or...
if you can't see it, just create new keystr file: # touch keystr
edit your keystr: # vi keystr
in vi editor, prees "i" and type "ON" without quote and save it by pressing "Volume Up + E" and type in ":wq!" without quote and yes, with colon
now just reboot by type in terminal : # reboot
much easier method that i can think so far(i don't use this method as i'm too lazy to install root explorer):
install root explorer (from Play Store)
go to root folder "/" and find efs >> imei
when you in there, if you find keystr file, just delete it and make new file by pressing + icon (as far as i remember)
then click the file and choose edit. use your favourite text editor. type in ON and save
reboot your phone
and now, you are good to go and play with your power button all night...:silly:
Click to expand...
Click to collapse
I face the same issue as yours. I am a newbie and hence I chose second method as you've suggested. I have installed MI Root Explorer. I could find efs but cant find imei. It says either the folder has no data or I dont have access. Thank you.
keyur1401 said:
I face the same issue as yours. I am a newbie and hence I chose second method as you've suggested. I have installed MI Root Explorer. I could find efs but cant find imei. It says either the folder has no data or I dont have access. Thank you.
Click to expand...
Click to collapse
Is your phone rooted? If yes, try open supersu for first time for it dowload su binaries then open your root browser again.
edit: saw u posted asking bout fm radio. I never get it working since the first day I bought this phone and I don't think it will. The application reset not working? Have you tried to reset from cwm?
Sent from my GT-I9100 using xda app-developers app
kunterk said:
Is your phone rooted? If yes, try open supersu for first time for it dowload su binaries then open your root browser again.
edit: saw u posted asking bout fm radio. I never get it working since the first day I bought this phone and I don't think it will. The application reset not working? Have you tried to reset from cwm?
Sent from my GT-I9100 using xda app-developers app
Click to expand...
Click to collapse
Thanks for the reply. No, my phone is not rooted. I shall do it using Siyah-s2-v60b4.tar. Then I shall follow your advise. Hope this works. Thank you.
Further help !
keyur1401 said:
Thanks for the reply. No, my phone is not rooted. I shall do it using Siyah-s2-v60b4.tar. Then I shall follow your advise. Hope this works. Thank you.
Click to expand...
Click to collapse
I have rooted my phone and I could see three apps SuperSU, CWM and STweaks. The SuerSU hasn't downloaded the binaries. What should I do next ? Thanks in advance.
---------- Post added 28th January 2013 at 12:04 AM ---------- Previous post was 27th January 2013 at 11:18 PM ----------
kunterk said:
Hi guys,
As title says, I just lost my lock screen after flashing the official jb. Below are the details:
1) using cm10.1
2) full wipe (using full wipe script zip as downloaded from apriliam3)
3) installed official jb from odin
> at this point, I started to lose my lock screen
4) afraid of this bug came from cm10.1, I tried to flash wanam leaked jb, and the lock screen just fine.
5) So after waiting for wanam to release his v14, I flashed again and the bug say hi again to me.
Got pissed off, I even try to use so many type of wipe, from philz to nukewipe.
Yes, I can get my lock screen from any other rom except from this official jb based.
Hope someone can answer this or at least give me some idea.
p/s: sorry to mentioned name above, I love your work, but I can't post directly to your thread as I don't have enough privilege to post there.
p/ss:sorry for my bad English
Cheers.
Sent from my GT-I9100 using xda app-developers app
edit:
i will write down as simple as i can on how to fix this issue. first of all, u will need a rooted rom / kernel. in my case, i've flashed this wipe script, wanamlite v14, dorimanx kernel and installed terminal (from PlayStore)
my steps:
open terminal and login as root: $ su
go to /efs/imei/ folder: # cd /efs/imei
check if keystr file exist: # ls
if you can see keystr listed, just remove it: # rm keystr or...
if you can't see it, just create new keystr file: # touch keystr
edit your keystr: # vi keystr
in vi editor, prees "i" and type "ON" without quote and save it by pressing "Volume Up + E" and type in ":wq!" without quote and yes, with colon
now just reboot by type in terminal : # reboot
much easier method that i can think so far(i don't use this method as i'm too lazy to install root explorer):
install root explorer (from Play Store)
go to root folder "/" and find efs >> imei
when you in there, if you find keystr file, just delete it and make new file by pressing + icon (as far as i remember)
then click the file and choose edit. use your favourite text editor. type in ON and save
reboot your phone
and now, you are good to go and play with your power button all night...:silly:
Click to expand...
Click to collapse
Dear Friend, I've reached there almost but the vi command not found. I have rooted my phone, added a terminal and done everything as you have directed. Any help, please ? Thanks in advance.
keyur1401 said:
I have rooted my phone and I could see three apps SuperSU, CWM and STweaks. The SuerSU hasn't downloaded the binaries. What should I do next ? Thanks in advance.
---------- Post added 28th January 2013 at 12:04 AM ---------- Previous post was 27th January 2013 at 11:18 PM ----------
Dear Friend, I've reached there almost but the vi command not found. I have rooted my phone, added a terminal and done everything as you have directed. Any help, please ? Thanks in advance.
Click to expand...
Click to collapse
Suppose the vi is the most basic text editor. You also can use echo as replacement. Eg. echo ON >> /efs/imei/keystr
Additional, you can set this too, just to make sure system can use it properly:
chmod 0744 /efs/imei/keystr
chown 1000.1000 /efs/imei/keystr
Do this to factorymode as well. Hope this solve yours.
Sent from my GT-I9100 using xda app-developers app
Related
Hello, sorry for the title error (2.3.6).
This is the way to restore your Nexus One to 100% stock Android 2.3.6, waiting ICS Android 4 official OTA updates (if there will be one).
This rom contains:
hboot
radio
recovery
system ...
(all things return stock except the unlocked bootloader but it isn't a problem)
Thank to Football for the rom e to the XDA wiki for the guide. I decided to create this thread for who is in truble (as me some days ago) and for who wants to return stock before the possible relasing of ICS. Before everything backup your data (and sd card for security) and from custom recovery do:
-wipe battery stats (if you want)
-wipe data and cache
-wipe dalvik cache
Now:
1)Download the shipped rom GRK39F from PASSIMG_Passion_Google_WWE_3.13.1700.1_GRK39F_relase_signed.zip
2)Rename the downloaded ZIP file to PASSIMG.ZIP.
3)Transfer the provided PASSIMG.ZIP file to the root of your SD card.
4)Power down your phone.
5)Hold down the Volume Down button as you power your phone back on.
6)A screen should appear showing your phone's system searching for various files. This will take up to 2 minutes.
7)The phone will ask you if you want to start the update. Press the Volume Up button to start the update.
8)If you followed these steps correctly - congratulations, you are now on stock 2.3.6 ROM.
MD5: 3052bd01807a6a757330523498148cc9
SHA1: bb8a7b616f22630407302655d4d4d491b16f55fb
I'm not responsible if you do some mistakes.
Please give me thanks that if it was helpful for you
Hallo. I've been looking for this instruction. Thank you. BTW your signature shows that you own Nexus S, not Nexus One. Are you sure the instruction you wrote is for Nexus One?
Yes i had also a nexus one this guide works perfectly for me...i took this from XDA wiki and i updated the latest build
Sent from my Nexus S using Tapatalk
Thank you man, but I wonder if Google would give 4.0 to us Nexus One users...
Thanks a lot, the most recent stock ROM in the FAQ was FRF91.
Edit: The file hosting you link to says it can't find the file (AFTER the stupid wait 60 seconds ) Would you mind re-uploading this to a more reputable file host?
Yes this afternoon i'll upload it on dropbox
Sent from my Nexus S using Tapatalk
ale.landra91 said:
Yes this afternoon i'll upload it on dropbox
Sent from my Nexus S using Tapatalk
Click to expand...
Click to collapse
I updated the link! Download it!
ale.landra91 said:
I updated the link! Download it!
Click to expand...
Click to collapse
Excellent, I got it! Thanks!
Dumb question, but there's no reason I can't just flash this in Amon-Ra or CW, is there? Your instructions are for stock recovery, but as far as I know it should work in any recovery, shouldn't it? (Obviously stock recovery will be flashed on reboot with a stock ROM, I know that.)
you can't flash it by stock recovery or custom recovery. This is not a custom or stock rom...it is a shipped image (in fact you have to name it not in "update" but in "passimg"). You don't have to enter in any recovery...while you boot in the bootloader all is automatic without using recovery! i don't know if im clear, i don't speak english very well
ale.landra91 said:
5)Hold down the Volume Down button as you power your phone back on.
6)A screen should appear showing your phone's system searching for various files. This will take up to 2 minutes.
7)The phone will ask you if you want to start the update. Press the Volume Up button to start the update.
Click to expand...
Click to collapse
No recovery request in the passage
Your English is fine I forgot that the bootloader handles the updates, not the recovery (which is why the name has to be specific, it looks for that file in the boot sequence). Answers my real question, anyway, which was whether I'd need to revert to stock recovery to apply it (I don't).
Thank you for your help.
No you don't have to...this method works for every rom and recovery
Sent from my Nexus S using Tapatalk
Hi , could you put a mirror download link .thanks in advance
Nexus74 said:
Hi , could you put a mirror download link .thanks in advance
Click to expand...
Click to collapse
Sorry but if you click "here" the download starts automatically...i can't upload it to another host site...if you upload it to another site after downlading please give me the link and i'll add it
thank you
I think ur ROM have some problem while u had uploaded
would u please check one again!
many thank
Didn't work
I followed thee steps you suggested. But after it scanned the SD card it didn't ask for anything.It just sat there at the bootloader screen. I'm using CM7.1 right, don't know if that affects anything.
No it is not a problem cm7 ...i Think that you should do this passage if you are using windows:
1) rename in PASSIMG (without .zip)
2) copy it in the root of SD card (not in a folder)
this should be the solution
Sent from my Nexus S using Tapatalk
ale.landra91 said:
No it is not a problem cm7 ...i Think that you should do this passage if you are using windows:
1) rename in PASSIMG (without .zip)
2) copy it in the root of SD card (not in a folder)
this should be the solution
Sent from my Nexus S using Tapatalk
Click to expand...
Click to collapse
Hey
yea that's what I did. But I didn't clear cache and data via recovery beforehand. Could that be the reason?
I think not....but for a good use of stock ROM you have to clear everything. If the file is complete downloaded and named correctly the bootloader has to recognize it. Sorry
Sent from my Nexus S using Tapatalk
Hey
I think the zip file has an issue. It said something while searching for files in the bootloader. Can you reupload maybe?
Sent from my Nexus One using XDA App
Hello, I have a problem, I hope you can help a user,
To start updating the device and everything works perfect except that the phone is not locked for more than press the button.
Specific, I pressed the button, and the screen turns off, but if you press it again, the screen lights up but not in the blocking state, if not, on the desktop or wherever you leave the phone before (well either the browser, whatsapp, any game or whatever).
I tried changing the slide lock pattern, the password, and all, nothing works.
By having this problem, what ice was reinstall rom (including all wipes, and other steps) and nothing has changed. I've also tried installing a lower version of android (4.0.3 to be exact) to beams of odin, even in that version still does not work the screen lock ....
Since we no longer know what to do, I turn to you xD
PD:
I've noticed that others further back than indicated, the power button has lost the function that you had to if you were you kept pressed for a few seconds a menu will appear with options (off, airplane mode, reboot and some more) well now I see that menu, the phone goes directly.
Sorry about all this, but I need urgent help TT
Sorry for my bad English
And sorry again if I'm wrong in the place where I write this
Re: [Q] Power botton Isues
Try flashing JB leak.
My bet is you'll get your lockscreen back.
Sent from the little guy
gastonw said:
Try flashing JB leak.
My bet is you'll get your lockscreen back.
Sent from the little guy
Click to expand...
Click to collapse
Could you tell me more specifically is that by JB leak ... I think that is the one I have, if I indicases of where I can get the files would greatly appreciate it ^^
Re: [Q] Power botton Isues
Right over here:
http://www.sammobile.com/2012/11/15/i9100xxlsj-–-galaxy-s-ii-android-4-1-2-jelly-bean-test-firmware/
Sent from the little guy
gastonw said:
Right over here:
(Link)
Sent from the little guy
Click to expand...
Click to collapse
Thank you very much for your help, in about 1 hour has finished downloading (Hotfile is very slow xD), hope it works
this is installed by odin, or recovery? (I think odin, but better ensure xD)
Re: [Q] Power botton Isues
odin / mobile odin
Check Q&A, there's a thread about hotfile not working, some guy posted a premium account generator. something like leecherexpress.com/hotfile or similar.
Sent from the little guy
gastonw said:
odin / mobile odin
Check Q&A, there's a thread about hotfile not working, some guy posted a premium account generator. something like leecherexpress.com/hotfile or similar.
Sent from the little guy
Click to expand...
Click to collapse
Hi, I have to tell you two stories.
The good is that doing what you've told me, everything works fine (at least for now)
The bad news is that if you then install the official version and not the leak, I lose everything .... and what bothers me most of the leak is a bug that has to do that sometimes when you unlock the phone, takes time to answer the screen .... xD
But still, many thanks!
Ziddent said:
Hi, I have to tell you two stories.
The good is that doing what you've told me, everything works fine (at least for now)
The bad news is that if you then install the official version and not the leak, I lose everything .... and what bothers me most of the leak is a bug that has to do that sometimes when you unlock the phone, takes time to answer the screen .... xD
But still, many thanks!
Click to expand...
Click to collapse
Yep, I'm good at bets.
I don't know why after flashing LS8 some get no lockscreens, it's weird. JB leak works all the time tho, wich weirder.
I would flash LS8 via Mobile Odin, no wipes. Just to see if it gets fixed.
This is often caused but a problem in EFS in the /efs/imei/keystr file it can be permissions or the fact that the file does not exist with ON in it
If the file does not exist use root explorer to make sure /efs/imei/keystr has the work on in it and premissions are rw-rw-r--
or terminal emulator to
su
echo -n ON > /efs/imei/keystr
chmod 644 /efs/imei/keystr
reboot
Re: [Q] Power botton Isues
Plod72 said:
This is often caused but a problem in EFS in the /efs/imei/keystr file it can be permissions or the fact that the file does not exist with ON in it
If the file does not exist use root explorer to make sure /efs/imei/keystr has the work on in it and premissions are rw-rw-r--
or terminal emulator to
su
echo -n ON > /efs/imei/keystr
chmod 644 /efs/imei/keystr
reboot
Click to expand...
Click to collapse
This is why I don't know
Sent from the little guy
gastonw said:
Yep, I'm good at bets.
I don't know why after flashing LS8 some get no lockscreens, it's weird. JB leak works all the time tho, wich weirder.
I would flash LS8 via Mobile Odin, no wipes. Just to see if it gets fixed.
Click to expand...
Click to collapse
try what You told me, but I have not worked, yet I appreciate the help ^ ^
Plod72 said:
This is often caused but a problem in EFS in the /efs/imei/keystr file it can be permissions or the fact that the file does not exist with ON in it
If the file does not exist use root explorer to make sure /efs/imei/keystr has the work on in it and premissions are rw-rw-r--
or terminal emulator to
su
echo -n ON > /efs/imei/keystr
chmod 644 /efs/imei/keystr
reboot
Click to expand...
Click to collapse
This really worked for me, but not on the first try, on the first try, I corrupted the IMEI, restore it with a copy of the efs folder, and went back to try, this time if it worked xD
Thank you very much for the help.
I have to mark the post in some way so that people know that this solved or not necessary? If yes, how should mark it?
Ziddent said:
try what You told me, but I have not worked, yet I appreciate the help ^ ^
This really worked for me, but not on the first try, on the first try, I corrupted the IMEI, restore it with a copy of the efs folder, and went back to try, this time if it worked xD
Thank you very much for the help.
I have to mark the post in some way so that people know that this solved or not necessary? If yes, how should mark it?
Click to expand...
Click to collapse
Glad you pulled it off.
You can rename the thread with a (SOLVED) instead of the [Q].
Hi,
Without really giving it a second thought I went and encrypted my device. I didn't think I'd be stuck with this rom and/or that CWM would become worthless.
I made plans on selling this one to buy SGS4 instead, when it hits the market and I wanted to do an as proper sale ad possible.
I need help decrypting the device and if possible unroot it and installing the original TouchWiz. I'd be saticfied with a rooted device, as well, only with the original "rom".
Any help is appreciated!
AW: Sticky situation!
Hi.
I guess download mode still works.
Do shouldn't it be sufficient to flash a stock rom there?
I never did this but my guess is it will work.
Regards.
Sent from my GT-I9300 using xda app-developers app
Thanks for the quick reply, this sounds easy!
Can someone back this info up?
Also, where can I download the rom? samsung.com?
Re: Sticky situation!
Hey
He is right..
You can download it from sammobile.com/firmwares or you can google it..prefer the firmware for where you stay..
That ways you'll remove the root and also factory reset your phone..
Sent from my GT-I9300 using xda app-developers app
pingaan said:
Thanks for the quick reply, this sounds easy!
Can someone back this info up?
Also, where can I download the rom? samsung.com?
Click to expand...
Click to collapse
If you can reach download mode (shutdown phone then power + home + volume down) it should be fine.
Just ensure you're flashing the correct ROM.
Like tchindalia suggested. Find your Rom here.
Regards
PS: To leave download mode hold the power button for quite some time.
Which one should I pick? I mean there are none from EU, or it me just being blind?
pingaan said:
Which one should I pick? I mean there are none from EU, or it me just being blind?
Click to expand...
Click to collapse
Make sure you select the GT-I9300 and not GT-I9300T
Oh right.. And now it's narrowed down to two alternatives! Does it matter which one of the Swedish ones I choose? VDS or HTS?
AW: Sticky situation!
In general it doesn't matter.
It's just a question of Bloatware.
Think about the CSC as android+carrier-ware.
If you have a backup of your esf partition there is a small file with your device csc.
Regards.
Sent from my GT-I9300 using xda app-developers app
Re: Sticky situation!
Settings/security/decrypt phone... It is as easy as it is written
Enviado desde mi GT-I9300 usando Tapatalk 2
worf_1977 said:
Settings/security/decrypt phone... It is as easy as it is written
Enviado desde mi GT-I9300 usando Tapatalk 2
Click to expand...
Click to collapse
Have you ever tried encrypting? There's no such thing as a decrypt option..
Anyway, the reason why I still haven't marked this thread as solved is that I still haven't tried it out yet! :-|
I will, soon!
Thanks alot for all the helpful posts.
Re: Sticky situation!
I encrypted my S3 and decrypted it under settings... Took me lots of time to realize that encrypt option becomes decrypt one there
Enviado desde mi GT-I9300 usando Tapatalk 2
I suppose you ran some other rom than CM then, because the option stays the same.
Re: Sticky situation!
pingaan said:
I suppose you ran some other rom than CM then, because the option stays the same.
Click to expand...
Click to collapse
In fact under stock JB decrypt option is enabled. Once the phone is ,of course, encrypted
Enviado desde mi GT-I9300 usando Tapatalk 2
Help here please, badly needed
hi Everyone,
Im using S3 I9300 rooted with stock rom
I was going through this post (http://forum.xda-developers.com/show....php?t=1772234) where it showed how to swipe ur sd card as internal memory and vice virsa but required a kernel with int.l something which I dint have .
In order to follow the instructions I downloaded the file; MVLALH1_Insecure_kernel_CWM and flashed it on my phone. then I downloaded the file from the post (extsd2internalsd2_mattiadj_and_infx_6) and flashed it through CMW but my phone dint read my SD card as internal memory so I read more
EXTRACT FROM THE POST:
THE GUIDE
First of all make a nandroid backup!! I'm not responsable for any problem! You make this procedure at your risk!!!1. Format external sd card from your pc as fat32 or extfat
2. Copy attached zip in you external sd. Choose the right zip. If you have formatted your sd as fat32 choose _fat32 version, if the filesystem is extfat choose _extfat version
3. Go into recovery
4. Flash the zip
5. Reboot and....enjoy your memory increase!!!!
I'm on official jelly bean with kernel with init.d support but the mod seems not working or my kernel/rom does not support init.d
1. Flash the mod
2.Install script manager from play store https://play.google.com/store/apps/d...51bGwsMSwyLDNd
3.Open script manager, click on browse as root then ok
4.Choose the file name 11extsd2internalsd located in /system/etc/init.d and click on Script/Executable
5.Now tap on Su, Boot and Save
6.Reboot your phone and enjoy!
[/COLOR]
So I went on the second paragraph of instructions and downloaded the script manager and went to the 11extsd2internalsd file. I was told to select the option script/executable but couldn't find any option having both so selected executable and then selected SU and BOOT and then restarted my phone
Now Im not sure when it happened but my S3 is not detecting my sim card thou my sim is working perfectly and I have no clue how to fix it
please can anyone help me I tried to explain as best I could but still please ask if u want to know more cuz right now my s3 is without sim card
xenonr said:
If you can reach download mode (shutdown phone then power + home + volume down) it should be fine.
Just ensure you're flashing the correct ROM.
Like tchindalia suggested. Find your Rom here.
Regards
PS: To leave download mode hold the power button for quite some time.
Click to expand...
Click to collapse
I did this some months ago - It worked for me so it might as well work for you! Good luck!
tchindalia said:
Hey
He is right..
You can download it from sammobile.com/firmwares or you can google it..prefer the firmware for where you stay..
That ways you'll remove the root and also factory reset your phone..
Sent from my GT-I9300 using xda app-developers app
Click to expand...
Click to collapse
Did what you guys suggested yesterday but what you said wasn't entirely true. Flashing the stock firmware from download mode worked fine, but it actually just put me in an even more sticky situation.
My current situation: device still rooted and still encrypted, only difference is that it won't acceptt my old encryption password. In other words; I can't use the phone at all.
Any ideas to this problem? Is it possible to clear the internal memory and start from scratch perhaps?
Cheers.
pingaan said:
Did what you guys suggested yesterday but what you said wasn't entirely true. Flashing the stock firmware from download mode worked fine, but it actually just put me in an even more sticky situation.
My current situation: device still rooted and still encrypted, only difference is that it won't acceptt my old encryption password. In other words; I can't use the phone at all.
Any ideas to this problem? Is it possible to clear the internal memory and start from scratch perhaps?
Cheers.
Click to expand...
Click to collapse
Did you factory reset after the flash?
I didn't... I suppose it's fine with the usual reset in CWM?
pingaan said:
I didn't... I suppose it's fine with the usual reset in CWM?
Click to expand...
Click to collapse
Well if you are on stock it will be 3e recovery and a factory reset will wipe data AND sd card(internal) just so you are aware
I can;t seem to find a guide to install the right ClockworkMod so I can install Jelly Bean. Is there any guides on hbow to install a recovery and Jelly Bean from stock GB Touchwiz? (btw it is a YP-G1).
Thanks!
rosser725 said:
I can;t seem to find a guide to install the right ClockworkMod so I can install Jelly Bean. Is there any guides on hbow to install a recovery and Jelly Bean from stock GB Touchwiz? (btw it is a YP-G1).
Thanks!
Click to expand...
Click to collapse
Just flash the Terrasilent Kernel with Odin to get CWM. That's the recommended starting point for installing CM10 anyway.
Remember to do all your backups (including and -----> **ESPECIALLY** <------ your EFS.rfs) first because when you flash the new ROM you'll want to clear your Dalvik cache and reset to factory settings, which would wipe all of the data on the device.
Once you've installed Terrasilent, press the power button and volume up at the same time to get into CWM.
I don't have my EFS.. I can't figure out how to get it back. I don't have a lock screen or a power menu.
rosser725 said:
I don't have my EFS.. I can't figure out how to get it back. I don't have a lock screen or a power menu.
Click to expand...
Click to collapse
Well, in any case, flash Terrasilent for CWM and then use that to upgrade to Jellybean.
In the future though, remember to backup your EFS before you flash a new ROM. You can't get it back once you've lost it, and faking one doesn't always work right.
F22Rapture said:
Remember to do all your backups (including and -----> **ESPECIALLY** <------ your EFS.rfs) first[...]
Click to expand...
Click to collapse
This, so much.
http://forum.xda-developers.com/showthread.php?t=1632376
It takes all of five minutes(if you have ADB set up) and I cannot recommend it highly enough.
Guys we don't even know if he has his efs so why bother flashing terrasilent? Hmm do you have a efs backup laying somewhere on your /sdcard like efs.tar? Maybe you can get your efs if you have this.
Sent from my Nexus 7 using Tapatalk HD
I don't have an efs backup. A friend gave this to me because he bricked it, but I unbricked it with Heimdall and there's no lockscreen or power menu, and I heard about this problem back when I had my Infuse 4G but I never ran into it.
rosser725 said:
I don't have an efs backup. A friend gave this to me because he bricked it, but I unbricked it with Heimdall and there's no lockscreen or power menu, and I heard about this problem back when I had my Infuse 4G but I never ran into it.
Click to expand...
Click to collapse
Well, if you're absolutely sure there isn't one, go ahead with Terrasilent I suppose.
Zac, since you're here I had some questions for you:
1. I noticed that in the CM9 thread you said the gapps package needs to check for the EFS folder, but the CM10 gapps post didn't mention it. Is it still necessary?
2. Do I need to clear the user data when switching between builds of the same ROM, or only between major versions (ie. CM9->CM10)?
3. I noticed that "Cell Standby" is sucking up quite a bit of battery life (latest CM10 build). Is this something we can fix (or workaround), or is the problem "upstream?"
Thanks for all the work you and bbelos (and others) have put in over the past few months. It's really great to see it all paying off so well.
rosser725 said:
I don't have an efs backup. A friend gave this to me because he bricked it, but I unbricked it with Heimdall and there's no lockscreen or power menu, and I heard about this problem back when I had my Infuse 4G but I never ran into it.
Click to expand...
Click to collapse
Hmm you could ask for somebody to make a dummy efs with the necessary information to get CM9/CM10 flashed into your device
F22Rapture said:
Well, if you're absolutely sure there isn't one, go ahead with Terrasilent I suppose.
Zac, since you're here I had some questions for you:
1. I noticed that in the CM9 thread you said the gapps package needs to check for the EFS folder, but the CM10 gapps post didn't mention it. Is it still necessary?
2. Do I need to clear the user data when switching between builds of the same ROM, or only between major versions (ie. CM9->CM10)?
3. I noticed that "Cell Standby" is sucking up quite a bit of battery life (latest CM10 build). Is this something we can fix (or workaround), or is the problem "upstream?"
Thanks for all the work you and bbelos (and others) have put in over the past few months. It's really great to see it all paying off so well.
Click to expand...
Click to collapse
1. It's not the gapps that checks the efs folder, it's the zip installer script
2. It's not mandatory but if you experience problems, it's recommended to do so
3. As I've already said in the FAQ, it wont change anything because the device don't have any antenna or anything cell related. The battery won't even be touched.
Would anybody here be able to do that for me?
Sent from my YP-G1 using xda app-developers app
Bump
rosser725 said:
Would anybody here be able to do that for me?
Sent from my YP-G1 using xda app-developers app
Click to expand...
Click to collapse
do you have a us or intl device
rosser725 said:
I can;t seem to find a guide to install the right ClockworkMod so I can install Jelly Bean. Is there any guides on hbow to install a recovery and Jelly Bean from stock GB Touchwiz? (btw it is a YP-G1).
Thanks!
Click to expand...
Click to collapse
If you have the INTL version, you have to download Kernel r14 (Odin):
http://forum.xda-developers.com/showthread.php?t=1414565
Now, the Odin program:
http://forum.xda-developers.com/showthread.php?t=2189539
1->Shut down your mobile.
2->Start Odin 3 (for example).
3->Connect the galaxy player with USB while pressing the volume down button.
4->Now, Odin will have to say that it's connected to your mobile. Then press on PDA and charge the YP-G70-Kernel-r14.tar
5->Tick ONLY Auto Reboot and F. Reset Time.
6->Pres Start and it will flash your Kernel.
7->Start your galaxy player while pressing volume up and home button. That's all! You will be in CWM recovery!
For US galaxy player, it's pretty the same, but the kernel is here: http://forum.xda-developers.com/showthread.php?t=1445840 (Download the .tar version! If not you'll be nothing with Odin )
Ooww... If it's a YP-G1 I don't know... Sure is the same but you've to find the adient kernel...
txordi said:
Ooww... If it's a YP-G1 I don't know... Sure is the same but you've to find the adient kernel...
Click to expand...
Click to collapse
the problem isnt that he cant find the kernel. i kernel s included in the rom that you have downloaded and only needs to be extracted,
his problem now is that he lost his efs and doesnt have it anymore. you need your efs in order to flash CM10 because the updater script checks for certain files
US Model
Sent from my YP-G1 using xda app-developers app
when writing the title i saw a similair thread and they said he blew his digitizer, posting this question anyway just to see if somebody can confirm that.
Hallo,
First off some details:
I have a galaxy s3 i9300.
I was attempting to install android 4.4.
Due to "error 7" this was a lot harder then it should have been ( the versions of cwm that i could get to work gave error 7 and newer versions did not load)
Eventually i installed philz touch version 6 wich was able to install this kitkat file: http://forum.xda-developers.com/devdb/project/dl/?id=11372
(back-to-n00t_ROM_V9).
However the screen stopped responding, the solutions found using google (take our battery, factory reset, unscrew the back and check a connector) did not work.
I think i got android 4.4 running, the other buttons work fine and i can acces the recovery and the download mode.
During my process i downloaded a kernel of a s2
(https://emilgeorgejames.wordpress.c...ogenmod-11-kk4-4-4-on-samsung-s-ii-gt-i9100g/)
Which, as far as i can see might be the problem, however i dont know anything about kernels etc. i tried installing s3 kernels from here (http://forum.xda-developers.com/galaxy-s3/general/ref-galaxy-s3-stock-kernel-bootloaders-t2189063) which did not solve the problem.
I installed android 4.3 again from here (http://www.sammobile.com/firmwares/database/GT-I9300/), i installed the Netherlands version which had a pda of i9300XUGOL2 and a CSC I9300TNLGOC1 (what ever that means)
Currently i am downloading I9300XXEMG5_I9300ODDEMG1_INU from (http://www.sammobile.com/firmwares/confirm/17479/I9300XXEMG5_I9300ODDEMG1_INU/) since that matches the kernal version i mentioned above.
Take note, i am very new at this, i spend some time today and yesterday trying to get android 4.4 working which is all the experience i have with this subject.
In advance, thank you all for any help you can provide.
I hope i dont have to buy a new phone, i just wanted to play pokemon go
pls help to get below answer from you
*is touch working on recovery mod(philpz touch recovery)
if it working try with cm 13 it gave pure kernel from source.i think you must need to check your digitizer and also pls see this https://www.youtube.com/watch?v=ily16gjJw_Y
dimuthu7 said:
pls help to get below answer from you
*is touch working on recovery mod(philpz touch recovery)
if it working try with cm 13 it gave pure kernel from source.i think you must need to check your digitizer and also pls see this [your link because i cant post links?]
Click to expand...
Click to collapse
Hi thanks for the reply!
The touch screen is not working in recovery, i guess i`ll try installing cm 13 anyway.
I tried what is shown on youtube before and it did not work unfortunaly.
I installed cm13 nightly build from here: download.cyanogenmod.org/?device=i9300
Screen is still unresponsive.
krediax said:
Hi thanks for the reply!
The touch screen is not working in recovery, i guess i`ll try installing cm 13 anyway.
I tried what is shown on youtube before and it did not work unfortunaly.
Click to expand...
Click to collapse
so my bet is you made the phone go to emergency (touch)-firmware flash and it failed... this occures if you flash a wrong kernel or a kernel that was broken due to download (that happens sometimes... thats why there are md5sums out )
we can fix that but first:
MAKE SURE YOU HAVE A i9300 ... then proceed
1. make sure you are on a correct i9300 kernel
2. make sure you are on my latest twrp for i9300
3. make sure to flash latest cm13 official for i9300
if you boot to twrp and the touch dont work then install "minimal adb and fastboot" (no link... google... ) to your PC
then open adb and connect the phone while in twrp
then enter this command in terminal:
adb twrp mount system
adb shell ls /system/etc/
and show me what you see
Sent from my GT-I9300 using XDA Free mobile app
SdtBarbarossa said:
so my bet is you made the phone go to emergency (touch)-firmware flash and it failed... this occures if you flash a wrong kernel or a kernel that was broken due to download (that happens sometimes... thats why there are md5sums out )
we can fix that but first:
MAKE SURE YOU HAVE A i9300 ... then proceed
1. make sure you are on a correct i9300 kernel
2. make sure you are on my latest twrp for i9300
3. make sure to flash latest cm13 official for i9300
if you boot to twrp and the touch dont work then install "minimal adb and fastboot" (no link... google... ) to your PC
then open adb and connect the phone while in twrp
then enter this command in terminal:
adb twrp mount system
adb shell ls /system/etc/
and show me what you see
Sent from my GT-I9300 using XDA Free mobile app
Click to expand...
Click to collapse
I definitly installed the wrong kernal at one point, cause im stupid and tought what could go wrong?
I tried to follow your steps.
1. i think i have a correct kernal installed now, i instaled one from (forum.xda-developers.com/galaxy-s3/general/ref-galaxy-s3-stock-kernel-bootloaders-t2189063) i removed the http:// else i cant post the link.
2. i installed 3.0.2-1 for the i9300, however it asks me about unmodified system partitions and to exit that screen i need to have touch screen enabled. It twrp needed or is philz touch / cmw also oke?
3. How do i flash cm13? I have odin but the only cm13 files i could find were either a zip or a recovery.img The zip is on my sd card and installed atm i could reinstall it again from sd card if that also works and then reboot?
thanks for the help
Try to restore your Stock firmware with kies, flash twrp with odin and then install cm13.
Gesendet von meinem LG-H850 mit Tapatalk
krediax said:
I definitly installed the wrong kernal at one point, cause im stupid and tought what could go wrong?
I tried to follow your steps.
1. i think i have a correct kernal installed now, i instaled one from (forum.xda-developers.com/galaxy-s3/general/ref-galaxy-s3-stock-kernel-bootloaders-t2189063) i removed the http:// else i cant post the link.
2. i installed 3.0.2-1 for the i9300, however it asks me about unmodified system partitions and to exit that screen i need to have touch screen enabled. It twrp needed or is philz touch / cmw also oke?
3. How do i flash cm13? I have odin but the only cm13 files i could find were either a zip or a recovery.img The zip is on my sd card and installed atm i could reinstall it again from sd card if that also works and then reboot?
thanks for the help
Click to expand...
Click to collapse
yea that twrp screen is normal...
we can do EVERYTHING via adb... its really mighty on twrp...
Sent from my GT-I9300 using XDA Free mobile app
YannikM said:
Try to restore your Stock firmware with kies, flash twrp with odin and then install cm13.
Gesendet von meinem LG-H850 mit Tapatalk
Click to expand...
Click to collapse
Did not work
SdtBarbarossa said:
yea that twrp screen is normal...
we can do EVERYTHING via adb... its really mighty on twrp...
Sent from my GT-I9300 using XDA Free mobile app
Click to expand...
Click to collapse
Okay i did the following steps:
back to stock with kies
installed philz touch 6
installed cm13 md5sum: db517fbbacdb167b06f5b483dbdce
installed twrp 3.0.2-1
Now i cant use anything in recovery since i cant go passed the partition system.
Using adb i can give commands and i tried your commands.
However i have no clue what to place on the etc part in: "adb shell ls /system/etc/"
When literally typing that it returns: "ls: /system/etc/: No such file or directory"
krediax said:
Did not work
Okay i did the following steps:
back to stock with kies
installed philz touch 6
installed cm13 md5sum: db517fbbacdb167b06f5b483dbdce
installed twrp 3.0.2-1
Now i cant use anything in recovery since i cant go passed the partition system.
Using adb i can give commands and i tried your commands.
However i have no clue what to place on the etc part in: "adb shell ls /system/etc/"
When literally typing that it returns: "ls: /system/etc/: No such file or directory"
Click to expand...
Click to collapse
it has no scence if you dont listen to me.... i sayd TWRP .... not Philz .... so on Philz that will never work
Sent from my GT-I9300 using XDA Free mobile app
---------- Post added at 04:56 PM ---------- Previous post was at 04:55 PM ----------
sorry didnt saw last words....
did you do adb twrp mount system before?
Sent from my GT-I9300 using XDA Free mobile app
SdtBarbarossa said:
it has no scence if you dont listen to me.... i sayd TWRP .... not Philz .... so on Philz that will never work
Sent from my GT-I9300 using XDA Free mobile app
---------- Post added at 04:56 PM ---------- Previous post was at 04:55 PM ----------
sorry didnt saw last words....
did you do adb twrp mount system before?
Sent from my GT-I9300 using XDA Free mobile app
Click to expand...
Click to collapse
Yes, that gave back a big list called "Android Debug Bridge version 1.0.36 Revision fd9e4d07b0f5 -android", looking trought that list if found the shell command which said:
adb shell [-e escape] [-n] [-Tt] [-x] [command] - run remote shell command (interactive shell ifno command given)
(-e: choose escape character, or "none"; default '~')
(-n: don't read from stdin)
(-T: disable PTY allocation)
(-t: force PTY allocation)
(-x: disable remote exit codes and stdout/stderr septeration)
krediax said:
Yes, that gave back a big list called "Android Debug Bridge version 1.0.36 Revision fd9e4d07b0f5 -android", looking trought that list if found the shell command which said:
adb shell [-e escape] [-n] [-Tt] [-x] [command] - run remote shell command (interactive shell ifno command given)
(-e: choose escape character, or "none"; default '~')
(-n: don't read from stdin)
(-T: disable PTY allocation)
(-t: force PTY allocation)
(-x: disable remote exit codes and stdout/stderr septeration)
Click to expand...
Click to collapse
adb shell twrp mount system
adb shell ls /system/etc
Sent from my GT-I9300 using XDA Free mobile app
SdtBarbarossa said:
adb shell twrp mount system
adb shell ls /system/etc
Sent from my GT-I9300 using XDA Free mobile app
Click to expand...
Click to collapse
That did something.
These are the results:
D:\Programs\Android-sdk\android-sdk\platform-tools>adb shell ls /system/etc
CHANGELOG-CM.txt media_codecs_google_audio.xml
CHANGES.txt media_codecs_google_telephony.xml
NOTICE.html.gz media_codecs_google_video.xml
apns-conf.xml media_profiles.xml
audio_effects.conf mkshrc
audio_policy.conf nano
bash nfcee_access.xml
bluetooth permissions
build-manifest.xml ppp
clatd.conf preloaded-classes
dhcpcd recovery-resource.dat
event-log-tags security
excluded-input-devices.xml sound
fallback_fonts.xml srm.bin
fonts.xml ssh
gps.conf sysconfig
gps.xml system_fonts.xml
hosts terminfo
init.d updatecmds
media_codecs.xml vimrc
media_codecs_ffmpeg.xml wifi
edit: I added spaces to make things more organised but that didn`t seem to work.
will look deper when im home... that command was just to make sure you have acess to a running system... will need to find the correct touchfirmware updater for sgs3
Sent from my GT-I9300 using XDA Free mobile app
SdtBarbarossa said:
will look deper when im home... that command was just to make sure you have acess to a running system... will need to find the correct touchfirmware updater for sgs3
Sent from my GT-I9300 using XDA Free mobile app
Click to expand...
Click to collapse
I googled a bit on touch firm ware updater, there are a couple of links.
Not going to install anyting tough, going to wait what you think since it seems like you know what you are talking about!
krediax said:
I googled a bit on touch firm ware updater, there are a couple of links.
Not going to install anyting tough, going to wait what you think since it seems like you know what you are talking about!
Click to expand...
Click to collapse
ok so on sony devices (wich uses rmi4 ) you can flash it directly... on your samsung thats not possible... because you use tsp_malfes .... BUT
1. flash a full stockrom ( for your device !!!)
2. get a usb otg mouse and connect
3. use the mouse to controll your phone now
4. go to dialer and type *#*#2663#*#
this should initialise a touchscreen firmware update
if it suceed... your touch should work after reboot
if it suceeded and your touch doesnt work after reboot it is maybe burned due to overvoltage
if it failed give me the error message
Sent from my GT-I9300 using XDA Free mobile app
---------- Post added at 09:51 PM ---------- Previous post was at 09:15 PM ----------
ah and btw make sure to activate wifi before
Sent from my GT-I9300 using XDA Free mobile app
SdtBarbarossa said:
ok so on sony devices (wich uses rmi4 ) you can flash it directly... on your samsung thats not possible... because you use tsp_malfes .... BUT
1. flash a full stockrom ( for your device !!!)
2. get a usb otg mouse and connect
3. use the mouse to controll your phone now
4. go to dialer and type *#*#2663#*#
this should initialise a touchscreen firmware update
if it suceed... your touch should work after reboot
if it suceeded and your touch doesnt work after reboot it is maybe burned due to overvoltage
if it failed give me the error message
Sent from my GT-I9300 using XDA Free mobile app
---------- Post added at 09:51 PM ---------- Previous post was at 09:15 PM ----------
ah and btw make sure to activate wifi before
Sent from my GT-I9300 using XDA Free mobile app
Click to expand...
Click to collapse
It never started the update, it gave an error called:
Connection Problem or Invalid MMI Code
I could try to bypass it by using method 2 mentioned here: http://www.technobezz.com/fix-connection-problem-invalid-mmi-code/
Which is to add + signs after every *. However i dont know if thats a smart thing to do.
edit: I called somebody to make sure i dont have connection problems.
krediax said:
It never started the update, it gave an error called:
Connection Problem or Invalid MMI Code
I could try to bypass it by using method 2 mentioned here: http://www.technobezz.com/fix-connection-problem-invalid-mmi-code/
Which is to add + signs after every *. However i dont know if thats a smart thing to do.
edit: I called somebody to make sure i dont have connection problems.
Click to expand...
Click to collapse
are you on wifi?
Sent from my GT-I9300 using XDA Free mobile app
SdtBarbarossa said:
are you on wifi?
Sent from my GT-I9300 using XDA Free mobile app
Click to expand...
Click to collapse
Yes i am
krediax said:
Yes i am
Click to expand...
Click to collapse
then maybe try that + stuff... i guess your verification number of touch is broken (mmi)
Sent from my GT-I9300 using XDA Free mobile app