Related
Found this via google groups.
You can unlock your phone via an adb shell command
Code:
adb shell
input keyevent 82
or on one line:
adb shell input keyevent 82
key event 82:
public static final int KEYCODE_MENU
Since: API Level 1
Key code constant: Menu key.
Constant Value: 82 (0x00000052)
Click to expand...
Click to collapse
Background: I flashed a kernel and rebooted and when the phone was fully booted I could not unlock the lock screen!
Had disabled the slider and had the menu key set to unlock (cm7). Unfortunately the kernel must have had a bug or something and all my soft buttons were not working.
Neat! It never occured to me that ADB might support sending key events.
Any updates to this? I locked myself with gesture. LOL
mh do you know what it is for the Desire??
I tryed this, but it doesn't worked. had a simular problem. I worked on the lockscreen and than i removed the ring, and i could push it XD
Thanks a lot man for sharing this.
Working awesome with Nexus 5.
Thank you!!!
Thank you for good information . :good::good::good::good:
Doesn't work with Samsung S6
Hi, it doesn't work with Samsung S6. Any generic solution for all the mobile devices ?
UPDATE:
if you want to get your stock webos back you just need to start
webosdoctorp302hstnhwifi.jar ( find it with google / its the newest webos 3.02)
get the device into developer mode reset (power button + middle button ) and then ( power button + volume up )
follow the instructions of webosdoctor
to get into developermode in the webos just type webos20090606
If you want to mod your webos or want some good software for it, like an Fileexplorer ( internalz pro ) and things like that:
start WebOSQuickInstall-4.2.3.jar ( google it )
if you want a videoplayer just install kalemsoft media player for touchpad
( can be found on the homepage of kalemsoft)
have fun people.
ps: i heard someone trying to port mplayer to the webos, thats great. with that you can play mkv files with subtitles
Updated 1st Post
jlove said:
i just found a solution for everyone with the same issue.
if you press power button and middle button together for abou 10 sec - 15 sec. the device will hard reset.
now press power and wolume button up --> now it is in usb developer mode
start webos doctor and istall the new os.
Click to expand...
Click to collapse
I don't have an issue, but it was very nice of you to come back with a response to your own issue. Now a search will wield an actual resolution. Too many unsolved cases here.
if you have a hd touchpad tablet, then some day, maybe tomorow maybe in a year, you will have that issue.
and then smile and lean back, because now you know the solution
What version is out now? Im on 3.0.2
jlove said:
i just found a solution for everyone with the same issue.
if you press power button and middle button together for abou 10 sec - 15 sec. the device will hard reset.
now press power and wolume button up --> now it is in usb developer mode
start webos doctor and istall the new os.
Click to expand...
Click to collapse
Good post, will save a lot of people. Have a sticky
jlove said:
i just found a solution for everyone with the same issue.
if you press power button and middle button together for abou 10 sec - 15 sec. the device will hard reset.
now press power and wolume button up --> now it is in usb developer mode
start webos doctor and istall the new os.
Click to expand...
Click to collapse
So then, is this a way I can completely reset the device to be like new if I want to sell or give it to someone?
Where do I get a complete copy of the OS to keep on my computer for a possible reload?
Risks of hacking
I have a similar question - and I've checked the boards and wiki, but didn't have much luck finding a simple answer.
What are the risks of modding, hacking, or jailbreaking? I'm assuming that as long as I don't physically impact the hardware (overheating or otherwise) that there will be some way to get the device back to the original state through reinstalling / reset. Can I screw up with software enough that it permanently bricks the device?
I'm new at this, but looking forward to doing some playing around. I just wanted a better idea of what I'm getting into.
From what I've read the web doctor can cure it.
Thanks for the info. Hopefully these devices prove hard to brick. =D Means we don't have to worry as much about beta software.
The longtime webOS folks in the precentral forums are claiming it's impossible to brick a TouchPad.
if you want to get your stock webos back you just need to start
webosdoctorp302hstnhwifi.jar ( find it with google / its the newest webos 3.02)
get the device into developer mode reset (power button + middle button ) and then ( power button + volume up )
follow the instructions of webosdoctor
to get into developermode in the webos just type webos20090606
If you want to mod your webos or want some good software for it, like an Fileexplorer ( internalz pro ) and things like that:
start WebOSQuickInstall-4.2.3.jar ( google it )
if you want a videoplayer just install kalemsoft media player for touchpad
( can be found on the homepage of kalemsoft)
have fun people.
ps: i heard someone trying to port mplayer to the webos, thats great. with that you can play mkv files with subtitles
From the number of reports of android bricks I have seen I would say that is not true. Then again its pretty hard to brick a iPhone
Longtime WebOS user here, it is impossible to brick a palm pre or other webOS devices. The only devices that actually brick are ones that have hardware damage (bad motherboard, etc). Has to do with the bootloader and it's ability to survive just about anything short of nuclear winter. Rwhitby is the man to ask about this stuff but I've done about everything possible to my devices and they still work :-D
It hangs at 12% :-( looks like dead ...
Please OP change the Title. You can not brick a Touchpad unless you play with something that you will never play...
blah
Anyone having trouble restoring the device with the webosdoctorp302hstnhwifi.jar download and run webosdoctorp300hstnhwifi.jar
I tried this after being unsuccesfull after a friend suggested that some people have a different/earlier build
Thats the only thing that worked for me. 3.02 did not
I get stuck with both webdoc jar files ... no idea why.
I can connect via novaterm ... no problem but what´s next to "manually" put the image into the device.
"Once connected to the device, type:
lvm.static vgscan --ignorelockingfailure
lvm.static vgchange -ay --ignorelockingfailure
"
that does not work...
logs:
LOG 1
HTML:
26.08.2011 00:13:25 com.palm.nova.installer.recoverytool.CardController logPrint
INFO: Trenchcoat: Start cluster beyond limit (2845090973 > 901667). Truncating file.
26.08.2011 00:13:25 com.palm.nova.installer.recoverytool.CardController logPrint
INFO: Trenchcoat: /.palm/=2R3UM52A=/=2TLV4Y===/=2T745F5Q=/=2R3UM552M6BWYD57ZYKCQ====/=2RT35HNKV6JQJQESQJQSIUNJGBL65XXM7F3ZYVJHYJY======/=2QL45P5I=/=2TT34X2KG6Y======/=2QL45T6S77JRJA===/=2RP65R6SQ754LB6MARNITEKQ=/=2RL3A====/=2T745T7Q4/\014\215¶XÃñ\214°.\007\212(
LOG 2
HTML:
Trenchcoat: /.palm/=2R3UM52A=/=2TLV4Y===/=2T745F5Q=/=2R3UM552M6BWYD57ZYKCQ====/=2RT35HNKV6JQJQESQJQSIUNJGBL65XXM7F3ZYVJHYJY======/=2QL45P5I=/=2TT34X2KG6Y======/=2QL45T6S77JRJA===/=2RP65R6SQ754LB6MARNITEKQ=/=2RL3A====/=2T745T7Q4/FSCK0015.REN
26.08.2011 00:13:22 com.palm.nova.installer.recoverytool.CardController logPrint
INFO: Trenchcoat: Directory has non-zero size. Fixing it.
26.08.2011 00:13:22 com.palm.nova.installer.recoverytool.CardController logPrint
INFO: Trenchcoat: /.palm/=2R3UM52A=/=2TLV4Y===/=2T745F5Q=/=2R3UM552M6BWYD57ZYKCQ====/=2RT35HNKV6JQJQESQJQSIUNJGBL65XXM7F3ZYVJHYJY======/=2QL45P5I=/=2TT34X2KG6Y======/=2QL45T6S77JRJA===/=2RP65R6SQ754LB6MARNITEKQ=/=2RL3A====/=2T745T7Q4/FSCK0015.REN
Log 0
HTML:
26.08.2011 00:13:29 com.palm.nova.installer.recoverytool.CardController logPrint
INFO: Trenchcoat: /.palm/=2R3UM52A=/=2TLV4Y===/=2T745F5Q=/=2R3UM552M6BWYD57ZYKCQ====/=2RT35HNKV6JQJQESQJQSIUNJGBL65XXM7F3ZYVJHYJY======/=2QL45P5I=/=2TT34X2KG6Y======/=2QL45T6S77JRJA===/=2RP65R6SQ754LB6MARNITEKQ=/=2RHVA====/s"\012);\012\000\000.\000\000\000
26.08.2011 00:13:29 com.palm.nova.installer.recoverytool.CardController logPrint
INFO: Trenchcoat: Bad file name.
26.08.2011 00:13:29 com.palm.nova.installer.recoverytool.CardController logPrint
INFO: Trenchcoat: Auto-renaming it.
26.08.2011 00:13:29 com.palm.nova.installer.recoverytool.CardController logPrint
INFO: Trenchcoat: Renamed to FSCK0001.REN
26.08.2011 00:14:38 com.palm.nova.installer.recoverytool.CardController logPrint
INFO: Unknown trenchcoat error
26.08.2011 00:14:38 com.palm.nova.installer.recoverytool.CardController logPrint
INFO: retrying trenchcoat
26.08.2011 00:14:38 com.palm.nova.installer.core.stages.TrenchcoatStage$TrenchcoatReaderThread run
There is a Quote icon to add codes guys...
Just like this:
<html>
</html>
Click to expand...
Click to collapse
TravisAntonio said:
There is a Quote icon to add codes guys...
Just like this:
Click to expand...
Click to collapse
you can also use the
Code:
tag like so:
[code]
this is code;
Hey guys,
Tonight, Elite Recognized Developer Rebellos and myself managed two very major breakthroughs for Samsung Exynos based devices.
1. Stable implementation of the Open Galaxy Bootloader (based on Uboot)
Code:
��BL2
U-Boot 2010.12-00051-g02bdbef-dirty (Dec 23 2012 - 01:53:11) for EXYNOS4_GALAXY
CPU: S5PC220 [Samsung SOC on SMP Platform Base on ARM CortexA9]
APLL = 1000MHz, MPLL = 800MHz
DRAM: 1 GiB
[I2C] CLK_GATE_IP_PERIL: 0xFFFFFFFF, enabling channel 7
[I2C] channel 7 initialised with freq 400000 and timeout 1000000.
[I2C] ePrescaler: 16 nPrescaler: 15.
[I2C->ERR] Timeout Slave Address
pmic_s5m8767_init set reg 0xE to 0x6F with mask 0x0
pmic_s5m8767_init set reg 0x5A to 0x58 with mask 0x0
pmic_s5m8767_init set reg 0x5B to 0xB4 with mask 0x0
pmic_s5m8767_init set reg 0xA to 0xE with mask 0xE
pmic_s5m8767_init set reg 0x11 to 0xE with mask 0x0
pmic_s5m8767_init set LDO2 to enable 0x1
pmic_s5m8767_init set LDO4 to enable 0x1
pmic_s5m8767_init set LDO5 to enable 0x0
pmic_s5m8767_init set LDO6 to enable 0x1
pmic_s5m8767_init set LDO7 to enable 0x1
pmic_s5m8767_init set LDO8 to enable 0x1
pmic_s5m8767_init set LDO9 to V 1800
pmic_s5m8767_init set LDO10 to enable 0x1
pmic_s5m8767_init set LDO11 to V 1950 with enable 0x1
pmic_s5m8767_init set LDO12 to enable 0x1
pmic_s5m8767_init set LDO13 to enable 0x0
pmic_s5m8767_init set LDO14 to V 1950 with enable 0x1
pmic_s5m8767_init set LDO15 to enable 0x1
pmic_s5m8767_init set LDO16 to enable 0x1
pmic_s5m8767_init set LDO18 to enable 0x1
pmic_s5m8767_init set LDO19 to V 1800 with enable 0x1
pmic_s5m8767_init set LDO20 to V 3300
pmic_s5m8767_init set LDO21 to V 3300
pmic_s5m8767_init set LDO22 to V 2800
pmic_s5m8767_init set LDO27 to V 1500
PMIC: S5M8767
====================
S5M8767 PMIC registers
====================
ID = 0x05
ONSRC = 0x01
STATUS1 = 0x11
STATUS2 = 0x11
STATUS3 = 0x07
IRQ1 = 0x09
IRQ2 = 0x38
IRQ3 = 0x00
PWROFFSRC = 0x00
PMIC_RTC_WTSR_SMPL_REG = 0x80
S5M8767_REG_BUCHG = 0x6f
i2c_gpio_new_port virtual channel 0 registered
max77693 charger PMIC rev = PASS2, REG_ID2: 0x4
BL1 version: 20111128
Checking Boot Mode... EMMC4.41
REVISION: 1.1
[ERROR] response timeout error : 00000104 cmd 1
FAIL: waiting for status update.
MMC Device 0: 0 MB
MMC Device 1: 7580 MB
MMC Device 2 not found
FAIL: waiting for status update.
FAIL: waiting for status update.
mmc read failed
*** Warning - using default environment
Hit any key to stop autoboot: 0
GALAXY #
GALAXY #
What's this mean? We can now work INSIDE the Samsung TrustZone on production devices! This means some serious debugging of bootloaders is possible.
2. fastboot on the Galaxy Camera
Code:
[email protected]:~/Desktop/GCAMBoot$ sudo fastboot devices
SMDKEXYNOS-01 fastboot
[email protected]:~/Desktop/GCAMBoot$ sudo fastboot boot ./BOOT.bin
downloading 'boot.img'...
OKAY [ 1.642s]
booting...
OKAY [ 0.217s]
finished. total time: 1.859s
[email protected]:~/Desktop/GCAMBoot$
What does this REALLY mean? It means that not only do we have a way to get away from Samsung closed source bootloaders, but we can now boot TOTALLY from SDCard on the Galaxy Camera and the Galaxy S3.... What's that mean? We can fix brick-bugged Galaxy S3 devices!
I need a Galaxy S3 to work with. Anyone have a brick or a GS3 they're not using? I need it.
I will be performing the following:
1. EMMC Disable hardware mod (can be undone later)
2. UART hookups for debugging and working in fastboot mode.
3. attempting to rework GS3 Ramdisk for SDCard boot.
4. recreating the proper partition structure on a 16 gig.
From the current track record, i'm guessing that just about everyone will need this in a year or so. We hope to have this ready fairly quickly so anyone can just open their device, drop a bead of solder over a resistor, insert an SDCard and boot up again.
The further implications of this are: directly booting ubuntu, Chrome OS, WebOS or just about anything else... This tool will make it easy!
I estimate this will take 3-6 weeks of research. If you can donate a GS3 or do an extended loan, it will help out many people with bricked EMMCs. The device can even be bricked.
Very good news. Great work Adam
Great waiting for somebody to donate his dead s3
Sent from my GT-I9300 using xda app-developers app
Thanks for all your hard work .
jje
brilliant.....
loking foreward to experimental roms to boot from my separate sd card
like cyanogen, ubuntu and so on!!!
Good news just before x-mas
Thanks
Thank god! Adam,
at least there is now hope for 'to be dead' S3s
+1
AWESOME!
Ty for your great work guys!
so in theory we could not only boot any ROM from SD to unbrick, but also boot Linux natively from our SD card instead of chrooting in?
Leave it to Adam and other Elite Developers to find such awesomeness! It's great to know that you can't truly hard brick a phone. And running ANY rom you want from the sdcard? That sounds freaking awesome!
Great news.
Good job.:thumbup:
Verzonden door mijn GT-I9300 met xda premium
Just some questions to get the picture.
1. EMMC Disable hardware mod (can be undone later)
This would be a semi-permanent resistor shortening (same as we would do when following the instructions of the official samsung unbrick guide) or am I wrong?
3. attempting to rework GS3 Ramdisk for SDCard boot.
What ramdisk do you mean? do you want to boot a rom from sd or a custom bootloader from sd?
Love your work guys think u will be going down in The History Of The Galaxy S3 lol
Keep up the goods
Sent from my GT-I9300 using Tapatalk.Siyah Kernel Rules The Galaxy
theq86 said:
Just some questions to get the picture.
1. EMMC Disable hardware mod (can be undone later)
This would be a semi-permanent resistor shortening (same as we would do when following the instructions of the official samsung unbrick guide) or am I wrong?
3. attempting to rework GS3 Ramdisk for SDCard boot.
What ramdisk do you mean? do you want to boot a rom from sd or a custom bootloader from sd?
Click to expand...
Click to collapse
Yes and the ramdisk needs to be reworked for uboot and booting from SDCard.
I'd appreciate it if you guys kept the "thanks" to a minimum.. I need a device to work with. Nothing has been done for GS3 yet and nothing will until we get a device. Extra posts make people think that something's already happened. It hasn't. I need a device.
Thanks, hopefully somebody loan a device
Please make out a sticky too
Sent from my GT-I9100 using xda app-developers app
Hmm.. thinking about it
Sent from my GT-I9300 using Tapatalk 2
thank you very much for sharing the info and for all the hardwork.
Great work!
I suggest crowd funding. Add a donate button, i will give 10 $. 49 sponsors needed left.
Sent from my GT-I9300 using xda app-developers app
jo_keks said:
Great work!
I suggest crowd funding. Add a donate button, i will give 10 $. 49 sponsors needed left.
Click to expand...
Click to collapse
I'll pledge to this as well. Perhaps we dont need 500, because a used s3 can be obtained for less, and if I understood correctly adam can even work with a "sudden death" victim?
jo_keks said:
Great work!
I suggest crowd funding. Add a donate button, i will give 10 $. 49 sponsors needed left.
Sent from my GT-I9300 using xda app-developers app
Click to expand...
Click to collapse
+1 :good:
sodeknetters said:
I'll pledge to this as well. Perhaps we dont need 500, because a used s3 can be obtained for less, and if I understood correctly adam can even work with a "sudden death" victim?
Click to expand...
Click to collapse
He requires a SDS(sudden death syndrome) Galaxy S3. We can even ask a SDS victims to sell his device to adam instead of sending it for a repair. The money can for this can be generated through crowd funding .
i like the idea and hope it will be turned into a tool kit for those situations as the S3 SDS can potentially affect any S3.
Not much but here you go Confirmation number: 9CY83908VJ862193J
Hi,
Got this spaking i9505 s4, but it seems the *#197328640# service mode is missing, im using this mode to select wcdma band, In my S2 it is there.
Did samsung removed : *#197328640#, if yes how do we access wcdma select band?
Also *#2263# is not working
Thanks,
Roy
Same problem here!
Service mode:
*#0011#
Options*--> back
Options -->key input -->1
Black screen with number 1 up on the left
buy samsung service mode apk
buy samsung service mode apk from the play store
bernny26 said:
buy samsung service mode apk from the play store
Click to expand...
Click to collapse
Service mode is not working, I can get in to what says service mode but then back does not work abd it stuck in some sort active data mode.
docurley said:
Service mode is not working, I can get in to what says service mode but then back does not work abd it stuck in some sort active data mode.
Click to expand...
Click to collapse
I did read that its modem related?
this post says so?
http://forum.xda-developers.com/showpost.php?p=42550422&postcount=3539
rodnah said:
I did read that its modem related?
this post says so?
http://forum.xda-developers.com/showpost.php?p=42550422&postcount=3539
Click to expand...
Click to collapse
Well I tried the modem reflash and still no Service mode just the same old screen shot each time.
docurley said:
Well I tried the modem reflash and still no Service mode just the same old screen shot each time.
Click to expand...
Click to collapse
Did you manage to solve this? I'm stuck at the same point. Menu -> back doesn't do anything at all.
TY
squaredd said:
Did you manage to solve this? I'm stuck at the same point. Menu -> back doesn't do anything at all.
TY
Click to expand...
Click to collapse
No I did not I ended up selling the phone as I wanted to change networks but I could not unlock the pjone.
Ei.. any fix for this?
i BELIEVE this is part of Samsung's "business strategy".. i was resolve this using the Samsung Service Mode apk (which I cracked and patched :highfive, however i have another issue related to this (see attached pic)!
In this case...may i ask if anyone from XDA knows the secret code for the UMTS Menu for me to access the Network Unlock menu???
RESOLVED thru SERENDIPITY!
mrryanangeles16 said:
i BELIEVE this is part of Samsung's "business strategy".. i was resolve this using the Samsung Service Mode apk (which I cracked and patched :highfive, however i have another issue related to this (see attached pic)!
In this case...may i ask if anyone from XDA knows the secret code for the UMTS Menu for me to access the Network Unlock menu???
Click to expand...
Click to collapse
Hi XDA Peeps!
I was able to unlock my i9505!
I just did the following steps:
1. Dial *#0011# via Phone Utility apk [Phone Connectivity Status will appear (via Service Mode)];
2. Tap on the left soft key (LSK) and select Key Input > Enter 1 > Hit OK;
3. Tap on the LSK and select BACK [You're now just a few steps away!];
4. Tap on the LSK and select Key Input > Enter 1 > Hit OK [Your screen shall have a different output now (i.e., a single digit "1" on line 1)];
5. WAIT for 5 seconds until the UMTS MAIN MENU appears > Select Debug Screen > Select Phone Control > Select Network Lock;
6. Next, tap on: [3] PERSO SHA256 OFF;
7. From here, go back to the UMTS MAIN MENU by tapping on Menu (left soft key on SGS4) and selecting Back from the options;
8. Once you are in the UMTS menu, tap on: [6]COMMON;
9. There, select: [6]NV REBUILD;
10. Now in the NV Rebuild menu, tap on: [4] Restore Back-up;
11. Samsung Galaxy S4 will now go into a temporary freezing state. After a while you’ll see some activities. The screen will be black and the LED will turn Blue. The Menu and Back key button on phone will also light;
12. Lastly, your Samsung Galaxy S4 will reboot automatically and will take a minute or two in booting up (depending on your ROM's Boot Animation);
BOOM! Your Galaxy S4 GT i9505 is now SIM-unlocked! Try a SIM card from another carrier to confirm the process and do not forget to share this to your friends too!
XDA_AndioAngeles
FB: facebook.com/rmasr.angeles
Does not work on samsung secure boot devices
mrryanangeles16 said:
Hi XDA Peeps!
I was able to unlock my i9505!
I just did the following steps:
1. Dial *#0011# via Phone Utility apk [Phone Connectivity Status will appear (via Service Mode)];
2. Tap on the left soft key (LSK) and select Key Input > Enter 1 > Hit OK;
3. Tap on the LSK and select BACK [You're now just a few steps away!];
4. Tap on the LSK and select Key Input > Enter 1 > Hit OK [Your screen shall have a different output now (i.e., a single digit "1" on line 1)];
5. WAIT for 5 seconds until the UMTS MAIN MENU appears > Select Debug Screen > Select Phone Control > Select Network Lock;
6. Next, tap on: [3] PERSO SHA256 OFF;
7. From here, go back to the UMTS MAIN MENU by tapping on Menu (left soft key on SGS4) and selecting Back from the options;
8. Once you are in the UMTS menu, tap on: [6]COMMON;
9. There, select: [6]NV REBUILD;
10. Now in the NV Rebuild menu, tap on: [4] Restore Back-up;
11. Samsung Galaxy S4 will now go into a temporary freezing state. After a while you’ll see some activities. The screen will be black and the LED will turn Blue. The Menu and Back key button on phone will also light;
12. Lastly, your Samsung Galaxy S4 will reboot automatically and will take a minute or two in booting up (depending on your ROM's Boot Animation);
BOOM! Your Galaxy S4 GT i9505 is now SIM-unlocked! Try a SIM card from another carrier to confirm the process and do not forget to share this to your friends too!
XDA_AndioAngeles
FB: facebook.com/rmasr.angeles
Click to expand...
Click to collapse
This method does not work if your base band has been upgraded to I9505XXUBMG7 wish i had know what samsung was planning i would of done the unlock before upgrading. oh well the power of hind sight i suppose :crying:
I tried this...but when I put in the (star) #0011# the next screen says
"No Service"...what does that mean?
dorian2kx said:
I tried this...but when I put in the (star) #0011# the next screen says
"No Service"...what does that mean?
Click to expand...
Click to collapse
Same problem. Did you manage to sort this?
bump
any resolution? I get {connection problem or code MMI not valid}
UMTS Never appears for me unless I do this on my i545
Enter Phone Menu ..
* # 27663368378 #
[1] UMTS
[2] DEBUG
[6] PHONE CONTROL
[6] NETWORK LOCK
[3] PERSOSHA256 OFF
On this step off #3 is not a choice for me
MENU> BACK 3 TIMES .. [UMTS MAIN MENU]
[6] COMMON
[6] NV REBUILD
If it says GOLDEN-BACKUP exists ..
[4] RESTORE BACK-UP
any assistance is greatly appreciated
i545
Enter Phone Menu ..
* # 0011 #
press [menu]
press back
press [menu]
press key input
press Q
press [menu]
press 0000
wait for 30 seconde
winny57 said:
Enter Phone Menu ..
* # 0011 #
press [menu]
press back
press [menu]
press key input
press Q
press [menu]
press 0000
wait for 30 seconde
Click to expand...
Click to collapse
Improved your post. Worked for me, thanks!
*#0011#
Press [MENU]
press [Back]
press [MENU]
Press [Key Input]
Input [Q]
press [MENU]
Press [Key Input]
Input [0000]
Wait 30 Seconds.
If you get "0", exit the ServiceMode and restart.
no probleme
Still nothing on i545
Can someone please let me know. Thanks.
bueller213 said:
Can someone please let me know. Thanks.
Click to expand...
Click to collapse
There is currently a working method for the SPH-L720 S4, but none as of yet that I know have developed for S5.
You'd think similarities would allow it to be done, but the model previously is what caused some of the issues.
Accessing the service menu is vital and it previously was believed to be inaccessible without downgrading modems.
But I found a thread showing how to access it. Here's the S4 forum: forum.xda-developers.com/showthread.php?t=2530610
here's the method to access service menu:
Dial *#0011# and then hit:
==> [MENU] + [Back]
==> [MENU] + [Key Input] + "Q"
==> [MENU] + [Key Input] + "0000"
==> <wait ~5-10 seconds>