Database Develop

[Q] au SCL22

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

[FIX] Restoring G900A after attempting to flash modified recovery [10 Dec 2014]

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.

need vie-l29 Partition list

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

Bricked P10 lite (tried to flash C432 on C109)

Hello,
I tried to flash C432 ROM on my current C109 ROM, but the Update.app process always fails at 5%...
I extracted update.app,
I tried to flash with fastboot but I probably made something wrong when I tried to wipe data/factory reset with factory recovery...
I can only flash boot / recovery / cust / system
My issue is now the ROM tries to boot, then bootloop to eRecovery...
I can't find a way to revive it...
I tried to flash C109B110 and C432B120 but it does not change my bootloop issue
The original ROM is WAS-LX1AB109C100, I can't find it anywhere ...
Can someone help me ?
Thank you
Edit : My bootloader is unlocked btw

Hey, look here
http://hwmt.ru/hwmtsite/firmware-database/?firmware_model=WAS-LX1&firmware_page=0
Try to flash a newer version

aburezk said:
Hey, look here
http://hwmt.ru/hwmtsite/firmware-database/?firmware_model=WAS-LX1&firmware_page=0
Try to flash a newer version
Click to expand...
Click to collapse
Already tried, didn't find a solution...
The Update mode always fails at 5%... I can flash with fastboot, but still no luck currently...

Orphee said:
Already tried, didn't find a solution...
The Update mode always fails at 5%... I can flash with fastboot, but still no luck currently...
Click to expand...
Click to collapse
Are you using the original recovery?or TWRP?

Tried both, i think my biggest mistake was to format /data with TWRP...

Orphee said:
Tried both, i think my biggest mistake was to format /data with TWRP...
Click to expand...
Click to collapse
I remember I did something similar when I had lg g2 the solution was to run some commands in adb and it worked bypassed the loop
---------- Post added at 03:12 PM ---------- Previous post was at 03:10 PM ----------
These are the commands
adb shell
dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/fota
dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/misc

aburezk said:
I remember I did something similar when I had lg g2 the solution was to run some commands in adb and it worked bypassed the loop
---------- Post added at 03:12 PM ---------- Previous post was at 03:10 PM ----------
These are the commands
adb shell
dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/fota
dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/misc
Click to expand...
Click to collapse
You do this while in TWRP ? Cause I don't think I have access to ADB when booting.

Orphee said:
You do this while in TWRP ? Cause I don't think I have access to ADB when booting.
Click to expand...
Click to collapse
Yes from twrp

