Database Users

[Q] Bad ROM install, alternative methods to fix? [SOLVED]

Hello all,
My brother has been having problems with his Google Play store (force closing, etc) as well as some other Google services. He wasn't even able to actually load Play Store and browse, so to fix his problem I decided the best route would be to start clean and do a factory reset. This worked well, for about 2-3 hours until he told me he wanted me to put the Google Edition 4.3 JB ROM on his phone. (He's a hipster, trololol)
So I looked up the thread of the AOSP Google Edition 4.3 JB for his GT-I9505. Having flashed my Galaxy S3 many times with UltimaROM and various other ROMs, I figured his S4 wouldn't be much different to any of the other Galaxy devices we've had in the past. So I download TWRP, and also rooted his phone via Motochopper. Once I installed TWRP I hit wipe and wiped the data and dalvik cache. Then I installed the ROM. Few moments later and we reboot the phone.
Phone decides to go into a boot loop, so I go back into TWRP and wipe again like I would with my Galaxy S3, but still getting a boot loop.
I really should have made a back-up of his original stock ROM (I made a boo-boo, I know ) but I figured he had nothing to lose. The problem now is that I can't flash any other ROMs because normally I would just transfer the .zip's onto the phone and then install from there. He doesn't have an SD card either, and mines doesn't work anymore (water damage...).
So my question is, what other ways can I transfer .zip's onto his phone so we can flash another ROM and not let his phone be a huge expensive paper weight.
I know about ADB and I downloaded the ADT Bundle from Google's site, but I have no idea how to execute adb or fastboot. They open cmd but then immediately shutdown again after a flash of a wall of text.
I'm able to access recovery & download modes fine. I've tried "mount" but when it mounts the S4, Windows doesn't pick up on it like it would if I were to do MTP otherwise I'd be able to transfer files no problem.

Can anyone help please?

man...use PhilzRecovery and use adb to flash the rom!
Put the flashable zip in the same folder wich contains adb.
Select from PhilzRecovery "install zip from sideload"
Connect the phone to pc and in the adb window type "adb sideload ..........." (wehere "............." is the name of the flashable zip.
I restored my phone once in this way
otherwise...buy a cheam 2gb micro sd card and put the flashable zip on it.
Select install zip from sdcard and that`s it.
Or you can use adb file explorer to copy the flashable zip on internal memory
there are many solutions for your problem.
The easyest would be the one using "adb sideload"
I hope i helped you!
Have a nice day!!!
PS: to open adb window do this way "press and hold shift while click-ing right click on the folder that contains adb files"
you will get a menu containg "open command window here" and click on it!
In the windows that appears type "adb devices" just to see if the phone is correctly recognised by windows.
Remember that using Philz Recovery is the most secure way.
Twrp has some weird problems formatting data(i don`t know why)
to put the phone just boot into recovery mode and adb should recognize your phone!

http://forum.xda-developers.com/showthread.php?t=2265477 Just follow this. I guess it's a soft brick and you'll just need to flash the stock firmware.

EDIT: Seems I was wrong, but the ADB tip will come in handy though. Thanks!

Ok I think I may have bricked / soft-bricked the phone. I've tried flashing the stock ROM (different firmwares) with and without a PIT file and they all keep failing. Yet if I flash a ROM like Cyanogen Mod it'll get to the Cyanogen Mod boot screen, but then crash there?
The phone is definitely a i9505, so I can't see what the hell I'm doing wrong. :/ It was an Orange UK model, but it was factory unlocked when bought new and he's been using o2 sim's ever since.
All I do is flash .tar.md5's with Odin 3 v1.85, and then install .zip's in the recovery (Philz Recovery)
For the stock ROM I'm just flashing with Odin.
I've never had so much drama with a phone before. -__-

EDIT: Solved this on my own. Had to flash MH8 since I'm on a secured bootloader.
Thanks anyway.

[Q] nook color CM10.2 update problems CyanogenROM_Downloader/TWRP

