I would like to start a new thread with topic as listed. It´s just so much easier to do searches this way.
As of now, there is no custom recovery for our device. While the root method from the i9505 also works on our device, custom recoveries do not. The issue seems to be with the display driver.
I would greatly appreciate if someone more knowledgable than me could elaborate on this.
I would be interested in this too. Also whether there is any prospect of rom development for the international active.
Sent from my HTC One using Tapatalk 2
Bumping.
Wouldn't it be a good idea to have a separate section for the i9295?
Yes there's a lot less audience for the device, but it is still an S4 model.
Any ideas on who we could contact to get the separate section made? (Not to mention one for the S4 Zoom when it's released)
Sent from my GT-I9300 using xda app-developers app
tryerxda said:
Bumping.
Wouldn't it be a good idea to have a separate section for the i9295?
Yes there's a lot less audience for the device, but it is still an S4 model.
Any ideas on who we could contact to get the separate section made? (Not to mention one for the S4 Zoom when it's released)
Sent from my GT-I9300 using xda app-developers app
Click to expand...
Click to collapse
Agree and bump...I'm thinking of getting this phone (it was my ideal choice, like the S4...but can be put underwater!), but the lack of community is starting to put me off...
timonoj said:
Agree and bump...I'm thinking of getting this phone (it was my ideal choice, like the S4...but can be put underwater!), but the lack of community is starting to put me off...
Click to expand...
Click to collapse
Patience - this just startet selling and shops seem to find it hard to keep up with customers, at least here in Germany.
Doolittle Duckbill said:
Patience - this just startet selling and shops seem to find it hard to keep up with customers, at least here in Germany.
Click to expand...
Click to collapse
Here in Hong Kong, as usual you can find it before anywhere in the shady shops in some tech markets. Right now for some 450€, which to be honest isn't a bad price. But Fortress and all the big shops (kind of like Media Markt) still don't sell it. I hope you're right and the buyers will come around to it. I'm holding my purchase until this is cleared up, I woudln't want a phone with no support. I had enough trouble with the S2 and its unsupported Exynos chipset.
hope to see in the near future a custom recovery for this devise
this are the mountpoints?
atform/msm_sdcc.1/by-name <
lrwxrwxrwx root root 1970-01-06 01:35 aboot -> /dev/block/mmcblk0p6
lrwxrwxrwx root root 1970-01-06 01:35 apnhlos -> /dev/block/mmcblk0p1
lrwxrwxrwx root root 1970-01-06 01:35 backup -> /dev/block/mmcblk0p23
lrwxrwxrwx root root 1970-01-06 01:35 boot -> /dev/block/mmcblk0p20
lrwxrwxrwx root root 1970-01-06 01:35 cache -> /dev/block/mmcblk0p18
lrwxrwxrwx root root 1970-01-06 01:35 carrier -> /dev/block/mmcblk0p28
lrwxrwxrwx root root 1970-01-06 01:35 efs -> /dev/block/mmcblk0p10
lrwxrwxrwx root root 1970-01-06 01:35 fota -> /dev/block/mmcblk0p22
lrwxrwxrwx root root 1970-01-06 01:35 fsg -> /dev/block/mmcblk0p24
lrwxrwxrwx root root 1970-01-06 01:35 hidden -> /dev/block/mmcblk0p27
lrwxrwxrwx root root 1970-01-06 01:35 m9kefs1 -> /dev/block/mmcblk0p13
lrwxrwxrwx root root 1970-01-06 01:35 m9kefs2 -> /dev/block/mmcblk0p14
lrwxrwxrwx root root 1970-01-06 01:35 m9kefs3 -> /dev/block/mmcblk0p15
lrwxrwxrwx root root 1970-01-06 01:35 mdm -> /dev/block/mmcblk0p2
lrwxrwxrwx root root 1970-01-06 01:35 modemst1 -> /dev/block/mmcblk0p11
lrwxrwxrwx root root 1970-01-06 01:35 modemst2 -> /dev/block/mmcblk0p12
lrwxrwxrwx root root 1970-01-06 01:35 pad -> /dev/block/mmcblk0p9
lrwxrwxrwx root root 1970-01-06 01:35 param -> /dev/block/mmcblk0p19
lrwxrwxrwx root root 1970-01-06 01:35 persdata -> /dev/block/mmcblk0p26
lrwxrwxrwx root root 1970-01-06 01:35 persist -> /dev/block/mmcblk0p17
lrwxrwxrwx root root 1970-01-06 01:35 recovery -> /dev/block/mmcblk0p21
lrwxrwxrwx root root 1970-01-06 01:35 rpm -> /dev/block/mmcblk0p7
lrwxrwxrwx root root 1970-01-06 01:35 sbl1 -> /dev/block/mmcblk0p3
lrwxrwxrwx root root 1970-01-06 01:35 sbl2 -> /dev/block/mmcblk0p4
lrwxrwxrwx root root 1970-01-06 01:35 sbl3 -> /dev/block/mmcblk0p5
lrwxrwxrwx root root 1970-01-06 01:35 ssd -> /dev/block/mmcblk0p25
lrwxrwxrwx root root 1970-01-06 01:35 system -> /dev/block/mmcblk0p16
lrwxrwxrwx root root 1970-01-06 01:35 tz -> /dev/block/mmcblk0p8
lrwxrwxrwx root root 1970-01-06 01:35 userdata -> /dev/block/mmcblk0p29
[email protected]:/ $
And attached the log of the first TWRP build thx to Dees_Troy
At the moment the screen didn´t work.
when you run the logfile of the stock recovery, is there anything resembling these lines:
Starting the UI...Pixel format: 1080x1920 @ 32bpp
Pixel format: RGBX_8888
framebuffer: fd 4 (1080 x 1920)
??
One would suspect that´s where the difference is, as everything seems to run except graphics
Doolittle Duckbill said:
when you run the logfile of the stock recovery, is there anything resembling these lines:
Starting the UI...Pixel format: 1080x1920 @ 32bpp
Pixel format: RGBX_8888
framebuffer: fd 4 (1080 x 1920)
??
One would suspect that´s where the difference is, as everything seems to run except graphics
Click to expand...
Click to collapse
the log from stock recovery
Ok, so in the TWRP for the i9095 we have:
ro.sf.lcd_density=320
while in stock recovery for the i9295 we have:
ro.sf.lcd_density=480
OK is there anybody here who can compile TWRP and knows where to set lcd density? My head is too small for these things...
Edit: On second thought, this may just be the scale factor for the screen and may not have anything to do with the display driver, so I just might be on the wrong track here... don´t know for sure
Doolittle Duckbill said:
Ok, so in the TWRP for the i9095 we have:
ro.sf.lcd_density=320
while in stock recovery for the i9295 we have:
ro.sf.lcd_density=480
OK is there anybody here who can compile TWRP and knows where to set lcd density? My head is too small for these things...
Edit: On second thought, this may just be the scale factor for the screen and may not have anything to do with the display driver, so I just might be on the wrong track here... don´t know for sure
Click to expand...
Click to collapse
Do you have log files for the 9505 booting twrp? Or know where to get them? I'm obviously looking myself.
On the htc one (i run both) there was an issue with the TWRP screen driver after a firmware upgrade. Is it worth contacting the TWRP team to ask them about the drivers?
Sent from my GT-I9295 using Tapatalk 4 Beta
Doolittle Duckbill said:
when you run the logfile of the stock recovery, is there anything resembling these lines:
Starting the UI...Pixel format: 1080x1920 @ 32bpp
Pixel format: RGBX_8888
framebuffer: fd 4 (1080 x 1920)
??
One would suspect that´s where the difference is, as everything seems to run except graphics
Click to expand...
Click to collapse
This is also difference:
initalized graphics for qualcomm.
pixel format -> GGL_PIXEL_FORMAT_RGBX_8888
return for qualcomm. double_buffering = 0
framebuffer: fd 4 (1080 x 1920)
---------- Post added at 06:09 AM ---------- Previous post was at 06:07 AM ----------
Have somebody contact to the cwm team?
So I managed to get cwm booted. It's saying "Warning: No file_context". I've been googling I can't find an explanation and source code is of little help. Anyone has a clue what it could be?
I'm running a backup. See if I fry anything
A preliminary version is of cwm up
http://forum.xda-developers.com/showthread.php?t=2387980
Sent from my GT-I9295 using xda premium
LeJay said:
So I managed to get cwm booted. It's saying "Warning: No file_context". I've been googling I can't find an explanation and source code is of little help. Anyone has a clue what it could be?
I'm running a backup. See if I fry anything
Click to expand...
Click to collapse
Its only a warning displayed when the kernel does not support SELinux.
Envoyé depuis mon GT-I9103
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 ?
LG G3 system img dump
System dump size: 2.4GB
Rar: 990MB
Download system:
Mega: https://mega.co.nz/#!iI8nQCpR!T0JebFjem_Ga9uxoirXJFOk8dVx6wEJCNhjRNU6yt5M
Download all other partition (include aboot, boot, etc....)
https://mega.co.nz/#!OMMCFLJB!3fmUAZzhDm9WwvXp-U0_TXqBF9GqKLufKyc7SApegt4
Pass unrar: LGViet.com
source: lgviet.com
@OptimusRs
@Hid3rs
@xdabbeb
Thx - I see twice the same downlaod link (dump + partitions)
bender_007 said:
Thx - I see twice the same downlaod link (dump + partitions)
Click to expand...
Click to collapse
Edited thanks
Two aboot's eh?
bobbarker2 said:
Two aboot's eh?
Click to expand...
Click to collapse
LG G3 Full partition info:
G3 has 2 bootloaders ?!
Yes, i'm researching
adb shell ls -la /dev/block/platform/msm_sdcc.1/by-name/
lrwxrwxrwx root root 1970-01-01 08:13 DDR -> /dev/block/mmcblk0p4
lrwxrwxrwx root root 1970-01-01 08:13 aboot -> /dev/block/mmcblk0p5
lrwxrwxrwx root root 1970-01-01 08:13 abootf -> /dev/block/mmcblk0p16
lrwxrwxrwx root root 1970-01-01 08:13 boot -> /dev/block/mmcblk0p18
lrwxrwxrwx root root 1970-01-01 08:13 cache -> /dev/block/mmcblk0p41
lrwxrwxrwx root root 1970-01-01 08:13 dbi -> /dev/block/mmcblk0p3
lrwxrwxrwx root root 1970-01-01 08:13 dbibak -> /dev/block/mmcblk0p10
lrwxrwxrwx root root 1970-01-01 08:13 drm -> /dev/block/mmcblk0p36
lrwxrwxrwx root root 1970-01-01 08:13 eksst -> /dev/block/mmcblk0p29
lrwxrwxrwx root root 1970-01-01 08:13 encrypt -> /dev/block/mmcblk0p28
lrwxrwxrwx root root 1970-01-01 08:13 factory -> /dev/block/mmcblk0p39
lrwxrwxrwx root root 1970-01-01 08:13 fota -> /dev/block/mmcblk0p34
lrwxrwxrwx root root 1970-01-01 08:13 fsc -> /dev/block/mmcblk0p25
lrwxrwxrwx root root 1970-01-01 08:13 fsg -> /dev/block/mmcblk0p24
lrwxrwxrwx root root 1970-01-01 08:13 grow -> /dev/block/mmcblk0p43
lrwxrwxrwx root root 1970-01-01 08:13 laf -> /dev/block/mmcblk0p33
lrwxrwxrwx root root 1970-01-01 08:13 misc -> /dev/block/mmcblk0p32
lrwxrwxrwx root root 1970-01-01 08:13 modem -> /dev/block/mmcblk0p1
lrwxrwxrwx root root 1970-01-01 08:13 modemst1 -> /dev/block/mmcblk0p21
lrwxrwxrwx root root 1970-01-01 08:13 modemst2 -> /dev/block/mmcblk0p22
lrwxrwxrwx root root 1970-01-01 08:13 mpt -> /dev/block/mmcblk0p38
lrwxrwxrwx root root 1970-01-01 08:13 pad -> /dev/block/mmcblk0p8
lrwxrwxrwx root root 1970-01-01 08:13 pad1 -> /dev/block/mmcblk0p23
lrwxrwxrwx root root 1970-01-01 08:13 pad2 -> /dev/block/mmcblk0p27
lrwxrwxrwx root root 1970-01-01 08:13 persist -> /dev/block/mmcblk0p19
lrwxrwxrwx root root 1970-01-01 08:13 rct -> /dev/block/mmcblk0p30
lrwxrwxrwx root root 1970-01-01 08:13 recovery -> /dev/block/mmcblk0p20
lrwxrwxrwx root root 1970-01-01 08:13 rpm -> /dev/block/mmcblk0p6
lrwxrwxrwx root root 1970-01-01 08:13 rpmbak -> /dev/block/mmcblk0p11
lrwxrwxrwx root root 1970-01-01 08:13 rpmf -> /dev/block/mmcblk0p13
lrwxrwxrwx root root 1970-01-01 08:13 sbl1 -> /dev/block/mmcblk0p2
lrwxrwxrwx root root 1970-01-01 08:13 sbl1b -> /dev/block/mmcblk0p9
lrwxrwxrwx root root 1970-01-01 08:13 sdif -> /dev/block/mmcblk0p15
lrwxrwxrwx root root 1970-01-01 08:13 sns -> /dev/block/mmcblk0p37
lrwxrwxrwx root root 1970-01-01 08:13 spare1 -> /dev/block/mmcblk0p17
lrwxrwxrwx root root 1970-01-01 08:13 spare2 -> /dev/block/mmcblk0p31
lrwxrwxrwx root root 1970-01-01 08:13 spare3 -> /dev/block/mmcblk0p35
lrwxrwxrwx root root 1970-01-01 08:13 ssd -> /dev/block/mmcblk0p26
lrwxrwxrwx root root 1970-01-01 08:13 system -> /dev/block/mmcblk0p40
lrwxrwxrwx root root 1970-01-01 08:13 tz -> /dev/block/mmcblk0p7
lrwxrwxrwx root root 1970-01-01 08:13 tzbak -> /dev/block/mmcblk0p12
lrwxrwxrwx root root 1970-01-01 08:13 tzf -> /dev/block/mmcblk0p14
lrwxrwxrwx root root 1970-01-01 08:13 userdata -> /dev/block/mmcblk0p42
I saw drivers for both IMX214 and IMX135 in the system dump. Any better way to know for sure what camera it's using?
abootf, tzf, rpmf, sdif etc are all blank (00s)... interesting.
would like to see fota partition. possibly misc partition(just edit imei out of misc with hex editor) or PM me with info instead.
wargreymon89 said:
I saw drivers for both IMX214 and IMX135 in the system dump. Any better way to know for sure what camera it's using?
Click to expand...
Click to collapse
That's very interesting. I suppose there are a few possibilities here. One would be that the G3 does use the IMX214 after all, or that the IMX214 and IMX135 are both used in different versions of the G3 (less likely). Perhaps the phone originally was being developed with the 135 and so initial prototypes used it, while the end production model would use the 214? Another possibility would be that perhaps the drivers come as a package from Sony and both the 135 and 214 are supported or come in the same package.
An editor at AndroidCentral claims he was told by LG that the sensor is not the same as the G2, meanwhile Anandtech reported that it was. It'd be nice to have some confirmation, but I suppose thus far the results speak for themselves as the G3 looks to be quite capable, whether that's due to improved software processing or a new sensor or both.
klmd said:
That's very interesting. I suppose there are a few possibilities here. One would be that the G3 does use the IMX214 after all, or that the IMX214 and IMX135 are both used in different versions of the G3 (less likely). Perhaps the phone originally was being developed with the 135 and so initial prototypes used it, while the end production model would use the 214? Another possibility would be that perhaps the drivers come as a package from Sony and both the 135 and 214 are supported or come in the same package.
An editor at AndroidCentral claims he was told by LG that the sensor is not the same as the G2, meanwhile Anandtech reported that it was. It'd be nice to have some confirmation, but I suppose thus far the results speak for themselves as the G3 looks to be quite capable, whether that's due to improved software processing or a new sensor or both.
Click to expand...
Click to collapse
I sure hope and believe it uses IMX214, both due to the obvious improvement in pictures and that LG usually picks the latest and best hardware. I guess only a tear down or D85X system dump with one or the other driver missing will prove what it's using.
autoprime said:
abootf, tzf, rpmf, sdif etc are all blank (00s)... interesting.
would like to see fota partition. possibly misc partition(just edit imei out of misc with hex editor) or PM me with info instead.
Click to expand...
Click to collapse
edited
About the LG Camera
hoangnova said:
LG G3 Full partition info:
G3 has 2 bootloaders ?!
Yes, i'm researching
adb shell ls -la /dev/block/platform/msm_sdcc.1/by-name/
lrwxrwxrwx root root 1970-01-01 08:13 userdata -> /dev/block/mmcblk0p42
Click to expand...
Click to collapse
Hi, Do you know the Camera details, These are from CameraApp, Can anyone confirmed the panorama_preview_size?
</item>
<item name="panorama_picture_size"> 4160x2340
</item>
<item name="panorama_preview_size"> 768x432
</item>
<item name="panorama_preview_size_on_screen"> 1920x1080
</item>
<item name="gestureshot_supported"> true
</item>
<item name="beautyshot_supported"> true
</item>
<item name="hdr_supported"> 3
</item>
Here is another config files for LG G3
</item>
<item name="panorama_picture_size"> 4160x2340
</item>
<item name="panorama_preview_size"> 1280x720
</item>
<item name="panorama_preview_size_on_screen"> 2560x1440
</item>
<item name="gestureshot_supported"> true
</item>
<item name="beautyshot_supported"> true
</item>
<item name="hdr_supported"> 2
What is all this info Worth? Does this mean development for cm11 will be easier? Speaking about that do you think it will be easy to root and have cm on this device?
Thanks in advance!
Sent from my SM-G900T using Tapatalk
I'm very thankful for this, cause I deleted some system apks and got myself a nasty bootloop! :silly:
is that for all G3 Variants, does it work with D855?
sycolon said:
is that for all G3 Variants, does it work with D855?
Click to expand...
Click to collapse
Its useless now.
@Ferindel my device is stuck on fastboot mode, cant enter the system or the Download mode.
what can i do i need help.
sycolon said:
@Ferindel my device is stuck on fastboot mode, cant enter the system or the Download mode.
what can i do i need help.
Click to expand...
Click to collapse
I got out of the fastboot loop by downloading the rin image from http://forum.xda-developers.com/lg-g3/orig-development/kernel-rin-kernel-1-0-t2847581 and using
Code:
fastboot boot D855-rin-1.0.1.img
sycolon said:
is that for all G3 Variants, does it work with D855?
Click to expand...
Click to collapse
Ferindel said:
Its useless now.
Click to expand...
Click to collapse
Why exactly is it useless???
It's a perfect way to have all system apps, in case of something went wrong by mistakenly deleting one etc.
i have no system nothing on my phone so i think just this kernel will do nothing, i need to back on stock or to have Download mode to flash KDZ file ...
---------- Post added at 10:43 PM ---------- Previous post was at 10:32 PM ----------
i flashed a aboot image from the file the colores of my screen in the logo where lost, i tried to delete and flash (laf,boot,aboot,recovery) , but nothing work, i couldn't have a Download Mode on my device.
last i did
macbook-proyi-macbook-pro-15:rar macbookpro$ ./fastboot erase boot
erasing 'boot'...
OKAY [ 0.017s]
finished. total time: 0.018s
macbook-proyi-macbook-pro-15:rar macbookpro$ ./fastboot erase aboot
erasing 'aboot'...
OKAY [ 0.008s]
finished. total time: 0.008s
macbook-proyi-macbook-pro-15:rar macbookpro$ ./fastboot erase laf
erasing 'laf'...
OKAY [ 0.017s]
finished. total time: 0.018s
macbook-proyi-macbook-pro-15:rar macbookpro$ ./fastboot erase recovery
erasing 'recovery'...
OKAY [ 0.017s]
finished. total time: 0.017s
macbook-proyi-macbook-pro-15:rar macbookpro$ ./fastboot reboot
rebooting...
Click to expand...
Click to collapse
now my device is dead, black screen, no lights nothing....
any help!!! please, my phone is just 3 months old..... **** and i paid for one month i have a year from now.....
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!
Im not really a dev but i know my way around android. I figured this could help kickstart development for us. I have pulled my boot.img and attached it below.
Here are the mount points for building a rom. May differ from the different varients. My model is XT1527 US LTE.
HTML:
ls -al /dev/block/platform/soc.0/by-name
lrwxrwxrwx root root 1970-01-23 12:12 DDR -> /dev/block/mmcblk0p3
lrwxrwxrwx root root 1970-01-23 12:12 aboot -> /dev/block/mmcblk0p4
lrwxrwxrwx root root 1970-01-23 12:12 abootBackup -> /dev/block/mmcblk0p14
lrwxrwxrwx root root 1970-01-23 12:12 boot -> /dev/block/mmcblk0p33
lrwxrwxrwx root root 1970-01-23 12:12 cache -> /dev/block/mmcblk0p43
lrwxrwxrwx root root 1970-01-23 12:12 carrier -> /dev/block/mmcblk0p41
lrwxrwxrwx root root 1970-01-23 12:12 cid -> /dev/block/mmcblk0p28
lrwxrwxrwx root root 1970-01-23 12:12 clogo -> /dev/block/mmcblk0p30
lrwxrwxrwx root root 1970-01-23 12:12 dhob -> /dev/block/mmcblk0p24
lrwxrwxrwx root root 1970-01-23 12:12 factorytune1 -> /dev/block/mmcblk0p11
lrwxrwxrwx root root 1970-01-23 12:12 factorytune2 -> /dev/block/mmcblk0p35
lrwxrwxrwx root root 1970-01-23 12:12 frp -> /dev/block/mmcblk0p20
lrwxrwxrwx root root 1970-01-23 12:12 fsc -> /dev/block/mmcblk0p26
lrwxrwxrwx root root 1970-01-23 12:12 fsg -> /dev/block/mmcblk0p25
lrwxrwxrwx root root 1970-01-23 12:12 hob -> /dev/block/mmcblk0p23
lrwxrwxrwx root root 1970-01-23 12:12 hyp -> /dev/block/mmcblk0p7
lrwxrwxrwx root root 1970-01-23 12:12 hypBackup -> /dev/block/mmcblk0p18
lrwxrwxrwx root root 1970-01-23 12:12 keystore -> /dev/block/mmcblk0p39
lrwxrwxrwx root root 1970-01-23 12:12 kpan -> /dev/block/mmcblk0p36
lrwxrwxrwx root root 1970-01-23 12:12 logo -> /dev/block/mmcblk0p29
lrwxrwxrwx root root 1970-01-23 12:12 logs -> /dev/block/mmcblk0p9
lrwxrwxrwx root root 1970-01-23 12:12 metadata -> /dev/block/mmcblk0p13
lrwxrwxrwx root root 1970-01-23 12:12 misc -> /dev/block/mmcblk0p32
lrwxrwxrwx root root 1970-01-23 12:12 modem -> /dev/block/mmcblk0p1
lrwxrwxrwx root root 1970-01-23 12:12 modemst1 -> /dev/block/mmcblk0p21
lrwxrwxrwx root root 1970-01-23 12:12 modemst2 -> /dev/block/mmcblk0p22
lrwxrwxrwx root root 1970-01-23 12:12 oem -> /dev/block/mmcblk0p40
lrwxrwxrwx root root 1970-01-23 12:12 padA -> /dev/block/mmcblk0p12
lrwxrwxrwx root root 1970-01-23 12:12 padB -> /dev/block/mmcblk0p19
lrwxrwxrwx root root 1970-01-23 12:12 padC -> /dev/block/mmcblk0p37
lrwxrwxrwx root root 1970-01-23 12:12 persist -> /dev/block/mmcblk0p31
lrwxrwxrwx root root 1970-01-23 12:12 recovery -> /dev/block/mmcblk0p34
lrwxrwxrwx root root 1970-01-23 12:12 rpm -> /dev/block/mmcblk0p5
lrwxrwxrwx root root 1970-01-23 12:12 rpmBackup -> /dev/block/mmcblk0p15
lrwxrwxrwx root root 1970-01-23 12:12 sbl1 -> /dev/block/mmcblk0p2
lrwxrwxrwx root root 1970-01-23 12:12 sec -> /dev/block/mmcblk0p10
lrwxrwxrwx root root 1970-01-23 12:12 sp -> /dev/block/mmcblk0p38
lrwxrwxrwx root root 1970-01-23 12:12 ssd -> /dev/block/mmcblk0p27
lrwxrwxrwx root root 1970-01-23 12:12 system -> /dev/block/mmcblk0p42
lrwxrwxrwx root root 1970-01-23 12:12 tz -> /dev/block/mmcblk0p6
lrwxrwxrwx root root 1970-01-23 12:12 tzBackup -> /dev/block/mmcblk0p16
lrwxrwxrwx root root 1970-01-23 12:12 userdata -> /dev/block/mmcblk0p44
lrwxrwxrwx root root 1970-01-23 12:12 utags -> /dev/block/mmcblk0p8
lrwxrwxrwx root root 1970-01-23 12:12 utagsBackup -> /dev/block/mmcblk0p17
Excellent.... Thank u....I will try to release a ROM within a week
Shawn5162 said:
Excellent.... Thank u....I will try to release a ROM within a week
Click to expand...
Click to collapse
good news, good luck for your build
Shawn5162 said:
Excellent.... Thank u....I will try to release a ROM within a week
Click to expand...
Click to collapse
awesome, if you need a tester, please pm.
Shawn5162 said:
Excellent.... Thank u....I will try to release a ROM within a week
Click to expand...
Click to collapse
Shawn, you got a Moto E 2015? :laugh:
I find myself fortunate getting MotoG 2015 n Moto E 2015, both being worked upon by you! Thanks man!
If anybody who us good at linux knows how to add these mount points to cwm or philz touch im trying to port a build for us pm me.
WIFI tethering
I just picked this phone up today and cricket has ripped out the WIFI tethering. If anyone has a stock rooted rom please send me a link.
Mounting points are different on my cmda moto e2 will try to upload them later
bzo22 said:
Mounting points are different on my cmda moto e2 will try to upload them later
Click to expand...
Click to collapse
yup the cdma models and the 3g only models will probably have different mounts.
cmda xt1526 boostmobile surina
s -al /dev/block/platform/soc.0/by-name <
/dev/block/platform/soc.0/by-name: Permission denied
1|[email protected]_cdma:/ $ su
s -al /dev/block/platform/soc.0/by-name <
lrwxrwxrwx root root 1970-01-31 14:18 DDR -> /dev/block/mmcblk0p3
lrwxrwxrwx root root 1970-01-31 14:18 aboot -> /dev/block/mmcblk0p4
lrwxrwxrwx root root 1970-01-31 14:18 abootBackup -> /dev/block/mmcblk0p14
lrwxrwxrwx root root 1970-01-31 14:18 boot -> /dev/block/mmcblk0p33
lrwxrwxrwx root root 1970-01-31 14:18 cache -> /dev/block/mmcblk0p42
lrwxrwxrwx root root 1970-01-31 14:18 carrier -> /dev/block/mmcblk0p40
lrwxrwxrwx root root 1970-01-31 14:18 cid -> /dev/block/mmcblk0p28
lrwxrwxrwx root root 1970-01-31 14:18 clogo -> /dev/block/mmcblk0p30
lrwxrwxrwx root root 1970-01-31 14:18 dhob -> /dev/block/mmcblk0p24
lrwxrwxrwx root root 1970-01-31 14:18 factorytune1 -> /dev/block/mmcblk0p11
lrwxrwxrwx root root 1970-01-31 14:18 factorytune2 -> /dev/block/mmcblk0p35
lrwxrwxrwx root root 1970-01-31 14:18 frp -> /dev/block/mmcblk0p20
lrwxrwxrwx root root 1970-01-31 14:18 fsc -> /dev/block/mmcblk0p26
lrwxrwxrwx root root 1970-01-31 14:18 fsg -> /dev/block/mmcblk0p25
lrwxrwxrwx root root 1970-01-31 14:18 hob -> /dev/block/mmcblk0p23
lrwxrwxrwx root root 1970-01-31 14:18 hyp -> /dev/block/mmcblk0p7
lrwxrwxrwx root root 1970-01-31 14:18 hypBackup -> /dev/block/mmcblk0p18
lrwxrwxrwx root root 1970-01-31 14:18 keystore -> /dev/block/mmcblk0p39
lrwxrwxrwx root root 1970-01-31 14:18 kpan -> /dev/block/mmcblk0p36
lrwxrwxrwx root root 1970-01-31 14:18 logo -> /dev/block/mmcblk0p29
lrwxrwxrwx root root 1970-01-31 14:18 logs -> /dev/block/mmcblk0p9
lrwxrwxrwx root root 1970-01-31 14:18 metadata -> /dev/block/mmcblk0p13
lrwxrwxrwx root root 1970-01-31 14:18 misc -> /dev/block/mmcblk0p32
lrwxrwxrwx root root 1970-01-31 14:18 modem -> /dev/block/mmcblk0p1
lrwxrwxrwx root root 1970-01-31 14:18 modemst1 -> /dev/block/mmcblk0p21
lrwxrwxrwx root root 1970-01-31 14:18 modemst2 -> /dev/block/mmcblk0p22
lrwxrwxrwx root root 1970-01-31 14:18 padA -> /dev/block/mmcblk0p12
lrwxrwxrwx root root 1970-01-31 14:18 padB -> /dev/block/mmcblk0p19
lrwxrwxrwx root root 1970-01-31 14:18 padC -> /dev/block/mmcblk0p37
lrwxrwxrwx root root 1970-01-31 14:18 persist -> /dev/block/mmcblk0p31
lrwxrwxrwx root root 1970-01-31 14:18 recovery -> /dev/block/mmcblk0p34
lrwxrwxrwx root root 1970-01-31 14:18 rpm -> /dev/block/mmcblk0p5
lrwxrwxrwx root root 1970-01-31 14:18 rpmBackup -> /dev/block/mmcblk0p15
lrwxrwxrwx root root 1970-01-31 14:18 sbl1 -> /dev/block/mmcblk0p2
lrwxrwxrwx root root 1970-01-31 14:18 sec -> /dev/block/mmcblk0p10
lrwxrwxrwx root root 1970-01-31 14:18 sp -> /dev/block/mmcblk0p38
lrwxrwxrwx root root 1970-01-31 14:18 ssd -> /dev/block/mmcblk0p27
lrwxrwxrwx root root 1970-01-31 14:18 system -> /dev/block/mmcblk0p41
lrwxrwxrwx root root 1970-01-31 14:18 tz -> /dev/block/mmcblk0p6
lrwxrwxrwx root root 1970-01-31 14:18 tzBackup -> /dev/block/mmcblk0p16
lrwxrwxrwx root root 1970-01-31 14:18 userdata -> /dev/block/mmcblk0p43
lrwxrwxrwx root root 1970-01-31 14:18 utags -> /dev/block/mmcblk0p8
lrwxrwxrwx root root 1970-01-31 14:18 utagsBackup -> /dev/block/mmcblk0p17
[email protected]_cdma:/ #
bzo22 said:
s -al /dev/block/platform/soc.0/by-name <
<SNIP>
[email protected]_cdma:/ #
Click to expand...
Click to collapse
How did you get root on the xt1526 boost phone bzo22? Any chance you could post the stock boot loader img file or direct me to a working copy of a bootloader for it?
phliptrip said:
How did you get root on the xt1526 boost phone bzo22? Any chance you could post the stock boot loader img file or direct me to a working copy of a bootloader for it?
Click to expand...
Click to collapse
I used twrp to flash super user the recovery works for our device too...but do not flash it just boot it from fastboot. Which partition is boot loader stored . is it aboot or boot section
aboot.img
bzo22 said:
I used twrp to flash super user the recovery works for our device too...but do not flash it just boot it from fastboot. Which partition is boot loader stored . is it aboot or boot section
Click to expand...
Click to collapse
Here u go the aboot.img
Rooted this Phone
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
phliptrip said:
How did you get root on the xt1526 boost phone bzo22? Any chance you could post the stock boot loader img file or direct me to a working copy of a bootloader for it?
Click to expand...
Click to collapse
---------- Post added at 08:32 PM ---------- Previous post was at 08:29 PM ----------
i have root on this phone look and see.
http://imgur.com/tll9LYH,TeVRm5I,4dBA7v5,TdZJI1m,vJyFZEa
---------- Post added at 08:35 PM ---------- Previous post was at 08:32 PM ----------
here are some more pictures of my phone.
http://imgur.com/tll9LYH,TeVRm5I,4dBA7v5,TdZJI1m,vJyFZEa#1
http://imgur.com/tll9LYH,TeVRm5I,4dBA7v5,TdZJI1m,vJyFZEa#2
http://imgur.com/tll9LYH,TeVRm5I,4dBA7v5,TdZJI1m,vJyFZEa#3
http://imgur.com/tll9LYH,TeVRm5I,4dBA7v5,TdZJI1m,vJyFZEa#4.
there you go. im not giving you the files.because i can
fix-this! said:
Im not really a dev but i know my way around android. I figured this could help kickstart development for us. I have pulled my boot.img and attached it below.
Here are the mount points for building a rom. May differ from the different varients. My model is XT1527 US LTE.
HTML:
ls -al /dev/block/platform/soc.0/by-name
lrwxrwxrwx root root 1970-01-23 12:12 DDR -> /dev/block/mmcblk0p3
lrwxrwxrwx root root 1970-01-23 12:12 aboot -> /dev/block/mmcblk0p4
lrwxrwxrwx root root 1970-01-23 12:12 abootBackup -> /dev/block/mmcblk0p14
lrwxrwxrwx root root 1970-01-23 12:12 boot -> /dev/block/mmcblk0p33
lrwxrwxrwx root root 1970-01-23 12:12 cache -> /dev/block/mmcblk0p43
lrwxrwxrwx root root 1970-01-23 12:12 carrier -> /dev/block/mmcblk0p41
lrwxrwxrwx root root 1970-01-23 12:12 cid -> /dev/block/mmcblk0p28
lrwxrwxrwx root root 1970-01-23 12:12 clogo -> /dev/block/mmcblk0p30
lrwxrwxrwx root root 1970-01-23 12:12 dhob -> /dev/block/mmcblk0p24
lrwxrwxrwx root root 1970-01-23 12:12 factorytune1 -> /dev/block/mmcblk0p11
lrwxrwxrwx root root 1970-01-23 12:12 factorytune2 -> /dev/block/mmcblk0p35
lrwxrwxrwx root root 1970-01-23 12:12 frp -> /dev/block/mmcblk0p20
lrwxrwxrwx root root 1970-01-23 12:12 fsc -> /dev/block/mmcblk0p26
lrwxrwxrwx root root 1970-01-23 12:12 fsg -> /dev/block/mmcblk0p25
lrwxrwxrwx root root 1970-01-23 12:12 hob -> /dev/block/mmcblk0p23
lrwxrwxrwx root root 1970-01-23 12:12 hyp -> /dev/block/mmcblk0p7
lrwxrwxrwx root root 1970-01-23 12:12 hypBackup -> /dev/block/mmcblk0p18
lrwxrwxrwx root root 1970-01-23 12:12 keystore -> /dev/block/mmcblk0p39
lrwxrwxrwx root root 1970-01-23 12:12 kpan -> /dev/block/mmcblk0p36
lrwxrwxrwx root root 1970-01-23 12:12 logo -> /dev/block/mmcblk0p29
lrwxrwxrwx root root 1970-01-23 12:12 logs -> /dev/block/mmcblk0p9
lrwxrwxrwx root root 1970-01-23 12:12 metadata -> /dev/block/mmcblk0p13
lrwxrwxrwx root root 1970-01-23 12:12 misc -> /dev/block/mmcblk0p32
lrwxrwxrwx root root 1970-01-23 12:12 modem -> /dev/block/mmcblk0p1
lrwxrwxrwx root root 1970-01-23 12:12 modemst1 -> /dev/block/mmcblk0p21
lrwxrwxrwx root root 1970-01-23 12:12 modemst2 -> /dev/block/mmcblk0p22
lrwxrwxrwx root root 1970-01-23 12:12 oem -> /dev/block/mmcblk0p40
lrwxrwxrwx root root 1970-01-23 12:12 padA -> /dev/block/mmcblk0p12
lrwxrwxrwx root root 1970-01-23 12:12 padB -> /dev/block/mmcblk0p19
lrwxrwxrwx root root 1970-01-23 12:12 padC -> /dev/block/mmcblk0p37
lrwxrwxrwx root root 1970-01-23 12:12 persist -> /dev/block/mmcblk0p31
lrwxrwxrwx root root 1970-01-23 12:12 recovery -> /dev/block/mmcblk0p34
lrwxrwxrwx root root 1970-01-23 12:12 rpm -> /dev/block/mmcblk0p5
lrwxrwxrwx root root 1970-01-23 12:12 rpmBackup -> /dev/block/mmcblk0p15
lrwxrwxrwx root root 1970-01-23 12:12 sbl1 -> /dev/block/mmcblk0p2
lrwxrwxrwx root root 1970-01-23 12:12 sec -> /dev/block/mmcblk0p10
lrwxrwxrwx root root 1970-01-23 12:12 sp -> /dev/block/mmcblk0p38
lrwxrwxrwx root root 1970-01-23 12:12 ssd -> /dev/block/mmcblk0p27
lrwxrwxrwx root root 1970-01-23 12:12 system -> /dev/block/mmcblk0p42
lrwxrwxrwx root root 1970-01-23 12:12 tz -> /dev/block/mmcblk0p6
lrwxrwxrwx root root 1970-01-23 12:12 tzBackup -> /dev/block/mmcblk0p16
lrwxrwxrwx root root 1970-01-23 12:12 userdata -> /dev/block/mmcblk0p44
lrwxrwxrwx root root 1970-01-23 12:12 utags -> /dev/block/mmcblk0p8
lrwxrwxrwx root root 1970-01-23 12:12 utagsBackup -> /dev/block/mmcblk0p17
Click to expand...
Click to collapse
hey bro i needed some help. first can this boot image be used for 3g version.
If not then please can you tell me how to extract the boot.img of moto e 3g version
I've got the XT1527 for cricket and I'm willing to test. I'm no dev but ive been flashing roms constantly on all sorts of devices for a few years and id like to get involved and learn more if possible. This is my daily driver though so I might be a little cautious until there's a working twrp or something for the US version but this is a good phone so I'm very eager to see what ends up being made for this phone. Normally I'll look a phone up before buying it to make sure there's plenty of stuff available to keep me busy with it but when I saw this one had very little I actually got excited since Im sure this one will wind up with some good stuff and for the first time I won't be starting with a phone months after the forum died down lol
hakr4life said:
I've got the XT1527 for cricket and I'm willing to test. I'm no dev but ive been flashing roms constantly on all sorts of devices for a few years and id like to get involved and learn more if possible. This is my daily driver though so I might be a little cautious until there's a working twrp or something for the US version but this is a good phone so I'm very eager to see what ends up being made for this phone. Normally I'll look a phone up before buying it to make sure there's plenty of stuff available to keep me busy with it but when I saw this one had very little I actually got excited since Im sure this one will wind up with some good stuff and for the first time I won't be starting with a phone months after the forum died down lol
Click to expand...
Click to collapse
Same here keep me in the loop. I'm eager to brick my new phone
Sent from my MotoE2(4G-LTE) using XDA Free mobile app
+1 for at%t/aio/cricket users on the XT1527 model. there has got to be a workaround for the unlock on this. @mdewii23 @hakr4life
Can someone provide stock recovery?
I've scoured the internet over and over and come up with nothing yet
Sent from my Nexus 4 using XDA Free mobile app
Sorry to ask, im newbie but as far i understand.
Ascend xt got:
Unlockeable bootloader
TWRP
Root
So what is missing for our custom roms?
yunior597 said:
Sorry to ask, im newbie but as far i understand.
Ascend xt got:
Unlockeable bootloader
TWRP
Root
So what is missing for our custom roms?
Click to expand...
Click to collapse
maybe start with a system dump?
Sent from my LGLS676
Sands207 said:
maybe start with a system dump?
Sent from my LGLS676
Click to expand...
Click to collapse
cause its not easy for one or u would of released a rom already 2 we dont have original source code for device so that slows progress 3 if we go to build one we have to modify a source from another device. i tried porting it was fail everytime, but u can always try to make one. pick one you like and port it or build it. im working on lineage atm someone else resurrection remix. and thats all i think
madvane20 said:
cause its not easy for one or u would of released a rom already 2 we dont have original source code for device 3 if we go to build one we have to modify a source from another device i tried porting was fail everytime but u can always try to make one. pick one you like and port it or build it. im working on lineage atm someone else resurrection remix. and thats all i think
Click to expand...
Click to collapse
Start here, get your system dump and create a fresh device tree on github https://forum.xda-developers.com/showthread.php?t=2450045 then you will have a base for cm, rr whatever you choose to build. If you want to build aosp source would be needed I believe or backported but a system dump will literally give you the same files that you would gain from building from source, I just went through this myself. Just trying to help, follow the guide and if you need help with a device tree I could try and help. good luck ?
Sent from my LGLS676
Sands207 said:
Start here, get your system dump and create a fresh device tree on github https://forum.xda-developers.com/showthread.php?t=2450045 then you will have a base for cm, rr whatever you choose to build. If you want to build aosp source would be needed I believe or backported but a system dump will literally give you the same files that you would gain from building from source, I just went through this myself. Just trying to help, follow the guide and if you need help with a device tree I could try and help. good luck
Sent from my LGLS676
Click to expand...
Click to collapse
go for it as u will have noticed if u read the other thread we have dumped the system i have even dumped all partitions. just cause u have the files doesnt mean u can click here and magic full working os comes out. without original source code we have to make changes to the source from a device with similiar hardware. as well as make sure correct paths to files that the other source did not include. this is due to other phones sometimes have different file structures. i dunno bout anyone else but im doing my best and going as fast as i can without just 100% fail. uploading my source i made to build on my server if it boots after i build it good if everything works awesome if not if it boots then i can go through check whats missing
madvane20 said:
go for it as u will have noticed if u read the other thread we have dumped the system i have even dumped all partitions. just cause u have the files doesnt mean u can click here and magic full working os comes out
Click to expand...
Click to collapse
you wanna be rude then figure it out for yourself, was just trying to help you lol
Sent from my LGLS676
Sands207 said:
you wanna be rude then figure it out for yourself, was just trying to help you lol
Sent from my LGLS676
Click to expand...
Click to collapse
wasnt being rude i modified my last post being i was in a hurry and didnt type it out so well. i was just saying man if u know the easy way to make us a rom. go for it alot of people will thank you. if not give us time its not a easy process. also by the way my first time making a rom well building from source i tried to port for about week and a half on windows that didnt work. now im using linux so hope that gives more promising results. as well building it also takes some time why i switched to using my server to compile it uploading files still got 50 gig to go. after i get a wroking one im going to try and fix our twrp to allow for those who want stock to do ota updates from twrp and backup cust and other partitions if feel a need too. hope u dont take this as being rude as it providing info and and letting you know if u can build one then thats awesome. if not give people time heres a list of the partitions
lrwxrwxrwx root root 1969-12-31 21:59 DDR -> /dev/block/mmcblk0p4
lrwxrwxrwx root root 1969-12-31 21:59 aboot -> /dev/block/mmcblk0p7
lrwxrwxrwx root root 1969-12-31 21:59 boot -> /dev/block/mmcblk0p10
lrwxrwxrwx root root 1969-12-31 21:59 cache -> /dev/block/mmcblk0p22
lrwxrwxrwx root root 1969-12-31 21:59 config -> /dev/block/mmcblk0p25
lrwxrwxrwx root root 1969-12-31 21:59 cust -> /dev/block/mmcblk0p23
lrwxrwxrwx root root 1969-12-31 21:59 erecovery -> /dev/block/mmcblk0p12
lrwxrwxrwx root root 1969-12-31 21:59 fsc -> /dev/block/mmcblk0p19
lrwxrwxrwx root root 1969-12-31 21:59 fsg -> /dev/block/mmcblk0p9
lrwxrwxrwx root root 1969-12-31 21:59 hyp -> /dev/block/mmcblk0p2
lrwxrwxrwx root root 1969-12-31 21:59 log -> /dev/block/mmcblk0p17
lrwxrwxrwx root root 1969-12-31 21:59 misc -> /dev/block/mmcblk0p16
lrwxrwxrwx root root 1969-12-31 21:59 modem -> /dev/block/mmcblk0p14
lrwxrwxrwx root root 1969-12-31 21:59 modemst1 -> /dev/block/mmcblk0p26
lrwxrwxrwx root root 1969-12-31 21:59 modemst2 -> /dev/block/mmcblk0p27
lrwxrwxrwx root root 1969-12-31 21:59 oeminfo -> /dev/block/mmcblk0p15
lrwxrwxrwx root root 1969-12-31 21:59 pad -> /dev/block/mmcblk0p21
lrwxrwxrwx root root 1969-12-31 21:59 pad0 -> /dev/block/mmcblk0p8
lrwxrwxrwx root root 1969-12-31 21:59 persist -> /dev/block/mmcblk0p18
lrwxrwxrwx root root 1969-12-31 21:59 recovery -> /dev/block/mmcblk0p11
lrwxrwxrwx root root 1969-12-31 21:59 rpm -> /dev/block/mmcblk0p5
lrwxrwxrwx root root 1969-12-31 21:59 sbl1 -> /dev/block/mmcblk0p1
lrwxrwxrwx root root 1969-12-31 21:59 sec -> /dev/block/mmcblk0p3
lrwxrwxrwx root root 1969-12-31 21:59 sgb -> /dev/block/mmcblk0p13
lrwxrwxrwx root root 1969-12-31 21:59 ssd -> /dev/block/mmcblk0p20
lrwxrwxrwx root root 1969-12-31 21:59 system -> /dev/block/mmcblk0p24
lrwxrwxrwx root root 1969-12-31 21:59 tz -> /dev/block/mmcblk0p6
lrwxrwxrwx root root 1969-12-31 21:59 userdata -> /dev/block/mmcblk0p28
Well, i see, good luck with that. I hope to see a rom in future. Hate all this bloatware and etc.
yunior597 said:
Well, i see, good luck with that. I hope to see a rom in future. Hate all this bloatware and etc.
Click to expand...
Click to collapse
i have a debloated rom however i need to upload a flashable zip that also removes the garbage from cust partition make a guide on how to remove it. or i may just repack the system image i debloated as well make guide to on how to get rid of stuff off there. theres already a guide how to backup and restore the cust as well as posts bout it all i might just make a guide for alot of it and also make a video on step by step rooting etc
madvane20 said:
wasnt being rude i modified my last post being i was in a hurry and didnt type it out so well. i was just saying man if u know the easy way to make us a rom. go for it alot of people will thank you. if not give us time its not a easy process. also by the way my first time making a rom well building from source i tried to port for about week and a half on windows that didnt work. now im using linux so hope that gives more promising results. as well building it also takes some time why i switched to using my server to compile it uploading files still got 50 gig to go. after i get a wroking one im going to try and fix our twrp to allow for those who want stock to do ota updates from twrp and backup cust and other partitions if feel a need too. hope u dont take this as being rude as it providing info and and letting you know if u can build one then thats awesome. if not give people time heres a list of the partitions
lrwxrwxrwx root root 1969-12-31 21:59 DDR -> /dev/block/mmcblk0p4
lrwxrwxrwx root root 1969-12-31 21:59 aboot -> /dev/block/mmcblk0p7
lrwxrwxrwx root root 1969-12-31 21:59 boot -> /dev/block/mmcblk0p10
lrwxrwxrwx root root 1969-12-31 21:59 cache -> /dev/block/mmcblk0p22
lrwxrwxrwx root root 1969-12-31 21:59 config -> /dev/block/mmcblk0p25
lrwxrwxrwx root root 1969-12-31 21:59 cust -> /dev/block/mmcblk0p23
lrwxrwxrwx root root 1969-12-31 21:59 erecovery -> /dev/block/mmcblk0p12
lrwxrwxrwx root root 1969-12-31 21:59 fsc -> /dev/block/mmcblk0p19
lrwxrwxrwx root root 1969-12-31 21:59 fsg -> /dev/block/mmcblk0p9
lrwxrwxrwx root root 1969-12-31 21:59 hyp -> /dev/block/mmcblk0p2
lrwxrwxrwx root root 1969-12-31 21:59 log -> /dev/block/mmcblk0p17
lrwxrwxrwx root root 1969-12-31 21:59 misc -> /dev/block/mmcblk0p16
lrwxrwxrwx root root 1969-12-31 21:59 modem -> /dev/block/mmcblk0p14
lrwxrwxrwx root root 1969-12-31 21:59 modemst1 -> /dev/block/mmcblk0p26
lrwxrwxrwx root root 1969-12-31 21:59 modemst2 -> /dev/block/mmcblk0p27
lrwxrwxrwx root root 1969-12-31 21:59 oeminfo -> /dev/block/mmcblk0p15
lrwxrwxrwx root root 1969-12-31 21:59 pad -> /dev/block/mmcblk0p21
lrwxrwxrwx root root 1969-12-31 21:59 pad0 -> /dev/block/mmcblk0p8
lrwxrwxrwx root root 1969-12-31 21:59 persist -> /dev/block/mmcblk0p18
lrwxrwxrwx root root 1969-12-31 21:59 recovery -> /dev/block/mmcblk0p11
lrwxrwxrwx root root 1969-12-31 21:59 rpm -> /dev/block/mmcblk0p5
lrwxrwxrwx root root 1969-12-31 21:59 sbl1 -> /dev/block/mmcblk0p1
lrwxrwxrwx root root 1969-12-31 21:59 sec -> /dev/block/mmcblk0p3
lrwxrwxrwx root root 1969-12-31 21:59 sgb -> /dev/block/mmcblk0p13
lrwxrwxrwx root root 1969-12-31 21:59 ssd -> /dev/block/mmcblk0p20
lrwxrwxrwx root root 1969-12-31 21:59 system -> /dev/block/mmcblk0p24
lrwxrwxrwx root root 1969-12-31 21:59 tz -> /dev/block/mmcblk0p6
lrwxrwxrwx root root 1969-12-31 21:59 userdata -> /dev/block/mmcblk0p28
Click to expand...
Click to collapse
While i appreciate the info and don't worry about it try this at least to get started. Look up @superR's kitchen and take your files, throw down the 10 bucks and get the donate version with plugins, which i can say personally helps a ton or Android Studio maybe? and take what you have and make a ROM that way although the kitchen is like ly the easiest route. You are well on your way! Im passing through and trying to help, tonight ill download the files you have and see what i can piece together if you want but obviously i can't make any promises. Providing info like you did is the way to go ? link me to your files either in a pm or here and ill see what i can do.
Sent from my LGLS676
Sands207 said:
While i appreciate the info and don't worry about it try this at least to get started. Look up @superR's kitchen and take your files, throw down the 10 bucks and get the donate version with plugins, which i can say personally helps a ton or Android Studio maybe? and take what you have and make a ROM that way although the kitchen is like ly the easiest route. You are well on your way! Im passing through and trying to help, tonight ill download the files you have and see what i can piece together if you want but obviously i can't make any promises. Providing info like you did is the way to go link me to your files either in a pm or here and ill see what i can do.
Sent from my LGLS676
Click to expand...
Click to collapse
oh im doing fine free tools im uusing my 16 core 18gv burstable to 30 gb server to compile my builds as go throw to debug
---------- Post added at 05:46 AM ---------- Previous post was at 05:45 AM ----------
oh im doing fine free tools im using my 16 core 18 gb burstable to 30 gb server to compile my builds as go throw to debug
madvane20 said:
oh im doing fine free tools im uusing my 16 core 18gv burstable to 30 gb server to compile my builds as go throw to debug
---------- Post added at 05:46 AM ---------- Previous post was at 05:45 AM ----------
oh im doing fine free tools im using my 16 core 18 gb burstable to 30 gb server to compile my builds as go throw to debug
Click to expand...
Click to collapse
madvane20,
You mentioned earlier that we don't have source code. I checked the Huawei site and found the source code posted. Perhaps Huawei silently posted it without anyone noticing because people stop checking.
H1611 Huawei Ascend XT, Texas-A1(H1611), Android6.0, EMUI4.1
http://consumer.huawei.com/en/opens...Type=openSourceSoftware&pageSize=10&curPage=1
Search for "ascend" and it shows up as the only result. It contains kernel.tar.gz at 168 MB along with a readme.txt on how to build it. I extracted a *.c file to make sure it has real source code, and it sure does.
Perhaps this will help with development. Do you think this is the last piece we need to get it all going? If so, I am ready to go out and buy one!
Thanks for keeping it going.
pekcle
[/COLOR]
pekcle said:
madvane20,
You mentioned earlier that we don't have source code. I checked the Huawei site and found the source code posted. Perhaps Huawei silently posted it without anyone noticing because people stop checking.
H1611 Huawei Ascend XT, Texas-A1(H1611), Android6.0, EMUI4.1
http://consumer.huawei.com/en/opens...Type=openSourceSoftware&pageSize=10&curPage=1
Search for "ascend" and it shows up as the only result. It contains kernel.tar.gz at 168 MB along with a readme.txt on how to build it. I extracted a *.c file to make sure it has real source code, and it sure does.
Perhaps this will help with development. Do you think this is the last piece we need to get it all going? If so, I am ready to go out and buy one!
Thanks for keeping it going.
pekcle
Click to expand...
Click to collapse
Awesome that you found this, Huawei has released the source code. Should be easier to compile a ROM and tweak TWRP now.
In the search box, indeed type Ascend and it comes up from the above link
Awesome! Here's the direct download link if anyone wants to skip the search:
http://download-c1.huawei.com/downl...oadId=90665&version=353730&siteCode=worldwide
pekcle said:
madvane20,
You mentioned earlier that we don't have source code. I checked the Huawei site and found the source code posted. Perhaps Huawei silently posted it without anyone noticing because people stop checking.
H1611 Huawei Ascend XT, Texas-A1(H1611), Android6.0, EMUI4.1
http://consumer.huawei.com/en/opens...Type=openSourceSoftware&pageSize=10&curPage=1
Search for "ascend" and it shows up as the only result. It contains kernel.tar.gz at 168 MB along with a readme.txt on how to build it. I extracted a *.c file to make sure it has real source code, and it sure does.
Perhaps this will help with development. Do you think this is the last piece we need to get it all going? If so, I am ready to go out and buy one!
Thanks for keeping it going.
pekcle
Click to expand...
Click to collapse
yea im extracting it now check some thinks then i will upload or download it with my server im sure i can compile on it alot faster im going to build a twrp on my vm though faster atm then the server cause i have to fix some configs on my server i think
I'll be posting my H1611.STOCK.ROOTED.NOVA.B150.ROM.zip and H1611.B150.Debloated.Rom.zip along with instructions soon
clsA said:
I'll be posting my H1611.STOCK.ROOTED.NOVA.B150.ROM.zip and H1611.B150.Debloated.Rom.zip along with instructions soon
Click to expand...
Click to collapse
i hope to be posting a cooked version of lineage for us now that i have the source it might help me fix bugs that arise
This phone is so sad without custom roms...
yunior597 said:
This phone is so sad without custom roms...
Click to expand...
Click to collapse
It's taking time but it will come. We have a couple devs that are not all that experienced and learning as they go. I'm sure it will be worth the wait.
One thing people forget it's time consuming (especially when you are just learning) and everyone expects it for nothing. The devs do it as a hobby in their free time. If we want an experienced dev and want results, the answer is simple. Get as many people as we can, pool some money together and pay someone with all that knowledge for their time.
Then we would have some custom Roms ASAP... Three XDA members that I know of are working on it and once we have something I hope many of us will donate to thank them for their efforts.
I thought about starting a bounty to collect funds and pay someone. If you really know what you are doing it does not take very long. Say 100 members at $5 a pop, that would get us some pretty good results and what you are asking for
What do you not currently have which you expect to gain from a custom ROM?
yunior597 said:
This phone is so sad without custom roms...
Click to expand...
Click to collapse