twrp 3.2.1 error 255 - LeEco Le 2 Guides, News, & Discussion

good afternoon
Yesterday I had a problem, which I do not know how to solve and if it could have happened to any of you?
I have the official twrp 3.2.1 installed on my LE2 X527, and wanted to install another rom on the phone.
I did the backup of the rom I had, and I installed the new one, it went well, but I did not like this rom, I went back to the twrp and erased everything, and here my problems begin.
I tried to restore my old one, and at the end it was 255, and I did not install it.
I went to see youtube what was error 255, and there they said it could be by having my twrp in 32 bits, and it would have to have twrp in 64bits so it does not happen.
Someone can help me in this, because maybe someone has already gone through this.or it will pass.
thank you

Related

[Q] imei problem after rom flash

If someone could help me I'd be very grateful.
I have cwm 6.0.3.2(0611) but was running TWRP previously. The first custom rom I installed was crdroid and today I tried to install graviton rom. I did this using TRWP. However, after installing, my SIM was not recognised and I had no IMEI and the baseband version showed 'unknown'.
I then flashed CWM and tried to re-install crdroid with the latest version but came up against the same problem. However, after installing this I also had no bootanimation. After browsing this forum for an answer, I couldn't really find anything that helped too much so I did a nandroid restore.
This worked and put me back to my stock rom.
I then tried to reflash the latest crdroid but the problems have all returned again.
Can anyone help me? I'd like to be able to flash the roms I want again but it seems that anything I'm doing is wiping the IMEI/baseband/bootanimation.
welshyoot said:
If someone could help me I'd be very grateful.
I have cwm 6.0.3.2(0611) but was running TWRP previously. The first custom rom I installed was crdroid and today I tried to install graviton rom. I did this using TRWP. However, after installing, my SIM was not recognised and I had no IMEI and the baseband version showed 'unknown'.
I then flashed CWM and tried to re-install crdroid with the latest version but came up against the same problem. However, after installing this I also had no bootanimation. After browsing this forum for an answer, I couldn't really find anything that helped too much so I did a nandroid restore.
This worked and put me back to my stock rom.
I then tried to reflash the latest crdroid but the problems have all returned again.
Can anyone help me? I'd like to be able to flash the roms I want again but it seems that anything I'm doing is wiping the IMEI/baseband/bootanimation.
Click to expand...
Click to collapse
You could try backing up your EFS partition and grabbing the Modem you had in your stable ROM. Once you flash, you could try to restore the EFS (on the rom that you have the issue on) and flash the modem if the unknown baseband/lost imei continue after that.
Cheers, I did think of something like that - I saw a few threads which suggested flashing the modem (twice?) but it seemed to me that I should be able to flash a rom without having to backup efs and restoring each time (the issue happens with every rom flash now for some reason). I saw a few similar threads but nothing with the exact same problem, and no real solutions so far.

Flashing another ROM turned into some bigger problem

Hi guys, the times has come for me to open up my own account - I screwed up. I hope this is the right sub forum and apologize if it is not.
LG G2 Germany, formerly: TWRP recovery, Paranoid Android 5.1.1
Loved the rom but there were some issues like the screen turning off and on randomly, wouldn't accept pin right away, so I decided to go for CM 12.1.
Booted into recovery, factory wiped, tried to flash the .zip, but neither the rom nor the gapps would even begin to flash. It just said error.
Went crazy, tried some other CM versions, none of them worked. I've never had this issue before, when I flashed PA it all went just peachy.
Went even crazier and I can't really remember what I did in my panic spiral, but I somehow ended up with a soft-bricked phone. Managed to re-install the LG firmware .kdz, however, only the 4.2 one worked (4.4 gave me a bootloop.)
Now, getting this bad boy rooted and ready to flash custom roms is somewhat of a problem. I managed to get it into recovery though (after some issues with the recovery image), but flashing CM still won't work. Same error as before. I think there may be something wrong with the recovery image. I still had the image .apk from the first time I rooted my phone (also with 4.2) and it worked just fine so I figured I'd just use it again and do it like I did it last time. However, I am able to get into recovery mode. I've tried ClockworkMod and TWRP, but as a result of my panicking, it's just really a big ol' mess right now. I hope I've included all the info needed.
Please help, I'm actually lost.
Are you flashing the latest TWRP which is 2.8.7.1?
http://blastagator.ddns.net/twrp.html
Hey, thanks for replying. At the moment it only boots into recovery, unfortunately. ADB does not work, even after re-installing the usb drivers. My computer recognizes the device now though, but I can't get any files onto that thing at the moment.
Edit: It's not the latest TWRP
If you install the latest TWRP, you may be able to boot into TWRP and copy over a ROM to flash.

