Related
I've had my A500 running fine for months rooted on a stock ROM. Yesterday I decided to install a different font with a font installer. My system is now stuck in a boot loop on the screen which displays "ANDROID". It turns out the font I installed ended in *.txt, not *.ttf, but it is indeed a valid font file. I know this because I had the same problem on another device and I was able to spot the problem before rebooting the other device.
The easiest way to fix this would be to simply mount the tablet memory on my computer, find the font, and change the file extension - but how do I do that? Is it possible without booting the device?
meztek said:
I've had my A500 running fine for months rooted on a stock ROM. Yesterday I decided to install a different font with a font installer. My system is now stuck in a boot loop on the screen which displays "ANDROID". It turns out the font I installed ended in *.txt, not *.ttf, but it is indeed a valid font file. I know this because I had the same problem on another device and I was able to spot the problem before rebooting the other device.
The easiest way to fix this would be to simply mount the tablet memory on my computer, find the font, and change the file extension - but how do I do that? Is it possible without booting the device?
Click to expand...
Click to collapse
If it boots far enough you should be able to access a terminal via adb. The adb service is started quite early during boot. Get the android sdk and try typing "adb shell". If it works you get a normal linux shell and then you can delete or rename the font using that.
I was looking at how close my Nexus 5 really is to my R1 HD, and besides the obvious Qualcomm MTK thing they are amazingly similar.
I took the official Hammerhead NetHunter 3.0 Marshmallow zip and put it on my external and card.
I then did a factory reset including dalvik and cache in TWRP.
Installed SuperSU and booted my phone. I then installed Busybox Pro and rebooted back into TWRP.
Once in TWRP I clicked install and chose my saved nethunter-hammerhead-marshmallow-3.0.zip
It will open the Aroma installer. On the first screen click everything except the RF Analyzer, MAKE SURE YOU HAVE THE OLDER VERSION OF SUPERSU CHECKED TO INSTALL AS WELL.
On the next screen click everything but custom boot screen and custom wallpaper.
Click next and be patient while it installs everything, extracts the chroot image, and verifies the extract. Took about 10-12min till it completed to 100%.
A funny side note.....when running this on My Nexus 5 it would always freeze between 90-93? and after about an hour of being frozen I would do a hard reboot. On a Nexus 6 I would install it on, same thing but if I didn't wait 90+min I couldn't later manually install chroot or any metapackages.
After install finishes reboot your phone. Once rebooted I opened up From Toolbox Pro and used Root Browser to open the Hammerhead install zip. Once opened I extracted bootanimation.zip from system/media and Hammerheadwallpaper from wallpaper.
Go to Boot Animations in Rom Toolbox Pro, choose local and you can either install bootanimation.zip as it is, or choose resize and change the framerate up to 40.
Then open wallpaper chooser from your desktop and choose Hammerheadwallpaper from your extracted folder.
Finally open the NetHunter app and click install chroot. Once it verifies it already is then choose install metapackage. I always choose the forensics package.
Once that is installed go ahead and reboot your newly modded phone with a working Kali Linux install on it.
So does this mean that other ROMs meant for the Nexus 5 could more or less function on the R1?
wh00p said:
So does this mean that other ROMs meant for the Nexus 5 could more or less function on the R1?
Click to expand...
Click to collapse
I'm not a kernel person and that's the only thing that didn't work, was Kali dirty kernel changing.
I honestly can't answer that but seems plausible to me if someone can figure out the kernel thing.
Sent from my BLU R1 HD using XDA Labs
wh00p said:
So does this mean that other ROMs meant for the Nexus 5 could more or less function on the R1?
Click to expand...
Click to collapse
this isnt a rom it's a linux system you flash ON TOP of the n5 stock rom, so no
This is incredible, thank you for sharing!
I had my hopes up at first, but now I'm getting skeptical. If a kernel port wouldn't work, how can this boot considering the differences between mediatek and Qualcomm?
Unless that just doesn't even matter at all, considering its like a virtual machine computer-inside-a-computer
jasonmerc said:
I had my hopes up at first, but now I'm getting skeptical. If a kernel port wouldn't work, how can this boot considering the differences between mediatek and Qualcomm?
Unless that just doesn't even matter at all, considering its like a virtual machine computer-inside-a-computer
Click to expand...
Click to collapse
There is a universal kernel option in setup. Like I said though it didn't flash the kernel to kalidirty kernel. Everything else worked though. With the views I'm sure someone else can verify they got it working as well.
blu kernel source, binaries available?
Are the blu kernel source, binaries available to try and create a custom ROM?
That's a nice option!
I was actually looking at https://www.pwnieexpress.com/products/pentesting-community-editions yesterday which may be another cool alternative to this one, to see if there was a way to build this for the Blu.
I don't think the Nexus 5 image will work out of the box but there are detailed instructions on how to build a custom rom too, maybe when the device-tree etc is working for CM we will be able to give it a try.
(also the lack of USB OTG will be very detrimental)
emc2cube said:
That's a nice option!
I was actually looking at https://www.pwnieexpress.com/products/pentesting-community-editions yesterday which may be another cool alternative to this one, to see if there was a way to build this for the Blu.
I don't think the Nexus 5 image will work out of the box but there are detailed instructions on how to build a custom rom too, maybe when the device-tree etc is working for CM we will be able to give it a try.
(also the lack of USB OTG will be very detrimental)
Click to expand...
Click to collapse
have you done anymore looking into the AOPP ?
wfandreas said:
have you done anymore looking into the AOPP ?
Click to expand...
Click to collapse
Yes, but no success so far.
HeeyMaan said:
I was looking at how close my Nexus 5 really is to my R1 HD, and besides the obvious Qualcomm MTK thing they are amazingly similar.
I took the official Hammerhead NetHunter 3.0 Marshmallow zip and put it on my external and card.
I then did a factory reset including dalvik and cache in TWRP.
Installed SuperSU and booted my phone. I then installed Busybox Pro and rebooted back into TWRP.
Once in TWRP I clicked install and chose my saved nethunter-hammerhead-marshmallow-3.0.zip
It will open the Aroma installer. On the first screen click everything except the RF Analyzer, MAKE SURE YOU HAVE THE OLDER VERSION OF SUPERSU CHECKED TO INSTALL AS WELL.
On the next screen click everything but custom boot screen and custom wallpaper.
Click next and be patient while it installs everything, extracts the chroot image, and verifies the extract. Took about 10-12min till it completed to 100%.
A funny side note.....when running this on My Nexus 5 it would always freeze between 90-93? and after about an hour of being frozen I would do a hard reboot. On a Nexus 6 I would install it on, same thing but if I didn't wait 90+min I couldn't later manually install chroot or any metapackages.
After install finishes reboot your phone. Once rebooted I opened up From Toolbox Pro and used Root Browser to open the Hammerhead install zip. Once opened I extracted bootanimation.zip from system/media and Hammerheadwallpaper from wallpaper.
Go to Boot Animations in Rom Toolbox Pro, choose local and you can either install bootanimation.zip as it is, or choose resize and change the framerate up to 40.
Then open wallpaper chooser from your desktop and choose Hammerheadwallpaper from your extracted folder.
Finally open the NetHunter app and click install chroot. Once it verifies it already is then choose install metapackage. I always choose the forensics package.
Once that is installed go ahead and reboot your newly modded phone with a working Kali Linux install on it.
Click to expand...
Click to collapse
Which supersu did you install ?
HeeyMaan said:
I was looking at how close my Nexus 5 really is to my R1 HD, and besides the obvious Qualcomm MTK thing they are amazingly similar.
I took the official Hammerhead NetHunter 3.0 Marshmallow zip and put it on my external and card.
I then did a factory reset including dalvik and cache in TWRP.
Installed SuperSU and booted my phone. I then installed Busybox Pro and rebooted back into TWRP.
Once in TWRP I clicked install and chose my saved nethunter-hammerhead-marshmallow-3.0.zip
It will open the Aroma installer. On the first screen click everything except the RF Analyzer, MAKE SURE YOU HAVE THE OLDER VERSION OF SUPERSU CHECKED TO INSTALL AS WELL.
On the next screen click everything but custom boot screen and custom wallpaper.
Click next and be patient while it installs everything, extracts the chroot image, and verifies the extract. Took about 10-12min till it completed to 100%.
A funny side note.....when running this on My Nexus 5 it would always freeze between 90-93? and after about an hour of being frozen I would do a hard reboot. On a Nexus 6 I would install it on, same thing but if I didn't wait 90+min I couldn't later manually install chroot or any metapackages.
After install finishes reboot your phone. Once rebooted I opened up From Toolbox Pro and used Root Browser to open the Hammerhead install zip. Once opened I extracted bootanimation.zip from system/media and Hammerheadwallpaper from wallpaper.
Go to Boot Animations in Rom Toolbox Pro, choose local and you can either install bootanimation.zip as it is, or choose resize and change the framerate up to 40.
Then open wallpaper chooser from your desktop and choose Hammerheadwallpaper from your extracted folder.
Finally open the NetHunter app and click install chroot. Once it verifies it already is then choose install metapackage. I always choose the forensics package.
Once that is installed go ahead and reboot your newly modded phone with a working Kali Linux install on it.
Click to expand...
Click to collapse
what command it that last pic?
wfandreas said:
Which supersu did you install ?
Click to expand...
Click to collapse
Originally I installed the one off the Google play store and then pro off the store as well.
Once installing nethunter I used the older supersu that comes in the zip.
wfandreas said:
what command it that last pic?
Click to expand...
Click to collapse
That's the bootup from vnc. You have to go set your passwords and boot into it.
HeeyMaan said:
That's the bootup from vnc. You have to go set your passwords and boot into it.
Click to expand...
Click to collapse
thank you, I did the same install, works well.
Hi,
I've been looking into how to get Bromite Webview as Android Webview. I'm using xXx Nolimits to remove most gapps. As a consequence the android system webview is broken. It can be fixed by installing android system webview from the play store. However I'd like to use Bromite instead (search "bromite" "Installing-SystemWebView" - I haven't posted enough to include links yet).
In order for that to work, it seems there needs to be a key in framework-res.apk identifying com.android.webview as one of the sanctioned webviews. Unfortunately it isn't there. com.google.android.webview *is* and I think that's why the play store installation works.
I'm wondering whether framework-res.apk can be modified to include com.android.webview, and whether that would let Bromite Webview be used if the play store android webview isn't installed.
Anyone understand framework-res.apk and/or knows how to safely modify it?
Google "Nanolx download." They have a separate bromite system webview zip you can flash. It may work, although I have not tried myself. I was able to use it successfully on my old Moto G5+ to do what you want.
I removed every gapps from ES file manager, it was the same issue webview was broken but in magisk there is zip it worked fine for me:good:
anonymous 4 u said:
I removed every gapps from ES file manager, it was the same issue webview was broken but in magisk there is zip it worked fine for me:good:
Click to expand...
Click to collapse
I just install the module and it shows "disabled for owner"...............
PattayaGlock said:
I just install the module and it shows "disabled for owner"...............
Click to expand...
Click to collapse
Uninstall the Chrome first then reboot
anonymous 4 u said:
Uninstall the Chrome first then reboot
Click to expand...
Click to collapse
I don't have Chrome on my phone.
Oos+Omega kernel+xXx.NoLimits.
Pulled Google down to the nano level.
PattayaGlock said:
I don't have Chrome on my phone.
Oos+Omega kernel+xXx.NoLimits.
Pulled Google down to the nano level.
Click to expand...
Click to collapse
Try going to Lucky patcher or similar defreezing app and enable the package... Goodluck...
All I can find for lucky patcher is a shady app to bypass paying for apps and some other shady sites promising they aren't malware.
With my particular set up it appears Bromite just is not feasible.
The Magisk module does not work.
I am missing the required file to install via TWRP.
It is not built into the xXx module.
Thanks for the replies.
PattayaGlock said:
All I can find for lucky patcher is a shady app to bypass paying for apps and some other shady sites promising they aren't malware.
With my particular set up it appears Bromite just is not feasible.
The Magisk module does not work.
I am missing the required file to install via TWRP.
It is not built into the xXx module.
Thanks for the replies.
Click to expand...
Click to collapse
Bromite module for magisk can't be flashed with twrp coz it download the correct package real time, guess you had ran out of luck...
Right.
Those were 2 different installs. The Bromite wiki has I structions for a TWRP install, but it say if you are misiing this file "whateveritwas" this method will not work
The.magisk module I stalled but would not work due to what appears to be a bug in his last release.
Installing Bromite apk won't change default perferred webview engine. You will need to decompile (not just unzip) framework-res.apk with some tool (I recommend APK easy tool, search for it). And inside /res/xml/config_webview_packages.xml you would like to change preferred webview engine to Bromite's apk class name (APK easy tool could read that too). Next you should compile your modified framework-res.apk and find the way to inject it in your system (I prefer Magisk for that). Also you would want to disable original chrome package.
I'm wanting to change the boot animation on my OnePlus 6T but when I go to move a new bootanimation.zip to
/system/media it say task failed and the .zip file that's there has 0 bytes.
Anyone got any idea why it's not working? Didn't have this issue with any other phone.
Cheers
Newrooter22 said:
I'm wanting to change the boot animation on my OnePlus 6T but when I go to move a new bootanimation.zip to
/system/media it say task failed and the .zip file that's there has 0 bytes.
Anyone got any idea why it's not working? Didn't have this issue with any other phone.
Cheers
Click to expand...
Click to collapse
A couple of reasons.
OnePlus left zero room on system partition. You'd need to remove something beforehand.
Many file explorers, titanium backup, etc are having issues modifying the system partition. Best luck I've had is using the built in file explorer in TWRP.
I literally replaced my bootanimation yesterday. I used a Magisk module for a bootanimation and repalced the bootanimation in the module install location which is on your data partition. This way, you can remove the module and still keep your original bootanimation should you wish to revert back. The bootanimation I used was originally for a 720p screen so I had to modify it for the dimensions of the OP6T (1080 x 2340). I am still trying to work on modifying the Magisk module so it has my bootanimation instead. It didn't work when I tried it yesterday and had to replace the file manually after, which then worked.
ffejy462 said:
A couple of reasons.
OnePlus left zero room on system partition. You'd need to remove something beforehand.
Many file explorers, titanium backup, etc are having issues modifying the system partition. Best luck I've had is using the built in file explorer in TWRP.
Click to expand...
Click to collapse
You can increase the size of the system partition with this tool: https://forum.xda-developers.com/oneplus-6/how-to/tool-epr-enchilada-partition-resizer-t3963587
I would avoid trying to resize the partitions as suggested above unless you fully understand what it is doing and what issues may arise from messing with the partition tables.
I just put my bootanimation.zip into the system-less hosts Magisk module. I have been using that module for any system files I need to replace. It's nice and simple plus you can revert the changes by just disabling the module.
Jager said:
I would avoid trying to resize the partitions as suggested above unless you fully understand what it is doing and what issues may arise from messing with the partition tables.
I just put my bootanimation.zip into the system-less hosts Magisk module. I have been using that module for any system files I need to replace. It's nice and simple plus you can revert the changes by just disabling the module.
Click to expand...
Click to collapse
Can you tell me the name of the module I searched for "system-less host" module but magisk never showed anything. Thanks
Newrooter22 said:
Can you tell me the name of the module I searched for "system-less host" module but magisk never showed anything. Thanks
Click to expand...
Click to collapse
It's built into Magisk. In the settings...
Edit:
Also if you understand what I am doing then you will see that you can basically use any Magisk module to accomplish this. It just has to be mounting files against the /system partition. I used the system-less hosts since it literally is only replacing one file on the /system partition so nothing complex was going on with this module.
Are there any working ROMs on the Onn 8" that are running Android 10? I wanna have the latest version of Android.
antoinejr1111 said:
Are there any working ROMs on the Onn 8" that are running Android 10? I wanna have the latest version of Android.
Click to expand...
Click to collapse
All the android 10 GSI's are too large for our system partition. The only one that installs is PHH's 10 v209 but video playback isnt possible outside of YouTube. Its also very unstable, it required several resets do to even simple modifications.
Sent from my SM-G975U1 using XDA Labs
jwarrior319 said:
All the android 10 GSI's are too large for our system partition. The only one that installs is PHH's 10 v209 but video playback isnt possible outside of YouTube. Its also very unstable, it required several resets do to even simple modifications.
Click to expand...
Click to collapse
Yeah we need a repartitioning utility to increase /system size. I believe some of the GSI Android 10 ROMs would be great for the Onn tablets if only the allocated /system size was larger. Has anyone tried doing this via TWRP? If /system could be formatted to a larger size, the /userdata partition could be decreased in size to compensate.
Viva La Android said:
Yeah we need a repartitioning utility to increase /system size. I believe some of the GSI Android 10 ROMs would be great for the Onn tablets if only the allocated /system size was larger. Has anyone tried doing this via TWRP? If /system could be formatted to a larger size, the /userdata partition could be decreased in size to compensate.
Click to expand...
Click to collapse
Another option would be a custom rom built for our devices. Or maybe a modified gsi with only the sruff needed for our device. The img size would be much smaller. Things like fingerprint unlock and such is just waisting space.
Sent from my SM-G975U1 using XDA Labs
jwarrior319 said:
Another option would be a custom rom built for our devices. Or maybe a modified gsi with only the sruff needed for our device. The img size would be much smaller. Things like fingerprint unlock and such is just waisting space.
Click to expand...
Click to collapse
True. An image kitchen can be used to decompile the GSI so that non-essential apps and services could be deleted. A slimmed down Android !10 GSI would surely work on this device.
So i tried the new PHH 10 V214. It does install and boot in the same we we install his Pie versions. But, it still cant play video outside of youtube app/website. Still a vendor problem i would assume. Havent tested it long enough to know if the other issues exist yet or not. Im restoring my backup of bliss rom pie.
Sent from my SM-G975U1 using XDA Labs
jwarrior319 said:
So i tried the new PHH 10 V214. It does install and boot in the same we we install his Pie versions. But, it still cant play video outside of youtube app/website. Still a vendor problem i would assume. Havent tested it long enough to know if the other issues exist yet or not. Im restoring my backup of bliss rom pie.
Sent from my SM-G975U1 using XDA Labs
Click to expand...
Click to collapse
I tried to install PHH 10 v215 (both A/B image and A-only) - but I cannot get it to boot. It does not go past the ONN logo and then reboots. Have made backups of all partitions using TWRP.
Tried both methods - fastboot flash system and TWRP install image.
Also tried the 9.0 pixel experience. Same result.
Any ideas what could be going wrong?
angadsg said:
I tried to install PHH 10 v215 (both A/B image and A-only) - but I cannot get it to boot. It does not go past the ONN logo and then reboots. Have made backups of all partitions using TWRP.
Tried both methods - fastboot flash system and TWRP install image.
Also tried the 9.0 pixel experience. Same result.
Any ideas what could be going wrong?
Click to expand...
Click to collapse
At the boot logo connect to adb. Make sure its recognized and issue the following command: adb shell setprop debug.stagefright.ccodec 0
Sent from my SM-G975U1 using XDA Labs
Viva La Android said:
True. An image kitchen can be used to decompile the GSI so that non-essential apps and services could be deleted. A slimmed down Android !10 GSI would surely work on this device.
Click to expand...
Click to collapse
How can I get this image kitchen with Windows 10 or Linux? And possibly how to decompress the image.
antoinejr1111 said:
How can I get this image kitchen with Windows 10 or Linux? And possibly how to decompress the image.
Click to expand...
Click to collapse
Personally, I use @SuperR.'s Kitchen for cooking Android ROMs. The kitchen allows you, for example, to toss in a system.img of an Android 10 based ROM. The kitchen decompiles the image into a workable /system folder and full filesystem. You are given options to debloat, add root, BusyBox, deodex, zipalign, etc. You can also toss in the boot.img and vendor.img from the Android 10 ROM and the kitchen will create for you the META-INF file with updater-script and update-binary. It will add your symlinks, permissions and all Edify commands needed to mete out a TWRP flashable Android 10 ROM with all the customizations you've added. The kitchen is available in both a free and a donate version (which is $15 I think). It's available for Linux and Windows based systems. Here is a link to the Windows version I use. Well worth the humble amount of money he asks for the donate version, as you'll see in the thread. https://forum.xda-developers.com/ap...dows-linux-superr-s-kitchen-v3-0-0-0-t3601702
Viva La Android said:
Personally, I use @SuperR.'s Kitchen for cooking Android ROMs. The kitchen allows you, for example, to toss in a system.img of an Android 10 based ROM. The kitchen decompiles the image into a workable /system folder and full filesystem. You are given options to debloat, add root, BusyBox, deodex, zipalign, etc. You can also toss in the boot.img and vendor.img from the Android 10 ROM and the kitchen will create for you the META-INF file with updater-script and update-binary. It will add your symlinks, permissions and all Edify commands needed to mete out a TWRP flashable Android 10 ROM with all the customizations you've added. The kitchen is available in both a free and a donate version (which is $15 I think). It's available for Linux and Windows based systems. Here is a link to the Windows version I use. Well worth the humble amount of money he asks for the donate version, as you'll see in the thread. https://forum.xda-developers.com/ap...dows-linux-superr-s-kitchen-v3-0-0-0-t3601702
Click to expand...
Click to collapse
Do you think you can break down a version of Android 10 that works for the Onn 8" and send it to me? Please?
antoinejr1111 said:
Do you think you can break down a version of Android 10 that works for the Onn 8" and send it to me? Please?
Click to expand...
Click to collapse
My only dilemma there is that I've got multiple projects going right now for various LG and Motorola devices. However, I fully plan on future development for the Onn series of tablets (primarily the newer Onn Surf series due to Treble support). As soon as my schedule permits, I'm on it. Here's the beauty with Project Treble: if an Android 10 GSI will boot on the Onn Surf 10.1, it is almost certain that it will also boot on the Surf 8. Out of curiosity, what is the allocated /system partition size on the Onn Surf 8? Is it the same as the Surf 10.1? Also, I noticed recently that there are some rather slim GSI builds of Android 10 (Go Edition). Some of these might be worth looking into.