Hi all,
I've noticed that while I'm booted in recovery mode, my phone is not installed properly as shown here:
I've tried reinstalling Kies, installing only the latest Samsung USB drivers but it won't work in recovery. However, in DL mode and when booted up in Android, it works normally. I've also tried uninstalling the device from Device Manager and reinstall the drivers manually by pointing to the folder, but no drivers are found.
I'm using TWRP v.2.5.0.2 and I've pressed the "Mount USB Storage" button, but it doesn't make any difference.
The other day when I was trying a custom ROM and I accidently erased the internal memory, realizing that I also wiped out the ROM itself, it would've eased things alot if this would've worked..
I've searched around about this, but all I could find was people recommending to reinstall Kies or the drivers. Well, I've done that a couple of times and it doesn't make a difference.
Anyone know how to fix this?
Thanks!
My Device:
i9505
Stock ROM 4.2.2
I9505XXUAME2
I, too, find that my PC does not connect successfully to the phone in recovery.
I've tried various recoveries and the only one that gave me a successful connection, I seem to recall, was this one http://forum.xda-developers.com/showthread.php?p=42665827.
So try different recoveries.
However, since I use Odin this is not a problem for me. I'm also using TWRP.
Sent from my GT-I9505
Yeah, I use Odin too, but it would be nice to know that if sh*t hits the fan, you're able to xfer files in recovery mode. Does anyone else have any insight on this? Is it possible to solve this driver issue?
Marthax said:
Hi all,
I've noticed that while I'm booted in recovery mode, my phone is not installed properly as shown here:
I've tried reinstalling Kies, installing only the latest Samsung USB drivers but it won't work in recovery. However, in DL mode and when booted up in Android, it works normally. I've also tried uninstalling the device from Device Manager and reinstall the drivers manually by pointing to the folder, but no drivers are found.
I'm using TWRP v.2.5.0.2 and I've pressed the "Mount USB Storage" button, but it doesn't make any difference.
The other day when I was trying a custom ROM and I accidently erased the internal memory, realizing that I also wiped out the ROM itself, it would've eased things alot if this would've worked..
I've searched around about this, but all I could find was people recommending to reinstall Kies or the drivers. Well, I've done that a couple of times and it doesn't make a difference.
Anyone know how to fix this?
Thanks!
My Device:
i9505
Stock ROM 4.2.2
I9505XXUAME2
Click to expand...
Click to collapse
I'm using Philz Touch (based on CWM) and I have no problem. I can even mount the SD card and write/read it from Windows. I'm not using KIES at all and the drivers were installed by Windows 8 from Microsoft Update the first time I connected my i9505 to my PC.
Is Windows 8 what you use as an OS for you PC ? Even with prior versions, try to force Windows to automatically download the drivers when the phone is connected in normal (not recovery) mode.
I can confirm that using the drivers that Windows 8 installs and using the latest version of PhilZ's recovery enables an ADB connection in recovery.
Sent from my GT-I9505
Installed PhilZ's and that fixed it !
I'm using Windows 7 BTW.
Marthax said:
Installed PhilZ's and that fixed it !
I'm using Windows 7 BTW.
Click to expand...
Click to collapse
Happy for you ! Hope it could help someone else
Just as a sidenote, I noticed now that when I wiped before flashing latest nightly CM and flash failed, I tried to connect using the "Mount USB" to transfer the zip file once again but it didn't come up in Win 7 at all. The device was invisible all of a sudden.. Tried changing USB port and reconnecting again, rebooting into recovery once more, but the problem persisted. Luckily, when I rebooted into recovery again and wiped once more, the flash succeeded. Phew..
I'm encountering a strange issue. After flashing TWRP 2.8.0.0 over my TWRP 2.7.2.1 install the phone is no longer recognized by Windows in recovery mode. When I connect the phone during regular system operation everything works including ADB.
When I reboot in recovery, Windows starts the "unknown device" wizard but fails to find the correct drivers. What am I missing guys?
AO7 said:
I'm encountering a strange issue. After flashing TWRP 2.8.0.0 over my TWRP 2.7.2.1 install the phone is no longer recognized by Windows in recovery mode. When I connect the phone during regular system operation everything works including ADB.
When I reboot in recovery, Windows starts the "unknown device" wizard but fails to find the correct drivers. What am I missing guys?
Click to expand...
Click to collapse
It's a problem of TWRP, nothing on your end. Philz recovery works.
Related
I'll try to make this brief.. long-time lurker, first time poster.
My Nexus 4 currently is in a brick state. I had PA 3.99 RC2 installed, and when attempting to flash a new font file, the device will now no longer boot, stalling at the boot logo. I foolishly did not make a back-up (though I thought I did.. probably tapped the wrong button). From that point, I tried a data wipe as well as a cache/dalvik cache wipe, and the same thing happens.
I have an old back-up (about a week or 2) on my phone from a different ROM (I believe MIUI) but when I attempt to restore it with Clockwork Mod Recover I get an "md5 mismatch error."
Currently, I do not have the proper Nexus 4 drivers on my computer - when I plug my device in, it does not show up for me to drag/drop anything in to it to flash it. Is it still possible to install the proper USB drivers in its current state?
I plan to try installing the drivers and android SDK and then sideloading a ROM onto it with ADB, but I'm not sure if I'll be able to install the drivers properly for the phone to show up on my computer, and I won't be able to check until I get back to my desktop computer (my laptop has restricted privileges so I can't install drivers) until tomorrow.
Anyone else have any other ideas or suggestions? Please let me know.
Kirbyscream said:
I'll try to make this brief.. long-time lurker, first time poster.
My Nexus 4 currently is in a brick state. I had PA 3.99 RC2 installed, and when attempting to flash a new font file, the device will now no longer boot, stalling at the boot logo. I foolishly did not make a back-up (though I thought I did.. probably tapped the wrong button). From that point, I tried a data wipe as well as a cache/dalvik cache wipe, and the same thing happens.
I have an old back-up (about a week or 2) on my phone from a different ROM (I believe MIUI) but when I attempt to restore it with Clockwork Mod Recover I get an "md5 mismatch error."
Currently, I do not have the proper Nexus 4 drivers on my computer - when I plug my device in, it does not show up for me to drag/drop anything in to it to flash it. Is it still possible to install the proper USB drivers in its current state?
I plan to try installing the drivers and android SDK and then sideloading a ROM onto it with ADB, but I'm not sure if I'll be able to install the drivers properly for the phone to show up on my computer, and I won't be able to check until I get back to my desktop computer (my laptop has restricted privileges so I can't install drivers) until tomorrow.
Anyone else have any other ideas or suggestions? Please let me know.
Click to expand...
Click to collapse
Adb works in recovery, so you can install adb drivers, then use "adb push" or "adb sideload". Try installing the same ROM version you had before (PA). It might work, and also save your data.
abaaaabbbb63 said:
Adb works in recovery, so you can install adb drivers, then use "adb push" or "adb sideload". Try installing the same ROM version you had before (PA). It might work, and also save your data.
Click to expand...
Click to collapse
Took awhile to get ADB drivers to work (fastboot was recognizing it fine)... pushed over the .zip file and just installed it, and everything works great! Thank you!
This isn't my phone. It was just running the stock OS with root. I think what happened is that an update from tmobile was released, and got installed, which corrupted the ROM/OS. The only backup it has is a couple of months old. I've tried wiping data/system/caches and factory resets which did not work. I've also tried restoring from the backup; just system, then both data and system, and no results.
Currently it has no ROM on it that I can install.
No matter what I do it always reboots back to TWRP. It has TWRP 2.6.3.2
I've tried to mount the SD card from the Mount menu so I can push a ROM to it, which doesn't work.
I've tried using ADB sideload but it doesn't seem to start, and I'm not able to see the device from command line with 'adb devices'
I've tried using the LG PC Suite, but it also cannot detect the device.
Please help, thanks!
brickwall99 said:
This isn't my phone. It was just running the stock OS with root. I think what happened is that an update from tmobile was released, and got installed, which corrupted the ROM/OS. The only backup it has is a couple of months old. I've tried wiping data/system/caches and factory resets which did not work. I've also tried restoring from the backup; just system, then both data and system, and no results.
Currently it has no ROM on it that I can install.
No matter what I do it always reboots back to TWRP. It has TWRP 2.6.3.2
I've tried to mount the SD card from the Mount menu so I can push a ROM to it, which doesn't work.
I've tried using ADB sideload but it doesn't seem to start, and I'm not able to see the device from command line with 'adb devices'
I've tried using the LG PC Suite, but it also cannot detect the device.
Please help, thanks!
Click to expand...
Click to collapse
sounds like you dont have lg drivers installed. can get them from the lg g2 official website.
freebee269 said:
sounds like you dont have lg drivers installed. can get them from the lg g2 official website.
Click to expand...
Click to collapse
Is that what would prevent side load from working?
I've installed the drivers previously, and can use adb/USB storage with my LG G2.
brickwall99 said:
Is that what would prevent side load from working?
I've installed the drivers previously, and can use adb/USB storage with my LG G2.
Click to expand...
Click to collapse
you said you see no adb devices, this usually means the adb drivers are not installed. no adb drivers = no sideload. also make sure you are in twrp when you are trying to use adb. also i'd recommend updating to twrp 2.6.3.3 from the official twrp site, it's much better than 2.6.3.2. also if you are using an outdated adb.exe that will give you adb problems. can get the latest from android website.
freebee269 said:
you said you see no adb devices, this usually means the adb drivers are not installed. no adb drivers = no sideload. also make sure you are in twrp when you are trying to use adb. also i'd recommend updating to twrp 2.6.3.3 from the official twrp site, it's much better than 2.6.3.2. also if you are using an outdated adb.exe that will give you adb problems. can get the latest from android website.
Click to expand...
Click to collapse
Well, I have no way to transfer any files to the phone, so I can't install the new recovery. All I need to do is be able to push a ROM file to the phone, I think, so I can install it.
I am using adb sideload from recovery. I'm not aware of another location to do so. It just sits at the prompt saying starting sideload...
brickwall99 said:
Well, I have no way to transfer any files to the phone, so I can't install the new recovery. All I need to do is be able to push a ROM file to the phone, I think, so I can install it.
I am using adb sideload from recovery. I'm not aware of another location to do so. It just sits at the prompt saying starting sideload...
Click to expand...
Click to collapse
that's because you have no adb connection. no connection = no pushing files. that's why i said you need to get adb working first.
I installed the universal adb driver and now 'adb devices' does show the device, and I'm transferring the ROM with adb sideload 'filename', so hopefully this will work.
Thanks!
brickwall99 said:
I installed the universal adb driver and now 'adb devices' does show the device, and I'm transferring the ROM with adb sideload 'filename', so hopefully this will work.
Thanks!
Click to expand...
Click to collapse
good news. hope you get up and running now. still update your twrp.
freebee269 said:
good news. hope you get up and running now. still update your twrp.
Click to expand...
Click to collapse
Okay I got the ROM transferred and I have installed it successfully.
Using this one: http://forum.xda-developers.com/showthread.php?t=2598361
But when I reboot it goes straight to recovery.
A factory reset fails. I'm only able to advanced wipe of system/data, also it fails when I wipe cache or dalvik.
So I've tried wiping system/data, then installing the ROM again, and it just reboots straight back to recovery.
I sideloaded TWRP 2.6.3.5 for tmobile. Verified it shows 2.6.3.5 TWRP now. I'll try to sideload/install the ROM again.
Edit: When trying to factory reset it says failed to mount cache.
Okay so I have successfully installed the ROM with TWRP 2.6.3.5 and when I reboot it still goes straight into recovery.
What next?
Thanks
Edit: Is there perhaps something wrong with the bootloader, or what? I'm thinking part of the issue is because I can't mount or wipe cache/dalvik?
I'm in the exact same position with the d800. Stuck in twrp. I think we need to sideload a working boot.img. Idk. I was working on it all night reading everything I could about adb because although I had the lg drivers and my PC recognized my phone was connected it would give me a driver error. Thus I couldn't use the flash tool. Can you get to download mode?
from my Note Thrizzle
rawb123456 said:
I'm in the exact same position with the d800. Stuck in twrp. I think we need to sideload a working boot.img. Idk. I was working on it all night reading everything I could about adb because although I had the lg drivers and my PC recognized my phone was connected it would give me a driver error. Thus I couldn't use the flash tool. Can you get to download mode?
from my Note Thrizzle
Click to expand...
Click to collapse
How do you start download mode?
I was able to mount cache now, after unchecking format setting (use rm instead of -rf), but after doing factory reset and advanced wipe (everything except internal storage), then installing ROM, it still reboots straight back into recovery. Damn.
Any luck? I tried flashing CM11 on TWRP 2.6.3.2 (per XDA instructions) and it failed. Now I am stuck in recovery and can't ADB new recovery
brickwall99 said:
How do you start download mode?
I was able to mount cache now, after unchecking format setting (use rm instead of -rf), but after doing factory reset and advanced wipe (everything except internal storage), then installing ROM, it still reboots straight back into recovery. Damn.
Click to expand...
Click to collapse
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
Hey guys! I'm not a developer. I unlocked the bootloader of my Nexus 4 and rooted it. Along with that i even installed a matrix kernel. So now what happened is my phone wouldn't display anything after starting up but it was connecting to my PC as i had enabled USB debugging mode. But as the phone wasn't starting, i formatted everything except the sd card, cleared the cache and dalvik cache and reinstalled the franco kernel. Even that didn't start so i downloaded CM 11 nightly version and tried to install it, but it didn't get installed. I installed the matrix kernel again and tried to install CM 11 but even then it didn't get installed. Now my phone is stuck on the google logo and the only thing i can do is go to the bootloader, recovery etc. but I can't connect it to my PC as i had factory reset it, the USB debugging had stopped. Basically i just need help in figuring out what should i do. I'm ready to have my phone back to its stock settings and i'm even ready to keep my phone rooted. I just need a way for it to start working. Please guys!! Some help here!!
Don't panic. The first thing you need to do is flash the factory image in fastboot. After you get your phone back then you need to read a lot before you flash anything again
Sent from my Nexus 5 using XDA Free mobile app
hm.madkhn said:
Hey guys! I'm not a developer. I unlocked the bootloader of my Nexus 4 and rooted it. Along with that i even installed a matrix kernel. So now what happened is my phone wouldn't display anything after starting up but it was connecting to my PC as i had enabled USB debugging mode. But as the phone wasn't starting, i formatted everything except the sd card, cleared the cache and dalvik cache and reinstalled the franco kernel. Even that didn't start so i downloaded CM 11 nightly version and tried to install it, but it didn't get installed. I installed the matrix kernel again and tried to install CM 11 but even then it didn't get installed. Now my phone is stuck on the google logo and the only thing i can do is go to the bootloader, recovery etc. but I can't connect it to my PC as i had factory reset it, the USB debugging had stopped. Basically i just need help in figuring out what should i do. I'm ready to have my phone back to its stock settings and i'm even ready to keep my phone rooted. I just need a way for it to start working. Please guys!! Some help here!!
Click to expand...
Click to collapse
Relax!
Download the Nexus 4 factory image from Google and flash it using fastboot from your PC.
This will revert the phone to pure stock unrooted settings and then just try rooting the phone again from there.
Check of your kernel and ROM files were proper, if they were corrupted then it could have lead to the bootloop
rondias18 said:
Relax!
Download the Nexus 4 factory image from Google and flash it using fastboot from your PC.
This will revert the phone to pure stock unrooted settings and then just try rooting the phone again from there.
Check of your kernel and ROM files were proper, if they were corrupted then it could have lead to the bootloop
Click to expand...
Click to collapse
Hey! Thanks for the help but the USB debugging mode in my phone is switched off as i had reset it. So basically i can't connect it to my PC.
It shows under device manager etc but doesn't show in My Computer. I'm running Windows 8 64 bit.
rondias18 said:
Relax!
Download the Nexus 4 factory image from Google and flash it using fastboot from your PC.
This will revert the phone to pure stock unrooted settings and then just try rooting the phone again from there.
Check of your kernel and ROM files were proper, if they were corrupted then it could have lead to the bootloop
Click to expand...
Click to collapse
And by the way, I downloaded CM11 Nightly but it couln't get installed due to some error and before installing the ROM i installed the matrix kernel but after installing, the phone didn't start. It showed the starting animation but did not start the phone up. Can you please tell me how to enable USB Debugging from CWM Recovery? Coz it's stuck on the Google logo and i can't start it, so neither can I enable the USB debugging mode.
Is your recovery up to date? If not please flash the latest one or flash trwp recovery instead. Use adb sideload, since you cant access your usb debugging
hm.madkhn said:
Hey! Thanks for the help but the USB debugging mode in my phone is switched off as i had reset it. So basically i can't connect it to my PC.
It shows under device manager etc but doesn't show in My Computer. I'm running Windows 8 64 bit.
Click to expand...
Click to collapse
You don't need USB debugging for fastboot. Download the factory stuff from google, turn off device, hold volume down and boot up device (i.e. into bootloader), and run the "flash-all.bat" (after extracting the downloaded file) .. This will wipe your data. If you want to keep data, open the flash-all.bat file and remove the "-w" from the last line.
Marvlesz said:
You don't need USB debugging for fastboot. Download the factory stuff from google, turn off device, hold volume down and boot up device (i.e. into bootloader), and run the "flash-all.bat" (after extracting the downloaded file) .. This will wipe your data. If you want to keep data, open the flash-all.bat file and remove the "-w" from the last line.
Click to expand...
Click to collapse
Remove userdata.img too or it will overwrite your apps
Sent from my SAMSUNG-SGH-I727 using XDA Free mobile app
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.