I'm not a noob, but not exactly a ROM flashing god either. I bought a used SIII and after trying a few ROMs decided to go back to stock for a bit and possibly sell it. I flashed the LEM firmware and it got stuck at the samsung "pulsing" logo, so I flashed the LK3 and got the same thing. So now I am kinda stuck in no man's land. It will boot and give me the swirling Samsung logo and then the AT&T dripping planet logo and then stops at the pulsing Samsung logo. For $h1ts and giggles, I tried flashing TWRP through Odin and of course that didn't help. Tried going through the toolkit and because I can't put the phone into developer mode, that doesn't work either. I'm assuming that even though I made some stupid mistakes here it should still be salvageable given that it is booting and being recognized by my PC. Am I SOL or can I make this thing work? Open to any suggestions and thoughts.
Thanks!
Boot into the stick recovery after Odin and do a factory reset, reboot then profit
Making the iPhone jealous one user at a time.
can you access Recovery Mode? if so, wipe data, cache and reboot.
I'm good now. I guess I just panicked a little. Need to be able to sell this one so I can buy a new toy soon. Not sure exactly what made it work (I flashed the recovery boot image from the toolkit) among all the things I tried, but I was eventually able to boot into recovery and wiped and reinstalled Quantum. Thanks for the fast replies.
Related
So I am the proud owner of a shiny, new Galaxy Nexus (GSM). Unlocked the bootloader and installed CWM recovery and was doing great. Today I decided to install the volume fix. Installed the zip through recovery, completed and rebooted. The phone got stuck in a bootloop over and over and over and over and would not boot Android at all. Did a ton of research here and everywhere and, in a panic, I booted into CWM recovery, reset the cache & did a full factory reset. NOW, the phone will not go past the Google bootscreen with the unlock symbol, no matter what I do. AND, I can't even flash the original google image because I can't get in to set USB debugging so my computer won't even recognize the phone (FYI, I'm on a Mac). I am at a complete loss and don't know what to do. If I could only get the computer to recognize the phone I could flash the original google image through Terminal, but alas, I can't. Any ideas? If I can somehow get this phone back up and running I would be eternally grateful. For now, I think I may be SOL. Thanks....
This happened to me, I was not able to solve the issue, even though I could push and pull data to and from the device via ADB. I could still not get past the google logo. I decided to lock the boot loader again and return to the store for a new device.
http://groups.google.com/group/android-building/msg/2cd2b16ed56a7e84
Sent from my Galaxy Nexus using XDA App
hartford said:
So I am the proud owner of a shiny, new Galaxy Nexus (GSM). Unlocked the bootloader and installed CWM recovery and was doing great. Today I decided to install the volume fix. Installed the zip through recovery, completed and rebooted. The phone got stuck in a bootloop over and over and over and over and would not boot Android at all. Did a ton of research here and everywhere and, in a panic, I booted into CWM recovery, reset the cache & did a full factory reset. NOW, the phone will not go past the Google bootscreen with the unlock symbol, no matter what I do. AND, I can't even flash the original google image because I can't get in to set USB debugging so my computer won't even recognize the phone (FYI, I'm on a Mac). I am at a complete loss and don't know what to do. If I could only get the computer to recognize the phone I could flash the original google image through Terminal, but alas, I can't. Any ideas? If I can somehow get this phone back up and running I would be eternally grateful. For now, I think I may be SOL. Thanks....
Click to expand...
Click to collapse
One more post like this in Dev section and you'll be banned for 3 weeks
Hi, first let me give you the background of my phone.
I bought it off eBay used and it came in an almost perfect condition, preinstalled with Gingerbread 2.3.6. The only problems known with the phone is that it won't get recognized by Samsung Kies, but it does by my PC. Onto the problem...
My friend introduced me to the Cyanogen Mod 9, telling me it could increase battery life, performance, etc. I was interested and wanted to install this mod. I first rooted my phone with a Zip off a tutorial and that worked flawlessly and I had Super User. I then installed Rom Manager and proceeded to installing the mod. He gave me two zips to put into my SD card to install for the Cmod and Google Play. Long story short, after wiping cache, data user, and every other wipe before installing these two zips, I was stuck in a boot loop with the Samsung Logo and Cyanogen Mod 9 Animation. I didn't think much of it and turned off my phone for the night, leaving it for the morning.
This morning, I tried going to Download Mode and flashing a stock os with Odin3 and it went from boot loop to soft bricked. It gave me a message to connect the phone to Samsung Kies in order for it to before restored, but the problem is that the phone isn't recognized by the program. I tried .tar files and it led to nothing on Odin3 because it wouldn't get past "Get Pit for Mapping...". I tried numerous times and on one occasion, I accidentally had Re-Partition ticked but the flash didn't go through so I unplugged my device. After that, the phone turned off and no response after that.
It won't turn on, no device recognized through USB or Odin3. I tried the wall charger to see if it was the battery's fault but it led to nothing. What are my options in reviving my Samsung Galaxy S2 ?
Yikes. Sounds hard bricked. I think your only option is to pay to get try a jtag recovery. Search the board on that.
Sorry man.
Sent from my SGH-T989 using xda app-developers app
I agree. Not a lot of options especially since warranty will be difficult without proof of purchase.
For future reference (for you and anyone else in this situation) the boot loop you experienced is due to cwm v5.0.2.7 not wiping caches correctly. After flashing an ics rom, if you are running this recovery, you have to flash the darkside cache wipe to get the rom to boot.
yoft1 said:
I agree. Not a lot of options especially since warranty will be difficult without proof of purchase.
For future reference (for you and anyone else in this situation) the boot loop you experienced is due to cwm v5.0.2.7 not wiping caches correctly. After flashing an ics rom, if you are running this recovery, you have to flash the darkside cache wipe to get the rom to boot.
Click to expand...
Click to collapse
Thanks for the replies! I was wondering how reputable is MobileTechVideos on doing JTAG repairs on bricked phones. Also, do you have a tutorial on how I can try to install Cyanogen Mod 9 again with the Dark Side cache wipe so i wont get the same problem again? Thank you.
Ok, so I flashed a MIUI port for the AT&T Note 2, and it was disgusting...it crashed everything, and needless to say I ended up stuck at the boot logo for a long time. FINALLY managed to get it to flash via Odin...so I flashed Stock Rom...and now it's stuck on Samsung logo...Ok..so I go flash CWM...do a wipe and everything, and install CM10.1 via that...stuck at CM logo. I've left each ROM plugged in, stuck on boot screen for over 20-30 minutes each. I'm at a loss of what to do. Could I need to flash a kernel? or am I missing something obvious? The good news, I guess, is with a few steps, I can get into DL mode and use Odin, and I can flash CWM and get into that..but I can't inject anything into my phone so CWM can use it, I only have what's there now, which is CM10.1. I'm so mad...I've never had too many issues with ROMs but this one jacked things up badly...guess that's what I get for using a port even though it noted that everything was working now. Anyway...does anyone have any advice?
Edit: I flashed CWM, and tried to clear cache/dalvik then factory reset...the first two worked...as soon as I hit factory reset, that's where the screen goes black and it resets...it's like it just refuses to do it. I'm seriously at a loss here. Is it toast?
Edit again: sorry but I'm trying more to give more info. I went into CWM and went to advanced and started formatting one by one...it's when you hit format /data that it immediately dies and restarts. So..something weird is going on there. Can I use a PIT file for this phone, if it exists, to reformat and just get it going? I'm desperate...
Us this http://forum.xda-developers.com/showthread.php?t=2052779 on a PC.
Follow directions and Odin back to stock.
Sent from my SAMSUNG-SGH-I317 using xda premium
I have been using the i747z ROMs for quite some time and after trying a bunch of other ROMs I always reverted back to theirs. So when their 3.0 version came out with Android 4.3 I installed it, using ClockWorkMod recovery. Right after it installed, CWM displayed a message about the boot loader and to fix it. So I went ahead and did that (Don't really remember what the message was) What I know is that I lost root. Also the phone could not connect to the mobile network, only on Wifi. So this morning, I factory reset the phone again, and attempted to root the phone with Odin with CF-Auto-Root-d2att-d2uc-samsungsghi747 (which I had used when I first rooted the phone). Now the phone doesn't boot past the 2nd samsung logo, it starts out with the Samsung logo with the blue circle around it, then the AT&T Rethink Possible and then the plain white Samsung logo. Also, the LED has a slow blue flicker.
I can get the phone into download mode and I have used Odin to attempt to load the stock firmware and the stock bootloader. But after restarting the phone I can't get past the same screen described above.
I am pretty sure this is not related to the i747z v3.0 ROM but rather something a miss with the order in which things need to start in Android. I have done some reading on that but I am not sure what I need to do to correct this soft brick situation. ( I have googled "soft brick" as well)
Any thoughts would be greatly appreciated!
mozphoto said:
I have been using the i747z ROMs for quite some time and after trying a bunch of other ROMs I always reverted back to theirs. So when their 3.0 version came out with Android 4.3 I installed it, using ClockWorkMod recovery. Right after it installed, CWM displayed a message about the boot loader and to fix it. So I went ahead and did that (Don't really remember what the message was) What I know is that I lost root. Also the phone could not connect to the mobile network, only on Wifi. So this morning, I factory reset the phone again, and attempted to root the phone with Odin with CF-Auto-Root-d2att-d2uc-samsungsghi747 (which I had used when I first rooted the phone). Now the phone doesn't boot past the 2nd samsung logo, it starts out with the Samsung logo with the blue circle around it, then the AT&T Rethink Possible and then the plain white Samsung logo. Also, the LED has a slow blue flicker.
I can get the phone into download mode and I have used Odin to attempt to load the stock firmware and the stock bootloader. But after restarting the phone I can't get past the same screen described above.
I am pretty sure this is not related to the i747z v3.0 ROM but rather something a miss with the order in which things need to start in Android. I have done some reading on that but I am not sure what I need to do to correct this soft brick situation. ( I have googled "soft brick" as well)
Any thoughts would be greatly appreciated!
Click to expand...
Click to collapse
After flashing through odin did you format data?If not try it.
Go into recovery and wipe data.
**SOLVED**
Thanks xXFl4sh, I had tried that.
Solved!
Alright where do I start? How about RTFM Some how I had missed the part about flashing a bootloader and a modem after the ROM. Not recalling having to do that before, I skipped right over it. Once the recovery CWM 6.0.3.1 was finally loaded, getting the flashing the ROM, the bootloader and the modem was easy as usual.
The key was having to use Odin to install a recovery in .tar or .tar.md5 format since I could not access a Recovery Mode on the GS3, as well as a rooted stock image (I used root66_ATT_I747UCDLK3.tar.md5 which is a rooted Android 4.1.1 for AT&T) For the recovery, I couldnt' find a .tar or .tar.md5 for ClockWorkMod (did find a utility to convert it, but didn't want to introduce another variable into the mix) so I used one from Team Win Recovery (v2.6.3.0) and with that I loaded the CWM recovery. Once all of that was in place, I proceed to factory reset, clear data, cache, system and then flash the new ROM, bootloader and modem.
In all of this I learned quite a bit about the whole process and how to narrow down possible resolutions. I still see the "Rom may flash stock recovery on boot" message after flashing either a ROM, bootloader or modem, but just backing out without answering Yes or No seems to work. Also (and this may be related, I don't see the option to restart in recovery from shutdown menu). Don't really know what that's all about for now, and honestly don't want to mess around (at least for a while)
I know the steps are general, but I hope this can help some else if they get their devices in a soft brick situation. As for the i747z v3 ROM with 4.3, I really like it, everything works (Wifi,Blutooth,tethering) and the battery seems good as well.
Thanks!
Hello all,
I've got a Tab 3 7.0 T210R stuck on the Samsung logo with pulsing blue background. I've read through several Samsung boot loop help threads as well as the general Loop noob helper but haven't found a fix yet.
For my stuck T210R, What I've done & can do:
Was rooted with a "patched" stock UK ROM from last March [sorry, don't recall which]
Was running fine until after I tried to install from Play the TWRP Manager, I obviously did something bad! like select wrong device maybe
I can get into Philz, TWRP, & use Odin
I don't have a recovery back up [i really don't care about restoring back to anything - just want it to work, clean slate, ya know]
Tried a couple of latest ROM's through Philz and a stock ROM XAC-T210RUEAMK1-20131122134958.zip though ODIN. They seemed to be successful but I still can't get past Samsung logo
I've tried these ROMS that seem to load but ixna on successful boot afterwards:
ODIN: KIES_HOME_T210RUEAMK1_T210RXACAMK1_1304745_REV00_user_low_ship.tar.md5
Philz: Stock.rooted.deodexed.T210R.zip
Philz: TAB3-T210-HASSAN-ROM-V1.0-kitkat-4.4.2-Aroma-Mods-all Languages.zip
Philz: cm-10.1-20131209(1)-UNOFFICIAL-lt02wifiue.mine.zip
What's killing me is that loading new or stock ROM's SEEM to work - no errors or anything obviously indicative that I'll still be boot looping as soon as I restart. I'm quite desperate and thinking I'm truly bricked.
I haven't yet tried using ADB but if I can use ODIN and TWRP or Philz, will ADB do anything better than what I've already done? I haven't tried anything with the kernel as I can't really understand what to do there. I read and read and read the kernel threads but with my experience its really not as straight forward as rooting or flashing a ROM or software, and I could conceivably screw up worse! I'm mildly experienced at following guides to have rooted and ROM loaded a 1st gen Kindle Fire, Samsung SII skyrocket, S4, Tab 2 7.0, Tab 3 7.0.
No replies or interest? Please help
I'm I in the wrong forum? Did I offend someone? Could really use some input, please.
Any one seen this before? If you've any experience LOSING this battle, please speak up and I'll know to just resign to now owning a pretty white Samsung brick.
Boot to customed recovery under wipe choose format this will zero all partitions then redo
thanks!
andynroid said:
Boot to customed recovery under wipe choose format this will zero all partitions then redo
Click to expand...
Click to collapse
if i could find the "thanks" button I'd use it.
I'm traveling now but definitely try your solution. By "redo" I presume you mean load a ROM. When I wipe I also presume I'll still have custom recovery? I should still be able to ODIN, too, if needed?
thanks again
Yes exactly recovery will not go away once you have formatted the partitions you can now flash a new customed ROM or reflash original FW using Odin..Cheers
Hey buddy wanted to know if you ever found a solution for your issue? I am in the same bind you were in. Can you help guide me. I tried installing the same files you did and to no avail. I bought a Tab 3 T210R from eBay that was stuck in boot loop, I am assuming that it isn't rooted as when I would I went into download mode, it said the firmware was official.