aburezk said:
Yes from twrp
Click to expand...
Click to collapse
in /dev/block/platform/hi_mci.0/by-name/
Code:
lrwxrwxrwx 1 root root 20 May 31 14:24 vrl_backup -> /dev/block/mmcblk0p2
lrwxrwxrwx 1 root root 20 May 31 14:24 vrl -> /dev/block/mmcblk0p1
lrwxrwxrwx 1 root root 21 May 31 14:24 version -> /dev/block/mmcblk0p46
lrwxrwxrwx 1 root root 21 May 31 14:24 vendor -> /dev/block/mmcblk0p47
lrwxrwxrwx 1 root root 21 May 31 14:24 userdata -> /dev/block/mmcblk0p49
lrwxrwxrwx 1 root root 21 May 31 14:24 trustfirmware -> /dev/block/mmcblk0p25
lrwxrwxrwx 1 root root 21 May 31 14:24 teeos -> /dev/block/mmcblk0p24
lrwxrwxrwx 1 root root 21 May 31 14:24 system -> /dev/block/mmcblk0p44
lrwxrwxrwx 1 root root 21 May 31 14:24 splash2 -> /dev/block/mmcblk0p19
lrwxrwxrwx 1 root root 21 May 31 14:24 sensorhub -> /dev/block/mmcblk0p26
lrwxrwxrwx 1 root root 21 May 31 14:24 secure_storage -> /dev/block/mmcblk0p13
lrwxrwxrwx 1 root root 21 May 31 14:24 rrecord -> /dev/block/mmcblk0p42
lrwxrwxrwx 1 root root 21 May 31 14:24 reserved9 -> /dev/block/mmcblk0p43
lrwxrwxrwx 1 root root 21 May 31 14:24 reserved8 -> /dev/block/mmcblk0p33
lrwxrwxrwx 1 root root 21 May 31 14:24 reserved7 -> /dev/block/mmcblk0p32
lrwxrwxrwx 1 root root 21 May 31 14:24 reserved6 -> /dev/block/mmcblk0p35
lrwxrwxrwx 1 root root 21 May 31 14:24 reserved5 -> /dev/block/mmcblk0p15
lrwxrwxrwx 1 root root 21 May 31 14:24 reserved4 -> /dev/block/mmcblk0p14
lrwxrwxrwx 1 root root 20 May 31 14:24 reserved3 -> /dev/block/mmcblk0p9
lrwxrwxrwx 1 root root 21 May 31 14:24 reserved2 -> /dev/block/mmcblk0p23
lrwxrwxrwx 1 root root 21 May 31 14:24 reserved1 -> /dev/block/mmcblk0p17
lrwxrwxrwx 1 root root 21 May 31 14:24 recovery2 -> /dev/block/mmcblk0p22
lrwxrwxrwx 1 root root 21 May 31 14:24 recovery -> /dev/block/mmcblk0p29
lrwxrwxrwx 1 root root 21 May 31 14:24 product -> /dev/block/mmcblk0p48
lrwxrwxrwx 1 root root 21 May 31 14:24 persist -> /dev/block/mmcblk0p16
lrwxrwxrwx 1 root root 21 May 31 14:24 patch -> /dev/block/mmcblk0p40
lrwxrwxrwx 1 root root 20 May 31 14:24 oeminfo -> /dev/block/mmcblk0p8
lrwxrwxrwx 1 root root 20 May 31 14:24 nvme -> /dev/block/mmcblk0p7
lrwxrwxrwx 1 root root 21 May 31 14:24 modemnvm_update -> /dev/block/mmcblk0p21
lrwxrwxrwx 1 root root 21 May 31 14:24 modemnvm_system -> /dev/block/mmcblk0p12
lrwxrwxrwx 1 root root 21 May 31 14:24 modemnvm_img -> /dev/block/mmcblk0p11
lrwxrwxrwx 1 root root 20 May 31 14:24 modemnvm_factory -> /dev/block/mmcblk0p6
lrwxrwxrwx 1 root root 21 May 31 14:24 modemnvm_backup -> /dev/block/mmcblk0p10
lrwxrwxrwx 1 root root 21 May 31 14:24 modem_om -> /dev/block/mmcblk0p18
lrwxrwxrwx 1 root root 21 May 31 14:24 modem_fw -> /dev/block/mmcblk0p31
lrwxrwxrwx 1 root root 21 May 31 14:24 misc -> /dev/block/mmcblk0p20
lrwxrwxrwx 1 root root 21 May 31 14:24 hisitest2 -> /dev/block/mmcblk0p39
lrwxrwxrwx 1 root root 21 May 31 14:24 hisitest1 -> /dev/block/mmcblk0p38
lrwxrwxrwx 1 root root 21 May 31 14:24 hisitest0 -> /dev/block/mmcblk0p37
lrwxrwxrwx 1 root root 20 May 31 14:24 fw_lpm3 -> /dev/block/mmcblk0p3
lrwxrwxrwx 1 root root 21 May 31 14:24 fw_hifi -> /dev/block/mmcblk0p27
lrwxrwxrwx 1 root root 20 May 31 14:24 frp -> /dev/block/mmcblk0p4
lrwxrwxrwx 1 root root 20 May 31 14:24 fastboot -> /dev/block/mmcblk0p5
lrwxrwxrwx 1 root root 21 May 31 14:24 dts -> /dev/block/mmcblk0p30
lrwxrwxrwx 1 root root 21 May 31 14:24 dfx -> /dev/block/mmcblk0p34
lrwxrwxrwx 1 root root 21 May 31 14:24 cust -> /dev/block/mmcblk0p45
lrwxrwxrwx 1 root root 21 May 31 14:24 cache -> /dev/block/mmcblk0p36
lrwxrwxrwx 1 root root 21 May 31 14:24 bootfail_info -> /dev/block/mmcblk0p41
lrwxrwxrwx 1 root root 21 May 31 14:24 boot -> /dev/block/mmcblk0p28
I don't have fota.

