So yeah, i rooted my samsung galaxy fit earlier today with no issues, then proceeded to flash a rom. After receiving many errors (e-big partition size, usb not accessible etc) i now cannot turn my phone on as i get stuck at a screen with a picture of a phone and a computer with a warning sign inbetween them.
I've been doing this between two computers, reinstalled drivers numerous times, removed the sim and sd from the phone and tried again, rebooted computers etc.
I can only access download mode, and the other mentioned screen. I can't even access recovery mode.
Every time i have tried to flash using odin i have made sure samsung kies has been shut and it's processes have been ended via the task manager.
At this point i no longer care whether or not my phone is rooted, i just care about being able to use my phone.
I cannot get Samsung Kies to recognise the phone either, on both computers. I get stuck on 'connecting'. I've reinstalled drivers several times with the same result.
Just to clarify, odin does detect the phone, with the 'healthy' yellow box.
Any kind of help is appreciated, perhaps there's a way to force a restore to the stock rom?
I'm pretty desperate.
Issue now solved. I just wasn't aware that there was a version of odin specifically for use with Samsung Galaxy Fit, Pop and Mini.
Related
Where to start...
First, as a disclaimer, I may use language or terms that sound noobish. I have rooted and run custom ROMs on several devices in the past, however generally when I get a ROM I like I stick with it, so I'm not constantly tinkering. I've done my best to search and find solutions so please go easy on me.
17 days ago I was running stock 4.3 on my SGNII when the battery died. Upon charging I found I was stuck in bootloop and had a bad /efs mount. I searched and searched and spent around 15 hours trying this and that but to no avail. I finally threw my hands in the air and got ahold of Josh at mobiletechvideos and he was able to fix the efs mount issue. However, he left me in factory mode which required me to root to get out of, and once I did this I was unable to activate data on my carrier (Ting). I was so happy to have my phone "back" though that I used it like this for 4 or 5 days. I could get on wifi and I could call and send text messages. I had been off the grid so this felt like something I'd fix fully later.
Well I kept reading and found "fix" after "fix", flashed this and that and still no dice. FINALLY, last night, I found this thread: http://forum.xda-developers.com/showthread.php?t=2086769 which helped immensely. I was able to get TWRP flashed by unchecking the "auto-reboot" option in Odin and pulling the battery after the update took, and via TWRP I was able to install the ROM. I booted up, the device activated, I was running 4.1.2, I made and received some calls, the birds were chirping, the air was sweet...
I had struggled for so long and I had finally achieved success! Then, for seemingly no reason at all, I accepted an OTA update which bricked my Note2. Devastation.
The current state of things...
* Cannot get past the initial "Samsung Galaxy Note 2" screen
* Cannot boot into recovery
* I CAN get into dl mode,
* but, I CANNOT successfully flash anything. TWRP will flash like it took, but upon reboot I'm not able to boot into it. I'm also able to flash a ROM but it fails when it gets to sbin, and upon rebooting I'm greeted by the screen "Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again."
When I try to use Kies it doesn't find the device. I've installed all of the most recent drivers and I'm running Kies as administrator. I select Tools > Emergency Firmware Recovery, THEN connect my device as instructed.
I'm at the apex of frustration. I beg thee to help!!
Hey im new here so please excuse me if this is in the wrong category
hi, i currently have a Samsung s2 skyrocket which was rooted and recently acting up so i tried factory resetting it, after factory resetting it the phone kept freezing at the boot up so i looked up possible solution for this problem which only made it worse. after trying to load my stock firmware back onto my phone using Odin i got an error afterwards from accidentally disconnecting it which read "Firmware upgrade encountered an issue. Please select recovery mode in kies & try again" I've tried connecting to Kies only for my computer to not recognize my phone even after running the connection error solution in the Kies application. i cant even get into recovery mode for my phone only shows a blank screen and starts to vibrate.
Hello,
Welcome to XDA.
Samsung Kies should have correctly installed your drivers and you should still be able to flash the stock firmware via Odin even in this state. I've had to do this more than a few times on S2, try doing a google search for "USB drivers for samsung phones" and install them manually if you haven't tried that already, sometimes you have to uninstall the drivers then reinstall them, try other USB ports also. Are you certain that you have the correct firmware, just to be sure before you start?
Once you have the drivers properly installed and your PC recognizes the device, charge the battery to full if you can even if you have to do it with an external charger(you don't want it dying in the middle of flashing), open Odin, try to boot to download mode, when the "connect to kies" screen or if download mode comes up then connect to Odin(don't use Kies), if recognized you'll get a blue or yellow comm# box and it will say <ADDED!> in the dialogue box, select the AP tab in Odin, browse to the stock firmware file and select it, when back in Odin screen select Start, give it a few to flash, when done you'll get a green PASS and the device will reboot, give it time to load into system, sign in to google account and you should be good to go. sometimes you have to flash a couple of times to get it. I hope this helps. Good luck.
get into recovery, install the newest twrp, either through custom recovery already on your phone via zip or through odin using a tar.
reboot into recovery again (should be the newest twrp at this point)
if you still have anything on your internalSD, back it up through mount>mount as usb, plug phone into pc, browse, backup, or use file manager
wipe everything except externalSD
install rom then suggested gapps pack for that rom
reboot to system
wait like 15 mins for phone to do its thing during first boot
good luck
Hi, I'm in a bit of a rage right now. Need my phone for work, and also afraid of loosing all the pictures and videos I've taken
So my phone has worked perfectly for months, updated several times, but today after the last update it's stuck on the boot logo, the Samsung one.
I've tried hard reset with Power+Down, it just reboots to the same logo and stays there forever. I also can't get into recovery mode with Power+Up+Home, it just gives me a yellow triangle with an exclamation mark in it for 1 second then boots back to the samsung logo. Tried Kies 3, it doesn't recognice the phone at all, tried everything in there.
The only thing I can access is the Download mode Down+Power+Home, I have no idea what to do there, I've read about Odin but that looks like some NASA-stuff way above my knowledge, isn't there just a way to get it back to previous version? Orginal, stock and all that? Don't wanna mess with roots if that can be done
I'm out of ideas, please help me, are all my data gone? Pictures, video etc? :'(
Help please
*Sorry for bad English, not my native, but I hope it got trough.
Sounds like an update gone wrong. Restoring the phone isn't so hard but saving your pictures and data is harder in most cases. You can try using Smart Switch and see if your device shows up on failed updates, maybie it can repair the installation. You can also use Smart Switch to restore the phone completely, but this DELETES everything on it. If you haven't rooted phone and have warranty, I'd return it to Samsung with strict instructions that phone broke when software update and that you want to keep your data/pictures. If the phone is rooted there are ways to extract data from the phone memory but I'd only do that as a last option.
schoolsux said:
Sounds like an update gone wrong. Restoring the phone isn't so hard but saving your pictures and data is harder in most cases. You can try using Smart Switch and see if your device shows up on failed updates, maybie it can repair the installation. You can also use Smart Switch to restore the phone completely, but this DELETES everything on it. If you haven't rooted phone and have warranty, I'd return it to Samsung with strict instructions that phone broke when software update and that you want to keep your data/pictures. If the phone is rooted there are ways to extract data from the phone memory but I'd only do that as a last option.
Click to expand...
Click to collapse
Yeah, I did the upgrade with modelname and S/N trough Smart Switch, it worked, but all data was lost including all my contact phone numbers, hade over 350 :| don't think they are synced either? :|
Anyway, glad the phone works, will never install these stupid updates again, never noticed a single improvment after them anyways
I've come across a problem that's frustrating me to no end. I've been rooting phones for a few years now, usually older models. A friend asked me to root his newly aquired S6 (canadian model, eh), shouldn't be an isssue. I do the standard issue Enable Developer, wipe data/cache, install root and rom, and call it a day. I go to reboot it, and it's in a boot loop for the Samsung screen. I've had boot loops occur before, I'll take care of it.
I've been at this all day (10+ hours), and still don't have a way to escape this boot loop. Problem is that I didn't know about the Reactivation Lock that was still active when I attempted to root. Here' what I've attempted:
- Uninstall/Reinstall USB drivers several times and different versions. Phone will still not show up under ADB Devices and not detected by windows or toolkits (but will still register via Odin).
- Restore from backup: will only boot into stock recovery mode, no option for restore.
- Reinstall Firmware via USB OTG - "USB access is disabled"
- Install other roms, always fail or are denied access
- Update/Change kernel , see above
I could list on and on all the little tricks and toips i've tried from the internet, but what it essentially comes down to is I can't install anything onto the device due to the device not being recognized or being blocked by a permission, and yet I can't get into the actual Android OS to disable/Enable any permissions. Factory reset does not fix this loop, nor does clearing caches. I've tried sideloading, pushing, and various other means to get into Android, but nothing is working. Help?
Hi all! I have been trying to fix this tablet for weeks. It's an SM-T580 Galaxy Tab A 10.1 tablet. It's actually my girlfriend's tablet and she tried to root it first and she royally screwed it up and I am having a lot of trouble cleaning it up.
So, when I got to it, she already had it stuck on the downloader mode and if you tried to boot it, it went to the blue screen that says "An error has occurred while updating the device software. Use the Emergency recovery function in the smart switch PC software."
So here is everything I did as well as I can remember it:
1. Tried every version of smart switch and KIES software. It does not recognize it ever.
2. Tried to flash custom recovery, but FRP lock is still enabled. She must not have correctly changed the settings in the tablet before beginning the root.
3. Tried to flash stock firmware, but it says it needs to be repartitioned. I downloaded what I thought was the pit file, and repartitioned the chip, but it still won't successfully boot. I tried several different cables and ports.
4. Tried to flash probably 10 different firmwares to see if anything would stick. Used several different versions of Odin all the way from 1.3 up to 13.5. Nothing will successfully boot.
5. Found stock recovery (I believe) and got stock recovery on there but when i get to recovery it says it can't mount anything. It gets a huge list of errors like "can't mount E..." I am able to ADB sideload, but so far nothing I try to sideload works because it says it has the wrong footer and the wrong signature.
Am I boned? She left it plugged in for like a week at least, so my assumption is the emmc chip burned out. Any and all help massively appreciated!