Question TWRP for SM-A127M? [A127MUBU8DWC6] - Samsung Galaxy A12

Then... Every time I go to the official site (twrp.me) and download any updated version of TWRP (3.6.2 or 3.7.0) I get the surprise that it sends me to download mode and the only thing I have caught so far is the DT LOAD FAIL. It only happens with those versions, when I try it with an unofficial 3.6.0 version it works, I want to update to the latest version to avoid all kinds of problems.

Related

TWRP version issue : can't install cyanogenmod

Hello,
I have a perfectly working moto G 4g with cyanogenmod, and did the install very easily the first time. I am stoked with it so when my mother asked me for a new phone I got another MotoG 4G, and went directly to install TWRP and cyanogenmod... BUT :
- when I want to flash Cyanogenmod build zip, TWRP tells me the version is not supported by this cyanogen build.... apparently it wants version 0x411A and nothing else. The only version available on TWRP website is the newest 0.3.2.0 ....
- I have tryed another twrp version found online (a 2.7.8 not official) and it fails again to install Cyanogenmod, saying the TWRP version is not correct.
Where can I get the correct 0x411A version of TWRP ? Or is the message actualy is about something else ?
Best regards and thanks in advance for your help.
I was confusing Bootloader version and TWRP version. I used a tool found on XDA that has updated my bootloader.
Then i was able to install cyanogenmod but was stuck on the logo for the first boot.
Updated TWRP to the latest one and trying again, flashed darvin cache, and i am flashing nightly cyanogen+gapps.
I hope it'll work this time

Cyanogenmod update fails with error 7

Hello everybody, I hope to find help here.
My phone is the HTC One A9, Europe Version ("hiaeuhl"). Recovery is TWRP 3.0.2-0.
The background story is that I already managed to install Cyanogenmod after downgrading the original ROM to Version 1.10 and unlocked the bootloader with the HTC Unlock tool. I also managed to decrypt the device.
I'd like to update my system regularly, but unfortunately the last running version is the cm-13.0-20160904-NIGHTLY-hiaeuhl.zip from September 4th.
If I try to install the latest versions of Cyanogenmod (for example from September 9th) I always get the error
hiae.veryfy.trustzone() failed to read current TZ version: -2
Updater process ended with ERROR 7
I already tried to remove the lines that check this in the file updater_script inside the ROM's zip, then I could install the update, but afterwards I was stuck in a boot loop.
The error has nothing to do with the encryption, it apears with and without device encryption, and it has nothing to do which system (original or custom) is installed before flashing. It is also indifferent if I try the update via the system's update function or directly in TWRP. It's the fact that the Cyanogenmod version from September 4th is the last working for me. I definetly chose the right one for hiaeuhl, but it seems the developers have added a feature that makey my device incompatible to this ROM.
If there is anything I can do to update my system again, please let me know.
Have the same issue.
We need to update it, but I don't know how
jira.cyanogenmod.org/browse/NIGHTLIES-3351
Here is how I could solve the issue:
- flashing the latest stock firmware (and let it possibly completely update)
- install TWRP via fastboot
- from TWRP a factory reset
- install new version of the Cyanogenmod from TWRP
It worked for me, now I can use my beloved custom Rom
The Same Problem
I have exactly the same Problem, last working CM-Update was the 3rd September
Did you try my solution? With the older CM Rom versions for the HTC A9 you had to downgrade the stock rom, otherwise the CM wouldn't have started after the installation. Now it seems that the stock rom has to be the latest one (for me the 1.56) that you are able to flash the latest CM versions.
I do not have the latest stock Rom, my os is 1.27.161.6, seems actually cm needs 1.57, i am unlocked and s-off
You should probably find the right version for your phone here:
http://forum.xda-developers.com/one-a9/general/wip-ruu-htc-one-a9-t3240344
You should take the one with the right cid for your phone (which you can find with "fastboot getvar all" in the fastboot mode)
Thanks, i will try it and report
The last build i found for my version is 1.27. this is what i have
Hmmm... then I guess you have to wait until the new version appears in the forum. Seems that you have a device with vodafone branding. Since you already set S-off you also have the possibility to change your cid to one of the existing newer firmwares.
Is there a solution without going back to stock?
I'm not an expert, but I don't think so. It seems that the version number of the stock rom is stored somewhere even after changing the system to Cyanogenmod, and this version has to be the latest one. So unfortunately, as far as I know, you'll have to do the flashing procedure again...
thanks Silberhase, now i am on CM 13 again. Thats what i did: wrote Supdercid, searched a ruu-version for my build, found a 1.56.401.70 version, flashed this, then flashed twrp 3.0.2.0 again, factory reset - without factory reset i was not able to install cm, format data, recovery, latest cm update, flash gapps, restore my other data with titanium, done....
I'm glad to hear it worked for you!
Yes, but next Problem or better i actually do not know what problems will raise. After updating today successfully to last cm build phone is encrypted... TWRP requires password for decryption. Problem all over forums. Today i habe no fun to Format data again and restore all.
That's also what I experienced. Other users reported that the current TWRP version 3.0.2.0 can't handle the encryption of the HTC One A9. And every update will encrypt the device again. As a workaround you can do this:
- copy the downloaded update from /sdcard/cmupdater to the external memory card
- boot to the recovery (when asked for password push the cancel button) and install both the update and the gapps again (without wiping anything) from the memory card.
Its a pity, all worked perfectly. Installed last cm.. Which encrypted phone. Restored my backup. All Working. Updated apps, want backup again.... .... Error opening /system/addon.d (not a directory)..error in generating tarlist......Create tarfork()
Process Ended with error 255
I'm trying to help as much as I can even though I have no experience with all this. I never did a backup
Maybe you find the answer here:
http://forum.xda-developers.com/nexus-6/help/e-createtarfork-process-error255-t3302462
Maybe it helps to mount "system" in TWRP and then delete /system/addon.d. But it seems that this step has to be repeated before every backup.
Any news to this theme? Is Twrp able to handle A9 again in new Version?
The recent version 3.0.2.0 of TWRP is available for the A9 but can't handle it's encryption. It works anyway if you are willing to use some workarounds.