Orphee said:
in /dev/block/platform/hi_mci.0/by-name/
Code:
lrwxrwxrwx 1 root root 20 May 31 14:24 vrl_backup -> /dev/block/mmcblk0p2
lrwxrwxrwx 1 root root 20 May 31 14:24 vrl -> /dev/block/mmcblk0p1
lrwxrwxrwx 1 root root 21 May 31 14:24 version -> /dev/block/mmcblk0p46
lrwxrwxrwx 1 root root 21 May 31 14:24 vendor -> /dev/block/mmcblk0p47
lrwxrwxrwx 1 root root 21 May 31 14:24 userdata -> /dev/block/mmcblk0p49
lrwxrwxrwx 1 root root 21 May 31 14:24 trustfirmware -> /dev/block/mmcblk0p25
lrwxrwxrwx 1 root root 21 May 31 14:24 teeos -> /dev/block/mmcblk0p24
lrwxrwxrwx 1 root root 21 May 31 14:24 system -> /dev/block/mmcblk0p44
lrwxrwxrwx 1 root root 21 May 31 14:24 splash2 -> /dev/block/mmcblk0p19
lrwxrwxrwx 1 root root 21 May 31 14:24 sensorhub -> /dev/block/mmcblk0p26
lrwxrwxrwx 1 root root 21 May 31 14:24 secure_storage -> /dev/block/mmcblk0p13
lrwxrwxrwx 1 root root 21 May 31 14:24 rrecord -> /dev/block/mmcblk0p42
lrwxrwxrwx 1 root root 21 May 31 14:24 reserved9 -> /dev/block/mmcblk0p43
lrwxrwxrwx 1 root root 21 May 31 14:24 reserved8 -> /dev/block/mmcblk0p33
lrwxrwxrwx 1 root root 21 May 31 14:24 reserved7 -> /dev/block/mmcblk0p32
lrwxrwxrwx 1 root root 21 May 31 14:24 reserved6 -> /dev/block/mmcblk0p35
lrwxrwxrwx 1 root root 21 May 31 14:24 reserved5 -> /dev/block/mmcblk0p15
lrwxrwxrwx 1 root root 21 May 31 14:24 reserved4 -> /dev/block/mmcblk0p14
lrwxrwxrwx 1 root root 20 May 31 14:24 reserved3 -> /dev/block/mmcblk0p9
lrwxrwxrwx 1 root root 21 May 31 14:24 reserved2 -> /dev/block/mmcblk0p23
lrwxrwxrwx 1 root root 21 May 31 14:24 reserved1 -> /dev/block/mmcblk0p17
lrwxrwxrwx 1 root root 21 May 31 14:24 recovery2 -> /dev/block/mmcblk0p22
lrwxrwxrwx 1 root root 21 May 31 14:24 recovery -> /dev/block/mmcblk0p29
lrwxrwxrwx 1 root root 21 May 31 14:24 product -> /dev/block/mmcblk0p48
lrwxrwxrwx 1 root root 21 May 31 14:24 persist -> /dev/block/mmcblk0p16
lrwxrwxrwx 1 root root 21 May 31 14:24 patch -> /dev/block/mmcblk0p40
lrwxrwxrwx 1 root root 20 May 31 14:24 oeminfo -> /dev/block/mmcblk0p8
lrwxrwxrwx 1 root root 20 May 31 14:24 nvme -> /dev/block/mmcblk0p7
lrwxrwxrwx 1 root root 21 May 31 14:24 modemnvm_update -> /dev/block/mmcblk0p21
lrwxrwxrwx 1 root root 21 May 31 14:24 modemnvm_system -> /dev/block/mmcblk0p12
lrwxrwxrwx 1 root root 21 May 31 14:24 modemnvm_img -> /dev/block/mmcblk0p11
lrwxrwxrwx 1 root root 20 May 31 14:24 modemnvm_factory -> /dev/block/mmcblk0p6
lrwxrwxrwx 1 root root 21 May 31 14:24 modemnvm_backup -> /dev/block/mmcblk0p10
lrwxrwxrwx 1 root root 21 May 31 14:24 modem_om -> /dev/block/mmcblk0p18
lrwxrwxrwx 1 root root 21 May 31 14:24 modem_fw -> /dev/block/mmcblk0p31
lrwxrwxrwx 1 root root 21 May 31 14:24 misc -> /dev/block/mmcblk0p20
lrwxrwxrwx 1 root root 21 May 31 14:24 hisitest2 -> /dev/block/mmcblk0p39
lrwxrwxrwx 1 root root 21 May 31 14:24 hisitest1 -> /dev/block/mmcblk0p38
lrwxrwxrwx 1 root root 21 May 31 14:24 hisitest0 -> /dev/block/mmcblk0p37
lrwxrwxrwx 1 root root 20 May 31 14:24 fw_lpm3 -> /dev/block/mmcblk0p3
lrwxrwxrwx 1 root root 21 May 31 14:24 fw_hifi -> /dev/block/mmcblk0p27
lrwxrwxrwx 1 root root 20 May 31 14:24 frp -> /dev/block/mmcblk0p4
lrwxrwxrwx 1 root root 20 May 31 14:24 fastboot -> /dev/block/mmcblk0p5
lrwxrwxrwx 1 root root 21 May 31 14:24 dts -> /dev/block/mmcblk0p30
lrwxrwxrwx 1 root root 21 May 31 14:24 dfx -> /dev/block/mmcblk0p34
lrwxrwxrwx 1 root root 21 May 31 14:24 cust -> /dev/block/mmcblk0p45
lrwxrwxrwx 1 root root 21 May 31 14:24 cache -> /dev/block/mmcblk0p36
lrwxrwxrwx 1 root root 21 May 31 14:24 bootfail_info -> /dev/block/mmcblk0p41
lrwxrwxrwx 1 root root 21 May 31 14:24 boot -> /dev/block/mmcblk0p28
I don't have fota.
Click to expand...
Click to collapse
Thats was for LG G2, it's different here

