Do not know what I did right
SD file transfer
Do
Command
Su
Sync
Reboot recovery
I pressed install file is shown getting error
Why?
CM11 is in alpha. You must expect a brick if something goes wrong.
And (no offense) from that you wrote, you don't seem to know how to restore a brick.
My recommendation is not to try it!!
Also, isn't one post enough for your problem?!
Sent from my D620R [Stock 4.4.2]
Vagelis1608 said:
CM11 is in alpha. You must expect a brick if something goes wrong.
And (no offense) from that you wrote, you don't seem to know how to restore a brick.
My recommendation is not to try it!!
Also, isn't one post enough for your problem?!
Sent from my D620R [Stock 4.4.2]
Click to expand...
Click to collapse
Hahaha do not understand what you record
Just realized that trying to install it.. why?
The stock recovery not install CM11 need to flash CWM or TWRP. To do this, first unlock the bootloader. Here is the topic http://forum.xda-developers.com/g2-mini/development/bootloader-unlock-t2827748
Vagelis1608 said:
CM11 is in alpha. You must expect a brick if something goes wrong.
And (no offense) from that you wrote, you don't seem to know how to restore a brick.
My recommendation is not to try it!!
Also, isn't one post enough for your problem?!
Sent from my D620R [Stock 4.4.2]
Click to expand...
Click to collapse
Using CM11 from 09.08.2014 and I have no problem with it. Rom a lot better and smoother than stock
eta82 said:
Using CM11 from 09.08.2014 and I have no problem with it. Rom a lot better and smoother than stock
Click to expand...
Click to collapse
He obviously doesn't know what to do if anything goes wrong (no offense).
If he bricks his phone, it's his responsibility, not ours!
Sent from my D620R [Stock 4.4.2]
Vagelis1608 said:
He obviously doesn't know what to do if anything goes wrong (no offense).
If he bricks his phone, it's his responsibility, not ours!
Sent from my D620R [Stock 4.4.2]
Click to expand...
Click to collapse
You're right. It's not our problem if you decide to take this step and unlock the bootloader must reckon with the possibility to brick your phone. On this subject is mentioned in the subject line phone unlock and flash CWM so I guess is aware of what they are reading
eta82 said:
You're right. It's not our problem if you decide to take this step and unlock the bootloader must reckon with the possibility to brick your phone. On this subject is mentioned in the subject line phone unlock and flash CWM so I guess is aware of what they are reading
Click to expand...
Click to collapse
You say my phone can be brick... brick I do not know what it is but I guess it lock Cell Phones
http://forum.xda-developers.com/g2-mini/development/bootloader-unlock-t2827748
What's this? I need to do this?
You can return to its former wonder anyway? Reset?
I just want step by step how to install it did not confuse me
Or, should you? http://forum.xda-developers.com/g2-mini/development/rom-pac-rom-lg-g2-mini-d620-alpha-t2876820
http://forum.xda-developers.com/g2-mini/development/bootloader-unlock-t2827748
How do I install this example TWRP-d620.img
What do I do with this file?
I have ADB
There are all [=
Just what to do where to start an application I beg help me
Write me step by step how to do this request
You can also talk to me on Skype haimmalka85
haimmalka said:
You say my phone can be brick... brick I do not know what it is but I guess it lock Cell Phones
http://forum.xda-developers.com/g2-mini/development/bootloader-unlock-t2827748
What's this? I need to do this?
You can return to its former wonder anyway? Reset?
I just want step by step how to install it did not confuse me
Or, should you? http://forum.xda-developers.com/g2-mini/development/rom-pac-rom-lg-g2-mini-d620-alpha-t2876820
Click to expand...
Click to collapse
This means that you can spoil your phone. Already it does not run, it will be worthless :crying:
But if you're not afraid to lose a few $ no to help these subjects
http://forum.xda-developers.com/g2-mini/development/bootloader-unlock-t2827748
http://forum.xda-developers.com/g2-mini/development/recovery-testing-lg-g2-mini-d620-t2835276
If you do not understand what it says forsake activities
Try it on your own risk
and once you decide to unlock the bootloader then flash CWM then download CM11 upload on SD back up the rom and flash Cm11 in CWM
eta82 said:
This means that you can spoil your phone. Already it does not run, it will be worthless :crying:
But if you're not afraid to lose a few $ no to help these subjects
http://forum.xda-developers.com/g2-mini/development/bootloader-unlock-t2827748
http://forum.xda-developers.com/g2-mini/development/recovery-testing-lg-g2-mini-d620-t2835276
If you do not understand what it says forsake activities
Try it on your own risk
and once you decide to unlock the bootloader then flash CWM then download CM11 upload on SD back up the rom and flash Cm11 in CWM
Click to expand...
Click to collapse
I understand ..
You send me a link
I went not understand what to do
I explain I consumed
Give me a direction where to start
This material misunderstood me explain a little request briefed
haimmalka said:
I understand ..
You send me a link
I went not understand what to do
I explain I consumed
Give me a direction where to start
This material misunderstood me explain a little request briefed
Click to expand...
Click to collapse
First Unlock the bootloader of this guidance document http://forum.xda-developers.com/g2-mini/development/bootloader-unlock-t2827748 editing aboot.img own or use this with attachet
Next flash CWM http://forum.xda-developers.com/g2-mini/development/recovery-testing-lg-g2-mini-d620-t2835276
in terminal emulator enter a command
su
reboot recovery to enter CWM
next use CWM to flash CM11
eta82 said:
First Unlock the bootloader of this guidance document http://forum.xda-developers.com/g2-mini/development/bootloader-unlock-t2827748 editing aboot.img own or use this with attachet
Next flash CWM http://forum.xda-developers.com/g2-mini/development/recovery-testing-lg-g2-mini-d620-t2835276
in terminal emulator enter a command
su
reboot recovery to enter CWM
next use CWM to flash CM11
Click to expand...
Click to collapse
Thanks for attempting to help
http://forum.xda-developers.com/g2-mini/development/bootloader-unlock-t2827748
I came here
I do not know what to do here
What this example
Get aboot.img and abootb.img:
Use "ADB SHELL" or a Terminal Emulator:
dd if = / dev / block / platform / msm_sdcc.1 / by-name / aboot of = / sdcard / aboot.img
dd if = / dev / block / platform / msm_sdcc.1 / by-name / abootb of = / sdcard / abootb.img
Open each with a hex editor.
Search for the byte chain 20 00 EB 00 00 50 FF FF E0 E3 0A
Make sure that it exists only once.
Replace the next 4 byte by DF FF FF EA.
You will get: 20 00 EB 00 00 50 E3 FF E0 FF FF FF DF 0A EA
Save aboot.img as aboot4.img and abootb.img as abootb4.img
Do it on your own risk!
Flash back unto them:
dd if = / sdcard / aboot4.img of = / dev / block / platform / msm_sdcc.1 / by-name / aboot
dd if = / sdcard / abootb4.img of = / dev / block / platform / msm_sdcc.1 / by-name / abootb
It also
What to do where to start
What actions do
http://forum.xda-developers.com/g2-mini/development/recovery-testing-lg-g2-mini-d620-t2835276
I think I give up I'm selling this instrument complicated
Request If you want to help spare 10 minutes of your time
Skype picks me together (haimmalka85) made this request, I brought up in front of you
haimmalka said:
Thanks for attempting to help
http://forum.xda-developers.com/g2-mini/development/bootloader-unlock-t2827748
I came here
I do not know what to do here
What this example
Get aboot.img and abootb.img:
Use "ADB SHELL" or a Terminal Emulator:
dd if = / dev / block / platform / msm_sdcc.1 / by-name / aboot of = / sdcard / aboot.img
dd if = / dev / block / platform / msm_sdcc.1 / by-name / abootb of = / sdcard / abootb.img
Open each with a hex editor.
Search for the byte chain 20 00 EB 00 00 50 FF FF E0 E3 0A
Make sure that it exists only once.
Replace the next 4 byte by DF FF FF EA.
You will get: 20 00 EB 00 00 50 E3 FF E0 FF FF FF DF 0A EA
Save aboot.img as aboot4.img and abootb.img as abootb4.img
Do it on your own risk!
Flash back unto them:
dd if = / sdcard / aboot4.img of = / dev / block / platform / msm_sdcc.1 / by-name / aboot
dd if = / sdcard / abootb4.img of = / dev / block / platform / msm_sdcc.1 / by-name / abootb
It also
What to do where to start
What actions do
http://forum.xda-developers.com/g2-mini/development/recovery-testing-lg-g2-mini-d620-t2835276
I think I give up I'm selling this instrument complicated
Request If you want to help spare 10 minutes of your time
Skype picks me together (haimmalka85) made this request, I brought up in front of you
Click to expand...
Click to collapse
Make a backup of the file aboot
Code:
dd if=/dev/block/platform/msm_sdcc.1/by-name/aboot of=/sdcard/aboot.img
Phone must be rooted and install busybox instal it
If you have D620r you can download the file from the first post at the bottom of the attached here you have a direct link to this file. you have to download it to your computer. Then copy the file to the phone memory (sdcard), download the terminal emulator play store and install on your phone.
OK
Next
Open terminal emulator and give root privileges type in the terminal
Code:
su
dd if=/sdcard/aboot4.img of=/dev/block/platform/msm_sdcc.1/by-name/aboot
Done
eta82 said:
Make a backup of the file aboot
Code:
dd if=/dev/block/platform/msm_sdcc.1/by-name/aboot of=/sdcard/aboot.img
Phone must be rooted and install busybox instal it
If you have D620r you can download the file from the first post at the bottom of the attached here you have a direct link to this file. you have to download it to your computer. Then copy the file to the phone memory (sdcard), download the terminal emulator play store and install on your phone.
OK
Next
Open terminal emulator and give root privileges type in the terminal
Code:
su
dd if=/sdcard/aboot4.img of=/dev/block/platform/msm_sdcc.1/by-name/aboot
Done
Click to expand...
Click to collapse
D620r
Yes it is my device
I need someone to help me guidance
Do it with me together
You can do this with me via Skype request?
dd if=/dev/block/platform/msm_sdcc.1/by-name/aboot of=/sdcard/aboot.img This stage right?
Now with I understand correctly download it aboot.img - [Click for QR Code] (2.00 MB, 234 views)
Copy it to the SD memory card!??
Copy it to the SD memory card
Then this command register
su
dd if = / sdcard / aboot4.img of = / dev / block / platform / msm_sdcc.1 / by-name / aboot
Then do what it will do?
Should be connected USB device?
Or after it copies a file can then install rom memory?
eta82 said:
Make a backup of the file aboot
Code:
dd if=/dev/block/platform/msm_sdcc.1/by-name/aboot of=/sdcard/aboot.img
Phone must be rooted and install busybox instal it
If you have D620r you can download the file from the first post at the bottom of the attached here you have a direct link to this file. you have to download it to your computer. Then copy the file to the phone memory (sdcard), download the terminal emulator play store and install on your phone.
OK
Next
Open terminal emulator and give root privileges type in the terminal
Code:
su
dd if=/sdcard/aboot4.img of=/dev/block/platform/msm_sdcc.1/by-name/aboot
Done
Click to expand...
Click to collapse
Busybox is not needed
Stock includes the dd command
Sent from my D620R [Stock 4.4.2]
Vagelis1608 said:
Busybox is not needed
Stock includes the dd command
Sent from my D620R [Stock 4.4.2]
Click to expand...
Click to collapse
I'm going nuts who can help me it has been installed properly
https://www.youtube.com/watch?v=8aRrmxCOnQ0 It's okay to do the right directory request is made?
haimmalka said:
D620r
Yes it is my device
I need someone to help me guidance
Do it with me together
You can do this with me via Skype request?
dd if=/dev/block/platform/msm_sdcc.1/by-name/aboot of=/sdcard/aboot.img This stage right?
Now with I understand correctly download it aboot.img - [Click for QR Code] (2.00 MB, 234 views)
Copy it to the SD memory card!??
Copy it to the SD memory card
Then this command register
su
dd if = / sdcard / aboot4.img of = / dev / block / platform / msm_sdcc.1 / by-name / aboot
Then do what it will do?
Should be connected USB device?
Or after it copies a file can then install rom memory?
Click to expand...
Click to collapse
what you can see on the screenshot does not have assigned permissions root is visible stamp ($) and should be (#)
# You get when you give root privileges
haimmalka said:
Then do what it will do?
Should be connected USB device?
Or after it copies a file can then install rom memory?
Click to expand...
Click to collapse
If you are using a terminal on the phone there is no need to connect the USB
eta82 said:
what you can see on the screenshot does not have assigned permissions root is visible stamp ($) and should be (#)
# You get when you give root privileges
If you are using a terminal on the phone there is no need to connect the USB
Click to expand...
Click to collapse
Before I make this Guide
https://www.youtube.com/watch?v=8aRrmxCOnQ0
I have a strange problem why it does not appear to me
??
I get this message
haimmalka said:
D620r
Yes it is my device
I need someone to help me guidance
Do it with me together
You can do this with me via Skype request?
dd if=/dev/block/platform/msm_sdcc.1/by-name/aboot of=/sdcard/aboot.img This stage right?
Now with I understand correctly download it aboot.img - [Click for QR Code] (2.00 MB, 234 views)
Copy it to the SD memory card!??
Copy it to the SD memory card
Then this command register
su
dd if = / sdcard / aboot4.img of = / dev / block / platform / msm_sdcc.1 / by-name / aboot
Then do what it will do?
Should be connected USB device?
Or after it copies a file can then install rom memory?
Click to expand...
Click to collapse
haimmalka said:
Before I make this Guide
https://www.youtube.com/watch?v=8aRrmxCOnQ0
I have a strange problem why it does not appear to me
??
I get this message
Click to expand...
Click to collapse
To access the options developers have to tap 7-10 times is an option in Settings> Info About phone> Build number
haimmalka said:
Before I make this Guide
https://www.youtube.com/watch?v=8aRrmxCOnQ0
I have a strange problem why it does not appear to me
??
I get this message
Click to expand...
Click to collapse
Google: How to activate adb
Google: Install adb in 15 seconds
Sent from my D620R [Stock 4.4.2]
Vagelis1608 said:
Google: How to activate adb
Google: Install adb in 15 seconds
Sent from my D620R [Stock 4.4.2]
Click to expand...
Click to collapse
OK I managed to figure out what to do
I'm stuck here
I did not get here just like what?
Continue?
Related
DISCLAIMER
NB Same info as in thread by dagentooboy for Galaxy S unlock, which I used on the two Galaxy S' I owned and two others. Thanks should be sent on to them
NB I have seen the thread in Galaxy S II Original Android Development but that method adds too much complication
NB Tested on my Galaxy S II International which was network locked to Three
[PHONE MUST BE ROOTED]
To check if you have Network Lock type *#7465625# into phone dialer
1. Using root explorer or adb copy nv_data.bin and the md5 sum for that file from /efs
For adb or terminal emulator type:
su
cat /efs/nv_data.bin >> /sdcard/nv_data.bin
cat /efs/nv_data.bin.md5 >> /sdcard/nv_data.bin.md5
!!Keep a backup of these files!!
2. Using a hex editor go to hex address 181468 You should see FF 01 00 00 00
In order the blocks after FF are:
Network Lock
Network Subset Lock
SP Lock
CP Lock
3. The first block after FF with 01 is the network lock. Change this to 00
4. Delete nv_data.bin and the md5 for it. Put the edited nv_data.bin on sdcard root (KEEP YOUR BACKUP)
In adb or terminal emulator:
su
rm /efs/nv_data.bin
rm /efs/nv_data.bin.md5
cat /sdcard/nv_data.bin >> /efs/nv_data.bin
chmod 755 /efs/nv_data.bin
chown radio.radio /efs/nv_data.bin || chown 1001.1001 /efs/nv_data.bin
reboot
DONE
Thank you very much for this post - I am awaiting my UK 32gig SGS2 which I believe is locked to Orange UK - rooting it then following your instructions should be fairly straight forward. I have no idea what fw version it is likely to have - all I know is that its brand new, white and 32gig.
I took the plunge from my Desire HD so fingers crossed I will be happy with my decision to change!
Thanks again for your post...
No problem. Glad it was a help. Thought it should be posted in his forum as well as the same method that worked for the SGS1 works for the SGS2.
Congrats on the purchase. You'll love the phone. Have had mine for a few weeks and it's been great.
I have spend many hours going through XDA dev forums to prepare for the arrival of the SGS2 and I am still trying to work out what ROM to go for.
I recently moved to MIUI on the Desire HD and am really enjoying the difference between this and the HTC Sense bloat. I'm hoping that the extra screen and power of the SGS2 will make me prefer this device as the Desire HD is an old but well respected bit of kit.
The SGS2 looks simple enough to root so, hopefully, over the weekend I'll get it rooted unlocked and have a rom that I can start to tinker with.
Thanks again!
---------- Post added at 05:46 PM ---------- Previous post was at 05:44 PM ----------
http://forum.xda-developers.com/showthread.php?t=1064978&page=36
Incidentally, how does your method differ from the APKs that unlock the sim on these devices?
Rooting is very easy. Just get CF_ROOT for your firmware version. Chainfire has been making the best rooting kernels.
This method lets you do it yourself. The apps work but sometimes won't depending on the phone, not really sure why tbh, but didn't work on my phone so I used this method.
DISCLAIMER
NB Same info as in thread by dagentooboy for Galaxy S unlock, which I used on the two Galaxy S' I owned and two others. Thanks should be sent on to them
NB I have seen the thread in Galaxy S II Original Android Development but that method adds too much complication
NB Tested on my Galaxy S II International which was network locked to Three
[PHONE MUST BE ROOTED]
To check if you have Network Lock type *#7465625# into phone dialer
1. Using root explorer or adb copy nv_data.bin and the md5 sum for that file from /efs
For adb or terminal emulator type:
su
cat /efs/nv_data.bin >> /sdcard/nv_data.bin
cat /efs/nv_data.bin.md5 >> /sdcard/nv_data.bin.md5
!!Keep a backup of these files!!
2. Using a hex editor go to hex address 181468 You should see FF 01 00 00 00
In order the blocks after FF are:
Network Lock
Network Subset Lock
SP Lock
CP Lock
3. The first block after FF with 01 is the network lock. Change this to 00
4. Delete nv_data.bin and the md5 for it. Put the edited nv_data.bin on sdcard root (KEEP YOUR BACKUP)
In adb or terminal emulator:
su
rm /efs/nv_data.bin
rm /efs/nv_data.bin.md5
cat /sdcard/nv_data.bin >> /efs/nv_data.bin
chmod 755 /efs/nv_data.bin
chown radio.radio /efs/nv_data.bin || chown 1001.1001 /efs/nv_data.bin
reboot
DONE
but small confusion in hex edit
my model is I9100
country uk
carrier tmobile
for me i edit this address:
2. Using a hex editor go to hex address 18145C You should see FF 01 00 00 00
In order the blocks after FF are:
Network Lock
Network Subset Lock
SP Lock
CP Lock
3. The first block after FF with 01 is the network lock. Change this to 00
Not trying to flame or anything but all I did was download a free app from the market and it did all this for me, even backed up the efs!
= What are you even doing asking whether or not you should root your phone on XDA?! =
does this work on ics??? Thanks!
davidheffernan said:
DISCLAIMER
NB Same info as in thread by dagentooboy for Galaxy S unlock, which I used on the two Galaxy S' I owned and two others. Thanks should be sent on to them
NB I have seen the thread in Galaxy S II Original Android Development but that method adds too much complication
NB Tested on my Galaxy S II International which was network locked to Three
[PHONE MUST BE ROOTED]
To check if you have Network Lock type *#7465625# into phone dialer
1. Using root explorer or adb copy nv_data.bin and the md5 sum for that file from /efs
For adb or terminal emulator type:
su
cat /efs/nv_data.bin >> /sdcard/nv_data.bin
cat /efs/nv_data.bin.md5 >> /sdcard/nv_data.bin.md5
!!Keep a backup of these files!!
2. Using a hex editor go to hex address 181468 You should see FF 01 00 00 00
In order the blocks after FF are:
Network Lock
Network Subset Lock
SP Lock
CP Lock
3. The first block after FF with 01 is the network lock. Change this to 00
4. Delete nv_data.bin and the md5 for it. Put the edited nv_data.bin on sdcard root (KEEP YOUR BACKUP)
In adb or terminal emulator:
su
rm /efs/nv_data.bin
rm /efs/nv_data.bin.md5
cat /sdcard/nv_data.bin >> /efs/nv_data.bin
chmod 755 /efs/nv_data.bin
chown radio.radio /efs/nv_data.bin || chown 1001.1001 /efs/nv_data.bin
reboot
DONE
Click to expand...
Click to collapse
simple and easy, since it took me few hour on seeking network code by using HEX-WORKSHOP, this took me just in few minutes, it's great... cheers!!!!
this is like a one click method for sim unlock S2 i9100p
http://forum.xda-developers.com/showthread.php?t=1360174
Even you can't get the unlock code - copy the patch file back, will work.
Tested with Galaxy S2 GT-i9100P
Orange UK
Thanks
Adnan
P.S. Sorry there will be few clicks
-edit and delated
sundar83 said:
DISCLAIMER
NB Same info as in thread by dagentooboy for Galaxy S unlock, which I used on the two Galaxy S' I owned and two others. Thanks should be sent on to them
NB I have seen the thread in Galaxy S II Original Android Development but that method adds too much complication
NB Tested on my Galaxy S II International which was network locked to Three
[PHONE MUST BE ROOTED]
To check if you have Network Lock type *#7465625# into phone dialer
1. Using root explorer or adb copy nv_data.bin and the md5 sum for that file from /efs
For adb or terminal emulator type:
su
cat /efs/nv_data.bin >> /sdcard/nv_data.bin
cat /efs/nv_data.bin.md5 >> /sdcard/nv_data.bin.md5
!!Keep a backup of these files!!
2. Using a hex editor go to hex address 181468 You should see FF 01 00 00 00
In order the blocks after FF are:
Network Lock
Network Subset Lock
SP Lock
CP Lock
3. The first block after FF with 01 is the network lock. Change this to 00
4. Delete nv_data.bin and the md5 for it. Put the edited nv_data.bin on sdcard root (KEEP YOUR BACKUP)
In adb or terminal emulator:
su
rm /efs/nv_data.bin
rm /efs/nv_data.bin.md5
cat /sdcard/nv_data.bin >> /efs/nv_data.bin
chmod 755 /efs/nv_data.bin
chown radio.radio /efs/nv_data.bin || chown 1001.1001 /efs/nv_data.bin
reboot
DONE
but small confusion in hex edit
my model is I9100
country uk
carrier tmobile
for me i edit this address:
2. Using a hex editor go to hex address 18145C You should see FF 01 00 00 00
In order the blocks after FF are:
Network Lock
Network Subset Lock
SP Lock
CP Lock
3. The first block after FF with 01 is the network lock. Change this to 00
Click to expand...
Click to collapse
The same for me I got 18145C and not 181468 but...Yersterday I was able to unlock it,then I uninstall the root flashing back the firmware brand A1 nad...the handy was back sim lock.Today I have done everything again,root,delated the two file,edited the bon file in line 18145C changeing 01 to 00 but...thi time nothing worked .My question is:Maybe I must delaate olsoo some .bak files?There is a different root that after,to unroot it ,I musent refash it?I think Is the falsh the problem (maybe).Any suggest?
Thank's
Helen
Thanks it work's for me with some different methode by my self.
Will this method work on any phone? I used it a few years ago on a galaxy gio, but now I need to unlock a galaxy grand prime, so I'm wondering if this is usable only on older devices. I'm asking without trying it myself because the phone in question is not mine, so I don't have it at the moment.
hi ... im trying to unlock samsung galaxy s3 sgh1747m.
i cant find the nv_data.bin file . anyone can help plz? where is this located?
in efs folder i can t see anything.
ty vm
T-Mobile Austria will remove own Locks for free.
Currently it is not success story, but may be it could helps to somebody.
I bought an old S2 with broken display as parts replacement for my phone. So, I swap mainboard and after succeed flashing of Android 7 I find out that network was locked.
S2 Spec:
Exactly similar Problem was found here.
Model > GT-I9100
Android-Version > 4.0.4
Band > I9100BOLP7
Kernel-Version > 3.0.15-1056084, [email protected]#3
Build > IMM76D.BOLPM
1. This tread does not help me, after reboot that was no Network code asked, but always shown "no SIM" instead.
2. I try this app, but it could not find any code for me.
3. I try app from Helroz and it manage to find some code, but shown me only � � � Symbols instead of the code...
4. I found this app. And after run it was saying that it could do the job for some EUR. However at the "Details" of the app I find out the MCC MNC code and check it here. I find out that it was belongs to T-Mobile Austria. After google it I found this and this FAQ. Based on last one I goes to support the via Chat. The offer me unlock code for 50 EUR, but after I point to the last FAQ, they ask me to use Web Contact to solve this issue. So, I also open a ticketed via Contact here. My point was that I bought phone on Ebay few days ago and based on information in last FAQ it should be unlocked for free. I attach screenshots of the Bills copies from Ebay and PayPal. And after 1 Hour I got an Email with Code.:laugh:
Unfortunately Phone is hanging on the "Requesting SIM Network unlock code" Message, seems I need to go back to stock Android first and try again...
At home a apply an old android 4.1.2 from Sammobile together with pit from here file was in "3 parts Firmware".
Android-Version > 4.1.2
Band > I9100BOLP9
Kernel-Version > 3.0.31-889555, [email protected] #3
Build > JZO54K:I9100WLSD
Basically if you boot directly after flash you will see password enter prompt, that"s because we are back from Android 7 to 4 and we need to boot into recovery mode and wipe everything that can be wiped under it. After this action phone will let you normally boot. During the boot I saw prompt to enter Network Lock Code. That was a time to check if it works:fingers-crossed:
After I entered code - it booted and works perfectly on Android 4.:laugh:
I will do upgrade back to the newest ROM, hope this Lock will never back.
Also I think that this tread solution could help if I knew about the lock before to flash it with Android 7, but only rooting instead.
Does this works for Samsung Galaxy Ace 3 S7275R ?
I just founded that this app work with S2 too, not just S1..
https://play.google.com/store/apps/details?id=com.helroz.galaxysunlock
Sent from my GT-I9100 using XDA Labs
no such file found ...but i have service its crazy .....any ideas? sm-g920p sprint on boost
can be work on J200F ?
I am looking around this thread has anyone seen anything on YP-GB70 or is this the same as YP-G70? It is from Korea. I guess steve's kernal is NOT compatible with this device. What Kernal / ROM is? Any suggestions
Korean YP GB70 root and non root kernels (firmware KPH)
Hello,
you can find root and non root kernels for Korean Samsung Galaxy Player YP GB70. It is flashable only over the last KPH firmware (as of March 2012). As I cannot yet post links to outside pages (new user) try to decode the URL from this:
HTTP doubledot slash slash bvlgarian dot tistory dot com slash 138
You can flash the kernels with Odin.
That's great help you can give us.
We are many from outside to buy this YP-GB70 from korea and we need support to improve our device or rearrange it.
Our "little" problem is to find the right connexion or links to the people having knowledge and tools available.
I tried the link you provide us, if right, have a look of what i got.
What item is it to open?
Anyway don't be shy with your english it is better than mine. (french I am)
Regards
I got it after several Trials (bulgarian versus bvlugarian!)
Now I have to dig in the subject. * we keep in touch.
Thanks again,
Hey
Hi, Im a Korean Galaxy Player user.(YP-GB70.)
This Root Knernel is not rooting kernel. Because, This Kernel flashed Odin, device has bricked. But, Korean Galaxy Player's Rooting Rom is appear.
(In fact, This is my custum Rom.)
I tested the "rooted kernel" it leads my device alive from KPH brick gotten after upgrade (I felt Happy). Only problem is it doesn't reconize any internal mémory as well as external SD. So anybody got that?
Anyway, send us link for any other rooting solution. you are welcome.
Korean YP GB70 root and non root kernels (firmware KPL)
Hi folks,
here are root and non root kernels for Korean Samsung Galaxy Player YP GB70. It is flashable only over the last KPL firmware (as of April 2012):
http://bvlgarian.tistory.com/320
Once you flash root kernel via ODIN and set up SUDO, you can flash back to nonroot kernel (apparently the features of root kernel are not very well implemented/maintained anymore). Even if you flash back to nonroot kernel, the device would remain rooted.
---
If you want to flash complete customized ROM for Korean GB70:
http://greenview.tistory.com/31
The *.egg archives can be decompressed by AllZip.
---
And before you start, you can temporarily flash RJ's Custom Kernel r13 for YP-GB70. This kernel has support for ClockworkMod, so you can backup your original KPL ROM to sdcard. After flashing with ODIN you can call ClockworkdMod via combination "HOME button" + "POWER button" + "Vol. Up".
The kernel is here:
http://greenview.tistory.com/attachment/[email protected]
Once you backup your ROM, you should go back to stock kernel, RJ's kernel probably wouldn't boot, it is usable only for backup/restore.
---
Note: if you don't know what you are doing, ie. if you aren't comfortable with fdisk, adb etc., you should expect some major setbacks ;-).
Many thanks for your support.
I still have the following problem to understand and to solve in order to have my device fully working.
Detail:
-When using no rooted kernel it stay in loop at Galaxy player logo for a while....
-When using rooted kernel it starts 100% but I can't access any Sd memory or USB connexion like the internal memory is not adressed.
Who knows about this issue?
Any help is appreciated.
Korean YP GB70 partition softbrick recovery
lolo9393 said:
Many thanks for your support.
I still have the following problem to understand and to solve in order to have my device fully working.
Detail:
-When using no rooted kernel it stay in loop at Galaxy player logo for a while....
-When using rooted kernel it starts 100% but I can't access any Sd memory or USB connexion like the internal memory is not adressed.
Who knows about this issue?
Any help is appreciated.
Click to expand...
Click to collapse
It looks like one or more of your partitions are damaged. Probably by setting a wrong option in ODIN. I've did that mistake and here's how to fix it with a good chance of not losing your data:
* Install root kernel via ODIN
* Start your device normally (do not put your device in DOWNLOAD mode), it's OK if it hangs.
* On your PC install Android SDK + platform tools and make sure your adb is working.
* "adb shell" to your device
* "sudo su" or "su"
* "mount -t tmpfs tmpfs /tmp"
* "exit"
* "exit"
* Get busybox binary: http://www.4shared.com/file/DffR-A0B/busybox.html
* Untar /unzip the binary
* Push the binary to your device: "adb push busybox /tmp/busybox".
Then get fdisk working:
* "adb shell" to your device
* "sudo su" or "su"
* "cd /tmp"
* "chmod 775 busybox"
* "ln -s busybox fdisk"
* "./fdisk /dev/block/mmcblk0"
* List your partitions by pressing "p".
Here's the listing of CORRECT partition sizes (for 16GB model!):
Disk /dev/block/mmcblk0: 15.9 GB, 15925772288 bytes
1 heads, 16 sectors/track, 1944064 cylinders
Units = cylinders of 16 * 512 = 8192 bytes
Device Boot Start End Blocks Id System
/dev/block/mmcblk0p1 5 1944064 15552480 5 Extended
Partition 1 does not end on cylinder boundary
/dev/block/mmcblk0p5 9 40 256 83 Linux
/dev/block/mmcblk0p6 45 76 256 83 Linux
/dev/block/mmcblk0p7 81 240 1280 83 Linux
/dev/block/mmcblk0p8 245 404 1280 83 Linux
/dev/block/mmcblk0p9 409 1048 5120 83 Linux
/dev/block/mmcblk0p10 1053 2332 10240 83 Linux
/dev/block/mmcblk0p11 2337 3296 7680 83 Linux
/dev/block/mmcblk0p12 3301 4260 7680 83 Linux
/dev/block/mmcblk0p13 4265 38824 276480 83 Linux
/dev/block/mmcblk0p14 38829 55980 137216 83 Linux
/dev/block/mmcblk0p15 55985 64176 65536 83 Linux
/dev/block/mmcblk0p16 64181 313396 1993728 83 Linux
/dev/block/mmcblk0p17 313401 1937720 12994560 83 Linux
If some of them are mismatched (p14 and p15 probably), delete them and create again in fdisk. You don't have to format them, just setup correct type (T 83). Finally write (w) and quit fdisk.
* "sync; sync; sync"
* "reboot"
If the device still hangs:
* Put your device in SYSTEM RECOVERY mode: ("Pwr button" + "Vol up" + "Home button")
* Choose "wipe cache partition"
* Choose "reboot system now"
If the device still hangs:
* Put your device in SYSTEM RECOVERY mode: ("Pwr button" + "Vol up" + "Home button")
* Choose "wipe data/factory reset"
* Choose "reboot system now"
If the device still hangs, then try your service or shop.
Attached what i got with heimdall ytd.
I will start ADB today when free. i must learn about first.
Thanks
Today edit:
I have followed your clear instruction, here attached the result before going forward in another mistake let me have your direction to follow.
I mind this can help many other people like me!
missed attachment
Attachment can't be sent under msg edit sorry.
Partitions
lolo9393 said:
Attachment can't be sent under msg edit sorry.
Click to expand...
Click to collapse
You did a good job! Your model is 32GB by the way, so the size of your partition p17 would be different from my model. Your partition p14 is corrupted and p15-17 are missing. You should delete p14 and create p14-17 as type 83 (Linux). You can make the same sizes, as my example, except for the p17, which you can simply create from block 313401 until the end of the disk . Then try the rest of my instructions.
If the formatting in SYSTEM RECOVERY mode would not help you, you can create tool "mke2fs" the same way you created "fdisk" and you can format the partitions via command:
"./mke2fs -j /dev/block/mmcblk0p14"
That's for partition p14, you should also do that for the rest (p15-17) and then try to format again in SYSTEM RECOVERY.
That should help.
Before correcting the wrong blocks by hand, I innocently accepted the light offer to correct block 14 by typing "w" that's may be not good. but i cann't retur to read dev/block/mmblck0 to see the resulting. What's wrong?
Sorry if bothering for you but that's common problem with beginners!
fdisk
Try: "./fdisk dev/block/mmblck0". What happens?
chongkwan said:
Try: "./fdisk dev/block/mmblck0". What happens?
Click to expand...
Click to collapse
Thanks
Now, You can go to sleep and have a good night.
I'll finish the work with care.
Regards
Great success!
My device restarted after KPL Fw flashing (odin). I have not lost any personal data (photo and music), that's strange after some 20 different flash process and wipes.
Your are top expert guy!
Many THANKS for your help.
I was seeking for solution from end january when I Missrooted my device!
I have in meantime learn so much about Android and also improved my english somehow.
In case I can give you back a service, please ask.
I am sure your problem solving would help many other infortunate guys, why not to make this "sticky".
I can add what is good not to be done to avoid problem then!
Best Regards
Very good! Congratulations Your partitions are correct now. I am sorry you had to wait so long.
trying to fellow the above tutorial with no lcuk , i'm stuck in adb shell error device not found, any clue ?
Hi
In post N°8 You have everything you "must" do.
Rooted kernel is RJ's 14 kernel and nothing else for our device.
You go recovery and adb will connect.
then "shell" et voila.
Forget playing with the PIT file; it si no reason it is wrong at this step, avoid adding a difficulty, please.
Keep informed as you want
now after flashing a Korean kernel the device does boot up normally and everything seems to be fine apart from memory, internal memory and staff is all showing unavailable ?!?! strange situation ?!?! does anybody have an idea about how to fix that ?
Fine,
You mind you are just at a "wipe" step to be done.
Normally full wipe is enough to get the device restarted from home.
OK do it and give me the result reported at the screen after this step.
Hello everybody !
I'm a noob on Android and I have a strange problem. I rooted my Wiko Pulp Fab (Lollipop 5.1) with KingRoot (after so many tries with other solutions) and now when I get root internet seems doesn't work.
I intend to use Linux Deploy and it can't download distribs (I tried use domain names and IPs, no difference)
And when I connect to my phone's shell with adb I have the same problem.
Normal user in shell, connection work:
Code:
[email protected]:/ $ ping wikipedia.fr
PING wikipedia.fr (78.109.84.114) 56(84) bytes of data.
64 bytes from wikimedia2.typhon.net (78.109.84.114): icmp_seq=1 ttl=56 time=17.9 ms
64 bytes from wikimedia2.typhon.net (78.109.84.114): icmp_seq=2 ttl=56 time=29.8 ms
64 bytes from wikimedia2.typhon.net (78.109.84.114): icmp_seq=3 ttl=56 time=30.1 ms
64 bytes from wikimedia2.typhon.net (78.109.84.114): icmp_seq=4 ttl=56 time=30.0 ms
64 bytes from wikimedia2.typhon.net (78.109.84.114): icmp_seq=5 ttl=56 time=29.1 ms
...
Root in shell, connection doesn't work:
Code:
[email protected]:/ # ping wikipedia.fr
connect: Bad file number
2|[email protected]:/ # ping 78.109.84.114
connect: Bad file number
I tried ping and other binaries, it doesn't work.
What's wrong ? I heard that is a C message error about socket usage, but how can I fix it ?
Maybe it is a problem with KingRoot ? I tried many many solutions to root my phone but nothing work. I tried to install "su" myself with adb or fastboot but it doesn't work (I don't know very much Android yet, I'd just beginning learn few days ago).
Many thanks for your help !
EDIT
I found a solution so I publish it here, maybe it can help !
If this error appear, it is probably beacause SELinux is in enforce mode. SELinux is a security module who restrict users.
To display refused operations:
Code:
# dmesg | grep -i denied
To activate SELinux permissive mode:
Code:
# setenforce 0
That's all !
The issue is that with LP root now needs a kernel change to make root work properly. King root is a joke and should never be used
zelendel said:
The issue is that with LP root now needs a kernel change to make root work properly. King root is a joke and should never be used
Click to expand...
Click to collapse
OK so what can i do ? Where can I found doc about kernel change ?
remipassmoilesel said:
OK so what can i do ? Where can I found doc about kernel change ?
Click to expand...
Click to collapse
The ingest issue is that this OEM doesn't comply with gpl laws so you may not even be able to find the source code for the kernel. Let alone having an unlocked bootloader to flash the kernel.
I'll be honest. With these small companies your best bet is just use the phone as it comes.
In fact I have downloaded the whole source code, available online. I tried to build it once but finally I'm not sure of what can I do with that.
Do you think I can build my own /system image with a su binary or that will be not enought ?
remipassmoilesel said:
In fact I have downloaded the whole source code, available online. I tried to build it once but finally I'm not sure of what can I do with that.
Do you think I can build my own /system image with a su binary or that will be not enought ?
Click to expand...
Click to collapse
You found the kernel source code? You do know that the kernel source and android source are different. Also you will need to have an unlocked bootloader to even flash it.
zelendel said:
You found the kernel source code? You do know that the kernel source and android source are different. Also you will need to have an unlocked bootloader to even flash it.
Click to expand...
Click to collapse
I think I have both, kernel and android: http://www.wikogeek.com
So what can I do ?
1) Build all and obtain the 3 img files (boot.img, ....),
2) Mount the img files and insert su binary and others custom files,
3) Push the img files to the phone with fastboot
Is that correct ?
I have one question more. With Fastboot, can I push just some files or I can just overwirte the whole partition ?
Thanks for your help.
I found a solution so I publish it here, maybe it can help !
If this error appear, it is probably beacause SELinux is in enforce mode. SELinux is a security module who restrict users.
To display refused operations:
Code:
# dmesg | grep -i denied
To activate SELinux permissive mode:
Code:
# setenforce 0
That's all !
I think I have figured out how to root every G6 that is still ARB 0, and doesn't currently have root.
However, I can't test it (sorry not buying yet another G6), so I need someone willing to try.
If I am wrong, you WILL end up with a brick that can't be fixed except by LG.
If you are interested, reply to this thread. Please do not PM me, it will be ignored (sorry too many PMs).
Also, please don't quote this entire post .. just @ mention me.
-- Brian
@runningnak3d I will try it. I have a G6 H873 to test the method on. If it bricks, it bricks for science.
@runningnak3d does this also include bootloader unlock as alluded you may be able to accomplish in your LAF thread? If yes, then i have a H870DS im willing to risk.
@runningnak3d I have an LG G6 sitting on a desk doing nothing because of lack of root option, I wouldn't care to brick it if it is trying to root it, I vae another device as a daily driver
I am crafting up the procedure, and will try to get something out today.
I am going to have to pull the KDZs for the various models, but until I can do that, what ARB are you guys on. List model / Android version / ARB version
As for the DS -- that will have to be last (if this works at all) because a custom kernel will have to be compiled, and I am not going to do that until we know that it works on the single SIM models.
-- Brian
runningnak3d said:
I am crafting up the procedure, and will try to get something out today.
I am going to have to pull the KDZs for the various models, but until I can do that, what ARB are you guys on. List model / Android version / ARB version
As for the DS -- that will have to be last (if this works at all) because a custom kernel will have to be compiled, and I am not going to do that until we know that it works on the single SIM models.
-- Brian
Click to expand...
Click to collapse
US997z US Cellular unlocked ARB not sure but if that means anti-rollback version 0000 android Oreo 8.0.0
[ro.lge.swversion_arb]: [ ] I guess that means 00
runningnak3d said:
I am crafting up the procedure, and will try to get something out today.
I am going to have to pull the KDZs for the various models, but until I can do that, what ARB are you guys on. List model / Android version / ARB version
As for the DS -- that will have to be last (if this works at all) because a custom kernel will have to be compiled, and I am not going to do that until we know that it works on the single SIM models.
-- Brian
Click to expand...
Click to collapse
LG-H870DS/8.0.0/?
SW ver V20d-TWN-XX
Kernel 3.18.71
Hi Brian, how do we find ARB version?
bick said:
LG-H870DS/8.0.0/?
SW ver V20d-TWN-XX
Kernel 3.18.71
Hi Brian, how do we find ARB version?
Click to expand...
Click to collapse
use adb shell... once in adb shell type: getprop ro.lge.swversion_arb
if the output in command prompt window is empty I guess is = 00 if it is 01 then you should get 01 as the output of the command
JEANRIVERA said:
use adb shell... once in adb shell type: getprop ro.lge.swversion_arb
if the output in command prompt window is empty I guess is = 00 if it is 01 then you should get 01 as the output of the command
Click to expand...
Click to collapse
Came back with nothing:
C:\adb>adb shell
lucye:/ $ getprop ro.lge.swversion_arb
lucye:/ $
bick said:
Came back with nothing:
C:\adb>adb shell
lucye:/ $ getprop ro.lge.swversion_arb
lucye:/ $
Click to expand...
Click to collapse
I guess that means it is 00 then
Model: H873
Android Version: 8.0.0
ARB: 00
---------- Post added at 08:49 AM ---------- Previous post was at 08:45 AM ----------
JEANRIVERA said:
US997z US Cellular unlocked ARB not sure but if that means anti-rollback version 0000 android Oreo 8.0.0
[ro.lge.swversion_arb]: [ ] I guess that means 00
Click to expand...
Click to collapse
When I retrieve that value, it returns "ARB00", so I'm not sure if having no value at all means the same thing or not.
Code:
lucye:/ $ getprop ro.lge.swversion_arb
ARB00
A much more reliable way:
Code:
adb shell cat /sys/bus/platform/devices/lge-qfprom/antirollback
Example from an H872:
Code:
$ adb shell cat /sys/bus/platform/devices/lge-qfprom/antirollback
1
With that said, if you are ARB 0, then first we need to get a laf version that we can work with.
Follow the instructions in this post: https://forum.xda-developers.com/tmobile-g6/how-to/root-h872-to-including-11g-t3775518
Except:
Instead of the H91810p KDZ, download the H91510e: link
Instead of any of the H872 KDZs, download the KDZ for the version that is currently on your phone.
Only do PART 1 of the procedure to get the H915 laf onto your phone. Do NOT proceed onto flashing TWRP. If you do, you will brick your phone.
Also, go ahead and get an SD card formatted FAT16 or FAT32. It can't be exFat, NTFS, or ext2, 3, or 4 -- laf can only read FAT partitions on the SD card. It only needs to be big enough to hold TWRP, and the eng. aboot (256meg would do).
Lastly, get FWUL downloaded and burned to a USB stick, and make sure you can boot with it and have network connectivity.
Really last this time -- anyone that wants try this is welcome, but I suggest that you let ONE person try it so that you don't all end up with bricks if I am wrong.
Once I get confirmation that someone has completed the above steps, I will post the remainder on how to unlock your bootloader, and actually flash TWRP.
-- Brian
Okay, going through the procedure for my device now. If anyone wants protection from bricking their phone, I've taken on the smallest straw. Will update very soon.
UPDATE
Sorry for the delay everyone. I said 'very soon' but my wife had an errand schedule for our day.
My initial download of the KDZ apparently corrupted so it took me a while to figure out that it was the problem. Fresh download was accepted by LG UP just fine.
LG UP indicated an "ARB PASS: SUCCESS" after the laf partition flashed and then once my H87320g KDZ was flashed without the laf, it has now rebooted into a stock LG install, no bootloop or brick.
Download TWRP: link
Download eng. aboot: link
Copy them both to your SD card, and then put it in your phone, and boot to download mode. Your screen probably won't init -- so all you will see is "download mode" in blue, and not the full download mode screen .. that is normal.
Boot up FWUL from the USB stick, and hook your phone up to your PC.
Login (password is linux)
On the desktop is an LG folder -- open it. Inside is runningnak3d icon -- double click it.
You will be at a shell prompt. Type:
Code:
git pull
git checkout h872-miscwrte
./partitons.py --list
Post the output here...
-- Brian
runningnak3d said:
Download TWRP: link
Click to expand...
Click to collapse
Which TWRP should I grab, the one for H872?
---------- Post added at 03:42 PM ---------- Previous post was at 03:25 PM ----------
I downloaded the H872 one. Here is the output of those commands:
Code:
[B][[email protected] lglafsploit]$[/B] git pull
remote: Enumerating objects: 73, done.
remote: Counting objects: 100% (73/73), done.
remote: Compressing objects: 100% (49/49), done.
remote: Total 66 (delta 42), reused 28 (delta 17)
Unpacking objects: 100% (66/66), done.
From https://gitlab.com/runningnak3d/lglaf
11caab1..05a924a h872-miscwrte -> origin/h872-miscwrte
3ef85ef..8c04118 h918-miscwrte -> origin/h918-miscwrte
* [new branch] h932-dd-write -> origin/h932-dd-write
4f5522c..be4d9e0 v10-miscwrte -> origin/v10-miscwrte
Already up to date.
[B][[email protected] lglafsploit]$[/B] git checkout h872-miscwrte
Branch 'h872-miscwrte' set up to track remote branch 'h872-miscwrte' from 'origin'.
Switched to a new branch 'h872-miscwrte'
[B][[email protected] lglafsploit]$[/B] ./partitions.py --list
MBR Header
LBA size (sector size): {0} 512
Number of MBR partitions: 1
# Active From(#s) Size(#s) Code Type
1 _ 1 4294967295 EE EFI GPT protective MBR
GPT Header
Disk GUID: 98101B32-BBE2-4BF2-A06E-2BB33D000C20
LBA size (sector size): 4096
GPT First LBA: 1
GPT Last LBA: 59391
Number of GPT partitions: 29
# Flags From(#s) To(#s) GUID/UID Type/Name
1 1152921504606846976 6 10245 20117F86-E985-4357-B9EE-374BC1D8487D Unknown
471A9803-7DF2-5BFE-55D0-6B0A138D0E0E boot
2 1152921504606846976 10246 20613 9D72D4E4-9958-42DA-AC26-BEA7A90B0434 Unknown
CEE95E9A-4402-59CD-3748-2AE13F052C01 recovery
3 1152921504606846976 20614 30981 DF24E5ED-8C96-4B86-B00B-79667DC6DE11 Unknown
27DDFCD8-D866-57EA-0DEA-04D6FCC0C386 recoverybak
4 1152921504606846976 30982 31493 A053AA7F-40B8-4B1C-BA08-2F68AC71A4F4 Unknown
4C1ADAD3-D945-8B94-5FD8-461F57BF5546 tz
5 1152921504606846976 31494 32005 E6C8667F-8044-44A7-B1D9-BEFE88AAD86C Unknown
A48C85CC-487D-AE1E-4A66-4223711B9FD1 tzbak
6 1152921504606846976 32006 32517 400FFDCD-22E0-47E7-9A23-F16ED9382388 Unknown
97D88AF5-8BAF-4993-2172-94D497B88DC3 aboot
7 1152921504606846976 32518 33029 C993E3DF-FE66-49C9-8D8D-7C681C4DCAE9 Unknown
695164DD-4E12-F27E-1989-28CBB576459E abootbak
8 0 33030 34053 4627AE27-CFEF-48A1-88FE-99C3509ADE26 Unknown
D267834D-FAB1-920A-E6FC-A56D7420459F raw_resources
9 0 34054 35077 C1DAB2CF-697D-4665-B43D-00BA47487528 Unknown
B9795B4C-400D-1E60-205B-5650DEE574C5 raw_resourcesbak
10 1152921504606846976 35078 35205 098DF793-D712-413D-9D4E-89D711772228 Unknown
C56E8DC3-3671-12F1-8A01-BC9981649736 rpm
11 1152921504606846976 35206 35333 680CA584-238C-4E0F-8438-15F43257A055 Unknown
C3DB3F2B-A906-A9ED-5021-259DEC048569 rpmbak
12 1152921504606846976 35334 35461 E1A6A689-0C8D-4CC6-B4E8-55A4320FBD8A Unknown
88BE6260-D924-EAF8-BE5A-363EDE26C991 hyp
13 1152921504606846976 35462 35589 24C03326-2523-4E03-8C5E-B07ED7A44CD9 Unknown
0CE8ECBE-46EE-3889-9130-6533519A807F hypbak
14 1152921504606846976 35590 35717 C00EEF24-7709-43D6-9799-DD2B411E7A3C Unknown
343B1328-A7F3-5284-0463-11EC47201309 pmic
15 1152921504606846976 35718 35845 4E646DCC-29E2-459A-B7C5-618E6F3AD76A Unknown
34B1563F-E471-03A6-99F3-FEC1CC85CC80 pmicbak
16 0 35846 35877 F65D4B16-343D-4E25-AAFC-BE99B6556A6D Unknown
D6A64FD3-7F54-545C-48D8-9791D2D632ED devcfg
17 0 35878 35909 10A0C19C-516A-5444-5CE3-664C3226A794 Unknown
0572C0B3-91F0-E82E-08D0-4276C17B4C3F devcfgbak
18 1152921504606846976 35910 57925 A8944C60-3BD0-442F-94C1-D137A5F9C383 Unknown
F5165B81-2DA2-B61D-C11C-82E7B5C7409F modem
19 1152921504606846976 57926 58053 303E6AC3-AF15-4C54-9E9B-D9A8FBECF401 Unknown
7A18B22B-D98E-598B-48D9-672F34850E54 sec
20 1152921504606846976 58054 58181 4F772165-0F3C-4BA3-BBCB-A829E9C969F9 Unknown
494050D0-F6E5-1440-FA96-4E4ECB3DD491 keymaster
21 1152921504606846976 58182 58309 7C29D3AD-78B9-452E-9DEB-D098D542F092 Unknown
4A9A5D18-8149-97ED-C7A9-04B53EFE2E85 keymasterbak
22 1152921504606846976 58310 58437 73471795-AB54-43F9-A847-4F72EA5CBEF5 Unknown
FD7411E7-3C64-42A8-D306-6B31AD271019 cmnlib
23 1152921504606846976 58438 58565 7C29D3AD-78B9-452E-9DEB-D098D542F092 Unknown
8A2F1492-8C9E-3F67-EB15-84FADE9A8058 cmnlibbak
24 1152921504606846976 58566 58693 8EA64893-1267-4A1B-947C-7C362ACAAD2C Unknown
F00B6251-F0EA-9516-C3A3-C3D7AEDDF7A1 cmnlib64
25 1152921504606846976 58694 58821 379D107E-229E-499D-AD4F-61F5BCF87BD4 Unknown
3B2CA5FC-07C6-9A73-2EE4-E4E9E7D3001A cmnlib64bak
26 1152921504606846976 58822 58949 E6E98DA2-E22A-4D12-AB33-169E7DEAA507 Unknown
C4655C1F-AC8F-9BC0-469D-211E69A237E9 apdp
27 1152921504606846976 58950 59077 ED9E8101-05FA-46B7-82AA-8D58770D200B Unknown
705B6B2F-C1C5-C343-B70F-6DB5F9E10D68 msadp
28 1152921504606846976 59078 59205 11406F35-1173-4869-807B-27DF71802812 Unknown
BE798179-83E0-F385-4B9B-3FF815104459 dpo
29 0 59206 59206 3716CB88-FF5A-4DEE-A392-12A05637B49D Unknown
830F530A-C109-D818-959A-1C0BADE11951 grow5
While the H872 version should work, grab the one for the US997.
OK....
Here goes the magic (or the boom and cry -- depending on the outcome).
Actually -- let's make sure you have full root access first....
Type:
Code:
./lglaf.py
whoami
-- Brian
Alright, I grabbed the US997 version. Here is the output:
Code:
[B][[email protected] lglafsploit]$[/B] ./lglaf.py
LGLAF.py by Peter Wu (https://lekensteyn.nl/lglaf)
Type a shell command to execute or "exit" to leave.
# whoami
Hello, I am LAF. Nice to meet you.#
xrosser said:
Alright, I grabbed the US997 version. Here is the output:
Code:
[B][[email protected] lglafsploit]$[/B] ./lglaf.py
LGLAF.py by Peter Wu (https://lekensteyn.nl/lglaf)
Type a shell command to execute or "exit" to leave.
# whoami
Hello, I am LAF. Nice to meet you.#
Click to expand...
Click to collapse
Hmmm... that isn't good. That makes no sense actually.
Try:
Code:
!EXEC toybox whoami\0
Two spaces between EXEC and toybox
-- Brian
Same output. It is a strange return for that command... I even tried 'echo $USER' and same result.
Code:
[[email protected] lglafsploit]$ ./lglaf.py
LGLAF.py by Peter Wu (https://lekensteyn.nl/lglaf)
Type a shell command to execute or "exit" to leave.
# whoami
Hello, I am LAF. Nice to meet you.# !EXEC toybox whoami\0
Hello, I am LAF. Nice to meet you.# echo $USER
Hello, I am LAF. Nice to meet you.#
Many of 6GB RAM Nokia X6 has an issue, that you can't flash system partition properly - after 1st sparse flashed, fastboot will prompt "error flashing partition".
This guide introduces a workaround for this issue.
4GB RAM Nokia X6 / 6.1 Plus needn't to follow this guide.
And 6GB RAM Nokia 7 Plus needn't to follow this guide.
Or if your 6GB RAM Nokia X6 can flash stock firmware properly, you needn't to read this guide any further.
Click to expand...
Click to collapse
I still don't clear the pattern of 6GB RAM Nokia X6 that can't flash partitions.
Prerequisites:
- Bootloader must be completely unlocked
- You have fully unpacked firmware
- Use OST LA 6.0.4 or NOST v0.4 by @stollD
Here's how:
1. Make a copy of DRG-2XXX-0-00XX-B0X.mlf at the same directory, in this example, I made a copy of "DRG-221F-0-00CN-B03.mlf".
2. Use Notepad++ or any code editor that supports unix to open "DRG-221F-0-00CN-B03 - Copy.mlf".
3. Navigate to these codes.
Code:
[Package Info 31]
PACKAGE_NAME = "system_a"
BOOT_NAME = "system_a"
OPTION = 0x40000
IMAGE_FILE = "DRG-0-221F-00CN-system.img"
[Package Info 32]
PACKAGE_NAME = "system_b"
BOOT_NAME = "system_b"
OPTION = 0x40000
IMAGE_FILE = "DRG-0-221F-00CN-system_other.img"
And modify them to:
Code:
[Package Info 31]
PACKAGE_NAME = "system_a"
BOOT_NAME = "system_a"
OPTION = 0x4
IMAGE_FILE = ""
[Package Info 32]
PACKAGE_NAME = "system_b"
BOOT_NAME = "system_b"
OPTION = 0x4
IMAGE_FILE = ""
Save it.
4. Use OST LA or NOST to flash this - you'll definitely encounter C6DA error, but don't worry about that.
5. Download TWRP for Nokia 7 Plus that doesn't require flash from here (TBA) and execute these commands under OST LA installation directory:
NOTE: YOU MUST USE fastboot-android.exe included in OST LA - DO NOT USE fastboot.exe provided by Google.
Click to expand...
Click to collapse
Code:
.\fastboot-android format userdata
.\fastboot-android reboot-bootloader
.\fastboot-android boot D:\Nokia7plusv3.2.1.0-noflash.img
After your phone booted to TWRP, you may find the touch screen doesn't work, don't worry - we only need to use adb commands.
6. Execute following commands:
[QUOTE]
You can use adb.exe from both OST LA or platform tools.
[/QUOTE]
[CODE]
.\adb push D:\DRG-221F-0-00CN-B03.nb0_unpacked\systeminfo.img /data/systeminfo.img
.\adb push D:\DRG-221F-0-00CN-B03.nb0_unpacked\DRG-0-221F-00CN-system.img /data/system_a.img
.\adb push D:\DRG-221F-0-00CN-B03.nb0_unpacked\DRG-0-221F-00CN-system_other.img /data/system_b.img
.\adb shell
simg2img /data/system_a.img /data/system_a.img.ext4
simg2img /data/system_b.img /data/system_b.img.ext4
dd if=/data/systeminfo.img of=/dev/block/bootdevice/by-name/systeminfo_a
dd if=/data/systeminfo.img of=/dev/block/bootdevice/by-name/systeminfo_b
dd if=/data/system_a.img.ext4 of=/dev/block/bootdevice/by-name/system_a
dd if=/data/system_b.img.ext4 of=/dev/block/bootdevice/by-name/system_b
rm /data/systeminfo.img
rm /data/system_a.img
rm /data/system_b.img
reboot
That's all for the whole 6GB RAM Nokia X6 stock firmware flashing guide.
If you're a developer, 6GB RAM Nokia X6 is definitely unsuitable for developing.
Thanks for the guide, it will be very useful for me. I'm trying to flash this phone for a long time and I just can't unbrick it.
A few issues I've come over while following it:
OST_LA and NOST didn't want to flash DRG-221F-0-00CN-B03 ("you need to update your software" or something like that), so I had to unpack DRG-229D-0-00WW-B01.
I couldn't find Nokia7plusv3.2.1.0-noflash.img anywhere, so I used Twrp_N6.1plus_global_Aug.
When I try to use simg2img in adb shell, I get the following error:
Code:
~ # simg2img /data/system_a.img /data/system_a.img.ext4
error: file_write: write: Out of memory
Cannot write output file
---
Update: I've flashed 250A and it works like a charm! Just had to edit the .mlf according to this guide.
Hi @hikari_calyx,
have you tried flashing Nokia X6 6GB version to 6.1 Plus International Version (Android One)?
Anything I need to consider?
Hey I bought the Nokia x6 TA-1099 6gb Chinese variant it came with the global ROM 00WW_3_38A I believe it was flashed by the seller. When I got the phone I saw there was an OTA to update the pie to v3.45B I want to know if it's safe to update via OTA because it's meant for 6.1plus
:good: thanks
twrp fails
when iam flashing twrp it is showing that no such partiton is found recovery b