Related
Hi,
Long story short. I had TWRP 2.5.0.2 with my SGH-I377 (Galaxy S4 AT&T). I used it to flash this GE ROM by Maddog (http://forum.xda-developers.com/showthread.php?t=2340783)
After flashing, the ROM works just fine without issue. The Model Number in the about phone section however showed to be GT-I9505G, but I didn't mind too much since it works flawlessly in everyway. When I tried to update TWRP to 2.6.3.0, GooManager downloaded the wrong img due to this (it was my fault for not looking at the version before clicking yes). But now after reboot, i can't get into TWRP recovery anymore, it keeps saying "System software not authorized by ATT has been found on your phone". I was able to bypass by going to download mode and cancel to boot back into my old GE ROM. But now I can't seem to find away to get the correct TWRP version back on the phone.
I can download the correct img from this site, put it on my internal/ext SD, but I can't find a way to install it from within GooManager or from a File Manager.
http://techerrata.com/browse/twrp2/jflteatt
I need some assistance with instructions on how to install TWRP manually from an img file. Or from a tar file using ODIN if anyone has the link to necessary files and instructions on how to do it. At this point, it doesn't even have to be 2.6.3.0, I'll be just happy to get 2.5.2.0 back.
thinking21 said:
Hi,
Long story short. I had TWRP 2.5.0.2 with my SGH-I377 (Galaxy S4 AT&T). I used it to flash this GE ROM by Maddog (http://forum.xda-developers.com/showthread.php?t=2340783)
After flashing, the ROM works just fine without issue. The Model Number in the about phone section however showed to be GT-I9505G, but I didn't mind too much since it works flawlessly in everyway. When I tried to update TWRP to 2.6.3.0, GooManager downloaded the wrong img due to this (it was my fault for not looking at the version before clicking yes). But now after reboot, i can't get into TWRP recovery anymore, it keeps saying "System software not authorized by ATT has been found on your phone". I was able to bypass by going to download mode and cancel to boot back into my old GE ROM. But now I can't seem to find away to get the correct TWRP version back on the phone.
I can download the correct img from this site, put it on my internal/ext SD, but I can't find a way to install it from within GooManager or from a File Manager.
http://techerrata.com/browse/twrp2/jflteatt
I need some assistance with instructions on how to install TWRP manually from an img file. Or from a tar file using ODIN if anyone has the link to necessary files and instructions on how to do it. At this point, it doesn't even have to be 2.6.3.0, I'll be just happy to get 2.5.2.0 back.
Click to expand...
Click to collapse
You won't be able to install it with Goo Manager. Head over the the TWRP website and find your phone that way, and grab the flashing zip file and just flash it in recovery. I had the same issue a few weeks ago.
After some more digging, I was able to find a solution.
For anyone who runs into this problem...I was able to use Quick Flasher from this thread http://forum.xda-developers.com/showthread.php?t=1694617 , then choose the flash a new recovery using the correct TWRP img
Everything is good now, I am able to get into TWRP recovery 2.6.3.0
thinking21 said:
Hi,
Long story short. I had TWRP 2.5.0.2 with my SGH-I377 (Galaxy S4 AT&T). I used it to flash this GE ROM by Maddog (http://forum.xda-developers.com/showthread.php?t=2340783)
After flashing, the ROM works just fine without issue. The Model Number in the about phone section however showed to be GT-I9505G, but I didn't mind too much since it works flawlessly in everyway. When I tried to update TWRP to 2.6.3.0, GooManager downloaded the wrong img due to this (it was my fault for not looking at the version before clicking yes). But now after reboot, i can't get into TWRP recovery anymore, it keeps saying "System software not authorized by ATT has been found on your phone". I was able to bypass by going to download mode and cancel to boot back into my old GE ROM. But now I can't seem to find away to get the correct TWRP version back on the phone.
I can download the correct img from this site, put it on my internal/ext SD, but I can't find a way to install it from within GooManager or from a File Manager.
http://techerrata.com/browse/twrp2/jflteatt
I need some assistance with instructions on how to install TWRP manually from an img file. Or from a tar file using ODIN if anyone has the link to necessary files and instructions on how to do it. At this point, it doesn't even have to be 2.6.3.0, I'll be just happy to get 2.5.2.0 back.
Click to expand...
Click to collapse
You can get it right here
http://www.teamw.in/project/twrp2/182
That's straight from the horses mouth there. I didn't read much into it, but it looks like they have a odin flashable version. Also make sure that the newest version of TWRP doesn't conflict with the ROM your using. I have read quite a few where the latest version causes issues.
Hello Im new to the world of Custom Recovery and Flashing Roms. So I'm having a bit of a problem!!!! I rooted my Sprint Galaxy s4 with odin on my iMac threw Parallels V Machine and windows. Worked great! i installed TWRP which also worked well. Ok heres my problem.... I boot into recovery and wipe all the things i need to and I've done my research for a rom that works with my phone I've also watched countless number of youtube videos on how to flash. i have the rom downloaded on my sd card. When i pull it up it lets me pick the rom but no swipe to flash. Instead... When i tap on the rom it goes into the files that the rom has in it and thats it... no way to flash it. Then I'm left with no choice but to restore my backed up stock rom. Does anyone have any ideas? What am i doing wrong if anything? Please help if possible. Thank you!
You are in the wrong forum. This is the Verizon variant.
But to answer your question it sounds like you extracted the zip file to a folder.
You do but extract it. You only flash the .zip file as a whole.
Sent from my Verizon Galaxy S4 using Tapatalk 2.
But i didn't extract anything i pulled it from my iMac is that the problem?
Does it have [Rom filename].zip? Or just show the rom filename?
The file list in twrp to install a rom will show filename extensions.
Sent from my Verizon Galaxy S4 using Tapatalk 2.
Moved to correct Q&A forum
There are 6 S4 forums...make sure you choose correctly
Also questions go in Q&A
Thanks
FNM
As was mentioned you've done something wrong; and that looks to be that you've extracted the ROM zip.
Since you downloaded it on a Mac it probably used the download manger and uzipped it.
You need to download the file (and keep it) so that it looks something like this:
Stock_Rooted_Deodexed_MF9_Rom.zip
or
Sacs_Custom_Rom_4.3_v3.1.zip
or
MetalROM_v3.3.zip
etc.
Copy that to you exernal SD card then in TWRP select install zip after you've followed the OP's instructions on wiping to select it and install.
I apologize for the Noob question(s), but does anyone know if the **.zip.md5sum** file as listed below needs to be flashed in conjunction with the actual Rom? If so, do they need to be flashed in a particular order? I haven't been doing so since it appears to be a blank file based on the size. I only ask because ever since switching to OmniRom from GummyRom, my phone seems to get stuck at the Samsung logo screen. About half the time it requires a battery pull because my phone seems to just be stuck at boot. I'm using the latest version of CWM and have read in the Omni thread that switching to the latest version of TWRP resolved the problem. I am just curious if others are or have experienced this problem and what they did to resolve it?
Lastly, I know this is more like a three part question and if I have to post it in another thread I will. But I did try to install TWRP from the Goo Manager app and when the download page loads it doesn't install anything. The page just says it's preparing my download, but doesn't download anything. Any thoughts or suggestions would be greatly appreciated...
I am using a Verizon Galaxy S4
omni-4.4.1-20131208-jfltevzw-NIGHTLY.zip 2013-12-08 18:40 193587 KB
omni-4.4.1-20131208-jfltevzw-NIGHTLY.zip.md5sum 2013-12-08 18:40 0 KB
droidzen10 said:
I apologize for the Noob question(s), but does anyone know if the **.zip.md5sum** file as listed below needs to be flashed in conjunction with the actual Rom? If so, do they need to be flashed in a particular order? I haven't been doing so since it appears to be a blank file based on the size. I only ask because ever since switching to OmniRom from GummyRom, my phone seems to get stuck at the Samsung logo screen. About half the time it requires a battery pull because my phone seems to just be stuck at boot. I'm using the latest version of CWM and have read in the Omni thread that switching to the latest version of TWRP resolved the problem. I am just curious if others are or have experienced this problem and what they did to resolve it?
Lastly, I know this is more like a three part question and if I have to post it in another thread I will. But I did try to install TWRP from the Goo Manager app and when the download page loads it doesn't install anything. The page just says it's preparing my download, but doesn't download anything. Any thoughts or suggestions would be greatly appreciated...
I am using a Verizon Galaxy S4
omni-4.4.1-20131208-jfltevzw-NIGHTLY.zip 2013-12-08 18:40 193587 KB
omni-4.4.1-20131208-jfltevzw-NIGHTLY.zip.md5sum 2013-12-08 18:40 0 KB
Click to expand...
Click to collapse
First things first, the MD5sum is the checksum of the ROM at buildtime, all you need to do is have this in the same folder as the ROM when flashing and TWRP will verify the checksum of the ROM before installing, so if it is a mismatch it stops you right there.
It should not be flashed.
Its been a while since I used the twrp check-sum someone correct me if wrong.....I verify the MD5 before i put the rom on phone to ensure its a good download.
GooManager has always been flaky on my Skyrocket and on my buddies S3, but that is just me talking, nothing against goomanager. That being said I have always preferred to flash recoveries from the recovery, or odin this ensures (me) that the flash went well.
You can almost always find a zip of the latest recovery for your phone in one of the development threads or you can ask on the S4 Q&A thread if someone has one or if they can get you one. I haven't been to your forum but i'm sure there is a TWRP thread to follow.
OmniRom flashing question
Tweakecho said:
First things first, the MD5sum is the checksum of the ROM at buildtime, all you need to do is have this in the same folder as the ROM when flashing and TWRP will verify the checksum of the ROM before installing, so if it is a mismatch it stops you right there.
It should not be flashed.
Its been a while since I used the twrp check-sum someone correct me if wrong.....I verify the MD5 before i put the rom on phone to ensure its a good download.
GooManager has always been flaky on my Skyrocket and on my buddies S3, but that is just me talking, nothing against goomanager. That being said I have always preferred to flash recoveries from the recovery, or odin this ensures (me) that the flash went well.
You can almost always find a zip of the latest recovery for your phone in one of the development threads or you can ask on the S4 Q&A thread if someone has one or if they can get you one. I haven't been to your forum but i'm sure there is a TWRP thread to follow.
Click to expand...
Click to collapse
Thanks for your answer and suggestion regarding flashing a recovery. I've been doing a lot of reading here on XDA and quite a few have suggested using Flashify to flash recoveries....
Tweakecho said:
First things first, the MD5sum is the checksum of the ROM at buildtime, all you need to do is have this in the same folder as the ROM when flashing and TWRP will verify the checksum of the ROM before installing, so if it is a mismatch it stops you right there.
Click to expand...
Click to collapse
It doesn't work that way for me. I always put the files in the same folder but TWRP 2.6.3.3 always says that there is no md5 file to be found.
Riiquiem said:
It doesn't work that way for me. I always put the files in the same folder but TWRP 2.6.3.3 always says that there is no md5 file to be found.
Click to expand...
Click to collapse
It's because the file extension is wrong.
Zip md5 Verification (looks for file with zipname.zip.md5)
So, if you downloaded these files :
omni-4.4.1-20131208-jfltevzw-NIGHTLY.zip
omni-4.4.1-20131208-jfltevzw-NIGHTLY.zip.md5sum
You need to rename "omni-4.4.1-20131208-jfltevzw-NIGHTLY.zip.md5sum" to "omni-4.4.1-20131208-jfltevzw-NIGHTLY.zip.md5".
AngryHapposai said:
It's because the file extension is wrong.
Zip md5 Verification (looks for file with zipname.zip.md5)
So, if you downloaded these files :
omni-4.4.1-20131208-jfltevzw-NIGHTLY.zip
omni-4.4.1-20131208-jfltevzw-NIGHTLY.zip.md5sum
You need to rename "omni-4.4.1-20131208-jfltevzw-NIGHTLY.zip.md5sum" to "omni-4.4.1-20131208-jfltevzw-NIGHTLY.zip.md5".
Click to expand...
Click to collapse
That explains why mine always reports an error as well. *fixes all future build md5's
Having the same problem MD5 not found while flashing ROM. lemme try renaming. Will say again, if its work
I wanted to install Xposed on my Samsung Galaxy Note 4 SM-910C Version 6.0.1
So through a lot of "googling" i found a way to root my phone with Chainfire through Odin Flashing, which worked (Root Checker confirmed it so i guess it worked)
After a few more google searches i managed to flash TWRP Recovery through Odin which also worked.
Here's where i went a bit off instructions: After TWRP i went on to attempt installing Xposed Firmware on to my phone. I downloaded An Xposed APK from the instruction website i was reading but it also required i download another Xposed file which i went on to install through TWRP recovery. This particular File i donwloaded from another source since the one on the instruction site's mirror was broken, it was Armv7 and it matched what my phone's hardware required.
After installing this Xposed file on TWRP i went on to reboot my phone but before this TWRP told me that root access wasn't installed and prompted me to install SuperSU, this really confused me since Root checker said that i already had Super User turned On. I don't know why but i actually agreed to it and installed it AGAIN.
My phone rebooted until the animated Samsung Logo came on and it never moved past that for about an hour.
Right now all i can do is pull my battery out and boot recovery, i tried factory resetting my phone and wiping everything. now what happens is TWRP keeps on prompting me to install SuperSU and now it doesn't even reach the animated Samsung logo it always gets stuck on the [Samsung GALAXY Note 4].
I'm sorry if i posted this text wall but i thought these details might help, can anyone help me?
Edit: Sorry for the title don't know how to change it, fyi i wanted to change that to "Messed up trying to install Xposed Framework"
SpoonOjiisan said:
I wanted to install Xposed on my Samsung Galaxy Note 4 SM-910C Version 6.0.1
So through a lot of "googling" i found a way to root my phone with Chainfire through Odin Flashing, which worked (Root Checker confirmed it so i guess it worked)
After a few more google searches i managed to flash TWRP Recovery through Odin which also worked.
Here's where i went a bit off instructions: After TWRP i went on to attempt installing Xposed Firmware on to my phone. I downloaded An Xposed APK from the instruction website i was reading but it also required i download another Xposed file which i went on to install through TWRP recovery. This particular File i donwloaded from another source since the one on the instruction site's mirror was broken, it was Armv7 and it matched what my phone's hardware required.
After installing this Xposed file on TWRP i went on to reboot my phone but before this TWRP told me that root access wasn't installed and prompted me to install SuperSU, this really confused me since Root checker said that i already had Super User turned On. I don't know why but i actually agreed to it and installed it AGAIN.
My phone rebooted until the animated Samsung Logo came on and it never moved past that for about an hour.
Right now all i can do is pull my battery out and boot recovery, i tried factory resetting my phone and wiping everything. now what happens is TWRP keeps on prompting me to install SuperSU and now it doesn't even reach the animated Samsung logo it always gets stuck on the [Samsung GALAXY Note 4].
I'm sorry if i posted this text wall but i thought these details might help, can anyone help me?
Edit: Sorry for the title don't know how to change it, fyi i wanted to change that to "Messed up trying to install Xposed Framework"
Click to expand...
Click to collapse
Since you have twrp, find supersu.zip and save into sdcard. Flash supersu.zip to gain root access. And for xposed. Make sure it is arm-sdk23.
Sent from my SM-G925F
Rosli59564 said:
Since you have twrp, find supersu.zip and save into sdcard. Flash supersu.zip to gain root access. And for xposed. Make sure it is arm-sdk23.
Sent from my SM-G925F
Click to expand...
Click to collapse
Did a quick google search do these work?
download.chainfire.eu/696/supersu/
androidsage.com/2016/04/06/how-to-install-xposed-framework-on-marshmallow-update-with-xposed-v81/
and btw how exactly do i save this into my sd card, i can't get past the product logo.
also thanks a lot for replying man
edit: oh wait if you mean put the zips into an external sd card imma try that now. thx
Hi,
You have to use custom built version of xposed if you use stock or any touchwiz-based-rom(other versions cause bootloops). Just google 'xposed custom build by wanam'. Hope that helps.
Just wanted to clear some stuff up, if i am able to flash supersu.zip and a custom built xposed framework, will my phone stop getting stuck on the product logo?
Because being unable to use my phone normally is my top priority right now. The root and getting xpose3d installed is secondary. I really can't get through the product logo, i hope someone can shed some light on this.
but still, i really appreciate your replies.
SpoonOjiisan said:
Just wanted to clear some stuff up, if i am able to flash supersu.zip and a custom built xposed framework, will my phone stop getting stuck on the product logo?
Because being unable to use my phone normally is my top priority right now. The root and getting xpose3d installed is secondary. I really can't get through the product logo, i hope someone can shed some light on this.
but still, i really appreciate your replies.
Click to expand...
Click to collapse
I strongly believe you flashed wrong xposed zip. There is no arm7 zip by wanam. Hence find arm-sdk23. I think the last 1 is v81.
Supersu is just to give you root access. I won't causing phone to stuck at boot logo. Or do you mean splash screen showing 'samsung galaxy note 4'?
Sent from my SM-G925F
I honestly don't know if that will solve the problem, but you can try it. If it doesn't work, try flashing a rom via recovery or stock rom via odin. Since your data is already gone, I would suggest you wiping your phone completely and flashing a custom rom(I have a SM-N910C as well and I use erobot). Before doing anything, do a full backup in recovery, just in case.
Edit: If you wiped everything in recovery, including /system, that is probably the reason why your phone is stuck. Flash a rom and yo should be good.
Yeah that one exactly, splash screen showing note 4.
so based on what you guys said i should first flash a ROM so it works normally and then i can attempt for Supersu and Xposed arm-sdk23? was watching this random video you think i might have somehow wiped my touchwiz OS? was fiddling around in the Recovery trying to solve it you think i might have done that?
Since you have the same phone and you are using erobot i might go for that same ROM just to be on the safe side, i don't want to try something random.
So first try flashing custom ROM >> SuperSU >> Xposed
That's what i'm going for (i might need confirmation haha kinda scared now, i think i almost bricked my phone)
I believe your phone has to be rooted before you can install a custom rom. I can't tell if your is, but I would do the following:
Make a full backup in twrp>flash supersu again just to make sure the phone has root access>flash a custom rom.zip from your SD card>boot the custom rom, if everything works, flash xposed CUSTOM BUILD(!) and install the xposed installer.apk
I am not a pro, so wait for someone to confirm what I have written. I suggest you to use erobot as your custom rom because of the user-friendly aroma installer. Erobot is prerooted if you choose custom kernel in aroma installer, so keep in mind not to choose stock kernel.
Hope it helped
SuperSU >> Erobot >> Xposed
Ok got it, its currently 23:36 here in the Philippines guess i'm going to sleep, i'm doin that stuff tomorrow confirmation or not.
I can't really afford to throw this phone and it was a gift. So you guys have no idea how much i appreciate your help. /downslash/ Rosli thanks a bunch guys. goodnight
Hi there.. dont worry about the su not install button.. its common as i've aslo rooted my phone through chainfire an it does show me too. Click on do not install..an yeah you have flashed wrong xposed that bricked your phone.. did you backed up your phone before flashing xposed framework? If so try to restore..if not try to get in downloading mod an flash the official framework through odin.. try visiting sammobile.com there tou will get the official framework.. before flashing read ann the instruction or take a look to video tutorial on youtube about how to unbrick phone.. this might help you all the best
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