Hello,
I fixed it with DC Phoenix and the right FW.
Thanks !

Orphee said:
Hello,
I fixed it with DC Phoenix and the right FW.
Thanks !
Click to expand...
Click to collapse
:good:

can you please give me the link for dc phoenix?
Orphee said:
Hello,
I fixed it with DC Phoenix and the right FW.
Thanks !
Click to expand...
Click to collapse
i have the same problem with my p10 lite. please give me the link of dc phoenix.

geanish95 said:
i have the same problem with my p10 lite. please give me the link of dc phoenix.
Click to expand...
Click to collapse
https://www.dc-unlocker.com/file-list/DC-unlocker_softwares/DC_Phoenix

Good evening I have a huawei p10 lite and I installed another firmware of another phone.
Now the p10 lite phone does not turn on, it is off, can anyone help me restore it?
Thanks so much
Angel
---------- Post added at 06:49 PM ---------- Previous post was at 06:37 PM ----------
I wanted to tell you that the phone Huawei p10 lite does not go into fastboot mode and do not know how to restore it.
I installed the firmware of another telephone DC Phoenix.
And now she does not turn on
Thank you and sorry for my English not perfect

Angelo_Thanks said:
Good evening I have a huawei p10 lite and I installed another firmware of another phone.
Now the p10 lite phone does not turn on, it is off, can anyone help me restore it?
Thanks so much
Angel
---------- Post added at 06:49 PM ---------- Previous post was at 06:37 PM ----------
I wanted to tell you that the phone Huawei p10 lite does not go into fastboot mode and do not know how to restore it.
I installed the firmware of another telephone DC Phoenix.
And now she does not turn on
Thank you and sorry for my English not perfect
Click to expand...
Click to collapse
Try plugging USB hold power+vol down
What's your model?

Hi my model is Huawei p10 Lite WAS-LX1A a few days ago I received the upgrade to C432B131 I wanted to install it as a please but did not allow me with unlocked and root recovery TWRP.
Then I installed it I do not know how to do it after several attempts but the phone did not work well. When I clicked on developer options she returned to the home page. So that I then installed a firmware of another phone and so no longer signs of life. I tried various keystrokes but nothing turned on.
Can you help me please?
Thanks the phone is new.
Angel

I DC Phoenix active on the PC does not know yet how long the activation with credits. How can I restore the Huawei P10 Lite phone that does not turn on?
The phone does not go in fastboot mode !!!
Thank you very much for helping
Angel

I tried to charge the Huawei p10 lite phone
but will not charge does not light any LED while it is charging anything.
can you help me?
Is there a way to restart the phone with a Toolkit or something else?
I thank you for the answer.

Angelo_Thanks said:
I tried to charge the Huawei p10 lite phone
but will not charge does not light any LED while it is charging anything.
can you help me?
Is there a way to restart the phone with a Toolkit or something else?
I thank you for the answer.
Click to expand...
Click to collapse
You may send a message on dc phoenix support website, I know he has another tool (HCU? ), if there is a way to revive it, he will probably know how...

[DUMP/UNPACK] - OnePlus 6T [OOS 9.0.5/6/7]

DUMP - OnePlus 6T [OOS 9.0.5/6]
{
"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"
}
boot.img will help get TWRP issues actually do something with their device. ?!
system.img and vendor.img will help with ports , dev , ect.
these zips are not "flashable" !!! just compressed files
Download: DUMP - OnePlus 6T [OOS 9.0.5]
Download: DUMP - OnePlus 6T [OOS 9.0.6]
Download: DUMP - OnePlus 6T [OOS 9.0.7]
My dump & My G-D upload

thx for the dump. will try to boot the system on my op5 since with openbeta he got treble support

S3V3N said:
DUMP - OnePlus 6T [OOS 9.0.5]
boot.img will help get TWRP issues actually do something with their device. ?!
system.img and vendor.img will help with ports , dev , ect.
these zips are not "flashable" !!! just compressed files
Download: DUMP - OnePlus 6T [OOS 9.0.5]
My dump & My G-D upload
Click to expand...
Click to collapse
Yes, I think this is all I need to fix my device. Oneplus sent me a device that wouldn't boot. L2 Tech remoted in to my pc and said apparently the firmware hasn't been flashed to the device. After 5 minutes of troubleshooting they weren't able to get it to flash.
Eventually I was able to get it to register to my pc and this might be what fixes it for me. Downloading as I type this. Unfortunately I already ordered a replacement that shipped an hour ago and have a refund process to return this one started... At least I can play with it til the new one arrives.

