O.K So I am new to Android just switched from the apple side of things.... DUN DUN DUN so, this is watsup, I downloaded doin rooted and downgraded firmware to 4.1.1 to unlock phone, well after unlocking phone the 4.3 ota popped up, I was half asleep inadvertanely upgraded now my phone is soft bricked I believe, I can get into download but not recovery, I have spent 3 days trying to figure this out, I have downgraded my firmware and it says pass on odin but then i get stuck in bootloop i'm guessing where it wont go past the "Samsung note 2" screen. please help me! its a very expensive paperweight and now i'm stuck with no phone, please help I have no idea what to do , all I want is a working phone I will get it factory UNLOCKED LOL!, I dont care, I just need help!
JONKEEFE said:
O.K So I am new to Android just switched from the apple side of things.... DUN DUN DUN so, this is watsup, I downloaded doin rooted and downgraded firmware to 4.1.1 to unlock phone, well after unlocking phone the 4.3 ota popped up, I was half asleep inadvertanely upgraded now my phone is soft bricked I believe, I can get into download but not recovery, I have spent 3 days trying to figure this out, I have downgraded my firmware and it says pass on odin but then i get stuck in bootloop i'm guessing where it wont go past the "Samsung note 2" screen. please help me! its a very expensive paperweight and now i'm stuck with no phone, please help I have no idea what to do , all I want is a working phone I will get it factory UNLOCKED LOL!, I dont care, I just need help!
Click to expand...
Click to collapse
I have never had your issue before but I am hoping I'm leading you in the right direction I would Google how to reset back to stock there's a lot of vids on it on YouTube but here's what I think would fix your problem
Sounds like you need to download a factory image go into download mode plug it into Odin and use the factory image to reset it back to normal, word of advise, just root it and learn about ROMs 4.3 is over rated in my opinion 4.4.2 is the newest we have on the aosp side and it is awesome, I highly recommend beanstalk 4.4.2
Also I found this in another post not sure if it applies to you but I'm sure someone else can confirm or deny
"If you update to 4.3...you WILL have a locked bootloader...and currently no good way to root..
Additionally....your KNOX flag will trip and your warranty is toast...if you attempt to root...( as of today, and until the devs can fix Sammy's latest patch)...
Beyond that...you can never go back to 4.1.2 again...
Stay on a 4.1.2 bootloader without KNOX and then you can flash every rom we have along with a full return to stock if you want...
An update to 4.3 will stop any means of going back."
Sent from my GT-N7105 using Tapatalk
No I have done a ton of research and can't figure it out, I feel like i've tried everything. I keep trying to go to stock rom, used Keis, used Odin, Used Heindal, flashed stock recovery roms, flashed stock combo roms, have like 12 counts of custom binary downloads and KNOC WARRANTY VOID : 1 and in download mode in red at the top it says in Odin Mode and then Red in the bottom after it says (in Gray) KNox warranty void: 1 and
AP SWREV A2 it then says in red again unsupported version under those....
Roms? You need a stock image for it to work totally different
Sent from my GT-N7105 using Tapatalk
http://forum.xda-developers.com/showthread.php?t=2581321
HOW-TO Downgrade from 4.3 OFFICIAL MK6 to LJ2 4.1.1
Did you thank your Developer today?
Do not try this!!!!!!!!!!!!!!!!!!!!!!!!!
Jspex said:
http://forum.xda-developers.com/showthread.php?t=2581321
HOW-TO Downgrade from 4.3 OFFICIAL MK6 to LJ2 4.1.1
Did you thank your Developer today?
Click to expand...
Click to collapse
Do NOT try this!!!!
I did, and i bricked my phone!!!!!! You gonna end up with expensive brick. I am noit able to do anything with my phone except for gettinh into download mode, where it says "knox warranty void:1".
Any idea what to do???
fuzio1963 said:
Do NOT try this!!!!
I did, and i bricked my phone!!!!!! You gonna end up with expensive brick. I am noit able to do anything with my phone except for gettinh into download mode, where it says "knox warranty void:1".
Any idea what to do???
Click to expand...
Click to collapse
You did the battery pull part as well? I think the trick is to have your fingers on the buttons first then slide the battery back in to force the recovery but until I try it myself I don't know for sure.
Did you thank your Developer today?
Jspex said:
You did the battery pull part as well? I think the trick is to have your fingers on the buttons first then slide the battery back in to force the recovery but until I try it myself I don't know for sure.
Did you thank your Developer today?
Click to expand...
Click to collapse
Did that right.
I have the same issue..... Had 4.3 ota.... Flashed cwm thru odin. Restarted the phone, it will not boot past the "samsung galaxy note 2" screen. Flashed stock rom thru odin, still stuck at the samsung note 2 screen. I can get into download mode with no issues whatsoever. I cannot get into recovery mode, whether stock or cwm. Nothing. Can I flash another 4.3 or 4.4 rom thru odin? I just need my phone working again..... thanks gentlemen
http://forum.xda-developers.com/show....php?t=2581321
HOW-TO Downgrade from 4.3 OFFICIAL MK6 to LJ2 4.1.1
Do this it works. If it does get stuck on the second Samsung logo pull the battery,
Boot into Stock recovery, and do a factory reset.
It will boot the 4.1.1 stock ROM but it will have the MK6 bootloader. You can flash TWRP or CWM thru ODIN and flash other ROMs. 4.3 ROMs is all I have tried.
I've just spent hours doing this. It's almost impossible to brick this phone. If you do brick it you have done something really really fricking stupid.
I've done a lot of stupid ****, and I have always brought it back to life.
dicksteele said:
http://forum.xda-developers.com/show....php?t=2581321
HOW-TO Downgrade from 4.3 OFFICIAL MK6 to LJ2 4.1.1
Do this it works. If it does get stuck on the second Samsung logo pull the battery,
Boot into Stock recovery, and do a factory reset.
It will boot the 4.1.1 stock ROM but it will have the MK6 bootloader. You can flash TWRP or CWM thru ODIN and flash other ROMs. 4.3 ROMs is all I have tried.
I've just spent hours doing this. It's almost impossible to brick this phone. If you do brick it you have done something really really fricking stupid.
I've done a lot of stupid ****, and I have always brought it back to life.
Click to expand...
Click to collapse
Yup! Fricking stupid------like upgrading from 4.3 to 4.4.1, then in recovery factory reset, and in ODIN trying to get back to 4.1.1 How stupid is that??? If YOU have done this, would you be able to reboot into recovery????? Try it.........
You probably did something wrong. Im the OP of the How to downgrade 4.3 MK6 to LJ2 and Ive done it many time over.
This is the problem i cant get into recovery mode only download, I flashed the firmware from sammobile and did all the steps but it literally wont let me into recovery to wipe the data, I'm stuck on the first samsung Galaxy Note II screen
Have you guys tried to flash cwm or twrp after flashing 4.1.1? Since all you can get into is dl mode try flashing a custom recovery them attempt the battery pull/recovery step.
Did you thank your Developer today?
Jspex said:
Have you guys tried to flash cwm or twrp after flashing 4.1.1? Since all you can get into is dl mode try flashing a custom recovery them attempt the battery pull/recovery step.
Did you thank your Developer today?
Click to expand...
Click to collapse
Agree. Get into DL mode flash TWRP from here.
http://goo.im/devs/OpenRecovery/t0lteatt
It should boot right into recovery.
---------- Post added at 07:31 AM ---------- Previous post was at 07:19 AM ----------
fuzio1963 said:
Yup! Fricking stupid------like upgrading from 4.3 to 4.4.1, then in recovery factory reset, and in ODIN trying to get back to 4.1.1 How stupid is that??? If YOU have done this, would you be able to reboot into recovery????? Try it.........
Click to expand...
Click to collapse
I personally have done it five times in the last two days. Plus ODIN'd MA4.
Actually I've done it the correct way. I have no idea what you are referring to in your post.
From a non-bootable 4.3 OTA, because I installed a mod from the theme/apps section, I flashed the LJ2 in ODIN. It did not boot. I reread the OP and saw that if it didn't boot, do a factory reset.
I flashed it again in ODIN, probably did not need to, it hung.
I pulled battery, did the power/home/up and got to stock recovery. Factory reset it boots.
Testing different scenarios I got boot loops, reflashed LJ2 and did same procedure.
I found out later from Zen all I had to do was flash a recovery and it would fix the error saying I have an error in my firmware, I need to recover using Kies. There was no need for that.
I understand you all can't get to recovery try flashing a custom recovery from ODIN like suggested above.
dicksteele said:
Agree. Get into DL mode flash TWRP from here.
http://goo.im/devs/OpenRecovery/t0lteatt
It should boot right into recovery.
---------- Post added at 07:31 AM ---------- Previous post was at 07:19 AM ----------
I personally have done it five times in the last two days. Plus ODIN'd MA4.
Actually I've done it the correct way. I have no idea what you are referring to in your post.
From a non-bootable 4.3 OTA, because I installed a mod from the theme/apps section, I flashed the LJ2 in ODIN. It did not boot. I reread the OP and saw that if it didn't boot, do a factory reset.
I flashed it again in ODIN, probably did not need to, it hung.
I pulled battery, did the power/home/up and got to stock recovery. Factory reset it boots.
Testing different scenarios I got boot loops, reflashed LJ2 and did same procedure.
I found out later from Zen all I had to do was flash a recovery and it would fix the error saying I have an error in my firmware, I need to recover using Kies. There was no need for that.
I understand you all can't get to recovery try flashing a custom recovery from ODIN like suggested above.
Click to expand...
Click to collapse
I was trying to say: even I have done this step-by-step, after battery pull out, I still canNOT boot into recovery! Even i flashed recovery into my phone via odin, after flashing 4.1.1 It just shows Galaxy Note II screen.......what is it, you are NOT getting??
fuzio1963 said:
I was trying to say: even I have done this step-by-step, after battery pull out, I still canNOT boot into recovery! Even i flashed recovery into my phone via odin, after flashing 4.1.1 It just shows Galaxy Note II screen.......what is it, you are NOT getting??
Click to expand...
Click to collapse
I can honestly say that I will be done trying to help you with this. What YOU are not getting is we are trying to help YOU fix YOUR mistake.
I understand it is frustrating when you hit a snag that leaves your phone in soft brick form but as EVERY OP states you are doing these things AT YOUR OWN RISK. Getting angry and impatient with those that are trying to help will get you nowhere fast.
Good luck fixing your phone and I really hope you get this figured out.
Did you thank your Developer today?
fuzio1963 said:
I was trying to say: even I have done this step-by-step, after battery pull out, I still canNOT boot into recovery! Even i flashed recovery into my phone via odin, after flashing 4.1.1 It just shows Galaxy Note II screen.......what is it, you are NOT getting??
Click to expand...
Click to collapse
I'm getting from every post I have read that you've done in multiple threads, you don't desire any help.
That's what I get.
EDIT : Damn Jspex beat me to it.
EDIT 2: OP, I'll PM you and give you my contact info and see if we can get you going.
As to not let one person ruin the OPs chances of fixing things here is a good way to get into recovery that does take a little know how. Its always good to know the basics of adb anyway when modding android devices.
http://forum.xda-developers.com/showthread.php?t=1853159
Did you thank your Developer today?
Jspex said:
Last resort:
http://forum.xda-developers.com/showthread.php?t=1853159
Did you thank your Developer today?
Click to expand...
Click to collapse
If your device is not being recognized try a different USB port.
Or from the command prompt;
type "adb kill-server"
then type "adb devices", adb will restart on port 5307.
No quotes of course
Related
AT&T Galaxy SIII Bricked While Trying to Flash Back to Stock... Desperate For Help
Had my AT&T Galaxy S III rooted, stock ROM. Was having some issues after rooting so I decided to go back to bone stock, completely unroot so I flashed the I747UCALEM build from these forums on Odin 3.07. Needless to say the phone was held up mid flash, and I got a "FAIL" in Odin. When I tried to reboot the phone, I got a "Firmware upgrade encountered an issue. Please select recovery mode in Kies and try again" When I reboot the phone this comes up and it's almost like a permanent download mode. I tried to reflash in Odin to unbrick the phone and it fails every single time.
Am I completely screwed? If I send it back to Samsung like this they'll see the that I rooted (didnt trip the flash counter) and void my warranty. Not sure what to do here. Thanks for any advice guys.
statusnone said:
Had my AT&T Galaxy S III rooted, stock ROM. Was having some issues after rooting so I decided to go back to bone stock, completely unroot so I flashed the I747UCALEM build from these forums on Odin 3.07. Needless to say the phone was held up mid flash, and I got a "FAIL" in Odin. When I tried to reboot the phone, I got a "Firmware upgrade encountered an issue. Please select recovery mode in Kies and try again" When I reboot the phone this comes up and it's almost like a permanent download mode. I tried to reflash in Odin to unbrick the phone and it fails every single time.
Am I completely screwed? If I send it back to Samsung like this they'll see the that I rooted (didnt trip the flash counter) and void my warranty. Not sure what to do here. Thanks for any advice guys.
Click to expand...
Click to collapse
Sounds like you got a bad file re-download the AT&T software again from here http://forum.xda-developers.com/showthread.php?t=1737848 make sure you have Kies disabled i do think if its running in the background odin won't flash right don't hold me to it.and as long as you can get in download mode you should be able to fix it.also check here http://forum.xda-developers.com/showthread.php?t=1727443
statusnone said:
Had my AT&T Galaxy S III rooted, stock ROM. Was having some issues after rooting so I decided to go back to bone stock, completely unroot so I flashed the I747UCALEM build from these forums on Odin 3.07. Needless to say the phone was held up mid flash, and I got a "FAIL" in Odin. When I tried to reboot the phone, I got a "Firmware upgrade encountered an issue. Please select recovery mode in Kies and try again" When I reboot the phone this comes up and it's almost like a permanent download mode. I tried to reflash in Odin to unbrick the phone and it fails every single time.
Am I completely screwed? If I send it back to Samsung like this they'll see the that I rooted (didnt trip the flash counter) and void my warranty. Not sure what to do here. Thanks for any advice guys.
Click to expand...
Click to collapse
Hmm this actually happened to me first time I tried to root (stupid computer fell asleep mid flash) however I was just able to reenter download mode and flash again, curious though , what did the screen say and where In the flash process did the Odin fail, for Me luckily it was 2/3 of the way through flashing system so I didn't have much to worry about. Though I imagine if it was writing something important like the sbl or somethimg and it failed you might be in trouble . All in all I would say try flashing again a few times maybe the file you downloaded is bad.
bec48 said:
Sounds like you got a bad file re-download the AT&T software again from here http://forum.xda-developers.com/showthread.php?t=1737848 make sure you have Kies disabled i do think if its running in the background odin won't flash right don't hold me to it.and as long as you can get in download mode you should be able to fix it.also check here http://forum.xda-developers.com/showthread.php?t=1727443
Click to expand...
Click to collapse
Downloading the UCALEM build from that link now on my laptop (my PC is notorious for connection issues with this phone, I should of known) and I'll pray for the best. Thank you very much for the help, I'll post back once I'm on my way.
I can't even download either firmwares. The direct downloads stop for some random reason at around 33 MB and there's 0 seeders for the torrent versions. Any other way to get these firmwares? Samsung updates isn't being nice tonight.
statusnone said:
I can't even download either firmwares. The direct downloads stop for some random reason at around 33 MB and there's 0 seeders for the torrent versions. Any other way to get these firmwares? Samsung updates isn't being nice tonight.
Click to expand...
Click to collapse
The update is in Kies as well.
Finally got the update to download, used a different browser. Flashed the new build through Odin and it worked, unbricked the phone. Apparently it is the connection through my regular PC. Thanks for everyones help!
I rooted my phone with GALAXY NOTE 2 Toolkit. It was working fine for few months. Recently I noticed a problem when I tried to reboot it, but I pulled the battery out and after reinserting all went OK. then Next day or two another time when I tried to reboot, I got to the point where I cannot boo the phone anymore. I get to the initial T-MOBILE screen and that's where it gets stuck.
I tried to upload a recent ROM through Odin. It worked fine, no errors, no problems, but when I try to boo the same thing happens.
I also tried to get to the other menu ( Power+Home+VolumeUp). It shows the menu with some options but I'm not sure how can I use those. I treid few things but it does not work.
I need to use the phone for work every day so I am completely stuck and this is critical for me.
I would appreciate any help.
Arthur
SAME HERE!!!
aklisiewicz said:
i rooted my phone with galaxy note 2 toolkit. It was working fine for few months. Recently i noticed a problem when i tried to reboot it, but i pulled the battery out and after reinserting all went ok. Then next day or two another time when i tried to reboot, i got to the point where i cannot boo the phone anymore. I get to the initial t-mobile screen and that's where it gets stuck.
I tried to upload a recent rom through odin. It worked fine, no errors, no problems, but when i try to boo the same thing happens.
I also tried to get to the other menu ( power+home+volumeup). It shows the menu with some options but i'm not sure how can i use those. I treid few things but it does not work.
I need to use the phone for work every day so i am completely stuck and this is critical for me.
I would appreciate any help.
Arthur
Click to expand...
Click to collapse
i have same issue..
I just odin 4.3 file and everything went to okay.. But stuck on samsung galaxy note2..
I did several number and number og count became 7 and knox warranty void 1...
Could go to down or recovery mode and installing roms but stuck...
Also how can i reset the count? Can i install stock image to go back?
Thank you in advance..
go to recovery mode if you can
kim621973 said:
i have same issue..
I just odin 4.3 file and everything went to okay.. But stuck on samsung galaxy note2..
I did several number and number og count became 7 and knox warranty void 1...
Could go to down or recovery mode and installing roms but stuck...
Also how can i reset the count? Can i install stock image to go back?
Thank you in advance..
Click to expand...
Click to collapse
i just figure it out that go back to recovery mode and do factory reset couple time and boot it!!
back up to normal mine...
do odin 4.3 stock image
go back to recovery mode.
wipe cache/factory reset x3
boot it...
one more thing that you can't downgrade to 4.1.2 or..etc.. if odin 4.3 update it..
i think that someone mentioned..be careful..
we need kill the KNOX ON 4.3 UPDATE FILE...
ALL THE TROUBLE COMING FROM THE KNOX...
THANK YOU.
I HOPE THAT IT HELP!!!!.
kim621973 said:
i just figure it out that go back to recovery mode and do factory reset couple time and boot it!!
back up to normal mine...
do odin 4.3 stock image
go back to recovery mode.
wipe cache/factory reset x3
boot it...
one more thing that you can't downgrade to 4.1.2 or..etc.. if odin 4.3 update it..
i think that someone mentioned..be careful..
we need kill the KNOX ON 4.3 UPDATE FILE...
ALL THE TROUBLE COMING FROM THE KNOX...
THANK YOU.
I HOPE THAT IT HELP!!!!.
Click to expand...
Click to collapse
While Knox is a problem, the bootloader is the booger that won't allow return to 4.1.2. Sammy hosed us on that little bit of trickery.
If my wife didn't have a GS3 that I maintain I might have OTA'd. I have been watching their "upgrade" process for a while and knew that there was trouble in the OTA.
It will be painful for a while as people migrate in with problems that have been covered several times. We'll get through it.
Hastily spouted for your befuddlement
Hi all, hope somebody can rescue me!
I have an N7100. It's been running stock ROM 4.1.2 for ages (rooted). I've rooted and loaded ROMs on a fair few devices over the years, but typically by following step-by-step guides - I'm a noob to all intents and purposes.
Last night I decided to upgrade to 4.4.2.
I did it without performing a wipe first.
Backed up apps and settings using Titanium Backup Pro
Downloaded N7100XXUFNE1 from Sammobile (sammobile.com/firmwares/3/?download=32635)
Loaded it via Odin 3.9
It worked, in a fashion, maintaining most of my data and apps etc, but I couldn't get wifi to turn on and I kept getting error messages saying '[App X] could not be loaded'
I decided to bite the bullet and do a factory reset (by booting into recovery).
I still couldn't get wifi to work, but my bootloader had stayed at ME3, so I decided to apply the latest bootloader (ND3) as I read somewhere that this could be the issue (I wasn't overly concerned about Knox as the phone is almost 2 years old now anyway).
I applied it via ODIN again, except loading the file into the 'BL' section rather than the 'AP'.
Since doing that, it's stuck at the boot screen 'Samsung Galaxy Note II GT-N7100' and the only way to get out of it is to pull the battery.
I can got into 'Download Mode' but not into 'Recovery Mode'.
I have tried applying MJ5 bootloader.
I have tried reinstalling the whole stock again ROM again
I have tried applying Philz_Touch_6.07.9-n7100 recovery
All show as having completed successfully in Odin, but none of them changed anything - I'm still stuck at the boot screen
Does anybody have any ideas of what else I might try?
Thanks
Beardy
beardyweirdy said:
Hi all, hope somebody can rescue me!
I have an N7100. It's been running stock ROM 4.1.2 for ages (rooted). I've rooted and loaded ROMs on a fair few devices over the years, but typically by following step-by-step guides - I'm a noob to all intents and purposes.
Last night I decided to upgrade to 4.4.2.
I did it without performing a wipe first.
Backed up apps and settings using Titanium Backup Pro
Downloaded N7100XXUFNE1 from Sammobile (sammobile.com/firmwares/3/?download=32635)
Loaded it via Odin 3.9
It worked, in a fashion, maintaining most of my data and apps etc, but I couldn't get wifi to turn on and I kept getting error messages saying '[App X] could not be loaded'
I decided to bite the bullet and do a factory reset (by booting into recovery).
I still couldn't get wifi to work, but my bootloader had stayed at ME3, so I decided to apply the latest bootloader (ND3) as I read somewhere that this could be the issue (I wasn't overly concerned about Knox as the phone is almost 2 years old now anyway).
I applied it via ODIN again, except loading the file into the 'BL' section rather than the 'AP'.
Since doing that, it's stuck at the boot screen 'Samsung Galaxy Note II GT-N7100' and the only way to get out of it is to pull the battery.
I can got into 'Download Mode' but not into 'Recovery Mode'.
I have tried applying MJ5 bootloader.
I have tried reinstalling the whole stock again ROM again
I have tried applying Philz_Touch_6.07.9-n7100 recovery
All show as having completed successfully in Odin, but none of them changed anything - I'm still stuck at the boot screen
Does anybody have any ideas of what else I might try?
Thanks
Beardy
Click to expand...
Click to collapse
What happens when you try to reflash the stock 4.4.2 firmware via odin that u downloaded?
beardyweirdy said:
Hi all, hope somebody can rescue me!
I have an N7100. It's been running stock ROM 4.1.2 for ages (rooted). I've rooted and loaded ROMs on a fair few devices over the years, but typically by following step-by-step guides - I'm a noob to all intents and purposes.
Last night I decided to upgrade to 4.4.2.
I did it without performing a wipe first.
Backed up apps and settings using Titanium Backup Pro
Downloaded N7100XXUFNE1 from Sammobile (sammobile.com/firmwares/3/?download=32635)
Loaded it via Odin 3.9
It worked, in a fashion, maintaining most of my data and apps etc, but I couldn't get wifi to turn on and I kept getting error messages saying '[App X] could not be loaded'
I decided to bite the bullet and do a factory reset (by booting into recovery).
I still couldn't get wifi to work, but my bootloader had stayed at ME3, so I decided to apply the latest bootloader (ND3) as I read somewhere that this could be the issue (I wasn't overly concerned about Knox as the phone is almost 2 years old now anyway).
I applied it via ODIN again, except loading the file into the 'BL' section rather than the 'AP'.
Since doing that, it's stuck at the boot screen 'Samsung Galaxy Note II GT-N7100' and the only way to get out of it is to pull the battery.
I can got into 'Download Mode' but not into 'Recovery Mode'.
I have tried applying MJ5 bootloader.
I have tried reinstalling the whole stock again ROM again
I have tried applying Philz_Touch_6.07.9-n7100 recovery
All show as having completed successfully in Odin, but none of them changed anything - I'm still stuck at the boot screen
Does anybody have any ideas of what else I might try?
Thanks
Beardy
Click to expand...
Click to collapse
Have you tried flashing TWRP instead? This happened to me and got stuck on recovery boot, CWM and Philz Touch wonb't load. Flashed TWRP and worked like a charm.
I am having similar problem.
Tried to flash the TWRP Recovery from THIS via Odin.
Still phone isn't going past the Galaxy Note II logo.
Sidz4u said:
What happens when you try to reflash the stock 4.4.2 firmware via odin that u downloaded?
Click to expand...
Click to collapse
Thanks for the reply.
It processes OK and Odin says 'Pass!', but then it automatically restarts and gets stuck at the boot screen again. Still can't boot into recovery mode.
AliverMD said:
Have you tried flashing TWRP instead? This happened to me and got stuck on recovery boot, CWM and Philz Touch wonb't load. Flashed TWRP and worked like a charm.
Click to expand...
Click to collapse
Thanks for the suggestion. Just tried that, but unfortunately it just does the same thing ....
Man do this.....
Get older odin (personally my preferance nothing else)
Flash the latest stock rom that u have
It will say pass and the device will go into bootloop
Now remove battery any stick it in (just to stop bootloops)
Enter recovery (that shld be stock now)
And do a factory reset
If no recovery......get a custom one and do it
Then let the phone do its thing:good::good:
---------- Post added at 10:36 AM ---------- Previous post was at 10:32 AM ----------
If u have any wifi or other issues.....flash the new bootloader. ....with AP not the BL...and done....
Hope this helps......cheers:good:
devrog17 said:
Man do this.....
Get older odin (personally my preferance nothing else)
Flash the latest stock rom that u have
It will say pass and the device will go into bootloop
Now remove battery any stick it in (just to stop bootloops)
Enter recovery (that shld be stock now)
And do a factory reset
If no recovery......get a custom one and do it
Then let the phone do its thing:good::good:
---------- Post added at 10:36 AM ---------- Previous post was at 10:32 AM ----------
If u have any wifi or other issues.....flash the new bootloader. ....with AP not the BL...and done....
Hope this helps......cheers:good:
Click to expand...
Click to collapse
Thanks for the suggestion. I've tried doing just that (although not on an older version of Odin) and it hasn't helped, I can't get into recovery.
I will give flashing the Bootloader a go via the AP rather than BL when I get back from work tonight though. Cheers.
beardyweirdy said:
Thanks for the suggestion. I've tried doing just that (although not on an older version of Odin) and it hasn't helped, I can't get into recovery.
I will give flashing the Bootloader a go via the AP rather than BL when I get back from work tonight though. Cheers.
Click to expand...
Click to collapse
Yes try with older odin.......and also flashing bl via AP
Hope it helps......
DO HIT THAT THANKS BUTTON IF U FEEL I TRIED TO HELP U......
devrog17 said:
Yes try with older odin.......and also flashing bl via AP
Hope it helps......
DO HIT THAT THANKS BUTTON IF U FEEL I TRIED TO HELP U......
Click to expand...
Click to collapse
Just tried, but to no avail again. Thanks anyway. Anybody else got any suggestions as to what I might try? I'm starting to lose hope a bit here
Try to boot in recovery and do a factory reset
devrog17 said:
Try to boot in recovery and do a factory reset
Click to expand...
Click to collapse
Hi, I do appreciate you're only trying to help but, as explained numerous times in the thread, that's my whole problem.
In summary:
The phone gets stuck on the boot screen
I can't boot into recovery
I can only get into the odin download screen
Flashing a full stock rom doesn't change anything
Flashing Philz, TWRP or CW Recovery doesn't change anything
Reflashing the bootloader doesn't change anything
C
beardyweirdy said:
Hi, I do appreciate you're only trying to help but, as explained numerous times in the thread, that's my whole problem.
In summary:
The phone gets stuck on the boot screen
I can't boot into recovery
I can only get into the odin download screen
Flashing a full stock rom doesn't change anything
Flashing Philz, TWRP or CW Recovery doesn't change anything
Reflashing the bootloader doesn't change anything
Click to expand...
Click to collapse
Just to close this thread off, I've now paid to get the phone sorted at a local shop. Took them a while (think their first level support just tried all the things I'd already done), but their occasional staff member and all round guru managed to get it sorted. I don't know what he did as I didn't get the chance to speak to him. Cost me £30.
Hi everyone
Long time xda follower, newly registered, since I needed to ask a Q.
I rooted and switched to Lollipop on my ATT S3 (i747) a few months ago, Lately, I've started noticing battery issues as well as network issues with this ROM. I figure it is time for me to go back to stock.
However, if I remember correctly, when I tried previously the phone refused to downgrade back to stock. Kies was helpless because the trip counter had been reset (or something similar).
Please, is there a good how-to on downgrading this phone from Lollipop back to stock? If yes, would someone please point me to it?
Much thanks in advance.
lsiravi
Hmm.. I am going to give this a try:
http://forum.xda-developers.com/galaxy-s3/general/fix-s3-to-factory-unroot-stock-recovery-t2323847
lsiravi said:
Hi everyone
Long time xda follower, newly registered, since I needed to ask a Q.
I rooted and switched to Lollipop on my ATT S3 (i747) a few months ago, Lately, I've started noticing battery issues as well as network issues with this ROM. I figure it is time for me to go back to stock.
However, if I remember correctly, when I tried previously the phone refused to downgrade back to stock. Kies was helpless because the trip counter had been reset (or something similar).
Please, is there a good how-to on downgrading this phone from Lollipop back to stock? If yes, would someone please point me to it?
Much thanks in advance.
lsiravi
Click to expand...
Click to collapse
lsiravi said:
Hmm.. I am going to give this a try:
http://forum.xda-developers.com/galaxy-s3/general/fix-s3-to-factory-unroot-stock-recovery-t2323847
Click to expand...
Click to collapse
Nope! No go!!
Triangle away reset the counter.
The stock recovery works well. I was able to boot to recovery and wipe the data and all that.
Odin says "SW Revcheck Fail" when trying to download the stock rom.
I rebooted into Lollipop, downloaded Triangle away again and reset the counter. Still Odin fails with the same message.
I tried flashing ROM first then the recovery as it was suggested in that link. Nope. Again "SW Revcheck fail". For the record, my SWREV appears to be 3. It is supposed to be 0. Triangle Away does NOT reset this. It did reset another counter (as reported by Triangle away itself - was 5, got reset to 0).
I remember *this* was the problem previously as well, hence the original Q:
How *do* you get back to stock from Lollipop on the Galaxy S3/ATT?
Meanwhile, although Keis failed to recognize the device, I tried to run a firmware recovery manually. It took a long time and in the end failed. It also messed up the recovery, so I had to flash CW again to make it bootable. I'm still back up with Lollipop at this point, but I don't want Lollipop.
Anyone anything else I can do? Any other guide out there to downgrade?
Thanks again
L
The thread you linked is for the international version of the s3.
Before flashing anything else, you need to confirm the bootloader on your phone to ensure that you don't flash anything that attempts to change the bootloader if your bootloader is mjb or newer.
audit13 said:
The thread you linked is for the international version of the s3.
Before flashing anything else, you need to confirm the bootloader on your phone to ensure that you don't flash anything that attempts to change the bootloader if your bootloader is mjb or newer.
Click to expand...
Click to collapse
Right. I finally figured it out.
First the 4.1.1 FWs weren't flashing (in other words SW REV CHK FAIL) was basically indicating that my Bootloader was far ahead of the 4.1.1. I dropped 4.1 after I figured that part out.
Next, I tried to flash a 4.4 (UCUFNE-rooted-odex is available as a zip-flash) through CWR, which didn't work (no boot, stuck at splash).
Next I got hold of a 4.3 (UCUEMJB-2024954-REV04-user-low-ship), which successfully flashed through Odin (repartition checked), but there was no sound, IMEI indicated null. Service Mode yielded a blank screen.
I flashed TWRP through Odin (was working on CWR since the beginning) and then flashed the UCUFNE-rooted-odex above on top of 4.3 through TWRP, which was successful, still no sound/IMEI/service mode.
Finally I got hold of the UCUFNE-Modembaseband zip (a small one - 20MB) and flashed that through TWRP. Both sound and IMEI came back.
I'm at 4.4.2 now, but an OTA update from ATT failed (probably because it went through TWRP)
Now I'm back to stock, albeit rooted ROM (because of the Rooted-Odex 4.4 flash), but I am a happy camper.
Thanks to XDA for various bits of info here and there. But essentially *this* is how you go back to stock from Lollipop.
L
Or... "How I was dumb".
I have a Sprint Note 4 (SM-910P) that I have had rooted for the past few months. I got interested in the new update that was release this month, so I flashed back to stock, ran the updates, and re-rooted over the weekend. I also decided to activate that new "Reactivation Lock" feature (you can see where this is going).
So it occurred to me that I had not reinstalled Cerberus, so downloaded the APK and went to boot into recovery so I could install it to root. I forgot to turn off my "Reactivation Lock", so it booted to a black screen with a yellow triangle and the message: "Custom Binary blocked by Reactivation Block. Secure Fail: Recovery". Pressing the power button turns the phone off. Trying to boot into recovery produces the same error. I can still boot into download mode.
I have been doing some research on how to fix this, and have found two suggested fixes, neither of which work for me:
Fix 1 tells me to boot into download mode, pull the battery, reinsert the battery, and the phone should boot up normally. This doesn't work.
Fix 2 tells me to boot into download mode, and flash to stock with Odin. I have downloaded the stock .tar and tried to flash it with Odin 3.10. I get a fail message. (Full Disclosure: I have only tried Fix 2 on my work test PC. It is an old Vista box that is very slow. I don't know if that is a contributing factor.)
I was hoping that some of you folks had some advice for me. I have all of my data backed up, so I'm not worried about starting over with a clean slate. I'm also not worried about tripping KNOX. That ship has sailed at this point. I just want my phone back.
thescreg said:
Or... "How I was dumb".
I have a Sprint Note 4 (SM-910P) that I have had rooted for the past few months. I got interested in the new update that was release this month, so I flashed back to stock, ran the updates, and re-rooted over the weekend. I also decided to activate that new "Reactivation Lock" feature (you can see where this is going).
So it occurred to me that I had not reinstalled Cerberus, so downloaded the APK and went to boot into recovery so I could install it to root. I forgot to turn off my "Reactivation Lock", so it booted to a black screen with a yellow triangle and the message: "Custom Binary blocked by Reactivation Block. Secure Fail: Recovery". Pressing the power button turns the phone off. Trying to boot into recovery produces the same error. I can still boot into download mode.
I have been doing some research on how to fix this, and have found two suggested fixes, neither of which work for me:
Fix 1 tells me to boot into download mode, pull the battery, reinsert the battery, and the phone should boot up normally. This doesn't work.
Fix 2 tells me to boot into download mode, and flash to stock with Odin. I have downloaded the stock .tar and tried to flash it with Odin 3.10. I get a fail message. (Full Disclosure: I have only tried Fix 2 on my work test PC. It is an old Vista box that is very slow. I don't know if that is a contributing factor.)
I was hoping that some of you folks had some advice for me. I have all of my data backed up, so I'm not worried about starting over with a clean slate. I'm also not worried about tripping KNOX. That ship has sailed at this point. I just want my phone back.
Click to expand...
Click to collapse
You updated to oe1. You need to get someones oe1 backup. As far as the lock out. Im not sure. I believe you can fix it from samsung site login to the device lock page? Not even sure it exists. But once you boot you should have the security option to enter your credentials. So just look on the thread about oe1 update. Someone posted a backup.
Sent from my SM-N910P using XDA Free mobile app
Well think ice broken through the oem bs i got 3 devs looking it a workaround the get ofin up
I FIXED IT!
Here is what I did. I got home, and reread some of the stuff that I found. I was going through a step-by-step provided by Xharky.
http://forum.xda-developers.com/showpost.php?p=53920665&postcount=25
Xharky said that it didn't really matter what you flashed in Odin, that you would probably get an error and that the phone would boot normally after a battery pull. So when I tried flashing the stock .tar with Odin 3.10, it failed, but the phone didn't boot back up; wrote off that fix.
When I got home, I sat down and thought it all out. Odin 3.09 has never worked well for me, and I had never used 3.10 before today. However, I haven't had any problems with Odin 3.07. So I fired it up, and flashed CF Auto Root. Sure enough, I got a fail result in Odin. I did a battery pull and rebooted... And my phone booted right up. I promptly got into my security settings and deactivated that damn Reactivation Block.
thescreg said:
I FIXED IT!
Here is what I did. I got home, and reread some of the stuff that I found. I was going through a step-by-step provided by Xharky.
http://forum.xda-developers.com/showpost.php?p=53920665&postcount=25
Xharky said that it didn't really matter what you flashed in Odin, that you would probably get an error and that the phone would boot normally after a battery pull. So when I tried flashing the stock .tar with Odin 3.10, it failed, but the phone didn't boot back up; wrote off that fix.
When I got home, I sat down and thought it all out. Odin 3.09 has never worked well for me, and I had never used 3.10 before today. However, I haven't had any problems with Odin 3.07. So I fired it up, and flashed CF Auto Root. Sure enough, I got a fail result in Odin. I did a battery pull and rebooted... And my phone booted right up. I promptly got into my security settings and deactivated that damn Reactivation Block.
Click to expand...
Click to collapse
Awesome bro. Thats what i like to hear. A true android heart. Im on the "beat the OE1" task in my head. Im running options and scouring. Lol.
Sent from my SM-N910P using XDA Free mobile app
Yea i beat oe1 also i downgraded
pbedard have you successfully downgraded from the OE1 update back to NK2 or OB7? I took the OE1 update two days after it came out. I didn't research it didn't make a nandroid like an idiot after I updated to OE1. Once I took it I decided I didnt like it so I Odin'd the official NK2 tar it failed then i proceeded to boot twrp recovery restore my NK2 backup I had before I odin'd the offical OB7 tar to take the OE1. Then we have Bootloop. I managed to flash the bobcat rom only I didnt flash the separate theme zip with it like you're supposed to but it's been working for now, not without bugs and a fc of apps every now and then. In my about device it states software OE1, baseband OE1, android version 4.4.4, kernel version 3.10.5-AELKernel-v5.5, and build number KTU84P.N910PVPU1ANK2. I'm guessing I'm just going to have to wait until the OE1 tar is out and just deal with the stockness of it until devs get their OE1 roms out. Thanks in advance if you have any input or thoughts on this depressing matter.
I got a new phone now from sprint i made it look like a softwsre issue
pbedard said:
I got a new phone now from sprint i made it look like a softwsre issue
Click to expand...
Click to collapse
How did you get a stock recovery. Store tried to factory reset mines and when they saw TWRP they new it was rooted, so vioded. If I can get stock recovery then i can fool them, lol. If you have any let me know, thanks in advance.
I backed it up with flashify
---------- Post added at 04:48 AM ---------- Previous post was at 04:47 AM ----------
If u know gow to use it ill give u a copy im not responsible thoigh if u hurt your device
I'd be willing to try it. I know exactly what store to take it too.
christophfloor said:
I'd be willing to try it. I know exactly what store to take it too.
Click to expand...
Click to collapse
Careful. A neighbor of mine did this once. Took about a month. His replacement after a couple of weeks stopped getting signal. He called the carrier and they said the phone he sent in was found flagged by asurion. Which they sent a note to his account. So his new phone was blacklisted until he paid for the brick. Take caution. They are catching on. Not saying this will surely happen but if people keep brick returning this will only get worse. Just a heads up. I have never returned a brick but I have returned rooted.
Sent from my SM-N910P using XDA Free mobile app
flynhawn2002 said:
How did you get a stock recovery. Store tried to factory reset mines and when they saw TWRP they new it was rooted, so vioded. If I can get stock recovery then i can fool them, lol. If you have any let me know, thanks in advance.
Click to expand...
Click to collapse
Well, here's a link to a flashable stock recovery zip for OB7 that I put together for you if it would help.
It is what it is... Flash at your own peril ...
RE-EDIT:
OB7 Stock Recovery Here
This IS a flashable ZIP
I'm still looking for the OE1 OTA update zip... Anyone have it?