Can anyone assist by pointing me in the right direction as to where I can find the gpt partition table for the Honor 5X?
TIA
metpolds said:
Can anyone assist by pointing me in the right direction as to where I can find the gpt partition table for the Honor 5X?
TIA
Click to expand...
Click to collapse
Only the L21 has a GPT partition that i can find
deadman96385 said:
Only the L21 has a GPT partition that i can find
Click to expand...
Click to collapse
Wow that seems strange. Thankyou for the information. Prior to receiving my L24 I made a handfull of Logos in anticipation of owners being able use them but as of at this time I can't load them into the appropriate partition. Still never say never I'll keep working away at it.
metpolds said:
Wow that seems strange. Thankyou for the information. Prior to receiving my L24 I made a handfull of Logos in anticipation of owners being able use them but as of at this time I can't load them into the appropriate partition. Still never say never I'll keep working away at it.
Click to expand...
Click to collapse
The logos go into /cust/hw/usa/logo on L24 in a oemlogo.mbn format
deadman96385 said:
The logos go into /cust/hw/usa/logo on L24 in a oemlogo.mbn format
Click to expand...
Click to collapse
Thanks for that info, I'll practice on my L24 until I'm certain I'm getting them right then I'll post.
Related
A2017G B02 successfully flashed and booted on A2017U (using update.zip). WiFi/Bluetooth and GPS working. Only broken piece is the cellular.
There are a few more color choices in themes but no 'Android Stock' theme. And a glove mode which would likely be useful here in northern Canada.
This should be good news for development as there appears to be only the modem differentiating the ROMs.
Now to see how well I can return to A2017U [UPDATE] Returning to A2017U I had to delete my call logs. The database version was newer in the A2017G, and it created a launcher crash loop. I used titanium backup to delete the call logs.
Don't do this. You could quite likely brick. But if you're going to anyway:
Point 1 : If this doesn't make sense to you, don't do it; you're in over your head.
Get a backup of ALL of your partitions using dd.
I copied the A2017G B02 update.zip to the root of my SD card, and flashed the recovery.img from that update.zip overtop of TWRP from within TWRP using dd. Refer to Point 1. Booted the phone to system, went to updates, and did the factory update from root of SD card. Remember, you will be stock A2017G which means no root/TWRP. You will have to use the method here assuming you now have an A2017G to get TWRP back on the device. I then flashed my NON-HLOS.bin from the backup I made earlier over modem partition.
The launcher sucks more than the stock one on A2017U as there is no menu button.
I believe you could just flash system.img (system.new.dat) and boot.img to get the same experience as that's the only two I flashed to return to A2017U (I had to flash NON-HLOS.bin back to A2017U).
Really good to know, so it should be also possible reversely and a ray of hope to unlock the G version somehow
Nice work! I guess this answers my questions as to whether the flash would unlock the different bands not included on the north American variant
Someone flash the U version to G please since the U version is a lot better than G atm haha
cctbrkr said:
Nice work! I guess this answers my questions as to whether the flash would unlock the different bands not included on the north American variant
Click to expand...
Click to collapse
Well, that would be part of the modem part, which isn't the same. The only way to get that to happen would be to use the QC recovery tools that let you tinker in the actual modem bits.
rikin93 said:
Someone flash the U version to G please since the U version is a lot better than G atm haha
Click to expand...
Click to collapse
Unfortunately, we can't do that well since there aren't any U factory images yet. It would have to be cobbled together from backups people make of all the different partitions, and even then it would have to be done via a bootloader unlocked version, which is only the U model.
Com' on ZTE -- release those factory images.
Hmm so that still sounds promising. Obviously we won't get hands on the recovery tool though?
jkuczera said:
A2017G B02 successfully flashed and booted on A2017U (using update.zip). WiFi/Bluetooth and GPS working. Only broken piece is the cellular.
There are a few more color choices in themes but no 'Android Stock' theme. And a glove mode which would likely be useful here in northern Canada.
This should be good news for development as there appears to be only the modem differentiating the ROMs.
Now to see how well I can return to A2017U
Click to expand...
Click to collapse
Can you try something before you switch back? If you have a good router (ac, multiple streams, 5ghz) can you check your link speed? You can use an app like aida64 to spit that info out in the network tab. The reason I ask, is because 2017U (actual models not software) reports 433Mbps being the max, while 2017G reports 866Mbps. We are trying to figure out if the US model got the cheaper wifi chip or if they screwed up the code.
test878 said:
Can you try something before you switch back? If you have a good router (ac, multiple streams, 5ghz) can you check your link speed? You can use an app like aida64 to spit that info out in the network tab. The reason I ask, is because 2017U (actual models not software) reports 433Mbps being the max, while 2017G reports 866Mbps. We are trying to figure out if the US model got the cheaper wifi chip or if they screwed up the code.
Click to expand...
Click to collapse
Yepper
jkuczera said:
Yepper
Click to expand...
Click to collapse
Nice to know that it's just a software thing.
Can you also try going far from your router, into an area with low signal, and turn on the "Signal Boost" option? Would be interesting to see if that's another software thing.
xtermmin said:
Nice to know that it's just a software thing.
Can you also try going far from your router, into an area with low signal, and turn on the "Signal Boost" option? Would be interesting to see if that's another software thing.
Click to expand...
Click to collapse
From the graphic on 'signal boost', it's for cellular (telephony) only. Wifi is not pictured or mentioned.
jkuczera said:
From the graphic on 'signal boost', it's for cellular (telephony) only. Wifi is not pictured or mentioned.
Click to expand...
Click to collapse
Ah, bummer, thanks for checking.
Wonder if there's a way to obtain the NON-HLOS.bin modem from a 2017U unit...
xtermmin said:
Wonder if there's a way to obtain the NON-HLOS.bin modem from a 2017U unit...
Click to expand...
Click to collapse
Just flashed the modem.img from my A2017U backup and now telephony is working as well.
jkuczera said:
Just flashed the modem.img from my A2017U backup and now telephony is working as well.
Click to expand...
Click to collapse
Holy snap, Chief post steps and where you got these files, wanna give it all try old.
jkuczera said:
Just flashed the modem.img from my A2017U backup and now telephony is working as well.
Click to expand...
Click to collapse
So, you're running the 2017G with the U modem?
DrakenFX said:
Holy snap, Chief post steps and where you got these files, wanna give it all try old.
Click to expand...
Click to collapse
With root, you should be able to dd or cat out all of the partitions from a root shell. Then you can backup all of the partitions as they exist in flash (blank space and all).
TeutonJon78 said:
With root, you should be able to dd or cat out all of the partitions from a root shell. Then you can backup all of the partitions as they exist in flash (blank space and all).
Click to expand...
Click to collapse
Only problem I have is not knowing their extension , I know how to use "dd" but isn't a issue dumping without the right extension? (.img, .bin, etc) and I meant I How-To guide for others users if they wanna try.
TeutonJon78 said:
So, you're running the 2017G with the U modem?
Click to expand...
Click to collapse
Yes
DrakenFX said:
Holy snap, Chief post steps and where you got these files, wanna give it all try old.
Click to expand...
Click to collapse
Refer to updated OP
DrakenFX said:
Only problem I have is not knowing their extension , I know how to use "dd" but isn't a issue dumping without the right extension? (.img, .bin, etc) and I meant I How-To guide for others users if they wanna try.
Click to expand...
Click to collapse
DD does not care about file extensions. It also doesn't care if you should flash to the wrong partition and permanently brick your device.
jkuczera said:
Just flashed the modem.img from my A2017U backup and now telephony is working as well.
Click to expand...
Click to collapse
Where did you take the modem.img from for the a2017u?
manu7irl said:
Where did you take the modem.img from for the a2017u?
Click to expand...
Click to collapse
Code:
adb shell
su
dd if=/dev/block/bootdevice/by-name/modem of=/sdcard/modem.img
and to pull to your adb directory
adb pull /sdcard/modem.img
Or use " modem_a2017u.img " To knowlage is from a2017u
DrakenFX said:
To knowlage is from a2017u
Click to expand...
Click to collapse
Could you post it here please.
manu7irl said:
Could you post it here please.
Click to expand...
Click to collapse
Will be easier for you just to pulled using your a7 using the command line from previous post.
Hi all, currently I'm on build number B360, L22 India. I want to use the custom roms available for this phone.
I read in one of the threads that the phone doesn't boot on this build, so wanted to know if there is any process to downgrade from B360 to B340 so that I can use the roms available for this phone. I regret my decision of upgrading my phone to the latest build..:crying:
Need help desperately
Any suggestions? Thanks
vishal.ekka said:
Hi all, currently I'm on build number B360, L22 India. I want to use the custom roms available for this phone.
I read in one of the threads that the phone doesn't boot on this build, so wanted to know if there is any process to downgrade from B360 to B340 so that I can use the roms available for this phone. I regret my decision of upgrading my phone to the latest build..:crying:
Need help desperately
Any suggestions? Thanks
Click to expand...
Click to collapse
Any Rom that works on B340 will also work on B360. What you read was wrong
Sent from my SM-N920T using Tapatalk
clsA said:
Any Rom that works on B340 will also work on B360. What you read was wrong
Click to expand...
Click to collapse
I read it here..
http://forum.xda-developers.com/hon...ogenmod-13-0-official-kiw-l24-t3430945/page91
That's the reason I'm hesitant in flashing these roms.
vishal.ekka said:
I read it here..
http://forum.xda-developers.com/hon...ogenmod-13-0-official-kiw-l24-t3430945/page91
That's the reason I'm hesitant in flashing these roms.
Click to expand...
Click to collapse
I see now, thanks for correcting me. Seems some things indeed changed while I was on vacation.
you should be able to easily revert to B340 with the files in the repository
clsA said:
I see now, thanks for correcting me. Seems some things indeed changed while I was on vacation.
you should be able to easily revert to B340 with the files in the repository
Click to expand...
Click to collapse
No problem:good:
Any chance
stinka318 said:
Any chance
Click to expand...
Click to collapse
There are many people that try to help.
I dont really see much of a question here.
What seems to be the issue?
What is needed is a modified kdz with cust to suite the regional zone......so I don't get the warning I keep getting on boot.
stinka318 said:
What is needed is a modified kdz with cust to suite the regional zone......so I don't get the warning I keep getting on boot.
Click to expand...
Click to collapse
basically there isn't one you have asked many times now.
Only option is to make one your self.
TheMadScientist420 said:
basically there isn't one you have asked many times now.
Only option is to make one your self.
Click to expand...
Click to collapse
No computer skills have little issue called dyslexia.....
TheMadScientist420 said:
basically there isn't one you have asked many times now.
Only option is to make one your self.
Click to expand...
Click to collapse
I have noticed that on the LG g3 there is a cust restore zip just wondering if someone could please look at it for me.......thanks in advance.
stinka318 said:
I have noticed that on the LG g3 there is a cust restore zip just wondering if someone could please look at it for me.......thanks in advance.
Click to expand...
Click to collapse
just because there is one for the G3 dont mean there is for the G5.
Again google is your friend
Hey!
I recently saw that a lot of updates were available for Lineage. However, last time I tried updating, I entered a bootloop that was acting exactly like the one of me trying to boot LineageOS when I used to be on over B442.
I was just wondering if anyones knows enough about all this VolTE stuff to help me.
Thanks !
Mikor4554 said:
Hey!
I recently saw that a lot of updates were available for Lineage. However, last time I tried updating, I entered a bootloop that was acting exactly like the one of me trying to boot LineageOS when I used to be on over B442.
I was just wondering if anyones knows enough about all this VolTE stuff to help me.
Thanks !
Click to expand...
Click to collapse
Hi, have you look around all forums and post ?
Its written n times no volte on custom roms. You have to fallback to a compatible Fw stock version
Mikor4554 said:
Hey!
I recently saw that a lot of updates were available for Lineage. However, last time I tried updating, I entered a bootloop that was acting exactly like the one of me trying to boot LineageOS when I used to be on over B442.
I was just wondering if anyones knows enough about all this VolTE stuff to help me.
Thanks !
Click to expand...
Click to collapse
no volte for custom roms ,,,,,
and also you will get bootloop if you flash a custom rom while you are on volte enabled firmware
so I should go back to a stock EMUI that was before VolTE and then intall Lineage ?
if so, how can I do that, knowing that I have the Chinese version (KIW-UL00) and stock firmwares are REALLY hard to find
Mikor4554 said:
so I should go back to a stock EMUI that was before VolTE and then intall Lineage ?
if so, how can I do that, knowing that I have the Chinese version (KIW-UL00) and stock firmwares are REALLY hard to find
Click to expand...
Click to collapse
Yes you need to go back to non volte firmware..
You need a rollback package to do that and stock firmware.
Mikor4554 said:
so I should go back to a stock EMUI that was before VolTE and then intall Lineage ?
if so, how can I do that, knowing that I have the Chinese version (KIW-UL00) and stock firmwares are REALLY hard to find
Click to expand...
Click to collapse
Yeah as you said its really hard - though i got you the older ones hope this helps and re-flashing the newest after the older firmware
KIW L21
KIW L22
KIW L24
kartrikpal said:
Yeah as you said its really hard - though i got you the older ones hope this helps and re-flashing the newest after the older firmware
KIW L21
KIW L22
KIW L24[/QUOTE
Thank you, but I'm not sure this can help.
As of what I found, I need to flash the update.app from an SD card.
However, I have read that this doesn't work if you have TWRP. Does flashing the separate boot.img, recovery.img,system.img and the other one that I don't remember will work?
Click to expand...
Click to collapse
Mikor4554 said:
Yeah as you said its really hard - though i got you the older ones hope this helps and re-flashing the newest after the older firmware
KIW L21
KIW L22
KIW L24[/QUOTE
Thank you, but I'm not sure this can help.
As of what I found, I need to flash the update.app from an SD card.
However, I have read that this doesn't work if you have TWRP. Does flashing the separate boot.img, recovery.img,system.img and the other one that I don't remember will work?
Click to expand...
Click to collapse
These won't work for you as these are for other models.
Mikor4554 said:
kartrikpal said:
Yeah as you said its really hard - though i got you the older ones hope this helps and re-flashing the newest after the older firmware
KIW L21
KIW L22
KIW L24[/QUOTE
Thank you, but I'm not sure this can help.
As of what I found, I need to flash the update.app from an SD card.
However, I have read that this doesn't work if you have TWRP. Does flashing the separate boot.img, recovery.img,system.img and the other one that I don't remember will work?
Click to expand...
Click to collapse
those wont work for him..he has CLOO model
Click to expand...
Click to collapse
Again you don't need to repeat what I said.
Fixed your issue op?
Need Oeminfo(C567) backup with TWRP BLA-A09
thanks
oeminfo is useless
salland said:
oeminfo is useless
Click to expand...
Click to collapse
for what it is useless?
if you have, share
Oeminfo
geogsm_1 said:
for what it is useless?
if you have, share
Click to expand...
Click to collapse
Nobody is going to share a backup containing their oeminfo containing their IMEI or serial numbers.
revjamescarver said:
Nobody is going to share a backup containing their oeminfo containing their IMEI or serial numbers.
Click to expand...
Click to collapse
and it is bad then I should not share? the experience?
Sharing oeminfo
geogsm_1 said:
and it is bad then I should not share? the experience?
Click to expand...
Click to collapse
Anything that contains that information should never be shared unless you don't care that your device could be "cloned" using that information. It's generally not a good idea.
revjamescarver said:
Nobody is going to share a backup containing their oeminfo containing their IMEI or serial numbers.
Click to expand...
Click to collapse
geogsm_1 said:
and it is bad then I should not share? the experience?
Click to expand...
Click to collapse
And not just that. Your unlock code is calculated based on the IMEI in oeminfo, if it changes so does your unlock code.
And as it is now (Not sure if this is the case of C567 too), you can only get an unlock code if oeminfo is intact, as it's generated using your IMEI.
So don't use someone elses oeminfo if you still want to be able to unlock.
revjamescarver said:
Anything that contains that information should never be shared unless you don't care that your device could be "cloned" using that information. It's generally not a good idea.
Click to expand...
Click to collapse
It doesn't use the info in oeminfo for your phones actual IMEI. That's in one of the nv partitions.