I have a Korean Galaxy S4, model number SHV-E330S. Copied the TWRP recovery.img to /dev/block/mmcblk0p10 but it turned out that 0p10 is the "param" partition, so now the phone cannot connect to cellular network, it shows the circle icon with strike-through. The phone still shows the correct IMEI number when dialing *#06#, and it can connect to wifi networks. Also can boot into recovery mode and wiping the system does not help.
Is there any way to make my phone work?
A bit more context of what I did:
Tried to install cyanogenmod on the phone, but it failed with "Signature verification failed". I thought it is because the stock recovery does not allow to install 3rd party roms.
So I tried to install CWM/TWRP recovery on it using ODIN3 when the phone was in download mode. It did not work, could not boot into CWM, it always started the stock recovery. I saw in the install guides that I can copy the recovery image to the phone with dd if I have root.
So I rooted it with this. It worked. Then I followed the instructions here (came from this site) and executed dd if=/sdcard/recovery.img of=/dev/block/mmcblk0p10
This website did not talk about creating a backup of that partition first, so I did not do that. The cellular network probably stopped working at this point, but I only noticed it later.
The partitions on my phone:
[email protected]:/ # ls -l /dev/block/platform/msm_sdcc.1/by-name
lrwxrwxrwx root root 1970-01-02 00:00 aboot -> /dev/block/mmcblk0p6
lrwxrwxrwx root root 1970-01-02 00:00 apnhlos -> /dev/block/mmcblk0p1
lrwxrwxrwx root root 1970-01-02 00:00 backup -> /dev/block/mmcblk0p17
lrwxrwxrwx root root 1970-01-02 00:00 boot -> /dev/block/mmcblk0p14
lrwxrwxrwx root root 1970-01-02 00:00 cache -> /dev/block/mmcblk0p24
lrwxrwxrwx root root 1970-01-02 00:00 dbi -> /dev/block/mmcblk0p4
lrwxrwxrwx root root 1970-01-02 00:00 ddr -> /dev/block/mmcblk0p5
lrwxrwxrwx root root 1970-01-02 00:00 efs -> /dev/block/mmcblk0p11
lrwxrwxrwx root root 1970-01-02 00:00 fota -> /dev/block/mmcblk0p16
lrwxrwxrwx root root 1970-01-02 00:00 fsc -> /dev/block/mmcblk0p19
lrwxrwxrwx root root 1970-01-02 00:00 fsg -> /dev/block/mmcblk0p18
lrwxrwxrwx root root 1970-01-02 00:00 hidden -> /dev/block/mmcblk0p25
lrwxrwxrwx root root 1970-01-02 00:00 modem -> /dev/block/mmcblk0p2
lrwxrwxrwx root root 1970-01-02 00:00 modemst1 -> /dev/block/mmcblk0p12
lrwxrwxrwx root root 1970-01-02 00:00 modemst2 -> /dev/block/mmcblk0p13
lrwxrwxrwx root root 1970-01-02 00:00 pad -> /dev/block/mmcblk0p9
lrwxrwxrwx root root 1970-01-02 00:00 param -> /dev/block/mmcblk0p10
lrwxrwxrwx root root 1970-01-02 00:00 persdata -> /dev/block/mmcblk0p22
lrwxrwxrwx root root 1970-01-02 00:00 persist -> /dev/block/mmcblk0p21
lrwxrwxrwx root root 1970-01-02 00:00 recovery -> /dev/block/mmcblk0p15
lrwxrwxrwx root root 1970-01-02 00:00 rpm -> /dev/block/mmcblk0p7
lrwxrwxrwx root root 1970-01-02 00:00 sbl1 -> /dev/block/mmcblk0p3
lrwxrwxrwx root root 1970-01-02 00:00 ssd -> /dev/block/mmcblk0p20
lrwxrwxrwx root root 1970-01-02 00:00 system -> /dev/block/mmcblk0p23
lrwxrwxrwx root root 1970-01-02 00:00 tz -> /dev/block/mmcblk0p8
lrwxrwxrwx root root 1970-01-02 00:00 userdata -> /dev/block/mmcblk0p26
[email protected]:/ #
Would it work if I copy the /dev/block/mmcblk0p10 partition from an other phone? What is on the param partition?
sullerandras said:
I have a Korean Galaxy S4, model number SHV-E330S. Copied the TWRP recovery.img to /dev/block/mmcblk0p10 but it turned out that 0p10 is the "param" partition, so now the phone cannot connect to cellular network, it shows the circle icon with strike-through. The phone still shows the correct IMEI number when dialing *#06#, and it can connect to wifi networks. Also can boot into recovery mode and wiping the system does not help.
Is there any way to make my phone work?
A bit more context of what I did:
Tried to install cyanogenmod on the phone, but it failed with "Signature verification failed". I thought it is because the stock recovery does not allow to install 3rd party roms.
So I tried to install CWM/TWRP recovery on it using ODIN3 when the phone was in download mode. It did not work, could not boot into CWM, it always started the stock recovery. I saw in the install guides that I can copy the recovery image to the phone with dd if I have root.
So I rooted it with this. It worked. Then I followed the instructions here (came from this site) and executed dd if=/sdcard/recovery.img of=/dev/block/mmcblk0p10
This website did not talk about creating a backup of that partition first, so I did not do that. The cellular network probably stopped working at this point, but I only noticed it later.
The partitions on my phone:
[email protected]:/ # ls -l /dev/block/platform/msm_sdcc.1/by-name
lrwxrwxrwx root root 1970-01-02 00:00 aboot -> /dev/block/mmcblk0p6
lrwxrwxrwx root root 1970-01-02 00:00 apnhlos -> /dev/block/mmcblk0p1
lrwxrwxrwx root root 1970-01-02 00:00 backup -> /dev/block/mmcblk0p17
lrwxrwxrwx root root 1970-01-02 00:00 boot -> /dev/block/mmcblk0p14
lrwxrwxrwx root root 1970-01-02 00:00 cache -> /dev/block/mmcblk0p24
lrwxrwxrwx root root 1970-01-02 00:00 dbi -> /dev/block/mmcblk0p4
lrwxrwxrwx root root 1970-01-02 00:00 ddr -> /dev/block/mmcblk0p5
lrwxrwxrwx root root 1970-01-02 00:00 efs -> /dev/block/mmcblk0p11
lrwxrwxrwx root root 1970-01-02 00:00 fota -> /dev/block/mmcblk0p16
lrwxrwxrwx root root 1970-01-02 00:00 fsc -> /dev/block/mmcblk0p19
lrwxrwxrwx root root 1970-01-02 00:00 fsg -> /dev/block/mmcblk0p18
lrwxrwxrwx root root 1970-01-02 00:00 hidden -> /dev/block/mmcblk0p25
lrwxrwxrwx root root 1970-01-02 00:00 modem -> /dev/block/mmcblk0p2
lrwxrwxrwx root root 1970-01-02 00:00 modemst1 -> /dev/block/mmcblk0p12
lrwxrwxrwx root root 1970-01-02 00:00 modemst2 -> /dev/block/mmcblk0p13
lrwxrwxrwx root root 1970-01-02 00:00 pad -> /dev/block/mmcblk0p9
lrwxrwxrwx root root 1970-01-02 00:00 param -> /dev/block/mmcblk0p10
lrwxrwxrwx root root 1970-01-02 00:00 persdata -> /dev/block/mmcblk0p22
lrwxrwxrwx root root 1970-01-02 00:00 persist -> /dev/block/mmcblk0p21
lrwxrwxrwx root root 1970-01-02 00:00 recovery -> /dev/block/mmcblk0p15
lrwxrwxrwx root root 1970-01-02 00:00 rpm -> /dev/block/mmcblk0p7
lrwxrwxrwx root root 1970-01-02 00:00 sbl1 -> /dev/block/mmcblk0p3
lrwxrwxrwx root root 1970-01-02 00:00 ssd -> /dev/block/mmcblk0p20
lrwxrwxrwx root root 1970-01-02 00:00 system -> /dev/block/mmcblk0p23
lrwxrwxrwx root root 1970-01-02 00:00 tz -> /dev/block/mmcblk0p8
lrwxrwxrwx root root 1970-01-02 00:00 userdata -> /dev/block/mmcblk0p26
[email protected]:/ #
Would it work if I copy the /dev/block/mmcblk0p10 partition from an other phone? What is on the param partition?
Click to expand...
Click to collapse
If you're rooted you can use the app Flashify to flash the recovery.img. I recommend TWRP though.
GDReaper said:
If you're rooted you can use the app Flashify to flash the recovery.img. I recommend TWRP though.
Click to expand...
Click to collapse
Thanks. But it is too late for that, isn't it? The phone is kind of bricked, and flashing a TWRP recovery will not magically unbrick it, right?
sullerandras said:
Thanks. But it is too late for that, isn't it? The phone is kind of bricked, and flashing a TWRP recovery will not magically unbrick it, right?
Click to expand...
Click to collapse
How is it bricked?
From what I understood, you don't have signal anymore, but other than that the phone works.
But you are right, flashing a recovery won't make your signal come back, but maybe flashing a modem will.
The param partition is setting where the boot images are stored, from what I've taken in other threads.
GDReaper said:
How is it bricked?
From what I understood, you don't have signal anymore, but other than that the phone works.
But you are right, flashing a recovery won't make your signal come back, but maybe flashing a modem will.
The param partition is setting where the boot images are stored, from what I've taken in other threads.
Click to expand...
Click to collapse
As I described in the first message in the thread, I accidentally overwrote the mmcblk0p10 partition which is the "param" partition. Since that the phone cannot connect to cellular network, so cannot make phone calls, cannot receive sms and cannot connect to LTE.
But it shows the correct "IMEI" and the correct "Baseband version" in Settings / About device. It can also connect to wifi network, so I can install/update apps and play games.
I downloaded the stock ROM from samsung-update.com: SKT-E330SKSUCNJ1-20141015090913.zip. It is 1.7GB and it took almost 24 hours to download.
I installed this ROM on the phone with ODIN but it did not help. So the problem is probably not with the "modem" partition since it was overwritten by the stock rom.
And found some details about the param partition here:
PARAM: This is the Parameter partition which contains a number of parameters,
variables and settings of the hardware. Apparently it has an 88 byte header
structure that tell us if the MODEMST1 and MODEMST2 have been backed up to the
FSG and BACKUP partitions, respectively. Furthermore it contain all the debug
settings (DLOW/DMID/DHIG etc), the "triangle" status of whether or not you have
flashed custom ROMs and the flash count (0x3FFE00). Current boot mode in use,
and much more. The info about this partition could easily occupy a book by
itself.
Click to expand...
Click to collapse
sullerandras said:
As I described in the first message in the thread, I accidentally overwrote the mmcblk0p10 partition which is the "param" partition. Since that the phone cannot connect to cellular network, so cannot make phone calls, cannot receive sms and cannot connect to LTE.
But it shows the correct "IMEI" and the correct "Baseband version" in Settings / About device. It can also connect to wifi network, so I can install/update apps and play games.
I downloaded the stock ROM from samsung-update.com: SKT-E330SKSUCNJ1-20141015090913.zip. It is 1.7GB and it took almost 24 hours to download.
I installed this ROM on the phone with ODIN but it did not help. So the problem is probably not with the "modem" partition since it was overwritten by the stock rom.
And found some details about the param partition here:
Click to expand...
Click to collapse
Try using a PIT file.
GDReaper said:
Try using a PIT file.
Click to expand...
Click to collapse
It turns out the phone is working, but the reception is bad: if I go to a better location then it works, I'm able to make and receive calls.
So the problem is not with the software. Maybe the antenna is spoiled? I suspect that because pulling the antenna out does not improve the signal level.
sullerandras said:
It turns out the phone is working, but the reception is bad: if I go to a better location then it works, I'm able to make and receive calls.
So the problem is not with the software. Maybe the antenna is spoiled? I suspect that because pulling the antenna out does not improve the signal level.
Click to expand...
Click to collapse
I would try and change the modem.
Otherwise try fixing the antenna if the modem doesn't change anything.
GDReaper said:
I would try and change the modem.
Otherwise try fixing the antenna if the modem doesn't change anything.
Click to expand...
Click to collapse
What do you mean "change the modem"?
I guess the modem's firmware was updated because after I reinstalled the original OS the phone updated itself OTA to the latest 5.0.1 android, and now it shows a different Baseband number than before.
Do you think this could still be a software issue?
sullerandras said:
What do you mean "change the modem"?
I guess the modem's firmware was updated because after I reinstalled the original OS the phone updated itself OTA to the latest 5.0.1 android, and now it shows a different Baseband number than before.
Do you think this could still be a software issue?
Click to expand...
Click to collapse
People say Modems can change reception. Although I never saw any changes myself.
Related
Hi
Phone get rooted now. but i can't unlock to use sim free. how can i get network control unlock key ?
doantri said:
Hi
Phone get rooted now. but i can't unlock to use sim free. how can i get network control unlock key ?
Click to expand...
Click to collapse
How to display network unlock guy?
how did you root your SCL22 Note 3?
can u tell me what is the method that you used to root your SCL22 note 3
because i have the same problem .
Hi
You should use CWM SM-N9005 then update SU via CWM
I need unlock phone to use with gsm simcard but can't get unlock code.
doantri said:
Hi
You should use CWM SM-N9005 then update SU via CWM
I need unlock phone to use with gsm simcard but can't get unlock code.
Click to expand...
Click to collapse
can you share the file you use to unlock your phone?
you can you galaxim(i think) you can download in google play for free or regionlock away
beast08 said:
can you share the file you use to unlock your phone?
you can you galaxim(i think) you can download in google play for free or regionlock away
Click to expand...
Click to collapse
- CWM recovery for N9005: https://mega.co.nz/#!C0Y1RbyT!Iq1A1Aaef1qioyDHkGQVtkRUdGN0LCa37umKGMDyDs8
- SuperSU: http://download.chainfire.eu/372/SuperSU/UPDATE-SuperSU-v1.86.zip
first install CWM recovery then flash SuperSU via recovery
vndnguyen said:
- CWM recovery for N9005: https://mega.co.nz/#!C0Y1RbyT!Iq1A1Aaef1qioyDHkGQVtkRUdGN0LCa37umKGMDyDs8
- SuperSU: http://download.chainfire.eu/372/SuperSU/UPDATE-SuperSU-v1.86.zip
first install CWM recovery then flash SuperSU via recovery
Click to expand...
Click to collapse
i tried this method before, flashing the SuperSU v1.86 to my phone, but everytime im opening the app, it saying su binary need to update, abd the phone will reboot to CWM recovery, and when i checked it will Root Checker, it says the phone is not properly rooted.
beast08 said:
i tried this method before, flashing the SuperSU v1.86 to my phone, but everytime im opening the app, it saying su binary need to update, abd the phone will reboot to CWM recovery, and when i checked it will Root Checker, it says the phone is not properly rooted.
Click to expand...
Click to collapse
I just provided these links per suggestion from doantri
I'm not sure if it works for your phone or not. Sorry to hear that.
Can you re upload the cwm file in other site? Im getting a hard tome downloading a file from mega
Sent from my SCL22 using xda app-developers app
need help
Hi everybody. I successfully rooted my scl22 using the instructions in a chinese site : " SCL22 root & sim unlock
Galaxy Note3 SCL22のRoot化(SC-01Fも対応)
SM-N9005用CWMをOdinから焼き込み、SuperSUをインストールすればRoot化完了。
・SM-N9005用CWMのダウンロード先
n9005-cwm-recovery-6.0.4.5(1116).tar
・SuperSUのダウンロード先
UPDATE-SuperSU-v1.65.zip
・sgs3_rooting_supersu_v3.zipも必要です。ググってください。
○順番
1.CWMをOdinで焼きこみ。
2.CWMを起動し、sgs3_rooting_supersu_v3.zipをインストール。
3.続けてUPDATE-SuperSU-v1.65.zipをインストール。
4.再起動すればsuが効くようになります。
○カウントアップはCWMを焼くとKNOX WARRANTYが変化します。
他は初期ROM焼いて初期化すれば元に戻ります。
※カウントアップするとオサイフがNGになります。
※Root化されたsystem.imgのみ焼けば大丈夫かも？
KNOX WARRANTY VOID : 0x0
↓
KNOX WARRANTY VOID : 0x1
Galaxy Note 3 SCL22の内部パーティション
[email protected]:/ # ls -l /dev/block/platform/msm_sdcc.1/by-name/
ls -l /dev/block/platform/msm_sdcc.1/by-name/
lrwxrwxrwx root root 1970-01-02 04:36 aboot -> /dev/block/mmcblk0p6
lrwxrwxrwx root root 1970-01-02 04:36 apnhlos -> /dev/block/mmcblk0p1
lrwxrwxrwx root root 1970-01-02 04:36 backup -> /dev/block/mmcblk0p17
lrwxrwxrwx root root 1970-01-02 04:36 boot -> /dev/block/mmcblk0p14
lrwxrwxrwx root root 1970-01-02 04:36 cache -> /dev/block/mmcblk0p24
lrwxrwxrwx root root 1970-01-02 04:36 dbi -> /dev/block/mmcblk0p4
lrwxrwxrwx root root 1970-01-02 04:36 ddr -> /dev/block/mmcblk0p5
lrwxrwxrwx root root 1970-01-02 04:36 efs -> /dev/block/mmcblk0p11
lrwxrwxrwx root root 1970-01-02 04:36 fota -> /dev/block/mmcblk0p16
lrwxrwxrwx root root 1970-01-02 04:36 fsc -> /dev/block/mmcblk0p19
lrwxrwxrwx root root 1970-01-02 04:36 fsg -> /dev/block/mmcblk0p18
lrwxrwxrwx root root 1970-01-02 04:36 modem -> /dev/block/mmcblk0p2
lrwxrwxrwx root root 1970-01-02 04:36 modemst1 -> /dev/block/mmcblk0p12
lrwxrwxrwx root root 1970-01-02 04:36 modemst2 -> /dev/block/mmcblk0p13
lrwxrwxrwx root root 1970-01-02 04:36 pad -> /dev/block/mmcblk0p9
lrwxrwxrwx root root 1970-01-02 04:36 param -> /dev/block/mmcblk0p10
lrwxrwxrwx root root 1970-01-02 04:36 persdata -> /dev/block/mmcblk0p22
lrwxrwxrwx root root 1970-01-02 04:36 persist -> /dev/block/mmcblk0p21
lrwxrwxrwx root root 1970-01-02 04:36 recovery -> /dev/block/mmcblk0p15
lrwxrwxrwx root root 1970-01-02 04:36 rpm -> /dev/block/mmcblk0p7
lrwxrwxrwx root root 1970-01-02 04:36 sbl1 -> /dev/block/mmcblk0p3
lrwxrwxrwx root root 1970-01-02 04:36 ssd -> /dev/block/mmcblk0p20
lrwxrwxrwx root root 1970-01-02 04:36 system -> /dev/block/mmcblk0p23
lrwxrwxrwx root root 1970-01-02 04:36 tz -> /dev/block/mmcblk0p8
lrwxrwxrwx root root 1970-01-02 04:36 userdata -> /dev/block/mmcblk0p25
zhongkai cheng*时间：*下午7:20
,but not beeing experienced in programming , i wasn't able to aply the second set of instructions. There is a script that should be run and i do not know how to do that. Maybe someone with experience can help us.
Please anyone help us to SIM unlock Note 3 SCL22
mvmaos said:
Hi everybody. I successfully rooted my scl22 using the instructions in a chinese site : " SCL22 root & sim unlock
Galaxy Note3 SCL22のRoot化(SC-01Fも対応)
SM-N9005用CWMをOdinから焼き込み、SuperSUをインストールすればRoot化完了。
・SM-N9005用CWMのダウンロード先
n9005-cwm-recovery-6.0.4.5(1116).tar
・SuperSUのダウンロード先
UPDATE-SuperSU-v1.65.zip
・sgs3_rooting_supersu_v3.zipも必要です。ググってください。
○順番
1.CWMをOdinで焼きこみ。
2.CWMを起動し、sgs3_rooting_supersu_v3.zipをインストール。
3.続けてUPDATE-SuperSU-v1.65.zipをインストール。
4.再起動すればsuが効くようになります。
○カウントアップはCWMを焼くとKNOX WARRANTYが変化します。
他は初期ROM焼いて初期化すれば元に戻ります。
※カウントアップするとオサイフがNGになります。
※Root化されたsystem.imgのみ焼けば大丈夫かも？
KNOX WARRANTY VOID : 0x0
↓
KNOX WARRANTY VOID : 0x1
Galaxy Note 3 SCL22の内部パーティション
[email protected]:/ # ls -l /dev/block/platform/msm_sdcc.1/by-name/
ls -l /dev/block/platform/msm_sdcc.1/by-name/
lrwxrwxrwx root root 1970-01-02 04:36 aboot -> /dev/block/mmcblk0p6
lrwxrwxrwx root root 1970-01-02 04:36 apnhlos -> /dev/block/mmcblk0p1
lrwxrwxrwx root root 1970-01-02 04:36 backup -> /dev/block/mmcblk0p17
lrwxrwxrwx root root 1970-01-02 04:36 boot -> /dev/block/mmcblk0p14
lrwxrwxrwx root root 1970-01-02 04:36 cache -> /dev/block/mmcblk0p24
lrwxrwxrwx root root 1970-01-02 04:36 dbi -> /dev/block/mmcblk0p4
lrwxrwxrwx root root 1970-01-02 04:36 ddr -> /dev/block/mmcblk0p5
lrwxrwxrwx root root 1970-01-02 04:36 efs -> /dev/block/mmcblk0p11
lrwxrwxrwx root root 1970-01-02 04:36 fota -> /dev/block/mmcblk0p16
lrwxrwxrwx root root 1970-01-02 04:36 fsc -> /dev/block/mmcblk0p19
lrwxrwxrwx root root 1970-01-02 04:36 fsg -> /dev/block/mmcblk0p18
lrwxrwxrwx root root 1970-01-02 04:36 modem -> /dev/block/mmcblk0p2
lrwxrwxrwx root root 1970-01-02 04:36 modemst1 -> /dev/block/mmcblk0p12
lrwxrwxrwx root root 1970-01-02 04:36 modemst2 -> /dev/block/mmcblk0p13
lrwxrwxrwx root root 1970-01-02 04:36 pad -> /dev/block/mmcblk0p9
lrwxrwxrwx root root 1970-01-02 04:36 param -> /dev/block/mmcblk0p10
lrwxrwxrwx root root 1970-01-02 04:36 persdata -> /dev/block/mmcblk0p22
lrwxrwxrwx root root 1970-01-02 04:36 persist -> /dev/block/mmcblk0p21
lrwxrwxrwx root root 1970-01-02 04:36 recovery -> /dev/block/mmcblk0p15
lrwxrwxrwx root root 1970-01-02 04:36 rpm -> /dev/block/mmcblk0p7
lrwxrwxrwx root root 1970-01-02 04:36 sbl1 -> /dev/block/mmcblk0p3
lrwxrwxrwx root root 1970-01-02 04:36 ssd -> /dev/block/mmcblk0p20
lrwxrwxrwx root root 1970-01-02 04:36 system -> /dev/block/mmcblk0p23
lrwxrwxrwx root root 1970-01-02 04:36 tz -> /dev/block/mmcblk0p8
lrwxrwxrwx root root 1970-01-02 04:36 userdata -> /dev/block/mmcblk0p25
zhongkai cheng*时间：*下午7:20
,but not beeing experienced in programming , i wasn't able to aply the second set of instructions. There is a script that should be run and i do not know how to do that. Maybe someone with experience can help us.
Click to expand...
Click to collapse
hey
anyone know a method to get unlock code for SCL22 Galaxy note 3 ?
mvmaos said:
Hi everybody. I successfully rooted my scl22 using the instructions in a chinese site : " SCL22 root & sim unlock
Galaxy Note3 SCL22のRoot化(SC-01Fも対応)
SM-N9005用CWMをOdinから焼き込み、SuperSUをインストールすればRoot化完了。
・SM-N9005用CWMのダウンロード先
n9005-cwm-recovery-6.0.4.5(1116).tar
・SuperSUのダウンロード先
UPDATE-SuperSU-v1.65.zip
・sgs3_rooting_supersu_v3.zipも必要です。ググってください。
○順番
1.CWMをOdinで焼きこみ。
2.CWMを起動し、sgs3_rooting_supersu_v3.zipをインストール。
3.続けてUPDATE-SuperSU-v1.65.zipをインストール。
4.再起動すればsuが効くようになります。
○カウントアップはCWMを焼くとKNOX WARRANTYが変化します。
他は初期ROM焼いて初期化すれば元に戻ります。
※カウントアップするとオサイフがNGになります。
※Root化されたsystem.imgのみ焼けば大丈夫かも？
KNOX WARRANTY VOID : 0x0
↓
KNOX WARRANTY VOID : 0x1
Galaxy Note 3 SCL22の内部パーティション
[email protected]:/ # ls -l /dev/block/platform/msm_sdcc.1/by-name/
ls -l /dev/block/platform/msm_sdcc.1/by-name/
lrwxrwxrwx root root 1970-01-02 04:36 aboot -> /dev/block/mmcblk0p6
lrwxrwxrwx root root 1970-01-02 04:36 apnhlos -> /dev/block/mmcblk0p1
lrwxrwxrwx root root 1970-01-02 04:36 backup -> /dev/block/mmcblk0p17
lrwxrwxrwx root root 1970-01-02 04:36 boot -> /dev/block/mmcblk0p14
lrwxrwxrwx root root 1970-01-02 04:36 cache -> /dev/block/mmcblk0p24
lrwxrwxrwx root root 1970-01-02 04:36 dbi -> /dev/block/mmcblk0p4
lrwxrwxrwx root root 1970-01-02 04:36 ddr -> /dev/block/mmcblk0p5
lrwxrwxrwx root root 1970-01-02 04:36 efs -> /dev/block/mmcblk0p11
lrwxrwxrwx root root 1970-01-02 04:36 fota -> /dev/block/mmcblk0p16
lrwxrwxrwx root root 1970-01-02 04:36 fsc -> /dev/block/mmcblk0p19
lrwxrwxrwx root root 1970-01-02 04:36 fsg -> /dev/block/mmcblk0p18
lrwxrwxrwx root root 1970-01-02 04:36 modem -> /dev/block/mmcblk0p2
lrwxrwxrwx root root 1970-01-02 04:36 modemst1 -> /dev/block/mmcblk0p12
lrwxrwxrwx root root 1970-01-02 04:36 modemst2 -> /dev/block/mmcblk0p13
lrwxrwxrwx root root 1970-01-02 04:36 pad -> /dev/block/mmcblk0p9
lrwxrwxrwx root root 1970-01-02 04:36 param -> /dev/block/mmcblk0p10
lrwxrwxrwx root root 1970-01-02 04:36 persdata -> /dev/block/mmcblk0p22
lrwxrwxrwx root root 1970-01-02 04:36 persist -> /dev/block/mmcblk0p21
lrwxrwxrwx root root 1970-01-02 04:36 recovery -> /dev/block/mmcblk0p15
lrwxrwxrwx root root 1970-01-02 04:36 rpm -> /dev/block/mmcblk0p7
lrwxrwxrwx root root 1970-01-02 04:36 sbl1 -> /dev/block/mmcblk0p3
lrwxrwxrwx root root 1970-01-02 04:36 ssd -> /dev/block/mmcblk0p20
lrwxrwxrwx root root 1970-01-02 04:36 system -> /dev/block/mmcblk0p23
lrwxrwxrwx root root 1970-01-02 04:36 tz -> /dev/block/mmcblk0p8
lrwxrwxrwx root root 1970-01-02 04:36 userdata -> /dev/block/mmcblk0p25
zhongkai cheng*时间：*下午7:20
,but not beeing experienced in programming , i wasn't able to aply the second set of instructions. There is a script that should be run and i do not know how to do that. Maybe someone with experience can help us.
Click to expand...
Click to collapse
Hi mvmaos, can you hsare the files that needed to root the phone? i cant seem to download the files in the chinese site, thanks in advance
---------- Post added at 06:48 PM ---------- Previous post was at 06:39 PM ----------
niranjan.anu said:
hey
anyone know a method to get unlock code for SCL22 Galaxy note 3 ?
Click to expand...
Click to collapse
Hi niranjan.anu, are you rooted already? have you tried the region unlock app? or the galaxsim unlock app? you can find that in palystore
beast08 said:
Hi mvmaos, can you hsare the files that needed to root the phone? i cant seem to download the files in the chinese site, thanks in advance
---------- Post added at 06:48 PM ---------- Previous post was at 06:39 PM ----------
Hi niranjan.anu, are you rooted already? have you tried the region unlock app? or the galaxsim unlock app? you can find that in palystore
Click to expand...
Click to collapse
Hi to you to . just google for them, they are easy to find. the two aps won't work for our phone, i tried them all, i succedeed even the script above , but it won't work. i will try these days at a samsung service, maybe they can be briebd .
the problem with our phone is that is locked in the service menu, and we can not acces that menu and our phone has gsm frequencies locked.
mvmaos said:
Hi to you to . just google for them, they are easy to find. the two aps won't work for our phone, i tried them all, i succedeed even the script above , but it won't work. i will try these days at a samsung service, maybe they can be briebd .
the problem with our phone is that is locked in the service menu, and we can not acces that menu and our phone has gsm frequencies locked.
Click to expand...
Click to collapse
too bad those two app wont work, so we have to wait until someone find a way on how to unlock our phone.
SCL22 Simunlock OK!
If you can send a SCL22 in Japan, I can do a SIM unlock.
Price : $90 + postage(Paypal)
mail : [email protected]
>>1
You are copying Root from my blog.
scl 22 unlock
Philipe9_person9 said:
If you can send a SCL22 in Japan, I can do a SIM unlock.
Price : $90 + postage(Paypal)
mail : [email protected]
>>1
You are copying Root from my blog.
Click to expand...
Click to collapse
unfortunately, sending it from Romania to Japan would cost me a bit to much, so, if there is an other way you can help me, i am listening...
Philipe9_person9 said:
If you can send a SCL22 in Japan, I can do a SIM unlock.
Price : $90 + postage(Paypal)
mail : [email protected]
>>1
You are copying Root from my blog.
Click to expand...
Click to collapse
Yep sending it to japan from srilanka is very diffcult. Can you guide us through email or skype to unlock it
Sent from my SCL22 using xda app-developers app
beast08 said:
i tried this method before, flashing the SuperSU v1.86 to my phone, but everytime im opening the app, it saying su binary need to update, abd the phone will reboot to CWM recovery, and when i checked it will Root Checker, it says the phone is not properly rooted.
Click to expand...
Click to collapse
I installed the CWM. but i can't go to the CWM recovery mode. What can be the reason ?
Thought I'll create a thread for developers on LG G Pad 7.0/8.0/10.1
I'll try to keep it updated as best as I can. If I forget/get to busy, PM me and tell me what to change
Help Wanted:
If you own a LG G Pad 8.0/10.1, mind doing the following things? It'll help with kernel development/porting CM11/other ROMs
Dump partition list/info : instructions
Dump /system/build.prop
Possibly need root for stuff below
Dump aboot, boot and recovery partition : need partition list first before posting instructions. probably instructions below will continue to work
Code:
dd if=/dev/block/platform/msm_sdcc.1/by-name/aboot of=/sdcard/aboot.img
dd if=/dev/block/platform/msm_sdcc.1/by-name/boot of=/sdcard/boot.img
dd if=/dev/block/platform/msm_sdcc.1/by-name/recovery of=/sdcard/recovery.img
LG G Pad 7.0
Model Name: v400
Released with KitKat 4.4.?
Kernel Source:
https://www.lg.com/global/support/opensource/opensourceList?types=ALL&search=v400
Root:
Towelroot works
Loki no longer works, can't bypass the locked bootloader to boot custom ROMs/kernels/recovery
Mode Name: v410 (LTE AT&T version)
Root: purpledrake works
LG G Pad 8.0
Unknown device.... not released yet?
LG G Pad 10.1
Model Name: v700, v700n (korean model?)
Released with KitKat 4.4.?
Kernel Source:
https://www.lg.com/global/support/opensource/opensourceList?types=ALL&search=v700
Root:
Towelroot works
paperWastage said:
Thought I'll create a thread for developers on LG G Pad 7.0/8.0/10.1
I'll try to keep it updated as best as I can. If I forget/get to busy, PM me and tell me what to change
Help Wanted:
If you own a LG G Pad 7.0/8.0/10.1, mind doing the following things? It'll help with kernel development/porting CM11/other ROMs
Dump partition list/info : instructions
Dump /system/build.prop
Possibly need root for stuff below
Dump aboot, boot and recovery partition : need partition list first before posting instructions. probably instructions below will continue to work
Code:
dd if=/dev/block/platform/msm_sdcc.1/by-name/aboot of=/sdcard/aboot.img
dd if=/dev/block/platform/msm_sdcc.1/by-name/boot of=/sdcard/boot.img
dd if=/dev/block/platform/msm_sdcc.1/by-name/recovery of=/sdcard/recovery.img
Click to expand...
Click to collapse
Hi, I own a G pad 7.0. It seems that I am the only one in the world I'm gonna try to help a little:
1. Dump partition:
-lrwxrwxrwx root root 1970-03-05 03:01 DDR -> /dev/block/mmcblk0p25
lrwxrwxrwx root root 1970-03-05 03:01 aboot -> /dev/block/mmcblk0p6
lrwxrwxrwx root root 1970-03-05 03:01 abootb -> /dev/block/mmcblk0p9
lrwxrwxrwx root root 1970-03-05 03:01 boot -> /dev/block/mmcblk0p17
lrwxrwxrwx root root 1970-03-05 03:01 cache -> /dev/block/mmcblk0p33
lrwxrwxrwx root root 1970-03-05 03:01 cust -> /dev/block/mmcblk0p31
lrwxrwxrwx root root 1970-03-05 03:01 drm -> /dev/block/mmcblk0p26
lrwxrwxrwx root root 1970-03-05 03:01 eksst -> /dev/block/mmcblk0p10
lrwxrwxrwx root root 1970-03-05 03:01 encrypt -> /dev/block/mmcblk0p23
lrwxrwxrwx root root 1970-03-05 03:01 factory -> /dev/block/mmcblk0p28
lrwxrwxrwx root root 1970-03-05 03:01 fota -> /dev/block/mmcblk0p29
lrwxrwxrwx root root 1970-03-05 03:01 fsc -> /dev/block/mmcblk0p20
lrwxrwxrwx root root 1970-03-05 03:01 fsg -> /dev/block/mmcblk0p19
lrwxrwxrwx root root 1970-03-05 03:01 grow -> /dev/block/mmcblk0p35
lrwxrwxrwx root root 1970-03-05 03:01 laf -> /dev/block/mmcblk0p16
lrwxrwxrwx root root 1970-03-05 03:01 misc -> /dev/block/mmcblk0p14
lrwxrwxrwx root root 1970-03-05 03:01 modem -> /dev/block/mmcblk0p1
lrwxrwxrwx root root 1970-03-05 03:01 modemst1 -> /dev/block/mmcblk0p12
lrwxrwxrwx root root 1970-03-05 03:01 modemst2 -> /dev/block/mmcblk0p13
lrwxrwxrwx root root 1970-03-05 03:01 mpt -> /dev/block/mmcblk0p30
lrwxrwxrwx root root 1970-03-05 03:01 pad -> /dev/block/mmcblk0p11
lrwxrwxrwx root root 1970-03-05 03:01 persist -> /dev/block/mmcblk0p15
lrwxrwxrwx root root 1970-03-05 03:01 rct -> /dev/block/mmcblk0p24
lrwxrwxrwx root root 1970-03-05 03:01 recovery -> /dev/block/mmcblk0p18
lrwxrwxrwx root root 1970-03-05 03:01 rpm -> /dev/block/mmcblk0p3
lrwxrwxrwx root root 1970-03-05 03:01 rpmb -> /dev/block/mmcblk0p7
lrwxrwxrwx root root 1970-03-05 03:01 sbl1 -> /dev/block/mmcblk0p2
lrwxrwxrwx root root 1970-03-05 03:01 sbl1b -> /dev/block/mmcblk0p22
lrwxrwxrwx root root 1970-03-05 03:01 sdi -> /dev/block/mmcblk0p5
lrwxrwxrwx root root 1970-03-05 03:01 sns -> /dev/block/mmcblk0p27
lrwxrwxrwx root root 1970-03-05 03:01 ssd -> /dev/block/mmcblk0p21
lrwxrwxrwx root root 1970-03-05 03:01 system -> /dev/block/mmcblk0p32
lrwxrwxrwx root root 1970-03-05 03:01 tz -> /dev/block/mmcblk0p4
lrwxrwxrwx root root 1970-03-05 03:01 tzb -> /dev/block/mmcblk0p8
lrwxrwxrwx root root 1970-03-05 03:01 userdata -> /dev/block/mmcblk0p34
- Dump build.prop, boot, aboot and recovery:
http://www37.zippyshare.com/v/4146966/file.html
http://www37.zippyshare.com/v/66268524/file.html
http://www37.zippyshare.com/v/51126864/file.html
http://www37.zippyshare.com/v/44186789/file.html
http://www37.zippyshare.com/v/85458029/file.html
I think for now nothing can be done with it (there is no recovery yet). I hope something can be done.
Hammerhand.17 said:
Hi, I own a G pad 7.0. It seems that I am the only one in the world I'm gonna try to help a little:
1. Dump partition:
-lrwxrwxrwx root root 1970-03-05 03:01 DDR -> /dev/block/mmcblk0p25
lrwxrwxrwx root root 1970-03-05 03:01 aboot -> /dev/block/mmcblk0p6
lrwxrwxrwx root root 1970-03-05 03:01 abootb -> /dev/block/mmcblk0p9
lrwxrwxrwx root root 1970-03-05 03:01 boot -> /dev/block/mmcblk0p17
lrwxrwxrwx root root 1970-03-05 03:01 cache -> /dev/block/mmcblk0p33
lrwxrwxrwx root root 1970-03-05 03:01 cust -> /dev/block/mmcblk0p31
lrwxrwxrwx root root 1970-03-05 03:01 drm -> /dev/block/mmcblk0p26
lrwxrwxrwx root root 1970-03-05 03:01 eksst -> /dev/block/mmcblk0p10
lrwxrwxrwx root root 1970-03-05 03:01 encrypt -> /dev/block/mmcblk0p23
lrwxrwxrwx root root 1970-03-05 03:01 factory -> /dev/block/mmcblk0p28
lrwxrwxrwx root root 1970-03-05 03:01 fota -> /dev/block/mmcblk0p29
lrwxrwxrwx root root 1970-03-05 03:01 fsc -> /dev/block/mmcblk0p20
lrwxrwxrwx root root 1970-03-05 03:01 fsg -> /dev/block/mmcblk0p19
lrwxrwxrwx root root 1970-03-05 03:01 grow -> /dev/block/mmcblk0p35
lrwxrwxrwx root root 1970-03-05 03:01 laf -> /dev/block/mmcblk0p16
lrwxrwxrwx root root 1970-03-05 03:01 misc -> /dev/block/mmcblk0p14
lrwxrwxrwx root root 1970-03-05 03:01 modem -> /dev/block/mmcblk0p1
lrwxrwxrwx root root 1970-03-05 03:01 modemst1 -> /dev/block/mmcblk0p12
lrwxrwxrwx root root 1970-03-05 03:01 modemst2 -> /dev/block/mmcblk0p13
lrwxrwxrwx root root 1970-03-05 03:01 mpt -> /dev/block/mmcblk0p30
lrwxrwxrwx root root 1970-03-05 03:01 pad -> /dev/block/mmcblk0p11
lrwxrwxrwx root root 1970-03-05 03:01 persist -> /dev/block/mmcblk0p15
lrwxrwxrwx root root 1970-03-05 03:01 rct -> /dev/block/mmcblk0p24
lrwxrwxrwx root root 1970-03-05 03:01 recovery -> /dev/block/mmcblk0p18
lrwxrwxrwx root root 1970-03-05 03:01 rpm -> /dev/block/mmcblk0p3
lrwxrwxrwx root root 1970-03-05 03:01 rpmb -> /dev/block/mmcblk0p7
lrwxrwxrwx root root 1970-03-05 03:01 sbl1 -> /dev/block/mmcblk0p2
lrwxrwxrwx root root 1970-03-05 03:01 sbl1b -> /dev/block/mmcblk0p22
lrwxrwxrwx root root 1970-03-05 03:01 sdi -> /dev/block/mmcblk0p5
lrwxrwxrwx root root 1970-03-05 03:01 sns -> /dev/block/mmcblk0p27
lrwxrwxrwx root root 1970-03-05 03:01 ssd -> /dev/block/mmcblk0p21
lrwxrwxrwx root root 1970-03-05 03:01 system -> /dev/block/mmcblk0p32
lrwxrwxrwx root root 1970-03-05 03:01 tz -> /dev/block/mmcblk0p4
lrwxrwxrwx root root 1970-03-05 03:01 tzb -> /dev/block/mmcblk0p8
lrwxrwxrwx root root 1970-03-05 03:01 userdata -> /dev/block/mmcblk0p34
- Dump build.prop, boot, aboot and recovery:
http://www37.zippyshare.com/v/4146966/file.html
http://www37.zippyshare.com/v/66268524/file.html
http://www37.zippyshare.com/v/51126864/file.html
http://www37.zippyshare.com/v/44186789/file.html
http://www37.zippyshare.com/v/85458029/file.html
I think for now nothing can be done with it (there is no recovery yet). I hope something can be done.
Click to expand...
Click to collapse
thanks for this.
@icedmayhem also provided similar files over PM, forgot to post updates here...
anyways, it looks like this device has the patched aboot source code.
loki won't work anymore (loki provides a way for us to bypass the locked bootloader to load non-stock recovery/kernels. This means there isn't an easy way to boot a custom recovery(TWRP) or custom ROM.
Can you check if you can unlock the bootloader? Don't know if LG provides a process to do this easily (for GPE / non-GPE devices)
strings aboot.img | fgrep overlap
The erase group overlaps the max requested for erase
kernel/ramdisk addresses overlap with aboot addresses.
Device tree addresses overlap with aboot addresses.
Boot image buffer address overlaps with aboot addresses.
Signature read buffer address overlaps with aboot addresses.
Click to expand...
Click to collapse
I wish I now how to do it, but I have no idea of how to do this
FYI I was able to successfully root the G Pad 7.0 At&t version using purpledrake. LG-V410
idelgado782 said:
FYI I was able to successfully root the G Pad 7.0 At&t version using purpledrake. LG-V410
Click to expand...
Click to collapse
Link? Or just any of them?
Thxfor the info looking for it now.
Impala126 said:
Link? Or just any of them?
Thxfor the info looking for it now.
Click to expand...
Click to collapse
Here's the link to the purpledrake thread. Once you download and install on your computer make sure the gpad USB mode is on ptp mode.
http://forum.xda-developers.com/showthread.php?p=54254055
No matter what, I can never stay away from android for long.
idelgado782 said:
Here's the link to the purpledrake thread. Once you download and install on your computer make sure the gpad USB mode is on ptp mode.
http://forum.xda-developers.com/showthread.php?p=54254055
No matter what, I can never stay away from android for long.
Click to expand...
Click to collapse
Yup worked like a champ. Turned on air plane mode, then usb debugging and then ptp. But I had to go to a term win on win7 and run bat file from there. wouldn't run with admin rights from windows explore.
idelgado782 said:
FYI I was able to successfully root the G Pad 7.0 At&t version using purpledrake. LG-V410
Click to expand...
Click to collapse
for your G Pad 7.0 AT&T LTE version, mind posting the same items that Hammerhand.17 provided (for the G Pad 7.0)?
more info the better, just easier for the next developer to try to help out
paperWastage said:
LG G Pad 7.0
Model Name: v400
Released with KitKat 4.4.?
Root:
Towelroot works
Click to expand...
Click to collapse
It works also with a normal V400? I mean with NO at&t version.
(the site is towelroot.com, right?)
Yes, I have root in my normal V400 with no problem.
Hammerhand.17 said:
Yes, I have root in my normal V400 with no problem.
Click to expand...
Click to collapse
Thank you
Hammerhand.17 said:
Yes, I have root in my normal V400 with no problem.
Click to expand...
Click to collapse
One more question, it will work for sure on 4.4.2?
Has anyone tried or been successful pulling a factory image file for the LG V410 which is the AT&T G Pad 7.0? I tried the other day but there was not an image on their servers at that time
Giammysz said:
One more question, it will work for sure on 4.4.2?
Click to expand...
Click to collapse
Yes, 4.4.2 is the version of my tablet.
Giammysz said:
One more question, it will work for sure on 4.4.2?
Click to expand...
Click to collapse
Yes! Even if you have already did the OTA incremental update ..... You will need to install a SU manager though like Super SU etc after rooting with Towel root...
Hammerhand.17 said:
Yes, 4.4.2 is the version of my tablet.
Click to expand...
Click to collapse
Anthonol said:
Yes! Even if you have already did the OTA incremental update ..... You will need to install a SU manager though like Super SU etc after rooting with Towel root...
Click to expand...
Click to collapse
Thank you all
I successfully rooted my tab, it's really simple with towelroot! Install, tap and ready!
help my CWM for SM G360H
courier72 said:
help my CWM for SM G360H
Click to expand...
Click to collapse
attach your stock boot.img and stock recovery.img and I will try to help.
y300-0100 said:
attach your stock boot.img and stock recovery.img and i will try to help.
Click to expand...
Click to collapse
View attachment boot.img View attachment recovery.img
twrp recovery test version
try this recovery. if not working i made stock recovery flashable via odin.
sources are here for you to check out (partitions , names):
https://github.com/Y300-0100/twrp_samsung_core33gxx
recovery.tar.md5 not work CWM for Samsung SM G360H Galaxy Core Prime
hanyyyy said:
recovery.tar.md5 not work CWM for Samsung SM G360H Galaxy Core Prime
Click to expand...
Click to collapse
Its stock recovery. Just made for odin.
did you tried twrp recovery? .
Y300-0100 said:
Its stock recovery. Just made for odin.
did you tried twrp recovery? .
Click to expand...
Click to collapse
i tried twrp recovery to by Odin
not work to when i git in recovery mod its gif me boot log and never get in recovery mod at all
hanyyyy said:
recovery.tar.md5 not work CWM for Samsung SM G360H Galaxy Core Prime
Click to expand...
Click to collapse
Y300-0100
Maybe more, need other files? Can I help?
courier72 said:
Y300-0100
Maybe more, need other files? Can I help?
Click to expand...
Click to collapse
Full partition table by name and block number.
what not working little more details like black screen or stuck in splash screen etc.
logcat if possible.
"Not working " answer doesn't mean anything for me.
It's like " my blender is not working. Any solution?
:.
Y300-0100 said:
Full partition table by name and block number.
:.
Click to expand...
Click to collapse
how to do it?
Y300-0100 said:
what not working little more details like black screen or stuck in splash screen etc.
Click to expand...
Click to collapse
stuck in splash screen
courier72 said:
how to do it?
Click to expand...
Click to collapse
for my device command is this:
Code:
ls -al /dev/block/platform/sprd-sdhci.3/by-name
but for your you should check this for your device "sprd-sdhci.3"
Just check your fstab. Command is same as for G355HN
Code:
1|[email protected]:/ $ ls -al /dev/block/platform/sprd-sdhci.3/by-name
lrwxrwxrwx root root 2014-12-17 11:33 CSC -> /dev/block/mmcblk0p19
lrwxrwxrwx root root 2014-12-17 11:33 FIXNV1 -> /dev/block/mmcblk0p1
lrwxrwxrwx root root 2014-12-17 11:33 FIXNV2 -> /dev/block/mmcblk0p2
lrwxrwxrwx root root 2014-12-17 11:33 FOTA_SIG -> /dev/block/mmcblk0p9
lrwxrwxrwx root root 2014-12-17 11:33 HIDDEN -> /dev/block/mmcblk0p21
lrwxrwxrwx root root 2014-12-17 11:33 KERNEL -> /dev/block/mmcblk0p17
lrwxrwxrwx root root 2014-12-17 11:33 MODEM -> /dev/block/mmcblk0p7
lrwxrwxrwx root root 2014-12-17 11:33 MODEM_BACKUP -> /dev/block/mmcblk0p8
lrwxrwxrwx root root 2014-12-17 11:33 OTA -> /dev/block/mmcblk0p10
lrwxrwxrwx root root 2014-12-17 11:33 Odin_reserved -> /dev/block/mmcblk0p16
lrwxrwxrwx root root 2014-12-17 11:33 PARAM -> /dev/block/mmcblk0p13
lrwxrwxrwx root root 2014-12-17 11:33 RECOVERY -> /dev/block/mmcblk0p18lrwxrwxrwx root root 2014-12-17 11:33 RUNTIMENV1 -> /dev/block/mmcblk0p11
lrwxrwxrwx root root 2014-12-17 11:33 RUNTIMENV2 -> /dev/block/mmcblk0p12
lrwxrwxrwx root root 2014-12-17 11:33 SBL1 -> /dev/block/mmcblk0p3
lrwxrwxrwx root root 2014-12-17 11:33 SBL2 -> /dev/block/mmcblk0p4
lrwxrwxrwx root root 2014-12-17 11:33 WDSP -> /dev/block/mmcblk0p5
lrwxrwxrwx root root 2014-12-17 11:33 WDSP_BACKUP -> /dev/block/mmcblk0p6
lrwxrwxrwx root root 2014-12-17 11:33 efs -> /dev/block/mmcblk0p14
lrwxrwxrwx root root 2014-12-17 11:33 fixnv1 -> /dev/block/platform/sprd-sdhci.3/by-name/FIXNV2
lrwxrwxrwx root root 2014-12-17 11:33 fixnv2 -> /dev/block/platform/sprd-sdhci.3/by-name/FIXNV1
lrwxrwxrwx root root 2014-12-17 11:33 prodnv -> /dev/block/mmcblk0p15
lrwxrwxrwx root root 2014-12-17 11:33 runtimenv1 -> /dev/block/platform/sprd-sdhci.3/by-name/RUNTIMENV1
lrwxrwxrwx root root 2014-12-17 11:33 runtimenv2 -> /dev/block/platform/sprd-sdhci.3/by-name/RUNTIMENV2
lrwxrwxrwx root root 2014-12-17 11:33 system -> /dev/block/mmcblk0p20
lrwxrwxrwx root root 2014-12-17 11:33 userdata -> /dev/block/mmcblk0p22
Y300-0100 said:
Just check your fstab. Command is same as for G355HN
Click to expand...
Click to collapse
Is not entirely clear. To do this, you need a computer and Linux?
courier72 said:
Is not entirely clear. To do this, you need a computer and Linux?
Click to expand...
Click to collapse
Just install android terminal.( from play store ) Command work's with non roted phones also .
and you shoud get this:
.
Y300-0100 said:
Just install android terminal.
Click to expand...
Click to collapse
But I do not understand what to do next
courier72 said:
But I do not understand what to do next
Click to expand...
Click to collapse
Oopen terminal, type command from above and hit enter...
k/platform/sprd-sdhci.3/by-name <
lrwxrwxrwx root root 2015-03-02 22:43 CSC -> /dev/block/mmcblk0p22
lrwxrwxrwx root root 2015-03-02 22:43 FOTA_SIG -> /dev/block/mmcblk0p11
lrwxrwxrwx root root 2015-03-02 22:43 HIDDEN -> /dev/block/mmcblk0p24
lrwxrwxrwx root root 2015-03-02 22:43 KERNEL -> /dev/block/mmcblk0p20
lrwxrwxrwx root root 2015-03-02 22:43 MODEM -> /dev/block/mmcblk0p8
lrwxrwxrwx root root 2015-03-02 22:43 MODEM2 -> /dev/block/mmcblk0p9
lrwxrwxrwx root root 2015-03-02 22:43 PARAM -> /dev/block/mmcblk0p16
lrwxrwxrwx root root 2015-03-02 22:43 RECOVERY -> /dev/block/mmcblk0p21
lrwxrwxrwx root root 2015-03-02 22:43 RESERVED2 -> /dev/block/mmcblk0p19
lrwxrwxrwx root root 2015-03-02 22:43 SBOOT -> /dev/block/mmcblk0p1
lrwxrwxrwx root root 2015-03-02 22:43 SBOOT2 -> /dev/block/mmcblk0p2
lrwxrwxrwx root root 2015-03-02 22:43 TDDSP -> /dev/block/mmcblk0p10
lrwxrwxrwx root root 2015-03-02 22:43 WDSP -> /dev/block/mmcblk0p7
lrwxrwxrwx root root 2015-03-02 22:43 efs -> /dev/block/mmcblk0p17
lrwxrwxrwx root root 2015-03-02 22:43 prodnv -> /dev/block/mmcblk0p18
lrwxrwxrwx root root 2015-03-02 22:43 system -> /dev/block/mmcblk0p23
lrwxrwxrwx root root 2015-03-02 22:43 tdfixnv1 -> /dev/block/mmcblk0p5
lrwxrwxrwx root root 2015-03-02 22:43 tdfixnv2 -> /dev/block/mmcblk0p6
lrwxrwxrwx root root 2015-03-02 22:43 tdruntimenv1 -> /dev/block/mmcblk0p14
lrwxrwxrwx root root 2015-03-02 22:43 tdruntimenv2 -> /dev/block/mmcblk0p15
lrwxrwxrwx root root 2015-03-02 22:43 userdata -> /dev/block/mmcblk0p25
lrwxrwxrwx root root 2015-03-02 22:43 wfixnv1 -> /dev/block/mmcblk0p3
lrwxrwxrwx root root 2015-03-02 22:43 wfixnv2 -> /dev/block/mmcblk0p4
lrwxrwxrwx root root 2015-03-02 22:43 wruntimenv1 -> /dev/block/mmcblk0p12
lrwxrwxrwx root root 2015-03-02 22:43 wruntimenv2 -> /dev/block/mmcblk0p13
[email protected]:/ $
Y300-0100 said:
Full partition table by name and block number.
what not working little more details like black screen or stuck in splash screen etc.
logcat if possible.
"Not working " answer doesn't mean anything for me.
It's like " my blender is not working. Any solution?
:.
Click to expand...
Click to collapse
stuck in splash screen
and this is the Full partition table by name and block number
ਊock/platform/sprd-sdhci.3/by-name <
lrwxrwxrwx root root 2015-03-02 21:27 CSC -> /dev/block/mmcblk0p22
lrwxrwxrwx root root 2015-03-02 21:27 FOTA_SIG -> /dev/block/mmcblk0p11
lrwxrwxrwx root root 2015-03-02 21:27 HIDDEN -> /dev/block/mmcblk0p24
lrwxrwxrwx root root 2015-03-02 21:27 KERNEL -> /dev/block/mmcblk0p20
lrwxrwxrwx root root 2015-03-02 21:27 MODEM -> /dev/block/mmcblk0p8
lrwxrwxrwx root root 2015-03-02 21:27 MODEM2 -> /dev/block/mmcblk0p9
lrwxrwxrwx root root 2015-03-02 21:27 PARAM -> /dev/block/mmcblk0p16
lrwxrwxrwx root root 2015-03-02 21:27 RECOVERY -> /dev/block/mmcblk0p21
lrwxrwxrwx root root 2015-03-02 21:27 RESERVED2 -> /dev/block/mmcblk0p19
lrwxrwxrwx root root 2015-03-02 21:27 SBOOT -> /dev/block/mmcblk0p1
lrwxrwxrwx root root 2015-03-02 21:27 SBOOT2 -> /dev/block/mmcblk0p2
lrwxrwxrwx root root 2015-03-02 21:27 TDDSP -> /dev/block/mmcblk0p10
lrwxrwxrwx root root 2015-03-02 21:27 WDSP -> /dev/block/mmcblk0p7
lrwxrwxrwx root root 2015-03-02 21:27 efs -> /dev/block/mmcblk0p17
lrwxrwxrwx root root 2015-03-02 21:27 prodnv -> /dev/block/mmcblk0p18
lrwxrwxrwx root root 2015-03-02 21:27 system -> /dev/block/mmcblk0p23
lrwxrwxrwx root root 2015-03-02 21:27 tdfixnv1 -> /dev/block/mmcblk0p5
lrwxrwxrwx root root 2015-03-02 21:27 tdfixnv2 -> /dev/block/mmcblk0p6
lrwxrwxrwx root root 2015-03-02 21:27 tdruntimenv1 -> /dev/block/mmcblk0p14
lrwxrwxrwx root root 2015-03-02 21:27 tdruntimenv2 -> /dev/block/mmcblk0p15
lrwxrwxrwx root root 2015-03-02 21:27 userdata -> /dev/block/mmcblk0p25
lrwxrwxrwx root root 2015-03-02 21:27 wfixnv1 -> /dev/block/mmcblk0p3
lrwxrwxrwx root root 2015-03-02 21:27 wfixnv2 -> /dev/block/mmcblk0p4
lrwxrwxrwx root root 2015-03-02 21:27 wruntimenv1 -> /dev/block/mmcblk0p12
lrwxrwxrwx root root 2015-03-02 21:27 wruntimenv2 -> /dev/block/mmcblk0p13
[email protected]:/ $
�
Cwm for samsung galaxy core prime
Any one can plz make cwm for core prime
twrp recovery test version
Changes I made :
https://github.com/Y300-0100/twrp_samsung_core33gxx/commit/8dde6d106ef5abf6ea52203d13091cb1b11480be
I will upload test build later
Do not use this root method for 5.1.1!! You will get a soft brick and there is no way to recover! If your on 5.0.2 and did not take the update then you can proceed to this root method.
Here is the untouched update to 5.1.1:
udpate.zip
UPDATE: 6/25
BOOST MOBILE HAS RELEASED AN UPDATE! The update is around 413MB. I pulled the update and will be updating it soon. If you are rooted do not update the phone. It could cause a brick and or unroot the device! So far I just found a new radio.img inside of it. I'll check it out later this afternoon.
Hello everyone,
I wanted to make this thread for the LG G Stylo (Boost Mobile) cause I could not find any forums or any post about this device!
Anyways if you are looking for a ROOT method for this device visit here:
Proof (picture) that the device is rooted at the bottom of this post.
LG One Click Root 1.3 (Graphic UI):
Code:
[url]http://forum.xda-developers.com/lg-g3/general/guide-root-lg-firmwares-kitkat-lollipop-t3056951[/url]
Here is the PARTITIONS from the device:
Code:
[email protected]:/ $ su
[email protected]:/ # ls -al /dev/block/bootdevice/by-name
lrwxrwxrwx root root 1970-01-04 18:18 DDR -> /dev/block/mmcblk0p23
lrwxrwxrwx root root 1970-01-04 18:18 aboot -> /dev/block/mmcblk0p5
lrwxrwxrwx root root 1970-01-04 18:18 abootbak -> /dev/block/mmcblk0p11
lrwxrwxrwx root root 1970-01-04 18:18 boot -> /dev/block/mmcblk0p18
lrwxrwxrwx root root 1970-01-04 18:18 cache -> /dev/block/mmcblk0p38
lrwxrwxrwx root root 1970-01-04 18:18 carrier -> /dev/block/mmcblk0p36
lrwxrwxrwx root root 1970-01-04 18:18 drm -> /dev/block/mmcblk0p31
lrwxrwxrwx root root 1970-01-04 18:18 eksst -> /dev/block/mmcblk0p26
lrwxrwxrwx root root 1970-01-04 18:18 encrypt -> /dev/block/mmcblk0p25
lrwxrwxrwx root root 1970-01-04 18:18 factory -> /dev/block/mmcblk0p29
lrwxrwxrwx root root 1970-01-04 18:18 fota -> /dev/block/mmcblk0p30
lrwxrwxrwx root root 1970-01-04 18:18 fsc -> /dev/block/mmcblk0p21
lrwxrwxrwx root root 1970-01-04 18:18 fsg -> /dev/block/mmcblk0p20
lrwxrwxrwx root root 1970-01-04 18:18 grow -> /dev/block/mmcblk0p40
lrwxrwxrwx root root 1970-01-04 18:18 hyp -> /dev/block/mmcblk0p3
lrwxrwxrwx root root 1970-01-04 18:18 hypbak -> /dev/block/mmcblk0p9
lrwxrwxrwx root root 1970-01-04 18:18 laf -> /dev/block/mmcblk0p17
lrwxrwxrwx root root 1970-01-04 18:18 metadata -> /dev/block/mmcblk0p14
lrwxrwxrwx root root 1970-01-04 18:18 misc -> /dev/block/mmcblk0p12
lrwxrwxrwx root root 1970-01-04 18:18 modem -> /dev/block/mmcblk0p33
lrwxrwxrwx root root 1970-01-04 18:18 modemst1 -> /dev/block/mmcblk0p15
lrwxrwxrwx root root 1970-01-04 18:18 modemst2 -> /dev/block/mmcblk0p16
lrwxrwxrwx root root 1970-01-04 18:18 mpt -> /dev/block/mmcblk0p32
lrwxrwxrwx root root 1970-01-04 18:18 pad -> /dev/block/mmcblk0p6
lrwxrwxrwx root root 1970-01-04 18:18 pad2 -> /dev/block/mmcblk0p35
lrwxrwxrwx root root 1970-01-04 18:18 persist -> /dev/block/mmcblk0p13
lrwxrwxrwx root root 1970-01-04 18:18 persistent -> /dev/block/mmcblk0p34
lrwxrwxrwx root root 1970-01-04 18:18 rct -> /dev/block/mmcblk0p27
lrwxrwxrwx root root 1970-01-04 18:18 recovery -> /dev/block/mmcblk0p19
lrwxrwxrwx root root 1970-01-04 18:18 rpm -> /dev/block/mmcblk0p4
lrwxrwxrwx root root 1970-01-04 18:18 rpmbak -> /dev/block/mmcblk0p10
lrwxrwxrwx root root 1970-01-04 18:18 sbl1 -> /dev/block/mmcblk0p1
lrwxrwxrwx root root 1970-01-04 18:18 sbl1bak -> /dev/block/mmcblk0p7
lrwxrwxrwx root root 1970-01-04 18:18 sec -> /dev/block/mmcblk0p24
lrwxrwxrwx root root 1970-01-04 18:18 sns -> /dev/block/mmcblk0p28
lrwxrwxrwx root root 1970-01-04 18:18 ssd -> /dev/block/mmcblk0p22
lrwxrwxrwx root root 1970-01-04 18:18 system -> /dev/block/mmcblk0p37
lrwxrwxrwx root root 1970-01-04 18:18 tz -> /dev/block/mmcblk0p2
lrwxrwxrwx root root 1970-01-04 18:18 tzbak -> /dev/block/mmcblk0p8
lrwxrwxrwx root root 1970-01-04 18:18 userdata -> /dev/block/mmcblk0p39
[email protected]:/ #
Here is how to get into STOCK RECOVERY:
Code:
1) Turn the device off
2) While holding the phone on, press and hold VOLUME -(DOWN) at the same time
3) When you see the LG boot logo hurry up and let go of the VOLUME -(DOWN) and hold it again for a few sec (kinda tricky)
4) Then this will get you into recovery mode
Here is how to get into DOWNLOAD MODE:
Code:
1) Turn the device off
2) While holding the VOLUME +(UP) key plug in the device into the pc
3) A screen should pop up and press the VOLUME +(UP) key until you see DOWNLOAD MODE with the progress bar
4) Done
NOTE: Pull out the battery once your done in DOWNLOAD MODE to get out of it and power the device like normal.
SYSTEM DUMP:
NOTE: These files are from 5.0.2 NOT 5.1.1!
Code:
[URL="http://www.mediafire.com/download/grau3kv5m1rbzwa/aboot.img"]aboot.img[/URL]
[URL="http://www.mediafire.com/download/f6cly93iusa83xz/boot.img"]boot.img [/URL]
[URL="http://www.mediafire.com/download/1opyd4a9fimbw8p/laf.img"]laf.img[/URL]
[URL="http://www.mediafire.com/download/qt3o5rrm4h2qo5o/recovery.img"]recovery.img[/URL]
[URL="http://www.mediafire.com/download/t7a3qq60xh2pm0c/system.zip"]system.img[/URL]
All files will be uploaded to my mediafire account!
Please make mirrors if you like.
NOTE: I am not a DEV! I will upload files to help others try to get something going for this device. I will test things as I go.
Just tried this root method on the TMO version of this and out didn't start. Curiously tried the manual method for the G3/G4 and i get a device offline when doing an ADB device list.
Sent from my LG-H631 using XDA Free mobile app
Make sure you install the right drivers. I had to install the drivers and then restart my laptop. It took me like 2-3 times to finally root the device with the Graphical UI method. On a side note I had to toggle MTP and the other one and then let the drivers install for each one. I then put the phone into charge mode and it finally rooted.
I will give it one more try tonight. I had uninstalled and re installed the LG drivers a few times. I can connect fine to my L90 and my G2. But for some reason this thing shows connected but "offline" in ADB. Toggled back and forth between MTP and PTP a few times too. No response when in download mode ekther.
Sent from my LG-H631 using XDA Free mobile app
Any luck Cahiatt on the root? My LG Flex has an issue that I have to send it back for repairs and I've been considering ordering the Stylo. Just need root though for all the stuff I like to do.
Thanks!
Haven't gone back to it yet. Ended up on other chores for the weekend.
Sent from my LG-H631 using XDA Free mobile app
Well the short answer is this worked on the TMO version also.
I don't have a long answer. For whatever reason when I tried again it just worked. There must have been something software related hanging on my desktop PC that was interfering with the port used by ADB or who knows what. I just went back, plugged the phone in and it worked. Woo Hoo!!!!
Sent from my LG-H631 using XDA Free mobile app
Can anyone with the tmobile stylo confirm the 2gb ram and 13mp cam?
Im considering this over the g4, more budget friendly.
I have a few questions.
Hows the lcd? Does it show alot of pixelation? Im hearing its pretty good for 720p.
Does it have a notification led?
I know it has lollipop but is it 5.0, 5.0.2 or 5.1?
Pretty good specs for under $300 id say.
fix-this! said:
Can anyone with the tmobile stylo confirm the 2gb ram and 13mp cam?
Im considering this over the g4, more budget friendly.
I have a few questions.
Hows the lcd? Does it show alot of pixelation? Im hearing its pretty good for 720p.
Does it have a notification led?
I know it has lollipop but is it 5.0, 5.0.2 or 5.1?
Pretty good specs for under $300 id say.
Click to expand...
Click to collapse
LCD is pretty good. I came from a G2 and don't notice any pixelation. Text and video quality is very good. It isn't as bright outdoors and doesn't have auto brightness but am pleased with it.
Camera is 13mp. Pictures seem better than my G2. Better focus.
Does have notification LED.
Running 5.0.2
It does have 2gb of RAM and performs similarly to my G2 before. WiFi and cell reception actually seem better also.
I think it is a pretty solid device for the price. I actually wish it were a little smaller but it is still relatively thin and light for the size.
Sent from my LG-H631 using XDA Free mobile app
i might pick one up today. anybody know if twrp is available so we can have a backup in case of a softbrick? hoping xda make a section for this device.
As far as TWRP no one has compiled it for this device yet. The device is pretty new so I would give it some time.
HTML:
ls -al /dev/block/bootdevice/by-name
lrwxrwxrwx root root 1970-01-01 21:24 DDR -> /dev/block/mmcblk0p23
lrwxrwxrwx root root 1970-01-01 21:24 aboot -> /dev/block/mmcblk0p5
lrwxrwxrwx root root 1970-01-01 21:24 abootbak -> /dev/block/mmcblk0p11
lrwxrwxrwx root root 1970-01-01 21:24 boot -> /dev/block/mmcblk0p18
lrwxrwxrwx root root 1970-01-01 21:24 cache -> /dev/block/mmcblk0p37
lrwxrwxrwx root root 1970-01-01 21:24 drm -> /dev/block/mmcblk0p31
lrwxrwxrwx root root 1970-01-01 21:24 eksst -> /dev/block/mmcblk0p26
lrwxrwxrwx root root 1970-01-01 21:24 encrypt -> /dev/block/mmcblk0p25
lrwxrwxrwx root root 1970-01-01 21:24 factory -> /dev/block/mmcblk0p29
lrwxrwxrwx root root 1970-01-01 21:24 fota -> /dev/block/mmcblk0p30
lrwxrwxrwx root root 1970-01-01 21:24 fsc -> /dev/block/mmcblk0p21
lrwxrwxrwx root root 1970-01-01 21:24 fsg -> /dev/block/mmcblk0p20
lrwxrwxrwx root root 1970-01-01 21:24 grow -> /dev/block/mmcblk0p39
lrwxrwxrwx root root 1970-01-01 21:24 hyp -> /dev/block/mmcblk0p3
lrwxrwxrwx root root 1970-01-01 21:24 hypbak -> /dev/block/mmcblk0p9
lrwxrwxrwx root root 1970-01-01 21:24 laf -> /dev/block/mmcblk0p17
lrwxrwxrwx root root 1970-01-01 21:24 metadata -> /dev/block/mmcblk0p14
lrwxrwxrwx root root 1970-01-01 21:24 misc -> /dev/block/mmcblk0p12
lrwxrwxrwx root root 1970-01-01 21:24 modem -> /dev/block/mmcblk0p33
lrwxrwxrwx root root 1970-01-01 21:24 modemst1 -> /dev/block/mmcblk0p15
lrwxrwxrwx root root 1970-01-01 21:24 modemst2 -> /dev/block/mmcblk0p16
lrwxrwxrwx root root 1970-01-01 21:24 mpt -> /dev/block/mmcblk0p32
lrwxrwxrwx root root 1970-01-01 21:24 pad -> /dev/block/mmcblk0p6
lrwxrwxrwx root root 1970-01-01 21:24 pad2 -> /dev/block/mmcblk0p35
lrwxrwxrwx root root 1970-01-01 21:24 persist -> /dev/block/mmcblk0p13
lrwxrwxrwx root root 1970-01-01 21:24 persistent -> /dev/block/mmcblk0p34
lrwxrwxrwx root root 1970-01-01 21:24 rct -> /dev/block/mmcblk0p27
lrwxrwxrwx root root 1970-01-01 21:24 recovery -> /dev/block/mmcblk0p19
lrwxrwxrwx root root 1970-01-01 21:24 rpm -> /dev/block/mmcblk0p4
lrwxrwxrwx root root 1970-01-01 21:24 rpmbak -> /dev/block/mmcblk0p10
lrwxrwxrwx root root 1970-01-01 21:24 sbl1 -> /dev/block/mmcblk0p1
lrwxrwxrwx root root 1970-01-01 21:24 sbl1bak -> /dev/block/mmcblk0p7
lrwxrwxrwx root root 1970-01-01 21:24 sec -> /dev/block/mmcblk0p24
lrwxrwxrwx root root 1970-01-01 21:24 sns -> /dev/block/mmcblk0p28
lrwxrwxrwx root root 1970-01-01 21:24 ssd -> /dev/block/mmcblk0p22
lrwxrwxrwx root root 1970-01-01 21:24 system -> /dev/block/mmcblk0p36
lrwxrwxrwx root root 1970-01-01 21:24 tz -> /dev/block/mmcblk0p2
lrwxrwxrwx root root 1970-01-01 21:24 tzbak -> /dev/block/mmcblk0p8
lrwxrwxrwx root root 1970-01-01 21:24 userdata -> /dev/block/mmcblk0p38
[email protected]:/ $
heres the mounts for the tmobile lg g stylo.
and heres a system dump for the tmobile variant. might help get development going.
mega link: https://mega.co.nz/#!R1VwiLiA!GJ2O1Tw-pVw2P8QEHcpM0c464Qlq6Ro8CZty0YAkNs4
I took the plunge yesterday and got the T-Mobile variant. So far, it's been pretty nice. I would ding the camera app a star, though, since it doesn't seem to offer any manual exposure controls. You can choose between standard and HDR mode, and if HDR is off, you can chose off/manual/auto flash. I'm guessing they don't want to steal the G4's thunder. That being said, it takes very nice pictures, and the autofocus is nice and fast.
This morning, I had one glitch: Google Maps and Google Play Music weren't playing any sounds, even though I could hear sound effects when I tapped the screen. I rebooted and the problem went away, and haven't had any further trouble.
I like the screen - it's nice and bright and has good contrast. Sure, it's 720p instead of qHD, but it's plenty sharp for me. The phone seems nice and snappy, and doesn't seem laggy at all. It's nice that the T-Mobile version has 2 GB RAM and 16 GB internal storage.
From what I've seen so far, the battery should hold up nicely. However, the supplied 1.2A charger seems to run a bit hot. I'll be using the 2A charger that came with my Avant instead. I did make sure to unlock the Avant before upgrading; its supplied app unlocked the phone without any hassle.
Overall, for a budget phablet, it's quite good. I had been considering a ZTE Zmax, but I'm glad I held out for the Stylo, even if I rarely use the stylus.
I'm going to have to update my signature.
The lcd is my biggest issue. Even for 720p hd its got alot of pixelation on the fonts. My moto e 2015 actually renders better. :/ i assume this is becuase its a large lcd at 5.7". Wish lg would of gave it 1080p.
Its strong points are the camera and the overall design of the device, very sleek compared to the g3 or g4. Especially the back of the phone. Little choppy performance to but i suspect this is from the 5.0.2 memory leak.
Ill test for a few days before i decide if ill keep it or not. Good budget device though.
Anyone knows if the boot loader is unlocked? I expect the MetroPCS and T-Mobile variants to have one.
fix-this! said:
HTML:
ls -al /dev/block/bootdevice/by-name
lrwxrwxrwx root root 1970-01-01 21:24 DDR -> /dev/block/mmcblk0p23
lrwxrwxrwx root root 1970-01-01 21:24 aboot -> /dev/block/mmcblk0p5
lrwxrwxrwx root root 1970-01-01 21:24 abootbak -> /dev/block/mmcblk0p11
lrwxrwxrwx root root 1970-01-01 21:24 boot -> /dev/block/mmcblk0p18
lrwxrwxrwx root root 1970-01-01 21:24 cache -> /dev/block/mmcblk0p37
lrwxrwxrwx root root 1970-01-01 21:24 drm -> /dev/block/mmcblk0p31
lrwxrwxrwx root root 1970-01-01 21:24 eksst -> /dev/block/mmcblk0p26
lrwxrwxrwx root root 1970-01-01 21:24 encrypt -> /dev/block/mmcblk0p25
lrwxrwxrwx root root 1970-01-01 21:24 factory -> /dev/block/mmcblk0p29
lrwxrwxrwx root root 1970-01-01 21:24 fota -> /dev/block/mmcblk0p30
lrwxrwxrwx root root 1970-01-01 21:24 fsc -> /dev/block/mmcblk0p21
lrwxrwxrwx root root 1970-01-01 21:24 fsg -> /dev/block/mmcblk0p20
lrwxrwxrwx root root 1970-01-01 21:24 grow -> /dev/block/mmcblk0p39
lrwxrwxrwx root root 1970-01-01 21:24 hyp -> /dev/block/mmcblk0p3
lrwxrwxrwx root root 1970-01-01 21:24 hypbak -> /dev/block/mmcblk0p9
lrwxrwxrwx root root 1970-01-01 21:24 laf -> /dev/block/mmcblk0p17
lrwxrwxrwx root root 1970-01-01 21:24 metadata -> /dev/block/mmcblk0p14
lrwxrwxrwx root root 1970-01-01 21:24 misc -> /dev/block/mmcblk0p12
lrwxrwxrwx root root 1970-01-01 21:24 modem -> /dev/block/mmcblk0p33
lrwxrwxrwx root root 1970-01-01 21:24 modemst1 -> /dev/block/mmcblk0p15
lrwxrwxrwx root root 1970-01-01 21:24 modemst2 -> /dev/block/mmcblk0p16
lrwxrwxrwx root root 1970-01-01 21:24 mpt -> /dev/block/mmcblk0p32
lrwxrwxrwx root root 1970-01-01 21:24 pad -> /dev/block/mmcblk0p6
lrwxrwxrwx root root 1970-01-01 21:24 pad2 -> /dev/block/mmcblk0p35
lrwxrwxrwx root root 1970-01-01 21:24 persist -> /dev/block/mmcblk0p13
lrwxrwxrwx root root 1970-01-01 21:24 persistent -> /dev/block/mmcblk0p34
lrwxrwxrwx root root 1970-01-01 21:24 rct -> /dev/block/mmcblk0p27
lrwxrwxrwx root root 1970-01-01 21:24 recovery -> /dev/block/mmcblk0p19
lrwxrwxrwx root root 1970-01-01 21:24 rpm -> /dev/block/mmcblk0p4
lrwxrwxrwx root root 1970-01-01 21:24 rpmbak -> /dev/block/mmcblk0p10
lrwxrwxrwx root root 1970-01-01 21:24 sbl1 -> /dev/block/mmcblk0p1
lrwxrwxrwx root root 1970-01-01 21:24 sbl1bak -> /dev/block/mmcblk0p7
lrwxrwxrwx root root 1970-01-01 21:24 sec -> /dev/block/mmcblk0p24
lrwxrwxrwx root root 1970-01-01 21:24 sns -> /dev/block/mmcblk0p28
lrwxrwxrwx root root 1970-01-01 21:24 ssd -> /dev/block/mmcblk0p22
lrwxrwxrwx root root 1970-01-01 21:24 system -> /dev/block/mmcblk0p36
lrwxrwxrwx root root 1970-01-01 21:24 tz -> /dev/block/mmcblk0p2
lrwxrwxrwx root root 1970-01-01 21:24 tzbak -> /dev/block/mmcblk0p8
lrwxrwxrwx root root 1970-01-01 21:24 userdata -> /dev/block/mmcblk0p38
[email protected]:/ $
heres the mounts for the tmobile lg g stylo.
Click to expand...
Click to collapse
Could I also get the output of adb shell cat proc/partitions and a backup of the recovery image. I'm going to unpack and repack the image which will cause the signature to change. If the bootloader is unlocked the image will still boot even after the signature has been modified.
Great to see more people on board. I'm almost positive the boot loader is locked by default. I tried to erase my laf and see if it would boot into fast boot but that was a no go. Let me know if anyone can access fast boot?
androidguy1991 said:
Great to see more people on board. I'm almost positive the boot loader is locked by default. I tried to erase my laf and see if it would boot into fast boot but that was a no go. Let me know if anyone can access fast boot?
Click to expand...
Click to collapse
Sounds like the same thing on the G4. What exactly happens after LAF is removed? I'm surprised the Send_Command root method worked for this device as it didn't for the G4.
When I removed laf it goes into the first download screen and says hold volume up to get into download mode or something like that. So I keep holding it and it does nothing. I tried to throw in some fast boot comments while its stuck on that screen and it does nothing. One thing I did find interesting is when you boot into stock recovery there is an option to reboot into bootloader but it just reboots the phone like normal.
I am currently running CM 12.1
(Used CM13 with RazorKernel For some days which had a bootlogo)
Here's the partition info of our device
Code:
lrwxrwxrwx root root 2016-01-11 17:56 DDR -> /dev/block/mmcblk0p19
lrwxrwxrwx root root 2016-01-11 17:56 aboot -> /dev/block/mmcblk0p4
lrwxrwxrwx root root 2016-01-11 17:56 abootbak -> /dev/block/mmcblk0p5
lrwxrwxrwx root root 2016-01-11 17:56 boot -> /dev/block/mmcblk0p22
lrwxrwxrwx root root 2016-01-11 17:56 cache -> /dev/block/mmcblk0p24
lrwxrwxrwx root root 2016-01-11 17:56 config -> /dev/block/mmcblk0p28
lrwxrwxrwx root root 2016-01-11 17:56 fsc -> /dev/block/mmcblk0p16
lrwxrwxrwx root root 2016-01-11 17:56 fsg -> /dev/block/mmcblk0p20
lrwxrwxrwx root root 2016-01-11 17:56 hyp -> /dev/block/mmcblk0p10
lrwxrwxrwx root root 2016-01-11 17:56 hypbak -> /dev/block/mmcblk0p11
lrwxrwxrwx root root 2016-01-11 17:56 keystore -> /dev/block/mmcblk0p27
lrwxrwxrwx root root 2016-01-11 17:56 misc -> /dev/block/mmcblk0p15
lrwxrwxrwx root root 2016-01-11 17:56 modem -> /dev/block/mmcblk0p1
lrwxrwxrwx root root 2016-01-11 17:56 modemst1 -> /dev/block/mmcblk0p13
lrwxrwxrwx root root 2016-01-11 17:56 modemst2 -> /dev/block/mmcblk0p14
lrwxrwxrwx root root 2016-01-11 17:56 oem -> /dev/block/mmcblk0p29
lrwxrwxrwx root root 2016-01-11 17:56 pad -> /dev/block/mmcblk0p12
lrwxrwxrwx root root 2016-01-11 17:56 persist -> /dev/block/mmcblk0p25
lrwxrwxrwx root root 2016-01-11 17:56 recovery -> /dev/block/mmcblk0p26
lrwxrwxrwx root root 2016-01-11 17:56 rpm -> /dev/block/mmcblk0p6
lrwxrwxrwx root root 2016-01-11 17:56 rpmbak -> /dev/block/mmcblk0p7
lrwxrwxrwx root root 2016-01-11 17:56 sbl1 -> /dev/block/mmcblk0p2
lrwxrwxrwx root root 2016-01-11 17:56 sbl1bak -> /dev/block/mmcblk0p3
lrwxrwxrwx root root 2016-01-11 17:56 sec -> /dev/block/mmcblk0p21
[COLOR="Red"]lrwxrwxrwx root root 2016-01-11 17:56 splash -> /dev/block/mmcblk0p18[/COLOR]
lrwxrwxrwx root root 2016-01-11 17:56 ssd -> /dev/block/mmcblk0p17
lrwxrwxrwx root root 2016-01-11 17:56 system -> /dev/block/mmcblk0p23
lrwxrwxrwx root root 2016-01-11 17:56 tz -> /dev/block/mmcblk0p8
lrwxrwxrwx root root 2016-01-11 17:56 tzbak -> /dev/block/mmcblk0p9
lrwxrwxrwx root root 2016-01-11 17:56 userdata -> /dev/block/mmcblk0p30
As you can see "mmcblk0p18" belongs to splash partiton.
I was successful in dumping splash.img on sdcard with adb shell as:
Code:
dd if=/dev/block/mmcblkp018 of=/storage/sdcard1/splash.img
But now what?
How to edit it?
I've searched for many hours but came up with mediatek or HTC guides which is pretty annoying -_-
Tools I've tried so far--> Android Kitchen, Kernel Kitchen, Logo Builder, nbimg tool.
Please help me through this.. I desperately want to make a splash image for my device.
noobpremium said:
I am currently running CM 12.1
(Used CM13 with RazorKernel For some days which had a bootlogo)
Here's the partition info of our device
Code:
lrwxrwxrwx root root 2016-01-11 17:56 DDR -> /dev/block/mmcblk0p19
lrwxrwxrwx root root 2016-01-11 17:56 aboot -> /dev/block/mmcblk0p4
lrwxrwxrwx root root 2016-01-11 17:56 abootbak -> /dev/block/mmcblk0p5
lrwxrwxrwx root root 2016-01-11 17:56 boot -> /dev/block/mmcblk0p22
lrwxrwxrwx root root 2016-01-11 17:56 cache -> /dev/block/mmcblk0p24
lrwxrwxrwx root root 2016-01-11 17:56 config -> /dev/block/mmcblk0p28
lrwxrwxrwx root root 2016-01-11 17:56 fsc -> /dev/block/mmcblk0p16
lrwxrwxrwx root root 2016-01-11 17:56 fsg -> /dev/block/mmcblk0p20
lrwxrwxrwx root root 2016-01-11 17:56 hyp -> /dev/block/mmcblk0p10
lrwxrwxrwx root root 2016-01-11 17:56 hypbak -> /dev/block/mmcblk0p11
lrwxrwxrwx root root 2016-01-11 17:56 keystore -> /dev/block/mmcblk0p27
lrwxrwxrwx root root 2016-01-11 17:56 misc -> /dev/block/mmcblk0p15
lrwxrwxrwx root root 2016-01-11 17:56 modem -> /dev/block/mmcblk0p1
lrwxrwxrwx root root 2016-01-11 17:56 modemst1 -> /dev/block/mmcblk0p13
lrwxrwxrwx root root 2016-01-11 17:56 modemst2 -> /dev/block/mmcblk0p14
lrwxrwxrwx root root 2016-01-11 17:56 oem -> /dev/block/mmcblk0p29
lrwxrwxrwx root root 2016-01-11 17:56 pad -> /dev/block/mmcblk0p12
lrwxrwxrwx root root 2016-01-11 17:56 persist -> /dev/block/mmcblk0p25
lrwxrwxrwx root root 2016-01-11 17:56 recovery -> /dev/block/mmcblk0p26
lrwxrwxrwx root root 2016-01-11 17:56 rpm -> /dev/block/mmcblk0p6
lrwxrwxrwx root root 2016-01-11 17:56 rpmbak -> /dev/block/mmcblk0p7
lrwxrwxrwx root root 2016-01-11 17:56 sbl1 -> /dev/block/mmcblk0p2
lrwxrwxrwx root root 2016-01-11 17:56 sbl1bak -> /dev/block/mmcblk0p3
lrwxrwxrwx root root 2016-01-11 17:56 sec -> /dev/block/mmcblk0p21
[COLOR="Red"]lrwxrwxrwx root root 2016-01-11 17:56 splash -> /dev/block/mmcblk0p18[/COLOR]
lrwxrwxrwx root root 2016-01-11 17:56 ssd -> /dev/block/mmcblk0p17
lrwxrwxrwx root root 2016-01-11 17:56 system -> /dev/block/mmcblk0p23
lrwxrwxrwx root root 2016-01-11 17:56 tz -> /dev/block/mmcblk0p8
lrwxrwxrwx root root 2016-01-11 17:56 tzbak -> /dev/block/mmcblk0p9
lrwxrwxrwx root root 2016-01-11 17:56 userdata -> /dev/block/mmcblk0p30
As you can see "mmcblk0p18" belongs to splash partiton.
I was successful in dumping splash.img on sdcard with adb shell as:
Code:
dd if=/dev/block/mmcblkp018 of=/storage/sdcard1/splash.img
But now what?
How to edit it?
I've searched for many hours but came up with mediatek or HTC guides which is pretty annoying -_-
Tools I've tried so far--> Android Kitchen, Kernel Kitchen, Logo Builder, nbimg tool.
Please help me through this.. I desperately want to make a splash image for my device.
Click to expand...
Click to collapse
Which splash? Mi Logo splash? Tux Logo splash? Razor kernel splash I assume? If its Tux Logo splash, it is needed for some LCD types to work. For Mi Logo / Razor kernel splash I think, you must edit in kernel level and compile the kernel yourself.
I want to modify bootsplash too but im soo noob to do that,
Never tried by myself, as your reference, try it at your own risk: https://www.codeaurora.org/cgit/quic/la/device/qcom/common/tree/display/logo?h=LA.BR.1.2.7_rb1.1
nick37332001 said:
Which splash? Mi Logo splash? Tux Logo splash? Razor kernel splash I assume? If its Tux Logo splash, it is needed for some LCD types to work. For Mi Logo / Razor kernel splash I think, you must edit in kernel level and compile the kernel yourself.
Click to expand...
Click to collapse
Damn I dont have time to download sources and compile the kernel myself
Any other method to edit?
And yes its razor kernel splash (which is that blue thing ) or The Mi logo splash which appears before bootanimation.
But the thing is razor kernel had its splash and Kuma's cm12.1 dont!
Just that default "Linux's Penguin" appears in corner :3
Hope you got what I wanted to say
ketut.kumajaya said:
Never tried by myself, as your reference, try it at your own risk: https://www.codeaurora.org/cgit/quic/la/device/qcom/common/tree/display/logo?h=LA.BR.1.2.7_rb1.1
Click to expand...
Click to collapse
Okay Thanks for the reply. That's from kernel source I assume.
However I'll see to it
ketut.kumajaya said:
Never tried by myself, as your reference, try it at your own risk: https://www.codeaurora.org/cgit/quic/la/device/qcom/common/tree/display/logo?h=LA.BR.1.2.7_rb1.1
Click to expand...
Click to collapse
Too bad but I romoved ubuntu from pc just 2 dyas ago.. one more reason to regret -_-
maybe nick can do it :3
BTW any other method to do it? Like using cygwin?
noobpremium said:
Okay Thanks for the reply. That's from kernel source I assume.
However I'll see to it
Click to expand...
Click to collapse
Have you tried the latest version? I think kiran removed the logo
nick37332001 said:
Have you tried the latest version? I think kiran removed the logo
Click to expand...
Click to collapse
I dont want to flash CM13 now. I'm on 12.1.
Leave razorkernel. I'm not talking about 'only' razorkernel. If he is able to do so others should be too and for defferent kernel.
I've seen threads for bootlogo for motoX etc running lollipop
Anyways, do you have ubuntu? so you can run the script Kuma gave us link of.
noobpremium said:
I dont want to flash CM13 now. I'm on 12.1.
Leave razorkernel. I'm not talking about 'only' razorkernel. If he is able to do so others should be too and for defferent kernel.
I've seen threads for bootlogo for motoX etc running lollipop
Anyways, do you have ubuntu? so you can run the script Kuma gave us link of.
Click to expand...
Click to collapse
the script is python so you should be able to run it on windows.
nick37332001 said:
the script is python so you should be able to run it on windows.
Click to expand...
Click to collapse
Okay I'm nooob man. I didn't know that i can run it on windows, but I'll see to it.
Sent from my 2014818 using Tapatalk
nick37332001 said:
the script is python so you should be able to run it on windows.
Click to expand...
Click to collapse
Okay now here I am, successfully running that script on windows.
It created splash.img successfully but it was too small in size, around 65 KB :|
The one that i dumped was exactly 10MB.
Then also I flashed it but what I got was dessorted Mi logo and the same Penguin.
Now what? I'll see if I can decompile splash.img that I dumped using PIL.
Any help will be appreciated
Sent from my 2014818 using Tapatalk
You can give a try with Android Image Kitchen.....
Lennoard said:
You can give a try with Android Image Kitchen.....
Click to expand...
Click to collapse
Okay I'll see
Sent from my Xiaomi Redmi 2
noobpremium said:
Okay I'll see
Sent from my Xiaomi Redmi 2
Click to expand...
Click to collapse
Sorry for digging up old thread but how did it go? Did you manage to change default splashscreen?
What ive done myself so far was use X-Plore app with SuperSU access to copy splash file from /root/dev/block/bootdevice/by-name to external SD. In X-Plore splash file was 0b but upon copy it was 10MB.
Then i tried to use tool from other topic nbimg to convert splashscreen from 'unknown' format to BMP but result was bad. The tool is supposed to identify image resolution but it didnt know how in Redmi case (tool was orignally designed for HTC device i think) so i tried using w1280 h720 argument but result was like below:
http://i.imgur.com/sxYl65J.png
Well then i timply took any 720x720 image and used that nbimg tool to convert it to splash and then tried to replace it in /root/dev/block/bootdevice/by-name but on reboot it was reverted back to original
KonradIC13 said:
Sorry for digging up old thread but how did it go? Did you manage to change default splashscreen?
What ive done myself so far was use X-Plore app with SuperSU access to copy splash file from /root/dev/block/bootdevice/by-name to external SD. In X-Plore splash file was 0b but upon copy it was 10MB.
Then i tried to use tool from other topic nbimg to convert splashscreen from 'unknown' format to BMP but result was bad. The tool is supposed to identify image resolution but it didnt know how in Redmi case (tool was orignally designed for HTC device i think) so i tried using w1280 h720 argument but result was like below:
http://i.imgur.com/sxYl65J.png
Well then i timply took any 720x720 image and used that nbimg tool to convert it to splash and then tried to replace it in /root/dev/block/bootdevice/by-name but on reboot it was reverted back to original
Click to expand...
Click to collapse
No problem for digging old thread.
I did all the things exactly as what you did and had same results.
I still desperately want to make bootlogos for our belowed wt88047 but I just can't @ketut.kumajaya please just one hint for us and we will figure out rest.
I tried that python script on windows too but same broken splash.
Sent from my 2014818 using Tapatalk
@noobpremium @KonradIC13
[GUIDE] How to Create Custom Splash Screen (Boot Logo) for Redmi 2
No need to edit kernel.. The kernel has the logo that displays after Mi Boot Logo..
The boot logo (splash screen) is present in a separate partition..
GokulNC said:
@noobpremium @KonradIC13
[GUIDE] How to Create Custom Splash Screen (Boot Logo) for Redmi 2
No need to edit kernel.. The kernel has the logo that displays after Mi Boot Logo..
The boot logo (splash screen) is present in a separate partition..
Click to expand...
Click to collapse
What did you do exactly?
I'll have a look at your stuff and try it right now.
Seems you posted the thread just a while ago.
Sent from my 2014818 using Tapatalk
TWRP for backing up splash
noobpremium said:
What did you do exactly?
I'll have a look at your stuff and try it right now.
Seems you posted the thread just a while ago.
Sent from my 2014818 using Tapatalk
Click to expand...
Click to collapse
Can I try the batman logo.bin file inside the zip I pointed you to, through this method?
Also, will taking a Backup through recovery work for this, or do I have to flash the whole fastbot ROM if this fails?
.
P.S - Found this, but am reluctant to try, as I have office in an hour. (Will it work if I have MM 6.0.1 installed as Primary ROM? As is says for KK in that thread)
http://en.miui.com/thread-114090-1-1.html
EDIT - Or will this be more relevant -
http://en.miui.com/thread-249552-1-1.html
shanx_verma said:
Can I try the batman logo.bin file inside the zip I pointed you to, through this method?
Also, will taking a Backup through recovery work for this, or do I have to flash the whole fastbot ROM if this fails?
.
P.S - Found this, but am reluctant to try, as I have office in an hour. [emoji14] [emoji14] (Will it work if I have MM 6.0.1 installed as Primary ROM? As is says for KK in that thread)
http://en.miui.com/thread-114090-1-1.html
EDIT - Or will this be more relevant -
http://en.miui.com/thread-249552-1-1.html
Click to expand...
Click to collapse
Just use his tool no need of any flashable zip or something.
Sorry I didn't get time for your batman logo. I'll try tonight.
Btw, you can make your logo easily with that tool.
After it's compiled, flash is with terminal emulator or just fastboot command
"fastboot flash splash splash.img" and done.
Sent from my 2014818 using Tapatalk