Code:
drwxr-xr-x 2 root root 2060 1970-01-01 04:52 .
drwxr-xr-x 3 root root 2200 1970-01-01 04:52 ..
lrwxrwxrwx 1 root root 15 1970-01-01 04:52 ALIGN_TO_128K_1 -> /dev/block/sdd1
lrwxrwxrwx 1 root root 15 1970-01-01 04:52 ALIGN_TO_128K_2 -> /dev/block/sdf1
lrwxrwxrwx 1 root root 16 1970-01-01 04:52 ImageFv -> /dev/block/sde72
lrwxrwxrwx 1 root root 16 1970-01-01 04:52 LOGO_a -> /dev/block/sde20
lrwxrwxrwx 1 root root 16 1970-01-01 04:52 LOGO_b -> /dev/block/sde48
lrwxrwxrwx 1 root root 15 1970-01-01 04:52 abl_a -> /dev/block/sde8
lrwxrwxrwx 1 root root 16 1970-01-01 04:52 abl_b -> /dev/block/sde36
lrwxrwxrwx 1 root root 16 1970-01-01 04:52 aging -> /dev/block/sde58
lrwxrwxrwx 1 root root 15 1970-01-01 04:52 aop_a -> /dev/block/sde1
lrwxrwxrwx 1 root root 16 1970-01-01 04:52 aop_b -> /dev/block/sde29
lrwxrwxrwx 1 root root 16 1970-01-01 04:52 apdp -> /dev/block/sde63
lrwxrwxrwx 1 root root 15 1970-01-01 04:52 bluetooth_a -> /dev/block/sde5
lrwxrwxrwx 1 root root 16 1970-01-01 04:52 bluetooth_b -> /dev/block/sde33
lrwxrwxrwx 1 root root 16 1970-01-01 04:52 boot_a -> /dev/block/sde11
lrwxrwxrwx 1 root root 16 1970-01-01 04:52 boot_b -> /dev/block/sde39
lrwxrwxrwx 1 root root 15 1970-01-01 04:52 cdt -> /dev/block/sdd2
lrwxrwxrwx 1 root root 16 1970-01-01 04:52 cmnlib64_a -> /dev/block/sde13
lrwxrwxrwx 1 root root 16 1970-01-01 04:52 cmnlib64_b -> /dev/block/sde41
lrwxrwxrwx 1 root root 16 1970-01-01 04:52 cmnlib_a -> /dev/block/sde12
lrwxrwxrwx 1 root root 16 1970-01-01 04:52 cmnlib_b -> /dev/block/sde40
lrwxrwxrwx 1 root root 16 1970-01-01 04:52 config -> /dev/block/sda12
lrwxrwxrwx 1 root root 15 1970-01-01 04:52 ddr -> /dev/block/sdd3
lrwxrwxrwx 1 root root 16 1970-01-01 04:52 devcfg_a -> /dev/block/sde14
lrwxrwxrwx 1 root root 16 1970-01-01 04:52 devcfg_b -> /dev/block/sde42
lrwxrwxrwx 1 root root 16 1970-01-01 04:52 devinfo -> /dev/block/sde61
lrwxrwxrwx 1 root root 16 1970-01-01 04:52 dip -> /dev/block/sde62
lrwxrwxrwx 1 root root 15 1970-01-01 04:52 dsp_a -> /dev/block/sde9
lrwxrwxrwx 1 root root 16 1970-01-01 04:52 dsp_b -> /dev/block/sde37
lrwxrwxrwx 1 root root 16 1970-01-01 04:52 dtbo_a -> /dev/block/sde18
lrwxrwxrwx 1 root root 16 1970-01-01 04:52 dtbo_b -> /dev/block/sde46
lrwxrwxrwx 1 root root 15 1970-01-01 04:52 frp -> /dev/block/sda6
lrwxrwxrwx 1 root root 15 1970-01-01 04:52 fsc -> /dev/block/sdf5
lrwxrwxrwx 1 root root 15 1970-01-01 04:52 fsg -> /dev/block/sdf4
lrwxrwxrwx 1 root root 16 1970-01-01 04:52 fw_4j1ed_a -> /dev/block/sde21
lrwxrwxrwx 1 root root 16 1970-01-01 04:52 fw_4j1ed_b -> /dev/block/sde49
lrwxrwxrwx 1 root root 16 1970-01-01 04:52 fw_4u1ea_a -> /dev/block/sde22
lrwxrwxrwx 1 root root 16 1970-01-01 04:52 fw_4u1ea_b -> /dev/block/sde50
lrwxrwxrwx 1 root root 16 1970-01-01 04:52 fw_ufs3_a -> /dev/block/sde23
lrwxrwxrwx 1 root root 16 1970-01-01 04:52 fw_ufs3_b -> /dev/block/sde51
lrwxrwxrwx 1 root root 16 1970-01-01 04:52 fw_ufs4_a -> /dev/block/sde24
lrwxrwxrwx 1 root root 16 1970-01-01 04:52 fw_ufs4_b -> /dev/block/sde52
lrwxrwxrwx 1 root root 16 1970-01-01 04:52 fw_ufs5_a -> /dev/block/sde25
lrwxrwxrwx 1 root root 16 1970-01-01 04:52 fw_ufs5_b -> /dev/block/sde53
lrwxrwxrwx 1 root root 16 1970-01-01 04:52 fw_ufs6_a -> /dev/block/sde26
lrwxrwxrwx 1 root root 16 1970-01-01 04:52 fw_ufs6_b -> /dev/block/sde54
lrwxrwxrwx 1 root root 16 1970-01-01 04:52 fw_ufs7_a -> /dev/block/sde27
lrwxrwxrwx 1 root root 16 1970-01-01 04:52 fw_ufs7_b -> /dev/block/sde55
lrwxrwxrwx 1 root root 16 1970-01-01 04:52 fw_ufs8_a -> /dev/block/sde28
lrwxrwxrwx 1 root root 16 1970-01-01 04:52 fw_ufs8_b -> /dev/block/sde56
lrwxrwxrwx 1 root root 15 1970-01-01 04:52 hyp_a -> /dev/block/sde3
lrwxrwxrwx 1 root root 16 1970-01-01 04:52 hyp_b -> /dev/block/sde31
lrwxrwxrwx 1 root root 16 1970-01-01 04:52 keymaster_a -> /dev/block/sde10
lrwxrwxrwx 1 root root 16 1970-01-01 04:52 keymaster_b -> /dev/block/sde38
lrwxrwxrwx 1 root root 15 1970-01-01 04:52 keystore -> /dev/block/sda5
lrwxrwxrwx 1 root root 16 1970-01-01 04:52 limits -> /dev/block/sde67
lrwxrwxrwx 1 root root 16 1970-01-01 04:52 logdump -> /dev/block/sde71
lrwxrwxrwx 1 root root 16 1970-01-01 04:52 logfs -> /dev/block/sde69
lrwxrwxrwx 1 root root 15 1970-01-01 04:52 mdtp_a -> /dev/block/sde7
lrwxrwxrwx 1 root root 16 1970-01-01 04:52 mdtp_b -> /dev/block/sde35
lrwxrwxrwx 1 root root 15 1970-01-01 04:52 mdtpsecapp_a -> /dev/block/sde6
lrwxrwxrwx 1 root root 16 1970-01-01 04:52 mdtpsecapp_b -> /dev/block/sde34
lrwxrwxrwx 1 root root 16 1970-01-01 04:52 minidump -> /dev/block/sde57
lrwxrwxrwx 1 root root 15 1970-01-01 04:52 misc -> /dev/block/sda3
lrwxrwxrwx 1 root root 15 1970-01-01 04:52 modem_a -> /dev/block/sde4
lrwxrwxrwx 1 root root 16 1970-01-01 04:52 modem_b -> /dev/block/sde32
lrwxrwxrwx 1 root root 15 1970-01-01 04:52 modemst1 -> /dev/block/sdf2
lrwxrwxrwx 1 root root 15 1970-01-01 04:52 modemst2 -> /dev/block/sdf3
lrwxrwxrwx 1 root root 16 1970-01-01 04:52 msadp -> /dev/block/sde64
lrwxrwxrwx 1 root root 16 1970-01-01 04:52 odm_a -> /dev/block/sda15
lrwxrwxrwx 1 root root 16 1970-01-01 04:52 odm_b -> /dev/block/sda16
lrwxrwxrwx 1 root root 15 1970-01-01 04:52 oem_dycnvbk -> /dev/block/sda8
lrwxrwxrwx 1 root root 15 1970-01-01 04:52 oem_stanvbk -> /dev/block/sda9
lrwxrwxrwx 1 root root 16 1970-01-01 04:52 op1 -> /dev/block/sde59
lrwxrwxrwx 1 root root 15 1970-01-01 04:52 op2 -> /dev/block/sda7
lrwxrwxrwx 1 root root 15 1970-01-01 04:52 param -> /dev/block/sda4
lrwxrwxrwx 1 root root 15 1970-01-01 04:52 persist -> /dev/block/sda2
lrwxrwxrwx 1 root root 16 1970-01-01 04:52 qupfw_a -> /dev/block/sde15
lrwxrwxrwx 1 root root 16 1970-01-01 04:52 qupfw_b -> /dev/block/sde43
lrwxrwxrwx 1 root root 16 1970-01-01 04:52 reserve1 -> /dev/block/sda10
lrwxrwxrwx 1 root root 16 1970-01-01 04:52 reserve2 -> /dev/block/sda11
lrwxrwxrwx 1 root root 16 1970-01-01 04:52 sec -> /dev/block/sde60
lrwxrwxrwx 1 root root 16 1970-01-01 04:52 splash -> /dev/block/sde66
lrwxrwxrwx 1 root root 16 1970-01-01 04:52 spunvm -> /dev/block/sde65
lrwxrwxrwx 1 root root 15 1970-01-01 04:52 ssd -> /dev/block/sda1
lrwxrwxrwx 1 root root 16 1970-01-01 04:52 sti -> /dev/block/sde70
lrwxrwxrwx 1 root root 16 1970-01-01 04:52 storsec_a -> /dev/block/sde19
lrwxrwxrwx 1 root root 16 1970-01-01 04:52 storsec_b -> /dev/block/sde47
lrwxrwxrwx 1 root root 16 1970-01-01 04:52 system_a -> /dev/block/sda13
lrwxrwxrwx 1 root root 16 1970-01-01 04:52 system_b -> /dev/block/sda14
lrwxrwxrwx 1 root root 16 1970-01-01 04:52 toolsfv -> /dev/block/sde68
lrwxrwxrwx 1 root root 15 1970-01-01 04:52 tz_a -> /dev/block/sde2
lrwxrwxrwx 1 root root 16 1970-01-01 04:52 tz_b -> /dev/block/sde30
lrwxrwxrwx 1 root root 16 1970-01-01 04:52 userdata -> /dev/block/sda17
lrwxrwxrwx 1 root root 16 1970-01-01 04:52 vbmeta_a -> /dev/block/sde17
lrwxrwxrwx 1 root root 16 1970-01-01 04:52 vbmeta_b -> /dev/block/sde45
lrwxrwxrwx 1 root root 16 1970-01-01 04:52 vendor_a -> /dev/block/sde16
lrwxrwxrwx 1 root root 16 1970-01-01 04:52 vendor_b -> /dev/block/sde44
lrwxrwxrwx 1 root root 15 1970-01-01 04:52 xbl_a -> /dev/block/sdb1
lrwxrwxrwx 1 root root 15 1970-01-01 04:52 xbl_b -> /dev/block/sdc1
lrwxrwxrwx 1 root root 15 1970-01-01 04:52 xbl_config_a -> /dev/block/sdb2
lrwxrwxrwx 1 root root 15 1970-01-01 04:52 xbl_config_b -> /dev/block/sdc2
OnePlus6T:/ #
if someone need the partition above
i owned the oneplus 6T since yesterday. i will make my Eragon Custom Rom for it very soon

