Deleted. Beaups released a full unlock using this. No need.
npjohnson said:
All,
Due to the recent accidental leak of Samsung eMMC vendor commands allowing write to protected eMMC areas, we are now able to write CID values on production devices.
Beaups has written an awesome tool called 'SamsungCID' (found here: https://github.com/beaups/SamsungCID). This makes the process all teh simpler!
I have built this tool from his source, and used it on a multitude of devices that use a Samsung eMMC. It works without flaw on the Moto G (Second Generation), Galaxy S5 (VZW/ATT, though, ATT doesn't have a Developer Edition that I am aware of), and many, many others.
How does this apply to you?
The S5 uses a Samsung eMMC, and has a Developer Edition. This means that it is vulnerable to this exploit.
How can I help this progress?
I need a few thing to make this work:
- A few testers with Production devices, and root (temp-root should work fine) -- I will contact these people individually, do not ask here to test.
- One person with a Developer Edition that has root (need an aboot dump, and them to run one command).
If any of you know of someone with a Developer Edition, please get them in contact with me. I can be reached on Hangouts, or on Telegram (@npjohnson).
PLEASE do not post your CID publicly.
I will be trying to package this into an app that will extend across multiple vulnerable devices.
Click to expand...
Click to collapse
I know we'll be able to get a bootloader unlock from this, but hopefully we'll be able to get it done ASAP. I've already moved on to the Nexus 6, but I'd still love to have my S5's bootloader unlocked anyway. Good luck with this, I can't wait.
npjohnson said:
All,
Due to the recent accidental leak of Samsung eMMC vendor commands allowing write to protected eMMC areas, we are now able to write CID values on production devices.
Beaups has written an awesome tool called 'SamsungCID' (found here: https://github.com/beaups/SamsungCID). This makes the process all teh simpler!
I have built this tool from his source, and used it on a multitude of devices that use a Samsung eMMC. It works without flaw on the Moto G (Second Generation), Galaxy S5 (VZW/ATT, though, ATT doesn't have a Developer Edition that I am aware of), and many, many others.
How does this apply to you?
The S5 uses a Samsung eMMC, and has a Developer Edition. This means that it is vulnerable to this exploit.
How can I help this progress?
I need a few thing to make this work:
- A few testers with Production devices, and root (temp-root should work fine) -- I will contact these people individually, do not ask here to test.
- One person with a Developer Edition that has root (need an aboot dump, and them to run one command).
If any of you know of someone with a Developer Edition, please get them in contact with me. I can be reached on Hangouts, or on Telegram (@npjohnson).
PLEASE do not post your CID publicly.
I will be trying to package this into an app that will extend across multiple vulnerable devices.
Click to expand...
Click to collapse
cant wait to see this going
So how have you gone about compiling and running this? Try as I may I can't seem to do a proper build. It's probably the lowest of the low, but if you could send me a binary, I'd greatly appreciate it
I'd be more than willing to try it on my rooted verizon s5.
Successfully compiled the tool - currently scouring the internet looking for anyone with a developer edition that might be able to help, we should have this done in no time. Have already sent out messages to a few, will look for more. I'll PM you if I get any details
Kinda cool watching this unfold over a few weeks, I'm really excited for what's to come.
You all need to check something else first, you need your current CID
If it starts with anything other than 15, this will not work for you. Samsung EMMC's start with CID 15, Toshiba 11, and there may be more. If you Don't start with 15, this WILL NOT WORK.
Regarding a compiled verison
http://s000.tinyupload.com/?file_id=64141875024257149501
Yeah...unfortunately mine starts with an 11 :c
Yep, mine starts with a 15. I'm ready to start any testing. All of my possible developer editions have fallen through - many requesting a purchase of the actual phone. I'll keep looking, but I might be outta options atm.
I can't believe all we need to open this phone up is a dev phone for a few minutes. It would add new life. I'm searching out people as well. Hopefully we find something soon
Mine starts with a 15 and it's not my daily driver, count me in for testing!
Question. Didn't someone post in one of the forums (General or Android Development) about them having a Walmart Straight Talk S5 and that it was actually a VZW Dev Ed? Because he was wanting to put a CM ROM on it. If that's true, then we also need to find anyone with that particular device as well. If i can find the thread it was posted in I'll add the link. Found the links. If it's true we need to see if these variants could help out.
http://forum.xda-developers.com/showpost.php?p=65432642&postcount=48
http://forum.xda-developers.com/showpost.php?p=65143644&postcount=1
al50 said:
Question. Didn't someone post in one of the forums (General or Android Development) about them having a Walmart Straight Talk S5 and that it was actually a VZW Dev Ed? Because he was wanting to put a CM ROM on it. If that's true, then we also need to find anyone with that particular device as well. If i can find the thread it was posted in I'll add the link. Found the links. If it's true we need to see if these variants could help out.
http://forum.xda-developers.com/showpost.php?p=65432642&postcount=48
http://forum.xda-developers.com/showpost.php?p=65143644&postcount=1
Click to expand...
Click to collapse
That's actually brilliant. It MIGHT work, but even though they have identical hardware, I don't know if that guarantees that it will have a compatible bootloader - unless it does, in which case that's amazing, and we need to get a hold of someone with one asap. Unless they are the same model, just rebranded, I don't see this working as the bootloaders may not be signed with Verizon's keys.
True. Forgot about the VZW keys... Was thinking too much of finding a Dev Ed....lol
al50 said:
True. Forgot about the VZW keys... Was thinking too much of finding a Dev Ed....lol
Click to expand...
Click to collapse
Don't give up hope so fast. I'm getting in contact with a few people, and I'll certainly try it. This may actually be the same phone, I see a lot of websites suggesting Straight Talk phones are the exact same as Verizon ones. We shall see. My information about the keys might not even be accurate, with my limited knowledge.
It was a good thought though, even if it isn't true
How can you compile it? I'm running Ubuntu 14.04.1 and i can't even get NDK to install correctly.. Any help?
CreeperPVP said:
How can you compile it? I'm running Ubuntu 14.04.1 and i can't even get NDK to install correctly.. Any help?
Click to expand...
Click to collapse
Hmm. I dunno. I'm currently on Windows - there wasn't really any installation for NDK, just running from the extracted folder. I can post a link to a compiled version of the program, I'm pretty sure someone in another thread posted one.
---------- Post added 30th March 2016 at 12:02 AM ---------- Previous post was 29th March 2016 at 11:59 PM ----------
Here's a link to the thread, the OP has a link at the bottom. http://forum.xda-developers.com/showthread.php?t=3337909
Is there a way to check CID from the phone? I can't seem to find out how to check it, build prop and whatnot doesn't have anything about it like some places suggest, and can't use fastboot.
Sent from my SAMSUNG-SM-G900A using Tapatalk
Rakuu said:
Is there a way to check CID from the phone? I can't seem to find out how to check it, build prop and whatnot doesn't have anything about it like some places suggest, and can't use fastboot.
Sent from my SAMSUNG-SM-G900A using Tapatalk
Click to expand...
Click to collapse
Use eMMC brickbug checker on the play store. First 2 numbers of your cid should be 11 or 15. You want 15
Rakuu said:
Is there a way to check CID from the phone? I can't seem to find out how to check it, build prop and whatnot doesn't have anything about it like some places suggest, and can't use fastboot.
Sent from my SAMSUNG-SM-G900A using Tapatalk
Click to expand...
Click to collapse
Search google play for "eMMC Brickbug Check"
Sent from my SM-G900V using Tapatalk
Related
Hi,
I thought this was not yet possible to port Cyanogenmod on Dual Sim devices, at least not properly, but then I saw this post:
http://forum.xda-developers.com/showthread.php?t=2246874
It gave me a real hope for the generic MT6589 device I am currently using.
I am new to all of this, so I hope I don't bother everyone.
Also, my device uses obviously different hardware, but uses the same processor, so I managed to install the above ROM and got it working but without any screen display.
In other words, it was working, and I could see everything as far as the installation wizzard was concerned, so I thought I was fine, but then when I was done and it rebooted, I could not see anything on the display anymore, but the phone was still working working.
So I am assuming some obvious hardware drivers differences, and that the old drivers were still working till I restarted?
Is there a way to modify the rom to make it work?
What files would I need to pull from my device to add/replace in the posted ROM to make it worlk, if that is possible?
Or does cynanogenmod have to compile with the files of my device to work, even though the processor bit had already been done?
If so, I have no problem in trying to compile cyanogenmod from scratch, but I will still get the dual SIM problem, and I thought this has been fixed in this ROM.
So what modifications would need to be done to incorporate the DUAL SIM issue, and make it work, or has this already been resolved upstream?
Is there a github or such of the modifications and alterations that were done to Cyanogenmod for this posted ROM in order to get it working?
I am willing to use those files and port it to my device, but without these modifications, I will not be able to do anything, even though the kernel sources for MT6589 are openly available now.
Sorry for asking this question here, but I tried to reply to the original post and it did not let me.
Is it okay to ask this here?
If not, please excuse me, and if you can forward me to the right place.
Thanks and regards
noobworld said:
Hi,
I thought this was not yet possible to port Cyanogenmod on Dual Sim devices, at least not properly, but then I saw this post:
http://forum.xda-developers.com/show....php?t=2246874
It gave me a real hope for the generic MT6589 device I am currently using.
I am new to all of this, so I hope I don't bother everyone.
Also, my device uses obviously different hardware, but uses the same processor, so I managed to install the above ROM and got it working but without any screen display.
In other words, it was working, and I could see everything as far as the installation wizzard was concerned, so I thought I was fine, but then when I was done and it rebooted, I could not see anything on the display anymore, but the phone was still working working.
So I am assuming some obvious hardware drivers differences, and that the old drivers were still working till I restarted?
Is there a way to modify the rom to make it work?
What files would I need to pull from my device to add/replace in the posted ROM to make it worlk, if that is possible?
Or does cynanogenmod have to compile with the files of my device to work, even though the processor bit had already been done?
If so, I have no problem in trying to compile cyanogenmod from scratch, but I will still get the dual SIM problem, and I thought this has been fixed in this ROM.
So what modifications would need to be done to incorporate the DUAL SIM issue, and make it work, or has this already been resolved upstream?
Is there a github or such of the modifications and alterations that were done to Cyanogenmod for this posted ROM in order to get it working?
I am willing to use those files and port it to my device, but without these modifications, I will not be able to do anything, even though the kernel sources for MT6589 are openly available now.
Sorry for asking this question here, but I tried to reply to the original post and it did not let me.
Is it okay to ask this here?
If not, please excuse me, and if you can forward me to the right place.
Thanks and regards
Click to expand...
Click to collapse
link is dead.
who is the dev.
prantoroy said:
link is dead.
who is the dev.
Click to expand...
Click to collapse
Thanks for the headsup.
I placed in an incomplete link, here is the complete link:
http://forum.xda-developers.com/showthread.php?t=2246874
I also updated the post.
The developper seems to be:
bgcngm
Thanks
noobworld said:
Thanks for the headup.
I placed in an incomplete link, here is the complete link:
http://forum.xda-developers.com/showthread.php?t=2246874
I also updated the post.
The developper seems to be:
bgcngm
Thanks
Click to expand...
Click to collapse
give sme time.will try
---------- Post added at 10:44 AM ---------- Previous post was at 10:42 AM ----------
prantoroy said:
give sme time.will try
Click to expand...
Click to collapse
just as I thought.the kernel.
its not fr u. ask dev to create a kernel fr u!
Thank you for your fast reply.
Where do I ask?
Also, I was hoping to learn how to do it, and have the sources if possible, or at least how to modify the sources, because I have about three of these chinese devices, all using the same processor, but with different hardware.
Thanks
prantoroy said:
give sme time.will try
---------- Post added at 10:44 AM ---------- Previous post was at 10:42 AM ----------
just as I thought.the kernel.
its not fr u. ask dev to create a kernel fr u!
Click to expand...
Click to collapse
noobworld said:
Thank you for your fast reply.
Where do I ask?
Also, I was hoping to learn how to do it, and have the sources if possible, or at least how to modify the sources, because I have about three of these chinese devices, all using the same processor, but with different hardware.
Thanks
Click to expand...
Click to collapse
Ask The dev
And Its not that easy
prantoroy said:
Ask The dev
And Its not that easy
Click to expand...
Click to collapse
Well, I tried posting on the original thread, but couldn't.
Then tried to send a private message, but couldn't.
So I started this thread.
You said:
And Its not that easy
Click to expand...
Click to collapse
Did you mean it is not easy to contact the dev, or not easy to compile the sources for my devices?
Just wanted to be sure.
Thanks again
noobworld said:
Well, I tried posting on the original thread, but couldn't.
Then tried to send a private message, but couldn't.
So I started this thread.
You said:
Did you mean it is not easy to contact the dev, or not easy to compile the sources for my devices?
Just wanted to be sure.
Thanks again
Click to expand...
Click to collapse
no you cant post until u have 10 posts
and its not easy to develop rom
prantoroy said:
no you cant post until u have 10 posts
and its not easy to develop rom
Click to expand...
Click to collapse
I can see that, but I think with some patience I can do it.
Also, I have been using Linux for years now, and it seems I just need to figure out how things are laid out in Android.
And once I get used to that, then things become easier.
I am assuming that the linux kernel needs to be compiled with the specific drivers related to my hardware, right?
However, that would still not take into account:
- The changes made in Android/Cyanogenmod that take into account Dual SIM functionality
- How Cyanogenmod is actually laid-out, such as are changes done directly to stock android, or applied as patches?
I was thinking of the following:
1) Checking for the difference between stock Android and Cyanogenmod, and save aside the diff changes to make a patch file.
2) Then hope to find the sources of the stock android that has already been modified to work with MT6589, since these devices obviously use Android on them with some modifications
3) Then apply the patch made in (1) on these sources
Thus, I also need one important question answered:
If I were to download the sources for Cyanogenmod (which I already did), are the patches to the stock Android already applied, or are they placed in a separate folder, and applied on compilation?
I have this feeling that the above patches will probably not work out, because there will probably be extra functions, code that the patch will not be able to take into account, and will have some type of non-working or broken system, until I figure out what is missing.
I might get it to boot to a certain point (most probably shell like), and it would stop there.
Well, in either case, after writing all this down, I started to visualize more the hard part you are talking about, and this would require good knowledge of Android Code and structure.
Thus, if anyone can give me the required Cyanogenmod sources that have already been modified to work on an MT6589, or the diff patches between the normal and modified Cynogenmod, then that would be amazing.
Then I will have to only figure out at that point the propriety files I need to pull from the device, and specific vendor modifications.
Of course, I am just speculating, as this depends on how Android/Cyanogenmod is structured, and I could be completely off the mark, and have no idea what I am talking about.
Thanks
noobworld said:
I can see that, but I think with some patience I can do it.
Also, I have been using Linux for years now, and it seems I just need to figure out how things are laid out in Android.
And once I get used to that, then things become easier.
I am assuming that the linux kernel needs to be compiled with the specific drivers related to my hardware, right?
However, that would still not take into account:
- The changes made in Android/Cyanogenmod that take into account Dual SIM functionality
- How Cyanogenmod is actually laid-out, such as are changes done directly to stock android, or applied as patches?
I was thinking of the following:
1) Checking for the difference between stock Android and Cyanogenmod, and save aside the diff changes to make a patch file.
2) Then hope to find the sources of the stock android that has already been modified to work with MT6589, since these devices obviously use Android on them with some modifications
3) Then apply the patch made in (1) on these sources
Thus, I also need one important question answered:
If I were to download the sources for Cyanogenmod (which I already did), are the patches to the stock Android already applied, or are they placed in a separate folder, and applied on compilation?
I have this feeling that the above patches will probably not work out, because there will probably be extra functions, code that the patch will not be able to take into account, and will have some type of non-working or broken system, until I figure out what is missing.
I might get it to boot to a certain point (most probably shell like), and it would stop there.
Well, in either case, after writing all this down, I started to visualize more the hard part you are talking about, and this would require good knowledge of Android Code and structure.
Thus, if anyone can give me the required Cyanogenmod sources that have already been modified to work on an MT6589, or the diff patches between the normal and modified Cynogenmod, then that would be amazing.
Then I will have to only figure out at that point the propriety files I need to pull from the device, and specific vendor modifications.
Of course, I am just speculating, as this depends on how Android/Cyanogenmod is structured, and I could be completely off the mark, and have no idea what I am talking about.
Thanks
Click to expand...
Click to collapse
ok I will help u.
go here
http://forum.xda-developers.com/forumdisplay.php?f=613
prantoroy said:
ok I will help u.
go here
http://forum.xda-developers.com/forumdisplay.php?f=613
Click to expand...
Click to collapse
Wow... Even though I searched for so long, I did not find this.
I guess I did not know what to search for.
I thank you a lot.
I will probably take a while to learn how to use this, so I will disappear until I figure it out.
If I managed to do anything, then will come back and post my status.
Thanks again
noobworld said:
Wow... Even though I searched for so long, I did not find this.
I guess I did not know what to search for.
I thank you a lot.
I will probably take a while to learn how to use this, so I will disappear until I figure it out.
If I managed to do anything, then will come back and post my status.
Thanks again
Click to expand...
Click to collapse
glad I could help.
and don't bother .its my job to help new.
and pm me if u need smthing.
and please close thread.
I have an old phone that uses Android 2.x, I think froyo or gingerbread. I want to download AFWall+ which is a firewall application that's the successor to DroidWall. The problem is the most recent version no longer supports the Android version used by my old phone. The app's details are here (I can't make it a hyperlink because I don't have 10 posts):
Code:
https://play.google.com/store/apps/details?id=dev.ukanth.ufirewall&hl=en
The relevant part says:
- Supports 4.x ,5.x and 6.x (for 2.x support use 1.3.4.1 version)
Click to expand...
Click to collapse
But the problem is I don't know how to get the 1.3.4.1 version and verify it is the legitimate version. There are a lot of websites that offer downloads for older versions of apks but they could inject anything they want in them couldn't they?
I would ask the developer in his thread what is the proper way to go about this but as I mentioned I don't meet the post requirements at the moment.
Thanks for any help you can offer.
agenda21 said:
I have an old phone that uses Android 2.x, I think froyo or gingerbread. I want to download AFWall+ which is a firewall application that's the successor to DroidWall. The problem is the most recent version no longer supports the Android version used by my old phone. The app's details are here (I can't make it a hyperlink because I don't have 10 posts):
Code:
https://play.google.com/store/apps/details?id=dev.ukanth.ufirewall&hl=en
The relevant part says:
But the problem is I don't know how to get the 1.3.4.1 version and verify it is the legitimate version. There are a lot of websites that offer downloads for older versions of apks but they could inject anything they want in them couldn't they?
I would ask the developer in his thread what is the proper way to go about this but as I mentioned I don't meet the post requirements at the moment.
Thanks for any help you can offer.
Click to expand...
Click to collapse
use this google search to find it.
i saw it on several sites, but cant post the links because they contain warez.
edit,
ha, im an idiot, i didnt read your whole post. yea, im not sure how you would verify.
maybe mention the dev here and he may come. @devsnamehere <-- thats how to mention someone.
bweN diorD said:
yea, im not sure how you would verify.
maybe mention the dev here and he may come. @devsnamehere <-- thats how to mention someone.
Click to expand...
Click to collapse
Thanks.
@ukanth can you tell me how to obtain and verify version 1.3.4.1?
agenda21 said:
Thanks.
@ukanth can you tell me how to obtain and verify version 1.3.4.1?
Click to expand...
Click to collapse
I thought f-droid builds still pointing to 1.3.4.1. I will upload in OP of my thread. Thanks !
ukanth said:
I thought f-droid builds still pointing to 1.3.4.1. I will upload in OP of my thread. Thanks !
Click to expand...
Click to collapse
@ukanth Sorry to bother you again but I can't find version 1.3.4.1 in your thread. Did you ever get a chance to post it somewhere? I can get it from a 3rd party website but I just need you to give me the hashes of the packages so I don't install something that's trojaned. I'm a computer programmer but I don't know much about phones, so please keep that in mind if you have special instructions. Thanks
agenda21 said:
@ukanth Sorry to bother you again but I can't find version 1.3.4.1 in your thread. Did you ever get a chance to post it somewhere? I can get it from a 3rd party website but I just need you to give me the hashes of the packages so I don't install something that's trojaned. I'm a computer programmer but I don't know much about phones, so please keep that in mind if you have special instructions. Thanks
Click to expand...
Click to collapse
@agenda21, Can you try this and let me know, this I found in my backup's. If it doesn't work, then I will build one using the old source and update it.
https://www.dropbox.com/s/c3g4lqzbltbuxfq/dev.ukanth.ufirewall-171.apk?dl=0
I raised a request in f-droid to restore the old version https://gitlab.com/fdroid/fdroiddata/issues/362 . Lets see.
Introduction:
My name as you may be able to tell is Francesco, and I am a long time user of the Samsung Galaxy S Series Devices. My current device is the SM-G935W8. I have just requested Developer Access on Android File Host so I can give access to everyone for the Stock Firmware for the SM-G935W8 of which I grabbed from Samsung SmartSwitch on Windows. I am an experienced programmer in the Languages C# and Java. I have made a few personal apps that aren't even worth mentioning.
Goal:
My Goal is to contribute and dedicate myself to the Canadian Users because I have noticed the lack of support towards them. I am currently working on a ROM based on the stock firmware of which I am trying to release. I am going to need help on it as I am rather new to this area of Android but nonetheless does not mean I am terrible. I have done my research and have gotten some of the tools that are needed and have already successfully built a ROM just not able to boot it but I believe it is because I missed a step with the boot.img. The main tool I am using is the one that Superr has created called SuperRs_Kitchen. I am currently using v1.0.5.6 as the newest version I was having issues with.
If anyone has any questions, please feel free to ask me and I will try and answer them to the best of my ability.
I will provide an upload link once and if I get approved for requesting developer access. If I don't I will then use a different mirror to host it.
Please be patient, and I do not have an ETA on when the link will be up.
Welcome Francesco! Nice to see some W8 support here! Really looking forward to see development from you
Sent from my SM-G935W8 using Tapatalk
FrancescoM01 said:
Introduction:
My name as you may be able to tell is Francesco, and I am a long time user of the Samsung Galaxy S Series Devices. My current device is the SM-G935W8. I have just requested Developer Access on Android File Host so I can give access to everyone for the Stock Firmware for the SM-G935W8 of which I grabbed from Samsung SmartSwitch on Windows. I am an experienced programmer in the Languages C# and Java. I have made a few personal apps that aren't even worth mentioning.
Goal:
My Goal is to contribute and dedicate myself to the Canadian Users because I have noticed the lack of support towards them. I am currently working on a ROM based on the stock firmware of which I am trying to release. I am going to need help on it as I am rather new to this area of Android but nonetheless does not mean I am terrible. I have done my research and have gotten some of the tools that are needed and have already successfully built a ROM just not able to boot it but I believe it is because I missed a step with the boot.img. The main tool I am using is the one that Superr has created called SuperRs_Kitchen. I am currently using v1.0.5.6 as the newest version I was having issues with.
If anyone has any questions, please feel free to ask me and I will try and answer them to the best of my ability.
I will provide an upload link once and if I get approved for requesting developer access. If I don't I will then use a different mirror to host it.
Please be patient, and I do not have an ETA on when the link will be up.
Click to expand...
Click to collapse
im from sprints s7 edge i have a question. where is the downloaded file found in smart switch. ive looked every where.
what folder does windows put it in
thanks
Robalboa said:
im from sprints s7 edge i have a question. where is the downloaded file found in smart switch. ive looked every where.
what folder does windows put it in
thanks
Click to expand...
Click to collapse
When SmartSwitch says it's downloading your firmware:
If you open up the run dialogue, type in %APPDATA% you will be brought to the Roaming folder. Click in the address bar to actually go to the APPDATA Folder, click Local, then go into the Temp folder.
Sort the results by last modified.
You will see one that has a random generated name and is a .tmp file. Keep your eye on this file and the size. Keep pressing refresh. Once that file is done another file will be created above it with the exact same name but it will be a zip file. Keep an eye on the file size as for this one as well. Keep refreshing until it the file size stops changing. In my experience it's still the exact same size as the tmp file, but just wait about 5 seconds after it stop changing, then copy it to somewhere like your desktop.
jark99 said:
Welcome Francesco! Nice to see some W8 support here! Really looking forward to see development from you
Sent from my SM-G935W8 using Tapatalk
Click to expand...
Click to collapse
Thank you. I know there isn't much support for this device, but the ROM I believe the one that is called Renovated Edge does work on the W8 version, but it will change your CSC to XAC and it was a real pain trying to get it back to RWC. Actually took me a couple days to figure out how to do it.
FrancescoM01 said:
Thank you. I know there isn't much support for this device, but the ROM I believe the one that is called Renovated Edge does work on the W8 version, but it will change your CSC to XAC and it was a real pain trying to get it back to RWC. Actually took me a couple days to figure out how to do it.
Click to expand...
Click to collapse
I am happy with echoerom for my G935W8
Sent from my Pebble Time
I hope this is the right thread.
Hello bois, I got a QiKU 360 N4 which is a pretty sick phone for the money I paid it.
It came out recently on the chinese market and its bootloader is locked.
I googled a bit and found some tutorials tho unlock the bootloader and install TWRP, because somebody compiled that already! Awesome, right?
Too bad are in chinese, yeah.
Google translate doesn't help that much, it is incomprehensible, and even if it did help: I am required to sign up to the chinese forum to read the whole tutorial (which requires me to understand how to sign up) and from what I understand the procedure makes use of a software running on windows to enter the bootloader and such software is in chinese only!
So I am looking for some kind soul who could translate the procedure and, if possible, reupload the necessary files somewhere so people like me wouldn't have to sign up to the linked chinese forum to get them.
In exchange I can offer some tips on health and fitness for I have a master in sports sciences. Or, I could offer you a beer?
P.S. sadly xda does not allow me to post links, can link in private... I guess.
Robert Hall said:
I hope this is the right thread.
Hello bois, I got a QiKU 360 N4 which is a pretty sick phone for the money I paid it.
It came out recently on the chinese market and its bootloader is locked.
I googled a bit and found some tutorials tho unlock the bootloader and install TWRP, because somebody compiled that already! Awesome, right?
Too bad are in chinese, yeah.
Google translate doesn't help that much, it is incomprehensible, and even if it did help: I am required to sign up to the chinese forum to read the whole tutorial (which requires me to understand how to sign up) and from what I understand the procedure makes use of a software running on windows to enter the bootloader and such software is in chinese only!
So I am looking for some kind soul who could translate the procedure and, if possible, reupload the necessary files somewhere so people like me wouldn't have to sign up to the linked chinese forum to get them.
In exchange I can offer some tips on health and fitness for I have a master in sports sciences. Or, I could offer you a beer?
P.S. sadly xda does not allow me to post links, can link in private... I guess.
Click to expand...
Click to collapse
Please PM me the link to the website . I don't know Chinese but I remember a root tool that was in Chinese and I will try my best to "mimic" how I got my way around that.
RAZERZDAHACKER said:
Please PM me the link to the website . I don't know Chinese but I remember a root tool that was in Chinese and I will try my best to "mimic" how I got my way around that.
Click to expand...
Click to collapse
I've sent you a message however I don't think you'll manage without knowing chinese
The tool they use is to unlock the bootloader and it's a proprietary tool.
Robert Hall said:
I've sent you a message however I don't think you'll manage without knowing chinese
The tool they use is to unlock the bootloader and it's a proprietary tool.
Click to expand...
Click to collapse
Yea I saw it, I'll see what I can do...
I'm sorry but I did not have time yesterday. I don't have access to a proper computer so I am using my raspberry pi to do all this. Since it does not have a photo editor I am working on a google slide document that will be accessible by link. I'll post it here as fast as I am done
---------- Post added at 10:36 PM ---------- Previous post was at 10:20 PM ----------
Here is how far I have come. I assume you have to download a bunch but at least the company gives you information. I've heard numerous people who buy Chinese phones and are stuck with whatever software they offer.
Yeah there is no chance to write a custom rom because the kernel source is never being given by Mediatek.
However having the ability to backup and play around with the stock firmware is great.
Robert Hall said:
Yeah there is no chance to write a custom rom because the kernel source is never being given by Mediatek.
However having the ability to backup and play around with the stock firmware is great.
Click to expand...
Click to collapse
True, I like how it has become a meme that "I'll die before mtk releases their sources".
Any more news on this? Loving my N4 so far, but would like to install TWRP and gapps, but not quite sure how. Have read somewhere that Kingroot has worked on other Qiku/360 phones but haven't got that far myself. Any chance you could send me that link to me too, your googling skills are clearly far superior to my own!
Hi.
I wiped my data from the stock recovery and now i am stuck at boot logo.I don't know how that happened.but i think i have to flash stock firmware which i cant find anywhere.
Qiku forum is unresponsive and there is no other place with info of this rare phone.
Help me out here please
help me please! I.want to unlock my QIKU N4S, but i can not download from chinese forum. thank you a lot!
Bootloader unlock - HERE
Found some ROM's also .... Althought, You'll Need TAMPERMONKEY and Baidu Download Script for Tampermoney
ROM'S - HERE and other Tools + rom's HERE
There is a whole Qiku N4 forum but it's in chinese .... didnt have time to bother with it,
since it requires to be registered ...
And, as bonus ...
I found Russian modified ROM's ....
HERE for HW version A01
and
HERE for HW version M02
TWRP Recovery - HERE
Check HW version of your phone, if you want to flash roms and BEFORE screwing it up.
Hope that's enough for now ....
p.s. Be carefull what are you doing and flashing into phone. Links I posted are from third party sources,
people reported they are working, but all you do - you do on your own responsibility.
b.r.
Alex
mobilexpert said:
Bootloader unlock - HERE
Found some ROM's also .... Althought, You'll Need TAMPERMONKEY and Baidu Download Script for Tampermoney
ROM'S - HERE and other Tools + rom's HERE
There is a whole Qiku N4 forum but it's in chinese .... didnt have time to bother with it,
since it requires to be registered ...
And, as bonus ...
I found Russian modified ROM's ....
HERE for HW version A01
and
HERE for HW version M02
TWRP Recovery - HERE
Check HW version of your phone, if you want to flash roms and BEFORE screwing it up.
Hope that's enough for now ....
p.s. Be carefull what are you doing and flashing into phone. Links I posted are from third party sources,
people reported they are working, but all you do - you do on your own responsibility.
b.r.
Alex
Click to expand...
Click to collapse
if you want root your phone,you must use ROM V019
mobilexpert said:
ROM'S - HERE and other Tools + rom's HERE
Click to expand...
Click to collapse
Hello Alex,
Those links are sadly down.
Do you know any other link to a stock N4 image and scatter file that I could use to factory-reset a pattern-locked N4 ? I got my hands on a discarded one, but the factory reset option in recovery mode requires that cloud account be first deleted, which I can't to because of the pattern lock.
Thanks !
EDIT :
Sorry, I spoke too fast. I gave another try and the links are up, though in chinese. I'll try to get what I can. Thank you !
I am Chinese
Robert Hall said:
I hope this is the right thread.
Hello bois, I got a QiKU 360 N4 which is a pretty sick phone for the money I paid it.
It came out recently on the chinese market and its bootloader is locked.
I googled a bit and found some tutorials tho unlock the bootloader and install TWRP, because somebody compiled that already! Awesome, right?
Too bad are in chinese, yeah.
Google translate doesn't help that much, it is incomprehensible, and even if it did help: I am required to sign up to the chinese forum to read the whole tutorial (which requires me to understand how to sign up) and from what I understand the procedure makes use of a software running on windows to enter the bootloader and such software is in chinese only!
So I am looking for some kind soul who could translate the procedure and, if possible, reupload the necessary files somewhere so people like me wouldn't have to sign up to the linked chinese forum to get them.
In exchange I can offer some tips on health and fitness for I have a master in sports sciences. Or, I could offer you a beer?
P.S. sadly xda does not allow me to post links, can link in private... I guess.
Click to expand...
Click to collapse
Hello Is the 360n4 on your hand still there? I can help you with the problem!
1915007283 said:
Hello Is the 360n4 on your hand still there? I can help you with the problem!
Click to expand...
Click to collapse
Hi !
I'm not the original poster, but am in the same situation, and have a N360 at hand. Are you willing to help me ?
Hello
breversa said:
Hi !
I'm not the original poster, but am in the same situation, and have a N360 at hand. Are you willing to help me ?
Click to expand...
Click to collapse
Is the cell phone on your hand 360n4? This cell phone has two versions of 360n4 and 360n4s
Yes, it a 360N4, not a 360N4S.
What I'm trying to do is follow that howto : http://www.cnroms.com/360-n4-061-unlock-bootloader-install-twrp-recovery.html to downgrade it, then factory reset it and install TWRP.
However, I can't read chinese (can't even tell whether it's cantonese or mandarin). Google Translate helps, but most link seem to be broken, and when they're not, the download speed is abysmally slow (several days…).
Is there any way you could help me ? Maybe get the needed files and reupload them somewhere faster ?
I see
breversa said:
Yes, it a 360N4, not a 360N4S.
What I'm trying to do is follow that howto : http://www.cnroms.com/360-n4-061-unlock-bootloader-install-twrp-recovery.html to downgrade it, then factory reset it and install TWRP.
However, I can't read chinese (can't even tell whether it's cantonese or mandarin). Google Translate helps, but most link seem to be broken, and when they're not, the download speed is abysmally slow (several days…).
Is there any way you could help me ? Maybe get the needed files and reupload them somewhere faster ?
Click to expand...
Click to collapse
We have a lot of links, and if you have QQ, I think I can give you faster links
Because I don't know what tools you use to chat
1915007283 said:
We have a lot of links, and if you have QQ, I think I can give you faster links
Because I don't know what tools you use to chat
Click to expand...
Click to collapse
QQ ? What's that ?
In case your links are private, why not using private messages on this here forum ?
I'm sorry
breversa said:
QQ ? What's that ?
In case your links are private, why not using private messages on this here forum ?
Click to expand...
Click to collapse
I just came to this forum, I still don't know how to send messages
With HD10 (2017) unlock/TWRP available - link (thanks to @k4y0z!!!), the next natural question is a custom ROM. The subject may turn out to be slightly trickier than what appears at first sight.
Let's have a discussion thread to brainstorm on this and not wonder off-topic in other places.
I had seen @DragonFire1024 & @Rortiz2 tried to work on that, so feel free to chime in as necessary.
What we have:
HD10 (2017) chipset - MT8173 (2+2 cores), there is an beefier brother to it, MT8176 (2+4 cores). For most practical purposes both chipsets seem almost identical software-wise.
MT8173 was introduced in March 2015 (time of Lollipop domination - Android 5). MT8176 was introduced in October 2016 (getting toward Nougat - Android 7).
The efforts up to date on a custom ROM for this chipset appear to be by @Goayandi, who is still active on XDA, so his work could be used a starting point. I believe @Goayandi was working on Android 7 (Nougat). Here are some of the original links:
XDA : Mediatek MT8173 & MT8176 development
Reddit: Mediatek MT8173 & MT8176 development
Stuff from Amazon for MT8173 (both HD10 2017 and FireTV2) is Lollipop-vintage (Android 5), other devices with these chipsets seem to have reached Nougat (Android 7). It does not appear that there is any known MT8173/MT8176 device with Android 8, or 9 (or is there?). It seems that @diplomatic has an Asus like this with Nougat.
At the moment, it feels a a Nougat custom ROM might be the ceiling for the device, given the difficulties of finding proprietary pieces for MTK chipsets to get Android 8 or 9 going. Now, even Android 7 is still a bit of a challenge, given limited prior success.
More thoughts/ideas? Feel free to fill this thread with random thoughts as much as you want - that's what it's for!!!
I'm really looking forward to an AOSP experience on this tablet, to be honest. Can't wait to see what they come up with!
GuyInDogSuit said:
I'm really looking forward to an AOSP experience on this tablet, to be honest. Can't wait to see what they come up with!
Click to expand...
Click to collapse
As long as I can set up everything properly I'm ready to go. I've managed to get past script issues I think. I can get it to flash and it boots to the orange fire logo and sits for eternity. This was the same result pre and post TWRP. So at this point it's probably the installation and improper setup of the tree and files. If someone can point me to a guide or give me instructions on how to add support to my AOSP working directory, that would be great. This bit of the leg work is hard as there really aren't any guides that are detailed enough or that work anymore.
Secondly, I think if we are going to use a kernel, we either use the 7.0 source, or just use the kit I have to build our own. Amazon cherry picked the crap out of the kernel practically to the bare bones, so I think expanding from it is just a waste of time, especially since we have the kit that does a lot of the work for us, including providing signatures and the tools to sign etc.
Sent from my Galaxy Tab3 Lite 7.0 using XDA Labs
I wouldn't mind even if the best ROM available is a 6.0 Marshmallow one. Anything that gives AOSP on a stable base for the Fire HD10 is going to be awesome.
DragonFire1024 said:
As long as I can set up everything properly I'm ready to go. I've managed to get past script issues I think. I can get it to flash and it boots to the orange fire logo and sits for eternity. This was the same result pre and post TWRP. So at this point it's probably the installation and improper setup of the tree and files. If someone can point me to a guide or give me instructions on how to add support to my AOSP working directory, that would be great. This bit of the leg work is hard as there really aren't any guides that are detailed enough or that work anymore.
Secondly, I think if we are going to use a kernel, we either use the 7.0 source, or just use the kit I have to build our own. Amazon cherry picked the crap out of the kernel practically to the bare bones, so I think expanding from it is just a waste of time, especially since we have the kit that does a lot of the work for us, including providing signatures and the tools to sign etc.
Sent from my Galaxy Tab3 Lite 7.0 using XDA Labs
Click to expand...
Click to collapse
So did you end up successfully unbricking your device?
I did share working amazon kernel sources in the HD-10 Unlock thread.
They worked well in my tree to compile TWRP.
k4y0z said:
So did you end up successfully unbricking your device?
I did share working amazon kernel sources in the HD-10 Unlock thread.
They worked well in my tree to compile TWRP.
Click to expand...
Click to collapse
Sorry for being out of the loop - were those kernel sources for Lollipop? Or does it even matter at all - meaning they would be good to go with newer Android versions as well.
Could you link to those posts in here?
bibikalka said:
Sorry for being out of the loop - were those kernel sources for Lollipop? Or does it even matter at all - meaning they would be good to go with newer Android versions as well.
Could you link to those posts in here?
Click to expand...
Click to collapse
They will likely need some patches to work with newer versions, but it's a good start I'd say.
It's the most recent version amazon has published.
k4y0z said:
So did you end up successfully unbricking your device?
I did share working amazon kernel sources in the HD-10 Unlock thread.
They worked well in my tree to compile TWRP.
Click to expand...
Click to collapse
I am working on it as we speak. I downloaded the zip from the second post in this thread, 1.1. extracted and ran sudo ./bootrom-step.sh. said it can't find build/payload directory it doesn't exist. So I assume I use that folder from the other unbricking thread copy it to yours? Assuming its a yes to that question, I keep getting the serial port errors. I also had to delete a setting in udev (this was my own addition to it) and rebooted PC. Now I am having a cigarette. When I do it again, if I still get serial port errors, time to try each of the 8 or 10 other ports on the PC.
Sent from my MotoG3 using XDA Labs
---------- Post added at 06:23 PM ---------- Previous post was at 06:21 PM ----------
bibikalka said:
Sorry for being out of the loop - were those kernel sources for Lollipop? Or does it even matter at all - meaning they would be good to go with newer Android versions as well.
Could you link to those posts in here?
Click to expand...
Click to collapse
The one I have and provided is a source to 7.0. looks nicely stocked.
Sent from my MotoG3 using XDA Labs
bibikalka said:
With HD10 (2017) unlock/TWRP available - link (thanks to @k4y0z!!!), the next natural question is a custom ROM. The subject may turn out to be slightly trickier than what appears at first sight.
Let's have a discussion thread to brainstorm on this and not wonder off-topic in other places.
I had seen @DragonFire1024 & @Rortiz2 tried to work on that, so feel free to chime in as necessary.
What we have:
HD10 (2017) chipset - MT8173 (2+2 cores), there is an beefier brother to it, MT8176 (2+4 cores). For most practical purposes both chipsets seem almost identical software-wise.
MT8173 was introduced in March 2015 (time of Lollipop domination - Android 5). MT8176 was introduced in October 2016 (getting toward Nougat - Android 7).
The efforts up to date on a custom ROM for this chipset appear to be by @Goayandi, who is still active on XDA, so his work could be used a starting point. I believe @Goayandi was working on Android 7 (Nougat). Here are some of the original links:
XDA : Mediatek MT8173 & MT8176 development
Reddit: Mediatek MT8173 & MT8176 development
Stuff from Amazon for MT8173 (both HD10 2017 and FireTV2) is Lollipop-vintage (Android 5), other devices with these chipsets seem to have reached Nougat (Android 7). It does not appear that there is any known MT8173/MT8176 device with Android 8, or 9 (or is there?). It seems that @diplomatic has an Asus like this with Nougat.
At the moment, it feels a a Nougat custom ROM might be the ceiling for the device, given the difficulties of finding proprietary pieces for MTK chipsets to get Android 8 or 9 going. Now, even Android 7 is still a bit of a challenge, given limited prior success.
More thoughts/ideas? Feel free to fill this thread with random thoughts as much as you want - that's what it's for!!!
Click to expand...
Click to collapse
Hi bibikalka,
Very good idea this thread.
What you can do, is to port a port a ROM of another MT8173 tablet to the FIRE HD10 2017.
This works and I have tested it on my BQ Aquaris M8 (MT8163) it has a similar MTK so I guess it will work. I have ported for example a ROM of an asus zenpad that uses MT8163 and at least the rom boots.
BTW: Oreo on MT8176: https://www.xda-developers.com/alldocube-x-10-5-inch-android-8-1-oreo/
DragonFire1024 said:
I am working on it as we speak. I downloaded the zip from the second post in this thread, 1.1. extracted and ran sudo ./bootrom-step.sh. said it can't find build/payload directory it doesn't exist. So I assume I use that folder from the other unbricking thread copy it to yours? Assuming its a yes to that question, I keep getting the serial port errors. I also had to delete a setting in udev (this was my own addition to it) and rebooted PC. Now I am having a cigarette. When I do it again, if I still get serial port errors, time to try each of the 8 or 10 other ports on the PC.
Click to expand...
Click to collapse
Apparently I forgot to add the right files.
give me a moment.
---------- Post added at 06:47 PM ---------- Previous post was at 06:36 PM ----------
DragonFire1024 said:
I am working on it as we speak. I downloaded the zip from the second post in this thread, 1.1. extracted and ran sudo ./bootrom-step.sh. said it can't find build/payload directory it doesn't exist. So I assume I use that folder from the other unbricking thread copy it to yours? Assuming its a yes to that question, I keep getting the serial port errors. I also had to delete a setting in udev (this was my own addition to it) and rebooted PC. Now I am having a cigarette. When I do it again, if I still get serial port errors, time to try each of the 8 or 10 other ports on the PC.
Click to expand...
Click to collapse
I have fixed the upload, please use amonet-suez-v1.1.1.zip
DragonFire1024 said:
The one I have and provided is a source to 7.0. looks nicely stocked.
Click to expand...
Click to collapse
But these aren't amazon sources are they?
They probably are missing some drivers then.
But if they are for mt8173 they could be used as a source to patch the amazon-sources.
k4y0z said:
Apparently I forgot to add the right files.
give me a moment.
---------- Post added at 06:47 PM ---------- Previous post was at 06:36 PM ----------
I have fixed the upload, please use amonet-suez-v1.1.1.zip
But these aren't amazon sources are they?
They probably are missing some drivers then.
But if they are for mt8173 they could be used as a source to patch the amazon-sources.
Click to expand...
Click to collapse
I'll provide a link in a few. Trying your fix now.
Sent from my Galaxy Tab3 Lite 7.0 using XDA Labs
Rortiz2 said:
Hi bibikalka,
Very good idea this thread.
What you can do, is to port a port a ROM of another MT8173 tablet to the FIRE HD10 2017.
This works and I have tested it on my BQ Aquaris M8 (MT8163) it has a similar MTK so I guess it will work. I have ported for example a ROM of an asus zenpad that uses MT8163 and at least the rom boots.
BTW: Oreo on MT8176: https://www.xda-developers.com/alldocube-x-10-5-inch-android-8-1-oreo/
Click to expand...
Click to collapse
Excellent find! Here is a review link:
https://forum.xda-developers.com/ge...ldocube-x-review-media-playback-king-t3902539
Alldocube X kind of has 2x of everything compared to HD10 2017, but at 2x price I wonder how fast Oreo would be on HD10 and if 2Gb of RAM would cut it. But this is definitely the device to copy if one wants latest and greatest!
And here is a thread with misc download links for ROMs:
https://forum.xda-developers.com/ge...n/10-5-inch-super-amoled-2560-x-1600-t3821327
bibikalka said:
Excellent find! Here is a review link:
https://forum.xda-developers.com/ge...ldocube-x-review-media-playback-king-t3902539
Alldocube X kind of has 2x of everything compared to HD10 2017, but at 2x price I wonder how fast Oreo would be on HD10 and if 2Gb of RAM would cut it. But this is definitely the device to copy if one wants latest and greatest!
And here is a thread with misc download links for ROMs:
https://forum.xda-developers.com/ge...n/10-5-inch-super-amoled-2560-x-1600-t3821327
Click to expand...
Click to collapse
I will try to port lineage 15.1 but the safest thing is that it will not work.
I have also ported an AOSP Rom for anyone who wants to try it. Tomorrow I will give more info.
Rortiz2 said:
I will try to port lineage 15.1 but the safest thing is that it will not work.
I have also ported an AOSP Rom for anyone who wants to try it. Tomorrow I will give more info.
Click to expand...
Click to collapse
This is great news! I am eagerly awaiting more info about this AOSP ROM
Rortiz2 said:
I will try to port lineage 15.1 but the safest thing is that it will not work.
I have also ported an AOSP Rom for anyone who wants to try it. Tomorrow I will give more info.
Click to expand...
Click to collapse
ffstudios said:
This is great news! I am eagerly awaiting more info about this AOSP ROM
Click to expand...
Click to collapse
Alright, we have both an eager developer, and a tester!!! Just remember, avoid bricking !
Very recently (March 2019) @wangyiling seems to have put together a LineageOS 15.1 ROM for MT8173/8176 - link, so hopefully we can re-purpose that for HD10. It's great to have an active developer elsewhere looking at the same thing!
It feels that if there is at least something that boots the kernel, it'd be a huge step forward.
bibikalka said:
Alright, we have both an eager developer, and a tester!!! Just remember, avoid bricking !
Very recently (March 2019) @wangyiling seems to have put together a LineageOS 15.1 ROM for MT8173/8176 - link, so hopefully we can re-purpose that for HD10. It's great to have an active developer elsewhere looking at the same thing!
It feels that if there is at least something that boots the kernel, it'd be a huge step forward.
Click to expand...
Click to collapse
If my testing on ROMs caused my brick, we have to be careful. I've been testing and flashing test ROMs for months now and never bricked like this. I think I may know what happened and if I'm right, I'm not sure what effect if any this will have on flashing a rom. According to the fstab.mt8173 file in the root directory, the partitions we flash for a rom, aren't part of the EMMC: data, system, cache are all ext4. All other partitions are however EMMC. So if I recall correctly, I did list the system as EMMC in the build script, but did intend to remove it. I made a last minute adjustment to the script and didn't change that part though.
https://forum.xda-developers.com/showpost.php?p=78542898&postcount=618
Sent from my MotoG3 using XDA Labs
Rortiz2 said:
I will try to port lineage 15.1 but the safest thing is that it will not work.
I have also ported an AOSP Rom for anyone who wants to try it. Tomorrow I will give more info.
Click to expand...
Click to collapse
I too am willing to test. Just let me know and I'll be sure to wear my best testing pants. [emoji41]
Sent from my SM-G9650/DS running stang5litre Pie ROM
AOSP ROM TEST 1 (suez)
Ok guys so here's the first test for the AOSP ROM.
First of all, I am not responsible for bricked devices. It is you who decides to try the ROM without knowing if it will work because it is a TEST.
DOWNLOAD: Removed
INSTALL INSTRUCTIONS:
- Boot TWRP
- Make NANDROID BACKUP
- Make wipes
- Format data
- Install ROM
- Reboot
Please. If the installation fails, send the errors and if the ROM starts, comment on the bugs.
Regards!
Rortiz2 said:
Ok guys so here's the first test for the AOSP ROM.
First of all, I am not responsible for bricked devices. It is you who decides to try the ROM without knowing if it will work because it is a TEST.
DOWNLOAD: https://mega.nz/#!C5dEQIKR!14BcGTiaT-xsrPUc-AxmWrTLj92Y5A2VgeNX2VA1uUE
INSTALL INSTRUCTIONS:
- Boot TWRP
- Make NANDROID BACKUP
- Make wipes
- Format data
- Install ROM
- Reboot
Please. If the installation fails, send the errors and if the ROM starts, comment on the bugs.
Regards!
Click to expand...
Click to collapse
Sounds good to me. Won't have a chance till later this afternoon/evening to give it a whirl, but when I do I'll definitely share my results and any information that may be useful. Thank you!
Sent from my SM-G9650/DS running stang5litre Pie ROM
Rortiz2 said:
Ok guys so here's the first test for the AOSP ROM.
First of all, I am not responsible for bricked devices. It is you who decides to try the ROM without knowing if it will work because it is a TEST.
DOWNLOAD: https://mega.nz/#!C5dEQIKR!14BcGTiaT-xsrPUc-AxmWrTLj92Y5A2VgeNX2VA1uUE
...
Please. If the installation fails, send the errors and if the ROM starts, comment on the bugs.
Click to expand...
Click to collapse
Which AOSP version is this? Could you try that Oreo Lineage stuff from @wangyiling at some point as well?
One of these days we'll have a ROM developer and a tester within the same person Too bad we've lost @DragonFire1024 since his tablet got bricked