Hi all. I have a Nook Color running CM 10.2 and am trying to upgrade it without success.
I have Superuser, CyanogenmodRom_Download, and TWRP downloaded.
Using CyanogenmodROM_Downloader configured to use TWRP I can successfully download a new Nightly. When I select Flash it takes me to Cyanboot. I select Internal eMMC Recovery and it brings up a notice saying that the Install Failed.
I tried using TWRP->Install->CyanogenROM_Downloader->cm-10.2-20131009-NIGHTLY-encore.zip. I'm not Wiping anything. Cyanboot into Internal eMMC recovery and the existing release instead of the update is installed.
Also, the only way I can tell which build is installed is with the CyanogenROM_Downloader. I looked around the web for something that would tell me where to look and didn't find anything. I also looked around /etc and didn't find anything obvious. Is there an easy way to tell what nightly build is installed?
I've been beating on this step for a couple of days now and looking around this site and the web and haven't found anything that helps although I'm sure it's out there somewhere. Any suggestions would be appreciated.
Thanks
Steve S.

Finding installed ROM
sjs_bebop said:
Hi all. I have a Nook Color running CM 10.2 and am trying to upgrade it without success.
I have Superuser, CyanogenmodRom_Download, and TWRP downloaded.
Using CyanogenmodROM_Downloader configured to use TWRP I can successfully download a new Nightly. When I select Flash it takes me to Cyanboot. I select Internal eMMC Recovery and it brings up a notice saying that the Install Failed.
I tried using TWRP->Install->CyanogenROM_Downloader->cm-10.2-20131009-NIGHTLY-encore.zip. I'm not Wiping anything. Cyanboot into Internal eMMC recovery and the existing release instead of the update is installed.
Also, the only way I can tell which build is installed is with the CyanogenROM_Downloader. I looked around the web for something that would tell me where to look and didn't find anything. I also looked around /etc and didn't find anything obvious. Is there an easy way to tell what nightly build is installed?
I've been beating on this step for a couple of days now and looking around this site and the web and haven't found anything that helps although I'm sure it's out there somewhere. Any suggestions would be appreciated.
Thanks
Steve S.
Click to expand...
Click to collapse
Go into system settings / about tablet (at bottom of settings)
About 3/4 down list you'll see the ROM installed. Also kernel info plus other info.
For updates ;
I go to this link and download directly.
http://download.cyanogenmod.org/?type=nightly&device=encore
Also I copy and paste the md5 sum into MD5 checker (free in play store), run the check.
Reboot into recovery using power button menu and install in TWRP there. I had too many problems using cm downloader, goo manager, etc.

nook color cm10.2 update problems
Thanks. That helps. I can determine the version now.
But I still can't get update to work. I downloaded from the location you gave using the browser and can see the file using TWRP and selecting install. This boots into the cyanoboot loader, there are two options enabled: 'Internal eMMC Normal' and 'Internal eMMC Recovery.' Normal seems to reboot -- which makes sense. Recovery re-installs the currently installed version. Also, using ADB I can see the new cm-nightly zip file in /storage/sdcard1/Download.
I don't see TWRP during the reboot. Should I??
I also don't get an option to select a new image to install. Should I?
I also tried copying the cm-nightly zip file to the /emmc directory and that doesn't seem to make any difference.

