my life is sad I have been working on rooting my phone for over 3 years...
i just need help
i just need help
Is my life really worth it?
- Thread starter 『フレーバー』
- Start date
I 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
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
Attachments
D
Deleted member 9635294
Guest
Oh that is erfangsi based ones Which only supports qualcommn and exynos
see if this boots, Android 11
or this, also Android 11
Last edited by a moderator:
D
Deleted member 9635294
Guest
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...
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 :
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
D
Deleted member 9635294
Guest
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...
D
Deleted member 9635294
Guest
Post #142 I asked him to try Android 11 GSI but that failed. Boots forever.
Anyway somewhat it may be solved by executing the following code in TWRP.
Code:
adb shell
su
mount -o rw,remount /
echo "setprop debug.stagefright.ccodec 0" >> /system/bin/rw-system.sh
Last edited by a moderator:
D
Deleted member 10052738
Guest
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.
D
Deleted member 9635294
Guest
The real problem is no devices with Android 9 runs on a same/similar unisoc/spreadtrum chip, according to my research.
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
try this:
How to root Unisoc | Spreadtrum Android 9; Case study: Teclast P80X
In this tutorial, we are going to show how to root a Unisoc / Spreadtrum android 9 (pie) device by patching the stock recovery.img using magisk manager and signing using avbtool. The variant used in t
forum.hovatek.com
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.
I would like to learn how make a device tree from scratch or maybe learn how to make my very own custom rom. Anyways could you give me some tips or a reliable article to learn from?
Last edited:
Similar threads
Top Liked Posts
-
There are no posts matching your filters.
-
11DDeleted member 1890170Android phones/tablets powered by UniSoc ( formerly Spreadtrum ) chipset can only get bootloader-unlocked if both the vbmeta-sign.img - what contains the public keys - and vbmeta.pem - what holds the private keys - are present on device.1DDeleted member 1890170
As I can see I stated it wrong: must read "are present" instead of "are present on device". Sorry for this.
1. Typically people by means of SPD Research Tool extract existing vbmeta-sign.img, then pass this extracted file to fastboot what rewrites it at its own when you run
You don't have to create vbmeta-sign.img at your own as you can read elsewhere.Code:fastboot devices fastboot --disable-verity --disable-verification flash vbmeta-sign vbmeta-sign.img fastboot reboot
2. File vbmeta.pem what holds the unlock-token what you get with
must get created at your own - see attachment. Once created you rename it to signature.bin and flash it as followsCode:fastboot devices fastboot oem get_identifier_token
Code:fastboot flashing unlock_bootloader signature.bin
HTH1OMG I DID SOMETHING
I flashed the aonly img from
And It finished and it's booting into lingos os1
