Related
[Guide]Restore to Stock "Bricked" "Unlocked" LG Optimus G f180,E97x
The problem starts when you unlock F180 Bootloader with "freegee":
Unlock the bootloader:
There are 2 ways:
Method 1: Unlock the bootloader
http://www.mediafire.com/download/kzbp2gicuj22cv5/Tool_Root_Unlock_BL_4.1.2_edited.zip
Advantages:
- enough fastboot functions: Start, Power Off, Recovery mod, Restart Bootloader
- Easy on the function keys
-Cons:
- To Relock, just you have to flash KDZ
Method 2: Unlock by app
https://play.google.com/store/apps/details?id=edu.shell.freegee_free&hl=en
Advantages:
- Add.
- Can be easily Relock by app.
Cons:
- Right to Recovery through app (on Stock Rom & 975).
- Loss of function fastboot that this very important function.
- When crashes, not able to Recovery by pressing hard.
It is recommended to use the first way. :angel:
on E975, E970, E97.x unlock, select KT or SKT. Because E975 and the S / K has Same bootloader unlock.
i have already faced this situation to unlock bootloader with freegee and stuck with google logo and fastboot mode :crying:
not even KDZ flash working, always result in fastboot or KDZ tool stop working. also tried different KDZ and flashing Tools
Tried "TeenyBin" ,not success :crying: but get twrp working, then flash CM10 as suggested but got this
Subsystem Crash!
------------------------------------------------------------
DemiGod Crash Handler : Subsystem Crash! : External_modem (Undefined error)
Press key to choose Dload Mode/Reboot/Fastboot.
1) Volume Up : Dload Mode.
2) Volume Down : Reboot.
3) Power : Fastboot.
------------------------------------------------------------
to solve this have to remove sim card and change baseband in TWRP using ADB
then perform a hardreset.
now the device comes in life again
but you find the device is not properly working may be sim or gprs or wifi or something else.
now have to unlock bootloader again by adb with this method
Method 1: Unlock the bootloader
http://www.mediafire.com/download/kzbp2gicuj22cv5/Tool_Root_Unlock_BL_4.1.2_edited.zip
Advantages:
- fastboot functions: Start, Power Off, Recovery mod, Restart Bootloader
- Easy on the function
-Cons:
- To Relock, you have to flashed KDZ
Click to expand...
Click to collapse
after that will able to flash the stock KDZ without any problem
put device in D/W mode and flash it with appropriate official KDZ
Guide to flash KDZ
http://forum.xda-developers.com/showthread.php?t=2388440
:good:
have to follow the procedure because adb in recovery not able to replace the bootloader files
KDZ flash After mako bootloader unlock
step 1:
use TeenyBin http://forum.xda-developers.com/showthread.php?t=2249500
get twrp working, then flash CM10 for you device.
you will got this
Subsystem Crash!
------------------------------------------------------------
DemiGod Crash Handler : Subsystem Crash! : External_modem (Undefined error)
Press key to choose Dload Mode/Reboot/Fastboot.
1) Volume Up : Dload Mode.
2) Volume Down : Reboot.
3) Power : Fastboot.
------------------------------------------------------------
step 2:
to solve this have to remove sim card and change baseband in TWRP using ADB
then perform a hardreset.
to reflash the bootloader files you have to enter in CM10 or some ROM with SU or busybox;
now the device comes in life in CM10
now the device comes in life again
but you find the device is not properly working may be sim or gprs or wifi or something else.
now have to unlock bootloader again by adb with this method
Quote:
Method 1: Unlock the bootloader
http://www.mediafire.com/download/kz...1.2_edited.zip
Advantages:
- fastboot functions: Start, Power Off, Recovery mod, Restart Bootloader
- Easy on the function
-Cons:
- To Relock, you have to flashed KDZ
after that will able to flash the stock KDZ without any problem
put device in D/W mode and flash it with appropriate official KDZ
Guide to flash KDZ
http://forum.xda-developers.com/show....php?t=2388440
have to follow the procedure because adb in recovery not able to replace the bootloader files
Click to expand...
Click to collapse
UNLOCk steps:
enable USB debugging
connect as MTP
follow the steps in script
umar_fiaz said:
The problem starts when you unlock F180 Bootloader with "freegee":
Unlock the bootloader:
There are 2 ways:
Method 1: Unlock the bootloader
http://www.mediafire.com/download/kzbp2gicuj22cv5/Tool_Root_Unlock_BL_4.1.2_edited.zip
Advantages:
- enough fastboot functions: Start, Power Off, Recovery mod, Restart Bootloader
- Easy on the function keys
-Cons:
- To Relock, just you have to flash KDZ
Method 2: Unlock by app
https://play.google.com/store/apps/details?id=edu.shell.freegee_free&hl=en
Advantages:
- Add.
- Can be easily Relock by app.
Cons:
- Right to Recovery through app (on Stock Rom & 975).
- Loss of function fastboot that this very important function.
- When crashes, not able to Recovery by pressing hard.
It is recommended to use the first way. :angel:
on E975, E970, E97.x unlock, select KT or SKT. Because E975 and the S / K has Same bootloader unlock.
i have already faced this situation to unlock bootloader with freegee and stuck with google logo and fastboot mode :crying:
not even KDZ flash working, always result in fastboot or KDZ tool stop working. also tried different KDZ and flashing Tools
Tried "TeenyBin" ,not success :crying: but get twrp working, then flash CM10 as suggested but got this
Subsystem Crash!
------------------------------------------------------------
DemiGod Crash Handler : Subsystem Crash! : External_modem (Undefined error)
Press key to choose Dload Mode/Reboot/Fastboot.
1) Volume Up : Dload Mode.
2) Volume Down : Reboot.
3) Power : Fastboot.
------------------------------------------------------------
to solve this have to remove sim card and change baseband in TWRP using ADB
then perform a hardreset.
now the device comes in life again
but you find the device is not properly working may be sim or gprs or wifi or something else.
now have to unlock bootloader again by adb with this method
after that will able to flash the stock KDZ without any problem
put device in D/W mode and flash it with appropriate official KDZ
Guide to flash KDZ
http://forum.xda-developers.com/showthread.php?t=2388440
:good:
have to follow the procedure because adb in recovery not able to replace the bootloader files
Click to expand...
Click to collapse
BROTHER..i have a LG E975..i unlocked bootloader and now have a mako bootloader installed..its model version is e960 i.e nexus 4..installed kitkat..now i want 2 get back to stock rom..but my model number is changed from e975 to e960..f i try to restock it with lg flash tool it say check phone model..can u plz help me brother ..would be vry thankful to u
umar_fiaz said:
The problem starts when you unlock F180 Bootloader with "freegee":
Unlock the bootloader:
There are 2 ways:
Method 1: Unlock the bootloader
http://www.mediafire.com/download/kzbp2gicuj22cv5/Tool_Root_Unlock_BL_4.1.2_edited.zip
Advantages:
- enough fastboot functions: Start, Power Off, Recovery mod, Restart Bootloader
- Easy on the function keys
-Cons:
- To Relock, just you have to flash KDZ
Method 2: Unlock by app
https://play.google.com/store/apps/details?id=edu.shell.freegee_free&hl=en
Advantages:
- Add.
- Can be easily Relock by app.
Cons:
- Right to Recovery through app (on Stock Rom & 975).
- Loss of function fastboot that this very important function.
- When crashes, not able to Recovery by pressing hard.
It is recommended to use the first way. :angel:
on E975, E970, E97.x unlock, select KT or SKT. Because E975 and the S / K has Same bootloader unlock.
i have already faced this situation to unlock bootloader with freegee and stuck with google logo and fastboot mode :crying:
not even KDZ flash working, always result in fastboot or KDZ tool stop working. also tried different KDZ and flashing Tools
Tried "TeenyBin" ,not success :crying: but get twrp working, then flash CM10 as suggested but got this
Subsystem Crash!
------------------------------------------------------------
DemiGod Crash Handler : Subsystem Crash! : External_modem (Undefined error)
Press key to choose Dload Mode/Reboot/Fastboot.
1) Volume Up : Dload Mode.
2) Volume Down : Reboot.
3) Power : Fastboot.
------------------------------------------------------------
to solve this have to remove sim card and change baseband in TWRP using ADB
then perform a hardreset.
now the device comes in life again
but you find the device is not properly working may be sim or gprs or wifi or something else.
now have to unlock bootloader again by adb with this method
after that will able to flash the stock KDZ without any problem
put device in D/W mode and flash it with appropriate official KDZ
Guide to flash KDZ
http://forum.xda-developers.com/showthread.php?t=2388440
:good:
have to follow the procedure because adb in recovery not able to replace the bootloader files
Click to expand...
Click to collapse
thx for post my friend i have e975 i use freege and mako unlock .I used the first two months trouble-ROM but i have Subsystem crash error.... (external modem ) and i back to stock kdz but no root +bootloader unlocked i use my rom but I found something new
----------------------------------------------------
This problem can easily be solved, I spent 20+ hours on researching this, it's not an operator problem, but a common problem with both the Optimus G and the Nexus 4.
What causes it? Extreme low power states of the processor, some modems are too sensitive for this kind of deeeeeeep sleep (depending on production batch). These states are called C0 (WiFi) until C3 (complete power collapse).
Disable C2 and C3 and enable C0 and C1 and voila, it will never happen again
How? Buy and install Fauxclock, I don't know how to do it manually nor I couldn't find any other app.
You can thank me, but you should also thank Faust because he brought me this solution. Joying all the custom roms for months without problems
---------------------------------------------
Quote:
Originally Posted by metrixx02 View Post
my friend thx for post but ... i have one question what is this c0,c1,c2,c3c ????? CORES ?
x_justin :
No some power state of the processor, linux terms. Nothing to do with core numbers. As far as I know the only app that can change this is FauxClock from the play store, but it's worth the money. Just disable C2 and C3, it's still good for the battery. Stock roms from LG also have this disabled.
C0 Operational state. CPU fully turned on.
C1 First idle state. Stops CPU main internal clocks via software. Bus interface unit and APIC are kept running at full speed.
C2 Stops CPU main internal clocks via hardware. State where the processor maintains all software-visible states, but may take longer to wake up through interrupts.
C3 Stops all CPU internal clocks. The processor does not need to keep its cache coherent, but maintains other states. Some processors have variations of the C3 state that differ in how long it takes to wake the processor through interrupts.
http://doc.opensuse.org/products/draft/SLES/SLES-tuning_sd_draft/cha.tuning.power.html
PLS ONE USER TEST İT
NOT TESTED BY ME
THX x_justin
umar_fiaz said:
The problem starts when you unlock F180 Bootloader with "freegee":
Unlock the bootloader:
There are 2 ways:
Method 1: Unlock the bootloader
http://www.mediafire.com/download/kzbp2gicuj22cv5/Tool_Root_Unlock_BL_4.1.2_edited.zip
Advantages:
- enough fastboot functions: Start, Power Off, Recovery mod, Restart Bootloader
- Easy on the function keys
-Cons:
- To Relock, just you have to flash KDZ
Method 2: Unlock by app
https://play.google.com/store/apps/details?id=edu.shell.freegee_free&hl=en
Advantages:
- Add.
- Can be easily Relock by app.
Cons:
- Right to Recovery through app (on Stock Rom & 975).
- Loss of function fastboot that this very important function.
- When crashes, not able to Recovery by pressing hard.
It is recommended to use the first way. :angel:
on E975, E970, E97.x unlock, select KT or SKT. Because E975 and the S / K has Same bootloader unlock.
i have already faced this situation to unlock bootloader with freegee and stuck with google logo and fastboot mode :crying:
not even KDZ flash working, always result in fastboot or KDZ tool stop working. also tried different KDZ and flashing Tools
Tried "TeenyBin" ,not success :crying: but get twrp working, then flash CM10 as suggested but got this
Subsystem Crash!
------------------------------------------------------------
DemiGod Crash Handler : Subsystem Crash! : External_modem (Undefined error)
Press key to choose Dload Mode/Reboot/Fastboot.
1) Volume Up : Dload Mode.
2) Volume Down : Reboot.
3) Power : Fastboot.
------------------------------------------------------------
to solve this have to remove sim card and change baseband in TWRP using ADB
then perform a hardreset.
now the device comes in life again
but you find the device is not properly working may be sim or gprs or wifi or something else.
now have to unlock bootloader again by adb with this method
after that will able to flash the stock KDZ without any problem
put device in D/W mode and flash it with appropriate official KDZ
Guide to flash KDZ
http://forum.xda-developers.com/showthread.php?t=2388440
:good:
have to follow the procedure because adb in recovery not able to replace the bootloader files
Click to expand...
Click to collapse
Hey thanks a ton bro! I just had a few questions before using the first method to unlock my phones bootloader.
Is this method safe? Has it been tested enough yet? I dont want to use FreeGee again (soft bricked my phone the first time around using it).
If yes, can you please tell the steps to unlock using the 1st method?
Thnks again!
alimzia said:
Hey thanks a ton bro! I just had a few questions before using the first method to unlock my phones bootloader.
Is this method safe? Has it been tested enough yet? I dont want to use FreeGee again (soft bricked my phone the first time around using it).
If yes, can you please tell the steps to unlock using the 1st method?
Thnks again!
Click to expand...
Click to collapse
you say that u had used freegee??then did u also get ur bootloader of mako?
how did u switch back to stock rom??help me plz...
i need a kdz link for e975 too
I've tested the first method one time without any problem. I highly recommend to use this method rather in play store
yogivin said:
you say that u had used freegee??then did u also get ur bootloader of mako?
how did u switch back to stock rom??help me plz...
i need a kdz link for e975 too
Click to expand...
Click to collapse
Sorry I forgot to mention that was with the at&t version (had that earlier). After it got softbricked by using FreeGee I used teenybin to revive it. Wasn't able to get back into the official rom though. Instead used teenybin to flash recovery (teenybin also unlocks the bootloader in the process) and from there I used a zip file of the official Rom.
I don't know this, Im not entirely sure, but maybe if you can get a zip file (as you do for roms) you can then flash it via recovery. It wont lock back the bootloader ofcourse. Again, I m not sure about it and you best ask a senior member. It did work for me though, on At&t version.
---------- Post added at 07:52 PM ---------- Previous post was at 07:04 PM ----------
yawako said:
I've tested the first method one time without any problem. I highly recommend to use this method rather in play store
Click to expand...
Click to collapse
Can you please lay down the step by step how to unlock bootloader via this method? I do have some idea but don't want to do something stupid and make matters even worse.
Also, I had already tried using FreeGee before i stumbles upon your post. It did nothing, instead during the unlocking process FreeGee force closed. So does that change anything anyhow? I havent even rebooted my phone since then in fear of a possible hard brick
Highly appreciate your replies people!
yogivin said:
BROTHER..i have a LG E975..i unlocked bootloader and now have a mako bootloader installed..its model version is e960 i.e nexus 4..installed kitkat..now i want 2 get back to stock rom..but my model number is changed from e975 to e960..f i try to restock it with lg flash tool it say check phone model..can u plz help me brother ..would be vry thankful to u
Click to expand...
Click to collapse
Edited: to show flash step by step
umar_fiaz said:
Edited: to show flash step by step
Click to expand...
Click to collapse
Can you also add the step by step procedure to unlock bootloader using the first method? As in wether your phone should be in download mode, charge only mode etc etc.
alimzia said:
Can you also add the step by step procedure to unlock bootloader using the first method? As in wether your phone should be in download mode, charge only mode etc etc.
Click to expand...
Click to collapse
enable usb debugging
connect as MTP
follow the script
Hey
Yesterday I flash CM11 over stock 4.1.2 on my Optimus G (E975) and later decided to go back to stock again.
Everything was done witouht problems using nand back up with CWM
But later I realiced that M5 was out and, once again tried to install it but I couldnt
Dont know what happen but now while device is turning on, or trying to go into recovery or dowload mode screen is BLACk.
Device is working properly, I mean I turn it off/on and no problem. Just cant enter fastboot, recovery or download mode.
I tried a couple method to go back to stock using KDZ but proceess stop and nothing, just keep pressing power buttom and phone reboot (just black screen during the process)
Please, any ideas/suggestions
O no please.
I follow method one, I get succes message and now my wifi refuses to turn on. WTF
Update 2:
Now Im screwed. I tried to install another recover with Rom Manager and now phone refuses to turn on.
Something is detected in the pc while conecting it but I have only a black screen
Please what can I do??
ErnestoD said:
Hey
Yesterday I flash CM11 over stock 4.1.2 on my Optimus G (E975) and later decided to go back to stock again.
Everything was done witouht problems using nand back up with CWM
But later I realiced that M5 was out and, once again tried to install it but I couldnt
Dont know what happen but now while device is turning on, or trying to go into recovery or dowload mode screen is BLACk.
Device is working properly, I mean I turn it off/on and no problem. Just cant enter fastboot, recovery or download mode.
I tried a couple method to go back to stock using KDZ but proceess stop and nothing, just keep pressing power buttom and phone reboot (just black screen during the process)
Please, any ideas/suggestions
O no please.
I follow method one, I get succes message and now my wifi refuses to turn on. WTF
Update 2:
Now Im screwed. I tried to install another recover with Rom Manager and now phone refuses to turn on.
Something is detected in the pc while conecting it but I have only a black screen
Please what can I do??
Click to expand...
Click to collapse
have you tried TeenyBin http://forum.xda-developers.com/showthread.php?t=2249500
Yes but I could solve that problem now.
One thing I learned: I will never install a custom rom on my OG. I had several devices before this one and always with custom roms. But with LG there are so many risks and problems to perform needed actions
Thanks
umar_fiaz said:
have you tried TeenyBin http://forum.xda-developers.com/showthread.php?t=2249500
Click to expand...
Click to collapse
ErnestoD said:
Yes but I could solve that problem now.
One thing I learned: I will never install a custom rom on my OG. I had several devices before this one and always with custom roms. But with LG there are so many risks and problems to perform needed actions
Thanks
Click to expand...
Click to collapse
very true. iv learned the lesson too..it was risky to install stock back
its not a cheap phone after all..moreover stock roms are the best ones. u wont get those features n qlides etc in custom
It appears to be that certain functions are sensitive to low power states.
Without downloading the fauxclock app, I took out the SIM from the phone. This allows the phone to work well enough without crashing due to the modem being initialized in a low power state.
Got into performance and set the minimum clock at 1000MHz (for now).
Phone works again.
Recovery mode only
Hello,
I have F180L, I upgraded it to 4.4.2 kitkat then rooted it with freegee and installed cwm via freegee. then booted into recovery and installed Sling 2.2 kitkat. every thing was working great until I factory reset the phone. Now, the phone is stuck in cwm. It starts and boots into cwm . even if I turn off the phone and plug in the power, the phone boots in cwm. it is not even charging because of the led light which is always on in cwm. I have tried everything but nothing is happening ....
someone plz help me and suggest me something to charge and unbrick my phone
Recovery mode only
w8ing for reply...
someone help me please
solution
farhan.ahmed said:
w8ing for reply...
someone help me please
Click to expand...
Click to collapse
1st try to get in download mode..hope u know how to get into download mode.
there is some key combination
vol up+insert cable
yogivin said:
1st try to get in download mode..hope u know how to get into download mode.
there is some key combination
vol up+insert cable
Click to expand...
Click to collapse
I have installed teenybins now I have fastboot and twrp recovery but when i use install zip from sd card, it gives me error E: Can`t mount /sdcard. when i try adb sideload, it show an error can`t read xxx.zip
I need tot and dll files for F180L to try LGNPST
please help me
farhan.ahmed said:
I have installed teenybins now I have fastboot and twrp recovery but when i use install zip from sd card, it gives me error E: Can`t mount /sdcard. when i try adb sideload, it show an error can`t read xxx.zip
I need tot and dll files for F180L to try LGNPST
please help me
Click to expand...
Click to collapse
i dont think there is any need for teenybins n etc
jus try to get into download mode and thn try this link
http://forum.xda-developers.com/showthread.php?p=53659718#post53659718
I read this thread many times over before unlocking my T-Mobile M919 and Metro M919N Galaxy S4 smartphones. http://forum.xda-developers.com/showthread.php?t=2283068
Both phones were on Android 4.4.4 when I got them and the newer, revised method linked above near the end of the thread scared the crap out of me with its "ERASE EFS 1/2/3."
The original method would no longer be possible as most people's phones are updated past the OP's firmware version and the 4.4.4 bootloaders can not be downgraded past 4.4.2. I unlocked both of my phones by doing the following.
1) downgraded both to T-Mobile 4.4.2 firmware TMB-M919UVUFNB4-20140314115123-v4.4.2 Both phones can run either Metro or T-Mobile firmware. I rooted both phones.
2) downgraded the modems to MDL and shutdown the phones.
3) ran Region Lockaway and rebooted.
4) Used the original steps in the thread linked above.
Here they are with a tweak or two
"Goto phone dailer, and enter *#27663368378# for the debug service menu. ( I used the *#0011# dialing method, chose "key input" with the left menu key and then entered 1 and ok and waited 15 seconds. You can also use the "PhoneINFO Samsung" app on the PlayStore if you root your phone before accessing the service menu)
In "ServiceMode", select [1] UMTS
In "UMTS MAIN MENU", select [1] DEBUG SCREEN
In "DEBUG SCREEN", select [6] PHONE CONTROL
In "PHONE CONTROL", select [6] NETWORK LOCK
In "NETWORK LOCK", select [3] PERSO SHA256 OFF
It should show:
SHA256_ENABLED_FLAG[1]
SHA256_OFF => SHA256_ON
Now touch the first line SHA256_ENABLED_FLAG[1]
It should show:
MENU NOT EXIST
PRESS BACK KEY
Current Command is 116631
Now press the menu button and select "Back"
It should show:
SHA256_ENABLED_FLAG[0]
SHA256_OFF => Not Change
Again, press the menu button and select "Back", and you're back in the "NETWORK LOCK" screen
Press the menu button and select "Back", and you're in the "PHONE CONTROL" screen
Press the menu button and select "Back", and you're in the "DEBUG SCREEN" screen
Finally, press the menu button and select "Back", and you're back in the "UMTS MAIN MENU" screen
Select [6] COMMON
In "COMMON" screen, select [6] NV REBUILD
Now you are in the "NV REBUILD" screen, you should see the following text:
------------------------------
Golden-Backup exist
You can Restore Cal/NV
------------------------------
Now for the final step.
In "NV REBUILD" screen, select [4] Restore Back-up
The button lights for menu and back should come on, and the phone will auto reboot in a few seconds."
After rebooting, I ran Region Lock Away again and shut down. I inserted AT&T sim cards in both phones. I cold booted both. Upon reaching the home screens, I immediately saw AT&T in the top left corner and 4G to the right with five bars of signal strength.
I upgraded both phones back to their 4.4.4 firmwares, rooted them again, and ran Region Lock Away again. (Remember, Region Lock Away says that it is writing to the modem)
Both phones were still domestically unlocked and worked perfectly.
Why downgrade the firmware to 4.4.2? When I downgraded just modems and not the 4.4.4 firmware, the phones were sluggish and the service menu would crash or the phone would simply not respond to anything. Downgrading the modem firmware to an earlier version than the 4.4.2's NB4 modem worked perfectly.
There may be other ways to do this, but my method is much less risky that the newer method posted in the thread I referred to. Is the Region Lock Away necessary so many times? I can not be certain, but my method worked PERFECTLY on two phones side by side. I would not erase my EFS info regardless of if I had a backup or not.
Good Luck.........
Unlock procedure works
I can verify that this procedure works. Thanks! Although I spent most of the day trying because this temperamental M919 refused to be flashed by the laptop that I use for all my flashing, I got it to work by flashing it with my desktop.
jsdad said:
I can verify that this procedure works. Thanks! Although I spent most of the day trying because this temperamental M919 refused to be flashed by the laptop that I use for all my flashing, I got it to work by flashing it with my desktop.
Click to expand...
Click to collapse
I was able to flash within my Windows 8 hard drive but not my Windows 7 one. I do not get it. Same brands of hard drives, drivers, everything. I had KIES on neither machine, nothing. One worked and one did not.
Well, I followed a very similar XDA thread to SIM unlock the M919. It also involved downgrading from 4.4.4 to 4.2. I successfully unlocked my device! But now I have no Wifi... I tried flashing every single modem, every firmware (Official TW ones via Odin, every custom rom using TWRP). They flashed well and everything worked besides the Wifi. I've found some threads from people with the exact same problem (they tried to unlock it using the same method) but those are old threads with no solution.
I've spent 24hrs reading and flashing and wiping and reading again. Any ideas? Will send $20 on Paypal if you find me a solution!
Thank you.
domenicostorino said:
Well, I followed a very similar XDA thread to SIM unlock the M919. It also involved downgrading from 4.4.4 to 4.2. I successfully unlocked my device! But now I have no Wifi... I tried flashing every single modem, every firmware (Official TW ones via Odin, every custom rom using TWRP). They flashed well and everything worked besides the Wifi. I've found some threads from people with the exact same problem (they tried to unlock it using the same method) but those are old threads with no solution.
I've spent 24hrs reading and flashing and wiping and reading again. Any ideas? Will send $20 on Paypal if you find me a solution!
Thank you.
Click to expand...
Click to collapse
Anyone, please?
Curious my friend Have you tried M919UNANB1 for Tmobile it is included in The Sickness' s INSANE KIT KAT VII, works well wifi occasionally messes up if you don't clear your ram and cache and bog the system down
Thank you my T-mo M919 was unlocked relatively easy
1. Root my m919 FOK3 with cf-root https://autoroot.chainfire.eu/
2. Flash Only the MDL modem.bin http://forum.xda-developers.com/showpost.php?p=54672654&postcount=15
3. Ran Region Lock Away http://forum.xda-developers.com/showthread.php?t=2470551 and select Reboot and Now is Unlock
4. Restore My Original Modem.bin Flash from here http://forum.xda-developers.com/showpost.php?p=64613889&postcount=160
5. And That´s all
gatonico said:
Thank you my T-mo M919 was unlocked relatively easy
1. Root my m919 FOK3 with cf-root https://autoroot.chainfire.eu/
2. Flash Only the MDL modem.bin http://forum.xda-developers.com/showpost.php?p=54672654&postcount=15
3. Ran Region Lock Away http://forum.xda-developers.com/showthread.php?t=2470551 and select Reboot and Now is Unlock
4. Restore My Original Modem.bin Flash from here http://forum.xda-developers.com/showpost.php?p=64613889&postcount=160
5. And That´s all
Click to expand...
Click to collapse
Worked for me on M919UVUFNK2 4.4.4 :good::good:
BarakOsama said:
Worked for me on M919UVUFNK2 4.4.4 :good::good:
Click to expand...
Click to collapse
Worked for me also on NH7 4.4.4 :good:
Sent from my SGH-M919 using XDA-Developers mobile app
Thanks you, this is way easier then the other method. & works of course.
gatonico said:
Thank you my T-mo M919 was unlocked relatively easy
1. Root my m919 FOK3 with cf-root https://autoroot.chainfire.eu/
2. Flash Only the MDL modem.bin http://forum.xda-developers.com/showpost.php?p=54672654&postcount=15
3. Ran Region Lock Away http://forum.xda-developers.com/showthread.php?t=2470551 and select Reboot and Now is Unlock
4. Restore My Original Modem.bin Flash from here http://forum.xda-developers.com/showpost.php?p=64613889&postcount=160
5. And That´s all
Click to expand...
Click to collapse
Direct link to chainfire root method.
http://forum.xda-developers.com/showthread.php?t=2294005
Odin3 v3.07 (has the "PHONE" selection)
https://mega.nz/#!apJjlSIK!k3gaM7XCj_td_Kc7jF2EPERIjcv61M-4gOwkgVD0Uqc
Direct link to UVUAMDL Bandbase/modem
http://forum.xda-developers.com/showthread.php?t=2282342
OK3 Bandbase/modem
https://mega.nz/#!bkwU3K5I!BiXPAPVsWab77x0US-E8xqgC2x1dHv08H-F2oNuhLXA
FOh3 Bandbase/modem
https://mega.nz/#!bgJFXbKB!vuNAbaAJa--lkvJ2H-T5ZjKMqp4jnxk-kd3B1fs0qKU
trying this ans is not working for me, what possibly am I doing wrong?
CSC error w/ custom ROM
RegionAway is giving me a CSC error, but I have a custom ROM installed. Downloading stock firmware, will flash that and try again. THANKS
Issue
jmacguire said:
I read this thread many times over before unlocking my T-Mobile M919 and Metro M919N Galaxy S4 smartphones. http://forum.xda-developers.com/showthread.php?t=2283068
Both phones were on Android 4.4.4 when I got them and the newer, revised method linked above near the end of the thread scared the crap out of me with its "ERASE EFS 1/2/3."
The original method would no longer be possible as most people's phones are updated past the OP's firmware version and the 4.4.4 bootloaders can not be downgraded past 4.4.2. I unlocked both of my phones by doing the following.
1) downgraded both to T-Mobile 4.4.2 firmware TMB-M919UVUFNB4-20140314115123-v4.4.2 Both phones can run either Metro or T-Mobile firmware. I rooted both phones.
2) downgraded the modems to MDL and shutdown the phones.
3) ran Region Lockaway and rebooted.
4) Used the original steps in the thread linked above.
Here they are with a tweak or two
"Goto phone dailer, and enter *#27663368378# for the debug service menu. ( I used the *#0011# dialing method, chose "key input" with the left menu key and then entered 1 and ok and waited 15 seconds. You can also use the "PhoneINFO Samsung" app on the PlayStore if you root your phone before accessing the service menu)
In "ServiceMode", select [1] UMTS
In "UMTS MAIN MENU", select [1] DEBUG SCREEN
In "DEBUG SCREEN", select [6] PHONE CONTROL
In "PHONE CONTROL", select [6] NETWORK LOCK
In "NETWORK LOCK", select [3] PERSO SHA256 OFF
It should show:
SHA256_ENABLED_FLAG[1]
SHA256_OFF => SHA256_ON
Now touch the first line SHA256_ENABLED_FLAG[1]
It should show:
MENU NOT EXIST
PRESS BACK KEY
Current Command is 116631
Now press the menu button and select "Back"
It should show:
SHA256_ENABLED_FLAG[0]
SHA256_OFF => Not Change
Again, press the menu button and select "Back", and you're back in the "NETWORK LOCK" screen
Press the menu button and select "Back", and you're in the "PHONE CONTROL" screen
Press the menu button and select "Back", and you're in the "DEBUG SCREEN" screen
Finally, press the menu button and select "Back", and you're back in the "UMTS MAIN MENU" screen
Select [6] COMMON
In "COMMON" screen, select [6] NV REBUILD
Now you are in the "NV REBUILD" screen, you should see the following text:
------------------------------
Golden-Backup exist
You can Restore Cal/NV
------------------------------
Now for the final step.
In "NV REBUILD" screen, select [4] Restore Back-up
The button lights for menu and back should come on, and the phone will auto reboot in a few seconds."
After rebooting, I ran Region Lock Away again and shut down. I inserted AT&T sim cards in both phones. I cold booted both. Upon reaching the home screens, I immediately saw AT&T in the top left corner and 4G to the right with five bars of signal strength.
I upgraded both phones back to their 4.4.4 firmwares, rooted them again, and ran Region Lock Away again. (Remember, Region Lock Away says that it is writing to the modem)
Both phones were still domestically unlocked and worked perfectly.
Why downgrade the firmware to 4.4.2? When I downgraded just modems and not the 4.4.4 firmware, the phones were sluggish and the service menu would crash or the phone would simply not respond to anything. Downgrading the modem firmware to an earlier version than the 4.4.2's NB4 modem worked perfectly.
There may be other ways to do this, but my method is much less risky that the newer method posted in the thread I referred to. Is the Region Lock Away necessary so many times? I can not be certain, but my method worked PERFECTLY on two phones side by side. I would not erase my EFS info regardless of if I had a backup or not.
Good Luck.........
Click to expand...
Click to collapse
Hi all,
Could you please help me somebody? I have done the SW downgrade atfer that my phone wasn't work. The T-MOBILE 4GLTE logos was freezen. What was the problem?
I kingo rooted my S4 lol. Then did a reset to get the Phish out.
So guys, bought this phone used 3 days ago. The phone was rooted and the fingerprint scanner was not working giving some error. So I decided to get the phone returned back to stock.
I flashed the G925TUVU3DOJ7_G925TTMB3DOJ7_G925TUVU3DOJ7_HOME.tar file via odin 3.10.6. All files were successfully flashed with pass message but now i am stuck on the boot screen at s6 edge logo. I did a factory reset and wiped the cache but no luck.
The recovery shows an error of dm-verity verification failed... as well in the bottom. I can get the phone in download mode. The current binary is samsung official but in system status it still says Custom. I tried flashing G925TUVU2COF6_G925TTMB2COF6_G925TUVU2COF6_HOME.tar but it doesn't let me flash it as I read i cannot downgrade.
I have tried searching at different places but couldn't seem to find any appropriate solution as most of them are for cof6 or cof8 firmware. I would appreciate a lot if someone could guide me step-by-step procedure to get my phone working back.
Note: I think that the phone IMEI was also repaired as the IMEI on back glass and in the system does not match.
I also cannot get any assistance from t-mobile as I live in Pakistan. I could not attach shots as i have less than 10 posts so writing the status:
In download mode:
PRODUCT NAME: SM-G925T
CURRENT BINARY: Samsung Official
SYSTEM STATUS: Custom
FRP LOCK: OFF
Secure Download: Enabled
KNOX WARRANTY VOID: 1 (0x0301)
AP SWREV: B:3 K:2 S:2
Recovery error at the bottom:
dm-verity verification failed. . .
Need to check DRK first. . .
It sounds like there may be an issue with your IMEI. I think you should try and use Smart Switch on your PC to do an emergency recovery. It will completely wipe the phone and reset everything to how it should be.
Emergency recovery requires the serial number in order to proceed. You can get that by going into Download mode but before you hit Vol Up to continue hit Home instead. It will show IMEI and Serial Number (the bottom number).
Samsung Smart Switch for PC can be downloaded from Here. Install Smart Switch. Start up Smart Switch and click more in upper right corner. If you don't have the Samsung drivers installed you can install them from here. Or if you would like to reinstall them.
After you are done with drivers connect your phone to the PC and click more and click "Emergency software recovery and initialization" (the first option). It should ask for your serial number. enter it and it should start doing it's thing.
Hopefully this works for you and good luck.
Thanks for the fast reply. I flashed it using the smart switch software. The program completed successfully but still the same result. Stuck at boot logo and same dm-verity error in recovery
DM Verity Verification failed
muhsaad said:
Thanks for the fast reply. I flashed it using the smart switch software. The program completed successfully but still the same result. Stuck at boot logo and same dm-verity error in recovery
Click to expand...
Click to collapse
Hello , if you still facing this issue after flash full stock
try to write unikernel v8-002 (remember FRP LOCK = OFF )
It must work ,
i am sure after flash Unikernel is will work
post result if not work
Thanks alot @jayshaa. Finally booted up... Hats off to you man...!! :good:
Sorry to disturb again... Today when I restart the phone, I couldn't pass the boot screen as I gave me the error Custom Binary blocked by FRP Lock. Frp lock turned on automatically and now I am again stuck at the boot screen. I again flashed the stock rom but the frp lock is still on. I couldn't flash the kernal as well because of this lock.
Someone please guide me to turn this frp lock off and get my phone working again.
Need to check DRK first. .
This error means at some point your efs probably was wiped meaning the drk was wiped... unless this is fixed the phone will boot loop everytime you update unless you flash a modified kernel...
So how do I fix that or turn frp lock off?
Anyone???
muhsaad said:
Sorry to disturb again... Today when I restart the phone, I couldn't pass the boot screen as I gave me the error Custom Binary blocked by FRP Lock. Frp lock turned on automatically and now I am again stuck at the boot screen. I again flashed the stock rom but the frp lock is still on. I couldn't flash the kernal as well because of this lock.
Someone please guide me to turn this frp lock off and get my phone working again.
Click to expand...
Click to collapse
That can only be turned off via Developer Options in Settings. If you flashed a custom kernel then you cannot turn it off because you will boot loop. You must flash stock kernel. Or just reflash the stock firmware package.
After you get back to stock. get to developer options and turn off the FRP lock. Then you can flash away.
Hi, I flash my samsung s6 edge + G928T using the files for Misterjunky that I thanks a lot, and my phone was very good. But now I forgot to diseable the oem lock and i reset it. the phone ask me now the last user account, but when I buy the phone, i hadn't put a google account there. I flash it because it was a costum rom and I wanted an official.
Now I want to know how can I found the last user account whitch block my frp, and then I will go to where I buy the phone and try to found the password and reset my phone. The seller says me that he haven't put an account there, even if it was there when he clean it, normally I will not got a frp lock problem, but if I can know whitch google account was there maybe he can remember to the password and help me to resolve my problem.
Thanks a lot.
Sorry for my bad english
re: OEM lock
Amir Tech said:
Hi, I flash my samsung s6 edge + G928T using the files for Misterjunky that I thanks a lot, and my phone was very good. But now I forgot to diseable the oem lock and i reset it. the phone ask me now the last user account, but when I buy the phone, i hadn't put a google account there. I flash it because it was a costum rom and I wanted an official.
Now I want to know how can I found the last user account whitch block my frp, and then I will go to where I buy the phone and try to found the password and reset my phone. The seller says me that he haven't put an account there, even if it was there when he clean it, normally I will not got a frp lock problem, but if I can know whitch google account was there maybe he can remember to the password and help me to resolve my problem.
Thanks a lot.
Sorry for my bad english
Click to expand...
Click to collapse
You should have NEVER disable the OEM Unlock.
It should always remain ENABLED even if you
upgrade firmware or flash a new or different rom.
After flashing any custom roms the phone will never
display "Official", usually it will display "unknown".
The thing you need to do to fix the problem is:
#1: Be sure you have Odin v3.10.7 ready to use. (other versions may not be fully compatible)
#2: Download the official Samsung G928T TAR firmware (unless you already have it)
#3: Open Odin and put the official firmware tar file into Odin's AP slot.
#4: Put the phone into "download" mode.
#5: Connect USB cable from phone to your computer.
#6: Be sure Odin recognizes your phone (com:xx should light up)
#7: Don't change any options in Odin
#8: Click START in odin and wait until it's done flashing and rebooting the phone.
If you have done all 8 steps correctly, your phone will reboot and work properly.
If it's not working properly after it reboots then go into the phone's stock recovery
mode and do a "factory data reset" then when it reboots everything should be fine.
Good luck,
Have a very Merry Christmas!
Greetings,
I have a certain problem, i have an Samsung J6 Plus which has suddenly rebooted and since then it just turns on the samsung logo, then it turns off the screen, then the screen flashes and finally it reboots again.
I have tried everything, the phone has a pie binary so i could only flash one rom i found.
But even after flashing every part of OS on its own, performing a NAND Erase and re-partitioning with pit file, i still get the same result. The phone restarts after the flash, and then turns off the screen, flashes etc...
Every time the same, no matter what i try.
Has anyone experienced similar problem ?
I have read about 15 of other threads here with similar problems and tried every solution that works for some people but nothing works for me.
stefan1301 said:
Greetings,
I have a certain problem, i have an Samsung J6 Plus which has suddenly rebooted and since then it just turns on the samsung logo, then it turns off the screen, then the screen flashes and finally it reboots again.
I have tried everything, the phone has a pie binary so i could only flash one rom i found.
But even after flashing every part of OS on its own, performing a NAND Erase and re-partitioning with pit file, i still get the same result. The phone restarts after the flash, and then turns off the screen, flashes etc...
Every time the same, no matter what i try.
Has anyone experienced similar problem ?
I have read about 15 of other threads here with similar problems and tried every solution that works for some people but nothing works for me.
Click to expand...
Click to collapse
You shouldn't have used the nand erase option, that is an easy way to brick the device when used improperly. I doubt you will be able to repair it with Odin now.
Sent from my SM-S767VL using Tapatalk
Droidriven said:
You shouldn't have used the nand erase option, that is an easy way to brick the device when used improperly. I doubt you will be able to repair it with Odin now.
Sent from my SM-S767VL using Tapatalk
Click to expand...
Click to collapse
But, you see, i did it as a last option, because i tried to flash several different roms before that, and at first it didn’t let me flash Oreo and older, just failed in odin, because of Pie binary.
So i flashed official pie ( first time only AP, and second time all files), and it didn’t help either, the phone was still acting the same (the same thinh happens like before all the flashing).
I can’t boot into recovery, it ends up being the same as trying to boot normally, and it won’t let me flash other recovery because of the frp.
stefan1301 said:
But, you see, i did it as a last option, because i tried to flash several different roms before that, and at first it didn’t let me flash Oreo and older, just failed in odin, because of Pie binary.
So i flashed official pie ( first time only AP, and second time all files), and it didn’t help either, the phone was still acting the same (the same thinh happens like before all the flashing).
I can’t boot into recovery, it ends up being the same as trying to boot normally, and it won’t let me flash other recovery because of the frp.
Click to expand...
Click to collapse
Sounds to me like the hardware itself is bricked or damaged. If that is the case, the only option is to replace the motherboard.
Sent from my SM-S767VL using Tapatalk
Try to flash latest rom
Here is the solution
stefan1301 said:
Greetings,
I have a certain problem, i have an Samsung J6 Plus which has suddenly rebooted and since then it just turns on the samsung logo, then it turns off the screen, then the screen flashes and finally it reboots again.
I have tried everything, the phone has a pie binary so i could only flash one rom i found.
But even after flashing every part of OS on its own, performing a NAND Erase and re-partitioning with pit file, i still get the same result. The phone restarts after the flash, and then turns off the screen, flashes etc...
Every time the same, no matter what i try.
Has anyone experienced similar problem ?
I have read about 15 of other threads here with similar problems and tried every solution that works for some people but nothing works for me.
Click to expand...
Click to collapse
I'm having the same issue after oreo update for j7 nxt so what i did is easily rooting phone via Magisk!
Ahh,, maybe u have frp lock?
Just google for (Combination rom of your device) then flash it with odin. After that you can go to settings -> about device -> software information -> Build number (click on this option 5-7 times).
Then back to settings you'll see an additiona setting (Developer options) go inside it and click on (OEM unlocking) and cograts you have unlocked frp lock
Note : there is a fairly chance that you won't find this option (OEM unlocking)! So what to do? You just need to trick the phone by changing the date/time for 2014 and restart then check if it's there if still not there just try again with different dates for ex. 2013 and restart (keep doind this and every restart check the developer options section, Just KEEP TRY!! until you find the button there in developer options
After that go flash the stock rom then install TWRP then ROOT via Magisk and you're all done
alaanhaliko said:
I'm having the same issue after oreo update for j7 nxt so what i did is easily rooting phone via Magisk!
Ahh,, maybe u have frp lock?
Just google for (Combination rom of your device) then flash it with odin. After that you can go to settings -> about device -> software information -> Build number (click on this option 5-7 times).
Then back to settings you'll see an additiona setting (Developer options) go inside it and click on (OEM unlocking) and cograts you have unlocked frp lock
Note : there is a fairly chance that you won't find this option (OEM unlocking)! So what to do? You just need to trick the phone by changing the date/time for 2014 and restart then check if it's there if still not there just try again with different dates for ex. 2013 and restart (keep doind this and every restart check the developer options section, Just KEEP TRY!! until you find the button there in developer options
After that go flash the stock rom then install TWRP then ROOT via Magisk and you're all done
Click to expand...
Click to collapse
OEM unlock does not "by itself" remove FRP, there is more to the process than just enabling OEM unlock, removing the Google account from the device and disabling MDM(find my device) is what actually "unlocks" FRP.
https://blog.elcomsoft.com/2016/05/understanding-and-bypassing-reset-protection/
Sent from my SM-S767VL using Tapatalk
Droidriven said:
OEM unlock does not "by itself" remove FRP, there is more to the process than just enabling OEM unlock, removing the Google account from the device and disabling MDM(find my device) is what actually "unlocks" FRP.
Sent from my SM-S767VL using Tapatalk
Click to expand...
Click to collapse
Since he didn't mention about getting this message "only official binaries are allowed to be flashed"
Then itsn't something related to RMM.
Also as what he said he can't flash TWRP as he gets "OEM LOCK" it's also called "FRP LOCK" the type of lock i'm talking about is in (download mode) that doesn't allow to install custom binaries, so the only solution is tirning (OEM lock) option and that's enough to flash custom binaries such as TWRP.
The type you are talking about seems to be RMM lock which could be fixed using Miracle Box but as it's not allowed to dicuss this stuff here in xda + his problem is frp locked and phone doesn't booting, so the only solution we can provide in this situation is Combination rom which will boot even if you bricked your phone, even if you've Rooted and bricked your device's kernel (even if it won't boot anymore).. combination should boot, i faced the exact issue but as i explained in my last post. And hmm it could be 80% the solution.
Thank for your reply.
Your Iraqi friend,
My regards.
alaanhaliko said:
Since he didn't mention about getting this message "only official binaries are allowed to be flashed"
Then itsn't something related to RMM.
Also as what he said he can't flash TWRP as he gets "OEM LOCK" it's also called "FRP LOCK" the type of lock i'm talking about is in (download mode) that doesn't allow to install custom binaries, so the only solution is tirning (OEM lock) option and that's enough to flash custom binaries such as TWRP.
The type you are talking about seems to be RMM lock which could be fixed using Miracle Box but as it's not allowed to dicuss this stuff here in xda + his problem is frp locked and phone doesn't booting, so the only solution we can provide in this situation is Combination rom which will boot even if you bricked your phone, even if you've Rooted and bricked your device's kernel (even if it won't boot anymore).. combination should boot, i faced the exact issue but as i explained in my last post. And hmm it could be 80% the solution.
Thank for your reply.
Your Iraqi friend,
My regards.
Click to expand...
Click to collapse
No, I'm talking specifically of FRP lock.
The point you make about binaries has nothing to do with FRP. Binaries can be blocked on both FRP locked and FRP unlocked devices. The binaries only prevent flashing firmware with a lower binary than the current binary installed on the device. Binary version is related to RMM or KG state, not FRP. FRP is directly related to MDM and only "partially" related to the things you mention and only because there are other "tamper-proof" elements that "can" trigger FRP. Have you ever noticed that a device that does not have a Google account signed in does not encounter FRP issues when the device is factory reset, but if there is a Google account signed in the device, factory reset triggers FRP? If it were as you you seem to be suggesting, FRP would be triggered on devices that have no Google account associated to them when attempting to flash/modify the device, but this is not what happens.
OEM unlock really only applies to unlocking bootloader in order to flash unapproved software or make modifications to the system partition without being blocked.
https://blog.elcomsoft.com/2016/05/understanding-and-bypassing-reset-protection/
Sent from my SM-S767VL using Tapatalk