Does anyone know if it is possible to get an android 10/11 GSI installed and working on this phone? I have tried numerous times, with GSIs found online, from the official site. Have checked to make sure I'm using one for the correct architecture. I've had varying results.
The different results I've had:
Stuck in bootloop. When in recovery, can't mount system partition.
Stuck on boot screen. Unrecoginized by PC. Can't mount System in Recovery.
Stuck on boot screen. Recognized by PC (makes ding). Can't access the phone. Can't mount System in recovery.
Stuck on boot screen. Unrecognized by PC. CAN mount System in recovery.
I have tried various methods, steps, and combinations of steps. Using TWRP and attempting to flash system with fastboot as well. When I was able to mount System after flashing the GSI, I also tried installing Magisk. It installed, but did not fix the problem. I can't remember everything I tried, but it was over the course of a few days, with multiple attempts per day. Around 5-10 each day. I can not figure out what I'm doing wrong, if it is even my error. It may just not be possible? Or may require steps that I have no knowledge of. If anyone has any advice, or knows if it's not possible with this phone, I would greatly appreciate it.
Edit: Also, I was using SP Flash Tool with the firmware from Cubot website to reinstall stock.
Elrandra said:
Does anyone know if it is possible to get an android 10/11 GSI installed and working on this phone? I have tried numerous times, with GSIs found online, from the official site. Have checked to make sure I'm using one for the correct architecture. I've had varying results.
The different results I've had:
Stuck in bootloop. When in recovery, can't mount system partition.
Stuck on boot screen. Unrecoginized by PC. Can't mount System in Recovery.
Stuck on boot screen. Recognized by PC (makes ding). Can't access the phone. Can't mount System in recovery.
Stuck on boot screen. Unrecognized by PC. CAN mount System in recovery.
I have tried various methods, steps, and combinations of steps. Using TWRP and attempting to flash system with fastboot as well. When I was able to mount System after flashing the GSI, I also tried installing Magisk. It installed, but did not fix the problem. I can't remember everything I tried, but it was over the course of a few days, with multiple attempts per day. Around 5-10 each day. I can not figure out what I'm doing wrong, if it is even my error. It may just not be possible? Or may require steps that I have no knowledge of. If anyone has any advice, or knows if it's not possible with this phone, I would greatly appreciate it.
Edit: Also, I was using SP Flash Tool with the firmware from Cubot website to reinstall stock.
Click to expand...
Click to collapse
TWRP 3.3.1 + Root CUBOT X19
[ROM][CUBOT X19][UNOFFICIAL] Havoc OS 3.11 [10.0][2020-11-30]
Wipe System, Data, Dalvik, Cache OR advanced Wipe without internal storage/micro sd card
Reboot TO TWRP
Wipe System, Data, Dalvik, Cache OR advanced Wipe without internal storage/micro sd card
Reboot TO TWRP
Flash the ROM
Willing to help if you still have an interest in the topic
same, doesnt work for me aswell
A GSI ROM can only get flashed if device supports TREBLE.
To check this you may use that app
Treble Check - Apps on Google Play
Check your device for Project Treble support and more
play.google.com
jwoegerbauer said:
A GSI ROM can only get flashed if device supports TREBLE.
To check this you may use that app
Treble Check - Apps on Google Play
Check your device for Project Treble support and more
play.google.com
Click to expand...
Click to collapse
yes it is treble supported
hi,
if i flash "Havoc-OS-v3.12-20201230-Official-arm64-ab.img" to my cubot x19 it runs fine without any problems.
however if i try to flash the images directly from google (either "https://ci.android.com/builds/branches/aosp-android10-gsi/grid?" or "https://developer.android.com/topic/generic-system-image/releases") the phone gets stuck after displaying the boot screen.
does anyone know how to solve this problem?
kind regards,
xt1622-blue27
xt1622-blue27 said:
hi,
if i flash "Havoc-OS-v3.12-20201230-Official-arm64-ab.img" to my cubot x19 it runs fine without any problems.
however if i try to flash the images directly from google (either "https://ci.android.com/builds/branches/aosp-android10-gsi/grid?" or "https://developer.android.com/topic/generic-system-image/releases") the phone gets stuck after displaying the boot screen.
does anyone know how to solve this problem?
kind regards,
xt1622-blue27
Click to expand...
Click to collapse
These are raw copies
If you want to try Android 11 : https://forum.xda-developers.com/t/...si-flashen-ohne-bootlop.4333513/post-85711061
Related
I've gone through numerous threads about "unbricking" but I have not been able to find any specific instructions for what to do in my situation. I have installed Ubuntu on a USB drive in order to access ADB/Fastboot and have allowed myself to spend a few days troubleshooting the problem myself, but must admit that I am in over my head and require some sort of guidance if possible. Any insight or help is appreciated.
How I got to where I am:
I believe when I installed TWRP I had to use the build prop exploit, but I can't remember clearly
At some point after installing TWRP, I believe I removed SafeStrap
I installed the CM-11 ROM and used it for a period of time without issue
CM-12 for Thor was released, so I installed it over the CM-11 installation I believe
I realized that by installing CM-12, I had made my gf's save files for Final Fantasy inaccessible
I tried to restore to a backup I had made of CM-11 and was met with a bootloop
By trying to "start from scratch", I wiped all options allowed without realizing the consequences
Any reboots of the device brings it to a black screen after the gray Kindle Fire logo
Here are some observations I have made while trying to figure out a solution:
In TWRP, ADB shows the device as being in "recovery"
In "adb shell" with the device booted into TWRP, the command "su" produces "/sbin/sh: su: not found"
I am allowed to drag .zip files into "Internal Storage" for the device, but flashing "13.3.1.0.zip" or "cm-12 ... .zip", for example, leads to the device booting into a black screen (I have tried mounting /system in TWRP)
Fastboot commands tend to hang on the linux terminal with the device not responding to commands
EDIT: After a little dicking around, I found out how to make the device show up under Windows 8.1 by using a guide outlined here: http://forums.team-nocturnal.com/index.php/topic/1362-how-to-adb-fastboot-in-windows-xp-7-81-10/
I am now familiarizing myself with ADB/Fastboot commands a bit more to see if I can figure anything out on my own.
I haven't been able to figure this out on my own - is there anyone who could give me some advice about my situation?
Basically TLDR is that I did a factory reset on TWRP, I can boot into TWRP but can't seem to flash anything, though I can put zips on my internal storage.
aimlessanomaly said:
I haven't been able to figure this out on my own - is there anyone who could give me some advice about my situation?
Basically TLDR is that I did a factory reset on TWRP, I can boot into TWRP but can't seem to flash anything, though I can put zips on my internal storage.
Click to expand...
Click to collapse
Sound like you either lost write permissions on the system partition or the partition contents are corrupt. I have also heard problems within the data partition can create flashing problems. Have you tried the advanced wipe functions in twrp? You'll need to do a little poking around to determine which items are safe to wipe. Obviously you don't want to touch boot and recovery but (intelligently) neither is an option in twrp.
Davey126 said:
Sound like you either lost write permissions on the system partition or the partition contents are corrupt. I have also heard problems within the data partition can create flashing problems. Have you tried the advanced wipe functions in twrp? You'll need to do a little poking around to determine which items are safe to wipe. Obviously you don't want to touch boot and recovery but (intelligently) neither is an option in twrp.
Click to expand...
Click to collapse
I get a lot of errors involving /system when I try to mount and then repair or flash anything. Also, when I reboot it often says "Your device does not appear to be rooted - Install SuperSU now?" When I swipe to install it just restarts normally to my white kindle fire logo.
EDIT: I somehow was able to flash the cm11 ROM onto my kindle, rebooted, and my tablet is working again! I tried a bunch of different repair options and even used the option that makes you type out "yes" ( can't remember the name, need to sleep atm), but somehow got it working. Thanks for the help so far.
Would anyone help me get root on doogee bl 12000? This is a version without a pro so this is a different topic than this one.
No kingoroot or framaroot programs work.
I have flashtoola and rom for this phone. I tried using adb to upload files with the 12000 pro doodge but there was always some error.
I also tried to upload files via flashtoola and recovery. However, without success.
Root Doogee BL12000
Hallo there. I'm trying to root my Bl12000. I've got a TWRP from twrp builder. It works, but whatever zip file I'm trying to install I always get "failed to mount data", invalid argument. The twrp also tells me, that there's bo OS installed, but there is. Phone is working fine after reboot. SuperSu can't be installed. Full wipe is not possible, also "failed to mount" and so on.
any help ?
Tia, Chris
I think it's the encryption. Any ideas how to remove it?
Installed twrp via fastboot and sp flash tool, but I can't boot phone into it. Searched dozens of sites, no success. Flashed the twrp again with sp flash tool and according to sp it was successful. I tried several ways to boot the phone into it afterwards, no luck
My goal is to root this phone only. I'm not very experienced so if anyone could please give me a hand here and tell me where or what I'm doing wrong, that'd would be great and much appreciated. Thanks.
Ok. If I flash the twrp with Sp flash tool and type "fastboot reboot" on the adb console, sending the command while I hold vol+ and power-, the phone boots into the twrp. Next time it will be gone, so I have to flash it again. Noticed that, done.
But all this is taking me nowhere, because the encryption still prevents me from installing any zip file or format a partition. Yuck ?
Root Bl12000
Since the SuperSu method took me nowhere I decided to try Magisk. And.......HURRAY !!!!!!.......it worked.....for a moment. Booted the patched boot.img and got superuser. But with the first reboot I got stuck in bootloop. Tried again, in case I missed something, but same ****.
IT WORKS !!!!! My mistake was to assume, that Magisk works the same way as rooting with SuperSu does. So after rooting with Magisk I tried to install root apps as I was used to, but Magisk does not work that way.
Well, it'll take me awhile to figure this out ?
Why does an app keep coming back on my phone after I have done factory reset?
Christian1968.Bolz said:
Hallo there. I'm trying to root my Bl12000. I've got a TWRP from twrp builder. It works, but whatever zip file I'm trying to install I always get "failed to mount data", invalid argument. The twrp also tells me, that there's bo OS installed, but there is. Phone is working fine after reboot. SuperSu can't be installed. Full wipe is not possible, also "failed to mount" and so on.
any help ?
Tia, Chris
I think it's the encryption. Any ideas how to remove it?
Installed twrp via fastboot and sp flash tool, but I can't boot phone into it. Searched dozens of sites, no success. Flashed the twrp again with sp flash tool and according to sp it was successful. I tried several ways to boot the phone into it afterwards, no luck
My goal is to root this phone only. I'm not very experienced so if anyone could please give me a hand here and tell me where or what I'm doing wrong, that'd would be great and much appreciated. Thanks.
Lucky Patcher 9Apps VidMate
Ok. If I flash the twrp with Sp flash tool and type "fastboot reboot" on the adb console, sending the command while I hold vol+ and power-, the phone boots into the twrp. Next time it will be gone, so I have to flash it again. Noticed that, done.
But all this is taking me nowhere, because the encryption still prevents me from installing any zip file or format a partition. Yuck
Click to expand...
Click to collapse
This Recovery is only supported for Doogee BL12000
You should have either PC or Laptop.
Make sure to charge your phone for at least 50%.
Download and install latest Doogee USB Drivers on your PC/Laptop [All Android USB Drivers]
Download the SP Flash Tool Software
VCOM driver: Download – Instal the VCOM Driver on your computer (still compatible with MT67xx phones)
Before flashing a custom recovery, you need to unlock the bootloader on Doogee BL12000
Take a full backup just in case if you need it later
TWRP+root bl 12000
joachim97 said:
Would anyone help me get root on doogee bl 12000? This is a version without a pro so this is a different topic than this one.
No kingoroot or framaroot programs work.
I have flashtoola and rom for this phone. I tried using adb to upload files with the 12000 pro doodge but there was always some error.
I also tried to upload files via flashtoola and recovery. However, without success.
Click to expand...
Click to collapse
On the forum 4pda can be found for bl 12000
TWRP+ROOT
when you install twrp formatting you can not do it, but immediately install magisk and reboot ...
Hi! After using my mi pad 4 for a while with TWRP and Phh-Treble AOSP, I tried to flash a new version of the ROM.
I am not sure what I did wrong at that time but I am not able to boot the system anymore. The device always gets stuck on the mi logo.
I am still able to access recovery & fastboot using the volume keys and use them from my computer.
I tried wiping partitions from TWRP (Dalvik / ART Cache, Data, Internal Storage, Cache, System) and reverting the ROM but I am still not able to boot the system.
No matter what ROM I use, I only get the mi logo when booting system.
I also tried to flash the system from fastboot but it makes no difference. I get no errors no matter which method I use.
I am on Linux but could arrange Windows if necessary for some tool. Any help is appreciated.
Hi @qppq,
I had a similar issue when I was playing with the Mi Pad 4 for the first time.
I think the Problem was, that I did not deleted the Cache after flashing the Rom and Disable Dm-Verity.
And another time by changing the "/vendor/build.prop" instead of "/system/build.prop"
I was able to fix my system by flashing the "system.img" and "vendor.img" from the Fastboot ROM (Fastboot Update) via TWRP.
You can find it here: https://en.miui.com/thread-4590474-1-1.html (clover_images_V10.1.1.0.ODJCNFI_20181101.0000.00_8.1_cn_9ff5f9dcea.tgz)
You can also use the "flash_all_except_storage" Skript to fix you device.
Best Regards,
Datafreak
Hi @datafreak,
Thanks to you I got the system running again.
After flashing system.img & vendor.img or using the flash_all_except_storage script, the device still did not boot completely (in the 20min I waited) but at least it got past that initial screen to the system.
Flashing TWRP, wiping some partitions and flashing AOSP after that made the system usable again.
I didn't know that people distribute images with all these partitions. Quite useful here.
Thanks again!
qppq
Hi everyone!
I'm using a Samsung gt-n8010. It could be done for due to the age, but maybe there is still hope.
My problem is that the tablet boots always to TWRP recovery and I can switch to download mode as well. Everything seems all right, internal storage and sd card shows exactly how they should, BUT... I can't do anything in TWRP. If I have the Keep system partition read only unticked, it still says the storage is read only and /data/media is not accessable. I can see it and access it with TWRP File manager. I tried flashing ROM and Recovery, also stockROM with Odin, but Failed. Clearing Cache, Data, Dalvik... also ends up with error. Format Data works, and also changing the partition types, but when I reboot device, it all comes back the same as before, no changes take effect. In Download mode I tried to use Adb from computer terminal, but it was stuck saying 'Waiting for device'. If Tab is in Recovery my PC shows both internal storage and sd card, but the internal storage is empty when I open it.
For details: I use Lineage OS 18.1 with TWRP 3.6.1_9-0. On my computer I use Linux Mint 20.3, but I tried with a laptop using Win10 as well, no success.
I've read many solutions on 'Unmodified system partition' or some had 0MB internal storage problem, but in my case that is different, as I have them all, but it seems all is read only and not accessable. I even tried to have the last Backup (2 month old) set using Restore of TWRP, but during the process, the tablet reboots and TWRP comes up again. I can't even turn it off, as TWRP comes up after some minutes.
Please help me somehow to be able to use the Tablet. If you need any further details, just tell me.
TWRP is not out yet on android 12, if you have it as of writing it wont be able to unencrypt your device. So all you can do is use it to install roms (YOU MUST FIRST FACTORY RESET THE DEVICE).
I also have never used odin as I have prefered adb
Code:
adb shell
/sbin/recovery --wipe_data
/sbin/recovery --update_package=SDCARD:romname.zip
adb should work in twrp?
I see your point. I intended to change/downgrade LineageOS version, but I was not successful. Now I am not able to do a factory reset either with success from TWRP, but I give a try to your adb codes. Give me some time
leathan said:
TWRP is not out yet on android 12, if you have it as of writing it wont be able to unencrypt your device. So all you can do is use it to install roms (YOU MUST FIRST FACTORY RESET THE DEVICE).
I also have never used odin as I have prefered adb
Code:
adb shell
/sbin/recovery --wipe_data
/sbin/recovery --update_package=SDCARD:romname.zip
adb should work in twrp?
Click to expand...
Click to collapse
Hi, I gave a try to that code both on TWRP and Linux terminal (from PC). But no effect First I did a FactoryWipe (successful) and went back to the Terminal each time. I tried with ROM zip and TWRP img as well, but after rebooting, TWRP 3.6.1 comes back again. I downloaded Lineage OS 17.1 (with GAPPS pico) and TWRP 3.5.0-9. It seems somehow I got stuck with that TWRP 3.6 and all I get on every attempt of flashing or wiping is it can't see '/data/media (No such file or directory)' or 'Unable to make /cache/recovery: Read-only file system'. I hope there would be a solution to get my system out of Read-only state
Nektarin87 said:
Hi, I gave a try to that code both on TWRP and Linux terminal (from PC).
Click to expand...
Click to collapse
Do you have adb installed and do you see your phone when you type "
Code:
adb devices
"
Usually its as simple as just booting into TWRP -> Factory reset then install the rom and done.
Maybe you do need odin but im pretty sure you can use adb instead like I outlined above, I hated using odin but if you find the right file it should also fix your issue.
What is the codename for your tablet? I cant find it on lineageos's site, what guide did you use its an official lineageos im assuming?
leathan said:
Do you have adb installed and do you see your phone when you type "
Code:
adb devices
"
Usually its as simple as just booting into TWRP -> Factory reset then install the rom and done.
Maybe you do need odin but im pretty sure you can use adb instead like I outlined above, I hated using odin but if you find the right file it should also fix your issue.
What is the codename for your tablet? I cant find it on lineageos's site, what guide did you use its an official lineageos im assuming?
Click to expand...
Click to collapse
Well, I have adb installed, but as my Tablet can only load in recovery it says like these:
adb devices
List of devices attached
4107cd04a2b611b5 recovery
When I load Odin or fastload mode (Download mode as tablet says) I can not list it with 'Fastboot device" command. It says 'waiting for device'.
My tablet is Samsung gt-n8010 (10.1) and I follow this thread to make changes:
LineageOS 16.0 Android 9 for GT-N8000 GT-N8010 GT-N8013 GT-N8020 FINAL VERSION EOL
/* * Your warranty is now void. * * I am not responsible for bricked devices, dead SD cards, * thermonuclear war, or you getting fired because the alarm app failed. Please * do some research if you have any concerns about features included in...
forum.xda-developers.com
I had Lineage OS 18.1 installed and maybe what caused the issue is that I did not update the TWRP, or we do not have a TWRP ready for it yet, but currently I have TWRP 3.6.1_9-0 installed and stuck with. As I mentioned, on rebooting tablet always starts with TWRP, asking if I want system read only or not with an Unmodified system partition heading. I can not boot OS at all, I can go to Download mode, but Odin always failed indicating my system is read-only.
Ok yes your device is listed as recovery because it has not booted anything. I'm not sure if the commands I gave work without the system actually booting however.
After you entered adb commands there was no error text?
Also if you cant get odin to recognize your phone (RUN IT AS ADMINISTRATOR) you should figure out that first as thats a last resort fix when you really mess things up which I dont think you have yet. I think you must have something off in your configuration if its not reading anything make sure u can access another phone to rule out your pc, but get this working asap.
Usually if your device boot loops you can wipe the cache, and now days remove magisk modules.
If your device still boots straight to recovery It should be as easy as I outlined above, try not isntalling the apps/plugins after the initial rom, and again make sure you wipe cache/data before hand.
If your device boots straight to the bootloader then your left with Odin.
Man I hate video guides. But it looks good (unless he forgot to wipe) should have been as simple as that. He does not however provide you with the firmware (not rom) file that I believe you are going to need if you improperly downgraded the android a full version number. Post on his youtube and find that firmware file and fix your odin connection and flash it. If odin is also dead I have no idea but I have never in nearly 20 years had a phone fully brick even when I try to brick them. But I know it can be possible but your most likely going to recover from this.
If he doesn't respond just read more and learn, you may need some specific large file though to flash over what I believe may now be missing partitions entirely.
Maybe someone else here can help too. Good luck!
leathan said:
Man I hate video guides. But it looks good (unless he forgot to wipe) should have been as simple as that. He does not however provide you with the firmware (not rom) file that I believe you are going to need if you improperly downgraded the android a full version number. Post on his youtube and find that firmware file and fix your odin connection and flash it. If odin is also dead I have no idea but I have never in nearly 20 years had a phone fully brick even when I try to brick them. But I know it can be possible but your most likely going to recover from this.
If he doesn't respond just read more and learn, you may need some specific large file though to flash over what I believe may now be missing partitions entirely.
Maybe someone else here can help too. Good luck!
Click to expand...
Click to collapse
Hi there, I actually find some videos or instructions useful and some helped me out a lot. But as always, things can only be proper if anyone is qualified to do it or when you have the exact same issue on the device. Now back to my case...
I tried many ways, many aspects, but none helped me out. There was this good and working Samsung 10.1 gt-n8010 and one afternoon I found it turned off. When I charged it for a while I turned it on and all it could load is TWRP and I could not do anything. It seems to be working, but I could not see internal storage, while it showed all the 12 GB amount I had, so the issue is not that it shows 0 GB like in many videos. I tried to wipe cache, data, system, even change partition types, all ended with a fail saying my 'system is read only'. I also tried to use Odin and Heimdall to flash new recovery and ROM, also gave a chance to stockRom with android 4.1 or 4.4, but in all cases it said FAILED. To conclude all: I think it could be a hardware issue and as the machine is more the 10 yrs of age, it would not be a surprise, but it's a same it can't be flashed.
If anyone had a similar issue or may have suggestions I'm all ears and the thread remaines, but I am out of ideas at the moment and put my Samsung tab on the shelves.
Figured it out.
Dear all,
I am trying to replace the stock OS on my Lenovo tablet with some more open alternative, like LineageOS. I got as far as installing a modified version of TWRP on it and got root access.
I also found some unofficial gis LOS images but I couldn't install them via TWRP as the SYSTEM partition does not show up when I have to select which partition I want to install the image to. Mounting (ticking) the system partition in TWRP makes no difference. These are the partitions listed:
Boot
Vendor Image
Recovery
Modem (Image)
Persist (Image)
Splash
So I went ahead, and installed it from fastboot like this:
fastboot flash system image.img
Click to expand...
Click to collapse
The command succeeded, but when restarting, the device gets back to fastboot. I can boot into TWRP as well, but no matter what image I try to install, I get the same result.
I wonder what I am doing wrong... A few years back I have converted several phones to LOS and others with no problem. But I have no experience with gis. Maybe that's the problem.
Could someone more experienced help me? maybe I am trying the wrong gis images.
Thanks for any pointers in advance!