Related
So this is kind of a unique issue i'm having. I have the I-747 on AT&T and flashed AOKP rom (it was taking too long to get JB). It worked for about 3 days and then got stuck in the android boot screen (used the rom feature to get rid of the pink unicorns). after that, I booted into recovery and reset my phone, and it worked again for a few more days, then it wouldnt boot again (I dont believe I changed any settings between the boots). After this time, it wouldnt let me boot into recovery and would only boot to the android start screen and stop. I used odin to flash the stock rom, which only took me to the 2nd samsung boot screen and stopped (after the AT&T splash shows up). I looked online and saw someone say try CF-root using odin, tried that and it didnt help. Then tried using a custom kernel siyah s3, and now it will only show the initial samsung splash screen before turning off again. Any suggestions here? I figured I'd stop researching since i dont want to really mess up my phone worse than it already is
mrneilix said:
So this is kind of a unique issue i'm having. I have the I-747 on AT&T and flashed AOKP rom (it was taking too long to get JB). It worked for about 3 days and then got stuck in the android boot screen (used the rom feature to get rid of the pink unicorns). after that, I booted into recovery and reset my phone, and it worked again for a few more days, then it wouldnt boot again (I dont believe I changed any settings between the boots). After this time, it wouldnt let me boot into recovery and would only boot to the android start screen and stop. I used odin to flash the stock rom, which only took me to the 2nd samsung boot screen and stopped (after the AT&T splash shows up). I looked online and saw someone say try CF-root using odin, tried that and it didnt help. Then tried using a custom kernel siyah s3, and now it will only show the initial samsung splash screen before turning off again. Any suggestions here? I figured I'd stop researching since i dont want to really mess up my phone worse than it already is
Click to expand...
Click to collapse
I have a similar issue, someone please help
Your main issue now is that you flashed siyah. We don't have one. If you can get to download mode, you will want to flash back to stock.
Sent from my SGH-I747 using xda premium
As DeathSdoor said...flash stock.
Sent from my SAMSUNG-SGH-I747
d3athsd00r said:
Your main issue now is that you flashed siyah. We don't have one. If you can get to download mode, you will want to flash back to stock.
Sent from my SGH-I747 using xda premium
Click to expand...
Click to collapse
Thanks guys! So I used odin to flash the stock boot loader and stock rom, but it is still hanging up on the 2nd samsung screen like it initially did (the one after the AT&T boot animation). Any other ideas on what could be the cause?
How long is the hang? Sure is just not the 1st initial boot of the new rom?
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
blaker13 said:
How long is the hang? Sure is just not the 1st initial boot of the new rom?
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
Click to expand...
Click to collapse
The first boot can take as long as 5 minutes sometimes. So, if you haven't waited that long, then try out some patience. Otherwise, try booting into recovery (stock now) and factory reset.
Sent from my SGH-I747 using xda premium
bump!
I have this same issue. I have restored to stock rom and it does the Samsung boot, then AT&T, then it goes to Samsung pulsating with a blue pulsating LED.
I have left it in that mode for at least 15 minutes and it never boots.
I can still get into download mode.
Thanks in advance for any help!
Has anyone tried booting into recovery after flashing the stock ROM and wiping caches then rebooting?
jethro650 said:
Has anyone tried booting into recovery after flashing the stock ROM and wiping caches then rebooting?
Click to expand...
Click to collapse
I let it run for 2 hours (left the house came back and i was still on. And phone wont boot into recovery at all ( i tried many times, but it just boots normally and skips recovery until it gets to the 2nd samsung screen, then stops there).
I dont know if this is relevant, but while the phone is off and plugged in, i can still see the battery meter and the Green LED (so i'm guessing it's still working, it just wont boot)
mrneilix said:
And phone wont boot into recovery at all ( i tried many times, but it just boots normally and skips recovery until it gets to the 2nd samsung screen, then stops there).
Click to expand...
Click to collapse
Same here!!!
jethro650 said:
Has anyone tried booting into recovery after flashing the stock ROM and wiping caches then rebooting?
Click to expand...
Click to collapse
As Jethro said clean everything and factory format in recovery. Your just not doing the buttons right to get in to recovery
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
blaker13 said:
As Jethro said clean everything and factory format in recovery. Your just not doing the buttons right to get in to recovery
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
Click to expand...
Click to collapse
I went into recovery many times before, I'm definitely hitting the buttons right but it still wont go into recovery, it just tries booting like normal. I can go into download mode easily, but that's it.
jbizz, did you start getting this error after flashing AOKP rom also? trying to figure out what could have caused the issue in the first place
I'm not really skilled on these things, but I once had a similar issue with my phone not booting and had to end up using Kies to emergency restore it. Odin wouldn't recognize my phone but kies would.
Although I think my issue with odin may be stemming from my computers usb ports...
Sent from my SGH-I747 using XDA Premium HD app
I actually flashed a bad kernel and the phone wouldn't boot after that.
What is the proper way to boot into Stock Recovery?
Sent from my SAMSUNG-SGH-I777 using xda premium
Fixed it! What I did was go into Kies software and did a firmware upgrade instead of trying to flash from odin, then put it in download mode instead of recovery, but it still worked. Thanks for all the help, guys! guess it's time to move to a CM based rom?
mrneilix said:
Fixed it! What I did was go into Kies software and did a firmware upgrade instead of trying to flash from odin, then put it in download mode instead of recovery, but it still worked. Thanks for all the help, guys! guess it's time to move to a CM based rom?
Click to expand...
Click to collapse
Thats bad badassness! I will try that when I get home!
Sent from my SAMSUNG-SGH-I777 using xda premium
mrneilix:
Please give me step by step what you did! Kies is being a bastard!
Sent from my SAMSUNG-SGH-I777 using xda premium
jbizz said:
mrneilix:
Please give me step by step what you did! Kies is being a bastard!
Sent from my SAMSUNG-SGH-I777 using xda premium
Click to expand...
Click to collapse
Sure, I'm doing this largely from memory since I mostly figured it out by throwing stuff at the wall to see what sticks.
Open Kies->tools->firmware upgrade and initialization->enter model name then serial number (they're behind the battery) -> put the phone in download mode and plug it in. it should take care of the rest.
Fair warning, this will fully wipe your phone, i lost all my pics (thank you google+'s instant upload or i'd be PISSED) and titanium backup (there goes my 3 stars on every level in angry birds and great scores in temple run), but at least you get a phone that can function as more than a paper weight, right?
mrneilix:
You're my new best friend and I don't even know you!!!
Thanks for the help, you're a legend!
Sent from my SAMSUNG-SGH-I747 using xda premium
(ADDED $20 BOUNTY IF YOU HELP ME, WILL PAYPAL YOU WITHIN 24 HOURS)
Hey guys,
I've been flashing ROMS for years and this is my first real issue.
I tried to upgrade from an earlier version of CM10 to the newest one. After I flashed GAPPS this caused the phone to get stuck on reboot so I went back to CWM recovery.
ALL MY DOWNLOADED FILES WERE GONE IN CWM. Including all the roms I had, and my NANDROID backup (which I would have just reflashed right there).
I tried to Odin back to stock and it passes but gets stuck on the Samsung boot logo every time.
I've tried to scour threads on XDA and on Google. The closest thing I found was a thread where it mentioned I'd need Tmobile Bootchain commands but I can't find those either.
All help is greatly appreciated.
Have you tried to Odin using a different computer.. or redownload Odin and the files needed
Sent from my SGH-T999 using xda premium
Odin the stock firmware you mean from a different comp? I don't think that is the issue since Odin shows that the flash was successful. The phone reboots itself and it gets passed the Samsung Galaxy S3 screen to the Tmobile Android 4g boot animation.
Additionally, people in the Verizon S3 forum are describing my issue exactly here (http://forum.xda-developers.com/showthread.php?t=1840030)
SeanFloyd said:
(ADDED $20 BOUNTY IF YOU HELP ME, WILL PAYPAL YOU WITHIN 24 HOURS)
Hey guys,
I've been flashing ROMS for years and this is my first real issue.
I tried to upgrade from an earlier version of CM10 to the newest one. After I flashed GAPPS this caused the phone to get stuck on reboot so I went back to CWM recovery.
ALL MY DOWNLOADED FILES WERE GONE IN CWM. Including all the roms I had, and my NANDROID backup (which I would have just reflashed right there).
I tried to Odin back to stock and it passes but gets stuck on the Samsung boot logo every time.
I've tried to scour threads on XDA and on Google. The closest thing I found was a thread where it mentioned I'd need Tmobile Bootchain commands but I can't find those either.
All help is greatly appreciated.
Click to expand...
Click to collapse
After a successful odin flash boot into stock recovery manually and select wipe data, factory reset, then wipe cache partition. Reboot, bingo.
Sent from my SGH-T999V using xda premium
neysito said:
After a successful odin flash boot into stock recovery manually and select wipe data, factory reset, then wipe cache partition. Reboot, bingo.
Sent from my SGH-T999V using xda premium
Click to expand...
Click to collapse
I can't get into stock recovery man, or any kind of recovery.Holding vol up + home + power hangs permanently after the SGS 3 boot screen, nothing happens.
Go to Doc's stickie and I think it is in the 2nd post, there is an Odin flashable version of TWRP (maybe a copy of CWR but since I don't use it I'm not sure).
Flash that and let it "try" and reboot. It won't but you can do the key combo to get into TWRP recovery and either flash a ROM, Restore or at the very least Factory Reset, which would be my first choice.
Somewhere back there in your efforts, I think you may have erased your internal and if that is where your backups were kept then that might be why they are gone. Just a thought though.
In odin, uncheck auto reboot. Flash the recovery tar in pda spot. When it says pass, pull the battery and boot into recovery with volume up, home, and power. Release the power button when u feel the vibrate. Then thank mrmako777 for teaching me this tonight
Click to expand...
Click to collapse
You are the mf'in man. This is what fixed my phone. Give me your email so I can paypal you $20.
To anyone who can't get into recovery if you mess up your phone with the wrong GAPPS, this method is the only thing that worked for me.
SeanFloyd said:
To anyone who can't get into recovery if you mess up your phone with the wrong GAPPS, this method is the only thing that worked for me.
Click to expand...
Click to collapse
Glad you had it all worked out.
This is exactly what was suggested to you before, since you said in your OP you had already odin back to stock. What I don't get is how come you were not able to boot into original recovery when it was just going on a boot loop. It doesn't matter. At least you fixed it. Enjoy
Sent from my SGH-T999V using xda premium
neysito said:
Glad you had it all worked out.
This is exactly what was suggested to you before, since you said in your OP you had already odin back to stock. What I don't get is how come you were not able to boot into original recovery when it was just going on a boot loop. It doesn't matter. At least you fixed it. Enjoy
Sent from my SGH-T999V using xda premium
Click to expand...
Click to collapse
My bad man, I quoted the wrong reply. Here is what fixed it.
GalaxyS3Guy said:
In odin, uncheck auto reboot. Flash the recovery tar in pda spot. When it says pass, pull the battery and boot into recovery with volume up, home, and power. Release the power button when u feel the vibrate. Then thank mrmako777 for teaching me this tonight
Sent from my SGH-T999 using Tapatalk 2
Click to expand...
Click to collapse
I've been on XDA for sometime but this has me frustrated. My note 3 keeps rebooting over and over. It will show the Note III screen then the Samsung screen and then the white with pink T-Mobile screen. After several seconds...it starts to reboot this same manner over and over. Every once and a while it will boot up to lock screen. When I swipe the screen it says that the system is not responding. It asked me do I want to wait or cancel. Eventually it just reboots and starts the process over and over. I have tried odin maybe 50 times. Tried kies. It will load the odin tar stock rom and say successful but the rebooting just starts again. I've tried a stock kernel and I tried the green compusion kernel. Please, if you have the knowledge to help, I would be very grateful. I've flashed roms and odined bricked devices for years...but this one has me stuck....Thanks ahead of time. It will go into download mode fine. It will go into recovery fine as well.
I have read the other threads and post similar to this one but they haven't help up to this point and do not seem ti be active anymore.
BACARDILIMON said:
What where you loading when phone went bad
NOTE 3
Click to expand...
Click to collapse
I was on Darthstalker and was flashing Jedi Elite. I may have in the process also tried to restore a backup with efs. But...the problem was already occurring.
teknowiz23 said:
so i take it since you have flashed odin back to stock, you are getting stock recovery menu and not twrp or cwm right?
Click to expand...
Click to collapse
I'm on stock recovery right now nut I have and can odin twrp easily. Yes I have backups but they don't load correctly either.
brojoe11 said:
I'm on stock recovery right now nut I have and can odin twrp easily. Yes I have backups but they don't load correctly either.
Click to expand...
Click to collapse
k, when you odin back to stock are you using AP and CSC or just AP?
**and, are you using the stock tmo firmware off of sammy website or one for the root?
brojoe11 said:
I'm on stock recovery right now nut I have and can odin twrp easily. Yes I have backups but they don't load correctly either.
Click to expand...
Click to collapse
Have you tried the complete restore function in Kies? Where you have to enter your Model & Serial number?
Using the stock downloaded from sammobile. And I have tried kies restor with the model and sn. It load perfectly on the phone just like odin but when the phone starts to boot up....it bootloops.
I just load the md5 file in PDA and hit start.
brojoe11 said:
Using the stock downloaded from sammobile. And I have tried kies restor with the model and sn. It load perfectly on the phone just like odin but when the phone starts to boot up....it bootloops.
I just load the md5 file in PDA and hit start.
Click to expand...
Click to collapse
okay, have you tried using the AP and CSC in the de la vega root method instead? i would try that if you haven't.
** for your comvenience
http://forum.xda-developers.com/showthread.php?t=2484223
if you can't get CSC and AP availability in odin,
close odin
open odin.ini
change csc and ap to =1 under {ButtonOption]
reopen odin and flash AP and CSC
teknowiz23 said:
okay, have you tried using the AP and CSC in the de la vega root method instead? i would try that if you haven't.
** for your comvenience
http://forum.xda-developers.com/showthread.php?t=2484223
Click to expand...
Click to collapse
I'll sure give it a shot. Thanks.
brojoe11 said:
I'll sure give it a shot. Thanks.
Click to expand...
Click to collapse
good luck man, that's the situation we all slightly fear in the very depths of our mind when we are flashing.. that sucks. half the fun though lol..
teknowiz23 said:
good luck man, that's the situation we all slightly fear in the very depths of our mind when we are flashing.. that sucks. half the fun though lol..
Click to expand...
Click to collapse
Fun once you get your heart settled back in your chest, realizing you may have just made a fancy paperweight.
Did you also try the steps here in post # 2?
http://forum.xda-developers.com/showthread.php?t=2467001
chstewart said:
Fun once you get your heart settled back in your chest, realizing you may have just made a fancy paperweight
Click to expand...
Click to collapse
wouldn't know, hasn't happened to me yet. if there's one thing i've noticed with this stuff, is that it is very rare to permanently (although slightly possible via software/software-hardware conflicts) to brick a device unless you do something really stupid. i'm fairly confident that joe will get this working.
Thanks for all the confidence and the humor as well. Yeah, I've come close to bricking several devices. But usually with some great insight and help....they are "usually" restorable . Thanks guys. I'm downloading root de la vega files now...soon we shall see....
Thanks for the twrp thread link. I've flashed twrp several times...no problem..the problem is when the rom starts to load it just loops and loops and...
well...tried it...it loaded. came to tmobile screen then began looping again...unbelieveable....
brojoe11 said:
well...tried it...it loaded. came to tmobile screen then began looping again...unbelieveable....
Click to expand...
Click to collapse
Reboot into stock recovery and wipe data and cache. That's power, home and volume up button to get into recovery.
Sent from my SM-N900T using XDA Premium 4 mobile app
gforceriders said:
Reboot into stock recovery and wipe data and cache. That's power, home and volume up button to get into recovery.
Sent from my SM-N900T using XDA Premium 4 mobile app
Click to expand...
Click to collapse
try twrp and restore previously working system or boot partition. i'd only try one at a time.
OOOOOORRRRRR
try reflashing stock kernel then wiping cache, dalvik, fix permissions.
if that don't work try a custom kernel then wipe cache, dalvik, and fix permissions.
i think you are one step closer.
Message came up and said "process system isn't responding" and then looped again....any more ideas?
brojoe11 said:
Message came up and said "process system isn't responding" and then looped again....any more ideas?
Click to expand...
Click to collapse
k. restore a previously working system partition. preferably one from a stock rooted but whatever rom system should be worth a try.
brojoe11 said:
Message came up and said "process system isn't responding" and then looped again....any more ideas?
Click to expand...
Click to collapse
I am telling you this happen to me. Just run Odin back to stock and reboot into recovery after and wipe data and cache. Even if your phone doesn't seem to go into download mode still run odin.
Sent from my SM-N900T using XDA Premium 4 mobile app
gforceriders said:
I am telling you this happen to me. Just run Odin back to stock and reboot into recovery after and wipe data and cache. Even if your phone doesn't seem to go into download mode still run odin.
Sent from my SM-N900T using XDA Premium 4 mobile app
Click to expand...
Click to collapse
You let it totally boot. then go into recovery and wipe data and cache right?
I restored system and then boot from a stock rooted backup. Still didn't work...So, I'll try the odin with stock and wipe data and cache...thanks guys. Maybe one of these will work.
brojoe11 said:
You let it totally boot. then go into recovery and wipe data and cache right?
I restored system and then boot from a stock rooted backup. Still didn't work...So, I'll try the odin with stock and wipe data and cache...thanks guys. Maybe one of these will work.
Click to expand...
Click to collapse
No when you odin you should still have the boot loop. Then you can do a battery pull and reboot into stock recovery and wipe data and cache.
Sent from my SM-N900T using XDA Premium 4 mobile app
Hello! Let me start by saying that i have researched a ton and there is a lot of great information on here. The info I've read however doesn't seem to work for me.
My situation is I spilled a little bit of water on my phone (really not much), but it got inside my phone a little, which was already rooted using auto root. My power button thinks its constantly being pushed (i think). It doesn't bootloop, but as soon as i pop the battery in it turns on, and my phone was unresponsive to me clicking the power button. The rest of the phone was fully functional and i checked with Tmobile and it is still under warrenty (didn't mention the water). They told me to backup the phone which i was able to do in kies with no problem. Then they said do a factory reset, which again I did with no problem. It didn't solve my issue which i kinda knew it wouldn't, so the next step for me was to unroot my phone so i can return it. I popped it in odin, selected the original firmware and it started , then it disconnected by itself. Now the firmware upgrade screen pops up, but i am still able to get it into download mode (for me since the power button is suspect) i just have to hold the home and volume down, pop in the battery and it goes to download mode. The problem is that every time i try to hit start in Odin it gets to the part about the PIT partition and disconnects and says there is no PIT partition. Everywhere i've read says to either use a PIT partition (can't find one for the M919) or that the partition is in the m5 file, which as far as i can tell it is not (at least not it's own file). I've tried downloading the stock firmware from a multitude of different places even Sammobile with no luck and I've also tried different computers, different cables, and all the USB ports available to me.
Can anyone please tell me where to go from here please? I need to get this replaced asap!
(sorry i also posted this in the general section on accident)
I really think I just need the PIT partition, but I can't seem to find one for the m919 model
I have also tried different version of Odin (1.85, 3.07, and 3.09) all with the same result
What stock firmware are you trying to flash?
4.4.2?
Sent from my SGH-M919 using XDA Premium 4 mobile app
i think so. the name of the file is M919UVUAMDL_M919TMBAMDL_M919UVUAMDL_HOME.tar.md5
Ace$$ said:
i think so. the name of the file is M919UVUAMDL_M919TMBAMDL_M919UVUAMDL_HOME.tar.md5
Click to expand...
Click to collapse
When you're in download mode do you see anything that mentions KNOX in the upper-left hand corner? I only ask because MDL (4.2.2) firmware is the pre-KNOX firmware and will have no mention of KNOX in the text in download mode; it also will not flash if your bootloader has been updated to MK2 (4.3) or NB4 (4.4.2).
You're trying to flash mdl to a phone that won't take it. (ie it's already been updated to mk2 or nb4).
I'd flash the mk2 or nb4 tar file.
Sent from my SGH-M919 using XDA Premium 4 mobile app
---------- Post added at 12:56 AM ---------- Previous post was at 12:55 AM ----------
You can get them here: http://forum.xda-developers.com/showthread.php?t=2816508
Sent from my SGH-M919 using XDA Premium 4 mobile app
no nothing about knox.
Fu** yeah!! :fingers-crossed: that looks like it might be the problem. i'll download and post how it goes
Ace$$ said:
no nothing about knox.
Fu** yeah!! :fingers-crossed: that looks like it might be the problem. i'll download and post how it goes
Click to expand...
Click to collapse
If the string "KNOX WARRANTY VOID:" doesn't appear in download mode, then your phone has not been updated to 4.3 or 4.4.2 as android_monsters stated. MDL should have flashed as there was nothing related to the bootloader or KNOX keeping you from a successful flash.
One thing I did encounter myself while trying to re-flash my pre-KNOX device; did you ever update your modem/baseband to MK2 or NB4? If you did, I would recommend finding the individual MDL modem/baseband files and manually reverting them before flashing the stock MDL firmware again. Odin never failed for me at the device .pit file, but I did encounter the firmware upgrade screen while trying to revert to stock with an updated modem. Doesn't make sense to me as the stock firmware has the modem and all in it, but that fixed it for me.
That did the trick all right! :victory: :victory:
Thanks!
SAVED :angel:
I had the same problem but when i tried to flash the lastest firmware its stock on samsung logo... anyone can help me?
Ace$$ said:
That did the trick all right! :victory: :victory:
Thanks!
Click to expand...
Click to collapse
Reverting the modem before flashing the stock firmware fixed your problem? Awesome! :highfive:
Hold the power button and the volume up button and try booting into recovery,
Wipe cache
3 times
Wipe dalvik
3 times
Wipe system
3 times
Reflash rom
1 time
Wipe cache
At least 1 time
Reboot or
Flash gapps
(Only if needed)
If that doesn't help, then maybe try a different rom?
Sent from my GT-I9505G using XDA Free mobile app
Infamous_CA said:
I had the same problem but when i tried to flash the lastest firmware its stock on samsung logo... anyone can help me?
Click to expand...
Click to collapse
I'm assuming you're flashing the stock firmware via Odin... if that's the case, simply factory reset via stock recovery and you should be good to go.
lordcheeto03 said:
I'm assuming you're flashing the stock firmware via Odin... if that's the case, simply factory reset via stock recovery and you should be good to go.
Click to expand...
Click to collapse
I tried but it dosnt show recovery.. I flash a recovery but it dossnt boot on recovery. It show samsung galaxy but the screen turn in black.. I think that maybe it a board problem.
Sent from my HTC One X using XDA Premium 4 mobile app
Infamous_CA said:
I tried but it dosnt show recovery.. I flash a recovery but it dossnt boot on recovery. It show samsung galaxy but the screen turn in black.. I think that maybe it a board problem.
Sent from my HTC One X using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Try re-flashing the stock firmware in Odin. Don't flash a custom recovery at this point, just the stock firmware. Once it passes in Odin, power it off. Hold Power + Volume Up while powering up. It should show the Galaxy S4 screen with "Booting Recovery" in the upper-left.
Yes it say that on blue letters but dosnt show the recovery menu
Sent from my HTC One X using XDA Premium 4 mobile app
Infamous_CA said:
Yes it say that on blue letters but dosnt show the recovery menu
Sent from my HTC One X using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Ah. Well I don't know what to say; perhaps someone else may know? Sorry and good luck.
lordcheeto03 said:
Ah. Well I don't know what to say; perhaps someone else may know? Sorry and good luck.
Click to expand...
Click to collapse
Thanks for ur help man.
Sent from my HTC One X using XDA Premium 4 mobile app
Hello all,
previous searches have yielded limited answers so I apologize if this has been answered already.
I've been running CM for the past 5 or 6 months and have had zero problems with it. Last week however something happened and I got stuck in a boot loop. Me being a genius obviously didn't make a backup of anything so I flashed the stock rom via odin back onto the phone. After flash through odin I get the green light and pass indication. I go to restart the phone in recovery and I get the sick droid with the red yield sign above him. I then go to wipe/factory reset then reboot and it goes as far as the Samsung logo doing its animation and then stops just after and freezes. A regular power up without going into recovery first results in a boot loop.
I tried the recovery process through Kies and get the "This devices version cannot be updated" error. I am running the current version of Kies. I'm assuming its because it knows I've been rooted?
Note 2 Sprint
thank you in advance.
Rhett
eshleman said:
Hello all,
previous searches have yielded limited answers so I apologize if this has been answered already.
I've been running CM for the past 5 or 6 months and have had zero problems with it. Last week however something happened and I got stuck in a boot loop. Me being a genius obviously didn't make a backup of anything so I flashed the stock rom via odin back onto the phone. After flash through odin I get the green light and pass indication. I go to restart the phone in recovery and I get the sick droid with the red yield sign above him. I then go to wipe/factory reset then reboot and it goes as far as the Samsung logo doing its animation and then stops just after and freezes. A regular power up without going into recovery first results in a boot loop.
I tried the recovery process through Kies and get the "This devices version cannot be updated" error. I am running the current version of Kies. I'm assuming its because it knows I've been rooted?
Note 2 Sprint
thank you in advance.
Rhett
Click to expand...
Click to collapse
Which stock version did you flash through odin? Mc2, mk4, or ne2?
Sent from my GT-N7105 using XDA Premium 4 mobile app
jlmancuso said:
Which stock version did you flash through odin? Mc2, mk4, or ne2?
Sent from my GT-N7105 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
ne2
I dont think kies has NE2 yet so you can only use odin. Boot into recovery (stock is fine) and do a factory reset. Then power off (do not reboot) and go into download mode and flash ne2 tar again through odin. Then hopefully you will be able to boot. Note that 4.4.2 is a large rom and will take around 5 mins to actually boot up.
Sent from my GT-N7105 using XDA Premium 4 mobile app
jlmancuso said:
I dont think kies has NE2 yet so you can only use odin. Boot into recovery (stock is fine) and do a factory reset. Then power off (do not reboot) and go into download mode and flash ne2 tar again through odin. Then hopefully you will be able to boot. Note that 4.4.2 is a large rom and will take around 5 mins to actually boot up.
Sent from my GT-N7105 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Thank you for the response,
When I go to wipe/reset I get the dead android with the red triangle. I am assuming there is a fault in my stock recovery. I still went ahead and wiped/reset data and removed battery after, waited a few minutes, inserted battery, booted into download mode, flashed stock ne2, everything with odin passed. I booted phone up and it immediately went into a boot loop with the samsung logo for about 5 minutes then shut off completely. the battery has a full charge.
I'm open for other options if some are available.Would it be possible to skip the stock recovery and go straight into a custom recovery? I'm planning on rooting and installing CM again but obviously making a backup this time.
eshleman said:
Thank you for the response,
When I go to wipe/reset I get the dead android with the red triangle. I am assuming there is a fault in my stock recovery. I still went ahead and wiped/reset data and removed battery after, waited a few minutes, inserted battery, booted into download mode, flashed stock ne2, everything with odin passed. I booted phone up and it immediately went into a boot loop with the samsung logo for about 5 minutes then shut off completely. the battery has a full charge.
I'm open for other options if some are available.Would it be possible to skip the stock recovery and go straight into a custom recovery? I'm planning on rooting and installing CM again but obviously making a backup this time.
Click to expand...
Click to collapse
Use odin to flash philz touch recovery 6.0.7.9.
Sent from my SPH-L900 using XDA Free mobile app
skye206 said:
Use odin to flash philz touch recovery 6.0.7.9.
Sent from my SPH-L900 using XDA Free mobile app
Click to expand...
Click to collapse
Like he said use odin to flash philz 6.07.9 but uncheck reboot option. Once everything is done disconnect and pull battery (this is safe as long as everything finished flashing). Then do recovery key sequence while inserting battery. Then flash your rom. If still having issues with booting I have a special file that you can odin that should fix it.
Sent from my SPH-L900 using XDA Premium 4 mobile app
jlmancuso said:
Like he said use odin to flash philz 6.07.9 but uncheck reboot option. Once everything is done disconnect and pull battery (this is safe as long as everything finished flashing). Then do recovery key sequence while inserting battery. Then flash your rom. If still having issues with booting I have a special file that you can odin that should fix it.
I downloaded the 6.07.09 philz zip file, however I'm having trouble finding the tar.md5 file to flash through odin.
Also, once philz touch recovery is installed can I immediately flash a recent version of CM11 nightly straight from my external SD card?
Thank you,
Rhett
Click to expand...
Click to collapse
Here is a direct link to 6.07.9 tar.md5 https://goo.im/devs/philz_touch/CWM_Advanced_Edition/l900/philz_touch_6.07.9-l900.tar.md5/
Once you flash it boot into recovery and flash cm11. If cm11 wont boot I have another file for you to use but it is only needed if cm11 does not boot.
Sent from my GT-N7105 using XDA Premium 4 mobile app
jlmancuso said:
Here is a direct link to 6.07.9 tar.md5 https://goo.im/devs/philz_touch/CWM_Advanced_Edition/l900/philz_touch_6.07.9-l900.tar.md5/
Once you flash it boot into recovery and flash cm11. If cm11 wont boot I have another file for you to use but it is only needed if cm11 does not boot.
Sent from my GT-N7105 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I really appreciate the help,
I successfully flashed Philz recovery through odin. Booted to recovery and went to wipe/reset for a new rom, then installed zip - CM11 (yesterday's version) flashed successfully, selected reboot, samsung logo flashed and then phone shut off.
Am I rooted automatically if I have Philz recovery? They only thing I can think of is I don't have an OS at all on my device or I am not rooted?
Thank you in advance
eshleman said:
I really appreciate the help,
I successfully flashed Philz recovery through odin. Booted to recovery and went to wipe/reset for a new rom, then installed zip - CM11 (yesterday's version) flashed successfully, selected reboot, samsung logo flashed and then phone shut off.
Am I rooted automatically if I have Philz recovery? They only thing I can think of is I don't have an OS at all on my device or I am not rooted?
Thank you in advance
Click to expand...
Click to collapse
Yeah kind of thought that might happen. Flash the attachment from this (fix.tar) http://forum.xda-developers.com/showpost.php?p=53035491&postcount=287 through odin and it should fix your issue. Also you are not rooted automatically because of Philz. Root is controlled by the rom but almost every custom rom (omni excluded) comes rooted so hope that helps that question.
jlmancuso said:
Yeah kind of thought that might happen. Flash the attachment from this (fix.tar) http://forum.xda-developers.com/showpost.php?p=53035491&postcount=287 through odin and it should fix your issue. Also you are not rooted automatically because of Philz. Root is controlled by the rom but almost every custom rom (omni excluded) comes rooted so hope that helps that question.
Click to expand...
Click to collapse
I'm assuming the fix.tar changes the recovery to CWM? I flashed the fix zip successfully, rebooted, CM logo came on for a couple minutes, I did a happy dance, then the phone shut off again. Pulled battery, turned back on and its stuck in a boot loop now with samsung logo.
eshleman said:
I'm assuming the fix.tar changes the recovery to CWM? I flashed the fix zip successfully, rebooted, CM logo came on for a couple minutes, I did a happy dance, then the phone shut off again. Pulled battery, turned back on and its stuck in a boot loop now with samsung logo.
Click to expand...
Click to collapse
Do a factory reset (normal not clean for new rom) and see what happens.
Sent from my SCH-I605 using XDA Premium 4 mobile app
jlmancuso said:
Do a factory reset (normal not clean for new rom) and see what happens.
Sent from my SCH-I605 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
When I flashed the fix.tar. it changed the recovery to CWM which only gives me the option to wipe data/factory reset, whereas with the philz I had the option to wipe for just a new rom. or a complete reset
Good then you can mix them up. Do the factory reset. Also you sure it is cwm or is it the stock recovery? I have not used that file since 4.4.2 came out but thought it was all stock.
Sent from my SCH-I605 using XDA Premium 4 mobile app
jlmancuso said:
Good then you can mix them up. Do the factory reset. Also you sure it is cwm or is it the stock recovery? I have not used that file since 4.4.2 came out but thought it was all stock.
Sent from my SCH-I605 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Yes, after the fix.tar flash the recovery changed to CWM. However, I'm still having no luck. I tried system wipe/restore then reboot but the phone boots to samsung logo then shuts off. Ill go over the steps I've taken again.
1. Flashed stock recovery through odin - got red triangle above dead android. I'm assuming problem with stock recovery
2. Flashed Philz recovery through odin - did factory reset, flashed current version of CM11, boot, samsung logo comes on then phone shuts off.
3. Flashed fix.tar. through odin.- boot, CM logo comes on like its booting for a minute, then phone shuts off, pull battery, restart phone then goes into a boot loop. wipe data does the same thing. After a couple times of that I'm now at a point where when I reboot from recovery it goes straight to samsung logo then shuts off. Holding the power button (like a regular startup) does nothing. The phone is only responsive to recovery mode and download mode. Not to mention the phone has to be plugged in to either the computer or the wall for any of this to work. Even though the battery indicator says the charge is at 100%.
eshleman said:
Yes, after the fix.tar flash the recovery changed to CWM. However, I'm still having no luck. I tried system wipe/restore then reboot but the phone boots to samsung logo then shuts off. Ill go over the steps I've taken again.
1. Flashed stock recovery through odin - got red triangle above dead android. I'm assuming problem with stock recovery
2. Flashed Philz recovery through odin - did factory reset, flashed current version of CM11, boot, samsung logo comes on then phone shuts off.
3. Flashed fix.tar. through odin.- boot, CM logo comes on like its booting for a minute, then phone shuts off, pull battery, restart phone then goes into a boot loop. wipe data does the same thing. After a couple times of that I'm now at a point where when I reboot from recovery it goes straight to samsung logo then shuts off. Holding the power button (like a regular startup) does nothing. The phone is only responsive to recovery mode and download mode. Not to mention the phone has to be plugged in to either the computer or the wall for any of this to work. Even though the battery indicator says the charge is at 100%.
Click to expand...
Click to collapse
So you can not run on battery power at all? Sounding like a hardware issue. If you know someone else with a note 2 I would try swapping batteries. After that I am not sure what to try.
Sent from my SCH-I605 using XDA Premium 4 mobile app
jlmancuso said:
So you can not run on battery power at all? Sounding like a hardware issue. If you know someone else with a note 2 I would try swapping batteries. After that I am not sure what to try.
Sent from my SCH-I605 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I have a friend that also has a note 2, I'll try his battery this weekend and let you know what happens. Thanks again for all the help.
eshleman said:
I have a friend that also has a note 2, I'll try his battery this weekend and let you know what happens. Thanks again for all the help.
Click to expand...
Click to collapse
A different battery didn't help. I reflashed the stock rom, where I get the original problem of the red exclamation point laying down android screen. Is there a way to rid the download screen of the system status as being displayed as "custom" and the knox warranty void: as 1 with the condition the phone is in? I believe if I can reset the counter and prove it is a hardware problem they will cover it under warranty. If not I believe my only option is to destroy/crush the phone beyond repair and claim the insurance which is $200 to replace the phone.
Can you post the link where you got the stock rom?
Sent from my SPH-L710 using Xparent Cyan Tapatalk 2