Hi, after recovering from an error in twrp saying my /data partition didn't exist by flashing these stock images my phone has lacked any WiFi functionality when a custom ROM is installed, i havent yet tried if the stock ROM behaves like this as well(Wi-Fi can't be enabled at all).
I remember reading the bootloader.img contains the modem/radio libraries but that it wasn't possible to flash this from twrp, is this something I can try doing via fastboot or adb? What I've tried as well is factory resetting via twrp and reflashing the Android Marshmallow and the Nougat versions of the lineageOS ROM, to no avail.
I actually wanted to post this on the lineageOS for lenovo p2 dev thread, but I'm new here so that wasn't possible so if anyone has suggestions on where to look or where to maybe cross-post this, please let me know.
Thanks in advance
Related
Was on 4.4.2 stock NJ2...Odin'ed a custom recovery like TWRP...rebooted.....NO IMEI and BASEBAND. That's about as simple, yet complex it gets. Tried reverting back to stock recovery in Odin, only to find that NO IMEI and BASEBAND still shows up. THE ONLY way I've successfully kept the IMEI/BASEBAND....is by keeping everything stock, from recovery to rom. Why would this be? I've even tried restoring the EFS folder....to no avail!!!! I'M FRUSTRATED!!!! My end goal is to be able to flash a rom, use TWRP/CWM, and KEEP the IMEI/BASEBAND!!!
ANY HELP? ANYONE having the same issue or fix?
THANKS!!!!!!:good:
Possible fix...
Make sure you have not used device encryption on the rom prior to your desired rom...
If you have then a device full wipe script is needed to clean up the phone prior to flashing the new rom...
(don't forget to check your SD card for encryption or data files that may be affected)...
Flash TWRP version 2.8.6.0 and flash your new rom....
Higher TWRP versions have been buggy for me...
Best I've got atm....g
It's because you are using TWRP 3.0.0.1, that one is broken
I recently flashed Resurrection Remix standard Nougat Edition with the latest version of open gapps, nothing else. I then proceeded to make a backup with TWRP as IMO its always good to have a backup at this fresh working condition. This is the issue going into TWRP and choosing backup and swiping to start the backup i get the error "unable to mount storage" and the backup fails.
I am able to access files via MTP with windows but for some reason TWRP isn't working.
I am afraid to do anything at the moment as without a means to backup or restore via backup i'm afraid of bricking my device. Since i've owned my 1+3 I've always just stayed stock with magisk but i thought hey why not have fun right so I decided to check out Resurrection Remix and I it but I don't like not being able to create backups or really even use TWRP. My first thought would to Re-Flash TWRP but as i said without some more knowledge I don't want to try anything.
Thank you in advance for reading my post and thank you a thousand times if you can help me out. If you need information or any sort of logs please ask.
lebeatnik said:
I recently flashed Resurrection Remix standard Nougat Edition with the latest version of open gapps, nothing else. I then proceeded to make a backup with TWRP as IMO its always good to have a backup at this fresh working condition. This is the issue going into TWRP and choosing backup and swiping to start the backup i get the error "unable to mount storage" and the backup fails.
I am able to access files via MTP with windows but for some reason TWRP isn't working.
I am afraid to do anything at the moment as without a means to backup or restore via backup i'm afraid of bricking my device. Since i've owned my 1+3 I've always just stayed stock with magisk but i thought hey why not have fun right so I decided to check out Resurrection Remix and I it but I don't like not being able to create backups or really even use TWRP. My first thought would to Re-Flash TWRP but as i said without some more knowledge I don't want to try anything.
Thank you in advance for reading my post and thank you a thousand times if you can help me out. If you need information or any sort of logs please ask.
Click to expand...
Click to collapse
I am tired of repeating this.
I think that you are on the official version of TWRP which is good if your ROM is OOS. But when shifting to custom ROMs, it is a good idea to flash eng.stk's TWRP.
The official TWRP will not work with custom ROMs.
The official TWRP will not work with custom ROMs.
???!!!
I'm with official twrp 3.1.1.2 , flashing custom ROMs and using them , till today, no problem. I think his data encrypted so twrp not showing storage.
I am on the official version of TWRP I have not read anywhere about that issue, so if I flash eng.stk's TWRP it should work? Sorry your tired of repeating it but it's not on the ROMs thread so idk where I would have gotten that info, but thanks
drmuruga said:
The official TWRP will not work with custom ROMs.
???!!!
I'm with official twrp 3.1.1.2 , flashing custom ROMs and using them , till today, no problem. I think his data encrypted so twrp not showing storage.
Click to expand...
Click to collapse
May be I shouldn't have been that categorical, but for many, the issue is there. Glad that it works for you.
---------- Post added at 05:27 PM ---------- Previous post was at 05:25 PM ----------
lebeatnik said:
I am on the official version of TWRP I have not read anywhere about that issue, so if I flash eng.stk's TWRP it should work? Sorry your tired of repeating it but it's not on the ROMs thread so idk where I would have gotten that info, but thanks
Click to expand...
Click to collapse
Why don't you try? You are not going to lose anything.
Also take into account the post above yours regarding encryption.
It worked, for some reason official TWRP would not unlock after I entered the encryption code, blue spark TWRP works, thanks, this is probably what I would have tried but it's nice to have gotten some info on the issue before I went flashing things Willie nillie
After you flash your files in TWRP, then select reboot, and reboot back into TWRP
Hi all!
I'd like to share a problem that I've been having for two days now and that I can't solve by myself.
See, I can't flash any custom ROMs. I had no problem unlocking it and flashing TWRP but while I can flash the Global or China version of Miui, I can't flash Lineage or RR.
At first, I had the error 7 code, and I did the assert trick I was able to flash but then my mix 2 was stuck in bootloop.
I tried a fastboot format userdata as it was suggested in RR's thread but it didn't work and the method quoted didn't work either.
I've read a few threads where they talked about how the partition were encrypted and had to be formated but I didn't find any clear tutorials (or i'm really blind an idiot, which is possible)
I don't know if it can help, but I did wipe dalvik/cache/data every time before flashing
For now, I've switched back to Global but would really like if anyone could help me going stock ;_;
EDIT: I've also used the Format Data option in TWRP but it didn't have any effects or I used it at the wrong time, which is, once again, quite possible
don't give up bro
Did you find out any solve?
Full wipe- type yes
Reboot back into recovery and then try installing the roms
Dasporal said:
Hi all!
I'd like to share a problem that I've been having for two days now and that I can't solve by myself.
See, I can't flash any custom ROMs. I had no problem unlocking it and flashing TWRP but while I can flash the Global or China version of Miui, I can't flash Lineage or RR.
At first, I had the error 7 code, and I did the assert trick I was able to flash but then my mix 2 was stuck in bootloop.
I tried a fastboot format userdata as it was suggested in RR's thread but it didn't work and the method quoted didn't work either.
I've read a few threads where they talked about how the partition were encrypted and had to be formated but I didn't find any clear tutorials (or i'm really blind an idiot, which is possible)
I don't know if it can help, but I did wipe dalvik/cache/data every time before flashing
For now, I've switched back to Global but would really like if anyone could help me going stock ;_;
EDIT: I've also used the Format Data option in TWRP but it didn't have any effects or I used it at the wrong time, which is, once again, quite possible
Click to expand...
Click to collapse
Maybe try going completely back to MIUI9 global with Miflash/XiaomiTool. After that re-flash TWRP. Format data, reboot recovery, Full wipe, Install ROM and Gapps, reboot system. This should work fine.
Hey there,
I've been using an old beta of OmniROM Oreo for months now, but wanted to try the 9.0 ROMs that are out there. I followed the instructions in both the Lineage and Omni threads and updated to the TWRP that's needed, then flashed the chiron firmware that's needed, then wiped all and formatted data, then installed the ROM. When I went to flash the rom, TWRP told me that my filesystem was read only and suggested I leave it that way for security. I said OK, everything installed fine, but when it restarts it fails to boot the OS and then reboots into recovery (TWRP). I have tried flashing the firmware, different ROMs, etc., but not getting anywhere.
I'm assuming this is related to leaving the filesystem read-only, but not really sure.
Anyone know what I did wrong? And how to fix it?
Thanks
Hi. I have a MTK6739 which came with the "GO" version of Android (1GB ram). It came with Oreo, and it is GSI compatible (Arm with A only).
I recently wanted to give some GSI images a try and tried to flash AOSP. I tried to flash the system image using fastboot and also SP Flash Tool (of MTK). Both gave me the same error:
FAILED (remote: sparse image size span overflow.)
After getting this error, i reset my phone and my default system is still there, so nothing is being written to the system partition. I thought maybe treble AOSP images are larger than my phone's system partition but when i checked, the default system img of my phone is actually larger than the GSI images (I have also tried a "go" version of a gsi image with the same outcome).
What is my problem here please?
PS: My bootloader is unlocked.
What version of Android did your phone come with? If it's 8.X, then you have what is called Treble Legacy, which from what I am experiencing is sorta buggy. Do you have TWRP installed? It will help to have it, for a number of reasons. When a flash fails on mine, it typically wont boot the OS but rather just boot into TWRP, which makes it easy to simply kick it back in fastboot or do a wipe of a partition.
My BV5500 is GSI Enabled (Legacy) and even though it supports Treble, images won't load with TWRP even though it has Treble support. What images that do run have to be flashed with fastboot. I did use MTK tools to flash a few partitions again, but for the most part I use TWRP/Fastboot.
Mine also has the same behavoir as yours, you flash a ROM and /system is empty! (Or unchanged) So def a bug somewhere.
Chaos Storm said:
What version of Android did your phone come with? If it's 8.X, then you have what is called Treble Legacy, which from what I am experiencing is sorta buggy. Do you have TWRP installed? It will help to have it, for a number of reasons. When a flash fails on mine, it typically wont boot the OS but rather just boot into TWRP, which makes it easy to simply kick it back in fastboot or do a wipe of a partition.
My BV5500 is GSI Enabled (Legacy) and even though it supports Treble, images won't load with TWRP even though it has Treble support. What images that do run have to be flashed with fastboot. I did use MTK tools to flash a few partitions again, but for the most part I use TWRP/Fastboot.
Mine also has the same behavoir as yours, you flash a ROM and /system is empty! (Or unchanged) So def a bug somewhere.
Click to expand...
Click to collapse
Mine came with Android 8.1. Unfortunately my device doesn't have TWRP. In my situation, the flash fails but the phone still boots to its original OS. So nothing is overwritten. What i didn't do however is that i didn't "wipe" the partition before flashing the gsi image. And why should i anyway? The default flashing software of MTK (SP Flash Tool) doesn't even have a wipe option. It just overwrites to the partition. I never had to wipe the old rom to flash the stock rom before, it happened automatically.
Did you have any success with any of the gsi images that you have tried?
twilightened said:
Mine came with Android 8.1. Unfortunately my device doesn't have TWRP. In my situation, the flash fails but the phone still boots to its original OS. So nothing is overwritten. What i didn't do however is that i didn't "wipe" the partition before flashing the gsi image. And why should i anyway? The default flashing software of MTK (SP Flash Tool) doesn't even have a wipe option. It just overwrites to the partition. I never had to wipe the old rom to flash the stock rom before, it happened automatically.
Did you have any success with any of the gsi images that you have tried?
Click to expand...
Click to collapse
Yes, XenonHD and AOSP GSI 8.1 Oreo "Go" work. Also, Lineage and RessurectionRemix work but are very slow. This is in part to Gapps.
In the end, I used AOSP GSI 8.1 Oreo "Go", which was designed for 1GB RAM devices, and since it's been tweaked to run on slow hardware, it runs plenty fast.
On my BV5500 I would often have trouble getting a flash to function. Sometimes I would have to use SP Flash to restore stock boot and stock recovery, and then it would boot, complain of corruption, ask me to wipe, then kick me back into fastboot, where I would flash the rom and twrp.
Sometimes when I tried to flash a ROM that had worked previously it would say it finished but the partition would be empty.
As regards to wiping, perhaps its a bug but I found that my chances of flashing were better if the system partition was wiped prior to flashing.
Oh, one more thing: when I flash these ROMS, they all are sparse images and send data in small chunks. At least when done via fastboot. Perhaps try a different ROM or re-download the ROM, it's possible it's corrupt. Worth a shot.
Chaos Storm said:
Yes, XenonHD and AOSP GSI 8.1 Oreo "Go" work. Also, Lineage and RessurectionRemix work but are very slow. This is in part to Gapps.
In the end, I used AOSP GSI 8.1 Oreo "Go", which was designed for 1GB RAM devices, and since it's been tweaked to run on slow hardware, it runs plenty fast.
On my BV5500 I would often have trouble getting a flash to function. Sometimes I would have to use SP Flash to restore stock boot and stock recovery, and then it would boot, complain of corruption, ask me to wipe, then kick me back into fastboot, where I would flash the rom and twrp.
Sometimes when I tried to flash a ROM that had worked previously it would say it finished but the partition would be empty.
As regards to wiping, perhaps its a bug but I found that my chances of flashing were better if the system partition was wiped prior to flashing.
Oh, one more thing: when I flash these ROMS, they all are sparse images and send data in small chunks. At least when done via fastboot. Perhaps try a different ROM or re-download the ROM, it's possible it's corrupt. Worth a shot.
Click to expand...
Click to collapse
Thanks for the reply. I will try wiping first and flashing after that. Let's see if it is gonna work.
PS: By the way, these images come as img.xz format. I first unpack them and get the img. Am i doing it wrong? Should i just flash the img.xz images?
twilightened said:
Thanks for the reply. I will try wiping first and flashing after that. Let's see if it is gonna work.
PS: By the way, these images come as img.xz format. I first unpack them and get the img. Am i doing it wrong? Should i just flash the img.xz images?
Click to expand...
Click to collapse
No, you are doing it correctly. I think they compress them to save bandwidth.
just need to resize that partition
twilightened said:
Hi. I have a MTK6739 which came with the "GO" version of Android (1GB ram). It came with Oreo, and it is GSI compatible (Arm with A only).
Click to expand...
Click to collapse
Which device? Please tell.
I have also Blackview A20 (go).
Flash stock with spflash. Only for stock
Let it reboot. reset. Allow it to reboot once again. Check everything GPS/wifi/bt. Enable ON
Do not connect to Google accounts. not needed.
Enable adb
Charge at least 90% - some devices will NOT flash and silently ignore.
fastboot erase system
fastboot flash system gsi.img
fastboot reboot
If it asks you a password, just type anything. Then it will ask you reset phone. Say OK.
all done
Note always check the sha1sum or md5sum of GSI. Despite having
kusti420 said:
just need to resize that partition
Click to expand...
Click to collapse
Excuse me, I'm new to this, would you have a tutorial? I have several phones that would help
kusti420 said:
just need to resize that partition
Click to expand...
Click to collapse
how can i resize the partition pls?