Recovery Loop Help!!

I was running CM 14.0 with TWRP. I did a OTA download through CM Updater to 14.1 nightly. The phone rebooted to recovery and nothing happened. I manually found the OTA under sdcard/cmupdater and flashed the file. Now, whenever i try to boot the phone, it keeps going into recovery. I tried restoring nandroid backup, wiping everything and installing the older cm14.0 zip and nothing worked, phone keeps going into recovery, what can I do, please help!!
I think there are few users reported same issue before.
Try to check the ROM thread. If Im not mistaken, the solution has been posted there.
Hope this help. Good luck
Sent from my Nexus 4
Sorry, I panicked and didnt look through the forums thoroughly before posting. I managed to boot my phone up by flashing factory images and going back to stock. Afterwards, I tried to install the CM 14.0 again (StephanMC's build) which was working fine before I tried the update process. TWRP throws error 7 when I try to flash it. I looked around and found that the problem can be fixed by editing the Meta-INF, but I did not have this problem before, did I mess something up in the factory image flash process?
Would it be wise to go ahead and force install the ROM by editing the zip?

G900F Bricked after update: cm-14.1-20161219-NIGHTLY-klte.zip

Hello all.
I have a Galaxy S5 running cyanogen 13 ( cm-13.0-20161013-SNAPSHOT-ZNH5YAO21L-klte.zip ). Last night I updated it with the cyanogen tool, as usual, thinking that I was just getting a more updated version of cyanogen 13, but apparently I got it working with android 7.1.
As gapps were not working, I downloaded both 7.1 gapps, and cm-13 to try to install gapps or comeback to cm-13 if it did not work.
The problem is that I had no chance to test it. I rebooted the phone with the option "recovery reboot" and after it turned off it showed something like "no command", then it got to the first screen (recovey booting... in blue, samsung galaxy s5 white logo...) and freezed there.
I've tried every key combination and it does change nothing. I've read in another forum an user having the same issue so I advice you to not install this update. At least not from CM13. I will update when I get more details from the other users or if one of us success while trying to unbrick.
I suggest you to install twrp with Odin so you are sure that you have working recovery. Then backup what left of this not working ROM and download cm 13 and gapps for it. Then wipe system partition and install those two. By some chance you will end up with working ROM. If it works, I suggest you to backup all data with titanium backup and clean flash cm 13 to be sure that you got rid of all the issues... If cm 13 doesn't boot also wipe data and start on new.
I hope it helps you
LGaljo said:
I suggest you to install twrp with Odin so you are sure that you have working recovery. Then backup what left of this not working ROM and download cm 13 and gapps for it. Then wipe system partition and install those two. By some chance you will end up with working ROM. If it works, I suggest you to backup all data with titanium backup and clean flash cm 13 to be sure that you got rid of all the issues... If cm 13 doesn't boot also wipe data and start on new.
I hope it helps you
Click to expand...
Click to collapse
Hello!
Thank you very much, as I found the problem was the recovery I've re installed TRWP. CM14 was replacing it each time I installed it by ODIN so i had to start it just directly after flashing it (without letting the phone boot) and i've installed last CM14 klte file and 7.1 GAPPs
Now all is working , I hope it can help others with the same problem
Thank you!

A20 stuck in SANSUNG logo screen

After trying a bunch of options, I had to turn to asking for help please.
I installed TWRP and rooted via Magisk a few weeks ago. Everything worked perfectly for a few weeks. Then, suddenly the screen had an issue where the touchscreen stopped working. I could boot back to TWRP but the touchscreen was still not working. After allowing the battery to drain to 0, the touchscreen started working again.
I got into TWRP and tried to restore a previous backup, but suddenly the screen got stuck at the SAMSUNG screen.
Since then I have tried a factory install, a wipe of the data/system file, I tried an install from a stock image I got here, etc. Somewhere in the last 3 days (yes, been trying for 3 days) I managed to wipe the OS.
TWRP 3.3.1-0 is still installed, and I can access that. Note: I see the following in RED when I try a restore.
E: FBE found but FBE support not present in TWRP
Could anyone please assist in this ?
MorneDJ said:
After trying a bunch of options, I had to turn to asking for help please.
I installed TWRP and rooted via Magisk a few weeks ago. Everything worked perfectly for a few weeks. Then, suddenly the screen had an issue where the touchscreen stopped working. I could boot back to TWRP but the touchscreen was still not working. After allowing the battery to drain to 0, the touchscreen started working again.
I got into TWRP and tried to restore a previous backup, but suddenly the screen got stuck at the SAMSUNG screen.
Since then I have tried a factory install, a wipe of the data/system file, I tried an install from a stock image I got here, etc. Somewhere in the last 3 days (yes, been trying for 3 days) I managed to wipe the OS.
TWRP 3.3.1-0 is still installed, and I can access that. Note: I see the following in RED when I try a restore.
E: FBE found but FBE support not present in TWRP
Could anyone please assist in this ?
Click to expand...
Click to collapse
That's really strange.
What is your firmware date?
physwizz said:
That's really strange.
What is your firmware date?
Click to expand...
Click to collapse
I used this Firmware: XFA-A205FXXU2ASFA-20190803073130
MorneDJ said:
After trying a bunch of options, I had to turn to asking for help please.
I installed TWRP and rooted via Magisk a few weeks ago. Everything worked perfectly for a few weeks. Then, suddenly the screen had an issue where the touchscreen stopped working. I could boot back to TWRP but the touchscreen was still not working. After allowing the battery to drain to 0, the touchscreen started working again.
I got into TWRP and tried to restore a previous backup, but suddenly the screen got stuck at the SAMSUNG screen.
Since then I have tried a factory install, a wipe of the data/system file, I tried an install from a stock image I got here, etc. Somewhere in the last 3 days (yes, been trying for 3 days) I managed to wipe the OS.
TWRP 3.3.1-0 is still installed, and I can access that. Note: I see the following in RED when I try a restore.
E: FBE found but FBE support not present in TWRP
Could anyone please assist in this ?
Click to expand...
Click to collapse
Reflash stock firmware via ODIN
then reinstall twrp
Or if you don't have a pc download a GSi in another phone with a SD card , extract the .img GSi file , put the sd card in your phone and flash it via Twrp to SYSTEM
Also use twrp 3.0.2-0 because newer versions are reported to have some problems
Imyou said:
Reflash stock firmware via ODIN
then reinstall twrp
Or if you don't have a pc download a GSi in another phone with a SD card , extract the .img GSi file , put the sd card in your phone and flash it via Twrp to SYSTEM
Also use twrp 3.0.2-0 because newer versions are reported to have some problems
Click to expand...
Click to collapse
OK, two main questions.
- Which GSi would you recommend for the A20.
- How do I downgrade to TWRP 3.0.2-0, as I could only find the one version for the A20
MorneDJ said:
OK, two main questions.
- Which GSi would you recommend for the A20.
- How do I downgrade to TWRP 3.0.2-0, as I could only find the one version for the A20
Click to expand...
Click to collapse
GSIs are here
https://forum.xda-developers.com/galaxy-a20/how-to/gsi-galaxy-a20-t3964546
Not sure about 3.0.2-0
I use this one
https://forum.xda-developers.com/ga...p-samsung-galaxy-a20-custom-recovery-t3955271
MorneDJ said:
OK, two main questions.
- Which GSi would you recommend for the A20.
- How do I downgrade to TWRP 3.0.2-0, as I could only find the one version for the A20
Click to expand...
Click to collapse
Gsi* - I recommend HavocOs
Very stable , everything works and no bugs so far.
Been using it as my daily driver for like 2 weeks!
And as for twrp you can retry with the one you have but I don't know if the problem will happen again.
I'm sorry I have lost the link that I found my twrp
OK. I have tried a few GSI roms, but all of them the same problem where the phone gets stuck in the bootloader. I finally just decided to go back to standard Samsung ROM, but my touchscreen is dead. I am currently setting it up using an OTG connector with a USB mouse ....
Any idea what I can try. Yesterday the touchscreen was working in TWRP, but, after numerous retries and flashing that is no longer working. I do not want to chuck the phone ...
MorneDJ said:
OK. I have tried a few GSI roms, but all of them the same problem where the phone gets stuck in the bootloader. I finally just decided to go back to standard Samsung ROM, but my touchscreen is dead. I am currently setting it up using an OTG connector with a USB mouse ....
Any idea what I can try. Yesterday the touchscreen was working in TWRP, but, after numerous retries and flashing that is no longer working. I do not want to chuck the phone ...
Click to expand...
Click to collapse
Touch screen not working.
I would take it back under warranty.

Categories

Resources