{
"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"
}
These are for the H815 variant only. Files are from software version 10A.
Included below: a stock rom.. a stock rooted rom.. and flashable boot, modem and bootloader zips.
Requirements:
You must have TWRP 2.8.7+ installed to use these files. Thanks to Dees_Troy as always for that. And, of course, you must have your bootloader unlocked for TWRP to work. Please do not ask if "model x" is supported... did you unlock via LG's official unlock tool? Yes? then you can use it. No? then you can't.
Downloads:
ROMS:
Your options are 100% stock rom or 100% stock rom + root. No customizations here. Rom is odexed. Zip flashable in TWRP.
LG-H81510A-Flashable.System.Boot.zip
100% stock untouched system/rom and stock boot.img (kernel + dtb + ramdisk).
Not going to upload a rooted image this time... just a waste of space. Easier to just flash stock/untouched rom then flash the SuperSU zip from Chainfire... or just let TWRP root it (when you go to reset to system, if TWRP detects no root it will ask if you want TWRP to root you).
Latest SuperSu zip can always be downloaded here - download.chainfire.eu/supersu
Thanks as always to Chainfire for maintaining SuperSU!
Extras:
TWRP-Flashable stock extras. If you ever need to restore the modem, boot or bootloader.. these are the files that make it easy.
LG-H81510A-Flashable.Modem.zip
This is a flashable stock 10A modem.
LG-H81510A-Flashable.Boot.zip
This is a flashable stock 10A boot.img. Boot.img contains kernel + dtb + ramdisk.
LG-H81510A-Flashable.Bootloader.zip
This is a flashable stock 10A bootloader. It contains aboot, factory, hyp, laf, rpm, sbl1, sdi, sec and tz.
Also, all stock images are available from @wolfgart's CODEFIRE DIRECTORY
#TEAMCODEFIRE
Click to expand...
Click to collapse
y u quote OP?
?
Sent from my Nexus 6 using Tapatalk
Yo
Sent from my LG G4
Second ROM is on the way..
So, with this ROM we can return the phone to locked/stock bootloader? What does the 10A stand for? Sorry I haven't ROM'ed in a few years (since a few HTC's ago), been just rooting for the last few years and using Nova Launcher. Is this still only for H815 EU's (which are able to have the BL unlocked via LG) or is this for all H815's?
thank you sir
TWRP-Link dont work on me.
But if it is the modified with simlink from @Wolfgart, than recovery works (backup/recovery), tested much times, all fine
http://techerrata.com/dees_troy/p1.img
Example: tried Xposed arm64 = bootloop! !!! dont test Xposed yet!!! all testers got bootloop
--> recovery and back in the world
most know, BUT FIRST after getting unlock and TWRP --> do a NANDROID!!! and TEST it!!!
Since most of us don't have root, me including(H815-L) i wonder if we somehow can install it via LG Flash tool, like a KDZ file?
i messed up..
its flashing of "LG-H81510A-Flashable.RootedSystem.Boot.zip" enough, or do i need to flash modem, bootloader too
masze said:
i messed up..
its flashing of "LG-H81510A-Flashable.RootedSystem.Boot.zip" enough, or do i need to flash modem, bootloader too
Click to expand...
Click to collapse
if you just have all other partitions stock and cleaned you only have to flash "LG-H81510A-Flashable.RootedSystem.Boot.zip" (system and boot img included).
wolfgart said:
if you just have all other partitions stock and cleaned you only have to flash "LG-H81510A-Flashable.RootedSystem.Boot.zip" (system and boot img included).
Click to expand...
Click to collapse
its totally wiped and erased.. nothing!!
im reach twrp thru Hard reset..
masze said:
its totally wiped and erased.. nothing!!
Click to expand...
Click to collapse
mhh ?
which is your situation now. It's not clear reading your post.
wolfgart said:
mhh ?
which is your situation now. It's not clear reading your post.
Click to expand...
Click to collapse
not booting, but i can get into twrp via hard reset button comb.. so im able to flash
(i know this is a f***** mess)
do think i can rescue my phone?
do i need to flash more files you think..
system, boot, modem and bootloader!! in that order?
masze said:
not booting, but i can get into twrp via hard reset button comb.. so im able to flash
Click to expand...
Click to collapse
ah ok.
so upload in your sdcard :
LG-H81510A-Flashable.Bootloader.zip
LG-H81510A-Flashable.Modem.zip
LG-H81510A-Flashable.RootedSystem.Boot.zip (if you want stock rooted one or other zip if you want unrooted one)
and flash in this order. Before flash all this job make a system/dalvik/cache wipe from TWRP
after all flash ended reboot your G4
wolfgart said:
ah ok.
so upload in your sdcard :
LG-H81510A-Flashable.Bootloader.zip
LG-H81510A-Flashable.Modem.zip
LG-H81510A-Flashable.RootedSystem.Boot.zip (if you want stock rooted one or other zip if you want unrooted one)
and flash in this order. Before flash all this job make a system/dalvik/cache wipe from TWRP
Click to expand...
Click to collapse
i love you! thanks bro
Can i send you a donation?
---------- Post added at 10:05 AM ---------- Previous post was at 09:58 AM ----------
ok, here it goes! all files on sd.
im report back, how it goes!
EDIT:
Fail to flash bootloader!
E:error executing updater binare in zip LG-H81510A-Flashable.bootloader.zip
EDIT2:
Skipped to flash bootloader.. flashed RootedSystem.Boot and modem...
and my phone booted up!!!!
YES!!!!!!
can give a detailed instructions on what to do? too scared i might missed on something that could potentially brick my phone
Sent from my LG-H815 using Tapatalk 2
@wolfgart
Could you list partition of H815 EU to me ? Maybe I will devs adb tools for LGG4 like LGG2.
ll /dev/block/platform/soc.0/by-name
Did you do this rom with a TWRP backup or do you have the official KDZ file? I formatted system partition, so no more recovery or OS and I can't us ADB
somboons said:
@wolfgart
Could you list partition of H815 EU to me ? Maybe I will devs adb tools for LGG4 like LGG2.
ll /dev/block/platform/soc.0/by-name
Click to expand...
Click to collapse
just done on the first day....
http://pastebin.com/7jJT96Rn
Make attention that on booted OS you can see platform name as : f9824900.sdhci
Accessing adb shell from TWRP Recovery you will have platform's name as : soc.0
wolfgart said:
just done on the first day....
http://pastebin.com/7jJT96Rn
Make attention that on booted OS you can see platform name as : f9824900.sdhci
Accessing adb shell from TWRP Recovery you will have platform's name as : soc.0
Click to expand...
Click to collapse
Thank you.like H818P
ll /dev/block/platform/f9824900.sdhci/by-name
lrwxrwxrwx root root 2015-01-09 15:04 DDR -> /dev/block/mmcblk0p30
lrwxrwxrwx root root 2015-01-09 15:04 aboot -> /dev/block/mmcblk0p8
lrwxrwxrwx root root 2015-01-09 15:04 abootbak -> /dev/block/mmcblk0p14
lrwxrwxrwx root root 2015-01-09 15:04 apdp -> /dev/block/mmcblk0p18
lrwxrwxrwx root root 2015-01-09 15:04 boot -> /dev/block/mmcblk0p38
lrwxrwxrwx root root 2015-01-09 15:04 cache -> /dev/block/mmcblk0p49
lrwxrwxrwx root root 2015-01-09 15:04 cust -> /dev/block/mmcblk0p48
lrwxrwxrwx root root 2015-01-09 15:04 devinfo -> /dev/block/mmcblk0p17
lrwxrwxrwx root root 2015-01-09 15:04 dpo -> /dev/block/mmcblk0p20
lrwxrwxrwx root root 2015-01-09 15:04 drm -> /dev/block/mmcblk0p40
lrwxrwxrwx root root 2015-01-09 15:04 eksst -> /dev/block/mmcblk0p33
lrwxrwxrwx root root 2015-01-09 15:04 encrypt -> /dev/block/mmcblk0p32
lrwxrwxrwx root root 2015-01-09 15:04 factory -> /dev/block/mmcblk0p43
lrwxrwxrwx root root 2015-01-09 15:04 fota -> /dev/block/mmcblk0p44
lrwxrwxrwx root root 2015-01-09 15:04 fsc -> /dev/block/mmcblk0p27
lrwxrwxrwx root root 2015-01-09 15:04 fsg -> /dev/block/mmcblk0p26
lrwxrwxrwx root root 2015-01-09 15:04 grow -> /dev/block/mmcblk0p51
lrwxrwxrwx root root 2015-01-09 15:04 hyp -> /dev/block/mmcblk0p6
lrwxrwxrwx root root 2015-01-09 15:04 hypbak -> /dev/block/mmcblk0p12
lrwxrwxrwx root root 2015-01-09 15:04 keystore -> /dev/block/mmcblk0p29
lrwxrwxrwx root root 2015-01-09 15:04 laf -> /dev/block/mmcblk0p37
lrwxrwxrwx root root 2015-01-09 15:04 limits -> /dev/block/mmcblk0p16
lrwxrwxrwx root root 2015-01-09 15:04 misc -> /dev/block/mmcblk0p22
lrwxrwxrwx root root 2015-01-09 15:04 modem -> /dev/block/mmcblk0p1
lrwxrwxrwx root root 2015-01-09 15:04 modemst1 -> /dev/block/mmcblk0p24
lrwxrwxrwx root root 2015-01-09 15:04 modemst2 -> /dev/block/mmcblk0p25
lrwxrwxrwx root root 2015-01-09 15:04 mpt -> /dev/block/mmcblk0p42
lrwxrwxrwx root root 2015-01-09 15:04 msadp -> /dev/block/mmcblk0p19
lrwxrwxrwx root root 2015-01-09 15:04 persist -> /dev/block/mmcblk0p23
lrwxrwxrwx root root 2015-01-09 15:04 persistent -> /dev/block/mmcblk0p35
lrwxrwxrwx root root 2015-01-09 15:04 pmic -> /dev/block/mmcblk0p2
lrwxrwxrwx root root 2015-01-09 15:04 pmicbak -> /dev/block/mmcblk0p10
lrwxrwxrwx root root 2015-01-09 15:04 raw_resources -> /dev/block/mmcblk0p45
lrwxrwxrwx root root 2015-01-09 15:04 raw_resourcesbak -> /dev/block/mmcblk0p46
lrwxrwxrwx root root 2015-01-09 15:04 rct -> /dev/block/mmcblk0p34
lrwxrwxrwx root root 2015-01-09 15:04 recovery -> /dev/block/mmcblk0p39
lrwxrwxrwx root root 2015-01-09 15:04 rpm -> /dev/block/mmcblk0p7
lrwxrwxrwx root root 2015-01-09 15:04 rpmbak -> /dev/block/mmcblk0p13
lrwxrwxrwx root root 2015-01-09 15:04 sbl1 -> /dev/block/mmcblk0p3
lrwxrwxrwx root root 2015-01-09 15:04 sbl1bak -> /dev/block/mmcblk0p9
lrwxrwxrwx root root 2015-01-09 15:04 sdi -> /dev/block/mmcblk0p5
lrwxrwxrwx root root 2015-01-09 15:04 sdibak -> /dev/block/mmcblk0p15
lrwxrwxrwx root root 2015-01-09 15:04 sec -> /dev/block/mmcblk0p31
lrwxrwxrwx root root 2015-01-09 15:04 sns -> /dev/block/mmcblk0p41
lrwxrwxrwx root root 2015-01-09 15:04 spare1 -> /dev/block/mmcblk0p21
lrwxrwxrwx root root 2015-01-09 15:04 spare2 -> /dev/block/mmcblk0p36
lrwxrwxrwx root root 2015-01-09 15:04 ssd -> /dev/block/mmcblk0p28
lrwxrwxrwx root root 2015-01-09 15:04 system -> /dev/block/mmcblk0p47
lrwxrwxrwx root root 2015-01-09 15:04 tz -> /dev/block/mmcblk0p4
lrwxrwxrwx root root 2015-01-09 15:04 tzbak -> /dev/block/mmcblk0p11
lrwxrwxrwx root root 2015-01-09 15:04 userdata -> /dev/block/mmcblk0p50
[email protected]:/ $
Click to expand...
Click to collapse
Related
I want to know if anyone could share the content of this file. I tried looking at the fstab and translate it to the file but I haven't got it to work and the sgs4mini isn't supported by kitchen (but many people have made rom flashables for the mini, although I'm not sure if using the kitchen). Could anyone provide us one?
Which model? I9190, I9192 or I9195?
ladislav.heller said:
Which model? I9190, I9192 or I9195?
Click to expand...
Click to collapse
Sorry, I forgot to add that, it's I9190. Although having them all in one post would be really helpful to anyone needing one in the future for another version of the phone.
rpgdev said:
Sorry, I forgot to add that, it's I9190. Although having them all in one post would be really helpful to anyone needing one in the future for another version of the phone.
Click to expand...
Click to collapse
Send me the output of command:
ls -la /dev/block/platform/msm_sdcc.1/by-name
ladislav.heller said:
Send me the output of command:
ls -la /dev/block/platform/msm_sdcc.1/by-name
Click to expand...
Click to collapse
It wasn't clear where so I did it on my cm installation:
Code:
lrwxrwxrwx root root 2014-04-18 23:56 aboot -> /dev/block/mmcblk0p5
lrwxrwxrwx root root 2014-04-18 23:56 backup -> /dev/block/mmcblk0p16
lrwxrwxrwx root root 2014-04-18 23:56 boot -> /dev/block/mmcblk0p13
lrwxrwxrwx root root 2014-04-18 23:56 cache -> /dev/block/mmcblk0p22
lrwxrwxrwx root root 2014-04-18 23:56 efs -> /dev/block/mmcblk0p10
lrwxrwxrwx root root 2014-04-18 23:56 fota -> /dev/block/mmcblk0p15
lrwxrwxrwx root root 2014-04-18 23:56 fsg -> /dev/block/mmcblk0p17
lrwxrwxrwx root root 2014-04-18 23:56 hidden -> /dev/block/mmcblk0p23
lrwxrwxrwx root root 2014-04-18 23:56 modem -> /dev/block/mmcblk0p1
lrwxrwxrwx root root 2014-04-18 23:56 modemst1 -> /dev/block/mmcblk0p11
lrwxrwxrwx root root 2014-04-18 23:56 modemst2 -> /dev/block/mmcblk0p12
lrwxrwxrwx root root 2014-04-18 23:56 pad -> /dev/block/mmcblk0p8
lrwxrwxrwx root root 2014-04-18 23:56 param -> /dev/block/mmcblk0p9
lrwxrwxrwx root root 2014-04-18 23:56 persdata -> /dev/block/mmcblk0p20
lrwxrwxrwx root root 2014-04-18 23:56 persist -> /dev/block/mmcblk0p19
lrwxrwxrwx root root 2014-04-18 23:56 recovery -> /dev/block/mmcblk0p14
lrwxrwxrwx root root 2014-04-18 23:56 rpm -> /dev/block/mmcblk0p6
lrwxrwxrwx root root 2014-04-18 23:56 sbl1 -> /dev/block/mmcblk0p2
lrwxrwxrwx root root 2014-04-18 23:56 sbl2 -> /dev/block/mmcblk0p3
lrwxrwxrwx root root 2014-04-18 23:56 sbl3 -> /dev/block/mmcblk0p4
lrwxrwxrwx root root 2014-04-18 23:56 ssd -> /dev/block/mmcblk0p18
lrwxrwxrwx root root 2014-04-18 23:56 system -> /dev/block/mmcblk0p21
lrwxrwxrwx root root 2014-04-18 23:56 tz -> /dev/block/mmcblk0p7
lrwxrwxrwx root root 2014-04-18 23:56 userdata -> /dev/block/mmcblk0p24
rpgdev said:
It wasn't clear where so I did it on my cm installation:
Code:
lrwxrwxrwx root root 2014-04-18 23:56 aboot -> /dev/block/mmcblk0p5
lrwxrwxrwx root root 2014-04-18 23:56 backup -> /dev/block/mmcblk0p16
lrwxrwxrwx root root 2014-04-18 23:56 boot -> /dev/block/mmcblk0p13
lrwxrwxrwx root root 2014-04-18 23:56 cache -> /dev/block/mmcblk0p22
lrwxrwxrwx root root 2014-04-18 23:56 efs -> /dev/block/mmcblk0p10
lrwxrwxrwx root root 2014-04-18 23:56 fota -> /dev/block/mmcblk0p15
lrwxrwxrwx root root 2014-04-18 23:56 fsg -> /dev/block/mmcblk0p17
lrwxrwxrwx root root 2014-04-18 23:56 hidden -> /dev/block/mmcblk0p23
lrwxrwxrwx root root 2014-04-18 23:56 modem -> /dev/block/mmcblk0p1
lrwxrwxrwx root root 2014-04-18 23:56 modemst1 -> /dev/block/mmcblk0p11
lrwxrwxrwx root root 2014-04-18 23:56 modemst2 -> /dev/block/mmcblk0p12
lrwxrwxrwx root root 2014-04-18 23:56 pad -> /dev/block/mmcblk0p8
lrwxrwxrwx root root 2014-04-18 23:56 param -> /dev/block/mmcblk0p9
lrwxrwxrwx root root 2014-04-18 23:56 persdata -> /dev/block/mmcblk0p20
lrwxrwxrwx root root 2014-04-18 23:56 persist -> /dev/block/mmcblk0p19
lrwxrwxrwx root root 2014-04-18 23:56 recovery -> /dev/block/mmcblk0p14
lrwxrwxrwx root root 2014-04-18 23:56 rpm -> /dev/block/mmcblk0p6
lrwxrwxrwx root root 2014-04-18 23:56 sbl1 -> /dev/block/mmcblk0p2
lrwxrwxrwx root root 2014-04-18 23:56 sbl2 -> /dev/block/mmcblk0p3
lrwxrwxrwx root root 2014-04-18 23:56 sbl3 -> /dev/block/mmcblk0p4
lrwxrwxrwx root root 2014-04-18 23:56 ssd -> /dev/block/mmcblk0p18
lrwxrwxrwx root root 2014-04-18 23:56 system -> /dev/block/mmcblk0p21
lrwxrwxrwx root root 2014-04-18 23:56 tz -> /dev/block/mmcblk0p7
lrwxrwxrwx root root 2014-04-18 23:56 userdata -> /dev/block/mmcblk0p24
Click to expand...
Click to collapse
Attached...
ladislav.heller said:
Attached...
Click to expand...
Click to collapse
It worked thank you! Your script's content is very different from the other galaxy files included in the kitchen tho I would have never guessed!
I could flash the rom and it booted (although it took a long time even after the third boot up) and the wifi didn't work even though I have flashed the same (but stock) rom with Odin and everything works just fine since it's the one my phone came with originally. The thread main topic is solved tho, thanks!
[OTA/RECOVERY/HBOOT/RUUS/FIRMWARE/DUMPS] T-Mobile HTC M8 - AndroidFileHost & How Tos
IF SOMEONE IS INTERESTED IN TAKING OVER THIS THREAD CONTACT ME I NO LONGER HAVE A M8
{
"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"
}
**ALL FILES ARE USE AT YOUR OWN RISK!**
All Files Are Untouched Stock
**CLICK GROUP TITLE FOR FOLDER**
OTA's:
Android 4.4.3 - 2.22.531.5 coming from 1.57.531.7
Android 4.4.3 - 2.22.531.6 coming from 2.22.531.5
Android 4.4.4 - 3.32.531.2 coming from 2.22.531.6
Stock Firmwares:
Firmware - 2.22.531.5
Stock H-boot (All Hboots include a MD5 file) [Make sure to unzip do not flash zip.]:
Non IMG:
3.16.0.0000 - Android 4.4.2 - 1.57.531.7
3.18.0.0000 - Android 4.4.3 - 2.22.531.5
3.19.0.0000 - Android 4.4.4 - 3.32.531.2
IMG:
3.16.0.0000 - Android 4.4.2 - 1.57.531.7
3.18.0.0000 - Android 4.4.3 - 2.22.531.5
3.19.0.0000 - Android 4.4.4 - 3.32.531.2
Recoveries:
Stock Recovery - 1.12.531.19
Stock Recovery - 1.57.531.7
Stock Recovery - 3.32.531.2
RUUS (EXE):
TMOUS_1.57.531.7
TMOUS_2.22.531.5
Having issues? RUU won't load?
Make Sure To Have VC REDIST 2005, 2008, and 2010 Installed
RUUS (ZIP):
TMOUS_1.57.531.7-rom.zip
TMOUS_2.22.531.5-rom.zip
Stock Dumps:
1.57.531.7-System.img
2.22.531.5-System.img
3.32.531.2 - System.img
Stock TWRP Nandroid Backups: COMING SOON
Android 4.4.2 - 1.57.531.7
Android 4.4.3 - 2.22.531.5
Android 4.4.3 - 2.22.531.6
How tos:
Backup Hboot (MUST HAVE ROOT):
To back up hboot use the following code in cmd prompt:
Code:
adb shell
su
dd if=/dev/block/mmcblk0p11 of=/sdcard/mmcblk0p11
This will back up your hboot to your internal sdcard.
If you want a hboot image use this:
Code:
adb shell
su
dd if=/dev/block/mmcblk0p11 of=/sdcard/mmcblk0p11.img
Restore Hboot backup from either booted inside Android or from Recovery:
BEFORE FLASHING MAKE SURE TO CHECK MD5 IF YOU DOWNLOADED ONE OF MY FILES!
Make sure the backup hboot is on your internal sdcard and then issue this command in cmd prompt:
Code:
adb shell
su
dd if=/sdcard/mmcblk0p11 of=/dev/block/mmcblk0p11
Next run this code to make sure it flashed correctly if it says they differ DO NOT REBOOT!
Code:
diff /sdcard/mmcblk0p11 /dev/block/mmcblk0p11
If you use a .img run this:
Code:
adb shell
su
dd if=/sdcard/mmcblk0p11 of=/dev/block/mmcblk0p11.img
And just like the other one run this:
if it says they differ DO NOT REBOOT!
Code:
diff /sdcard/mmcblk0p11 /dev/block/mmcblk0p11.img
Are you S-ON?
***IF YOU ARE S-ON THEY WILL DIFFER CAUSE YOU CAN"T FLASH THESE***
HTC M8 Partition Information
lrwxrwxrwx root root 2014-09-30 00:08 adsp -> /dev/block/mmcblk0p16
lrwxrwxrwx root root 2014-09-30 00:08 board_info -> /dev/block/mmcblk0p3
lrwxrwxrwx root root 2014-09-30 00:08 boot -> /dev/block/mmcblk0p42
lrwxrwxrwx root root 2014-09-30 00:08 cache -> /dev/block/mmcblk0p46
lrwxrwxrwx root root 2014-09-30 00:08 carrier -> /dev/block/mmcblk0p37
lrwxrwxrwx root root 2014-09-30 00:08 cdma_record -> /dev/block/mmcblk0p33
lrwxrwxrwx root root 2014-09-30 00:08 cir_img -> /dev/block/mmcblk0p40
lrwxrwxrwx root root 2014-09-30 00:08 control -> /dev/block/mmcblk0p30
lrwxrwxrwx root root 2014-09-30 00:08 custdata -> /dev/block/mmcblk0p22
lrwxrwxrwx root root 2014-09-30 00:08 ddr -> /dev/block/mmcblk0p14
lrwxrwxrwx root root 2014-09-30 00:08 debug_config -> /dev/block/mmcblk0p28
lrwxrwxrwx root root 2014-09-30 00:08 devlog -> /dev/block/mmcblk0p39
lrwxrwxrwx root root 2014-09-30 00:08 dsps -> /dev/block/mmcblk0p15
lrwxrwxrwx root root 2014-09-30 00:08 extra -> /dev/block/mmcblk0p32
lrwxrwxrwx root root 2014-09-30 00:08 fataldevlog -> /dev/block/mmcblk0p27
lrwxrwxrwx root root 2014-09-30 00:08 fsc -> /dev/block/mmcblk0p34
lrwxrwxrwx root root 2014-09-30 00:08 fsg -> /dev/block/mmcblk0p19
lrwxrwxrwx root root 2014-09-30 00:08 hboot -> /dev/block/mmcblk0p11
lrwxrwxrwx root root 2014-09-30 00:08 local -> /dev/block/mmcblk0p31
lrwxrwxrwx root root 2014-09-30 00:08 mfg -> /dev/block/mmcblk0p5
lrwxrwxrwx root root 2014-09-30 00:08 misc -> /dev/block/mmcblk0p24
lrwxrwxrwx root root 2014-09-30 00:08 modem_st1 -> /dev/block/mmcblk0p25
lrwxrwxrwx root root 2014-09-30 00:08 modem_st2 -> /dev/block/mmcblk0p26
lrwxrwxrwx root root 2014-09-30 00:08 pdata -> /dev/block/mmcblk0p29
lrwxrwxrwx root root 2014-09-30 00:08 pg1fs -> /dev/block/mmcblk0p2
lrwxrwxrwx root root 2014-09-30 00:08 pg2fs -> /dev/block/mmcblk0p6
lrwxrwxrwx root root 2014-09-30 00:08 radio -> /dev/block/mmcblk0p20
lrwxrwxrwx root root 2014-09-30 00:08 radio_config -> /dev/block/mmcblk0p18
lrwxrwxrwx root root 2014-09-30 00:08 recovery -> /dev/block/mmcblk0p43
lrwxrwxrwx root root 2014-09-30 00:08 reserve -> /dev/block/mmcblk0p41
lrwxrwxrwx root root 2014-09-30 00:08 reserve_1 -> /dev/block/mmcblk0p4
lrwxrwxrwx root root 2014-09-30 00:08 reserve_2 -> /dev/block/mmcblk0p23
lrwxrwxrwx root root 2014-09-30 00:08 reserve_3 -> /dev/block/mmcblk0p44
lrwxrwxrwx root root 2014-09-30 00:08 rpm -> /dev/block/mmcblk0p8
lrwxrwxrwx root root 2014-09-30 00:08 sbl1 -> /dev/block/mmcblk0p1
lrwxrwxrwx root root 2014-09-30 00:08 sbl1_update -> /dev/block/mmcblk0p7
lrwxrwxrwx root root 2014-09-30 00:08 sdi -> /dev/block/mmcblk0p10
lrwxrwxrwx root root 2014-09-30 00:08 sensor_hub -> /dev/block/mmcblk0p38
lrwxrwxrwx root root 2014-09-30 00:08 skylink -> /dev/block/mmcblk0p36
lrwxrwxrwx root root 2014-09-30 00:08 sp1 -> /dev/block/mmcblk0p12
lrwxrwxrwx root root 2014-09-30 00:08 ssd -> /dev/block/mmcblk0p35
lrwxrwxrwx root root 2014-09-30 00:08 system -> /dev/block/mmcblk0p45
lrwxrwxrwx root root 2014-09-30 00:08 tool_diag -> /dev/block/mmcblk0p21
lrwxrwxrwx root root 2014-09-30 00:08 tz -> /dev/block/mmcblk0p9
lrwxrwxrwx root root 2014-09-30 00:08 userdata -> /dev/block/mmcblk0p47
lrwxrwxrwx root root 2014-09-30 00:08 wcnss -> /dev/block/mmcblk0p17
lrwxrwxrwx root root 2014-09-30 00:08 wifi -> /dev/block/mmcblk0p13
More to come...
Do I have to s-off to flash the Ota? Just go go to stock 1.57 w/ stock recovery. Then just put it on the root of my sdcard and boot into fastboot and let it update right? Since it's a tmobile update and the Id matches. Have have not done it this way in a really long time
billydroid said:
Do I have to s-off to flash the Ota? Just go go to stock 1.57 w/ stock recovery. Then just put it on the root of my sdcard and boot into fastboot and let it update right? Since it's a tmobile update and the Id matches. Have have not done it this way in a really long time
Click to expand...
Click to collapse
You don't need S-off for this all you need to have is a complete stock ROM including the file that bootloader unlock deletes (if you've unlocked bootloader) and the stock recovery. And the easiest way to flash it is going to be to put the OTA on the root of your internal storage boot into stock recovery and when you see just an image of a phone hold the power button and then press up on the volume key and it will give you the option to install from internal storage. (It may be power and volume down if up doesn't work.)
The file unlocking the bootloader deletes? I never knew of such a file
---------- Post added at 08:59 PM ---------- Previous post was at 08:58 PM ----------
If I restore a stock backup. It's that file in there?
billydroid said:
The file unlocking the bootloader deletes? I never knew of such a file
---------- Post added at 08:59 PM ---------- Previous post was at 08:58 PM ----------
If I restore a stock backup. It's that file in there?
Click to expand...
Click to collapse
It deletes the calculator app, flashlight and some other file when you unlock the bootloader I know the stock backups I've used don't have them so I followed this thread to get them back and you should then be full stock.
Restore stock backup, downloaded off xda. Fish stock recovery. Then flash Ota through the stock recovery. Thats it right?
---------- Post added at 09:03 PM ---------- Previous post was at 09:02 PM ----------
I don't need to relock first, correct?
---------- Post added at 09:04 PM ---------- Previous post was at 09:03 PM ----------
Sorry for all the questions. I haven't flashed through a stock recovery in years.
Do I extract this 2.22 zip and then put on the root of the sdcard or leave it as is?
billydroid said:
Restore stock backup, downloaded off xda. Fish stock recovery. Then flash Ota through the stock recovery. Thats it right?
---------- Post added at 09:03 PM ---------- Previous post was at 09:02 PM ----------
I don't need to relock first, correct?
---------- Post added at 09:04 PM ---------- Previous post was at 09:03 PM ----------
Sorry for all the questions. I haven't flashed through a stock recovery in years.
Do I extract this 2.22 zip and then put on the root of the sdcard or leave it as is?
Click to expand...
Click to collapse
That is correct.
DONT extract the 2.22 zip flash it as a zip.
Best way?
What is the best way to flash just the firmware? I am on viper so i think I have everything but the firmware updated.
aaronc_98 said:
What is the best way to flash just the firmware? I am on viper so i think I have everything but the firmware updated.
Click to expand...
Click to collapse
That's been my issue too.. It's a mission to get just the firmware without replacing custom recovery and such... I got a FW from another member that just flashes the firmware and new radio.. Uploading now... You have to flash it through Hboot.
Here you go : https://www.dropbox.com/s/7dqnr7xrsdeyb93/2.22.401.4-noredtext.zip
aaronc_98 said:
What is the best way to flash just the firmware? I am on viper so i think I have everything but the firmware updated.
Click to expand...
Click to collapse
Luigiesin said:
That's been my issue too.. It's a mission to get just the firmware without replacing custom recovery and such... I got a FW from another member that just flashes the firmware and new radio.. Uploading now... You have to flash it through Hboot.
Here you go : https://www.dropbox.com/s/7dqnr7xrsdeyb93/2.22.401.4-noredtext.zip
Click to expand...
Click to collapse
As I recall you will need to go back to complete stock and relock your bootloader. I think you should be able to back up your rom and restore it after you update the firmware and unlock it again.
Badcam3 said:
As I recall you will need to go back to complete stock and relock your bootloader. I think you should be able to back up your rom and restore it after you update the firmware and unlock it again.
Click to expand...
Click to collapse
I haven't tried it yet but from what I know this only updates the necessary partitions without locking the bootloader.. This is just the bare firmware... It won't replace recovery and won't lock bootloader.
Luigiesin said:
I haven't tried it yet but from what I know this only updates the necessary partitions without locking the bootloader.. This is just the bare firmware... It won't replace recovery and won't lock bootloader.
Click to expand...
Click to collapse
You still need to relock the bootloader if you are not S-off if I remember right.
Badcam3 said:
You still need to relock the bootloader if you are not S-off if I remember right.
Click to expand...
Click to collapse
I'm S off actually
Luigiesin said:
I'm S off actually
Click to expand...
Click to collapse
I would go with relocking your bootloader and going the safe way but you can still flash the firmware with S-off it's just not as safe.
http://venomroms.com/firmware_443/
T-Mobile 4.4.3 RUU is now available in the OP under RUUs.
Rom.zip is uploading now!
sapplegater said:
T-Mobile 4.4.3 RUU is now available in the OP under RUUs.
Rom.zip is uploading now!
Click to expand...
Click to collapse
Rom.zip is worthless without decryption
Behold_this said:
Rom.zip is worthless without decryption
Click to expand...
Click to collapse
Its there for backup purposes, also for those who need the zip to flash cause the RUU won't start.
sapplegater said:
Its there for backup purposes, also for those who need the zip to flash cause the RUU won't start.
Click to expand...
Click to collapse
The RUU straight from HTCDEV won't start? I always had to run them from a pure Win 8 or Win 7 install if that's the issue?
Most of the time it's because of the issue I posted in the OP but if they can't that's why I posted the Rom.zip
New OTA in first post!
Ive soft bricked following
http://forum.xda-developers.com/showthread.php?t=3170550
original prewarning instructions for F500L flashing rooted system.img 10w over 10a.
Some have been able to successfully boot their devices using H815 10b kdz but loose or have faint signal strength.
So here's where I need help backing up my modem(s) before hand.
I've tried LG bridge to restore to stock as well as other LG support tools to.no avail.
Any help or suggestions would be great.
EDIT:Ended up flashing H810 10A KDZ, it booted but had the same problems others had with H815 10B, no signal. Flashing the modem.img from F500L backup did not flash back/restore. I ended up trying H811 KDZ and rendered my phone useless. After it completed flashing, it reset to dark screen. Lost download mode. It still has "QHSUSB__BULK", there seems to be a way to recover from here, there are instructions for the Nexus 6 and LG G3, but none for G4. I gave up and bought a replacement H811.
You are probably going to have to wait for a kdz. You might as well try and flash away. As long as you don't f-up download mode, you haven't much to lose.
You should be able to run the below using send_command.exe. This will back modem up to your internal storage. You can't use sdcard because it would have to be mounted.
Code:
dd if=/dev/block/platform/f9824900.sdhci/by-name/modem of=/data/media/0/modem.img
---------- Post added at 10:37 AM ---------- Previous post was at 10:21 AM ----------
To be safe, do your EFS partitions too:
Code:
dd if=/dev/block/platform/f9824900.sdhci/by-name/modemst1 of=/data/media/0/modemst1.img
Code:
dd if=/dev/block/platform/f9824900.sdhci/by-name/modemst2 of=/data/media/0/modemst2.img
tabp0le said:
You are probably going to have to wait for a kdz. You might as well try and flash away. As long as you don't f-up download mode, you haven't much to lose.
You should be able to run the below using send_command.exe. This will back modem up to your internal storage. You can't use sdcard because it would have to be mounted.
Code:
dd if=/dev/block/platform/f9824900.sdhci/by-name/modem of=/data/media/0/modem.img
---------- Post added at 10:37 AM ---------- Previous post was at 10:21 AM ----------
To be safe, do your EFS partitions too:
Code:
dd if=/dev/block/platform/f9824900.sdhci/by-name/modemst1 of=/data/media/0/modemst1.img
Code:
dd if=/dev/block/platform/f9824900.sdhci/by-name/modemst2 of=/data/media/0/modemst2.img
Click to expand...
Click to collapse
I think there are 3 modem partitions, have to search. It was posted here somewhere.
Awesome ill try.
I have a backup of my original system.img as well but dont know if or how to get it back on to internal memory of the phone. Unfortunately did a hard rest to troubleshoot the bootloop.
clockcycle said:
I think there are 3 modem partitions, have to search. It was posted here somewhere.
Awesome ill try.
I have a backup of my original system.img as well but dont know if or how to get it back on to internal memory of the phone. Unfortunately did a hard rest to troubleshoot the bootloop.
Click to expand...
Click to collapse
Unfortunately there is no way to get it back on the phone's internal storage.
I have an idea though. Try backing up ALL your partitions. Then flash KDZ. Then copy old system.img you had backed up to internal storage. Reflash ALL your partitions in DL mode.
Code:
dd if=/dev/block/platform/f9824900.sdhci/by-name/boot of=/data/media/0/boot.img
Code:
dd if=/dev/block/platform/f9824900.sdhci/by-name/recovery of=/data/media/0/recovery.img
Code:
dd if=/dev/block/platform/f9824900.sdhci/by-name/carrier of=/data/media/0/carrier.img
Code:
dd if=/dev/block/platform/f9824900.sdhci/by-name/aboot of=/data/media/0/aboot.img
tabp0le said:
Unfortunately there is no way to get it back on the phone's internal storage.
I have an idea though. Try backing up ALL your partitions. Then flash KDZ. Then copy old system.img you had backed up to internal storage. Reflash ALL your partitions in DL mode.
Click to expand...
Click to collapse
Yea ill do that. Will do some research on here to find that partition list. Then figure out how to back each up.
Once ive got that ill do the test with kdz.
clockcycle said:
Yea ill do that. Will do some research on here to find that partition list. Then figure out how to back each up.
Once ive got that ill do the test with kdz.
Click to expand...
Click to collapse
I just included a few of them with commands in my previous post. You're model is different than mine, so not everything will be the same. But, you will have the same partitions, just slightly different placement. Here is a list of my partitions:
Code:
[email protected]:/ # ls -l /dev/block/platform/f9824900.sdhci/by-name
ls -l /dev/block/platform/f9824900.sdhci/by-name
lrwxrwxrwx root root 2015-02-18 13:46 DDR -> /dev/block/mmcblk0p30
lrwxrwxrwx root root 2015-02-18 13:46 aboot -> /dev/block/mmcblk0p8
lrwxrwxrwx root root 2015-02-18 13:46 abootbak -> /dev/block/mmcblk0p14
lrwxrwxrwx root root 2015-02-18 13:46 apdp -> /dev/block/mmcblk0p18
lrwxrwxrwx root root 2015-02-18 13:46 boot -> /dev/block/mmcblk0p38
lrwxrwxrwx root root 2015-02-18 13:46 cache -> /dev/block/mmcblk0p54
lrwxrwxrwx root root 2015-02-18 13:46 carrier -> /dev/block/mmcblk0p47
lrwxrwxrwx root root 2015-02-18 13:46 devinfo -> /dev/block/mmcblk0p17
lrwxrwxrwx root root 2015-02-18 13:46 dpo -> /dev/block/mmcblk0p20
lrwxrwxrwx root root 2015-02-18 13:46 drm -> /dev/block/mmcblk0p40
lrwxrwxrwx root root 2015-02-18 13:46 eksst -> /dev/block/mmcblk0p33
lrwxrwxrwx root root 2015-02-18 13:46 encrypt -> /dev/block/mmcblk0p32
lrwxrwxrwx root root 2015-02-18 13:46 eri -> /dev/block/mmcblk0p43
lrwxrwxrwx root root 2015-02-18 13:46 factory -> /dev/block/mmcblk0p49
lrwxrwxrwx root root 2015-02-18 13:46 felica -> /dev/block/mmcblk0p48
lrwxrwxrwx root root 2015-02-18 13:46 fota -> /dev/block/mmcblk0p51
lrwxrwxrwx root root 2015-02-18 13:46 fsc -> /dev/block/mmcblk0p27
lrwxrwxrwx root root 2015-02-18 13:46 fsg -> /dev/block/mmcblk0p26
lrwxrwxrwx root root 2015-02-18 13:46 grow -> /dev/block/mmcblk0p56
lrwxrwxrwx root root 2015-02-18 13:46 hyp -> /dev/block/mmcblk0p6
lrwxrwxrwx root root 2015-02-18 13:46 hypbak -> /dev/block/mmcblk0p12
lrwxrwxrwx root root 2015-02-18 13:46 keystore -> /dev/block/mmcblk0p29
lrwxrwxrwx root root 2015-02-18 13:46 laf -> /dev/block/mmcblk0p37
lrwxrwxrwx root root 2015-02-18 13:46 limits -> /dev/block/mmcblk0p16
lrwxrwxrwx root root 2015-02-18 13:46 misc -> /dev/block/mmcblk0p22
lrwxrwxrwx root root 2015-02-18 13:46 modem -> /dev/block/mmcblk0p1
lrwxrwxrwx root root 2015-02-18 13:46 modemst1 -> /dev/block/mmcblk0p24
lrwxrwxrwx root root 2015-02-18 13:46 modemst2 -> /dev/block/mmcblk0p25
lrwxrwxrwx root root 2015-02-18 13:46 mpt -> /dev/block/mmcblk0p42
lrwxrwxrwx root root 2015-02-18 13:46 msadp -> /dev/block/mmcblk0p19
lrwxrwxrwx root root 2015-02-18 13:46 operatorlogging -> /dev/block/mmcblk0p46
lrwxrwxrwx root root 2015-02-18 13:46 persist -> /dev/block/mmcblk0p23
lrwxrwxrwx root root 2015-02-18 13:46 persistent -> /dev/block/mmcblk0p35
lrwxrwxrwx root root 2015-02-18 13:46 pmic -> /dev/block/mmcblk0p2
lrwxrwxrwx root root 2015-02-18 13:46 pmicbak -> /dev/block/mmcblk0p10
lrwxrwxrwx root root 2015-02-18 13:46 raw_resources -> /dev/block/mmcblk0p44
lrwxrwxrwx root root 2015-02-18 13:46 raw_resourcesbak -> /dev/block/mmcblk0p45
lrwxrwxrwx root root 2015-02-18 13:46 rct -> /dev/block/mmcblk0p34
lrwxrwxrwx root root 2015-02-18 13:46 recovery -> /dev/block/mmcblk0p39
lrwxrwxrwx root root 2015-02-18 13:46 rpm -> /dev/block/mmcblk0p7
lrwxrwxrwx root root 2015-02-18 13:46 rpmbak -> /dev/block/mmcblk0p13
lrwxrwxrwx root root 2015-02-18 13:46 sbl1 -> /dev/block/mmcblk0p3
lrwxrwxrwx root root 2015-02-18 13:46 sbl1bak -> /dev/block/mmcblk0p9
lrwxrwxrwx root root 2015-02-18 13:46 sdi -> /dev/block/mmcblk0p5
lrwxrwxrwx root root 2015-02-18 13:46 sdibak -> /dev/block/mmcblk0p15
lrwxrwxrwx root root 2015-02-18 13:46 sec -> /dev/block/mmcblk0p31
lrwxrwxrwx root root 2015-02-18 13:46 sns -> /dev/block/mmcblk0p41
lrwxrwxrwx root root 2015-02-18 13:46 spare1 -> /dev/block/mmcblk0p21
lrwxrwxrwx root root 2015-02-18 13:46 spare2 -> /dev/block/mmcblk0p36
lrwxrwxrwx root root 2015-02-18 13:46 spare3 -> /dev/block/mmcblk0p50
lrwxrwxrwx root root 2015-02-18 13:46 spare4 -> /dev/block/mmcblk0p52
lrwxrwxrwx root root 2015-02-18 13:46 ssd -> /dev/block/mmcblk0p28
lrwxrwxrwx root root 2015-02-18 13:46 system -> /dev/block/mmcblk0p53
lrwxrwxrwx root root 2015-02-18 13:46 tz -> /dev/block/mmcblk0p4
lrwxrwxrwx root root 2015-02-18 13:46 tzbak -> /dev/block/mmcblk0p11
lrwxrwxrwx root root 2015-02-18 13:46 userdata -> /dev/block/mmcblk0p55
---------- Post added at 11:28 AM ---------- Previous post was at 11:18 AM ----------
fyi, you probably don't have to include the spare partitions or userdata. @autoprime could probably tell us there are others that don't need to be included.
tabp0le said:
I just included a few of them with commands in my previous post. You're model is different than mine, so not everything will be the same. But, you will have the same partitions, just slightly different placement. Here is a list of my partitions:
[/COLOR]fyi, you probably don't have to include the spare partitions or userdata. @autoprime could probably tell us there are others that don't need to be included.
Click to expand...
Click to collapse
So let me clarify, by different placement, you mean altho I backup named recovery.img partition, it might actually not be recovery. But as long as I back up the parition regardless of what I name it, and recover it to same partition, it should be ok, correct?
Or are they same named partitions, except physically placed on device in different locations? But as long as I backup up name it should backup regardless of physical location and restore the same?
clockcycle said:
So let me clarify, by different placement, you mean altho I backup named recovery.img partition, it might actually not be recovery. But as long as I back up the parition regardless of what I name it, and recover it to same partition, it should be ok, correct?
Or are they same named partitions, except physically placed on device in different locations? But as long as I backup up name it should backup regardless of physical location and restore the same?
Click to expand...
Click to collapse
They are located on slightly different blocks of memory. The names are the same. If you back it up by name, it doesn't matter what you name the .img file. As long as you restore it to the proper location.
ie.
Code:
dd if=/dev/block/platform/f9824900.sdhci/by-name/recovery of=/data/media/0/recovery.img
could be run as
Code:
dd if=/dev/block/platform/f9824900.sdhci/by-name/recovery of=/data/media/0/blahblahblah.img
as long as you restore blahblahblah.img back to the recovery partition.
tabp0le said:
They are located on slightly different blocks of memory. The names are the same. If you back it up by name, it doesn't matter what you name the .img file. As long as you restore it to the proper location.
(ie. dd if=/dev/block/platform/f9824900.sdhci/by-name/recovery of=/data/media/0/recovery.img could be run as dd if=/dev/block/platform/f9824900.sdhci/by-name/recovery of=/data/media/0/blahblahblah.img
as long as you restore blahblahblah.img back to the recovery partition.
Click to expand...
Click to collapse
Awesome appreciate your help. Ill get on this task
http://csmg.lgmobile.com:9002/csmg/b2c/client/auth_model_check2.jsp?esn=TYPE_YOUR_ESN_HERE
I was hoping this would return a KDZ
@tabp0le
Bad news, phone isn't doing anything when I type commands to back up, it just returns to #
EDIT: I checked /dev/block/platform/ nothing found. I ran dd if=/dev/block/mmcblk0 bs=8192 skip=65536 count=548352 of=/data/media/0/system.img" and it works.
clockcycle said:
@tabp0le
Bad news, phone isn't doing anything when I type commands to back up, it just returns to #
EDIT: I checked /dev/block/platform/ nothing found. I ran dd if=/dev/block/mmcblk0 bs=8192 skip=65536 count=548352 of=/data/media/0/system.img" and it works.
Click to expand...
Click to collapse
Hmm. Try substituting the /dev/block/platform for the actual partition names... (make sure you have the right ones for your device) example below.
For my modem, I would try:
Code:
dd if=/dev/block/mmcblk0p1 of=/data/media/0/modem.img
I think you should only need your modems, system and boot partitions.
tabp0le said:
Hmm. Try substituting the /dev/block/platform for the actual partition names... (make sure you have the right ones for your device) example below.
For my modem, I would try:
Code:
dd if=/dev/block/mmcblk0p1 of=/data/media/0/modem.img
Click to expand...
Click to collapse
Tried that, returns to #, no modem.img in /data/media/0/
Need to figure out how to calculate bs, skip, count ect.. Of each partition. Not sure exact what we absolutely need. Assuming system, boot, modems at minimum.
clockcycle said:
Need to figure out how to calculate bs, skip, count ect.. Of each partition. Not sure exact what we absolutely need. Assuming system, boot, modems at minimum.
Click to expand...
Click to collapse
Yeah, boot and modems is what we need. I don't know how to calculate those numbers. I can't seem to get a response from anyone either. Nothing on Google that I have found either!
dd if=/sdcard/modem.img bs=8192 seek=65536 count=11008 of=/dev/block/mmcblk0p1
kwan788 said:
dd if=/sdcard/modem.img bs=8192 seek=65536 count=11008 of=/dev/block/mmcblk0p1
Click to expand...
Click to collapse
How did you get the numbers?
Sent from my LGLS991 using XDA Free mobile app
kwan788 said:
dd if=/sdcard/modem.img bs=8192 seek=65536 count=11008 of=/dev/block/mmcblk0p1
Click to expand...
Click to collapse
How did you calculate? Need boot.img, modem st1 and st2 bs, skip,count to back up too.
We're so close..
tabp0le said:
How did you get the numbers?
Sent from my LGLS991 using XDA Free mobile app
Click to expand...
Click to collapse
clockcycle said:
How did you calculate? Need boot.img, modem st1 and st2 bs, skip,count to back up too.
We're so close..
Click to expand...
Click to collapse
Another forumer send me the command..and i try flashed..then after reboot stuck at logo.. the forumer say H815 partition size is not same with F500L so will stuck at logo..
{
"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"
}
I wonder if any other variant will boot, work better, or if 815 our only hope.
Firmwares and Partition Table
Partition tables for our device (BLU LIFE ONE X 2016 L00:
Code:
[email protected]_LIFE_ONE_X:/ # ls -l /dev/block/platform/mtk-msdc.0/by-name/
ls -l /dev/block/platform/mtk-msdc.0/by-name/
lrwxrwxrwx root root 2016-05-23 16:48 boot -> /dev/block/mmcblk0p7
lrwxrwxrwx root root 2016-05-23 16:48 cache -> /dev/block/mmcblk0p21
lrwxrwxrwx root root 2016-05-23 16:48 expdb -> /dev/block/mmcblk0p10
lrwxrwxrwx root root 2016-05-23 16:48 flashinfo -> /dev/block/mmcblk0p23
lrwxrwxrwx root root 2016-05-23 16:48 frp -> /dev/block/mmcblk0p17
lrwxrwxrwx root root 2016-05-23 16:48 keystore -> /dev/block/mmcblk0p14
lrwxrwxrwx root root 2016-05-23 16:48 lk -> /dev/block/mmcblk0p5
lrwxrwxrwx root root 2016-05-23 16:48 logo -> /dev/block/mmcblk0p9
lrwxrwxrwx root root 2016-05-23 16:48 metadata -> /dev/block/mmcblk0p19
lrwxrwxrwx root root 2016-05-23 16:48 nvdata -> /dev/block/mmcblk0p18
lrwxrwxrwx root root 2016-05-23 16:48 nvram -> /dev/block/mmcblk0p2
lrwxrwxrwx root root 2016-05-23 16:48 oemkeystore -> /dev/block/mmcblk0p12
lrwxrwxrwx root root 2016-05-23 16:48 para -> /dev/block/mmcblk0p6
lrwxrwxrwx root root 2016-05-23 16:48 proinfo -> /dev/block/mmcblk0p1
lrwxrwxrwx root root 2016-05-23 16:48 protect1 -> /dev/block/mmcblk0p3
lrwxrwxrwx root root 2016-05-23 16:48 protect2 -> /dev/block/mmcblk0p4
lrwxrwxrwx root root 2016-05-23 16:48 recovery -> /dev/block/mmcblk0p8
lrwxrwxrwx root root 2016-05-23 16:48 seccfg -> /dev/block/mmcblk0p11
lrwxrwxrwx root root 2016-05-23 16:48 secro -> /dev/block/mmcblk0p13
lrwxrwxrwx root root 2016-05-23 16:48 system -> /dev/block/mmcblk0p20
lrwxrwxrwx root root 2016-05-23 16:48 tee1 -> /dev/block/mmcblk0p15
lrwxrwxrwx root root 2016-05-23 16:48 tee2 -> /dev/block/mmcblk0p16
lrwxrwxrwx root root 2016-05-23 16:48 userdata -> /dev/block/mmcblk0p22
Build.prop file (as txt, use notepad++ to open): https://www.dropbox.com/s/xkhvyf1ihmlw13k/build.prop.txt?dl=0
Kernels: (attached to post)
To obtain your own Firmware partitions as img (replace: replace mmcblk0p20 with your partition directory (see partition tables I posted), and replace system.img with your partition name)
Following commands:
Code:
su
dd if=/dev/block/mmcblk0p20 of=/sdcard/system.img
Open adb and run:
Code:
adb pull /sdcard/system.img
Roms
Eragon ROM (booting, no camera or baseband): http://forum.xda-developers.com/android/software/eragon-os-9-9-port-l0070uu-t3385777
CM 12.1 (bootloop): http://forum.xda-developers.com/android/development/port-blu-life-one-x-2016-l0070uu-t3380836
Can someone here make a boot.img with a custom kernel that can function with cyanogenmod 12.1?
There are some people trying to port it to this device but we need someone to make that kernel.
crDROID and Resurrection Remix for the Micromax Canvas 5 both work for this device, tested myself.
Not sure if it's just me, or do SIM cards not register with these? If anyone could tell me, it'd be much appreciated.
crDROID - https://forum.xda-developers.com/android/development/crdroid-v3-5-micromax-canvas-5-e481-t3685656
Resurrection Remix - https://forum.xda-developers.com/android/development/micromax-canvas-5-e481-ressurection-t3667680
Cheers,
Awanonimik.
> Can I just use fastboot to flash one of those boot.img files? I'm trying to get my SIM cards to register, would you think that'd help?
> Does anyone have the modem.bin / radio.img for this? Still trying to fix my SIM card detection.
Hello.
So, as I described here, I success got root on this device. Now, I want a full backup in case things going bad. And obvious, a way to restore this backup.
I was searching for days for a ROM, but it simply don't exist (yet). This model have an identification (alps l1 mp6 v2 gxq6580 weg l p69) wich is used in some other devices (includings Samsung clones), so, I checked all the ROMs I found looking into /system partition on my device and comparing with /system image of the ROMs (I used SuperR's Kitchen), and none of them are equal, I mean, a lot of files (includind build.prop) are different, so there is a great chance to brick my phone if I use it.
Even if it is found, I can't restore with SP Flash Tools, because it don't work with this phone. I tried to readback, but it recognizes but never start. As the phone is a MT6580 based SoC, maybe is compatability issue also. MTK Droid Tools don't work also. It recognizes, but can't do anything (don't generate scatter, don't root, don't nothing), again maybe a compatibility also.
The stock recovery have no option to backup, and I'm afraid to flash a CWM or TWRP, because I don't know much about porting these things, and I don't have much information about partitions and these things yet. ADB while in recovery give me an unauthorized device, by the way.
The phone accept fastboot commands, but don't accept the 'fastboot boot image.img", to try a temporary recovery, it only accept the 'fastboot flash image.img'. As sayed on the thread above, the bootloader is now unlocked, by the way.
So... this the situation... Can't have backup for now. If it help you to help me, there is the result of ls -all /dev/block/platform/mtk-msdc.0/by-name/ command in adb shell:
Code:
1|[email protected]_weg_l:/ # ls -all /dev/block/platform/mtk-msdc.0/by-name/
lrwxrwxrwx root root 2017-03-30 00:16 boot -> /dev/block/mmcblk0p7
lrwxrwxrwx root root 2017-03-30 00:16 cache -> /dev/block/mmcblk0p19
lrwxrwxrwx root root 2017-03-30 00:16 expdb -> /dev/block/mmcblk0p11
lrwxrwxrwx root root 2017-03-30 00:16 flashinfo -> /dev/block/mmcblk0p21
lrwxrwxrwx root root 2017-03-30 00:16 frp -> /dev/block/mmcblk0p12
lrwxrwxrwx root root 2017-03-30 00:16 keystore -> /dev/block/mmcblk0p17
lrwxrwxrwx root root 2017-03-30 00:16 lk -> /dev/block/mmcblk0p6
lrwxrwxrwx root root 2017-03-30 00:16 logo -> /dev/block/mmcblk0p10
lrwxrwxrwx root root 2017-03-30 00:16 metadata -> /dev/block/mmcblk0p14
lrwxrwxrwx root root 2017-03-30 00:16 nvdata -> /dev/block/mmcblk0p13
lrwxrwxrwx root root 2017-03-30 00:16 nvram -> /dev/block/mmcblk0p2
lrwxrwxrwx root root 2017-03-30 00:16 oemkeystore -> /dev/block/mmcblk0p15
lrwxrwxrwx root root 2017-03-30 00:16 para -> /dev/block/mmcblk0p9
lrwxrwxrwx root root 2017-03-30 00:16 proinfo -> /dev/block/mmcblk0p1
lrwxrwxrwx root root 2017-03-30 00:16 protect1 -> /dev/block/mmcblk0p3
lrwxrwxrwx root root 2017-03-30 00:16 protect2 -> /dev/block/mmcblk0p4
lrwxrwxrwx root root 2017-03-30 00:16 recovery -> /dev/block/mmcblk0p8
lrwxrwxrwx root root 2017-03-30 00:16 seccfg -> /dev/block/mmcblk0p5
lrwxrwxrwx root root 2017-03-30 00:16 secro -> /dev/block/mmcblk0p16
lrwxrwxrwx root root 2017-03-30 00:16 system -> /dev/block/mmcblk0p18
lrwxrwxrwx root root 2017-03-30 00:16 userdata -> /dev/block/mmcblk0p20
[email protected]_weg_l:/ #
I sucessfully (I think) dump a boot image with dd command (dd if=/dev/block/mmcblk0p7 of=/sdcard/boot.img), but I'm not sure it is 100% perfect and if it can be safely used to restore (and how to restore... maybe 'fastboot flash'?). Maybe I can dump some other images, but I don't tried yet.
If you need any other information, I reply in almost same time.
Thanks in advice.
So, I did a dd to dump boot and recovery, and open them sucessfuly on kitchen. Unfortunally, I can't do the same with system because adb only works with phone in normal mode.
Anyway to get the system for this phone? And, can I use these dumped files with 'fastboot flash' command?
Thanks!
romulocarlos said:
So, I did a dd to dump boot and recovery, and open them sucessfuly on kitchen. Unfortunally, I can't do the same with system because adb only works with phone in normal mode.
Anyway to get the system for this phone? And, can I use these dumped files with 'fastboot flash' command?
Thanks!
Click to expand...
Click to collapse
Hello, i have recently posted a complete ROM on needrom. https://www.needrom.com/download/sony-xperia-c6-clone-mt6580/
i guess that is the one your are looking for. Good luck and sorry for my bad englich.
Help
Rom is corrupted, is not it? It's working? tell me how to download, I thank you