Hi, Hoping someone can help me with my recent goofup.
I was running a version of LineageOS. Now I hadnt used the tablet for a while during the xmas break. But the last week I took out and it had rebooted on me randomly a few times. After which I decided to put a stock rom back on.
i downloaded a stock rom from sammobile and attempted to install the ROM via odin but the tablet kept rebooting me after the install process
after a few failed attempts on various ROM. I thought it might be easier to go back LineageOS so i loaded twrp back on and have been trying ever since to LineageOS 16.0
I downloded the ROM's - lineage-16.0-20200128-nightly-gts28vewifi-signed. When I try to install the ROM after following the instructions of wiping the device I get this "zip signature verification failed"
my tablet is SMT-713 so am pretty sure gts28vewifi is correct. Please can someone help me out on clues on how I get passed the hurdle.
yes such a goofup. i should have just cleared the ROM instead of attempting to put a stock rom on
Which stock ROM did you download? Was it the latest software? Fair warning, I'm a T813 owner, so I don't know anything about the T713 really, just that it's fairly similar. If you installed the wrong ROM, or the an older one, Lineage won't install. I created this guide, for the T813 about updating the firmware on it because of the firmware / install issues on LOS.
Related
Hi there,
my 802 is running on TWRP after I updated to the latest stock ROM (30D Europe Open). Unfortunately due to problems mentioned in another thread I cannot install a custom ROM currently. Does anyone here have a mirror for me where I can download a TWRP backup of the stock ROM?
Thank you in advance
If you can't install a custom rom, what makes you think you can install a stock? It's pretty easy.
Very helpful... I flashed the latest KDZ on the G2, rooted it and installed TWRP 3.0.2.0, so far so good (believe it or not I flashed a dozen other android devices before). However when I try to install a Marshmallow ROM it gives me Error 7, so that means that getprop.device or so doesnt bring the correct value up. Now when I tried to switch to an older TWRP which is supposed to not have that Error 7 issue (2.7.0.0) I get an error saying I am missing the Loki files in the tmp folder. Now I do not know how to get around the Error 7 (the fix that is mentioned on here didnt work for me, brings up Error 6 instead) I would like to return to a stock backup.
How about giving me actual advice or leaving and letting other people help?
Edit: Booted in Download Mode and flashed v30D KDZ with the 2014 LG Flashtool. Works with Stock ROM for now
Hi
I have been trying for a few days now, but I cant seem to get my WileyFox storm to install OpenGapps (or any Gapps for that matter)
I have flashed the recover to use TWRP and installed [ROM][7.1.2_r17][OFFICIAL] AospExtended ROM V4.3 [OMS/DUI][kipper]
I then tried to install OpenGapps for ARM 7.1.2 Stock using TWRP to flash the zip.
The flash failed saying the device architecture was wrong
I have tried a variety of different types (ARM, ARM64, x86 & so on) with a variety of Android versions as a target.
But nothing works.
I thought the issue may be with the ROM or something so I installed AOKP
This still didnt resolve the issue.
It looks like I have been able to install BeansGapps without any architecture issue, however when I boot the system there is no change.
Am I missing a step, or doing something completely wrong?
Any advice would be appreciated
Its a bit odd replying to myself, but anyway...
OK so I managed to get this working.
It seems to have been an issue with TWRP 3.0.3 and my phone.
The recovery I was using is here:
https://forum.xda-developers.com/wi...t/recovery-team-win-recovery-project-t3367544
I had TWRP installed and then installed AOKP (as mentioned in my first post)
After many many attempts at getting GApps installed with TWRP I finally realised it might be the recovery.
I tried to reflash the recovery with a newer version, and as you can guess...it forced the phone into a bootloader loop
In desperation I went looking for the original twrp recovery and ended finding this page (I'd forgotten where I got the original image):
http://www.androidinfotech.com/2017/03/root-wileyfox-storm-twrp.html
Anyway, I installed that recovery which got me out of the bootloop
It said it was a cyanogenmod recovery...which I thought was odd
I tried to flash GApps and hey presto! It worked
Anyway leaving this here for info.
I hope no-one else runs into such hassle.
Had this exact same issue a few days ago. Searched around for a newer version of TWRP and that sorted it out for me. Couldn't find it on the official TWRP website though.
I hope this works for me to. I will try this tommorow. Breaking my head trying to get my storm to work. Lineage os is making my storm go in an infinite bootloop back to TWRP and every issue you have is relatable. Finding a TWRP for the storm also took me an hour and it doesn't work properly. I hope this works for me but thank you in advance
Hello,
Firstly, my device is the Asus Zenfone Max Pro M1 6GB Ram variant.
I was using the Pixel Experience rom as my daily ROM (I don't remember which build), it worked fabulously. But I hadn't updated it in a few months. So after enough procrastination I decided to update. I tried the regular software update method where you go to settings and check for updates, when it booted to TWRP recovery, it failed with an error. I thought it was because the update was the latest one and I was on an older build. So I tried doing a clean install by booting into recovery and wiping everything except internal storage. But the same error popped up again
I don't remember the exact error but it was an Error 7 and said something about the 'firmware version' required is 15.2016.1901.339 or newer. At first I didn't really get it and I kept trying again.
But after spending some hours it started making some sense and so I tried to install the required firmware. Even after doing so, the error kept showing up.
I thought it might be a ROM specific error. So I also tried Resurrection Remix (Pie version) but it yielded the same Error 7. This is the phone I use on a daily basis so I had to get it working somehow. So I flashed the stock ROM, the one that comes out the box. I flashed it using the flashall_AFT.cmd, I'm on the stock ROM now and it's obviously nothing like a custom ROM.
I also tried editing the updater script from the ROMs and deleting the part that was about the error (the first few lines). That didn't work either. The Error 7 was gone but another Error 6 popped up which said it failed to install.
I'd love to go back to using a custom ROM. It bugs me because I couldn't find any way to fix the error.
I'd greatly appreciate it if you can guide me step-by-step on how to install the custom ROM from where I am now i.e from the stock and fix the error.
I hope the above information suffices.
Thanks.
Azyaan124 said:
Hello,
Firstly, my device is the Asus Zenfone Max Pro M1 6GB Ram variant.
I was using the Pixel Experience rom as my daily ROM (I don't remember which build), it worked fabulously. But I hadn't updated it in a few months. So after enough procrastination I decided to update. I tried the regular software update method where you go to settings and check for updates, when it booted to TWRP recovery, it failed with an error. I thought it was because the update was the latest one and I was on an older build. So I tried doing a clean install by booting into recovery and wiping everything except internal storage. But the same error popped up again
I don't remember the exact error but it was an Error 7 and said something about the 'firmware version' required is 15.2016.1901.339 or newer. At first I didn't really get it and I kept trying again.
But after spending some hours it started making some sense and so I tried to install the required firmware. Even after doing so, the error kept showing up.
I thought it might be a ROM specific error. So I also tried Resurrection Remix (Pie version) but it yielded the same Error 7. This is the phone I use on a daily basis so I had to get it working somehow. So I flashed the stock ROM, the one that comes out the box. I flashed it using the flashall_AFT.cmd, I'm on the stock ROM now and it's obviously nothing like a custom ROM.
I also tried editing the updater script from the ROMs and deleting the part that was about the error (the first few lines). That didn't work either. The Error 7 was gone but another Error 6 popped up which said it failed to install.
I'd love to go back to using a custom ROM. It bugs me because I couldn't find any way to fix the error.
I'd greatly appreciate it if you can guide me step-by-step on how to install the custom ROM from where I am now i.e from the stock and fix the error.
I hope the above information suffices.
Thanks.
Click to expand...
Click to collapse
Most pie roms are base on the latest stock pie firmware, you probably need to flash that. Plus Ur twrp version is probably not the newest, all the links are available in the telegram group, and I'm not going to put them here out of respect for the devs. But .339 firmware is the Oreo firmware, I think the one u need to flash is the .050 firmware.
The telegram groups have them all and a little searching can give you all the links you need.
Azyaan124 said:
Hello,
Firstly, my device is the Asus Zenfone Max Pro M1 6GB Ram variant.
I was using the Pixel Experience rom as my daily ROM (I don't remember which build), it worked fabulously. But I hadn't updated it in a few months. So after enough procrastination I decided to update. I tried the regular software update method where you go to settings and check for updates, when it booted to TWRP recovery, it failed with an error. I thought it was because the update was the latest one and I was on an older build. So I tried doing a clean install by booting into recovery and wiping everything except internal storage. But the same error popped up again
I don't remember the exact error but it was an Error 7 and said something about the 'firmware version' required is 15.2016.1901.339 or newer. At first I didn't really get it and I kept trying again.
But after spending some hours it started making some sense and so I tried to install the required firmware. Even after doing so, the error kept showing up.
I thought it might be a ROM specific error. So I also tried Resurrection Remix (Pie version) but it yielded the same Error 7. This is the phone I use on a daily basis so I had to get it working somehow. So I flashed the stock ROM, the one that comes out the box. I flashed it using the flashall_AFT.cmd, I'm on the stock ROM now and it's obviously nothing like a custom ROM.
I also tried editing the updater script from the ROMs and deleting the part that was about the error (the first few lines). That didn't work either. The Error 7 was gone but another Error 6 popped up which said it failed to install.
I'd love to go back to using a custom ROM. It bugs me because I couldn't find any way to fix the error.
I'd greatly appreciate it if you can guide me step-by-step on how to install the custom ROM from where I am now i.e from the stock and fix the error.
I hope the above information suffices.
Thanks.
Click to expand...
Click to collapse
The latest Pixel Experience works great!
So you are on the Stock Firmware then.
1) Unlock the bootloader by Unofficial method (It will help when you want to relock it in future.)
2) Flash the latest TWRP Recovery.
3) Download whatever ROM you want to install and read all the requirements first! The error 7 you mentioned was the Firmware issue and could have been fixed by flashing the Firmware first and then the ROM.
GApps are not required for Pixel Experience as it comes with all the necessary Google Apps.
I have a Tab E 8 (SM-T377P) and I cannot get any version of TWRP new than 2.8.7.0 to flash, Magisk will not flash, and no custom roms will install.
I've tried both lineage 15.1 and 16, both the standard and GO versions.
It's on stock firmware, 5.1
I rooted with cfautoroot with Odin 3.10.7.
Hopefully someone has an idea on what I need to do.
:edit:
I was able to get magisk installed by rerooting with cfautoroot and then doing a full unroot and restoring bootimage with supersu. Still can't install any roms though
So I was able to update to Nougat using the rom posted in this thread. It was the ONLY place I was able to find the stock firmware. I was hoping that installing 7.1.1 would put me on a new bootloader/kernel that might allow me to install an Oreo rom.
Still, the only TWRP that I can get to boot is the one posted in this thread, which is 2.8.7. The dev posted links to 3.0.2-1 that do not work, but I've tried multiple different versions of TWRP, and they all boot loop and I have to reinstall 2.8.7 via Odin.
All roms say that they are intended for SM-T377P and cancel, although my device is exactly that.
So, after doing a total wipe and flash back to stock 7.1.1 using Odin, I was able to boot back into Download mode and install the latest version of the TWRP posted in this thread - https://forum.xda-developers.com/ga...official-lineageos-16-0-galaxy-tab-e-t3847488
Still won't let me install a custom rom though...
Alright got it up and running on Lineage 16.
I bought this off of eBay to use as a dashboard for my smart home. When I opened it and put it into download mode for the first time, I noticed that it said it was running a custom binary even though everything looked bone stock, it wasn't even rooted. I didn't pay it any mind and went about trying to root it and install TWRP as the dew guides stated. Nothing would work, so I decided to upgrade it to stock 7.1 since it was on 5.1. After I did this, I noticed that in download mode it stated that it was on stock binary and I was able to update to the most recent TWRP for this device. Then I was able to install Lineage and all is well now.
This thread doesn't appear to be getting any traction, but I figured I'd update it in case someone searches a similar issue in the future.
Krunk_Kracker said:
Alright got it up and running on Lineage 16.
I bought this off of eBay to use as a dashboard for my smart home. When I opened it and put it into download mode for the first time, I noticed that it said it was running a custom binary even though everything looked bone stock, it wasn't even rooted. I didn't pay it any mind and went about trying to root it and install TWRP as the dew guides stated. Nothing would work, so I decided to upgrade it to stock 7.1 since it was on 5.1. After I did this, I noticed that in download mode it stated that it was on stock binary and I was able to update to the most recent TWRP for this device. Then I was able to install Lineage and all is well now.
This thread doesn't appear to be getting any traction, but I figured I'd update it in case someone searches a similar issue in the future.
Click to expand...
Click to collapse
Thank you for documenting your progress.
I am in a similar situation.
I am the original owner of my t377p.
I'm going to try your steps to see if it will work for me.
UPDATE:
Flashing back to Stock and starting the process all over again, as you described above--fixed the problem. I am now running LineageOS16.
Thank you!
I'm glad it worked for you!
That's exactly why I updated the thread, I knew I wouldn't be the last one have this odd issue.
Do you have a copy of twrp the servers are down and I've been trying for week to download it
Hello,
i got a second phone for my GF as i was really happy with this phone and had it flashed without any issues before. This second phone is used and was over a year in use from the guy i've bought it from. It was 100% fine and he always used the shipped Android with it.
So i went on, got the latest TWRP for the phone. Flashed it without any issues and tried to install LineageOS from their website. Flashed it and tried to flash TWRP back as LOS replaces it. I wanted to use TWRP install the backups. But that's where it started to go wrong. Lineage seemed to have been gone from that point on. I couldn't get it to work again, even with reflashing and such. I've downloaded CRDroid and Paranoid and tried them but no luck. Non of them where booting up and TWRP stays showing a warning about "No OS installed".
After some more digging, i've found some posts stating that i would need newest firmware and venders. I've downloaded and flashed them but this made it even worse. The phone started to be stuck in fastboot. I got it working again by flashing latest MIUI version with Xiaomi Flash Tool.
Then i've installed TWRP again but somehow any rom i flash does not boot. The phone starts with the MI logo and flashes once and loads TWRP. There is no message about missing OS or any kind or error when flashing any of these roms.
Anyone able to help me?