Related
Q&A for [RECOVERY] CWM Recovery 6.0.5.1.2
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer. Thanks for understanding and for helping to keep XDA neat and tidy! :smile:
Full backup of one AFTV and restore on another
It's great to see that modstore was able to clone an AFTV.
I dont understand what modstore is saying here:
modstore said:
I'm not sure if anyone has tried backing up one Fire TV and restoring to another, but I just tried it, and all seems good.
Doing the restore though, changed the registered account to that of the backup. So I'm not sure if it would have been registered properly, probably not. But I changed it to the account I wanted it registered too, and all seems good now.
Click to expand...
Click to collapse
Changed what registered account? Does this mean that the new AFTV was setup to have the same amazon account as the backed up AFTV before the restore took place on the new AFTV?
I really want to be able to clone. It sounds like its possible, I just want to avoid the trial and error if possible. I'm sure others are interested in the procedure too.
eville84 said:
It's great to see that modstore was able to clone an AFTV.
I dont understand what modstore is saying here:
Changed what registered account? Does this mean that the new AFTV was setup to have the same amazon account as the backed up AFTV before the restore took place on the new AFTV?
I really want to be able to clone. It sounds like its possible, I just want to avoid the trial and error if possible. I'm sure others are interested in the procedure too.
Click to expand...
Click to collapse
Yes, from what he said that the registration info went over with the backup. If you want to clone machines, then this will work.
he didn't want to clone machines, so he had to put in the correct register info on the machine he put the backup on.
nyder said:
Yes, from what he said that the registration info went over with the backup. If you want to clone machines, then this will work.
he didn't want to clone machines, so he had to put in the correct register info on the machine he put the backup on.
Click to expand...
Click to collapse
There might be a way to make it trigger the initial Registration page after doing a restore of a clone. I'll add it to my list and maybe come up with a special update.zip that will make it happen.
So if you have a FTV set up with xbmc etc you can make a direct copy of it into a stock FTV, thus cloning it as said above?
I've looked around and can't seem to find what to do. I've used adb before but have never ran into this issue yet seems so silly.
When I type "su" in adb shell i get this error "system/bin/sh: su: not found"
I've googled and all I can find is reinstalling the superuser on the phone... I'm trying to unlock the boot loader
hellot1M said:
I've looked around and can't seem to find what to do. I've used adb before but have never ran into this issue yet seems so silly.
When I type "su" in adb shell i get this error "system/bin/sh: su: not found"
I've googled and all I can find is reinstalling the superuser on the phone... I'm trying to unlock the boot loader
Click to expand...
Click to collapse
You need root first. What fw are you on? If it's a rootable version, do that first and then follow the guides for updating here.
Yea figured it out. I'm on 1.3.0 this sucks. I'm trying to sell my amazon box to get a nexus player. Amazon has no idea how to run a home media center.
Thanks!
Bricked mine. Cant boot into recovery anymore using keyboard. Any tips ?
Sent from my SM-N910V using Tapatalk
patt2k said:
Bricked mine. Cant boot into recovery anymore using keyboard. Any tips ?
Sent from my SM-N910V using Tapatalk
Click to expand...
Click to collapse
What guide, and which step of said guide, were you running through that you bricked it?
Sent from my TARDIS
0p3nsrc said:
What guide, and which step of said guide, were you running through that you bricked it?
Sent from my TARDIS
Click to expand...
Click to collapse
Guide from AFTVNEWS.
I got recovery to work everything was fine I could reboot from recovery back to recovery again (CWM) but after I did factory reset in CWM it gets stuck on amazon logo.
The reason I did factory reset was because of Error.7 in CWM I had that few times when flashing different roms on different phones/tablets
sometimes getting older cwm or simply factory reset would help.
So now it gets stuck on Amazon logo the keyboard trick to get back into CWM does not work anymore.
Anything else I can try before I call up amazon hoping they replace it ?
I can honestly say if you followed rbox's custom recovery install guide, used his recovery image, and made sure the md5 matched, you shouldn't have had any problems.
Out of curiosity, do you have an external hard drive plugged in?
Sent from my TARDIS
0p3nsrc said:
I can honestly say if you followed rbox's custom recovery install guide, used his recovery image, and made sure the md5 matched, you shouldn't have had any problems.
Out of curiosity, do you have an external hard drive plugged in?
Sent from my TARDIS
Click to expand...
Click to collapse
Yea I did follow instructions correctly. And no I do not only had the usb keyboard plugged in so I could get into recovery.
Almost every device I rooted w/ custom recovery gave me Error 7 tablets phone etc.. I seem to have bad luck with that error lol.
Since I was on the very last step.. flashing rom -> getting error 7 grr
patt2k said:
Yea I did follow instructions correctly. And no I do not only had the usb keyboard plugged in so I could get into recovery.
Almost every device I rooted w/ custom recovery gave me Error 7 tablets phone etc.. I seem to have bad luck with that error lol.
Since I was on the very last step.. flashing rom -> getting error 7 grr
Click to expand...
Click to collapse
I think cwm still has some issues. It works fine for installing rbox's pre-rooted ROMs, but I can't backup my ftv. It always errors out.
Was this the first time you've gone through cwm install? Did you try installing one of his custom ROMs and then got that error? Did you verify that your recovery download went okay? Check the md5 against what's listed on the site.
I know it's a lot of questions, but I'm just trying to delve deeper to see what may have caused your error.
(I'm tech support, so I've always got more questions to ask )
Sent from my TARDIS
0p3nsrc said:
I think cwm still has some issues. It works fine for installing rbox's pre-rooted ROMs, but I can't backup my ftv. It always errors out.
Was this the first time you've gone through cwm install? Did you try installing one of his custom ROMs and then got that error? Did you verify that your recovery download went okay? Check the md5 against what's listed on the site.
I know it's a lot of questions, but I'm just trying to delve deeper to see what may have caused your error.
(I'm tech support, so I've always got more questions to ask )
Sent from my TARDIS
Click to expand...
Click to collapse
Yes sir everything was checked few times. Bunch of times made sure even file size is correct etc...
I did install recovery however at first when I had wrong firmware I installed via ADB SHELL then I Downgraded to unlock bootloader after I downgraded I installed recovery via adbfire I think newest version .17 however it was still the newest firmware of recovery anyway.... and yepp it was stock pre-rooted latest firmware that ends with "0" that did not require the fire tv boot menu.. but now I am thinking if I had the boot menu I could have got into recovery! so AFTVNEWS mis-lead me on this part... the bootmenu would be great on all firmwares actually.
patt2k said:
Yes sir everything was checked few times. Bunch of times made sure even file size is correct etc...
I did install recovery however at first when I had wrong firmware I installed via ADB SHELL then I Downgraded to unlock bootloader after I downgraded I installed recovery via adbfire I think newest version .17 however it was still the newest firmware of recovery anyway.... and yepp it was stock pre-rooted latest firmware that ends with "0" that did not require the fire tv boot menu.. but now I am thinking if I had the boot menu I could have got into recovery! so AFTVNEWS mis-lead me on this part... the bootmenu would be great on all firmwares actually.
Click to expand...
Click to collapse
I'm not sure about adbfire anything. I do all mine through Linux/android terminal/windows command line. The boot menu works on firmware 51.1.4.0. When it's sitting at the logo, have you tried connecting via adb, just to see if it initialized enough to poke around? (not sure if it works that way with ftv, but I'd try, regardless)
Sent from my TARDIS
0p3nsrc said:
I'm not sure about adbfire anything. I do all mine through Linux/android terminal/windows command line. The boot menu works on firmware 51.1.4.0. When it's sitting at the logo, have you tried connecting via adb, just to see if it initialized enough to poke around? (not sure if it works that way with ftv, but I'd try, regardless)
Sent from my TARDIS
Click to expand...
Click to collapse
As far as I saw I could only connect via adb at least when in recovery mode.. otherwise it was a no go... anyways thanks for helping me out. I think there is no rescue in this situation by somehow fixing it. I mean just wanted to have few features like swap storage with a flash drive and have newest FW. But that's ok.
Thanks for your time!
patt2k said:
As far as I saw I could only connect via adb at least when in recovery mode.. otherwise it was a no go... anyways thanks for helping me out. I think there is no rescue in this situation by somehow fixing it. I mean just wanted to have few features like swap storage with a flash drive and have newest FW. But that's ok.
Thanks for your time!
Click to expand...
Click to collapse
Sorry I couldn't be of more help :/ the issue you'll probably see is that unlocking the bootloader voids any warranty with amazon.. So I'm not sure what amazon may or may not do for you.
Sent from my TARDIS
About the possible Lollipop ROM for FireTV,is there a way to get the latest qualcomm Adreno 320 drivers like [email protected] from another device for flashing in proper FTV directories since it is meant for Lollipop?
I am hoping for the fix for Dolphin to be runnable and Reicast to no longer cause reboots,as well as better performance for things like Mupen64Plus AE.
Hey guys.
I'm new to this forum... and am posting this as I no longer know what to do, and need some guidance.
First I'll say that I've looked ALL OVER this forum and others, but couldn't solve my problem.
...So I subscribed in the hopes that someone will be able to more properly guide me.
------------------------------------------
So, first thing's fisrt - the story from the beginning:::
My device is an OPPO Find7 (QHD Version)
I've been using Cyanogenmod 11 for many months and without any problems.
Few days ago I installed the first nightly update of CM12 - and phone went into boot loop.
I had to restore to the ColorOS backup that was saved on my phone... Reinstalled CM11 and all is good.
Later I again updated to CM12 - and again was forced to revert back to Backup and then to CM11 due to bugs (phone wouldn't wake up after being locked, etc)
Anyway, There were three nightly build of CM12 to that point,and the last one was working in a relatively stable manner,
exept two bugs.
1. Contact names didn't appear when mamkiing to receiving a call - even though they were saved on the phone.
But this bug can be overlooked.
2. This one was more cirtical - - For some reason the phone said that I have no more free
space (even though I had 20+GB), thus preventing me from installing or updating
anything.
I figured that, perhaps, becuase of all the re-installs that I've done - my system memory got clogged.
So I decided, with more haste than thought, to perform a full wipe...SDcard and all, which consequently also removed
my ColorOS backup and everything, basically.
-----------------------------------------
The currrent outcome of what I did:::
Phone has no OS installed on it, and PC doesn't llow my to put files in there.
I can currently boot in three different states:
1. Normal boot with power button - - - OPPO logo appears - followed by a black
screen PC recognizes that I've connected a device, tries to install MTP Device and
evetually fails.
2. Power Button + Vol Up - - - Fastboot screen.
3. Power button+Vol-Down - - - Boots into the Gummified Team Win Recovery 2.7.1.0
In here, several things need to be mentioned.
- In the "Mount" section, I can choose which Partitions to mount to unmount, but
don't actually have the "Mount" button inside... So I can't mount.
- ADB Sideload doesn't work. When activating - it says "Starting ADB Sideload
Feature and just goes on forever, until I cancel it - and it says that it failed.
--------------------------------------------------
What I tried doing:::
Tried to use the Recovery Installer for OPPO, which is the exe that is available on the internet, that comes with drivers and all - and open command line with various options.
Tried installing the stock Color OS recovery, but when booting into it I still get the teamwin recovery
I am unsure how to proceed.
Is there a way to fix my phone?
I have my CM11 working version and gapps ready - just need to place it in the phone somehow.
Any help?
Outblaze713 said:
Hey guys.
I'm new to this forum... and am posting this as I no longer know what to do, and need some guidance.
First I'll say that I've looked ALL OVER this forum and others, but couldn't solve my problem.
...So I subscribed in the hopes that someone will be able to more properly guide me.
------------------------------------------
So, first thing's fisrt - the story from the beginning:::
My device is an OPPO Find7 (QHD Version)
I've been using Cyanogenmod 11 for many months and without any problems.
Few days ago I installed the first nightly update of CM12 - and phone went into boot loop.
I had to restore to the ColorOS backup that was saved on my phone... Reinstalled CM11 and all is good.
Later I again updated to CM12 - and again was forced to revert back to Backup and then to CM11 due to bugs (phone wouldn't wake up after being locked, etc)
Anyway, There were three nightly build of CM12 to that point,and the last one was working in a relatively stable manner,
exept two bugs.
1. Contact names didn't appear when mamkiing to receiving a call - even though they were saved on the phone.
But this bug can be overlooked.
2. This one was more cirtical - - For some reason the phone said that I have no more free
space (even though I had 20+GB), thus preventing me from installing or updating
anything.
I figured that, perhaps, becuase of all the re-installs that I've done - my system memory got clogged.
So I decided, with more haste than thought, to perform a full wipe...SDcard and all, which consequently also removed
my ColorOS backup and everything, basically.
-----------------------------------------
The currrent outcome of what I did:::
Phone has no OS installed on it, and PC doesn't llow my to put files in there.
I can currently boot in three different states:
1. Normal boot with power button - - - OPPO logo appears - followed by a black
screen PC recognizes that I've connected a device, tries to install MTP Device and
evetually fails.
2. Power Button + Vol Up - - - Fastboot screen.
3. Power button+Vol-Down - - - Boots into the Gummified Team Win Recovery 2.7.1.0
In here, several things need to be mentioned.
- In the "Mount" section, I can choose which Partitions to mount to unmount, but
don't actually have the "Mount" button inside... So I can't mount.
- ADB Sideload doesn't work. When activating - it says "Starting ADB Sideload
Feature and just goes on forever, until I cancel it - and it says that it failed.
--------------------------------------------------
What I tried doing:::
Tried to use the Recovery Installer for OPPO, which is the exe that is available on the internet, that comes with drivers and all - and open command line with various options.
Tried installing the stock Color OS recovery, but when booting into it I still get the teamwin recovery
I am unsure how to proceed.
Is there a way to fix my phone?
I have my CM11 working version and gapps ready - just need to place it in the phone somehow.
Any help?
Click to expand...
Click to collapse
Do you have an OTG Usb drive. If so, you can use it with Nameless TWRP. Copy the Installation files into the USB drive and plug the usb drive into the phone. Now boot into Nameless recovery. It will show USBOTG. You can install the CM11 from USBOTG.
Flash Nameless recovery using Fastboot.
Download Nameless Recovery from HERE.
soft brick
This link explains how to restore our find 7 to factory settings:
oppoforums.com/threads/guida-riportare-il-find-7-7a-nello-stato-dacquisto-con-il-firmware-sahara.24561
if phone doesn't start try it i've use it several times and it works fine
I might just be reposting what dracula6mt was talking about, but there's an English post with full brick recovery here: http://www.oppoforums.com/threads/guide-how-to-recover-your-bricked-find-7-7a.23067/. I've used it before and it works perfectly. Just make sure you follow it exactly as written!
Bug
same bug report
for retrive your data just open the gummy twrp recovery, go on mount --> sd card and internal memory... in this way when you connect the phone to pc you will be able to see what's inside and try to rescue your data. in the same way you can send files to it.
I suggest you to get back your files, reboot the phone in fastboot mode (hold power and volume +) and just flash a recovery, it depends about what you want to install:
twrp for custom roms https://dl.twrp.me/find7/
colorOS stock recovery http://community.oppo.com/en/forum.php?mod=viewthread&tid=17397&extra=
you have to install fastboot on your pc and do from a command prompt:
fastboot devices
this will check if your phone is connected
fastboot flash recovery nameoftherecoveryfile.img
that will flash the recovery, only check the name of the .img file you want to install
be carreful, twrp has only a version for both find7s (QHD) and find7a while colorOS recovery 1.0 is different, unified for both models in 1.2 if i remember right...
after that you just have to put on your external storage the rom you want to use, wipe all except the external sd card, and flash...
Outblaze713 said:
Hey guys.
I'm new to this forum... and am posting this as I no longer know what to do, and need some guidance.
First I'll say that I've looked ALL OVER this forum and others, but couldn't solve my problem.
...So I subscribed in the hopes that someone will be able to more properly guide me.
------------------------------------------
So, first thing's fisrt - the story from the beginning:::
My device is an OPPO Find7 (QHD Version)
I've been using Cyanogenmod 11 for many months and without any problems.
Few days ago I installed the first nightly update of CM12 - and phone went into boot loop.
I had to restore to the ColorOS backup that was saved on my phone... Reinstalled CM11 and all is good.
Later I again updated to CM12 - and again was forced to revert back to Backup and then to CM11 due to bugs (phone wouldn't wake up after being locked, etc)
Anyway, There were three nightly build of CM12 to that point,and the last one was working in a relatively stable manner,
exept two bugs.
1. Contact names didn't appear when mamkiing to receiving a call - even though they were saved on the phone.
But this bug can be overlooked.
2. This one was more cirtical - - For some reason the phone said that I have no more free
space (even though I had 20+GB), thus preventing me from installing or updating
anything.
I figured that, perhaps, becuase of all the re-installs that I've done - my system memory got clogged.
So I decided, with more haste than thought, to perform a full wipe...SDcard and all, which consequently also removed
my ColorOS backup and everything, basically.
-----------------------------------------
The currrent outcome of what I did:::
Phone has no OS installed on it, and PC doesn't llow my to put files in there.
I can currently boot in three different states:
1. Normal boot with power button - - - OPPO logo appears - followed by a black
screen PC recognizes that I've connected a device, tries to install MTP Device and
evetually fails.
2. Power Button + Vol Up - - - Fastboot screen.
3. Power button+Vol-Down - - - Boots into the Gummified Team Win Recovery 2.7.1.0
In here, several things need to be mentioned.
- In the "Mount" section, I can choose which Partitions to mount to unmount, but
don't actually have the "Mount" button inside... So I can't mount.
- ADB Sideload doesn't work. When activating - it says "Starting ADB Sideload
Feature and just goes on forever, until I cancel it - and it says that it failed.
--------------------------------------------------
What I tried doing:::
Tried to use the Recovery Installer for OPPO, which is the exe that is available on the internet, that comes with drivers and all - and open command line with various options.
Tried installing the stock Color OS recovery, but when booting into it I still get the teamwin recovery
I am unsure how to proceed.
Is there a way to fix my phone?
I have my CM11 working version and gapps ready - just need to place it in the phone somehow.
Any help?
Click to expand...
Click to collapse
There is a much easier way :
http://www.androidbrick.com/ultimat...ide-snapdragons-are-unbrickable-qhsusb_dload/
mail me to : [email protected], greetings.
os_man said:
There is a much easier way :
http://www.androidbrick.com/ultimat...ide-snapdragons-are-unbrickable-qhsusb_dload/
mail me to : [email protected], greetings.
Click to expand...
Click to collapse
I know you, you are every where in all sites when searching for brick solutions...and are just thinking of earring money....fuuuii you rotten bastard,I want you too get your greedy as out of here, right now
And reporting this too forum admin right away, so they lock your ip right away
Greedy bastard, seen hundreds of posts, where people begged for the password you locked the rar file with, and only giving it when they pay you....gonna say it again.....
**** OFF
spoonymoon said:
I know you, you are every where in all sites when searching for brick solutions...and are just thinking of earring money....fuuuii you rotten bastard,I want you too get your greedy as out of here, right now
And reporting this too forum admin right away, so they lock your ip right away
Greedy bastard, seen hundreds of posts, where people begged for the password you locked the rar file with, and only giving it when they pay you....gonna say it again.....
**** OFF
Click to expand...
Click to collapse
Every human beeing who can communicate gets the password for free, especialy OPPO and OPO owners, every e-mail i get starting with "Pasword pleaseee pleaseee pleaseee" gets different behaviour of course. OH, and every CLEVER people already knows the tool in my article, i mentioned it a couple of times, for stupids like you its impossible to see of course. I helped hundreds of people for free and sometimes i request for donation, ITS MY VERY COMMON RIGHT + to help those i want and not to help to those that i dont want.
Greetings from TURKEY you silly Viking.
spoonymoon said:
I know you, you are every where in all sites when searching for brick solutions...and are just thinking of earring money....fuuuii you rotten bastard,I want you too get your greedy as out of here, right now
And reporting this too forum admin right away, so they lock your ip right away
Greedy bastard, seen hundreds of posts, where people begged for the password you locked the rar file with, and only giving it when they pay you....gonna say it again.....
**** OFF
Click to expand...
Click to collapse
Taken from my article ( for those who can read ) :
Please Stop asking for password without reading the article completely till the end, THIS TOOL WONT WORK UNLESS YOU HAVE THE NECESSARY SERVICE ROM ! Try sharing your phone model first and also try to share the service ( QPST ) Rom if you have it so more people can use it, THANK YOU.
os_man said:
Every human beeing who can communicate gets the password for free, especialy OPPO and OPO owners, every e-mail i get starting with "Pasword pleaseee pleaseee pleaseee" gets different behaviour of course. OH, and every CLEVER people already knows the tool in my article, i mentioned it a couple of times, for stupids like you its impossible to see of course. I helped hundreds of people for free and sometimes i request for donation, ITS MY VERY COMMON RIGHT + to help those i want and not to help to those that i dont want.
Greetings from TURKEY you silly Viking.
Click to expand...
Click to collapse
Hahaha,if so why, don't you post a link here, on mega or something, instead of all this " mail me" crap??? That would be a honest thing too do, instead....
And no, it's not common too sort in who and which, you want to help out, at least not here on XDA, we help every body, with no exceptions.
I say again, give us this file freely or I report you too forum admins.
My x9076 is bricked because of me making a lvm error, but I'd rather have it semi Working, with messed up partitions, like now, than pay our beg some guy like you for something that not working any way.
Last chance give this freely or get locked out from xda
EDIT: believe me, this turk psyko, has NOTHING not known already, regarding unbricking devices, there´s hundreds of posts here and on oppo forum about people having storage issues etc, not one ever mentioned anything about any other tools than those oppo them selves gave us, there is NO other working ways not known as this cracy dude claims, he´s just running a scam and wants 20$ for nothing - OS_MAN is a fraud dude all over.
EDIT 2: Silence from sir os_man tells the truth....
spoonymoon said:
Hahaha,if so why, don't you post a link here, on mega or something, instead of all this " mail me" crap??? That would be a honest thing too do, instead....
And no, it's not common too sort in who and which, you want to help out, at least not here on XDA, we help every body, with no exceptions.
I say again, give us this file freely or I report you too forum admins.
My x9076 is bricked because of me making a lvm error, but I'd rather have it semi Working, with messed up partitions, like now, than pay our beg some guy like you for something that not working any way.
Last chance give this freely or get locked out from xda
Click to expand...
Click to collapse
Never threaten a Turk Do whatever you can !
If XDA will lock me becouse of you, let it be
And i dont think that you can help anybody with that brain of yours, you even cant rescue your unbrickable Oppo..
spoonymoon said:
I say again, give us this file freely or I report you too forum admins.
Click to expand...
Click to collapse
When asking for help in a free space and for free, sometimes some manners can really make a huge difference. I think you fail to understand that even though you have a problem and someone might have a solution, that someone has no obligation whatsoever to share their time and the fruit of their research with you, especially so when threatened.
Hmm, considering the files and how-to's for unbricking a Find7 are freely available from Oppo forums (and here, I believe), I'm pretty suspicious of anyone doing ANYTHING other than giving them away freely. The files I downloaded and have used, a few times now, were free and had no passwords on zip/rar archives.
As for 'fruits of research', this guy wasn't the guy who put up the how-to's or did the initial research on it so, in my books, he doesn't get the credit, be it kudos OR cash money.
Some folks seem to literally want something for nothing. No harm in asking for donations, sure, but don't be at all surprised if I tell you to go f*** yourself. That's not how this game works, we all stand on each other's shoulders.
Hi,
I've followed the guides to porting CM to a new device. I've managed to compile and got lots of files. I'm unfortunately unable to test my work...
The basis is the great work of @wulsic for Galaxy Fame (the Lite is an ever cheaper version of the Fame so I hope this will work...).
I'd like to flash recovery to test at least the first piece of the compilation...
Problem: I've been unable to connect to the phone using heimdall (I'm under linux). My computer's kernel complains that the phone refuses the assigned USB address. The connection is ok for adb. I've pulled lot of files without problem. For heimdall (phone in "odin" mode), connection problem.
Problem2: I've tried Flashify. The phone is rooted and Flashify has root access. It locks as soon as I choose any command (flash boot/recovery/zip, backup boot/recovery).
Question: since the disk seems to be regular a block device of an SD card (even if soldered on board), is it safe to use
Code:
dd if=recovery.img of=/dev/block/mmc0p6 bs=131072
to flash a partition?
It clearly works the other way (switching if= and of=) to backup the partition (I've done it!). Does it work to flash?
Thanks
SurJector
SurJector said:
Hi,
I've followed the guides to porting CM to a new device. I've managed to compile and got lots of files. I'm unfortunately unable to test my work...
The basis is the great work of @wulsic for Galaxy Fame (the Lite is an ever cheaper version of the Fame so I hope this will work...).
I'd like to flash recovery to test at least the first piece of the compilation...
Problem: I've been unable to connect to the phone using heimdall (I'm under linux). My computer's kernel complains that the phone refuses the assigned USB address. The connection is ok for adb. I've pulled lot of files without problem. For heimdall (phone in "odin" mode), connection problem.
Problem2: I've tried Flashify. The phone is rooted and Flashify has root access. It locks as soon as I choose any command (flash boot/recovery/zip, backup boot/recovery).
Question: since the disk seems to be regular a block device of an SD card (even if soldered on board), is it safe to use
Code:
dd if=recovery.img of=/dev/block/mmc0p6 bs=131072
to flash a partition?
It clearly works the other way (switching if= and of=) to backup the partition (I've done it!). Does it work to flash?
Thanks
SurJector
Click to expand...
Click to collapse
Maybe @faizauthar12 or @zainifame can answer. They are the main developers for this phone. Or try to post this question in a more general thread, since the question also doesn't appear too Galaxy Fame - specific to me. Hope this helps.
BenjyTec said:
Maybe @faizauthar12 or @zainifame can answer. They are the main developers for this phone. Or try to post this question in a more general thread, since the question also doesn't appear too Galaxy Fame - specific to me. Hope this helps.
Click to expand...
Click to collapse
Thanks.
I've tried and it works... I've uploaded the file on the phone, padded it to a multiple of the erase block size and flashed using
Code:
dd if=padded-recovery.img of=/dev/block/mmcbl0p6 bs=524288
and rebooted in recovery mode. The recovery started, however I'll need to work on the code now because the recovery itself does not work (scrambled display).
SurJector said:
Thanks.
I've tried and it works... I've uploaded the file on the phone, padded it to a multiple of the erase block size and flashed using
Code:
dd if=padded-recovery.img of=/dev/block/mmcbl0p6 bs=524288
and rebooted in recovery mode. The recovery started, however I'll need to work on the code now because the recovery itself does not work (scrambled display).
Click to expand...
Click to collapse
Well, could you later put ur sourcecode on github and or give me more details about the recovery
I assume it is cwm? And the scrambled display, do you mean like oblique lines?
And since the only differences between the devices are BCM21654 and BCM21654G they are very close to similair to each other so if you want an stable base and so you could try Cyanogenmod 11 because cm10 isn't really finished and later use the Fame as base sourcecode and change the needed things to make it fully work on ur fame lite:good: All I can do is try to help, but I can't promise I can help 100% as I am also busy with school and other things
Still thankyou for helping users to freedom of samsung bloatware
wulsic said:
Well, could you later put ur sourcecode on github and or give me more details about the recovery
I assume it is cwm?
Click to expand...
Click to collapse
Yes, it is the CWM recovery included in CM10
wulsic said:
And the scrambled display, do you mean like oblique lines?
Click to expand...
Click to collapse
No they were horizontal lines. The display was not correctly recognized. With Samsung's kernel and
Code:
TARGET_RECOVERY_PIXEL_FORMAT := "RGBX_8888"
in BoardConfig.mk the display is correct. I'm now trying to merge Samsung's source code with your kernel. I have noted that width and height of the display are hardcoded in the kernel, nice work Samsung! Several other details are hardcoded (like a binary blob for the display).
wulsic said:
And since the only differences between the devices are BCM21654 and BCM21654G they are very close to similar to each other so if you want an stable base and so you could try Cyanogenmod 11 because cm10 isn't really finished and later use the Fame as base sourcecode and change the needed things to make it fully work on ur fame lite:good: All I can do is try to help, but I can't promise I can help 100% as I am also busy with school and other things
Click to expand...
Click to collapse
I've gone with CM10 because the base firmware is 4.1.2 and CM says "Use the same CM version as your base firmware".
wulsic said:
Still thankyou for helping users to freedom of samsung bloatware
Click to expand...
Click to collapse
You are welcome!
SurJector said:
Yes, it is the CWM recovery included in CM10
No they were horizontal lines. The display was not correctly recognized. With Samsung's kernel and
Code:
TARGET_RECOVERY_PIXEL_FORMAT := "RGBX_8888"
in BoardConfig.mk the display is correct. I'm now trying to merge Samsung's source code with your kernel. I have noted that width and height of the display are hardcoded in the kernel, nice work Samsung! Several other details are hardcoded (like a binary blob for the display).
I've gone with CM10 because the base firmware is 4.1.2 and CM says "Use the same CM version as your base firmware".
You are welcome!
Click to expand...
Click to collapse
Is the galaxy fame lite's kernel sourcecode not available on samsung's open source website? You can see my kernel tree for the commits and you could cherry-pick them.
Well yh, it's recommended to do. But even phones whom were ending with 2.3.7 got until kitkat
Up
Sent from my SM-G313HZ using XDA-Developers Legacy app
If you are on Lollipop, this guide is NOT for you!
Almost none of this is my work, I just collect it and put it together in one place and I'm writing a small how-to get things done.
PLEASE ONLY PROCEED AT YOUR OWN RISK!!!!!!!!!
ONLY FOR ZX551ML
Bootloader unlock:
Currently the only way I was able to get ROOT on the phone was by installing it from TWRP which required an unlocked bootloader, so the first step is to get the bootloader unlocked, to do this please follow this steps:
1) Enable USB debugging - If you do not know what is that and how to do it, you should probably STOP right here.
2) Download and extract: Unlock 6_ZX551ML.ZIP
3) From the extracted folder run unlock.bat (This will restart your phone into fastboot mode, downgrade the bootloader and unlock it)
4) When step 3 is completed, you need to run restore.bat
If everything went on correctly your boot screen should be inverted (white background, black Asus text). This was the most risky part. I only have my phone and it worked, but if something goes wrong here you might end up bricking your phone, so please take extreme care, always read the messages on the screen!!!!!
Custom Recovery:
1) Now to get a custom recovery, please download TWRP-3.0.2-M1-Z00A.img.
2) Put your phone into bootloader mode, if your phone is currently in use, just use the following commands:
Code:
adb reboot bootloader
Alternatively you can power off the phone, remove the USB cable. Power it back on while holding the volume up button.
3) once your phone if in bootloader mode please use the following command:
Code:
fastboot flash recovery TWRP-3.0.2-M1-Z00A.img
4) Use the vol up & down to select "RECOVERY"
5) Use the power button (short press) to reboot to TWRP
ROOTING
1) Download BETA-SuperSU-v2.74-2-20160519174328-patch-by-shakalaca-for-zenfone2-6.0_(1).zip
2) In recovery select Advanced -> Sideload
3) From your computer use the following commands:
Code:
adb sideload "BETA-SuperSU-v2.74-2-20160519174328-patch-by-shakalaca-for-zenfone2-6.0_(1).zip"
4) Once it's completed installing, restart the phone to system
FLASHABLE STOCK ROM
If you have TWRP installed and you want to flash the latest stock ROM, you will need to, make sure you un-root your phone from the supersu app, reboot to recovery and sideload the zip. You can also copy the zip to your phone and install it from twrp. When installing the stock rom, your bootloader will be locked again, so you will need to unlock it (if you wish), also you will need to root again, because the root is lost. However the modified stock rom will NOT remove the custom recovery giving you freedom to flash whatever you like in the future...
XPOSED
Xposed on our device won't work if we have SuperSu installed. If you want to use Xposed modules you will need to use PHH's SuperUser instead. All files required for Xposed/Magisk/Phh's SuperUser are available in the Xposed folder.
Available modified stock rom versions:
UL-Z00A-WW-4.21.40.141-user-TWRP.zip - Updated: 2016-Oct-07
UL-Z00A-WW-4.21.40.197-user-TWRP.zip - Updated: 2016-Dec-16
Files can be downloaded from: here
Again, please proceed on your own risk.
Special tanks and credits to all the guys who made this possible, namely:
@sorg @social-design-concepts @shakalaca - For bootloader unlock
@jrior001 for the TWRP
@shakalaca - For the modified SuperSU package.
Magisk / systemless should also work?
any way to get back the noninverted Bootscreen?
Tr4sHCr4fT said:
Magisk / systemless should also work?
any way to get back the noninverted Bootscreen?
Click to expand...
Click to collapse
Yes I'm using Magisk, but even with it I wasn't able to use Google Pay. To get back to non inverted, you will need to flash the locked bootloader.
Emil Borconi said:
Yes I'm using Magisk, but even with it I wasn't able to use Google Pay. To get back to non inverted, you will need to flash the locked bootloader.
Click to expand...
Click to collapse
While essentially true the user can always use a different boot animation by flashing one via twrp. There might even be one somewhere of the unmodified asus screen.
Can anyone confirm the flashable Rom mentioned in Post #1 is MM 6.0.1? I ask because my phone upgraded itself right after I booted it up and I wondered if it was on a newer version than the downloadable one. Pretty sure the update was only security updates given it was only around 80mb.
The actuall boot screen is only a couple of seconds long while the boot animation shown
---------- Post added at 10:00 PM ---------- Previous post was at 09:02 PM ----------
Well as usual the linux users drew the short straw. The shell script is for mac users. I decided to see about running the lines manually but never even reached the "danger zone". As soon as I did an "adb reboot bootloader" I followed up with "sudo fastboot devices" (some linux distro's need sudo..some don't)....and nothing shows up although I can clearly see the device is hooked up and in fastboot mode as well as the fact the adb reboot bootloader worked. I swap out one of my other devices and check things...they show up fine in fastboot....ok...so what's missing from this picture?
*update* solved by updating the ubuntu adb and fastboot binaries from here: https://github.com/simmac/minimal_adb_fastboot/tree/master/linux
*update2* bootloader unlocked, supersu flashed and verified. Much appreciated.
I ran the bootloader unlock and it appeared to work. Now it keeps booting back into the bootloader. I can't seem to get it to boot normal. Suggestions?
Nevermind, I didn't realize that I needed to run restore.bat while still in the bootloader. It is booting now! I was able to follow your guide and it is now rooted.
Regarding the marshmallow zip you include. I have a couple questions.
- For the modified stock version that will keep the recovery do I just need to flash it from recovery?
- Do I need to unroot before flashing this modified stock marshmallow?
Thanks!
slgooding said:
I ran the bootloader unlock and it appeared to work. Now it keeps booting back into the bootloader. I can't seem to get it to boot normal. Suggestions?
Nevermind, I didn't realize that I needed to run restore.bat while still in the bootloader. It is booting now! I was able to follow your guide and it is now rooted.
Regarding the marshmallow zip you include. I have a couple questions.
- For the modified stock version that will keep the recovery do I just need to flash it from recovery?
- Do I need to unroot before flashing this modified stock marshmallow?
Thanks!
Click to expand...
Click to collapse
Happy to read you got it booting, by the time I got to answer you seemed to git it figured out.
Regarding the zip, yes flash from recovery and you don't need to unroot before, but you will need to root after flashing.
However I do suggest you make a backup before flashing jsut in case....
Emil Borconi said:
Happy to read you got it booting, by the time I got to answer you seemed to git it figured out.
Regarding the zip, yes flash from recovery and you don't need to unroot before, but you will need to root after flashing.
However I do suggest you make a backup before flashing jsut in case....
Click to expand...
Click to collapse
I'm assuming the file is just for folks who are on lollipop who want to upgrade? Didn't see any need to flash it since already on 6.0.1 and have it rooted...unless I'm missing something again.
I read this after I went to 6.0.1 from Asus's manual download and update process. I can't get ADB to connect in the OS (developer mode never displays, even though it tells me I'm a developer after doing kernel ver. button process). I tried to get adb devices -l in fastboot and recovery, and it wont discover it. I've tried multiple windows drivers (including the one that worked when I flashed the firmware the first time) to no avail. Any ideas?
Irishman2020 said:
I read this after I went to 6.0.1 from Asus's manual download and update process. I can't get ADB to connect in the OS (developer mode never displays, even though it tells me I'm a developer after doing kernel ver. button process). I tried to get adb devices -l in fastboot and recovery, and it wont discover it. I've tried multiple windows drivers (including the one that worked when I flashed the firmware the first time) to no avail. Any ideas?
Click to expand...
Click to collapse
If windows doesn't see the phone when in recovery there is something wrong, this can be:
1) Wrong driver
2) Damaged USB cable
3) Damaged USB port.
When you are in recovery you should see the phone with adbm if you are in fastboot you should see the phone with:
Code:
fastboot devices
If nothing works you have the nuclear option.
Manually download the original firmware from Asus website: https://www.asus.com/support/Download/39/1/0/26/BXbNqJplzZiLmk6G/32/
copy the zip to an Sd card.
1) Now Turn Off your phone and boot into recovery mode by pressing Power+Volume UP.
2) Now in recovery mode choose to apply update from sdcard.
3) Now select the zip file.
4) Now wait until the process complete and then Reboot the phone.
5) Done!
famewolf said:
I'm assuming the file is just for folks who are on lollipop who want to upgrade? Didn't see any need to flash it since already on 6.0.1 and have it rooted...unless I'm missing something again.
Click to expand...
Click to collapse
More or less true, but somehow I was on a 6.0.1 version which is now gone from the firmware list of Zenfone, meaning I have updated from 6.0.1 to 6.0.1
Again now I see there is a new firmware released yesterday if I have the time I will patch that system image as well so it can be upgraded with TWRP.
famewolf said:
I'm assuming the file is just for folks who are on lollipop who want to upgrade? Didn't see any need to flash it since already on 6.0.1 and have it rooted...unless I'm missing something again.
Click to expand...
Click to collapse
Just for you I've just uploaded the 4.21.40.197 release as well... so now there is a point of the TWRP rom's
Emil Borconi said:
Just for you I've just uploaded the 4.21.40.197 release as well... so now there is a point of the TWRP rom's
Click to expand...
Click to collapse
Typical....now you've given me work I need to do on the phone. ;P
Appreciate your work!
Out of curiosity have you tried xposed?
famewolf said:
Typical....now you've given me work I need to do on the phone. ;P
Appreciate your work!
Out of curiosity have you tried xposed?
Click to expand...
Click to collapse
Yes and it works. I tried a few modules, but generally speaking I'm not a big xposed user myself. Nify doesn't work to well because of all the asus software on it and I wasn't able to get google assistant either. Android audo mod worked perfectly, so yeah generally speaking xposed work's
Emil Borconi said:
Yes and it works. I tried a few modules, but generally speaking I'm not a big xposed user myself. Nify doesn't work to well because of all the asus software on it and I wasn't able to get google assistant either. Android audo mod worked perfectly, so yeah generally speaking xposed work's
Click to expand...
Click to collapse
Thanks...that answers all my questions except for figuring out what's safe to disable. I put a post in q&a but no replies..the zoom appears to have a very small group on xda. I'll figure it out eventually.
famewolf said:
Thanks...that answers all my questions except for figuring out what's safe to disable. I put a post in q&a but no replies..the zoom appears to have a very small group on xda. I'll figure it out eventually.
Click to expand...
Click to collapse
Actually most if them can be. Here is a print screen of the ones I have disabled on my phone hover I have a zenpad z380c which I use as my car dashboard and on that one o have disabled almost of all of the apps, except zenhome, audio manager and the file manager.
Yes I was surprised to find out that there is almost no zoom community.
Emil Borconi said:
Actually most if them can be. Here is a print screen of the ones I have disabled on my phone hover I have a zenpad z380c which I use as my car dashboard and on that one o have disabled almost of all of the apps, except zenhome, audio manager and the file manager.
Yes I was surprised to find out that there is almost no zoom community.
Click to expand...
Click to collapse
I'm actually enjoying mobile managers auto startup managing...it's done a good job of keeping 10000 things from running at startup that don't need to although "Startup Manager" would do a similar job for free. I'm liking the zenui launcher and calling screen so don't want to break anything related to that...the phone's been performing exceptionally well for days on end with no required reboots. Been very impressed. Previously been fighting with a T-mobile V10 and an Alcatel Idol 3...the v10 had spontaneous reboots...the idol had a stock rom with a bunch of lag in it....tiny to nothing development on both of those.
What about Zentalk, ZenChoice, PhotoCollage, MyAsus Service center, Clean Master, Audiowizard and Bug Reporter?
famewolf said:
I'm actually enjoying mobile managers auto startup managing...it's done a good job of keeping 10000 things from running at startup that don't need to although "Startup Manager" would do a similar job for free. I'm liking the zenui launcher and calling screen so don't want to break anything related to that...the phone's been performing exceptionally well for days on end with no required reboots. Been very impressed. Previously been fighting with a T-mobile V10 and an Alcatel Idol 3...the v10 had spontaneous reboots...the idol had a stock rom with a bunch of lag in it....tiny to nothing development on both of those.
Click to expand...
Click to collapse
I use tasker for that, but yes I agree as a whole is not bad, this is my 4rd Asus product (Zenfone 4, Zenfone 2, Zoom and Zenpad) and overall I'm quite impressed with how they perform, just the support from Asus isn't really the top of the cream... they released MM when other were releasing N... so yeah a bit of sour taste, otherwise happy. And the camera, I think it's brilliant, not the best on the market, but the optical zoom is cool, as well as the camera app which allows you to do some nice manual shooting.
Emil Borconi said:
I use tasker for that, but yes I agree as a whole is not bad, this is my 4rd Asus product (Zenfone 4, Zenfone 2, Zoom and Zenpad) and overall I'm quite impressed with how they perform, just the support from Asus isn't really the top of the cream... they released MM when other were releasing N... so yeah a bit of sour taste, otherwise happy. And the camera, I think it's brilliant, not the best on the market, but the optical zoom is cool, as well as the camera app which allows you to do some nice manual shooting.
Click to expand...
Click to collapse
I listed a few apps in my previous post I wondered if you had looked at..it was a last minute addition so you may have missed it. I own tasker...I'm unaware of using it to stop tasks from running at bootup although I have used it to MAKE some apps run after "Boot Completed".
famewolf said:
I listed a few apps in my previous post I wondered if you had looked at..it was a last minute addition so you may have missed it. I own tasker...I'm unaware of using it to stop tasks from running at bootup although I have used it to MAKE some apps run after "Boot Completed".
Click to expand...
Click to collapse
Generally tasker can be used for almost anything.... but I'm doing most of the thing with root+shell scripts, but yes nothing wrong with the app provided by Asus. I think everybody uses the setup/software he/she is most comfortable using... and there is no right or wrong.... that's until you are NOT and iCrap user, because that is the ultimate WRONG! )
Emil Borconi said:
Generally tasker can be used for almost anything.... but I'm doing most of the thing with root+shell scripts, but yes nothing wrong with the app provided by Asus. I think everybody uses the setup/software he/she is most comfortable using... and there is no right or wrong.... that's until you are NOT and iCrap user, because that is the ultimate WRONG! )
Click to expand...
Click to collapse
Well from the lack of posts it appears you and I ARE the zenfone zoom community. Any idea where the system updates get stored after downloading? I thought in /cache based on regular zenfone posts but was unable to see it. I've got one available but it has to be modified for twrp compatibility as well as unrooting temporarily.
Hello all,
I've been seeing similar threads about the N7 being used for car use here and other places, but there are enough differences in what I saw, or the software was outdated or the computer they were using (I'm on a Mac) or bad mirrors in downloads that I get confused and stuck and stop trying for a while. If I can get ALL of the instructions that are the most current in light of what software is available with fresh links, I think I'll be set.
Background: Recently purchased an '04 Mazda RX-8 with a very dated GPS nav screen that pops up when you turn the car on. I purchased the N7 to go in this slot since it has a lot more features I would like to have like Torque and the ability to play music from Pandora or Spotify from my phones' hotspot, and it should be able to just barely fit with the charge cable and headphone jack output connected. I would like to eventually have mine permanently installed here. I have found enough videos to feel comfortable with the wiring of this. I have a bluetooth adapter for Mazda's in case the analog cable doesn't fit/work, a USB hub and 3amp charger all ordered.
I currently am rooted and on stock 4.3 with Kernel 3.4.0-g1f57c39 Build JWR66N I have TWRP installed on my device
Where I'm stuck at and need help is the uploading of the correct (subjective term) Lineage ROM for what I'm using this for AND the correct Kernal (that I think has to match the ROM?), which is using the OTG cable to charge, and have the option to pull music off an SD card connected to a USB hub. I understand I'll need Elementalx to go with a compatible ROM? I plan on getting some sort of car themed launcher so that I would use the launcher screen every time I hop in the car and start it. I would like the tablet to go into power saving mode when power is removed from the OTG cable. I have also seen installs using a magnet in the dash so that when the tablet goes down, it shuts off the screen (also triggering power saving mode?) Many users were using TIMUR's Kernel, which I understand to be unsupported and outdated.
I see other threads with older versions like 14.1 of L OS using the kernal that supports OTG charging. Do I need to have an older version of Lineage or can I use the 17.X version? Whatever makes the tablet stable and consumes the least amount of power when in standby would be ideal. What Gapps configuration should I use? Can I download all of this on the tablet and flash from there using TWRP? I've been out of the Android scene for a while and a lot has changed. Just need some coaching on what the steps will be to get the right versions of these flashed without bricking my N7! Thanks for your help!
PS: Sorry about the images. They wouldn't orient correctly.
nathanthepilot said:
I've been seeing similar threads about the N7 being used for car use here and other places, but there are enough differences in what I saw.......
I currently am rooted and on stock 4.3 with Kernel 3.4.0-g1f57c39 Build JWR66N I have TWRP installed on my deviceWhere I'm stuck at and need help is the uploading of the correct (subjective term) Lineage ROM for what I'm using this for AND the correct Kernal (that I think has to match the ROM?), which is using the OTG cable to charge...............
Click to expand...
Click to collapse
I guess you are referring to the currently active thread on the subject. I propose that you settle on LOS14.1 and follow these steps:
get LOS14.1
get gapps (select ARM 7.1 pico)
get ElementalX-N7-6.17
get addonsu-14.1-arm-signed.zip //optional - if you want root
boot TWRP
copy LOS, addonsu, gapps and EX to N7
in TWRP do standard 'Wipe' THEN install LOS, THEN addonsu, THEN gapps
in TWRP install EX and preset "doubletap2wake", "Battery life extender" and "USB OTG + charge mode"
That's it. Have a nice ride :fingers-crossed:
k23m said:
I guess you are referring to the currently active thread on the subject. I propose that you settle on LOS14.1 and follow these steps:
get LOS14.1
get gapps (select ARM 7.1 pico)
get ElementalX-N7-6.17
get addonsu-14.1-arm-signed.zip //optional - if you want root
boot TWRP
copy LOS, addonsu, gapps and EX to N7
in TWRP do standard 'Wipe' THEN install LOS, THEN addonsu, THEN gapps
in TWRP install EX and preset "doubletap2wake", "Battery life extender" and "USB OTG + charge mode"
That's it. Have a nice ride :fingers-crossed:
Click to expand...
Click to collapse
Thank you for the reply and information, K23m! I have all of the files downloaded onto my Mac, have transferred them to the N7 via Android File Transfer and got LOS to install. I'm in the middle of getting all of the other elements to install and I'll report back if there are any troubles. Thanks again for the quick, and on-point reply. This is all I needed! :good::highfive:
nathanthepilot said:
Thank you for the reply and information, K23m! I have all of the files downloaded onto my Mac, have transferred them to the N7 via Android File Transfer and got LOS to install. I'm in the middle of getting all of the other elements to install and I'll report back if there are any troubles. Thanks again for the quick, and on-point reply. This is all I needed! :good::highfive:
Click to expand...
Click to collapse
Well, after I got LOS installed, I was unable to get the root zip installed. I got "Zip signature verification failed!" and it wouldn't install. Also not able to install Googleapps for the same reason. I think maybe the files didn't transfer properly. I can't get USB debugging to work on LOS with my Android File Transfer App on the Mac. I'll have to do some research. I think I need to re-download or re-transfer the files to the N7 to get them to load properly. Very limited on what I can do with no Play store or USB debugging. I'll try again in the morning.
Update: I was able to download the files directly onto the tablet and get them installed. Play store works. Thanks again for the help! I think I just didn't transfer the files correctly. I selected all of them and dragged them to the N7. I think that caused a problem with the files. Anyway, a download from the N7 itself worked. Cheers!
k23m said:
I guess you are referring to the currently active thread on the subject. I propose that you settle on LOS14.1 and follow these steps:
get LOS14.1
get gapps (select ARM 7.1 pico)
get ElementalX-N7-6.17
get addonsu-14.1-arm-signed.zip //optional - if you want root
boot TWRP
copy LOS, addonsu, gapps and EX to N7
in TWRP do standard 'Wipe' THEN install LOS, THEN addonsu, THEN gapps
in TWRP install EX and preset "doubletap2wake", "Battery life extender" and "USB OTG + charge mode"
That's it. Have a nice ride :fingers-crossed:
Click to expand...
Click to collapse
Thanks for this. I have been using my nexus 7 in my vehicle for years, but it needed a refresh. I followed this and worked perfect.
I did the same but instead of addonsu I installed Magisk. And now when I try to install ElementalX-N7-6.17 I got a "Zip signature verification failed!". I have downloaded it again. The md5 sum is also correct. How can I fix that?
k23m said:
get LOS14.1
get gapps (select ARM 7.1 pico)
get ElementalX-N7-6.17
Click to expand...
Click to collapse
I am wondering if the usb issues with elementalx were corrected since my last test with a flo tablet lineageos 14.1 and elementalx as i mentioned earlier here:
https://forum.xda-developers.com/showpost.php?p=74291365&postcount=6042