Phone is Lenovo A6000, not plus. I installed multiple TWRPs, 3.1.0 and 2.9 something.
I even installed CWM, still couldn't boot to the recovery.
Now, I know how to flash with fastboot, and I know how to boot. Booting doesn't work at all, it says "booting" and never finishes.
Flashing says "okay" and I reboot, do a reboot to recovery, and I get put into bootloader/fastboot.
Any help? I just bought the phone today, no one messed with it.
Edit: Nevermind. CWM installed. How do I install TWRP, so it works? Also, forgot to mention that the phone has the latest stock rom, 4.4.4.
Edit#2: While trying to install "TWRP-3.1.0-Lenovo-A6000.img",
I got an error.
"Can't open /tmp/update.zip (bad)"
"Installation aborted."
Edit#3: Same error with multiple TWRP images.
First of all the twrp 3.1.0 is meant for nougat roms. Since you are flashing that recovery on KitKat rom which it won't support. So first try updating phone to stock lollipop. Then flash twrp 2.8. then take a complete backup(most important) and save it on SD card. After that flash any rom you want. If you are flashing marshmallow or nougat rom then after flashing rom flash 3.1.0 twrp.
I have long ago (10 minutes after last edit) fixed the problem already by flashing stock firmware through some weird software, and then started updating to latest lollipop firmware, and then installed TWRP 3.1 and then installed RR android version 7.1.2. But, thank you for trying to help. I hereby ask a moderator to close the thread because the problem was resolved. Thank you.
Related
I'm rooted correctly and have the newest TWRP recovery installed. I've successfully flashed the update for a newer recovery than the stock one when you first put a custom recovery and I flashed an update for the radio on my d800.
I haven't tried flashing any stock roms only new 4.4.1 or.2 Roms. My question is did I miss a step, do i need to flash something else like the latest OTA then wipe again and go for AOSP. I'm by no means new to flashing.
When i try to flash it this is what I get
"error executing updater binary in zip "
Any tips?
Nvm. I switched recovery. Used the unofficial CWR and even though it holds up on clearing the cache it installed beautifully.
So I was on a early January build of Mahdi Roms. I decided today to update it. I was told to wipe everything flash the radio zip, cloudy rom. let it boot up then flash the new mahdi rom.
However, im on twrp 2.6.3. and when i flashed the radio and flashed the stock rom it booted up into twrp instead. I tried wiping and reflashing but it failed. I tried to reboot but it said my device isnt rooted and need to install SU so i swiped to continue however my device froze on the LG logo for about 10+ minute. So here I am still with no working phone for about 2 hours
any idea as to what to do?
Hi all,
I was running the official Google 5.1.1 version until this morning. I now did an oem unlock using fastboot and installed the latest twrp recovery 3.0.0, and finally copied overy CM-13 nightly (and Chroma-2016-02 for testing purposes) using adb.
Flashing itself work flawless, there is no warning or error message, but when hitting "Reboot" within twrp the Google logo shows up for a few seconds and it directly boots into twrp again. This is with both, CM-13 and the latest Chroma.
So I basically cannot get my Nexus-4 bootet regulary any more.
Any ideas what the problem might be?
Any help is welcome,
regards, mistersixt.
Mmmh, strange, I did a factory installation (latest 5.1.1 from Google) and started the same thing from scratch ... and guess what... the system is booting fine now.
No idea why it did not work on my first attempt .
Regards, mistersixt.
mistersixt said:
Hi all,
I was running the official Google 5.1.1 version until this morning. I now did an oem unlock using fastboot and installed the latest twrp recovery 3.0.0, and finally copied overy CM-13 nightly (and Chroma-2016-02 for testing purposes) using adb.
Flashing itself work flawless, there is no warning or error message, but when hitting "Reboot" within twrp the Google logo shows up for a few seconds and it directly boots into twrp again. This is with both, CM-13 and the latest Chroma.
So I basically cannot get my Nexus-4 bootet regulary any more.
Any ideas what the problem might be?
Any help is welcome,
regards, mistersixt.
Click to expand...
Click to collapse
Same here. Running stock until today, wanted to see a different ROM, flashed TWRP 3.0.0, it refused to boot anything else. Tried to flash DU, then tried Chroma. Did a full wipe, then an advanced wipe selecting everything, then a full format, same thing. Installed TWRP 2.8.7, same thing. Finally installed latest stock, it is now booting, optimizing apps. I don't know if installing a custom rom will work or not yet.
Edit: Yeap, after flashing stock 5.1.1 and installing TWRP 3 again, the phone is now booting into DU.
First time I did a wipe with TWRP, it complained that it couldn't mount /data. Since this is the first time doing it, I assumed it was normal. After going through a full format, it didn't complain about data anymore, but it did complain about something to do with /dev/zero and another file under /dev/. I assume it was trying to dd /dev/zero to a file under /dev/ that didn't exist.
+1
Done the whole process from scratch again and worked like a charm
Hello, same story here.
First I:
- unlocked bootloader
- flashed TWRP (last version)
- flashed Chroma and Gapps
- reboot
=> I consistently rebooted on TWRP. No way to properly install the ROM. No error message at all.
Then I found this thread, and did as described:
- flashed the latest stock ROM
- flashed TWRP again (took me ages to manage to do this: TWRP would not install. I don't know how I finally did it, but at some point it suddenly worked. Probably a driver problem)
- flashed Chroma and Gapps again
Bingo, this time it worked! I don't know why it didn't work the first time. Could it be linked to the bootloader unlock thing?
I officially upgraded to 3.0.2, unlocked and rooted my phone.
It was fine for the first few times I flashed multiple ROMs. But ever since I flashed Exodus, I keep having issues switching to different ROM.
A week ago, I flashed "Switch to OOS3_H2OSMMv7" zip and was able to flash Resurrection Remix, but today when I tried switching to CM13 or PA it gets stuck at flashing the ROM zip. I tried flashing the firmware zip again and flash the ROM, but to no avail. It won't flash any ROMs now, just stuck at recovery while flashing the zip.
I have a working fastboot and recovery mode though, so I'm trying to avoid flashing the entire factory image but that seems to be only option left. Does anyone have any clue as to why this is happening and how I can fix it?
Edit: Resurrection Remix gets installed fine, CM13 and PA still giving me issues.
Edit: I downloaded the latest version of CM13 and it works. Earlier I was using June 30 build which seems to have issues with the new firmware. I'll try out the new PA build to see if it fixes that too.
What error does your recovery gives?
Do you have Data Backup?
Can you access ADB while in Recovery?
piyushmodi01 said:
What error does your recovery gives?
Do you have Data Backup?
Can you access ADB while in Recovery?
Click to expand...
Click to collapse
It does not show any error as it just looping while installing the zip. I have to force shut down the phone to exit it.
Yes, I have backed up all my data
Yes, I am able to access my phone in both ADB and in fastboot modes.
After flashing Custom ROM, Wipe data, cache, d-cache and then reboot.
If still doesnt work try flashing another custom ROM. You can use adb-sideload to flash another zip in recovery mod.
Hi Guys,
i lately got on old Samsung Tab 9.7 with an official Android 7 Nougar running on it.
I decided to flash twrp_3.1.0-1_sm-t550_13317 with Odin3_v3.10.7. I followed the steps ashyx described in his thread. So far so good..
Afterwards I installed SR5-SuperSU-v2.82-SR5-20171001224502 from SDCard and it prompted to reboot... now there is the problem.. It won't reboot. It says "Check failed" and I have to factory reset it. When pressing the button it boots into twrp and I can only spot red lines until it reboots with kernel binary and I'm back at the same point.
Any ideas what to do?
btw. are there any new version of twrp , SuperSu or Magisk I can use? Couldn't find any newer versions. I also search for any ROM which has the most up-to-date status (if there are any xD)
Thanks guys
Not my type of tablet but when the SM-T585 had those issues it was a wrong version of TWRP, so maybe look into that.
And SuperSU, really? That's been dead for years, use Magisk instead. It has a whole subforum here on XDA.
/edit: I managed somehow to install latest twrp and lineageOS.. but on first boot it brings up an encryption error.
"encryption was interrupted and can't complete..."
I need to factory reset the tablet... but with that i run again into a bootloop. I can't wipe "data" via twrp Error 8 was it, i think at least ^^
/edit2: I'd go with magisk... but I only find the .apk .. what do I have to flash in twrp?
/edit3:
Managed to reinstall twrp with latest verion twrp-3.5.2_9-0-gt510wifi.img. wiped all data ... Installed Magisk-v23.0 afterwards lineage-18.1-20211108-UNOFFICIAL-gt510wifi . But again.. encryption error on Lineage boot.
Problem solved.
reverted to complete stock, afterwards flashed twrp, installed magisk + lineage 18.1 + OGapps 11.0.
Now it's running.