Related
Hi all,
Thought i share my work with porting a ROM from the p9 lite onto my honor 5c nem-ul10 chinese phone. This should work on all variants of the honor 5c models.
I have stripped out all the huawei apps and tried to make it a close to google stock apps that i use daily. It has adaway, busybox, Wi-Fi privacy police and viper4android installed and is rooted with superuser
As always, i take no responsibility if you brick your phone. Do a full backup of your phone before flashing.
I'd recommend doing a full wipe before installing.
Haven't figured yet how to make a flashable zip yet, but am sharing a TWRP backup of the ROM of my work.
Please say thanks if you like my work, feedback welcome.
http://goo.gl/wae4nx
Cheers,
Paul
Wondering if it will work on NEM-TL00H.What about the Baseband?
索素伊凌子 said:
Wondering if it will work on NEM-TL00H.What about the Baseband?
Click to expand...
Click to collapse
Shouldn't be an issue, just make sure you take a full backup you can go back too if this doesn't work
OK,thanks a lot!
Liffeyman said:
Hi all,
Haven't figured yet how to make a flashable zip yet, but am sharing a TWRP backup of the ROM of my work.
Cheers,
Paul
Click to expand...
Click to collapse
Lay out the firmware file which you ported, I will try to make ZIP for TWRP
DRUGER said:
Lay out the firmware file which you ported, I will try to make ZIP for TWRP
Click to expand...
Click to collapse
https://mega.nz/#F!N49UgYSb!yJB-a_O4YABQe2i-_lD58w
thats the full rom for the p9lite, not the stripped version in my rom
What about compatibilty with Honor 7 Lite? Its the same phone as Honor 5c, the only difference is LTE support in Honor 7 Lite.
sajty said:
What about compatibilty with Honor 7 Lite? Its the same phone as Honor 5c, the only difference is LTE support in Honor 7 Lite.
Click to expand...
Click to collapse
Hey, it should work, if the SOC is the same as the 5c. I have been able to across flash any of the ROMs used on the Kirin 650 chip.
Just make sure you have a full twrp backup, i'd even go as far as testing the backup. Have you been able to get able to find the official ROM for your phone?
Hello,
I have bought an Honor 5C, chinese version (NEM-UL10).
Can i flash any of the international (european) official 5C roms?
Thank you
Miguel
mjjferreira said:
Hello,
I have bought an Honor 5C, chinese version (NEM-UL10).
Can i flash any of the international (european) official 5C roms?
Thank you
Miguel
Click to expand...
Click to collapse
You can but only if you follow this guide http://forum.xda-developers.com/hon...de-porting-5c-models-p9-lite-roms-5c-t3444021
If you try using the dload method it crap out tell you its the wrong version
Thank yoy
Just wondering what roms have worked successfully on the RS988, as well as Kernels. I've not seen any evidence of any compatibility, but I'm not sure I want to risk it without confirming that first. Thanks for any and all replies.
To the best of my knowledge... none.
alex03man said:
Just wondering what roms have worked successfully on the RS988, as well as Kernels. I've not seen any evidence of any compatibility, but I'm not sure I want to risk it without confirming that first. Thanks for any and all replies.
Click to expand...
Click to collapse
ED2O9 said:
To the best of my knowledge... none.
Click to expand...
Click to collapse
Yeah currently there ate no ROMs or kennels for any other devices except h830 (t mobile) and h850 (unlocked European version). This is due to the fact that those were the only devices that could be boot loader unlocked. Now if this new method is working for you guys on other devices and you have working twrp for your devices that actually flash files then the devs building ROMs for the two currently supported should be able to include the other devices but do NOT flash any roms for any other device to yours. Kindly ask the devs (like @King_lilrowrow or @gwolfu) if they could support your devices. I don't currently fully know if this is possible as I'm not sure you guys can flash files via twrp successfully yet, you would have to ask a dev. If unable to flash files you may need twrp updated for each device (kernel specific stuff), but again not sure as I'm not a developer. Hopefully this heels and hopefully you guys get a chance to enjoy custom ROMs like I have. I know I couldn't deal without, I'm a flashaholic. I actually returned my RS988 for a h830.
jeffsga88 said:
Yeah currently there ate no ROMs or kennels for any other devices except h830 (t mobile) and h850 (unlocked European version). This is due to the fact that those were the only devices that could be boot loader unlocked. Now if this new method is working for you guys on other devices and you have working twrp for your devices that actually flash files then the devs building ROMs for the two currently supported should be able to include the other devices but do NOT flash any roms for any other device to yours. Kindly ask the devs (like @King_lilrowrow or @gwolfu) if they could support your devices. I don't currently fully know if this is possible as I'm not sure you guys can flash files via twrp successfully yet, you would have to ask a dev. If unable to flash files you may need twrp updated for each device (kernel specific stuff), but again not sure as I'm not a developer. Hopefully this heels and hopefully you guys get a chance to enjoy custom ROMs like I have. I know I couldn't deal without, I'm a flashaholic. I actually returned my RS988 for a h830.
Click to expand...
Click to collapse
If other G5's have BL unlocked and a working build of TWRP then it will be easy for me to add support to my CM14.1 (LineageOS) builds.
The TWRP version targeting 20a/b isn't 100% needed but avoids issues with TZ assertion.
The only device I'm aware of thats close to an unlock method (via someone I know) is the H840 (LG G5 SE)
When any other G5 model is supported you'll see it on our GitHub site: https://www.github.com/ConquestTeam/
King_lilrowrow said:
If other G5's have BL unlocked and a working build of TWRP then it will be easy for me to add support to my CM14.1 (LineageOS) builds.
The TWRP version targeting 20a/b isn't 100% needed but avoids issues with TZ assertion.
The only device I'm aware of thats close to an unlock method (via someone I know) is the H840 (LG G5 SE)
When any other G5 model is supported you'll see it on our GitHub site: https://www.github.com/ConquestTeam/
Click to expand...
Click to collapse
Yeah from what I read in this thread http://forum.xda-developers.com/lg-g5/how-to/guide-adb-root-rw-dm-verity-off-sprint-t3523499 it appears that this method allowed them to flash twrp, although not sure if it's working 100% (I know they're having issues flashing SuperSU). Not sure if it's also unlocking the boot loader or not or of it simply bypasses the boot loader unlocking issues like old exploits on g2, g3 and g4. But as I said before I'm on h830 so not sure about this method and what exactly it's doing. But it appears to replace recovery with twrp. Also it appears to only be disabling DM verity and mounting system as rw via adb, not sure if it's allowing you to do this via twrp or not. Again if not, I'm assuming that you may need a new twrp built based on the modified kernel and boot image this method flashes. If that's they case maybe someone can goto twrp thread and ask support to be added specifically for these other versions, don't know.
King_lilrowrow said:
When any other G5 model is supported you'll see it on our GitHub site: https://www.github.com/ConquestTeam/
Click to expand...
Click to collapse
Getting a 404.
fallenturtle said:
Getting a 404.
Click to expand...
Click to collapse
github.com/kinglilrowrow
The team I was in parted ways, I work alone now
King_lilrowrow said:
github.com/kinglilrowrow
The team I was in parted ways, I work alone now
Click to expand...
Click to collapse
Since RS988 is now bootloader unlockable, do you have any plans to support this device?
I appreciate your work!!
lentm said:
Since RS988 is now bootloader unlockable, do you have any plans to support this device?
I appreciate your work!!
Click to expand...
Click to collapse
At this time my focus is bringing up the G6 as well as a few other projects I'm working on.
I may look into supporting the RS988 and H840 shortly.
King_lilrowrow said:
At this time my focus is bringing up the G6 as well as a few other projects I'm working on.
I may look into supporting the RS988 and H840 shortly.
Click to expand...
Click to collapse
Sorry to bug, but did you ever get the chance to look into RS988 support?
Thanks.
King_lilrowrow said:
At this time my focus is bringing up the G6 as well as a few other projects I'm working on.
I may look into supporting the RS988 and H840 shortly.
Click to expand...
Click to collapse
Any update? I'd really appreciate rs988 support!
RS988 Porting
So now that we have full bootloader and root capability w/custom recovery. Does anyone know what it would take to port any AOSP ROMS or stock ROM's like Fulmics to this device?
jmgamer12 said:
So now that we have full bootloader and root capability w/custom recovery. Does anyone know what it would take to port any AOSP ROMS or stock ROM's like Fulmics to this device?
Click to expand...
Click to collapse
Not sure but I do know it would make many of us very happy to see it. I've not stumbled upon the root procedure yet but anxious to get started.
LGtMgG2t said:
Not sure but I do know it would make many of us very happy to see it. I've not stumbled upon the root procedure yet but anxious to get started.
Click to expand...
Click to collapse
If you look it up in XDA, there Are already threads with bootloader unlock + root + TWRP threads to get you started. I'm running stock rooted and it's pretty solid. Just wanna see if this device can get into the ROM game
Sent from my RS988 using Tapatalk
Hey, did you use TWRP? Thx
jmgamer12 said:
So now that we have full bootloader and root capability w/custom recovery. Does anyone know what it would take to port any AOSP ROMS or stock ROM's like Fulmics to this device?
Click to expand...
Click to collapse
Yes
-lukin- said:
Hey, did you use TWRP? Thx
Click to expand...
Click to collapse
Yes. It's currently the only custom recovery for this device.
Cool I see h830 and h850 on the TWRP devices page. So rs988 works too? :good:
jmgamer12 said:
Yes. It's currently the only custom recovery for this device.
Click to expand...
Click to collapse
-lukin- said:
Cool I see h830 and h850 on the TWRP devices page. So rs988 works too? :good:
Click to expand...
Click to collapse
If you poke around LG G6 ROM Development forums you'll find a thread on unlocking bootloader's for this device and there is a download for the RS988 specific TWRP. It's not on the TWRP site
Sent from my RS988 using Tapatalk
"LG G5 ROM Development forums" - Good tip!
jmgamer12 said:
If you poke around LG G6 ROM Development forums you'll find a thread on unlocking bootloader's for this device and there is a download for the RS988 specific TWRP. It's not on the TWRP site
Sent from my RS988 using Tapatalk
Click to expand...
Click to collapse
-lukin- said:
"LG G6 ROM Development forums" - Good tip!
Click to expand...
Click to collapse
Whoops slight error. I meant LG G5
Sent from my RS988 using Tapatalk
http://www.ztemobile.de/forums/topic/zte-sucht-axon-7-android-nougat-beta-tester/
A couple of days ago i had contact with ZTE Germany for this N update. (my previous post)
They stated clearly that this update was scheduled for end of january.
Now, today as i read, they are looking for 20 testers...isn't this not a little bit too late when a release would be scheduled by the end of this month ?
In general how quick can a beta Nougat be tested to release a full working N?
Didnt they sey end of february mid march? not really sure but i think i read something like that on a screenshot from zte germany
MrPepperino said:
Didnt they sey end of february mid march? not really sure but i think i read something like that on a screenshot from zte germany
Click to expand...
Click to collapse
That was for the mini version
Maybe someone would ask in the thread. Really sad if they change the release
Well, the A2017U and A2017G are pretty similiar, so I guess they already have most of the features in.
A sprint is about 2 weeks and you can go from a public beta to release in one or two sprints.
Sent from my ZTE A2017G using Tapatalk
razorsbk said:
A sprint is about 2 weeks and you can go from a public beta to release in one or two sprints.
Sent from my ZTE A2017G using Tapatalk
Click to expand...
Click to collapse
How do you know they are working with sprints? How do you know they have 2 week sprints? Still, big issues can come from the public beta test which will delay the release.
razorsbk said:
A sprint is about 2 weeks and you can go from a public beta to release in one or two sprints.
Sent from my ZTE A2017G using Tapatalk
Click to expand...
Click to collapse
Had some further discussion this morning with ZTE.
They keep holding the date of the end of January even with this test...let's wait and see.
ZTE remarked also that the update to Nougat would imply that it would be difficult and not be recommandable to downgrade to 6 again (if you would/want/needed to).
Can someone confirm this that downgrading to 6 would be very tricky and risky?
Hmm I think that with ADB method it shouldn't be tricky - but I might be wrong. May the update will change recovery / bootloader idk.
PS. I'm from Poland and I do not speak Germany but I will be willing to help as beta tester.
MrMD69 said:
Hmm I think that with ADB method it shouldn't be tricky
Click to expand...
Click to collapse
I would think ADB would make this easy as usual, but i have never downgraded (if i and other users are needed to for some reason) before.
Perhaps someone, who has allready performed a OS-downgrade before or does know exactly how this should be done, could give us some insight in this ( even to prevent some possible issues in the future)
raystef66 said:
I would think ADB would make this easy as usual, but i have never downgraded (if i and other users are needed to for some reason) before.
Perhaps someone, who has allready performed a OS-downgrade before or does know exactly how this should be done, could give us some insight in this ( even to prevent some possible issues in the future)
Click to expand...
Click to collapse
It's usually very easy (done it with a Nexus 5, Xperia Ray, Xperia Z1 Compact, Oneplus X). You just have to flash the previous OS's zip in recovery - or, in the Galaxy and Xperia's cases, with a PC tool (Odin, Flashtool). The Oneplus was the most complicated but even that was simple - I had to flash the older bootloader as well. Although ZTE may have something up their sleeve... I'm not sure.
Here's hoping Nougat will be so good we won't want to downgrade!
As long as ZTE doesn't do nasty things in the bootloader downgrading on unlocked devices will be trivial and very likely possible on locked ones too.
If they install more restrictive bootloader you can probably avoid that by keeping the old one but that means blindly flashing the OTA won't be an option.
Personally I feel like nougat would have to be exceptional for me to live with stock and to renounce xposed, otherwise I will stick with lineage for the time being.
NadavCE said:
It's usually very easy (done it with a Nexus 5, Xperia Ray, Xperia Z1 Compact, Oneplus X). You just have to flash the previous OS's zip in recovery - or, in the Galaxy and Xperia's cases, with a PC tool (Odin, Flashtool). The Oneplus was the most complicated but even that was simple - I had to flash the older bootloader as well. Although ZTE may have something up their sleeve... I'm not sure.
Here's hoping Nougat will be so good we won't want to downgrade!
Click to expand...
Click to collapse
Indeed let's hope the N update is that good we dont need to downgrade afterall
I saw some reflashing of a nexus from Lollipop to Kitkat and it was really simple. Just flash in ADB the 'flash-all' with an unlocked BL and you're good to go.(+wipe data/factory data reset in recovery)
If there is no flash-all file which files have to be flashed in fastboot and in what order ? Is there some guide to do this properly for all type of phones using ADB?
raystef66 said:
Indeed let's hope the N update is that good we dont need to downgrade afterall
I saw some reflashing of a nexus from Lollipop to Kitkat and it was really simple. Just flash in ADB the 'flash-all' with an unlocked BL and you're good to go.(+wipe data/factory data reset in recovery)
If there is no flash-all file which files have to be flashed in fastboot and in what order ? Is there some guide to do this properly for all type of phones using ADB?
Click to expand...
Click to collapse
IIRC the order is: bootloader, recovery, system. But there are a ton of guides online, and here on XDA, that you can use to verify :good:
raystef66 said:
I would think ADB would make this easy as usual, but i have never downgraded (if i and other users are needed to for some reason) before.
Perhaps someone, who has allready performed a OS-downgrade before or does know exactly how this should be done, could give us some insight in this ( even to prevent some possible issues in the future)
Click to expand...
Click to collapse
I downgraded Moto g xt1039 from 7.1.1 to original 4.0.2 (or 5.x I can not remember) via service menu recovery. That was super easy - sotck OTA image (flashable with all things eg. Bootloader, recovery etc), then fews pushing , wipe, reboot and done
You can find step by step guide in Moto g 4g development submenu on XDA
As mentioned above, sometimes changes are made in the bootloader which deny a downgrade. Same with the modem/baseband. I've seen older moto g's (xt1031) refuse to work with a downgraded baseband.
As enthusiasts, we'll have to take apart the update and flash only what needs to be flashed to obtain a working nougat.
There is a possibility of partitions changing when going to nougat. There was some added partitions that if you went to roll on one of the phones that I have owned that would brick your phone if it wasn't done correctly. I wish that I could remember the phone but the update added something like 10 more partitions that dealt with bootloader security and what not. This could possibly be an issue but I do not know much about ZTE phones.
IIRC, htc did this on the evo 4g lte during one of the 4.x upgrades.. I believe it was on 4.3. The emmc was completely restructured.
I just bought recently MI A3 2 days ago and upon unboxing , I instantly updated it to android 10. Then I suddenly noticed on my official receipt that it is a MI A3 EU... But here is my current rom and it came from OTA. MI meaning it is global. The store is an official MI Store here in the Philippines. In the box it has EU label also next to MI A3 label. Am i global or EU? Planning to unlock and flash stock pie and relock
You are definitely in Global ROM, as the Android 10 EU ROM haven't rolled out yet. Also, there are no practical differences between one rom or another, more than EU policies and stuff like that.
wilburyh said:
You are definitely in Global ROM, as the Android 10 EU ROM haven't rolled out yet. Also, there are no practical differences between one rom or another, more than EU policies and stuff like that.
Click to expand...
Click to collapse
Well actually just concern with warranty
Do not downgrade Android version after you successfully installed Android 10. There are user reports and also Xiaomi confirms that it makes permanent changes to some partitions and your phone won't work correctly after the downgrade.
_mysiak_ said:
Do not downgrade Android version after you successfully installed Android 10. There are user reports and also Xiaomi confirms that it makes permanent changes to some partitions and your phone won't work correctly after the downgrade.
Click to expand...
Click to collapse
Thank you for the warning i almost did it. But what are the suppose issues others are reporting? Even in fastboot issues will arise?
amnher said:
Thank you for the warning i almost did it. But what are the suppose issues others are reporting? Even in fastboot issues will arise?
Click to expand...
Click to collapse
Ok. When i had chat with Xiaomi chat support. Technician told me that it is safe to downgrade android version. There will be no issues provided i perform factory reset.
amnher said:
Thank you for the warning i almost did it. But what are the suppose issues others are reporting? Even in fastboot issues will arise?
Click to expand...
Click to collapse
Official warning: https://c.mi.com/thread-2918723-1-0.html
I can't find the report on mi forum, but I recall that it was non functional WiFi and maybe some other things. Most probably related to persist partition.
There is no other option how to rollback than to use Fastboot, so yes, even if you use Fastboot you're risking non functional phone.
I don't know about stock 9 rom, but after I flashed the offical Android 10 rom, I went back to miui (which is Android 9) and my phone is working perfectly fine.
_mysiak_ said:
Official warning: https://c.mi.com/thread-2918723-1-0.html
I can't find the report on mi forum, but I recall that it was non functional WiFi and maybe some other things. Most probably related to persist partition.
There is no other option how to rollback than to use Fastboot, so yes, even if you use Fastboot you're risking non functional phone.
Click to expand...
Click to collapse
That is so unfortunate I dont wanna risk my 2 day old phone
Termi92 said:
I don't know about stock 9 rom, but after I flashed the offical Android 10 rom, I went back to miui (which is Android 9) and my phone is working perfectly fine.
Click to expand...
Click to collapse
Well MIUI is different from Android One
Is there a tutorial like this for Honor 5X?
https://www.reddit.com/r/LineageOS/comments/am6dn9/encrypt_phone_on_oneplus_3_not_working/
ephemunch said:
Is there a tutorial like this for Honor 5X?
https://www.reddit.com/r/LineageOS/comments/am6dn9/encrypt_phone_on_oneplus_3_not_working/
Click to expand...
Click to collapse
Just clean flash it.
Edit: Last time I encrypted my lineageos, I couldn't flash anyting through twrp as it wouldn't ask me for decryption password. So make sure your current TWRP supports decryption or else you'll run in to the same problem as I did.
Then I can't take the risk if it wasn't possible to flash via TWRP (twrp-3.4.0-0-kiwi).
So you couldn't even flash LineageOS updates.
Goddamit. 2020 (almost 2021) and still not possible to encrypt smartphone easily with LineageOS+TWRP.
ephemunch said:
Then I can't take the risk if it wasn't possible to flash via TWRP (twrp-3.4.0-0-kiwi).
So you couldn't even flash LineageOS updates.
Goddamit. 2020 (almost 2021) and still not possible to encrypt smartphone easily with LineageOS+TWRP.
Click to expand...
Click to collapse
Those decryption commits never went far with developers. Also, you should not encrypt this device, it will lag like hell probably.
ephemunch said:
Goddamit. 2020 (almost 2021) and still not possible to encrypt smartphone easily with LineageOS+TWRP.
Click to expand...
Click to collapse
To be fair, it's just this one device. I don't have any other device that doesn't support encryption. I have 5 other devices currently running LOS all with encryption that work perfectly. The only one that hasn't ever worked correctly has been the Honor 5X.