Hello. I am trying to install TWRP on my S7 Edge, because I want the Xposed Framework. I have the Exynos version.
I am trying to follow this short guide: http://forum.xda-developers.com/showpost.php?p=66277202&postcount=28
I am rooted, I have all the zip files, and I have TWRP Manager installed. However, when I go to try and install it, it says:
"Something is wrong
Flashing recovery was unsuccessful. Either you already have this recovery installed or another error has occurred. Would you like to attempt rebooting to recovery now?"
If I select OK, I get into the TWRP Recovery, but I am unable to mount /data so I can take a backup.
Is this because of Android 6, that the device is encrypted and it won't mount /data?
I have read places that I need to flash a new kernel and format my user data, but if I have to take it that far, I don't really want to do it.
Please let me know your thoughts on this.
Thanks!
Hi there,
I followed all the instructions but I didnt read the part where it tells you that you have to install something so it can boot again. It seems that I am now unable to boot. I was really hoping that someone can help me.
I tried to install it after the first failed boot attempt but it didnt change anything.
Thank you in advance for your help.
It seems like you've installed the official build of xposed framework which is not compatible with most of Samsung devices.
You need to download the unofficial build for Samsung from here http://forum.xda-developers.com/xposed/unofficial-xposed-samsung-lollipop-t3180960
TWRP should be accessible if you've installed it correctly by holding the Power, Vol up and home button at the same time.
If it boots to TWRP, go to mount the mount USB storage and place the downloaded version of Xposed on the phone then unmount USB storage and install it.
That's all
Themohd is correct
Also, there is some verity opt zip which i needed to install with twrp for disabling encryption
And remember to flash supersu v2.65+ for MM,I lost my moto droid maxx to that.
Hello everyone! New member here.
I'm posting because I experienced something similar to this.
I was flashing TWRP from pure stock but missed a certain step (provided below). When TWRP loaded, it seemed like it couldn't detect any of the partitions on my S7 Edge, so I restarted it to system and ended up in bootloop.
Here is the step from the TWRP guide:
Step: 8. Hold [Volume Up] + [Home] buttons near the end of the flash, and keep holding them until you are in recovery
Guide: http://forum.xda-developers.com/s7-edge/development/recovery-official-twrp-hero2lte-3-0-0-0-t3334084
So my question is, what does step 8 do exactly? Was it significant enough to cause the bootloop on my phone or could it have been something else? I was doing this because I want to flash Xposed Framework.
EDIT: After thinking about it, I'm sure step 8 brings you straight to recovery instead of booting into system then restarting manually into TWRP. So now I'm wondering this, what caused TWRP to not detect any of the partitions? In detail, TWRP showed all the partition sizes as "0 MB" when I went to a certain page (forgot what exactly lol). But I will follow the instructions step-by-step and get back to you guys.
Guys this is help less.
After rooting my device I followed some instructions to get the Lineage 14. I flashed a BootLoader and a Modem as instructed and went forth to mount USB in order to transfer the custom rom into the device. But this is where the problem is.
It says E: Cant find partition to mount storage. I've tried to reboot, wide, data, storage, system and cache and repair the partition I don't know what else to do.
Anyone else can help? Btw I am fairly new to this stuff so please dumb it down for me.
Another thing, when I go to reboot my recovery it says my device isn't rooted and asks to install superSu, however it was rooted before I entered download mode and started installing bootloader and modem.
Now I have no operating system in the device so i can literally only use Recovery or download mode.
Is my device bricked? I don't know. :crying: :crying:
Pobi123 said:
Guys this is help less.
After rooting my device I followed some instructions to get the Lineage 14. I flashed a BootLoader and a Modem as instructed and went forth to mount USB in order to transfer the custom rom into the device. But this is where the problem is.
It says E: Cant find partition to mount storage. I've tried to reboot, wide, data, storage, system and cache and repair the partition I don't know what else to do.
Anyone else can help? Btw I am fairly new to this stuff so please dumb it down for me.
Another thing, when I go to reboot my recovery it says my device isn't rooted and asks to install superSu, however it was rooted before I entered download mode and started installing bootloader and modem.
Now I have no operating system in the device so i can literally only use Recovery or download mode.
Is my device bricked? I don't know. :crying: :crying:
Click to expand...
Click to collapse
If you can boot recovery, all is not lost.
First, are you sure that you flashed the correct bootloader/modem for your s5 model (G900 T, P, V, F, etc? Odin should not let you flash the wrong one, but anything is possible.
If Bl/modem is correct, them the next thing is to get the custom rom onto the phone.
-make sure you have downloaded everything you need (rom, root method(pref Magisk), gapps if wanted)
- boot into recovery, I'm recommending and assuming that you are using the latest Twrp, if not, d/l official Twrp for your model, and flash that with Odin
-In twrp select wipe, format data, just in case.
-now you should be able to mount usb storage, using the option in twrp
- now you should be able to mount your phone to your PC and transfer the rom, put it somewhere easy to find on the phone. also copy gapps and Magisk zips
-now, still in twrp, select install, select rom zip, select add more, select Magisk zip, also flash gapps at this time if you want to use them.
-click the button to flash
-click wipe cache/dalvik
-click reboot
-pray ?
BlueCyclone said:
If you can boot recovery, all is not lost.
First, are you sure that you flashed the correct bootloader/modem for your s5 model (G900 T, P, V, F, etc? Odin should not let you flash the wrong one, but anything is possible.
If Bl/modem is correct, them the next thing is to get the custom rom onto the phone.
-make sure you have downloaded everything you need (rom, root method(pref Magisk), gapps if wanted)
- boot into recovery, I'm recommending and assuming that you are using the latest Twrp, if not, d/l official Twrp for your model, and flash that with Odin
-In twrp select wipe, format data, just in case.
-now you should be able to mount usb storage, using the option in twrp
- now you should be able to mount your phone to your PC and transfer the rom, put it somewhere easy to find on the phone. also copy gapps and Magisk zips
-now, still in twrp, select install, select rom zip, select add more, select Magisk zip, also flash gapps at this time if you want to use them.
-click the button to flash
-click wipe cache/dalvik
-click reboot
-pray ?
Click to expand...
Click to collapse
Hey man! Thank you so much for your reply. I installed CPE1 bootloader and modem driver, honestly I don't even know what they do. Was this a wrong thing to do?
I rooted my device using cf auto root, then flashed the bootloader and modem using Odin. After that I (stupidly) tried to boot my stock OS and it was stuck in a bootloop.
Unfortunately I won't be able to try your instructions this till tomorrow evening but I'll keep you posted!! do you mind if I pm?
Edit: I was using twrp 2.8.7 I believe, could this have been the problem? Also I updated twrp to latest and tried micro sd as storage and flashed a Rom but the phone is still bootlooping
Pobi123 said:
Hey man! Thank you so much for your reply. I installed CPE1 bootloader and modem driver, honestly I don't even know what they do. Was this a wrong thing to do?
I rooted my device using cf auto root, then flashed the bootloader and modem using Odin. After that I (stupidly) tried to boot my stock OS and it was stuck in a bootloop.
Unfortunately I won't be able to try your instructions this till tomorrow evening but I'll keep you posted!! do you mind if I pm?
Edit: I was using twrp 2.8.7 I believe, could this have been the problem? Also I updated twrp to latest and tried micro sd as storage and flashed a Rom but the phone is still bootlooping
Click to expand...
Click to collapse
Ok I see you have S5 plus. I'm not familiar with that device to know which baseband it should be.
One thing you might try is to boot recovery and clear cache/dalvik and then try booting the custom rom.
If all else fails, you might try Samfirm
https://forum.xda-developers.com/galaxy-tab-s/general/tool-samfirm-samsung-firmware-t2988647
That should give you a stock firmware file to flash with odin.
You can pm if you need to, I don't own an S5+, nor am I a veteran flasher but I will try to help if I can.
BlueCyclone said:
Ok I see you have S5 plus. I'm not familiar with that device to know which baseband it should be.
One thing you might try is to boot recovery and clear cache/dalvik and then try booting the custom rom.
If all else fails, you might try Samfirm
https://forum.xda-developers.com/galaxy-tab-s/general/tool-samfirm-samsung-firmware-t2988647
That should give you a stock firmware file to flash with odin.
You can pm if you need to, I don't own an S5+, nor am I a veteran flasher but I will try to help if I can.
Click to expand...
Click to collapse
Ive tried the suggestion you gave me, no success. However I honestly dont know if it could be my fault. I'm gonna flash the stock firmware and restart the whole root process.
Thanks for your help man!
Pobi123 said:
Ive tried the suggestion you gave me, no success. However I honestly dont know if it could be my fault. I'm gonna flash the stock firmware and restart the whole root process.
Thanks for your help man!
Click to expand...
Click to collapse
Ok sorry I couldn't be more help
Oh, you don't need to use of cfautoroot anymore, you can just flash Magisk after the rom, and then use Magisk manager to manage all your root permissions.
So if you are going back to stock, I would:
-Flash stock in Odin
-probably boot stock once to verify (first boot takes long)
-odin flash latest twrp(uncheck auto-reboot, just battery pull after it says pass)
-power on phone with key combo to boot recovery
- format data
-flash rom/gapps?/Magisk
-wipe cache/dalvik
-reboot system (first boot will take long)
Hope you get your phone working again
BlueCyclone said:
Ok sorry I couldn't be more help
Oh, you don't need to use of cfautoroot anymore, you can just flash Magisk after the rom, and then use Magisk manager to manage all your root permissions.
So if you are going back to stock, I would:
-Flash stock in Odin
-probably boot stock once to verify (first boot takes long)
-odin flash latest twrp(uncheck auto-reboot, just battery pull after it says pass)
-power on phone with key combo to boot recovery
- format data
-flash rom/gapps?/Magisk
-wipe cache/dalvik
-reboot system (first boot will take long)
Hope you get your phone working again
Click to expand...
Click to collapse
Good News! Phone is back in full working order after flashing stock firmware. It was kinda scary though, I had to fix an error in Odin and then the phone wouldn't even boot up! Left it over night, booted it again and it worked fine Thanks a lot for your help, I'll try not to soft brick my device again
I attempted to install LineageOS 17.1 on my Mi A1, but while wiping storage, I accidentally also clicked Internal Storage and wiped it too. Now, I tried to restore my backup but when I go to restart to turn on my Mi A1, it gets stuck in a boot loop. I also tried using XiaoMiFlash and the original ROM to get all the firmware settings to stock. Now, I tried also installing custom ROM again, LineageOS 17.1 but it also gets stuck in a boot loop. Is there anything else I can do?? I'm very frustrated... I hope my device isn't completely bricked. Any help is appreciated.
I need help pls asap said:
I attempted to install LineageOS 17.1 on my Mi A1, but while wiping storage, I accidentally also clicked Internal Storage and wiped it too. Now, I tried to restore my backup but when I go to restart to turn on my Mi A1, it gets stuck in a boot loop. I also tried using XiaoMiFlash and the original ROM to get all the firmware settings to stock. Now, I tried also installing custom ROM again, LineageOS 17.1 but it also gets stuck in a boot loop. Is there anything else I can do?? I'm very frustrated... I hope my device isn't completely bricked. Any help is appreciated.
Click to expand...
Click to collapse
Welcome to XDA!
Its not recommended to open more than 1 thread on same topic, please have a read of the forum rules and most importantly, enjoy your stay!
It should be ok with mi flash tool
lafactorial said:
It should be ok with mi flash tool
Click to expand...
Click to collapse
I have already tried that, the only issue now is that the Custom ROM after installing (LineageOS 17.1) will not boot properly. Maybe this is because I skipped TWRP Recovery? Well, I don't know why but TWRP Recovery zip will not copy into phone storage. it is originally .img file, but the guide I'm following has .zip file so I converted into zip via Windows Explorer (file manager). But, it does not copy and when I use img to zip website converter iand it does copy, but it says "invalid zip file format" once flashing.
One thing I should note, the backup does work now. I had a typo when making the folder so it wouldn't work. Backup does work now, but something really stupid is happening. When I go to turn on screen lock, it will keep looping me into "which type do you want to choose, fingerprint + pin, password, pattern" after completing the process. If I don't choose fingerprint, it finishes but the screen lock isn't effective. Any help on this?
I need help pls asap said:
I have already tried that, the only issue now is that the Custom ROM after installing (LineageOS 17.1) will not boot properly. Maybe this is because I skipped TWRP Recovery? Well, I don't know why but TWRP Recovery zip will not copy into phone storage. it is originally .img file, but the guide I'm following has .zip file so I converted into zip via Windows Explorer (file manager). But, it does not copy and when I use img to zip website converter iand it does copy, but it says "invalid zip file format" once flashing.
Click to expand...
Click to collapse
You cannot just convert that image file into a zip file like that.
Where did you get that twrp file from?
If you want to install twrp, you need to flash the twrp.img file via fastboot, then sideload the twrp.zip via trwp.
(maybe just flashing the img file works too, but I often read that you have to do both).
Hi all,
So many years ago I used to do this flashing the custom roms on my old galaxy s4, and it was pretty straight forward.
THis s8 though is giving me real problems.
I'm trying to flash lineage 19 on it but I just can't seem to do it. I have run into error messages, boot loops, apparently deleted the boot sector off after using TWRP which only worked once...
I have googled and googled but I can't find the exact guide for my phone. It's a UK phone.
I have managed to get a samsung rom back on it using Odin, but it's got so T roam option which doesn't do anything..
Please can someone help?
It should work like this:
1. Enable OEM-unlocking in the developer options
2. Download the no-verity-opt-encrypt rom (google it, you will find links) on an SD Card or if you can plug that in your phone on an USB Stick
3. Install twrp using odin ( you was able to do this, right?)
4. Boot into twrp (Do not boot in the os first, go to twrp directly after flashing it)
5. Go to wipe, tap on format data and type "yes" to format your data partition.
6. Flash the no-verity-opt-encrypt zip
7. You can now boot to the system. If you already have the install zip for Lineage, you can also flash this now before booting to the system.
8. Done