Alright so first off don't know if I should be posting this here. Anyway. I tried to Change my recovery messed up and my phone got bricked. So I went back to stock 4.1.1 and worked fine. Did the updates but when it got to 4.1.2 it dowloaded it and installed it but when it went to boot up it keep on flashing samsung galaxy note 2 boot logo. So I try to flash it again but this time it gets to the nand write start on odin and keeps on failing. Someone please help me I'm stumped on this one
Are you having a problem with not getting a no you Verizon update if not try doing that download with Odin and it may fix it but if you can do a factory reset do that before installing an update or anything
Related
I recently just bricked my phone and I recovered following this " http://forum.xda-developers.com/showthread.php?t=1457458 "
but i bricked it again and this guide doesn't seem to help me and i need help fixing my phone again... i've tried almost everything i know of.. i looked up xda and can't find much about where im at...
i recently installed ICS stock firmware and installed dorimanx kernel rooted and CWM with speedmod and installed nightlykang's CM10... there were some bugs in the CM10 like i lost all my contacts no drop menu and such so i tried reflashing... after reflashing my phone just bricked.. so i tried flashing a stock firmware 4.0.4 ics i had and it failed... now i've been stuck in firmware upgrade encountered an issue please select recovery mode in kies and try again... i tried flashing a gingerbread and it didn't work... at 1 point my phone some how went into recover mode and i was able to get my phone working but it woudln't read my SIM card.. even though it was in, i took it out and plugged it back in and no luck... so i reflashed and back to the same stage... help please...!
Why have you got 3 threads about basically the same thing running concurrently.
Your time would be better spent reading the rules and searching........than spamming.
i was trying to remove the rom from my phone to test something out to compare it to regular android 4.1 which just came out for at&t. i hit factory wipe/reset, noticed that didn't remove it, so i downloaded rom manager, flash cwm recovery, and then did format/system. now the phone always gets stuck on the Samsung GALAXY SIII screen and won't even start up! i can turn it off but when i start it up again it gets stuck. i can't get into recovery mode either. kies won't work. please help me!!!
lotamaster said:
i was trying to remove the rom from my phone to test something out to compare it to regular android 4.1 which just came out for at&t. i hit factory wipe/reset, noticed that didn't remove it, so i downloaded rom manager, flash cwm recovery, and then did format/system. now the phone always gets stuck on the Samsung GALAXY SIII screen and won't even start up! i can turn it off but when i start it up again it gets stuck. i can't get into recovery mode either. kies won't work. please help me!!!
Click to expand...
Click to collapse
Well first off even if it did work trying to flash anything from kies would leave you in a bootloop. Running a custom roms kills the ability to update that way without going back to stock. Doing a factory reset does not remove a custom rom from the device. Reflash the rom and then boot up.
I'm having strange problems with an I9300 I'm trying to fix for friend. Now unfortunately I end up doing things like this not because I know anything about these things, but because I'm I'm slightly more computer literate than the rest of my group of friends, so I'll apologise now if these are stupid questions, I have searched but could find nothing.
Now last night my friend comes to mine with his phone stuck in a boot loop. Now beyond the fact it already had a custom ROM on it I can tell you nothing except he claims he installed AVG and it happened. So I reboot into Windows, start up Kies, and see what I can do. Which so far has been:
1) Try to perform an Upgrade and Initialisation. Jump through the hoops, end up with the message "This device's version cannot be updated."
2) Ok, that didn't work. Hit sammobile to find a stock rom and fire up Odin. Ohh success...
3) Oh noes, too soon. The Samsung chime cuts off early and it's stuck with a pulsating logo.
3) Ok well maybe a downgrade first? Get a 4.1 stock rom and try again. Odin sees no problems again, the chime plays fully. But nope, it's just a longer boot loop.
4) After much head scratching and just trying random stuff I end up finding CM9.1 will boot fully, but the EFS data is screwed. This is the only rom I've found so far that will boot.
So from where I started I'm closer and if the radio worked this would be fine. Now the only suggestion I've heard to get the radio working is flashing a stock rom through Kies but I have no idea how to get Kies to play along. Any ideas?
Thanks.
Your downgrade screwed the efs, flash 4.3 and pray it is still readable.
Your mistake was to not factory reset after the first Odin flash.
123c
boomboomer said:
Your downgrade screwed the efs, flash 4.3 and pray it is still readable.
Your mistake was to not factory reset after the first Odin flash.
Click to expand...
Click to collapse
I did actually try that before flashing 4.3 with Odin and after. Was still stuck in a boot loop... :/
Thanks
I rooted my wife's phone last week using KingRoot and the Super-sume. Installed Titanium Backup and everything was working fine. She was given a notice to take an OTA update today which she did. Now the phone is stuck on the Samsung screen with the unlocked padlock. When I boot into recovery, it automatically tries to install the update, but gets an error. It then reboots and just hangs up on the Samsung Custom screen again.
How can I get this back to stock?
I can get into ODIN mode if that helps.
I found this thread and downloaded the pit file at the bottom for the Verizon version. Is this what I want to flash with ODIN? Will this fix the issue?
http://forum.xda-developers.com/showthread.php?t=2265477
So after more reading I don't think that will work as the phone was on OCT I think. It was on 5.0.1. I can't get it past the Samsung screen so I can't check.
Can someone please help....my wife is ready to kill me!!!!!!!
Nevermind. I figured it out. I found stock 5.0.1 firmware and was able to install it using ODIN. Working perfectly now.
So the first thing was I rooted a Samsung S4 SGH-M919.
I used Chainfire's files and Odin. it worked just fine.
Gave the phone to my wife but the firmware 4.4.2 was clearly outdated that none of the apps she played worked, everything just froze on her or crashed.
So I decided to install a custom rom, this led me to Imperium Lollipop 5.0.1
Well that in turn made the phone unbootable. It would continuously go into these 4 circular swirling balls and get stuck there. I cant even get into Recovery Mode. Only Download Mode.
So this made me do some searching and I dl'ed SGH-M919 stock firmware 4.2.2
I used Odin to flash that and it failed.
So now the phone boots into a screen that telling me to uses Kies to fix the issue.
I'm at a loss what to do next.
Can someone give me the necessary steps to fix the phone and where I intended to go with this?
Much appreciated. thanks.
catheapp said:
So the first thing was I rooted a Samsung S4 SGH-M919.
I used Chainfire's files and Odin. it worked just fine.
Gave the phone to my wife but the firmware 4.4.2 was clearly outdated that none of the apps she played worked, everything just froze on her or crashed.
So I decided to install a custom rom, this led me to Imperium Lollipop 5.0.1
Well that in turn made the phone unbootable. It would continuously go into these 4 circular swirling balls and get stuck there. I cant even get into Recovery Mode. Only Download Mode.
So this made me do some searching and I dl'ed SGH-M919 stock firmware 4.2.2
I used Odin to flash that and it failed.
So now the phone boots into a screen that telling me to uses Kies to fix the issue.
I'm at a loss what to do next.
Can someone give me the necessary steps to fix the phone and where I intended to go with this?
Much appreciated. thanks.
Click to expand...
Click to collapse
Are you sure that you have the right bootloader installed for the lollipop rom? Did you factory reset before installing custom rom? Try to wipe davlik after installation completes before restarting device. Also follow the instructions given by the rom thread op.