I know --- the bootloader is locked. But I still had to prove it to myself. And the info provided here may be useful to developers as well as to end-users.
Here is my story:
Running stock KK 4.4.2 (NCE) on my G900A, I successfully rooted using GeoHot’s towelroot https://towelroot.com/.
Then I froze the AT&T software updater app via Titanium Backup Pro --- since there is presently no way to re-root after updating.
Then I modified the stock recovery image to enable “adbd” (Android Debug Bridge daemon). Here’s a brief description of the process:
Running ADB with root and busybox installed, I created directory: /sdcard/Boot and did this:
Code:
dd if=/dev/block/mmcblk0p16 of=/sdcard/Boot/recovery.img
Then on Windows, I unpacked recovery.img to kernel and /ramdisk and modified the /ramdisk/init.rc script as follows:
Code:
service recovery /sbin/recovery
service adbd /sbin/adbd recovery
[COLOR="Blue"]
# se[email protected] (09 Dec 2014)
# disabled
# [email protected] (09 Dec 2014)
[/COLOR]
socket adbd stream 660 system system
##++ Security R&D Group
service qrngd /system/bin/qrngd -f
class load_ode_env
user root
group root
oneshot
Then I repacked kernel and modified /ramdisk to recovery-repack.img, dropped it into /sdcard/Boot and flashed it to the recovery partition from 4.4.2 via ADB:
Code:
dd if=/sdcard/Boot/recovery-repack.img of=/dev/block/mmcblk0p16
When I rebooted, my phone returned an error message and rebooted again, this time to download mode. Oh well, I was really hoping to sneak this one past AT&T.
Somewhat nervous, I scoured the web for two days in search of a decent stock NCE build to recover my G900A. But all of the links were slow, flaky, costly and/or plagued with ads --- except for this one…
NCE Stock TAR with md5: http://www.rwilco12.com/forum/showthread.php?tid=883
Odin versions (esp. v1.85 --- considered the most stable):
http://www.rwilco12.com/forum/showthread.php?tid=101
So I downloaded the 1.5GB zip, decompressed to: “G900AUCU1ANCE_G900AATT1ANCE_G900AUCU1ANCE_HOME.tar.md5”
and ran Odin v1.85 with:
“\{Path-to}\G900AUCU1ANCE_G900AATT1ANCE_G900AUCU1ANCE_HOME.tar.md5”
in the PDA slot with Auto Reboot and F. Reset Time checked and no others checked except for PDA. Execution was flawless (ref. image below) and my G900A gracefully rebooted to stock KK 4.4.2--- with all of my installed apps, data and settings intact. And I quickly recovered root by re-launching the towelroot APK.
Of course I did lose busybox since it installs under /system/xbin. No problem, I just went to the BB app I had installed earlier and reinstalled BB from there.
Note: When I stripped off the .md5 suffix and opened the resulting .tar file with 7zip, an error message was returned but the file listing was still shown:
Note the absence of a data image --- a good thing if you have installed apps etc.
Something else I found helpful is the G900A partition map. Navigating to /dev/block/platform/msm_sdcc.1/by-name …
Code:
cd /dev/block/platform/msm_sdcc.1/by-name
[email protected]:/dev/block/platform/msm_sdcc.1/by-name # ls -ld *
ls -ld *
lrwxrwxrwx root root 2014-01-02 11:49 aboot -> /dev/block/mmcblk0p6
lrwxrwxrwx root root 2014-01-02 11:49 apnhlos -> /dev/block/mmcblk0p1
lrwxrwxrwx root root 2014-01-02 11:49 backup -> /dev/block/mmcblk0p18
lrwxrwxrwx root root 2014-01-02 11:49 boot -> /dev/block/mmcblk0p15
lrwxrwxrwx root root 2014-01-02 11:49 cache -> /dev/block/mmcblk0p24
lrwxrwxrwx root root 2014-01-02 11:49 dbi -> /dev/block/mmcblk0p4
lrwxrwxrwx root root 2014-01-02 11:49 ddr -> /dev/block/mmcblk0p5
lrwxrwxrwx root root 2014-01-02 11:49 efs -> /dev/block/mmcblk0p12
lrwxrwxrwx root root 2014-01-02 11:49 fota -> /dev/block/mmcblk0p17
lrwxrwxrwx root root 2014-01-02 11:49 fsc -> /dev/block/mmcblk0p19
lrwxrwxrwx root root 2014-01-02 11:49 fsg -> /dev/block/mmcblk0p9
lrwxrwxrwx root root 2014-01-02 11:49 modem -> /dev/block/mmcblk0p2
lrwxrwxrwx root root 2014-01-02 11:49 modemst1 -> /dev/block/mmcblk0p13
lrwxrwxrwx root root 2014-01-02 11:49 modemst2 -> /dev/block/mmcblk0p14
lrwxrwxrwx root root 2014-01-02 11:49 pad -> /dev/block/mmcblk0p10
lrwxrwxrwx root root 2014-01-02 11:49 param -> /dev/block/mmcblk0p11
lrwxrwxrwx root root 2014-01-02 11:49 persdata -> /dev/block/mmcblk0p22
lrwxrwxrwx root root 2014-01-02 11:49 persist -> /dev/block/mmcblk0p21
lrwxrwxrwx root root 2014-01-02 11:49 recovery -> /dev/block/mmcblk0p16
lrwxrwxrwx root root 2014-01-02 11:49 rpm -> /dev/block/mmcblk0p7
lrwxrwxrwx root root 2014-01-02 11:49 sbl1 -> /dev/block/mmcblk0p3
lrwxrwxrwx root root 2014-01-02 11:49 ssd -> /dev/block/mmcblk0p20
lrwxrwxrwx root root 2014-01-02 11:49 system -> /dev/block/mmcblk0p23
lrwxrwxrwx root root 2014-01-02 11:49 tz -> /dev/block/mmcblk0p8
lrwxrwxrwx root root 2014-01-02 11:49 userdata -> /dev/block/mmcblk0p25
[email protected]:/dev/block/platform/msm_sdcc.1/by-name #
Note especially the boot, recovery, system, data and cache partitions…
Code:
lrwxrwxrwx root root 2014-01-02 11:49 aboot -> /dev/block/mmcblk0p6
lrwxrwxrwx root root 2014-01-02 11:49 boot -> /dev/block/mmcblk0p15
lrwxrwxrwx root root 2014-01-02 11:49 cache -> /dev/block/mmcblk0p24
lrwxrwxrwx root root 2014-01-02 11:49 persdata -> /dev/block/mmcblk0p22
lrwxrwxrwx root root 2014-01-02 11:49 recovery -> /dev/block/mmcblk0p16
lrwxrwxrwx root root 2014-01-02 11:49 system -> /dev/block/mmcblk0p23
lrwxrwxrwx root root 2014-01-02 11:49 userdata -> /dev/block/mmcblk0p25
Many thanks to Rwilco12 for SGS5 support: http://www.rwilco12.com/
Also thanks to Krang for consolidating Rwilco12’s SGS5 links: http://www.rwilco12.com/forum/member.php?action=profile&uid=450
sendust7 said:
I know --- the bootloader is locked. But I still had to prove it to myself. And the info provided here may be useful to developers as well as to end-users.
Here is my story:
Running stock KK 4.4.2 (NCE) on my G900A, I successfully rooted using GeoHot’s towelroot https://towelroot.com/.
Then I froze the AT&T software updater app via Titanium Backup Pro --- since there is presently no way to re-root after updating.
Then I modified the stock recovery image to enable “adbd” (Android Debug Bridge daemon). Here’s a brief description of the process:
Running ADB with root and busybox installed, I created directory: /sdcard/Boot and did this:
Code:
dd if=/dev/block/mmcblk0p16 of=/sdcard/Boot/recovery.img
Then on Windows, I unpacked recovery.img to kernel and /ramdisk and modified the /ramdisk/init.rc script as follows:
Code:
service recovery /sbin/recovery
service adbd /sbin/adbd recovery
[COLOR="Blue"]
# [email protected] (09 Dec 2014)
# disabled
# [email protected] (09 Dec 2014)
[/COLOR]
socket adbd stream 660 system system
##++ Security R&D Group
service qrngd /system/bin/qrngd -f
class load_ode_env
user root
group root
oneshot
Then I repacked kernel and modified /ramdisk to recovery-repack.img, dropped it into /sdcard/Boot and flashed it to the recovery partition from 4.4.2 via ADB:
Code:
dd if=/sdcard/Boot/recovery-repack.img of=/dev/block/mmcblk0p16
When I rebooted, my phone returned an error message and rebooted again, this time to download mode. Oh well, I was really hoping to sneak this one past AT&T.
Somewhat nervous, I scoured the web for two days in search of a decent stock NCE build to recover my G900A. But all of the links were slow, flaky, costly and/or plagued with ads --- except for this one…
NCE Stock TAR with md5: http://www.rwilco12.com/forum/showthread.php?tid=883
Odin versions (esp. v1.85 --- considered the most stable):
http://www.rwilco12.com/forum/showthread.php?tid=101
So I downloaded the 1.5GB zip, decompressed to: “G900AUCU1ANCE_G900AATT1ANCE_G900AUCU1ANCE_HOME.tar.md5”
and ran Odin v1.85 with:
“\{Path-to}\G900AUCU1ANCE_G900AATT1ANCE_G900AUCU1ANCE_HOME.tar.md5”
in the PDA slot with Auto Reboot and F. Reset Time checked and no others checked except for PDA. Execution was flawless (ref. image below) and my G900A gracefully rebooted to stock KK 4.4.2--- with all of my installed apps, data and settings intact. And I quickly recovered root by re-launching the towelroot APK.
Of course I did lose busybox since it installs under /system/xbin. No problem, I just went to the BB app I had installed earlier and reinstalled BB from there.
Note: When I stripped off the .md5 suffix and opened the resulting .tar file with 7zip, an error message was returned but the file listing was still shown:
Note the absence of a data image --- a good thing if you have installed apps etc.
Something else I found helpful is the G900A partition map. Navigating to /dev/block/platform/msm_sdcc.1/by-name …
Code:
cd /dev/block/platform/msm_sdcc.1/by-name
[email protected]:/dev/block/platform/msm_sdcc.1/by-name # ls -ld *
ls -ld *
lrwxrwxrwx root root 2014-01-02 11:49 aboot -> /dev/block/mmcblk0p6
lrwxrwxrwx root root 2014-01-02 11:49 apnhlos -> /dev/block/mmcblk0p1
lrwxrwxrwx root root 2014-01-02 11:49 backup -> /dev/block/mmcblk0p18
lrwxrwxrwx root root 2014-01-02 11:49 boot -> /dev/block/mmcblk0p15
lrwxrwxrwx root root 2014-01-02 11:49 cache -> /dev/block/mmcblk0p24
lrwxrwxrwx root root 2014-01-02 11:49 dbi -> /dev/block/mmcblk0p4
lrwxrwxrwx root root 2014-01-02 11:49 ddr -> /dev/block/mmcblk0p5
lrwxrwxrwx root root 2014-01-02 11:49 efs -> /dev/block/mmcblk0p12
lrwxrwxrwx root root 2014-01-02 11:49 fota -> /dev/block/mmcblk0p17
lrwxrwxrwx root root 2014-01-02 11:49 fsc -> /dev/block/mmcblk0p19
lrwxrwxrwx root root 2014-01-02 11:49 fsg -> /dev/block/mmcblk0p9
lrwxrwxrwx root root 2014-01-02 11:49 modem -> /dev/block/mmcblk0p2
lrwxrwxrwx root root 2014-01-02 11:49 modemst1 -> /dev/block/mmcblk0p13
lrwxrwxrwx root root 2014-01-02 11:49 modemst2 -> /dev/block/mmcblk0p14
lrwxrwxrwx root root 2014-01-02 11:49 pad -> /dev/block/mmcblk0p10
lrwxrwxrwx root root 2014-01-02 11:49 param -> /dev/block/mmcblk0p11
lrwxrwxrwx root root 2014-01-02 11:49 persdata -> /dev/block/mmcblk0p22
lrwxrwxrwx root root 2014-01-02 11:49 persist -> /dev/block/mmcblk0p21
lrwxrwxrwx root root 2014-01-02 11:49 recovery -> /dev/block/mmcblk0p16
lrwxrwxrwx root root 2014-01-02 11:49 rpm -> /dev/block/mmcblk0p7
lrwxrwxrwx root root 2014-01-02 11:49 sbl1 -> /dev/block/mmcblk0p3
lrwxrwxrwx root root 2014-01-02 11:49 ssd -> /dev/block/mmcblk0p20
lrwxrwxrwx root root 2014-01-02 11:49 system -> /dev/block/mmcblk0p23
lrwxrwxrwx root root 2014-01-02 11:49 tz -> /dev/block/mmcblk0p8
lrwxrwxrwx root root 2014-01-02 11:49 userdata -> /dev/block/mmcblk0p25
[email protected]:/dev/block/platform/msm_sdcc.1/by-name #
Note especially the boot, recovery, system, data and cache partitions…
Code:
lrwxrwxrwx root root 2014-01-02 11:49 aboot -> /dev/block/mmcblk0p6
lrwxrwxrwx root root 2014-01-02 11:49 boot -> /dev/block/mmcblk0p15
lrwxrwxrwx root root 2014-01-02 11:49 cache -> /dev/block/mmcblk0p24
lrwxrwxrwx root root 2014-01-02 11:49 persdata -> /dev/block/mmcblk0p22
lrwxrwxrwx root root 2014-01-02 11:49 recovery -> /dev/block/mmcblk0p16
lrwxrwxrwx root root 2014-01-02 11:49 system -> /dev/block/mmcblk0p23
lrwxrwxrwx root root 2014-01-02 11:49 userdata -> /dev/block/mmcblk0p25
Many thanks to Rwilco12 for SGS5 support: http://www.rwilco12.com/
Also thanks to Krang for consolidating Rwilco12’s SGS5 links: http://www.rwilco12.com/forum/member.php?action=profile&uid=450
Click to expand...
Click to collapse
Actually a little searching on the forums and you'll find a very simple painless way to reroot after the update, also odin 3.09 or 3.10 is the current version. And if you also search for safestrap in the forums you'll find recovery. You have provided a lot of info here thanks for that but could have saved yourself a lot of grief and time by searching first
Sent from my SAMSUNG-SM-G900A using XDA Free mobile app
Question, did this return the phone to stock completely? Removing root and safestrap?
can not locate
cstayton said:
Actually a little searching on the forums and you'll find a very simple painless way to reroot after the update, also odin 3.09 or 3.10 is the current version. And if you also search for safestrap in the forums you'll find recovery. You have provided a lot of info here thanks for that but could have saved yourself a lot of grief and time by searching first
Sent from my SAMSUNG-SM-G900A using XDA Free mobile app
Click to expand...
Click to collapse
Safestrap is not available for the SM-G900A? i can not find any.
Related
I currently having a au (Japan) SCL22 which is a au kddi branded Galaxy Note 3. I'm wondering if anyone knows how to root it?
ken0ryu said:
I currently having a au (Japan) SCL22 which is a au kddi branded Galaxy Note 3. I'm wondering if anyone knows how to root it?
Click to expand...
Click to collapse
I suppose unless somebody gets the official firmware to people who know how to root devices here, we won't see one. =) Someone is on the Docomo version already. I am sure it will be rooted, just a bit later. Until then, I will keep wondering why I will have to void my warranty in order to have access to what Note 3 can already do - unrestricted multi-tasking with multi windows and s pen window...
Snakiest said:
I suppose unless somebody gets the official firmware to people who know how to root devices here, we won't see one. =) Someone is on the Docomo version already. I am sure it will be rooted, just a bit later. Until then, I will keep wondering why I will have to void my warranty in order to have access to what Note 3 can already do - unrestricted multi-tasking with multi windows and s pen window...
Click to expand...
Click to collapse
This phone can't root now.
doantri said:
This phone can't root now.
Click to expand...
Click to collapse
Well, that is what I said. I remember it took about 6 months for the AU version of the Galazy S2 to get rooted, so I expect something like this with Note 3.
This is ridiculousness! I had a desire HD on Softbank and could run any desire HD rom on it I wanted. Now I switch to au to find this is not the case huh? Why can't we use sprint or Verizon roms/recoveries?
You ever figure anything out? This is killing me. Custom rom seems like is never going to happen
ken0ryu said:
I currently having a au (Japan) SCL22 which is a au kddi branded Galaxy Note 3. I'm wondering if anyone knows how to root it?
Click to expand...
Click to collapse
rooted note scl22
dan.kels.r said:
You ever figure anything out? This is killing me. Custom rom seems like is never going to happen
Click to expand...
Click to collapse
thanks for replay but some one rooted done
how to root Galaxy note 3 SCL22
hi
i also want to know same thing, how to root Galaxy note 3 SCL22
anyone know pls help us
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.
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
You may have rooted, but you also blew your KNOX fuse and now your warranty is voided. KNOX WARRANTY VOID : 0x1 this line tells you that the KNOX has been tripped. This is impossible to reset so if you ever have to send your phone in for repairs now you will not be able to make a warranty claim. This is what haapens when you get impatient and try things that have not been proven like KINGOROOT.
need help
Solarenemy68 said:
You may have rooted, but you also blew your KNOX fuse and now your warranty is voided. KNOX WARRANTY VOID : 0x1 this line tells you that the KNOX has been tripped. This is impossible to reset so if you ever have to send your phone in for repairs now you will not be able to make a warranty claim. This is what haapens when you get impatient and try things that have not been proven like KINGOROOT.
Click to expand...
Click to collapse
i do not care about the knox.
mi problem is that i can not use a european sim for gsm , hence the need to unlock the phone. so if you can help with that script, please do.
i saw on youtube someone in vietnam, that unlocked a japanesse version of note 3, and offers his service for money, but only if you can go with the phone to him..., so... it can be done.
mvmaos said:
i do not care about the knox.
mi problem is that i can not use a european sim for gsm , hence the need to unlock the phone. so if you can help with that script, please do.
i saw on youtube someone in vietnam, that unlocked a japanesse version of note 3, and offers his service for money, but only if you can go with the phone to him..., so... it can be done.
Click to expand...
Click to collapse
can you provide me that vietnam video link pls. If you have any additional details about unlocking SCL22 pls share with us. I will do
the same. Because i want to unlock my Note 3 SCL22 immediately.
need help
niranjan.anu said:
can you provide me that vietnam video link pls. If you have any additional details about unlocking SCL22 pls share with us. I will do
the same. Because i want to unlock my Note 3 SCL22 immediately. [/QUOTE
watch?v=7E12QTQv3Io just check that id on youtube or search for "unlock scl22"
Click to expand...
Click to collapse
mvmaos said:
niranjan.anu said:
can you provide me that vietnam video link pls. If you have any additional details about unlocking SCL22 pls share with us. I will do
the same. Because i want to unlock my Note 3 SCL22 immediately. [/QUOTE
watch?v=7E12QTQv3Io just check that id on youtube or search for "unlock scl22"
Click to expand...
Click to collapse
I send a message to this person. He replied as
"I can unlock SCL22 but i cant to do it by network. sorry"
Click to expand...
Click to collapse
scl 22 unlock
niranjan.anu said:
mvmaos said:
I send a message to this person. He replied as
"I can unlock SCL22 but i cant to do it by network. sorry"
Click to expand...
Click to collapse
did you try to ask him, at least how it can be done,or, like , what tool or software he's using ?
Click to expand...
Click to collapse
Hm, that root should be fine in a year when the warranty ends unless some smart fellow comes up with a better way to do it. As for the SIM-unlock, I hear it is possible to ask either the carrier or the phone maker for the unlock key (or whatever it is). I believe some companies even do that officially for a fee. You guys should contact AU and then Samsung support for that, really, especially if you are Japanese - should be a lot easier than for some of us here. And then report here to let everybody know.
I have another AU phone, Xperia Acro. Long time ago, I also was looking for a way to unlock it, to use with European SiM. That was hard to find. After long search, I found a company which did it for about 50 bucks. But, at the end, I could only use my phone to do phone calls, but no SMS. Tried different ways - but SMS didn't work. Fund similar complaints about SMS on my AU model online, so its a real issue. And using phone without SMS in Europe sucks.
Got another phone for Europe, after all.
AU have something weird about their frequency so that might be that SCL22 will not be able to handle SMS either, even unlocked. Think if you really need to unock it
How To Root Samsung Galaxy Note 3
How To Root Samsung Galaxy Note 3 SCL22 au by KDDI (JAPAN phone) 100% working.
Quote:
My phone details (Tested devise)
Samsung Galaxy Note 3 SCL22 AU by KDDI (JAPAN phone) SM-N900J
Android Version - 4.4.2
Baseband Version - SCL22KDU2FNF7
Kernel Version - 3.4.0-1990145
This is all the stuff you need to Root your phone -
01. Kies3Setup.exe
02. ODIN 3.07 (Do Not Use 3.09)
03. UPDATE-SuperSU-v2.35.zip
04. hltedcm-KK-KBC-CWM-v6.0.5.0_r0-recovery.tar
05. CWMrecovery-scl22kk.tar
06. Stock firmware - (for that you need to register and download the stock kernel from sammobile. you better download it just in case )
DOWNLOAD LINKS -
01.hltedcm-KK-KBC-CWM-v6.0.5.0_r0-recovery.tar - https://mega.co.nz/#!1FI3xICS!7Un6z5...8GUZMkxkAwa7n4
02.02.CWMrecovery-scl22kk.tar - https://mega.co.nz/#!FZoEAbxC!j_l24G...3Vl63DHMSThuwE
03.twrp.tar - https://mega.co.nz/#!wd5Ama5b!33WccV...a6F0uHlBf_CVRE
04.SuperSU.rar - https://mega.co.nz/#!xY5CBJ4Y!NCN_DL...7l0b5P7UmaesyA
Quote:
(This file comes with a RAR format so extract it and inside that folder you can see UPDATE-SuperSU-v2.35.zip file )
05.Odin307.zip - https://mega.co.nz/#!Bd5x0CzC!UavXZ3...nWex3ECZ_mH8LI
01.Connect your phone to PC and copy and paste UPDATE-SuperSU-v2.35.zip to phone SD card
02.Start Odin 3.07
03.Put your phone to Download mode
04.Flash the hltedcm-KK-KBC-CWM-v6.0.5.0_r0-recovery.tar
05.Flash the CWMrecovery-scl22kk.tar
06.Start your phone then put it to Recovery mode and install UPDATE-SuperSU-v2.35.zip
07.Start your phone in normal mode. And now you all set and ROOT.
FINISH.!
Enjoy your rooted phone.!
ken0ryu said:
I currently having a au (Japan) SCL22 which is a au kddi branded Galaxy Note 3. I'm wondering if anyone knows how to root it?
Click to expand...
Click to collapse
Read this - http://forum.xda-developers.com/galaxy-note-3/general/samsung-galaxy-note-3-scl22-au-kddi-t2964801
Info for Developers
Device: SM-N910F
Code:
lrwxrwxrwx root root 2014-01-01 05:07 aboot -> /dev/block/mmcblk0p7
lrwxrwxrwx root root 2014-01-01 05:07 apnhlos -> /dev/block/mmcblk0p1
lrwxrwxrwx root root 2014-01-01 05:07 boot -> /dev/block/mmcblk0p17
lrwxrwxrwx root root 2014-01-01 05:07 cache -> /dev/block/mmcblk0p25
lrwxrwxrwx root root 2014-01-01 05:07 dbi -> /dev/block/mmcblk0p5
lrwxrwxrwx root root 2014-01-01 05:07 ddr -> /dev/block/mmcblk0p6
lrwxrwxrwx root root 2014-01-01 05:07 efs -> /dev/block/mmcblk0p13
lrwxrwxrwx root root 2014-01-01 05:07 fota -> /dev/block/mmcblk0p19
lrwxrwxrwx root root 2014-01-01 05:07 hidden -> /dev/block/mmcblk0p26
lrwxrwxrwx root root 2014-01-01 05:07 mdm1m9kefs1 -> /dev/block/mmcblk0p14
lrwxrwxrwx root root 2014-01-01 05:07 mdm1m9kefs2 -> /dev/block/mmcblk0p15
lrwxrwxrwx root root 2014-01-01 05:07 mdm1m9kefs3 -> /dev/block/mmcblk0p10
lrwxrwxrwx root root 2014-01-01 05:07 mdm1m9kefsc -> /dev/block/mmcblk0p16
lrwxrwxrwx root root 2014-01-01 05:07 misc -> /dev/block/mmcblk0p20
lrwxrwxrwx root root 2014-01-01 05:07 modem -> /dev/block/mmcblk0p2
lrwxrwxrwx root root 2014-01-01 05:07 pad -> /dev/block/mmcblk0p11
lrwxrwxrwx root root 2014-01-01 05:07 param -> /dev/block/mmcblk0p12
lrwxrwxrwx root root 2014-01-01 05:07 persdata -> /dev/block/mmcblk0p23
lrwxrwxrwx root root 2014-01-01 05:07 persist -> /dev/block/mmcblk0p22
lrwxrwxrwx root root 2014-01-01 05:07 recovery -> /dev/block/mmcblk0p18
lrwxrwxrwx root root 2014-01-01 05:07 rpm -> /dev/block/mmcblk0p8
lrwxrwxrwx root root 2014-01-01 05:07 sbl1 -> /dev/block/mmcblk0p3
lrwxrwxrwx root root 2014-01-01 05:07 sbl1bak -> /dev/block/mmcblk0p4
lrwxrwxrwx root root 2014-01-01 05:07 ssd -> /dev/block/mmcblk0p21
lrwxrwxrwx root root 2014-01-01 05:07 system -> /dev/block/mmcblk0p24
lrwxrwxrwx root root 2014-01-01 05:07 tz -> /dev/block/mmcblk0p9
lrwxrwxrwx root root 2014-01-01 05:07 userdata -> /dev/block/mmcblk0p27
These are the partitions for the UnitedStates Cricket Desire 510 if anybody needs them
[email protected]_a11ul8x26:/ $ ls -al /dev/block/bootdevice/by-name
ls -al /dev/block/bootdevice/by-name
lrwxrwxrwx root root 2014-12-31 16:00 adsp -> /dev/block/mmcblk
0p16
lrwxrwxrwx root root 2014-12-31 16:00 board_info -> /dev/block/
mmcblk0p3
lrwxrwxrwx root root 2014-12-31 16:00 boot -> /dev/block/mmcblk
0p40
lrwxrwxrwx root root 2014-12-31 16:00 cache -> /dev/block/mmcbl
k0p42
lrwxrwxrwx root root 2014-12-31 16:00 carrier -> /dev/block/mmc
blk0p37
lrwxrwxrwx root root 2014-12-31 16:00 cdma_record -> /dev/block
/mmcblk0p33
lrwxrwxrwx root root 2014-12-31 16:00 control -> /dev/block/mmc
blk0p30
lrwxrwxrwx root root 2014-12-31 16:00 custdata -> /dev/block/mm
cblk0p22
lrwxrwxrwx root root 2014-12-31 16:00 ddr -> /dev/block/mmcblk0
p14
lrwxrwxrwx root root 2014-12-31 16:00 debug_config -> /dev/bloc
k/mmcblk0p28
lrwxrwxrwx root root 2014-12-31 16:00 devlog -> /dev/block/mmcb
lk0p38
lrwxrwxrwx root root 2014-12-31 16:00 dsps -> /dev/block/mmcblk
0p15
lrwxrwxrwx root root 2014-12-31 16:00 extra -> /dev/block/mmcbl
k0p32
lrwxrwxrwx root root 2014-12-31 16:00 fataldevlog -> /dev/block
/mmcblk0p27
lrwxrwxrwx root root 2014-12-31 16:00 fsc -> /dev/block/mmcblk0
p34
lrwxrwxrwx root root 2014-12-31 16:00 fsg -> /dev/block/mmcblk0
p19
lrwxrwxrwx root root 2014-12-31 16:00 hboot -> /dev/block/mmcbl
k0p11
lrwxrwxrwx root root 2014-12-31 16:00 local -> /dev/block/mmcbl
k0p31
lrwxrwxrwx root root 2014-12-31 16:00 mfg -> /dev/block/mmcblk0
p5
lrwxrwxrwx root root 2014-12-31 16:00 misc -> /dev/block/mmcblk
0p24
lrwxrwxrwx root root 2014-12-31 16:00 modem_st1 -> /dev/block/m
mcblk0p25
lrwxrwxrwx root root 2014-12-31 16:00 modem_st2 -> /dev/block/m
mcblk0p26
lrwxrwxrwx root root 2014-12-31 16:00 pdata -> /dev/block/mmcbl
k0p29
lrwxrwxrwx root root 2014-12-31 16:00 pg1fs -> /dev/block/mmcbl
k0p2
lrwxrwxrwx root root 2014-12-31 16:00 pg2fs -> /dev/block/mmcbl
k0p6
lrwxrwxrwx root root 2014-12-31 16:00 radio -> /dev/block/mmcbl
k0p20
lrwxrwxrwx root root 2014-12-31 16:00 radio_config -> /dev/bloc
k/mmcblk0p18
lrwxrwxrwx root root 2014-12-31 16:00 recovery -> /dev/block/mm
cblk0p41
lrwxrwxrwx root root 2014-12-31 16:00 reserve -> /dev/block/mmc
blk0p39
lrwxrwxrwx root root 2014-12-31 16:00 reserve_1 -> /dev/block/m
mcblk0p4
lrwxrwxrwx root root 2014-12-31 16:00 reserve_2 -> /dev/block/m
mcblk0p23
lrwxrwxrwx root root 2014-12-31 16:00 rpm -> /dev/block/mmcblk0
p8
lrwxrwxrwx root root 2014-12-31 16:00 sbl1 -> /dev/block/mmcblk
0p1
lrwxrwxrwx root root 2014-12-31 16:00 sbl1_update -> /dev/block
/mmcblk0p7
lrwxrwxrwx root root 2014-12-31 16:00 sdi -> /dev/block/mmcblk0
p10
lrwxrwxrwx root root 2014-12-31 16:00 skylink -> /dev/block/mmc
blk0p36
lrwxrwxrwx root root 2014-12-31 16:00 sp1 -> /dev/block/mmcblk0
p12
lrwxrwxrwx root root 2014-12-31 16:00 ssd -> /dev/block/mmcblk0
p35
lrwxrwxrwx root root 2014-12-31 16:00 system -> /dev/block/mmcb
lk0p43
lrwxrwxrwx root root 2014-12-31 16:00 tool_diag -> /dev/block/m
mcblk0p21
lrwxrwxrwx root root 2014-12-31 16:00 tz -> /dev/block/mmcblk0p
9
lrwxrwxrwx root root 2014-12-31 16:00 userdata -> /dev/block/mm
cblk0p44
lrwxrwxrwx root root 2014-12-31 16:00 wcnss -> /dev/block/mmcbl
k0p17
lrwxrwxrwx root root 2014-12-31 16:00 wifi -> /dev/block/mmcblk
0p13
[email protected]_a11ul8x26:/ $
Pretty sure the few 510 devs that we do have are already aware of this.
HampTheToker said:
Pretty sure the few 510 devs that we do have are already aware of this.
Click to expand...
Click to collapse
Yep, we sure are lol.. Regular users really wouldn't have a need for this type of information.
Yes i understand but there are people who build roms that donnot know how to do this i am a dev myself and didnt know how to do this when i first started building roms
Released on asus website 14/12/2015:
Marshmallow:
http://dlcdnet.asus.com/pub/ASUS/ZenFone/ZE551KL/UnlockTool_ASUS_AndroidM20160928_Singed.zip
Lollipop:
http://dlcdnet.asus.com/pub/ASUS/ZenFone/ZE600KL/ZE600KL_UnlockApp.zip
The APKs for each are binary identical, so it is not really important which unlock utility you download.
Frequently asked questions:
Q: will this work on ZE500KG / ZE500KL / ASUS_Z00RD / ASUS_Z00RD_5 / ASUS_Z00RD_7 / ASUS_Z00ED / ASUS_Z00EDB / ASUS_Z00E_1 / ASUS_Z00E_2 / ASUS_Z00E_3
A: we do not think so, but we do not know if anyone has tried it.
Q: can I relock bootloader?
A: we do not have a way of re-locking bootloader right now. Hopefully it will be possible using a backup of some partition to restore original bootloader, but we have not found it yet.
Q: can I restore my warranty by re-locking the bootloader?
A: we believe that ASUS records the serial number of the device through the unlock utility, so it will not be possible to make a warranty claim even if you do manage to re-lock the bootloader.
Q: can I still receive OTA updates?
A: we do not know, because no updates have been released since the unlock utility was released.
Q: can I still update firmware manually?
A: yes, definitely. fetch the new firmware zip from ASUS website and flash in stock recovery or transfer to root of sd-card and boot the phone normally (it will find the update zip file and prompt you).
Download notes from the site:
Unlock Device App: Unlock boot loader
Notice:
1. Update your software image to V1.15.40.771 or latest version
2. Before you download, install, and use the Unlock Device App you acknowledge and assume complete risk to the quality and performance of this App, including but not limited to the following: once you activate the App you will not be able to recover your ASUS product (“Original Product”) back to original locked conditions; the Original Product with the activated App will not be deemed the Original Product; the Revised Product will no longer be covered under the warranty of the Original Product; the software of Revised Product will no longer be deemed the software of the Original Product and can no longer receive ASUS software updates; your purchased digital content may also be affected.
You also acknowledge ASUS does not guarantee service satisfaction to any Revised Product, including events involving paid service requested by you to be performed to the Revised Product.
Furthermore, such repaired Revised Product will not be covered under the warranty of the Original Product; the software of the repaired Revised Product will not be deemed the software of the Original Product and will not receive ASUS software updates.
It is strongly advised that you avoid activating this App unless you fully understand and accept the risks that may arise.
Click to expand...
Click to collapse
Do you think this would work on the US 551KL? If so thatd be great
* edit *
firmware v1.15.40.771 now released for ZE600KL, so I will try to flash now on ZE550KL and then unlock
http://dlcdnet.asus.com/pub/ASUS/ZenFone/ZE600KL/UL-Z00L-WW-1.15.40.771-user.zip
Please note, I have ZE550KL-1A025TW version, Snapdragon 615, 2GB RAM (ASUS_Z00LD / ASUS_Z00L_93)
I updated my ZE550KL to firmware v1.15.40.771:
http://dlcdnet.asus.com/pub/ASUS/ZenFone/ZE600KL/UL-Z00L-WW-1.15.40.771-user.zip
then ran the ZE600KL unlock utility.
Unlock utility runs without errors, phone reboots, no errors, everything still working fine.
Confirmed unlock successful
Code:
C:\adb>fastboot oem device-info
...
(bootloader) Device unlocked: true
(bootloader) Charger screen enabled: false
(bootloader) Display panel:
OKAY [ 0.010s]
finished. total time: 0.010s
Let me get this straight, you flashed ZE600KL firmware on your ZE550KL and it worked? Not something I would recommend.
Yeh i did, in the source code they seem to be built with identical makefiles so i just figured i would experiment
Sent from my GT-I9195 using Tapatalk
You can test your bootloader status, if you type in fastboot mode "fastboot oem device-info"
Can someone please paste the output on a rooted ZE550KL in adb shell:
Code:
ls -al /dev/block/platform/dw_mmc/by-name
I already compiled a cm recovery, but i am not sure about the block names...
destilant said:
Can someone please paste the output on a rooted ZE550KL in adb shell:
I already compiled a cm recovery, but i am not sure about the block names...
Click to expand...
Click to collapse
Would the recovery also work for a 551KL? I can get you that, if i can help. And also test the recovery
wickedpygmy said:
Yeh i did, in the source code they seem to be built with identical makefiles so i just figured i would experiment
Sent from my GT-I9195 using Tapatalk
Click to expand...
Click to collapse
fair enough. How do it look? The 600KL is a 6" phone and the 5500KL a 5.5". Does it appear to overlap or anything?
capeorigins said:
Would the recovery also work for a 551KL? I can get you that, if i can help. And also test the recovery
Click to expand...
Click to collapse
Nope, the ZE551KL is shipped with a Snapdragon 615 MSM8939, the ZE550KL with a 610 MSM8916, so it wont work...
destilant said:
You can test your bootloader status, if you type in fastboot mode "fastboot oem device-info"
Click to expand...
Click to collapse
Code:
C:\adb>adb devices
List of devices attached
F8AZCY01P722 device
C:\adb>adb reboot bootloader
C:\adb>fastboot oem device-info
...
(bootloader) Device unlocked: true
(bootloader) Charger screen enabled: false
(bootloader) Display panel:
OKAY [ 0.010s]
finished. total time: 0.010s
C:\adb>
destilant said:
Can someone please paste the output on a rooted ZE550KL in adb shell:
Code:
ls -al /dev/block/platform/dw_mmc/by-name
I already compiled a cm recovery, but i am not sure about the block names...
Click to expand...
Click to collapse
Moreover, can somebody please upload raw backups of the 'aboot' (& 'abootbak' if present) partition before & after unlocking the bootloader? You need root access & can use something like this one.
destilant said:
You can test your bootloader status, if you type in fastboot mode "fastboot oem device-info"
Click to expand...
Click to collapse
heywheelie said:
fair enough. How do it look? The 600KL is a 6" phone and the 5500KL a 5.5". Does it appear to overlap or anything?
Click to expand...
Click to collapse
looks normal, both have same resolution. I think both phones use the same firmware since the kernel is identical and Asus don't release Z00m firmware but use Z00L for both models.
Titokhan said:
Moreover, can somebody please upload raw backups of the 'aboot' (& 'abootbak' if present) partition before & after unlocking the bootloader? You need root access & can use something like this one.
Click to expand...
Click to collapse
@Titokhan must be too late for me to do this, since I already unlocked and have no way to get back?
attached is aboot and abootbak after unlocking, maybe @heywheelie can upload the before?
destilant said:
Nope, the ZE551KL is shipped with a Snapdragon 615 MSM8939, the ZE550KL with a 610 MSM8916, so it wont work...
Click to expand...
Click to collapse
the ZE550KL has a snapdragon 615 not 610
destilant said:
Can someone please paste the output on a rooted ZE550KL in adb shell:
Code:
ls -al /dev/block/platform/dw_mmc/by-name
I already compiled a cm recovery, but i am not sure about the block names...
Click to expand...
Click to collapse
doesnt look like folder exists.
Code:
[email protected]_Z00L_93:/ # ls -al /dev/block/platform/
drwxr-xr-x root root 1970-05-15 01:49 7824900.sdhci
[email protected]_Z00L_93:/ #
heywheelie said:
the ZE550KL has a snapdragon 615 not 610
Click to expand...
Click to collapse
init! i wish people would stop polluting the version/hardware topic, especially since its so confusing already
wickedpygmy said:
looks normal, both have same resolution. I think both phones use the same firmware since the kernel is identical and Asus don't release Z00m firmware but use Z00L for both models.
Click to expand...
Click to collapse
might be same firmware but specs do differ slightly
https://www.asus.com/Phone/ZenFone-2-Laser-ZE550KL/specifications/
https://www.asus.com/Phone/ZenFone-2-Laser-ZE600KL/specifications/
WLAN bands differ, bluetooth is 4.0 on 550 and 4.1 on 6.0. Nothing dramatic but different
destilant said:
Can someone please paste the output on a rooted ZE550KL in adb shell:
Code:
ls -al /dev/block/platform/dw_mmc/by-name
I already compiled a cm recovery, but i am not sure about the block names...
Click to expand...
Click to collapse
This any use?
Code:
[email protected]_Z00L_93:/ # ls -al /dev/block/platform/7824900.sdhci/by-name
lrwxrwxrwx root root 1970-05-15 01:49 ADF -> /dev/block/mmcblk0p42
lrwxrwxrwx root root 1970-05-15 01:49 APD -> /dev/block/mmcblk0p43
lrwxrwxrwx root root 1970-05-15 01:49 DDR -> /dev/block/mmcblk0p9
lrwxrwxrwx root root 1970-05-15 01:49 aboot -> /dev/block/mmcblk0p12
lrwxrwxrwx root root 1970-05-15 01:49 abootbak -> /dev/block/mmcblk0p13
lrwxrwxrwx root root 1970-05-15 01:49 abootdebug -> /dev/block/mmcblk0p34
lrwxrwxrwx root root 1970-05-15 01:49 asdf -> /dev/block/mmcblk0p33
lrwxrwxrwx root root 1970-05-15 01:49 asusfw -> /dev/block/mmcblk0p40
lrwxrwxrwx root root 1970-05-15 01:49 asusgpt -> /dev/block/mmcblk0p27
lrwxrwxrwx root root 1970-05-15 01:49 asusgpt1 -> /dev/block/mmcblk0p28
lrwxrwxrwx root root 1970-05-15 01:49 asusgpt2 -> /dev/block/mmcblk0p29
lrwxrwxrwx root root 1970-05-15 01:49 asuskey -> /dev/block/mmcblk0p22
lrwxrwxrwx root root 1970-05-15 01:49 asuskey2 -> /dev/block/mmcblk0p23
lrwxrwxrwx root root 1970-05-15 01:49 asuskey3 -> /dev/block/mmcblk0p24
lrwxrwxrwx root root 1970-05-15 01:49 asuskey4 -> /dev/block/mmcblk0p25
lrwxrwxrwx root root 1970-05-15 01:49 asuskey5 -> /dev/block/mmcblk0p26
lrwxrwxrwx root root 1970-05-15 01:49 boot -> /dev/block/mmcblk0p37
lrwxrwxrwx root root 1970-05-15 01:49 cache -> /dev/block/mmcblk0p44
lrwxrwxrwx root root 1970-05-15 01:49 config -> /dev/block/mmcblk0p32
lrwxrwxrwx root root 1970-05-15 01:49 devinfo -> /dev/block/mmcblk0p15
lrwxrwxrwx root root 1970-05-15 01:49 factory -> /dev/block/mmcblk0p20
lrwxrwxrwx root root 1970-05-15 01:49 factorybak -> /dev/block/mmcblk0p21
lrwxrwxrwx root root 1970-05-15 01:49 fsc -> /dev/block/mmcblk0p17
lrwxrwxrwx root root 1970-05-15 01:49 fsg -> /dev/block/mmcblk0p16
lrwxrwxrwx root root 1970-05-15 01:49 hyp -> /dev/block/mmcblk0p7
lrwxrwxrwx root root 1970-05-15 01:49 hypbak -> /dev/block/mmcblk0p8
lrwxrwxrwx root root 1970-05-15 01:49 keystore -> /dev/block/mmcblk0p31
lrwxrwxrwx root root 1970-05-15 01:49 misc -> /dev/block/mmcblk0p30
lrwxrwxrwx root root 1970-05-15 01:49 modem -> /dev/block/mmcblk0p41
lrwxrwxrwx root root 1970-05-15 01:49 modemst1 -> /dev/block/mmcblk0p18
lrwxrwxrwx root root 1970-05-15 01:49 modemst2 -> /dev/block/mmcblk0p19
lrwxrwxrwx root root 1970-05-15 01:49 oem -> /dev/block/mmcblk0p36
lrwxrwxrwx root root 1970-05-15 01:49 persist -> /dev/block/mmcblk0p39
lrwxrwxrwx root root 1970-05-15 01:49 persistent -> /dev/block/mmcblk0p35
lrwxrwxrwx root root 1970-05-15 01:49 recovery -> /dev/block/mmcblk0p38
lrwxrwxrwx root root 1970-05-15 01:49 rpm -> /dev/block/mmcblk0p3
lrwxrwxrwx root root 1970-05-15 01:49 rpmbak -> /dev/block/mmcblk0p4
lrwxrwxrwx root root 1970-05-15 01:49 sbl1 -> /dev/block/mmcblk0p1
lrwxrwxrwx root root 1970-05-15 01:49 sbl1bak -> /dev/block/mmcblk0p2
lrwxrwxrwx root root 1970-05-15 01:49 sec -> /dev/block/mmcblk0p11
lrwxrwxrwx root root 1970-05-15 01:49 splash -> /dev/block/mmcblk0p14
lrwxrwxrwx root root 1970-05-15 01:49 ssd -> /dev/block/mmcblk0p10
lrwxrwxrwx root root 1970-05-15 01:49 system -> /dev/block/mmcblk0p45
lrwxrwxrwx root root 1970-05-15 01:49 tz -> /dev/block/mmcblk0p5
lrwxrwxrwx root root 1970-05-15 01:49 tzbak -> /dev/block/mmcblk0p6
lrwxrwxrwx root root 1970-05-15 01:49 userdata -> /dev/block/mmcblk0p46
[email protected]_Z00L_93:/ #
Hi
can any one verify if the list of my partition is correct and the name matches with the mmcblk0pxx, my vie-l29 was unbricked and recived an erase_emmc
it boot but instable and wifi and sound not working
lrwxrwxrwx root root 1970-01-02 06:44 3rdmodem -> /dev/block/mmcblk0p35
lrwxrwxrwx root root 1970-01-02 06:44 3rdmodemnvm -> /dev/block/mmcblk0p14
lrwxrwxrwx root root 1970-01-02 06:44 3rdmodemnvmbkp -> /dev/block/mmcblk0p15
lrwxrwxrwx root root 1970-01-02 06:44 boot -> /dev/block/mmcblk0p28
lrwxrwxrwx root root 1970-01-02 06:44 cache -> /dev/block/mmcblk0p36
lrwxrwxrwx root root 1970-01-02 06:44 cust -> /dev/block/mmcblk0p40
lrwxrwxrwx root root 1970-01-02 06:44 dfx -> /dev/block/mmcblk0p34
lrwxrwxrwx root root 1970-01-02 06:44 dts -> /dev/block/mmcblk0p30
lrwxrwxrwx root root 1970-01-02 06:44 fastboot -> /dev/block/mmcblk0p5
lrwxrwxrwx root root 1970-01-02 06:44 frp -> /dev/block/mmcblk0p4
lrwxrwxrwx root root 1970-01-02 06:44 fw_hifi -> /dev/block/mmcblk0p27
lrwxrwxrwx root root 1970-01-02 06:44 fw_lpm3 -> /dev/block/mmcblk0p3
lrw-rw---- system system 1970-01-02 06:44 hisitest0 -> /dev/block/mmcblk0p37
lrw-rw---- system system 1970-01-02 06:44 hisitest1 -> /dev/block/mmcblk0p38
lrw-rw---- system system 1970-01-02 06:44 hisitest2 -> /dev/block/mmcblk0p41
lrwxrwxrwx root root 1970-01-02 06:44 misc -> /dev/block/mmcblk0p20
lrwxrwxrwx root root 1970-01-02 06:44 modem -> /dev/block/mmcblk0p31
lrwxrwxrwx root root 1970-01-02 06:44 modem_dsp -> /dev/block/mmcblk0p32
lrwxrwxrwx root root 1970-01-02 06:44 modem_dtb -> /dev/block/mmcblk0p33
lrwxrwxrwx root root 1970-01-02 06:44 modem_om -> /dev/block/mmcblk0p18
lrwxrwxrwx root root 1970-01-02 06:44 modemnvm_backup -> /dev/block/mmcblk0p10
lrwxrwxrwx root root 1970-01-02 06:44 modemnvm_factory -> /dev/block/mmcblk0p6
lrwxrwxrwx root root 1970-01-02 06:44 modemnvm_img -> /dev/block/mmcblk0p11
lrwxrwxrwx root root 1970-01-02 06:44 modemnvm_system -> /dev/block/mmcblk0p12
lrwxrwxrwx root root 1970-01-02 06:44 modemnvm_update -> /dev/block/mmcblk0p21
lrwxrwxrwx root root 1970-01-02 06:44 nvme -> /dev/block/mmcblk0p7
lrwxrwxrwx root root 1970-01-02 06:44 oeminfo -> /dev/block/mmcblk0p8
lrwxrwxrwx root root 1970-01-02 06:44 persist -> /dev/block/mmcblk0p16
lrwxrwxrwx root root 1970-01-02 06:44 recovery -> /dev/block/mmcblk0p29
lrwxrwxrwx root root 1970-01-02 06:44 recovery2 -> /dev/block/mmcblk0p22
lrw-rw---- system system 1970-01-02 06:44 reserved1 -> /dev/block/mmcblk0p17
lrwxrwxrwx root root 1970-01-02 06:44 reserved2 -> /dev/block/mmcblk0p23
lrwxrwxrwx root root 1970-01-02 06:44 secure_storage -> /dev/block/mmcblk0p13
lrwxrwxrwx root root 1970-01-02 06:44 sensorhub -> /dev/block/mmcblk0p26
lrwxrwxrwx root root 1970-01-02 06:44 splash -> /dev/block/mmcblk0p9
lrwxrwxrwx root root 1970-01-02 06:44 splash2 -> /dev/block/mmcblk0p19
lrwxrwxrwx root root 1970-01-02 06:44 system -> /dev/block/mmcblk0p39
lrwxrwxrwx root root 1970-01-02 06:44 teeos -> /dev/block/mmcblk0p24
lrwxrwxrwx root root 1970-01-02 06:44 trustfirmware -> /dev/block/mmcblk0p25
lrwxrwxrwx root root 1970-01-02 06:44 userdata -> /dev/block/mmcblk0p42
lrwxrwxrwx root root 1970-01-02 06:44 vrl -> /dev/block/mmcblk0p1
lrwxrwxrwx root root 1970-01-02 06:44 vrl_backup -> /dev/block/mmcblk0p2
thank you
any one pls , just share your partition list of your working p9 plus