Related
edit: on a whim I looked at the heimdall command line options and saw "close pc screen" as one of the arguments and tried that and it booted up perfectly!!!!! So relieved it was something that simple!
I got my S4 last night and immediately tried to root it after I got it, I read up on some stuff (not new to rooting, I've rooted multiple devices in the past) and attempted to flash TWRP via Odin but then it said it failed for some reason, I tried again and it failed. I figured everything was fine until I rebooted and got "Firmware upgrade encountered an issue. Please select recovery mode in kies and try again." I tried to connect it to my old Windows XP pc (my main pc runs Arch Linux) and kies kept saying "connecting" no matter how many times I tried to make it connect or reinstall the drivers.
I can get to download mode and I'm trying to flash the stock firmware via heimdall but it's taking forever to uncompress the image. I got the images from here: http://forum.xda-developers.com/showthread.php?t=2258628
I tried to flash cf-autoroot with heimdall in hopes that it would restore my bootloader but it wouldn't flash because it said it was missing an XML file.
I think I'm just missing the bootloader/recovery image but I'm not sure. Am I heading in the right direction?
If you have root and still have access to the phone when u turn it on flash cwm recovery via Odin or if Ur phone turns on nd have root then download goomanager nd you can install twrp with that app with no problems
Sent from my SGH-M919 using xda premium
im having the same issue...
i am flashing Modem_UVUAMDL.tar and philz touch 5.08.5-jfltetmo as recovery, OUDHS jfltetmo also, but nothing is working
i was running infamous 4.0 ROM, flashed the cyanogenmod nightly and somehow everything exploded and now the only thing on my screen is the SGS4 stock image... it wont boot into recovery mode only download.
i am on an OSX using heimdall and i do not ever have access to a PC!
icecreamwithyou said:
im having the same issue...
i am flashing Modem_UVUAMDL.tar and philz touch 5.08.5-jfltetmo as recovery, OUDHS jfltetmo also, but nothing is working
i was running infamous 4.0 ROM, flashed the cyanogenmod nightly and somehow everything exploded and now the only thing on my screen is the SGS4 stock image... it wont boot into recovery mode only download.
i am on an OSX using heimdall and i do not ever have access to a PC!
Click to expand...
Click to collapse
Did you find a fix I have the same issue but I do have a pc?
brando56894 said:
edit: on a whim I looked at the heimdall command line options and saw "close pc screen" as one of the arguments and tried that and it booted up perfectly!!!!! So relieved it was something that simple!
I got my S4 last night and immediately tried to root it after I got it, I read up on some stuff (not new to rooting, I've rooted multiple devices in the past) and attempted to flash TWRP via Odin but then it said it failed for some reason, I tried again and it failed. I figured everything was fine until I rebooted and got "Firmware upgrade encountered an issue. Please select recovery mode in kies and try again." I tried to connect it to my old Windows XP pc (my main pc runs Arch Linux) and kies kept saying "connecting" no matter how many times I tried to make it connect or reinstall the drivers.
I can get to download mode and I'm trying to flash the stock firmware via heimdall but it's taking forever to uncompress the image. I got the images from here: http://forum.xda-developers.com/showthread.php?t=2258628
I tried to flash cf-autoroot with heimdall in hopes that it would restore my bootloader but it wouldn't flash because it said it was missing an XML file.
I think I'm just missing the bootloader/recovery image but I'm not sure. Am I heading in the right direction?
Click to expand...
Click to collapse
I just recently purchased a rooted S4 and I downloaded a ROM from this site that wasn't compatible with my S4 and flashed it (BIG mistake I know now). So now I can't start up my phone. I read here that I should wipe out the divalk cache/cache and restart (didn't work). Reset to factory settings and reboot (didn't work). Download the TWRP flashable zip and flash it from the Recovery memory then reboot (didn't work). Now I'm really worried. Can you please help me?
Warrior1016 said:
I just recently purchased a rooted S4 and I downloaded a ROM from this site that wasn't compatible with my S4 and flashed it (BIG mistake I know now). So now I can't start up my phone. I read here that I should wipe out the divalk cache/cache and restart (didn't work). Reset to factory settings and reboot (didn't work). Download the TWRP flashable zip and flash it from the Recovery memory then reboot (didn't work). Now I'm really worried. Can you please help me?
Click to expand...
Click to collapse
What does it do when you boot up?
Hello all,
Quick background - my wife's T-Mobile S4 went kaput on our honeymoon last night, but I was at least able to save some of her data. The problem now goes to installing a new ROM on her device.
I have wiped EVERYTHING and formatted the data, but when I install ANY ROM (I've tried multiple), I always get the E: Unable to mount '/data" error. Normally, I would just ODIN the stock tar, then install a custom recovery again and then the ROM, but I only have my work computer for the rest of my honeymoon and I don't have administrative access to run ODIN (you might not think it requires it, but if you're only a standard user then you cannot bypass UAC to run it).
Does anyone have any ideas on how to get this to mount? The phone will not boot past the "Samsung Galaxy S4" screen. I've tried going into TWRP and mounting Data but it will not work.
Any help is greatly appreciated! Please keep in mind that I don't have access to ODIN!
- Taxmaster
Taxmaster said:
Hello all,
Quick background - my wife's T-Mobile S4 went kaput on our honeymoon last night, but I was at least able to save some of her data. The problem now goes to installing a new ROM on her device.
I have wiped EVERYTHING and formatted the data, but when I install ANY ROM (I've tried multiple), I always get the E: Unable to mount '/data" error. Normally, I would just ODIN the stock tar, then install a custom recovery again and then the ROM, but I only have my work computer for the rest of my honeymoon and I don't have administrative access to run ODIN (you might not think it requires it, but if you're only a standard user then you cannot bypass UAC to run it).
Does anyone have any ideas on how to get this to mount? The phone will not boot past the "Samsung Galaxy S4" screen. I've tried going into TWRP and mounting Data but it will not work.
Any help is greatly appreciated! Please keep in mind that I don't have access to ODIN!
- Taxmaster
Click to expand...
Click to collapse
Sounds like a twrp issue. Try grabbing the cwm flash able zip and adb push to the sd card and then use twrp to install it. I've read so many issues about twrp. I recommend staying away from it. Philz touch recovery is really awesome too.
Sent from my SGH-M919 using Tapatalk 2
elesbb said:
Sounds like a twrp issue. Try grabbing the cwm flash able zip and adb push to the sd card and then use twrp to install it. I've read so many issues about twrp. I recommend staying away from it. Philz touch recovery is really awesome too.
Sent from my SGH-M919 using Tapatalk 2
Click to expand...
Click to collapse
Hello! I actually downloaded Philz touch recovery in both .zip and in .md5, so that is what I intend to go with. The issue is how I push it using adb, as I believe I need to install something in order to do so, but I don't have any administrative privileges! This is what's preventing me from running ODIN in the first place!
Can you confirm that I can push using adb without installing anything?
Thank you! - Taxmaster
I had this issue. Odin flashing and then booting into "STOCK RECOVERY" after flashing and then a factory reset in the stock recovery followed by a fresh re-flash from Odin worked to get my phone back up and running again.
I don't know how you are going to be able to fix it by just flashing a recovery. I tried for hours and could not get it to boot from just recovery alone.
Monkz said:
I had this issue. Odin flashing and then booting into "STOCK RECOVERY" after flashing and then a factory reset in the stock recovery followed by a fresh re-flash from Odin worked to get my phone back up and running again.
I don't know how you are going to be able to fix it by just flashing a recovery. I tried for hours and could not get it to boot from just recovery alone.
Click to expand...
Click to collapse
What you noted would be my plan if I had admin rights to my computer, but since I cannot get ODIN, I'm screwed at the moment. I'm hoping someone can assist with the "adb" proposal, however I'm not sure one can download/run adb without installation or prompt from UAC
Taxmaster said:
What you noted would be my plan if I had admin rights to my computer, but since I cannot get ODIN, I'm screwed at the moment. I'm hoping someone can assist with the "adb" proposal, however I'm not sure one can download/run adb without installation or prompt from UAC
Click to expand...
Click to collapse
I don't believe admin is required for adb... You could always try it... worst thing that could happen would be nothing.
lordcheeto03 said:
I don't believe admin is required for adb... You could always try it... worst thing that could happen would be nothing.
Click to expand...
Click to collapse
Using ADB does not require admin privelages, however, if your computer does not have the necessary drivers to detect the device in recovery, then you will have to install the drivers, which then yes UAC is required. HOWEVER, if you have another phone or device that supports MicroSD cards, you can just pop in the MicroSD into a working device and transfer the zip that way, then transfer back the sd card and flash
elesbb said:
Using ADB does not require admin privelages, however, if your computer does not have the necessary drivers to detect the device in recovery, then you will have to install the drivers, which then yes UAC is required. HOWEVER, if you have another phone or device that supports MicroSD cards, you can just pop in the MicroSD into a working device and transfer the zip that way, then transfer back the sd card and flash
Click to expand...
Click to collapse
I did exactly what's noted above --> took out the SDcard, put it in another phone, transferred over the .zip, put it back in her phone, went to TWRP, wiped everything on the device, installed the .zip, and rebooted into recovery from TWRP, and then the new recovery booted! I did another wipe/factory reset and then installed a ROM, but when I hit reboot, it didn't reboot past the Samsung Galaxy S4 splash screen , and to make matters worse, when I go to enter recovery pressing home+up+power, it says "Recovery Booting ...." in the top left corner but it won't boot into recovery!!!
Thoughts?
If someone could strip administrative privileges off of a version of ODIN v3 for me, that would be great! I don't see how else to get around this now!
-Taxmaster
Taxmaster said:
I did exactly what's noted above --> took out the SDcard, put it in another phone, transferred over the .zip, put it back in her phone, went to TWRP, wiped everything on the device, installed the .zip, and rebooted into recovery from TWRP, and then the new recovery booted! I did another wipe/factory reset and then installed a ROM, but when I hit reboot, it didn't reboot past the Samsung Galaxy S4 splash screen , and to make matters worse, when I go to enter recovery pressing home+up+power, it says "Recovery Booting ...." in the top left corner but it won't boot into recovery!!!
Thoughts?
If someone could strip administrative privileges off of a version of ODIN v3 for me, that would be great! I don't see how else to get around this now!
-Taxmaster
Click to expand...
Click to collapse
Out of curiosity, are you flashing a ROM for the T-Mobile S4? If no, are you using a T-Mobile kernel? I only ask because a kernel for a different device will normally cause you to not be able to pass the initial Galaxy S4 screen... Also, as far as TWRP goes, sometimes it doesn't go right into recovery. If it fails to enter recovery after a reasonable amount of time, just hold power to turn it off and try again. I've had to do it 2-3 times at least just to successfully enter TWRP.
lordcheeto03 said:
Out of curiosity, are you flashing a ROM for the T-Mobile S4? If no, are you using a T-Mobile kernel? I only ask because a kernel for a different device will normally cause you to not be able to pass the initial Galaxy S4 screen... Also, as far as TWRP goes, sometimes it doesn't go right into recovery. If it fails to enter recovery after a reasonable amount of time, just hold power to turn it off and try again. I've had to do it 2-3 times at least just to successfully enter TWRP.
Click to expand...
Click to collapse
I am installing a T-Mobile S4 ROM that uses a custom kernel. The ROM before was the same ROM just a lower revision, same kernel.
With respect to TWRP, I thought it was all gone now that I installed the CWM touch version. I've tried doing it a million times and cannot get back into either TWRP or CWM. At this point, the only thing I can do is turn on the device to see the "Samsung Galaxy S4" screen, attempt booting into recovery but never make it past the screen saying "Recovery Booting", or enter Download Mode but I cannot use it since I can't run ODIN on my work laptop .... stupid admin privileges!
Taxmaster said:
I am installing a T-Mobile S4 ROM that uses a custom kernel. The ROM before was the same ROM just a lower revision, same kernel.
With respect to TWRP, I thought it was all gone now that I installed the CWM touch version. I've tried doing it a million times and cannot get back into either TWRP or CWM. At this point, the only thing I can do is turn on the device to see the "Samsung Galaxy S4" screen, attempt booting into recovery but never make it past the screen saying "Recovery Booting", or enter Download Mode but I cannot use it since I can't run ODIN on my work laptop .... stupid admin privileges!
Click to expand...
Click to collapse
Not sure what happened there.. very strange. But seems as if you have no recovery xD lol Maybe heimdall will work. Never used it not sure if it needs UAC to work. But dont use TWRP anymore
As far as your situation goes, maybe if you have the time and fast enough internet, see if you can download a linux distro (i recommend fedora as it is small and light) then make a bootable USB from that distro (if you have a flash drive) then use Heimdall in linux to flash the tar image.
Or just wait to get home. not sure how long your honeymoon is xD
elesbb said:
Not sure what happened there.. very strange. But seems as if you have no recovery xD lol Maybe heimdall will work. Never used it not sure if it needs UAC to work. But dont use TWRP anymore
As far as your situation goes, maybe if you have the time and fast enough internet, see if you can download a linux distro (i recommend fedora as it is small and light) then make a bootable USB from that distro (if you have a flash drive) then use Heimdall in linux to flash the tar image.
Or just wait to get home. not sure how long your honeymoon is xD
Click to expand...
Click to collapse
I think I just need to accept that fact that I have been had and that the only thing I can do is wait until I'm home to use ODIN. Absolutely asinine in my opinion, however it seems the only logical conclusion at this point.
If anyone else cares to chime in with suggestions, please let me know!
-Taxmaster
I have had the same problem several times. The only way I have been able to boot up is to completely format data and either restore from backup or reflash a new ROM. If I wipe the dalvik cache after doing so however, it will not boot (hangs at the galaxy s4 screen like you said) and I will have to reflash or restore a 2nd time. (I'm using twrp too, but will switch to cwm if this happens again)
I m curious. Have you run into this problem again? Seems like every time my phone shuts off and tries to boot I have to restore from a backup that is days or weeks old. Super annoying. The first time this happened I restored to stock from Odin and did not use any backups in the hope that it would solve my problem and prevent it from happening again. No such luck.
coolastar said:
I have had the same problem several times. The only way I have been able to boot up is to completely format data and either restore from backup or reflash a new ROM. If I wipe the dalvik cache after doing so however, it will not boot (hangs at the galaxy s4 screen like you said) and I will have to reflash or restore a 2nd time. (I'm using twrp too, but will switch to cwm if this happens again)
I m curious. Have you run into this problem again? Seems like every time my phone shuts off and tries to boot I have to restore from a backup that is days or weeks old. Super annoying. The first time this happened I restored to stock from Odin and did not use any backups in the hope that it would solve my problem and prevent it from happening again. No such luck.
Click to expand...
Click to collapse
I ended up having to wait until I got home to use ODIN. I ODIN'd up the stock .tar and then installed Philz touch recovery (CWM-based), then I did a full wipe of everything and installed a ROM. Problem solved.
With that noted, I abandoned TWRP and am now only using CWM on my wife's phone.
Taxmaster said:
I ended up having to wait until I got home to use ODIN. I ODIN'd up the stock .tar and then installed Philz touch recovery (CWM-based), then I did a full wipe of everything and installed a ROM. Problem solved.
With that noted, I abandoned TWRP and am now only using CWM on my wife's phone.
Click to expand...
Click to collapse
Same, TWRP just has too many problems.
CWM is much more reliable.
Sent from my SGH-M919 using xda premium
Taxmaster said:
I ended up having to wait until I got home to use ODIN. I ODIN'd up the stock .tar and then installed Philz touch recovery (CWM-based), then I did a full wipe of everything and installed a ROM. Problem solved.
With that noted, I abandoned TWRP and am now only using CWM on my wife's phone.
Click to expand...
Click to collapse
If you were using TWRP 2.6.0, that could have been the problem. I reverted back to 2.5.0.2 and like many others, have had no issues. If you had a TWRP backup, that might have fixed it early on.
I got a replacement GS3 through insurance and rooted it yesterday. Instead of flashing CWM I tried going with TWRP this time but didn't realize that TWRP doesn't read external SD cards and my roms were all saved on the external SD. And of course, this was after I wiped everything. So I tried unrooting and flashing back the stock firmware but it keeps failing in ODIN. So I tried re-rooting and flashing CWM which works but none of the roms will flash. I keep getting a system 7 error or something to that effect when I try flashing any rom. So now I can either get to recovery mode, or download mode. If I power the phone on it gets stuck on the Galaxy S3 screen. Any thoughts as to processes to try? Links? Threads? I've tried just about everything I could find.
kinjo1023 said:
I got a replacement GS3 through insurance and rooted it yesterday. Instead of flashing CWM I tried going with TWRP this time but didn't realize that TWRP doesn't read external SD cards and my roms were all saved on the external SD. And of course, this was after I wiped everything. So I tried unrooting and flashing back the stock firmware but it keeps failing in ODIN. So I tried re-rooting and flashing CWM which works but none of the roms will flash. I keep getting a system 7 error or something to that effect when I try flashing any rom. So now I can either get to recovery mode, or download mode. If I power the phone on it gets stuck on the Galaxy S3 screen. Any thoughts as to processes to try? Links? Threads? I've tried just about everything I could find.
Click to expand...
Click to collapse
Since when does TWRP not read external SD cards? It see's mine just fine, for well over a year. Where is your nandroid backup, you know the one you made before you did anything just incase it didn't go as planned? In any case you didn't give much information to help troubleshoot. 'I tried unrooting' - if you were going to flash a stock ROM there is no need to unroot anything as the stock firmware is just that, stock. How did it fail in ODIN? Did it say why it failed, what file were you trying to flash? More often than not the system 7 error is caused from an out of date recovery, normally i would tell you to start there but given the fact you admitted to just randomly attempting to flash things to the device you are going to want to start from stock. The second sticky thread in this sub-forum is where you should start reading, because based on your post you either need a refresher or never have read it to begin with.
dntesinfrno said:
Since when does TWRP not read external SD cards? It see's mine just fine, for well over a year. In any case you didn't give much information to help troubleshoot. 'I tried unrooting' - if you were going to flash a stock ROM there is no need to unroot anything as the stock firmware is just that, stock. How did if fail in ODIN? Did it say why it failed, what file were you trying to flash? More often than not the system 7 error is caused from an out of date recovery, normally i would tell you to start there but given the fact you admitted to just randomly attempting to flash things to device you are going to want to start from stock. http://forum.xda-developers.com/showthread.php?t=1725839
Click to expand...
Click to collapse
For whatever reason, TWRP wouldn't read my sd card. And when I said I tried unrooting - I just meant flashing back to the stock ROM. Odin fails when it gets to system write. It goes down a bunch of lines of code successfully but when it gets to system write, it fails every time. I've downloaded a few different stock ROM versions for AT&T and tried switching USB ports around my laptop. I've also tried a few different versions of ODIN but I'm not coming up with anything but a soft bricked phone still.
kinjo1023 said:
For whatever reason, TWRP wouldn't read my sd card. And when I said I tried unrooting - I just meant flashing back to the stock ROM. Odin fails when it gets to system write. It goes down a bunch of lines of code successfully but when it gets to system write, it fails every time. I've downloaded a few different stock ROM versions for AT&T and tried switching USB ports around my laptop. I've also tried a few different versions of ODIN but I'm not coming up with anything but a soft bricked phone still.
Click to expand...
Click to collapse
Did you have usb debugging enabled before you attempted to flash via ODIN? It sounds like it doesn't have permission to write to the /system partition. You can try doing a factory reset from recovery to get past the bootloader and make sure, or use Kies to flash to stock via this thread.
dntesinfrno said:
Did you have usb debugging enabled before you attempted to flash via ODIN? It sounds like it doesn't have permission to write to the /system partition. You can try doing a factory reset from recovery to get past the bootloader and make sure, or use Kies to flash to stock via this thread.
Click to expand...
Click to collapse
I could have swore I made sure to check before I started the process but I cant' check now because the phone won't boot. Can't flash back to stock. Can't flash any roms. I can get into download mode and recovery though. It's weird. I've reverted other phones back to stock plenty of times. It just keeps failing no matter what I do with this.
dntesinfrno said:
Did you have usb debugging enabled before you attempted to flash via ODIN? It sounds like it doesn't have permission to write to the /system partition. You can try doing a factory reset from recovery to get past the bootloader and make sure, or use Kies to flash to stock via this thread.
Click to expand...
Click to collapse
Here's another question for you, I've looked all over for the newest CWM in .tar format but everything comes in .img format. I can't use the .img in ODIN to flash to the phone and can't boot my phone to use the CWM app to flash. I suppose I could try TWRP again but when I flashed the first time - TWRP wouldn't read my EXT SD card.....
kinjo1023 said:
Here's another question for you, I've looked all over for the newest CWM in .tar format but everything comes in .img format. I can't use the .img in ODIN to flash to the phone and can't boot my phone to use the CWM app to flash. I suppose I could try TWRP again but when I flashed the first time - TWRP wouldn't read my EXT SD card.....
Click to expand...
Click to collapse
if you could wipe everything get on odin with 4.1.2 update reboot use cf root to root it (if you dont have root) after reboot download ROM Manager from Play Store install CWM recovery (easiest way to root) hope this works
I flashed Slimkat 4.4.4 a couple weeks ago and don't like it so I attempted to change it to AOSP tonight and I wiped the cache, partition, formatted the system and attempted to flash the rom and got a "fail" sign. Now when I reboot from TWRP menu, it keeps going back into TWRP recovery, after I see the Samsung and Slimkat words on my phone. I tried rebooting into system, keeps going back into recovery. I was going to attempt to reflash Slimkat but now my laptop won't recognize my phone. I saw where someone pulled the battery out and it just booted into recovery. Please help me and thank you in advance.
This is why you should never manually format your /system partition. If your rom flash fails, you have no OS to boot into. I really dont know why so many people still say to do this.
You need to either use Odin to flash your firmware, or download another rom (or your previous one) and flash it from TWRP. Youll have to plug your external SD Card into your computer and copy it to there, then put the card back in and flash.
DocHoliday77 said:
This is why you should never manually format your /system partition. If your rom flash fails, you have no OS to boot into. I really dont know why so many people still say to do this.
You need to either use Odin to flash your firmware, or download another rom (or your previous one) and flash it from TWRP. Youll have to plug your external SD Card into your computer and copy it to there, then put the card back in and flash.
Click to expand...
Click to collapse
Lesson learned. I really don't know who to listen to, I should have just left it alone like a good girl. But I really did not like Slimkat. :laugh: My laptop is not recognizing my phone through usb. Would Odin recognize it if I put it in download mode?
Its worth a try I think. But otherwise do you have a way to plug your sd card into the computer? You could copy a rom to flash im recovery that way.
If not youll probably need to try installing different drivers. You can get plenty to try from the link in my sig.
I usually say to just follow the instructions in the OP of what you are trying to flash. If they tell you to format system, I would ignore that part unless they have a good explanation for why.
DocHoliday77 said:
Its worth a try I think. But otherwise do you have a way to plug your sd card into the computer? You could copy a rom to flash im recovery that way.
If not youll probably need to try installing different drivers. You can get plenty to try from the link in my sig.
I usually say to just follow the instructions in the OP of what you are trying to flash. If they tell you to format system, I would ignore that part unless they have a good explanation for why.
Click to expand...
Click to collapse
I'm guessing the only other way to plug an sd card into my computer is to stick the card in another phone? Meanwhile I will try to install drivers and get my computer to recognize my phone.
You can usually find an adapter for a few bucks online or at places like wal mart. Sorry. Was just assuming you had one. Without it, yes youll have to try different drivers or find another way to get it going via one of the two methods I mentioned.
When trying different drivers, just installing the package doesn't always do the job. You should go into device manager and manually select update drivers, then browse to the folder in Program Files and choose it there.
When you plug in now, does it at least detect it? Are you trying while in Download Mode?
DocHoliday77 said:
You can usually find an adapter for a few bucks online or at places like wal mart. Sorry. Was just assuming you had one. Without it, yes youll have to try different drivers or find another way to get it going via one of the two methods I mentioned.
When trying different drivers, just installing the package doesn't always do the job. You should go into device manager and manually select update drivers, then browse to the folder in Program Files and choose it there.
When you plug in now, does it at least detect it? Are you trying while in Download Mode?
Click to expand...
Click to collapse
I tried putting my SD card into my daughters phone which is a Samsung but different model and I thought I put the old Slimkat rom what looked to be the extsdcard folder but when I went to recovery to install the rom I saw the corrupt rom I attempted to install last night. When I went to device manager to manually update the drivers, the computer recognizes my phone but said that the drivers couldn't be installed. Maybe I'm getting confused with this TWRP recovery I'm not familiar with. It has an install feature, so I tried to flash the rom last night using that. Did I screw up?
Ok....I finally managed to get the files onto my SD card. I attempted to install the Slim rom (the one that's been on my phone the last couple weeks) and heres the message I get:
Format and Mount System, Mount Data.....
Symlinks and permissions....
set_metadata-recursive: some changes failed
E:Error executing updater binary in zip ' /extern
Error flashing zip '/external_sd/Slim-d2lte-4.4.
Updating partition details....
FAILED
What version of TWRP are you using? You could try flashing CWM or Philz recoveries and try the rom again. If you still get flashing errors you may have to find a way to get Odin to work.
Try uninstalling drivers from device manager. Then with the phone unplugged, reinstall the driver package. Plug phone back in and hopefully itll automatically install the drivers and work.
And have you tried connecting while booted to Download Mode?
DocHoliday77 said:
What version of TWRP are you using? You could try flashing CWM or Philz recoveries and try the rom again. If you still get flashing errors you may have to find a way to get Odin to work.
Try uninstalling drivers from device manager. Then with the phone unplugged, reinstall the driver package. Plug phone back in and hopefully itll automatically install the drivers and work.
And have you tried connecting while booted to Download Mode?
Click to expand...
Click to collapse
I'm using TWRP 2.6.3.0. Ok friggin awesome...I rebooted it into download mode and the computer recognizes my phone.
You might need an updated recovery to flash that rom. Latest TWRP is 2.7.1.0.
But since you can connect in Download Mode you can flash your firmware via Odin...hopefully.
If you have the I747, it depends on if you have ever updated via ota. If so, do you remember if you had updated to 4.3 or 4.4.2?
DocHoliday77 said:
You might need an updated recovery to flash that rom. Latest TWRP is 2.7.1.0.
But since you can connect in Download Mode you can flash your firmware via Odin...hopefully.
If you have the I747, it depends on if you have ever updated via ota. If so, do you remember if you had updated to 4.3 or 4.4.2?
Click to expand...
Click to collapse
I have the i747. I've never been able to do an OTA update, I heard because it was rooted. When I tried to unroot it, I still wasn't able to do an OTA update. I'm going to try to update the recovery first and then the rom. Which rom do you use? The main reason I don't like SlimKat is because of the Google search bar on the home screen and all the extra crap on the lockscreen I couldn't get rid of.
Update: I flashed the latest TWRP and it still bootlooped. So I flashed CWM instead and it booted right back into CWM recovery.
I have a T999 and I only use Touchwiz roms. Personal preference.
When you are in Download Mode, if you do not see a Warranty Bit, youll be free to flash any firmware you want with Odin. You can download it at http://sammobile.com/firmwares
DocHoliday77 said:
I have a T999 and I only use Touchwiz roms. Personal preference.
When you are in Download Mode, if you do not see a Warranty Bit, youll be free to flash any firmware you want with Odin. You can download it at http://sammobile.com/firmwares
Click to expand...
Click to collapse
Doc, Thank you so much for helping me. I flashed the slimkat rom in cwm recovery and its fine now. However I don't want Slimkat and I was eyeing Touchwiz. Someone was saying how great a rom it is so I'm going to try that shortly. No more TWRP for me. I'm comfortable with CWM. Thanks again. :victory:
I was trying to install a custom firmware and it failed for some reason. Now I'm stuck in on the logo.
I have tried about 7 or 8 different stock firmwares on Odin, 3 of them failed because they were the wrong region, and 5 were successful but still stuck in on the logo.
ROMS Tried:
BTU-T520XXUAOD2-20150603140459
T520UEUANI1_T520XARANI1_XAR
T520UEUAOD1_T520XARAOD1_XAR
T520UEUAND1_T520XARAND1_XAR
T520UEUANF4_T520XARANF4_XAR
T520UEUANK1_T520XARANK1_XAR
I read from another thread that all I have to do is clear the cache/dalvik cache. I tried to do this through adb but adb devices does not show any devices, it just comes up blank. Android Studio won't download platform tools or the Google USB drivers either so maybe that's why its not detected?
This tablet was purchased in the US.
If someone can provide me with a STOCK rom that will work or help me figure out adb to clear the cache that would be awesome.
Thank you!
You should only flash the region your device is made for. Hopefully you have custom rom like twrp, go into that and wipe delvic and cache , that may fix boot prob
Sent from my SM-T320 using Tapatalk
cloud71 said:
You should only flash the region your device is made for. Hopefully you have custom rom like twrp, go into that and wipe delvic and cache , that may fix boot prob
Sent from my SM-T320 using Tapatalk
Click to expand...
Click to collapse
I only flashed the UK ROM because I couldn't find the US ROM. It turns out that the US ROM is labelled "Cellular South" which is far from obvious. And in terms of TWRP I think that went away when I tried to flash stock. I can try to flash TWRP back with Odin tomorrow and see if it will take though.
Have you tried using Kies to do emergency restore? I had soft-bricked my 10.1 when I got it trying to root. Wasn't paying attention and accidentally tried flashing the CF-auto-root file that was for my phone (Note 4) to the tablet. Found the stock rom but all the ones I found was taking like 8-10hrs to download.
So i used Kies and under Tools, selected Firmware Upgrade and Initialization. PUt in my serial number and model number and had tablet in "Downloading mode" and was able to recover the tablet that way. When i tried doing the Emergency restore, it wouldn't recognize device as being connected so I had to try the other options for it work.