Sounds like a problem I had a while back
sjs_bebop said:
Thanks. That helps. I can determine the version now.
But I still can't get update to work. I downloaded from the location you gave using the browser and can see the file using TWRP and selecting install. This boots into the cyanoboot loader, there are two options enabled: 'Internal eMMC Normal' and 'Internal eMMC Recovery.' Normal seems to reboot -- which makes sense. Recovery re-installs the currently installed version. Also, using ADB I can see the new cm-nightly zip file in /storage/sdcard1/Download.
I don't see TWRP during the reboot. Should I??
I also don't get an option to select a new image to install. Should I?
I also tried copying the cm-nightly zip file to the /emmc directory and that doesn't seem to make any difference.
Click to expand...
Click to collapse
You may be having partition problems. I have had either lost the ability to install new nightlies or the ability to backup. Read the instructions through completely first. Get the info together and then start.
If you have a backup App like titanium backup, backup all files and data before anything else. Also if you can, do a backup in recovery before doing the following.
Check this link: http://forum.xda-developers.com/showthread.php?p=28457126#post28457126 by Leapinlar
I set up a 2Gb sd bootable card to run these from using the CWM recovery (If you need help check eyeballer's link below).
I put the partition repair files on it. Also the 1.4.3 Stock rom, the TWRP open recovery. zip 2.4.1.0 (http://forum.xda-developers.com/showpost.php?p=37554712&postcount=129), and the latest Rom you want to install and Gapps.
After following leapinlar's instructions including installing the 1.4.3 Stock rom (fixes other possible problems), then follow eyeballer's install for the Rom, Gapps and recovery here (http://forum.xda-developers.com/showthread.php?t=1030227&highlight=install+cm7+to+nook+color).
After booting and doing the initial CM setup return to recovery and VERY IMPORTANT ***restore only the data*** Not boot or system from your latest backup. This should get you back up and running. If you have a backup like Titanium restore "newer versions of apps" if you had to use an older recovery backup. Once you have everything set reboot into recovery and do another backup for safeties sake.
Including my wife's Nook I have four units and have needed to do this 4 or 5 times. Takes a little time but has always worked great. I keep the card available and update the Rom, Gapps or whatever else needs changing.
This link also contains a lot of helpful info. I have all these bookmarked on both my PC and Nook.
User Tips http://forum.xda-developers.com/showthread.php?p=25354258#post25354258

[Q] Stuck in recovery mode upgrading CM 10 to CM 11

I was running CyanogenMod 10.1.x versions, using ROM Manager to upgrade as new ones were available. However, when I tried to upgrade to 10.2.1 it kept rebooting every several minutes, showing the new bootup screen with the rotating arrow. I tried upgrading to version 11...M9 also with ROM Manager and now it only comes up in recovery mode (CWM v6.0.3.1). There seems to be no way to finalize the installation. I can't sideload from the PC, since, although DeviceManager shows "Google Galaxy Nexus ADB Interface," I do not see any entries in Device Management or in the Explorer, so I can't offload a full backup, nor can I use adb to sideload the new CM. I can't instal from the internal sdcard, since it starts with "...Installing /sdcard/update.zip" and then can't find it - it comes up with the "(no such file or directory)."
Since (except for Device Manager) nothing on the PC recognizes a connection with the Nexus 10, I'm pretty much out of options. I can do a complete "wipe data/factory reset" I suppose, but would like something not so drastic (given no backup). When I look at CWM's display of mounted and unmounted storage, sdcard is unmounted and won't mount. I've even done a full wipe and factory reset, with the same results.
A brand-new install of the Samsung USB Drivers 1.5.33.0 through Skip's app now results in an error message when I reattach the tablet saying the driver install failed. I still show the device in Device Manager.
I have Skip's Universal Android Toolkit v1.0.2 and it seems to recognize that a Nexus 10 is connected, but can't do anything to it (it expects you are originally booted to Android, not recovery.
This is my first Samsung device, so I'm totally unfamiliar using Odin and haven't figured out how to use it to correct the problem.
It seems that, if I can sideload a copy of CM 11, I should be okay, but all roads look closed.
Any ideas?
I'm locked in a loop.
'

Third post in this thread
http://forum.xda-developers.com/showthread.php?t=2670400
Will give you instruction to fully restore, but will be worst case scenario, you will also find links to drivers that are confirmed working, may need to manually update them
So yes you are right you should want to use adb sideload to get the proper ROM on
And in the future try to not use ROM manager as issues like this happen all to often, rather just boot to recovery, wipe, flash
Your other option is an sdcard and otg cable to flash a ROM
Let me know if you get stuck, best of luck!

Thanks - will keep trying.
demkantor said:
Third post in this thread
http://forum.xda-developers.com/showthread.php?t=2670400
Will give you instruction to fully restore, but will be worst case scenario, you will also find links to drivers that are confirmed working, may need to manually update them
So yes you are right you should want to use adb sideload to get the proper ROM on
And in the future try to not use ROM manager as issues like this happen all to often, rather just boot to recovery, wipe, flash
Your other option is an sdcard and otg cable to flash a ROM
Let me know if you get stuck, best of luck!
Click to expand...
Click to collapse
I downloaded the latest Android SDK with platform tools and put the cm zip file in the directory with adb.exe. On the tablet, in ClockworkmMod Recovery, I selected "install zip from sideload." The tablet went into sideload mode and instructed me to type "adb sideload <filename>. So I typed: "adb sideload cm-11-20140805-SNAPSHOT-M9-manta.zip" and hit the enter key. The PC reported 100% downloaded. The tablet listed:
Restarting adbd...
Finding update package...
Opening update package...
Installing update...
set_metadata_recursive: some changes failed
E:Error in /tmp/update.zip
(Status 7)
Installation aborted.
I'm at least communicating between the PC and tablet, but the update is still failing. Any hope of trying to flash standard ROM, re-root, and start again?

You need to update your recovery, grab the latest TWRP or CWM .img for manta and flash in via fastboot first, then boot to new recovery then flash ROM

Thanks, I grovel at your feet!
Thanks for the help. I ended up downloading the newest Android SDK, installing the platform-tools, and flashing the 4.4.2 factory rom. Normally, this loses all of your data (though, through carelessness I hadn't disabled autosave to the Google Cloud, so all was restored). Now I have an unrooted tab with KitKat on it, but it won't take me long to root it again and this time, I'll flash custom ROMs manually, the way I do on my other devices. Once burned...
So thanks again for the help. It did the trick.

Beartooth01 said:
Thanks for the help. I ended up downloading the newest Android SDK, installing the platform-tools, and flashing the 4.4.2 factory rom. Normally, this loses all of your data (though, through carelessness I hadn't disabled autosave to the Google Cloud, so all was restored). Now I have an unrooted tab with KitKat on it, but it won't take me long to root it again and this time, I'll flash custom ROMs manually, the way I do on my other devices. Once burned...
So thanks again for the help. It did the trick.
Click to expand...
Click to collapse
Great to see @demkantor help get you back up and running ..
@Beartooth01 Can you plz add "SOLVED" to the thread title
Thx Josh

[Q&A] [ROM][LOLLIPOP][5.0][LRX21T][UNTOUCHED PURE STOCK][Nexus⁴]

Q&A for [ROM][LOLLIPOP][5.0][LRX21T][UNTOUCHED PURE STOCK][Nexus⁴]
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.
Before posting, please use the forum search and read through the discussion thread for [ROM][LOLLIPOP][5.0][LRX21T][UNTOUCHED PURE STOCK][Nexus⁴]. If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.
Thanks for understanding and for helping to keep XDA neat and tidy!

So i kinda figured it out.
well, I sort of did something(i think) and its now working fine... I went to twrp.. did a factory reset. Then went for advance wipe and wiped system cache and dalvik. Then followed the same procedure. Bootloader-->radio-->Rom-->Kernel. It worked just fine. The first boot took some 15 minutes.

does the internal storage work for you? it works only on twrp for me :/
i can't see anything in file explorer and canìt restore from twrp :/ that's a big problem guys.

If you can not see your old nandroid backups
After rooting If you can not see your old nandroid backups
Via file explorers try to enable usb debuging from
dev. opt. if not worked (Recovires or SuperSU issue)
But you can see and restore your old or new backups via recovery (TWRP tested)
New recoveries and superSU may fix this issues.
Want to ask? SuperSU XDA Thread here
Note: SE Linux Mod Changer may help to fix this issue
Recommended Recovery is TWRP 2.8.1.0
​

HunterAtXDA said:
I also got this message
Code:
unmount of /system failed: no such volume
followed by
Code:
unmount of /data failed: no such volume
a few minutes later. The process finished a few minutes later without any more output but I'm booting now after wiping the cache and everything seems fine.
Click to expand...
Click to collapse
I had the this same problem. After installing everything, I let it sit for 20 minutes and it finally showed the Android logo. After that it was stuck on a black screen. I wiped everything and repeated the install procedure again, minus the kernal, and got the same "unmount of /system failed: no such volume" while flashing the rom zip. It booted after a while and everything works except my storage is FUKT. I cant see any of my pictures, music, etc, and the only thing I see via PC is the DCIM folder which is empty. Not cool

mattgrantlackey said:
I had the this same problem. After installing everything, I let it sit for 20 minutes and it finally showed the Android logo. After that it was stuck on a black screen. I wiped everything and repeated the install procedure again, minus the kernal, and got the same "unmount of /system failed: no such volume" while flashing the rom zip. It booted after a while and everything works except my storage is FUKT. I cant see any of my pictures, music, etc, and the only thing I see via PC is the DCIM folder which is empty. Not cool
Click to expand...
Click to collapse
Recommended Recovery is TWRP 2.8.1.0

mattgrantlackey said:
I had the this same problem. After installing everything, I let it sit for 20 minutes and it finally showed the Android logo. After that it was stuck on a black screen. I wiped everything and repeated the install procedure again, minus the kernal, and got the same "unmount of /system failed: no such volume" while flashing the rom zip. It booted after a while and everything works except my storage is FUKT. I cant see any of my pictures, music, etc, and the only thing I see via PC is the DCIM folder which is empty. Not cool
Click to expand...
Click to collapse
Nothing wrong with my storage. I installed the bootloader, radio, and rom on top of my existing 4.4.4 rom by sideloading in CWM. Wiped caches and rebooted to make sure everything was working, then back to CWM to sideload the kernel. I haven't rooted yet.

HunterAtXDA said:
Nothing wrong with my storage. I installed the bootloader, radio, and rom on top of my existing 4.4.4 rom by sideloading in CWM. Wiped caches and rebooted to make sure everything was working, then back to CWM to sideload the kernel. I haven't rooted yet.
Click to expand...
Click to collapse
Did you have the "unmount of /system failed: no such volume" while flashing the rom zip?

mattgrantlackey said:
Did you have the "unmount of /system failed: no such volume" while flashing the rom zip?
Click to expand...
Click to collapse
Yes, and a similar error about /data

JaMeVu said:
Recommended Recovery is TWRP 2.8.1.0
Click to expand...
Click to collapse
Same error after using ADB to flash v2.8.1.0 TWRP, full wipe, and reinstall of everything in the correct procedure. My storage is still not working.

mattgrantlackey said:
Same error after using ADB to flash v2.8.1.0 TWRP, full wipe, and reinstall of everything in the correct procedure. My storage is still not working.
Click to expand...
Click to collapse
try this
enable usb debuging via dev opt.
connect phone to pc
put files to your sd card then reboot to recovery then flash

JaMeVu said:
try this
enable usb debuging via dev opt.
connect phone to pc
put files to your sd card then reboot to recovery then flash
Click to expand...
Click to collapse
I always enable usb debugging, didn't help. And as far as the file transfer, it won't let me. I can only access it while in TWRP. All my files are there, its just android can't see them, and wont show under windows either. Not sure what the issue is there, I've tried everything I know of. I'll just flash CM12 that I was using before. Let me know if you figure out this problem, as I'm curious as to what is causing it (and I'm not the only one having it).

mattgrantlackey said:
Wont let me. I can only access it while in TWRP. All my files are there, its just android can't see them, and wont show under windows either. Not sure what the issue is there, I've tried everything I know of. I'll just flash CM12 that I was using before. Let me know if you figure out this problem, as I'm curious as to what is causing it (and I'm not the only one having it).
Click to expand...
Click to collapse
re plug usb cable take it of then plug
no we do not have this kind of problem here many phones we tested and flashed

JaMeVu said:
re plug usb cable take it of then plug
no we do not have this kind of problem here many phones we tested and flashed
Click to expand...
Click to collapse
Same problems as me:
spupuz said:
does the internal storage work for you? it works only on twrp for me :/
i can't see anything in file explorer and canìt restore from twrp :/ that's a big problem guys.
Click to expand...
Click to collapse
spupuz said:
big big problem can't see the internal storage partition at all.
Click to expand...
Click to collapse

mattgrantlackey said:
Same problems as me:
spupuz said:
big big problem can't see the internal storage partition at all.
Click to expand...
Click to collapse
try re flash everything but not autoroot using..
Click to expand...
Click to collapse

try re flash everything but not autoroot using..[/QUOTE]
All of this was without autoroot. Don't worry about it man, I just installed my old rom. For some reason this ROM doesn't like me and spupuz's phone. Thanks for trying to help me, I appreciate your time. Let me know if someone else has the issue and you figure it out, I'm very curious as to what it might be.

mattgrantlackey said:
try re flash everything but not autoroot using..
Click to expand...
Click to collapse
All of this was without autoroot. Don't worry about it man, I just installed my old rom. For some reason this ROM doesn't like me and spupuz's phone. Thanks for trying to help me, I appreciate your time. Let me know if someone else has the issue and you figure it out, I'm very curious as to what it might be.[/QUOTE]
ok but we test it many phones and 1500+ downloads
may be u are using multirom ? or multirom twrp ?

JaMeVu said:
ok but we test it many phones and 1500+ downloads
may be u are using multirom ? or multirom twrp ?
Click to expand...
Click to collapse
Nope, no multirom or multirom twrp. I have no idea.

After rooting If you can not see your old nandroid backups
Via file explorers try to enable usb debuging from
dev. opt. if not worked (Recovires or SuperSU issue)
But you can see and restore your old or new backups via recovery (TWRP tested)
New recoveries and superSU may fix this issues.
Want to ask? SuperSU XDA Thread here
Note: SE Linux Mod Changer may help to fix this issue
Recommended Recovery is TWRP 2.8.1.0
​

I flashed this ROM this morning, and I initially had the weird can't unmount /system error. I rewiped, using twrp to ensure that /system was wiped too. Install went fine. I have a weird glitch or something on my recent apps list, though. I attached a picture. Anyone know what this is? It doesn't seem to be causing any functional problem, but it looks bad.
Edit: I cleared the cache for google now launcher, and restarted recovery and wiped my cache partition and the error went away.

Potentially bricked S4 (GT-I9505)?

Hello all,
I decided to install a recovery mode called Philz touch v6.07.6, which completed successfully and I can access to both download mode and this recovery menu. Then used Kingroot to root the phone. I then tried to use the ADB system to install a ROM due to not having an SD card at the time. I had chosen the option to clean install which deleted cache and formatted certain folders. The installation process then failed and I can only access download mode and recovery and my phone does not connect to my laptop anymore, or any other. I cannot seem to connect my phone to any computer, either with different cables or USB port.
I've uninstalled KIES, smart switch. uninstalled and reinstalled all drivers but my phone still does not connect to Odin or ADB server. I cannot install a new recovery menu as I cannot see my phone on Odin.
Thinking an SD card with a ROM would resolve the issue I purchased a card, added a ROM to it but I cannot find anything I put on the sd card. Choosing install from zip then SD card it shows clockworkmod/ but nothing else. Using free browse mode i've looked into every folder and cannot find anything that is on my SD card. I see no option under mounts and storage to mount the SD card
Thank you for your time and if you can advise me on what I am doing wrong.
Edit: I forgot to mention - When powering the phone on normally without trying to get into recovery or download mode, the top left of the screen says:
"Kernel is not seanandroid enforcing"
Set Warranty Bit : kernel

You do realize the S4 has an internal storage, right? It's a built-in microSD card.
So you absolutely don't need one to use and/or flash custom ROMs on it.
Your second mistake was flashing PhilZ recovery. It's a mistake because that recovery is outdated.
Your third mistake was trying to flash the ROM via ADB when you can simply flash it with the recovery.
The reason why the ROM zip doesn't show up in your recovery id because, most probably, the internal storage is selected by default. So, either navigate to the microSD card folder or move the ROM zip to your internal storage.
I also recommend switching to TWRP recovery.

@Aysta, if it's not too late for you, just flash the latest twrp Recovery ". Tar. File" in Odin (>AP) by switching off the device in download mode. After that just copy your desired custom rom and gapps to your sd-card by an sd-card reader in Windows and the rest you know, which as i assume, will follow... [emoji6]
P. S I just experienced the same yesterday evening when i bricked one of my Sammy's while using an experimental kernel (. Img) file.
Anyhow, this just solved everything for me [emoji4]

Aysta said:
Hello all,
I decided to install a recovery mode called Philz touch v6.07.6, which completed successfully and I can access to both download mode and this recovery menu. Then used Kingroot to root the phone. I then tried to use the ADB system to install a ROM due to not having an SD card at the time. I had chosen the option to clean install which deleted cache and formatted certain folders. The installation process then failed and I can only access download mode and recovery and my phone does not connect to my laptop anymore, or any other. I cannot seem to connect my phone to any computer, either with different cables or USB port.
I've uninstalled KIES, smart switch. uninstalled and reinstalled all drivers but my phone still does not connect to Odin or ADB server. I cannot install a new recovery menu as I cannot see my phone on Odin.
Thinking an SD card with a ROM would resolve the issue I purchased a card, added a ROM to it but I cannot find anything I put on the sd card. Choosing install from zip then SD card it shows clockworkmod/ but nothing else. Using free browse mode i've looked into every folder and cannot find anything that is on my SD card. I see no option under mounts and storage to mount the SD card
Thank you for your time and if you can advise me on what I am doing wrong.
Edit: I forgot to mention - When powering the phone on normally without trying to get into recovery or download mode, the top left of the screen says:
"Kernel is not seanandroid enforcing"
Set Warranty Bit : kernel
Click to expand...
Click to collapse
You have to get your phone working with Odin, it's your only way out.
lekiaM said:
@Aysta, if it's not too late for you, just flash the latest twrp Recovery ". Tar. File" in Odin (>AP) by switching off the device in download mode. After that just copy your desired custom rom and gapps to your sd-card by an sd-card reader in Windows and the rest you know, which as i assume, will follow... [emoji6]
P. S I just experienced the same yesterday evening when i bricked one of my Sammy's while using an experimental kernel (. Img) file.
Anyhow, this just solved everything for me [emoji4]
Click to expand...
Click to collapse
Odin doesn't detect his device, read his full post.

MigoMujahid said:
You have to get your phone working with Odin, it's your only way out.
Odin doesn't detect his device, read his full post.
Click to expand...
Click to collapse
"this doesnt make sense than, either"
And i overlooked it. Can happen mate.

Thank you for your assistance guys, i've still not been able to flash a new recovery as my phone just will not connect. I read installing older drivers helps but it didn't. Older odin didn't work. I need to access an operating system which isn't Windows 10 according to another website. So will create a virtual machine and let you all know how it goes.

Ubuntu has worked! i installed jodin3 and my phone shows up on there while in download mode

lekiaM said:
"this doesnt make sense than, either"
And i overlooked it. Can happen mate.
Click to expand...
Click to collapse
Aysta said:
Ubuntu has worked! i installed jodin3 and my phone shows up on there while in download mode
Click to expand...
Click to collapse
That's why i told you it's the Only way, Odin must detect your phone, otherwise you're screwed.