Hi,
I've been trying to find a custom recovery for the new Asus Tinkerboard, which is based on a RK3288 chipset, running Android 6.0.1, so I can install zip files from sdcard etc.
The generic CWM 6.0.5.1 by @Oma7144 *almost* works, but it usually hangs after saying can't open /dev/block/...../misc (no such file or directory).
The one time it got past this it gave me the menu option for reboot/install zip etc, but I couldn't move up and down the menu with my USB-attached keyboard.
Does anyone know if there's a later build, or a tinkerboard-specific one anywhere?
Thanks,
Iain
iainfm said:
Hi,
I've been trying to find a custom recovery for the new Asus Tinkerboard, which is based on a RK3288 chipset, running Android 6.0.1, so I can install zip files from sdcard etc.
The generic CWM 6.0.5.1 by @Oma7144 *almost* works, but it usually hangs after saying can't open /dev/block/...../misc (no such file or directory).
The one time it got past this it gave me the menu option for reboot/install zip etc, but I couldn't move up and down the menu with my USB-attached keyboard.
Does anyone know if there's a later build, or a tinkerboard-specific one anywhere?
Thanks,
Iain
Click to expand...
Click to collapse
Hey lain,
Did you solved your problem till now?
i think the big problem is that the Tinker board is not so popolar at the moment and you see this specialy on xda that there are not much to find about it.
I have the TB too and i am actually very active at the Tinker board community Forum but also there are not much solutions for some things i need or want for example bluetooth functions to use it as a headset.
But try your luck there and ask your question.
Greets
Check out TWRP Builder
iainfm said:
Hi,
I've been trying to find a custom recovery for the new Asus Tinkerboard, which is based on a RK3288 chipset, running Android 6.0.1, so I can install zip files from sdcard etc.
The generic CWM 6.0.5.1 by @Oma7144 *almost* works, but it usually hangs after saying can't open /dev/block/...../misc (no such file or directory).
The one time it got past this it gave me the menu option for reboot/install zip etc, but I couldn't move up and down the menu with my USB-attached keyboard.
Does anyone know if there's a later build, or a tinkerboard-specific one anywhere?
Thanks,
Iain
Click to expand...
Click to collapse
They already compiled a working I'm going of TWRP and it can be downloaded thru the site or app. Heads up thou, I have a TB S with 7.1.2 and it would not work, just bootlooped or wouldn't return to recovery at all. Let me know if that works for you, the img number is 630 I believe, just follow the instructions, I already rooted and installed play on mine before doing this
supasleeze said:
They already compiled a working I'm going of TWRP and it can be downloaded thru the site or app. Heads up thou, I have a TB S with 7.1.2 and it would not work, just bootlooped or wouldn't return to recovery at all. Let me know if that works for you, the img number is 630 I believe, just follow the instructions, I already rooted and installed play on mine before doing this
Click to expand...
Click to collapse
had same issue, not sure if mine is s or not, i think it's just the regular TB.
the port poorly ported or it's just intentional anti-leech. if you look in the fstab files, you'll see it...
honestly, the best way would be to port it by yourself. i'm gonna try doing that sometime this month, no guarantees though
Related
Hi all,
Hopefully this is something fairly simple to answer, but my dilemma is that I want to flash a different ROM onto my wifi Xoom. I understand the basic process (I flashed the ROM on my old HTC Hero several times), but have been running into trouble on the Xoom and I think it boils down to the fact that Recovery Mode can't mount my SD card. I assume by SD card it means internal storage, but it can't read that or an actual SD card so I'm not sure it matters.
Anyway, after a couple of hours of research, I discovered that the best way to fix this is apparently to re-flash my recovery to version 3.2.0.0 of CWM instead of the 5.8.3.1 the current version of ROM Manager installed. After digging around, I found what I believe is 3.2.0.0, but I can't figure out where to put it so ROM Manager can find it and flash it over the current Recovery image. Also, if anyone has a link to download 3.2.0.0 that they know works, please let me know because I couldn't find a working download link anywhere.
I've also looked into doing it through Fastboot, but can't exactly figure out how to do that, either. I downloaded the fastboot.exe application and installed the Android SDK, but it tells me that it can't start because AdbWinApi.dll is missing. Being a non-developer type, I have no idea where this is supposed to come from, how I should install it, and if there's any other steps I'm missing.
So if anybody can help me out with either of these (preferably using the older version of CMW), that'd be great, but if anyone has an even easier way to do it, please share by all means. I know what I'm doing once I get to the point of installing the new ROM and Gapps, I just need my Xoom to be able to find them first.
Thanks in advance to anyone who can help out!
Stu
Use this thread
http://forum.xda-developers.com/showthread.php?t=1074979
In the future use the search button, it was pretty easy to find with just a little effort.
063_XOBX said:
Use this thread
http://forum.xda-developers.com/showthread.php?t=1074979
In the future use the search button, it was pretty easy to find with just a little effort.
Click to expand...
Click to collapse
Will do...and thanks, that worked.
Hi all,
to make it plain and short: I messed up.
I have a GT-S5830i which I unrooted according to the Sticky Note in the forum, installed CWM Recovery and then 'installed from ZIP' a CM9_cooperve_Beta_05.zip that I found in one of the posts in the forum. The installation went on without error message but since then the phone does not make it beyond the initial screen "Samsung Galaxy Ace GT-S5830i". I can start recovery mode and Download mode. In reovery mode I can format cache, data, sdcard, sd-ext but *not* system. Error Message: "E: format_volume: make_ext4fs failed on /dev/block/st19"
I have tried already several methods according to the forum, e.g.
1) 'install from ZIP' older Cyanogenmod
2) the tool ext4_formatter.zip
3) re-flash with ODIN with several tar-ROMs, all failed. Odin finds the phone (since I start Odin as Admin now), but after I hit 'start' it tries to establish a connection to the phone and ends after a while with 'Failed'
I'm basically lost now, don't know what else to do. Any advise is appreciated (it's my mom's phone, she is getting impatient )
Thx, cheers!
Xala
Hi @xalarsk , So you can't format your /system partition , which is required for installation of your rom ,, you need to try this method from here mate . Follow my instruction from the line @post#4 :"1. Download one of the newest ,,," to the end of the post and please do not use CM9 beta , because it is unstable and will wreak havoc with your system eventually . ( either cm7 or cm11 is the place you should go for CyanogenMod experience for cooperVe device ).
If you fail at any level please give us your logcat ( error massage ) for better support for your Odin process you mentioned .
Cygwin not working
Hi @ehsanotaku,
thank you for your quick reply, it's appreciated!
Unfortunately I couldn't get cygwin to install all necessary packets. The ZIP-test always failed. I have a Linux system running (Linux Mint 17) though, and hope that might help. In the meantime I tried to download the already split packages as described in another of your forum posts, but the website provides only exe-files instead of zip-files. Is there another location to download them?
#UPDATE: It seems there is a SplitFUS2 version for linux somewhere but couldn't find links to download. Anybody can help? I'll also PM Doky73
Cheers, Holger
xalarsk said:
Hi @ehsanotaku,
thank you for your quick reply, it's appreciated!
Unfortunately I couldn't get cygwin to install all necessary packets. The ZIP-test always failed. I have a Linux system running (Linux Mint 17) though, and hope that might help. In the meantime I tried to download the already split packages as described in another of your forum posts, but the website provides only exe-files instead of zip-files. Is there another location to download them?
#UPDATE: It seems there is a SplitFUS2 version for linux somewhere but couldn't find links to download. Anybody can help? I'll also PM Doky73
Cheers, Holger
Click to expand...
Click to collapse
Cygwin was meant for windows platform to get the native Linux environment/command line you already got there . You can create a virtual instance of the windows 7 inside virtualbox or any kind of apps you are preferring such as Vmware/Parallel etc etc to get the job done .
Splitfus2 only supports windows platform as far as i know mate,,, either vitalization as i said or the pre-made zip package ( which is clearly not .exe file ,, push the download now and get yourself a descent downland manager,, tested and zip packaged delivered ) from here is the feasible approach for your problem .
Ok, had all the files ready, just the Boot loader <DefaultCalDataWithBoot_S5830iXXLB1_REV00.tar.rar seems to be broken. I downloaded the link provided in your post #8 several times with several download managers, also uses 7-zip and several online unrar services..result always the same: The archive is broken. Is that possible? Would you mind to check yourself?
xalarsk said:
Ok, had all the files ready, just the Boot loader <DefaultCalDataWithBoot_S5830iXXLB1_REV00.tar.rar seems to be broken. I downloaded the link provided in your post #8 several times with several download managers, also uses 7-zip and several online unrar services..result always the same: The archive is broken. Is that possible? Would you mind to check yourself?
Click to expand...
Click to collapse
Another fellow had similar issue with my attachment that was corrected here @ post#27
Unbricked, SD card not recognized
Update: Phone has been unbricked, many thanks for that!
Currently I have still issues with the external SD card, which also holds the ZIP files. Phone won't recognize it, not even format it properly. Still working on that.
Cheers, Xala
xalarsk said:
Update: Phone has been unbricked, many thanks for that!
Currently I have still issues with the external SD card, which also holds the ZIP files. Phone won't recognize it, not even format it properly. Still working on that.
Cheers, Xala
Click to expand...
Click to collapse
Mostly this happened because of the bug inside CM9 beta you used . Study this topic mate i troubleshooted while ago for a sample of the symptoms external SD card would show after unstable ICS usage .
Also as an alternative to the method i instructed there , you can format/Re-partition your SD card by putting it inside card reader and using app such as free MiniTool Partition Wizard "Gparted" tool for Linux users Or "iPartiton" for Mac users etc etc ,, to get the job done . You can find several tutorials inside XDA for this matter mate.
Phone works with CM7.2, can I upgrade to CM9?
Hi again,
first of all, props to @ehsanotaku, I will hit the 'Thanks' buttons.
Now, this is a bit beyond the topic, but I'd like to ask anyway for recommendations of CM9 roms. The one I picked from a post inside this forum bricked my phone and made me start this thread, I don't want to go down this road again. So I'd be glad for any recommendation of a stable ROM that will put my phone beyond Android 4.0.
Cheers again,
Xala
So i have a similar issue. I used to have CM11 installed, but i figured thats too slow for me. Then i went back to stock rom (XXMJ2) which works fine. But now i have a problem.
Everytime i want to flash a stock based or cm7 based rom on my phone, it gets messed up. Today i wanted to flash this
http://forum.xda-developers.com/galaxy-ace/s5830i-develop/cm-7-2-kitkat-smart-r2-t3075267
i naturally downloaded clockwork mod recovery (5.0.2.6) and tried to flash it. Flashing was done pretty quickly (10 seconds or so) and when i rebooted, i obviously got stuck at sammy logo. Now booting back to the recovery (first e3 then cwm) i got bunch of error about partritions not being able to be mounted (happens the same if i want to manually mout them or format them)...
So, what to do ?
I have a suspicion, that flashing CM11 and the latest cwm recovery for it somehow messed up partritions.
hojnikb said:
So i have a similar issue. I used to have CM11 installed, but i figured thats too slow for me. Then i went back to stock rom (XXMJ2) which works fine. But now i have a problem.
Everytime i want to flash a stock based or cm7 based rom on my phone, it gets messed up. Today i wanted to flash this
http://forum.xda-developers.com/galaxy-ace/s5830i-develop/cm-7-2-kitkat-smart-r2-t3075267
i naturally downloaded clockwork mod recovery (5.0.2.6) and tried to flash it. Flashing was done pretty quickly (10 seconds or so) and when i rebooted, i obviously got stuck at sammy logo. Now booting back to the recovery (first e3 then cwm) i got bunch of error about partritions not being able to be mounted (happens the same if i want to manually mout them or format them)...
So, what to do ?
I have a suspicion, that flashing CM11 and the latest cwm recovery for it somehow messed up partritions.
Click to expand...
Click to collapse
ok not going to excruciating details of symptoms and explaining all of your errors for now just please read my advice @ post2 of this topic and follow the procedures accordingly and finished it with formatter tools and cm7 instructions you will find there ., after that you can install Kitkat Smart R2 like you are coming from another CM7 build instruction . btw some problem regarding super user privileges and play store 492-498 infamous bug was reported for this fairly new development .
Hey! I am trying to get Cyanogenmod 12.1 on my stock Nook Tablet. I no longer use the Nook Tablet as often and would like to give it a new life by making it an Android. After reading a ton of articles and forums, I have tried a ton of them, but none of them seem to work successfully. One of them I tried was, Install CM for acclaim on the wiki.cyanogenmod.org website , the process went successfully until I rebooted and it continued to boot me to the regular Nook setup. I think it is because the Clockworkmod Recovery is outdated. I also see that Cyanogenmod's latest recovery is also available, but how do I put it on my SD card successfully. Please provide a step to step guide for me. Thank you!
BornReady_ said:
Hey! I am trying to get Cyanogenmod 12.1 on my stock Nook Tablet. I no longer use the Nook Tablet as often and would like to give it a new life by making it an Android. After reading a ton of articles and forums, I have tried a ton of them, but none of them seem to work successfully. One of them I tried was, Install CM for acclaim on the wiki.cyanogenmod.org website , the process went successfully until I rebooted and it continued to boot me to the regular Nook setup. I think it is because the Clockworkmod Recovery is outdated. I also see that Cyanogenmod's latest recovery is also available, but how do I put it on my SD card successfully. Please provide a step to step guide for me. Thank you!
Click to expand...
Click to collapse
I just did this about a week ago (finally) and there are no better instructions for getting started than those provided by digixmax here. Just ignore the statements about CM 11 and forge ahead. Later in that thread there are a variety of recommendations for file substitutions in the method if you are aiming for CM 12 instead of 11. I followed the ones here. These also work.
My own discovery was that you should ignore the TWRP error messages about being unable to mount '/bootdata'. I finally came across that somewhere and it proved to be true for me.
Take it slow. Gather together all the files you will need first. Then prep the SD card (don't forget to set the flag). Then copy the files over in the order specified. It matters. Then go for it! (don't neglect to backup the stock system before wiping things--you may be glad you did).
My start-up with CM 12.1 was really rough and I thought I might abandon it but after a few days and quite a number of reboots things settled down. Maybe that has something to do with coming from CM 10.2.1, maybe not. Anyway, the system is no worse than CM 10.2.1 and I don't have trouble with cold or warm boots hanging like I used to with CM 10.2.1.
My pet peeves are listed here and/or here but may be idiosynchratic to my device or particular flash.
nmyshkin said:
I just did this about a week ago (finally) and there are no better instructions for getting started than those provided by digixmax here. Just ignore the statements about CM 11 and forge ahead. Later in that thread there are a variety of recommendations for file substitutions in the method if you are aiming for CM 12 instead of 11. I followed the ones here. These also work.
My own discovery was that you should ignore the TWRP error messages about being unable to mount '/bootdata'. I finally came across that somewhere and it proved to be true for me.
Take it slow. Gather together all the files you will need first. Then prep the SD card (don't forget to set the flag). Then copy the files over in the order specified. It matters. Then go for it! (don't neglect to backup the stock system before wiping things--you may be glad you did).
My start-up with CM 12.1 was really rough and I thought I might abandon it but after a few days and quite a number of reboots things settled down. Maybe that has something to do with coming from CM 10.2.1, maybe not. Anyway, the system is no worse than CM 10.2.1 and I don't have trouble with cold or warm boots hanging like I used to with CM 10.2.1.
My pet peeves are listed here and/or here but may be idiosynchratic to my device or particular flash.
Click to expand...
Click to collapse
I literally just finished sending a message to digixmax when you posted this. I remember seeing you in the other forum, trying to get CM12.1 to install. I did all this instructions over and over for hours, but I keep getting stuck at the CyanoBoot section. I get the Boot Menu, but then the SDC Recovery option isn't available, I see it, but it isn't clickable.
BornReady_ said:
I literally just finished sending a message to digixmax when you posted this. I remember seeing you in the other forum, trying to get CM12.1 to install. I did all this instructions over and over for hours, but I keep getting stuck at the CyanoBoot section. I get the Boot Menu, but then the SDC Recovery option isn't available, I see it, but it isn't clickable.
Click to expand...
Click to collapse
OK, so as soon as the cyanoboot screen appears you hold down the N button, right?
Also, did you boot with the power cable connected?
nmyshkin said:
OK, so as soon as the cyanoboot screen appears you hold down the N button, right?
Also, did you boot with the power cable connected?
Click to expand...
Click to collapse
Yes, I booted with the power cable connected, I tried on being connected to the laptop and power wall as well. I also held down the N button, which is why I got to the Boot Menu.
Bear with me
Are you sure you got the SD card version of TWRP?
Yes, 100% sure.
BornReady_ said:
Yes, 100% sure.
Click to expand...
Click to collapse
Well that was interesting! We're "live" apparently
I want to help but I'm not digixmax... I'll bet he has an idea. Wait for him to get back to you while I rummage around.
Lol, thanks for the help anyways though. I will have to wait for digixmax.
Wow, everytime you mention digixmax, he replies. He just privated messaged me in return.
If you can get to the CyanoBoot menu but its menu entry for "SDC recovery" is greyed out then it's because CyanoBoot (flashing_boot.img) cannot find a recovery.img file on your bootable SDcard.
Which version of SD-based recovery did you download and use?
You might want to wait for and check against the answer to my inquiry post at http://forum.xda-developers.com/showpost.php?p=65016892&postcount=41 (I no longer have a NT and as such cannot vouch for any specific recent recovery versions).
I'm sorry, I should have been more precise. I don't know if it will help, but this is the TWRP recovery image I used successfully when I tried this process. That's v. 2.8.6.0
digixmax said:
If you can get to the CyanoBoot menu but its menu entry for "SDC recovery" is greyed out then it's because CyanoBoot (flashing_boot.img) cannot find a recovery.img file on your bootable SDcard.
Which version of SD-based recovery did you download and use?
You might want to wait for and check against the answer to my inquiry post at http://forum.xda-developers.com/showpost.php?p=65016892&postcount=41 (I no longer have a NT and as such cannot vouch for any specific recent recovery versions).
Click to expand...
Click to collapse
I have seen everyone else's folders and they seem to include "flashing_boot.img" However, the file I downloaded from your page only has "flashing_boot" When I try to rename the file, the Nook Tablet won't even turn on anymore at all. Matter of fact, I can't even get to the Boot Menu now, it keeps having that red line that states, "booti: bad boot image magic (in memory)" I'm losing hope...
BornReady_ said:
I have seen everyone else's folders and they seem to include "flashing_boot.img" However, the file I downloaded from your page only has "flashing_boot" When I try to rename the file, the Nook Tablet won't even turn on anymore at all. Matter of fact, I can't even get to the Boot Menu now, it keeps having that red line that states, "booti: bad boot image magic (in memory)" I'm losing hope...
Click to expand...
Click to collapse
Don't give up. If you're using a Windows machine to prepare the card then whether the .IMG is displayed or not depends on your settings. It does not show on mine but a look at the file properties shows it is an .IMG file.
So that's the wrong tree. SDCards have been known to be problematic so if you have another around you might want to give it a try. You also might do a slow (complete) format on it before preparing it from scratch.
The other thing, of course, is the integrity of the individual files. Checking the MD5 values is a pain but sometimes reveals a bad download.
nmyshkin said:
Don't give up. If you're using a Windows machine to prepare the card then whether the .IMG is displayed or not depends on your settings. It does not show on mine but a look at the file properties shows it is an .IMG file.
So that's the wrong tree. SDCards have been known to be problematic so if you have another around you might want to give it a try. You also might do a slow (complete) format on it before preparing it from scratch.
The other thing, of course, is the integrity of the individual files. Checking the MD5 values is a pain but sometimes reveals a bad download.
Click to expand...
Click to collapse
I have tried everything. It doesn't seem to work. I'm also sure there aren't issues with downloading because I have redownloaded the files over 7 times. Is there a way I can download the folder of files that you used to install cyanogenmod?
BornReady_ said:
I have tried everything. It doesn't seem to work. I'm also sure there aren't issues with downloading because I have redownloaded the files over 7 times. Is there a way I can download the folder of files that you used to install cyanogenmod?
Click to expand...
Click to collapse
I've already shut down my computer for the night. I'll have a look at the size that an image of the card would be. Maybe that's the easiest way if there's room in my dropbox. If you've read through the CM11/12 thread you know I ran into problems and if you were to look at the CM10 thread you'd find me floundering around there also, so I know how frustrating it can be. And then suddenly it just works.
I'll let you know tomorrow.
BornReady_ said:
I have seen everyone else's folders and they seem to include "flashing_boot.img" However, the file I downloaded from your page only has "flashing_boot" When I try to rename the file, the Nook Tablet won't even turn on anymore at all. Matter of fact, I can't even get to the Boot Menu now, it keeps having that red line that states, "booti: bad boot image magic (in memory)" I'm losing hope...
Click to expand...
Click to collapse
As @nmyshkin pointed out, it's most likely because your Windows Explorer is configured not to display the file-name extension, so when you try to rename "flashing_boot" to "flashing_boot.img" you in effect end up with a file with name "flashing_boot.img.img".
This is likely also the root cause of your original problem: if you now just rename the TWRP recovery file you had downloaded (which already has the hidden .img extension) to "recovery" (and not "recovery.img" lest you end up with a file named "recovery.img.img") then CyanoBoot will see the recovery file.
For avoidance of doubt, just set your Windows Explorer to display file-name extension.
digixmax said:
As @nmyshkin pointed out, it's most likely because your Windows Explorer is configured not to display the file-name extension, so when you try to rename "flashing_boot" to "flashing_boot.img" you in effect end up with a file with name "flashing_boot.img.img".
This is likely also the root cause of your original problem: if you now just rename the TWRP recovery file you had downloaded (which already has the hidden .img extension) to "recovery" (and not "recovery.img" lest you end up with a file named "recovery.img.img") then CyanoBoot will see the recovery file.
For avoidance of doubt, just set your Windows Explorer to display file-name extension.
Click to expand...
Click to collapse
You are totally correct. I enabled Windows Explorer to display file-name extension and the TWRP recovery file turned out as "recovery.img.img" I am going to try it out now and reply with if it works or not.
Alright, I have been trying and following the instructions clearly, but it keeps giving me the red line stating, "booti: bad boot image magic (in memory)" now. I have gotten to the Boot Menu before, but now it won't even let me get there. What does this message mean?
BornReady_ said:
Alright, I have been trying and following the instructions clearly, but it keeps giving me the red line stating, "booti: bad boot image magic (in memory)" now. I have gotten to the Boot Menu before, but now it won't even let me get there. What does this message mean?
Click to expand...
Click to collapse
Is flashing_boot file on your SD card correctly named "flashing_boot.img", and not "flashing_boot.img.img"?
Hello,
I've purchased this one: http://www.dx.com/p/x96-tv-box-andr...-2gb-ram-16gb-rom-us-plug-449347#.WPuxONryuUk
Just wondering what ROMs and recoveries work. I've searched a bunch and found some dead links and conflicting information so I'm hesitant to flash it especially where I do not have a stock image to go back to if it renders it bricked.
If anyone can help out, it would be much appreciated.
Thank you,
Scott
Note: Keeping a repository here as I find more information about this box: https://drive.google.com/open?id=0Bzj6JjnAJZjjczVIbFlHS3VUWlU
Working on it
Custom TWRP and stripped down/modded firmware is on the way.
I hope we can get a pure Android Rom working on it
Again: Working on it
Fully unbranded and hopefully with unlocked custom bootanimation (Original Google would be my prefered option over Mbox).
Give me a bit of time and you will find flashable ZIP soon
All done
Another question about the box: is-it possible to have Android TV instead of a modded android marshmallow? Because the interface would be a lot easier to use.
Android TV is a complete different story and you can't really compare the two like this.
Android TV uses the Leanback launcher if I am not mistaken.
Already tried to include it into a testrom but so far no real luck as it uses a lot more binaries that are not included in the standard system.
Will have to create some symlinks, add binaries and do a lot of testing - not to mention finding all the included apps for android TV and figuring out how to make them work.
If the interface is your only trouble check some nice launchers first, like Apex for example.
Once I have something cooked up that actually works as expected you will find it in this section somewhere
Also interesting to test that , as mine is not even root ^^
Rom
Any news about the firmware for this device?
Nope, still no updates coming from the chinamen, seems they already abandoned firmware updates and moved on to different devices.
See this thread (beta 6 I used for.mine)
https://forum.xda-developers.com/an...gic/rom-x96-2-16gb-root-supersu-twrp-t3596525
I join the thread because because of a storm my X96 looks brick. I've been looking everywhere but I do not find the guide for unbrick. I wanted to save it not to throw it but I do not know where to download the firmware how to do unbrick. I know I'm in the wrong thread but I did not want to open it a lot like this and make it confusing. Thank you all
As long as you get into the TWRP recovery on the SD card all should be fine - assuming the box is a X96.
If that fails only the burn tool or burn card maker can help with a genuine firmware to get going again.
Hi guys sorry to bump an old thread. I'm still trying to find the TWRP zip for these so I can do a complete back up and then paste on other boxes.
Have an X96 Amlogic S905X Quad Core 2G/16G Android 6.0 Wifi HD 4K TV Box.
I flashed the FULLY UNBRANDED Kodi 17, everything looked fine but the box's red light just stays on after the reboot.
Does not go into TWRP at all or nothing on screen.
It now a paperweight?
Downloaded the Stock firmware (Android 6.0.1 X96 Amlogic S905x 20161122) and am trying to start box with a bootable SD-card.
BurnCardMaker asks for an IMG file with all the relevant (aml_autoscript, factory_update_param.aml, firmware.zip, recovery.img, u-boot.bin, etc) files in but i cannot find this IMG file.
Without these BurnCardMaker does not work at all or nothing happens on TV box at least.
Must also say, i use a 64gig SD card but it worked for the initial flash.
Am i wasting my time with this box now?
Thanks for help.
(I posted this on the Android Mods Thread on accedent)I have a LG Nexus 5 HammerHead and tried to flash the newest Kali NetHunter using TWRP 3.5.2. After I flashed the ROM successfully, I have notice that the phone itself says no wifi networks found when swipe down to look at the wifi connections. I go to the wifi settings it says "Searching for wifi networks" with a spinning wheel of death(the loading icon). I've tried configuring it to use 2.4 Mhrz and didn't work, set it up to where it would only find good connections and still didn't work, I even did a factory reset and actually made it worse. I even reflashed it and see if that fixed it, nope. I connected it to the internet using a Ethernet adapter that is made for phones using a micro USB connection, updated the apps, updated and upgraded Kali NetHunter itself in the terminal and wifi connections is still not finding any connections at all. Could It be that Kali NetHunter doesn't support the internal wifi card that is built into my phone, could it be that twrp is having some errors on their end, or is it a bug that Offensive Security is not aware about? Please Help?
This may happen cos of wi-fi firmware. These files are called fw_bcmdhd.bin and fw_bcmdhd_apsta.bin. There are two versions of firmware:
1. https://github.com/LineageOS/androi...c531cd30abd21d93c5a04/bcmdhd/firmware/bcm4339
2. https://github.com/LineageOS/androi...5f8949fe77780d922c973/bcmdhd/firmware/bcm4339
You need to find where these files are stored in your rom, replace them with files from version 1 or version 2, restore permissions for these files if necessary and reboot your phone.
z3DD3r said:
This may happen cos of wi-fi firmware. These files are called fw_bcmdhd.bin and fw_bcmdhd_apsta.bin. There are two versions of firmware:
1. https://github.com/LineageOS/androi...c531cd30abd21d93c5a04/bcmdhd/firmware/bcm4339
2. https://github.com/LineageOS/androi...5f8949fe77780d922c973/bcmdhd/firmware/bcm4339
You need to find where these files are stored in your rom, replace them with files from version 1 or version 2, restore permissions for these files if necessary and reboot your phone.
Click to expand...
Click to collapse
Honestly, I have been trying to find these files and can't seem to find them. I even put the file name on the search bar of my windows 10 and it can't find them either. I think its just missing firmware on Offensive Security's end in this situation. I've had a troublesome experience with their kali linux products such as kali linux itself on having missing firmware after installation. Thank you for helping me out and hopefully these files should do the trick after I re-flash NetHunter with the firmware you have provided. As a matter of fact would the files belong in the firmware folder?
Martisabolt said:
Honestly, I have been trying to find these files and can't seem to find them. I even put the file name on the search bar of my windows 10 and it can't find them either. I think its just missing firmware on Offensive Security's end in this situation. I've had a troublesome experience with their kali linux products such as kali linux itself on having missing firmware after installation. Thank you for helping me out and hopefully these files should do the trick after I re-flash NetHunter with the firmware you have provided. As a matter of fact would the files belong in the firmware folder?
Click to expand...
Click to collapse
You will not find them in the search bar of your windows)
And no, firmware is not missed. Without wi-fi firmware you will be unable to enable Wi-Fi at all. In your case Wi-Fi can be enabled but you didn't see any networks.
Also /firmware - is incorrect place. It is a mount point of the /modem partition.
Wi-Fi firmware can be located at /system/firmware or /system/vendor/firmware/. Try to find them in TWRP. Boot into TWRP, mount System partition, open File Manager and review all the paths i've listed here. But i can't be sure cos i've never used Kali NetHunter.
z3DD3r said:
You will not find them in the search bar of your windows)
And no, firmware is not missed. Without wi-fi firmware you will be unable to enable Wi-Fi at all. In your case Wi-Fi can be enabled but you didn't see any networks.
Also /firmware - is incorrect place. It is a mount point of the /modem partition.
Wi-Fi firmware can be located at /system/firmware or /system/vendor/firmware/. Try to find them in TWRP. Boot into TWRP, mount System partition, open File Manager and review all the paths i've listed here. But i can't be sure cos i've never used Kali NetHunter.
Click to expand...
Click to collapse
Ok, I've been to those locations and in the system's folder, no firmware folder. However, in the sys folder, there is and does not show any firmware files in TWRP.
Give me the links to ROM files u flashed
This came directly from kali.org.
What was your base ROM before installing Kali? Stock Android 6.0.1?
yes
Well, Wi-Fi firmware in stock android 6.0.1 is located at /system/vendor/firmware/ folder. I've looked in the kali installer script and didn't find any scripts which can modify or delete this firmware. So we can try to install different firmwares into stock folders. I've attached 2 flashable zips for you. Try the -DHD version first. Flash it in TWRP and reboot your phone. If it doesn't help, then try -STOCK version.
It this will not help then i'm out of options
z3DD3r said:
Well, Wi-Fi firmware in stock android 6.0.1 is located at /system/vendor/firmware/ folder. I've looked in the kali installer script and didn't find any scripts which can modify or delete this firmware. So we can try to install different firmwares into stock folders. I've attached 2 flashable zips for you. Try the -DHD version first. Flash it in TWRP and reboot your phone. If it doesn't help, then try -STOCK version.
It this will not help then i'm out of options
Click to expand...
Click to collapse
Ok, I have tried both. Sadly I guess I'm out of luck and this is now nothing but a bricked phone in my hand. None of these files worked and actually made my phone crash when I tried to load the first file. I tried the second file as well and now I can't turn wifi on. I might as well have to build my own rom or junk this phone
Martisabolt said:
Ok, I have tried both. Sadly I guess I'm out of luck and this is now nothing but a bricked phone in my hand. None of these files worked and actually made my phone crash when I tried to load the first file. I tried the second file as well and now I can't turn wifi on. I might as well have to build my own rom or junk this phone
Click to expand...
Click to collapse
Don't hurry to kill your phone) Try to revert to complete stock 6.0.1 and re-lock bootloader by this instruction:
[TUTORIAL] How to flash a factory image | Return to stock | Unroot/SAVE your Nexus 5
How to flash a factory image | Return to stock | Unroot your Nexus 5 Hello Nexus 5 Users! I see many users that don't know how to restore their Nexus 5 to stock. It may come in handy, either when you want to RMA your phone, or you want to...
forum.xda-developers.com
And if your wi-fi will not work then yes, something bad happened with hardware
z3DD3r said:
Don't hurry to kill your phone
Click to expand...
Click to collapse
I tried both packages and thery didn't break my ROM. Unhappily they did not help.
I use the Re4son Kernel and can set wlan0 to monitor mode. But airodump is blind then.
@r.mutt @Martisabolt
Hammerhead kernel source (Marshmallow)
These are the complete Nexmon files seperately arranged.
Either you use a proper file manager with root permission, or just use the TWRP fiile manager and insert/copy them into the according sections.Maybe set the correct permission, while you're there and of course know your stuff. :>
Martisabolt said:
Ok, I have tried both. Sadly I guess I'm out of luck and this is now nothing but a bricked phone in my hand. None of these files worked and actually made my phone crash when I tried to load the first file. I tried the second file as well and now I can't turn wifi on. I might as well have to build my own rom or junk this phone
Click to expand...
Click to collapse
Hi Mate, Sorry for the delayed reply. Now i can afford nexus 5. Faced same issue as you. Thanks @z3DD3r for the hint.
Follow below instruction If you want wifi.
*Boot to Twrp
*locate /advanced/filemanager/vendor/firmware
You are there
(Note: 100% you can't see the files as discussed in above thread. But those are hidden(while installing nexmon from nethunter store i have seen those already exists in same folder))
*At bottom you see permisson blue box
*Click the same-select chmod 755-swipe to confirm
Now reboot to system. Here you go.