@skeleton1911
You're right
Because I am just collecting for the purchase of this phone, I unpacked the firmware and shared it. My mistake

My 6T is stuck in boot loop. It was rooted and had blue spark installed. Can I use these files to recover, how?

You take the boot.img .
Then with buttons hold power and vol+ and vol- until the phone reboots
Then you are in Fastboot Mode
Via ADB flash the boot.img
Fastboot flash boot boot.img
pramathesh said:
My 6T is stuck in boot loop. It was rooted and had blue spark installed. Can I use these files to recover, how?
Click to expand...
Click to collapse
Gesendet von meinem ONEPLUS A6013 mit Tapatalk
---------- Post added at 12:40 PM ---------- Previous post was at 12:37 PM ----------
Hold power and vol-+ and vol-
Gesendet von meinem ONEPLUS A6013 mit Tapatalk

skeleton1911 said:
You take the boot.img .
Then with buttons hold power and vol+ .
When the phone boots again release power but still hold vol+
Then you are in Fastboot Mode
Via ADB flash the boot.img
Fastboot flash boot boot.img
Gesendet von meinem ONEPLUS A6013 mit Tapatalk
Click to expand...
Click to collapse
Let me give this a try and report. My guess is that the 9.0.5 update was applied automatically thereby messing my phone. Also, if the phone was 9.0.4 the 9.0.5 image would work fine, right?

