Ok so i did the following in this order.
Installed twrp 3.3.1.0 via odin which worked perfectly.
Installed lineage os 17.1.
Installed no verify.
Installed gapps.
Had it all up ad running perfectly fine for a few weeks.
I decided to try a different os called pixel experience which i also got running just fine.
However i didn't like it and decided to go back to lineage os.
I used the exactly the same steps i used previously to wipe the system os inside twrp.
however when i tried to wipe the data it failed and then my phone auto rebooted and now i can't do anything.
It wont charge so needs to be plugged in to even turn on.
Once its plugged in it auto boots to a twrp splash screen and is stuck there and cant get into the twrp menu do install an os.
I can get into the download mode and odin detects the phone so i tried reinstalling twrp which says it was successful but when i reboot it gets stuck in the same splash screen.
i also tried reinstalling the original bl ap cp csc files that i had previously had installed which after many attempts finally go them to install but still loads the twrp splash screen and gets stuck there.
ive tried using adb fastboot loader using cmd but it doesn't detect the device so cant do any that way at all
i fear my phone is completely bricked and unusable please if you can offer any help would be much appreciated as im at the point where im looking to buy another phone as this is my old phone atm.
HI
Can't you come back to the last official firm for our S7 ?
It is an Oreo 8.0.0 firm
Have a look at samfirm ( or updato) and search for GF930FXXS8ETC2_xxx.zip
U flash that with Odin ( 3.13.1 I think) and yr phone is back to life !!!
Hope this helps
Related
I rooted my phone (regular s6, not edge) via the pingpong root method and everything was going swimmingly. I installed the twrp app from the play store and went to try and make a backup but after executing the backup it wouldn't reboot, the phone was normal as if i hadn't pressed anything. I installed twrp recovery via the app and went to reboot so I could backup manually but when I went to do so my phone wouldn't boot up. It is stuck on the GALAXY S6 Powered by Android screen.
I have seen similar posts which say to flash stock recovery via oding and re-root. However I dont have access to a windows pc at the moment and am stuck trying (and failing) to use jodin on my mac. It basically just doesn't work. I followed every step and it will not flash cf-auto root, I checked I had the right version and everything but it refuses to do anything so I am up ****s creek as they say...
Any help would be appreciated
Dear all,
I have read through most (if not all) the other "bricked" device threads, but they don't really fit my problem.
I was on TWRP (sthg) and CM 12.1 (latest) here from the forum.
Everything worked fine for ages.Yesterday I used the device to the latest miliAmpere and only later the connected the complete empty Tab to the Power and restarted it.
Next morning the device showed "Encryption failed" and something that I have to do a factory reset. There was a "reset"-button, but I didn't used it and shutted down the Tab via the power Off function.
Since then the device is not reacting. Currently it is bootlooping into TWRP (!). I cannot switch it off and it actually gets rather hot. The only way to stop this "cycle of death" is to go to download mode...
I already tried to change the recovery to CWM and also to TWRP again via ODIN. ODIN worked fine, but I still cannot start the recovery. TWRP makes a boot loop with its logo and CWM loops without showing anything.
I wonder what will be the next best steps. Odin is working fine, so I don't want to ruin that as well.
What do you think? Is the Bootloader corrupt?
Why does it always boot into recovery (I can't get into a System-Bootloop)?
Any help is really appreciated!
Best,
Jan
After I have reinstalled the original firmware from sammobile, I could boot into recovery. I then factory reseted, flashed TWRP via ODIN and switched back to CM12.1.
I lost all my data, but at least I still have my Tab
Best,
Jan
I was trying to get lineageos on my s6 edge+ but it is stuck in a samsung logo loop after being unable to flash the rom and now it won't go back into TWRP either.
Initially I flashed the official TWRP for the zenlte which worked fine, it just did not want to install the rom due to apparently not having any device data. (Rom is for zenlte, this device is . (or something along those lines))
after a few attempts and doing a quick wipe I flashed an unofficial twrp and thats when it started looping without being able to get back into recovery mode.
Download mode does still work after a power off but flashing the official twrp again makes no difference.
This is a little beyond me and I'm not entirely sure what is going on.
The last phone I installed a custom rom on was an s4 so I'm a bit out of the loop with this new security stuff. I would have expected to at least be able to boot back into twrp.
Ok some progress:
Recovery mode worked again after leaving phone off (but still attached to computer) for a while. (I had given up but decided to try again after a few hours)
Partitions were missing / corrupted. Did a full format.
Installing rom still gave the 'device type is .' message.
Edited the rom zip to allow "" and " " ( in META-INF\com\google\android\updater-script )
Flashed rom + gapps + magisk in 1 go.
This ended up in LineageOS trying to start but rebooting into recovery after about 5 minutes.
Re-instralled just the rom, this gave a few errors about Magisk missing, re-installed Magisk as well before wiping cache and rebooting.
Now it came up with the welcome screen rather quickly.
Weird, but problem solved any ways.
Thanks! That was also my problem.
Hello,
I'm running the samsung galaxy a8 (2018) canada version, so sm-a530W
Recently tried installing twrp, everything was looking okay, i booted up got to regular booting and accessing the phone, then i powered it off and powered it back on and i'm stuck at Downloading mode only.
What are my options here? I can't seem to boot into twrp now either or flash it again, seems to go back to download mode regardless
Hm actually so I just went into odin and flashed twrp again but let it auto-reboot this time and it lets me get through to my twrp and system but turning it off again leads it back to downloading mode, do I need to reflash a boot image and where do I get one?
Realized I may not have turned on USB debugging when I installed twrp, is that what's causing all these issues? and how would I best resolve this
After installing TWRP you have to treble-ize your phone. For this, reboot into TWRP with the given option. Then flash TWRP treble so you avoid getting locked out. Details of the procedure in this thread. Depending on your android version steps might be different so make sure to read everything and follow it carefully.
How can in get out of this boot loop, any advice, answers, help appreciated?
As background my Lenovo Tab 4 10 plus (stock 7.1 rom) had a failed SD card so I replaced the card and factory reset and thought I would try TWRP, Linageos 17.1 with magisk and relevent gapps - this all worked fine other than a Skype issue. I then found an 18.1 rom and tried that and this is where it seems to have gone wrong I set it up in the same ways as the 17.1 rom but with Andriod 11 gapps to suit, did a factory reset and 30 seocnds in I got the boot loop.
To fix it I tried going back to the 17.1 rom set-up that had worked but this then boot looped even with a full recovery reset. I have gone back to the stock rom backup in TWRP again with a recovery reset same boot loop. I have even used the Lenovo recovery tool to EDL mode flash a newly downloaded stock rom and it's still boot looping. I can only think that the 18.1 andriod 11 rom changed something fundimental but I can't find what?
Further I have another problem, the EDL flash worked but it locked the bootloader, however as I can't get in to Andriod with the boot loops, I can't switch ADB mode on so I can't unlock the bootloader to get TWRP up again.
So is there a way to start ADB without access to develeoper settings maybe through fastboot or recovery which I can get in to? Unlock the bootloader without ADB? Does anyone know why after the 18.1 Andriod 11 based rom, I have this continous boot loop?
I have a tb-x704f wich was totally caught in a boot loop, but I manisched to get back to working stock.
I was running firmware s000056 when I flashed twrp without backing up anything. I thought I never would have to go back to nougat, but standby time on lineage os was just not good for me, as I only use my tablet maybe half an hour a day, and I had to charge several times a week nevertheless.
So I tried to get back to stock and awesome standby time.
It was not easy bootloop after bootloop.
Tried Lenovo rescue and smart assistant multiple times, factory reset before and after flash, without SD card inserted etc, but bootloop.
Tried flashing the rom downloaded from the rescue tool with qfil but same result.
I then tried flashing the files with miflash 2016.08.30.0 still the same rom as I thought it had to be s000056. Miflash stopped halfway with some kind of error.
I then downloaded a stock rom from lenovo-forums.ru http://lenovo-forums.ru/topic/24135-lenovo-tab4-a10-plus-proshivka-tb-x704f_s000037_170703_row_qfil/
from the link in the discussion in the bottom of the site.
I had twrp still so from there I got into terminal and wrote "reboot edl" to get into emergency download mode and then flashed away. I presume that I could just as well had gotten in to edl mode by pressing vol+ and vol- simultaneously and then connected to PC holding those to buttons pressed. When the tablet was finished it was off, so I started going to recovery and wipeed cache and did a factory reset. Then booted and instead of bootloop it showed the Lenovo screen with a progress bar underneath. I successfully booted and took a update and then i am back to stock s000056.
The rom I got from lenovo-forums.ru stated it was only for EU and wi-fi model only. I am in Denmark and my tablet is WiFi only.
I think chances for success is greater using miflash than other tools when recovering from bootloop, but then again I don't know. Maybe I could just have flashed the s000037 rom with qfil or maybe I was just lucky, who knows.
But this what worked for me.
I hope this can help someone as I could not with the help of god find any useful help regarding this problem.
pallep said:
I hope this can help someone as I could not with the help of god find any useful help regarding this problem.
Click to expand...
Click to collapse
Thanks kind man You helped finish my struggle!
The only thing I want to add is that the ROM from the original link is no longer available, so I found the correct ROM using Google from the original filename here https://firmware247.com/lenovo-tab4-a10-plus-tb-x704f-firmware/