Hi guys. This is the first time I've asked for help here. I have been flashing custom roms for several years now, and go figure, the one device I would be unable to recover is my own beloved Galaxy Tab S .
WiFi 16gb SM-T700.
I have flashed this dozens of times since in the last three years, this issue is TOUGH.
Here is what happened.
Tried to gain root with Kingroot ( First time trying that one. :/ )
Then i pushed TWRP 3.1.* through Odin
Flashed AICP 7.1.2 / GAPPS
Success
Booted the tablet. Play Store worked. Everything worked. I had root. I downloaded a few of my favorite apps and then restarted into recovery to make a backup.
TWRP was asking me something it never did before, something installing the Official App,..I swiped??
Anyways, I never got the backup. Here is where I'm stuck.
When I turn the tablet on, it says "Can't do normal boot, Kernal Length" and shuts off when I let go. I cannot boot into recovery from any method. The OS will not load. I have access to download mode, but absolutely nothing will go through in Odin. I have tried 6 or 7 different versions of Odin/ both with the single AP file and all four separate (BL, AP, CSC, blah) I have tried repairing the bootloader, reinstalling a recovery, new roms, PIT files, nothing at all will PASS in odin. Samsung Kies won't see the device in DL mode. I even donated to the UNIFIED Android Toolkit, which did Sh**. The PRO version. I have spent at least two entire days worth of time and this is beyond me. PLEASE HELP ME!! I can't get it. I paid a pretty penny for this the day it came out, and it doesn't have a scratch on it and I love and care for my devices and respect the software and the dedicated work I see all of you put into this community which makes it easy for people like me. Thank You.
Odin acknowledges it, and I have download mode, and i'm out of ideas.
Does anybody have a good one I can try?
(I'm wrong, I can't help)
Related
Hi Everyone,
First of all I would like to apologize, if I am repeating any question. I tried many threads but I couldn't understand completely. Hence I am afraid I need to ask individually. Hope thats fine with the community.
So, I own a Samsung Galaxy SII since last 27 months. I bought it with Orange on a contract in France and the company unlocked it many months ago since I do not live in France anymore. I have never flashed the phone with any other ROM, or provided root access or anything else. I have always used Kies to update the software. If I remember correctly the phone currently has Jelly Bean on it (4.1.2 I think). It doesn't have any external SD card, just the internal memory.
Due to some unknown reason, since yesterday the phone is not able to boot up. Its stuck at "Samsung GALAXY S II GT-I9100" screen. I tried to used Volume up+Home+Power keys to go into recovery mode which is not possible. I also tried to go in Download mode using Volume down+Home+Power keys which is possible. Then I tried to connect with Kies to connect it but after 15-20 mins Kies gives error in recognizing the device. When I open ODIN 1.85 (I guess that is the version which should work with my phone), it does shows "Added" status for the device.
Now after reading many posts I have realized that restoring to stock rom would resolve the issue, but it still dint for many. What is appropriate way to deal with this problem. I found some stock rom on the page of mobile network comparison webpage , but I am not sure if I should use it or not. Also I am afraid if I should check the region/model etc for this. I guess I should only install ROM which lies in France-Orange category.
I do not care about any data since I back up my phone from time to time. But I do not wish to play around with the phone much, unless required. However I would appreciate if there is any way to restore the contacts and message stuff.
Thank you very much for your help and support. I highly appreciate the effort.
Hey Guys,
I tried to root my Samsung S4 GT-I9502 (OS Android 4.3), for that I found this website:
http://marrkdaviid.com/2013/08/fix-caller-id-install-google-play-on-the-galaxy-s4-i9502/
But it failed (more information below) and I had the following error message and no wifi.
I am able to put the device into download mode, though I keep getting this error message when I try flashing the device in Odin.
(here someone with a similar problem: http://androidforums.com/international-galaxy-s4-all-things-root/768632-sos-cannot-open-gt-i9502-after-failed-boot.html)
"Complete(Write) operation failed."
When attempting to flash the device, it quickly goes through boot.img, recovery.img and system.img (when it should take longer for each step, and you should see the little green progress bar move), before failing. Does this mean that Odin is having issues writing to the device?
I live in China and I just bought the phone, I needed 5 days to download the necessary files, because most download pages are blocked in China. So I am loosing my last nerve right now.
I am pretty confident that I have the correct Samsung drivers installed. I don’t have Samsung Kies installed. I have even tried using a different computer (Laptops), and two different ROMs.
I have tried flashing the below ROMs:
I9502ZNUCMG2_I9502CHUCMG2_I9502ZNUCMG2_HOME.tar.md5
I9502ZNUEMK3_I9502CHUEMK3_I9502ZNUEMK3_SVA.tar.md5
Someone with a the same problem tried the 'Firmware upgrade and initialization' option in Samsung Kies, but it didn’t work, so I didn’t try. (Here the link: http://forum.xda-developers.com/showthread.php?t=2382979)
Instead I tried a recovery. I used Odin 3.07 and the following file:
i9502-cwm-recovery.tar.md5
I got my phone back to work for a while, I reset the phone, just in case. But know I can’t switch the Wifi on and the phone wants to Reboot.
So I allowed the phone to Reboot, I clicked on “reboot system now” and then on “Yes – (I forgot what was written behind the Yes, but I didn’t just click on the normal Yes, I clicked on the Yes - …)
The problem here: The Phone changed to a China Unicom Screen and stayed like that. After 5 h I took the battery out, but I couldn’t restart the phone.
So I did an cwm recovery and know I am afraid to reboot. The Wifi is not working and I can’t find any information about how to fix it.
So please help me. Do I reboot? Can I already install SVA ROM, although I couldn’t flash the Stock Firmware? Do I send the phone back and give up?
Please let me know if you need any other information to be able to help me.
PS: This is the first time that I flash a smart phone. And although I already spent several days now, searching the internet for how-to-dos, tips & tricks, guidelines, Q&As and god knows what, I still do not fully understand what exactly I am doing here. Hence, I would be very happy to receive somewhat easy understandable answers.
Thank you so much for your help!
Anna
Hi,
I have one hard bricked Galaxy Note Pro 12.1 2014 Version tablet I bricked while loading custom ROM. I mistakenly popped out the external sd card that the rom was installing from. I was having some trouble with battery issues and was thinking a fresh install of the custom rom would fix it.
When the external card popped out while the rom was loading from the screen said it failed. On reboot the screen goes thru Galaxy logo then goes black. I tried installing recovery images and whatnot thru odin. Some would pass some would fail. And on reboot it just goes thru logo then goes black. I could see its on but nothing else. It does accept a charge though.
Its probably completely broken and at a complete loss but I thought maybe there was some chance. I think it might be possible to repartition or something to that affect but thought I'd see what is possible.
FYI: Not under warranty. Knox is tripped. I am willing to provide a $50 reward to whomever can walk me thru a possible fix. Yeah I know, if you help and it works again I could just say it still doesn't work but all I can offer is my word that you will be rewarded if it gets fixed.
Thank you for any positive feedback.
Tom
Solved
Kies was able to fix this problem. I tried odin a recovery tar , everything numerous times, even kies several times, nothing would do it. Also tried odin a stock rom and that helped a tiny bit. After installing stock rom several times (at first it didnt want to and would fail) it finally did go thru on like the 3rd try installed and passed. But then it would only go to samsung logo and lock up. This morning it tried kies again and miraculously it didnt lock up like it did before and install all the way thru. On reboot it went past logo and turned on completely as new. Moral of the story, have faith and dont give up. I almost trashed this thing and was ready to press the buy it now button for a new one but I decided to insanely try again as if some miracle might happen. And sure as sh#t a miracle happened.
Hi everybody.. I've been viewing and reading the XDA forums for years, looking for help and tips with various phones.. I just registered today so I could share my recent experience with rooting the Note II (sch-i605 from Verizon) that I bought used.
I was doing my due diligence, researching different methods of rooting, several different websites, which I've concluded are a waste of time because they all link back to the best! Trying to decide if it was worth it with the locked bootloader.. After reading up on several different threads, I figured what the heck.. So I bit the bullet and dove in.. No easy task this, because I don't have internet access at home, other than on my wife's phone with unlimited data.. Downloading the files necessary, saferoot, safestrap, twrp, various versions of drivers, some programs.. All very time consuming over 4g! Lol..
Anyway, having rooted a Motorola Droid Razr, a Samsung Epic 4g, OG Droid, an LG G2, along others in the past, I'm not an expert, but not exactly a n00b at rooting either.. I Odin on my PC from when I did the Epic, and adb was there from multiple devices, so that saved a little time.. So over to the PC I go with my Note 2, wife's G2 and my trusty USB cable..
Saferoot worked beautifully! First time success! Installed jrummy root check to verify.. :good:
I let that be it for while since the bootloader is perma-locked.. But after a couple hours of reading more threads about ROMs, I started feeling the itch again.. So off to download twrp so I can play with some shiny new ROMs.. The twrp website has installation instructions for twrp manager from the play store, upgrading from inside an earlier version, fresh install with Odin, and using "su dd if=/sdcard/twrp.img of=/dev/block/mmcblk0p9".. Since I was on the other side of the room, I decided to try the dd method.. Not having experience with this particular command, I figured some practice was in order.. Read up on what it does, played around with it using some worthless files.. Then I used it in reverse.. Finally I ran the did command for real.. That's when it all went downhill.. When I rebooted I ended up with the Dreaded Yellow Triangle of Doom! Unauthorized software and take the phone to Verizon.. Ask I had was download mode.. :crying:
Fought with the phone and the computer for a while until my wife made me give it up for the night. Studied up some more on the , and jumped right into things first thing this morning.. Downloaded a couple .IMG stock room files, one rooted one not, and a stock recovery .IMG to use with Odin.. Got them into the PC, Windows 7 Pro, hooked up the new brick and fired up Odin.. No joy.. Odin wouldn't see my phone! Time for a smoke break, just had to step back and think about things for a minute or two. After a Google search and some digging, i found a YouTube video describing exactly my problem(Odin or Kies won't recognise download mode). I tried it, and guess what, IT FREAKING WORKED! I don't understand it, but taking the battery out made Odin see my phone!
Now onward we go..Back to trusty old XDA! That's when I found the Android toolkit bySkipSoft.. Talk about a phone saver! Got my phone hooked up, in download mode, tried a few different things in the Unified Android Toolkit, couldn't download anything since the PC has no internet but I already had stock recovery and stock rom images, and the toolkit told me where to stick em! First I tried to use a few adb commands to try to get the data off the phone I wanted to save, but I finally gave up because adb couldn't see the phone since it couldn't see that USB debugging was active, even though I promised it was..
Before I tried flashing the stock rom I thought I'd flash the recovery since that was the beginning of the problem. About 4 mouse clicks, 30 seconds, and a reboot, my phone was alive again! :victory:
Still on the stock mj9 release, rooted with saferoot, and chugging along splendidly.. I may just let it sit this way for a while.. Lol!
TLDR: got a used Note 2, rooted it, b0rked it, and fixed it with the help of the awesome devs and members of XDA!
Unfortunately, I didn't keep track of all the threads, devs, and members I looked at and read that helped me solve my conundrum.. However, the main reason I finally registered was so that I could say a great big THANK YOU to the community here.. It's the best! And you came through for me in my hour of need..
Theude
P.s. as I have time over the next few days I'm going to try to find the posts I used for information, and add my thanks there too.. Also will try to post links, but they'll probably be in text not actual links lol..
Hi. I have spent the past 10 hours trying to root my phone and install an XtraLite type of ROM because I am so sick of have 75% of my RAM used up when I haven't even started using the phone. I softbricked my phone, and after hours of trying to solve every minor issue that came up I finally found a solution and managed to flash a stock ROM. I have a lot of questions that I would love to get answers to because I am a little bit confused right now.
My history.
Bootloader
I spent so much time googling this and I decided to trust one site that said, if you can't find the "OEM Unlocked" option in "Developer Options" then your bootloader is probably already unlocked. This was the closest I got to an answer, along with many people with SM-G925F saying the root was successful for them without doing something to their bootloader. Can someone please clarify what I need to do with the bootloader with my EU SM-G925F?
Flashmode/Download Mode
Prior to this I spent very long trying the "adb-windows reboot bootloader/flashboot-windows oem unlock" without any results. However I somehow came to the conclusion that "Download" mode for my Samsung was no different. Any clarification on this subject please?
Rooting
The first rooting guide I trusted was the CF-Auto-Root page. This is where the bootloader question was raised but as I came to the conclusion that the bootloader already was unlocked, I decided to give it a shot. I downloaded SM-G925F file, added it to AP on Odin, and flashed my phone. Now my phone was locked in a bootloop. According to CF-Root page "A modified recovery and cache partition will be flashed, which will install (only) SuperSU, then clean-up the cache partition and re-flash the stock recovery. For the root to work, the device must reboot into recovery. Most devices will do this automatically after flashing these files, but in case that does not happen, please boot into recovery manually.". As you probably guessed, my phone never booted into recovery mode, and I was never able to manually do it either since the phone was in a unstoppable bootloop. Did I do something wrong here or misunderstand anything?
ROM Instructions
My first choice was: http://forum.xda-developers.com/gal...xtrestolite-deodexed-mod-edition-1-3-t3119968
I failed the first step, never even managed to root with CF-Root. And regarding TWRP, I did download the correct version "twrp-3.0.0-0-zerolteeu" I assume. However, many descriptions say my phone needs to be rooted before I can install TWRP so I never tried to install it. Even if, I couldn't find a detailed enough description of how to install TWRP. All it says is "flash it". Problem is, I am not sure if I am supposed to be in "Download mode" and use Odin loading TWRP into "AP" or how does this work?
Never got to the ROM installing, but it would be nice to have something more detailed than "Put it on your phone, install it". Like, do I enter recovery mode and navigate to the rar file and chose to install it? Not sure how this works.
My solution to bootloop
This part took me the longest. For those stuck in a bootloop. Holding DownVolume + Power button for at least 15 sec will simulate disconnection of the battery. This helps you turn you device off. Also, if you nothing happens, make sure you unplug the USB cable as it keeps trying charge and show the status it tries to boot and keeps looping as a result. I could always manage to get into "download mode" through DownVolume + Home Button + Power Button no matter what, and I am grateful for that. I managed to find the exact build I was using on my phone "G925FXXU3COJ1_G925FOJV3COJ1_G925FXXU3COI9_HOME". But everytime I tried to flash, it always failed in the end. I spent hours on google. Someone mentioned something about it failing on a certain point of the writing, involving hidden.img. I googled for info on how to resolve this, and someone suggested to rename hidden.img to hidden.tar but it did not help. I also read some threads regarding using a matching PIT file and there were about 7 different ones to chose from. I tried them all without success. Finally I read something about removing hidden.img from the ROM. I renamed the ROM from .tar.md5 to .tar. Unpacked it, and then repacked it without hidden.img using tar-Tool from these forums. The following flash of the new created tar.md5 (without hidden.img in it) was successful.
Slave for stubborness
Unfortunately since I spent so long getting through this horrible experience, I would feel bad have wasted an entire day just to get a phone that is now reset. I could have done that in 30 seconds. However I am persistent to get this working and I am truly grateful for any help you people can supply my with. I did manage to root and ROM my old S3 but that was a while ago and I only remember a few small things about Odin and so forth. However things seem much more complicated now than before.
Thank you in advance,
Alex