pramathesh said:
Let me give this a try and report. My guess is that the 9.0.5 update was applied automatically thereby messing my phone. Also, if the phone was 9.0.4 the 9.0.5 image would work fine, right?
Click to expand...
Click to collapse
Read above again. Hold all buttons.
Also 9.0.5 is on slot b
And 9.0.4 on a.
So if it don't work you can just set slot b
Fastboot --set-active=b
Gesendet von meinem ONEPLUS A6013 mit Tapatalk

skeleton1911 said:
Read above again. Hold all buttons.
Also 9.0.5 is on slot b
And 9.0.4 on a.
So if it don't work you can just set slot b
Fastboot --set-active=b
Gesendet von meinem ONEPLUS A6013 mit Tapatalk
Click to expand...
Click to collapse
So, if I get this right 9.0.5 can be flashed in a and b either. It a cause of concern then, right?

You can flash it in both yes. But useless . If it's on b it's fine
pramathesh said:
So, if I get this right 9.0.5 can be flashed in a and b either. It a cause of concern then, right?
Click to expand...
Click to collapse
Gesendet von meinem ONEPLUS A6013 mit Tapatalk

skeleton1911 said:
You can flash it in both yes. But useless . If it's on b it's fine
Gesendet von meinem ONEPLUS A6013 mit Tapatalk
Click to expand...
Click to collapse
Downloading the files now. Hoping it works fine, let's hope you are still online just in case something goes off!
---------- Post added at 05:39 PM ---------- Previous post was at 05:31 PM ----------
skeleton1911 said:
You can flash it in both yes. But useless . If it's on b it's fine
Gesendet von meinem ONEPLUS A6013 mit Tapatalk
Click to expand...
Click to collapse
I have a weird problem of the device not getting detected. This is the same machine I had used to root the device earlier. No device number is getting shown but the reboot command did work on the terminal

