After months of Samsung not fixing the known issue, I got mine working again today. Here is what I did, hope any with same problem have similar results. I am not an expert or anything, just finally found a way to get my tablet working again.
I downloaded the Kies program from Samsung website to my pc. I went ahead and used the "Lite" version. Once it recognized my tablet, I had it check for updates. I went ahead and installed the update and the progress screen stalled again and then the tablet rebooted again and still had the same problem not powering off.
So here is what I did different this time after the failed update attempt and it worked!!!!!
I went ahead and force closed the Kies program which was still trying to run with ctrl alt del. I then unplugged the tablet from the computer usb and then plugged it back in.
I restarted Kies Lite and it told me the last attempt failed and if I wanted to use recovery method, so I clicked yes.
It then gave some steps to do to get the process started but they were WRONG! Instead , I disconnected the usb cord, then pressed both the power button and the volume up key for about 15 seconds until the tablet rebooted itself into recovery mode. This booted into a recovery screen which gave a warning about loading custom ROM or something but I went ahead and proceeded anyhow by following the on screen instruction.
I then reconnected the usb cord and then the button to get started was highlighted and able to be clicked, so I clicked start.
And to my surprise it actually finally started updating instead of just sitting there hung up.
I let it continue installing and when the tablet rebooted, I disconnected the usb cord and the tablet was on its way to finish updating and installing the 4.2.2 working update with a power button that finally worked again.
This was my experience I wanted to share with others that are as frustrated as I was, just dont blame me if it doesnt work haha.
Update: I was able to successfully fix my inlaws tablet as well this evening with absolutely no issue. He has read about it and also tried various methods posted everywhere but mine was the only way that worked.
Only download you need is the Samsung Kies program, no need looking for outdated links, unzipping, Odin recovery options, etc. This is to get it back to stock Samsung ROM which currently is the 4.2.2.
Please post up your results if you try it and have a minute, Im curious how many others this works for after spending so much time reading, searching and testing diferent methods.
Related
Ok so I'm not a noob around here. I'm pretty good with the android stuff, but this one has got me stumped. I have a perfectly working sidekick 4g with B2b 2.5 on here. All of a sudden it forces itself into a repeated reboot. It shows me the white sidekick/samsung screen, and about 3 seconds later reboot into the same thing. And it does this over, and over, and over again. At some point it stops and functions normally, but only for a few minutes, then repeats the process. I've already changed roms, back to glorious overdose. It will even reboot in CWM. The only time it stays stable is when it's in download mode. Another problem there. ODIN doesn't recognize when the sidekick is plugged in through USB. So even if I wanted to ODIN, I can't. I tried booting without my sd card, and my sim card. No avail. and i disabled lagfix, still reboots. I take the battery out, and when I put it back in, it turns itself on just so it can continue restarting. There's nothing stopping this phone. Please help if you can. Thanks for taking the time to read this!
first, enable voodoo. i tried disabling voodoo once and it just kept rebooting. i pulled the battery, put it back in, enabled voodoo, and it booted normally. however, in your case, i would run fix permissions before trying to reboot. to run fix permissions, while in recovery mode go to advanced. select fix permissions, wait for it to say done, hit the back button, and reboot. see if that helps. if not, you may want to ask someone more experienced.
Thanks for your reply. I found out that my windows(8) didn't correctly install my sidekick drivers. tried it on my xp machine and bam, ODIN worked like a charm. Unfortunantly, the problem persisted. So i know it's not a software problem. I contacted samsung yesterday and sent in my phone today. I ODINed back to stock then updated to kj1 through kies. I read up on it a little more and people said it was maybe a loose connection on the phone. I'm still in warranty, so I'll let samsung deal with that.
Hi guys, my phone is right borked and I hope someone can help me out. I've been searching forums all day and I find bits and pieces of advice that apply to parts of my situation, but haven’t found a fix yet.
I installed CyanogenMod on my Rogers Samsung G3 a couple months back. Everything has been going smoothly until last night when I installed an update.
The phone rebooted and got stuck on the Samsung splash screen with the blue cyanogen dude. I left it for 30 min and when I got back, it was still the same.
I took the battery out, turned it back on and ended up in the same spot. I took the battery out again, turned it on and left it over night. Same thing this morning.
On advice from this forum I put the phone in recovery mode. I thought I had TWRP, but Clockwork Recovery comes up.
I did a factory reset, and cleared the cache. Rebooted and still the same thing.
I tried to flash the ROM, but it doesn't work. The android dude just lies there, dead. Poor guy.
I plugged it into my computer but even though the computer makes the connection ‘cah-ching’ its not recognized. Through the recovery screen I tried unmounting and mounting everything, and mounting as usb and the computer still won’t pick it up. I uninstalled Kies, and the drivers for the phone and re installed everything. The driver pop up says MTP has failed.
Any suggestions?
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!!
Hello everyone, I have lots of issues with this tablet since I bought it. It works painfully slow, yet resetting it doesn't change anything, still the same problem. I also tried to root it via Kingroot and it werk, however it took me lot of time due to the system being unresponsive / unstable and almost useless. It comes with android 4.0.3 and I also tried looking up for any possibilites to reinstall the firmware since I'm extremely sure it could be caused from the firmware it also got installed from the factory. I also tried searching for custom roms and other ways around for TWRP or any custom recovery, but no result. I also tried up with the Flashify app to try extracting / backing up / dumping the recovery and the kernel but the app freezes up. I also tried a possibility to update the firmware from their official page, hence it failed to do so since it gives an error in their flashing software that dosen't tell me nor it logs it what it could be caused up from the connecting part.
primux.es/producto/tablets/tablet-primux-siroco-2-101/189
(not sure if anyone understands spanish thought but I can translate if needed)
This is the page from where I tried to download and install their software and their firmware down below on the page. primuxcomputers.es/primux/siroco2upgrade.pdf
There are the instructions where I tried to follow but at the "Imagen 9: Icono" part got me stuck in there. It requests me to insert the cable in the tablet holding the "Home" button and while holding it, plugging in the USB cable throught PC, and tap quickly the "Power" button 3 times. However it gives me a red X icon and yet nothing shows up in the devices: No ID, no other kind of detection no logs no nothing. After it showed up the X on the status, it disconnects itself and it changes to ready / green icon and plugs itself in again but nothing really happens to detect it again thought.
I also tried to boot in recovery mode but nothing happens menawhile Flashify keeps on the rebooting in recovery mode in loop doing nothing else... I'm seriously in pain with this tablet. And if you ask me to return it, not gonna even bother doing that..
I seriously hope any answer very soon and don't get dissapointed by the ignorance of this topic..
Hi everyone.
Last night my phone ran out of power and when I charged it back up it wouldn't boot at all, so this morning I decided to try and fix it but I think I have just screwed it up even more to the point that its completely bricked.
I could still access TWRP and tried to reinstall the firmware and flash TWRP through the checkbox execpt about 1 minute in the screen went off due to the time out, but the screen wouldn't come back on at all so I left it for an hour just in case if it was still running in the background, after this time I hard restarted the phone and entered TWRP again and but it didn't install the firmware properly and my computer wasn't reading the phone properly so as a test I tried to swap bootloader from A to B stupidly and now I can't seem to access anything, only thing I can do is the menu where it says start, power off, recovery mode and restart bootloader. Pressing any of these settings seems to just put me back in to this menu again.
When plugging in the phone in to the PC it make's no noise at all as well.
Have I completely hard bricked my phone? Or is there a way to fix it?
Thanks Ben
All fixed I flashed the RAW firmware