Need help with updating to latest OS

I recently downgraded from OS beta 16 to OS 9.5.2. Now I want to upgrade to the latest one OS 10.3.3. i even downloaded the full version. but when trying to install it says failed.
Good evening mate,
well, in your case, you should just use the MSMTools. It's a software which we can use to install any version of the OOS, but obviously, each version flashes the build it was built for.
Just go to this thread: https://forum.xda-developers.com/oneplus-7/how-to/op7-unbrick-tool-to-restore-device-to-t3954325/
thanks to @Some_Random_Username
There, you should see some spoiler buttons, just choose the one you want, download the software and then follow the instructions at the bottom of that post.
Remember, using this software LOCKS your bootloader and also WIPE everything on the device.
My advise is to choose GM57BA 10.3.2, and then just update to 10.3.3 by OTA.
sekk said:
Good evening mate,
well, in your case, you should just use the MSMTools. It's a software which we can use to install any version of the OOS, but obviously, each version flashes the build it was built for.
Just go to this thread: https://forum.xda-developers.com/oneplus-7/how-to/op7-unbrick-tool-to-restore-device-to-t3954325/
thanks to @Some_Random_Username
There, you should see some spoiler buttons, just choose the one you want, download the software and then follow the instructions at the bottom of that post.
Remember, using this software LOCKS your bootloader and also WIPE everything on the device.
My advise is to choose GM57BA 10.3.2, and then just update to 10.3.3 by OTA.
Click to expand...
Click to collapse
Yes I tried using it yesterday but I stupidly updated to 9.5.8. But I have the same problem not getting any OTA updates. Now I will install 10.3.2. But is it guaranteed to get OTA since I dint get any when 9.5.8 was installed through MSMTools. Thank you
JNRao said:
Yes I tried using it yesterday but I stupidly updated to 9.5.8. But I have the same problem not getting any OTA updates. Now I will install 10.3.2. But is it guaranteed to get OTA since I dint get any when 9.5.8 was installed through MSMTools. Thank you
Click to expand...
Click to collapse
Yes, you should get every available OTA... But if you don't, just downlaod the app Oxygen Updater from play store, set it up nad use it to download the updates!

older versions of TWRP

where can i download older versions of TWRP
I have tried what is on the current page for One plus 7 pro from .80 to .70 and I cannot install a single rom with any of them.
I wouldlike to try and older version of TWRP to see if this helps
Thanks Bart
This be closed I found it a much older version on the TWRP site itself and that actually allowed me to to flash the ROM

Flashing an older Magisk version with an old TWRP version to ensure compatibility, and updating Magisk later

Hello and Happy Holidays to everyone. The TWRP version of my tablet (SM-T285) is 3.1.1, which is an old version from March 2017. Now I flashed the latest version of Magisk with it, but it failed and perhaps left a partial root due to being flashed by an older version of TWRP.
So I flashed my tablet's stock ROM and started everything over again.
I thought it may be a good idea to flash a version of Magisk from around the same time my TWRP build is released to ensure compatibility, which happens to be version 12. I'll then update Magisk to the latest version later. However, since I'm a newbie at these things, I decided to ask in this forum first if what I'm going to do is fine. Will it be okay if I do so?

Categories

Resources