my life is sad I have been working on rooting my phone for over 3 years...
i just need help
i just need help
Oh that is erfangsi based ones Which only supports qualcommn and exynosI posted a pic of "hello".
I switched to remix os because it sounds cool, but I can't upgrade higher than 8.1?
Something does happen when I flash an android 9 remix os:
The remix os logo shows
Its goes smaller and bigger
Thats it never goes to a home page or anything
Ok it may not mount some partitions and there is a low low low low low possibility for the TWRP to fry the EMMC. This is what I can imagine of about flashing or booting TWRP without partition details, not trashing your work, but to warn the OP.
No I found out why it dosn't work...Oh that is erfangsi based ones Which only supports qualcommn and exynos
see if this boots, Android 11
or this, also Android 11
Oh didn't spot that problem!No I found out why it dosn't work...
it's becuase the api level isn't supported:
Because device device wasn't released with Android 9 or higher.
Read this, especially the "Check Device Compliance" section: https://developer.android.com/topic/generic-system-image
How ever I found out some more interesting information about my phone:
My phone company (Maxwest) rebrands phones! So here is my original phone :
But Coolpad released this phone using android 7. Which means Maxwest had to change the api level of the device.Entry-Level Coolpad 1801-T0 Seen On TENAA - Gizmochina
Coolpad has been under the radar for a while following the woes of its former largest stakeholder, LeEco. The smartphone company was also in the news recently over patent issues with Xiaomi but it appears it is back to making phones as a new device has been spotted on TENAA. The Coolpad 1801-T0...www.gizmochina.com
Post #142 I asked him to try Android 11 GSI but that failed. Boots forever.I'm not sure about that. Isn't that the requirement with just Google's GSI? Have you tried a Android 9/10/11 phh GSI?
adb shell
su
mount -o rw,remount /
echo "setprop debug.stagefright.ccodec 0" >> /system/bin/rw-system.sh
Good ideaMaybe the OP can try runing 'adb logcat' or 'dmesg' to see if the error can be solved. It could just be that some binaries are missing and they need to be pushed.
I'm also thinking of forking the phh generic device tree and making it more specific to the phone so that the op can have an actual custom rom. What do you think of that?
The real problem is no devices with Android 9 runs on a same/similar unisoc/spreadtrum chip, according to my research.Hey, interesting thread. I also have a phone with unisoc chip that I did a little bit of tinkering with but couldn't go any further than just unlocking the bootloader (using the same hovatek guide). Also this one comes with a unisoc sc7731e chip and same 8.1 stock rom.
btw, I have an idea, can you try using/porting a boot image by replacing the kernel from an android 9 device that has the same chipset as yours, that might make it to boot into an android 9 rom.
try this:I have a maxwest nitro 5p, I got it free from the government assistance provider. the phone is a chore to use to say the least. I would like to root and load a custom rom but I can't find any info on this particular in the modding community
Hello Seppppx! I am happy to tell you the twrp successfully flashed! Not only that I was able to root my device as well.So far I have built this twrp with this tree https://github.com/Seplx/twrp_device_maxwest_sharkl2
you can download it from here
recovery.img
drive.google.com
try to boot it with
'fastboot boot recovery.img'
if it boots I recommend that you don't do any operation within it as I'm still missing the partition sizes and I don' know the side effects of that.
Hello? wait don't leave me now!!user@user-HP-EliteBook-8460p:~/Downloads$ fastboot flash --disable-verity --disable-verification vbmeta vbmeta-sign.img
target didn't report max-download-size
sending 'vbmeta' (12 KB)...
OKAY [ 0.001s]
writing 'vbmeta'...
OKAY [ 0.362s]
finished. total time: 0.364s
user@user-HP-EliteBook-8460p:~/Downloads$
sorry I shouldn't get to exsited I think I just flashed the stock vbmeta.img.
But is there anyway to test if it is?
fastboot devices
fastboot --disable-verity --disable-verification flash vbmeta-sign vbmeta-sign.img
fastboot reboot
fastboot devices
fastboot oem get_identifier_token
fastboot flashing unlock_bootloader signature.bin