Related
Hello,
After rooting my Tattoo, I installed ROM manager and flashed the clockworkMod Recovery 3.0.0.6 (for tattoo/click).
When I install the rom cyanogenmod 7 RC1 or RC2 (I try CM7 nightlybuild 19 as well) via clockworkmod, he said that the rom is successfully installed but when I launch the ROM, the ROM stucked on the tattoo boot screen (not on the CM7 boot screen, I never saw the CM7 boot screen).
Any idea to resolve my problem?
Thanks
Stuck for how long? About 2 minutes it is ok and then the CM boot logo come up.
First boot takes a long time.
Did you wipe your device before flashing CM ROM? If not do so in recovery menu. (wipe all, factory setting, clear cache etc...)
Same here. At first when i got boot screen, i thought i blew it, but it took few minutes to urn up...
it happened twice to me. Wipe cache at first ... if it doesn't boot, wipe all.
Good luck!
I wipe all before every flash.
I flash the rom "update-cm-7.0.0-RC2-click-signed.zip" and after the gapps "gapps-gb-20110307-signed.zip".
On my screen, I saw only "TATTOO". , I waited during 10 minutes...
charlesdg said:
I wipe all before every flash.
I flash the rom "update-cm-7.0.0-RC2-click-signed.zip" and after the gapps "gapps-gb-20110307-signed.zip".
On my screen, I saw only "TATTOO". , I waited during 10 minutes...
Click to expand...
Click to collapse
try other rom file. and don't install gap yet. I had been there too.
I tried the rom "FroYo AOSP(2.2.2_r1) for Tattoo v0.3 released" and it works!
How can I install cyanogenmod 7? which rom can I use from cyanogenmod 7?
I tried repeating installation 6 times then it worked. I think install isn't clean. try again.
with which rom?
Try latest cyanogen rom rc - and here you will find all the info.
It's really great, try it.
charlesdg said:
I wipe all before every flash.
I flash the rom "update-cm-7.0.0-RC2-click-signed.zip" and after the gapps "gapps-gb-20110307-signed.zip".
On my screen, I saw only "TATTOO". , I waited during 10 minutes...
Click to expand...
Click to collapse
I have the same problem. Today I've tried the RC3 without being able to boot it, stuck at Tattoo logo. Doing a logcat I see many "DEBUG" row. The previous nightly build 31 boot correctly but after a while hang and sometime the system reboot itself. The nFinityGB 0.92 and previous, despite being CyanogenMod based, runs correctly. I've not been able to figure why I have so many problem with a rom that for most people is rock solid.
Please let me know if nFinityGB rom works correctly.
Have had success booting RC2.2 & RC3
I have had no problems flashing or booting Cyanogen 7 RC2.2 and RC3, using Rom Manager from Android market.
The problem seems to be solved in RC3, but the default cpu speed is too high to boot without getting some instability. At the third try I've been able to get into cpu settings to lower the maximum speed to 615 MHz. Now it works without stabilty issues.
Hey guys someone please help me out...even im stuck with the same problem....
Boot LOOPs continuously... i dont find any solution to this... phone isnt working atol and if i want to get back to the stock rom it says "USB CCONNECTION ERROR" so im really in a bad situation here....
guess have to travel to college without music (
I try the CM7 RC4 and the rom is bootlooping when I launch it! :-s
I went back on the CM6 :-(
charlesdg said:
I try the CM7 RC4 and the rom is bootlooping when I launch it! :-s
I went back on the CM6 :-(
Click to expand...
Click to collapse
If you feel dare, you can use this little init script that i've created for personal use. It sets a maximum cpu frequency of 528MHz in the early boot phase, allowing the phone to be stable. Once the phone booted, you can change the cpu speed using the CM Settings menu.
To place it in the correct directory, you must use adb.
- Just download it somewhere in your computer
- rename it removing the .txt extension (the resulting name will be 02slowdown)
- normally flash the CyanogenMod rom and do not reboot
- connect the usb cable between the phone and the computer
- mount the /system partition using the Clockwork storage and mounts menu
- copy the script in the /system partition with the command
Code:
adb push 02slowdown /system/etc/init.d/
- change the script owner with
Code:
adb shell chown root:shell /system/etc/init.d/02slowdown
- change the permissions with
Code:
adb shell chmod 750 /system/etc/init.d/02slowdown
- reboot and cross your finger
Now the phone should boot regularly without getting nasty FC
Hope this will help someone.
There is another way to apply this workaround: you can open the zipped rom with 7zip or something like that and put the "02slowdown" script in the /system/etc/init.d subdirectory of the archive. I used this method to flash the cm7 stable version.
my first reboot took a bit longer too. I just waited and voilá. Droid skater and CM7 installed.
lupp0l0 said:
If you feel dare, you can use this little init script that i've created for personal use. It sets a maximum cpu frequency of 528MHz in the early boot phase, allowing the phone to be stable. Once the phone booted, you can change the cpu speed using the CM Settings menu.
To place it in the correct directory, you must use adb.
- Just download it somewhere in your computer
- rename it removing the .txt extension (the resulting name will be 02slowdown)
- normally flash the CyanogenMod rom and do not reboot
- connect the usb cable between the phone and the computer
- mount the /system partition using the Clockwork storage and mounts menu
- copy the script in the /system partition with the command
Code:
adb push 02slowdown /system/etc/init.d/
- change the script owner with
Code:
adb shell chown root:shell /system/etc/init.d/02slowdown
- change the permissions with
Code:
adb shell chmod 750 /system/etc/init.d/02slowdown
- reboot and cross your finger
Now the phone should boot regularly without getting nasty FC
Hope this will help someone.
Click to expand...
Click to collapse
Thanks man! It works for the rom CM7 stable mod
charlesdg said:
Thanks man! It works for the rom CM7 stable mod
Click to expand...
Click to collapse
I'm glad to be useful!
There is another way to apply this workaround: you can open the zipped rom with 7zip or something like that and put the "02slowdown" script in the system/etc/init.d subdirectory of the archive. I used this method to flash the cm7 stable version.
Sent from my HTC click using XDA App
lupp0l0 said:
I'm glad to be useful!
There is another way to apply this workaround: you can open the zipped rom with 7zip or something like that and put the "02slowdown" script in the system/etc/init.d subdirectory of the archive. I used this method to flash the cm7 stable version.
Sent from my HTC click using XDA App
Click to expand...
Click to collapse
If I don't, every times I launch cm7, I have to do the manipulation (with adb) explain above?
Hello, I am new to the community and although I have flashed loads of roms to various devices this is the first I have tried to build from source.
As it says in the title I am trying to build for my Oppo find 5 which there is a nightly build for, I wanted to try and build from source though.
I have set up the build environment as described on the omni website.
I have followed a set of instructions but when I come to build using
Code:
brunch find5
i dont get a zip in the out folder. I do get the following notes though in the terminal after the build.
Note: Some input files use or override a deprecated API.
Note: Recompile with -Xlint:deprecation for details.
Note: Some input files use unchecked or unsafe operations.
Note: Recompile with -Xlint:unchecked for details.
Note: Some input files use or override a deprecated API.
Note: Recompile with -Xlint:deprecation for details.
Note: Some input files use unchecked or unsafe operations.
Note: Recompile with -Xlint:unchecked for details.
Click to expand...
Click to collapse
Those errors are meaningless. Post the full log as an attachment please.
Although I'd suggest reading through the errors first - the first skill anyone needs in Android development is the ability to look through a log and analyze what is what.
At the very least you might've forgotten envsetup. You probably forgot to pull blobs with extract-files (or finding them through some other source...) too - nearly everyone does.
Hello Entropy,
I have an issue too when building find5 KK. In fact no really building as i manage to get the homemade zip file, manage to flash it, it boots ok, everything is working except that my radio is not recognised so no IMEI and no mobile network, wifi is ok. Here is a link to my own build witch has exactly the same size in KB that the official nightly. Strange stuff is that if i flash the official nightly over my build then no issue, and the radio is recognised.
Blobs are coming from donkey github
I tried to flash from aokp 4.3 build, then also from Color OS, same result.
Flashed maxwen radios 4.1 and 4.2 over my build same issue
I'm building from virtual box ubuntu 12.04, JDK 1.6 update 45, on a Mac.
The only thing i see that may be wrong is that at the end of each build before the package is delivered i see no radio.img found, skipping install, but i've read that it was coming without radio.
Tried to add a line in the build.prop to disable selinux "ro.boot.selinux=disabled" i did not help.
I use maxwen TWRP patched recovery, but also tried with last cwm recovery and same result.
With the same build environment i manage to build I9300 omni kitkat without issue.
Any idea what could be wrong?
Many thanks in advance, and also thanks for the great job you all with Omni:good:
jejecule said:
Hello Entropy,
I have an issue too when building find5 KK. In fact no really building as i manage to get the homemade zip file, manage to flash it, it boots ok, everything is working except that my radio is not recognised so no IMEI and no mobile network, wifi is ok. Here is a link to my own build witch has exactly the same size in KB that the official nightly. Strange stuff is that if i flash the official nightly over my build then no issue, and the radio is recognised.
Blobs are coming from donkey github
I tried to flash from aokp 4.3 build, then also from Color OS, same result.
Flashed maxwen radios 4.1 and 4.2 over my build same issue
I'm building from virtual box ubuntu 12.04, JDK 1.6 update 45, on a Mac.
The only thing i see that may be wrong is that at the end of each build before the package is delivered i see no radio.img found, skipping install, but i've read that it was coming without radio.
Tried to add a line in the build.prop to disable selinux "ro.boot.selinux=disabled" i did not help.
I use maxwen TWRP patched recovery, but also tried with last cwm recovery and same result.
With the same build environment i manage to build I9300 omni kitkat without issue.
Any idea what could be wrong?
Many thanks in advance, and also thanks for the great job you all with Omni:good:
Click to expand...
Click to collapse
hm - that actually sounds strange
sounds like wrong blobs - are you are really using the ones
from donkeycojote
maxwen said:
hm - that actually sounds strange
sounds like wrong blobs - are you are really using the ones
from donkeycojote
Click to expand...
Click to collapse
yes i'm sure. i was first using the one from themuppets github, then Guillaume advised me to use the coyote ones. Size of the find5 vendor folder is 40,1MB, 132 files. Strangely i had this issues with my last 5 builds, but with the today one, problem disappeared and now my baseband is recognised and everything ok, though i still have this no radio.img message at the end of the build.
Really strange indeed i hate not to know what was the issue Anyway i will build again tomorrow and let you know, Chasmodo from Asylum team is also helping me a lot in understanding some stuffs as i'm a new and noob in building
One question about blobs: when i try to extract it from my device, it works when i run an 4.3 aokp build but then i get error in building. If i try to extract blobs from omni 4.4 (official nightly) i get some access denied on some blobs and then also some errors in the build. No issue with coyote ones though.
Many thanks for your time mate!
So guys, my problem with find5 modem seems to be fixed, no issue with today build neither. But.....now facing exactly the same issue with jftlexx(i9505)...
Build went OK, blobs from coyote, flash and boot OK....but no modem again, I may be do wrong stuff when flashing or missing something.
Before flashing I always do factory reset + wipe system, then flash build, gapps(pa ones mostly) + supersu.
Same repo, same vendor, I9300 OK but manually added local manifest as in your tuto.
Rebuilding atm
Thanks a lot
Sent from my Find 5 using xda app-developers app
Hey guys, a new version of Phoenix OS (v2.0.7) is out and I have created rooted images for you guys to use.
Instructions:
Download the correct system rooted.7z file provided in the Download section and extract it
Install Phoenix OS and restart your computer.
Boot into Phoenix OS and finish the system initialization wizard. Restart the computer and boot into your main OS.
Go to C:\Phoenix OS (or wherever your Phoenix OS installation is) and replace the system.img file that's already there with the one you just downloaded
Reboot your computer now and boot into Phoenix OS.
Install the latest version of SuperSU. Sign in to Play Store using your Google account and update SuperSU that way. If you for some reason cannot use the Play Store, you can find SuperSU on the official thread. Download the flashable zip, extract Superuser.apk from the common folder, and install it in Phoenix OS by opening the .apk file with the default file manager that comes with the OS.
Update the binary by choosing Normal and your Phoenix OS should now be fully rooted
Download:
Phoenix OS x86 v2.0.7 (13 June) Rooted Image + original system.img + PhoenixOSInstaller_v2.0.7.151.32bit.exe
https://drive.google.com/drive/folders/0B_UTWXKFnZoNVGpBZmxQS0dhRjg
Phoenix OS x64 v2.0.7 (13 June) Rooted Image + original system.img + PhoenixOSInstaller_v2.0.7.150.64bit.exe
https://drive.google.com/drive/folders/0B_UTWXKFnZoNclN5SGdFUGlTRGs
Download Phoenix OS v2.0.7 here (original thread):
http://bbs.phoenixstudio.org/en/showthread.php?tid=6186
History:
Uploaded v2.0.7 system images
Oooh... now I can test this to see if it fixes my G+ compatibility issue
The Wrath of Kahn said:
Oooh... now I can test this to see if it fixes my G+ compatibility issue
Click to expand...
Click to collapse
Sure! Let us know if it works out well for you
meanhacker said:
Sure! Let us know if it works out well for you
Click to expand...
Click to collapse
Sadly, no. It is rooted successfully and everything else seems fine, but "device not compatible" again. Unfortunately this is a deal killer for me =/
The Wrath of Kahn said:
Sadly, no. It is rooted successfully and everything else seems fine, but "device not compatible" again. Unfortunately this is a deal killer for me =/
Click to expand...
Click to collapse
Did you try both, the 32 and 64 bit versions? I will try it on my Surface Pro 3 sometime and will let you know my results. Meanwhile, you can post it on their official forum and let them know that G+ isn't working
meanhacker said:
Did you try both, the 32 and 64 bit versions? I will try it on my Surface Pro 3 sometime and will let you know my results. Meanwhile, you can post it on their official forum and let them know that G+ isn't working
Click to expand...
Click to collapse
Only tried 64 bit... guess I could give 32 bit a shot. Tomorrow then...
The Wrath of Kahn said:
Only tried 64 bit... guess I could give 32 bit a shot. Tomorrow then...
Click to expand...
Click to collapse
I tried opening G+ on the v2.0.6 and got the same error as you. Perhaps you can use the browser to browse G+ for now until a solution is available? Also, look into spoofing your deice model into a model of an actual tablet. Maybe that will work if you edit the build.prop file.
If anyone get's "grub minimal bash like line editing issue" when trying to boot
Hi I just tried phoenix OS. yesterday on my unbranded baytrail tablet (ub15ms10) I was stuck with this issue for a while and I finally came up with the fix using the grub prompt! (I used "rufus" to create the boot usb drive)
First, list your drives with ls ls Mine came up with hd0 and some others, but since I was booting from a usb drive, that's all that matters at the moment. hd0 will be the drive that you need so set it as the target and below is basically what you need to type to try it out without installing.
set root=(hd0,1)
linux /kernel root=/dev/ram0
initrd /initrd.img
boot
You should then be able to boot Pheonix OS 2.0.7 32bit. I did not try the 64bit version since there's no point because tablet has less then 4GB of RAM. What works: It makes good use of the tablet's GPU, it didn't lag in anyway for games such as clash royal. Browsing is good, playstore works..The performance is nice, It runs well on a 2GB ram tablet with a 1.3Ghz Intel Atom Z3735F. GPS works, bluetooth works.
What doesn't work: No audio, no brightness control. I didn't bother testing anything else since I lost interest as soon as audio didn't work. I'd probably be able to fix it myself by messing around with the kernel parameters but it's a PITA.
meanhacker said:
I tried opening G+ on the v2.0.6 and got the same error as you. Perhaps you can use the browser to browse G+ for now until a solution is available? Also, look into spoofing your deice model into a model of an actual tablet. Maybe that will work if you edit the build.prop file.
Click to expand...
Click to collapse
I tried editing the build.prop before with no luck, but I'm not experienced in doing it so I may have missed the fields that I needed.
irex102 said:
Hi I just tried phoenix OS. yesterday on my unbranded baytrail tablet (ub15ms10) I was stuck with this issue for a while and I finally came up with the fix using the grub prompt! (I used "rufus" to create the boot usb drive)
First, list your drives with ls ls Mine came up with hd0 and some others, but since I was booting from a usb drive, that's all that matters at the moment. hd0 will be the drive that you need so set it as the target and below is basically what you need to type to try it out without installing.
set root=(hd0,1)
linux /kernel root=/dev/ram0
initrd /initrd.img
boot
You should then be able to boot Pheonix OS 2.0.7 32bit. I did not try the 64bit version since there's no point because tablet has less then 4GB of RAM. What works: It makes good use of the tablet's GPU, it didn't lag in anyway for games such as clash royal. Browsing is good, playstore works..The performance is nice, It runs well on a 2GB ram tablet with a 1.3Ghz Intel Atom Z3735F. GPS works, bluetooth works.
What doesn't work: No audio, no brightness control. I didn't bother testing anything else since I lost interest as soon as audio didn't work. I'd probably be able to fix it myself by messing around with the kernel parameters but it's a PITA.
Click to expand...
Click to collapse
For the audio and other issues for baytrail/cherrytrail devices, someone made a kernel that apparently fixes these issues in debian/ubuntu which can be found here: https://yadi.sk/d/pW1Fbl-VyVPoR/Linux 4.12/Linux 4.12rc5. If someone else could use these kernels sources to apply a patch for android x86 that would be awesome.
irex102 said:
For the audio and other issues for baytrail/cherrytrail devices, someone made a kernel that apparently fixes these issues in debian/ubuntu which can be found here: https://yadi.sk/d/pW1Fbl-VyVPoR/Linux 4.12/Linux 4.12rc5. If someone else could use these kernels sources to apply a patch for android x86 that would be awesome.
Click to expand...
Click to collapse
Hey I found some readied kernels that fixes all the issues on baytrail tablets for android x86 7.1: https://drive.google.com/drive/folders/0B1HDhURlGNctY045UWFhalo5MW8 All that's left is to patch a rom for these devices. More info found here: https://github.com/burzumishi/linux-baytrail-flexx10/issues/12#issuecomment-309275211
#Quest
i'm already install phoenix os latest version, can i replace old system.img with system.img rooted without uninstall my latest phoenix os already installed on my pc?
Nicojoy said:
i'm already install phoenix os latest version, can i replace old system.img with system.img rooted without uninstall my latest phoenix os already installed on my pc?
Click to expand...
Click to collapse
What version of Phoenix OS do you have installed? If you have v2.0.7, you're in the right thread, so go ahead and download either a 32 or 64-bit version of the rooted image and replace it with your current system.img.
This will work on a Nexus 9 or it only works in pc's?
when i update su binary like you say it says to me installation failed
edit: ifound soulition its to update super su to the latest version with play store or aptoide or arc market or app vn and the install the binary data its soooo easyyyyyyy
Waiting for rooted system.img for Phoenix OS 2.1.0
SU Binary busy?
So I followed the instructions (although the step 6 is kind of confusing, English is not my native language so...) booted with the rooted sys image, installed superSU from the Play Store and when I open it it says "SU binary busy" and send me to a FAQ where it says that
"The SU files are already occupied by other software, such as Kingroot."
So I need to install the binary somehow? or something went wrong?
Oh BTW, used Root checker and it says it's not propely installed
Thanks for the image, buddy
MrSlenderman said:
"The SU files are already occupied by other software, such as Kingroot."
Click to expand...
Click to collapse
I also ran into this problem using the newest version from the play store, I could avoid this though by installing version 2.79 through an apk.
But now it won't let me update the binary, since everytime I select "Normal" the installation fails after a minute or so.
Any ideas?
Guys, when to expect a rooted image for V 2.1.0 x86
thank you, but i bit confused about when i update the os,
so when i update the os, the rooted image will gone ? and i need to wait for another rooted image ?
Coconut Kernel for LineageOS 15.1 - With Nethunter Support
Code:
***I'm not responsible for any problems that might occur flashing this kernel or what you do with the kernel support***
This kernel is only for Lineage-OS 15.1 or ROMs based on it
Since I did not find a kernel for LOS Oreo with USB Wifi drivers, compiled one.
This kernel has been built from the LOS 15.1 source on git with changes adapted for standalone compiling. So i don't know if any ROM feature is broken though i believe stock features should work.
Yes, it supports monitor mode and packet injection.
Drivedroid is also supported by default in the kernel.
How to use USB Wifi Adapters?
Download from attachment and flash the kernel in twrp
Reboot (First boot will be a bit slow)
Plugin the adapter
MAKE SURE THAT USB OTG IS ENABLED IN SETTINGS FOR ANY OTHER LINEAGEOS BASED ROM
Test by issuing the command ifconfig wlan1 up
It's also important to be on latest 5.0.8 firmware (not rom) for this to work.
Troubleshooting
If the above steps don't work for you,
1. Clean install latest oxygen os 5.0.8 from stock recovery by side loading ( this will install latest firmware which is required)
2. Do system, dalvik, cache, data wipe(firmware will be still there)
3. Flash any lineage15.1 based rom or LOS itself and gapps
4. Flash and enable root
5. Flash coconut kernel
6. Install and open terminal and type ifconfig wlan1 up as root to test after plugging in usb card
This is the failsafe method
You can use the usb adapters in any chroot environment(eg LinuxDeploy) - not just nethunter.
To mods - i created a separated thread for people to not flash incorrect zip. if its against the rules, i can merge it.
Source
https://github.com/LineageOS/android_kernel_oneplus_msm8996
Been looking for this for ages, gonna test now
Hey can you add the driver for the Atheros AR9271 Chipset?
hairyfred said:
Hey can you add the driver for the Atheros AR9271 Chipset?
Click to expand...
Click to collapse
It's added and tested working. Does it not work for you?
fredrickz said:
It's added and tested working. Does it not work for you?
Click to expand...
Click to collapse
None of the drivers seem to work, in about phone it says I'm using your kernel so I'm a bit confused
I tried manually moving the file from system/etc/firmware to system/lib/modules and to modprobe it but that doesn't work there either
it's probs a simple mistake I've made, I'm on omni rom 8.1
hairyfred said:
Hey can you add the driver for the Atheros AR9271 Chipset?
Click to expand...
Click to collapse
hairyfred said:
None of the drivers seem to work, in about phone it says I'm using your kernel so I'm a bit confused
I tried manually moving the file from system/etc/firmware to system/lib/modules and to modprobe it but that doesn't work there either
it's probs a simple mistake I've made, I'm on omni rom 8.1
Click to expand...
Click to collapse
I personally tested it on Lineage OS 15.1
I don't know about omnirom. My kernel has nothing to do with the folder /system/etc/firmware
See the screenshot.
There is no need to load the module as all drivers are built-in.
Post me an output of dmesg | grep htc
Reboot the phone, plugin your WiFi card, open terminal, type su, then type dmesg | grep htc
Also check if otg support is enabled in omnirom. Just plugin a USB flash drive on to the otg cable/adapter and see if the drive shows up. If yes, then otg is enabled, else you need to enable that.
I think otg maybe disabled by default in omnirom. Search otg in settings
fredrickz said:
I personally tested it on Lineage OS 15.1
I don't know about omnirom. My kernel has nothing to do with the folder /system/etc/firmware
See the screenshot.
There is no need to load the module as all drivers are built-in.
Post me an output of dmesg | grep htc
Reboot the phone, plugin your WiFi card, open terminal, type su, then type dmesg | grep htc
Also check if otg support is enabled in omnirom. Just plugin a USB flash drive on to the otg cable/adapter and see if the drive shows up. If yes, then otg is enabled, else you need to enable that.
Click to expand...
Click to collapse
I type it, no output, kernel might be incompatible with my rom :/ even though its lineage based
hairyfred said:
I type it, no output, kernel might be incompatible with my rom :/ even though its lineage based
Click to expand...
Click to collapse
Chk the otg settings. Plugin a flash drive and see if it gets detected also type otg in settings and see if theres an option to enable it.
If you enable otg, you should remove and insert the card and test
fredrickz said:
Chk the otg settings. Plugin a flash drive and see if it gets detected also type otg in settings and see if theres an option to enable it.
If you enable otg, you should remove and insert the card and test
Click to expand...
Click to collapse
OTG is detected , it can use usbs etc
Send me a link of the omnirom u use
fredrickz said:
Send me a link of the omnirom u use
Click to expand...
Click to collapse
http://dl.omnirom.org/oneplus3/ latest one
hairyfred said:
http://dl.omnirom.org/oneplus3/ latest one
Click to expand...
Click to collapse
Just downloaded and installed that.
Flashed the ROM after wiping data, system, cache
Flashed supersu
Didn't flash gapps as I was just testing.
Flashed my kernel
Rebooted
Downloaded termux
Typed su
Plugged in USB ath9271 tplink wn722n
Typed ifconfig wlan1 up
And it worked
Possible problems for you
You need to install the latest firmware and modem for OxygenOs 5.0.8 .the latest you can get
For that you can either flash full oxygen OS ROM from op3 recovery by side loading
OR
you could download and flash only the firmware and.modem collection.
I recommend you flash stock oxygen is 5.0.8 official from their website.
Then wipe system data cache and then flash omni ROM latest and gapps and SuperSU whatever
Then reboot and complete initial setup
Then reboot and flashy my kernel.
It will work.
Firmware and modem only for OnePlus 3 OOS 5.0.8 Latest
https://androidfilehost.com/?fid=11410963190603878417
Xda thread
https://forum.xda-developers.com/oneplus-3/how-to/op3-flashable-firmware-modem-zips-t3816066
fredrickz said:
Firmware and modem only for OnePlus 3 OOS 5.0.8 Latest
https://androidfilehost.com/?fid=11410963190603878417
Xda thread
https://forum.xda-developers.com/oneplus-3/how-to/op3-flashable-firmware-modem-zips-t3816066
Click to expand...
Click to collapse
HAVOC 2.2 is AOSP base, should i try on that? If No please add support for it, its a Highly customizable Rom an Top Liked, I want to test your kernel
Hayatzada said:
HAVOC 2.2 is AOSP base, should i try on that? If No please add support for it, its a Highly customizable Rom an Top Liked, I want to test your kernel
Click to expand...
Click to collapse
The kernel should work on that ROM but for all the specific features of that rom, i should build the kernel from the customized version of their source. If their source is updated with all rom features, and it's available in git, maybe i can try.
You can ask the rom devs regarding updated kernel source for their rom and if you find one let me know. I'll look into it.
fredrickz said:
The kernel should work on that ROM but for all the specific features of that rom, i should build the kernel from the customized version of their source. If their source is updated with all rom features, and it's available in git, maybe i can try.
You can ask the rom devs regarding updated kernel source for their rom and if you find one let me know. I'll look into it.
Click to expand...
Click to collapse
i installed magisk module Nethunter but can't see Nethunter Icon on Havoc 2.2. any idia what the problem would be?
Hayatzada said:
i installed magisk module Nethunter but can't see Nethunter Icon on Havoc 2.2. any idia what the problem would be?
Click to expand...
Click to collapse
I've compiled a kernel with USB WiFi drivers supporting monitor mode and packet injection for havoc 2.2 pie. You can try that too. I'll try to post it in a cpl of days. Im just testing the kernel for any stability issues. As if now its working fine and USB adapters are also working good.
I personally have used nethunter only by installing the nethuter apk or by flashing the zip file for the ROM version. If magisk module is giving problems, you can do any of the following
1. Download nethunter apk by searching online
2. Download armhf or arm64 full ROM zip from nethunter nightly website(both works on OP3)
3. Extract Kali image from the zip and place in root of internal storage.
4. Open nethunter app and install from sdcard
5. Install additional tools if required
OR
Simply omit nethunter and use another chroot app like Linux Deploy.
You can install and use all tools in Linux deploy the same way as net hunter like airgeddon, metasploit, Beef, airmon-ng, wifite, reaver etc
I think a new version of net hunter is on its way too..
fredrickz said:
I've compiled a kernel with USB WiFi drivers supporting monitor mode and packet injection for havoc 2.2 pie. You can try that too. I'll try to post it in a cpl of days. Im just testing the kernel for any stability issues. As if now its working fine and USB adapters are also working good.
I personally have used nethunter only by installing the nethuter apk or by flashing the zip file for the ROM version. If magisk module is giving problems, you can do any of the following
1. Download nethunter apk by searching online
2. Download armhf or arm64 full ROM zip from nethunter nightly website(both works on OP3)
3. Extract Kali image from the zip and place in root of internal storage.
4. Open nethunter app and install from sdcard
5. Install additional tools if required
OR
Simply omit nethunter and use another chroot app like Linux Deploy.
You can install and use all tools in Linux deploy the same way as net hunter like airgeddon, metasploit, Beef, airmon-ng, wifite, reaver etc
I think a new version of net hunter is on its way too..
Click to expand...
Click to collapse
Thanks a lot for your reply, installed nethunter apk and placed in root of internal storage after renaming but not detected by chroot(have successfully done it before in Nougat), i personally dislike Linux deploy method so waiting for resolving, i think its a Pie issue. By the way thanks again.
Hayatzada said:
Thanks a lot for your reply, installed nethunter apk and placed in root of internal storage after renaming but not detected by chroot(have successfully done it before in Nougat), i personally dislike Linux deploy method so waiting for resolving, i think its a Pie issue. By the way thanks again.
Click to expand...
Click to collapse
Try the download option in nethunter app. Renaming to correct file should get it detected in nethunter app
Regarding linuxdeploy, you can change the default repository to any other mirror and get blazing fast speed. Try the following
Install to a file or directory selecting kali-rolling
Use http://kali.download/kali as source instead of default http://http.kali.org/kali
Then select other configurations and install it
What was the filename you renamed the kali archive to?
fredrickz said:
Try the download option in nethunter app. Renaming to correct file should get it detected in nethunter app
Regarding linuxdeploy, you can change the default repository to any other mirror and get blazing fast speed. Try the following
Install to a file or directory selecting kali-rolling
Use http://kali.download/kali as source instead of default http://http.kali.org/kali
Then select other configurations and install it
What was the filename you renamed the kali archive to?
Click to expand...
Click to collapse
i successfully installed kali but nethunter terminal crashes when ever i open it.
UPDATE: I discontinued work for this tablet model, due to the lack of NEON support for the Nvidia Tegra 2 CPU used in this model. Any existing work I uploaded will remain online, but I won't be uploading anything new. I'm also considering selling my tablet to anyone interested.
I have become successful with getting postmarketOS to run on this tablet for the past 2 months, running mainline Linux (5.8.0 as of this writing). This allows us to use this tablet model for a little longer, without getting stuck on older Linux kernel versions.
postmarketOS is an experimental, touch-optimized and pre-configured Alpine Linux. It can be installed on smartphones and other devices.
About postmarketOS, from their homepage:
We are sick of not receiving updates shortly after buying new phones. Sick of the walled gardens deeply integrated into Android and iOS. That's why we are developing a sustainable, privacy and security focused free software mobile OS that is modeled after traditional Linux distributions. With privilege separation in mind. Let's keep our devices useful and safe until they physically break!
Click to expand...
Click to collapse
Wiki page for this tablet: https://wiki.postmarketos.org/wiki/Acer_Iconia_Tab_A500_(acer-picasso)
Most features should work, except for the camera and 3D acceleration. Wi-Fi and Bluetooth work only if the non-free firmware is chosen to be installed.
How to install:
Follow the installation guide at https://wiki.postmarketos.org/wiki/Installation_guide, where theses specifics have to be specified when requested (this device is now in upstream pmaports):
Vendor: acer
Device code-name: picasso
Install non-free Wi-Fi + Bluetooth firmware: y
Only the mainline kernel is available for installation now, as downstream kernels no longer successfully compile. The user interface may be freely selected, as long as it is not one that requires 3D acceleration. To use KDE Plasma 5, add these lines to /etc/security/pam_env.conf:
Code:
QT_IM_MODULE=qtvirtualkeyboard
QT_QUICK_BACKEND=software
LIBGL_ALWAYS_SOFTWARE=1
Next, run the following commands in succession, after each one finishes, assuming the working directory contains the pmbootstrap.py script:
Code:
> ./pmbootstrap.py build device-acer-picasso
> ./pmbootstrap.py build firmware-acer-picasso
> ./pmbootstrap.py build linux-postmarketos-grate
From here on out, the generated chroot can be either installed to the eMMC, or a microSD card that must be inserted at or before boot time (the latter method allows for dual-booting Android already installed to the eMMC, although it can be directly accessed from the Linux system). The boot partition always has to be flashed to the eMMC in fastboot mode, as it is not possible to boot directly off of a microSD card.
If installing to the eMMC, run
Code:
> ./pmbootstrap.py install
> ./pmbootstrap.py flasher flash_kernel --partition secboot
> ./pmbootstrap.py flasher flash_rootfs
(optional) > ./pmbootstrap.py flasher boot
If installing to a microSD card, run
Code:
> ./pmbootstrap.py install --sdcard [path to the device for installation]
> ./pmbootstrap.py flasher flash_kernel --partition secboot
Depending on what user interface was chosen earlier in the installation process, there may not be enough packages installed to get a fully-loaded GUI. Besides the built-in Wi-Fi, it is also possible to use a USB ethernet adapter, or connect to another computer with a micro-USB cable and get RNDIS access that enables using SSH to the tablet.
Using another distro in place of postmarketOS
Advanced: Using another distro in place of postmarketOS
It is possible, if using the microSD card method, to use a different distro instead of postmarketOS, for those who want more software OOTB. I use the Ubuntu MATE rootfs from https://ubuntu-mate.org/ports/raspberry-pi/ as my daily driver, but other distros may take more effort to get working. Glibc limitations no longer apply, as the kernel version is no longer stuck at 3.1.0 (unlike with my earlier attempts). Carefully follow the instructions listed below, or the resulting system will become unbootable:
Use losetup or GNOME Disks (Utility) to mount the image in read-write mode.
Run GParted with the loop image and the target microSD card as the arguments.
Copy only the larger rootfs partition to the microSD card. Resize as necessary to get it to fit on the target microSD card.
Make sure on the target microSD card the boot partition is named 'pmOS_boot' and the rootfs 'pmOS_root'. The initramfs is hard-coded to search for partitions with these names by default for microSD cards. The loop image is not needed after this point, and can be safely detached.
On the copied rootfs, edit /etc/fstab to reflect the partition layout. To get access to Wi-Fi and Bluetooth, copy the kernel modules and firmware from the pmOS rootfs on the host system to the microSD rootfs.
Let me know if something wasn't understood from my instructions, or more clarification is needed. The instructions here can be somewhat overwhelming for those who have less Linux experience, but at least we're not forced to stay on old distro versions anymore.
Premade Linux images
I finally have managed to create a premade image to make the installation process easier for other people, especially for those who don't want to go through the hassle of compiling software. Every image I make can be found at https://drive.google.com/drive/folders/1pMqaS5GaM6N9TAKlNGQZWCG8UTiRn4pK?usp=sharing.
For all images:
Kernel version: 5.15.0-rc4
Includes all compiled kernel modules from postmarketOS builds, plus nonfree firmware enabled.
The postmarketOS splash screen will appear, although the underlying OS differs based the image used.
Images available:
Ubuntu MATE 20.04.1 (ubuntu-mate-20.04.1-desktop-armhf+acer-picasso.img.xz) (size: 1.3 GiB):
Based on 'ubuntu-mate-20.04.1-desktop-armhf+raspi.img.xz', available from https://ubuntu-mate.org/ports/raspberry-pi/
Underlying OS is Ubuntu 20.04.1, which is supported for 5 years until April 2025. However, Ubuntu MATE officially has support only until April 2023.
Requires at least an 8 GB or greater size microSD card (the image is 5.6 GiB decompressed).
The setup screen will open upon the first successful boot, where a username and password have to be set.
Most extra packages for the Raspberry Pi family of computers have been removed, including the kernels.
The battery icon in MATE cannot be enabled graphically, as the preferences window has been patched to permanently hide such an option (as the Raspberry Pis lack native battery support); instead run the command
Code:
gsettings set org.mate.power-manager icon-policy 'always'
to manually enable it.
The PPA at https://launchpad.net/~grate-driver/+archive/ubuntu/ppa is pre-configured to be accessed. Most packages from this repository, including the opentegra driver, come preinstalled. They currently are enough to get 2D acceleration working, but not for 3D acceleration.
Except for what has been mentioned above, any packages shipped may have to be updated once an internet connection is established.
Arch Linux ARM (ArchLinuxARM-armv7-latest+acer-picasso.img.xz) (size: 576.6 MiB):
Based on 'ArchLinuxARM-armv7-latest.tar.gz', available from https://archlinuxarm.org/about/downloads
Rolling release distro often with the latest versions of most packages. More recent software can be acquired at a small expense of instability.
Requires at least an 2 GB or greater size microSD card (the image is 1.9 GiB decompressed). Larger size is recommended for installing more packages.
To login into system:
Login as the default user alarm with the password alarm.
The default root password is root.
Initially command-line only; contains no desktop environment installed.
Use any image writing program with these images. If such a program does not support XZ compression, the image needs to be extracted instead, and that has to be used.
I hope the images will proves useful to some people. Let me know if any issue pops up during usage of this image!
hey Worldblender,
I have flashed the premade file you shared to an sdcard but I'm unsure as to how to boot into it?
tehno said:
hey Worldblender,
I have flashed the premade file you shared to an sdcard but I'm unsure as to how to boot into it?
Click to expand...
Click to collapse
The instructions were written assuming that the user has already flashed the custom bootloader as described here: https://forum.xda-developers.com/iconia-a500/a500-2019-2020-t4039271. Sorry for not making this clear anywhere, but that custom bootloader, along with flashing the boot image found in the first partition named "pmOS_boot" to either boot or secboot using fastboot, should get you set up to boot the SD card image.
Hi Worldblender,
Nice to see you work on this legacy device.
I definitely don't want to use android or can use it anymore on this tablet.
Nice to see some linux flavor being ported to it.
I had a look a the dedicated page on postmarketos.
Can you confirm the only GUI availbale as for now is the one called "Weston" ?
Or is MATE also working (from the screenshot) ?
Weston seem very basic, MATE more friendly.
How about performance ?
I'm considering reusing it to display a grafana dashboard in firefox for instance, maybe more if performance isn't too bad.
Worldblender said:
The instructions were written assuming that the user has already flashed the custom bootloader as described here: https://forum.xda-developers.com/iconia-a500/a500-2019-2020-t4039271. Sorry for not making this clear anywhere, but that custom bootloader, along with flashing the boot image found in the first partition named "pmOS_boot" to either boot or secboot using fastboot, should get you set up to boot the SD card image.
Click to expand...
Click to collapse
Thank you Worldblender for your work in writing up instructions and compiling the image too.
However, I'm still a bit lost as to what to do with your Ubuntu Mate image.
I've gotten the TWRP bootloader installed onto my Acer A500 tablet, but whether I use Rufus to expand your image onto an SD card, or just copy the compressed image onto the SD card, the [ Install ] does not see any images inside of the drive. Am I supposed to decompress your image in Windows and use the 0.img and 1.img in place of the nvflash's boot.img and recovery.img?
While I can see the two partitions in Ubuntu, I'm equally lost as to what to do with them, and how to get it onto the tablet.
coluwyvurne said:
Thank you Worldblender for your work in writing up instructions and compiling the image too.
However, I'm still a bit lost as to what to do with your Ubuntu Mate image.
I've gotten the TWRP bootloader installed onto my Acer A500 tablet, but whether I use Rufus to expand your image onto an SD card, or just copy the compressed image onto the SD card, the [ Install ] does not see any images inside of the drive. Am I supposed to decompress your image in Windows and use the 0.img and 1.img in place of the nvflash's boot.img and recovery.img?
While I can see the two partitions in Ubuntu, I'm equally lost as to what to do with them, and how to get it onto the tablet.
Click to expand...
Click to collapse
Wait for me to give out an update to the image, as there likely has been a new kernel version released that I would like to have updated first.
TWRP will not be used at all for this installation process, as the image is too big to flash with fastboot. Just flash the image to a microSD card, as the boot image that will be flashed will automatically pick it up shortly after booting. The only thing that does have to be flashed is the boot.img, which can be found in the first partition, and you will be only using fastboot for this process, not anything else.
I released a new version of the premade Ubuntu MATE image just now, named 'ubuntu-mate-20.04.1-desktop-armhf+acer-picasso.img.xz'. The following changes have been made since the last image:
Kernel version upgraded to 5.10.1-rc1
Based on Ubuntu MATE 20.04.1
Everything that changed since the beta1 image
Other than these changes, there are no other differences that can be noticed right away.
Direct link: https://drive.google.com/file/d/1mr-7e29KJYeagJju0Yo1qUpT2YRb61AR/view?usp=sharing
Many thanks for your work. I've entered today this forum just curious about something new and found this!
Second life for this old machine!
For those with problems installing, I've flashed precompiled image using balenaEtcher into the sdcard.
Then, extracted .xz image, extracted .img, then extracted 0.img and copied boot file from there. After that, renamed the file to boot.img and flashed it with fastboot.
As I've the old modified skrillex bootloader, the command is fastboot flash secboot boot.img.
It boots and works well for now!
Worldblender said:
[*] Add the PPA at https://launchpad.net/~grate-driver/+archive/ubuntu/ppa to get access to updated video drivers. They currently are enough to get 2D acceleration working, but not for 3D acceleration.
Click to expand...
Click to collapse
@Worldblender
Hi, i apt updated after adding grate-driver ppa, it seems it broken xorg because X don't start anymore
Can you detail how to proceed ?
pheex79 said:
@Worldblender
Hi, i apt updated after adding grate-driver ppa, it seems it broken xorg because X don't start anymore
Can you detail how to proceed ?
Click to expand...
Click to collapse
Can you still switch to a virtual terminal with Ctrl-Alt-[F1-F7]? You will need a USB keyboard to do this. Then try, after logging in with your username and password:
Code:
systemctl stop lightdm
startx
If startx does not bring something up, could you try running journalctl, and show me any log entries relating to lightdm?
If that still fails, you can try (if ppa-purge is not installed, install that first)
Code:
ppa-purge ppa:grate-driver/ppa
@Worldblender
one binary missing but i think this error is present before adding ppa
"/sbin/prime-switch: 22: /usr/bin/gpu-manager: not found"
Xorg log:
Require OpenGL version 2.1 or later
modeset(0): Failed to initialize glamor at ScreenInit() time
pheex79 said:
@Worldblender
one binary missing but i think this error is present before adding ppa
"/sbin/prime-switch: 22: /usr/bin/gpu-manager: not found"
Xorg log:
Require OpenGL version 2.1 or later
modeset(0): Failed to initialize glamor at ScreenInit() time
Click to expand...
Click to collapse
I never received such an error, but the specific package you must install is xserver-xorg-video-opentegra. No other Nvidia driver is going to work.
Worldblender said:
I never received such an error, but the specific package you must install is xserver-xorg-video-opentegra. No other Nvidia driver is going to work.
Click to expand...
Click to collapse
It works ! Thank you
xserver-xorg-video-opentegra was not installed
when adding ppa grate i only did an "apt upgrade" cmd i thought all grate items were installed (a few are installed when upgrading apt)
Nice work thank you so much.
Is there any chance for Manjaro arm? Or is it limited to debian based distros?
Note that after following the instructions for installing the Ubuntu MATE image from @Worldblender from a starting point of just the stock image, I have Ubuntu MATE installed on the external SD card and no OS installed on the eMMC because it was wiped during the bootloader replacement. Reading back through the posts suggests this is by design.
@Worldblender, so I'm very new at rooting devices, and have a little experience with Ubuntu but feel pretty lost. Any chance you could hook me up with a step by step install of the Nov2 image (unless you've put together another new version) from a stock(not rooted or anything) A500? I apologize if I overlooked something.
Edit: I got it working after doing this thing called reading, I definitely overlooked some things after reading closer. For someone else that might find themselves in my shoes here's what I did.
I followed this link: https://forum.xda-developers.com/iconia-a500/a500-2019-2020-t4039271 to get the bootloader installed
and then followed @whylly 's instructions:
whylly said:
For those with problems installing, I've flashed precompiled image using balenaEtcher into the sdcard.
Then, extracted .xz image, extracted .img, then extracted 0.img and copied boot file from there. After that, renamed the file to boot.img and flashed it with fastboot.
As I've the old modified skrillex bootloader, the command is fastboot flash secboot boot.img.
Click to expand...
Click to collapse
Hi there ! I have an iconia a500, rooted with lightspeed 4.8. Can I install this and then make it switch to Khali linux ? My ultimate objective is to get Khali on this tablet. I've worked my way down from ver 2.5x linuxdeploy all the way down to 2.0 lol So I'm thinking maybe if I apply your OS it will update the Kernal from 4.0.3 to 5 yes ? (That's a big jump for linuxdeploy) then I can apt-get khalifull ? Am I off base would this work ? Unless you have an image already of course in which case pleaaaaaaaaaaaaaase I'll pay for the bloody thing if I have to I've been pulling my hair out for days. Tried frikkin everything.
Unless anybody has a better method of course in which case feel free to suggest. If I have to make the image from scratch so be it
EDIT: UGhhhhhh after days of troubleshooting, I got to linuxdeploy2.0-1.16 installed kali (the native one on the app not from the repository as that gives kernel too old once you get the install working). Managed to term in and tried to start lxde, failed because lxde doesn't exist (sigh) tried to apt-get... kernel too old. game over sigh
Unless someone has a workaround I don't think it's possible to get Khali on a500.
Sound work?