I was working fine using one of the ICS Roms until I decided that I needed the use of my keyboard dock and camera so why not go back to stock. As a complete noob, I should have left well enough alone.
I am not sure what I have done, but I am stuck in an endless boot.
I have a GTab 8.9 wifi only - U.S.
I have Clockwork and Odin, but not sure of the exact file to put in Odin (yes I read the instructions) I have also not been able to pin down which file to use in Recovery mode and how to get it onto my device while in this loop.
Last but not least, I have NO idea what a kernel is and if I should be concerned about that.
My question(s)
WHat process (Odin or CMR) should I use to get my tablet working?
With either of those processes, what file should I flash, put in the PDA field, etc?
Can I get a 1-2-3 list of how to get my beautiful brick back to working condition?
Related
So I have my new Rogers Captivate for 2 weeks and I decide I would like to flash a Custom ROM onto it. I duly search the forums, reading the stickies and things like that.
I find the guide on how to flash Custom ROMS with videos, decide following these will be my best guide. So I download the ODIN one click as told, get the phone into download mode and flash it back to stock as the video showed me. Though this completed successfully, I ended up with an AT&T boot loop after it was done with my button combo to access download mode broken. So after I do some more searching on the forum, I find out this is not an uncommon problem. The solution is to make or buy a USB Jig. So I order a USB Jig off eBay. Guy I bought it from was great, shipped it out to me and it arrived today. I get it, pop it in and bam. Phone goes into download mode.
Next I follow the instructions a few other Canadian Captivate Owners have posted and flash it back to Rogers 2.1 Stock with Odin 1.3 and no pit file. I still get the AT&T logo on boot but it gets past it now. Goes to the I896 boot screen, then the Animated Samsung Bootscreen, then to the Rogers Boot screen with the dots moving on the bottom. I am patient and wait a bit. It finishes with that and then goes to a completely black screen. At first I thought the phone as off, but I touched the buttons on the bottom and they light up. They stay lit up as well.
Thinking something has gone wrong, I reflash it again. Same thing happens. I try flashing the same ROM with a pit file from the Odin download. Same thing happens again. Nothing but a black screen and the buttons lit up.
I am at a loss as to what to do next, as I have searched the forums and not found a good answer for this problem. Should I try flashing a new stock ROM onto it? What is my next move here?
Phone:
Rogers Captivate 10.10
ROM currently installed:
I896UXJI2-homebinary.tar
*EDIT*
Nevermind, I managed to fix it. I had the AIO Captivate Tools 2.6 (Rogers) installed and after the phone booted it dutifully reported that it was in debugging mode. So I selected load custom ROM and selected Firefly 2.3. It goes through its thing and clockwork recovery installs. I select to install the ROM.zip AIO Tools copied over and after it does its thing. Presto, a few minutes later the phone boots into Firefly 2.3 with no problems. I am running the ROM I wanted and I am a lot happier now.
Hello I recently got my refurbished Captivate from AT&T and it came running 2.1 Android. First thing I did with it was go and root it by downloading the update.zip to it, and that went all fine and well.
Next thing I did was get ROM Manager and installed Clockwork Recovery Mod, then went ahead and made a backup of my ROM. So from here I was getting ready to get myself ready for Cyanogen Mod 7, and grabbed the Clockwork Mod version with speedmod and installed that through the Clockwork Recovery.
After I did this the boot screen changed on my phone and would lock up at the Galaxy S SGH-1897 Samsung screen, which had replaced the 3g one by AT&T. The phone will just hang at this bootscreen for infinite amount of time, any suggestions on how to help?
I'd like to point out that I currently have no USB cable for this phone, I did not receive a micro USB with it as it is a refurbished product and do not happen to have any laying around. I do however have a micro SD card, in which Clockwork doesn't seem to support this.
I come to you asking for help to resolve said issue, I can no longer use my phone as a result. I've tried restoring my backup but the same replaced boot logo appears and refuses to actually start up the phone.
The 3 zips that I can access on the internal SD are
-the root.zip
-clockworkmod
-clockworkmod with SpeedMod
Any ideas?
First of all, you will definitely need a micro USB cable. You need to flash back to stock at the moment. Don't worry though, if it's still showing the boot screen your phone "should" be fine.
Second of all, for CM7 you need to follow the EXACT instructions to install CM7 (you can risk bricking your phone with CM7, unlike any other usual ROMs). Do you know, and understand all of the steps involved?
Sorry, but what were you doing? You need odin to install cm7 & without a cord you were never going to succeed.
As mentioned above you need a cord, and need to reread the instructions
CM7
Ok, I am new to these forms and kind of a noob android user so please make it as simple as possible.
So, I rooted my phone but i never have messed with roms or kernels or anything (mostly because i dont understand them) so everything is stock (gingerbread 2.6 i believe). I was following an online guide to change the boot animation via root explorer and now my phone only shows the word "android" with the shine going through it. The weird thing is, I can turn on the phone and get to the homescreen, but I am not able to see anything except the boot screen. For example, when i turn it on, I am able to turn it off by pressing power then blindly searching for the turn off button on-screen.
I have searched long and hard for a solution, but they were all caused by uploading a CWM roms that went bad, but I didnt do that. I did have it at one point just to backup my rom because everyone said that it was important. So I do have a CWM backup, but no CWM app on my phone. I am able to get to recovery mode.
Please help thanks.
Droid 4 running Stock Jb 4.1.2, Safestrap 3.11, Liquid smooth 2.9, CM (last stable)
Everything working fine for a number of months, installed Liquid smooth via -> delete romslot 3, create romslot 3, install Liquid 2.8.
It ran for a number of days no problems. Restarted fine, all features worked great, even the annoying random restart from 2.4 went away.
6 - 10 days in, im surfin' the news sites at work, put it down, screen goes black, i pick it up. Hit the power button cause i realize its off and it just boot loops... so bad i had to vol-/+ pwr, go to flash mode and THEN turn it off b/c it just kept trying to restart, hang on logo.
I got home and decided to AP flash the latest:
9.8.2O-72_VZW-18-2
Blur_Version.98.72.182.XT894.Verizon.en.US for the maserati.
Boot looped a few times, i was able to get it to go into recovery mode, after that it loaded up the stock JB system. First boot it crashed and restarted, second boot it loaded but only the keyboard worked, not the touch screen. Went to the in OS option of factory reset mode + delete storage.
Rebooted, worked. Checked it a few boots, everything is fine. I use Druid 4 Utility Xt894 JB version and apply the root. Works great. Install safestrap, Create new partition, install liquid smooth 2.9. Works for an afternoon... at work today the touch screen stops responding, i restart it a few times. I try to enter recovery mode. Now im in boot loop again...
I've tried re flashing it again, a few times. I tried even going down to the previous release of JB for the phone. STILL 4.1.2!!!! But nothing.... it just boot loops... what did i do wrong? It was running great. No tweaks or anything done to it prior to it having its melt down.
Help please.. ive provided as much information as possible and though i only joined XDA now to post for help, i have read it for a long time as my main source for my phone and have donated to both CM and Liquidsmooth teams previously..
help!!!
I can't see where you are doing anything wrong. You have obviously done your research and have a good idea of what you are doing. I see, after you fastbooted, you went back to Liquid. I think I would try running CM10.1 or even stock for a few days and see if you have the issue there as well. If you do than it sounds to me like it might be a hardware issue. If not, maybe try re-downloading Liquid. Perhaps your zip got corrupted somehow.
I would love too. In fact i would be willing to run it on the stock crappy 4.1.2 if i could get it out of boot loop this time...
It just keeps boot looping on the logo. AP Fashboot flash and BP flash work but recovery and normal boot/reboot mode just goes into M logo boot loop.
I've re downloaded the 4.1.2 jb SBFs from 2 different sources to ensure its not a corrupt file, tried 18_1 and 18_2 software versions...
Is there a way to use the abd shell to get into the filesystem and check whats going on? Is the SBF the last call? or is there another route to see whats going on or just flash EVERYTHING? Like completely back to stock?
I can find my way around a PC file system but im not familiar with linux. Please help me understand, Is it like having CMOS and BIOS settings or equivalent to damaged CMOS firmware? What am i not replacing/reverting by SBF and HOW can i replace/revert BEYOND the basic sbf...
If ya point me in a direction or to someone who can help me out i can do all the foot work just point me in the right direction?
Is this applicable? I found a site talking about using CWM in a ADB shell file push to possibly get access to more features?
The article also goes into reading the busybox / ADB command screen? (sorry for not proper jargin) and see what its doing during the boot loop before it restarts?
Id add the link but i need more posts....
Update: Flashed 18_2 again with a "factory cable" i made, let it boot loop a series of times before it started up into the stock system again.
At first, again the touch screen wouldn't work, random lockups and restarts, etc. Since i just got it into the main system again and i had to leave for the weekend for a trip(no wifi or network), i couldn't mess with it all weekend but i left it on the whole time and kept checking its functionality... gradually its come back to full function. Touch screen works and is accurate, no more lockups, no more restarting, even stopped boot looping when i restart and enter recovery..
Im not sure and i couldn't find any forum converstations or write ups to support to idea but i think after a major crash and you flash new or reflash your SBF, it seems the phone needs time to recalibrate and index? Not sure, but just an FYI. Gonna try loading SS and liquid again.
I'm a complete newbie to android phone modding, and I was really proud of myself when I was able to install the Cyanogen 12.1 and Google Apps onto my Samsung S3 Mini. However, I made the mistake of trying to put my work email on it, which requires that my phone be encrypted. Well, I guess the encryption and rooted phone didn't want to play nice together, so I got the error message that my phone would be factory reset. Boo! Well, it got worse. Instead of a factory reset, my rooted phone now is stuck in what I have now learned is called a bootloop. Basically I turn my phone on, and the Cyanogen start screen (with the text "TEAMWIN") just infinitely flashes on the screen until I pull the battery.
I have tried using Odin 3.07 and cm12.1_golden.nova.20160210.ODIN_TWRP.tar.md5. I do the three button system boot, connect the usb, run Odin, get the phone recognized, and then install the .md5 in the PDA section of Odin. It tells me that it succeeded, but when I restart my phone it's still the same bootloop. I also tried swearing, but that didn't help either.
Has anyone else out there had experience with Cyanogen and this particular error? I would love to get this phone working again... preferably with either a Lollipop version of android or back to Cyanogen 12.1.
Any info would be greatly appreciated! Thanks everyone.
So I've got an update if anyone's interested... I can't call it progress, but it's a different problem now.
I was able to download and use Odin to do what was shown on this link: http://forum.xda-developers.com/showthread.php?t=2122548&highlight=root
Everything worked in Odin, the phone rebooted, and went to the Team Win Recovery Project diagnostics screen, rebooted again, and then to the samsung logo. However, it immediately goes to the "Encryption Failed" error screen, and the only option is to 'reset device'. Of course, doing this just reboots the phone and it then has the Team Win loading screen, Team Win Recovery Project diags screen, Samsung logo, and back to the 'Encryption Failed' screen again. So now I have a new infinite loop to solve. *sigh*
any thoughts?
Have you been able to get into TWRP? If you are, maybe you could wipe everything from there and flash the recovery version of your ROM.
I was able to put the stock bootloader onto the phone using Odin, download the original tar from here: http://live.samsung-updates.com/index.php?device=GT-I8190, then used the stock bootloader to install it from the sd card. Everything went fine, but now when I boot the phone it just hangs on the Samsung Galaxy S3 mini GT-i18190 start screen indefinitely. Is this progress, or have I created a new problem now?
You're playing around with heavy stuff. I won't recommend using an upgrade flash (CM over Odin) as an full flash. Please try flashing a stock image.
If you did something wrong to the partitioning, then it's likely to not allow you to do a successfull factory reset. Maybe you can try re-flashing a stock Odin image with PIT repartitioning.
Remember to try to backup the EFS folder, doing that kind of flash might wipe it.