pramathesh said:
Downloading the files now. Hoping it works fine, let's hope you are still online just in case something goes off!
---------- Post added at 05:39 PM ---------- Previous post was at 05:31 PM ----------
I have a weird problem of the device not getting detected. This is the same machine I had used to root the device earlier. No device number is getting shown but the reboot command did work on the terminal
Click to expand...
Click to collapse
only use adb fastboot. sdk . dont use a program etc.
if you want i can take a look, send me a private message, we go via teamviewer ( i need id and password of teamviewer then)

skeleton1911 said:
only use adb fastboot. sdk . dont use a program etc.
if you want i can take a look, send me a private message, we go via teamviewer ( i need id and password of teamviewer then)
Click to expand...
Click to collapse
Using minimal fastboot and adb. The device number isn't shown but fasboot reboot did work on it. Bluespark is showing partition b is active. So I am guessing that is where I have to flash the boot.img. I am happy to let you take over my PC and let you handle it. Let's get over PM, shall we?

pramathesh said:
Using minimal fastboot and adb. The device number isn't shown but fasboot reboot did work on it. Bluespark is showing partition b is active. So I am guessing that is where I have to flash the boot.img. I am happy to let you take over my PC and let you handle it. Let's get over PM, shall we?
Click to expand...
Click to collapse
yes. send me

skeleton1911 said:
yes. send me
Click to expand...
Click to collapse
fastboot did work. Just tried that before sending you a PM. I cannot thank you enough for saving my life here <3
---------- Post added at 06:03 PM ---------- Previous post was at 06:00 PM ----------
Restarting the phone is causing the loop to happen again. Any way to fix that?
Wifi isn't switching on either. Stuck pretty bad here now

pramathesh said:
fastboot did work. Just tried that before sending you a PM. I cannot thank you enough for saving my life here <3
---------- Post added at 06:03 PM ---------- Previous post was at 06:00 PM ----------
Restarting the phone is causing the loop to happen again. Any way to fix that?
Wifi isn't switching on either. Stuck pretty bad here now
Click to expand...
Click to collapse
i will help you.
now send me pm and we will manage it. (teamviewer)

Is this full dump include all partition? I used other fastboot stock rom and somehow end up losing my VOLTE ON SIM slot 1 but when i switch to sim slot 2 everything work...kinda frustrating...kinda news to OP

vouch post for @skeleton1911. Cannot thank you enough for going out of your way to help me resolve the issue

_BГ@ckθut said:
Is this full dump include all partition? I used other fastboot stock rom and somehow end up losing my VOLTE ON SIM slot 1 but when i switch to sim slot 2 everything work...kinda frustrating...kinda news to OP
Click to expand...
Click to collapse
no. not all.
i think he did not own the phone and therefore he dont has all...
BTW little tip:
Never ever flash the modem_st1 and modem_st2 image files.! after that the risk is high to lose imei numbers.
pramathesh said:
vouch post for @skeleton1911. Cannot thank you enough for going out of your way to help me resolve the issue
Click to expand...
Click to collapse
your welcome!