Hi
Phone get rooted now. but i can't unlock to use sim free. how can i get network control unlock key ?
doantri said:
Hi
Phone get rooted now. but i can't unlock to use sim free. how can i get network control unlock key ?
Click to expand...
Click to collapse
How to display network unlock guy?
how did you root your SCL22 Note 3?
can u tell me what is the method that you used to root your SCL22 note 3
because i have the same problem .
Hi
You should use CWM SM-N9005 then update SU via CWM
I need unlock phone to use with gsm simcard but can't get unlock code.
doantri said:
Hi
You should use CWM SM-N9005 then update SU via CWM
I need unlock phone to use with gsm simcard but can't get unlock code.
Click to expand...
Click to collapse
can you share the file you use to unlock your phone?
you can you galaxim(i think) you can download in google play for free or regionlock away
beast08 said:
can you share the file you use to unlock your phone?
you can you galaxim(i think) you can download in google play for free or regionlock away
Click to expand...
Click to collapse
- CWM recovery for N9005: https://mega.co.nz/#!C0Y1RbyT!Iq1A1Aaef1qioyDHkGQVtkRUdGN0LCa37umKGMDyDs8
- SuperSU: http://download.chainfire.eu/372/SuperSU/UPDATE-SuperSU-v1.86.zip
first install CWM recovery then flash SuperSU via recovery
vndnguyen said:
- CWM recovery for N9005: https://mega.co.nz/#!C0Y1RbyT!Iq1A1Aaef1qioyDHkGQVtkRUdGN0LCa37umKGMDyDs8
- SuperSU: http://download.chainfire.eu/372/SuperSU/UPDATE-SuperSU-v1.86.zip
first install CWM recovery then flash SuperSU via recovery
Click to expand...
Click to collapse
i tried this method before, flashing the SuperSU v1.86 to my phone, but everytime im opening the app, it saying su binary need to update, abd the phone will reboot to CWM recovery, and when i checked it will Root Checker, it says the phone is not properly rooted.
beast08 said:
i tried this method before, flashing the SuperSU v1.86 to my phone, but everytime im opening the app, it saying su binary need to update, abd the phone will reboot to CWM recovery, and when i checked it will Root Checker, it says the phone is not properly rooted.
Click to expand...
Click to collapse
I just provided these links per suggestion from doantri
I'm not sure if it works for your phone or not. Sorry to hear that.
Can you re upload the cwm file in other site? Im getting a hard tome downloading a file from mega
Sent from my SCL22 using xda app-developers app
need help
Hi everybody. I successfully rooted my scl22 using the instructions in a chinese site : " SCL22 root & sim unlock
Galaxy Note3 SCL22のRoot化(SC-01Fも対応)
SM-N9005用CWMをOdinから焼き込み、SuperSUをインストールすればRoot化完了。
・SM-N9005用CWMのダウンロード先
n9005-cwm-recovery-6.0.4.5(1116).tar
・SuperSUのダウンロード先
UPDATE-SuperSU-v1.65.zip
・sgs3_rooting_supersu_v3.zipも必要です。ググってください。
○順番
1.CWMをOdinで焼きこみ。
2.CWMを起動し、sgs3_rooting_supersu_v3.zipをインストール。
3.続けてUPDATE-SuperSU-v1.65.zipをインストール。
4.再起動すればsuが効くようになります。
○カウントアップはCWMを焼くとKNOX WARRANTYが変化します。
他は初期ROM焼いて初期化すれば元に戻ります。
※カウントアップするとオサイフがNGになります。
※Root化されたsystem.imgのみ焼けば大丈夫かも？
KNOX WARRANTY VOID : 0x0
↓
KNOX WARRANTY VOID : 0x1
Galaxy Note 3 SCL22の内部パーティション
[email protected]:/ # ls -l /dev/block/platform/msm_sdcc.1/by-name/
ls -l /dev/block/platform/msm_sdcc.1/by-name/
lrwxrwxrwx root root 1970-01-02 04:36 aboot -> /dev/block/mmcblk0p6
lrwxrwxrwx root root 1970-01-02 04:36 apnhlos -> /dev/block/mmcblk0p1
lrwxrwxrwx root root 1970-01-02 04:36 backup -> /dev/block/mmcblk0p17
lrwxrwxrwx root root 1970-01-02 04:36 boot -> /dev/block/mmcblk0p14
lrwxrwxrwx root root 1970-01-02 04:36 cache -> /dev/block/mmcblk0p24
lrwxrwxrwx root root 1970-01-02 04:36 dbi -> /dev/block/mmcblk0p4
lrwxrwxrwx root root 1970-01-02 04:36 ddr -> /dev/block/mmcblk0p5
lrwxrwxrwx root root 1970-01-02 04:36 efs -> /dev/block/mmcblk0p11
lrwxrwxrwx root root 1970-01-02 04:36 fota -> /dev/block/mmcblk0p16
lrwxrwxrwx root root 1970-01-02 04:36 fsc -> /dev/block/mmcblk0p19
lrwxrwxrwx root root 1970-01-02 04:36 fsg -> /dev/block/mmcblk0p18
lrwxrwxrwx root root 1970-01-02 04:36 modem -> /dev/block/mmcblk0p2
lrwxrwxrwx root root 1970-01-02 04:36 modemst1 -> /dev/block/mmcblk0p12
lrwxrwxrwx root root 1970-01-02 04:36 modemst2 -> /dev/block/mmcblk0p13
lrwxrwxrwx root root 1970-01-02 04:36 pad -> /dev/block/mmcblk0p9
lrwxrwxrwx root root 1970-01-02 04:36 param -> /dev/block/mmcblk0p10
lrwxrwxrwx root root 1970-01-02 04:36 persdata -> /dev/block/mmcblk0p22
lrwxrwxrwx root root 1970-01-02 04:36 persist -> /dev/block/mmcblk0p21
lrwxrwxrwx root root 1970-01-02 04:36 recovery -> /dev/block/mmcblk0p15
lrwxrwxrwx root root 1970-01-02 04:36 rpm -> /dev/block/mmcblk0p7
lrwxrwxrwx root root 1970-01-02 04:36 sbl1 -> /dev/block/mmcblk0p3
lrwxrwxrwx root root 1970-01-02 04:36 ssd -> /dev/block/mmcblk0p20
lrwxrwxrwx root root 1970-01-02 04:36 system -> /dev/block/mmcblk0p23
lrwxrwxrwx root root 1970-01-02 04:36 tz -> /dev/block/mmcblk0p8
lrwxrwxrwx root root 1970-01-02 04:36 userdata -> /dev/block/mmcblk0p25
zhongkai cheng*时间：*下午7:20
,but not beeing experienced in programming , i wasn't able to aply the second set of instructions. There is a script that should be run and i do not know how to do that. Maybe someone with experience can help us.
Please anyone help us to SIM unlock Note 3 SCL22
mvmaos said:
Hi everybody. I successfully rooted my scl22 using the instructions in a chinese site : " SCL22 root & sim unlock
Galaxy Note3 SCL22のRoot化(SC-01Fも対応)
SM-N9005用CWMをOdinから焼き込み、SuperSUをインストールすればRoot化完了。
・SM-N9005用CWMのダウンロード先
n9005-cwm-recovery-6.0.4.5(1116).tar
・SuperSUのダウンロード先
UPDATE-SuperSU-v1.65.zip
・sgs3_rooting_supersu_v3.zipも必要です。ググってください。
○順番
1.CWMをOdinで焼きこみ。
2.CWMを起動し、sgs3_rooting_supersu_v3.zipをインストール。
3.続けてUPDATE-SuperSU-v1.65.zipをインストール。
4.再起動すればsuが効くようになります。
○カウントアップはCWMを焼くとKNOX WARRANTYが変化します。
他は初期ROM焼いて初期化すれば元に戻ります。
※カウントアップするとオサイフがNGになります。
※Root化されたsystem.imgのみ焼けば大丈夫かも？
KNOX WARRANTY VOID : 0x0
↓
KNOX WARRANTY VOID : 0x1
Galaxy Note 3 SCL22の内部パーティション
[email protected]:/ # ls -l /dev/block/platform/msm_sdcc.1/by-name/
ls -l /dev/block/platform/msm_sdcc.1/by-name/
lrwxrwxrwx root root 1970-01-02 04:36 aboot -> /dev/block/mmcblk0p6
lrwxrwxrwx root root 1970-01-02 04:36 apnhlos -> /dev/block/mmcblk0p1
lrwxrwxrwx root root 1970-01-02 04:36 backup -> /dev/block/mmcblk0p17
lrwxrwxrwx root root 1970-01-02 04:36 boot -> /dev/block/mmcblk0p14
lrwxrwxrwx root root 1970-01-02 04:36 cache -> /dev/block/mmcblk0p24
lrwxrwxrwx root root 1970-01-02 04:36 dbi -> /dev/block/mmcblk0p4
lrwxrwxrwx root root 1970-01-02 04:36 ddr -> /dev/block/mmcblk0p5
lrwxrwxrwx root root 1970-01-02 04:36 efs -> /dev/block/mmcblk0p11
lrwxrwxrwx root root 1970-01-02 04:36 fota -> /dev/block/mmcblk0p16
lrwxrwxrwx root root 1970-01-02 04:36 fsc -> /dev/block/mmcblk0p19
lrwxrwxrwx root root 1970-01-02 04:36 fsg -> /dev/block/mmcblk0p18
lrwxrwxrwx root root 1970-01-02 04:36 modem -> /dev/block/mmcblk0p2
lrwxrwxrwx root root 1970-01-02 04:36 modemst1 -> /dev/block/mmcblk0p12
lrwxrwxrwx root root 1970-01-02 04:36 modemst2 -> /dev/block/mmcblk0p13
lrwxrwxrwx root root 1970-01-02 04:36 pad -> /dev/block/mmcblk0p9
lrwxrwxrwx root root 1970-01-02 04:36 param -> /dev/block/mmcblk0p10
lrwxrwxrwx root root 1970-01-02 04:36 persdata -> /dev/block/mmcblk0p22
lrwxrwxrwx root root 1970-01-02 04:36 persist -> /dev/block/mmcblk0p21
lrwxrwxrwx root root 1970-01-02 04:36 recovery -> /dev/block/mmcblk0p15
lrwxrwxrwx root root 1970-01-02 04:36 rpm -> /dev/block/mmcblk0p7
lrwxrwxrwx root root 1970-01-02 04:36 sbl1 -> /dev/block/mmcblk0p3
lrwxrwxrwx root root 1970-01-02 04:36 ssd -> /dev/block/mmcblk0p20
lrwxrwxrwx root root 1970-01-02 04:36 system -> /dev/block/mmcblk0p23
lrwxrwxrwx root root 1970-01-02 04:36 tz -> /dev/block/mmcblk0p8
lrwxrwxrwx root root 1970-01-02 04:36 userdata -> /dev/block/mmcblk0p25
zhongkai cheng*时间：*下午7:20
,but not beeing experienced in programming , i wasn't able to aply the second set of instructions. There is a script that should be run and i do not know how to do that. Maybe someone with experience can help us.
Click to expand...
Click to collapse
hey
anyone know a method to get unlock code for SCL22 Galaxy note 3 ?
mvmaos said:
Hi everybody. I successfully rooted my scl22 using the instructions in a chinese site : " SCL22 root & sim unlock
Galaxy Note3 SCL22のRoot化(SC-01Fも対応)
SM-N9005用CWMをOdinから焼き込み、SuperSUをインストールすればRoot化完了。
・SM-N9005用CWMのダウンロード先
n9005-cwm-recovery-6.0.4.5(1116).tar
・SuperSUのダウンロード先
UPDATE-SuperSU-v1.65.zip
・sgs3_rooting_supersu_v3.zipも必要です。ググってください。
○順番
1.CWMをOdinで焼きこみ。
2.CWMを起動し、sgs3_rooting_supersu_v3.zipをインストール。
3.続けてUPDATE-SuperSU-v1.65.zipをインストール。
4.再起動すればsuが効くようになります。
○カウントアップはCWMを焼くとKNOX WARRANTYが変化します。
他は初期ROM焼いて初期化すれば元に戻ります。
※カウントアップするとオサイフがNGになります。
※Root化されたsystem.imgのみ焼けば大丈夫かも？
KNOX WARRANTY VOID : 0x0
↓
KNOX WARRANTY VOID : 0x1
Galaxy Note 3 SCL22の内部パーティション
[email protected]:/ # ls -l /dev/block/platform/msm_sdcc.1/by-name/
ls -l /dev/block/platform/msm_sdcc.1/by-name/
lrwxrwxrwx root root 1970-01-02 04:36 aboot -> /dev/block/mmcblk0p6
lrwxrwxrwx root root 1970-01-02 04:36 apnhlos -> /dev/block/mmcblk0p1
lrwxrwxrwx root root 1970-01-02 04:36 backup -> /dev/block/mmcblk0p17
lrwxrwxrwx root root 1970-01-02 04:36 boot -> /dev/block/mmcblk0p14
lrwxrwxrwx root root 1970-01-02 04:36 cache -> /dev/block/mmcblk0p24
lrwxrwxrwx root root 1970-01-02 04:36 dbi -> /dev/block/mmcblk0p4
lrwxrwxrwx root root 1970-01-02 04:36 ddr -> /dev/block/mmcblk0p5
lrwxrwxrwx root root 1970-01-02 04:36 efs -> /dev/block/mmcblk0p11
lrwxrwxrwx root root 1970-01-02 04:36 fota -> /dev/block/mmcblk0p16
lrwxrwxrwx root root 1970-01-02 04:36 fsc -> /dev/block/mmcblk0p19
lrwxrwxrwx root root 1970-01-02 04:36 fsg -> /dev/block/mmcblk0p18
lrwxrwxrwx root root 1970-01-02 04:36 modem -> /dev/block/mmcblk0p2
lrwxrwxrwx root root 1970-01-02 04:36 modemst1 -> /dev/block/mmcblk0p12
lrwxrwxrwx root root 1970-01-02 04:36 modemst2 -> /dev/block/mmcblk0p13
lrwxrwxrwx root root 1970-01-02 04:36 pad -> /dev/block/mmcblk0p9
lrwxrwxrwx root root 1970-01-02 04:36 param -> /dev/block/mmcblk0p10
lrwxrwxrwx root root 1970-01-02 04:36 persdata -> /dev/block/mmcblk0p22
lrwxrwxrwx root root 1970-01-02 04:36 persist -> /dev/block/mmcblk0p21
lrwxrwxrwx root root 1970-01-02 04:36 recovery -> /dev/block/mmcblk0p15
lrwxrwxrwx root root 1970-01-02 04:36 rpm -> /dev/block/mmcblk0p7
lrwxrwxrwx root root 1970-01-02 04:36 sbl1 -> /dev/block/mmcblk0p3
lrwxrwxrwx root root 1970-01-02 04:36 ssd -> /dev/block/mmcblk0p20
lrwxrwxrwx root root 1970-01-02 04:36 system -> /dev/block/mmcblk0p23
lrwxrwxrwx root root 1970-01-02 04:36 tz -> /dev/block/mmcblk0p8
lrwxrwxrwx root root 1970-01-02 04:36 userdata -> /dev/block/mmcblk0p25
zhongkai cheng*时间：*下午7:20
,but not beeing experienced in programming , i wasn't able to aply the second set of instructions. There is a script that should be run and i do not know how to do that. Maybe someone with experience can help us.
Click to expand...
Click to collapse
Hi mvmaos, can you hsare the files that needed to root the phone? i cant seem to download the files in the chinese site, thanks in advance
---------- Post added at 06:48 PM ---------- Previous post was at 06:39 PM ----------
niranjan.anu said:
hey
anyone know a method to get unlock code for SCL22 Galaxy note 3 ?
Click to expand...
Click to collapse
Hi niranjan.anu, are you rooted already? have you tried the region unlock app? or the galaxsim unlock app? you can find that in palystore
beast08 said:
Hi mvmaos, can you hsare the files that needed to root the phone? i cant seem to download the files in the chinese site, thanks in advance
---------- Post added at 06:48 PM ---------- Previous post was at 06:39 PM ----------
Hi niranjan.anu, are you rooted already? have you tried the region unlock app? or the galaxsim unlock app? you can find that in palystore
Click to expand...
Click to collapse
Hi to you to . just google for them, they are easy to find. the two aps won't work for our phone, i tried them all, i succedeed even the script above , but it won't work. i will try these days at a samsung service, maybe they can be briebd .
the problem with our phone is that is locked in the service menu, and we can not acces that menu and our phone has gsm frequencies locked.
mvmaos said:
Hi to you to . just google for them, they are easy to find. the two aps won't work for our phone, i tried them all, i succedeed even the script above , but it won't work. i will try these days at a samsung service, maybe they can be briebd .
the problem with our phone is that is locked in the service menu, and we can not acces that menu and our phone has gsm frequencies locked.
Click to expand...
Click to collapse
too bad those two app wont work, so we have to wait until someone find a way on how to unlock our phone.
SCL22 Simunlock OK!
If you can send a SCL22 in Japan, I can do a SIM unlock.
Price : $90 + postage(Paypal)
mail : [email protected]
>>1
You are copying Root from my blog.
scl 22 unlock
Philipe9_person9 said:
If you can send a SCL22 in Japan, I can do a SIM unlock.
Price : $90 + postage(Paypal)
mail : [email protected]
>>1
You are copying Root from my blog.
Click to expand...
Click to collapse
unfortunately, sending it from Romania to Japan would cost me a bit to much, so, if there is an other way you can help me, i am listening...
Philipe9_person9 said:
If you can send a SCL22 in Japan, I can do a SIM unlock.
Price : $90 + postage(Paypal)
mail : [email protected]
>>1
You are copying Root from my blog.
Click to expand...
Click to collapse
Yep sending it to japan from srilanka is very diffcult. Can you guide us through email or skype to unlock it
Sent from my SCL22 using xda app-developers app
beast08 said:
i tried this method before, flashing the SuperSU v1.86 to my phone, but everytime im opening the app, it saying su binary need to update, abd the phone will reboot to CWM recovery, and when i checked it will Root Checker, it says the phone is not properly rooted.
Click to expand...
Click to collapse
I installed the CWM. but i can't go to the CWM recovery mode. What can be the reason ?
Related
Thought I'll create a thread for developers on LG G Pad 7.0/8.0/10.1
I'll try to keep it updated as best as I can. If I forget/get to busy, PM me and tell me what to change
Help Wanted:
If you own a LG G Pad 8.0/10.1, mind doing the following things? It'll help with kernel development/porting CM11/other ROMs
Dump partition list/info : instructions
Dump /system/build.prop
Possibly need root for stuff below
Dump aboot, boot and recovery partition : need partition list first before posting instructions. probably instructions below will continue to work
Code:
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/boot of=/sdcard/boot.img
dd if=/dev/block/platform/msm_sdcc.1/by-name/recovery of=/sdcard/recovery.img
LG G Pad 7.0
Model Name: v400
Released with KitKat 4.4.?
Kernel Source:
https://www.lg.com/global/support/opensource/opensourceList?types=ALL&search=v400
Root:
Towelroot works
Loki no longer works, can't bypass the locked bootloader to boot custom ROMs/kernels/recovery
Mode Name: v410 (LTE AT&T version)
Root: purpledrake works
LG G Pad 8.0
Unknown device.... not released yet?
LG G Pad 10.1
Model Name: v700, v700n (korean model?)
Released with KitKat 4.4.?
Kernel Source:
https://www.lg.com/global/support/opensource/opensourceList?types=ALL&search=v700
Root:
Towelroot works
paperWastage said:
Thought I'll create a thread for developers on LG G Pad 7.0/8.0/10.1
I'll try to keep it updated as best as I can. If I forget/get to busy, PM me and tell me what to change
Help Wanted:
If you own a LG G Pad 7.0/8.0/10.1, mind doing the following things? It'll help with kernel development/porting CM11/other ROMs
Dump partition list/info : instructions
Dump /system/build.prop
Possibly need root for stuff below
Dump aboot, boot and recovery partition : need partition list first before posting instructions. probably instructions below will continue to work
Code:
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/boot of=/sdcard/boot.img
dd if=/dev/block/platform/msm_sdcc.1/by-name/recovery of=/sdcard/recovery.img
Click to expand...
Click to collapse
Hi, I own a G pad 7.0. It seems that I am the only one in the world I'm gonna try to help a little:
1. Dump partition:
-lrwxrwxrwx root root 1970-03-05 03:01 DDR -> /dev/block/mmcblk0p25
lrwxrwxrwx root root 1970-03-05 03:01 aboot -> /dev/block/mmcblk0p6
lrwxrwxrwx root root 1970-03-05 03:01 abootb -> /dev/block/mmcblk0p9
lrwxrwxrwx root root 1970-03-05 03:01 boot -> /dev/block/mmcblk0p17
lrwxrwxrwx root root 1970-03-05 03:01 cache -> /dev/block/mmcblk0p33
lrwxrwxrwx root root 1970-03-05 03:01 cust -> /dev/block/mmcblk0p31
lrwxrwxrwx root root 1970-03-05 03:01 drm -> /dev/block/mmcblk0p26
lrwxrwxrwx root root 1970-03-05 03:01 eksst -> /dev/block/mmcblk0p10
lrwxrwxrwx root root 1970-03-05 03:01 encrypt -> /dev/block/mmcblk0p23
lrwxrwxrwx root root 1970-03-05 03:01 factory -> /dev/block/mmcblk0p28
lrwxrwxrwx root root 1970-03-05 03:01 fota -> /dev/block/mmcblk0p29
lrwxrwxrwx root root 1970-03-05 03:01 fsc -> /dev/block/mmcblk0p20
lrwxrwxrwx root root 1970-03-05 03:01 fsg -> /dev/block/mmcblk0p19
lrwxrwxrwx root root 1970-03-05 03:01 grow -> /dev/block/mmcblk0p35
lrwxrwxrwx root root 1970-03-05 03:01 laf -> /dev/block/mmcblk0p16
lrwxrwxrwx root root 1970-03-05 03:01 misc -> /dev/block/mmcblk0p14
lrwxrwxrwx root root 1970-03-05 03:01 modem -> /dev/block/mmcblk0p1
lrwxrwxrwx root root 1970-03-05 03:01 modemst1 -> /dev/block/mmcblk0p12
lrwxrwxrwx root root 1970-03-05 03:01 modemst2 -> /dev/block/mmcblk0p13
lrwxrwxrwx root root 1970-03-05 03:01 mpt -> /dev/block/mmcblk0p30
lrwxrwxrwx root root 1970-03-05 03:01 pad -> /dev/block/mmcblk0p11
lrwxrwxrwx root root 1970-03-05 03:01 persist -> /dev/block/mmcblk0p15
lrwxrwxrwx root root 1970-03-05 03:01 rct -> /dev/block/mmcblk0p24
lrwxrwxrwx root root 1970-03-05 03:01 recovery -> /dev/block/mmcblk0p18
lrwxrwxrwx root root 1970-03-05 03:01 rpm -> /dev/block/mmcblk0p3
lrwxrwxrwx root root 1970-03-05 03:01 rpmb -> /dev/block/mmcblk0p7
lrwxrwxrwx root root 1970-03-05 03:01 sbl1 -> /dev/block/mmcblk0p2
lrwxrwxrwx root root 1970-03-05 03:01 sbl1b -> /dev/block/mmcblk0p22
lrwxrwxrwx root root 1970-03-05 03:01 sdi -> /dev/block/mmcblk0p5
lrwxrwxrwx root root 1970-03-05 03:01 sns -> /dev/block/mmcblk0p27
lrwxrwxrwx root root 1970-03-05 03:01 ssd -> /dev/block/mmcblk0p21
lrwxrwxrwx root root 1970-03-05 03:01 system -> /dev/block/mmcblk0p32
lrwxrwxrwx root root 1970-03-05 03:01 tz -> /dev/block/mmcblk0p4
lrwxrwxrwx root root 1970-03-05 03:01 tzb -> /dev/block/mmcblk0p8
lrwxrwxrwx root root 1970-03-05 03:01 userdata -> /dev/block/mmcblk0p34
- Dump build.prop, boot, aboot and recovery:
http://www37.zippyshare.com/v/4146966/file.html
http://www37.zippyshare.com/v/66268524/file.html
http://www37.zippyshare.com/v/51126864/file.html
http://www37.zippyshare.com/v/44186789/file.html
http://www37.zippyshare.com/v/85458029/file.html
I think for now nothing can be done with it (there is no recovery yet). I hope something can be done.
Hammerhand.17 said:
Hi, I own a G pad 7.0. It seems that I am the only one in the world I'm gonna try to help a little:
1. Dump partition:
-lrwxrwxrwx root root 1970-03-05 03:01 DDR -> /dev/block/mmcblk0p25
lrwxrwxrwx root root 1970-03-05 03:01 aboot -> /dev/block/mmcblk0p6
lrwxrwxrwx root root 1970-03-05 03:01 abootb -> /dev/block/mmcblk0p9
lrwxrwxrwx root root 1970-03-05 03:01 boot -> /dev/block/mmcblk0p17
lrwxrwxrwx root root 1970-03-05 03:01 cache -> /dev/block/mmcblk0p33
lrwxrwxrwx root root 1970-03-05 03:01 cust -> /dev/block/mmcblk0p31
lrwxrwxrwx root root 1970-03-05 03:01 drm -> /dev/block/mmcblk0p26
lrwxrwxrwx root root 1970-03-05 03:01 eksst -> /dev/block/mmcblk0p10
lrwxrwxrwx root root 1970-03-05 03:01 encrypt -> /dev/block/mmcblk0p23
lrwxrwxrwx root root 1970-03-05 03:01 factory -> /dev/block/mmcblk0p28
lrwxrwxrwx root root 1970-03-05 03:01 fota -> /dev/block/mmcblk0p29
lrwxrwxrwx root root 1970-03-05 03:01 fsc -> /dev/block/mmcblk0p20
lrwxrwxrwx root root 1970-03-05 03:01 fsg -> /dev/block/mmcblk0p19
lrwxrwxrwx root root 1970-03-05 03:01 grow -> /dev/block/mmcblk0p35
lrwxrwxrwx root root 1970-03-05 03:01 laf -> /dev/block/mmcblk0p16
lrwxrwxrwx root root 1970-03-05 03:01 misc -> /dev/block/mmcblk0p14
lrwxrwxrwx root root 1970-03-05 03:01 modem -> /dev/block/mmcblk0p1
lrwxrwxrwx root root 1970-03-05 03:01 modemst1 -> /dev/block/mmcblk0p12
lrwxrwxrwx root root 1970-03-05 03:01 modemst2 -> /dev/block/mmcblk0p13
lrwxrwxrwx root root 1970-03-05 03:01 mpt -> /dev/block/mmcblk0p30
lrwxrwxrwx root root 1970-03-05 03:01 pad -> /dev/block/mmcblk0p11
lrwxrwxrwx root root 1970-03-05 03:01 persist -> /dev/block/mmcblk0p15
lrwxrwxrwx root root 1970-03-05 03:01 rct -> /dev/block/mmcblk0p24
lrwxrwxrwx root root 1970-03-05 03:01 recovery -> /dev/block/mmcblk0p18
lrwxrwxrwx root root 1970-03-05 03:01 rpm -> /dev/block/mmcblk0p3
lrwxrwxrwx root root 1970-03-05 03:01 rpmb -> /dev/block/mmcblk0p7
lrwxrwxrwx root root 1970-03-05 03:01 sbl1 -> /dev/block/mmcblk0p2
lrwxrwxrwx root root 1970-03-05 03:01 sbl1b -> /dev/block/mmcblk0p22
lrwxrwxrwx root root 1970-03-05 03:01 sdi -> /dev/block/mmcblk0p5
lrwxrwxrwx root root 1970-03-05 03:01 sns -> /dev/block/mmcblk0p27
lrwxrwxrwx root root 1970-03-05 03:01 ssd -> /dev/block/mmcblk0p21
lrwxrwxrwx root root 1970-03-05 03:01 system -> /dev/block/mmcblk0p32
lrwxrwxrwx root root 1970-03-05 03:01 tz -> /dev/block/mmcblk0p4
lrwxrwxrwx root root 1970-03-05 03:01 tzb -> /dev/block/mmcblk0p8
lrwxrwxrwx root root 1970-03-05 03:01 userdata -> /dev/block/mmcblk0p34
- Dump build.prop, boot, aboot and recovery:
http://www37.zippyshare.com/v/4146966/file.html
http://www37.zippyshare.com/v/66268524/file.html
http://www37.zippyshare.com/v/51126864/file.html
http://www37.zippyshare.com/v/44186789/file.html
http://www37.zippyshare.com/v/85458029/file.html
I think for now nothing can be done with it (there is no recovery yet). I hope something can be done.
Click to expand...
Click to collapse
thanks for this.
@icedmayhem also provided similar files over PM, forgot to post updates here...
anyways, it looks like this device has the patched aboot source code.
loki won't work anymore (loki provides a way for us to bypass the locked bootloader to load non-stock recovery/kernels. This means there isn't an easy way to boot a custom recovery(TWRP) or custom ROM.
Can you check if you can unlock the bootloader? Don't know if LG provides a process to do this easily (for GPE / non-GPE devices)
strings aboot.img | fgrep overlap
The erase group overlaps the max requested for erase
kernel/ramdisk addresses overlap with aboot addresses.
Device tree addresses overlap with aboot addresses.
Boot image buffer address overlaps with aboot addresses.
Signature read buffer address overlaps with aboot addresses.
Click to expand...
Click to collapse
I wish I now how to do it, but I have no idea of how to do this
FYI I was able to successfully root the G Pad 7.0 At&t version using purpledrake. LG-V410
idelgado782 said:
FYI I was able to successfully root the G Pad 7.0 At&t version using purpledrake. LG-V410
Click to expand...
Click to collapse
Link? Or just any of them?
Thxfor the info looking for it now.
Impala126 said:
Link? Or just any of them?
Thxfor the info looking for it now.
Click to expand...
Click to collapse
Here's the link to the purpledrake thread. Once you download and install on your computer make sure the gpad USB mode is on ptp mode.
http://forum.xda-developers.com/showthread.php?p=54254055
No matter what, I can never stay away from android for long.
idelgado782 said:
Here's the link to the purpledrake thread. Once you download and install on your computer make sure the gpad USB mode is on ptp mode.
http://forum.xda-developers.com/showthread.php?p=54254055
No matter what, I can never stay away from android for long.
Click to expand...
Click to collapse
Yup worked like a champ. Turned on air plane mode, then usb debugging and then ptp. But I had to go to a term win on win7 and run bat file from there. wouldn't run with admin rights from windows explore.
idelgado782 said:
FYI I was able to successfully root the G Pad 7.0 At&t version using purpledrake. LG-V410
Click to expand...
Click to collapse
for your G Pad 7.0 AT&T LTE version, mind posting the same items that Hammerhand.17 provided (for the G Pad 7.0)?
more info the better, just easier for the next developer to try to help out
paperWastage said:
LG G Pad 7.0
Model Name: v400
Released with KitKat 4.4.?
Root:
Towelroot works
Click to expand...
Click to collapse
It works also with a normal V400? I mean with NO at&t version.
(the site is towelroot.com, right?)
Yes, I have root in my normal V400 with no problem.
Hammerhand.17 said:
Yes, I have root in my normal V400 with no problem.
Click to expand...
Click to collapse
Thank you
Hammerhand.17 said:
Yes, I have root in my normal V400 with no problem.
Click to expand...
Click to collapse
One more question, it will work for sure on 4.4.2?
Has anyone tried or been successful pulling a factory image file for the LG V410 which is the AT&T G Pad 7.0? I tried the other day but there was not an image on their servers at that time
Giammysz said:
One more question, it will work for sure on 4.4.2?
Click to expand...
Click to collapse
Yes, 4.4.2 is the version of my tablet.
Giammysz said:
One more question, it will work for sure on 4.4.2?
Click to expand...
Click to collapse
Yes! Even if you have already did the OTA incremental update ..... You will need to install a SU manager though like Super SU etc after rooting with Towel root...
Hammerhand.17 said:
Yes, 4.4.2 is the version of my tablet.
Click to expand...
Click to collapse
Anthonol said:
Yes! Even if you have already did the OTA incremental update ..... You will need to install a SU manager though like Super SU etc after rooting with Towel root...
Click to expand...
Click to collapse
Thank you all
I successfully rooted my tab, it's really simple with towelroot! Install, tap and ready!
help my CWM for SM G360H
courier72 said:
help my CWM for SM G360H
Click to expand...
Click to collapse
attach your stock boot.img and stock recovery.img and I will try to help.
y300-0100 said:
attach your stock boot.img and stock recovery.img and i will try to help.
Click to expand...
Click to collapse
View attachment boot.img View attachment recovery.img
twrp recovery test version
try this recovery. if not working i made stock recovery flashable via odin.
sources are here for you to check out (partitions , names):
https://github.com/Y300-0100/twrp_samsung_core33gxx
recovery.tar.md5 not work CWM for Samsung SM G360H Galaxy Core Prime
hanyyyy said:
recovery.tar.md5 not work CWM for Samsung SM G360H Galaxy Core Prime
Click to expand...
Click to collapse
Its stock recovery. Just made for odin.
did you tried twrp recovery? .
Y300-0100 said:
Its stock recovery. Just made for odin.
did you tried twrp recovery? .
Click to expand...
Click to collapse
i tried twrp recovery to by Odin
not work to when i git in recovery mod its gif me boot log and never get in recovery mod at all
hanyyyy said:
recovery.tar.md5 not work CWM for Samsung SM G360H Galaxy Core Prime
Click to expand...
Click to collapse
Y300-0100
Maybe more, need other files? Can I help?
courier72 said:
Y300-0100
Maybe more, need other files? Can I help?
Click to expand...
Click to collapse
Full partition table by name and block number.
what not working little more details like black screen or stuck in splash screen etc.
logcat if possible.
"Not working " answer doesn't mean anything for me.
It's like " my blender is not working. Any solution?
:.
Y300-0100 said:
Full partition table by name and block number.
:.
Click to expand...
Click to collapse
how to do it?
Y300-0100 said:
what not working little more details like black screen or stuck in splash screen etc.
Click to expand...
Click to collapse
stuck in splash screen
courier72 said:
how to do it?
Click to expand...
Click to collapse
for my device command is this:
Code:
ls -al /dev/block/platform/sprd-sdhci.3/by-name
but for your you should check this for your device "sprd-sdhci.3"
Just check your fstab. Command is same as for G355HN
Code:
1|[email protected]:/ $ ls -al /dev/block/platform/sprd-sdhci.3/by-name
lrwxrwxrwx root root 2014-12-17 11:33 CSC -> /dev/block/mmcblk0p19
lrwxrwxrwx root root 2014-12-17 11:33 FIXNV1 -> /dev/block/mmcblk0p1
lrwxrwxrwx root root 2014-12-17 11:33 FIXNV2 -> /dev/block/mmcblk0p2
lrwxrwxrwx root root 2014-12-17 11:33 FOTA_SIG -> /dev/block/mmcblk0p9
lrwxrwxrwx root root 2014-12-17 11:33 HIDDEN -> /dev/block/mmcblk0p21
lrwxrwxrwx root root 2014-12-17 11:33 KERNEL -> /dev/block/mmcblk0p17
lrwxrwxrwx root root 2014-12-17 11:33 MODEM -> /dev/block/mmcblk0p7
lrwxrwxrwx root root 2014-12-17 11:33 MODEM_BACKUP -> /dev/block/mmcblk0p8
lrwxrwxrwx root root 2014-12-17 11:33 OTA -> /dev/block/mmcblk0p10
lrwxrwxrwx root root 2014-12-17 11:33 Odin_reserved -> /dev/block/mmcblk0p16
lrwxrwxrwx root root 2014-12-17 11:33 PARAM -> /dev/block/mmcblk0p13
lrwxrwxrwx root root 2014-12-17 11:33 RECOVERY -> /dev/block/mmcblk0p18lrwxrwxrwx root root 2014-12-17 11:33 RUNTIMENV1 -> /dev/block/mmcblk0p11
lrwxrwxrwx root root 2014-12-17 11:33 RUNTIMENV2 -> /dev/block/mmcblk0p12
lrwxrwxrwx root root 2014-12-17 11:33 SBL1 -> /dev/block/mmcblk0p3
lrwxrwxrwx root root 2014-12-17 11:33 SBL2 -> /dev/block/mmcblk0p4
lrwxrwxrwx root root 2014-12-17 11:33 WDSP -> /dev/block/mmcblk0p5
lrwxrwxrwx root root 2014-12-17 11:33 WDSP_BACKUP -> /dev/block/mmcblk0p6
lrwxrwxrwx root root 2014-12-17 11:33 efs -> /dev/block/mmcblk0p14
lrwxrwxrwx root root 2014-12-17 11:33 fixnv1 -> /dev/block/platform/sprd-sdhci.3/by-name/FIXNV2
lrwxrwxrwx root root 2014-12-17 11:33 fixnv2 -> /dev/block/platform/sprd-sdhci.3/by-name/FIXNV1
lrwxrwxrwx root root 2014-12-17 11:33 prodnv -> /dev/block/mmcblk0p15
lrwxrwxrwx root root 2014-12-17 11:33 runtimenv1 -> /dev/block/platform/sprd-sdhci.3/by-name/RUNTIMENV1
lrwxrwxrwx root root 2014-12-17 11:33 runtimenv2 -> /dev/block/platform/sprd-sdhci.3/by-name/RUNTIMENV2
lrwxrwxrwx root root 2014-12-17 11:33 system -> /dev/block/mmcblk0p20
lrwxrwxrwx root root 2014-12-17 11:33 userdata -> /dev/block/mmcblk0p22
Y300-0100 said:
Just check your fstab. Command is same as for G355HN
Click to expand...
Click to collapse
Is not entirely clear. To do this, you need a computer and Linux?
courier72 said:
Is not entirely clear. To do this, you need a computer and Linux?
Click to expand...
Click to collapse
Just install android terminal.( from play store ) Command work's with non roted phones also .
and you shoud get this:
.
Y300-0100 said:
Just install android terminal.
Click to expand...
Click to collapse
But I do not understand what to do next
courier72 said:
But I do not understand what to do next
Click to expand...
Click to collapse
Oopen terminal, type command from above and hit enter...
k/platform/sprd-sdhci.3/by-name <
lrwxrwxrwx root root 2015-03-02 22:43 CSC -> /dev/block/mmcblk0p22
lrwxrwxrwx root root 2015-03-02 22:43 FOTA_SIG -> /dev/block/mmcblk0p11
lrwxrwxrwx root root 2015-03-02 22:43 HIDDEN -> /dev/block/mmcblk0p24
lrwxrwxrwx root root 2015-03-02 22:43 KERNEL -> /dev/block/mmcblk0p20
lrwxrwxrwx root root 2015-03-02 22:43 MODEM -> /dev/block/mmcblk0p8
lrwxrwxrwx root root 2015-03-02 22:43 MODEM2 -> /dev/block/mmcblk0p9
lrwxrwxrwx root root 2015-03-02 22:43 PARAM -> /dev/block/mmcblk0p16
lrwxrwxrwx root root 2015-03-02 22:43 RECOVERY -> /dev/block/mmcblk0p21
lrwxrwxrwx root root 2015-03-02 22:43 RESERVED2 -> /dev/block/mmcblk0p19
lrwxrwxrwx root root 2015-03-02 22:43 SBOOT -> /dev/block/mmcblk0p1
lrwxrwxrwx root root 2015-03-02 22:43 SBOOT2 -> /dev/block/mmcblk0p2
lrwxrwxrwx root root 2015-03-02 22:43 TDDSP -> /dev/block/mmcblk0p10
lrwxrwxrwx root root 2015-03-02 22:43 WDSP -> /dev/block/mmcblk0p7
lrwxrwxrwx root root 2015-03-02 22:43 efs -> /dev/block/mmcblk0p17
lrwxrwxrwx root root 2015-03-02 22:43 prodnv -> /dev/block/mmcblk0p18
lrwxrwxrwx root root 2015-03-02 22:43 system -> /dev/block/mmcblk0p23
lrwxrwxrwx root root 2015-03-02 22:43 tdfixnv1 -> /dev/block/mmcblk0p5
lrwxrwxrwx root root 2015-03-02 22:43 tdfixnv2 -> /dev/block/mmcblk0p6
lrwxrwxrwx root root 2015-03-02 22:43 tdruntimenv1 -> /dev/block/mmcblk0p14
lrwxrwxrwx root root 2015-03-02 22:43 tdruntimenv2 -> /dev/block/mmcblk0p15
lrwxrwxrwx root root 2015-03-02 22:43 userdata -> /dev/block/mmcblk0p25
lrwxrwxrwx root root 2015-03-02 22:43 wfixnv1 -> /dev/block/mmcblk0p3
lrwxrwxrwx root root 2015-03-02 22:43 wfixnv2 -> /dev/block/mmcblk0p4
lrwxrwxrwx root root 2015-03-02 22:43 wruntimenv1 -> /dev/block/mmcblk0p12
lrwxrwxrwx root root 2015-03-02 22:43 wruntimenv2 -> /dev/block/mmcblk0p13
[email protected]:/ $
Y300-0100 said:
Full partition table by name and block number.
what not working little more details like black screen or stuck in splash screen etc.
logcat if possible.
"Not working " answer doesn't mean anything for me.
It's like " my blender is not working. Any solution?
:.
Click to expand...
Click to collapse
stuck in splash screen
and this is the Full partition table by name and block number
ਊock/platform/sprd-sdhci.3/by-name <
lrwxrwxrwx root root 2015-03-02 21:27 CSC -> /dev/block/mmcblk0p22
lrwxrwxrwx root root 2015-03-02 21:27 FOTA_SIG -> /dev/block/mmcblk0p11
lrwxrwxrwx root root 2015-03-02 21:27 HIDDEN -> /dev/block/mmcblk0p24
lrwxrwxrwx root root 2015-03-02 21:27 KERNEL -> /dev/block/mmcblk0p20
lrwxrwxrwx root root 2015-03-02 21:27 MODEM -> /dev/block/mmcblk0p8
lrwxrwxrwx root root 2015-03-02 21:27 MODEM2 -> /dev/block/mmcblk0p9
lrwxrwxrwx root root 2015-03-02 21:27 PARAM -> /dev/block/mmcblk0p16
lrwxrwxrwx root root 2015-03-02 21:27 RECOVERY -> /dev/block/mmcblk0p21
lrwxrwxrwx root root 2015-03-02 21:27 RESERVED2 -> /dev/block/mmcblk0p19
lrwxrwxrwx root root 2015-03-02 21:27 SBOOT -> /dev/block/mmcblk0p1
lrwxrwxrwx root root 2015-03-02 21:27 SBOOT2 -> /dev/block/mmcblk0p2
lrwxrwxrwx root root 2015-03-02 21:27 TDDSP -> /dev/block/mmcblk0p10
lrwxrwxrwx root root 2015-03-02 21:27 WDSP -> /dev/block/mmcblk0p7
lrwxrwxrwx root root 2015-03-02 21:27 efs -> /dev/block/mmcblk0p17
lrwxrwxrwx root root 2015-03-02 21:27 prodnv -> /dev/block/mmcblk0p18
lrwxrwxrwx root root 2015-03-02 21:27 system -> /dev/block/mmcblk0p23
lrwxrwxrwx root root 2015-03-02 21:27 tdfixnv1 -> /dev/block/mmcblk0p5
lrwxrwxrwx root root 2015-03-02 21:27 tdfixnv2 -> /dev/block/mmcblk0p6
lrwxrwxrwx root root 2015-03-02 21:27 tdruntimenv1 -> /dev/block/mmcblk0p14
lrwxrwxrwx root root 2015-03-02 21:27 tdruntimenv2 -> /dev/block/mmcblk0p15
lrwxrwxrwx root root 2015-03-02 21:27 userdata -> /dev/block/mmcblk0p25
lrwxrwxrwx root root 2015-03-02 21:27 wfixnv1 -> /dev/block/mmcblk0p3
lrwxrwxrwx root root 2015-03-02 21:27 wfixnv2 -> /dev/block/mmcblk0p4
lrwxrwxrwx root root 2015-03-02 21:27 wruntimenv1 -> /dev/block/mmcblk0p12
lrwxrwxrwx root root 2015-03-02 21:27 wruntimenv2 -> /dev/block/mmcblk0p13
[email protected]:/ $
�
Cwm for samsung galaxy core prime
Any one can plz make cwm for core prime
twrp recovery test version
Changes I made :
https://github.com/Y300-0100/twrp_samsung_core33gxx/commit/8dde6d106ef5abf6ea52203d13091cb1b11480be
I will upload test build later
Im not really a dev but i know my way around android. I figured this could help kickstart development for us. I have pulled my boot.img and attached it below.
Here are the mount points for building a rom. May differ from the different varients. My model is XT1527 US LTE.
HTML:
ls -al /dev/block/platform/soc.0/by-name
lrwxrwxrwx root root 1970-01-23 12:12 DDR -> /dev/block/mmcblk0p3
lrwxrwxrwx root root 1970-01-23 12:12 aboot -> /dev/block/mmcblk0p4
lrwxrwxrwx root root 1970-01-23 12:12 abootBackup -> /dev/block/mmcblk0p14
lrwxrwxrwx root root 1970-01-23 12:12 boot -> /dev/block/mmcblk0p33
lrwxrwxrwx root root 1970-01-23 12:12 cache -> /dev/block/mmcblk0p43
lrwxrwxrwx root root 1970-01-23 12:12 carrier -> /dev/block/mmcblk0p41
lrwxrwxrwx root root 1970-01-23 12:12 cid -> /dev/block/mmcblk0p28
lrwxrwxrwx root root 1970-01-23 12:12 clogo -> /dev/block/mmcblk0p30
lrwxrwxrwx root root 1970-01-23 12:12 dhob -> /dev/block/mmcblk0p24
lrwxrwxrwx root root 1970-01-23 12:12 factorytune1 -> /dev/block/mmcblk0p11
lrwxrwxrwx root root 1970-01-23 12:12 factorytune2 -> /dev/block/mmcblk0p35
lrwxrwxrwx root root 1970-01-23 12:12 frp -> /dev/block/mmcblk0p20
lrwxrwxrwx root root 1970-01-23 12:12 fsc -> /dev/block/mmcblk0p26
lrwxrwxrwx root root 1970-01-23 12:12 fsg -> /dev/block/mmcblk0p25
lrwxrwxrwx root root 1970-01-23 12:12 hob -> /dev/block/mmcblk0p23
lrwxrwxrwx root root 1970-01-23 12:12 hyp -> /dev/block/mmcblk0p7
lrwxrwxrwx root root 1970-01-23 12:12 hypBackup -> /dev/block/mmcblk0p18
lrwxrwxrwx root root 1970-01-23 12:12 keystore -> /dev/block/mmcblk0p39
lrwxrwxrwx root root 1970-01-23 12:12 kpan -> /dev/block/mmcblk0p36
lrwxrwxrwx root root 1970-01-23 12:12 logo -> /dev/block/mmcblk0p29
lrwxrwxrwx root root 1970-01-23 12:12 logs -> /dev/block/mmcblk0p9
lrwxrwxrwx root root 1970-01-23 12:12 metadata -> /dev/block/mmcblk0p13
lrwxrwxrwx root root 1970-01-23 12:12 misc -> /dev/block/mmcblk0p32
lrwxrwxrwx root root 1970-01-23 12:12 modem -> /dev/block/mmcblk0p1
lrwxrwxrwx root root 1970-01-23 12:12 modemst1 -> /dev/block/mmcblk0p21
lrwxrwxrwx root root 1970-01-23 12:12 modemst2 -> /dev/block/mmcblk0p22
lrwxrwxrwx root root 1970-01-23 12:12 oem -> /dev/block/mmcblk0p40
lrwxrwxrwx root root 1970-01-23 12:12 padA -> /dev/block/mmcblk0p12
lrwxrwxrwx root root 1970-01-23 12:12 padB -> /dev/block/mmcblk0p19
lrwxrwxrwx root root 1970-01-23 12:12 padC -> /dev/block/mmcblk0p37
lrwxrwxrwx root root 1970-01-23 12:12 persist -> /dev/block/mmcblk0p31
lrwxrwxrwx root root 1970-01-23 12:12 recovery -> /dev/block/mmcblk0p34
lrwxrwxrwx root root 1970-01-23 12:12 rpm -> /dev/block/mmcblk0p5
lrwxrwxrwx root root 1970-01-23 12:12 rpmBackup -> /dev/block/mmcblk0p15
lrwxrwxrwx root root 1970-01-23 12:12 sbl1 -> /dev/block/mmcblk0p2
lrwxrwxrwx root root 1970-01-23 12:12 sec -> /dev/block/mmcblk0p10
lrwxrwxrwx root root 1970-01-23 12:12 sp -> /dev/block/mmcblk0p38
lrwxrwxrwx root root 1970-01-23 12:12 ssd -> /dev/block/mmcblk0p27
lrwxrwxrwx root root 1970-01-23 12:12 system -> /dev/block/mmcblk0p42
lrwxrwxrwx root root 1970-01-23 12:12 tz -> /dev/block/mmcblk0p6
lrwxrwxrwx root root 1970-01-23 12:12 tzBackup -> /dev/block/mmcblk0p16
lrwxrwxrwx root root 1970-01-23 12:12 userdata -> /dev/block/mmcblk0p44
lrwxrwxrwx root root 1970-01-23 12:12 utags -> /dev/block/mmcblk0p8
lrwxrwxrwx root root 1970-01-23 12:12 utagsBackup -> /dev/block/mmcblk0p17
Excellent.... Thank u....I will try to release a ROM within a week
Shawn5162 said:
Excellent.... Thank u....I will try to release a ROM within a week
Click to expand...
Click to collapse
good news, good luck for your build
Shawn5162 said:
Excellent.... Thank u....I will try to release a ROM within a week
Click to expand...
Click to collapse
awesome, if you need a tester, please pm.
Shawn5162 said:
Excellent.... Thank u....I will try to release a ROM within a week
Click to expand...
Click to collapse
Shawn, you got a Moto E 2015? :laugh:
I find myself fortunate getting MotoG 2015 n Moto E 2015, both being worked upon by you! Thanks man!
If anybody who us good at linux knows how to add these mount points to cwm or philz touch im trying to port a build for us pm me.
WIFI tethering
I just picked this phone up today and cricket has ripped out the WIFI tethering. If anyone has a stock rooted rom please send me a link.
Mounting points are different on my cmda moto e2 will try to upload them later
bzo22 said:
Mounting points are different on my cmda moto e2 will try to upload them later
Click to expand...
Click to collapse
yup the cdma models and the 3g only models will probably have different mounts.
cmda xt1526 boostmobile surina
s -al /dev/block/platform/soc.0/by-name <
/dev/block/platform/soc.0/by-name: Permission denied
1|[email protected]_cdma:/ $ su
s -al /dev/block/platform/soc.0/by-name <
lrwxrwxrwx root root 1970-01-31 14:18 DDR -> /dev/block/mmcblk0p3
lrwxrwxrwx root root 1970-01-31 14:18 aboot -> /dev/block/mmcblk0p4
lrwxrwxrwx root root 1970-01-31 14:18 abootBackup -> /dev/block/mmcblk0p14
lrwxrwxrwx root root 1970-01-31 14:18 boot -> /dev/block/mmcblk0p33
lrwxrwxrwx root root 1970-01-31 14:18 cache -> /dev/block/mmcblk0p42
lrwxrwxrwx root root 1970-01-31 14:18 carrier -> /dev/block/mmcblk0p40
lrwxrwxrwx root root 1970-01-31 14:18 cid -> /dev/block/mmcblk0p28
lrwxrwxrwx root root 1970-01-31 14:18 clogo -> /dev/block/mmcblk0p30
lrwxrwxrwx root root 1970-01-31 14:18 dhob -> /dev/block/mmcblk0p24
lrwxrwxrwx root root 1970-01-31 14:18 factorytune1 -> /dev/block/mmcblk0p11
lrwxrwxrwx root root 1970-01-31 14:18 factorytune2 -> /dev/block/mmcblk0p35
lrwxrwxrwx root root 1970-01-31 14:18 frp -> /dev/block/mmcblk0p20
lrwxrwxrwx root root 1970-01-31 14:18 fsc -> /dev/block/mmcblk0p26
lrwxrwxrwx root root 1970-01-31 14:18 fsg -> /dev/block/mmcblk0p25
lrwxrwxrwx root root 1970-01-31 14:18 hob -> /dev/block/mmcblk0p23
lrwxrwxrwx root root 1970-01-31 14:18 hyp -> /dev/block/mmcblk0p7
lrwxrwxrwx root root 1970-01-31 14:18 hypBackup -> /dev/block/mmcblk0p18
lrwxrwxrwx root root 1970-01-31 14:18 keystore -> /dev/block/mmcblk0p39
lrwxrwxrwx root root 1970-01-31 14:18 kpan -> /dev/block/mmcblk0p36
lrwxrwxrwx root root 1970-01-31 14:18 logo -> /dev/block/mmcblk0p29
lrwxrwxrwx root root 1970-01-31 14:18 logs -> /dev/block/mmcblk0p9
lrwxrwxrwx root root 1970-01-31 14:18 metadata -> /dev/block/mmcblk0p13
lrwxrwxrwx root root 1970-01-31 14:18 misc -> /dev/block/mmcblk0p32
lrwxrwxrwx root root 1970-01-31 14:18 modem -> /dev/block/mmcblk0p1
lrwxrwxrwx root root 1970-01-31 14:18 modemst1 -> /dev/block/mmcblk0p21
lrwxrwxrwx root root 1970-01-31 14:18 modemst2 -> /dev/block/mmcblk0p22
lrwxrwxrwx root root 1970-01-31 14:18 padA -> /dev/block/mmcblk0p12
lrwxrwxrwx root root 1970-01-31 14:18 padB -> /dev/block/mmcblk0p19
lrwxrwxrwx root root 1970-01-31 14:18 padC -> /dev/block/mmcblk0p37
lrwxrwxrwx root root 1970-01-31 14:18 persist -> /dev/block/mmcblk0p31
lrwxrwxrwx root root 1970-01-31 14:18 recovery -> /dev/block/mmcblk0p34
lrwxrwxrwx root root 1970-01-31 14:18 rpm -> /dev/block/mmcblk0p5
lrwxrwxrwx root root 1970-01-31 14:18 rpmBackup -> /dev/block/mmcblk0p15
lrwxrwxrwx root root 1970-01-31 14:18 sbl1 -> /dev/block/mmcblk0p2
lrwxrwxrwx root root 1970-01-31 14:18 sec -> /dev/block/mmcblk0p10
lrwxrwxrwx root root 1970-01-31 14:18 sp -> /dev/block/mmcblk0p38
lrwxrwxrwx root root 1970-01-31 14:18 ssd -> /dev/block/mmcblk0p27
lrwxrwxrwx root root 1970-01-31 14:18 system -> /dev/block/mmcblk0p41
lrwxrwxrwx root root 1970-01-31 14:18 tz -> /dev/block/mmcblk0p6
lrwxrwxrwx root root 1970-01-31 14:18 tzBackup -> /dev/block/mmcblk0p16
lrwxrwxrwx root root 1970-01-31 14:18 userdata -> /dev/block/mmcblk0p43
lrwxrwxrwx root root 1970-01-31 14:18 utags -> /dev/block/mmcblk0p8
lrwxrwxrwx root root 1970-01-31 14:18 utagsBackup -> /dev/block/mmcblk0p17
[email protected]_cdma:/ #
bzo22 said:
s -al /dev/block/platform/soc.0/by-name <
<SNIP>
[email protected]_cdma:/ #
Click to expand...
Click to collapse
How did you get root on the xt1526 boost phone bzo22? Any chance you could post the stock boot loader img file or direct me to a working copy of a bootloader for it?
phliptrip said:
How did you get root on the xt1526 boost phone bzo22? Any chance you could post the stock boot loader img file or direct me to a working copy of a bootloader for it?
Click to expand...
Click to collapse
I used twrp to flash super user the recovery works for our device too...but do not flash it just boot it from fastboot. Which partition is boot loader stored . is it aboot or boot section
aboot.img
bzo22 said:
I used twrp to flash super user the recovery works for our device too...but do not flash it just boot it from fastboot. Which partition is boot loader stored . is it aboot or boot section
Click to expand...
Click to collapse
Here u go the aboot.img
Rooted this Phone
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
phliptrip said:
How did you get root on the xt1526 boost phone bzo22? Any chance you could post the stock boot loader img file or direct me to a working copy of a bootloader for it?
Click to expand...
Click to collapse
---------- Post added at 08:32 PM ---------- Previous post was at 08:29 PM ----------
i have root on this phone look and see.
http://imgur.com/tll9LYH,TeVRm5I,4dBA7v5,TdZJI1m,vJyFZEa
---------- Post added at 08:35 PM ---------- Previous post was at 08:32 PM ----------
here are some more pictures of my phone.
http://imgur.com/tll9LYH,TeVRm5I,4dBA7v5,TdZJI1m,vJyFZEa#1
http://imgur.com/tll9LYH,TeVRm5I,4dBA7v5,TdZJI1m,vJyFZEa#2
http://imgur.com/tll9LYH,TeVRm5I,4dBA7v5,TdZJI1m,vJyFZEa#3
http://imgur.com/tll9LYH,TeVRm5I,4dBA7v5,TdZJI1m,vJyFZEa#4.
there you go. im not giving you the files.because i can
fix-this! said:
Im not really a dev but i know my way around android. I figured this could help kickstart development for us. I have pulled my boot.img and attached it below.
Here are the mount points for building a rom. May differ from the different varients. My model is XT1527 US LTE.
HTML:
ls -al /dev/block/platform/soc.0/by-name
lrwxrwxrwx root root 1970-01-23 12:12 DDR -> /dev/block/mmcblk0p3
lrwxrwxrwx root root 1970-01-23 12:12 aboot -> /dev/block/mmcblk0p4
lrwxrwxrwx root root 1970-01-23 12:12 abootBackup -> /dev/block/mmcblk0p14
lrwxrwxrwx root root 1970-01-23 12:12 boot -> /dev/block/mmcblk0p33
lrwxrwxrwx root root 1970-01-23 12:12 cache -> /dev/block/mmcblk0p43
lrwxrwxrwx root root 1970-01-23 12:12 carrier -> /dev/block/mmcblk0p41
lrwxrwxrwx root root 1970-01-23 12:12 cid -> /dev/block/mmcblk0p28
lrwxrwxrwx root root 1970-01-23 12:12 clogo -> /dev/block/mmcblk0p30
lrwxrwxrwx root root 1970-01-23 12:12 dhob -> /dev/block/mmcblk0p24
lrwxrwxrwx root root 1970-01-23 12:12 factorytune1 -> /dev/block/mmcblk0p11
lrwxrwxrwx root root 1970-01-23 12:12 factorytune2 -> /dev/block/mmcblk0p35
lrwxrwxrwx root root 1970-01-23 12:12 frp -> /dev/block/mmcblk0p20
lrwxrwxrwx root root 1970-01-23 12:12 fsc -> /dev/block/mmcblk0p26
lrwxrwxrwx root root 1970-01-23 12:12 fsg -> /dev/block/mmcblk0p25
lrwxrwxrwx root root 1970-01-23 12:12 hob -> /dev/block/mmcblk0p23
lrwxrwxrwx root root 1970-01-23 12:12 hyp -> /dev/block/mmcblk0p7
lrwxrwxrwx root root 1970-01-23 12:12 hypBackup -> /dev/block/mmcblk0p18
lrwxrwxrwx root root 1970-01-23 12:12 keystore -> /dev/block/mmcblk0p39
lrwxrwxrwx root root 1970-01-23 12:12 kpan -> /dev/block/mmcblk0p36
lrwxrwxrwx root root 1970-01-23 12:12 logo -> /dev/block/mmcblk0p29
lrwxrwxrwx root root 1970-01-23 12:12 logs -> /dev/block/mmcblk0p9
lrwxrwxrwx root root 1970-01-23 12:12 metadata -> /dev/block/mmcblk0p13
lrwxrwxrwx root root 1970-01-23 12:12 misc -> /dev/block/mmcblk0p32
lrwxrwxrwx root root 1970-01-23 12:12 modem -> /dev/block/mmcblk0p1
lrwxrwxrwx root root 1970-01-23 12:12 modemst1 -> /dev/block/mmcblk0p21
lrwxrwxrwx root root 1970-01-23 12:12 modemst2 -> /dev/block/mmcblk0p22
lrwxrwxrwx root root 1970-01-23 12:12 oem -> /dev/block/mmcblk0p40
lrwxrwxrwx root root 1970-01-23 12:12 padA -> /dev/block/mmcblk0p12
lrwxrwxrwx root root 1970-01-23 12:12 padB -> /dev/block/mmcblk0p19
lrwxrwxrwx root root 1970-01-23 12:12 padC -> /dev/block/mmcblk0p37
lrwxrwxrwx root root 1970-01-23 12:12 persist -> /dev/block/mmcblk0p31
lrwxrwxrwx root root 1970-01-23 12:12 recovery -> /dev/block/mmcblk0p34
lrwxrwxrwx root root 1970-01-23 12:12 rpm -> /dev/block/mmcblk0p5
lrwxrwxrwx root root 1970-01-23 12:12 rpmBackup -> /dev/block/mmcblk0p15
lrwxrwxrwx root root 1970-01-23 12:12 sbl1 -> /dev/block/mmcblk0p2
lrwxrwxrwx root root 1970-01-23 12:12 sec -> /dev/block/mmcblk0p10
lrwxrwxrwx root root 1970-01-23 12:12 sp -> /dev/block/mmcblk0p38
lrwxrwxrwx root root 1970-01-23 12:12 ssd -> /dev/block/mmcblk0p27
lrwxrwxrwx root root 1970-01-23 12:12 system -> /dev/block/mmcblk0p42
lrwxrwxrwx root root 1970-01-23 12:12 tz -> /dev/block/mmcblk0p6
lrwxrwxrwx root root 1970-01-23 12:12 tzBackup -> /dev/block/mmcblk0p16
lrwxrwxrwx root root 1970-01-23 12:12 userdata -> /dev/block/mmcblk0p44
lrwxrwxrwx root root 1970-01-23 12:12 utags -> /dev/block/mmcblk0p8
lrwxrwxrwx root root 1970-01-23 12:12 utagsBackup -> /dev/block/mmcblk0p17
Click to expand...
Click to collapse
hey bro i needed some help. first can this boot image be used for 3g version.
If not then please can you tell me how to extract the boot.img of moto e 3g version
I've got the XT1527 for cricket and I'm willing to test. I'm no dev but ive been flashing roms constantly on all sorts of devices for a few years and id like to get involved and learn more if possible. This is my daily driver though so I might be a little cautious until there's a working twrp or something for the US version but this is a good phone so I'm very eager to see what ends up being made for this phone. Normally I'll look a phone up before buying it to make sure there's plenty of stuff available to keep me busy with it but when I saw this one had very little I actually got excited since Im sure this one will wind up with some good stuff and for the first time I won't be starting with a phone months after the forum died down lol
hakr4life said:
I've got the XT1527 for cricket and I'm willing to test. I'm no dev but ive been flashing roms constantly on all sorts of devices for a few years and id like to get involved and learn more if possible. This is my daily driver though so I might be a little cautious until there's a working twrp or something for the US version but this is a good phone so I'm very eager to see what ends up being made for this phone. Normally I'll look a phone up before buying it to make sure there's plenty of stuff available to keep me busy with it but when I saw this one had very little I actually got excited since Im sure this one will wind up with some good stuff and for the first time I won't be starting with a phone months after the forum died down lol
Click to expand...
Click to collapse
Same here keep me in the loop. I'm eager to brick my new phone
Sent from my MotoE2(4G-LTE) using XDA Free mobile app
+1 for at%t/aio/cricket users on the XT1527 model. there has got to be a workaround for the unlock on this. @mdewii23 @hakr4life
Can someone provide stock recovery?
I've scoured the internet over and over and come up with nothing yet
Sent from my Nexus 4 using XDA Free mobile app
Hello, everyone.
Since the ROM version on my OPT is not available for download (I got a phone with Oxygen 2.0.3), I decided to make a flashable image. This is the first time I do this, and I am kind of lost.
From this guide, I gathered that I need to find boot, kernel, system and misc partitions. Here are the partitions on OPT:
Code:
ls -al /dev/block/platform/f9824900.sdhci/by-name
lrwxrwxrwx root root 1970-01-24 09:32 DDR -> /dev/block/mmcblk0p6
lrwxrwxrwx root root 1970-01-24 09:32 DRIVER -> /dev/block/mmcblk0p25
lrwxrwxrwx root root 1970-01-24 09:32 LOGO -> /dev/block/mmcblk0p24
lrwxrwxrwx root root 1970-01-24 09:32 aboot -> /dev/block/mmcblk0p10
lrwxrwxrwx root root 1970-01-24 09:32 abootbak -> /dev/block/mmcblk0p11
lrwxrwxrwx root root 1970-01-24 09:32 apdp -> /dev/block/mmcblk0p12
lrwxrwxrwx root root 1970-01-24 09:32 bluetooth -> /dev/block/mmcblk0p2
lrwxrwxrwx root root 1970-01-24 09:32 boot -> /dev/block/mmcblk0p35
lrwxrwxrwx root root 1970-01-24 09:32 cache -> /dev/block/mmcblk0p41
lrwxrwxrwx root root 1970-01-24 09:32 config -> /dev/block/mmcblk0p40
lrwxrwxrwx root root 1970-01-24 09:32 devinfo -> /dev/block/mmcblk0p9
lrwxrwxrwx root root 1970-01-24 09:32 dpo -> /dev/block/mmcblk0p14
lrwxrwxrwx root root 1970-01-24 09:32 fsc -> /dev/block/mmcblk0p15
lrwxrwxrwx root root 1970-01-24 09:32 fsg -> /dev/block/mmcblk0p8
lrwxrwxrwx root root 1970-01-24 09:32 hyp -> /dev/block/mmcblk0p33
lrwxrwxrwx root root 1970-01-24 09:32 hypbak -> /dev/block/mmcblk0p34
lrwxrwxrwx root root 1970-01-24 09:32 keystore -> /dev/block/mmcblk0p39
lrwxrwxrwx root root 1970-01-24 09:32 limits -> /dev/block/mmcblk0p5
lrwxrwxrwx root root 1970-01-24 09:32 misc -> /dev/block/mmcblk0p38
lrwxrwxrwx root root 1970-01-24 09:32 modem -> /dev/block/mmcblk0p1
lrwxrwxrwx root root 1970-01-24 09:32 modemst1 -> /dev/block/mmcblk0p17
lrwxrwxrwx root root 1970-01-24 09:32 modemst2 -> /dev/block/mmcblk0p18
lrwxrwxrwx root root 1970-01-24 09:32 msadp -> /dev/block/mmcblk0p13
lrwxrwxrwx root root 1970-01-24 09:32 oem_dycnvbk -> /dev/block/mmcblk0p19
lrwxrwxrwx root root 1970-01-24 09:32 oem_stanvbk -> /dev/block/mmcblk0p20
lrwxrwxrwx root root 1970-01-24 09:32 param -> /dev/block/mmcblk0p21
lrwxrwxrwx root root 1970-01-24 09:32 persist -> /dev/block/mmcblk0p37
lrwxrwxrwx root root 1970-01-24 09:32 pmic -> /dev/block/mmcblk0p3
lrwxrwxrwx root root 1970-01-24 09:32 pmicbak -> /dev/block/mmcblk0p4
lrwxrwxrwx root root 1970-01-24 09:32 recovery -> /dev/block/mmcblk0p36
lrwxrwxrwx root root 1970-01-24 09:32 reserve1 -> /dev/block/mmcblk0p22
lrwxrwxrwx root root 1970-01-24 09:32 reserve2 -> /dev/block/mmcblk0p23
lrwxrwxrwx root root 1970-01-24 09:32 rpm -> /dev/block/mmcblk0p31
lrwxrwxrwx root root 1970-01-24 09:32 rpmbak -> /dev/block/mmcblk0p32
lrwxrwxrwx root root 1970-01-24 09:32 sbl1 -> /dev/block/mmcblk0p26
lrwxrwxrwx root root 1970-01-24 09:32 sbl1bak -> /dev/block/mmcblk0p27
lrwxrwxrwx root root 1970-01-24 09:32 sdi -> /dev/block/mmcblk0p28
lrwxrwxrwx root root 1970-01-24 09:32 sec -> /dev/block/mmcblk0p7
lrwxrwxrwx root root 1970-01-24 09:32 ssd -> /dev/block/mmcblk0p16
lrwxrwxrwx root root 1970-01-24 09:32 system -> /dev/block/mmcblk0p42
lrwxrwxrwx root root 1970-01-24 09:32 tz -> /dev/block/mmcblk0p29
lrwxrwxrwx root root 1970-01-24 09:32 tzbak -> /dev/block/mmcblk0p30
lrwxrwxrwx root root 1970-01-24 09:32 userdata -> /dev/block/mmcblk0p43
I see boot, system, and misc, but no kernel (there is kernel in the file system, though, I imagine it could be part of system), and I also see a bunch of strange names and a bunch of important-looking names.
Something tells me that Driver, DDR, Logo are somehow important and then there are modem and stuff, and tz looks important enough to back it up. Does anyone know what this all means? I saw links to stock Oxygen ROMs, so I imagine someone knows how to dump it.
Hey,
It's cool that you are trying to do this. Maybe try & send this guy a dm: Naman Bhalla
He's posted several other OxygenOS images, so I'm positive he can guide you in the process.
One interesting thing I noticed:
One OPT lets me connect ADB while it's in recovery rom. That is also automatically root if you do adb shell.
Another OPT does not let me connect with ADB at all. It also does not let me pick a proper ADB driver and insits on using a nexus driver instead. Very strange.
so uhm yeah i need edify_defs for G360H but it's a Spreadtrum chip and i only find example for MTD and EMMC ( it's a chip or what ?? MTD is a chip but wth is EMMC chip ?? i'm so confuse )
can someone pls share that file with me and if you need specific details of mount point , it's all be low boiiii
Thx and pls help
[email protected]:/ $ ls -la /dev/block/platform/sprd-sdhci.3/by-name
lrwxrwxrwx root root 2018-04-15 02:30 CSC -> /dev/block/mmcblk0p22
lrwxrwxrwx root root 2018-04-15 02:30 FOTA_SIG -> /dev/block/mmcblk0p11
lrwxrwxrwx root root 2018-04-15 02:30 HIDDEN -> /dev/block/mmcblk0p24
lrwxrwxrwx root root 2018-04-15 02:30 KERNEL -> /dev/block/mmcblk0p20
lrwxrwxrwx root root 2018-04-15 02:30 MODEM -> /dev/block/mmcblk0p8
lrwxrwxrwx root root 2018-04-15 02:30 MODEM2 -> /dev/block/mmcblk0p9
lrwxrwxrwx root root 2018-04-15 02:30 PARAM -> /dev/block/mmcblk0p16
lrwxrwxrwx root root 2018-04-15 02:30 RECOVERY -> /dev/block/mmcblk0p21
lrwxrwxrwx root root 2018-04-15 02:30 RESERVED2 -> /dev/block/mmcblk0p19
lrwxrwxrwx root root 2018-04-15 02:30 SBOOT -> /dev/block/mmcblk0p1
lrwxrwxrwx root root 2018-04-15 02:30 SBOOT2 -> /dev/block/mmcblk0p2
lrwxrwxrwx root root 2018-04-15 02:30 TDDSP -> /dev/block/mmcblk0p10
lrwxrwxrwx root root 2018-04-15 02:30 WDSP -> /dev/block/mmcblk0p7
lrwxrwxrwx root root 2018-04-15 02:30 efs -> /dev/block/mmcblk0p17
lrwxrwxrwx root root 2018-04-15 02:30 prodnv -> /dev/block/mmcblk0p18
lrwxrwxrwx root root 2018-04-15 02:30 system -> /dev/block/mmcblk0p23
lrwxrwxrwx root root 2018-04-15 02:30 tdfixnv1 -> /dev/block/mmcblk0p5
lrwxrwxrwx root root 2018-04-15 02:30 tdfixnv2 -> /dev/block/mmcblk0p6
lrwxrwxrwx root root 2018-04-15 02:30 tdruntimenv1 -> /dev/block/mmcblk0p14
lrwxrwxrwx root root 2018-04-15 02:30 tdruntimenv2 -> /dev/block/mmcblk0p15
lrwxrwxrwx root root 2018-04-15 02:30 userdata -> /dev/block/mmcblk0p25
lrwxrwxrwx root root 2018-04-15 02:30 wfixnv1 -> /dev/block/mmcblk0p3
lrwxrwxrwx root root 2018-04-15 02:30 wfixnv2 -> /dev/block/mmcblk0p4
lrwxrwxrwx root root 2018-04-15 02:30 wruntimenv1 -> /dev/block/mmcblk0p12
lrwxrwxrwx root root 2018-04-15 02:30 wruntimenv2 -> /dev/block/mmcblk0p13
[email protected]:/ $
I haven't got what you want!
What files you need?