Droid Turbo Think Tank
{
"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"
}
The main purpose of this thread is to discuss possible ideas for development and exploitation of the Motorola Droid Turbo. Topics can range from ideas on how to accomplish certain mods as we are trying to bake them into images to ways to flash different files to unlocking the BL. I am by no means an expert and I have some ideas I'd like to share with others on various topics. There is alot of hostility on this board, lets build some community!
__________________________________________________________________________________________________________
I do not however have total knowledge so I lack some skills to know if what I am saying is even possible. I am simply an android enthusiast, technologically inclined individual, and engineering student.
I will start us off: Since we have root permissions would it be possible to just dd a replacement recovery to the recovery partition, or even a modified bootloader. Or is that something R/W would prohibit/ not keep after a reboot? Would we be able to nandroid and restore/ install if we even could get a replacement recovery without the unlocked B/L?
Recovery Image DD:
Code:
dd if=/sdcard/recoveryfile.img of=/dev/block/mmcblk0p36
Here is a list of the partitions along with their name
Code:
[email protected]:/dev/block/platform/msm_sdcc.1 $ ls -al /dev/block/platform/msm_sdcc
.1/by-name
/platform/msm_sdcc.1/by-name <
lrwxrwxrwx root root 1969-12-31 19:00 [COLOR="Blue"]aboot[/COLOR] -> /dev/block/mmcbl
k0p6
lrwxrwxrwx root root 1969-12-31 19:00 [COLOR="blue"]abootBackup[/COLOR] -> /dev/block
/mmcblk0p13
lrwxrwxrwx root root 1969-12-31 19:00 [COLOR="blue"]boot [/COLOR]-> /dev/block/mmcblk
0p35
lrwxrwxrwx root root 1969-12-31 19:00 [COLOR="blue"]cache[/COLOR] -> /dev/block/mmcbl
k0p38
lrwxrwxrwx root root 1969-12-31 19:00 [COLOR="blue"]cid[/COLOR] -> /dev/block/mmcblk0
p25
lrwxrwxrwx root root 1969-12-31 19:00 [COLOR="blue"]clogo[/COLOR] -> /dev/block/mmcbl
k0p28
lrwxrwxrwx root root 1969-12-31 19:00 [COLOR="blue"]ddr[/COLOR] -> /dev/block/mmcblk0
p5
lrwxrwxrwx root root 1969-12-31 19:00 [COLOR="blue"]factorytune1 [/COLOR]-> /dev/bloc
k/mmcblk0p10
lrwxrwxrwx root root 1969-12-31 19:00 [COLOR="blue"]factorytune2 [/COLOR]-> /dev/bloc
k/mmcblk0p37
lrwxrwxrwx root root 1969-12-31 19:00 [COLOR="blue"]kpan [/COLOR]-> /dev/block/mmcblk
0p34
lrwxrwxrwx root root 1969-12-31 19:00 [COLOR="blue"]logo [/COLOR]-> /dev/block/mmcblk
0p27
lrwxrwxrwx root root 1969-12-31 19:00 [COLOR="blue"]logs [/COLOR]-> /dev/block/mmcblk
0p20
lrwxrwxrwx root root 1969-12-31 19:00 [COLOR="blue"]mdm1dhob [/COLOR]-> /dev/block/mm
cblk0p23
lrwxrwxrwx root root 1969-12-31 19:00 [COLOR="blue"]mdm1hob [/COLOR]-> /dev/block/mmc
blk0p22
lrwxrwxrwx root root 1969-12-31 19:00 [COLOR="blue"]mdm1m9kefs1 [/COLOR]-> /dev/block
/mmcblk0p17
lrwxrwxrwx root root 1969-12-31 19:00 [COLOR="blue"]mdm1m9kefs2 [/COLOR]-> /dev/block
/mmcblk0p18
lrwxrwxrwx root root 1969-12-31 19:00 [COLOR="blue"]mdm1m9kefs3 [/COLOR]-> /dev/block
/mmcblk0p31
lrwxrwxrwx root root 1969-12-31 19:00 [COLOR="blue"]mdm1m9kefsc [/COLOR]-> /dev/block
/mmcblk0p32
lrwxrwxrwx root root 1969-12-31 19:00 [COLOR="blue"]misc [/COLOR]-> /dev/block/mmcblk
0p29
lrwxrwxrwx root root 1969-12-31 19:00 [COLOR="blue"]modem [/COLOR]-> /dev/block/mmcbl
k0p1
lrwxrwxrwx root root 1969-12-31 19:00 [COLOR="blue"]padA [/COLOR]-> /dev/block/mmcblk
0p11
lrwxrwxrwx root root 1969-12-31 19:00 [COLOR="blue"]padB [/COLOR]-> /dev/block/mmcblk
0p19
lrwxrwxrwx root root 1969-12-31 19:00 [COLOR="blue"]padC [/COLOR]-> /dev/block/mmcblk
0p30
lrwxrwxrwx root root 1969-12-31 19:00 [COLOR="blue"]pds [/COLOR]-> /dev/block/mmcblk0
p26
lrwxrwxrwx root root 1969-12-31 19:00 [COLOR="blue"]persist [/COLOR]-> /dev/block/mmc
blk0p21
lrwxrwxrwx root root 1969-12-31 19:00 [COLOR="blue"]recovery [/COLOR]-> /dev/block/mm
cblk0p36
lrwxrwxrwx root root 1969-12-31 19:00 [COLOR="blue"]rpm [/COLOR]-> /dev/block/mmcblk0
p7
lrwxrwxrwx root root 1969-12-31 19:00 [COLOR="blue"]rpmBackup [/COLOR]-> /dev/block/m
mcblk0p14
lrwxrwxrwx root root 1969-12-31 19:00 [COLOR="blue"]sbl1 [/COLOR]-> /dev/block/mmcblk
0p2
lrwxrwxrwx root root 1969-12-31 19:00 [COLOR="blue"]sbl1bak [/COLOR]-> /dev/block/mmc
blk0p12
lrwxrwxrwx root root 1969-12-31 19:00 [COLOR="blue"]sdi [/COLOR]-> /dev/block/mmcblk0
p3
lrwxrwxrwx root root 1969-12-31 19:00 [COLOR="blue"]sec [/COLOR]-> /dev/block/mmcblk0
p4
lrwxrwxrwx root root 1969-12-31 19:00 [COLOR="blue"]sp [/COLOR]-> /dev/block/mmcblk0p
24
lrwxrwxrwx root root 1969-12-31 19:00 [COLOR="blue"]ssd [/COLOR]-> /dev/block/mmcblk0
p33
lrwxrwxrwx root root 1969-12-31 19:00 [COLOR="blue"]system [/COLOR]-> /dev/block/mmcb
lk0p39
lrwxrwxrwx root root 1969-12-31 19:00 [COLOR="blue"]tz [/COLOR]-> /dev/block/mmcblk0p
9
lrwxrwxrwx root root 1969-12-31 19:00 [COLOR="blue"]tzBackup [/COLOR]-> /dev/block/mm
cblk0p16
lrwxrwxrwx root root 1969-12-31 19:00 [COLOR="blue"]userdata [/COLOR]-> /dev/block/mm
cblk0p40
lrwxrwxrwx root root 1969-12-31 19:00 [COLOR="blue"]utags [/COLOR]-> /dev/block/mmcbl
k0p8
lrwxrwxrwx root root 1969-12-31 19:00 [COLOR="blue"]utagsBackup [/COLOR]-> /dev/block
/mmcblk0p15
[email protected]:/dev/block/platform/msm_sdcc.1 $
If a more knowledgeable user would comment on this I'd appreciate it!
Which are the imei blocks?
cascade128 said:
Which are the imei blocks?
Click to expand...
Click to collapse
The IMEI is in the utags partition.
Code:
su
dd if="/dev/block/platform/msm_sdcc.1/by-name/utags" of="/sdcard/utags.bin"
Then pull utags.bin off of the internal storage of the device and open it in a hex editor (you need root to copy it to the internal storage)
What about 2nd init? This seems to have been a good solution in the past. I believe this is how Safestrap worked. It used an exploit in a log file to launch 2nd init from the data partition. In this case the system would boot from data and we would presumably have full access. I don't know if the exploit would still work in 4.4.4. This would be the key, but the exploit could be added to a system image and flashed. Safestrap would be awesome, but even a simple 2nd init could work to start. I am just throwing this out there for discussion. This is way outside of my means, but someone else might be able to help.
Harry44 said:
Would we be able to nandroid and restore/ install if we even could get a replacement recovery without the unlocked B/L?
Click to expand...
Click to collapse
To answer your first question, no, dd'ing a new recovery in place wouldn't work. I think wp(write protect) would stop it and even if it doesn't, booting it would fail, as it verifies the signature of the partition it's booting from unless the device is unlocked or an engineering model. For your second question, yes, if you could miraculously perform the act of getting a recovery in there and it boots (emphasis on "and it boots") you *should* be able to backup/restore/install stuff.
r3pwn said:
The IMEI is in the utags partition.
Code:
su
dd if="/dev/block/platform/msm_sdcc.1/by-name/utags" of="/sdcard/utags.bin"
Then pull utags.bin off of the internal storage of the device and open it in a hex editor (you need root to copy it to the internal storage)
Click to expand...
Click to collapse
Thx.
What is utagsBackup.bin? Do i need to change it?
cascade128 said:
Thx.
What is utagsBackup.bin? Do i need to change it?
Click to expand...
Click to collapse
Not sure what your local laws are but check before modifying IMEI.
cascade128 said:
Thx.
What is utagsBackup.bin? Do i need to change it?
Click to expand...
Click to collapse
Erh, I wasn't aware that you wanted to CHANGE your IMEI. I am afraid that I am unable to assist you with that (well, I'm able, I just don't want to because it's illegal).
Harry44 said:
Not sure what your local laws are but check before modifying IMEI.
Click to expand...
Click to collapse
r3pwn said:
Erh, I wasn't aware that you wanted to CHANGE your IMEI. I am afraid that I am unable to assist you with that (well, I'm able, I just don't want to because it's illegal).
Click to expand...
Click to collapse
In our country, you have to register to use the mobile phone brought a passport outside the country due to a ridiculous law. Also you invest 50$ before the bank for this purpose.
That's not all. The passport to be registered abroad in the last 2 months need to be logged in our country. In addition, within the last 2 years it is supposed to be saved to another mobile phone passport...
This transaction is being processed on the IMEI number...
We were so old that we bring to mobile phones from abroad, used condition but in our country we are writing the IMEI number of the phone is registered. However we have to...
Any way we could boot back up an IRC for people who want to throw ideas off eachother a bit quicker, or just a general DT Discuss?
Sareniah said:
Any way we could boot back up an IRC for people who want to throw ideas off eachother a bit quicker, or just a general DT Discuss?
Click to expand...
Click to collapse
This would actually be a good idea. Anyone willing to set it up?
If someone have moto maxx and check files whats changes in unlocking bootloader and try change in droid turbo too.
I have some ideas for bootloader unlock. They're probably really stupid, but bear with me. Like OP, I'm no developer, just an Android enthusiast with basic knowledge of the inner workings.
So the Moto Maxx US (XT1250) and Droid Turbo (XT1254) are essentially the same device, right? They essentially have the same specs, same hardware, software, and they both work on CDMA carriers like Verizon. The only difference is that the Maxx's bootloader is not locked by Verizon. So here are a few ideas pertaining to that.
***NOTE: It has to be the XT1250 variant
Idea A:
1. XT1250 Maxx user uses "fastboot oem get_unlock_data" or goes through WinDroid to get the unlock key
2. Key is given to a Turbo user
3. Turbo user uses "fastboot oem unlock <maxx_key>
4. Profit
Idea B (risky):
1. Turbo user downloads XT1250 system .img
2. User flashes to Turbo using RSDlite or MOFO (not sure which would work better, if at all)
3. Use WinDroid to unlock BL, root, and install a custom recovery
4. Profit
Yes, yes, I know...they are probably bad ideas, but we must consider every possibility!
jake7405 said:
I have some ideas for bootloader unlock. They're probably really stupid, but bear with me. Like OP, I'm no developer, just an Android enthusiast with basic knowledge of the inner workings.
Click to expand...
Click to collapse
These wouldn't work. Good start on ideas, though.
Thanks!
Just a quick n00b question, why wouldnt flashing the xt1250 img work?
Sent from my XT1254
Thank you.
jake7405 said:
Thanks!
Just a quick n00b question, why wouldnt flashing the xt1250 img work?
Sent from my XT1254
Click to expand...
Click to collapse
The phone data itself (IMEI and stuff) is still the same, so the unlock data generated would still be the same, meaning Motorola would still reject it.
Was shown this as potential ways to head towards bl unlock. Leaving it here for greater minds to dissect.
http://manualwire.com/view/19580/
JakeDHS07 said:
Was shown this as potential ways to head towards bl unlock. Leaving it here for greater minds to dissect.
http://manualwire.com/view/19580/
Click to expand...
Click to collapse
Unless I'm mistaken, that would only help with a bootloader bypass. Trust me. Unlocks are better than bypasses.
r3pwn said:
The phone data itself (IMEI and stuff) is still the same, so the unlock data generated would still be the same, meaning Motorola would still reject it.
Click to expand...
Click to collapse
Any way to modify or change it? Also, would this probably end up hard bricking me if I tried?
Related
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.
hi dear members and developers i just want to share the persist data partition of motorola xt1540
this was readed by this way to coolaborate in a solution for bring us the " OEM UNLOCK " option enabled for unlock bootloader on locked devices
here is what i did
here is the parititons map
[email protected]_umts:/ # ls -al /dev/block/platform/msm_sdcc.1/by-name
ls -al /dev/block/platform/msm_sdcc.1/by-name
lrwxrwxrwx root root 1969-12-31 18:16 DDR -> /dev/block/mmcblk0
p3
lrwxrwxrwx root root 1969-12-31 18:16 aboot -> /dev/block/mmcbl
k0p4
lrwxrwxrwx root root 1969-12-31 18:16 abootBackup -> /dev/block
/mmcblk0p11
lrwxrwxrwx root root 1969-12-31 18:16 boot -> /dev/block/mmcblk
0p31
lrwxrwxrwx root root 1969-12-31 18:16 cache -> /dev/block/mmcbl
k0p40
lrwxrwxrwx root root 1969-12-31 18:16 carrier -> /dev/block/mmc
blk0p38
lrwxrwxrwx root root 1969-12-31 18:16 cid -> /dev/block/mmcblk0
p25
lrwxrwxrwx root root 1969-12-31 18:16 clogo -> /dev/block/mmcbl
k0p28
lrwxrwxrwx root root 1969-12-31 18:16 customize -> /dev/block/m
mcblk0p39
lrwxrwxrwx root root 1969-12-31 18:16 dhob -> /dev/block/mmcblk
0p22
lrwxrwxrwx root root 1969-12-31 18:16 frp -> /dev/block/mmcblk0
p17
lrwxrwxrwx root root 1969-12-31 18:16 fsc -> /dev/block/mmcblk0
p24
lrwxrwxrwx root root 1969-12-31 18:16 fsg -> /dev/block/mmcblk0
p23
lrwxrwxrwx root root 1969-12-31 18:16 hob -> /dev/block/mmcblk0
p21
lrwxrwxrwx root root 1969-12-31 18:16 hyp -> /dev/block/mmcblk0
p7
lrwxrwxrwx root root 1969-12-31 18:16 hypBackup -> /dev/block/m
mcblk0p14
lrwxrwxrwx root root 1969-12-31 18:16 keystore -> /dev/block/mm
cblk0p36
lrwxrwxrwx root root 1969-12-31 18:16 kpan -> /dev/block/mmcblk
0p30
lrwxrwxrwx root root 1969-12-31 18:16 logo -> /dev/block/mmcblk
0p27
lrwxrwxrwx root root 1969-12-31 18:16 logs -> /dev/block/mmcblk
0p16
lrwxrwxrwx root root 1969-12-31 18:16 metadata -> /dev/block/mm
cblk0p26
lrwxrwxrwx root root 1969-12-31 18:16 misc -> /dev/block/mmcblk
0p9
lrwxrwxrwx root root 1969-12-31 18:16 modem -> /dev/block/mmcbl
k0p1
lrwxrwxrwx root root 1969-12-31 18:16 modemst1 -> /dev/block/mm
cblk0p19
lrwxrwxrwx root root 1969-12-31 18:16 modemst2 -> /dev/block/mm
cblk0p20
lrwxrwxrwx root root 1969-12-31 18:16 oem -> /dev/block/mmcblk0
p37
lrwxrwxrwx root root 1969-12-31 18:16 padA -> /dev/block/mmcblk
0p10
lrwxrwxrwx root root 1969-12-31 18:16 padB -> /dev/block/mmcblk
0p18
lrwxrwxrwx root root 1969-12-31 18:16 padC -> /dev/block/mmcblk
0p34
lrwxrwxrwx root root 1969-12-31 18:16 persist -> /dev/block/mmc
blk0p29
lrwxrwxrwx root root 1969-12-31 18:16 recovery -> /dev/block/mm
cblk0p32
lrwxrwxrwx root root 1969-12-31 18:16 rpm -> /dev/block/mmcblk0
p5
lrwxrwxrwx root root 1969-12-31 18:16 rpmBackup -> /dev/block/m
mcblk0p12
lrwxrwxrwx root root 1969-12-31 18:16 sbl1 -> /dev/block/mmcblk
0p2
lrwxrwxrwx root root 1969-12-31 18:16 sp -> /dev/block/mmcblk0p
35
lrwxrwxrwx root root 1969-12-31 18:16 ssd -> /dev/block/mmcblk0
p33
lrwxrwxrwx root root 1969-12-31 18:16 system -> /dev/block/mmcb
lk0p41
lrwxrwxrwx root root 1969-12-31 18:16 tz -> /dev/block/mmcblk0p
6
lrwxrwxrwx root root 1969-12-31 18:16 tzBackup -> /dev/block/mm
cblk0p13
lrwxrwxrwx root root 1969-12-31 18:16 userdata -> /dev/block/mm
cblk0p42
lrwxrwxrwx root root 1969-12-31 18:16 utags -> /dev/block/mmcbl
k0p8
lrwxrwxrwx root root 1969-12-31 18:16 utagsBackup -> /dev/block
/mmcblk0p15
[email protected]_umts:/ #
Click to expand...
Click to collapse
since " oem unlock " ability is set on the pesist data partition i read partition using this command
adb shell dd if=/sdcard/unlock.img of=/dev/block/mmcblk0p29
Click to expand...
Click to collapse
all this is based on @playahate post , that talk about nexus 6 & 9 oem set on solution on semibricked devices , if anyone need to test this solucion on semibricked moto g3 xt1540 is invited
hope it helps to anyone
also i still loking for a temp root or full root acces without bootloader unlock , if anyone have this kind of solution please share
Wait....I don't quite understand....does this unlock the bootloader? If so, how do you push it there without unlocking first??
hp420 said:
Wait....I don't quite understand....does this unlock the bootloader? If so, how do you push it there without unlocking first??
Click to expand...
Click to collapse
(I think) in short what this does is enable OEM unlocking found in developer options, if you don't have access which has actually happened to me once before because of the first CAF 6.0 test we had.
The important part is the adb code used I believe.
christopherrrg said:
(I think) in short what this does is enable OEM unlocking found in developer options, if you don't have access which has actually happened to me once before because of the first CAF 6.0 test we had.
The important part is the adb code used I believe.
Click to expand...
Click to collapse
Oh, ok. That makes sense. Thanks!
Hello, can you share with me the hbo dhob & fsc files / partitions only, the one attached has all the partitions on it, thanks
So here we are
Its officialy confirmed
{
"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"
}
Cant wait to create a rom / kernel for This Beast
Who has received it
Itsnot reciveable , just spam them tell them that htc dev didnt publish it yet
Just copy and paste this to them ,, they should know their ota system sucks
We need a download link for HTC desire 820s Dual Sim Software Version 1.14.709.1 Sense 7 , Lolipop 5.0.2 Build as itsn't recievable as OTA " we didn't and will never recive it as kk users " it only come out of the box by luck.
Please publish it . we are stuck at kitkat
There's no way they can send lollipop and Sense 7 OTA. That's about 4 GBs!!!!
---------- Post added at 04:07 PM ---------- Previous post was at 04:04 PM ----------
I've been spamming them the entire week. They are too reluctant to give the source code or OTA
I think going to get refund and reppace this device
Mohamed Yaser said:
I think going to get refund and reppace this device
Click to expand...
Click to collapse
Let me be patient until December
What about battery ,charging 6% / Hour ??
Too slow?
Wait a minute. Isn't a50mldtul desire 820s?
where u got that from
http://www.droidviews.com/list-of-android-device-codenames/
Yeah it is
i think also we are getting a recovery soon
[email protected]_a50ml_dtul:/ $ su
/platform/mtk-msdc.0"This is our chip"/by-name <
lrwxrwxrwx root root 2015-07-08 00:46 boot -> /dev/block/mmcblk0p9
lrwxrwxrwx root root 2015-07-08 00:46 cache -> /dev/block/mmcblk0p20
lrwxrwxrwx root root 2015-07-08 00:46 cota -> /dev/block/mmcblk0p14
lrwxrwxrwx root root 2015-07-08 00:46 dkb -> /dev/block/mmcblk0p6
lrwxrwxrwx root root 2015-07-08 00:46 expdb -> /dev/block/mmcblk0p15
lrwxrwxrwx root root 2015-07-08 00:46 flashinfo -> /dev/block/mmcblk0p22
lrwxrwxrwx root root 2015-07-08 00:46 kb -> /dev/block/mmcblk0p5
lrwxrwxrwx root root 2015-07-08 00:46 lk -> /dev/block/mmcblk0p8
lrwxrwxrwx root root 2015-07-08 00:46 logo -> /dev/block/mmcblk0p13
lrwxrwxrwx root root 2015-07-08 00:46 metadata -> /dev/block/mmcblk0p18
lrwxrwxrwx root root 2015-07-08 00:46 nvram -> /dev/block/mmcblk0p2
lrwxrwxrwx root root 2015-07-08 00:46 para -> /dev/block/mmcblk0p12
lrwxrwxrwx root root 2015-07-08 00:46 proinfo -> /dev/block/mmcblk0p1
lrwxrwxrwx root root 2015-07-08 00:46 protect1 -> /dev/block/mmcblk0p3
lrwxrwxrwx root root 2015-07-08 00:46 protect2 -> /dev/block/mmcblk0p4
lrwxrwxrwx root root 2015-07-08 00:46 recovery -> /dev/block/mmcblk0p10
lrwxrwxrwx root root 2015-07-08 00:46 seccfg -> /dev/block/mmcblk0p7
lrwxrwxrwx root root 2015-07-08 00:46 secro -> /dev/block/mmcblk0p11
lrwxrwxrwx root root 2015-07-08 00:46 system -> /dev/block/mmcblk0p19
lrwxrwxrwx root root 2015-07-08 00:46 tee1 -> /dev/block/mmcblk0p16
lrwxrwxrwx root root 2015-07-08 00:46 tee2 -> /dev/block/mmcblk0p17
lrwxrwxrwx root root 2015-07-08 00:46 userdata -> /dev/block/mmcblk0p21
[email protected]_a50ml_dtul:/ #
http://forum.xda-developers.com/desire-820/orig-development/desire-820-models-msm-chipset-twrp-2-8-t3147260/page4
http://forum.xda-developers.com/des...20-models-msm-chipset-twrp-2-8-t3147260/page4
The kernel source code for a50mldtul is at htcdev
There's this one I flashed. Seems to be working fine. It can backup. Haven't tried restoring or installing zip though.
CWM
Isn't this the greatest breakthrough for our phone
Oh , May be i will start work on a rom
PS ,, Give me a link to our source code and How u did unlock the bl
I'm not sure how I unlocked it. I remember trying to unlock it at htcdev.com and using kingo htc bootloader unlock but I wasn't successfull. I don't know maybe it's still locked.
At htcdev there are kernel source codes with a50mldtul name under Desire 820 dual sim. But again I'm not if sure they are for Desire 820s.
You can get the CWM I flashed here
http://www.4shared.com/rar/SM6wcBzyce/CWM_820s.html
It's fully working for me
Gibz97 said:
I'm not sure how I unlocked it. I remember trying to unlock it at htcdev.com and using kingo htc bootloader unlock but I wasn't successfull. I don't know maybe it's still locked.
At htcdev there are kernel source codes with a50mldtul name under Desire 820 dual sim. But again I'm not if sure they are for Desire 820s.
You can get the CWM I flashed here
http://www.4shared.com/rar/SM6wcBzyce/CWM_820s.html
It's fully working for me
Click to expand...
Click to collapse
who made this cwm
I found it here
http://forum.xda-developers.com/and...6732-64bit-t2998980/post61761125#post61761125
Pretty old thread
---------- Post added at 12:19 AM ---------- Previous post was at 12:18 AM ----------
Mohamed Yaser said:
who made this cwm
Click to expand...
Click to collapse
Have you tried it?
Gibz97 said:
I found it here
http://forum.xda-developers.com/and...6732-64bit-t2998980/post61761125#post61761125
Pretty old thread
---------- Post added at 12:19 AM ---------- Previous post was at 12:18 AM ----------
Have you tried it?
Click to expand...
Click to collapse
i didn't find the kernel source ??
no not yet
This might seem like a newbie question but this isn't the case.
I already know Titanium backup exists and I have been using it for years. However a few months back I suffered from the ''infamous brick'' seen everywhere on this thread caused by the unofficial CM13 ROM.
This brick corrupted everything on my phone (EFS Partition, etc) and the ONLY thing i could ever boot into was the recovery.
2 months and $150 later in repairs (literally everyone failed to fix it software-side) I learned my lesson
I need to back up my entire phone incase something like this happens again. What app should I use, and what should I back up?
Thanks
Do a nandroid backup from the recovery
Nortabun said:
This might seem like a newbie question but this isn't the case.
I already know Titanium backup exists and I have been using it for years. However a few months back I suffered from the ''infamous brick'' seen everywhere on this thread caused by the unofficial CM13 ROM.
This brick corrupted everything on my phone (EFS Partition, etc) and the ONLY thing i could ever boot into was the recovery.
2 months and $150 later in repairs (literally everyone failed to fix it software-side) I learned my lesson
I need to back up my entire phone incase something like this happens again. What app should I use, and what should I back up?
Thanks
Click to expand...
Click to collapse
Here is a snapshot of everything on the entire phone.
[email protected]:/dev/block/platform/15540000.dwmmc0/by-name # ls -la
ls -la
lrwxrwxrwx root root 2015-12-31 13:08 BOOT -> /dev/block/mmcblk0p9
lrwxrwxrwx root root 2015-12-31 13:08 BOTA0 -> /dev/block/mmcblk0p1
lrwxrwxrwx root root 2015-12-31 13:08 BOTA1 -> /dev/block/mmcblk0p2
lrwxrwxrwx root root 2015-12-31 13:08 CACHE -> /dev/block/mmcblk0p19
lrwxrwxrwx root root 2015-12-31 13:08 CARRIER -> /dev/block/mmcblk0p7
lrwxrwxrwx root root 2015-12-31 13:08 CDMA-RADIO -> /dev/block/mmcblk0p12
lrwxrwxrwx root root 2015-12-31 13:08 DNT -> /dev/block/mmcblk0p15
lrwxrwxrwx root root 2015-12-31 13:08 EFS -> /dev/block/mmcblk0p3
lrwxrwxrwx root root 2015-12-31 13:08 HIDDEN -> /dev/block/mmcblk0p20
lrwxrwxrwx root root 2015-12-31 13:08 OTA -> /dev/block/mmcblk0p11
lrwxrwxrwx root root 2015-12-31 13:08 PARAM -> /dev/block/mmcblk0p8
lrwxrwxrwx root root 2015-12-31 13:08 PERSDATA -> /dev/block/mmcblk0p16
lrwxrwxrwx root root 2015-12-31 13:08 RADIO -> /dev/block/mmcblk0p13
lrwxrwxrwx root root 2015-12-31 13:08 RECOVERY -> /dev/block/mmcblk0p10
lrwxrwxrwx root root 2015-12-31 13:08 RESERVED2 -> /dev/block/mmcblk0p17
lrwxrwxrwx root root 2015-12-31 13:08 SYSTEM -> /dev/block/mmcblk0p18
lrwxrwxrwx root root 2015-12-31 13:08 TOMBSTONES -> /dev/block/mmcblk0p14
lrwxrwxrwx root root 2015-12-31 13:08 USERDATA -> /dev/block/mmcblk0p21
lrwxrwxrwx root root 2015-12-31 13:08 m9kefs1 -> /dev/block/mmcblk0p4
lrwxrwxrwx root root 2015-12-31 13:08 m9kefs2 -> /dev/block/mmcblk0p5
lrwxrwxrwx root root 2015-12-31 13:08 m9kefs3 -> /dev/block/mmcblk0p6
Option 1 Command line:
Quick and easy way to backup /system
dd if=/dev/block/mmcblk0p18 of=/sdcard/system.img bs=4096
Quick and easy way to backup the kernel
dd if=/dev/block/mmcblk0p9 of=/sdcard/boot.img bs=4096
Quick and easy way to back up EFS
dd if=/dev/block/mmcblk0p3 of=/sdcard/efs.img bs=4096
Quick and easy way to back up Radio
dd if=/dev/block/mmcblk0p13 of=/sdcard/radio.img bs=4096
Quick and easy way to back up Recovery
dd if=/dev/block/mmcblk0p10 of=/sdcard/recovery.img bs=4096
Create a directory on your machine. C:\Phonerecovery
Copy all those files from /sdcard to that directory.
With those images you can build a ODIN flash file
Using Cygwin or a Linux machine: tar -H ustar -c boot.img kernel.img recovery.img system.img > Unf*ckMyNote4.tar
Using ODIN to restore stock firmware usually will unf*ck a CM flashed phone. Keeping one handy from a provider of stock Samsung Note 4 firmware is also a good thing.
Option 2:
Custom recovery like CWM / TWRP installed on your phone
Since you were able to reboot into recovery having a TWRP backup probably would have saved you.
{
"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"
}
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