I know this was requested by others and here I present a list for other devs of the partition mount points for the i9205.
You can search various folders for this info but its not complete. Apps wont show the main partion points
{
"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"
}
To get this information for your device, open up terminal emulator and enter the following
Code:
ls -al /dev/block/platform/msm_sdcc.1/by-name
Here is the code
Code:
lrwxrwxrwx root root 2013-01-17 21:07 aboot -> /dev/block/mmcblk0p5
lrwxrwxrwx root root 2013-01-17 21:07 backup -> /dev/block/mmcblk0p16
lrwxrwxrwx root root 2013-01-17 21:07 boot -> /dev/block/mmcblk0p13
lrwxrwxrwx root root 2013-01-17 21:07 cache -> /dev/block/mmcblk0p21
lrwxrwxrwx root root 2013-01-17 21:07 efs -> /dev/block/mmcblk0p10
lrwxrwxrwx root root 2013-01-17 21:07 fota -> /dev/block/mmcblk0p15
lrwxrwxrwx root root 2013-01-17 21:07 fsg -> /dev/block/mmcblk0p17
lrwxrwxrwx root root 2013-01-17 21:07 hidden -> /dev/block/mmcblk0p22
lrwxrwxrwx root root 2013-01-17 21:07 modem -> /dev/block/mmcblk0p1
lrwxrwxrwx root root 2013-01-17 21:07 modemst1 -> /dev/block/mmcblk0p11
lrwxrwxrwx root root 2013-01-17 21:07 modemst2 -> /dev/block/mmcblk0p12
lrwxrwxrwx root root 2013-01-17 21:07 pad -> /dev/block/mmcblk0p8
lrwxrwxrwx root root 2013-01-17 21:07 param -> /dev/block/mmcblk0p9
lrwxrwxrwx root root 2013-01-17 21:07 persist -> /dev/block/mmcblk0p19
lrwxrwxrwx root root 2013-01-17 21:07 recovery -> /dev/block/mmcblk0p14
lrwxrwxrwx root root 2013-01-17 21:07 rpm -> /dev/block/mmcblk0p6
lrwxrwxrwx root root 2013-01-17 21:07 sbl1 -> /dev/block/mmcblk0p2
lrwxrwxrwx root root 2013-01-17 21:07 sbl2 -> /dev/block/mmcblk0p3
lrwxrwxrwx root root 2013-01-17 21:07 sbl3 -> /dev/block/mmcblk0p4
lrwxrwxrwx root root 2013-01-17 21:07 ssd -> /dev/block/mmcblk0p18
lrwxrwxrwx root root 2013-01-17 21:07 system -> /dev/block/mmcblk0p20
lrwxrwxrwx root root 2013-01-17 21:07 tz -> /dev/block/mmcblk0p7
lrwxrwxrwx root root 2013-01-17 21:07 userdata -> /dev/block/mmcblk0p23
Hope this helps someone
Sent from my GT-I9205 using xda premium
Thanks.
Two questions please:
- The LTE modem is installed on 3 partitions? Odin know this, work well?
- A Rom have also "persist.img.ext4" and "tz.mbn". Wath is this, a booloader?
At the moment installing new lte modems is a no go, its a known problem on the s4 thread and people over at darkys are working on it.
odin is samsungs software so stock packages will be ok, currently ive left modem out of the custom rom for now
thering1975 said:
At the moment installing new lte modems is a no go, its a known problem on the s4 thread and people over at darkys are working on it.
Click to expand...
Click to collapse
The S4 have the modem.bin from 52,... MB and NON-HLOS.bin from 9,... MB.
The Mega have only NON-HLOS.bin from 49,... MB. Are different.
I flashed the Odex Rom XXUAMG3 by Odin and the 4G work well whit new modem.
thats correct it will with odin yes, but not in cwm hence why most 4g s4 roms leave out the modem
taken from the s4 lte modem thread
CWM/TWRP flashable modems for Samsung Galaxy S4 LTE - GT-I9505
At the moment it is IMPOSSIBLE to flash ANY modem for I9505 through ANY Custom Recovery!
Click to expand...
Click to collapse
thering1975 said:
thats correct it will with odin yes, but not in cwm hence why most 4g s4 roms leave out the modem
Click to expand...
Click to collapse
Alright. I understood now.
Thank You
EDIT: In this case, for new Rom's we can extract the modem, make a .tar.md5 and flash by Odin. Work it, like this?
Only one way to find out lol
Anyone with the I9200 done this yet as i need to verify before i can start building for the I9200
thering1975 said:
Anyone with the I9200 done this yet as i need to verify before i can start building for the I9200
Click to expand...
Click to collapse
Here is my result from i9200 in attachment...
Excellent thanks I can start work on a rom ta
Sent from my GT-I9205 using xda premium
actually what base rom are you on
Right now i'm on I9200XXUAMEE
Sent from my GT-I9200 using xda app-developers app
hey guys,
can someone give me the exact mount point from the internal and external sdcard please
it's for 9205
thanks in advance
sent from my G-Note
To copy something to sdcard you dont need to mount so to speak in cwm
Just extraxt to /sdcard
Sent from my GT-I9205 using xda premium
no no,
I have to know the exact mount points for my uft zips that the battery icons will be flashed correctly
Kangburra posted yesterday a mount point for the internal sd but it is the path for the external
now I only have to know that correct path for the internal,
then it doesn't matter from which one the people flash the zips
sent from my G-Note
hara74 said:
no no,
I have to know the exact mount points for my uft zips that the battery icons will be flashed correctly
Kangburra posted yesterday a mount point for the internal sd but it is the path for the external
now I only have to know that correct path for the internal,
then it doesn't matter from which one the people flash the zips
Click to expand...
Click to collapse
Here You have the mobileodin.txt made by MobileOdin to send to Chainfire to make compatibility from i9205 whit MO.
From Stock Rom Sammobile XXUAMG4. You have here all about partitions, sizes and more info.
I hope this will useful.
hi, i need a i9205 pit file.
it's not working nomal booting - encryption failed
i tried factory reset but error - can't mount /data,
please, help me.
Hi,
Anyone knows which partition holds the bootloader?
treare said:
Hi,
Anyone knows which partition holds the bootloader?
Click to expand...
Click to collapse
Its normaly sbl. But as we have 3 i not sure
Sent from my GT-I9205 using XDA Premium 4 mobile app
Related
Hello, i try port miui to our galaxy...
I need partition layout of GT-I9305 to set up the installation script. Can anyone post it here?
Sent from my GT-I9305
I cant help
Gut it would be great if u create a miui Rom
Thanks For your work homey
Here you go
lrwxrwxrwx root root 2012-10-08 21:43 BOOT -> /dev/block/mmcblk0p8
lrwxrwxrwx root root 2012-10-08 21:43 BOTA0 -> /dev/block/mmcblk0p1
lrwxrwxrwx root root 2012-10-08 21:43 BOTA1 -> /dev/block/mmcblk0p2
lrwxrwxrwx root root 2012-10-08 21:43 CACHE -> /dev/block/mmcblk0p12
lrwxrwxrwx root root 2012-10-08 21:43 EFS -> /dev/block/mmcblk0p3
lrwxrwxrwx root root 2012-10-08 21:43 HIDDEN -> /dev/block/mmcblk0p14
lrwxrwxrwx root root 2012-10-08 21:43 OTA -> /dev/block/mmcblk0p15
lrwxrwxrwx root root 2012-10-08 21:43 PARAM -> /dev/block/mmcblk0p7
lrwxrwxrwx root root 2012-10-08 21:43 RADIO -> /dev/block/mmcblk0p10
lrwxrwxrwx root root 2012-10-08 21:43 RECOVERY -> /dev/block/mmcblk0p9
lrwxrwxrwx root root 2012-10-08 21:43 SYSTEM -> /dev/block/mmcblk0p13
lrwxrwxrwx root root 2012-10-08 21:43 TOMBSTONES -> /dev/block/mmcblk0p11
lrwxrwxrwx root root 2012-10-08 21:43 USERDATA -> /dev/block/mmcblk0p16
lrwxrwxrwx root root 2012-10-08 21:43 m9kefs1 -> /dev/block/mmcblk0p4
lrwxrwxrwx root root 2012-10-08 21:43 m9kefs2 -> /dev/block/mmcblk0p5
lrwxrwxrwx root root 2012-10-08 21:43 m9kefs3 -> /dev/block/mmcblk0p6
---------- Post added at 12:11 PM ---------- Previous post was at 11:39 AM ----------
Let us know how you go, honestly I dont know why experienced devs have not done this yet to other roms, it really doesnt seem so hard for a dev that knows what they are doing, all it really needs is the base firmware changed and the edited files in the I9300 JB base can probably be used in replace of the non-edited ones in the i9305 base saves you from editing the files again. then all the system files should be easily transferable and then the mounting points changed , that sounds like pretty much it or am i missing something?
btemtd said:
Here you go
lrwxrwxrwx root root 2012-10-08 21:43 BOOT -> /dev/block/mmcblk0p8
lrwxrwxrwx root root 2012-10-08 21:43 BOTA0 -> /dev/block/mmcblk0p1
lrwxrwxrwx root root 2012-10-08 21:43 BOTA1 -> /dev/block/mmcblk0p2
lrwxrwxrwx root root 2012-10-08 21:43 CACHE -> /dev/block/mmcblk0p12
lrwxrwxrwx root root 2012-10-08 21:43 EFS -> /dev/block/mmcblk0p3
lrwxrwxrwx root root 2012-10-08 21:43 HIDDEN -> /dev/block/mmcblk0p14
lrwxrwxrwx root root 2012-10-08 21:43 OTA -> /dev/block/mmcblk0p15
lrwxrwxrwx root root 2012-10-08 21:43 PARAM -> /dev/block/mmcblk0p7
lrwxrwxrwx root root 2012-10-08 21:43 RADIO -> /dev/block/mmcblk0p10
lrwxrwxrwx root root 2012-10-08 21:43 RECOVERY -> /dev/block/mmcblk0p9
lrwxrwxrwx root root 2012-10-08 21:43 SYSTEM -> /dev/block/mmcblk0p13
lrwxrwxrwx root root 2012-10-08 21:43 TOMBSTONES -> /dev/block/mmcblk0p11
lrwxrwxrwx root root 2012-10-08 21:43 USERDATA -> /dev/block/mmcblk0p16
lrwxrwxrwx root root 2012-10-08 21:43 m9kefs1 -> /dev/block/mmcblk0p4
lrwxrwxrwx root root 2012-10-08 21:43 m9kefs2 -> /dev/block/mmcblk0p5
lrwxrwxrwx root root 2012-10-08 21:43 m9kefs3 -> /dev/block/mmcblk0p6
---------- Post added at 12:11 PM ---------- Previous post was at 11:39 AM ----------
Let us know how you go, honestly I dont know why experienced devs have not done this yet to other roms, it really doesnt seem so hard for a dev that knows what they are doing, all it really needs is the base firmware changed and the edited files in the I9300 JB base can probably be used in replace of the non-edited ones in the i9305 base saves you from editing the files again. then all the system files should be easily transferable and then the mounting points changed , that sounds like pretty much it or am i missing something?
Click to expand...
Click to collapse
Because there is no Stock jb Version out for s3 but should Come in a few days maybe weeks....
What do you mean no stock JB ? There is stock jb out now for the i9300
Sent from my GT-I9305 using xda app-developers app
I ported MIUI JB for i9300 on AOSP CM10 base, maybe I can help. What base do you want to use?
Well the Xxali5 is the original release and most internationally used and most popular base at the moment
But Some countries released there ph0ne later with a firmware number xxali9. Not sure if there is even any changes. But your choice.
Sent from my GT-I9305 using xda app-developers app
btemtd said:
What do you mean no stock JB ? There is stock jb out now for the i9300
Sent from my GT-I9305 using xda app-developers app
Click to expand...
Click to collapse
there is noch stock jb miui!!!!!!!!!!!!!!!!!!!!!!!! its coming in future
aosp or cm doesnt work for our device!
greetz
F1tty said:
there is noch stock jb miui!!!!!!!!!!!!!!!!!!!!!!!! its coming in future
aosp or cm doesnt work for our device!
greetz
Click to expand...
Click to collapse
Yes indeed...
But as u said there is no stock JB that is what got me confused cause you didnt say MIUI!!!!!!
btemtd said:
Yes indeed...
But as u said there is no stock JB that is what got me confused cause you didnt say MIUI!!!!!!
Click to expand...
Click to collapse
Cause that thread belongs to miui.... If miui for I9300 JB is aviable i Port IT for i9305 specially for english and german maybe more depending on Base rom
Then i think that is part of the instructions. Maybe u can use a miui i9300 jb base and merge it the i9305 base
Sent from my GT-I9305 using xda app-developers app
I cant wait
Can u tell us your progress?
dying to hear the good news
any advance on this? would be amazingg
is there some news on porting ?
Porting is easy, if no one is going to do it I might do it if I get some spare time.. just don't expect any support or updates ok?
Sent from my GT-I9300 using xda app-developers app
cpl things needed as of right now anyone with the phone and has adb we need the results of this command to finish twrp..
ls -la /dev/block/platform/dw_mmc/by-name
and just packing up a test tar for root now might as well have twrp ready if root works
also run this *#1234#
and report info it gives please, might be able to acquire a full stock tar using the info we get from that
I get "'ls' is not recognized as an internal or external command, operable program or batch file"
Same thing without the space in between ls and the (-)
Did I goof somewhere?
[email protected]:/ $ ls -la /dev/block/platform/dw_mmc/by-name
lrwxrwxrwx root root 2011-12-31 17:00 BOOT -> /dev/block/mmcblk0p8
lrwxrwxrwx root root 2011-12-31 17:00 BOTA0 -> /dev/block/mmcblk0p1
lrwxrwxrwx root root 2011-12-31 17:00 BOTA1 -> /dev/block/mmcblk0p2
lrwxrwxrwx root root 2011-12-31 17:00 CACHE -> /dev/block/mmcblk0p12
lrwxrwxrwx root root 2011-12-31 17:00 EFS -> /dev/block/mmcblk0p3
lrwxrwxrwx root root 2011-12-31 17:00 HIDDEN -> /dev/block/mmcblk0p14
lrwxrwxrwx root root 2011-12-31 17:00 OTA -> /dev/block/mmcblk0p15
lrwxrwxrwx root root 2011-12-31 17:00 PARAM -> /dev/block/mmcblk0p7
lrwxrwxrwx root root 2011-12-31 17:00 RADIO -> /dev/block/mmcblk0p10
lrwxrwxrwx root root 2011-12-31 17:00 RECOVERY -> /dev/block/mmcblk0p9
lrwxrwxrwx root root 2011-12-31 17:00 SYSTEM -> /dev/block/mmcblk0p13
lrwxrwxrwx root root 2011-12-31 17:00 TOMBSTONES -> /dev/block/mmcblk0p11
lrwxrwxrwx root root 2011-12-31 17:00 USERDATA -> /dev/block/mmcblk0p16
lrwxrwxrwx root root 2011-12-31 17:00 m9kefs1 -> /dev/block/mmcblk0p4
lrwxrwxrwx root root 2011-12-31 17:00 m9kefs2 -> /dev/block/mmcblk0p5
lrwxrwxrwx root root 2011-12-31 17:00 m9kefs3 -> /dev/block/mmcblk0p6
[email protected]:/ $
---------- Post added at 09:26 PM ---------- Previous post was at 09:22 PM ----------
*#1234# run that from where? The dialer just tries to call that... adb gives a not found.
TWRP recovery has already been done by bigbiff http://goo.im/devs/OpenRecovery/t0ltevzw
He came into #galaxy-note-2 and got the info he needed.
slick_rick said:
TWRP recovery has already been done by bigbiff http://goo.im/devs/OpenRecovery/t0ltevzw
He came into #galaxy-note-2 and got the info he needed.
Click to expand...
Click to collapse
The boot loader doesn't need to be unlocked? Witch file do we use?
Sent from my SCH-I605 using Tapatalk 2
So...we have root already? How to root it? Can someone explain please?
And we have custom recovery already too?
FMXP said:
So...we have root already? How to root it? Can someone explain please?
And we have custom recovery already too?
Click to expand...
Click to collapse
Its a possibility not proven yet.
I got root on my N2!
{
"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"
}
Sent from my iPhone 5
slick_rick said:
TWRP recovery has already been done by bigbiff http://goo.im/devs/OpenRecovery/t0ltevzw
He came into #galaxy-note-2 and got the info he needed.
Click to expand...
Click to collapse
Can we flash that with odin or will it not boot because of the locked bootloader?
Sent from my SCH-I605 using Tapatalk 2
jellydroid13 said:
Can we flash that with odin or will it not boot because of the locked bootloader?
Sent from my SCH-I605 using Tapatalk 2
Click to expand...
Click to collapse
it will softbrick your device with the locked bootloader!
droidstyle said:
it will softbrick your device with the locked bootloader!
Click to expand...
Click to collapse
And thats why i ask
jellydroid13 said:
And thats why i ask
Click to expand...
Click to collapse
:good:
Hopefully today we get root because beans said he has a root method and he was getting his note today so..... Fingers crossed
Sent from my SCH-I605 using Xparent Red Tapatalk 2
As long as I can get WiFi tether, I'm good. Root will help me accomplish that and I'm ok with it not being unlocked.
kookahdoo said:
As long as I can get WiFi tether, I'm good. Root will help me accomplish that and I'm ok with it not being unlocked.
Click to expand...
Click to collapse
Me too I just want root to restore my apps.
Sent from my SCH-I605 using Xparent Red Tapatalk 2
I need root twrp custom roms lol... need to restore data from my gnex to here with titanium backup
Sent from my SCH-I605 using Tapatalk 2
Admiral2145 said:
I need root twrp custom roms lol... need to restore data from my gnex to here with titanium backup
Sent from my SCH-I605 using Tapatalk 2
Click to expand...
Click to collapse
Check the dev section we just got root
I545 ME7 new version has a lock, do not accidentally brush or misuse upgrade, think about tossing a Brush Brush RECOVERY trouble. Is it possible to upgrade will not be downgraded? The answer is definitely no. Well, we want to downgrade, then understand its partition structure is a must. You know, in the end we have to upgrade to upgrade what was a result of being locked!
First, here is the I545 partition table structure:
Code:
lrwxrwxrwx root root 1970-01-01 16:14 aboot -> /dev/block/mmcblk0p6
lrwxrwxrwx root root 1970-01-01 16:14 apnhlos -> /dev/block/mmcblk0p1
lrwxrwxrwx root root 1970-01-01 16:14 backup -> /dev/block/mmcblk0p23
lrwxrwxrwx root root 1970-01-01 16:14 boot -> /dev/block/mmcblk0p20
lrwxrwxrwx root root 1970-01-01 16:14 cache -> /dev/block/mmcblk0p18
lrwxrwxrwx root root 1970-01-01 16:14 carrier -> /dev/block/mmcblk0p28
lrwxrwxrwx root root 1970-01-01 16:14 efs -> /dev/block/mmcblk0p10
lrwxrwxrwx root root 1970-01-01 16:14 fota -> /dev/block/mmcblk0p22
lrwxrwxrwx root root 1970-01-01 16:14 fsg -> /dev/block/mmcblk0p24
lrwxrwxrwx root root 1970-01-01 16:14 hidden -> /dev/block/mmcblk0p27
lrwxrwxrwx root root 1970-01-01 16:14 m9kefs1 -> /dev/block/mmcblk0p13
lrwxrwxrwx root root 1970-01-01 16:14 m9kefs2 -> /dev/block/mmcblk0p14
lrwxrwxrwx root root 1970-01-01 16:14 m9kefs3 -> /dev/block/mmcblk0p15
lrwxrwxrwx root root 1970-01-01 16:14 mdm -> /dev/block/mmcblk0p2
lrwxrwxrwx root root 1970-01-01 16:14 modemst1 -> /dev/block/mmcblk0p11
lrwxrwxrwx root root 1970-01-01 16:14 modemst2 -> /dev/block/mmcblk0p12
lrwxrwxrwx root root 1970-01-01 16:14 pad -> /dev/block/mmcblk0p9
lrwxrwxrwx root root 1970-01-01 16:14 param -> /dev/block/mmcblk0p19
lrwxrwxrwx root root 1970-01-01 16:14 persdata -> /dev/block/mmcblk0p26
lrwxrwxrwx root root 1970-01-01 16:14 persist -> /dev/block/mmcblk0p17
lrwxrwxrwx root root 1970-01-01 16:14 recovery -> /dev/block/mmcblk0p21
lrwxrwxrwx root root 1970-01-01 16:14 rpm -> /dev/block/mmcblk0p7
lrwxrwxrwx root root 1970-01-01 16:14 sbl1 -> /dev/block/mmcblk0p3
lrwxrwxrwx root root 1970-01-01 16:14 sbl2 -> /dev/block/mmcblk0p4
lrwxrwxrwx root root 1970-01-01 16:14 sbl3 -> /dev/block/mmcblk0p5
lrwxrwxrwx root root 1970-01-01 16:14 ssd -> /dev/block/mmcblk0p25
lrwxrwxrwx root root 1970-01-01 16:14 system -> /dev/block/mmcblk0p16
lrwxrwxrwx root root 1970-01-01 16:14 tz -> /dev/block/mmcblk0p8
lrwxrwxrwx root root 1970-01-01 16:14 userdata -> /dev/block/mmcblk0p29
Know the partition table, then we have to look at the official ROM ME7 what is inside, at least to know what he upgraded partition was a result of being locked.
The following is the official package ME7 opened with RAR see:
{
"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"
}
You can see, there are 12 official package file , in fact, there should be 13 years , I feel like I had a SBL1.MBN delete the file, this is an important guiding document , a blank screen will be lost . Connection brush modes anyhow. So we know that under the first bar . BOOT.IMG is the core of the boot files will be lost card first screen . CACHE This is not , MODEM.BIN and NON-HLOS.BIN this is related to the baseband , I brush off alone , it will not be locked , and this has nothing to do , RECOVERY This is a card swipe mode , recovery mode , this is not , RPM is a power management scheme related , SBL2.MBN SBL3.MBN boot record which two are related , SYSTEM this is the system , nor is , TZ is that I do not understand what to do .
**Now the question comes, if not understand, a recovery in the past may have a try. Such high risk factor . Therefore, we even try , but also row a sequence . For example SBL1.MBN, this is the first boot , when this fails if the coverage directly on a black screen , and we try not to move it to this , at least we do not move it, cover the failure modes that can feed wire brush brush the official rescue package bricks ! Of course , this is not relevant to the lock BOOTLOADER .
***535 used all know , 535 is V version, it also has BOOTLOADER lock, then unlock 535 using what methods do, in fact, is replaced by the partition method, which is aboot.mbn replace this partition. In fact, it says so much just thinking, we can be like 535 as a direct replacement overwrite this partition. If not, then only SBL2 SBL3 SBL1 these three , this three risk factor is quite high, and our principle is can not move do not move these three !
Well, just say replace overridden methods !
First of all, we have to use ADB SHELL under the DD command. Then we will obtain ADB SHELL authority , which is first ROOT.
The ROOT method ME7 forum there, I will not say more . I direct that ADB SHELL command .
We go first to Taiwan MDK the machine, put a few partition backup, is SBL1.MBN SBL2.MBN SBL3.MBN and ABOOT.MBN If you are interested , you can put all of the above partition table partition backup under , be prepared to stay with maybe someday that can use ! ~ ~
Backup method is to obtain ROOT , enter ADB SHELL command:
Code:
adb shell
dd if=/dev/block/mmcblk0p3 of=/sdcard/sbl1.mbn bs=4096
dd if=/dev/block/mmcblk0p4 of=/sdcard/sbl2.mbn bs=4096
dd if=/dev/block/mmcblk0p5 of=/sdcard/sbl3.mbn bs=4096
dd if=/dev/block/mmcblk0p6 of=/sdcard/aboot.mbn bs=4096
To explain, dd command to copy the partition related commands, if the meaning can be understood as if it. If there IF = path behind the partition, partition backup to put this on the path of = this, SDCARD this is the path of built-in memory card, you can back up directly to an external memory card, you have to do to change the path down.
Next, we put the backup files are copied to the four external SD card, or copied to a computer backup.
Then again, we took our locked machine, and put the MDK overwrite these partitions ME7 partition. Cover only aboot.mbn oh.
We first connect the phone to the computer, the backup out who's copied to the phone's built-in memory card.
root, I do not say this directly into the adb shell input overrides command:
Code:
adb shell
dd if=/dev/block/mmcblk0p6 of=/sdcard/ME7_aboot.mbn bs=4096
dd if=/sdcard/aboot.mbn of=/dev/block/mmcblk0p6 bs=4096
Note that this command following the second IF = OF = position and the position in turn, because it is not backed up, it was restored. The first DD command can not operate, I was customary to put it back down. Be prepared!
Well, I write to you, these commands is very dangerous, and can not be successful looking at you peril Oh, I only provide ideas and does not promise any consequences. Understand their own caution to decide whether to try, do not understand it not tried!
New ideas are always appreciated. Thank you for your efforts!
There are two places to discuss this ...and remember, if you ever try any of this stuff, you do so at your own risk....
see http://forum.xda-developers.com/showthread.php?t=2500826
or
http://forum.xda-developers.com/showthread.php?t=2417713
or possibly here http://forum.xda-developers.com/showthread.php?t=2428226
I just ported from LG L90 to LG G2 mini d618.
original post is Here
thanks a lot for @BigMajster as the creator
You need:
-LG G2 mini d618
-Custom recovery
-30mb free space on external SD card
-external SD card with backup or update.zip with system
Warning:
- Do backup your ROM and internal SD, because this will erase the partitions /system, /cache & /data (including /data/media).
Ready? Let's get started:
-Boot phone to recovery mode
-Install PartitionTableTool_d618.zip from sdcard
-Now you have 3 options to choice:
Maximal- system partition have only 730mb so you can install only custom rom like CynogenMod
Optimal- system partition have 1,5gb so you can also install stock LG rom, but you still have more data.
Stock- this is orginal partition table
{
"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"
}
-Restore you backup or install new rom form update.zip
-Restore Internal SD
Disclaimer:
- I am not responsible if you brick your device or lost your data. It is possible that it does not work on all variants.
DOWNLOAD: http://d-h.st/mevf
lol, i'm using it for 5-6 months. Hack from l90 is fully supported on our g2 mini =)
System_F said:
lol, i'm using it for 5-6 months. Hack from l90 is fully supported on our g2 mini =)
Click to expand...
Click to collapse
Yes me too. I think not everyone knows about it, so I make a thread here.
myllo.setya said:
Yes me too. I think not everyone knows about it, so I make a thread here.
Click to expand...
Click to collapse
anyway thanks =)
System_F said:
lol, i'm using it for 5-6 months. Hack from l90 is fully supported on our g2 mini =)
Click to expand...
Click to collapse
Same here, i didn't know this need a port, in my case worked perfectly only editing updater-script
Its funny to see that lg set 890mb for cache, mostly useless
sergioslk said:
Same here, i didn't know this need a port, in my case worked perfectly only editing updater-script
Its funny to see that lg set 890mb for cache, mostly useless
Click to expand...
Click to collapse
in this version, I change kernel of ptt.img with d618 kernel. and I remove the phone type selection menu. in order to avoid mistakes in choosing the type of phone.
Woah cool. Ill try this tonight
please log d618
ls -al /dev/block/platform/msm_sdcc.1/by-name/
SkyLK said:
please log d618
ls -al /dev/block/platform/msm_sdcc.1/by-name/
Click to expand...
Click to collapse
see this attachment.
myllo.setya said:
I just ported from LG L90 to LG G2 mini d618.
original post is Here
thanks a lot for @BigMajster as the creator
You need:
-LG G2 mini d618
-Custom recovery
-30mb free space on external SD card
-external SD card with backup or update.zip with system
Warning:
- Do backup your ROM and internal SD, because this will erase the partitions /system, /cache & /data (including /data/media).
Ready? Let's get started:
-Boot phone to recovery mode
-Install PartitionTableTool_d618.zip from sdcard
-Now you have 3 options to choice:
Maximal- system partition have only 730mb so you can install only custom rom like CynogenMod
Optimal- system partition have 1,5gb so you can also install stock LG rom, but you still have more data.
Stock- this is orginal partition table
-Restore you backup or install new rom form update.zip
-Restore Internal SD
Disclaimer:
- I am not responsible if you brick your device or lost your data. It is possible that it does not work on all variants.
DOWNLOAD: http://d-h.st/mevf
Click to expand...
Click to collapse
What should I change to make it work on d620?
Fulga666 said:
What should I change to make it work on d620?
Click to expand...
Click to collapse
Just edit update-script from the zip. Remove the first line.
Now I can't mount Data/Cache, could I do something to fix this? I don't really want to flash a new kdz. :/
EDIT: Okay, I've fixed it, palyed with the wiping buttons and rebooted a few times.
myllo.setya said:
see this attachment.
Click to expand...
Click to collapse
thanks, please parameter -al
ls -al /dev/block/platform/msm_sdcc.1/by-name/
I want to compare size and name partitions d618 and d620r
SkyLK said:
thanks, please parameter -al
ls -al /dev/block/platform/msm_sdcc.1/by-name/
I want to compare size and name partitions d618 and d620r
Click to expand...
Click to collapse
This..
Code:
[email protected]:/ # ls -al dev/block/platform/msm_sdcc.1/by-name
lrwxrwxrwx root root 1970-03-10 07:57 DDR -> /dev/block/mmcblk0p21
lrwxrwxrwx root root 1970-03-10 07:57 aboot -> /dev/block/mmcblk0p6
lrwxrwxrwx root root 1970-03-10 07:57 abootb -> /dev/block/mmcblk0p9
lrwxrwxrwx root root 1970-03-10 07:57 boot -> /dev/block/mmcblk0p16
lrwxrwxrwx root root 1970-03-10 07:57 cache -> /dev/block/mmcblk0p33
lrwxrwxrwx root root 1970-03-10 07:57 cust -> /dev/block/mmcblk0p30
lrwxrwxrwx root root 1970-03-10 07:57 drm -> /dev/block/mmcblk0p24
lrwxrwxrwx root root 1970-03-10 07:57 eksst -> /dev/block/mmcblk0p31
lrwxrwxrwx root root 1970-03-10 07:57 encrypt -> /dev/block/mmcblk0p22
lrwxrwxrwx root root 1970-03-10 07:57 factory -> /dev/block/mmcblk0p26
lrwxrwxrwx root root 1970-03-10 07:57 fota -> /dev/block/mmcblk0p27
lrwxrwxrwx root root 1970-03-10 07:57 fsc -> /dev/block/mmcblk0p19
lrwxrwxrwx root root 1970-03-10 07:57 fsg -> /dev/block/mmcblk0p18
lrwxrwxrwx root root 1970-03-10 07:57 grow -> /dev/block/mmcblk0p35
lrwxrwxrwx root root 1970-03-10 07:57 laf -> /dev/block/mmcblk0p15
lrwxrwxrwx root root 1970-03-10 07:57 misc -> /dev/block/mmcblk0p13
lrwxrwxrwx root root 1970-03-10 07:57 modem -> /dev/block/mmcblk0p1
lrwxrwxrwx root root 1970-03-10 07:57 modemst1 -> /dev/block/mmcblk0p11
lrwxrwxrwx root root 1970-03-10 07:57 modemst2 -> /dev/block/mmcblk0p12
lrwxrwxrwx root root 1970-03-10 07:57 mpt -> /dev/block/mmcblk0p29
lrwxrwxrwx root root 1970-03-10 07:57 pad -> /dev/block/mmcblk0p10
lrwxrwxrwx root root 1970-03-10 07:57 persist -> /dev/block/mmcblk0p14
lrwxrwxrwx root root 1970-03-10 07:57 rct -> /dev/block/mmcblk0p23
lrwxrwxrwx root root 1970-03-10 07:57 recovery -> /dev/block/mmcblk0p17
lrwxrwxrwx root root 1970-03-10 07:57 rpm -> /dev/block/mmcblk0p3
lrwxrwxrwx root root 1970-03-10 07:57 rpmb -> /dev/block/mmcblk0p7
lrwxrwxrwx root root 1970-03-10 07:57 sbl1 -> /dev/block/mmcblk0p2
lrwxrwxrwx root root 1970-03-10 07:57 sbl1b -> /dev/block/mmcblk0p28
lrwxrwxrwx root root 1970-03-10 07:57 sdi -> /dev/block/mmcblk0p5
lrwxrwxrwx root root 1970-03-10 07:57 sns -> /dev/block/mmcblk0p25
lrwxrwxrwx root root 1970-03-10 07:57 ssd -> /dev/block/mmcblk0p20
lrwxrwxrwx root root 1970-03-10 07:57 system -> /dev/block/mmcblk0p32
lrwxrwxrwx root root 1970-03-10 07:57 tz -> /dev/block/mmcblk0p4
lrwxrwxrwx root root 1970-03-10 07:57 tzb -> /dev/block/mmcblk0p8
lrwxrwxrwx root root 1970-03-10 07:57 userdata -> /dev/block/mmcblk0p34
Sent from my LG-D618 using XDA Free mobile app
I have a problem. Device: d618 Rom: CM12.1
Can someone help me? Thanks. [emoji1]
lance26 said:
I have a problem. Device: d618 Rom: CM12.1
Can someone help me? Thanks. [emoji1]
Click to expand...
Click to collapse
Try this version: https://yadi.sk/d/CXh7jR6EgbLnc
Nikita Pro Android said:
Try this version: https://yadi.sk/d/CXh7jR6EgbLnc
Click to expand...
Click to collapse
It kinda worked but now I'm stuck in a bootloop. I guess i'll just have to flash my rom again. How do I enter cwm? What button combinations?
for recovery is: hold power + vol up, when you see lg logo, release both keys and press it and hold again until you see a warning for deletion of data, select yes with volume keys and enter with power key, both times yes
sergioslk said:
for recovery is: hold power + vol up, when you see lg logo, release both keys and press it and hold again until you see a warning for deletion of data, select yes with volume keys and enter with power key, both times yes
Click to expand...
Click to collapse
It worked. Thanks
myllo.setya said:
I just ported from LG L90 to LG G2 mini d618.
Click to expand...
Click to collapse
Hi, possible to port to LG G2 D802?
This is my phone:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
This is the phone I just bought for my mother:
Bought less than a week from each other. Same phone, different android versions- mine Android 4.4.4 and hers is Android 5.1.
How can I upgrade mine to 5.1? Upgrade button in the settings menu returns the server is unreachable.
bump
bump
BUMP
Do you have a data connection on your phone (mobile data or WiFi)? Same carrier?
augie7107 said:
Do you have a data connection on your phone (mobile data or WiFi)? Same carrier?
Click to expand...
Click to collapse
Yes. Everything is the same.
Both purchased at Walmart.
Both on Straight Talk.
Both used Mobile and WiFi without any problems.
BUMP
Bump
There is no way to update via pc. Look up ZTE USA service number and give them a call. They will connect you with tech support to get it sorted.
Did you ever get this sorted out? I just bought the same phone and it came with 4.4.4. Called ZTE and they said there's no update for this phone yet
Ive got a zte z936l I can obtain a temp root on it with king root but I think its unstabe can't seem to flash a custom
If you want to root this phone, you need to obtain temp root and dump your entire ROM to a safe place, like a computer. Then SWAP boot and recovery. And boot the ROM via recovery buttons. This will give you full root but when youre done using it you newd to switch boot and recovery back. ZTE is known for their system lockdown and this way circumvents it. If you can obtain the 5.1.1 bootstack from your moms phone via temp root and using dd commands to dump we can ALL have 5.1. All we will need is a twrp build.
bichofelix said:
If you want to root this phone, you need to obtain temp root and dump your entire ROM to a safe place, like a computer. Then SWAP boot and recovery. And boot the ROM via recovery buttons. This will give you full root but when youre done using it you newd to switch boot and recovery back. ZTE is known for their system lockdown and this way circumvents it. If you can obtain the 5.1.1 bootstack from your moms phone via temp root and using dd commands to dump we can ALL have 5.1. All we will need is a twrp build.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showpost.php?p=63578570&postcount=11
I seen this above post. Full root can be gained if instructions are followed. Can you confirm this? I may just email them and pit in the request for both of the zte lever phones here in the house.
As for following your instructions, I'd have no issue doing as you say and providing 5.1 for xda. I'd prefer some more detailed instructions and possibly a irc/messaging platform for instant communication.
After temp root, open terminal and dump everything in "dev/block/bootdevice/by-name/" with dd commands onto your sdcard or PC. (dd if=/path/to/partition of=/dump/location/filename)
From there we decompile the candidates for boot and recovery and once we know which is which, they can be swapped. Then you reboot and obtain temp root again, which this time it should give you full root. When you're done using it, just swap them back and reboot.
I'm not sure about that guy saying you can just unlock bootloader because even with twrp the system will have ro lock on it unless boot and recovery are swapped. Look at the zmax if you're curious how it works.
bichofelix said:
After temp root, open terminal and dump everything in "dev/block/bootdevice/by-name/" with dd commands onto your sdcard or PC. (dd if=/path/to/partition of=/dump/location/filename)
From there we decompile the candidates for boot and recovery and once we know which is which, they can be swapped. Then you reboot and obtain temp root again, which this time it should give you full root. When you're done using it, just swap them back and reboot.
I'm not sure about that guy saying you can just unlock bootloader because even with twrp the system will have ro lock on it unless boot and recovery are swapped. Look at the zmax if you're curious how it works.
Click to expand...
Click to collapse
ZMAX?
I am installing ADB now and will follow these instructions the best I can.
Team Win Recovery Project (TWRP), they do not show my device so which one is it that I need? That link I posted about root and boot loader codes, he shows 2.8.70 and the closest device I see is the ZTE Blade.
The fella you replied to said he could get temp root with king root.
bichofelix said:
After temp root, open terminal and dump everything in "dev/block/bootdevice/by-name/" with dd commands onto your sdcard or PC. (dd if=/path/to/partition of=/dump/location/filename)
Click to expand...
Click to collapse
I have done it.
Now to do the rest. I am not sure what file types I should name them all though.
Humphrey1989 said:
I have done it.
Now to do the rest. I am not sure what file types I should name them all though.
Click to expand...
Click to collapse
They are all .img files except a few. You may simply leave them blank.
As for twrp, somebody has to actually build it for our device. We currently have none.
Once the partitions are all dumped, please zip them and link me.
There should also be a fastboot mode we have access to, if we do, we can all simply flash the lollipop bootstack.
bichofelix said:
There should also be a fastboot mode we have access to, if we do, we can all simply flash the lollipop bootstack.
Click to expand...
Click to collapse
I tried >fastboot devices and it didn't show any.
I have restarted my phone once or twice after kingroot and it seems that I have perm root if I read the below right.
Code:
C:\Program Files (x86)\Android\android-sdk\platform-tools>adb shell
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
[email protected]:/ # su
/system/bin/sh: su: not found
127|[email protected]:/ # id
uid=0(root) gid=0(root) context=u:r:shell:s0
[email protected]:/ #
This is what I have and while be making copies of:
Code:
[email protected]:/dev/block/bootdevice/by-name # ls -l
lrwxrwxrwx root root 1970-04-01 08:25 DDR -> /dev/block/mmcblk0p3
lrwxrwxrwx root root 1970-04-01 08:25 aboot -> /dev/block/mmcblk0p20
lrwxrwxrwx root root 1970-04-01 08:25 abootbak -> /dev/block/mmcblk0p21
lrwxrwxrwx root root 1970-04-01 08:25 boot -> /dev/block/mmcblk0p23
lrwxrwxrwx root root 1970-04-01 08:25 cache -> /dev/block/mmcblk0p30
lrwxrwxrwx root root 1970-04-01 08:25 config -> /dev/block/mmcblk0p28
lrwxrwxrwx root root 1970-04-01 08:25 fsc -> /dev/block/mmcblk0p16
lrwxrwxrwx root root 1970-04-01 08:25 fsg -> /dev/block/mmcblk0p17
lrwxrwxrwx root root 1970-04-01 08:25 hyp -> /dev/block/mmcblk0p8
lrwxrwxrwx root root 1970-04-01 08:25 hypbak -> /dev/block/mmcblk0p9
lrwxrwxrwx root root 1970-04-01 08:25 keystore -> /dev/block/mmcblk0p27
lrwxrwxrwx root root 1970-04-01 08:25 misc -> /dev/block/mmcblk0p26
lrwxrwxrwx root root 1970-04-01 08:25 modem -> /dev/block/mmcblk0p22
lrwxrwxrwx root root 1970-04-01 08:25 modemst1 -> /dev/block/mmcblk0p18
lrwxrwxrwx root root 1970-04-01 08:25 modemst2 -> /dev/block/mmcblk0p19
lrwxrwxrwx root root 1970-04-01 08:25 oem -> /dev/block/mmcblk0p29
lrwxrwxrwx root root 1970-04-01 08:25 pad -> /dev/block/mmcblk0p14
lrwxrwxrwx root root 1970-04-01 08:25 persist -> /dev/block/mmcblk0p13
lrwxrwxrwx root root 1970-04-01 08:25 recovery -> /dev/block/mmcblk0p24
lrwxrwxrwx root root 1970-04-01 08:25 rpm -> /dev/block/mmcblk0p4
lrwxrwxrwx root root 1970-04-01 08:25 rpmbak -> /dev/block/mmcblk0p5
lrwxrwxrwx root root 1970-04-01 08:25 sbl1 -> /dev/block/mmcblk0p1
lrwxrwxrwx root root 1970-04-01 08:25 sbl1bak -> /dev/block/mmcblk0p2
lrwxrwxrwx root root 1970-04-01 08:25 sec -> /dev/block/mmcblk0p10
lrwxrwxrwx root root 1970-04-01 08:25 splash -> /dev/block/mmcblk0p25
lrwxrwxrwx root root 1970-04-01 08:25 ssd -> /dev/block/mmcblk0p15
lrwxrwxrwx root root 1970-04-01 08:25 system -> /dev/block/mmcblk0p31
lrwxrwxrwx root root 1970-04-01 08:25 tz -> /dev/block/mmcblk0p6
lrwxrwxrwx root root 1970-04-01 08:25 tzbak -> /dev/block/mmcblk0p7
lrwxrwxrwx root root 1970-04-01 08:25 userdata -> /dev/block/mmcblk0p32
lrwxrwxrwx root root 1970-04-01 08:25 ztecfg -> /dev/block/mmcblk0p12
lrwxrwxrwx root root 1970-04-01 08:25 ztelk -> /dev/block/mmcblk0p11
[email protected]:/dev/block/bootdevice/by-name #
Humphrey1989 said:
I tried >fastboot devices and it didn't show any.
I have restarted my phone once or twice after kingroot and it seems that I have perm root if I read the below right.
This is what I have and while be making copies of:
Click to expand...
Click to collapse
Oh **** yeah they're named. Zte has been known to only use /by-num/.
For fastboot to work you will need the fastboot drivers installed. Not sure if it uses the standard fastboot drivers or its own so Google might help. Try the ones in the zmax forum. You're the guy with lollipop, right?
bichofelix said:
You're the guy with lollipop, right?
Click to expand...
Click to collapse
lollipop? As in Android 5.1 on a ZTE LEVER LTE? Yes I am that guy. Right now I am doing all this on my phone which is 4.4.4 and then I will perform the same on the 5.1 ZTE LEVER LTE.