Hi everyone, i messed up today, i was running LOS 15.1 +twrp +unlocked. Everything was fine till i updated lineage Os to last version and i decided to flash the last firmware dec 2018 for 9.0 android. Since i lost audio while calling and fingerprint. I decided to flash nov-18 Firmware, it didn't solved the issue, then
I decided to flash stock rom using Mi flash the following versions with the clean_all script.
- tissot_images_7.8.23_20170823.0000.00_7.1_61cf97d794
- tissot_images_8.1.10_20180110.0000.00_8.0_8ea503201b
Since still bootlooping, no network, the screen is always locking itself....
The IMEI are still here, i just want to downgrade to earlier firmware
I unfortunately have no twrp backup of the EFS partition.....
my mistake...thanks for your help.
Related
Hi all,
This is what actually happend after installing H2oS 2.5.1....
Flashed h2o with twrp recovery stuck up at setup wizard...
So i used OOS unbrick tool to get back to stock but that stuck up at oneplus logo..
so next i flashed using hydrogen restore tool to 5.1.1
after that again flashed latest ver of h2os
so finally it worked..but due t few reasons i wanted to go back to oos..nothing help me
Installed TWRP on h2os 2.5.1 than copied my backup which was made with twrp dated [2016-04-08--17-02-42]
restored done setup done
then i get promp of software update oos 3.1...
tried updating and same happened null baseband null iemi.
SO went back to oos 3.0.1
Any solution you guys found out how to make thing back on track.
Unfortunately there is no way back now, have to wait for an oxygen update. But you can use cm 14.1, it works fine. Flash hydrogen 2.5 to fix your imei and install cm after.
Hi guys,
So I have a lot of data problems with Nougat roms (7.0 and 7.1.1).
CM based roms don't work for me, no data at all.
Last week I tried CitrusCaf 3.0 and my data worked a day then disappeared...
So I tried CitrusCaf 2.2 and it worked great until a few hours ago, I rebooted on TWRP didn't flash or do anything then rebooted the system and no data ....
I backed up and tried fix contexts, still no data.
I am on TWRP 3.0.2-2.
Do you think TWRP did something? Is it possible? Can we fix it?
I got the same problem, but only in 7.1.1 roms. If the roms were 7.1.0 or lower, data was working fine. I tried several firmwares and nothing. Only in cm based roms.
I have my problem fixed now. I have flashed a miui rom with miflash via edl(my bootloader was locked), and applied to official bootloader unlock.
I already got the official unlock, and I tried cm 7.1.1 and data works.
So I just need to grab a rom from here https://forum.xda-developers.com/redmi-note-3/how-to/links-direct-official-download-links-t3449488, reboot into edl, flash with Miflash and reboot then fastboot twrp, rom, gapps....
My bootloader is already officialy unlocked.
Well, at least it worked for me. You can try. If your bootloader is unlocked, you don't need to go from edl. You can do it from fastboot. You might need to flash firmware after coming from miui.
I just updated to Nougat and safetynet fails. I have not even rooted or put TWRP back on.
I'm using the EU ROM.
Previously I updated from 6.0 Sept to 6.0 Dec patch by flashing the boot and recovery image (from the Sept. firmware) on the device, then taking the update. And then flashing TWRP and magisk again.
6.0 Dec. to Nougat didn't go as well. I flashed the boot and recovery but the phone didn't boot... I used the Sept firmware as I do not have the Dec. firmware (I'm very adamant about getting the latest stock ROM for flashing purposes..). Anyways, so I had to flash the entire 6.0 Sept ROM again (I did not wipe my data) and then update to the December patch and then to Nougat. Would have been so much easier if I had the December patch ROM to flash...
I actually uninstalled magisk before all of this. But actually, magisk/root would be gone after flashing the boot image anyway.
After updating to Nougat I have not done any modding, but safetynet fails... Why is this? And I can only start from scratch from the 6.0 September patch...so starting over is not sounding good.
Possibly due to the unlocked bootloader from reading other threads...
d.casper.b said:
I just updated to Nougat and safetynet fails. I have not even rooted or put TWRP back on.
I'm using the EU ROM.
Previously I updated from 6.0 Sept to 6.0 Dec patch by flashing the boot and recovery image (from the Sept. firmware) on the device, then taking the update. And then flashing TWRP and magisk again.
6.0 Dec. to Nougat didn't go as well. I flashed the boot and recovery but the phone didn't boot... I used the Sept firmware as I do not have the Dec. firmware (I'm very adamant about getting the latest stock ROM for flashing purposes..). Anyways, so I had to flash the entire 6.0 Sept ROM again (I did not wipe my data) and then update to the December patch and then to Nougat. Would have been so much easier if I had the December patch ROM to flash...
I actually uninstalled magisk before all of this. But actually, magisk/root would be gone after flashing the boot image anyway.
After updating to Nougat I have not done any modding, but safetynet fails... Why is this? And I can only start from scratch from the 6.0 September patch...so starting over is not sounding good.
Possibly due to the unlocked bootloader from reading other threads...
Click to expand...
Click to collapse
I have the same issue with safetynet, I could only fix it while flashing this: Universal SafetyNet Fix v2 beta 4 !
https://forum.xda-developers.com/apps/magisk/xiaomi-safetynet-fix-t3600431
An unlocked bootloader will cause SafetyNet to fail in Nougat, at least in some devices (Pixel/Nexus, HTC 10/U11, OP3/3T too), could well be the reason it is failing.
I'm on a G5 Plus unlocked retus model XT1687 (I think). I was using Android 8.1 that came with the OTA update and decided to try a custom ROM.
So here is a list of most of my problems/f**kups:
Installed AEX based on 9, It bootlooped.
In the panic (first time messing with ROMs) accidentally deleted my backup.
Used this two guides to get out of the bootloop by fastbooting stock N firmware, it worked.
Flashed AEX again, this time It booted but It wasn't registering the fingerprint reader and I didn't have LTE and after and update It bootlooped again. Fastbooted stock firmware again, this time I had no signal altogether.
Flashed LineageOS based on Android 9, asked for password and then said that data was corrupted.
Formated, not wiped, tried again and this time had signal but no fingerprint, LTE etc.
Followed this instructions and got stock N working perfectly.
Flashed AEX again, no figerprint or LTE.
Re did previous step to get N again.
Flashed LineageOS again, had LTE but still no fingerprint reader.
Flashed stock N for the last time.
So right now I have Android N and can download the 8.1 OTA update but It fails to install. I would like to get LineageOS working or maybe AEX, but I don't really trust It (altough all the problems I had with It were most likely my fault). Or at least get stock 8.1 running again. this seems to be what I need to get stock 8.1 but after all that I did I'm not sure which steps I should follow.
Thanks for any help.
First thing to do after getting signal and LTE working is to make a TWRP back-up of persist and EFS folders.
Hi,
is anyone running latest B20 Oreo rom on an A2017U phone with Magisk v25?
When I patch boot image and flash it via EDL the phone doesn't boot it, I have to restore original boot.img to be able to boot android again.
Also, fastboot is not available in the stock EDL images, any idea how to get fastboot back?
Thanks
Hi,
For first, I flashed some ROMs earlier in my life but it was like 5 years ago. I'm not expert in that field. That being said... I'm running B02 Oreo ROM on A2017G but i had the same problem. I managed somehow to find somewhere (can't remember which site) that "Magisk 16.4 should work because 16.0 version had some problems". So I tried 16.4 and it worked for me. Unfortunately data partition, although it shouldn't after root, stays encrypted (in TWRP).
Also, if You boot to system and open Magisk manager it will show You that update is available. After updating to the latest app version it will say that your version of Magisk is not supported now and You should update it (meaning, flashing latest zip). I didn't try it but assuming that earlier it didn't want to boot with the latest version on "Magisk-v25.1.zip" it won't at this time too.
It's so hard to find any information about this phone this day's... I would love if someone knew how to disable this encryption. I tried I think every solution and nothings seems to work :/
I hope I'm not late and my post will help You